pve2.x does not test for virtualisation support beeing actually enabled

proxman

New Member
Jul 1, 2012
10
0
1
Hi,

While setting up a cluster on older Dell hardware i forgot to enable virtualisation support in the bios (bios default) on 2 out of 3. CPU itself is of course VT capable.
So, i was quite frustrated to see that moving a kvm guest from node1 with VT enabled to node2 and 3 ended up in a vm crash in the last steps of the migration.

I found the cause by looking to the long error output of kvm complains, which gave me the VT hint and found "VT supported but dissabled by bios" in dmsg.

This is probably a stupid error, but you dont think at first that a VT capable processor has it dissabled by default.
May i suggest to implement a warning/check for enabled VT in the installation process and/or in the proxmox logfile?

Ubuntu has https://launchpad.net/cpu-checker/ which includes kvm-ok tool to ckeck exactly for this.

Regards,
Proxman
 
if you try to start a VM on a non-vt node you will get an error. you did a live migration?
 
Yes, i created VM on node1 and tryed live-migration to non-vt-enabled node2. Of course kvm guest would not start on node2 directly either, but i did not test that before.
Took me a moment to realize what was going on, since pve did not complain about missing VT (since it booted on the 64 bit hardware and my mind set 64bit == VT).
 

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!