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

RE: [Xen-devel] Anyone succeeds HVM on latest x86-64 xen


  • To: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Cui, Dexuan" <dexuan.cui@xxxxxxxxx>
  • Date: Thu, 19 Jul 2007 14:45:03 +0800
  • Delivery-date: Wed, 18 Jul 2007 23:42:47 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcfJznEue30T92u4Q/axgoTx+3EJXgAAcEBQ
  • Thread-topic: [Xen-devel] Anyone succeeds HVM on latest x86-64 xen

It seems some c/s between 15516 and 15604 breaks x86_64 Xen.
IA32pae Xen c/s 15605 is OK.

-- Dexuan

-----Original Message-----
From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx 
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Tian, Kevin
Sent: 2007年7月19日 14:32
To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Anyone succeeds HVM on latest x86-64 xen

I tried latest xen and linux-xen staging tree, but failed to run HVM 
domain on x86-64 environment. domU creation is OK.

However the weird thing is not HVM domain itself. Instead system 
crashed on dom0 context. I saw once with some stack dump that 
xen's page fault handler is executed on a dom0's stack which then 
causes nested page fault due to unable to fetch vcpu pointer. But 
I'm curious why stack switch doesn't happen?

Does anybody else observe same failure? I'm still debugging it and 
send out early in case it's my environment issue.

Thanks,
Kevin

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

_______________________________________________
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®.