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: "Samuel Thibault" <samuel.thibault@xxxxxxxxxxxxx>
Subject: RE: [Xen-devel] Integrate kqemu emulation into xen hypervisor possible?
From: "Ross S. W. Walker" <rwalker@xxxxxxxxxxxxx>
Date: Tue, 1 Apr 2008 15:28:24 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Delivery-date: Tue, 01 Apr 2008 12:28:53 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
Importance: normal
In-reply-to: <20080401191515.GG5030@implementation>
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> <E2BB8074E5500C42984D980D4BD78EF9022A707B@xxxxxxxxxxxxxxxxxxxxx> <20080401191515.GG5030@implementation>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AciULLvIf3eeMk2SSYKaEwscZsD9iwAAEjqw
Thread-topic: [Xen-devel] Integrate kqemu emulation into xen hypervisor possible?
Samuel Thibault wrote:
> Ross S. W. Walker, le Tue 01 Apr 2008 15:04:58 -0400, a écrit :
> > Ok, I understand, merely removed the CPU emulation. Does that mean it
> > tracks very closely with upstream's version?
> Not so closely, but efforts are being done into that direction :)
> > 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.
> Qemu's qemu is called qemu, Xen's qemu-dm is called qemu-dm.  killall
> should work fine.

Doh! I even said 'qemu-dm' in my earlier post. Time for some more


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