From: Anthony Liguori <anthony@codemonkey.ws>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Avi Kivity <avi@redhat.com>, Juan Quintela <quintela@redhat.com>,
Chris Wright <chrisw@redhat.com>,
kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: KVM call agenda for Mar 16
Date: Tue, 16 Mar 2010 10:05:40 -0500 [thread overview]
Message-ID: <4B9F9E44.9050807@codemonkey.ws> (raw)
In-Reply-To: <20100316104537.GH23617@redhat.com>
On 03/16/2010 05:45 AM, Daniel P. Berrange wrote:
> On Tue, Mar 16, 2010 at 12:38:02PM +0200, Avi Kivity wrote:
>
>> On 03/16/2010 12:31 PM, Daniel P. Berrange wrote:
>>
>>>> Polling loops are an indication that something is wrong.
>>>>
>>>>
>>> Except when people suggest they are the right answer, qcow high
>>> watermark ;-P
>>>
>>>
>> I liked Anthony's suggestion of an lvm2 block format driver. No polling.
>>
> Doesn't that require giving QEMU privileges to perform LVM operations which
> implies QEMU having CAP_SYS_ADMIN ?
>
If QEMU is able to resize an LVM partition, it needs to carry privileges.
I'm not sure how this can be done safely in a lesser privileged
environment. Presumably, you're over committing storage and there's not
much you can do if the guests exhaust their storage all at once.
Regards,
Anthony Liguori
> Daniel
>
WARNING: multiple messages have this Message-ID (diff)
From: Anthony Liguori <anthony@codemonkey.ws>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Chris Wright <chrisw@redhat.com>,
qemu-devel@nongnu.org, Avi Kivity <avi@redhat.com>,
kvm@vger.kernel.org, Juan Quintela <quintela@redhat.com>
Subject: [Qemu-devel] Re: KVM call agenda for Mar 16
Date: Tue, 16 Mar 2010 10:05:40 -0500 [thread overview]
Message-ID: <4B9F9E44.9050807@codemonkey.ws> (raw)
In-Reply-To: <20100316104537.GH23617@redhat.com>
On 03/16/2010 05:45 AM, Daniel P. Berrange wrote:
> On Tue, Mar 16, 2010 at 12:38:02PM +0200, Avi Kivity wrote:
>
>> On 03/16/2010 12:31 PM, Daniel P. Berrange wrote:
>>
>>>> Polling loops are an indication that something is wrong.
>>>>
>>>>
>>> Except when people suggest they are the right answer, qcow high
>>> watermark ;-P
>>>
>>>
>> I liked Anthony's suggestion of an lvm2 block format driver. No polling.
>>
> Doesn't that require giving QEMU privileges to perform LVM operations which
> implies QEMU having CAP_SYS_ADMIN ?
>
If QEMU is able to resize an LVM partition, it needs to carry privileges.
I'm not sure how this can be done safely in a lesser privileged
environment. Presumably, you're over committing storage and there's not
much you can do if the guests exhaust their storage all at once.
Regards,
Anthony Liguori
> Daniel
>
next prev parent reply other threads:[~2010-03-16 15:07 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-16 7:01 KVM call agenda for Mar 16 Chris Wright
2010-03-16 7:01 ` [Qemu-devel] " Chris Wright
2010-03-16 9:18 ` Juan Quintela
2010-03-16 9:18 ` [Qemu-devel] " Juan Quintela
2010-03-16 9:29 ` Daniel P. Berrange
2010-03-16 9:29 ` [Qemu-devel] " Daniel P. Berrange
2010-03-16 9:43 ` Avi Kivity
2010-03-16 9:43 ` [Qemu-devel] " Avi Kivity
2010-03-16 10:31 ` Daniel P. Berrange
2010-03-16 10:31 ` [Qemu-devel] " Daniel P. Berrange
2010-03-16 10:38 ` Avi Kivity
2010-03-16 10:38 ` [Qemu-devel] " Avi Kivity
2010-03-16 10:45 ` Christoph Hellwig
2010-03-16 10:45 ` [Qemu-devel] " Christoph Hellwig
2010-03-16 10:45 ` Daniel P. Berrange
2010-03-16 10:45 ` [Qemu-devel] " Daniel P. Berrange
2010-03-16 11:16 ` Avi Kivity
2010-03-16 11:16 ` [Qemu-devel] " Avi Kivity
2010-03-16 15:05 ` Anthony Liguori [this message]
2010-03-16 15:05 ` Anthony Liguori
2010-03-16 15:23 ` Daniel P. Berrange
2010-03-16 15:23 ` [Qemu-devel] " Daniel P. Berrange
2010-03-16 15:46 ` Anthony Liguori
2010-03-16 15:46 ` [Qemu-devel] " Anthony Liguori
2010-03-16 10:09 ` Daniel P. Berrange
2010-03-16 10:09 ` [Qemu-devel] " Daniel P. Berrange
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=4B9F9E44.9050807@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=berrange@redhat.com \
--cc=chrisw@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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.