From mboxrd@z Thu Jan 1 00:00:00 1970 From: Samuel Thibault Subject: Re: Integrate kqemu emulation into xen hypervisor possible? Date: Tue, 1 Apr 2008 20:15:15 +0100 Message-ID: <20080401191515.GG5030@implementation> References: <20080401152527.GH4637@implementation.nationalexpresswifi.train> <20080401154852.GI4637@implementation.nationalexpresswifi.train> <20080401185223.GF31765@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Ross S. W. Walker" Cc: xen-devel@lists.xensource.com, "Daniel P. Berrange" List-Id: xen-devel@lists.xenproject.org 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. Samuel