From: Avi Kivity <avi@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
qemu-devel@nongnu.org, kvm@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [Qemu-devel] Re: [PATCH v2] virtio-blk physical block size
Date: Sun, 10 Jan 2010 14:35:48 +0200 [thread overview]
Message-ID: <4B49C9A4.10201@redhat.com> (raw)
In-Reply-To: <20100108154044.GB14634@lst.de>
On 01/08/2010 05:40 PM, Christoph Hellwig wrote:
> Maybe we should pick one on image creation and then stick to it. For an
> image format we could write down this information in the image, but for
> a raw images that's impossible.
>
The management system should remember it (like it remembers which images
belong to which guest, and how to expose them).
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2010-01-10 12:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1262018363-15871-1-git-send-email-avi@redhat.com>
2010-01-04 3:08 ` [Qemu-devel] Re: [PATCH v2] virtio-blk physical block size Rusty Russell
2010-01-04 7:02 ` Avi Kivity
2010-01-05 20:18 ` Jamie Lokier
2010-01-04 8:30 ` Christoph Hellwig
2010-01-05 12:56 ` Rusty Russell
2010-01-05 12:58 ` Avi Kivity
2010-01-05 20:16 ` Jamie Lokier
2010-01-08 15:40 ` Christoph Hellwig
2010-01-10 12:35 ` Avi Kivity [this message]
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=4B49C9A4.10201@redhat.com \
--to=avi@redhat.com \
--cc=hch@lst.de \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.linux-foundation.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).