All of lore.kernel.org
 help / color / mirror / Atom feed
From: agraf <670769@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 670769] Re: CDROM size not updated when changing image files
Date: Wed, 10 Nov 2010 03:47:58 -0000	[thread overview]
Message-ID: <AF431656-D0CC-4173-8AE8-6C7D77733292@suse.de> (raw)
In-Reply-To: 20101110031724.12399.20669.malone@gandwana.canonical.com


On 10.11.2010, at 04:17, Alex Davis wrote:

> Please note that until this bug is fixed, one cannot successfully
> install a guest OS from a set of CD-ROMS where the first disk image is
> smaller than subsequent ones.
> 
> -- 
> CDROM size not updated when changing image files
> https://bugs.launchpad.net/bugs/670769
> You received this bug notification because you are a member of qemu-
> devel-ml, which is subscribed to QEMU.
> 
> Status in QEMU: New
> 
> Bug description:
> I'm using qemu 13.0 with a plain Linux kernel using the ata_piix driver as the guest, and an initrd that starts a shell. When changing the image in the monitor and reading from the CDROM in the guest, the size is not updated. I'm using LInux 2.6.32.24
> as the host and I've tested 2.6.32.24, 2.6.35, and 2.6.36 as guests.  Both host and guest are 64-bit. Here is the command used to start the guest using the initrd:
> 
> ./x86_64-softmmu/qemu-system-x86_64 -cdrom /spare2/cd1.img -kernel /sources/linux-2.6.32.24-test/arch/x86/boot/bzImage -initrd /spare2/initrd.img -append 'root=/dev/ram0 rw' -cpu core2duo
> 
> Additional info on this bug can be found here: http://marc.info/?l=kvm&m=128746013906820&w=2. Note: this is how I discovered 
> the bug, using 32-bit Slackware install CDs.
> 
> I'm attaching the initrd I used in my tests: I created two different-sized fake CDROM images by dd'ing from /dev/zero. In my tests,
> cd1.img is smaller that cd2.img. In the monitor I executed 'change ide1-cd0 /spare2/cd2.img' to load the new image. I checked 
> the size by cat'ing /sys/block/sr0/size in the guest after reading the CDROM. Reading the CDROM was done by typing
> 'dd if=/dev/sr0 of=/dev/null bs=512 count=3'

Just to clarify, the contents of the image do change, but the reported
size does not?

Alex

-- 
CDROM size not updated when changing image files
https://bugs.launchpad.net/bugs/670769
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

Status in QEMU: New

Bug description:
I'm using qemu 13.0 with a plain Linux kernel using the ata_piix driver as the guest, and an initrd that starts a shell. When changing the image in the monitor and reading from the CDROM in the guest, the size is not updated. I'm using LInux 2.6.32.24
as the host and I've tested 2.6.32.24, 2.6.35, and 2.6.36 as guests.  Both host and guest are 64-bit. Here is the command used to start the guest using the initrd:

./x86_64-softmmu/qemu-system-x86_64 -cdrom /spare2/cd1.img -kernel /sources/linux-2.6.32.24-test/arch/x86/boot/bzImage -initrd /spare2/initrd.img -append 'root=/dev/ram0 rw' -cpu core2duo

Additional info on this bug can be found here: http://marc.info/?l=kvm&m=128746013906820&w=2. Note: this is how I discovered 
the bug, using 32-bit Slackware install CDs.

I'm attaching the initrd I used in my tests: I created two different-sized fake CDROM images by dd'ing from /dev/zero. In my tests,
cd1.img is smaller that cd2.img. In the monitor I executed 'change ide1-cd0 /spare2/cd2.img' to load the new image. I checked 
the size by cat'ing /sys/block/sr0/size in the guest after reading the CDROM. Reading the CDROM was done by typing
'dd if=/dev/sr0 of=/dev/null bs=512 count=3'

  reply	other threads:[~2010-11-10  3:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-04  5:08 [Qemu-devel] [Bug 670769] [NEW] CDROM size not updated when changing image files Alex Davis
2010-11-04  5:08 ` [Qemu-devel] [Bug 670769] " Alex Davis
2010-11-10  3:17 ` Alex Davis
2010-11-10  3:47   ` agraf [this message]
2010-11-10 12:55     ` Alex Davis
2010-11-10 13:11       ` agraf
2011-01-03 14:58         ` Alex Davis
2016-08-31 18:42 ` John Snow
2020-11-12  8:57 ` Thomas Huth
2021-01-12  4:17 ` Launchpad Bug Tracker

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=AF431656-D0CC-4173-8AE8-6C7D77733292@suse.de \
    --to=670769@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 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.