On Thu, Jan 01, 1970 at 12:00:00AM +0000, Ian Pratt wrote:
> > Is the current xen-merge tree supposed to work? I tried to
> > use it as a 64bit dom0 with a recent xen-unstable hypervisor,
> > and it didn't get farther than "Disabling xen tracebuffers"
> >
> > Didn't look too closely at the problem so far.
>
> That message somes from Xen, so its unlikely to be a problem with the
> dom0 image you're loading. Might be worth a 'make clean'.
>
> There has been a reported boot problem with x86_64 since the move to
> 2.6.14, and we're looking in to this.
One of the recent changes in xen-unstable seems to have fixed this problem.
I was able to boot x86_64 dom0 and domU with changesets 14428:76fc58fa82d9
and 14512:88d8d011df29. My xen-unstable tree was at changeset
7823:9c7aeec94f8a085d69e6a4de9d5a27ebe98c0287. There have been a few
interface breaking changes recently, so it's always best to use a matching
xen-unstable tree. I include the changeset number on every change I pull
across from xen-unstable, making it easy to find out which revision of
xen-unstable should work:
hg -v history | sed -n '/^linux-2.6-xen-sparse cset:/ {p;q}'
> > It also didn't build with a separate objdir.
>
> Good point -- we haven't tested this.
If someone could provide a patch, that would be neat...
christian
