On Fri, Nov 11, 2011 at 12:34 AM, Gianluca Cecchi wrote: > On Thu, Nov 10, 2011 at 6:38 PM, Richard W.M. Jones wrote: >> On Wed, Nov 09, 2011 at 04:00:47PM +0100, Gianluca Cecchi wrote: >>> I set up f16vm with serial console to see if something appears.. but >>> nothing appears when f16vm freezes >> >> Try using virt-dmesg from the host to see if the F16 guest >> gives any kernel errors before it freezes. >> > > Trying to reproduce, where the vm is already defined (because > installation failed but definition remained) now I get the L2 vm that > goes into paused mode and not able to have it exit from this state. > > L1 f6 is f16vm > L2 f16 is f16vmvm > > Tried with these L2 vms: > - winxp configured to start from cd iso > - f16vmvm configured to start form cd iso where I have CentOS 5.6 live > > For example starting the f16vmvm (so the L2 one) I see it after a few > seconds in paused state in virt-manager of f16vm (L1 one). > > [root@f16vm ~]# virsh list > Id Name State > ---------------------------------- > 1 f16vmvm paused > > [root@f16vm ~]# virsh domstate f16vmvm --reason > paused (unknown)
Update on paused state of L2 guest: inside L1 guest (f16vm) I create L2 guest named "c56" as red hat linux 5.4 or later and use iso of CentOS 56 live for installing I get the pause state and the file /var/log/libvirt/qemu/c56.log contains 2011-11-11 18:04:27.903: starting up LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none /usr/bin/qemu-kvm -S -M pc-0.14 -enable-kvm -m 1024 -smp 1,sockets=1,cores=1,threads=1 -name c56 -uuid 69857dbc-43b6-1f67-2576-16b9a0079a54 -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 -no-reboot -drive file=/storage1/c56L2.img,if=none,id=drive-virtio-disk0,format=raw -device virtio-blk-pci,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=2 -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 -netdev tap,fd=24,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:4e:fd:00,bus=pci.0,addr=0x3 -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=0x6 char device redirected to /dev/pts/1 KVM: entry failed, hardware error 0x80000021 If you're runnning a guest on an Intel machine without unrestricted mode support, the failure can be most likely due to the guest entering an invalid state for Intel VT. For example, the guest maybe running in big real mode which is not supported on less recent Intel processors. RAX=0000000000000000 RBX=ffffffff8006bdb5 RCX=0000000000000000 RDX=0000000000000000 RSI=0000000000000001 RDI=ffffffff80312738 RBP=0000000000023000 RSP=ffffffff80457f90 R8 =ffffffff80456000 R9 =000000000000003f R10=ffff81003fa20008 R11=0000000000000246 R12=0000000000000000 R13=0000000000000000 R14=0000000000000000 R15=0000000000000000 RIP=ffffffff8006bdde RFL=00000002 [-------] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES =0018 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA] CS =0010 0000000000000000 ffffffff 00a09b00 DPL=0 CS64 [-RA] SS =0018 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA] DS =0018 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA] FS =0000 0000000000000000 000fffff 00000000 GS =0000 ffffffff80425000 000fffff 00000000 LDT=0000 0000000000000000 000fffff 00000000 TR =0040 ffff810001733000 0000206f 00008b00 DPL=0 TSS64-busy GDT= ffffffff80458000 00000080 IDT= ffffffff804ac000 00000fff CR0=8005003b CR2=0000000001dda720 CR3=000000003fbdb000 CR4=000006e0 DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 DR6=00000000ffff0ff0 DR7=0000000000000400 EFER=0000000000000d01 Code=48 8b 04 25 10 00 00 00 8b 80 38 e0 ff ff a8 08 75 04 fb f4 <eb> 01 fb 65 48 8b 04 25 10 00 00 00 8b 80 38 e0 ff ff a8 08 74 d4 65 48 8b 04 25 10 00 00 BTW: my cpu infos 1) On physical host processor : 3 vendor_id : GenuineIntel cpu family : 6 model : 42 model name : Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz stepping : 7 cpu MHz : 800.000 cache size : 4096 KB physical id : 0 siblings : 4 core id : 1 cpu cores : 2 apicid : 3 initial apicid : 3 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 rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 x2apic popcnt xsave avx lahf_lm ida arat epb xsaveopt pln pts dts tpr_shadow vnmi flexpriority ept vpid bogomips : 5387.07 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual 2) The L1 guest f16vm is configued with cpu configuration as "core2duo" [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 x2apic hypervisor lahf_lm bogomips : 5387.76 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: _______________________________________________ virt mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/virt
