Hello!
I have been looking into VM hypervisor solutions for my organization and have been playing around with Proxmox recently.
I am trying to set up an evaluation system on one of my existing Debian hosts so that I can demonstrate Proxmox to others. I am doing this via a nested KVM setup.
However, I am running into an error which prevents Proxmox from starting any of the VMs I have tried to create.
I get the following error message:
This is a nested-kvm setup. My hardware is a Dell OptiPlex 3020 with an Intel i5-4570 (Haswell). The top-level hypervisor OS is Debian Unstable updated as of yesterday with qemu 2.8.
This same nested-kvm setup is working fine on my desktop system, which is a newer i5-6500 (Skylake), so I know that the nested KVM works in that situation.
The Dell system above was previously on Debian stable and was giving the same error message. I found the thread below and assumed the solution was to simply upgrade the qemu version to something newer:
https://forum.proxmox.com/threads/n...-host-doesnt-support-requested-feature.23289/
But now that I've gone from Debian stable (qemu 2.1) to unstable (qemu 2.8), the same problem exists.
Any advice?
I will look into figuring out how to edit the -cpu arguments in Proxmox and maybe remove the "enforce", but I am not sure how to do that yet. It doesn't look like there is any way to edit that kind of detail from the proxmox Web UI and I don't know the config files well enough yet to know where to look.
I have been looking into VM hypervisor solutions for my organization and have been playing around with Proxmox recently.
I am trying to set up an evaluation system on one of my existing Debian hosts so that I can demonstrate Proxmox to others. I am doing this via a nested KVM setup.
However, I am running into an error which prevents Proxmox from starting any of the VMs I have tried to create.
I get the following error message:
Code:
warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1]
kvm: Host doesn't support requested features
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' -pidfile /var/run/qemu-server/100.pid -daemonize -smbios 'type=1,uuid=d6f7d1f0-68cf-4588-8d2f-7d6e4ee40414' -name Linux-mint18-test1 -smp '2,sockets=2,cores=1,maxcpus=2' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vga qxl -vnc unix:/var/run/qemu-server/100.vnc,x509,password -cpu kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,enforce -m 2048 -k en-us -device 'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' -device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e' -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -spice 'tls-port=61000,addr=localhost,tls-ciphers=DES-CBC3-SHA,seamless-migration=on' -device 'virtio-serial,id=spice,bus=pci.0,addr=0x9' -chardev 'spicevmc,id=vdagent,name=vdagent' -device 'virtserialport,chardev=vdagent,name=com.redhat.spice.0' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:1a15274b4e55' -drive 'file=/var/lib/vz/template/iso/linuxmint-18.1-cinnamon-64bit.iso,if=none,id=drive-ide2,media=cdrom,aio=threads' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -netdev 'type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=4E:9D:C4:32:66:83,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300'' failed: exit code 1This is a nested-kvm setup. My hardware is a Dell OptiPlex 3020 with an Intel i5-4570 (Haswell). The top-level hypervisor OS is Debian Unstable updated as of yesterday with qemu 2.8.
This same nested-kvm setup is working fine on my desktop system, which is a newer i5-6500 (Skylake), so I know that the nested KVM works in that situation.
The Dell system above was previously on Debian stable and was giving the same error message. I found the thread below and assumed the solution was to simply upgrade the qemu version to something newer:
https://forum.proxmox.com/threads/n...-host-doesnt-support-requested-feature.23289/
But now that I've gone from Debian stable (qemu 2.1) to unstable (qemu 2.8), the same problem exists.
Any advice?
I will look into figuring out how to edit the -cpu arguments in Proxmox and maybe remove the "enforce", but I am not sure how to do that yet. It doesn't look like there is any way to edit that kind of detail from the proxmox Web UI and I don't know the config files well enough yet to know where to look.