New release candidate for Xen 4.0.1

New release candidate for Xen 4.0.1

[Keir Fraser]

Tag '4.0.1-rc4' is now avaiable at http://xenbits.xen.org/xen-unstable.hg.
Please test!

 -- Keir

Re: New release candidate for Xen 4.0.1

[Pasi Kärkkäinen]

On Fri, Jul 16, 2010 at 02:05:03PM +0100, Keir Fraser wrote:
> Tag '4.0.1-rc4' is now avaiable at http://xenbits.xen.org/xen-unstable.hg.
> Please test!
> 

I assume in http://xenbits.xen.org/xen-4.0-testing.hg instead :)

-- Pasi

Re: New release candidate for Xen 4.0.1

[Keir Fraser]

On 16/07/2010 14:28, "Pasi Kärkkäinen" <pasik@iki.fi> wrote:

> On Fri, Jul 16, 2010 at 02:05:03PM +0100, Keir Fraser wrote:
>> Tag '4.0.1-rc4' is now avaiable at http://xenbits.xen.org/xen-unstable.hg.
>> Please test!
>> 
> 
> I assume in http://xenbits.xen.org/xen-4.0-testing.hg instead :)

Oh yes, indeed!

 -- Keir

> -- Pasi
> 

Re: New release candidate for Xen 4.0.1

[Pasi Kärkkäinen]

On Fri, Jul 16, 2010 at 02:54:55PM +0100, Keir Fraser wrote:
> On 16/07/2010 14:28, "Pasi Kärkkäinen" <pasik@iki.fi> wrote:
> 
> > On Fri, Jul 16, 2010 at 02:05:03PM +0100, Keir Fraser wrote:
> >> Tag '4.0.1-rc4' is now avaiable at http://xenbits.xen.org/xen-unstable.hg.
> >> Please test!
> >> 
> > 
> > I assume in http://xenbits.xen.org/xen-4.0-testing.hg instead :)
> 
> Oh yes, indeed!
> 

I just installed 4.0.1-rc4, and it built/installed/worked smoothly.
I used the latest 2.6.32.16 pvops dom0 kernel.

I was testing various Fedora 13 and CentOS 5.5 PV guests.

-- Pasi

Re: New release candidate for Xen 4.0.1

[Boris Derzhavets]

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

Could you try opensuse 11.3 ?  I was experiencing VNC console issues vs RH's guests
going through install just fine.  11.3 didn't allow me "nographics" mode.

Boris.

--- On Tue, 7/20/10, Pasi Kärkkäinen <pasik@iki.fi> wrote:

From: Pasi Kärkkäinen <pasik@iki.fi>
Subject: Re: [Xen-devel] New release candidate for Xen 4.0.1
To: "Keir Fraser" <keir.fraser@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Date: Tuesday, July 20, 2010, 7:57 AM

On Fri, Jul 16, 2010 at 02:54:55PM +0100, Keir Fraser wrote:
> On 16/07/2010 14:28, "Pasi Kärkkäinen" <pasik@iki.fi> wrote:
> 
> > On Fri, Jul 16, 2010 at 02:05:03PM +0100, Keir Fraser wrote:
> >> Tag '4.0.1-rc4' is now avaiable at http://xenbits.xen.org/xen-unstable.hg.
> >> Please test!
> >> 
> > 
> > I assume in http://xenbits.xen.org/xen-4.0-testing.hg instead :)
> 
> Oh yes, indeed!
> 

I just installed 4.0.1-rc4, and it built/installed/worked smoothly.
I used the latest 2.6.32.16 pvops dom0 kernel.

I was testing various Fedora 13 and CentOS 5.5 PV guests.

-- Pasi


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



      

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

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

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

[PATCH] Re: New release candidate for Xen 4.0.1

[M A Young]

I have a minor fix for this. BASH_COMPLETION_DIR is used uninitialized in 
tools/libxl/Makefile which means that xl.sh can end up in / which is 
not ideal. The patch below sets a sensible default for this variable.

Signed-off-by: Michael Young <m.a.young@durham.ac.uk>

--- xen-4.0.1/tools/libxl/Makefile.orig	2010-07-16 18:27:14.000000000 +0100
+++ xen-4.0.1/tools/libxl/Makefile	2010-07-16 19:39:46.000000000 +0100
@@ -4,6 +4,7 @@

  XEN_ROOT = ../..
  include $(XEN_ROOT)/tools/Rules.mk
