From: - <1910586@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: Re: [Bug 1910586] Re: SD card size constraint conceptually wrong
Date: Fri, 14 May 2021 11:50:20 -0000 [thread overview]
Message-ID: <YJ5j/AyolpbGRnjE@eleven> (raw)
In-Reply-To: 162081768954.8198.16989470695778091097.malone@wampee.canonical.com
On Wed, May 12, 2021 at 11:08:09AM -0000, Thomas Huth wrote:
>
> If it is not fixed yet and you think that this bug report here is still
> valid, then you have two options:
Actually, you seem to have forgotten a third option: I simply don't care
enough, especially after the patronizing response to my original report,
to bother.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1910586
Title:
SD card size constraint conceptually wrong
Status in QEMU:
Incomplete
Bug description:
The patch discussed here:
https://www.mail-archive.com/qemu-devel@nongnu.org/msg720833.html
introduces an artificial size constraint for SD cards
that has no relation to reality.
I'm trying to use an _actual_ **physical** SD card,
and qemu tells me its size is "invalid".
Something here appears to be conceptually wrong.
--------------------------------------------------
# fdisk -l /dev/sdg
Disk /dev/sdg: 14.84 GiB, 15931539456 bytes, 31116288 sectors
Disk model: USB SD Reader
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x7a0c8bb0
Device Boot Start End Sectors Size Id Type
/dev/sdg1 2048 524287 522240 255M c W95 FAT32 (LBA)
/dev/sdg2 524288 31116287 30592000 14.6G 83 Linux
# qemu-system-aarch64 -M raspi3 -m 1G -kernel vmlinuz-5.4.79-v8 -dtb bcm2837-rpi-3-b-plus.dtb -append console=ttyAMA0\ root=/dev/mmcblk0p2\ rw -nographic -serial mon:stdio -drive file=/dev/sdg,format=raw
qemu-system-aarch64: Invalid SD card size: 14.8 GiB
SD card size has to be a power of 2, e.g. 16 GiB.
You can resize disk images with 'qemu-img resize <imagefile> <new-size>'
(note that this will lose data if you make the image smaller than it currently is).
--------------------------------------------------
The same invocation with a dump of the actual image
resized to match qemu's odd expectations works fine.
This is on QEMU 5.2.0, as evidenced by the following:
--------------------------------------------------
# qemu-system-aarch64 -version
QEMU emulator version 5.2.0
Copyright (c) 2003-2020 Fabrice Bellard and the QEMU Project developers
--------------------------------------------------
Is there a simple workaround that disables this rather
arbitrary constraint?
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1910586/+subscriptions
next prev parent reply other threads:[~2021-05-14 11:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 19:24 [Bug 1910586] [NEW] SD card size constraint conceptually wrong -
2021-01-07 22:13 ` Philippe Mathieu-Daudé
2021-01-07 22:13 ` Philippe Mathieu-Daudé
2021-01-08 18:31 ` [Bug 1910586] " -
2021-02-20 0:07 ` Philippe Mathieu-Daudé
2021-05-12 11:08 ` Thomas Huth
2021-05-14 11:50 ` - [this message]
2021-05-14 12:33 ` 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=YJ5j/AyolpbGRnjE@eleven \
--to=1910586@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).