[SOLVED] CT start works, VM doesn't start? Proxmox 4.0

fips

Renowned Member
May 5, 2014
175
7
83
Hey,

I setup a 4.0 testing environment on an old HP DL350G5 (my productive system running on 3.2 like a charm ;-)

Installing a LXC container was not a big issue, it worked as expected.
But after installing a KVM VM, it doesn't start.
It tells me it could not load the kernel module.

kvm module is loaded, modprobe kvm_intel is not supported.
VT is enabled and I can see the vmx CPU flag in /proc/cpuinfo.

Why I can start CT but now VM's?

Thanks
 
Last edited:
Hey,
Why I can start CT but now VM's?

That's because those are two completely different technologies. Containers processes run as processes on the host system while with KVM/QEMU a full system gets (para-) virtualized.
CT are limited to certain linux guest and VMs can run arbitrary guests.[1]

Short, LXC CTs do not need a Kernel module, while KVM VMs need one.

Did you enabled the Virtualization features in the BIOS? That could be needed even if the vmx flag shows up :)
 

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!