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

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

To: Pasi Kärkkäinen <pasik@xxxxxx>
Subject: [SPAM] Re: [Xen-devel] [SPAM] how does hypervisor isolates DomU from Dom0
From: Tapas Mishra <mightydreams@xxxxxxxxx>
Date: Mon, 16 Aug 2010 20:42:20 +0530
Cc: Xen List <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 16 Aug 2010 08:18:30 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=mTeEutTSFZzph2ZqotIC6wewnb37zq9Ka15xG0msPLk=; b=RgycD/FrDlCWFZfaAgkZ2Qa3xIH5u342a8pcLhloHynuaj0sA+495SwN1iN0rnnUwu 2BNDbDktc6LS68rEm9eKTTrMJvcAAKKwLE1RqOL5m/5dtzva45hz8xpvRKbyHeVfQ7fC pJuGr0ycuF8eCGbWBin5IYV6ZCaAHOxj5e9Kc=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=lOQnVqgNhhHSFoyKyPAq5FlIEEvxcTO0O9dDqse4AEeULCVwQ4Gq0qE9U6NM6a+Aju +ShofQSAB2+WGqJ1k0tVLz6V+zQqHc1/Vnh/FICeBTKok3txJViY/BzxKniNw1U9+rOj zaC8HWdmfbo1HzbymAfC2tNpOsOCGpX2TC23o=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
Importance: Low
In-reply-to: <20100816112425.GJ2804@xxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> 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.
-- 
Tapas
http://mightydreams.blogspot.com
http://wiki.xensource.com/xenwiki/Xen_on_4_app_servers

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel