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 		  
Home Products Support Community News
 
   
 

xen-devel

[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: [Xen-devel] [SPAM] how does hypervisor isolates DomU from Dom0

from [Pasi Kärkkäinen] [Permanent Link][Original]
To: Tapas Mishra <mightydreams@xxxxxxxxx>
Subject: Re: [Xen-devel] [SPAM] how does hypervisor isolates DomU from Dom0
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Mon, 16 Aug 2010 19:41:26 +0300
Cc: Xen List <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 16 Aug 2010 09:42:05 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AANLkTi=A1bv8qay8=UqiFcegt5Q+cVWqDO7dq4Lav3SC@xxxxxxxxxxxxxx>
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: <AANLkTi==yes96umbA=256cg0px_Q9hMXioZ7zRTZgFZH@xxxxxxxxxxxxxx> <AANLkTi=DqwAU+yuwP4sMBC4hEnJa0bJg+de2+u-RQQ0x@xxxxxxxxxxxxxx> <20100815204814.GT2804@xxxxxxxxxxx> <AANLkTinQ4jKf+K63g2SAr5RbE3fd=Ud4mxG8T9TMt98B@xxxxxxxxxxxxxx> <20100816112425.GJ2804@xxxxxxxxxxx> <AANLkTi=A1bv8qay8=UqiFcegt5Q+cVWqDO7dq4Lav3SC@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17) 
On Mon, Aug 16, 2010 at 08:42:20PM +0530, Tapas Mishra wrote:
> > Or take a look at the boottime messages.. first Xen hypervisor
> > is started (the lines starting with XEN), and when Xen hypervisor
> > is started it boots up the first guest VM: dom0 Linux. So you see
> > dom0 Linux boot messages after Xen boot messages.
> Yes this I have noticed.
> So dom0 is just a guest for the hypervisor but a previleged guest.
>

Yes, correct.

-- Pasi


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: [Xen-devel] [PATCH] Values of cpu_weight and cpu_cap are lost after xend restart, Stefano Stabellini
Next by Date:  Re: [Xen-devel] Xen patches merged to upstream Linux 2.6.36, plans for 2.6.37?, Mr. Teo En Ming (Zhang Enming) of Singapore
Previous by Thread:  [SPAM] Re: [Xen-devel] [SPAM] how does hypervisor isolates DomU from Dom0, Tapas Mishra
Next by Thread:  Re: [Xen-devel] Re: [PATCH] x86: unconditionally mark TSC unstable under Xen, Ævar Arnfjörð Bjarmason
Indexes:  [Date] [Thread] [Top] [All Lists]
 
   

Copyright , Citrix Systems Inc. All rights reserved. Legal and Privacy