nyuuzyou/wikis huggingface dataset:
Xen Maintainer, Committer and Developer Meeting/May 2013 Minutes

Not sure who attended, so omitting list
= Agenda =
Ian is going to start sending out a call for agenda only the week before and the agenda shortly before the call instead of the current two/one weeks before. Please reply to all if you have any issues to add so that people can prepare.
= Previous ACTIONS =
== VCPU == 
Boris has been unable to determine if an issue he is seeing is an eratta or just how things work.
Intel are working on improving PMU virtualisation. Don suggests Boris use the existing email thread to try and get a response before he tries escalating within Intel.
= Hackathon =
The hackathon is now fully subscribed. Special arrangements will need to be made for any additional attendees.
= 4.3 Feature Matrix =
* Nested Virt (currently "experimental")
** Jun: Need to clarify expectations of what works and what does not
** General feeling seems to be that this could become "tech preview"
** ACTION: Intel and AMD to start/contribute to a thread enumerating what is known to work and what is known to be broken. Don and Sherry will ping the appropriate people.
* TMEM (currently "experimental")
** No change
* OVMF (currently "experimental")
** No change
* Credit2 (currently "experimental")
** No change
== Feature Roadmap/Lifecycle ==
No clear definition for what is "experimental" and what is "tech preview" makes it hard to know how to categorise things to set expectations correctly.
ACTION: it seems like there should be one...
= Linux Maintainers =
Konrad is doing the majority of this, more people are needed.
James will work with the XenServer team to see if resource can be found.
ACTION: Konrad to send out a list of current issues, CCing James
= Security Vulnerability Process =
Needs formatting for ease of spotting changes, which Lars is doing on the new site shortly. Will put up for comment and move to a vote soon.
Needs buy in from community.
Category:Technical Coordination Team
Xen Maintainer, Committer and Developer Meeting/November 2012 Minutes

