nyuuzyou/wikis huggingface dataset:
Archived/Xen Technical Coordination Team (TCT) Meeting

== Upcoming Meetings ==
The purpose of these calls and the Technical Coordination Team (TCT) is to discuss technical issues, large contribution, co-ordinate contributions, work on roadmaps, etc. It is not a call that is entirely open to all community members: community members that actively contribute on an ongoing basis may request an invite.
== Meeting Operations ==
Getting invited:
* Anyone else who is active in the community who can show that they have been actively been contributing to the project can request an invite by mailing ian dot campbell at citrix dot com. Existing members of the TCT will vote on invite requests, if there is doubt on whether the community member has been contributing enough to the project. 
* The Xen Project Advisory Board chairman, Project Leads of mature projects, the Xen Project community managers and Committers are automatically invited to the call
Obligations to remain invited:
* If an organisation or individual that earned the right to be invited does not show up 3 times in a row without giving reason, invitation to the meeting may be revoked
* Project leads and committers are excluded from this constraint
== Members ==
* See :Category:Technical Coordination Team
== Meeting Minutes (2014) ==
* TCT Meeting/June 2014 Minutes
* TCT Meeting/May 2014 Minutes
* TCT Meeting/April 2014 Minutes
* TCT Meeting/March 2014 Minutes
* TCT Meeting/February 2014 Minutes
* TCT Meeting/January 2014 Minutes
== Meeting Minutes (2013) ==
* Xen Maintainer, Committer and Developer Meeting/January 2013 Minutes
* Xen Maintainer, Committer and Developer Meeting/February 2013 Minutes
* Xen Maintainer, Committer and Developer Meeting/March 2013 Minutes
* Xen Maintainer, Committer and Developer Meeting/April 2013 Minutes
* Xen Maintainer, Committer and Developer Meeting/May 2013 Minutes
* TCT Meeting/June 2013 Minutes
* TCT Meeting/July 2013 Minutes
* TCT Meeting/August 2013 Minutes
* TCT Meeting/September 2013 Minutes
* TCT Meeting/October 2013 Minutes
* TCT Meeting/November 2013 Minutes
== Meeting Minutes (2012) ==
In the May 2012 call, a vote was held to start publishing meeting minutes. Meeting minutes will be published in this section.
* Xen Maintainer, Committer and Developer Meeting/December 2012 Minutes
* Xen Maintainer, Committer and Developer Meeting/November 2012 Minutes
* Xen Maintainer, Committer and Developer Meeting/October 2012 Minutes
* Xen Maintainer, Committer and Developer Meeting/September 2012 Minutes
* Xen Maintainer, Committer and Developer Meeting/XenSummit NA 2012 Minutes
* Xen Maintainer, Committer and Developer Meeting/August 2012 Minutes
* Xen Maintainer, Committer and Developer Meeting/July 2012 Minutes 
* Xen Maintainer, Committer and Developer Meeting/June 2012 Minutes
Category:Developers
Category:Events
Category:Technical Coordination Team
Category:Community Meetings
Argo: Hypervisor-Mediated Exchange (HMX) for Xen

== Hypervisor Mediated Exchange (HMX) ==
The technologies provided by VMMs for communication between VMs have a critical impact on VM isolation properties, on the confidence components can have in the delivery of data and in the integrity of the data that is received. The video below identifies aspects of inter-VM communication system architecture that support important properties that are valuable for building secure systems. Terminology is introduced to enable classification of the existing body of art and survey relevant communication technologies in modern hypervisor, OS and microkernel systems. An example is presented — Argo, an inter-VM communication mechanism developed for the Xen hypervisor — and how it is distinguished from other communication channels on the Xen platform and elsewhere.
* PSEC 2018 talk by Christopher Clark (May 2018)
* Xen Summit 2019 video and slides (June 2019)
== V4V (historical) ==
V4V was created for Citrix XenClient and derivatives are currently deployed in production systems for OpenXT and millions of HP/Bromium laptops with uXen and vSentry/SureClick. 
* Jean Guyader: xen-devel thread on V4V requirements (May 2012)
* Ross Philipson: PATCH (V9) Add V4V to Xen (May 2013)
== Argo ==
Argo was derived from V4V, hypervisor patches were submitted to xen-devel in 2018 and merged in 2019 for Xen 4.12.
Note: Linux driver for Argo is not yet upstream.
Upstream
* Xen 4.12 design doc (March 2019)
History
* (June 2018)
* Minutes of x86 community call (September 2018)
* v1 patch series (November 2018)
* v3 patch series (January 6 2019)
* v4 patch series (January 14, 2019)
== Related Work ==
* Xinhua Zhang: Xen libvchan (2014)
* Roman Kagan: VMBus (Hyper-V) devices in QEMU/KVM (2015)
* Michael S. Tsirkin: The future of virtio: riddles, myths and surprises (2017)
Asking Xen User Questions

