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.
Not that big a deal, just drop in a new processor.
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.
i have an "Intel(R) Xeon(R) CPU L5410 @ 2.33GHz" processor on Supermicro X7DBR-E MB.
the processor is said to support VT .
http://ark.intel.com/Product.aspx?id=33090&processor=L5410&spec-codes=SLBBS
But i got the same error "Attention: This CPU does not support KVM virtual machines (no Intel VT / AMD-V support)."
And thers not even an option to enable or disable Virtualisation in BIOS.
any help??
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.
Hello i am working with proxmox and having the same problem reported but my server shows that indeed has vmx, what else can be the problem?
as vmware workstation already "consumes" VT, its not available for guests.
VMWare workstation doesn't require either AMD-V or Intel-VT support to work, although I think newer versions of them can take advantage of it if it exists.Hello,
I have ASUS P7P55D PRO P55 S/L DDR3 SLI LGA1156 and İNTEL i5-750 Quad-Core 2,66 8MB BOX LGA1156 desktop pc with xp 32bit installed. And I have Vmware Workstation installed on xp. I installed proxmox into Vmware workstation with Virtualization Engine set to Intel VT-x enabled. But I am also getting This CPU does not support KVM virtual machines (no Intel VT / AMD-V support).
I updated bios and search for Intel VT support and both CPU and Mother board supports it.
What do you think I can not use KVM with proxmox? Could it be possible because of Vmware?
Thanks
VMWare workstation doesn't require either AMD-V or Intel-VT support to work, although I think newer versions of them can take advantage of it if it exists.
If you are installing Proxmox, before that you go into and take a good look at all of your BIOS settings, because even though your hardware might "support" Intel-VT, it may not have it enabled by default, and you will have to change that setting, and save the changes.
Also, since you can't run Windows XP with or without VMWare on on the same system that you are installing Proxmox on, you won't have to worry about them conflicting; installing Proxmox will wipe the hard drive -- better grab a spare hard drive you can stand to have erased if you wish to test if your hardware configuration will support it, and then try it with a safety belt on -- you can always shut down, change back to your old hard drive and get back into Windows XP with all of your programs intact, if you need to.
proxmox-1:~# cat /proc/cpuinfo | grep vmx
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 aperfmperf pni dtes64 monitor ds_cpl vmx tm2 ssse3 cx16 xtpr pdcm dca sse4_1 xsave lahf_lm tpr_shadow vnmi flexpriority
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 aperfmperf pni dtes64 monitor ds_cpl vmx tm2 ssse3 cx16 xtpr pdcm dca sse4_1 xsave lahf_lm tpr_shadow vnmi flexpriority
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 aperfmperf pni dtes64 monitor ds_cpl vmx tm2 ssse3 cx16 xtpr pdcm dca sse4_1 xsave lahf_lm tpr_shadow vnmi flexpriority
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 aperfmperf pni dtes64 monitor ds_cpl vmx tm2 ssse3 cx16 xtpr pdcm dca sse4_1 xsave lahf_lm tpr_shadow vnmi flexpriority
proxmox-1:~#