== Attendees ==
* Ian Campbell
* George Coker
* Daniel De Graaf
* Boris Ostrovsky
* Olaf Hering
* Sherry Hurwitz
* Lars Kurth
* James Bulpin
* Jan Beulich
* Jason Douglas
* Donald Dugger
* Jun Nakajima
* Daniel Kiper
== Review ACTION items ==
* Lars to write up purpose/mechanics of monthly call (done, see discussion below)
* Konrad to summarize PV ops discussion from KS on xen-devel:
** DanielK: Konrad promised this, will do ASAP. He's very busy right now (Carry over)
* George to blog about uservoice.com (DONE, [ http://blog.xen.org/index.php/2012/10/15/xen-org-on-uservoice-com/ here] )
* Andres to follow up re: wait queues on xen-devel (DONE)
== Call mechanics ==
* Organisations contributing a certain amount are given two seats after majority vote
** Should extend to individuals if they contribute that amount?
* If an organisation doesn't show up 6 times in a row without reason, remove them
** No objections on the call
** Suggestions from Don and James for less than 6 months
** No objections to 3 months
** ACTION Ian will drop organisations from the invite/agenda etc as appropriate
== Transition to git ==
* still intended
* waiting for someone to have some free time to make switch
* request to have git clone over http as well as git (will do)
* planning to retain hg mirror until next stable branch created
== Community update ==
* archived XCI
* Lars approached by Anil Madhavapeddy about incubating Mirage
* At UDS, Linaro Connect, LinuxCon
** reception of Xen talks/booths picking up, seeing an effect
* Would like to do XenSummit in spring (April/May) in US/Asia, looking for a sponsor
* Have XenSummit in Europe with collocated LinuxCon in fall
Category:Technical Coordination Team
Xen Maintainer, Committer and Developer Meeting/October 2012 Minutes

= Minutes =
== Attendees ==
Ian Campbell
Andres Lagar-Cavilla
Adin Scannell
Boris Ostrovsky
Sherry Hurwitz
James Bulpin
Ian Pratt
Donald Dugger
Jun Nakajima
Kurt Hackel
George Dunlap
Matt Wilson
Apologies:
Lars Kurth
Jan Beulich
Daniel De Graaf
George Coker
== Call membership ==
Welcomed new call members from AWS, Gridcentric and NSA.
ACTION: Lars to write up purpose of monthly call
== Review ACTION items ==
Follow up on San Diego F2F meeting actions
* George has sent 4.3 list to xen-devel
** if you are working on stuff not on the list let George know
* Future Direction of Xen and PV:
** Konrad to summarize PV ops discussion from KS on xen-devel. Carried over
** Konrad to make concrete proposals regarding PVH and PVOPS and disucss on list when appropriate in future. Carried over
* EFI secure boot:
** Matt sent links to reference hardware a few weeks ago (DONE)
** Best practice doc - Stefano added to list for next doc day (DONE)
*** Next doc day on October 29
** On 4.3 todo list
* Nested virt
** On list for 4.3
** AMD support in 4.2? Not fully cooked, could declare as an experimental feature.
*** WinXP mode on Win7 is least stable case (but probably most
important)
*** Working on making work for 4.3
** Intel actively working on and testing nested support for 4.3
* NUMA working group - Lars checked, there is none (DONE)
* NUMA - link up with AnilM - interesting discussion but nothing for 4.3 timeframe (DONE)
* Guest NUMA - VMware vNUMA exists, vMotion works with it but afterwards the VM may not be optimised
** Matt Wilson posted a link to a blog article on xen-devel
* Upstream kernel features
** Intel are working on connecting up their Xen and Linux guys
== Current technical challenges ==
* AMD (Boris): oprofile vs perf status?
** Ideally perf on Xen would be feature comparable with on KVM
** Is perf sample based like oprofile? Yes, but can also use performance counters
** Sounds like this has no owner currently but Konrad and others would like to see it
== Coordinate current and future work ==
* Uservoice.com: George setup xenorg.uservoice.com to supplement 4.3 planning.
** Users can suggest new ideas and vote on them
** Was put up mid-August and mentioned on lists.
** ACTION George to blog about it
** How do we get xen.org contributors to pick these items up?
** Top features:
*** Boot HVM guests with pass-through for primary GPU
*** Storage motion (not sure if people want this for XCP or Xen+xl)
*** QXL GPU support for SPICE
*** PVSCSI
**** Konrad may have in a branch
***** Needs upstreaming to Linux
***** Need xl support for xend parity
*** libvirt driver enhancements (all libxl functionality in libvirt)
**** Talking to Suse about tracking their work
**** Suse are looking at this right now and have a team of devs on it
* 4.3
** Gridcentric wants to see wait queue in h/v in 4.3
*** willing to work with Keir on this
*** ACTION Andres to follow up on xen-devel
* XSM doc project - Citrix employing a contractor to write wiki docs on use of XSM.
** XenServer team (via James) can review - suggest also getting XenClient review
Category:Technical Coordination Team
Xen Maintainer, Committer and Developer Meeting/September 2012 Minutes

= Minutes =
Attendees: Boris Ostrovsky, Olaf Hering, Sherry Hurwitz, Jason Douglas, Lars Kurth, Ian Campbell, James Bulpin, Jan Beulich, Konrad R Wilk, Donald D Dugger, Jun Nakajima, Kurt Hackel
== Call membership (new organisations to invite representatives from existing organisations, etc) == 
We voted on call membership for AWS, GridCentric and NSA based on Xen 4.2 contributions. Motion to accept reps from each of these got approved.
I am still following up on Barcelona Tech (it seems that the majority of their contributions came from Roger Pau Monne)
ACTION: Lars to invite AWS, GridCentric and NSA to call (done) 
== Review outstanding ACTION items ==
* Simon: Discuss IRQ's and MSIs with MSIs and get Andy Cooper talking to Jun on xen-devel -- James to prod Andy (done)
* Lars: Start cleaning up Xen 4.2 feature list such that it is in good shape when we go into Xen 4.2 RC's (done)
* Ian to ping Keir and provoke either new RCs or actual releases (done)
ACTION: IanC to transfer actions from face-2-face meeting action to list
== PVOPS Update (Konrad) ==
Konrad was representing Xen at the Linux Kernel summit. One of the items which was discussed were requirements on the Xen community with regards to PVOPS code. It appears that people with a strong interest in the code are : Konrad, Peter & Thomas
Concrete outcomes from the meeting were
* We need to remove the "mapping_reserve" hack 
* We solved immediate and roadmap issues
* PV MMU OPS
** Discussed the potential of PVH
** No immediate urgency : in other words, we can get PVH production ready and then plan a longer-term architecture clean-up
** Looking at approximately 5 years after PVH is production ready
Category:Developers
Category:Transient
Category:Events
Category:Technical Coordination Team
Xen Management Tools

= Xen Management Tools =
NOTE: This page is ARCHIVED. All new listings should be entered into the Ecosystem Directory on XenProject.org. Look at the directions page for more information.
This page used to list various 3rd party management tools and interfaces for Xen. For XCP, please see the list of XCP Management Tools. It is being replaced by the Ecosystem Directory on XenProject.org. If you own one of the products, projects, or services below, please make sure it has been entered into the XenProject.org Ecosystem Directory.
= Management tools and interfaces =
* Libvirt and virt-manager. Libvirt and http://virt-manager.et.redhat.com/
* xen-tools. http://gitorious.org/xen-tools/xen-tools
* Zentific: http://www.zentific.com/
* Convirt: http://www.convirture.com/
* OpenQRM: http://www.openqrm.com/
* Xn-Suite: http://www.xncore.de/node/61
* Xen Orchestra: http://xen-orchestra.com/
* Ganeti: http://code.google.com/p/ganeti/
= Cloud frontends =
* Eucalyptus: http://open.eucalyptus.com/
* OpenNebula: http://opennebula.org/
* Nimbus: http://www.nimbusproject.org/
* openQRM: http://www.openqrm.com/
= Application Programming Interfaces (APIs) and libraries =
* XenAPI (XAPI): http://wiki.xensource.com/xenwiki/XAPI_Developer_Guide
* Libxenlight (libxl): Xen 4.0 contains initial implemention of libxl, which is common lowlevel library to manage Xen hypervisor. It's written in C so that it can be shared by various higher level tools and libraries. Xen 4.1 (xen-unstable) continues to add more features to libxl and xl. See Xen Summit 2010 NA slides about libxl: http://www.slideshare.net/xen_com_mgr/xen-summit-amd2010v3
Category:Xen
Category:Overview
Category:Users
Category:Beginners
Xen Profiling: oprofile and perf

By Konrad Rzeszutek Wilk from this email message
== Summary ==
I've been toying with some perf tools using the v3.5 kernel to get
an idea of what is working and what not. The executive summary
is that we should write a perf driver to interact with perf
Linux subsystem; and also to enhance the perf library to support
the --xen extensions (similar to how the --kvm exists). It might
also require adding some new hypercalls, though the existing
ones (the oprofile variant) could be retooled to use with perf.
== perf ==
What currently exists are two ways of collecting performance data
in both dom0 and domU (and by that I also mean PVHVM). The easiest
one is the 'perf' 
toolkit which works nicely - except that it is
using a timer mode - so not very accurate. However, if Xen is booted
with 'vpmu=1' parameter and perf is used within a PVHVM guest - the
data is much more accurate. So what would be good is to implement
a non-timer variant (so some model of APIC emulation combined
with collecting data in a oprofile ring and avoiding MSRs).
== oprofile ==
The good news is that the old performance system oprofile works
with the non-timer variant with some patches. You could also
run the oprofile in timer mode and get the same data that the 'perf'
does. The patches for the oprofile have been in the past posted
by Michael Petullo, and I created a git branch with them with
some little changes (basically to make them work with the new
kernel - they are still buggy though - rmmoding caused a crash).
They are now at:
: git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git devel/oprofile.v1
I plan to tinker a bit with them so they aren't completely hacked in with #ifdef CONFIG_XEN but I do not have any plans to upstream them.
I think the right direction is to make a new shiny perf driver.
Anyhow, if you want to play and get some performance data, the steps
are:
* Get the latest kernel from Linus's tree. Merge the above mentioned git branch
* Install oprofile. If you are using Fedora 17, the oprofile RPM already has the Xen enablement patches thanks to William Cohen (see ). If you are using a different distro, get oprofile and apply the patch mentioned in the URL.
* Run it. This is what I've been doing:
 opcontrol --start --passive-domains=2,3 
 --passive-images=/mnt/lab/nettest/vmlinux-pvhvm,/mnt/lab/nettest/vmlinux-pvhvm 
 --xen=/data/xen-syms --vmlinux=/data/vmlinux --callgraph=5
A co-worker mentioned that to get the exact data from the guest
(which is not what I was using it for), your guest config file
must contain this "magic":
 cpuid=['0xa:eax=0x07300403,ebx=0x00000004,ecx=0x00000000,edx=0x00000603'
for HVM guests. For PV guests the data shows up just fine.
Category:Xen
Category:Developers
Category:PVOPS
Category:Performance
Xen Project 4.10 Release Notes

= Overview =
Xen Project 4.10.0 was released on 12th of December, 2017.
Xen Project 4.10.0 is the work of 5.9 months of development (3.8 months of actual development, 2.1 months of hardening), with 1250 changesets.
Also see Xen Project 4.10 Acknowledgements
= New Feature Highlights =
The list of new features can be found on the following page: Xen Project 4.10 Feature List
You can find information on support status (including security support) for various features in SUPPORT.md (replacing Xen_Project_Release_Features).
Documentation is available on Xen Project 4.10 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.10 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.10.0) from the xen.git repo directly:
 git clone -b RELEASE-4.10.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.10.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.10.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:
* 
Category:Xen 
Category:Release Notes 
Category:Users
Category:Xen 4.10
Xen Project 4.11 Release Notes

= Overview =
Xen Project 4.11.0 was released on July 10, 2018.
Xen Project 4.11.0 is the work of 7.5 months of development.
Also see Xen Project 4.11 Acknowledgements
= New Feature Highlights =
The list of new features can be found on the following page: Xen Project 4.11 Feature List
You can find information on support status (including security support) for various features in SUPPORT.md and Hypervisor Support Matrix.
Documentation is available on Xen Project 4.11 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.11 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.11.0) from the xen.git repo directly:
 git clone -b RELEASE-4.11.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.11.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.11.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:
* 
Category:Xen 
Category:Release Notes 
Category:Users
Category:Xen 4.11
Xen Project 4.12 Release Notes

= Overview =
Xen Project 4.12.0 was released on 2nd of April 2019.
Xen Project 4.12.0 is the work of 9 months of development.
Also see Xen Project 4.12 Acknowledgements
= New Feature Highlights =
The list of new features can be found on the following page: Xen Project 4.12 Feature List
You can find information on support status (including security support) for various features in SUPPORT.md and Hypervisor Support Matrix.
Documentation is available on Xen Project 4.12 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.12 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.12.0) from the xen.git repo directly:
 git clone -b RELEASE-4.12.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.12.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.12.0
