Alexander Graf wrote: [...] > Also after two days of permanent stress testing I also got the Intel > machine w/ current git down: > > + sudo -u contain1 env -i /usr/local/bin/qemu-system-x86_64 -localtime > -kernel virtio-kernel -initrd virtio-initrd -nographic -append 'quiet > clocksource=acpi_pm cifsuser=contain1 cifspass=contain1 > root=cifs://contain1:contain1@xxxxxxxxxx/contain1 > realroot=//172.16.1.1/users/contain1 > ip=172.16.1.2:172.16.1.1::255.255.255.0::eth0:none console=ttyS0 > dhcp=off builder=1' -net nic,model=virtio,macaddr=52:54:00:12:34:1 -net > tap,ifname=tap1,script=/bin/true -m 2000 -nographic -smp 8 /dev/null > qemu: loading initrd (0x1daf359 bytes) at 0x000000007b240000 > Stuck ?? > > No backtrace here though. That's all I got from the serial console. > + sudo -u contain1 env -i /usr/local/bin/qemu-system-x86_64 -localtime -kernel virtio-kernel -initrd virtio-initrd -nographic -append 'quiet clocksource=acpi_pm cifsuser=contain1 cifspass=contain1 root=cifs://contain1:contain1@xxxxxxxxxx/contain1 realroot=//172.16.1.1/users/contain1 ip=172.16.1.2:172.16.1.1::255.255.255.0::eth0:none console=ttyS0 dhcp=off builder=1' -net nic,model=virtio,macaddr=52:54:00:12:34:1 -net tap,ifname=tap1,script=/bin/true -m 2000 -nographic -smp 8 /dev/null qemu: loading initrd (0x1daf359 bytes) at 0x000000007b240000 Stuck ?? (qemu) info cpus * CPU #0: pc=0xffffffff80221f1d thread_id=15211 CPU #1: pc=0xffffffff80221f1d thread_id=15212 CPU #2: pc=0xffffffff80221f1d thread_id=15213 CPU #3: pc=0xffffffff80221f1d thread_id=15214 CPU #4: pc=0xffffffff8049f7d0 thread_id=15215 CPU #5: pc=0xffffffff80221f1d thread_id=15216 CPU #6: pc=0xffffffff80221f1d thread_id=15217 CPU #7: pc=0x000000000009f02c thread_id=15218 (qemu) cpu 7 (qemu) info registers EAX=00000c06 EBX=000005b8 ECX=00000000 EDX=00000000 ESI=00000000 EDI=00000000 EBP=00000000 ESP=00000000 EIP=0000002c EFL=00033002 [-------] CPL=3 II=0 A20=1 SMM=0 HLT=0 ES =0000 00000000 0000ffff 0000f300 CS =9f00 0009f000 0000ffff 0000f300 SS =0000 00000000 0000ffff 0000f300 DS =0000 00000000 0000ffff 0000f300 FS =0000 00000000 0000ffff 0000f300 GS =0000 00000000 0000ffff 0000f300 LDT=0000 00000000 0000ffff 00008200 TR =0000 fffbd000 00002088 00008b00 GDT= 00000000 0000ffff IDT= 00000000 0000ffff CR0=60000010 CR2=00000000 CR3=00000000 CR4=00000000 DR0=00000000 DR1=00000000 DR2=00000000 DR3=00000000 DR6=ffff0ff0 DR7=00000400 FCW=037f FSW=0000 [ST=0] FTW=00 MXCSR=00000000 FPR0=0000000000000000 0000 FPR1=0000000000000000 0000 FPR2=0000000000000000 0000 FPR3=0000000000000000 0000 FPR4=0000000000000000 0000 FPR5=0000000000000000 0000 FPR6=0000000000000000 0000 FPR7=0000000000000000 0000 XMM00=00000000000000000000000000000000 XMM01=00000000000000000000000000000000 XMM02=00000000000000000000000000000000 XMM03=00000000000000000000000000000000 XMM04=00000000000000000000000000000000 XMM05=00000000000000000000000000000000 XMM06=00000000000000000000000000000000 XMM07=00000000000000000000000000000000 Is that guest really seriously in BIOS code? After booting Linux? (qemu) x /2i $pc-1 0x000000000009f02b: hlt 0x000000000009f02c: jmp 0x9f02b Where is this? Looks like panic code to me. Alex -- 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
