VB-3.1.6 loses network with win-7 64b host ubuntu-10.04 32b/64b guests + additions

[simon marshall]

Following investigation, I have separated this from ​http://www.virtualbox.org/ticket/6613.

I built new ubuntu-10.04 32b and 64b guests on my win7 64b host with 2d and 3d disabled. Everything seemed ok with the guests, so for each guest I shutdown, created a snapshot, rebooted, installed the GA, shutdown, created another snapshot and rebooted.

Unfortunately, after a number of reboots, the post-GA snapshot guest cannot find the network and reports "No network connection". However, the network icon at the bottom of the VB screen says "Adapter 1 (NAT): cable connected". If I go back to the pre-GA snapshot, then even after a number of reboots, the guest is always able to find the network.

How can I help debug this? What other information do you need?

[simon marshall]

32b pre-GA

[simon marshall]

32b post-GA

[simon marshall]

64b pre-GA

[simon marshall]

64b post-GA

[vasily Levchenko]

what output of

# ifconfig -a 

on your guest machine. from NAT perspective it reports that IP address was leased. is your gate (10.0.2.2) pingable and arpingable?

[simon marshall]

Replying to Hachiman:

what output of

# ifconfig -a 

on your guest machine. from NAT perspective it reports that IP address was leased. is your gate (10.0.2.2) pingable and arpingable?

Thanks for you response. On Ubuntu 32bit + guest additions, I get:

$ ifconfig -a
eth0      Link encap:Ethernet  HWaddr 08:00:27:ad:a2:ef  
          inet6 addr: fe80::a00:27ff:fead:a2ef/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:468 (468.0 B)
          Interrupt:10 Base address:0xd020 

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:480 (480.0 B)  TX bytes:480 (480.0 B)

On a concurrently run Ubuntu 64bit - guest additions, I get something similar, but with an "inet" entry for eth0. Is that the problem, that the above lacks an "inet" entry for eth0?

For the other:

$ ping -c 3 10.0.2.2
connect: Network is unreachable
$ arping -c 3 10.0.2.2
WARNING: interface is ignored: Operation not permitted
connect: Network is unreachable

They work fine on the Ubuntu 64bit - guest additions.

[vasily Levchenko]

Replying to marshals: Hm, could you please collect ​pcap-file and send it to me (vasily _dot_ levchenko _at_ Sun _dot_ COM) for further investigations?

[simon marshall]

Replying to Hachiman:

Hm, could you please collect ​pcap-file and send it to me

thanks, done.

[vasily Levchenko]

Replying to marshals:

Replying to Hachiman:

Hm, could you please collect ​pcap-file and send it to me

thanks, done.

thank you. For record, received pcap log contains only IPv6 traffic, but logs attached shows that DHCP requests was received and leases was done (UDP/IPv4).

[vasily Levchenko]

Replying to Hachiman:

Replying to marshals:

Replying to Hachiman:

Hm, could you please collect ​pcap-file and send it to me

thanks, done.

thank you. For record, received pcap log contains only IPv6 traffic, but logs attached shows that DHCP requests was received and leases was done (UDP/IPv4).

Ah, no indeed postGA contains information that DNS information was fetched but not leases IP address. what happens if:

# sudo dhclient eth0

?

[simon marshall]

Replying to Hachiman:

Ah, no indeed postGA contains information that DNS information was fetched but not leases IP address. what happens if:

# sudo dhclient eth0

From the ga snapshot, once the guest has announced its failure to get a network connection, I get:

Internet Systems Consortium DHCP Client V3.1.3
Copyright 2004-2009 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth0/08:00:27:ad:a2:ef
Sending on   LPF/eth0/08:00:27:ad:a2:ef
Sending on   Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
DHCPOFFER of 10.0.2.15 from 10.0.2.2
DHCPREQUEST of 10.0.2.15 on eth0 to 255.255.255.255 port 67
DHCPACK of 10.0.2.15 from 10.0.2.2
bound to 10.0.2.15 -- renewal in 38941 seconds.

[vasily Levchenko]

Have manual dhclient execution restored connectivity for you? I guess you haven't changed default behavior (acquiring IP via network manager), right? What version of Ubuntu do you use?

[simon marshall]

Replying to Hachiman:

I guess you haven't changed default behavior (acquiring IP via network manager), right? What version of Ubuntu do you use?

I haven't changed the VM network configuration in VB in the host or changed the network configuration in the guest itself. This is Ubuntu-10.04 32bit and 64bit, and also Kubuntu-10.04 32bit (I don't have 64bit). The VM has PCnet-FAST III(NAT).

[vasily Levchenko]

Replying to marshals:

Replying to Hachiman:

I guess you haven't changed default behavior (acquiring IP via network manager), right? What version of Ubuntu do you use?

I haven't changed the VM network configuration in VB in the host or changed the network configuration in the guest itself. This is Ubuntu-10.04 32bit and 64bit, and also Kubuntu-10.04 32bit (I don't have 64bit). The VM has PCnet-FAST III(NAT).

by "default behavior" I've meant using network manager, other way is manual editing /etc/network/interfaces file (all that activity on the guest).

BTW: Have manual dhclient execution restored connectivity for you?

[simon marshall]

Replying to Hachiman:

by "default behavior" I've meant using network manager, other way is manual editing /etc/network/interfaces file (all that activity on the guest).

(I wasn't sure exactly what you meant - fortunately I hadn't changed anything at all ;-)

BTW: Have manual dhclient execution restored connectivity for you?

Not automatically, no. But it seems I can get the network to work in the guest if I select "Auto eth0" from the network menu (from the icon in the top panel which shows the network is disconnected).

Why should this problem only occur if guest additions are installed? I should say, now I have started the guest many times to test this problem, that very occasionally the guest does start and see the network. I think (but cannot be 100% sure) that I have also seen a network failure when booting from the snapshot that does not have guest additions installed, but I have not managed to reproduce it. (At the time I was testing the VB crashes that tu4rned out to be due to Intel drivers in the host.)

So could it be an issue (timing?) in the interaction between VB and the guest when the VM is started, greatly acerbated by guest additions?

I'm guessing obviously. What would you like me to do to try and solve this issue?

[simon marshall]

I can confirm this is still a problem with VB-3.2.4.

[simon marshall]

Replying to marshals:

I can confirm this is still a problem with VB-3.2.4.

And 3.2.8.

However, see ​http://forums.virtualbox.org/viewtopic.php?f=3&t=30594&start=0#p156407.