Error when I create new VM

[majorgear]

you should put this option of your VM you have create on prox mox at No , KVM HARDWARE virtualisation --->NO
View attachment 24943

That is bad advice as it makes your VM's run slowly.

 

[sukupandachu]

you should put this option of your VM you have create on prox mox at No , KVM HARDWARE virtualisation --->NO

This worked. Thanks very much.
Although it is indeed very slow in my setup, even keyboard events take very long to execute.

My setup:
VBOX running on Windows, Dell 7480 laptop.
VBOX_VM setup with Nested VT-x/AMD-V/PAE/NX, KVM Paravirtualization
Proxmox 8.2 running on this VBOX_VM.
Containers work well on this Proxmox.
But I am trying to run some OPNSense simulation, so I need to run OPNSense as VM inside Proxmox.

 

[yonoss]

I got a similar issue today. The context is different though and the suggested fix doesn't solve the problem:
I woke up this morning realizing that the proxmox console was acting weirdly: showing just question marks in front of each VM and node. Some of the VMs were running though as I was able to access them.
So I triggered a restart, and after the restart, none of the VMs was starting anymore, throwing the error:

TASK ERROR: KVM virtualisation configured, but not available. Either disable in VM configuration or enable in BIOS.

Note that nothing was changed in Bios, and everything was working OK 12 hours ago.

After changing the KVM HARDWARE virtualisation --->NO the VMs are throwing a different error:

Error: Unknown device type.
can't create interface fwln100i0 - command '/sbin/ip link add name fwln100i0 mtu 1500 type veth peer name fwpr100p0 mtu 1500' failed: exit code 2

kvm: -netdev type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown: network script /var/lib/qemu-server/pve-bridge failed with status 512
TASK ERROR: start failed: QEMU exited with code 1

Any idea what is going on?
Thanks

 

[mukesh.73411]

you should put this option of your VM you have create on prox mox at No , KVM HARDWARE virtualisation --->NO
View attachment 24943

Thank you very much for the clear explanation

 

[Stereoscope]

That is bad advice as it makes your VM's run slowly.

What's the solution then? My Vt-d is enabled in BIOS and I certainly don't want slow performance.
I figured it out for my case. I was running Proxmox in VirtualBox. You also need to enable Vt-d in Virtual Box.

 

[joelrox]

Login into web console -> Click the vm -> Options -> Disable KVM hardware virtualization

 

[elamast]

What worked for me was to change the processor type (under hardware) to qemu64. This works with KVM virtualization on with my Optiplex 780 BIOS A14.

 

[denis.andrade]

you should put this option of your VM you have create on prox mox at No , KVM HARDWARE virtualisation --->NO
View attachment 24943

thank you very much!!