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

RE: [Xen-ia64-devel] Community effort neededtocatch upwithxen-unstable


  • To: "John Byrne" <john.l.byrne@xxxxxx>
  • From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
  • Date: Sat, 3 Sep 2005 12:07:58 +0800
  • Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Sat, 03 Sep 2005 04:06:04 +0000
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcWv6ox2tX9QqaYZTEatR8TDLUFvrAAUjSrA
  • Thread-topic: [Xen-ia64-devel] Community effort neededtocatch upwithxen-unstable

>From: John Byrne [mailto:john.l.byrne@xxxxxx]
>With all the various patches, things work fine and I get a login
prompt.

Good.
>
>I knew the x86 model was different, what I didn't know was what you did
>with this patch was legal. It looks to me as if you have the operating
>system accessing a page the VM really shouldn't let it have. I was
>trying to figure out how to reserve the page in the EFI memory map: add
>it to the end of the hypercall page or something. Maybe its fortunate I
>had to go home so you could come up with the more straightforward fix.

Current simple fix is still a temporary dirty fix, IMO. We have to find
a better/standard way to do such communication between Xen and guest.
Maybe just after this merge. ;-)

>
>Spoke a little too soon, again. Looks like dom0 just crashed hard:
>
>(XEN) +01+01Heartbeat... iip=f0000000040092d0,psr.i=0,pend=1
>(XEN) +01ia64_fault: General Exception: IA-64 Reserved Register/Field
>fault (data access): reflecting
>
>
>I've no clue what the problem might be, things were idle. Still, things
>are better.

Interesting. I'll see whether I can reproduce next week.

Thanks,
Kevin

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


 


Rackspace

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