nyuuzyou/wikis huggingface dataset:
Xen Project 4.8 Release Notes

= Overview =
Xen Project 4.8.0 was released on 2016 Dec 5.
Xen Project 4.8.0 is the work of 5.3 months of development, with 1245 changesets.
Also see Xen Project 4.8 Acknowledgements
= New Feature Highlights =
The list of new features can be found on the following page: Xen Project 4.8 Feature List
You can also see an evolution of features on Xen Project Release Features
Documentation is available on Xen Project 4.8 Man Pages
= Build Requirements =
The default installation prefix has been changed to /usr/local. Previously the default installation prefix was /usr To restore the previous behaviour, specify --prefix=/usr when running ./configure, e.g.:
 $ ./configure --prefix=/usr
If you choose to accept the new default then be sure to cleanup any residual bits of the old installation in the old prefix, especially libraries and tools which you might pick up by mistake.
Due to this change it may also now be necessary to run /sbin/ldconfig as root after installing Xen.
Note also that Xen now requires gcc v4.1 or greater.
= Build =
First of all you will have to get the Xen 4.8 source code, which you can either download through our release tarball (including signature) from our download page. Alternatively, you can get the source in the following way:
* With a recent enough git (>= 1.7.8.2) just pull from the proper tag (RELEASE-4.8.0) from the xen.git repo directly:
 git clone -b RELEASE-4.8.0 git://xenbits.xen.org/xen.git
* With an older git version (and/or if that does not work, e.g. complaining with a message like this: Remote branch RELEASE-4.8.0 not found in upstream origin, using HEAD instead), do the following:
 git clone git://xenbits.xen.org/xen.git
 cd xen
 git checkout RELEASE-4.8.0
Build instructions can be found at Compiling Xen From Source or Compiling Xen From Source on NetBSD.
= Known issues =
While we did the utmost to get a release out, there are certain fixes which were not complete on time. As such please reference this section if you are running into trouble.
Category:Xen 
Category:Release Notes 
Category:Users
Category:Xen 4.8
Xen Project 4.9 Release Notes

= Overview =
Xen Project 4.9.0 was released on 28th of June, 2017.
Xen Project 4.9.0 is the work of 6.6 months of development (4.2 months of actual development, 2.2 months of hardening), with 1549 changesets.
Also see Xen Project 4.9 Acknowledgements
= New Feature Highlights =
The list of new features can be found on the following page: Xen Project 4.9 Feature List
You can also see an evolution of features on Xen Project Release Features
Documentation is available on Xen Project 4.9 Man Pages
= Build Requirements =
The default installation prefix has been changed to /usr/local. Previously the default installation prefix was /usr To restore the previous behaviour, specify --prefix=/usr when running ./configure, e.g.:
 $ ./configure --prefix=/usr
If you choose to accept the new default then be sure to cleanup any residual bits of the old installation in the old prefix, especially libraries and tools which you might pick up by mistake.
Due to this change it may also now be necessary to run /sbin/ldconfig as root after installing Xen.
Note also that Xen now requires gcc v4.1 or greater.
= Build =
First of all you will have to get the Xen 4.9 source code, which you can either download through our release tarball (including signature) from our download page. Alternatively, you can get the source in the following way:
* With a recent enough git (>= 1.7.8.2) just pull from the proper tag (RELEASE-4.9.0) from the xen.git repo directly:
 git clone -b RELEASE-4.9.0 https://xenbits.xen.org/git-http/xen.git
* With an older git version (and/or if that does not work, e.g. complaining with a message like this: Remote branch RELEASE-4.9.0 not found in upstream origin, using HEAD instead), do the following:
 git clone https://xenbits.xen.org/git-http/xen.git
 cd xen
 git checkout RELEASE-4.9.0
