qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] Fwd: Bug#740464: qemu-kvm: support for seabios option "scre


From: Michael Tokarev
Subject: [Qemu-devel] Fwd: Bug#740464: qemu-kvm: support for seabios option "screen-and-debug"
Date: Sun, 02 Mar 2014 09:58:22 +0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20131103 Icedove/17.0.10

I'm forwarding this to upstream, such enhancements, in my opinion,
should not be done inside a single distribution, and since I don't
use (and don't even know how to use) the mentioned features I can't
further comment on this, and don't really want to become a broken
phone.

Thank you for the good analisys (in initial email and in a folllowup
at http://bugs.debian.org/740464 ).

BTW, this is not qemu-kvm, this is qemu.  Qemu-kvm has been merged
into qemu since version 1.3.

Thanks,

/mjt

------- Original message --------
Subject: Bug#740464: qemu-kvm: support for seabios option "screen-and-debug"
Date: Sat, 01 Mar 2014 14:27:35 -0800
From: Matt Taggart <address@hidden>

Package: qemu-kvm
Version: 1.7.0+dfsg-3
Severity: wishlist

I am using seabios with sgabios in kvm (in order to get early BIOS messages
on serial), and during the bootloader stage I am seeing all characters
printed twice. I found this page

  http://www.coreboot.org/SeaBIOS#Adding_sgabios_support

which explains the problem and that you can fix it by disabling the
"screen-and-debug" config option. It also references this list of other
config options

  http://www.coreboot.org/SeaBIOS#Other_Configuration_items

Looking at the qemu-kvm source, I see that in hw/nvram/fw_cfg.c and
qemu-options.hx there is support for changing a few of these, things like
show-boot-menu, boot-menu-wait, splashfile.

Could you please add support for enabling the "screen-and-debug" option?

Also interesting from that list might be
  boot-menu-message
  boot-menu-key
  boot-fail-wait

i(the others are either obscure or I don't know what they are for, so I
don't know if they would be useful).

Thanks,

-- 
Matt Taggart
address@hidden





reply via email to

[Prev in Thread] Current Thread [Next in Thread]