1270345569 J * ktwilight__ ~keliew@202.48-240-81.adsl-dyn.isp.belgacom.be 1270345849 Q * ktwilight_ Ping timeout: 480 seconds 1270346447 J * derjohn_foo ~aj@e180194247.adsl.alicedsl.de 1270346878 Q * derjohn_mob Ping timeout: 480 seconds 1270348156 J * infowolfe ~infowolfe@c-71-236-152-35.hsd1.or.comcast.net 1270348679 Q * derjohn_foo Ping timeout: 480 seconds 1270349258 Q * jfs Quit: Quitte 1270350063 J * SauLus_ ~SauLus@c192018.adsl.hansenet.de 1270350469 Q * SauLus Ping timeout: 480 seconds 1270350469 N * SauLus_ SauLus 1270351358 M * Bertl off to bed now ... have a good one everyone! 1270351371 N * Bertl Bertl_zZ 1270358443 J * petzsch ~markus@p4FF45D75.dip.t-dialin.net 1270360365 Q * petzsch Quit: Leaving. 1270361534 J * derjohn_mob ~aj@e180195181.adsl.alicedsl.de 1270363230 Q * derjohn_mob Ping timeout: 480 seconds 1270365634 J * ghislain ~AQUEOS@adsl2.aqueos.com 1270366142 J * dna ~dna@p54BC813E.dip0.t-ipconnect.de 1270368274 J * derjohn_mob ~aj@pD95FDBB4.dip.t-dialin.net 1270370634 J * bonbons ~bonbons@2001:960:7ab:0:2c0:9fff:fe2d:39d 1270373069 J * pdilung ~dilung@p54977434.dip.t-dialin.net 1270373122 M * pdilung Hollow: Thanks for commiting Gentoo's 309861 to CVS 1270373372 M * pdilung Hollow: Also, util-vserver-0.30.216_pre2883 works nice and mounts the CGROUPS infrastructure. I've made an ebuild for that. 1270373399 M * pdilung Hollow: works out of the box, so far 1270373461 M * pdilung Hollow: I'll try out features such as build, clone and if it will work the ebuild will be filed to Gentoo's bugzilla 1270374056 J * ghislain1 ~AQUEOS@adsl2.aqueos.com 1270374107 J * derjohn_foo ~aj@pD95FDBB4.dip.t-dialin.net 1270374115 Q * derjohn_mob Read error: Connection reset by peer 1270374366 Q * ghislain Ping timeout: 480 seconds 1270375353 Q * derjohn_foo Ping timeout: 480 seconds 1270375478 Q * pdilung Quit: leaving 1270375720 J * nhOmega ruskie@goatse.co.uk 1270378043 Q * ruskie Quit: Caught sigterm, terminating... 1270378043 N * nhOmega ruskie 1270378098 N * ruskie nhOmega 1270378103 N * nhOmega ruskie 1270378343 J * derjohn_foo ~aj@e180195181.adsl.alicedsl.de 1270378446 J * pdilung ~pdilung@b7.ivosoft.sb.cust.gts.sk 1270380036 J * __mart ~mart@122-62-16-132.jetstream.xtra.co.nz 1270380318 Q * __mart Remote host closed the connection 1270381179 Q * FireEgl Ping timeout: 480 seconds 1270382329 J * FireEgl FireEgl@173-16-9-10.client.mchsi.com 1270385545 Q * derjohn_foo Ping timeout: 480 seconds 1270386006 J * BenG ~bengreen@cpc2-aztw22-2-0-cust521.aztw.cable.virginmedia.com 1270386025 Q * BenG 1270389949 J * petzsch ~markus@p4FF47351.dip.t-dialin.net 1270391767 Q * petzsch Quit: Leaving. 1270392625 J * petzsch ~markus@p4FF47351.dip.t-dialin.net 1270393498 N * Bertl_zZ Bertl 1270393502 M * Bertl morning folks! 1270393827 M * petzsch good morning Bertl 1270396340 M * Bertl off for dinner now ... bbl 1270396345 N * Bertl Bertl_oO 1270397946 N * Bertl_oO Bertl 1270397951 M * Bertl back now ... 1270398472 J * balbir ~balbir@122.172.5.119 1270398483 M * pdilung morning Bertl ;) 1270398498 M * Bertl hey, how's going? 1270398909 Q * fosco Remote host closed the connection 1270398959 J * fosco fosco@marx.wirefull.org 1270399836 J * yarihm ~yarihm@207-35-239-77-pool.cable.fcom.ch 1270399895 M * pdilung Bertl: finished my work @ work and now going home ;) 1270400271 Q * pdilung Quit: leaving 1270403438 Q * yarihm Quit: Leaving 1270403802 Q * dna Quit: Verlassend 1270403959 Q * petzsch Quit: Leaving. 1270408508 J * petzsch ~markus@p4FF47351.dip.t-dialin.net 1270409360 J * ntrs ~ntrs@LNeuilly-152-21-3-238.w193-253.abo.wanadoo.fr 1270409536 J * pdilung ~dilung@p54977434.dip.t-dialin.net 1270409775 J * nick125 ~nick@router-gw1.net.nick125.com 1270409809 M * nick125 Good afternoon everyone. 1270410950 M * nick125 I was wondering if anyone here was running VServer on Ubuntu Karmic or Lucid...just wondering what your experiences are with it. 1270411038 M * Bertl probably some folks are 1270411056 M * Bertl the host distro is not that important for Linux-VServer 1270411177 M * nick125 Well, I was hoping to use their packages... 1270411208 M * Bertl well, what packages do they have :) 1270411246 M * nick125 kernel/utilities 1270411268 M * Bertl yeah, I presumed that, but what versions? 1270411285 M * nick125 let me check 1270411348 M * nick125 util-vserver: 0.30.216~r2842-2ubuntu2 1270411354 Q * petzsch Quit: Leaving. 1270411361 M * Bertl not the latest, but looks good 1270411426 M * nick125 Right now, I'm using Xen, but I'm looking for something that's easier on resource consumption. 1270411454 M * Bertl and you don't need full virtualization, I presume? 1270411506 M * nick125 Not really. 1270411522 M * Bertl well, then Linux-VServer is the way to go :) 1270412000 M * nick125 So, are there any benchmarks in regards to guest performance? 1270412065 M * Bertl we did a bunch of benchmarks some time ago, basically you run at host performance or faster 1270412099 M * Bertl the more similar guests you are running, the better it gets 1270412111 M * Bertl (because they can share certain resources) 1270412120 M * nick125 What kind of resources? 1270412154 M * Bertl if you use unification, they share read only filesystem parts, which in turn results in shared inode caches and page mappings 1270412177 M * nick125 Almost like a COW? 1270412191 M * Bertl yes 1270412214 M * nick125 What happens if you update the "base" image? Does it break things? 1270412246 M * Bertl there is no 'base' image 1270412263 M * Bertl i.e. unification uses hard links with certain properties 1270412284 M * Bertl when they diverge, a copy is created, on a regular basis you re-unify the guests 1270412373 M * nick125 Hmm. That seems pretty cool. All of my VMs are Ubuntu, so that could save quite of disk space, right? 1270412519 M * Bertl disk space, inode caches and thus memory 1270412630 M * nick125 How much of an impact does that have on I/O performance? 1270412663 M * Bertl shared (hardlinked) files also cause less I/O 1270412742 M * Bertl of course, with a high number of guests, I/O is the first bottleneck you'll encounter anyways 1270414134 M * Bertl so, if you plan to run 50+ guests, you'd better make sure that I/O is fast and memory available :) 1270414177 M * nick125 I only have 3 guests at the moment, so that shouldn't be an issue. It's a little 2.6ghz Celery box with 1.5GB of RAM. 1270414380 M * Bertl should be fine then 1270415369 A * nick125 looks for a kernel that'll work.. 1270415390 M * Bertl 2.6.33.x should be fine 1270416984 Q * ntrs Ping timeout: 480 seconds 1270417285 M * nick125 I'm a bit lazy, so I'm looking for a precompiled package ;) 1270417318 M * nick125 Are there still issues with vserver/upstart, or are those resolved? 1270417364 M * Bertl if the guest is set up properly, it should work 1270417389 M * nick125 What kind of steps need to be taken to setup a guest "properly?" 1270417475 M * Bertl http://linux-vserver.org/Upstart_issues 1270417508 M * nick125 So those steps are still applicable...okay. 1270417562 M * Bertl some of them, I haven't followed the upstart development 1270417606 M * Bertl IIRC, upstart coredumps when certain conditions are not met 1270417619 M * nick125 That's always fun. 1270417646 M * Bertl yeah, we had a long talk with the upstart developer here, he promised to fix them sooner or later 1270417735 Q * jrklein Quit: jrklein 1270417766 M * nick125 So, for the guest FS, right now, I'm using LVM with an LVM volume for each VM. Would that be a recommended way for VServer, or is some other configuration better? 1270417811 M * Bertl you can do that, but you won't benefit from unification that way 1270417821 M * Bertl still for 3 guests it doesn't matter that much 1270417939 M * nick125 My plans are to reinstall everything on my server, so I'm open to changes. 1270418128 M * Bertl you can migrate smoothly, i.e. start with the images you have, just clean them up 1270418129 M * nick125 (I'm planning on trying everything out in VBox first, just to make sure everything works) 1270418160 M * Bertl once you know what you are doing and what you want, migrate to new, probably unified guests 1270418287 M * nick125 I don't care too much about the guests, they're a few releases old and it's going to be a pain to upgrade them...so I'm open to options on those. 1270418325 M * Bertl well, whatever you prefer, usually consolidation works like this: 1270418350 M * Bertl setup the host system, make sure it works fine and you can create e.g. the debian guest via network 1270418375 M * Bertl create skeleton guests for each existing system (virtual or real) 1270418406 M * Bertl copy over the filesystem data to the skeleton guests, clean them up (remove dangerous devices) 1270418420 M * Bertl then start them, and thus replace the 'original' system 1270418462 M * Bertl with that done, create a new guest for each consolidated guest, adjust the settings and test according to your requirements 1270418467 M * nick125 Well, as far as how to setup disks goes, what's the best way for VServer? as in, most efficient use of resource, highest I/O, etc. 1270418512 M * Bertl I'd go for high performance and redundancy, so probably soft raid over 2 or 3-4 disks 1270418539 M * Bertl lvm is fine for maintaining 2-3 partitions 1270418553 M * Bertl one for the active guests, one for testing and a third one for backup 1270418558 M * nick125 I have RAID-5 over 3 disks at the moment. Would you put all of the guests on the same partition/LVM volume/FS or individual ones? 1270418559 M * Bertl (but YMMV) 1270418919 M * harry nick125: if you put them on several partitions, that means several different filesystems 1270418927 M * harry so that would disable the use of unification 1270418946 A * harry off to bed now 1270419055 Q * bonbons Quit: Leaving 1270419189 J * jfst ~jfs@ip-83-134-219-169.dsl.scarlet.be 1270419471 Q * nick125 Quit: WeeChat 0.3.0 1270422367 Q * ghislain1 Quit: Leaving.