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-community] Regarding paravirtualization

To: Xen-community@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-community] Regarding paravirtualization
From: Mourya Ch <chmourya@xxxxxxxxx>
Date: Sun, 3 Jan 2010 01:48:10 +0100
Delivery-date: Sat, 02 Jan 2010 16:48:07 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=tB7DJ1+zaRX7NHk0F2GjRjP2hOwtZYZ0WfGMuVjXawU=; b=wKvF3gViv02xoSiBjIjU4ktCIGRKxVRRMAUDHY00FIF7CethuKrcCjxPaBgyTtOmFD 9xkdPB6Rsqv0i7+ZURZf3ZdEirCJPlyQaaCFWXl6OgN2ookuvl0sLdQLJfSeJnVFEuJm k52DiEM/K51Lnyou/rbLJcC/DLvvXREYtQ2W8=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=F6Q6gxUn3CyvJ1Hu2zlFTbVhnidW6SbuxIIsUmrKqDX6IH1pFWapURaeffnoUrOJJP NHyjGFT7clS6r4+/y00EEBi64BgmvS/jJK1pEJih7j6FWXXhj2WERclXoTijMqjCWZYo uAtv5xw0+XA289NaKBlbTYRItwvwLft0zRVM8=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-archive: <http://lists.xensource.com/archives/html/xen-community>
List-help: <mailto:xen-community-request@lists.xensource.com?subject=help>
List-id: Community Discussion <xen-community.lists.xensource.com>
List-post: <mailto:xen-community@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-community>, <mailto:xen-community-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-community>, <mailto:xen-community-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-community-bounces@xxxxxxxxxxxxxxxxxxx
OK, i was reading a document from VMware (understanding full
virtualization, paravirtualization, HAV). There it was written that in
para virtualization all the priviliged instructions are handled by the
hypervisor and the guest OS runs in Ring 0. I didnt understand why the
guest OS should be in Ring 0 when all the sensitive instructions are
traped into hypervisor. This is same as binary translation where guest
OS resides in Ring 3 and VMM resides in Ring 0, then all the sensitive
instructions are trapped into VMM. Also, i didnt understand where the
VMM resides in paravirtualization when the guest OS runs in Ring 0.
Also, in case of Xen the guest OS resides in Ring 1 and VMM in Ring 0,
this makes some sense to me (or am i missing something ?)

Mourya Chintalapati
MS, IT (Pervasive Computing)
Klagenfurt, Austria

Xen-community mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-community] Regarding paravirtualization, Mourya Ch <=