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

[Xen-devel] Re: Is hypercall_hvm_op in changeset 11060 effective?


  • To: "Li, Xin B" <xin.b.li@xxxxxxxxx>
  • From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
  • Date: Mon, 14 Aug 2006 14:13:46 +0100
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Mon, 14 Aug 2006 06:14:12 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Aca9yABevSNKoKxKQoeZHIOaybJ/twALEKfOAAuHctAAJFLMkAA1uYtQAAY5wuk=
  • Thread-topic: Is hypercall_hvm_op in changeset 11060 effective?

Looks like it could be a 32-on-64 issue if you're running 64-bit Xen.
Perhaps the current test for this situation, in hvm_do_hypercall() in
arch/x86/hvm/hvm.c, is broken. It just tests guest_paging_levels, but that
may not work if paging is disabled. That's probably where you should look if
you're trying to debug this.

 -- Keir

On 14/8/06 11:17 am, "Li, Xin B" <xin.b.li@xxxxxxxxx> wrote:

>> The use of HVMOP_get_param in hvmloader was inconsistent with its
>> implementation within Xen. This is now fixed in c/s 11070. Thanks for
>> pointing out the problem!
>> 
> 
> Still can not work, I got:
> (XEN) (GUEST: 6) HVM Loader
> (XEN) (GUEST: 6) Detected Xen v3.0
> (XEN) (GUEST: 6) Loading ROMBIOS ...
> (XEN) (file=hvm.c, line=596) Bad HVM op 1222980.
> (XEN) (GUEST: 6) hypercall_hvm_op returned error: 38
> (XEN) (GUEST: 6) Loading Cirrus VGABIOS ...
> (XEN) (GUEST: 6) Loading VMXAssist ...
> (XEN) (GUEST: 6) VMX go ...
> 
> Maybe caused by the hypercall page 



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


 


Rackspace

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