Opened 2 years ago
#21531 new defect
Directly opening VM settings to resolve "missing adapter" message after import fails
Reported by: | ViperPotato | Owned by: | |
---|---|---|---|
Component: | network | Version: | VirtualBox-7.0.4 |
Keywords: | Cc: | ||
Guest type: | other | Host type: | other |
Description ¶
I'm importing an appliance exported from a Linux host with a host-only network 'vboxnet0' on a Windows 10 host without such a network adapter present.
On powering up, I'm notified about the missing host-only network 'vboxnet0', and I have two options:
- Change Network Settings
- Close VM
When I select the first option, the VM settings window opens for a split second before crashing. Powering up the VM again leads to the same behavior.
Opening the VM settings manually, choosing an appropriate host-only network, and saving works around this issue.
This happend after going from 7.0.2 to 7.0.4 and is still present in the current test build 7.0.97.
Log from 7.0.6 attached.