1375922596 Q * fback Ping timeout: 480 seconds 1375922786 J * fback fback@red.fback.net 1375927784 Q * SteeleNivenson Quit: Leaving 1375938942 J * Fog_Watch ~ian@21.55.70.115.static.exetel.com.au 1375939739 M * Bertl_oO off to bed now ... have a good one everyone! 1375939744 N * Bertl_oO Bertl_zZ 1375940021 Q * Fog_Watch Remote host closed the connection 1375940693 Q * fback Read error: Connection reset by peer 1375940694 J * fback fback@red.fback.net 1375940956 J * Fog_Watch ~ian@21.55.70.115.static.exetel.com.au 1375941244 M * Fog_Watch I'm wanting to allocate cores to guests and the host. A couple of days ago Bertl suggested cpusets for this. Bearing in mind I'm on Gentoo 3.9, is this best explained in /usr/src/linux/Documentation/cgroups/cpusets.txt? 1375943135 Q * fback Ping timeout: 480 seconds 1375944835 J * fback fback@red.fback.net 1375945395 J * BenG ~bengreen@cpc35-aztw23-2-0-cust207.18-1.cable.virginmedia.com 1375946001 Q * fback Ping timeout: 480 seconds 1375946630 M * daniel_hozac yes 1375947093 M * Fog_Watch Interesting. I think I might be getting somewhere with this. 1375947146 M * Fog_Watch I'm up to addressing such errors as the following when I start a guest: "/usr/lib64/util-vserver/vserver.functions: line 914: /dev/cpuset/cpuset-hf/cpus: Permission denied" 1375948698 M * daniel_hozac it's most likely called cpuset.cpus 1375948902 Q * BenG Quit: I Leave 1375949117 J * imachine ~imachine@robot.greenhost24.pl 1375949567 M * Fog_Watch The error is: "/usr/lib64/util-vserver/vserver.functions: line 914: /dev/cpuset/kdc/cpus: Permission denied" 1375949582 M * Fog_Watch But: "ls: cannot access /dev/cpuset/kdc/cpus: No such file or directory" 1375949621 M * Fog_Watch "/dev/cpuset/kdc/cpuset.cpus" does exist though, like you said. 1375950157 Q * Romster Ping timeout: 480 seconds 1375950191 J * Romster ~romster@202.168.100.149.dynamic.rev.eftel.com 1375950954 Q * Romster Ping timeout: 480 seconds 1375952554 J * BenG ~BenG@cpc35-aztw23-2-0-cust207.18-1.cable.virginmedia.com 1375954161 Q * BenG Quit: I Leave 1375954441 Q * cuba33ci Remote host closed the connection 1375954459 J * cuba33ci ~cuba33ci@114-36-234-37.dynamic.hinet.net 1375958090 Q * Aiken Remote host closed the connection 1375958606 Q * imcsk8 Ping timeout: 480 seconds 1375959557 Q * ircuser-1 Ping timeout: 480 seconds 1375962139 J * ircuser-1 ~ircuser-1@35.222-62-69.ftth.swbr.surewest.net 1375963621 Q * hparker Quit: I've fallen off the 'net and can't get up 1375963881 J * hparker ~hparker@2001:470:1f0f:32c:beae:c5ff:fe01:b600 1375966201 Q * Fog_Watch Remote host closed the connection 1375967876 J * fback fback@red.fback.net 1375972056 J * BenG ~bengreen@bmex-gw.bristolwireless.net 1375972338 N * Bertl_zZ Bertl 1375972345 M * Bertl morning folks! 1375973228 Q * BenG Quit: I Leave 1375974558 M * fback hello Bertl! 1375974639 M * fback Bertl: quick question, id there a simple way to checkpoint/restore guest (eg to reboot the host and then restore guests, much like savestate in full blown virtualization) 1375974741 M * Bertl in theory, there is a freezer cgroup, but I haven't seen that working yet 1375974763 M * Bertl the simplest way is to wrap the entire host into some kind of VM 1375974787 M * Bertl i.e. run Linux-VServer inside a kvm/xen domu/whatever 1375974809 J * imcsk8 ~ichavero@148.229.1.11 1375976166 M * fback Bertl: my first thought was kvm/xem/whatever 1375976180 M * fback but then again, it doesn't solve anything 1375976206 M * fback you end up with "real" host you can easily reboot 1375976207 M * Bertl well, it works for planned host maintainance 1375976245 M * fback and then another host within kvm, with the same problem, how to reboot it without loosing guests state 1375976257 M * Bertl not sure what scenario you are trying to solve 1375976293 M * fback keep guests state, ie running processes 1375976338 M * Bertl you can keep that if you do not reboot, problem solved :) 1375976374 M * fback :)) 1375976416 M * fback by defauly every guest runs in dedicated container, right? 1375976446 M * Bertl depends on how you define container 1375976514 M * Bertl but as I said, it would be easier to describe the scenario you are trying to solve/avoid/whatever 1375976831 M * fback Bertl: a guest with shells, where shell owners leave their sessions on screen 1375976864 M * fback I have to upgrade host, so at some point all guests will have to be restarted 1375976907 M * fback Ideal solution would be to checkpoint this guest, reboot the host, then restore the guest 1375976995 M * Bertl upgrade the host means what exactly? 1375977131 M * fback get current stable / supported linux flavor :) 1375977156 M * Bertl kernel or userspace or both? 1375977194 M * fback userspace 1375977215 M * Bertl you can do that without bringing the kernel down and without affecting the guests 1375977340 M * fback how can I be sure there are no old libs kept by running processes? 1375977357 M * Bertl by restarting the host userspace processes 1375977377 M * Bertl ideally there should be nothing more than sshd running on the host 1375977401 M * fback no, you need ntp too 1375977417 M * Bertl so be it, but simple to restart as well 1375977424 M * fback and when you have backup power, some daemon to monitor that too 1375977463 M * fback and md-related daemons ;) 1375977491 M * Bertl everything but init should be easy, and a proper init should be able to restart itself or at least transfer execution to the 'new' init if there is one 1375977526 M * fback Bertl: that's why I always have doubts after userspace upgrade 1375977539 M * fback especially when libc is replaced 1375977600 M * fback ...and I'm never sure, if new process will use new version of library, when inode is still kept by old version, now only in memory... 1375977653 M * fback btw, what about kernel upgrades? This would be great to keep guests state in this case too 1375977694 M * Bertl it would be very strange when a file, which got replaced by a newer version, on open would result in a handle to the old contents no? 1375977735 M * fback on the first open yes 1375977742 M * Bertl note that processes do not 'request' libraries out of nowhere or conveniently map arbitrary space they consider libraries 1375977752 M * fback but on subsequent, well I'm not sure ;) 1375977761 M * Bertl instead the library is a file, which will simply be mapped 1375977824 M * Bertl but it's easy to test, just replace your favorite library by some random data and see what works and what fails :) 1375977851 M * Bertl any newly started process or any process loading (dynamically linking) a library will get the new, random data 1375977876 M * fback ofc, but one file (or more speciffic, the inode) is mapped only once 1375977901 M * fback hm 1375977950 M * fback then removing old one and installing new one will work 1375977987 M * fback and I'm sure someone already thought about how to replace system libraries :) 1375978065 M * fback then again, it's how I assume it shoould go 1375978075 M * fback but how far it's from reality ;) 1375978188 J * bonbons ~bonbons@2001:a18:20b:a301:599c:ea9b:eed2:8bda 1375979273 J * Seattle ~chatzilla@c-24-147-64-244.hsd1.ma.comcast.net 1375979419 M * Seattle Hi All - was on ~6 months ago, had to work on other stuff, but was hoping to circle back. Have gotten Vserver to work on Squeeze, but are trying to use it on Wheezy. Have used http://repo.psand.net/info/ to patch kernel, and then compiled util-vserver by hand. On more than one test machine, everything goes fine when building guest until try to install gnome or lxde. 1375979423 Q * fosco_ Quit: leaving 1375979431 J * fosco fosco@91.208.40.1 1375979474 M * Seattle Am not sure this is a Vserver problem per se, but get insserv: Service mountkernfs has to be enabled to start service keyboard-setup 1375979476 M * Seattle insserv: exiting now! 1375979478 M * Seattle update-rc.d: error: insserv rejected the script header 1375979479 M * Seattle dpkg: error processing keyboard-configuration (--configure): 1375979481 M * Seattle subprocess installed post-installation script returned error exit status 1 1375979483 M * Seattle dpkg: dependency problems prevent configuration of console-setup-linux: 1375979485 M * Seattle console-setup-linux depends on keyboard-configuration (= 1.88); however: 1375979486 M * Seattle Package keyboard-configuration is not configured yet. 1375979523 M * Seattle and finally.... Sub-process /usr/bin/dpkg returned an error code (1). Breaks ability to do more installs... 1375979553 M * Seattle Got same results when patched kernel and util-vserver by hand... 1375979586 M * Seattle Do I have to (should I) dump Debian? 1375979703 M * Bertl sounds funny :) 1375979735 M * Bertl what is insserv and what does the mountkernfs service do? 1375979747 M * Bertl and do you get that on the host or inside a guest? 1375979824 M * Seattle Getting only on guests....am guessing this is to do with headers (maybe?) and hardware....Wheezy goes in clean on the host. Q: have other people gotten guests to work with Wheezy and gnome or LXDE? 1375979859 M * Bertl so, why do you enable the mountkernfs or keyboard-setup service inside a guest then? 1375979960 M * Seattle Not doing so "on purpose"....when in guest and do "apt-get install -y lxde" or gnome-core the install proceeds for quite a while, get screen asking for keyboard type, more install happens, and eventually this error pops up.... 1375980000 M * Seattle Is it something to do with flags or maybe "vestigial" settings am using in guests? 1375980002 M * Bertl so sounds like a 'debian not ready for container' problem 1375980009 M * Seattle ugh 1375980025 M * Bertl but nothing which should keep you from installing it anyway 1375980052 M * Bertl just do the install on a 'real' system, then copy the installation over to the guest and disable all the unneccesary stuff 1375980058 M * Seattle should I consider another linux dist? Assume that's probably a big learning curve... 1375980084 M * Seattle Or try to find someone who's gotten this to work? 1375980132 M * Bertl well, of course, there are a bunch of debian folks here on the channel, so if you be patient, somebody might chime in 1375980147 M * Bertl (alternatively post to the mailing list) 1375980198 M * Seattle OK - can try that suggestion (any hint on what is "unncessary stuff")? 1375980240 M * Bertl everything hardware related or directly manipulating the kernel, like doing mounts, loading kernel modules, accessing kernel memory or logging 1375980268 M * Seattle OK...afraid that's probably beyond me, so will stay on and also try mailing list... 1375980286 M * Bertl all hardware and kernel settings have been already done on the host, so no point to set them up or even try to reconfigure them in a guest 1375980295 M * Seattle right 1375980330 M * Bertl the most prominent services are usually network scripts/services, mount scripts/services, kernel modules and kernel logger 1375980355 M * Seattle OK Thanks! 1375980364 M * Bertl but often special hardware detection or (un)plug managers fall into this category as well 1375980406 M * Bertl I'd ask on a debian channel, if there is a special config to make when installing debian in a container 1375980436 M * Bertl sometimes there is a simple way to tell the distro that all those hardware related services are not needed 1375980475 M * Seattle Ah - great ideas. Let me try some of your suggestions, will post back if make progress (or if still stuck after next round of attempts) 1375980507 M * Seattle Thanks again 1375980518 M * Bertl you're welcome! feel free to hang around! 1375980525 M * Seattle Will do 1375982757 N * l0kit Guest2693 1375982768 J * l0kit ~1oxT@0001b54e.user.oftc.net 1375983164 Q * Guest2693 Ping timeout: 480 seconds 1375985188 M * Bertl off for a nap ... bbl 1375985196 N * Bertl Bertl_zZ 1375986069 M * Seattle Q: am having trouble getting Linux Vserver to work on Wheezy with gnome-core or lxde. Do other Linux dists support Vserver? Which ones do people like? 1375990781 J * hijacker_ ~hijacker@cable-84-43-134-121.mnet.bg 1375991252 Q * Seattle Remote host closed the connection 1375993323 N * Bertl_zZ Bertl 1375993330 M * Bertl back now ... 1375993343 Q * hijacker_ Quit: Leaving 1375993636 J * Fog_Watch ~ian@21.55.70.115.static.exetel.com.au 1375994203 J * Aiken ~Aiken@2001:44b8:2168:1000:21f:d0ff:fed6:d63f 1375996557 Q * bonbons Quit: Leaving 1375997149 J * tanjix tanjix@a.clients.kiwiirc.com 1375997214 M * tanjix hiho - I ran into an older bug that was discussed years ago, but I don't find a solution or I'm just not seeing it... creating a guest fails with: 1375997231 M * tanjix mv: cannot move `/etc/vservers/.defaults/vdirbase/vs9999' to `/etc/vservers/.defaults/vdirbase/vs9999.~1375997242~': Device or resource busy 1375999813 J * BenG ~BenG@cpc35-aztw23-2-0-cust207.18-1.cable.virginmedia.com 1376000835 J * SteeleNivenson ~SteeleNiv@pool-96-224-241-140.nycmny.fios.verizon.net 1376001967 Q * tanjix Quit: http://www.kiwiirc.com/ - A hand crafted IRC client 1376001972 J * tanjix tanjix@a.clients.kiwiirc.com 1376001975 Q * tanjix 1376001979 J * tanjix tanjix@a.clients.kiwiirc.com 1376001980 Q * tanjix 1376003698 Q * transacid Remote host closed the connection 1376004205 Q * DoberMann Ping timeout: 480 seconds 1376004387 J * transacid ~transacid@transacid.de 1376004728 J * DoberMann ~james@2a01:e35:8b44:84c0::2 1376005547 Q * ensc|w Remote host closed the connection 1376005556 J * ensc|w ~ensc@www.sigma-chemnitz.de 1376006239 Q * BenG Quit: I Leave