Greetings. I'm using KVM with a number of VMs, and quite succesfully. Thanks for the great code :) I've just started using an appliance ( IBM's Netezza 7.2 emulator ), and this launches a KVM-based VM on startup. Everything appears to be working ( though not particularly quickly ), and I get a LOT of warnings on the main VM's console: handle_exit: unexpected exit_ini_info 0x8000003a exit_code 0x60 handle_exit: unexpected exit_ini_info 0x800000ef exit_code 0x60 handle_exit: unexpected exit_ini_info 0x800000fd exit_code 0x60 ... etc Around the same time, my KVM host logged this: [146758.885232] kvm [2572]: vcpu0 unhandled rdmsr: 0xc0010112 Is this something to worry about? I have a quad-core AMD: processor : 0 vendor_id : AuthenticAMD cpu family : 21 model : 16 model name : AMD A8-5600K APU with Radeon(tm) HD Graphics stepping : 1 microcode : 0x6001119 cpu MHz : 2400.000 cache size : 2048 KB physical id : 0 siblings : 4 core id : 0 cpu cores : 2 apicid : 16 initial apicid : 0 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 mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce tbm topoext perfctr_core perfctr_nb arat cpb hw_pstate npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold bmi1 bugs : fxsave_leak bogomips : 7186.51 TLB size : 1536 4K pages clflush size : 64 cache_alignment : 64 address sizes : 48 bits physical, 48 bits virtual power management: ts ttp tm 100mhzsteps hwpstate cpb eff_freq_ro ... and I've used virt-manager to set up the VM, clicking 'Copy host CPU configuration' in the 'Processor' tab. Thanks :) Dan -- 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
