On 09/03/13 01:05, Rod Smith wrote: > On 09/02/2013 05:32 PM, Laszlo Ersek wrote:
>> Maybe -enable-kvm would make a difference... > > It causes it to crash with a new set of error messages: > > KVM internal error. Suberror: 1 > emulation failure > EAX=c0000033 EBX=fffcc0e4 ECX=c0000080 EDX=00000000 > ESI=fffcc2c4 EDI=00005042 EBP=fffcc000 ESP=00000000 > EIP=ffffff26 EFL=00000082 [--S----] CPL=0 II=0 A20=1 SMM=0 HLT=0 > ES =0008 00000000 ffffffff 00c09300 DPL=0 DS [-WA] > CS =0010 00000000 ffffffff 00c09b00 DPL=0 CS32 [-RA] > SS =0008 00000000 ffffffff 00c09300 DPL=0 DS [-WA] > DS =0008 00000000 ffffffff 00c09300 DPL=0 DS [-WA] > FS =0008 00000000 ffffffff 00c09300 DPL=0 DS [-WA] > GS =0008 00000000 ffffffff 00c09300 DPL=0 DS [-WA] > LDT=0000 00000000 0000ffff 00008200 DPL=0 LDT > TR =0000 00000000 0000ffff 00008b00 DPL=0 TSS64-busy > GDT= 00000000ffffff80 0000001f > IDT= 0000000000000000 0000ffff > CR0=c0000033 CR2=0000000000000000 CR3=00000000ffffe000 CR4=00000660 > DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 > DR3=0000000000000000 > DR6=00000000ffff0ff0 DR7=0000000000000400 > EFER=0000000000000500 > Code=00 c0 0f 32 0f ba e8 08 0f 30 0f 20 c0 0f ba e8 1f 0f 22 c0 <ea> 2d > ff ff ff 18 00 e9 93 00 00 00 fa bb 00 f0 8e db bb 6c ff 2e 66 0f 01 17 > 66 b8 23 00 > Connected to RFB server, using protocol version 3.8 > > the kvm and kvm_amd modules are loaded on my system when this happens. > >>>>> - the output produced on qemu's debug console. >>> There's no output displayed. >> >> You need to add >> >> -debugcon file:/tmp/test.debug -global isa-debugcon.iobase=0x402 > > Here's what I get: > > http://www.rodsbooks.com/test.debug > > That's from a run when I added -m, -device, and -global options as per > your example. I compared it with my log, and the differences that I can find in your output (presence of another hard disk (hdb), legacy booting from floppy) don't explain the problem -- I added -hdb too and attempted to boot from Floppy as well, and it keeps working for me (SeaBIOS simply progresses to the bootable CD-ROM). > >> Maybe it doesn't even hang for you, could it be just crazy slow with >> TCG? > > I left it running for half an hour and got nothing. I'd say that's > excessive even for something that's not using KVM. With TCG: I tested qemu at v1.4.0, v1.5.0, v1.6.0, and 4ff78e0d. They all hang (spin) in (or after) the SeaBIOS function handle_pcibios(). This happens before the video initialization -- none of these qemu versions even reaches the TianoCore splash screen. With kvm_intel (3.10), on an Intel(R) Xeon(R) CPU W3550 @ 3.07GHz: qemu 4ff78e0d seems to work flawlessly for me. With kvm_amd (3.10), on an AMD Opteron(tm) Processor 6168: using qemu 4ff78e0d, I'm experiencing the exact same emulation failure & cpu state dump that you do. It happens very early, no debug output is produced by OVMF or the SeaBIOS CSM. The emulation failure persists if I switch to "OVMF-pure-efi.fd" and the stock cirrus vgabios. Looks like you can only test it with kvm_intel right now. Laszlo ------------------------------------------------------------------------------ Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk _______________________________________________ edk2-devel mailing list edk2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/edk2-devel
