Resend, because probably it didn't reach the ml due to attachments size... I'm posting now links instead... On Wed, Nov 23, 2011 at 12:01 PM, Nadav Har'El wrote: > Unfortunately, this is a known bug - which I promised to work on, but > haven't yet got around to :( > nested-vmx.txt explictly lists under "known limitations" that: "The > current code supports running Linux guests under KVM guests." [snip] > I don't think there is any such guidelines. The only thing you really > need is "-cpu qemu64,+vmx" (replace qemu64 by whatever you want) to > advertise the exisance of VMX. > Ok, thanks for the answer. right now tested this config Host F16 with these packages kernel-3.1.1-2.fc16.x86_64 virt-manager-0.9.0-7.fc16.noarch qemu-kvm-0.15.1-3.fc16.x86_64 libvirt-0.9.6-2.fc16.x86_64 L1 guest f16vm with same virtualization related packages as the host L2 guest c56 configured as red hat 5.4 or above and configured to boot from cd cd is a iso of centos 5.6 live x86_64 L1 guest configured with "copy host cpu configuration" in virt-manager its cpuinfo gives: [root@f16vm ~]# cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 Duo CPU T7700 @ 2.40GHz stepping : 11 cpu MHz : 2693.880 cache size : 4096 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 pse36 clflush mmx fxsr sse sse2 ss syscall nx rdtscp lm constant_tsc up nopl pni vmx ssse3 cx16 sse4_1 sse4_2 x2apic popcnt hypervisor lahf_lm bogomips : 5387.76 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: qemu command line on my host for f16vm is /usr/bin/qemu-kvm -S -M pc-0.14 -cpu core2duo,+lahf_lm,+rdtscp,+popcnt,+x2apic,+sse4.2,+sse4.1,+xtpr,+cx16,+tm2,+est,+vmx,+ds_cpl,+pbe,+tm,+ht,+ss,+acpi,+ds -enable-kvm -m 3192 -smp 1,sockets=1,cores=1,threads=1 -name f16vm .... On L1 f16vm qemu command line for its L2 guest c56 is: [root@f16vm ~]# ps -ef|grep qemu qemu 1834 1 10 12:49 ? 00:01:07 /usr/bin/qemu-kvm -S -M pc-0.14 -enable-kvm -m 1024 -smp 1,sockets=1,cores=1,threads=1 -name c56 -uuid 15526957-51c9-1958-8a15-dea8f2626e5d -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/c56.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -drive file=/var/lib/libvirt/images/CentOS-5.6-x86_64-LiveCD.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -usb -vnc 127.0.0.1:0 -vga cirrus -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 [root@f16vm ~]# virsh start c56 After a while c56 goes into a paused state: [root@f16vm ~]# virsh domstate c56 paused [root@f16vm ~]# virsh domstate c56 --reason paused (unknown) I got only up to these lines attached with virt-dmesg run from f16vm against c56: https://docs.google.com/open?id=0BwoPbcrMv8mvMWVmYTRkNDMtMjMzMi00OWViLWI1NTctYjA1YzU2NmM0ZmU5 I post also the image related to what I see in console of c56 L2 guest before it gets paused.... https://docs.google.com/open?id=0BwoPbcrMv8mvMWVjNGNmYTUtNTcxOC00MzBkLWI5YWYtZDhmNDkxMzM1OTEx Thanks, Gianluca -- 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