For:
* Please send an e-mail to xen-users@lists.xenproject.org and follow Xen Users Netiquette
* For quick questions, check out the #XEN IRC channel on irc.freenode.net
* Raising bugs, see Reporting Bugs against Xen Project
* Man pages are at docs/unstable. For man pages of a specific release, go to xenbits.xen.org/docs and choose the right version.
* Documentation, see documentation on xenproject.org
* HowTo's, see :Category:HowTo, you can find a few example topics that are available from this page here:
** Xen Networking
** Xen FreeBSD
** Adding USB Devices to Xen HVM - http://www.virtuatopia.com/index.php 
** Xen on Fedora - http://rackerhacker.com/2011/08/05/xen-4-1-on-fedora-15-with-linux-3-0/ 
** Create and Install CentOS on Xen - http://wiki.centos.org/HowTos/Xen/InstallingCentOSDomU 
** http://www.virtuatopia.com/index.php/Configuring_a_VNC_based_Graphical_Console_for_a_Xen_Paravirtualized_domainU_Guest
** https://help.ubuntu.com/community/Xen Xen on Ubuntu
* Guest Conversion, see Xen_FAQ_Guest_Conversion
* Console, see Xen_FAQ_Console
* Drivers, see Xen_FAQ_Drivers,_Windows
* Domain0, see Xen_FAQ_Dom0
* DomainU/Guests, see Xen_FAQ_DomU
* Devices, see Xen_FAQ_Devices
* Installation Questions, see Xen_FAQ_Installation
* Networking Questions, see Xen_FAQ_Networking
* Security Questions, see Xen_FAQ_Security
* Design/Misc Questions, seeXen_FAQ_Design_and_in_Depth
Category:Xen
Category:FAQ
Category:Users
Assign Hardware to DomU with PCIBack as module

__NOTOC__
If the Dom0 XenLinux kernel is built with pciback as a module, attempting to use the kernel command-line parameter pciback.hide won't work. This includes loading pciback in an initrd. This means that if you wish to assign hardware to a DomU another method is needed.
There are two possibilities.
= Option 1: Late Binding =
Use late binding as described in section 5.3.1.3 of the user manual and put something like the following in an init script (/etc/rc.local will work on Fedora) to be executed before Xen domains. You can find the correct value for $BDF using lspci. For more information on BDF notation see Bus:Device.Function (BDF) Notation.
 
BDF=0000:05:02.0
# Unbind a PCI function from its driver as necessary
[ ! -e /sys/bus/pci/devices/$BDF/driver/unbind ] || \
 echo -n $BDF > /sys/bus/pci/devices/$BDF/driver/unbind
# Add a new slot to the PCI Backend's list
echo -n $BDF > /sys/bus/pci/drivers/pciback/new_slot
# Now that the backend is watching for the slot, bind to it
echo -n $BDF > /sys/bus/pci/drivers/pciback/bind
This has the disadvantage that if pciback is unloaded for any reason, you'll have to do it again.
= Option 2: Modify Config File =
Add a line to /etc/modprobe.conf to pass the hide parameter to pciback
 
