On 07/11/2014 17:22, Alex Williamson wrote: > On Fri, 2014-11-07 at 10:47 -0500, Timothy McDaniel wrote: >> here is my /proc/cpuinfo >> >> processor : 0 >> vendor_id : CentaurHauls >> cpu family : 6 >> model : 15 >> model name : VIA Nano processor U2250 (1.6GHz Capable) >> stepping : 3 >> cpu MHz : 800.000 >> cache size : 1024 KB >> fpu : yes >> fpu_exception : yes >> cpuid level : 10 >> wp : yes >> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge >> mca cmov pat clflush acpi mmx fxsr sse sse2 ss tm pbe syscall nx lm >> constant_tsc up rep_good nopl pni monitor vmx est tm2 ssse3 cx16 xtpr >> rng rng_en ace ace_en ace2 phe phe_en lahf_lm >> bogomips : 3191.62 >> clflush size : 64 >> cache_alignment : 128 >> address sizes : 36 bits physical, 48 bits virtual >> power management: >> >> also here is my uname -mrs >> Linux 3.2.0-4-amd64 x86_64 >> >> here is uname -a >> Linux sd-24793 3.2.0-4-amd64 #1 SMP Debian 3.2.63-2+deb7u1 x86_64 GNU/Linux >> >> please tell me if you need anymore info on helping me get kvm to work. > > Last I was aware, Via's implementation of vmx was broken. I'd guess > that's still the case. Thanks, Yes, there are many reports of this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570244 http://www.mail-archive.com/kvm@xxxxxxxxxxxxxxx/msg11662.html https://bugs.launchpad.net/qemu/+bug/712416 Can you try running vmxcap (scripts/kvm/vmxcap in git://qemu.org/qemu.git)? Paolo -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html