From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: John Snow <jsnow@redhat.com>, avocado-devel <avocado-devel@redhat.com>
Cc: Michael Tokarev <mjt@tls.msk.ru>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: qemu broke booting of old RedHat floppies
Date: Wed, 3 Feb 2021 17:30:56 +0100 [thread overview]
Message-ID: <d71657c6-a819-b2df-3e4b-0a6d690fd0c2@redhat.com> (raw)
In-Reply-To: <0bca1cd0-69c3-c07a-b4cf-015dcdbc6d61@msgid.tls.msk.ru>
Cc'ing avocado-devel for test idea.
On 1/20/21 4:11 PM, Michael Tokarev wrote:
> As someone noticed on IRC, old (2.x) RedHat floppies does not boot
> in current qemu. When qemu is booted from floppy image at
> https://archive.org/details/RedHatLinuxBootDisk521998
> (download the "ISO image" link there, it really is an 1.44 floppy),
> seabios says Boot failed and that's it.
>
> I run git bisect with it, knowing that qemu 2.1 works fine, and
> it pointed out to this commit which is oldish qemu-2.5+:
>
> commit 4812fa27fa75bce89738a82a191755853dd88408
> Author: John Snow <jsnow@redhat.com>
> Date: Fri Jan 22 15:51:05 2016 -0500
>
> fdc: change auto fallback drive for ISA FDC to 288
>
> The 2.88 drive is more suitable as a default because
> it can still read 1.44 images correctly, but the reverse
> is not true.
>
> Since there exist virtio-win drivers that are shipped on
> 2.88 floppy images, this patch will allow VMs booted without
> a floppy disk inserted to later insert a 2.88MB floppy and
> have that work.
>
> This patch has been tested with msdos, freedos, fedora,
> windows 8 and windows 10 without issue: if problems do
> arise for certain guests being unable to cope with 2.88MB
> drives as the default, they are in the minority and can use
> type=144 as needed (or insert a proper boot medium and omit
> type=144/288 or use type=auto) to obtain different drive types.
>
> As icing, the default will remain auto/144 for any pre-2.6
> machine types, hopefully minimizing the impact of this change
> in legacy hw to basically zero.
>
> Reviewed-by: Eric Blake <eblake@redhat.com>
> Signed-off-by: John Snow <jsnow@redhat.com>
> Message-id: 1453495865-9649-13-git-send-email-jsnow@redhat.com
>
> Now, I don't even know where to put that "type=144/288/auto" thing,
> I tried this:
>
> -drive
> file=RedHatLinuxBootDisk521998.disk1of1.img,if=floppy,format=raw,type=144
>
> but it says that format=raw does not support "type=144" option.
>
> And it's even more: I don't remember which size should be an 1.44Mb
> floppy :))
> The file size of that image is 1492992 bytes which does not look like it
> is of
> standard size, but I can't find which size it should be.
>
> Thanks!
>
> /mjt
>
next prev parent reply other threads:[~2021-02-03 16:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 15:11 qemu broke booting of old RedHat floppies Michael Tokarev
2021-01-20 15:39 ` Alexander Bulekov
2021-01-20 15:41 ` Thomas Huth
2021-03-12 6:23 ` John Snow
2021-02-03 16:30 ` Philippe Mathieu-Daudé [this message]
[not found] <0bca1cd0-69c3-c07a-b4cf-015dcdbc6d61@tls.msk.ru>
2021-01-20 15:20 ` Michael Tokarev
[not found] ` <098ce1c2-e304-bf37-c3f9-f8cd81028020@tls.msk.ru>
2021-01-20 16:02 ` Michael Tokarev
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=d71657c6-a819-b2df-3e4b-0a6d690fd0c2@redhat.com \
--to=philmd@redhat.com \
--cc=avocado-devel@redhat.com \
--cc=jsnow@redhat.com \
--cc=mjt@tls.msk.ru \
--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).