# hide (0000:05:02.0)
options pciback hide=(0000:05:02.0)
# hide more pci devices
options pciback hide=(0000:05:02.0)(0000:07:00.0)(0000:07:00.1)(0000:00:1d.0)
On its own, that will only work if no driver is loaded for the PCI function before pciback. That is, it won't unbind a driver that's already bound to it. So it's necessary to make sure that pciback is loaded before any such driver. Supposing that the usual driver for the PCI function is skge, we can make that happen by adding a line like this:
 
install skge /sbin/modprobe pciback ; /sbin/modprobe --first-time --ignore-install skge
In other words, the above says that whenever skge is asked to be loaded, pciback should be loaded first.
Note that to make use of this, a Linux kernel running in the guest domain has to have been compiled with pci frontend support. Look under "bus options (PCI etc)" for Xen PCI Frontend in the kernel configuration. 
Category:Xen
Category:Users
Category:HowTo
Assign hardware to DomU with PCIBack as module

#REDIRECT Assign Hardware to DomU with PCIBack as module
__NOTOC__
If the Dom0 XenLinux kernel is built with pciback as a module, attempting to use the kernel command-line parameter pciback.hide won't work. This includes loading pciback in an initrd. This means that if you wish to assign hardware to a DomU another method is needed.
There are two possibilities.
# Use late binding as described in section 5.3.1.3 of the user manual and put something like the following in an init script (/etc/rc.local will work on Fedora) to be executed before Xen domains. You can find the correct value for $BDF using lspci. For more information on BDF notation see Self:BDFNotation.
 
<nowiki>
BDF=0000:05:02.0
# Unbind a PCI function from its driver as necessary
[ ! -e /sys/bus/pci/devices/$BDF/driver/unbind ] || \
 echo -n $BDF > /sys/bus/pci/devices/$BDF/driver/unbind
# Add a new slot to the PCI Backend's list
echo -n $BDF > /sys/bus/pci/drivers/pciback/new_slot
# Now that the backend is watching for the slot, bind to it
echo -n $BDF > /sys/bus/pci/drivers/pciback/bind</nowiki>
 This has the disadvantage that if pciback is unloaded for any reason, you'll have to do it again.
# Add a line to /etc/modprobe.conf to pass the hide parameter to pciback
 
<nowiki>
# hide (0000:05:02.0)
options pciback hide=(0000:05:02.0)
# hide more pci devices
options pciback hide=(0000:05:02.0)(0000:07:00.0)(0000:07:00.1)(0000:00:1d.0)
</nowiki>
 On its own, that will only work if no driver is loaded for the PCI function before pciback. That is, it won't unbind a driver that's already bound to it. So it's necessary to make sure that pciback is loaded before any such driver. Supposing that the usual driver for the PCI function is skge, we can make that happen by adding a line like this:
 
<nowiki>
install skge /sbin/modprobe pciback ; /sbin/modprobe --first-time --ignore-install skge</nowiki>
 In words, the above says that whenever skge is asked to be loaded, pciback should be loaded first.
Note that to make use of this, a Linux kernel running in the guest domain has to have been compiled with pci frontend support. Look under "bus options (PCI etc)" for Xen PCI Frontend in the kernel configuration. At time of writing, the Fedora kernel-xen rpm for x86_64 2.6.17-1.2157_FC5.x86_64.rpm is compiled with it off.
Automotive Requirements