+BASH_COMPLETION_DIR ?= /etc/bash_completion.d/

  MAJOR = 1.0
  MINOR = 0

Re: [PATCH] Re: New release candidate for Xen 4.0.1

[Pasi Kärkkäinen]

On Fri, Jul 16, 2010 at 08:29:09PM +0100, M A Young wrote:
> I have a minor fix for this. BASH_COMPLETION_DIR is used uninitialized in 
> tools/libxl/Makefile which means that xl.sh can end up in / which is not 
> ideal. The patch below sets a sensible default for this variable.
>

Yeah, I noticed this problem aswell. This patch should go into xen-4.0-testing.hg.

-- Pasi

> Signed-off-by: Michael Young <m.a.young@durham.ac.uk>
>
> --- xen-4.0.1/tools/libxl/Makefile.orig	2010-07-16 18:27:14.000000000 +0100
> +++ xen-4.0.1/tools/libxl/Makefile	2010-07-16 19:39:46.000000000 +0100
> @@ -4,6 +4,7 @@
>
>  XEN_ROOT = ../..
>  include $(XEN_ROOT)/tools/Rules.mk
> +BASH_COMPLETION_DIR ?= /etc/bash_completion.d/
>
>  MAJOR = 1.0
>  MINOR = 0
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

Re: [PATCH] Re: New release candidate for Xen 4.0.1

[Keir Fraser]

On 20/07/2010 13:01, "Pasi Kärkkäinen" <pasik@iki.fi> wrote:

> On Fri, Jul 16, 2010 at 08:29:09PM +0100, M A Young wrote:
>> I have a minor fix for this. BASH_COMPLETION_DIR is used uninitialized in
>> tools/libxl/Makefile which means that xl.sh can end up in / which is not
>> ideal. The patch below sets a sensible default for this variable.
>> 
> 
> Yeah, I noticed this problem aswell. This patch should go into
> xen-4.0-testing.hg.

I am not the person to Cc on toolstack patches. Ian and Stefano and
responsible for applying tools patches to xen-unstable and backporting to
stable branches.

 -- Keir

[PATCH] Re: New release candidate for Xen 4.0.1

[M A Young]

I have a minor fix for this. BASH_COMPLETION_DIR is used uninitialized in 
tools/libxl/Makefile which means that xl.sh can end up in / which is not ideal. 
The patch below sets a sensible default for this variable.

Signed-off-by: Michael Young <m.a.young@durham.ac.uk>

--- xen-4.0.1/tools/libxl/Makefile.orig	2010-07-16 18:27:14.000000000 +0100
+++ xen-4.0.1/tools/libxl/Makefile	2010-07-16 19:39:46.000000000 +0100
@@ -4,6 +4,7 @@

  XEN_ROOT = ../..
  include $(XEN_ROOT)/tools/Rules.mk
+BASH_COMPLETION_DIR ?= /etc/bash_completion.d/

  MAJOR = 1.0
  MINOR = 0

Re: [PATCH] Re: New release candidate for Xen 4.0.1

[Keir Fraser]

Shouldn't this be in xen-unstable first, and then backported in the usual
way?

 K.

On 20/07/2010 19:01, "M A Young" <m.a.young@durham.ac.uk> wrote:

> I have a minor fix for this. BASH_COMPLETION_DIR is used uninitialized in
> tools/libxl/Makefile which means that xl.sh can end up in / which is not
> ideal. 
> The patch below sets a sensible default for this variable.
> 
> Signed-off-by: Michael Young <m.a.young@durham.ac.uk>
> 
> --- xen-4.0.1/tools/libxl/Makefile.orig 2010-07-16 18:27:14.000000000 +0100
> +++ xen-4.0.1/tools/libxl/Makefile 2010-07-16 19:39:46.000000000 +0100
> @@ -4,6 +4,7 @@
> 
>   XEN_ROOT = ../..
>   include $(XEN_ROOT)/tools/Rules.mk
> +BASH_COMPLETION_DIR ?= /etc/bash_completion.d/
> 
>   MAJOR = 1.0
>   MINOR = 0
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

