VM 101 not running TASK ERROR: Failed to run vncproxy.

enzopaez

New Member
Jan 26, 2021
3
0
1
27
Hello,

In a proxmox server I have 2 Container and 2 VM.

1611663521775.png


The 4 were working well from July 2020, until yesterday we had a power cut. The containers start correctly but I can't get the VMs to work.

I get the error:


VM 100 not running
TASK ERROR: Failed to run vncproxy.

In the two VMs.

I have another proxmox server, in which I also have VMs and containers and in that it starts all correctly.
I clarify that I am not an expert in proxmox since the person who configured everything is not there.
 
Hi,
could you also share the output of the VM <ID> - Start task log? The error message you posted is normally from the VM/CT <ID> - Console taks and is expected if the VM cannot be or is not started.
 
Hi,
could you also share the output of the VM <ID> - Start task log? The error message you posted is normally from the VM/CT <ID> - Console taks and is expected if the VM cannot be or is not started.
Could not access KVM kernel module: No such file or directory

kvm: failed to initialize KVM: No such file or directory

TASK ERROR: start failed: command '/usr/bin/kvm -id 101 -name VM-LINK -chardev 'socket,id=qmp,path=/var/run/qemu-server/101.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -pidfile /var/run/qemu-server/101.pid -daemonize -smbios 'type=1,uuid=6b9cd59b-7a39-42a7-97a4-1485a1184e13' -smp '1,sockets=1,cores=1,maxcpus=1' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vga std -vnc unix:/var/run/qemu-server/101.vnc,x509,password -no-hpet -cpu 'kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_reset,hv_vpindex,hv_runtime,hv_relaxed,enforce' -m 1024 -device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e' -device 'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:6594b6a2967b' -device 'ahci,id=ahci0,multifunction=on,bus=pci.0,addr=0x7' -drive 'file=/var/lib/vz/images/101/vm-101-disk-1.vmdk,if=none,id=drive-sata0,format=vmdk,cache=none,aio=native,detect-zeroes=on' -device 'ide-drive,bus=ahci0.0,drive=drive-sata0,id=sata0,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap101i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=86:08:9F:12:0B:D4,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -rtc 'driftfix=slew,base=localtime' -global 'kvm-pit.lost_tick_policy=discard'' failed: exit code 1
 
Please check your host's BIOS and see if virtualization is still enabled.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!