Network locks on savestate - Ubuntu 12.04.3 LTS precise32
Posted: 4. Nov 2013, 15:19
Hi,
I am running VirtualBox 4.2.18 r88780 on Win7-64 and a virtual machine created in Vagrant 1.3.5 (precise32 with GuestBoxAdditions 4.2.18).
The guest OS is precise32 (Ubuntu 12.04.3 LTS) and the virtualized network hardware is Intel PRO/1000 MT Desktop (82540EM).
Host is having 8GB RAM and 384 MB is allocated to the guest OS.
If I perfom the following sequence without waiting for the network interface to be brought back up in step 2, the network never comes back up again:
1. savestate
2. startvm <-- note that the network interface is brought back up after 5-50 seconds.
3. savestate
4. startvm <-- no network here.
If I inspect log files while the network is hanging, I see things like this (when waiting in deconfiguring network) -- see attachment.
My workaround right now is to have a cron job running mii-tools once a minute, and if there is no link on eth0, the link is re-negotiated.
FYI: These problems also happen randomly when I run the guest with VBoxVMService on Windows and reboot/standby the machine.
NOTE: This is only happening if Intel PRO/1000 MT Desktop (82540EM) is selected. AMD PCNet and Paravirtualized (virtio) adapter does not expose this problem.
I am running VirtualBox 4.2.18 r88780 on Win7-64 and a virtual machine created in Vagrant 1.3.5 (precise32 with GuestBoxAdditions 4.2.18).
The guest OS is precise32 (Ubuntu 12.04.3 LTS) and the virtualized network hardware is Intel PRO/1000 MT Desktop (82540EM).
Host is having 8GB RAM and 384 MB is allocated to the guest OS.
If I perfom the following sequence without waiting for the network interface to be brought back up in step 2, the network never comes back up again:
1. savestate
2. startvm <-- note that the network interface is brought back up after 5-50 seconds.
3. savestate
4. startvm <-- no network here.
If I inspect log files while the network is hanging, I see things like this (when waiting in deconfiguring network) -- see attachment.
My workaround right now is to have a cron job running mii-tools once a minute, and if there is no link on eth0, the link is re-negotiated.
FYI: These problems also happen randomly when I run the guest with VBoxVMService on Windows and reboot/standby the machine.
NOTE: This is only happening if Intel PRO/1000 MT Desktop (82540EM) is selected. AMD PCNet and Paravirtualized (virtio) adapter does not expose this problem.