Build instructions can be found at Compiling Xen From Source or Compiling Xen From Source on NetBSD.
= Known issues =
While we do the utmost to make the release perfect, there are always fixes which are not quite complete on time. We will add those here. So if you run into trouble, please check this section.
Currently known issues are:
* Xen may fail to boot on some Skull Canyon Intel NUCs. The symptom is a lack of progress messages after the bootloader. The cause is a buggy BIOS. There is a workaround available: you can backport git commit 5ec164fd61bd8fc7adfb1ca2907d9159eeb1e37b "x86/boot: re-arrange how/when we do disk I/O".
Category:Xen 
Category:Release Notes 
Category:Users
Category:Xen 4.9
Xen Project Advisory Board Meetings Minutes

== Meeting Minutes (2015) ==
* AB Meeting/June 2015 Minutes
* AB Meeting/May 2015 Minutes
* AB Meeting/April 2015 Minutes
* AB Meeting/March 2015 Minutes
* AB Meeting/February 2015 Minutes
* AB Meeting/January 2015 Minutes
== Offline Votes (2015) ==
* AB Votes/COLO-Contracts-June2015
== Meeting Minutes (2014) ==
* AB Meeting/December 2014 Minutes
* AB Meeting/November 2014 Minutes
* AB Meeting/October 2014 Minutes
* AB Meeting/September 2014 Minutes
* AB Meeting/August 2014 Minutes
* AB Meeting/July 2014 Minutes
* AB Meeting/June 2014 Minutes
* AB Meeting/May 2014 Minutes
* AB Meeting/April 2014 Minutes
* AB Meeting/March 2014 Minutes
* AB Meeting/February 2014 Minutes
* AB Meeting/January 2014 Minutes
== Off-line Votes (2014) ==
* AB Votes/STARTUP membership class
* AB Votes/2014 Xen Project Summit in Seattle
* AB Votes/Post XSA 108 PR - Clarification
* AB Votes/Xen Project Video Project
* AB Votes/Outreach Program for Women Round 8
* AB Votes/Funding for Windows PV Drivers subproject
== Meeting Minutes (2013) ==
* AB Meeting/May 2013 Minutes
* AB Meeting/June 2013 Minutes
* AB Meeting/July 2013 Minutes
* AB Meeting/August 2013 Minutes
* AB Meeting/September 2013 Minutes
* AB Meeting/October 2013 Minutes
* AB Meeting/November 2013 Minutes
* AB Meeting/December 2013 Minutes
== Off-line Votes (2013) ==
* AB Votes/Outreach Program For Women Round 7
Category:Advisory Board
Xen Project Development Projects

The table below goes to smaller projects that newcomers to the developer community may pick up. Note that different sub-projects will have projects in different locations.
Xen Project Team 	Project List 	Small Code Contributions 	Contact Information
Hypervisor, mini-os and other core technology projects	Hypervisor, mini-os and other core technology projects	Hypervisor, mini-os and other core technology projects 	Hypervisor, mini-os and other core technology projects
Hypervisor Skills needed:Linux/BSD, C, scripting 	Outreach Program Projects 	Ask on the list. To do Hypervisor development, you will need to have the correct hardware. You can find more information on how to check whether you have the right hardware at Outreachy/Hypervisor. 	xen-devel@lists.xenproject.orgIRC: #xendevel
Unikernel related projects 	Unikernel related projects 	Unikernel related projects 	Unikernel related projects
Unikraft Skills needed: Linux/BSD, C, scripting 	Outreach Program Projects 	Ask on the list 	minios-devel@lists.xenproject.orgIRC: #xendevel
Mirage OS Skills needed: Linux/BSD, OCaml 	MirageOS Pioneer Projects 	Ask on the list 	mirageos-devel@lists.xenproject.orgIRC: #mirage
Tools related projects 	Tools related projects 	Tools related projects 	Tools related projects
Infrastructure & Community 	Infra and Community Projects 	These may differ per individual project. Projects that are currently available cover projects such as improving a code review dashboard, process and tools related work, test and test infrastructure related projects, etc.	These may differ per individual project. Contact information for projects are:
* Mentor and other contact details in the projectalways CC xen-devel@lists.xenproject.orgIRC: #xendevel
XAPI Skills needed: Linux/BSD, OCaml 	None at this stage 	Ask on the list 	xen-api@lists.xenproject.orgIRC: #xenapi
Category:Xen
Category:Developers
Category:Index
Category:Project
Category:Transient
Xen Project Document Days

