| NAT crash with Debian Lenny default kernel [message #35026] |
Sat, 21 February 2009 11:58  |
Pijar
Messages: 1
Registered: August 2008
|
Junior Member |
|
|
I am stuck with this problem: I installed HN with Debian stable (yes, it's Lenny at last). It was a minimal default installation with Debian openvz kernel (linux-image-2.6.26-1-openvz-amd64_2.6.26-13_amd64.deb). The HN runs smoothly and I have created a container with Debian Lenny minimal installation in it and it runs without problems as well. The story begins when I try to run NAT inside the container. Adding:
IPTABLES="iptable_nat"
in the container's conf file and trying to start it gives an oops:
------------------------------
kama:~# vzctl start 202
Starting VE ...
VE is mounted
Adding IP address(es): 192.168.1.202
Message from syslogd@kama at Feb 21 12:40:16 ...
kernel:[114333.766326] ------------[ cut here ]------------
Message from syslogd@kama at Feb 21 12:40:16 ...
kernel:[114333.766384] invalid opcode: 0000 [1] SMP
Message from syslogd@kama at Feb 21 12:40:16 ...
kernel:[114333.770698] Code: 25 00 00 00 00 48 8b 80 08 07 00 00 bf 02 00 00 00 48 8b 98 c8 14 00 00 e8 13 58 fe ff 48 89 43 20 48 83 3d c6 da ff ff 00 74 04 <0f> 0b eb fe 31 db 48 c7 05 b3 da ff ff a1 a2 31 a0 eb 22 8b 15
------------------------------
Luckily it justs hangs the process of bringing up the container, not the HN itself.
Any ideas how to get around this problem? I need this NAT inside the container badly and I would prefer to stick with Debian kernel, maybe there's a kernel patch available so I could recompile the Debian kernel myself?
Thanks for any hints and help.
--
Jarek Pioro
Cirrus - Aedificaremus Tibi
http://www.cirrus.pl
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
