This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


RE: [Xen-devel] Integrate kqemu emulation into xen hypervisor possible?

To: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Subject: RE: [Xen-devel] Integrate kqemu emulation into xen hypervisor possible?
From: "Ross S. W. Walker" <rwalker@xxxxxxxxxxxxx>
Date: Tue, 1 Apr 2008 15:04:58 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Samuel Thibault <samuel.thibault@xxxxxxxxxxxxx>
Delivery-date: Tue, 01 Apr 2008 12:05:28 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
Importance: normal
In-reply-to: <20080401185223.GF31765@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Priority: normal
References: <E2BB8074E5500C42984D980D4BD78EF9022A7073@xxxxxxxxxxxxxxxxxxxxx> <20080401152527.GH4637@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <E2BB8074E5500C42984D980D4BD78EF9022A7074@xxxxxxxxxxxxxxxxxxxxx> <20080401154852.GI4637@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <E2BB8074E5500C42984D980D4BD78EF9022A7079@xxxxxxxxxxxxxxxxxxxxx> <20080401185223.GF31765@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AciUKYsgCFk/1IQrQXWbLXXOndRt0QAARt/A
Thread-topic: [Xen-devel] Integrate kqemu emulation into xen hypervisor possible?
Daniel P. Berrange wrote:
> On Tue, Apr 01, 2008 at 02:41:17PM -0400, Ross S. W. Walker wrote:
> > I have always wondered why the xen developers decided to keep the qemu
> > name for the domain device provider after they have completely gutted
> > and pratically rewritten the original code?
> Xen has not re-written the original code. QEMU provides both a CPU
> emulator and a plethora of devices. Xen merely uses the device emulation
> and not the CPU emulation. There's a few patches to integrate with Xen
> but it is not a re-write.

Ok, I understand, merely removed the CPU emulation. Does that mean it
tracks very closely with upstream's version?

> > How about calling it just 'dm' for domain manager?
> No, renaming functional components for mere cosmetic reasons, will cause real 
> world breakage for existing deployments. This is not a net win.

Well I was thinking of the situation where one might be running qemu
instances on dom0 and when trying to work out which instance belonged
to Xen and which to QEmu it would be difficult.

'killall qemu' would be very bad to find in a shutdown script.


This e-mail, and any attachments thereto, is intended only for use by
the addressee(s) named herein and may contain legally privileged
and/or confidential information. If you are not the intended recipient
of this e-mail, you are hereby notified that any dissemination,
distribution or copying of this e-mail, and any attachments thereto,
is strictly prohibited. If you have received this e-mail in error,
please immediately notify the sender and permanently delete the
original and any copy or printout thereof.

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>