From: Kevin Wolf <kwolf@redhat.com>
To: Corey Bryant <coreyb@linux.vnet.ibm.com>
Cc: libvir-list@redhat.com, aliguori@us.ibm.com,
qemu-devel@nongnu.org, tchicks@us.ibm.com
Subject: Re: [Qemu-devel] [PATCH v3] Add support for fd: protocol
Date: Wed, 27 Jul 2011 16:57:19 +0200 [thread overview]
Message-ID: <4E30274F.8000701@redhat.com> (raw)
In-Reply-To: <4E300E25.8010407@linux.vnet.ibm.com>
Am 27.07.2011 15:09, schrieb Corey Bryant:
> Kevin/Daniel, thanks a lot for your input.
>
> In terms of the support that libvirt requires, I just want to make sure
> all bases are covered.
>
> In order for this support to be useful to libvirt, the following are
> required (sorry if this is repetitive):
>
> 1) -blockdev (backing file support)
> 2) savevm (snapshot support)
savevm is harmless and doesn't need any special treatment.
> 3) snapshot_blkdev (snapshot support)
> 4) 'change' monitor command
> 5) -cdrom
>
> and as far as I know, the status of the above is:
>
> 1) Someone is slated to work on this (not me)
> 2) I need to figure out how to "re-open" file without an open (me)
> 3) This will be covered by live snapshots feature (not me)
> 4) Should just work as is (me)
> 5) May also just work as is (me)
>
> In other words, 1 and 3 will not be implemented by me (except perhaps
> some re-usable infrastructure). Could you confirm my understanding?
Yes, at least not at this point.
Kevin
next prev parent reply other threads:[~2011-07-27 14:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-26 12:51 [Qemu-devel] [PATCH v3] Add support for fd: protocol Corey Bryant
2011-07-26 13:02 ` Christoph Hellwig
2011-07-26 13:15 ` Corey Bryant
2011-07-26 14:02 ` [Qemu-devel] [libvirt] " Eric Blake
2011-07-26 14:05 ` [Qemu-devel] " Kevin Wolf
2011-07-26 14:46 ` Corey Bryant
2011-07-26 14:54 ` Kevin Wolf
2011-07-26 14:00 ` [Qemu-devel] [libvirt] " Eric Blake
2011-07-26 14:19 ` Kevin Wolf
2011-07-26 15:18 ` [Qemu-devel] " Kevin Wolf
2011-07-26 16:57 ` Corey Bryant
2011-07-26 17:10 ` Alexander Graf
2011-07-26 19:00 ` Corey Bryant
2011-07-27 8:11 ` Kevin Wolf
2011-07-27 8:22 ` Daniel P. Berrange
2011-07-27 8:36 ` Kevin Wolf
2011-07-27 8:43 ` Daniel P. Berrange
2011-07-27 13:09 ` Corey Bryant
2011-07-27 14:57 ` Kevin Wolf [this message]
2011-07-27 21:36 ` Blue Swirl
2011-08-11 16:28 ` Corey Bryant
2011-08-12 10:07 ` 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=4E30274F.8000701@redhat.com \
--to=kwolf@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=coreyb@linux.vnet.ibm.com \
--cc=libvir-list@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=tchicks@us.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 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).