----
__NOTOC__
----
== What is a Xen Project Document Day? ==
Xen Project document days are all day IRC events, facilitated by members of the Xen Project community. The purpose of Xen Project Document Days is to
* Improve user documentation
* Improve developer documentation, including the creation of man pages, etc.
* Improve and maintaining the wiki: this means fixing important pages, retiring old ones, help identify what is and isn’t important, write new pages, etc.
== How Does it Work? ==
* Request to be a Wiki editor
* Join us on IRC: freenode channel #xendocs
* Tell people what you intend to work on (to avoid doing something somebody else is already working on)
* Fix some documentation
* Help others
* And above all: have fun!
== THEME OF THE MONTH: "Beginner Information" ==
We've seen an increase of interest from potential new users recently and we need to make sure that people can successfully get started with 4.6 using our current set of Wiki pages. We have been slowly replacing the xm references with xl, but we could use people to read over many of the existing pages to make sure they still make sense with the latest release.
Pages of special interest include:
* Xen Project Beginners Guide (recently revised, but could use a read-through)
* Getting Started
* Xen Project Best Practices
* Xen Common Problems
And, of course, any other page which needs to reflect the realities of working with 4.6.
== Other ways to Help ==
Let us know if you struggled with some content, if something is missing, can be improved and you do not feel sure enough to make changes to a page. The way to do this is by making a comment on talk pages. Every wiki page has an associated talk page which can be used for discussion and communicating with other users. Talk pages can be accessed by clicking the “discussion” tab at the top of the page. Simply edit the page as normal to add your comment, following the conventions outlined in Help:Talk Pages.
== Proposed Dates for 2015 ==
Following the modifications we made in 2014 to make Document Day the last Wednesday of the month, this year's proposed dates are as follows:
* January 28, 2015
* February 25, 2015
* March 25, 2015
* April 29, 2015 (moved to May 6 because of the Hackathon)
* May 27, 2015
* June 24, 2015
* July 29, 2015
* August 26, 2015
* September 30, 2015
* October 28, 2015
* December 2, 2015 (due to holidays in November and December in multiple countries)
== Extra Days ==
Some community members indicated that they would like an extra doc day on a public holiday or weekend. We are looking for proposed dates. Please add dates below and sign up besides it. If we get more than 5 people signed up, we should hold a day on a weekend.
Category:Community
Category:Events
Xen Project Hypervisor Roadmap

== Release Manager ==
We confirmed Wei Liu from Citrix as Release Manager for Xen 4.6, 4.7 and 4.8 : see e-mail thread
We confirmed Julien Grall from ARM as Release Manager for Xen 4.9 and 4.10
== Roadmap ==
As in the past, roadmap discussions will mostly happen on the xen-devel mailing list (see below). The convention is that our release manager will regularly post an e-mail called Xen 4.X development update on the xen-devel list and that community members respond to it. 
== The Process ==
You can find information on how we make relases in this blog post. We also attached a few pictures for your convenience.
File:46-releaseprocess-1.png|Release Process Stages
File:46-releaseprocess-2.png|Stages in Detail
File:46-releaseprocess-3.png|How we create our Roadmap
Xen Project Hypervisor Roadmap/4.7

Rather than try to predict precisely what will make it into what
release, we are following an approach from the Agile world and call all uncompleted
features the "Backlog". We are however keeping track who is doing what, what is completed
and what is almost completed in this wiki page. For ongoing work check out the Process
section of this document.
== Release Manager ==
Wei Liu from Citrix remains Release Manager for Xen 4.7.
== Roadmap ==
As in the past, roadmap discussions will mostly happen on the xen-devel mailing list (see below). The convention is that our release manager will regularly post an e-mail called Xen 4.7 development update on the xen-devel list and that community members respond to it. 
== The Process ==
You can find information on how we make releases in this blog post. We also attached a few pictures for your convenience.
File:47-releaseprocess-0.png|Release Process Changes
File:47-releaseprocess-1.png|Release Process Stages
File:47-releaseprocess-2.png|Stages in Detail
File:47-releaseprocess-3.png|How we create our Roadmap
== Xen 4.7 Timeline ==
We are planning on a 8-month release cycle. Our current estimated dates:
 Development start: 13 October 2015
 <==== WE ARE HERE ===>
 Last posting date: 18 March 2016
 Hard code freeze: 1 April 2016
 Release date: 3 June 2016
