eth0 dies when using openVZ kernel. [message #27096] |
Sat, 09 February 2008 06:32 |
thorpe
Messages: 16 Registered: February 2008 Location: Sydney - Australia
|
Junior Member |
|
|
Bit of a strange one this, I'm not even sure where to start looking.
I'm using Debian Etch.
I've installed the openVZ kernel by following this guide on there site. All went smoothly. I boot into the new kernel, no problems, check ifconfig and I see...
eth0 Link encap:Ethernet HWaddr 00:08:A1:03:F1:14
inet addr:192.168.10.2 Bcast:192.168.10.255 Mask:255.255.255.0
inet6 addr: fe80::208:a1ff:fe03:f114/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:27 errors:4 dropped:0 overruns:0 frame:0
TX packets:35 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2972 (2.9 KiB) TX bytes:3031 (2.9 KiB)
Interrupt:185 Base address:0xe800
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:560 (560.0 b) TX bytes:560 (560.0 b)
venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Lovelly.
I then try to apt-get install the user-level tools and find out my connection has died. I try to ping another machine I have at 192.168.10.1, no response. I check ifconfig again, looks fine.
I reboot again into the openVZ kernel, ping 192.168.10.1 it responds. I ping it a few more times and after the third I onbce again get no response.
I then try to compile my own kernel following this guide ( I use my working .config file + make the changes suggested), I boot into it, same deal. I seem to have a network connection for about 10 seconds then it just dies.
I'm really not sure where to even start looking for any error messages. Anyone got any ideas?
|
|
|