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-users

Re: [Xen-users] Converting a HVM Guest into a PV-on-HVM Guest

To: Srujan Kotikela <ksrujandas@xxxxxxxxx>
Subject: Re: [Xen-users] Converting a HVM Guest into a PV-on-HVM Guest
From: Todd Deshane <todd.deshane@xxxxxxx>
Date: Mon, 20 Jun 2011 22:51:14 -0400
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 20 Jun 2011 19:52:41 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:from :date:x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=pa2voWov4CABiPwkCylAjL8OTOv9SRG79Hd+4vidReA=; b=EBbc2qhFkK86hnzoz/tJBowoZJoDymNW7bbdcOBc5KX0jG3JvLb1xWbKCXztwfY6ly /OG7DoOHA8PRS33iHvrKM2yfPsAbmWjH7MAQGLdz52f6Yg3ForysNjh4rpvqjvvrppb3 U7BwVjoR6fRMfOvX/F8rYWxCUXvkE+mCC6jCc=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; b=DP/oexrp+kLRk2XUlzDy+bZHXyMgiVQypNljk13vojMQ6joY6KYhHxt8DwOjbD7V9C PuiFzfVK1X7sSo92lB+S3kIUTYYJ9pTR39zXeEjPJlhIWIEhzMjINHXXJuZVusuc8r50 qBElXF8ZdskjBmisXVA5tBRHtsRWJpjmatKAQ=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <BANLkTikcjhshnu7ArCZkmvP_1Q8XmU8-6A@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <BANLkTim0Xo6pvuy41Ut1WSPgq48cr8qiUw@xxxxxxxxxxxxxx> <BANLkTi=j2h1F3C_60YOgNEt1YDRZyQB_Lw@xxxxxxxxxxxxxx> <BANLkTim6dqCSTDC6FsCvC-vv1WqWyGhUSg@xxxxxxxxxxxxxx> <BANLkTimjVNCAmM_i+m4ir80gz6gmX6i6rA@xxxxxxxxxxxxxx> <BANLkTinp7wFkEvHEJ1jxUVbhz=wY+iEP_w@xxxxxxxxxxxxxx> <BANLkTikcjhshnu7ArCZkmvP_1Q8XmU8-6A@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Mon, Jun 20, 2011 at 10:23 PM, Srujan Kotikela <ksrujandas@xxxxxxxxx> wrote:
>> Hi Todd,
>> Thanks for the reply.
>> I am trying to invoke a hypercall from the HVM guest. The only way I did
>> hypercalls from DomU till now (on PV guests) is use the libxc
>> library do_xen_hypercall (which in turn uses do_privcmd which in turn uses
>> ioctl).
>> Now I have a added a custom hypercall to xen and I am trying to invoke it
>> from HVM guest. As the HVM guest is not xenified (-linux) it doesn't have
>> the privcmd interface (/proc/xen/privcmd). So I am looking for a way to
>> invoke the custom hypercall from HVM. While in this try, I found that
>> pv-on-hvm will enable hypercalls from HVM guest. However I also read that it
>> may not allow all the hypercalls (correct me if I am wrong).
>> While looking at the other posts I found
>> this, http://xen.1045712.n5.nabble.com/hypercalls-from-HVM-guest-on-XEN-3-4-3-td4454566.html which
>> recommends to look into tools/firmware/hvmloader. There is some code in
>> hypercall.h in the hvmloader directory
>> (http://rswiki.csie.org/lxr/http/source/tools/firmware/hvmloader/hypercall.h?v=xen-4.0.0;a=ppc).
>> I am figuring out how to make use of this. Will update once I figure it out.
>> Sorry for not being unclear, earlier.

I do think that you are getting into the territory where you might
want to read this [1] and then ask on xen-devel for clarification.

[1] http://wiki.xensource.com/xenwiki/AskingXenDevelQuestions

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

<Prev in Thread] Current Thread [Next in Thread>