From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: [PATCH 02/15] xen: Add xen_machine_fv Date: Mon, 16 Aug 2010 10:07:51 -0500 Message-ID: <4C695447.6030603@codemonkey.ws> References: <1281622202-3453-2-git-send-email-stefano.stabellini@eu.citrix.com> <4C694054.8010600@redhat.com> <4C6947A6.70908@redhat.com> <4C694D64.8040402@codemonkey.ws> <4C695070.5010405@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4C695070.5010405@redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org To: Kevin Wolf Cc: Anthony Perard , "xen-devel@lists.xensource.com" , "qemu-devel@nongnu.org" , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org On 08/16/2010 09:51 AM, Kevin Wolf wrote: > Am 16.08.2010 16:38, schrieb Anthony Liguori: > >> >> To be honest, I think we'll need KVM, Xen, and QEMU specific machines. >> >> The right default set of hardware for all three is different. >> > Right, I agree. This is why I put the exception for the platform device. > There are probably some more devices for which the same applies. > > But these exceptions all about guest state. If qdev was finished, this > would be a matter of having a different configuration file, right? > > This series, as I understand it, is adding much more to the Xen FV > machine. Things that are not about which devices a VM contains, but > about some implementation details of the host. > Yeah, but dropping the target-xen will probably fix most of that stuff. Regards, Anthony Liguori > Kevin >