== Automotive Requirements ==
Automotive functions requirements for virtualized ECUs (copied from the AGL whitepaper)
=== Computing ===
* C1: Static resource partitioning and flexible on-demand resource allocation (CPU, RAM, GPU and IO).
* C2: Memory/IO bus bandwidth allocation and rebalancing.
=== Peripherals sharing ===
* P1: GPU and displays shall be shared between execution environments supporting both fixed (each one talks to its own display or to a specified area on a single display) and flexible configurations (shape, z-order, position and assignment of surfaces from different execution environments may change at run time).
* P2: Inputs shall be routed to one or multiple execution environments depending on current mode, display configuration (for touchscreens), active application (for jog dials & buttons), etc.
* P3: Audio shall be shared between execution environments. Sound complex mixing policies for multiple audio streams and routing of dynamic source/sink devices (BT profiles, USB speakers/microphones, etc.) shall be supported.
* P4: Network shall be shared between execution environments. Virtual networks with different security characteristics shall be supported (e.g., traffic filtering and security mechanisms).
* P5: Storage shall support static or shared allocation, together with routing of dynamic storage devices (USB mass storage).
=== Security ===
* SE1: Root of Trust and Secure boot shall be supported for all execution environments.
* SE2: Trusted Computing (discrete TPM, Arm TrustZone or similar) shall be available and configurable for all execution environments.
* SE3: Hardware isolation shall be supported (cache, interrupts, IOMMUs, firewalls, etc.).
* SE4: Secure updates shall be supported.
=== Performance and Power consumption ===
* PP1: Virtualization performance overhead shall be minimal: 1-2% on CPU/memory benchmarks, up to 5% on GPU benchmarks.
* PP2: Predictability shall be guaranteed. Minimal performance requirements shall be met in any condition (unexpected events, system overload, etc.).
* PP3: Execution environments fast boot: Less than 2 seconds for safety critical applications, less than 5 seconds for Instrument Cluster, and 10 seconds for IVI. Hibernate and Suspend to RAM shall be supported.
* PP4: Execution environments startup order shall be predictable.
* PP5: Advanced power management shall be implemented with flexible policies for each execution environment.
=== Safety ===
* SA1: System monitoring shall be supported to attest and verify that the system is correctly running.
* SA2: Restart shall be possible for each execution environment in case of failure.
* SA3: Redundancy shall be supported for the highest level of fault tolerance with fallback solutions available to react in case of failure.
* SA4: Real time support shall be guaranteed together with predictive reaction time.
Category:Safety_Certification
Category:Embedded and Automotive
Category:XenARM
Automotive Whitepapers

* The Automotive Grade Linux Software Defined Connected Car Architecture 2018-06-18, multiple contributors
* Driver Domain on ARM by Andrii Tseglytskyi 2015-08-06, GlobalLogic
* RT-Xen on ARM by Denys Drozdov 2015-03-10, GlobalLogic
* Device Passthrough to Driver Domain in Xen by Yurii Konovalenko 2015-02-25, GlobalLogic
* Managing co­processors for Linux PV domains by running a Xen hypervisor on ARM platforms by Andrii Tseglytskyi 2015-01-14, GlobalLogic
Category:Embedded and Automotive
Category:OpenEmbedded
Category:XenARM
Category:Whitepapers
BackendDriver

__NOTOC__
To allow unprivileged DomUs to share hardware, Dom0 must give them an interface by which to make requests for access to the hardware. This is accomplished by using a BackendDriver. The BackendDriver runs in Dom0 or a DriverDomain and communicates with FrontendDrivers via XenBus, XenStore, and shared memory pages. It queues requests from DomUs and relays them to the real hardware driver.
== See also ==
* Assign hardware to DomU with PCIBack as module
Category:Xen
Category:Glossary
Blktap2

