From: Michael Tokarev <mjt@tls.msk.ru>
To: qemu-devel qemu-devel <qemu-devel@nongnu.org>,
John Snow <jsnow@redhat.com>
Subject: Re: qemu broke booting of old RedHat floppies
Date: Wed, 20 Jan 2021 19:02:51 +0300 [thread overview]
Message-ID: <3a25a973-af9c-0d87-ae30-f0758742c3c6@msgid.tls.msk.ru> (raw)
In-Reply-To: <098ce1c2-e304-bf37-c3f9-f8cd81028020@tls.msk.ru>
And one more followup to my own email.
As I didn't remember what's the std size of 144M floppy image
I weren't able to check, but the file size looked suspectably
for me at the very beginning. And indeed, std 144M floppy is
smaller than that. After truncating the file to 1440*1024 bytes
it works fine. The extra content seem not to belong to the image
itself and were added by something on the way to the archive
page. So this issue ended up as being a non-issue.
One thing still bothers me:
> $ qemu-system-x86_64 \
> -drive file=RedHatLinuxBootDisk521998.disk1of1.img,if=none,id=d,format=raw \
> -device floppy,drive=d,type=144
>
> But it fails:
>
> qemu-system-x86_64: -device floppy,drive=d,type=144: Insufficient permission to perform this operation
This same error message is returned after truncating the image
to 1440*1024 bytes. By current qemu 5.2. Why?
Thanks,
/mjt
next prev parent reply other threads:[~2021-01-20 16:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0bca1cd0-69c3-c07a-b4cf-015dcdbc6d61@tls.msk.ru>
2021-01-20 15:20 ` qemu broke booting of old RedHat floppies Michael Tokarev
[not found] ` <098ce1c2-e304-bf37-c3f9-f8cd81028020@tls.msk.ru>
2021-01-20 16:02 ` Michael Tokarev [this message]
2021-01-20 15:11 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é
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=3a25a973-af9c-0d87-ae30-f0758742c3c6@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=jsnow@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.