From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 321068] Re: Early BIOS error message cannot be seen after reboot in VNC/SDL
Date: Wed, 02 Jun 2010 19:24:19 -0000 [thread overview]
Message-ID: <20100602192420.14606.70683.launchpad@wampee.canonical.com> (raw)
In-Reply-To: 20090125085118.20846.811.malonedeb@palladium.canonical.com
** Changed in: qemu
Status: New => Fix Released
--
Early BIOS error message cannot be seen after reboot in VNC/SDL
https://bugs.launchpad.net/bugs/321068
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Status in QEMU: Fix Released
Bug description:
Running kvm-83-637-gdfacd26, on F10: I installed an OS (W2K3/32bit), at the end of installation changed the CD to an ISO containing some drivers, then rebooted the VM. Since it was loaded with -boot d, it tried to boot from the CD - which was not bootable. However, the error message could not be read from the display, which was all garbled and messy. In the past it used to clear and one could have read the error.
parent reply other threads:[~2010-06-02 19:30 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20090125085118.20846.811.malonedeb@palladium.canonical.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100602192420.14606.70683.launchpad@wampee.canonical.com \
--to=anthony@codemonkey.ws \
--cc=321068@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).