[ANNOUNCE] Xen 3.0.4 release candidate 2

[ANNOUNCE] Xen 3.0.4 release candidate 2

[Keir Fraser]

Folks,

A second release candidate for Xen 3.0.4 is now available at
http://xenbits.xensource.com/xen-3.0.4-testing.hg.

This release candidate contains many fixes since -rc1:
 * Latest changesets from PPC and IA64 development trees
 * Several HVM bug fixes
 * Tools enhancements and bug fixes

RC2 is a serious candidate for final release, so please test and let us know
if we have more bugs to fix!

 -- Keir

Re: [ANNOUNCE] Xen 3.0.4 release candidate 2

[Daniel P. Berrange]

On Fri, Dec 15, 2006 at 02:28:55PM +0000, Keir Fraser wrote:
> Folks,
> 
> A second release candidate for Xen 3.0.4 is now available at
> http://xenbits.xensource.com/xen-3.0.4-testing.hg.
> 
> This release candidate contains many fixes since -rc1:
>  * Latest changesets from PPC and IA64 development trees
>  * Several HVM bug fixes
>  * Tools enhancements and bug fixes
> 
> RC2 is a serious candidate for final release, so please test and let us know
> if we have more bugs to fix!

Only two issues that I'm aware of wrt to userspace stack

Markus posted a patch to fix mouse button mappings in the paravirt VNC
driver - without it  middle & right mouse buttons are inverted which I
think is pretty important to fix.

http://lists.xensource.com/archives/html/xen-devel/2006-12/msg00534.html

Also on subject of VNC, the vncpassword auth patches for paravirt framebuffer
have not yet been merged. Since 3.0.4 fixed the HVM VNC server to be secure
it would be pity to release new PV FB without same level of security.

http://lists.xensource.com/archives/html/xen-devel/2006-12/msg00176.html

Regards,
Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

Re: [ANNOUNCE] Xen 3.0.4 release candidate 2

[Magnus Damm]

On 12/15/06, Keir Fraser <keir@xensource.com> wrote:
> Folks,
>
> A second release candidate for Xen 3.0.4 is now available at
> http://xenbits.xensource.com/xen-3.0.4-testing.hg.
>
> This release candidate contains many fixes since -rc1:
>  * Latest changesets from PPC and IA64 development trees
>  * Several HVM bug fixes
>  * Tools enhancements and bug fixes
>
> RC2 is a serious candidate for final release, so please test and let us know
> if we have more bugs to fix!

The ELF notes for kexec / kdump are screwed up on x86_64.

$ readelf -a vmcore-3.0.4-rc2-x86_64
[snip]
Notes at offset 0x00000120 with length 0x000002c8:
  Owner         Data size       Description
  CORE          0x00000150      NT_PRSTATUS (prstatus structure)
  CORE          0x00000150      NT_PRSTATUS (prstatus structure)

$ readelf -a vmcore-3.0.4-rc1-x86_64
[snip]
Notes at offset 0x00000120 with length 0x00000380:
  Owner         Data size       Description
  CORE          0x00000150      NT_PRSTATUS (prstatus structure)
  Xen           0x00000020      Unknown note type: (0x01000002)
  CORE          0x00000150      NT_PRSTATUS (prstatus structure)
  Xen           0x00000020      Unknown note type: (0x01000002)
  Xen           0x00000048      Unknown note type: (0x01000001)

x86_32 seems to work as expected though.

/ magnus

Re: [ANNOUNCE] Xen 3.0.4 release candidate 2

[Ian Campbell]

On Mon, 2006-12-18 at 21:48 +0900, Magnus Damm wrote:
> The ELF notes for kexec / kdump are screwed up on x86_64.

That was due to 12977:af39d20b2b728941421ef18e5c5b1012852eec80[0] which
I have now reverted. The reversion will be
13080:4ef0dbe95eac33033abeee36a8f13eaaeb9d5639 once it comes through
regression testing.

Hollis, what was the warning the change was introduced to avoid? If you
have any ideas for another workaround for them in the 3.0.4 release we'd
be grateful to hear it ASAP -- Keir plans to roll the final RC in the
next 24 hours.

Cheers,
Ian.

[0] http://xenbits2.xensource.com/xen-unstable.hg?cs=12977

> $ readelf -a vmcore-3.0.4-rc2-x86_64
> [snip]
> Notes at offset 0x00000120 with length 0x000002c8:
>   Owner         Data size       Description
>   CORE          0x00000150      NT_PRSTATUS (prstatus structure)
>   CORE          0x00000150      NT_PRSTATUS (prstatus structure)
> 
> $ readelf -a vmcore-3.0.4-rc1-x86_64
> [snip]
> Notes at offset 0x00000120 with length 0x00000380:
>   Owner         Data size       Description
>   CORE          0x00000150      NT_PRSTATUS (prstatus structure)
>   Xen           0x00000020      Unknown note type: (0x01000002)
>   CORE          0x00000150      NT_PRSTATUS (prstatus structure)
>   Xen           0x00000020      Unknown note type: (0x01000002)
>   Xen           0x00000048      Unknown note type: (0x01000001)
> 
> x86_32 seems to work as expected though.
> 
> / magnus

