virtualbox.org

I use VirtualBox as a sandbox for things. I have it set to use a network card (vmcard from here on out). My host does not use that network card, it has its own.

Before the recent update, vmcard was enabled, but IP4 and 6 were disabled for the host. It has always been set like that as when both cards are turned on, it broke host windows file and printer sharing. The VM had no issue using the card as it was set to bridge, so it was not piggybacking on the hosts internal IP.

First off, the only reason I updated is because my VM refused to start suddenly and for no apparent reason after a reboot. Now it's the bane of my existence as it does this stupid thing of telling me it can't use vmcard as it does not have an IP. So I have to go, enable IP4, start my VM, then go in and disable IP4 again. All because of some new and terrible detection you have added.

Is there a setting somewhere that will let my VM boot even if it detects a "broken" network?

There are existing topics already discussing this issue I believe. I don't have a note of them, but you could try searching. Something to do with IPv4 vs IPv6 perhaps.

Please open a ticket for this (unless there is one already). This restriction is not exactly intentional, but I don't know how feasible it is to get rid of it. You're not the first one to complain and that's why a single ticket is much better than scattered forum posts that no one reads.

mpack wrote:There are existing topics already discussing this issue I believe. I don't have a note of them, but you could try searching. Something to do with IPv4 vs IPv6 perhaps.

I tried searching, but I think I am using the wrong terms, because I didn't find anything on this.

Could not start the machine Windows because the following physical network interfaces were not found:

Realtek PCIe GBE Family Controller (adapter 1)

You can either change the machine's network settings or stop the machine.

Failed to start the virtual machine Windows.

Nonexistent host networking interface, name 'Realtek PCIe GBE Family Controller' (VERR_INTERNAL_ERROR).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

Went back to 4.3 since I cannot find a solution for this without enabling host ipv4 and thus ruining my internal network.

Why don't you just configure a dummy IP address which has nothing to do with your networks for the bridged adapter as a workaround?

Martin wrote:Why don't you just configure a dummy IP address which has nothing to do with your networks for the bridged adapter as a workaround?

You mean manually set it to an IP that is outside of my local scope? Sorry, tired.

Yes, exactly.

Martin wrote:Yes, exactly.

Thanks, I'll give that a shot.