Re: [PATCH] Re: New release candidate for Xen 4.0.1

[M A Young]

On Tue, 20 Jul 2010, Keir Fraser wrote:

> Shouldn't this be in xen-unstable first, and then backported in the usual
> way?

If that is the normal process then yes. I haven't checked whether this 
bug exists in xen-unstable, but a quick glance at the Makefile I am 
patching suggests that it probably does.

 	Michael Young

Re: [PATCH] Re: New release candidate for Xen 4.0.1

[Keir Fraser]

On 21/07/2010 10:42, "M A Young" <m.a.young@durham.ac.uk> wrote:

> On Tue, 20 Jul 2010, Keir Fraser wrote:
> 
>> Shouldn't this be in xen-unstable first, and then backported in the usual
>> way?
> 
> If that is the normal process then yes. I haven't checked whether this
> bug exists in xen-unstable, but a quick glance at the Makefile I am
> patching suggests that it probably does.

The precise process for toolset patches now is that they get applied to
http://xenbits.xen.org/staging/xen-unstable-tools.hg by Ian Jackson or
Stefano Stabellini. I merge that tree into main xen-unstable.hg nearly every
day. Then, for 4.0.x and 3.4.x stable branches, Ian and Stefano nominate
patches for backport from xen-unstable.

 -- Keir

> Michael Young

RE: [PATCH] Re: New release candidate for Xen 4.0.1

[Dan Magenheimer]

One result of this process is that it makes it difficult
to see changes via the xen-changelog mailing list as
the pull by Keir into xen-unstable just shows up as
a Merge, without any of the changeset title or log detail.
Any way to fix this?  If necessary, by adding the
staging/xen-unstable-tools.hg tree to the changelog
mailing list?

> -----Original Message-----
> From: Keir Fraser [mailto:keir.fraser@eu.citrix.com]
> Sent: Wednesday, July 21, 2010 4:23 AM
> To: M A Young
> Cc: Ian Campbell; xen-devel@lists.xensource.com; Stefano Stabellini
> Subject: Re: [PATCH] Re: [Xen-devel] New release candidate for Xen
> 4.0.1
> 
> On 21/07/2010 10:42, "M A Young" <m.a.young@durham.ac.uk> wrote:
> 
> > On Tue, 20 Jul 2010, Keir Fraser wrote:
> >
> >> Shouldn't this be in xen-unstable first, and then backported in the
> usual
> >> way?
> >
> > If that is the normal process then yes. I haven't checked whether
> this
> > bug exists in xen-unstable, but a quick glance at the Makefile I am
> > patching suggests that it probably does.
> 
> The precise process for toolset patches now is that they get applied to
> http://xenbits.xen.org/staging/xen-unstable-tools.hg by Ian Jackson or
> Stefano Stabellini. I merge that tree into main xen-unstable.hg nearly
> every
> day. Then, for 4.0.x and 3.4.x stable branches, Ian and Stefano
> nominate
> patches for backport from xen-unstable.
> 
>  -- Keir
> 
> > Michael Young
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

Re: [PATCH] Re: New release candidate for Xen 4.0.1

[Keir Fraser]

Er, no. There's still one email per changeset. You can ignore the merge
changesets: they're all trivial auto merges, and I'm not sure why they end
up with an associated diff, it must be how mercurial consolidates and merges
a branch.

 -- Keir

On 21/07/2010 17:30, "Dan Magenheimer" <dan.magenheimer@oracle.com> wrote:

