From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:38972) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qm5VM-0001R9-9V for qemu-devel@nongnu.org; Wed, 27 Jul 2011 10:54:41 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Qm5VI-0002qq-8b for qemu-devel@nongnu.org; Wed, 27 Jul 2011 10:54:36 -0400 Received: from mx1.redhat.com ([209.132.183.28]:2512) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qm5VI-0002qg-0Q for qemu-devel@nongnu.org; Wed, 27 Jul 2011 10:54:32 -0400 Message-ID: <4E30274F.8000701@redhat.com> Date: Wed, 27 Jul 2011 16:57:19 +0200 From: Kevin Wolf MIME-Version: 1.0 References: <1311684710-27074-1-git-send-email-coreyb@linux.vnet.ibm.com> <4E2EDABE.4050301@redhat.com> <4E2EF1E4.90007@linux.vnet.ibm.com> <4E2FC81A.5030501@redhat.com> <20110727082241.GG27072@redhat.com> <4E2FCE09.3080702@redhat.com> <20110727084304.GH27072@redhat.com> <4E300E25.8010407@linux.vnet.ibm.com> In-Reply-To: <4E300E25.8010407@linux.vnet.ibm.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v3] Add support for fd: protocol List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Corey Bryant Cc: libvir-list@redhat.com, aliguori@us.ibm.com, qemu-devel@nongnu.org, tchicks@us.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