== Running Roadmap Updates on xen-devel ==
See
* November: Xen 4.7 Development Update
Related Presentations
* Xen Project Release and Roadmap Process (4.7+) (Nov 2015)
== Xen 4.7 Completed Features ==
== Hypervisor == 
=== x86 === 
Intel CDP support
 - He Chen
== Record of Discussions and Votes leading to the 4.7 Release Process ==
* [Vote] Release cycle scheme
* RFC: Survey on release cycle
* RFC: LTS and stable release scheme
* RFC: change to 6 months release cycle
== Other Information about how we manage releases ==
* General Process
* How the Hypervisor team manages releases
* Release management: Risk, intuition, and freeze exceptions
Category:Xen
Category:Xen 4.7
Xen Project Meltdown and Spectre Technical FAQ

== Where can I find the current patch series that fixes Meltdown/SP3 == 
Please refer to XSA-254 for more details.
== Where can I find the current patch series that fixes Spectre/SP2 == 
See 
* x86: Mitigations for SP2/CVE-2017-5715/Branch Target Injection
* xen/arm64: Branch predictor hardening	(XSA-254 variant 2)
* xen/arm32: Branch predictor hardening	(XSA-254 variant 2)
* Note that newer versions of these patches appear at high velocity: please always check the xen-devel@ archives for the latest version
== Is there any practical advice about responding to XSA-254 (also known as the 'Meltdown' and 'Spectre' vulnerabilities)? ==
See Respond to Meltdown and Spectre, our FAQ and XSA 254.
== What are some dependencies between Xen features, guest types and mitigations? ==
Please refer to the OpenXT spreadsheet, Meltdown and Spectre Exposure Analysis: Xen, Linux & Windows.
Category:Security
Xen Project Test Days

----
__NOTOC__
== What is a Xen Project Test Day? ==
Xen Project Test Days are all day IRC events, facilitated by members of the Xen Project community. The purpose of Xen Project Test Days is to
* Provide focus in testing Xen Project Release Candidates
* Primary focus will be on ensuring that Xen Project RCs work with distros 
* Focus on new features of the Xen Project software release
== How Does it Work? ==
* Join us on IRC: freenode channel #xendevel
* Tell people what you intend to test
* Make sure that a Xen Project release candidate works for you
* Help others, get help!
* And above all: have fun!
== Proposed dates==
Test Days primarily make sense during the release candidate period of Xen Project. Test Days are expected to be scheduled roughly every week until it is determined that the software is ready for release. See "next dates" above.
== Archived Test Instructions from Earlier Release Cycles ==
* Xen 4.14 RC test instructions 
* Xen 4.13 RC test instructions 
* Xen 4.12 RC test instructions 
* Xen 4.11 RC test instructions 
* Xen 4.10 RC test instructions 
* Xen 4.9 RC test instructions 
* Xen 4.8 RC test instructions 
* Xen 4.7 RC test instructions 
* Xen 4.6 RC4 test instructions
* Xen 4.6 RC3 test instructions 
* Xen 4.6 RC2 test instructions 
* Xen 4.6 RC1 no Test Day
* Xen 4.5 RC4 test instructions
* Xen 4.5 RC3 test instructions
* Xen 4.5 RC2 test instructions
* Xen 4.5 RC1 test instructions
* Xen 4.4 RC4 test instructions
* Xen 4.4 RC3 test instructions
* Xen 4.4 RC2 test instructions
* Xen 4.4 RC1 no Test Day
* Xen 4.3 RC6 test instructions
* Xen 4.3 RC5 test instructions
* Xen 4.3 RC4 test instructions
* Xen 4.2 RC3 test instructions 
* Xen 4.2 RC2 test instructions 
* Xen 4.3 RC1 test instructions 
* XCP 1.6 test instructions 
Category:Community
Category:Events
Category:Test Day
Category:Xen_4.15
Xen Project User Summit

