From: Daniel Berrange <1747056@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1747056] [NEW] FreeDOS / MS-Dos / Windows 3.11 cannot perform reboot with 'isapc' machine
Date: Fri, 02 Feb 2018 18:15:46 -0000 [thread overview]
Message-ID: <151759534688.10002.1939402860055070584.malonedeb@wampee.canonical.com> (raw)
Public bug reported:
I was installing MS-Dos 6.22 + Windows 3.11 in preparation for running
Microsoft Bob, and noticed that when they try to perform a reboot, they
just get stuck. The console cursor stays flashing on/off, but the DOS
prompt no longer responds to input.
It is fairly easy to reproduce, even FreeDOS is impacted - download the
FreeDOS bootable CDROM image, then
$ qemu-img create demo.img 100MB
$ qemu-system-x86_64 -machine isapc -cdrom ~/Downloads/FD12CD.iso -hda
demo.img -monitor stdio
Wait for the installer to startup, and then in the monitor console run
sendkey ctrl-alt-delete
It will fail to reboot
Testing shows this is a regression from QEMU 2.8.0 onwards, and git
bisect further narrowed it down to a SEABIOS update
commit 6e99f5741ff1b408ea76e6caf2bd4f76df4060e9 (HEAD, tag: pull-seabios-20161027-2, tag: pull-seabios-20161027-1, refs/bisect/bad)
Author: Gerd Hoffmann <kraxel@redhat.com>
Date: Thu Oct 27 16:42:28 2016 +0200
seabios: update to 1.10.0 release.
Note that this seems particular to the "isapc" machine type - with the
"pc" machine type, reboot still works
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1747056
Title:
FreeDOS / MS-Dos / Windows 3.11 cannot perform reboot with 'isapc'
machine
Status in QEMU:
New
Bug description:
I was installing MS-Dos 6.22 + Windows 3.11 in preparation for running
Microsoft Bob, and noticed that when they try to perform a reboot,
they just get stuck. The console cursor stays flashing on/off, but the
DOS prompt no longer responds to input.
It is fairly easy to reproduce, even FreeDOS is impacted - download
the FreeDOS bootable CDROM image, then
$ qemu-img create demo.img 100MB
$ qemu-system-x86_64 -machine isapc -cdrom ~/Downloads/FD12CD.iso
-hda demo.img -monitor stdio
Wait for the installer to startup, and then in the monitor console run
sendkey ctrl-alt-delete
It will fail to reboot
Testing shows this is a regression from QEMU 2.8.0 onwards, and git
bisect further narrowed it down to a SEABIOS update
commit 6e99f5741ff1b408ea76e6caf2bd4f76df4060e9 (HEAD, tag: pull-seabios-20161027-2, tag: pull-seabios-20161027-1, refs/bisect/bad)
Author: Gerd Hoffmann <kraxel@redhat.com>
Date: Thu Oct 27 16:42:28 2016 +0200
seabios: update to 1.10.0 release.
Note that this seems particular to the "isapc" machine type - with the
"pc" machine type, reboot still works
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1747056/+subscriptions
next reply other threads:[~2018-02-02 18:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-02 18:15 Daniel Berrange [this message]
2018-02-05 12:32 ` [Qemu-devel] [Bug 1747056] Re: FreeDOS / MS-Dos / Windows 3.11 cannot perform reboot with 'isapc' machine Daniel Berrange
2018-03-05 18:08 ` Daniel Berrange
2020-12-01 10:40 ` Thomas Huth
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=151759534688.10002.1939402860055070584.malonedeb@wampee.canonical.com \
--to=1747056@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).