WARNING - OLD ARCHIVES

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/
Xen

xen-devel

[Top] [All Lists]

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

To: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [Qemu-devel] [PATCH 05/13] xen: groundwork for xen support
From: Gerd Hoffmann <kraxel@xxxxxxxxxx>
Date: 2008年8月27日 10:51:37 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, "Daniel P. Berrange" <berrange@xxxxxxxxxx>, qemu-devel@xxxxxxxxxx
Delivery-date: 2008年8月27日 01:53:38 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <18612.6399.960344.359943@xxxxxxxxxxxxxxxxxxxxxxxx>
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>
References: <1219336054-15919-1-git-send-email-kraxel@xxxxxxxxxx> <m2n.s.1KWDD7-002TB9@xxxxxxxxxxxxxxxxxxxxxx> <18611.56211.660082.627144@xxxxxxxxxxxxxxxxxxxxxxxx> <20080826125742.GB19615@xxxxxxxxxx> <48B40306.2080104@xxxxxxxxxx> <20080826132309.GC19615@xxxxxxxxxx> <18612.1557.455011.713070@xxxxxxxxxxxxxxxxxxxxxxxx> <20080826141400.GE19615@xxxxxxxxxx> <48B413D5.3080203@xxxxxxxxxx> <20080826144056.GG19615@xxxxxxxxxx> <48B417E1.6090709@xxxxxxxxxx> <18612.6399.960344.359943@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.16 (X11/20080723)
Ian Jackson wrote:
> Gerd Hoffmann writes ("Re: [Xen-devel] Re: [Qemu-devel] [PATCH 05/13] xen: 
> groundwork for xen support"):
>> But when running on xen we want being able to qemu tell it should *not*
>> use the xen hypervisor but emulate things, thus -xen-emulate.
>
> That should be the default. It is not safe to use the Xen hypervisor
> directly if there is a management toolstack which expects to mediate
> domain creation.
Ok. I think we have three cases then:
 (1) xen emulation using xenner (default, with or without kvm).
 (2) running on xen, with xend creating the domain, and
 (3) running on xen, with qemu creating the domain.
For (2) and (3) we need command line switches to enable these modes.
Specifying a domain ID makes sense in all three cases though. So I'd
keep the -xen-domid switch, like this:
 -xen-domid <nr> specify xen domain id.
 -xen-attach attach to specified domain (created by xend).
 -xen-create create the domain directly.
Comments?
cheers,
 Gerd
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date: RE: [Xen-devel] Xen 3.3.0 - Assertion '!((irq_stat[(((get_cpu_info()->processor_id)))].__local_irq_count) != 0)' failed at xmalloc.c:180 , Cui, Dexuan
Next by Date: Re: [Xen-devel] [PATCH] xen/Makefile: use CC --version instead of -v , Keir Fraser
Previous by Thread: Re: [Xen-devel] Re: [Qemu-devel] [PATCH 05/13] xen: groundwork for xen support , Ian Jackson
Next by Thread: Re: [Xen-devel] Re: [Qemu-devel] [PATCH 05/13] xen: groundwork for xen support , Ian Jackson
Indexes: [Date] [Thread] [Top] [All Lists]

Copyright ©, Citrix Systems Inc. All rights reserved. Legal and Privacy
Citrix This site is hosted by Citrix

AltStyle によって変換されたページ (->オリジナル) /