From: "Daniel P. Berrange" <berrange@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Anthony Liguori <aliguori@linux.vnet.ibm.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [ANNOUNCE][Call-For-Testing] Release 0.12.0-rc1 of QEMU
Date: Thu, 10 Dec 2009 12:16:10 +0000 [thread overview]
Message-ID: <20091210121610.GO13534@redhat.com> (raw)
In-Reply-To: <4B20BDD0.5060901@redhat.com>
On Thu, Dec 10, 2009 at 10:22:24AM +0100, Gerd Hoffmann wrote:
> On 12/09/09 17:56, Daniel P. Berrange wrote:
> >There's a small bug in SCSI drive hotplug where QEMU is not assigning
> >unique block device names when you leave the name unspecified
> >
> >$ /home/berrange/usr/qemu-0.12/bin/qemu -vnc :1 -monitor stdio -device lsi
> >QEMU 0.11.91 monitor - type 'help' for more information
> >(qemu) drive_add 0:0:4 file=/home/berrange/mcdboot.img,if=scsi
> >OK bus 0, unit 0
> >(qemu) drive_add 0:0:4 file=/home/berrange/mcdboot.img,if=scsi
> >OK bus 0, unit 1
> >(qemu) drive_add 0:0:4 file=/home/berrange/mcdboot.img,if=scsi
> >OK bus 0, unit 2
> >(qemu) drive_add 0:0:4 file=/home/berrange/mcdboot.img,if=scsi
> >OK bus 0, unit 3
> >(qemu) info block
> >ide1-cd0: type=cdrom removable=1 locked=0 [not inserted]
> >floppy0: type=floppy removable=1 locked=0 [not inserted]
> >sd0: type=floppy removable=1 locked=0 [not inserted]
> >scsi0-hd0: type=hd removable=0 file=/home/berrange/mcdboot.img ro=1
> >drv=raw encrypted=0
> >scsi0-hd0: type=hd removable=0 file=/home/berrange/mcdboot.img ro=1
> >drv=raw encrypted=0
> >scsi0-hd0: type=hd removable=0 file=/home/berrange/mcdboot.img ro=1
> >drv=raw encrypted=0
> >scsi0-hd0: type=hd removable=0 file=/home/berrange/mcdboot.img ro=1
> >drv=raw encrypted=0
> >(qemu)
> >
> >Notice they are all 'scsi0-hd0', instead of scsi0-hd1, scsi0-hd2, etc
>
> Fix attached.
>
> Note that the whole auto-naming only works reliable if you limit
> yourself to a single scsi bus (in any qemu version out there). I
> strongly recommend to simply name the drives yourself using id=<name>.
> Works in 0.12 and IIRC in 0.11 too.
Yes we are going to start explicitly naming all the QEMU devices
that libvirt creates. I just want this fix for existing released
libvirt which doesn't name devices.
Regards,
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
next prev parent reply other threads:[~2009-12-10 12:16 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-06 22:43 [Qemu-devel] [ANNOUNCE][Call-For-Testing] Release 0.12.0-rc1 of QEMU Anthony Liguori
2009-12-07 12:49 ` Luiz Capitulino
2009-12-07 13:45 ` Anthony Liguori
2009-12-07 13:59 ` Luiz Capitulino
2009-12-07 14:30 ` [Qemu-devel] " Michael S. Tsirkin
2009-12-07 14:36 ` Anthony Liguori
2009-12-07 14:45 ` Michael S. Tsirkin
2009-12-07 14:56 ` Anthony Liguori
2009-12-07 18:34 ` [Qemu-devel] " Daniel P. Berrange
2009-12-07 19:43 ` Anthony Liguori
2009-12-07 20:25 ` Daniel P. Berrange
2009-12-08 10:40 ` Gerd Hoffmann
2009-12-08 10:52 ` Daniel P. Berrange
2009-12-08 12:52 ` Gerd Hoffmann
2009-12-08 13:07 ` Gerd Hoffmann
2009-12-09 10:21 ` Daniel P. Berrange
2009-12-07 20:18 ` [Qemu-devel] [PULL] pci compliance fixes Michael S. Tsirkin
2009-12-09 10:27 ` [Qemu-devel] [ANNOUNCE][Call-For-Testing] Release 0.12.0-rc1 of QEMU Ian Molton
2009-12-09 16:56 ` Daniel P. Berrange
2009-12-10 9:22 ` Gerd Hoffmann
2009-12-10 12:16 ` Daniel P. Berrange [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-12-14 14:06 Anthony Liguori
2009-12-14 16:08 ` Artyom Tarasenko
2009-12-14 16:20 ` Anthony Liguori
2009-12-14 16:56 ` Blue Swirl
2009-12-14 17:00 ` Avi Kivity
2009-12-14 17:28 ` Anthony Liguori
2009-12-16 3:19 ` Ryan Harper
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=20091210121610.GO13534@redhat.com \
--to=berrange@redhat.com \
--cc=aliguori@linux.vnet.ibm.com \
--cc=kraxel@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.