From: Anthony Liguori <aliguori@linux.vnet.ibm.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
qemu-devel@nongnu.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [Qemu-devel] [PATCH] Make default invocation of block drivers safer
Date: Thu, 15 Jul 2010 07:35:49 -0500 [thread overview]
Message-ID: <4C3F00A5.2080201@linux.vnet.ibm.com> (raw)
In-Reply-To: <20100715092056.GA14564@redhat.com>
On 07/15/2010 04:20 AM, Daniel P. Berrange wrote:
> On Wed, Jul 14, 2010 at 01:50:02PM -0500, Anthony Liguori wrote:
>
>> On 07/14/2010 01:43 PM, Christoph Hellwig wrote:
>>
>>> Err, strong NACK. Please don't start messing with the contents of the
>>> data plane, we're getting into real trouble there. It's perfectly
>>> valid for a guest to create an image inside an image, and with hardware
>>> support for nested virtualization I guess this use case will become
>>> rather common, just as it already is on S/390 with VM.
>>>
>>>
>> Then we have to remove block format probing.
>>
>> The two things are fundamentally incompatible.
>>
> FWIW, the latest libvirt code will now always set a fmt=XXX arg even
> for raw, so probing will never be performed. We also always set a backing
> store format when creating qcow2 files.
>
I assume libvirt probes once, then updates the guest's XML?
This is definitely the most user friendly option of all except for the
fact that we don't have a writeable config file in QEMU today.
Regards,
Anthony Liguori
> The main remaining unsolved issues are backing stores with non-qcow2
> files for which QEMU will always probe, and pre-existing qcow2 files
> which have been created without backing store formats. It would be
> nice to have an explicit arg to disable all backing store probing,
> forcing backing format to either be raw, or match the parent image
> format.
>
> Regards,
> Daniel
>
next prev parent reply other threads:[~2010-07-15 12:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-14 16:12 [Qemu-devel] [PATCH] Make default invocation of block drivers safer Anthony Liguori
2010-07-14 16:42 ` [Qemu-devel] " Kevin Wolf
2010-07-14 17:40 ` Anthony Liguori
2010-07-15 8:00 ` Kevin Wolf
2010-07-14 18:43 ` [Qemu-devel] " Christoph Hellwig
2010-07-14 18:50 ` Anthony Liguori
2010-07-15 9:20 ` Daniel P. Berrange
2010-07-15 12:35 ` Anthony Liguori [this message]
2010-07-15 15:19 ` Markus Armbruster
2010-07-15 16:20 ` Anthony Liguori
2010-07-15 17:10 ` Kevin Wolf
2010-07-15 17:51 ` Anthony Liguori
2010-07-16 7:30 ` Kevin Wolf
2010-07-16 12:55 ` Stefan Hajnoczi
2010-07-16 13:00 ` Stefan Hajnoczi
2010-07-16 16:06 ` Markus Armbruster
2010-07-16 16:16 ` Anthony Liguori
2010-07-16 16:24 ` Kevin Wolf
2010-07-14 18:53 ` Anthony Liguori
2010-07-14 18:54 ` Aurelien Jarno
2010-07-14 19:04 ` Anthony Liguori
2010-07-15 8:09 ` Kevin Wolf
2010-07-15 9:10 ` Stefan Hajnoczi
2010-07-15 12:57 ` Anthony Liguori
2010-07-15 13:16 ` Kevin Wolf
2010-07-15 13:20 ` 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=4C3F00A5.2080201@linux.vnet.ibm.com \
--to=aliguori@linux.vnet.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=berrange@redhat.com \
--cc=hch@lst.de \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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.