Quantcast
Channel: Proxmox Support Forum
Viewing all articles
Browse latest Browse all 171679

Could not access KVM kernel module after upgradeing to 3.4-6

$
0
0
I did an upgrade today of Proxmox to version 3.4-6 I did not take a note of the previose version which was 3.4-something.

I've done upgrades in the past and they have been fine. I was told after the update that there had been a patch to the kernal ( think that was the termenolgy might have been update) and I should reboot this node when I have a chance. I procedded to reboot the node and the machine came backup as normal.

Although none of the VM's will start up. I am getting the following errors:

Could not access KVM kernel module: No such file or directory
failed to initialize KVM: No such file or directory
TASK ERROR: start failed: command '/usr/bin/kvm -id 110 -chardev 'socket,id=qmp,path=/var/run/qemu-server/110.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-server/110.vnc,x509,password -pidfile /var/run/qemu-server/110.pid -daemonize -smbios 'type=1,uuid=22951564-f8ae-4ce1-b247-b664ca248be6' -name KerioOperator -smp '4,sockets=2,cores=2,maxcpus=4' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000' -vga cirrus -cpu kvm64,+lahf_lm,+x2apic,+sep -m 4096 -k en-gb -cpuunits 1000 -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:67b81728199' -device 'ahci,id=ahci0,multifunction=on,bus=pci.0,addr=0x7 ' -drive 'file=/var/lib/vz/images/110/vm-110-disk-1.vmdk,if=none,id=drive-sata0,format=vmdk,aio=native,cache=none,detect-zeroes=on' -device 'ide-drive,bus=ahci0.0,drive=drive-sata0,id=sata0,bootindex=100' -drive 'file=/var/lib/vz/template/iso/kerio-operator-installer-2.3.3-3740-p2.iso,if=none,id=drive-ide2,media=cdrom,aio=native' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -netdev 'type=tap,id=net0,ifname=tap110i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=5A:3C:E1:37:70:33,netdev=net0,bus=pci.0 ,addr=0x12,id=net0,bootindex=300'' failed: exit code 1

Has anyone got any ideas of where I can start to look to resolve this problem. Just as a note this install of Proxmox is runnig on a MacMini and has been running fine for about 5 months and I have upgraded proxmox in the same fasion previously with not problem even going from 3.2 to 3.3 to 3.4

Viewing all articles
Browse latest Browse all 171679

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>