I code, therefore I am
--- On Tue, 10/19/10, Alex Davis <alex14641@xxxxxxxxx> wrote:
> From: Alex Davis <alex14641@xxxxxxxxx>
> Subject: Re: CD-ROM size not updated when switching CD-ROM images.
> To: "Stefan Hajnoczi" <stefanha@xxxxxxxxx>
> Cc: kvm@xxxxxxxxxxxxxxx
> Date: Tuesday, October 19, 2010, 8:03 PM
> I code, therefore I am
>
>
> --- On Tue, 10/19/10, Stefan Hajnoczi <stefanha@xxxxxxxxx>
> wrote:
>
> > From: Stefan Hajnoczi <stefanha@xxxxxxxxx>
> > Subject: Re: CD-ROM size not updated when switching
> CD-ROM images.
> > To: "Alex Davis" <alex14641@xxxxxxxxx>
> > Cc: kvm@xxxxxxxxxxxxxxx
> > Date: Tuesday, October 19, 2010, 4:31 AM
> > On Tue, Oct 19, 2010 at 4:43 AM, Alex
> > Davis <alex14641@xxxxxxxxx>
> > wrote:
> > > Steps to reproduce:
> > > ) Download the first two Slackware-13.1 32-bit
> CD-ROM
> > ISO images.
> > > ) Start KVM with the following command
> > > qemu-system-x86_64 -m 1024M \
> > > -cdrom < full path of 1st install disk
> >
> > \
> >
> > After changing the CD-ROM, does running "blockdev
> > --rereadpt /dev/sr0"
> > update the size as expected?
> The install CD does not have the blockdev command.
>
> > You ejected the CD-ROM on the QEMU side, the guest
> doesn't
> > necessarily
> > know about the medium change. What happens when you
> > use "eject
> > /dev/sr0" inside the guest instead?
> I get a 'no medium found' error from the 'dd..' command.
> After
> going into the the monitor, ejecting and reloading the
> disk,
> I still get the size of the first disk in the guest.
> >
> > I don't know how CD-ROM media change works on real
> > hardware, but that
> > is the behavior that QEMU should be following.
> >
> > Stefan
>
>
I attempted some debugging by putting a printf in the cdrom_change_cb
method in hw/ide/core.c to output nr_sectors after the CD-ROM has been
changed: the value is correct. So the problem seems to be that the
new value isn't being propagated to the guest.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
