Hi Herbert, - For IPV4 the VServer IP seems to show up only in the VServer as expected. No other IPs, not even a localhost IP showing up. - For IPV6 I see other IPV6 IPs on other interfaces. Might have been there before but I did not notice :(. I am not using IPV6. - Attached output from a kernel trace. - As expected vservser-stat doesn't show the vsersers, but they are in /proc/self/vinfo and /proc/virtual/ - I used to be able to go from a vserver IP through a openvpn tunnel to remote resources and appear as the vserver IP to the remote resources. Since 2.6.0 I always appear as my local TUN IP :(. Might be something I setup differently in netfilter.
All for now :), JES On Mon, 5 Jan 2004, Herbert Poetzl wrote: > > Hi Folks! > > a new (vs0.04) test release for 2.6 vserver is available > at http://www.13thfloor.at/vserver/e_patches/vs-26x/ > > this one brings network support (I doubt it's complete > but it allowed me to start two vserver on an emulated > host, with apache and sshd each, retrieve the web page, > and login via ssh) > > as usual, static context ids are advised, and some tools > do not handle the 'new' proc interface yet, the following > one-liner might help a little there ... > > sed -i 's|CTX=`g.*$|CTX=`sed\ "/VxID/\ s/.*:\w*//"\ /proc/self/vinfo`|' > /usr/lib/vserver/{save_s_context,vserverkillall} > > let me know, what works for you, and what doesn't > > TIA, > Herbert > > _______________________________________________ > Vserver mailing list > [EMAIL PROTECTED] > http://list.linux-vserver.org/mailman/listinfo/vserver > -- James B. MacLean [EMAIL PROTECTED] Department of Education Nova Scotia, Canada B3M 4B2
Debug: sleeping function called from invalid context at mm/slab.c:1856 in_atomic():1, irqs_disabled():0 Call Trace: [<c011c8b5>] __might_sleep+0xab/0xc9 [<c013e6b0>] __kmalloc+0x98/0x9f [<c0180c16>] proc_create+0x86/0xd6 [<c0180ddf>] create_proc_entry+0x61/0xc7 [<c0183200>] vx_proc_create+0x45/0xb2 [<c012ee5a>] find_or_create_vx_info+0xbe/0x146 [<c012f149>] vc_new_s_context+0xeb/0x220 [<c0123417>] sys_vserver+0xbb/0xd0 [<c0109277>] syscall_call+0x7/0xb Debug: sleeping function called from invalid context at mm/slab.c:1856 in_atomic():1, irqs_disabled():0 Call Trace: [<c011c8b5>] __might_sleep+0xab/0xc9 [<c013e6b0>] __kmalloc+0x98/0x9f [<c0180c16>] proc_create+0x86/0xd6 [<c0180ddf>] create_proc_entry+0x61/0xc7 [<c0183200>] vx_proc_create+0x45/0xb2 [<c012ee5a>] find_or_create_vx_info+0xbe/0x146 [<c012f149>] vc_new_s_context+0xeb/0x220 [<c0123417>] sys_vserver+0xbb/0xd0 [<c0109277>] syscall_call+0x7/0xb Debug: sleeping function called from invalid context at mm/slab.c:1856 in_atomic():1, irqs_disabled():0 Call Trace: [<c011c8b5>] __might_sleep+0xab/0xc9 [<c013e6b0>] __kmalloc+0x98/0x9f [<c0180c16>] proc_create+0x86/0xd6 [<c0180ddf>] create_proc_entry+0x61/0xc7 [<c0183200>] vx_proc_create+0x45/0xb2 [<c012ee5a>] find_or_create_vx_info+0xbe/0x146 [<c012f149>] vc_new_s_context+0xeb/0x220 [<c0123417>] sys_vserver+0xbb/0xd0 [<c0109277>] syscall_call+0x7/0xb Debug: sleeping function called from invalid context at mm/slab.c:1856 in_atomic():1, irqs_disabled():0 Call Trace: [<c011c8b5>] __might_sleep+0xab/0xc9 [<c013e6b0>] __kmalloc+0x98/0x9f [<c0180c16>] proc_create+0x86/0xd6 [<c0180ddf>] create_proc_entry+0x61/0xc7 [<c0183200>] vx_proc_create+0x45/0xb2 [<c012ee5a>] find_or_create_vx_info+0xbe/0x146 [<c012f149>] vc_new_s_context+0xeb/0x220 [<c0123417>] sys_vserver+0xbb/0xd0 [<c0109277>] syscall_call+0x7/0xb Debug: sleeping function called from invalid context at mm/slab.c:1856 in_atomic():1, irqs_disabled():0 Call Trace: [<c011c8b5>] __might_sleep+0xab/0xc9 [<c013e6b0>] __kmalloc+0x98/0x9f [<c0180c16>] proc_create+0x86/0xd6 [<c0180ddf>] create_proc_entry+0x61/0xc7 [<c0183200>] vx_proc_create+0x45/0xb2 [<c012ee5a>] find_or_create_vx_info+0xbe/0x146 [<c012f149>] vc_new_s_context+0xeb/0x220 [<c0123417>] sys_vserver+0xbb/0xd0 [<c0109277>] syscall_call+0x7/0xb Debug: sleeping function called from invalid context at mm/slab.c:1856 in_atomic():1, irqs_disabled():0 Call Trace: [<c011c8b5>] __might_sleep+0xab/0xc9 [<c013e6b0>] __kmalloc+0x98/0x9f [<c0180c16>] proc_create+0x86/0xd6 [<c0180ddf>] create_proc_entry+0x61/0xc7 [<c0183200>] vx_proc_create+0x45/0xb2 [<c012ee5a>] find_or_create_vx_info+0xbe/0x146 [<c012f149>] vc_new_s_context+0xeb/0x220 [<c0123417>] sys_vserver+0xbb/0xd0 [<c0109277>] syscall_call+0x7/0xb Debug: sleeping function called from invalid context at mm/slab.c:1856 in_atomic():1, irqs_disabled():0 Call Trace: [<c011c8b5>] __might_sleep+0xab/0xc9 [<c013e6b0>] __kmalloc+0x98/0x9f [<c0180c16>] proc_create+0x86/0xd6 [<c0180ddf>] create_proc_entry+0x61/0xc7 [<c0183200>] vx_proc_create+0x45/0xb2 [<c012ee5a>] find_or_create_vx_info+0xbe/0x146 [<c012f149>] vc_new_s_context+0xeb/0x220 [<c0123417>] sys_vserver+0xbb/0xd0 [<c0109277>] syscall_call+0x7/0xb
