Xen 4.6 released

Xen 4.6 released

[Wei Liu]

Hi all

I'm pleased to announce that Xen 4.6 is released. As release manager I
would like to thank everyone who involved in the making of 4.6 release
(either in the form of patch, bug report or packaging effort). This
release wouldn't have happened without all your contributions.

You can check out 4.6 release from xen.git with the tag "RELEASE-4.6.0".

Tarball can be obtained from:

  http://bits.xensource.com/oss-xen/release/4.6.0/xen-4.6.0.tar.gz

Signature for tarball:

  http://bits.xensource.com/oss-xen/release/4.6.0/xen-4.6.0.tar.gz.sig

Note that this is xen-devel@ only announcement. Official release
announcement on xen-announce@, press release, blog post and various
other docs / web pages will be available next week on October 13. The
official download link may also be different from the one provided
above.


Wei.

Re: Xen 4.6 released

[Konrad Rzeszutek Wilk]

On Wed, Oct 07, 2015 at 12:16:10PM +0100, Wei Liu wrote:
> Hi all
> 
> I'm pleased to announce that Xen 4.6 is released. As release manager I
> would like to thank everyone who involved in the making of 4.6 release
> (either in the form of patch, bug report or packaging effort). This
> release wouldn't have happened without all your contributions.

And you steering it along! Thank you!
> 
> You can check out 4.6 release from xen.git with the tag "RELEASE-4.6.0".
> 
> Tarball can be obtained from:
> 
>   http://bits.xensource.com/oss-xen/release/4.6.0/xen-4.6.0.tar.gz
> 
> Signature for tarball:
> 
>   http://bits.xensource.com/oss-xen/release/4.6.0/xen-4.6.0.tar.gz.sig
> 
> Note that this is xen-devel@ only announcement. Official release
> announcement on xen-announce@, press release, blog post and various
> other docs / web pages will be available next week on October 13. The
> official download link may also be different from the one provided
> above.
> 
> 
> Wei.
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

Re: Xen 4.6 released

[Lars Kurth]

On 07/10/2015 14:04, "Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>
wrote:

>On Wed, Oct 07, 2015 at 12:16:10PM +0100, Wei Liu wrote:
>> Hi all
>> 
>> I'm pleased to announce that Xen 4.6 is released. As release manager I
>> would like to thank everyone who involved in the making of 4.6 release
>> (either in the form of patch, bug report or packaging effort). This
>> release wouldn't have happened without all your contributions.
>
>And you steering it along! Thank you!
Well done everyone and Wei in particular. Thank you for putting in the
effort.
Lars

Re: Xen 4.6 released

[Chen, Tiejun]

On 10/7/2015 7:16 PM, Wei Liu wrote:
> Hi all
>
> I'm pleased to announce that Xen 4.6 is released. As release manager I
> would like to thank everyone who involved in the making of 4.6 release
> (either in the form of patch, bug report or packaging effort). This
> release wouldn't have happened without all your contributions.
>
> You can check out 4.6 release from xen.git with the tag "RELEASE-4.6.0".
>
> Tarball can be obtained from:
>
>    http://bits.xensource.com/oss-xen/release/4.6.0/xen-4.6.0.tar.gz

Wei and Ian,

Could we merge these following commits into xen-4.6.1?

commit 83215fba3a80c30b5191a4a1086dc510cca43069

     libxl: introduce libxl__is_igd_vga_passthru

commit 488508b49a65dda20cf6eb6d8f549e8d758e610f

     libxl: introduce gfx_passthru_kind

Currently they're already in staging branch.

I know we're going to sync qemu-upstream into qemu-xen in xen 4.7 to 
support IGD passthrough with qemu-xen. But actually only these two 
commits can make sure xen-4.6.x work out IGD passthrough with 
qemu-upstream, instead of qemu-xen. I mean we can set something like this,

device_model_version="qemu-xen"
device_model_override="/<path to qemu-upstream>/qemu-system-i386"

Thanks
Tiejun

>
> Signature for tarball:
>
>    http://bits.xensource.com/oss-xen/release/4.6.0/xen-4.6.0.tar.gz.sig
>
> Note that this is xen-devel@ only announcement. Official release
> announcement on xen-announce@, press release, blog post and various
> other docs / web pages will be available next week on October 13. The
> official download link may also be different from the one provided
> above.
>
>
> Wei.
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>

Re: Xen 4.6 released

[Jan Beulich]

>>> On 15.10.15 at 02:59, <tiejun.chen@intel.com> wrote:
> Wei and Ian,
> 
> Could we merge these following commits into xen-4.6.1?

Please don't hijack other threads for backport requests, and please
see ./MAINTAINERS of the respective branch for who to send such
to.

> commit 83215fba3a80c30b5191a4a1086dc510cca43069
> 
>      libxl: introduce libxl__is_igd_vga_passthru
> 
> commit 488508b49a65dda20cf6eb6d8f549e8d758e610f
> 
>      libxl: introduce gfx_passthru_kind
> 
> Currently they're already in staging branch.
> 
> I know we're going to sync qemu-upstream into qemu-xen in xen 4.7 to 
> support IGD passthrough with qemu-xen. But actually only these two 
> commits can make sure xen-4.6.x work out IGD passthrough with 
> qemu-upstream, instead of qemu-xen. I mean we can set something like this,
> 
> device_model_version="qemu-xen"
> device_model_override="/<path to qemu-upstream>/qemu-system-i386"

All of this sounds more like a feature than a bug fix, which normally
we wouldn't put into stable releases. Occasionally we make
exceptions in x.y.1 releases, but I don't see this justified here so
far.

Jan

Re: Xen 4.6 released

[Lars Kurth]

Tiejun,

On 15/10/2015 08:32, "Jan Beulich" <JBeulich@suse.com> wrote:

>>>> On 15.10.15 at 02:59, <tiejun.chen@intel.com> wrote:
>> Wei and Ian,
>> 
>> Could we merge these following commits into xen-4.6.1?
>
>Please don't hijack other threads for backport requests, and please
>see ./MAINTAINERS of the respective branch for who to send such
>to.

I wanted to explain why hijacking threads is bad practice. In this
example, you would normally start a new mail along the lines of "Please
backport XYZ to ABC" and if somebody needed to check why a specific bug
fix was back ported in for example 2 yeaqrs, such a mail will be easier to
find. Also of course there is the risk that the right people won't read
your mail if you hijack a thread.

Regards
Lars