Re: [ANNOUNCE] Xen 3.0.4 release candidate 2

[Ian Campbell]

On Mon, 2006-12-18 at 16:31 +0000, Ian Campbell wrote:
> Hollis, what was the warning the change was introduced to avoid? If you
> have any ideas for another workaround for them in the 3.0.4 release we'd
> be grateful to hear it ASAP -- Keir plans to roll the final RC in the
> next 24 hours.

I see now that powerpc uses -Wpacked. Is it OK to drop that?

Ian.

Re: [ANNOUNCE] Xen 3.0.4 release candidate 2

[Keir Fraser]

On 18/12/06 16:41, "Ian Campbell" <Ian.Campbell@XenSource.com> wrote:

> On Mon, 2006-12-18 at 16:31 +0000, Ian Campbell wrote:
>> Hollis, what was the warning the change was introduced to avoid? If you
>> have any ideas for another workaround for them in the 3.0.4 release we'd
>> be grateful to hear it ASAP -- Keir plans to roll the final RC in the
>> next 24 hours.
> 
> I see now that powerpc uses -Wpacked. Is it OK to drop that?

My default action will be to remove -Wpacked just in the 3.0.4 stable branch
(so it'll remain in xen-unstable) and then work out a better long-term fix.

 -- Keir

Re: [ANNOUNCE] Xen 3.0.4 release candidate 2

[Magnus Damm]

On 12/19/06, Ian Campbell <Ian.Campbell@xensource.com> wrote:
> On Mon, 2006-12-18 at 21:48 +0900, Magnus Damm wrote:
> > The ELF notes for kexec / kdump are screwed up on x86_64.
>
> That was due to 12977:af39d20b2b728941421ef18e5c5b1012852eec80[0] which
> I have now reverted. The reversion will be
> 13080:4ef0dbe95eac33033abeee36a8f13eaaeb9d5639 once it comes through
> regression testing.

.. and this commit will eventually end up in xen-3.0.4-testing.hg?

FYI: The ELF note code in 3.0.4-rc3 is still most likely broken on x86_64.

Can you please make sure the fix gets included in next release
candidate so I can run my tests?

/ magnus

Re: [ANNOUNCE] Xen 3.0.4 release candidate 2

[Hollis Blanchard]

I didn't pay much attention to the lengthy "packed" discussions of the
past. From a quick Google, it looks like the issues are that packed
doesn't work on Plan 9, and compounds an already bad situation on
PowerPC when Xen requires us to fake 16-bit atomic accesses.

-- 
Hollis Blanchard
IBM Linux Technology Center

On Mon, 2006-12-18 at 16:31 +0000, Ian Campbell wrote:
> On Mon, 2006-12-18 at 21:48 +0900, Magnus Damm wrote:
> > The ELF notes for kexec / kdump are screwed up on x86_64.
> 
> That was due to 12977:af39d20b2b728941421ef18e5c5b1012852eec80[0] which
> I have now reverted. The reversion will be
> 13080:4ef0dbe95eac33033abeee36a8f13eaaeb9d5639 once it comes through
> regression testing.
> 
> Hollis, what was the warning the change was introduced to avoid? If you
> have any ideas for another workaround for them in the 3.0.4 release we'd
> be grateful to hear it ASAP -- Keir plans to roll the final RC in the
> next 24 hours.
> 
> Cheers,
> Ian.
> 
> [0] http://xenbits2.xensource.com/xen-unstable.hg?cs=12977
> 
> > $ readelf -a vmcore-3.0.4-rc2-x86_64
> > [snip]
> > Notes at offset 0x00000120 with length 0x000002c8:
> >   Owner         Data size       Description
> >   CORE          0x00000150      NT_PRSTATUS (prstatus structure)
> >   CORE          0x00000150      NT_PRSTATUS (prstatus structure)
> >
> > $ readelf -a vmcore-3.0.4-rc1-x86_64
> > [snip]
> > Notes at offset 0x00000120 with length 0x00000380:
> >   Owner         Data size       Description
> >   CORE          0x00000150      NT_PRSTATUS (prstatus structure)
> >   Xen           0x00000020      Unknown note type: (0x01000002)
> >   CORE          0x00000150      NT_PRSTATUS (prstatus structure)
> >   Xen           0x00000020      Unknown note type: (0x01000002)
> >   Xen           0x00000048      Unknown note type: (0x01000001)
> >
> > x86_32 seems to work as expected though.
> >
> > / magnus