Ubuntu (10.04 LTS) guest - no network after update

[dvds]

Hello forum

I have an ubuntu guest on a ubuntu host, and did yesterday an update of everything, including VirtualBox to 3.2.6. Now, my ubuntu guest is not recognizing the NIC anymore... how can I try to fix this? How can I find more info about what went wrong?

root@guestpc:~# ifconfig -a
eth0 Link encap:Ethernet HWaddr 08:00:27:2e:a4:56
BROADCAST MULTICAST 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:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

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)

It's not UP nor RUNNING

Any idea

[Perryg]

Hopefully you also reboot everything since you upgraded it all.
Anyway check everything in the settings and make sure that they are still valid.
Then run lspci to make sure that the virtual nic is loaded. If so then try the following:
edit the /etc/udev/rules.d/70-persistent-net.rules or you can delete the rules and Linux will configure it on the next boot and see if you get your network back.

[dvds]

Hopefully you also reboot everything since you upgraded it all.

More than once but didn't help...

Anyway check everything in the settings and make sure that they are still valid.

Which settings do you mean? The one in the VBox GUI for the VM? Those are still fine.

Then run lspci to make sure that the virtual nic is loaded. If so then try the following:

Code: Select all

00:03.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 02)
	Subsystem: Intel Corporation Device 001e
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64 (63750ns min)
	Interrupt: pin A routed to IRQ 19
	Region 0: Memory at f0000000 (32-bit, non-prefetchable) [size=128K]
	Region 2: I/O ports at d010 [size=8]
	Capabilities: [dc] Power Management version 2
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [e4] PCI-X non-bridge device
		Command: DPERE- ERO+ RBC=512 OST=1
		Status: Dev=ff:1f.0 64bit- 133MHz- SCD- USC- DC=simple DMMRBC=2048 DMOST=1 DMCRS=8 RSCEM- 266MHz- 533MHz-
	Kernel driver in use: e1000
	Kernel modules: e1000

Is this good or bad?

edit the /etc/udev/rules.d/70-persistent-net.rules or you can delete the rules and Linux will configure it on the next boot and see if you get your network back.

Already tried that, tried now again, still nothing.

This is the re-created file:

Code: Select all

root@guestpc:~# cat /etc/udev/rules.d/70-persistent-net.rules 
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.

# PCI device 0x8086:0x100e (e1000)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="08:00:27:3b:39:a7", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

[Perryg]

From what I can tell here the guest is recognizing the NIC it just does not have an IP address assigned to it.
If running ifconfig eth0 returns information then it sees it and it is active.
Have you tried to trouble shoot the reason on the guest?
Did you also upgrade the guest as well as the host and VBox all at the same time?

[Sasquatch]

Do you by any chance use Bridged on the VM? If you do, then reboot the system and hold down Shift so you get the Grub2 menu. Now select the second kernel entry (the first is the newest, under that is the recovery mode for it, so select the third entry). This should get you back with a working VM network.
I think the problem is with the new kernel Ubuntu released last week and they broke the netflt module with it.

This is assuming you run Ubuntu 10.04.

[dvds]

From what I can tell here the guest is recognizing the NIC it just does not have an IP address assigned to it.
If running ifconfig eth0 returns information then it sees it and it is active.
Have you tried to trouble shoot the reason on the guest?
Did you also upgrade the guest as well as the host and VBox all at the same time?

Do you by any chance use Bridged on the VM? If you do, then reboot the system and hold down Shift so you get the Grub2 menu. Now select the second kernel entry (the first is the newest, under that is the recovery mode for it, so select the third entry). This should get you back with a working VM network.
I think the problem is with the new kernel Ubuntu released last week and they broke the netflt module with it.

This is assuming you run Ubuntu 10.04.

I tried to configure the network directly on the /etc/network/interfaces file, but this didn't help...

Code: Select all

allow-hotplug eth0
iface eth0 inet static
        address 10.1.0.2
        netmask 255.255.255.0

I did an update of everything (host+guest+vbox) after my holidays. The adapter is on an internal network, but not seen as "up&running" from the guest.

I installed a second VM (ubuntu 10.04 too) yesterday, and this one works (using it to write here)...

lan-KO.png (89.91 KiB) Viewed 4604 times

[dvds]

I just tried something, and seems to be working...

Code: Select all

ifconfig eth0 up
ifconfig eth0 10.1.0.2 netmask 255.255.255.0

Now the connection is up&running, and really working... mmh...

[Sasquatch]

Then check the VM config, did you remove the virtual cable (untick the checkbox)? It seems that Ubuntu doesn't detect the cable on boot. Changing the interfaces file to 'auto eth0' instead of 'allow-hotplug eth0' will do the trick too.

[dvds]

Then check the VM config, did you remove the virtual cable (untick the checkbox)? It seems that Ubuntu doesn't detect the cable on boot. Changing the interfaces file to 'auto eth0' instead of 'allow-hotplug eth0' will do the trick too.

Checkbox is still there, didn't touch that... 'auto eth0' works, thanks !

Still weird that it got lost during an update... !

Thanks a lot !

[Sasquatch]

The new VM you created, does it have all the updates like the 'faulty' VM does? If not, update it and check again, one of the updates might have broken interface link detection. If it does, then it's really weird, but I would still guess it's an OS error inside the VM, rather than VB being at fault (the new VM proved that).