Closed a1exsok closed 4 years ago
@alex22sok
It looks like you have done this configuration on macOS (client side). You need to do it on the server itself, in the GNS3 VM.
@grossmj
Yes, you are correct. After creating gns3_server.conf
, on the GNS3VM Server itself, with the below input appended, the issue is resolved:
[Qemu]
enable_hardware_acceleration = False
require_hardware_acceleration = False
@grossmj Sim você está correto. Depois de criar
gns3_server.conf
, no próprio servidor GNS3VM, com a entrada abaixo anexada, o problema é resolvido:[Qemu] enable_hardware_acceleration = False require_hardware_acceleration = False
funcionou, obrigado
@grossmj Yes, you are correct. After creating
gns3_server.conf
, on the GNS3VM Server itself, with the below input appended, the issue is resolved:[Qemu] enable_hardware_acceleration = False require_hardware_acceleration = False
Thanks, it worked for me on MAC M1 chips with Gns3 VMfusion
Where exactly does gns3_server.conf should be created in Windows ? It's very difficult to find help regarding these rare errors.
error while starting ...: KVM acceleration cannot be used (/dev/kvm doesn't exist). It is possible to turn off KVM support in the gns3_server.conf by adding enable_kvm = false to the [Qemu] section.
KVM acceleration cannot be used (/dev/kvm doesn't exist). It is possible to turn off KVM support in the gns3_server.conf by adding enable_kvm = false to the [Qemu] section.
The gns3_server.conf
is located in %APPDATA%\GNS3\2.2
by default.
I'm on Windows and the file extension is ini
file not conf
for some reason, despite GNS3 referring to conf
.
Added to gns3_server.ini
:
[Qemu]
enable_kvm = false
enable_hardware_acceleration = False
require_hardware_acceleration = False
Didn't work..
Later added same lines in GNS3 VM to file gns3_server.conf
in ~/GNS3/ and home directory and didn't work...
GNS3 VM screenshot:
Edit:
It somehow started working after several full restarts and corrupted Windows startup repairs due to latest Win update..
Now GNS3 VM shows KVM support available: True
.
And I can successfully launch a Qemu template router.
Although another problem arises when starting a router and opening a console, boot loop:
iPXE (http://ipxe.org) 00:06.0 CD00 PCI2.10 PnP PMM 3FF8C5F0 3FECC5F0 CD00
iPXE (http://ipxe.org) 00:07.0 CE00 PCI2.10 PnP PMM 3FF8C5F0 3FECC5F0 CE00
iPXE (http://ipxe.org) 00:0A.0 D100 PCI2.10 PnP PMM 3FF8C5F0 3FECC5F0 D100
iPXE (http://ipxe.org) 00:08.0 CF00 PCI2.10 PnP PMM 3FF8C5F0 3FECC5F0 CF00
iPXE (http://ipxe.org) 00:0B.0 D200 PCI2.10 PnP PMM 3FF8C5F0 3FECC5F0 D200
iPXE (http://ipxe.org) 00:09.0 D000 PCI2.10 PnP PMM 3FF8C5F0 3FECC5F0 D000
iPXE (http://ipxe.org) 00:0C.0 D300 PCI2.10 PnP PMM 3FF8C5F0 3FECC5F0 D300
Booting from Hard Disk...
Load system
SeaBIOS (version 1.13.0-1ubuntu1.1)
Machine UUID 862c7d93...
Booting from Hard Disk...
.config/GNS3/2.2/gns3_server.conf = here is the file that you want to add the following commands if you can not see the file. open the home page and press CTRL + H or you can use the terminal "vi" command before use this command "sudo apt install vim" to edit the file
[Qemu] enable_hardware_acceleration = False require_hardware_acceleration = False
Thank you guys
it works on me
.config/GNS3/2.2/gns3_server.conf = here is the file that you want to add the following commands if you can not see the file. open the home page and press CTRL + H or you can use the terminal "vi" command before use this command "sudo apt install vim" to edit the file
[Qemu] enable_hardware_acceleration = False require_hardware_acceleration = False
Thank you guys
it works on me
Thank you.
Running GNS3VM on AWS EC2 Ubuntu without KVM support and would like to disable KVM. Connecting from Mac GNS3 GUI, using OpenVPN.
Constantly getting the same error, when trying to start the Qemu Node.
=> error while starting appdconsole-1: KVM acceleration cannot be used (/dev/kvm doesn't exist). It is possible to turn off KVM support in the gns3_server.conf by adding enable_kvm = false to the [Qemu] section.
• Have tried to use old syntax of disabling, which is
• Also, have tried to use a new version of the same, per Qemu Mips for gns3
• Didn't help. Not possible to ignore that message, unfortunately...
Client Env: • OS: MacOS 10.15.5 • gns3gui : 2.2.13, running on MacOS
GNS3VM Env, remote: • OS: Ubuntu 18.04.5 LTS • gns3server : 2.2.13