From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Wolf Subject: Re: Re: [PATCH] qemu-xen: Fix PV segfault Date: Thu, 03 Jul 2008 10:16:49 +0200 Message-ID: <486C8AF1.6080804@suse.de> References: <4863E1F6.60909@suse.de> <18538.27111.959001.890654@mariner.uk.xensource.com> <486B3428.5000006@suse.de> <486B3E88.1020904@redhat.com> <20080702141917.GD23929@totally.trollied.org.uk> <486C876E.8040504@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <486C876E.8040504@redhat.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: Gerd Hoffmann Cc: xen-devel@lists.xensource.com, Ian Jackson , John Levon List-Id: xen-devel@lists.xenproject.org Gerd Hoffmann schrieb: > I also want to have the xen bits upstream (pv first as mentioned in the > previous mail). And I want to have it as runtime option, not > compile-time option, so you don't have a separate qemu-dm binary. Actually, I think Xen PV is a different architecture, not just a different PC machine. So to be consistent with qemu it would be a separate binary like qemu-system-xenpv. HVM on the other hand would be more of an accelerator for the existing x86 system emulation, just like kqemu or KVM. Kevin