== Xen Project User Summit was held on September 15, 2014 in Downtown Manhattan ==
The year 2013 marked the arrival of the very first Xen Project User Summit. In 2014, we drew a variety of people to the Lighthouse Executive Conference Center in the heart of New York City to discuss the use of the Xen Project hypervisor.
=== Sessions Announced: ===
Following were confirmed speakers and presentations discussed in New York:
* Konrad Wilk, Xen Project 4.5 Release Manager, Oracle Corporation — reports on the advances and features to be included in the upcoming Xen Project 4.5 release;
* Peter Linnell, Linux Technical Specialist, SUSE – gives an overview and demo of Xen Project software in OpenStack with SUSE Cloud;
* Don Marti, Technical Marketing Manager, Cloudius Systems – instructs how to deploy C and Java applications directly on Xen Project virtualization using OSv; 
* Olivier Lambert, founder of the Xen Orchestra Project, Vates -- discusses Xen Orchestra, a web-based interface for the Xen Project Hypervisor, as well as XenServer using the XAPI toolkit.
* Steven Maresca, Senior Security Engineer, Zentific LLC — talks about Zazen, a security framework for the cloud that uses several of Xen Project software’s latest features to deliver VM security;
* Johnny Hughes, CentOS Project – outlines using and understanding Xen4CentOS and shares the latest developments with the CentOS Virtualization SIG;
* Grant McWilliams, Custom Product Engineer, Sound Linux Training and Consulting — discusses the lessons learned from provisioning a large numbers of XAPI-based security appliances;
* Russell Pavlicek, Xen Project Evangelist – describes many of the advanced security features with Xen Project software that can be used in either traditional virtualization environments or a cloud;
* Will Auld, Performance Architect, Intel Corporation — introduces a high availability project called COLO, (COarse-grain LOck-stepping virtual machine solution for non-stop service);
* Tim Mackey, XenServer Community Manager, Citrix – presents XenServer.org one year later and a look at the next release;
* Adam Wick, Technical Director, Systems Software, Galois Inc. - defines what "unikernels" (sometimes called "cloud operating systems") are, why they are important to the future of cloud computing, and when and where to use them;
* Lars Kurth, Xen Project Advisory Board Chairman, Citrix – reports on the activities of the Xen Project Advisory Board, as well as the development community.
For more information about Xen Project User Summit, including how to register and to view the complete schedule, visit: http://events.linuxfoundation.org/events/xen-project-user-summit.
Category:Events
Xen Project Version Compatibility

= Guest ABI Guarantees =
The hypervisor API exposed to guests was declared to be a stable binary interface (ABI) with the release of Xen 3.0.0 in December 2005. Any changes to the guest visible ABI are done in a backwards compatible manner and new interfaces are optional and opt-in for guests.
If the hypervisor ABI is changed in a way which breaks an existing guest then this should be considered a bug.
= Live Migration Between Versions =
Xen Project supports migration (including live migration and save restore) both within a stable release branch (e.g. between any versions in the 4.2.x branch) and from one major release to the next (e.g. from release N to releaseN+1). This allows one to upgrade a pool of Xen Project hosts by evacuating and upgrading the hosts one by one.
Although it is not formally supported skipping a major release (e.g. migration from release N to release N+2) may often work.
Migrating down a version (e.g. from release N+1 down to release N) is not normally supported.
= Xen 3.x vs Xen Project 4.x =
The release following Xen 3.4 was named 4.0. However this was just a version number bump and does not imply anything particular with regards to compatibility guarantees between those two versions. From a compatibility point of view Xen Project 4.0 could just as easily have been called Xen 3.5.
In particular it is not the case that Xen Project 4.x is incompatible with guests using the Xen 3.x hypervisor API and the Guest API guarantees mentioned above continue to hold. Likewise live migration from version 3.4 to version 4.0 is supported.
Category:Compatibility
Category:Users
Xen Project X.YY Release Notes

