pve 4.0 beta nested can't start vm inside

mmenaz

Renowned Member
Jun 25, 2009
835
26
93
Northern east Italy
Hi, I've a 3.4 Proxmox on intel Xeon CPU. To do some experiment, I have:
- installed a 3.4 pve VM with CPU "host", and created a VM inside, disabled "KVM Hardware virtualization", and works fine (slow but starts)
- done the same with a 4.0 pve (updated to the latest packages available), but I get the error:
warning: TCG doesn't support requested feature: CPUID.01H:EDX.de [bit 2]
here what happens:
Code:
root@prox4:~# qm start 100
Running as unit 100.scope.
warning: TCG doesn't support requested feature: CPUID.01H:EDX.de [bit 2]
warning: TCG doesn't support requested feature: CPUID.80000001H:EDX [bit 2]
kvm: TCG doesn't support requested features
start failed: command '/usr/bin/systemd-run --scope --slice qemu --unit 100 -p 'CPUShares=1000' /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 -smbios 'type=1,uuid=8c04f40c-c4ad-45b0-82c1-95bcd9ce7356' -name sss -smp '1,sockets=1,cores=1,maxcpus=1' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000' -vga cirrus -cpu qemu64,enforce -m 512 -k it -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:c88193d57443' -drive '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/100/vm-100-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' -netdev 'type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=AA:86:51:57:3D:44,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -machine 'accel=tcg'' failed: exit code 1

this is the VM config:
Code:
# qm config 100
bootdisk: virtio0
cores: 1
ide0: local:100/vm-100-disk-1.qcow2,size=1G
ide2: none,media=cdrom
kvm: 0
memory: 512
name: sss
net0: e1000=AA:86:51:57:3D:44,bridge=vmbr0
numa: 0
ostype: l26
smbios1: uuid=8c04f40c-c4ad-45b0-82c1-95bcd9ce7356
sockets: 1

and here it's "host" VM (the config of the vm is running Proxmox 4)
Code:
# qm config 803
bootdisk: virtio0
cores: 2
cpu: host
description: proxmox  4 beta 1 IP .76%0A
ide2: none,media=cdrom
memory: 4096
name: prox4
net0: virtio=32:43:54:D9:B5:80,bridge=vmbr0
numa: 0
ostype: l26
smbios1: uuid=77383f4d-4e0b-43b6-b91a-f6883d56b879
sockets: 1
virtio0: hd2sata:803/vm-803-disk-1.qcow2,format=qcow2,cache=unsafe,size=32G

Any idea? Is it a bug?
Thanks
 
Did you had a look at http://pve.proxmox.com/wiki/Nested_Virtualization ?
I did the same as you but without disabling hardware virtualization, as it didn’t really makes sense why you want a slow machine^^, and used 4.0beta as host and a nested 4.0beta (even a nested in a nested, worked also fine, was naturally only for testing purpose ^^).
Why did you disable hardware vt, and did you use nested vt like described in the wiki, pleas post the output from:
Code:
cat /sys/module/kvm_intel/parameters/nested
Sorry if I'm missing something obvious.
 
Hello, I just met with same problem and found a point of issue.

The warning, "TCG doesn't support requested feature: CPUID.01H:EDX.de [bit 2]", is occurred during booting qemu(not qemu-kvm) with cpu enforced option because CPUID 01H:EDX.de is not available on qemu(not qemu-kvm) virtualization.
(ref:
http://x86.renejeschke.de/html/file_module_x86_id_45.html)

Since a qemu-server's commit 6a33d44, the enforce option is enabled by default (whether kvm hardware virtualization is disabled).

So, I fixed current problem, but I couldn't understand how to contribute to.
Please see a github pull request: https://github.com/proxmox/qemu-server/pull/2

Thanks :)