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

["Tian, Kevin" <kevin.tian@xxxxxxxxx>]

OK, attached is the set of patches by far. Based on them, now I can
enable grant table and also a small xenstore test in dom0 succeeds.
However the root device still can't be located:

Running on Xen! flags=0x0
xen-event-channel using irq 233
grant table at e000010000000000
after gnttab_resume
Grant table initialized
Xen virtual console successfully installed as tty0
Event-channel device installed.
xen_blk: Initialising virtual block device driver
(Seems the blkback and blkfront still no connection yet!!!)

NET: Registered protocol family 2
IP: routing cache hash table of 4096 buckets, 64Kbytes
TCP established hash table entries: 65536 (order: 6, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 6, 1048576 bytes)
TCP: Hash tables configured (established 65536 bind 65536)
NET: Registered protocol family 1
NET: Registered protocol family 17
VFS: Cannot open root device "hda1" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)

Thanks,
Kevin
>-----Original Message-----
>From: Tian, Kevin
>Sent: Friday, August 26, 2005 5:54 PM
>To: Tian, Kevin; Magenheimer, Dan (HP Labs Fort Collins);
>xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>Subject: RE: [Xen-ia64-devel] Community effort needed to catch
>upwithxen-unstable
>
>Currently I could "xend start" and "xm create" to create a domU, which
ran to
>the point mounting root fs and can't find root device then. This is
possible
>result since you explicitly disable gnttab interface for now. I'm still
looking into
>xen driver code, especially for how it works on ia64 previously, and
also new
>changes coming from this sync. However it really took time. Anyway, I
at least
>need attached patch to make tools directory compiled, and people may
based
>on it to continue with some debug.
>
>Thanks,
>Kevin
>
>>-----Original Message-----
>>From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
>>[mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Tian,
>>Kevin
>>Sent: Friday, August 26, 2005 9:42 AM
>>To: Magenheimer, Dan (HP Labs Fort Collins);
>>xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>>Subject: RE: [Xen-ia64-devel] Community effort needed to catch
>>upwithxen-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

Attachment: hg_cleanup_0826_libxc
Description: hg_cleanup_0826_libxc

Attachment: hg_cleanup_0829_xeno
Description: hg_cleanup_0829_xeno

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