Proposed option: Wed Feb 26, 2025
(~ +8 months from Xen 4.19 release)
- Last posting date Fri Nov 29, 2024 (+8 weeks from now)
Patches adding new features are expected to be posted to the mailing
list by this date, although perhaps not in their final version.
- Feature freeze Fri Dec 20, 2024 (+3 weeks from Last posting date)
Patches adding new features should be committed by this date.
Straightforward bugfixes may continue to be accepted by maintainers.
- Code freeze Fri Jan 17, 2025 (+4 weeks from Feature freeze)
Bugfixes only.
- Hard code freeze Fri Feb 07, 2025 (+3 weeks from Code freeze)
Bugfixes for serious bugs (including regressions), and low-risk fixes only.
- Final commits Fri Feb 21, 2025 (+2 weeks from Hard code freeze)
Branch off staging-4.20.
- Release Wed Feb 26, 2025
Xen Roadmap

== How we manage Roadmaps ==
You can find information on how we make releases in this blog post and Xen Project Release and Roadmap Process (4.7+) (Nov 2015). We also attached a few pictures for your convenience.
File:47-releaseprocess-0.png|Release Process Changes
File:47-releaseprocess-1.png|Release Process Stages
File:47-releaseprocess-2.png|Stages in Detail
File:47-releaseprocess-3.png|How we create our Roadmap
The following discussions and vote, were leading towards the latest version of the Release Management Process:
* [Vote] Release cycle scheme
* RFC: Survey on release cycle
* RFC: LTS and stable release scheme
== Roadmap Information for Specific Releases ==
Information on this page contains the most recent features requested for the next version of the Xen hypervisor. 
* Xen Project 47 Roadmap
* Xen Project 4.6 Roadmap
* Xen Project 4.5 Roadmap
* Xen Project 4.4 Roadmap
* Xen 4.3 Roadmap
* Xen 4.2 Features (including documentation) - See Xen 4.2
* Xen Roadmap/4.1 Feature Requests List
* Xen Roadmap/4.0 Feature Requests List
* Xen Roadmap/2009 Roadmap Document
* Xen Roadmap/Xen 3.4 Roadmap
* Xen Roadmap/Xen 3.3 Roadmap
* Xen Roadmap/July 2006 Roadmap Document
Category:Xen
Category:Project
Category:Developers
Xen Roadmap/Xen 3.3 Roadmap

Xen Roadmap
== Xen 3.3 Roadmap ==
Xen 3.3 features/enhancements set for development include the following:
* IO emulation "stub domains" for improved HVM IO performance and scalability
* replacement of Intel VT vmxassist by new 16b emulation code
* improved VT-d device pass-through e.g. for graphics devices
* enhanced C and P state power management
* exploitation of multi-queue support on modern NICs
* removal of domain lock for improved PV guest scalability
* 2MB page support for HVM and PV guests
* upgrade QEMU version
* enhanced xen api support
* switch to pv_ops as the main dom0/domU used for testing
Several of these items currently have no "owner" so please send email to xen-devel@lists.xensource.com if you have any interest in leading the development effort. The delivery schedule for 3.3 is not fixed so please monitor this page for future updates to include a complete development and test schedule for Xen 3.3.
Category:Xen
Category:Project
Category:Developers
Xen VGA Passthrough to Windows 8 Consumer Preview 64-bit English HVM domU and Windows XP Home Edition SP3 HVM domU with Xen 4.2-unstable Changeset 25070 and Linux Kernel 3.3.0 in Ubuntu 11.10 oneiric ocelot amd64 Final Release Dom0

#REDIRECT Xen VGA Passthrough to Windows 8 with Xen 4.2-unstable