From: Dor Laor <dlaor@redhat.com>
To: Federico Simoncelli <fsimonce@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, abaron@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qemu: new option for snapshot_blkdev to avoid image creation
Date: Tue, 11 Oct 2011 14:00:33 +0200 [thread overview]
Message-ID: <4E942FE1.1090902@redhat.com> (raw)
In-Reply-To: <21253396-fd2b-4bd2-afcf-2f5659347f5e@zmail02.collab.prod.int.phx2.redhat.com>
On 10/11/2011 01:56 PM, Federico Simoncelli wrote:
> ----- Original Message -----
>> From: "Dor Laor"<dlaor@redhat.com>
>> To: "Federico Simoncelli"<fsimonce@redhat.com>
>> Cc: qemu-devel@nongnu.org, abaron@redhat.com, "Kevin Wolf"<kwolf@redhat.com>
>> Sent: Friday, October 7, 2011 12:45:06 AM
>> Subject: Re: [Qemu-devel] [PATCH] qemu: new option for snapshot_blkdev to avoid image creation
>>
>> On 10/03/2011 06:09 PM, Federico Simoncelli wrote:
>>> Add the new option [-n] for snapshot_blkdev to avoid the image
>>> creation.
>>> The file provided as [new-image-file] is considered as already
>>> initialized
>>> and will be used after passing a check for the backing file.
>>
>> Seems ok to me as a way to go around fdget and still have selinux
>> gain.
>> Worth to get Kevin's view too.
>
> Hi Kevin, any news on this?
>
>> Federico, would you like to ack or extend the design:
>> http://wiki.qemu.org/Features/Snapshots
>
> Dor, should I do it now or only after my patch is acked?
We're not that strict in the OSS world ;) you can do it before and mark
as a pending request.
btw: Kevin is back so he will probably drain his queue soon.
next prev parent reply other threads:[~2011-10-11 12:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 16:09 [Qemu-devel] New option for snapshot_blkdev to avoid image creation Federico Simoncelli
2011-10-03 16:09 ` [Qemu-devel] [PATCH] qemu: new " Federico Simoncelli
2011-10-06 22:45 ` Dor Laor
2011-10-11 11:56 ` Federico Simoncelli
2011-10-11 12:00 ` Dor Laor [this message]
2011-10-04 7:33 ` [Qemu-devel] New " Stefan Hajnoczi
2011-10-04 8:27 ` Federico Simoncelli
2011-10-04 10:33 ` Stefan Hajnoczi
2011-10-11 12:30 ` Kevin Wolf
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=4E942FE1.1090902@redhat.com \
--to=dlaor@redhat.com \
--cc=abaron@redhat.com \
--cc=fsimonce@redhat.com \
--cc=kwolf@redhat.com \
--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).