1303435058 J * hparker ~hparker@2001:470:1f0f:32c:beae:c5ff:fe01:b647 1303439329 Q * quasisane Ping timeout: 480 seconds 1303441125 J * quasisane ~sanep@c-76-24-80-97.hsd1.nh.comcast.net 1303441477 Q * imcsk8 Quit: This computer has gone to sleep 1303446165 J * ghislain ~AQUEOS@adsl2.aqueos.com 1303446292 Q * lodan Ping timeout: 480 seconds 1303446634 J * fisted_ ~fisted@p50885F14.dip.t-dialin.net 1303446983 Q * fisted Ping timeout: 480 seconds 1303451136 Q * hparker Quit: Quit 1303451995 J * lodan ~lodan@rb178-1-88-163-25-248.fbx.proxad.net 1303453226 J * petzsch ~markus@p57B662F0.dip.t-dialin.net 1303453917 Q * SwenTjuln Ping timeout: 480 seconds 1303453969 J * SwenTjuln ~SwenTjuln@77.111.2.36 1303455987 J * derjohn_mob ~aj@pD957680E.dip.t-dialin.net 1303456854 P * petzsch 1303459494 N * Bertl_zZ Bertl 1303459501 M * Bertl morning folks! 1303459929 M * Mr_Smoke mo'in 1303459970 M * Mr_Smoke Bertl: about that issue I mentioned yesternite, I take it that /proc/stat is not virtualized ? 1303460051 J * imcsk8 ~ichavero@148.229.9.250 1303460054 M * Bertl since when does /proc/stat contain load information? 1303460071 M * Mr_Smoke I might have misphrased that 1303460079 M * Mr_Smoke I meant values for nice, user, idle etc. 1303460101 M * Mr_Smoke And it does contain that, right ? 1303460124 M * Bertl ah, yes, those are part of the 'virtualization' (not) done by cgroups 1303460139 M * Mr_Smoke Hehe, why the (not) ? 1303460154 M * Bertl because cgroups doesn't have that feature (yet) 1303460161 M * Mr_Smoke I see 1303460192 M * Mr_Smoke So it's a minor inconvenience we'll have to live with until cgroups is upgraded to that effect, right ? 1303460211 M * Bertl correct, if that ever happens ... 1303460226 M * Mr_Smoke Haha :) You don't trust it will happen then :) 1303460238 M * Bertl the thing is, the lxc folks believe that lxc is basically complete AFAIC 1303460240 M * Mr_Smoke In my case I'll resort to graphing CPU on the host and loadavg in the guest 1303460248 M * Mr_Smoke Ow. 1303460262 M * Mr_Smoke Last I heard, it was still a couple of miles behind 1303460269 M * Mr_Smoke (or so I gathered) 1303460302 M * Bertl yes, it definitely is IMHO, so it might make sense to keep them informed 1303463126 J * ensc ~irc-ensc@p5DF2CC61.dip.t-dialin.net 1303463210 Q * Mr_Smoke Read error: Connection reset by peer 1303463316 J * Mr_Smoke smokey@layla.lecoyote.org 1303463317 M * Bertl off for now ... bbl 1303463321 N * Bertl Bertl_oO 1303464610 Q * derjohn_mob Ping timeout: 480 seconds 1303464787 Q * imcsk8 Quit: This computer has gone to sleep 1303474197 M * Guy- sched_setscheduler(12263, SCHED_FIFO, { 10 }) = -1 EPERM (Operation not permitted) 1303474221 M * Guy- I gave the context SYS_NICE (using echo SYS_NICE >bcapabilities) 1303474231 M * Guy- then I restarted it 1303474241 M * Guy- shouldn't this work? 1303474291 M * Guy- BCaps: 0000000034cc04ff 1303474361 M * Guy- the SYS_NICE bit appears to be set 1303474600 M * Guy- this is 2.6.38.2-vs2.3.0.37-rc10 1303474913 M * daniel_hozac do you have CONFIG_RT_GROUP_SCHED? 1303476436 M * Guy- daniel_hozac: yes 1303479279 M * daniel_hozac does the guest's cgroup have rt runtime assigned? 1303479301 M * daniel_hozac cpu.{rt_runtime_us,rt_period_us 1303481243 M * Guy- rt_runtime_us is 0 1303481481 M * Guy- daniel_hozac: I don't know what this value does; does it limit how much time, within rt_period_us, the guest can spend running RT tasks? 1303482181 M * Guy- the maximum of rt_runtime_us seems to be 950000 when rt_period_us is 1000000 1303482483 M * Guy- daniel_hozac: I know have this: 1303482484 M * Guy- /etc/vservers//cgroup/cpu.rt_period_us:1000000 1303482484 M * Guy- /etc/vservers//cgroup/cpu.rt_runtime_us:950000 1303482486 M * Guy- *now 1303482505 M * Guy- daniel_hozac: however, on starting the guest, the actual values are: 1303482506 M * Guy- cpu.rt_period_us:1000000 1303482506 M * Guy- cpu.rt_runtime_us:0 1303482529 M * Guy- daniel_hozac: what am I missing? 1303483706 J * hparker ~hparker@2001:470:1f0f:32c:beae:c5ff:fe01:b647 1303488706 J * bonbons ~bonbons@2001:960:7ab:0:1c45:b730:9b25:1d35 1303489313 J * dowdle ~dowdle@scott.coe.montana.edu 1303489370 J * BenG ~bengreen@cpc12-aztw24-2-0-cust146.aztw.cable.virginmedia.com 1303489984 Q * BenG Quit: I Leave 1303490179 Q * dowdle Remote host closed the connection 1303490724 J * dowdle ~dowdle@scott.coe.montana.edu 1303492203 J * petzsch ~markus@p57B66419.dip.t-dialin.net 1303493215 Q * petzsch Quit: Leaving. 1303495133 Q * hparker Remote host closed the connection 1303498572 N * ensc Guest2892 1303498582 J * ensc ~irc-ensc@p5DF2F076.dip.t-dialin.net 1303498993 Q * Guest2892 Ping timeout: 480 seconds 1303502582 M * Mr_Smoke 2.6.38.4 is out, 3 minor hunks rejected 1303502806 J * cuba33ci_ ~cuba33ci@111-240-164-129.dynamic.hinet.net 1303503127 Q * cuba33ci Read error: Connection reset by peer 1303503136 N * cuba33ci_ cuba33ci 1303507501 J * manana ~mayday090@84.17.25.149 1303510354 J * derjohn_mob ~aj@38.Red-83-44-233.dynamicIP.rima-tde.net 1303511659 Q * bonbons Quit: Leaving 1303511684 Q * manana Remote host closed the connection 1303512152 J * radix ~radix@sslvpn.idsoftware.com 1303512251 M * radix anyone ever experience vservers losing their IP addresses? "ip addr" is just suddenly not showing an IP that I have configured in it (after a while of running) 1303512320 M * radix honestly, I don't know if it's related to vserver itself 1303512374 M * radix actually, there are two IPs configured, but only one of them is disappearing. this has happened on a number of my nodes recently -- they're losing their public IPs 1303512804 M * radix oh, maybe it's related to this: http://www.paul.sladen.org/vserver/archives/200908/0115.html 1303512809 Q * dowdle Remote host closed the connection 1303512982 Q * ryker Quit: Leaving. 1303513058 M * radix unfortunately there's no conclusion in that thread 1303513357 M * Bertl_oO you mean, after some time, without you doing anything on the host, the guest IP disappears, yes? 1303513362 N * Bertl_oO Bertl 1303513401 M * Bertl if so, what does 'ip a l' show _before_ the guest IP disappears? 1303513407 M * Bertl (on the host) 1303513426 M * radix I have been setting up a lot of vservers lately, so I have been doing lots of stuff on hosts 1303513453 M * Bertl so it might have disappeared because you changed something on the host? 1303513458 M * radix maybe :-) 1303513482 M * radix I'm going to keep trying to come up with a reproduction 1303513493 M * Bertl okay, 'ip a l' on the host (feel free to anonymize the info, but do it in a way which doesn't destroy the information :) 1303513518 M * radix okay, I think I did just reproduce it :o 1303513530 M * radix I shut off one of my vservers and all the rest on the same interface disappeared from ip a l 1303513537 M * Bertl yep, expected 1303513566 M * Bertl without promote secondaries enabled, when you remove the primary, all secondary addresses will be removed (see FAQ) 1303513580 M * radix I seeeeee 1303513590 M * Bertl the primary is the one which doesn't have 'secondary' added on 'ip a l' 1303513609 M * Bertl that's a mainline networking 'feature' btw :) 1303513689 M * radix I should have more thoroughly read the faq - I was searching for things like "lost IP" and whatnot 1303513798 M * Bertl in any case, problem solved I presume? 1303514883 Q * derjohn_mob Ping timeout: 480 seconds 1303515087 J * imcsk8 ~ichavero@148.229.9.250 1303515493 Q * imcsk8 Quit: This computer has gone to sleep 1303516099 M * Bertl off to bed now ... have a good one everyone! 1303516104 N * Bertl Bertl_zZ 1303516779 Q * ghislain Quit: Leaving.