Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Device 'vmnet-macos' could not be initialized Error #3659

Open
gradygambrell opened this issue Feb 21, 2022 · 3 comments
Open

Device 'vmnet-macos' could not be initialized Error #3659

gradygambrell opened this issue Feb 21, 2022 · 3 comments
Labels
question Further information is requested

Comments

@gradygambrell
Copy link

gradygambrell commented Feb 21, 2022

Describe the issue
qemu-aarch64-softmmu: -netdev
vmnet-macos,mode=shared,id=netO:
Device 'vmnet-macos' could not be
initialized
This error appeared when trying to install Windows 10/11.

Configuration

  • UTM Version: 3.0.4
  • OS Version: 12.2
  • Intel or Apple Silicon? Apple

Screen Shot 2022-02-21 at 1 02 52 PM

Upload VM
Unable to due to file size on Google Drive

@conath
Copy link
Contributor

conath commented Feb 24, 2022

Please try restarting your Mac. I get this error sometimes and restarting my Mac has always fixed it.

And a note, for a Windows guest I would choose "bridged" network mode. In my experience it works better for Windows network connectivity.

@conath conath changed the title qemu-aarch64-softmmu: -netdev vmnet-macos,mode=shared,id=netO: Device 'vmnet-macos' could not be initialized Error Device 'vmnet-macos' could not be initialized Error Feb 24, 2022
@conath conath added the question Further information is requested label Feb 24, 2022
@conath
Copy link
Contributor

conath commented Feb 24, 2022

Could also be #3636; @gradygambrell are you using macOS Internet Sharing? In that case please try changing the Network Mode to Emulated VLAN to get around this error.

@webong
Copy link

webong commented Apr 11, 2022

Could also be #3636; @gradygambrell are you using macOS Internet Sharing? In that case please try changing the Network Mode to Emulated VLAN to get around this error.

Thanks @conath, this worked for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants