From: Ryan Harper <ryanh@us.ibm.com>
To: Marc Haber <mh+qemu-devel@zugschlus.de>
Cc: john cooper <john.cooper@redhat.com>,
john cooper <john.cooper@third-harmonic.com>,
Ryan Harper <ryanh@us.ibm.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] virtio block device and sysfs
Date: Mon, 13 Sep 2010 09:34:24 -0500 [thread overview]
Message-ID: <20100913143424.GS30086@us.ibm.com> (raw)
In-Reply-To: <20100913085548.GA28448@torres.zugschlus.de>
* Marc Haber <mh+qemu-devel@zugschlus.de> [2010-09-13 03:56]:
> Hi John and Ryan,
>
> On Tue, Jun 29, 2010 at 01:33:33PM -0500, Ryan Harper wrote:
> > We've got a sysfs 'serial' attribute for virtio-blk devices upstream[1].
> > I've got udev support for using this attribute to create disk/by-id (and
> > a fix for by-path) symlinks[2]. All that remains is to
> > re-spin/post the qemu virtio-blk serial patches[3] and get that in and
> > we'll have the full stack working as I've already tested libvirt (which
> > has disk serial support).
>
> How is this going to work once the patches have been applied? Even
> qemu 0.11's -drive definition allows a serial= option, but currently
> (qemu-kvm 0.12.5, and 2.6.35.4 in the guest) the string passed to it
> isn't seen anywhere in the guest's /sys/block/vda.
It'll only be available to guests launched with newer qemu (0.13) as
virtio-blk serial support is a new feature.
>
> My test call was
> kvm -cdrom ~/bigstuff/grml64-small_sid_20100913.iso \
> -drive file=test.qcow2,if=virtio,media=disk,serial=foo
>
> Greetings
> Marc
>
> --
> -----------------------------------------------------------------------------
> Marc Haber | "I don't trust Computers. They | Mailadresse im Header
> Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834
> Nordisch by Nature | How to make an American Quilt | Fax: *49 3221 2323190
--
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
ryanh@us.ibm.com
next prev parent reply other threads:[~2010-09-13 14:35 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-06 22:42 [Qemu-devel] virtio block device and sysfs Marc Haber
2010-03-09 1:17 ` jvrao
2010-03-09 8:21 ` Marc Haber
2010-03-09 20:04 ` jvrao
2010-03-09 20:06 ` jvrao
2010-03-09 21:15 ` Marc Haber
2010-03-09 21:34 ` Anthony Liguori
2010-03-21 16:16 ` Jamie Lokier
2010-03-22 6:26 ` john cooper
2010-03-22 12:42 ` Marc Haber
2010-03-22 14:59 ` john cooper
2010-03-25 5:30 ` john cooper
2010-06-29 18:15 ` Marc Haber
2010-06-29 18:03 ` john cooper
2010-06-29 20:20 ` Marc Haber
2010-06-29 18:33 ` Ryan Harper
2010-06-29 18:36 ` Marc Haber
2010-06-29 18:36 ` Marc Haber
2010-06-30 7:01 ` Markus Armbruster
2010-09-13 8:55 ` Marc Haber
2010-09-13 14:34 ` Ryan Harper [this message]
2010-09-14 7:43 ` Marc Haber
2011-03-10 12:14 ` Marc Haber
2010-03-22 12:38 ` Marc Haber
2010-03-22 14:22 ` john cooper
2010-03-22 16:24 ` Jamie Lokier
2010-03-22 16:33 ` john cooper
2010-04-22 20:30 ` Marc Haber
2010-04-22 20:48 ` john cooper
2010-03-22 15:14 ` Paul Brook
2010-04-22 20:33 ` Marc Haber
2010-03-22 14:46 ` [Qemu-devel] " Michael S. Tsirkin
2010-03-22 14:52 ` Anthony Liguori
2010-03-20 18:32 ` [Qemu-devel] " Richard W.M. Jones
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=20100913143424.GS30086@us.ibm.com \
--to=ryanh@us.ibm.com \
--cc=john.cooper@redhat.com \
--cc=john.cooper@third-harmonic.com \
--cc=mh+qemu-devel@zugschlus.de \
--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).