> One result of this process is that it makes it difficult
> to see changes via the xen-changelog mailing list as
> the pull by Keir into xen-unstable just shows up as
> a Merge, without any of the changeset title or log detail.
> Any way to fix this?  If necessary, by adding the
> staging/xen-unstable-tools.hg tree to the changelog
> mailing list?
> 
>> -----Original Message-----
>> From: Keir Fraser [mailto:keir.fraser@eu.citrix.com]
>> Sent: Wednesday, July 21, 2010 4:23 AM
>> To: M A Young
>> Cc: Ian Campbell; xen-devel@lists.xensource.com; Stefano Stabellini
>> Subject: Re: [PATCH] Re: [Xen-devel] New release candidate for Xen
>> 4.0.1
>> 
>> On 21/07/2010 10:42, "M A Young" <m.a.young@durham.ac.uk> wrote:
>> 
>>> On Tue, 20 Jul 2010, Keir Fraser wrote:
>>> 
>>>> Shouldn't this be in xen-unstable first, and then backported in the
>> usual
>>>> way?
>>> 
>>> If that is the normal process then yes. I haven't checked whether
>> this
>>> bug exists in xen-unstable, but a quick glance at the Makefile I am
>>> patching suggests that it probably does.
>> 
>> The precise process for toolset patches now is that they get applied to
>> http://xenbits.xen.org/staging/xen-unstable-tools.hg by Ian Jackson or
>> Stefano Stabellini. I merge that tree into main xen-unstable.hg nearly
>> every
>> day. Then, for 4.0.x and 3.4.x stable branches, Ian and Stefano
>> nominate
>> patches for backport from xen-unstable.
>> 
>>  -- Keir
>> 
>>> Michael Young
>> 
>> 
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel

Re: [PATCH] Re: New release candidate for Xen 4.0.1

[Ian Jackson]

Keir Fraser writes ("Re: [PATCH] Re: [Xen-devel] New release candidate for Xen 4.0.1"):
> Er, no. There's still one email per changeset. You can ignore the merge
> changesets: they're all trivial auto merges, and I'm not sure why they end
> up with an associated diff, it must be how mercurial consolidates and merges
> a branch.

Right.

We could add the separate tools tree to the patchbot but it would
result in every tools patch being mailed out twice.

Ian.

Re: [PATCH] Re: New release candidate for Xen 4.0.1

[Stefano Stabellini]

On Tue, 20 Jul 2010, M A Young wrote:
> I have a minor fix for this. BASH_COMPLETION_DIR is used uninitialized in 
> tools/libxl/Makefile which means that xl.sh can end up in / which is not ideal. 
> The patch below sets a sensible default for this variable.
> 
> Signed-off-by: Michael Young <m.a.young@durham.ac.uk>
> 
> --- xen-4.0.1/tools/libxl/Makefile.orig	2010-07-16 18:27:14.000000000 +0100
> +++ xen-4.0.1/tools/libxl/Makefile	2010-07-16 19:39:46.000000000 +0100
> @@ -4,6 +4,7 @@
> 
>   XEN_ROOT = ../..
>   include $(XEN_ROOT)/tools/Rules.mk
> +BASH_COMPLETION_DIR ?= /etc/bash_completion.d/
> 
>   MAJOR = 1.0
>   MINOR = 0
> 

I would rather backport this to xen4.0:


# HG changeset patch
# User Keir Fraser <keir.fraser@citrix.com>
# Date 1276064492 -3600
# Node ID 0c10e80e083b115313bfc213e7683f4fc3f761bc
# Parent  87fe942a90b1d96b5e378fa5b221fd8eeba439da
tools: fix install bash-completion files to non-default locations.

Signed-off-by: Christoph Egger <Christoph.Egger@amd.com>

