[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


  • To: Nick Couchman <Nick.Couchman@xxxxxxxxx>
  • From: Tapas Mishra <mightydreams@xxxxxxxxx>
  • Date: Tue, 17 Aug 2010 08:09:56 +0530
  • Cc: Xen List <xen-users@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Mon, 16 Aug 2010 19:41:19 -0700
  • 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:content-transfer-encoding; b=t3pUG2czQon3fPEpDT8erNGw3eeUixRl99FFXEqmcSnG+gks5VPVMlD9LQ/VK7xi52 9VJhYeJlATmGpdDmBuWZikLbgLbaHCjSqPks/9+UqgnlZX5dQ0zX50uZC5RXLhEu1Rt8 1iJkojqlsV4tG8f/ANRskIt5DoNjJjvqZrtBY=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Ok.

On Mon, Aug 16, 2010 at 10:21 PM, Nick Couchman <Nick.Couchman@xxxxxxxxx> wrote:
>>>> On 2010/08/15 at 14:19, Tapas Mishra <mightydreams@xxxxxxxxx> wrote:
>> I am not clear with the working of hypervisor xen.
>> How does an instruction executed by kernel in Ring0 of DomU gets
>> mapped or executed by hypervisor and then is excuted in Dom0.
>> Is this thing some where on the wiki page?
>
> I'm not all that familiar with the internals of Xen, but I think the 
> high-level answer to your question is, it depends.  It depends on what type 
> of domU you're running.  Paravirtualized domUs are aware that they are 
> virtualized and that they do not have ring 0 access, so I'm guessing they do 
> not attempt to execute instructions in ring 0 without passing it through to 
> the hypervisor, which brokers those requests.  HVM domUs, on the other hand, 
> are full machines (more along the lines of how VMware does virtualization) 
> that can run an unmodified kernel.  So, kernels in HVM domUs attempt to 
> access ring 0 resources, which must then be translated by the HVM and passed 
> on to the hypervisor.
>
> That's my understanding of how it works...
>
> -Nick
>
>
>
> --------
> This e-mail may contain confidential and privileged material for the sole use 
> of the intended recipient.  If this email is not intended for you, or you are 
> not responsible for the delivery of this message to the intended recipient, 
> please note that this message may contain SEAKR Engineering (SEAKR) 
> Privileged/Proprietary Information.  In such a case, you are strictly 
> prohibited from downloading, photocopying, distributing or otherwise using 
> this message, its contents or attachments in any way.  If you have received 
> this message in error, please notify us immediately by replying to this 
> e-mail and delete the message from your mailbox.  Information contained in 
> this message that does not relate to the business of SEAKR is neither 
> endorsed by nor attributable to SEAKR.
>



-- 
Tapas
http://mightydreams.blogspot.com
http://wiki.xensource.com/xenwiki/Xen_on_4_app_servers

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.