Failed to start Windows 7 VM on 3.0 (fresh installation)

  • Thread starter Thread starter rothgar
  • Start date Start date
R

rothgar

Guest
I just installed Proxmox VE 3.0 yesterday and am trying to set up a Windows 7 64 bit VM. I uploaded my Windows 7 iso and created a new VM. When I try to start the VM I get the following error

Code:
[COLOR=#000000][FONT=tahoma]Could not access KVM kernel module: No such file or directory[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]failed to initialize KVM: No such file or directory[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]TASK ERROR: start failed: command '/usr/bin/kvm -id 100 -chardev 'socket,id=qmp,path=/var/run/qemu-server/100.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-server/100.vnc,x509,password -pidfile /var/run/qemu-server/100.pid -daemonize -name jlg-w7-x64-01 -smp 'sockets=1,cores=1' -nodefaults -boot 'menu=on' -vga std -no-hpet -k en-us -m 2048 -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' -drive 'file=/var/lib/vz/template/iso/SW_DVD5_Win_Pro_7w_SP1_64BIT_English_-2_MLF_X17-59279.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' -device 'ahci,id=ahci0,multifunction=on,bus=pci.0,addr=0x7' -drive 'file=/var/lib/vz/images/100/vm-100-disk-1.vmdk,if=none,id=drive-sata0,format=vmdk,aio=native,cache=none' -device 'ide-drive,bus=ahci0.0,drive=drive-sata0,id=sata0,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge' -device 'e1000,mac=42:5C:C4:9D:33:0C,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[/FONT][/COLOR]

I was hoping someone else would be able to help me troubleshoot what is going on with the VM.
 
enable vt in your bios!
 
wow, all of my troubles for that. I'm pretty embarrassed that was the issue because I know I changed that setting in the BIOS but I must not have saved the config. The VM is starting as it should be now. Thanks.

PS. I'd mark the thread as solved but I can't find how to edit the title. So if a mod wants to do that I'd appreciate it.