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

Add option for disable or skip Cannot start VM because hardware virtualization technology is already used by another software #3521

Closed
Mario156090 opened this issue Oct 11, 2023 · 4 comments · Fixed by GNS3/gns3-server#2307

Comments

@Mario156090
Copy link

Hello dear GNS3 development team,

In some hardware, as ryzen amd-v technology is possible start two virtualization technology on same time.

So, I believe we need an option for disable the message in the picture and GNS3 try start the VMs.

image

@grossmj
Copy link
Member

grossmj commented Oct 24, 2023

Thanks, have you tried to start both a VMware VM and a VirtualBox or KVM VM?

@Mario156090
Copy link
Author

Thanks, have you tried to start both a VMware VM and a VirtualBox or KVM VM?

Hello @grossmj I tried to start Vmware Workstation and Cisco IosV at same time, so this is possible from GNS3 only if you press the play every nodes at same time. But if you use for example 4 or more nodes with differents technologys GNS3 show the message on top thread, but if you turn on QEMUKVM from GNS3 and turn on Vmware VM from vmware workstation control panel you can got on both technologys.

@grossmj
Copy link
Member

grossmj commented Oct 29, 2023

Thanks, I think we should probably remove this check altogether.

@grossmj
Copy link
Member

grossmj commented Oct 30, 2023

This was already removed from our 3.0 branch, I just added the option to disable it in 2.2. Edit gns3_server.conf and add hardware_virtualization_check = False to the file.

Example:

[Server]
; check if hardware virtualization is used by other emulators (KVM, VMware or VirtualBox)
hardware_virtualization_check = False

@grossmj grossmj closed this as completed Oct 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants