Proxmox VM Creation Issue

[SnipeYa]

So I've installed Proxmox on a server I have at home and when I try and start a newly created VM (will eventually be windows 7) it comes up with this error, Could someone please help me out I'm usually pretty good at reading error codes and debugging but this just makes no sense to me. 

Running as unit 101.scope.
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/systemd-run --scope --slice qemu --unit 101 -p 'KillMode=none' -p 'CPUShares=1000' /usr/bin/kvm -id 101 -chardev 'socket,id=qmp,path=/var/run/qemu-server/101.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-server/101.vnc,x509,password -pidfile /var/run/qemu-server/101.pid -daemonize -smbios 'type=1,uuid=15487413-99c2-48bc-9591-b04d3b32a36a' -name Win7 -smp '1,sockets=1,cores=1,maxcpus=1' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000' -vga std -no-hpet -cpu 'kvm64,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_relaxed,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,enforce' -m 2048 -k en-us -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:72afb36c8a6' -drive 'file=/dev/cdrom,if=none,id=drive-ide2,media=cdrom,aio=threads' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -drive 'file=/var/lib/vz/images/101/vm-101-disk-1.qcow2,if=none,id=drive-ide0,format=qcow2,cache=none,aio=native,detect-zeroes=on' -device 'ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=100' -rtc 'driftfix=slew,base=localtime' -global 'kvm-pit.lost_tick_policy=discard'' failed: exit code 1

 

[Hamosch]

Have you updated everything and are you running as root or admin with the correct permissions (you might just want to verify that it's working by logging in to the web interface as root)

 

I can check the error code more thoroughly once I get home, but it seems to me you don't pass it a .iso for the installation?

 

Also a quick google search showed that it's common error if you don't have virtualization (vt-x, assuming Intel also might want to enable vt-d if your CPU supports it) enabled in BIOS.

If I remember correctly from when I installed ProXmoX (quite a while ago now) you also might need to tell KVM/qemu that your using kvm_intel or kvm_amd (?) in some flag somewhere.

[tt2468]

5 hours ago, SnipeYa said:

So I've installed Proxmox on a server I have at home and when I try and start a newly created VM (will eventually be windows 7) it comes up with this error, Could someone please help me out I'm usually pretty good at reading error codes and debugging but this just makes no sense to me. 

Running as unit 101.scope.
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/systemd-run --scope --slice qemu --unit 101 -p 'KillMode=none' -p 'CPUShares=1000' /usr/bin/kvm -id 101 -chardev 'socket,id=qmp,path=/var/run/qemu-server/101.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-server/101.vnc,x509,password -pidfile /var/run/qemu-server/101.pid -daemonize -smbios 'type=1,uuid=15487413-99c2-48bc-9591-b04d3b32a36a' -name Win7 -smp '1,sockets=1,cores=1,maxcpus=1' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000' -vga std -no-hpet -cpu 'kvm64,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_relaxed,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,enforce' -m 2048 -k en-us -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:72afb36c8a6' -drive 'file=/dev/cdrom,if=none,id=drive-ide2,media=cdrom,aio=threads' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -drive 'file=/var/lib/vz/images/101/vm-101-disk-1.qcow2,if=none,id=drive-ide0,format=qcow2,cache=none,aio=native,detect-zeroes=on' -device 'ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=100' -rtc 'driftfix=slew,base=localtime' -global 'kvm-pit.lost_tick_policy=discard'' failed: exit code 1

 

Are you sure it is done configuring the server? It seems to not find the vm, even though you created it. As Hamosch stated, make sure you are logged in with root. Are you able to post a screenshot of your webui?

[SnipeYa]

12 hours ago, Hamosch said:

Have you updated everything and are you running as root or admin with the correct permissions (you might just want to verify that it's working by logging in to the web interface as root)

 

I can check the error code more thoroughly once I get home, but it seems to me you don't pass it a .iso for the installation?

 

Also a quick google search showed that it's common error if you don't have virtualization (vt-x, assuming Intel also might want to enable vt-d if your CPU supports it) enabled in BIOS.

If I remember correctly from when I installed ProXmoX (quite a while ago now) you also might need to tell KVM/qemu that your using kvm_intel or kvm_amd (?) in some flag somewhere.

I've only just installed version 4.1, So I'd expect things to be upto date. As for permissions I created the VM from the web UI as root, then uploaded the windows 7 iso and set it as the installation media.

The server itself has 2 Xeon E5420's in it so unless virtualization is disabled in the bios all should be well there. But I'm fairly certain I've checked that already.

 

8 hours ago, Kyle Manning said:

Are you sure it is done configuring the server? It seems to not find the vm, even though you created it. As Hamosch stated, make sure you are logged in with root. Are you able to post a screenshot of your webui?

I'll get a screenshot when I get home from work, Not sure why it wouldn't find it the VHD and Installation ISO are both there on the server(at least i think so seeing them from the web UI).

[Hamosch]

3 hours ago, SnipeYa said:

I've only just installed version 4.1, So I'd expect things to be upto date. As for permissions I created the VM from the web UI as root, then uploaded the windows 7 iso and set it as the installation media.

The server itself has 2 Xeon E5420's in it so unless virtualization is disabled in the bios all should be well there. But I'm fairly certain I've checked that already.

 

I'll get a screenshot when I get home from work, Not sure why it wouldn't find it the VHD and Installation ISO are both there on the server(at least i think so seeing them from the web UI).

Ok, so what I would  do is :

• try to set up a new VM with the ISO selected at creation time (just to eliminate the chance that you didn't add it correctly). The fact that the error code does show the entire config but no target to an ISO file just seems off to me.
• Verify that virtualization is enabled in the BIOS.
• Also try if the following helps (this should make sure the required module is loaded): (could be outdated since the update to kernel V4, but im not sure, haven't had had any similar issues since the update)

• > modprobe kvm-intel

 

[SnipeYa]

4 hours ago, Hamosch said:

 

 

14 hours ago, Kyle Manning said:

 

 

18 hours ago, Hamosch said:

 

Turns out the system ROM was busted and kept disabling visualization for whatever reason, So now its running from the secondary backup ROM. 

 

Thanks for the help I had swore I turned it on so I didn't think to check it again and when i did I found this odd issue.

 

While we're all here how do I pass through a graphics card to a VM, I've looked for tutorials but can't seem to find any?

[Hamosch]

39 minutes ago, SnipeYa said:

 

 

Turns out the system ROM was busted and kept disabling visualization for whatever reason, So now its running from the secondary backup ROM. 

 

Thanks for the help I had swore I turned it on so I didn't think to check it again and when i did I found this odd issue.

 

While we're all here how do I pass through a graphics card to a VM, I've looked for tutorials but can't seem to find any?

as suspected,

anyway, GPU passthrough (or PCI passthrough) is a little trickier and requires you to go into the terminal. 

 

https://pve.proxmox.com/wiki/Pci_passthrough

https://www.reddit.com/r/pcmasterrace/comments/3lno0t/gpu_passthrough_revisited_an_updated_guide_on_how/

 

I have only used it for hdd and nic passthrough (as mine is a homelab with no need for a gpu), but I know that GPU passthrough can be quite tricky.