This CPU does not support KVM virtual machines (no Intel VT / AMD-V support)

T

tauren

New Member
Feb 4, 2009
9
0
1
I've got Proxmox VE installed on a bare metal system. The main web
interface reports this:
CPU(s) 8 x Intel(R) Xeon(R) CPU E5405 @ 2.00GHz

But when I go to create a virtual machine, it says this:
Attention: This CPU does not support KVM virtual machines (no Intel VT
/ AMD-V support).

If it helps, I'm using a SuperMicro SuperServer 6015TW-TV. In the BIOS I enabled "Intel <R> Virtualization Technology". I've also tried both enabling and disabling "Intel VT for Directed I/O <VT-d>". Each time I saved the BIOS settings and powered off the system. I've also tried reinstalling Proxmox with the settings changed. No matter what I do, I always get that message and cannot create a KVM virtual machine.

I couldn't find a bios version in the bios screens, but it said my BIOS is dated 12/2007. The Supermicro site shows a new BIOS dated 11/2008. However, it warns to not install a new BIOS unless you know for sure that the BIOS is the problem. The current BIOS shows options for enabling VT, so I would think it would work.

I believe my dual quad core Xeon 5405 CPUs support Intel VT. How do I get Proxmox to recognize this? Is there anything else I can try before installing a new bios?

Thanks,
Tauren
 
Have you unplugged the power cable at the back for a time after making the changes?

Cheers
--Guy
 
Guy said:
Have you unplugged the power cable at the back for a time after making the changes?

Cheers
--Guy
Click to expand...

Yes, each time I've unplugged the system for 5 to 10 seconds. I just shut it down again and unplugged it for 30 seconds to make sure. But after booting, I still get that message. And right now both BIOS settings related to VT support are enabled.

Tauren
 
tauren said:
Yes, each time I've unplugged the system for 5 to 10 seconds. I just shut it down again and unplugged it for 30 seconds to make sure. But after booting, I still get that message. And right now both BIOS settings related to VT support are enabled.

Tauren
Click to expand...

why don´t you update your bios?
 
I still can't get KVM working. The supermicro site says to not update the bios unless there is a specific reason to do so, so I asked Supermicro tech support about this. Below is the message I got back from them. Any idea what "check your OS installation and patch update file" mean? I see no reference to that in the link they provide.

Hi,

The BIOS does support hyper-V is does not require to update the
BIOS version. You might need to check your OS installation and patch
update file. See the link below.

http://www.zimbra.com/forums/installation/17683-running-zimbra-proxmox-v
irtualization-environment-based-openvz.html

Thank you
DL

-----Original Message-----
Sent: Thursday, February 05, 2009 11:50 PM
To: Technical Support
Subject: Flash BIOS on SYS-6015TW-TV

I have just purchased a SYS-6015TW-TV and loaded each of the twin
servers with dual quad-core Intel Xeon 5405 cpus (CPU(s) 8 x Intel(R)
Xeon(R) CPU E5405 @ 2.00GHz) and 32GB of kingston ECC reg ram.
Everything seems to be working great on the system. Except for that I
can't get Intel VT support working.

I'm using a product called Proxmox to do virtualization with both KVM
and OpenVZ. Because Proxmox doesn't detect VT support, it is not
allowing any use of KVM. I don't know if the problem is with Proxmox
or with the server. How can I figure that out to be sure?

My CPUs have VT support and I've enabled "Intel <R> Virtualization
Technology" in the BIOS. I've also tried both enabling and disabling
"Intel VT for Directed I/O <VT-d>". Each time I saved the BIOS
settings and powered off the system, unplugging power. I've also tried
reinstalling Proxmox with the settings changed. No matter what I do, I
always get the error message that there is no VT support and it cannot
create a KVM virtual machine.

The Proxmox tech support is suggesting I update the BIOS to the latest
version. However, I don't know how to do this. The bios downloads
want to create a floppy disk, but the 6015TW has no floppy disk or
cdrom drive. I have an external usb cd-rom drive I could use. And I
have a usb flash drive available. But how do update the bios with
these?

And, how do I know that the problem is related to the bios? Have
there been VT problems on this system?

Thanks!
Tauren
 
Supermicro obviously just googled and copypasted the first thing they found.

Your problem is you don't have Intel Hyper-V detected as enabled, their response is to show you a forum post that has nothing to do with your problem...
 
Just update your BIOS and see if it helps, Supermicro and other server/mobo manufacturer first-level tech support is not always competent. Mostly they just want to get rid of you.
 
OK, I'll try that. Any advice on how to update the bios without a floppy? The system has no floppy or cdrom, but I have an external USB cdrom drive. And I have a usb flash drive. Which one would be easier to use?

Thanks,
Tauren
 
You could just pull the cover off and hook up a floppy drive real quick, I do that sometimes. Or put the BIOS updater on a DOS bootable CD that you craft. Nero actually makes an ok DOS boot disk that automatically loads a CDROM driver and mounts your CD's contents as a drive letter.
 
bourne:~# cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Xeon(R) CPU E5405 @ 2.00GHz
stepping : 10
cpu MHz : 2000.076
cache size : 6144 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 4
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni tm2 ssse3 lahf_lm
bogomips : 4003.47
clflush size : 64
cache_alignment : 64
address sizes : 38 bits physical, 48 bits virtual
power management:

processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Xeon(R) CPU E5405 @ 2.00GHz
stepping : 10
cpu MHz : 2000.076
cache size : 6144 KB
physical id : 1
siblings : 4
core id : 0
cpu cores : 4
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni tm2 ssse3 lahf_lm
bogomips : 4000.24
clflush size : 64
cache_alignment : 64
address sizes : 38 bits physical, 48 bits virtual
power management:

processor : 2
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Xeon(R) CPU E5405 @ 2.00GHz
stepping : 10
cpu MHz : 2000.076
cache size : 6144 KB
physical id : 0
siblings : 4
core id : 1
cpu cores : 4
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni tm2 ssse3 lahf_lm
bogomips : 4000.24
clflush size : 64
cache_alignment : 64
address sizes : 38 bits physical, 48 bits virtual
power management:

processor : 3
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Xeon(R) CPU E5405 @ 2.00GHz
stepping : 10
cpu MHz : 2000.076
cache size : 6144 KB
physical id : 1
siblings : 4
core id : 1
cpu cores : 4
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni tm2 ssse3 lahf_lm
bogomips : 4000.21
clflush size : 64
cache_alignment : 64
address sizes : 38 bits physical, 48 bits virtual
power management:

processor : 4
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Xeon(R) CPU E5405 @ 2.00GHz
stepping : 10
cpu MHz : 2000.076
cache size : 6144 KB
physical id : 0
siblings : 4
core id : 2
cpu cores : 4
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni tm2 ssse3 lahf_lm
bogomips : 4000.19
clflush size : 64
cache_alignment : 64
address sizes : 38 bits physical, 48 bits virtual
power management:

processor : 5
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Xeon(R) CPU E5405 @ 2.00GHz
stepping : 10
cpu MHz : 2000.076
cache size : 6144 KB
physical id : 1
siblings : 4
core id : 2
cpu cores : 4
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni tm2 ssse3 lahf_lm
bogomips : 4000.20
clflush size : 64
cache_alignment : 64
address sizes : 38 bits physical, 48 bits virtual
power management:

processor : 6
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Xeon(R) CPU E5405 @ 2.00GHz
stepping : 10
cpu MHz : 2000.076
cache size : 6144 KB
physical id : 0
siblings : 4
core id : 3
cpu cores : 4
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni tm2 ssse3 lahf_lm
bogomips : 4000.19
clflush size : 64
cache_alignment : 64
address sizes : 38 bits physical, 48 bits virtual
power management:

processor : 7
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Xeon(R) CPU E5405 @ 2.00GHz
stepping : 10
cpu MHz : 2000.076
cache size : 6144 KB
physical id : 1
siblings : 4
core id : 3
cpu cores : 4
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni tm2 ssse3 lahf_lm
bogomips : 4000.19
clflush size : 64
cache_alignment : 64
address sizes : 38 bits physical, 48 bits virtual
power management:
 
Your cpuflags lacks "vmx" which means as far as Linux can tell, "Intel Hyper-V" is disabled. Best guess is your BIOS isn't setting it.
 
tog said:
You could just pull the cover off and hook up a floppy drive real quick, I do that sometimes. Or put the BIOS updater on a DOS bootable CD that you craft. Nero actually makes an ok DOS boot disk that automatically loads a CDROM driver and mounts your CD's contents as a drive letter.
Click to expand...

Yeah, that's what I'd normally do too. But the mobo doesn't have a floppy drive connector. I'll look into creating a DOS bootable CD.
 
tauren said:
Yeah, that's what I'd normally do too. But the mobo doesn't have a floppy drive connector. I'll look into creating a DOS bootable CD.
Click to expand...

or go for a USB floppy drive.
 
The same issue with Asus P5KPL/1600 and Core 2 Quad

Hi folks,

I have the same problem with devices above: Asus P5KPL/1600 (http://es.asus.com/products.aspx?l1=3&l2=11&l3=563&l4=0&model=2323&modelmenu=1) and a Core 2 Quad processor.
I have checked the BIOS settings but nothing related to HyperThreading.

Do you think I still have a chance to work with PVE in my server? (using KVM of course).

All help would be appreciate.

Regards!

Raúl
 
You're not looking for hyperthreading, you're looking for "Hyper-V" or "Virtualization Extensions" or something similar.

cat /proc/cpuinfo | grep vmx

If you don't have vmx listed in your cpuflags you don't have Hyper-V enabled. Same problem the OP is having, his CPU should support Hyper-V, but it seems to not be enabled properly by his BIOS.
 
tog said:
cat /proc/cpuinfo | grep vmx

If you don't have vmx listed in your cpuflags you don't have Hyper-V enabled. Same problem the OP is having, his CPU should support Hyper-V, but it seems to not be enabled properly by his BIOS.
Click to expand...
Yeah, the same problem... I've checked this before and no vmx flag.

I will look for BIOS updates or I'll contact with ASUS support directly.

Thanks a lot and I'll keep you informed ;)

Ciao
 
raulmarinperez said:
Dear all,

After update my BIOS, no way to enable the VT to get KVM working on Proxmox VE.

So, after some minutes googling I've discovered is not possible to use it with my Q8200 processor because is not supporting the VT feature.

Some useful links:

http://ark.intel.com/cpu.aspx?groupId=29765
http://ark.intel.com/cpu.aspx?groupId=36547

Today it's a sad day :(

Ciao ciao
Click to expand...

see also these links where you can easily find a suitable CPU:

Compare Intel Desktop:
http://compare.intel.com/pcc/default.aspx?familyID=1&culture=en-US

Compare Intel Xeon:
http://compare.intel.com/PCC/default.aspx?familyID=5&culture=en-US

For AMD:
http://www.amdcompare.com/
 
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back