OpenVZ Forum - RDF feed
type: channel
items: eth0 dies when using openVZ kernel.
items: Re: eth0 dies when using openVZ kernel.
items: SOLVED

eth0 dies when using openVZ kernel.
type: item
description: 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?
creator: thorpe
date: 2008-02-09T06:32:35-00:00

Re: eth0 dies when using openVZ kernel.
type: item
description: Hi, - Any strange messages in logs or dmesg? - Could you please use for example "tcpdump" utility to analyse packets behavior? - Please check arp or route table when you loose the connection. - By the way can you please try "/etc/init.d/vz stop"?
creator: maratrus
date: 2008-02-09T20:12:49-00:00

Re: eth0 dies when using openVZ kernel.
type: item
description: This still isn't working. eth0 just drops off the face of the earcth after about a minute. yet if a look at ifconfig it all looks normal. route comes up blank after eth0 dies. Ive got no idea where to start looking, here is a cat of /var/log/messages from the time I boot into the vz kernal till the time I need to reboot back into my normal working kernel. Anyone got any ideas? Or can recommend some vitualization that I might be able to get working? [code] Mar 3 19:16:46 oblivion kernel: Linux version 2.6.18-ovz-028stab051.1 () (tsd@debian.systs.org) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 Fri Dec 7 19:42:24 CET 2007 Mar 3 19:16:46 oblivion kernel: BIOS-provided physical RAM map: Mar 3 19:16:46 oblivion kernel: BIOS-e820: 0000000000000000 - 00000000000a0000 (usable) Mar 3 19:16:46 oblivion kernel: BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) Mar 3 19:16:46 oblivion kernel: BIOS-e820: 0000000000100000 - 000000001ff77000 (usable) Mar 3 19:16:46 oblivion kernel: BIOS-e820: 000000001ff77000 - 000000001ff79000 (ACPI NVS) Mar 3 19:16:46 oblivion kernel: BIOS-e820: 000000001ff79000 - 0000000020000000 (reserved) Mar 3 19:16:46 oblivion kernel: BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved) Mar 3 19:16:46 oblivion kernel: BIOS-e820: 00000000fee00000 - 00000000fee10000 (reserved) Mar 3 19:16:46 oblivion kernel: BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved) Mar 3 19:16:46 oblivion kernel: 0MB HIGHMEM available. Mar 3 19:16:46 oblivion kernel: 511MB LOWMEM available. Mar 3 19:16:46 oblivion kernel: found SMP MP-table at 000fe710 Mar 3 19:16:46 oblivion kernel: DMI 2.3 present. Mar 3 19:16:46 oblivion kernel: ACPI: PM-Timer IO Port: 0x808 Mar 3 19:16:46 oblivion kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) Mar 3 19:16:46 oblivion kernel: Processor #0 15:2 APIC version 20 Mar 3 19:16:46 oblivion kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] disabled) Mar 3 19:16:46 oblivion kernel: ACPI: IOAPIC (id[0x01] …
creator: thorpe
date: 2008-03-03T08:43:22-00:00

Re: eth0 dies when using openVZ kernel.
type: item
description: This looks like (somehow) that you/somebody has deleted the last address of the eth0 and add it again. ifconfig is basically useless for an analisys. You should check routes configuration. The best thigh to do is to install iproute2 package and use 'ip' utility. 'ip route list table all' will give exact information about all tables and 'ip route get <ip_addr>' will help to understand what happens. Basically, if you see packet drops, you should check the content of 'netstat -s'. Drops are not gone into void, they increase some counters and the exact counter name will help to understand what happens in the reality. Regards, Den
creator: den
date: 2008-03-03T12:00:56-00:00

Re: eth0 dies when using openVZ kernel.
type: item
description: Hopefully this will help you help me but I have no idea what any of this meens. Here is the output of 'ip route list table all' from my working kernel (with network working) 192.168.10.0/24 dev eth0 proto kernel scope link src 192.168.10.2 default via 192.168.10.1 dev eth0 broadcast 127.255.255.255 dev lo table 255 proto kernel scope link src 127.0.0.1 broadcast 192.168.10.255 dev eth0 table 255 proto kernel scope link src 192.168.10.2 local 192.168.10.2 dev eth0 table 255 proto kernel scope host src 192.168.10.2 broadcast 192.168.10.0 dev eth0 table 255 proto kernel scope link src 192.168.10.2 broadcast 127.0.0.0 dev lo table 255 proto kernel scope link src 127.0.0.1 local 127.0.0.1 dev lo table 255 proto kernel scope host src 127.0.0.1 local 127.0.0.0/8 dev lo table 255 proto kernel scope host src 127.0.0.1 local ::1 via :: dev lo proto none metric 0 mtu 16436 advmss 16376 hoplimit 4294967295 local fe80::208:a1ff:fe03:f114 via :: dev lo proto none metric 0 mtu 16436 advmss 16376 hoplimit 4294967295 fe80::/64 dev eth0 metric 256 expires 8532984sec mtu 1500 advmss 1440 hoplimit 4294967295 ff00::/8 dev eth0 metric 256 expires 8532984sec mtu 1500 advmss 1440 hoplimit 4294967295 unreachable default dev lo proto none metric -1 error -101 hoplimit 255 Now, here is the output of the same command using the ovz kernel. 192.168.10.0/24 dev eth0 proto kernel scope link src 192.168.10.2 default via 192.168.10.1 dev eth0 broadcast 127.255.255.255 dev lo table 255 proto kernel scope link src 127.0.0.1 broadcast 192.168.10.255 dev eth0 table 255 proto kernel scope link src 192.168.10.2 local 192.168.10.2 dev eth0 table 255 proto kernel scope host src 192.168.10.2 broadcast 192.168.10.0 dev eth0 table 255 proto kernel scope link src 192.168.10.2 broadcast 127.0.0.0 dev lo table 255 proto kernel scope link src 127.0.0.1 local 127.0.0.1 dev lo table 255 proto kernel scope host src 127.0.0.1 local 127.0.0.0/8 dev lo table 255 proto kernel scope host src 127.0.0.1 local ::1 via :: dev…
creator: thorpe
date: 2008-03-04T05:23:32-00:00

