I am pleased to announce the release of Xen 4.6.1. Xen Project Maintenance releases are released in line with our Maintenance Release Policy: this means we make one new point release per stable series every 4 months, which include back-ports of bug-fixes and security issues.
I am pleased to announce the release of Xen 4.6.1. This is available immediately from its git repository
or from the XenProject download page
(where a list of changes can also be found).
Note that, as also mentioned on the web page above, due to two oversights the fixes for both XSA-155 and XSA-162 have only been partially applied to this release. (Note further that the same applies to the recently announced 4.4.4 release.)
We recommend all users of the 4.6 stable series to update to this first point release.
Additional note published Feb 17th: We detected the missing patches before the official release, but towards the end of the release process. We then had a discussion whether to make a new release which would have forced us to skip a release number (aka move from 4.6.0 to 22.214.171.124 or 4.6.2) or release 4.6.1 with two security patches which were incomplete, and document what is missing. At this point, we had to decide whether to re-tag (and thus re-number the release) or whether to document any issues. A similar issue happened in 2013, when we released Xen 126.96.36.199 instead of Xen 4.1.6. At that time it became clear that many consumers of Xen have difficulties with a version number that does not fit into the normal version numbering pattern, which led to Xen 188.8.131.52 not being widely used. We cannot re-spin a release without changing the version number if issues are discovered late during the release process. Firstly, making a release involves both extensive testing and also has a security dimension. Normally, after testing succeeds we create a signed tag in the git tree. This means that there is a secure way of accounting for where the tarball came from. We then rebuild and do additional testing, write the release notes, do some more checking and sign the tarballs. The missing patches were discovered on Thursday, before the official release on Monday, but after we created the signed tag. Signed tags cannot be removed, as they have to be tamper proof, which makes everyone more secure.
Next week, the Xen,.org community is hosting a booth in the Citrix Synergy Exhibit Hall as part of my 2010 marketing plan for the Xen.org community and our technologies. This 4 day event (May 11 – 14) provides the Xen.org community with a chance to meet Fortune 500 customers of Citrix as well as their global community of resellers and smaller customers who are actively engaging in the virtualization marketplace.
In an effort to demonstrate the power of Xen.org technologies, I have invited both Zenoss and VMops (now Cloud.com) to join in the Xen.org booth to present their enterprise management and cloud hosting technologies based on open source Xen. Together, we can show the unique ability of our technology as a foundation in providing critical enterprise solutions for small to large companies as well as the cloud. Joining me in the Xen.org booth will also be Jeremy Fitzhardinge who offers substantial developer knowledge on Xen technology thereby ensuring that no question asked is left unanswered at our booth.
If you are in the San Francisco area next week, why not attend Citrix Synergy and visit the Xen.org booth.
Simon Crosby, CTO of Citrix Virtualization Division and I did an interview with Linux Magazine Brazil. The final article is at http://linuxmagazine.uol.com.br/images/uploads/pdf_aberto/LM_52_24_27_04_corp_citrix.pdf. The article is in Portuguese but translates fairly well with online tools.
Citrix Project Satori is the result of a collaborative agreement between XenSource and Microsoft, and was carried forward after XenSource was acquired by Citrix Systems. The base Satori components are released by Microsoft as the Linux Integration Components for Hyper-V, and provide support for paravirtualized XenLinux guests running on Hyper-V. The Linux Integration Components can be downloaded here.
The complete source code and license information (GPL version 2) on this project is now availalbe at http://www.xen.org/download/satori.html.
Hey, you! Yes, you. Did you register for Xen Summit at Oracle yet? All you have to do is click here. That’s all there is too it. Pretty simple.
What? You want to know who is speaking first? Ok, here are some speakers confirmed (expect full agenda to be released next week):
- Ian Pratt, Founder and Project Leader of Xen.org
- Kier Fraser, Xen Project Status Update
- Dan Magenheimer, Oracle Xen guru
- Jeremy Fitzhardinge, PVOPS Xen master (includes a demo!)
- Eddie Dong, Status of SR-IOV from Intel
- Ben Serebrin, Cross-vendor migration from AMD
Also more presentations from Intel, Fujitsu, Oracle, HP, Rice University, Neoclues, University of Madrid, Cambridge University, and others…
All that for only $215 including a great Xen Summit jacket, evening out at the Computer History Museum, and the chance to mingle with your fellow Xen Community members.
Oh, in that case, I better register right now.
It’s been a year since Citrix bought XenSource, the company created by the founders of the Xen open-source hypervisor, and integrated the business into its lineup of products delivering applications to desktops.
As part of the process, Citrix made the XenServer virtualization software central to its strategy, and appointed XenSource staff to senior executive positions.
ZDNet UK sat down with one of those executives, Ian Pratt, Citrix’s vice president for special products, to find out how the integration is going and where Citrix is going with Xen-branded products.