virtualbox.org

One thing that could help with figuring what your guest has set up now is if you posted the guest's .vbox file. Please right-click the guest in the main Virtualbox window's guest list, choose "Show in whatever-Linux-calls-its-file-&-folder-browser". In the window that opens, zip the guest's .vbox file, and post the zip file, using the forum's Upload Attachment tab.

Syntetik Vision wrote:use Intel PRO/1000 MT Server (82545EM) since this is a server instead of Intel PRO/1000 MT Desktop (82540EM)

I have not found that "server" vs "desktop" in the network adapter interferes, unless the guest OS has built-in drivers for one instead of the other. Other "server-class" capabilities like teaming & VLANs might be in one vs the other, and might be more suitable for setting up in the host hardware instead of the guest. FWIW XP has built-in drivers for the T server, not the MT Desktop. The 10/100/1000mbps of the different cards does not factor in, Virtualbox feeds network data to the guest as fast as the host hardware can receive it.

"Virtualbox Networks In Pictures" is about the kinds of networking available in the "Attached To" dropdown, not the "Adapter Type" dropdown. It's for what the guest networks to, not what card is used in the guest hardware. Often, the card picked by the New Guest Wizard when the guest is first set up is the best one to continue using, because the guest has built-in drivers for it.

From my previous quotes of the VBox.log file, the first group of 8 lines represent the information coming from the .vbox file. That means that there are only 4 network adapters configured, and at the time they have been configured, the 4th host network adapter had no number in its name.

When the VM is started, VirtualBox creates 4 internal network adapters IntNet#0-3, attaches them to the configured host adapters #113, #85, #112 and the numberless one, and provides 4 virtual network adapters E1000#0-3 to the guest.

When the VM is later suspended, the host network adapter with the number #111 turns up, and VirtualBox attaches its 5th internal network adapter IntNet#4 to it.

My first guess would be that the 4th network adapter is simply connected to the wrong (maybe non-existing) host network adapter. My second guess would be that each of these adapters can be missing its number sometimes, and that will lead to unexpected consequences: VirtualBox enumerates the host network adapters, at least when starting and resuming a VM, and the enumerated names are matched to the VirtualBox configuration, so they are supposed to be stable. Host network adapters may be not available at some times, but they may not change their name for VirtualBox to work correctly.

Sorry for the late reply, i didnt saw the second page of this thread.

In the attach, you have the .vbox file of the host. Already saw and everythings seems fine.

I saw some TX hangs related to some interfaces on the guests, that could also explain or give some clues for this weird behavior.

But as i said, this setup was working fine for months, the changes were the upgrade of Virtualbox and guest's Centos 7.

Thank you.

Definitely only 4 network cards, and no indication there has been a fifth.

Only thing I can suggest is to downgrade Virtualbox to what it was before and see if stable operation resumes.

Yes, i will try as soon as possible. Do you know if its possible to prevent Virtualbox to generate that dialog box ?

At least for now, i could start the servers if they go down with a powershell script but the machine dont go down until i click on the ok for close that dialog.

Thank you Scott

I found i way to disable errors dialog box on the ibm site

Find the following key in the registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Windows

Modify the value of "ErrorMode" according to these options:

Value Description
-------- -----------------
0 All errors appear in popups (Default)
1 System errors disabled, application errors still using popups
2 Neither system nor application errors use popups

Setting the value to 2 will disable all error message popups.

But i still need to test with older version of Virtualbox to see if the crashs stop.