= Xen blktap2 driver =
Xen blktap2 is a successor to the old blktap1 disk backend driver. See blktap wiki page for information about the old blktap1.
Xen blktap2 support is included in the Xen version 4.0 released in Apr 2010.
This wiki page is still under construction. Feel free to contribute/fix things!
== Usage ==
Example for Xen 4.0.0 "/etc/xen/<guest>" cfgfile for RAW images:
disk = [ "tap:tapdisk:aio:/path/images/disk.img,xvda,w" ]
Example for Xen 4.0.0 "/etc/xen/<guest>" cfgfile for VHD images:
disk = [ "tap:tapdisk:vhd:/path/images/disk.vhd,xvda,w" ]
Example for Xen 4.0.0 "/etc/xen/<guest>" cfgfile for QCOW2 images:
disk = [ "tap:qcow2:/path/images/disk.qcow2,xvda,w" ]
Notice: In Xen 4.0.0/4.0.1 don't mix file and tap simultaneously, in this case domU unable to see any disk device. May be bug or feature!
To define ISO images use:
disk = [ "tap:qcow2:/path/images/disk.qcow2,xvda,w","tap:tapdisk:aio:/path/images/somedistro.iso,xvdb,r" ]
== Changes in Xen 4.0.1 blktap2 support ==
Example for Xen 4.0.1 "/etc/xen/<guest>" cfgfile for RAW images:
disk = [ "tap2:tapdisk:aio:/path/images/disk.img,xvda,w" ]
Example for Xen 4.0.1 "/etc/xen/<guest>" cfgfile for VHD images:
disk = [ "tap2:tapdisk:vhd:/path/images/disk.vhd,xvda,w" ]
== VHD support ==
More information about VHD support can be found from the README file below.
== Dom0 kernel drivers for blktap2 ==
blktap2 functionality requires support from Xen tools and also a blktap2 driver in the dom0 kernel.
Please see Xen Kernel Feature Matrix wiki page for more information about Xen kernels having blktap2 driver.
== Documentation ==
Latest blktap2 README from xen-unstable source repository: http://xenbits.xensource.com/hg/xen-unstable.hg/file/tip/tools/blktap2/README
== Links related to blktap2 ==
* Announcement of the blktap2 patches with information about features: http://lists.xensource.com/archives/html/xen-devel/2009-02/msg00721.html
* blktap2 patches that were merged into xen-unstable in May 2009 for Xen 4.0.0: http://lists.xensource.com/archives/html/xen-devel/2009-05/msg00966.html
Category:Xen
Category:Users
Category:Developers
Category:HowTo
Blktap3

