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

RE: [Xen-ia64-devel] VTI still broken (non-p2m/vp)


  • To: "Alex Williamson" <alex.williamson@xxxxxx>, "xen-ia64-devel" <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Yang, Fred" <fred.yang@xxxxxxxxx>
  • Date: Mon, 15 May 2006 12:37:16 -0700
  • Delivery-date: Mon, 15 May 2006 12:41:57 -0700
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcZ4Vc5qXxMmQjs+REmaP2L/NJCQ8wAANyPA
  • Thread-topic: [Xen-ia64-devel] VTI still broken (non-p2m/vp)

Alex,

Anthony will work on this issue during his daytime :-) 
Thanks for the heads up,

-Fred 

>-----Original Message-----
>From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx 
>[mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf 
>Of Alex Williamson
>Sent: Monday, May 15, 2006 12:21 PM
>To: xen-ia64-devel
>Subject: [Xen-ia64-devel] VTI still broken (non-p2m/vp)
>
>
>   Heads up; VTI still appears to be somewhat broken on cset 10007 (w/o
>enabling dom0_vp).  I'm able to launch a VTI domain, however I only see
>a blk0 device at EFI.  I'm missing the partition table and the EFI
>filesystem on my boot disk.  Does anyone else see this?  It worked on
>cset 9999, so the regression happened in the step4 p2m/vp patches.
>Thanks,
>
>       Alex
>-- 
>Alex Williamson                             HP Linux & Open Source Lab
>
>
>_______________________________________________
>Xen-ia64-devel mailing list
>Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>http://lists.xensource.com/xen-ia64-devel
>

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