I see. I would be using Xen 3.0, but there is no doccumentation for what I 
need to do networking-wise. It's very simple in 2.0.7, but they made it very 
complicated in 3.0. I ended up concluding that either something about 
running NAT is broken in Xen 3.0, or there's a critical undoccumented step 
that I'm missing.
Back to the kernel, I'm still at a loss.
Michael
On Thursday 19 January 2006 03:38 pm, Ralph Passgang wrote:
> oh sorry! I must be blind... you tried to compile a kernel for xen 2.0.7,
> and I can't compile the actual xen stuff. But seems to be the same error
> anyway. I guess I am also not able to compile a kernel with debian unstable
> for xen 2.0.7 anymore, but I have not tested it...
>
> Am Donnerstag, 19. Januar 2006 21:34 schrieb Ralph Passgang:
> > Am Donnerstag, 19. Januar 2006 20:32 schrieb Michael Hrivnak:
> > > I'm having a tough time compiling a new kernel for xen 2.0.7. Even
> > > without changing any options from the original .config, I get the
> > > following errors. I've tried with gcc4 and gcc3.4. Any thoughts? This
> > > is on Mandriva 2006.
> > >
> > > I've found several accounts of similar errors via google, but no
> > > solutions.
> >
> > I also having exactly that error on a recent debian sid/unstable. xen
> > 2.0.7 compiled on debian unstable at least until 31.08.05, since (at
> > least) 29.09.05 it's failing with the same asm errors. a build log is
> > available at http://packages.debianbase.de/sid/i386/xen/xen_2.0.7-2.error 
> >
> > It is exactly the same source package with same kernel config that
> > "suddently" fails in a clean auto build environment. I also think that it
> > has nothing to do with gcc directly, but I am not 100% sure about that,
> > but I think I checked it and the gcc versions didn't changes between the
> > two dates I mentioned. So to be honest, I don't have clue what's wrong...
> >
> > I can provided detailed information about installed packages and
> > libraries (needed as dependencies) and more... but for me personaly xen 2
> > is not very important anymore, because of xen3 :)
> >
> > > Thanks,
> > > Michael
> >
> > --Ralph
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-users 
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users 
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users