Problems with tip (Remus?)

Problems with tip (Remus?)

[Dan Magenheimer]

[-- Attachment #1.1: Type: text/plain, Size: 487 bytes --]

Just updated to latest tip (20419), including rebuilding tools (but not dom0,
not sure if there is a new dependency there) and I'm getting an infinite
loop of error messages when xend is trying to launch, along the lines
of "Xend died due to signal 6!" and "Xend died due to signal 11!".

Everything was fine earlier today on a c/s >20400.  I'll try backing out
the remus changes that just went in, but thought I would give warning
and see if others run into the problem.

Dan

[-- Attachment #1.2: Type: text/html, Size: 1795 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: Problems with tip (Remus?)

[Brendan Cully]

On Monday, 09 November 2009 at 14:02, Dan Magenheimer wrote:
> Just updated to latest tip (20419), including rebuilding tools (but not dom0,
> not sure if there is a new dependency there) and I'm getting an infinite
> loop of error messages when xend is trying to launch, along the lines
> of "Xend died due to signal 6!" and "Xend died due to signal 11!".
>  
> Everything was fine earlier today on a c/s >20400.  I'll try backing out
> the remus changes that just went in, but thought I would give warning
> and see if others run into the problem.

I'll attempt to reproduce. Right now I'm being stopped by a different
error:

gcc -O1 -fno-omit-frame-pointer -fno-optimize-sibling-calls -m32 -march=i686 -g -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement  -nostdinc -fno-builtin -fno-common -iwithprefix include -Werror -Wno-pointer-arith -pipe -I/home/brendan/remus/xen-unstable.32/xen/include  -I/home/brendan/remus/xen-unstable.32/xen/include/asm-x86/mach-generic -I/home/brendan/remus/xen-unstable.32/xen/include/asm-x86/mach-default -msoft-float -fno-stack-protector -g -D__XEN__ -DVERBOSE -fno-omit-frame-pointer -DCONFIG_FRAME_POINTER -MMD -MF .unlzma.o.d -c unlzma.c -o unlzma.o
cc1: warnings being treated as errors
unlzma.c:534: warning: C99 inline functions are not supported; using GNU89
unlzma.c:534: warning: to disable this warning use -fgnu89-inline or the gnu_inline function attribute
make[4]: *** [unlzma.o] Error 1
make[4]: Leaving directory `/home/brendan/remus/xen-unstable.32/xen/common'

which I would guess is due to 20401:c4630f8f69cc interacting badly
with my Ubuntu 8.04 build environment.

RE: Problems with tip (Remus?)

[Dan Magenheimer]

Backed out to c/s 20404 and everything is fine again,
so either Remus or libxenlight or one of the e820 c/s.

> -----Original Message-----
> From: Brendan Cully [mailto:brendan@cs.ubc.ca]
> Sent: Monday, November 09, 2009 3:11 PM
> To: Dan Magenheimer
> Cc: Xen-Devel (E-mail)
> Subject: Re: [Xen-devel] Problems with tip (Remus?)
> 
> 
> On Monday, 09 November 2009 at 14:02, Dan Magenheimer wrote:
> > Just updated to latest tip (20419), including rebuilding 
> tools (but not dom0,
> > not sure if there is a new dependency there) and I'm 
> getting an infinite
> > loop of error messages when xend is trying to launch, along 
> the lines
> > of "Xend died due to signal 6!" and "Xend died due to signal 11!".
> >  
> > Everything was fine earlier today on a c/s >20400.  I'll 
> try backing out
> > the remus changes that just went in, but thought I would 
> give warning
> > and see if others run into the problem.
> 
> I'll attempt to reproduce. Right now I'm being stopped by a different
> error:
> 
> gcc -O1 -fno-omit-frame-pointer -fno-optimize-sibling-calls 
> -m32 -march=i686 -g -fno-strict-aliasing -std=gnu99 -Wall 
> -Wstrict-prototypes -Wno-unused-value 
> -Wdeclaration-after-statement  -nostdinc -fno-builtin 
> -fno-common -iwithprefix include -Werror -Wno-pointer-arith 
> -pipe -I/home/brendan/remus/xen-unstable.32/xen/include  
> -I/home/brendan/remus/xen-unstable.32/xen/include/asm-x86/mach
> -generic 
> -I/home/brendan/remus/xen-unstable.32/xen/include/asm-x86/mach
> -default -msoft-float -fno-stack-protector -g -D__XEN__ 
> -DVERBOSE -fno-omit-frame-pointer -DCONFIG_FRAME_POINTER -MMD 
> -MF .unlzma.o.d -c unlzma.c -o unlzma.o
> cc1: warnings being treated as errors
> unlzma.c:534: warning: C99 inline functions are not 
> supported; using GNU89
> unlzma.c:534: warning: to disable this warning use 
> -fgnu89-inline or the gnu_inline function attribute
> make[4]: *** [unlzma.o] Error 1
> make[4]: Leaving directory 
> `/home/brendan/remus/xen-unstable.32/xen/common'
> 
> which I would guess is due to 20401:c4630f8f69cc interacting badly
> with my Ubuntu 8.04 build environment.
>

Re: Problems with tip (Remus?)

[Brendan Cully]

Everything's looking good here, 64-bit Xen, 32-bit dom0.

On Monday, 09 November 2009 at 14:17, Dan Magenheimer wrote:
> Backed out to c/s 20404 and everything is fine again,
> so either Remus or libxenlight or one of the e820 c/s.
> 
> > -----Original Message-----
> > From: Brendan Cully [mailto:brendan@cs.ubc.ca]
> > Sent: Monday, November 09, 2009 3:11 PM
> > To: Dan Magenheimer
> > Cc: Xen-Devel (E-mail)
> > Subject: Re: [Xen-devel] Problems with tip (Remus?)
> > 
> > 
> > On Monday, 09 November 2009 at 14:02, Dan Magenheimer wrote:
> > > Just updated to latest tip (20419), including rebuilding 
> > tools (but not dom0,
> > > not sure if there is a new dependency there) and I'm 
> > getting an infinite
> > > loop of error messages when xend is trying to launch, along 
> > the lines
> > > of "Xend died due to signal 6!" and "Xend died due to signal 11!".
> > >  
> > > Everything was fine earlier today on a c/s >20400.  I'll 
> > try backing out
> > > the remus changes that just went in, but thought I would 
> > give warning
> > > and see if others run into the problem.
> > 
> > I'll attempt to reproduce. Right now I'm being stopped by a different
> > error:
> > 
> > gcc -O1 -fno-omit-frame-pointer -fno-optimize-sibling-calls 
> > -m32 -march=i686 -g -fno-strict-aliasing -std=gnu99 -Wall 
> > -Wstrict-prototypes -Wno-unused-value 
> > -Wdeclaration-after-statement  -nostdinc -fno-builtin 
> > -fno-common -iwithprefix include -Werror -Wno-pointer-arith 
> > -pipe -I/home/brendan/remus/xen-unstable.32/xen/include  
> > -I/home/brendan/remus/xen-unstable.32/xen/include/asm-x86/mach
> > -generic 
> > -I/home/brendan/remus/xen-unstable.32/xen/include/asm-x86/mach
> > -default -msoft-float -fno-stack-protector -g -D__XEN__ 
> > -DVERBOSE -fno-omit-frame-pointer -DCONFIG_FRAME_POINTER -MMD 
> > -MF .unlzma.o.d -c unlzma.c -o unlzma.o
> > cc1: warnings being treated as errors
> > unlzma.c:534: warning: C99 inline functions are not 
> > supported; using GNU89
> > unlzma.c:534: warning: to disable this warning use 
> > -fgnu89-inline or the gnu_inline function attribute
> > make[4]: *** [unlzma.o] Error 1
> > make[4]: Leaving directory 
> > `/home/brendan/remus/xen-unstable.32/xen/common'
> > 
> > which I would guess is due to 20401:c4630f8f69cc interacting badly
> > with my Ubuntu 8.04 build environment.
> >
> 

RE: Problems with tip (Remus?)

[Dan Magenheimer]

Works after a make clean and rebuild in tools.  Maybe there's some
file dependency missing somewhere?  In any case, problem solved,
thanks.

> -----Original Message-----
> From: Brendan Cully [mailto:brendan@cs.ubc.ca]
> Sent: Monday, November 09, 2009 4:04 PM
> To: Dan Magenheimer
> Cc: Xen-Devel (E-mail)
> Subject: Re: [Xen-devel] Problems with tip (Remus?)
> 
> 
> Everything's looking good here, 64-bit Xen, 32-bit dom0.
> 
> On Monday, 09 November 2009 at 14:17, Dan Magenheimer wrote:
> > Backed out to c/s 20404 and everything is fine again,
> > so either Remus or libxenlight or one of the e820 c/s.
> > 
> > > -----Original Message-----
> > > From: Brendan Cully [mailto:brendan@cs.ubc.ca]
> > > Sent: Monday, November 09, 2009 3:11 PM
> > > To: Dan Magenheimer
> > > Cc: Xen-Devel (E-mail)
> > > Subject: Re: [Xen-devel] Problems with tip (Remus?)
> > > 
> > > 
> > > On Monday, 09 November 2009 at 14:02, Dan Magenheimer wrote:
> > > > Just updated to latest tip (20419), including rebuilding 
> > > tools (but not dom0,
> > > > not sure if there is a new dependency there) and I'm 
> > > getting an infinite
> > > > loop of error messages when xend is trying to launch, along 
> > > the lines
> > > > of "Xend died due to signal 6!" and "Xend died due to 
> signal 11!".
> > > >  
> > > > Everything was fine earlier today on a c/s >20400.  I'll 
> > > try backing out
> > > > the remus changes that just went in, but thought I would 
> > > give warning
> > > > and see if others run into the problem.
> > > 
> > > I'll attempt to reproduce. Right now I'm being stopped by 
> a different
> > > error:
> > > 
> > > gcc -O1 -fno-omit-frame-pointer -fno-optimize-sibling-calls 
> > > -m32 -march=i686 -g -fno-strict-aliasing -std=gnu99 -Wall 
> > > -Wstrict-prototypes -Wno-unused-value 
> > > -Wdeclaration-after-statement  -nostdinc -fno-builtin 
> > > -fno-common -iwithprefix include -Werror -Wno-pointer-arith 
> > > -pipe -I/home/brendan/remus/xen-unstable.32/xen/include  
> > > -I/home/brendan/remus/xen-unstable.32/xen/include/asm-x86/mach
> > > -generic 
> > > -I/home/brendan/remus/xen-unstable.32/xen/include/asm-x86/mach
> > > -default -msoft-float -fno-stack-protector -g -D__XEN__ 
> > > -DVERBOSE -fno-omit-frame-pointer -DCONFIG_FRAME_POINTER -MMD 
> > > -MF .unlzma.o.d -c unlzma.c -o unlzma.o
> > > cc1: warnings being treated as errors
> > > unlzma.c:534: warning: C99 inline functions are not 
> > > supported; using GNU89
> > > unlzma.c:534: warning: to disable this warning use 
> > > -fgnu89-inline or the gnu_inline function attribute
> > > make[4]: *** [unlzma.o] Error 1
> > > make[4]: Leaving directory 
> > > `/home/brendan/remus/xen-unstable.32/xen/common'
> > > 
> > > which I would guess is due to 20401:c4630f8f69cc interacting badly
> > > with my Ubuntu 8.04 build environment.
> > >
> > 
>

Re: Problems with tip (Remus?)

[Brendan Cully]

On Monday, 09 November 2009 at 17:06, Dan Magenheimer wrote:
> Works after a make clean and rebuild in tools.  Maybe there's some
> file dependency missing somewhere?

That is undoubtedly true. At this point, make clean is the first thing
I try whenever I have problems of any kind with Xen.

Re: Problems with tip (Remus?)

[Keir Fraser]

On 09/11/2009 22:11, "Brendan Cully" <brendan@cs.ubc.ca> wrote:

> I'll attempt to reproduce. Right now I'm being stopped by a different
> error:

Fixed by xen-unstable:20420.

 -- Keir

Re: Problems with tip (Remus?)

[Brendan Cully]

On Monday, 09 November 2009 at 14:11, Brendan Cully wrote:
> On Monday, 09 November 2009 at 14:02, Dan Magenheimer wrote:
> > Just updated to latest tip (20419), including rebuilding tools (but not dom0,
> > not sure if there is a new dependency there) and I'm getting an infinite
> > loop of error messages when xend is trying to launch, along the lines
> > of "Xend died due to signal 6!" and "Xend died due to signal 11!".
> >  
> > Everything was fine earlier today on a c/s >20400.  I'll try backing out
> > the remus changes that just went in, but thought I would give warning
> > and see if others run into the problem.
> 
> I'll attempt to reproduce. Right now I'm being stopped by a different
> error:
> 
> gcc -O1 -fno-omit-frame-pointer -fno-optimize-sibling-calls -m32 -march=i686 -g -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement  -nostdinc -fno-builtin -fno-common -iwithprefix include -Werror -Wno-pointer-arith -pipe -I/home/brendan/remus/xen-unstable.32/xen/include  -I/home/brendan/remus/xen-unstable.32/xen/include/asm-x86/mach-generic -I/home/brendan/remus/xen-unstable.32/xen/include/asm-x86/mach-default -msoft-float -fno-stack-protector -g -D__XEN__ -DVERBOSE -fno-omit-frame-pointer -DCONFIG_FRAME_POINTER -MMD -MF .unlzma.o.d -c unlzma.c -o unlzma.o
> cc1: warnings being treated as errors
> unlzma.c:534: warning: C99 inline functions are not supported; using GNU89
> unlzma.c:534: warning: to disable this warning use -fgnu89-inline or the gnu_inline function attribute
> make[4]: *** [unlzma.o] Error 1
> make[4]: Leaving directory `/home/brendan/remus/xen-unstable.32/xen/common'
> 
> which I would guess is due to 20401:c4630f8f69cc interacting badly
> with my Ubuntu 8.04 build environment.

And later, this:

gcc  -O1 -fno-omit-frame-pointer -fno-optimize-sibling-calls -m64 -g -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement  -D__XEN_TOOLS__ -MMD -MF .libxl.o.d  -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE  -I. -fPIC -I../../tools/libxc -I../../tools/include -I../../tools/libxc -I../../tools/include -I../../tools/xenstore -I../../tools/include -c -o libxl.o libxl.c
libxl.c: In function ‘libxl_domain_suspend’:
libxl.c:262: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result
In function ‘open’,
    inlined from ‘libxl_create_device_model’ at libxl.c:512:
/usr/include/bits/fcntl2.h:51: error: call to ‘__open_missing_mode’ declared with attribute error: open with O_CREAT in second argument needs 3 arguments
make[4]: *** [libxl.o] Error 1
make[4]: Leaving directory `/nfs/anthrax/brendan/remus/xen-unstable.64/tools/libxl'

Looks like the mode argument is missing here:

    logfile_w = open(logfile, O_WRONLY|O_CREAT);

Re: Problems with tip (Remus?)

[Keir Fraser]

On 09/11/2009 22:33, "Brendan Cully" <brendan@cs.ubc.ca> wrote:

> Looks like the mode argument is missing here:
> 
>     logfile_w = open(logfile, O_WRONLY|O_CREAT);

Ah yes, thanks. That one is fixed by xen-unstable:20421.

 -- Keir