Re: [Xen-devel] Re: [PATCH 01 of 25] libxc: infrastructure for hypercall safe data buffers

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Tue, 2010-10-26 at 16:24 +0100, Ian Campbell wrote:
> On Tue, 2010-10-26 at 16:17 +0100, Olaf Hering wrote:
> > On Tue, Oct 26, Ian Jackson wrote:
> > 
> > > Ian Campbell writes ("[Xen-devel] Re: [PATCH 01 of 25] libxc: 
> > > infrastructure for hypercall safe data buffers"):
> > > > The following patch is needed before this one to fix build error in
> > > > xc_hcall_buf.c when building with stub domains.
> > > 
> > > I've committed, this, and the following 25-patch series (with the
> > > revised version of 01/25).
> > 
> > Does that actually for anyone?
> > Rev 22285 worked, rev 22313 broke.
> > 
> > ...
> > [2010-10-26 17:09:11 4743] INFO (SrvDaemon:332) Xend Daemon started
> > [2010-10-26 17:09:11 4743] ERROR (SrvDaemon:349) Exception starting xend 
> > ((14, 'Bad address'))
> > Traceback (most recent call last):
> >   File "/usr/lib64/python2.6/site-packages/xen/xend/server/SrvDaemon.py", 
> > line 335, in run
> >     xinfo = xc.xeninfo()
> > Error: (14, 'Bad address')
> > [2010-10-26 17:09:11 4742] INFO (SrvDaemon:220) Xend exited with status 1.
> > ...
> 
> hmm, I tested xend but trying it now myself I see that it is broken.
> I'll sort it out ASAP.

ASAP won't be today now unfortunately.

Reverting 9fad5e5e2fc1 followed by ca4a781c8ae8 fixes the issue for me,
with ca4a781c8ae8 more than likely being the actual culprit.

I'm sure I fixed something like this once before, must have rebroken it
in a rebase or something.

Ian.

> 
> > Does this series require dom0 kernel changes by any chance?
> 
> it shouldn't.
> 
> Ian.
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel



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