qemu -M isapc displays blank screen

Bug #1024248 reported by Michael Tokarev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
QEMU
Fix Released
Undecided
Unassigned
qemu (Debian)
Fix Released
Unknown

Bug Description

$ qemu-system-x86_64 -M isapc

This displays blank SDL window. It has been this way since forever I guess, at least according to http://bugs.debian.org/605525 (a Debian bugreport about it). However, this:

$ qemu-system-x86_64 -M isapc -enable-kvm

works (at least in current 1.1), and it works fine in qemu-kvm. On the other hand, this:

$ qemu-kvm -M isapc -no-kvm

also shows blank window. Something is wrong with isapc & TCG, and has been for a long time...

Thanks,

/mjt

Changed in qemu:
status: New → Confirmed
Changed in qemu (Debian):
status: Unknown → Confirmed
Revision history for this message
Michael Tokarev (mjt+launchpad-tls) wrote :

$ qemu-system-x86_64 -M isapc -chardev file,path=/dev/fd/1,id=seabios -device isa-debugcon,iobase=0x402,chardev=seabios
Start bios (version 1.7.0-20120603_194846-gandalf)
Unable to unlock ram - bridge not found
Ram Size=0x00000000 (0x0000000000000000 high)
WARNING - Unable to allocate resource at addSpace:118!
WARNING - Unable to allocate resource at addSpace:118!
WARNING - Unable to allocate resource at addSpace:118!
No space for init relocation.

$ qemu-system-x86_64 -M isapc -enable-kvm -chardev file,path=/dev/fd/1,id=seabios -device isa-debugcon,iobase=0x402,chardev=seabios
Start bios (version 1.7.0-20120603_194846-gandalf)
Unable to unlock ram - bridge not found
Ram Size=0x08000000 (0x0000000000000000 high)
Relocating init from 0x000e4540 to 0x07fe1d80 (size 57684)
=== PCI bus & bridge init ===
Detected non-PCI system
No apic - only the main cpu is present.
MP table addr=0x000fdb00 MPC table addr=0x000fdb10 size=216
SMBIOS ptr=0x000fdae0 table=0x000fd9d0 size=263
Scan for VGA option rom
Running option rom at c000:0003
Turning on vga text mode console
SeaBIOS (version 1.7.0-20120603_194846-gandalf)

So without kvm, the RAM size is detected as being 0.

FWIW.

Revision history for this message
Michael Tokarev (mjt+launchpad-tls) wrote :

It looks like this issue is fixed in 1.6.0 version

Changed in qemu:
status: Confirmed → Fix Released
Changed in qemu (Debian):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.