diff -r 87fe942a90b1 -r 0c10e80e083b Config.mk
--- a/Config.mk	Wed Jun 09 07:18:30 2010 +0100
+++ b/Config.mk	Wed Jun 09 07:21:32 2010 +0100
@@ -29,7 +29,7 @@ include $(XEN_ROOT)/config/$(XEN_TARGET_
 SHAREDIR    ?= $(PREFIX)/share
 DOCDIR      ?= $(SHAREDIR)/doc/xen
 MANDIR      ?= $(SHAREDIR)/man
-BASH_COMPLETION_DIR ?= /etc/bash_completion.d
+BASH_COMPLETION_DIR ?= $(CONFIG_DIR)/bash_completion.d
 
 ifneq ($(EXTRA_PREFIX),)
 EXTRA_INCLUDES += $(EXTRA_PREFIX)/include

Re: [PATCH] Re: New release candidate for Xen 4.0.1

[M A Young]

On Wed, 21 Jul 2010, Stefano Stabellini wrote:

> I would rather backport this to xen4.0:
>
>
> # HG changeset patch
> # User Keir Fraser <keir.fraser@citrix.com>
> # Date 1276064492 -3600
> # Node ID 0c10e80e083b115313bfc213e7683f4fc3f761bc
> # Parent  87fe942a90b1d96b5e378fa5b221fd8eeba439da
> tools: fix install bash-completion files to non-default locations.
>
> Signed-off-by: Christoph Egger <Christoph.Egger@amd.com>
>
> diff -r 87fe942a90b1 -r 0c10e80e083b Config.mk
> --- a/Config.mk	Wed Jun 09 07:18:30 2010 +0100
> +++ b/Config.mk	Wed Jun 09 07:21:32 2010 +0100
> @@ -29,7 +29,7 @@ include $(XEN_ROOT)/config/$(XEN_TARGET_
> SHAREDIR    ?= $(PREFIX)/share
> DOCDIR      ?= $(SHAREDIR)/doc/xen
> MANDIR      ?= $(SHAREDIR)/man
> -BASH_COMPLETION_DIR ?= /etc/bash_completion.d
> +BASH_COMPLETION_DIR ?= $(CONFIG_DIR)/bash_completion.d
>
> ifneq ($(EXTRA_PREFIX),)
> EXTRA_INCLUDES += $(EXTRA_PREFIX)/include
>

Adding that line at that place looks reasonable, though that patch won't 
work because there isn't currently a BASH_COMPLETION_DIR line in 
Config.mk, hence the original bug. It looks like the selective backport
http://xenbits.xensource.com/xen-4.0-testing.hg?rev/b1321a50f626
of xl stuff missed this.

 	Michael Young

Re: [PATCH] Re: New release candidate for Xen 4.0.1

[Stefano Stabellini]

On Wed, 21 Jul 2010, M A Young wrote:
> On Wed, 21 Jul 2010, Stefano Stabellini wrote:
> 
> > I would rather backport this to xen4.0:
> >
> >
> > # HG changeset patch
> > # User Keir Fraser <keir.fraser@citrix.com>
> > # Date 1276064492 -3600
> > # Node ID 0c10e80e083b115313bfc213e7683f4fc3f761bc
> > # Parent  87fe942a90b1d96b5e378fa5b221fd8eeba439da
> > tools: fix install bash-completion files to non-default locations.
> >
> > Signed-off-by: Christoph Egger <Christoph.Egger@amd.com>
> >
> > diff -r 87fe942a90b1 -r 0c10e80e083b Config.mk
> > --- a/Config.mk	Wed Jun 09 07:18:30 2010 +0100
> > +++ b/Config.mk	Wed Jun 09 07:21:32 2010 +0100
> > @@ -29,7 +29,7 @@ include $(XEN_ROOT)/config/$(XEN_TARGET_
> > SHAREDIR    ?= $(PREFIX)/share
> > DOCDIR      ?= $(SHAREDIR)/doc/xen
> > MANDIR      ?= $(SHAREDIR)/man
> > -BASH_COMPLETION_DIR ?= /etc/bash_completion.d
> > +BASH_COMPLETION_DIR ?= $(CONFIG_DIR)/bash_completion.d
> >
> > ifneq ($(EXTRA_PREFIX),)
> > EXTRA_INCLUDES += $(EXTRA_PREFIX)/include
> >
> 
> Adding that line at that place looks reasonable, though that patch won't 
> work because there isn't currently a BASH_COMPLETION_DIR line in 
> Config.mk, hence the original bug. It looks like the selective backport
> http://xenbits.xensource.com/xen-4.0-testing.hg?rev/b1321a50f626
> of xl stuff missed this.
 
Indeed.
Thanks for pointing out this bug.

Re: [PATCH] Re: New release candidate for Xen 4.0.1

[Keir Fraser]

On 21/07/2010 13:14, "Stefano Stabellini" <Stefano.Stabellini@eu.citrix.com>
wrote:

>> Adding that line at that place looks reasonable, though that patch won't
>> work because there isn't currently a BASH_COMPLETION_DIR line in
>> Config.mk, hence the original bug. It looks like the selective backport
>> http://xenbits.xensource.com/xen-4.0-testing.hg?rev/b1321a50f626
>> of xl stuff missed this.
>  
> Indeed.
> Thanks for pointing out this bug.

Yeah, I think we need to net effect of xen-unstable changesets 21253, 21517
and 21565 on Config.mk. I can sort that out easy enough, it's still
basically a one liner.

 -- Keir