1351037591 J * ard ~ard@shell2.kwaak.net
1351040484 J * Ghislain ~aqueos@adsl1.aqueos.com
1351041377 Q * Ghislain Read error: Connection reset by peer
1351044366 Q * clopez Ping timeout: 480 seconds
1351047336 Q * imcsk8 Ping timeout: 480 seconds
1351047352 J * imcsk8 ~ichavero@148.229.1.11
1351053030 M * Bertl off to bed now ... have a good one everyone!
1351053036 N * Bertl Bertl_zZ
1351053714 J * Ghislain ~aqueos@adsl1.aqueos.com
1351056143 Q * geos_one Quit: ChatZilla 0.9.89 [Firefox 15.0.1/20120920112759]
1351061248 Q * ncopa Quit: Leaving
1351061595 J * ncopa ~ncopa@3.203.202.84.customer.cdi.no
1351061979 Q * ensc|w Remote host closed the connection
1351061988 J * ensc|w ~ensc@www.sigma-chemnitz.de
1351062712 J * thierryp ~thierry@home.parmentelat.net
1351064812 J * kir ~kir@swsoft-msk-nat.sw.ru
1351067040 Q * fisted_ Read error: Connection reset by peer
1351067095 J * fisted ~fisted@xdsl-81-173-188-1.netcologne.de
1351069193 P * kir PING 1351069193
1351072561 J * clopez ~clopez@fanzine.igalia.com
1351074276 Q * thierryp Remote host closed the connection
1351077666 M * BlackPanx hello everyone
1351077723 M * BlackPanx one question... is it possible to push other default route in vserver guest than it's host ? i'd like vservers to have gateway let's say: 10.40.1.1 and not 193.2.1.66 as they have now  from host.
1351077845 M * daniel_hozac like i already said, use source based routing.
1351078096 M * BlackPanx if i understand.. this is by using iproute2 ?
1351078097 M * BlackPanx right ?
1351078102 M * daniel_hozac yes
1351078811 Q * ircuser-1 Ping timeout: 480 seconds
1351079743 M * BlackPanx http://valdemar.lemche.net/search/label/routing is this correct way ?
1351079758 M * BlackPanx last example
1351080323 N * Bertl_zZ Bertl
1351080326 M * Bertl morning folks!
1351080659 M * fback morning Bertl!
1351080728 M * fback Bertl: is there a way to make one physical interface available to the guest with admin privs?
1351082037 J * fback_ fback@red.fback.net
1351082127 Q * fback Read error: Connection reset by peer
1351082179 M * Bertl fback_: I guess you can do that with network namespaces
1351082194 M * Bertl (not sure about the security implications though)
1351082298 J * ircuser-1 ~ircuser-1@35.222-62-69.ftth.swbr.surewest.net
1351082318 M * uranus Bertl: on 3.0.x patches i got INFO: rcu_sched_state detected stall on CPU 7 (t=1680273 jiffies) messages. After that the Server does not react on anything expect sysrq. Do you know any issue there?
1351082368 M * uranus this happens between 2h uptime and sometimes +30 days of uptime
1351082557 M * Bertl do you have a kernel trace?
1351082584 M * uranus no it does not output any thing more then this line
1351082597 M * Bertl and does 'on 3.0.x' mean that it doesn't happen on 3.y.x with y > 0 ?
1351082615 M * uranus no i saw this only on 3.0
1351082641 M * uranus with y > 2 i had these state d issues and therefore gone back to 3.0
1351086557 J * vn539 vn539@134.19.178.119
1351086562 M * vn539 hi guys
1351086575 M * vn539 is there any tutorial to migrate linux-vserver to openvz
1351086594 M * Bertl probably on the OVZ pages somewhere
1351086616 M * vn539 there is something but nothing helpfull
1351086625 M * Bertl but why would you want to 'downgrade'? :)
1351086656 M * uranus Bertl: did you read my statements about 3.0?
1351086680 M * Bertl yes, I believe I did?
1351086695 M * Bertl (even asked a question you answered, no?)
1351086811 M * uranus well i asked about any known issues :)
1351086882 M * Bertl for that, I'd need the exact kernel and patch version
1351086900 M * uranus 3.0.42-vs2.3.2.4
1351086995 M * uranus 3.0.46-vs2.3.2.5
1351087011 M * uranus 3.0.27-vs2.3.2.3
1351087030 M * uranus these three kernels currently show all the same symptoms
1351087107 M * Bertl no known issues for 3.0.46-vs2.3.25
1351087120 M * Bertl *vs2.3.2.5
1351087222 M * uranus well not good :/
1351087245 M * uranus but thx for that - hopefully i get a trace in future
1351087272 M * Bertl if magic sysrq works (which you implied) it should be simple to get a stack trace for all processes
1351087284 M * Bertl and more specifically for each cpu including the affected one
1351087525 M * Bertl vn539: any specific reason for migrating?
1351091768 M * _are_ uranus: I am pretty confident I had similar outages, moving on to higher versioned kernels solved it for me.
1351093524 M * Bertl rcu stuff changed a lot recently, and a number of potential races were eliminated
1351093782 A * Ghislain wondering what recently means, by Bertl kernel standard might be the last 2 hours :D
1351094601 J * bonbons ~bonbons@2001:960:7ab:0:651a:90cd:9896:e74a
1351095570 M * Bertl hehe, well, in this case, recently means in 3.4 kernels and later
1351096433 Q * vn539 
1351096938 Q * clopez Ping timeout: 480 seconds
1351096944 Q * fisted Ping timeout: 480 seconds
1351097198 J * geos_one ~chatzilla@80.123.185.198
1351098301 M * Ghislain :)
1351099274 M * Bertl off for a nap .. bbl
1351099280 N * Bertl Bertl_zZ
1351101615 J * clopez ~clopez@88.16.60.213.dynamic.mundo-r.com
1351101916 Q * Hunger Ping timeout: 480 seconds
1351106034 J * Hunger hunger@proactivesec.com
1351108018 N * Bertl_zZ Bertl
1351108023 M * Bertl back now ...
1351109273 J * grobie ~grobie@tyr.schnuckelig.eu
1351110228 Q * FireEgl Quit: Leaving...
1351110860 Q * Rockj Ping timeout: 480 seconds
1351111883 J * Rockj rockj@rockj.net
1351112132 Q * bonbons Quit: Leaving
1351112766 J * fisted ~fisted@xdsl-81-173-188-1.netcologne.de
1351113143 J * fisted_ ~fisted@xdsl-87-78-182-221.netcologne.de
1351113554 Q * fisted Ping timeout: 480 seconds
1351120610 M * geos_one vserver/switch.c:23:0:
1351120612 M * geos_one vserver/context.h:109:2: error: unknown type name 'xid_t'
1351120613 M * geos_one vs_context.h:191:45: error: 'struct task_struct' has no member named 'vx_info'
1351120615 M * geos_one oh jear and also armv5 is broken just to inform you 
1351120655 M * Bertl what kernel/patch?
1351120666 M * geos_one 3.6.2
1351120760 M * geos_one http://pastebin.com/PntVPkEQ
1351120771 M * geos_one the full part of the log
1351120775 M * Bertl where did you find a 3.6.2 Linux-VServer patch?
1351120873 M * geos_one http://vserver.13thfloor.at/Experimental/patch-3.6-vs2.3.4.3-noxfs-nocow.diff
1351120899 M * geos_one but it works on amd64 with 3.6.2
1351120903 M * Bertl I presume that one didn't apply without rejects
1351120935 M * geos_one the only reject was the Makefile EXTRAVERSION
1351120954 M * geos_one otherwise without any problem
1351120954 M * Bertl really? interesting
1351120979 M * Bertl so which arch is giving you the vs_context.h:191:45: ?
1351121003 M * geos_one arm
1351121055 M * geos_one http://ftp.disconnected-by-peer.at/genlink/sys-kernel/linux-nas-patches/config/buffalo_ls_chl2-3.6.2-arm.config
1351121062 M * geos_one the kernel config used
1351121461 M * Bertl I'll check that, will take a little
1351121713 M * geos_one no problem 
1351121725 M * geos_one thx nyway for your hard work
1351121927 M * Bertl you're welcome!
1351122085 M * geos_one good night