Re: eth0 dies when using openVZ kernel.
type: item
description: Basically, all this output is just routes in the slightly different format that one from 'route' utility. Linux uses 2 tables by default for routing: - main and - local. The latter is used to determine the source address of the outgoing packet and to decide whether the packet is local. 'ip' interface is a bit never in respect to 'route' and is preferred for a lot of people, though it is not compatible with classical Unix one. For the problem. According to the statitics present, you have 'destination unreachable' error. So you have listed routing tables after the boot or when you see the problem? We need to see the latter. Additionally, could you share the result of 'ip route get <ip address you are trying to ping>' and 'arp -n' at the moment of the problem?
creator: den
date: 2008-03-04T06:13:35-00:00

Re: eth0 dies when using openVZ kernel.
type: item
description: Ok, thanks heaps for this. here is my routing tables list after the problem has occured (ie I have no connection). 192.168.10.0/24 dev eth0 proto kernel scope link src 192.168.10.2 default via 192.168.10.1 dev eth0 broadcast 127.255.255.255 dev lo table 255 proto kernel scope link src 127.0.0.1 broadcast 192.168.10.255 dev eth0 table 255 proto kernel scope link src 192.168.10.2 local 192.168.10.2 dev eth0 table 255 proto kernel scope host src 192.168.10.2 broadcast 192.168.10.0 dev eth0 table 255 proto kernel scope link src 192.168.10.2 broadcast 127.0.0.0 dev lo table 255 proto kernel scope link src 127.0.0.1 local 127.0.0.1 dev lo table 255 proto kernel scope host src 127.0.0.1 local 127.0.0.0/8 dev lo table 255 proto kernel scope host src 127.0.0.1 local ::1 via :: dev lo proto none metric 0 mtu 16436 advmss 16376 hoplimit 4294967295 local fe80::208:a1ff:fe03:f114 via :: dev lo proto none metric 0 mtu 16436 advmss 16376 hoplimit 4294967295 fe80::/64 dev eth0 metric 256 expires 2133422sec mtu 1500 advmss 1440 hoplimit 4294967295 ff00::/8 dev eth0 metric 256 expires 2133422sec mtu 1500 advmss 1440 hoplimit 4294967295 unreachable default dev lo proto none metric -1 error -101 hoplimit 255 Here is the ouput of 'ip route get 72.14.207.99' (google's ip) 72.14.207.99 via 192.168.10.1 dev eth0 src 192.168.10.2 cache mtu 1500 advmss 1460 hoplimit 64 And now, the output of 'arp -n' Address HWtype HWaddress Flags Mask Iface 192.168.10.1 (incomplete) eth0 Hope this helps. Thanks again.
creator: thorpe
date: 2008-03-04T07:24:28-00:00

Re: eth0 dies when using openVZ kernel.
type: item
description: ARP resolution does not work for the case. Could you check with tcpdump that there is an outgoing ARP request? tcpdump -ni eth0 arp If you see the request and do not see a reply, then you should check that your router really send the reply packet, it is best to be done in the similar way from the other host in the network.
creator: den
date: 2008-03-04T08:04:25-00:00

Re: eth0 dies when using openVZ kernel.
type: item
description: Quote: it is best to be done in the similar way from the other host in the network. And how exactly would I do that?
creator: thorpe
date: 2008-03-04T08:52:49-00:00

Re: eth0 dies when using openVZ kernel.
type: item
description: Also, do you think it might be worth my while trying another card? I've got a spare here.
creator: thorpe
date: 2008-03-04T09:30:09-00:00

Re: eth0 dies when using openVZ kernel.
type: item
description: basically, I do not have an answer for this. We have heard about e1000 problems with 028stab053 kernel. Though, this can be unrelevant. As for ARP, should should do the same tcpdump -n arp and check that you see both arp requests and arp reply for the case.
creator: den
date: 2008-03-04T11:22:59-00:00

SOLVED
type: item
description: Ok, I'm really not sure what the issue was, and to be honest no longer care. I pulled my card out, replaced it with my spare D-Link RTL8139 and all is now working. Thanks again for you help, now its time to go play with this thing. i'm sure I'll be back with more questions soon enough.
creator: thorpe
date: 2008-03-05T04:07:33-00:00