tags: [VirtualBox,Ubuntu,Windows,Nerwork,VM]
Copy the code

Problem Description:

When using VirtualBox to start a VM, two problems occur one by one

Mistake # 1:

(D) Nonexistent Host Networking Interface, Name 'Intel(R) Dual Band Wire-AC 8265' (VERR_INTERNAL_ERROR) return code E_FALL (0x80004005) Component: ConsoleWrap Iconsole {872da645-4a9b-1727-bee2-5585105b9eed}Copy the code

Possible cause: The VM is created on the previous computer, the network configuration on the previous device is used and then opened on the new computer. The bridge network interface remains the previous configuration, so the network interface does not exist

Solution:

Refer to the answer above to modify the.vbox virtual machine configuration file

<BridgedInterface name="Intel(R) Dual Band Wireless-AC 8265"/> to this: <BridgedInterface name=" current network interface device name "/>Copy the code

Hope this helps someone else.

Reference:

  • Nonexistent host networking interface

  • Get name of network that a network interface is connected to

Second mistake:

Description: For the first problem, I tried switching between different snapshots to solve the problem, but nothing worked and then a second error occurred

Virtual machine console - error ❌ cannot open a new task for virtual machine Linux 🔽 detail (D) cpum#1: X86_CPUID_FEATURE_ECX_PCID is not supported by the host but has already exposed to the guest [ver=19 pass=final] (VERR_SSM_LOAD_CPUID_MISMATCH) . Return code E_FALL (0x80004005) Component: ConsoleWrap interface: Iconsole {872DA645-4a9B-1727-Bee2-5585105b9eed}Copy the code

Cause analysis:

no

Solution:

The saved Virtualbox state cannot be restored

The first solution is actually here Cannot resume Saved Virtualbox State

However, I was not familiar with the use of VirtualBox at the time, and the question pointed to this discussion

There are two points in this discussion that indicate problems

When the VM is in saved state, the Discard button (yellow arrow pointing down) will be enabled. It’s next to the Start button. You don’t have to export and import anything, nor discard snapshots from the Snapshots tab. All you do with the discard button, is clear the ‘hibernate’ state. Same thing that you can do to Windows that is in hibernate, and you hit a key before it starts to resume from it, and select “Continue without resume” or similar from the menu you get. Or even better, the system is in standby, and you just pull the power cord

.

Ah, thank you. Very helpful.

So this is actually a good example of what I find confusing. It appears that there are actually three different “discard” actions? There is the big yellow button (which doesn’t tell you what it is going to discard — I assumed it would discard the entire virtual machine), there is the right-click on the current state and the right-click on a snapshot, each of which corresponds to a different keystroke. Not obvious.

Anyway, thank you again!

⚠️ Key: The virtualBox Manager menu option has a yellow down arrow button. Click this to discard state.

The specific reason might be to clear something, because it was switching the snapshot that caused the second problem

Before clearing:

Click Clear:

Reference:

  • Cannot resume saved Virtualbox state
  • VERR_SSM_LOAD_CPUID_MISMATCH error on Jaunty