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

RE: [Xen-ia64-devel] Community effort needed to catch up withxen-unstable


  • To: "Magenheimer, Dan \(HP Labs Fort Collins\)" <dan.magenheimer@xxxxxx>, <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
  • Date: Fri, 26 Aug 2005 09:42:15 +0800
  • Delivery-date: Fri, 26 Aug 2005 01:40:17 +0000
  • List-id: DIscussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcWpzFSxEuYaMJrXQ3Sk49Vkfrz73gAEk8yw
  • Thread-topic: [Xen-ia64-devel] Community effort needed to catch up withxen-unstable

We're working on it now... ;-) The network for Dom0 is good in our side,
and xend doesn't work.

Thanks,
Kevin

>-----Original Message-----
>From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
>[mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
>Magenheimer, Dan (HP Labs Fort Collins)
>Sent: Friday, August 26, 2005 7:26 AM
>To: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>Subject: [Xen-ia64-devel] Community effort needed to catch up
>withxen-unstable
>
>Per my email yesterday, xen-ia64-unstable was a couple weeks
>behind xen-unstable and xen-unstable has evolved considerably
>to support, for example, the new xenbus and xenstore
>mechanisms which will be in Xen 3.0.  This means that
>the core Xen drivers which were snapshotted two months
>ago in xenlinux-ia64 were hopelessly out of date and
>there will be significant work required to catch up.
>
>The hypervisor itself updated to the latest -unstable
>tip fairly easily, but I spent most of today trying to
>update the xenlinux-ia64 drivers.  I was able to work
>through all the syntactic issues (and mark them all
>with "#ifdef __ia64__") so that xenlinux will compile,
>but I made little attempt to resolve the semantic issues,
>and there are some new ones.
>
>This may not be popular, but I have checked in both updated
>trees: xen-ia64-unstable.hg and xenlinux-ia64-2.6.12.hg.
>The xen drivers are known to NOT work... indeed I have
>disabled them explicitly to avoid a domain0 kernel panic
>(see FIXME in driver/xen/core/gnttbl.c).  In addition,
>I noticed that domain0 normal networking seems to be
>broken (I have no clue why at this point).  Your mileage
>may vary.
>
>I would like to solicit (or maybe beg!) for your help
>in bug-hunting and bug-fixing to bring xen-ia64 back
>to the previous functionality (e.g. multiple domains
>working with grant tables, console and blk drivers).
>Some of you may have participated in implementation
>and debugging of the equivalent driver code on the x86 side
>and your help especially would be greatly appreciated.
>I see this as a community effort... I do not expect to
>accept new functionality patches until this is all
>working again.
>
>Thanks,
>Dan
>
>_______________________________________________
>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®.