Proxmox nested on vmware, cannot start vm

winproof

Well-Known Member
Oct 18, 2017
33
10
48
48
france
hello

i have a problem that i cannot resolv.

i have a win 7 host, with vmware workstation 14, and proxmox inside.

using for test cluster (3 proxmox), all is fine.

but i want create a simple vm (debian 9) for HA test.

i have VT-x/EPT ticked in vmware, and nested options activated on proxmox.

i can create vm (with cpu set to "host") but cannot start, error :

kvm: error: failed to set MSR 0x38d to 0x0
kvm: /home/builder/source/qemu.tmp/target/i386/kvm.c:1833: kvm_put_msrs: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.

with cpu set to "kvm64", vm start, but "stop" on BIOS, or very very very slow, after 10mn there is still cpu activity but nothing more.

a little help please :)

(sorry for my english, i'm french)

some informations:

root@p1:~# cat /sys/module/kvm_intel/parameters/nested
Y

root@p1:~# lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Thread(s) per core: 1
Core(s) per socket: 4
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 42
Model name: Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz
Stepping: 7
CPU MHz: 3300.040
BogoMIPS: 6600.08
Virtualization: VT-x
Hypervisor vendor: VMware
Virtualization type: full
L1d cache: 32K
L1i cache: 32K
L2 cache: 256K
L3 cache: 6144K
NUMA node0 CPU(s): 0-3
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx rdtscp lm constant_tsc arch_perfmon nopl xtopology tsc_reliable nonstop_tsc cpuid pni pclmulqdq vmx ss se3 cx16 pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx hyper visor lahf_lm tpr_shadow vnmi ept vpid tsc_adjust arat


root@p1:~# pveversion -v
proxmox-ve: 5.0-25 (running kernel: 4.13.4-1-pve)
pve-manager: 5.0-34 (running version: 5.0-34/b325d69e)
pve-kernel-4.13.4-1-pve: 4.13.4-25
pve-kernel-4.10.17-2-pve: 4.10.17-20
libpve-http-server-perl: 2.0-6
lvm2: 2.02.168-pve6
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-15
qemu-server: 5.0-17
pve-firmware: 2.0-3
libpve-common-perl: 5.0-20
libpve-guest-common-perl: 2.0-13
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-16
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.0-10
pve-qemu-kvm: 2.9.1-2
pve-container: 2.0-17
pve-firewall: 3.0-3
pve-ha-manager: 2.0-3
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.1.0-2
lxcfs: 2.0.7-pve4
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.7.2-pve1~bpo90

root@p1:~# cat /etc/pve/qemu-server/100.conf
bootdisk: scsi0
cores: 4
ide2: local:iso/debian-9.1.0-amd64-netinst.iso,media=cdrom
memory: 2048
name: ping
net0: virtio=06:F0:DE:2C:8A:7B,bridge=vmbr0,link_down=1
numa: 0
ostype: l26
scsi0: local:100/vm-100-disk-1.qcow2,size=10G
scsihw: virtio-scsi-pci
smbios1: uuid=b7fdde48-efdf-44b0-bdaa-98a14e194443
sockets: 1
 
I have this same problem. I'm trying to learn Proxmox and compare that to ESXi, but I'm not able to get a VM to start in Proxmox using kvm. There are no errors indicating that the hardware is missing, but VM's never progress past the BIOS screen. When I change the virtualization to software the VM's run, but they're very slow.

What's confusing is that there are no errors. I'm passing the hardware virtualization to Proxmox, and according to Proxmox it see's the hardware virtualization, but no VM's will run using the kvm engine.

This is my first try using Proxmox, I'm trying to learn it and see what it can do.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!