From: Peter Krempa <pkrempa@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-block@nongnu.org, armbru@redhat.com, pbonzini@redhat.com,
berrange@redhat.com, eblake@redhat.com, libvir-list@redhat.com,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/3] scsi-disk: Add device_id property
Date: Mon, 28 Jan 2019 09:50:41 +0100 [thread overview]
Message-ID: <20190128085041.GA16630@andariel.pipo.sk> (raw)
In-Reply-To: <20190125174653.4604-3-kwolf@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1931 bytes --]
On Fri, Jan 25, 2019 at 18:46:52 +0100, Kevin Wolf wrote:
> The new device_id property specifies which value to use for the vendor
> specific designator in the Device Identification VPD page.
>
> In particular, this is necessary for libvirt to maintain guest ABI
> compatibility when no serial number is given and a VM is switched from
> -drive (where the BlockBackend name is used) to -blockdev (where the
> vendor specific designator is left out by default).
>
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> ---
> hw/scsi/scsi-disk.c | 24 ++++++++++++++++--------
> 1 file changed, 16 insertions(+), 8 deletions(-)
[...]
> @@ -2904,7 +2910,9 @@ static const TypeInfo scsi_disk_base_info = {
> DEFINE_PROP_STRING("ver", SCSIDiskState, version), \
> DEFINE_PROP_STRING("serial", SCSIDiskState, serial), \
> DEFINE_PROP_STRING("vendor", SCSIDiskState, vendor), \
> - DEFINE_PROP_STRING("product", SCSIDiskState, product)
> + DEFINE_PROP_STRING("product", SCSIDiskState, product), \
> + DEFINE_PROP_STRING("device_id", SCSIDiskState, device_id)
This adds the property only to 'scsi-disk', whereas libvirt will use
'scsi-cd' or 'scsi-hd' depending on the media type if the 'scsi-cd'
device is detected. The following logic decides:
https://libvirt.org/git/?p=libvirt.git;a=blob;f=src/qemu/qemu_command.c;h=3e46f3ced3c1e6a4865e98e2d0cdce3214c4a5d2;hb=HEAD#l1978
This brings multiple questions:
1) Is this necssary also for scsi-cd/scsi-hd and if yes, the property
does not seem to be present for those
2) Is actually using 'scsi-cd'/'scsi-hd' the better option than
'scsi-disk'?
3) Since upstream libvirt supports qemu-1.5 and newer and 'scsi-cd' is
already supported there, can we assume that all newer versions support
it? (Basically the question is whether it can be compiled out by
upstream means).
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-01-28 8:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 17:46 [Qemu-devel] [PATCH 0/3] scsi-disk: Device Identification fixes Kevin Wolf
2019-01-25 17:46 ` [Qemu-devel] [PATCH 1/3] scsi-disk: Don't use empty string as device id Kevin Wolf
2019-01-29 12:30 ` Philippe Mathieu-Daudé
2019-01-29 16:37 ` Markus Armbruster
2019-01-30 11:39 ` Kevin Wolf
2019-01-25 17:46 ` [Qemu-devel] [PATCH 2/3] scsi-disk: Add device_id property Kevin Wolf
2019-01-28 8:50 ` Peter Krempa [this message]
2019-01-28 9:08 ` Peter Krempa
2019-01-28 14:41 ` Kevin Wolf
2019-01-28 16:55 ` Markus Armbruster
2019-01-28 17:49 ` Kevin Wolf
2019-01-29 7:10 ` Markus Armbruster
2019-01-29 12:25 ` [Qemu-devel] [libvirt] " Peter Krempa
2019-01-29 9:40 ` [Qemu-devel] " Peter Krempa
2019-01-25 17:46 ` [Qemu-devel] [PATCH 3/3] scsi-disk: Deprecate device_id fallback to BlockBackend name Kevin Wolf
2019-01-29 15:58 ` Daniel P. Berrangé
2019-02-04 9:56 ` Kevin Wolf
2019-02-04 10:06 ` Daniel P. Berrangé
2019-01-25 20:52 ` [Qemu-devel] [PATCH 0/3] scsi-disk: Device Identification fixes Eric Blake
2019-02-01 12:51 ` Kevin Wolf
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=20190128085041.GA16630@andariel.pipo.sk \
--to=pkrempa@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=libvir-list@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--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).