From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KSaZa-0000fc-Q1 for qemu-devel@nongnu.org; Mon, 11 Aug 2008 12:48:46 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KSaZY-0000dc-Jp for qemu-devel@nongnu.org; Mon, 11 Aug 2008 12:48:46 -0400 Received: from [199.232.76.173] (port=43721 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KSaZY-0000dM-Ah for qemu-devel@nongnu.org; Mon, 11 Aug 2008 12:48:44 -0400 Received: from smtp.eu.citrix.com ([62.200.22.115]:43228) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KSaZY-000424-4Y for qemu-devel@nongnu.org; Mon, 11 Aug 2008 12:48:44 -0400 Date: Mon, 11 Aug 2008 17:48:39 +0100 From: Samuel Thibault Message-ID: <20080811164839.GT4499@implementation.uk.xensource.com> References: <1217865045-10722-1-git-send-email-kraxel@redhat.com> <48973F8E.8080109@codemonkey.ws> <18592.27270.794441.413710@mariner.uk.xensource.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <18592.27270.794441.413710@mariner.uk.xensource.com> Subject: [Qemu-devel] Re: [Xen-devel] Xen's qemu branches, etc. Reply-To: 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, qemu-devel@nongnu.org Ian Jackson, le Mon 11 Aug 2008 17:36:22 +0100, a écrit : > Code in qemu intended to support Xen guests without the use of the Xen > hypervisor and tools should be called `xenemu' or some such. This > includes backend drivers for block and network devices, > xenstore/xenbus emulation, and so on. Mmm, for backends it would be a bit odd, since in xen upstream we do have backends too (console and framebuffer), and as Gerd said we could in theory use the block and network backends too. Samuel From mboxrd@z Thu Jan 1 00:00:00 1970 From: Samuel Thibault Subject: Re: Xen's qemu branches, etc. Date: Mon, 11 Aug 2008 17:48:39 +0100 Message-ID: <20080811164839.GT4499@implementation.uk.xensource.com> References: <1217865045-10722-1-git-send-email-kraxel@redhat.com> <48973F8E.8080109@codemonkey.ws> <18592.27270.794441.413710@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: <18592.27270.794441.413710@mariner.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Jackson Cc: xen-devel@lists.xensource.com, qemu-devel@nongnu.org, Anthony Liguori List-Id: xen-devel@lists.xenproject.org Ian Jackson, le Mon 11 Aug 2008 17:36:22 +0100, a =E9crit : > Code in qemu intended to support Xen guests without the use of the Xen > hypervisor and tools should be called `xenemu' or some such. This > includes backend drivers for block and network devices, > xenstore/xenbus emulation, and so on. Mmm, for backends it would be a bit odd, since in xen upstream we do have backends too (console and framebuffer), and as Gerd said we could in theory use the block and network backends too. Samuel