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


[Xen-devel] Re: [Qemu-devel] [PATCH 05/13] xen: groundwork for xen suppo

To: qemu-devel@xxxxxxxxxx
Subject: [Xen-devel] Re: [Qemu-devel] [PATCH 05/13] xen: groundwork for xen support
From: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Date: Tue, 26 Aug 2008 11:31:47 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Gerd Hoffmann <kraxel@xxxxxxxxxx>
Delivery-date: Tue, 26 Aug 2008 03:32:14 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <m2n.s.1KWDD7-002TB9@xxxxxxxxxxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Newsgroups: chiark.mail.nongnu.qemu.devel
References: <1219336054-15919-1-git-send-email-kraxel@xxxxxxxxxx> <m2n.s.1KWDD7-002TB9@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Gerd Hoffmann writes ("[Qemu-devel] [PATCH 05/13] xen: groundwork for xen 
> +/*
> + * Figure the environment we are running in.
> + * Returns true when xen is present, false otherwise.
> + * Also checks whenever the domain specified via -domid
> + * exists (so we can attach) or whenever it must be created.
> + */

I don't think this is the right approach.  The intent appears to be
that if you run a particular qemu rune, it will do a completely
different thing when running under Xen.

One bad effect of this is that it is not possible to do a software
emulation of the Xen environment if the host happens to actually be
running under Xen.

The command line, or chosen qemu executable, should specify what qemu
is supposed to do:
  - supporting tasks (hardware emulation etc.)
    for a real Xen domain managed by Xen tools via xenstore etc.
  - software emulation of the Xen environment for the benefit
    of a Xen domU but without using the Xen hypervisor (and
    this should obviously work even if running under Xen0
  - whatever other use cases are important; apparently Gerd
    seems keen to run some code with parts of the xend toolstack

Note that of course we have also ported qemu to our embedded minios so
that it can run as a service domain.

> +           "-domid          specify xen guest domain id\n"

Now would be a good time to rename this option to have the word `xen'
in it.


Xen-devel mailing list

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