From: john cooper <john.cooper@redhat.com>
To: KVM list <kvm@vger.kernel.org>, qemu-devel@nongnu.org
Cc: john.cooper@redhat.com, Rusty Russell <rusty@rustcorp.com.au>,
Christoph Hellwig <hch@lst.de>
Subject: [Qemu-devel] Re: [PATCH 0/2] Add serial number support for virtio_blk, V4a
Date: Wed, 03 Jun 2009 17:06:49 -0400 [thread overview]
Message-ID: <4A26E5E9.4030906@redhat.com> (raw)
In-Reply-To: <4A1F6130.9070705@redhat.com>
[Cosmetic changes to prior version, documentation
added to individual patches.]
This patch allows passing of a virtio_blk drive
serial number from qemu into a guest's virtio_blk
driver, and provides a means to access the serial
number from a guest's userspace.
Equivalent functionality currently exists for IDE
and SCSI, however it is not yet implemented for
virtio. Scenarios exist where guest code relies
on a unique drive serial number to correctly
identify the machine environment in which it
exists. The following patches, relative to
qemu-kvm.git and 2.6.29.3 respectively, provide
an equivalent mechanism for virtio_blk.
Usage:
With a patched qemu and guest virtio_blk driver,
launch the guest with a virtio_blk drive specifying
a serial number, eg:
-drive ... ,if=virtio,serial=ThisSpace4Rent, ...
In the guest retrieve via HDIO_GET_IDENTITY ioctl
to the virtio_blk driver, (eg):
# hdparm -i /dev/vda
hdparm -i /dev/vda
/dev/vda:
Model=QEMU VIRT_BLK, FwRev=0.10.50, SerialNo=ThisSpace4Rent
-john
--
john.cooper@redhat.com
next prev parent reply other threads:[~2009-06-03 21:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-29 4:14 [Qemu-devel] [PATCH 0/2] Add serial number support for virtio_blk, V4 john cooper
2009-06-03 21:06 ` john cooper [this message]
2009-06-03 21:07 ` [Qemu-devel] Re: [PATCH 1/2] Add serial number support for virtio_blk, V4a john cooper
2009-06-03 21:07 ` [Qemu-devel] Re: [PATCH 2/2] " john cooper
2009-06-04 6:31 ` Rusty Russell
2009-06-09 12:19 ` [Qemu-devel] [PATCH] " Rusty Russell
2009-06-09 12:42 ` [Qemu-devel] " Jens Axboe
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=4A26E5E9.4030906@redhat.com \
--to=john.cooper@redhat.com \
--cc=hch@lst.de \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=rusty@rustcorp.com.au \
/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).