From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KYIBd-00008G-8l for qemu-devel@nongnu.org; Wed, 27 Aug 2008 06:23:37 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KYIBX-00006R-TG for qemu-devel@nongnu.org; Wed, 27 Aug 2008 06:23:33 -0400 Received: from [199.232.76.173] (port=35593 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KYIBW-00005v-RV for qemu-devel@nongnu.org; Wed, 27 Aug 2008 06:23:31 -0400 Received: from mx1.redhat.com ([66.187.233.31]:40993) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KYIBW-00070X-Ge for qemu-devel@nongnu.org; Wed, 27 Aug 2008 06:23:30 -0400 Date: Wed, 27 Aug 2008 11:23:24 +0100 From: "Daniel P. Berrange" Subject: Re: [Xen-devel] Re: [Qemu-devel] [PATCH 05/13] xen: groundwork for xen support Message-ID: <20080827102324.GE25099@redhat.com> References: <18612.1557.455011.713070@mariner.uk.xensource.com> <20080826141400.GE19615@redhat.com> <48B413D5.3080203@redhat.com> <20080826144056.GG19615@redhat.com> <48B417E1.6090709@redhat.com> <18612.6399.960344.359943@mariner.uk.xensource.com> <48B51599.7040807@redhat.com> <18613.9249.931147.770220@mariner.uk.xensource.com> <20080827095625.GD25099@redhat.com> <18613.9648.179712.343123@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <18613.9648.179712.343123@mariner.uk.xensource.com> Reply-To: "Daniel P. Berrange" , qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Ian Jackson Cc: xen-devel@lists.xensource.com, Gerd Hoffmann , qemu-devel@nongnu.org On Wed, Aug 27, 2008 at 11:00:16AM +0100, Ian Jackson wrote: > Daniel P. Berrange writes ("Re: [Xen-devel] Re: [Qemu-devel] [PATCH 05/13] xen: groundwork for xen support"): > > There's no requirement from libvirt itself - just whatever infrastructure > > libvirt is using. So just a message about XenD/xm would be sufficient. > > Right, but I just wanted to avoid the situation where a naive user > sees `not for xm/xend systems' and thinks `that's not me because I'm > using libvirt'. They could be right in that thinking though - if using libvirt's QEMU backend, instead of XenD backend, then it'd be fine to launch VMs manually. Only the presence of XenD places constraints on usage. Regards, Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|