Build instructions can be found at Compiling Xen From Source or Compiling Xen From Source on NetBSD.
= Namespace changes affecting downstreams and users =
* kdd (tool for debugging guest OSes with the windows kernel debugger) has been renamed to xen-kdd in order to reduce namespace pollution.
* The fsimage library used by pygrub, which does not have a stable ABI, and the corresponding python module, have been renamed to 'xenfsimage' (to reduce namespace pollution). Any out-of-tree users of this library will have to be updated.
= 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:
* None currently known
Category:Xen 
Category:Release Notes 
Category:Users
Category:Xen 4.12
Xen Project 4.13 Release Notes

= Overview =
Xen Project 4.13.0 was released on Dec 18, 2019.
Xen Project 4.13.0 is the work of 8 months of development.
Also see Xen Project 4.13 Acknowledgements
= New Feature Highlights =
The list of new features can be found on the following page: Xen Project 4.13 Feature List
You can find information on support status (including security support) for various features in SUPPORT.md and Hypervisor Support Matrix.
Documentation is available on Xen Project 4.13 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.13 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.13.0) from the xen.git repo directly:
 git clone -b RELEASE-4.13.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.13.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.13.0
Build instructions can be found at Compiling Xen From Source or Compiling Xen From Source on NetBSD.
= Changes affecting downstreams and users =
* Xen 4.13 is now fully Py3 compatible 
* In Xen 4.13 we changed the minimum Py2 version to 2.6
= 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:
* None currently known
Category:Xen 
Category:Release Notes 
Category:Users
Category:Xen 4.13