From: Anthony Liguori <anthony@codemonkey.ws>
To: Ryan Harper <ryanh@us.ibm.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@gmail.com>,
qemu-devel <qemu-devel@nongnu.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [Qemu-devel] Block layer roadmap on wiki
Date: Mon, 22 Aug 2011 16:01:08 -0500 [thread overview]
Message-ID: <4E52C394.7050102@codemonkey.ws> (raw)
In-Reply-To: <20110822204810.GZ5792@us.ibm.com>
On 08/22/2011 03:48 PM, Ryan Harper wrote:
> * Stefan Hajnoczi<stefanha@gmail.com> [2011-08-22 15:32]:
>> We wouldn't rm -rf block/* because we still need qemu-nbd. It
>> probably makes sense to keep what we have today. I'm talking more
>> about a shift from writing our own image format to integrating
>> existing storage support.
>
> I think this is a key point. While I do like the idea of keeping QEMU
> focused on single VM, I think we don't help ourselves by not consuming
> the hypervisor platform services and integrating/exploiting those
> features to make using QEMU easier.
Let's avoid the h-word here as it's not terribly relevant to the discussion.
Configuring block devices is fundamentally a privileged operation. QEMU
fundamentally is designed to be useful as an unprivileged user.
That's the trouble with something like LVM. Only root can create LVM
snapshots and it's an all-or-nothing security model.
If you want to get QEMU out of the snapshot business, you need a file
system that's widely available that allows non-privileged users to take
snapshots of individual files.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2011-08-22 21:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-22 13:34 [Qemu-devel] Block layer roadmap on wiki Stefan Hajnoczi
2011-08-22 14:27 ` Ryan Harper
2011-08-22 17:58 ` Stefan Hajnoczi
2011-08-22 19:04 ` Anthony Liguori
2011-08-22 20:31 ` Stefan Hajnoczi
2011-08-22 20:48 ` Ryan Harper
2011-08-22 21:01 ` Anthony Liguori [this message]
2011-08-23 7:59 ` Stefan Hajnoczi
2011-08-23 11:25 ` Kevin Wolf
2011-08-23 12:21 ` Stefan Hajnoczi
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=4E52C394.7050102@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=hch@lst.de \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=ryanh@us.ibm.com \
--cc=stefanha@gmail.com \
/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.