== Overview ==
blktap3 is an improved version of blktap2. The main difference between blktap2 and blktap3 is that the tapdisk process running in dom0 is directly connected to blkfront, which means that blkback is no longer on the datapath longer in this configuration. The primary goal of blktap3 is to remove the burden of maintaining the blkback/blktap kernel modules in dom0.
Apart from simplified maintenance, blktap3 should (in theory) be faster than blktap2 since the datapath is shorter. However, some preliminary evaluation indicates that blktap3 is marginally slower than blktap2; evidence suggests that this is because of some inefficiencies that are rather easily addressable.
== Using blktap3==
blktap3 is not yet in upstream Xen (patches are sent from time to time).
To use blktap3 (you don't have to reinstall Xen or reboot, and blktap3 nicely coexists with blktap2):
# Apply all blktap3 patches (they live in https://bitbucket.org/tmakatos/blktap3-patches)
# cd into tools/blktap3 and run make install
# cd into tools/libxl and run make install
# Run the tapback daemon (run tapback -D for easier debugging)
# Modify your guest domain configuration to use the tap3 device instead of the tap one
Category:Xen
Category:Developers
Book/HelloXenProject/0-Contents

Title and Credits
Chapter 1: A Brief History of Virtualization
Chapter 2: Xen Project
Chapter 3: Dom(s) and Grub 
Chapter 4: Using Xen Project 
Chapter 5: Have Fun with The Xen Project 
Cover : The front cover of "Hello Xen Project" book 
Category:Users Category:HelloXenProjectBook
Book/HelloXenProject/0-Credits and Title

= Hello Xen Project =
== Credits ==
=== Original Author and Editor ===
* Author: Mohsen Mostafa Jokar
* Editor: Rashad Williams
For my parents
- Mohsen
I dedicate this book to my lovely wife Candice Williams and my mom Jean Williams
-Rashad
=== Subsequent Contributions ===
* Lars Kurth: Imported chapter 1 and established the process of copying the book
== License ==
A note about this book:
This book, Published under “CC-BY-SA-3.0” license. For more information you can visit https://freedomdefined.org/Licenses/CC-BY-SA-3.0 . The goal of this book is helping newbie users for learning Xen Project and invite advanced Xen Project users for improving the contents of this book and add more topics to it. I hope this book can help Xen Project users to learn it better and Paying off others to move to Xen Project and use it.
Category:Users Category:HelloXenProjectBook
Book/HelloXenProject/Instructions for Improvement

The content of the wiki page has now been converted. 
== General Improvements ==
But there are a number if areas which could do with improvements
* Empty spaces between chapters: the conversion left many \n in documents. These mean that extra empty space is added between chapters. These can be easily deleted
* Code or config file snippets are currently not specifically formatted or formatted in <nowiki>...</nowiki> blocks. The best way to do this is to use <syntaxhighlight lang="sh">...</syntaxhighlight> instead
* If you come across bullets like ●, replace with proper mark-up, aka: * 
* If you come across unnecessary ... blocks, feel free to remove
* Feel free to fix up badly formatted tables (see 1 and use class prettytable)
== Specific Issues ==
* Chapter 1 does not render with the built in Special:Book generator. Probably due to the table being too large. When using external book renderers, the tick boxes in Book/HelloXenProject/1-Chapter#Compare_Virtualization_Software do not render correctly.
Category:Users Category:HelloXenProjectBook
Book/HelloXenProject/Reference

== Reference ==
* https://en.wikipedia.org
* http://www.dummies.com
* http://www.cyberciti.biz
* http://www.linuxjournal.com
* http://www.itworld.com
* https://www.linux.com
* http://virt.kernelnewbies.org
* http://wiki.xen.org
* http://www.pcmag.com
* https://wiki.debian.org/Xen
* https://www.suse.com
* https://www.centos.org
* http://support.citrix.com
* http://selinuxproject.org
* http://danwalsh.livejournal.com
* https://www.howtoforge.com
* http://www.datacenterknowledge.com
* http://www.datamation.com
Category:Users Category:HelloXenProjectBook
Books

__NOTOC__
== Books in English ==
=== Xen Project ===
* Hello Xen Project by Mohsen Mostafa Jokar, 2017
* The Book of Xen, by Chris Takemura and Luke S. Crawford, October 2009, 312 pp. ISBN-13 978-1-59327-186-2, No Starch Press
** Book of Xen Wiki Edition
** Chapter 7 Sample Text
* The Definitive Guide to the Xen Hypervisor, by David Chisnall (Prentice Hall; November 9, 2007; hardcover: 320 pages)
** Chapter 6 Sample Text: Understanding Device Drivers
* Running Xen: A Hands-on Guide to the Art of Virtualization, by Jeanna Neefe Matthews, Eli M. Dow, Todd Deshane, Wenjin Hu, Jeremy Bongio, Patrick F. Wilbur, and Brendan Johnson (Prentice Hall; May 5, 2008; paperback: 720 pages)
** Chapter 3 Sample Text: The Xen Hypervisor 
* Professional XEN Virtualization, by William von Hagen (Wrox; August 27, 2007; paperback: 500 pages)
* Virtualization with Xen: Including XenEnterprise, XenServer, and XenExpress, by David E. Williams (Syngress; April 1, 2007; paperback: 512 pages)
=== XCP ===
* Virtualization with Xen: Including XenEnterprise, XenServer, and XenExpress, by David E. Williams (Syngress; April 1, 2007; paperback: 512 pages), Jaroszlaw Zdrzalek, Ralph Dehner (OpenSourcePress, May 2007, 370 pages)
* Citrix XenServer 6.0 Administration Essential Guide, by Daniele Tosatto (Packt Publishing; June 25, 2012; paperback: 364 pages)
== Books in German ==
* Xen 3 ( German), by Andrej Radonic and Frank Meyer (Franzis; October 2006; 439 pages)
* Xen Virtualisierung unter Linux ( German), by Timo Benk, Henning Sprang, Jaroszlaw Zdrzalek, Ralph Dehner (OpenSourcePress, May 2007, 370 pages)
== Books in Chinese ==
* System Virtualization: Theory & Implementation ( Chinese) by Intel R&D Team 
== Books in Japanese ==
* Xenoppix ( Japanese) -- Knoppix customized with Xen
* A new book + DVD ( Japanese) has been published in Japan called Chou Kanntan Xenoppix (Chou Kanntan means Super Easy)
Category:Xen
Category:Community
Category:Users
Category:Beginners
Category:Developers
Category:XCP