nyuuzyou/wikis huggingface dataset:
Xen FAQ Drivers, Windows

=== What is the Windows PV Driver Subproject/team? ===
This project has taken the the XenServer Windows PV Drivers, re-written them and contributed them to the Xen Project. The Windows PV Driver Subproject is developing these drivers under Xen Project governance. One of the reasons to do this, is to make the drivers more easily signable and distributable via the Windows driver update mechanism. Note that the subproject is not maintaining the GPL PV drivers.
You can find drivers at the Xen Project download page.
=== What are the GPLPV Drivers and where can I get them? ===
A collection of open source Window PV drivers that allow Windows to be para-virtualized. They are currently being implemented under the leadership of James Harper. More information on
these drivers at:
* Downloads
* Signed drivers from univention.de
* Installing the GPLPV Drivers
* GPLPV Home page
=== How can I tell if the GPLPV Drivers are loaded correctly? ===
If the drivers are installed correctly there should be a Xen Project device under 'System Devices' in device manager.
=== Can I get signed GPLPV Drivers? ===
Yes, you can get signed GPLPV drivers from univention.de and from ::Category:Windows PV Drivers.
Category:Xen
Category:FAQ
Category:Users
Category:Beginners
Category:Fundamentals
Category:Windows PV Drivers
Category:Drivers
Xen FAQ General

== What is the Xen Project Hypervisor? ==
The Xen Project Hypervisor is a virtual machine monitor (VMM) for x86-compatible computers. The hypervisor can securely execute multiple virtual machines, each running its own OS, on a single physical system with close-to-native performance. You can find an overview at Xen Project Software Overview.
== I'd like to read some kind of overview about Xen Project software ==
See the Xen Project Software Overview wiki page and :Category:Overview. Also check the following PDF documents (which are somewhat out-of-date):
* http://www.xen.org/files/Marketing/WhatisXen.pdf
* http://www.xen.org/files/Marketing/WhyXen.pdf
* http://www.xen.org/files/Marketing/NewtoXenGuide.pdf
* http://www.xen.org/files/Marketing/HowDoesXenWork.pdf
== How is the Xen Project software licensed? ==
Xen Project software is Open Source, and is released under terms of the GNU General Public License v2. Some Xen Project elements may contain licensing exceptions or a small number of files which are licensed under a GPL compatible license. If so, the source repository contains a COPYING file providing more information (see here for the COPYING file for the hypervisor).
Xen Project software does not come with an End User License as the GPL suffices. There is however a trademark policy that restricts the use of the Xen Project brand to ensure that all Xen Project branded hypervisors are compatible and will run the same guest VMs. You can find the trademark policy here. 
There is a separate trademark for Xen alone. That trademark is owned by Citrix, which controls the use of that mark.
Operating systems or other applications written to use Xen Project's hypercall interface are not derived works of Xen Project, hence may be licensed differently.
== Where can I read about the history of the Xen Project? ==
Please see the history article on the main XenProject.org website.
== Where do I find information on Compatibility? ==
You can find answers to questions such as the following, at Xen Project FAQ Compatibility:
* Which OSes run on the hypervisor?
* Does Xen Project support Microsoft Windows? 
* Does Xen Project run on laptops?
* Which architectures does Xen Project support? 
* Does Xen Project support 32bit and 64bit?
== Where do I find more General FAQs? ==
See the common problems document
Category:Xen
Category:FAQ
Category:Users
Category:Beginners
Xen FAQ Guest Conversion

=== How do I convert a Centos HVM Guest to a PV Guest? ===
Creating a Centos HVM domU with working PV drivers : http://pastebin.com/fb6fe631
Converting HVM guest to PV guest : http://pastebin.com/f6a5022bf
If you follow both parts correctly you should have a working PV domU. If anything goes wrong during conversion process, you should still be able to boot the previous HVM domU config if you select the non-xen kernel (second entry) from grub menu.list.
Category:Xen
Category:FAQ
Category:Users
Category:Beginners
Xen FAQ Help

== Where do I find documentation on Xen? ==
On this wiki: the following places are useful to start
* Overview 
* Xen Beginners Guide
* Getting Started and Installs
* Xen Features
* Information on Compatibility 
* Xen or XCP?
* Video Tutorial
* Xen Manuals
* Best practices for running Xen
For info on navigating the wiki see:
* Wiki Help
* Indexes to navigate the Wiki
== What support is available for Xen? ==
There is both paid and volunteer support available for Xen. Volunteer support is available via 
# The Xen mailing lists 
# On Internet Relay Chat (IRC) channel ##xen on irc.freenode.net 
#A search tool is available to search all Xen mailing lists.
Commercially support for Xen is typically only provided for commercial distributions of Xen. Also some Linux distributions commercially support Xen.
== Where can I find a list of available Xen dom0 kernels? ==
Take a look at the Dom0 Kernels for Xen wiki page.
== Where can I find answers to some common questions and problems about Xen? ==
Take a look at the Xen Common Problems wiki page.
== Where can I find Best Practices about running Xen? ==
Take a look at the Xen Best Practices wiki page.
== I'm interesting in being a Xen developer, is there a list of projects to work with? ==
Yes! Please check out the Xen Development Projects wiki page for more information!
== Where and how can I report a bug? ==
See
* Reporting Bugs against Xen
* Reporting Bugs against XCP
== Where and how can I submit a patch? ==
See
* Submitting Xen Patches
* You may also need to know Xen Repositories and Asking Xen Devel Questions
In a nutshell, you submit a patch in plain-text unified diff format with a discription by sending it to the xen-devel mailing list. Xen also requires you to sign 
the change with
<nowiki>
Signed-off-by: Name Surname <email@domain>
</nowiki>
at the end of the change description. This is required and indicates that you certify the patch under the Developer's Certificate of Origin.
Category:Xen
Category:FAQ
Category:Users
Category:Beginners
Xen FAQ Installation

= File Systems =
== Is there a way to have a shared root file system amongst a set of guest VMs? ==
Yes, the best way to achieve this is to install your guest with an LVM-backed block device. You can then create a snapshot of this filesystem, with the command:
lvcreate -L<size of snapshot> -s -n <snapshot name> <backend disk name>
You should create one snapshot per guest, and then put the snapshot into the guest's .cfg file.
Using snapshots allows you to avoid having to make a read-only root filesystem. However, should you wish to use a read only root fs, you can install the OS in an LVM partition and use it shared across all the xen domUs when you use the parition as 'r' instead of 'w' when defining the disk.
== Will I get good I/O performance if I use a file-backed (.img) block device? ==
No. Using lvm to create a volume, and using the 
disk=['phy:/...']
method in your .cfg file will yield better performance. This is particularly important for I/O intensive VMs, such as databases.
== How can I make disk resizing work? ==
I tried to resize a disk of my data guest from 100 to 400 GB. I did an lvresize
/dev/xendata/data-disk -L 400G an it works. I started the Guest and did an df -h to check the size but there are still 100 G
The container is bigger but the filesystem isn't. Resizing an LV doesn't make the FS any bigger.
Log into the DomU and do a resize2fs <device>. You can do this while it's mounted as long as the filesystem is getting bigger.
Oh, and if you've partitioned the LV inside the guest, you'll also need to resize the partition (BEFORE you do a resize2fs, etc.). There are two ways to do this - the safest is to use parted, which works if you're using ext2/ext3 (and a couple other of the most popular filesystems - reiser, I think). The other method is to delete the partition and recreate it with the extended end points. This isn't quite as safe and requires that 1) your start point for the partition is exactly the same as it was before, and 2) the partition is the last (or only) one on the LV.
== How do I overcommit storage? ==
This is a matter of what storage backend you use. If you use one of the following, you will be able to overcommit storage:
*sparse raw file (with file: or tap:aio:)
*qcow
*vmdk/vdisk (I think full support is only in newer Xen or Opensolaris)
*zvol (on Opensolaris)
If you use disk/partition/LVM for domU storage, you won't be able to.
= 32bit vs 64 bit =
== Is there any way to install 64Bit Linux DomU on 32Bit Linux Dom0? ==
Types of domU that can be run depends mostly on the hypervisor, and not dom0. So if you have a
64bit hypervisor, you should be able to run 32 and 64bit PV and HVM domUs, regardless whether dom0 is 32 or 64bit.
If you have 32bit dom0 and 32bit hypervisor, you should be able to run 64bit HVM domU, but not
64bit PV domU.
Category:Xen
Category:FAQ
Category:Users
Category:Beginners
Xen FAQ Linux Distributions

== What Debian packages do I need for Xen? ==
To run Xen and a single OS from a binary release you need install no extra packages. To build Xen, XenLinux and documentation from source you will need: make, libncurses5-dev, libncurses5, gcc, libc6-dev, zlib1g-dev, python, python-dev, python-twisted, openssl, openssl-dev, bridge-utils, iproute, libcurl3, libcurl3-dev, bzip2, module-init-tools, latex, latex2html, transfig, and tgif.
== How do I fix the 4gb seg fixup messages in my syslog? ==
 These messages are from a glibc that was built with negative GS register offsets. Xen can run with negative GS register references, but it must "trap and emulate" this condition, which is relatively resource intensive, and quite slow. If you don't have a patched glibc, see the no-tls-direct-seg-refs patch mentioned in XenSpecificGlibc. Most newer distributions are shipped with a "-mno-tls-direct-seg-refs" compiled glibc, but it might not be enabled by default. Some newer distributions like the RHEL5 Beta1/Beta2 require the ld.so.conf.d trick below to refer to the patched glibc. Some slightly older distributions like Ubuntu Dapper can be fixed with a simple rebuild of glibc: (see UbuntuDapperHowTo).
<nowiki>
 echo 'hwcap 0 nosegneg' > /etc/ld.so.conf.d/libc6-xen.conf && ldconfig
</nowiki>
Reference Link: http://lists.xensource.com/archives/html/xen-users/2006-11/msg00026.html and http://www.mail-archive.com/fedora-xen@redhat.com/msg00041.html 
== Where do I find more information about Xen and my favorite Linux/Unix distro? ==
Ubuntu
* Virtualization help page
* Xen wiki page
* Xen help page
Debian
* Xen wiki page
* Debian Xen package development list
Fedora
* Virtualization Wiki page
* Xen list
* Virtualization list
CentOS
* Xen lists
* Xen wiki page
* There are also other Xen-related pages on CentOS wiki... see search
OpenSUSE
* Xen lists
* Xen wiki page
Gentoo
* Xen wiki page
Arch Linux
* Xen wiki page
NetBSD
* Xen list
* Xen wiki page
FreeBSD
* Xen wiki page
Solaris
* Xen wiki page
Category:Xen
Category:FAQ
Category:Users
Category:Beginners
Xen FAQ Nesting

== Can I run Xen within Xen? ==
Yes, You can install Xen on the base system, create a HVM domain, and install Xen in that guest domain. Note that the inner Xen system will not (yet) support HVM again.
== What is the status of Nested Virtualization in Xen? ==
See this XenSummit presentation outlining the status from Intel - applies to Xen 4.2 (and 4.3): Nested Virtualitaion Update from Intel
Category:Xen
Category:Users
Category:Developers
Category:FAQ
Xen FAQ Security

= How do I restrict/bind the network card to domU witha firewall? =
If I install minimal linux for XEN in dom0 and a periphery firewall in domU and other applications in other instances of domU, is it possible to restrict/bind the network card to domU having periphery firewall and from there forward packets for dom0 or for other domUs? 
Is this possible? If so, is it secure? Or does dom0 always have direct access to Network Card and needs a separate firewall? And packets will always route from dom0 to all domUs ?
What are the issues involved?
Answer: The approach I've used at home is to hide a network card from Dom0 (see pic-back.hide) and pass it through to a DomU which then sees it as a native interface. I then run a firewall in the DomU and the outside traffic does NOT go through Dom0. The route for packets is then :
<nowiki>
real i/f -> DomU (firewall) -> VIF -> int bridge [ Dom0 | VIF -> DomU ]
</nowiki>
From security perspective, this is the same as having an L2 switch (when dom0's bridges have no IP
address) or L3 switch (when dom0's bridges have an IP address)
= Is Disk Encryption with Truecrypt or Loop-aes better? =
I want to use a Disk Encryption and the conplete physikal Disk in a DomU. I prefer
Truecrypt or Loop-aes. i will going to test loop-aes cause it should have the better performance. But, did anybody here using truecrypt or loop-aes ? What is the better one, in the fact of speed ?
Answer: dm-crypt/luks is one option, and performs about the same or better than loop-aes. Also it's less problematic because it doesn't use loop devices
Category:Xen
Category:FAQ
Category:Users
Category:Beginners
Category:Security
Xen Mailing List Moderators

== Volunteers Wanted ==
Most XenProject.org mailing lists are moderated for non-subscribers, primarily
as a SPAM prevention measure. We are a little short of moderators at the
moment which means that sometimes mails for genuine posters who happen
to not be subscribed get delayed for a few days.
We are looking for volunteers to help out with this, it should be a
couple of a minutes each day to clear out any SPAM which has made it
through the automated filters and accept the posts from non-subscribers.
* Moderating a specific list on a specific day per week
* Moderating a specific list at a specific time of day
If interested, please get in touch with community.manager@xenproject.org.
== Policy ==
The basic policy for moderation is:
* reject and blacklist spam, accept and whitelist everything else.
Most of the SPAM which gets through the filters is still pretty obvious
to the human eye and there are generally only a small number each day so
it is usually a pretty quick job.
Most of the regular articles are easily identifyable by title. Only rarely is 
it necessary to read the body of each message. 
== Moderator Resources ==
== Help ==
* Mailman docs on moderation
* Email commands quick reference
== List Moderators ==
* Nui Xinli, Beijing, UTC+8
* Jin Tong Lei, UTC+8 
* Olaf Hering, UTC+2 
* Juergen Gross, UTC+1
* Andrew Cooper, UTC
* Lars Kurth, UTC
* James Tripplet, US East
* Nick Hardiman, UTC
== Previous List Moderators ==
* Andrew Finkenstadt, US central
* Todd Deshane, US east
Category:Community
Xen Maintainer, Committer and Developer Meeting/April 2013 Minutes

= Attendees =
* Lars Kurth (Citrix)
* Ian Campbell (Citrix)
* James Bulpin (Citrix)
* Konrad Rzeszutek Wilk (Oracle)
* Boris Ostrovsky (Oracle)
* Olaf Hering (SuSE)
* Jan Beulich (SuSE)
* Sherry Hurwitz (AMD)
* Donald Dugger (Intel)
* Mike Woster (Linux Foundation)
* Brian Warner (Linux Foundation)
* Daniel De Graaf (NSA)
* Andres Lagar-Cavilla (GridCentric)
= Standing Agenda =
* Call membership (new organisations to invite, +/- representatives from existing organisations, etc).
** None
* Review DONE ACTION items.
** DONE: MSI-X issue.
** REMOVED: Handling of functional degradation: Citrix asked to remove it and they will reintroduce it when more concrete findings are found.
** DONE: Event channel scalability. Xen 4.4 will have the FIFO system and the expanded event channel system is not going to be developed further for Xen 4.3.
* NEW ACTION items.
** Intel (Donald) to look at VPMU undocumented quirks: http://article.gmane.org/gmane.comp.emulators.xen.devel/154718
** Citrix (Ian) to remind George about posting the Xen 4.3 status and a Changelog
** Citrix (Lars) to post on April 15th the details of Xen Project and also the changes to the Xen Governance Document on xen-devel.	
** Oracle: Poke George about moving the code freeze date and/or clarify what is meant by "new code".
* Current technical challenges.
** NONE
* Coordination on current and future work, e.g. planned development activities for next release(s), roadmap 
** Xen Project. The Linux Foundation (Mike) will provide a neutral umbralla for trademark, marketing, events, travel, etc. The development process is NOT going to change and the meritocracy is going to remain untouched. 
** Lars pointed out that the Xen Governance Document needs to be updated. Mainly to add the Xen Project AB and also clarify the Last Resort Chairman. There are further changes that need to be done and those changes will be posted on Xen devel mailing list. Changes that Lars mentioned were in regards to who can be a Mentor, Project Leads, etc.
** PVH for Xen 4.3. Konrad mentions that it looks unlikely that the PVH code will make it in Xen 4.3 as the code-freeze is right around the corner and it is still in the early phases of reviews. Ian mentioned that it should go in the Xen 4.4 early.
* Community news, activities.
** April 15th is when Linux Foundation announces Xen Project.
** April 15th is code freeze for Xen 4.3
Category:Technical Coordination Team
Xen Maintainer, Committer and Developer Meeting/August 2012 Minutes

== Attendees ==
Ian Campbell
Boris Ostrovsky
Sherry Hurwitz
Jason Douglas
James Bulpin
Jan Beulich
Donald Dugger
Kurt Hackel
== 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
* 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
: (OPEN) Some work has been done here
* UEFI
: Kurt: The person who is going to be working on this has been finishing up some kexec work which has delayed UEFI stuff
: One of the main things will be secure boot
* Hybrid
: Mukesh's Linux tree is in good shape.
: Last case (hybrid dom0 + PVHVM guest) is now working.
: Xen patch is on the way -- posting before XenSummit.
== Topics Discussed ==
=== 4.0.x and 4.1.x releases ===
* Jan: Latest RCs have been sitting for a couple of weeks
ACTION: Ian to ping Keir and provoke either new RCs or actual releases
=== Time based releases ===
* Sherry: Would allow alignment with hardware releases and planning
* James: Also helps with XenServer planning
* Jan: There are pro and cons, e.g. releasing just because 6 months has passed even though there may be nothing of particular interest in the tree
* James: A short list of "headline features" would help
*Jan: Need to consider if 6 months is the correct cadence, previously we have aimed for 9 months. Need to consider the overhead of the release process.
To be discussed further at development day meeting
=== Calls with no agenda ===
What should we do if there is no particular agenda on a given month
* James: The development meeting in two weeks has cannibalised from the agenda this month, unlike to be this quiet every month
* Jan: Reviewing the ACTIONS from last time is valuable in its own right
* Don: Even "not done" is useful since it helps motivate people.
Conclusion: Better to have a very short call than to cancel.
Category:Technical Coordination Team
Xen Maintainer, Committer and Developer Meeting/December 2012 Minutes

= Minutes =
== Attendees ==
* Ian Campbell
* Matt Wilson
* Daniel De Graaf
* Boris Ostrovsky
* Olaf Herring
* Sherry Hurwitz
* Lars Kurth
* Konrad Rzeszutek Wilk
* Donald Dugger
* Jun Nakajima
* Jan Beulich
Apologies:
* James Bulpin
== Review of ACTION items ==
* Konrad has posted to xen-devel RE PV ops discussion at kernel summit
* Konrad is also looking at improvements to the blk protocol
** Still a Work in progress.
** Goal is 1,000,000 IOPS to a block device.
** Will investigate generic ring improvements made in netchannel2.
** ACTION: Konrad to take the discussion to xen-devel.
== Coordination of current and future work ==
=== Patch Review ===
* Jan noted that it is hard to get review / ack on generic IOMMU code or the Intel/AMD specific portions.
** Intel situation has improved since this item was added to the agenda.
** Intel offered to maintain the generic code as did Jan.
*** ACTION Intel/Jan to send a patch against MAINTAINERS for generic IOMMU parts
** AMD are in the process of nominating a new maintainer after personnel changes.
*** ACTION AMD to nominate a new maintainer for the AMD code.
* Jan also noted that this wasn't specific to the IOMMU code and that in general it is hard to get acks against code which has no maintainer, he raised the PVSCSI interface header as a specific example.
** If people care about the code then we should try and find a maintainer.
** Otherwise can solicit explicit NACKs before checking in after a week or so in rather than waiting for an ACK
** Also an option to remove code which is unmaintained and getting in the way.
== Community News ==
=== Hardware vendors membership of the security pre-disclosure list ===
* Sherry asked about what the criteria for membership was and if AMD should be a member
* The criteria/guidelines are listed on
http://www.xen.org/projects/security_vulnerability_process.html
* There is a discussion ongoing (on the lists) about relaxing the criteria to make them more inclusive.
* Strictly speaking hardware vendors are not eligible to be on the list, however where a bug is thought to be hardware related the security team would involve the appropriate vendor during the early stages of producing the fix and drafting the advisory text.
=== Call dial in details changing ===
* ACTION: Ian to send out new dial in details to everyone (DONE)
Category:Technical Coordination Team
Xen Maintainer, Committer and Developer Meeting/March 2013 Minutes

= Attendees =
* Ian Campbell
* Daniel De Graaf
* Jan Beulich
* Konrad Rzeszutek Wilk
* Boris Ostrovsky
* Matt Wilson
* Olaf Herring
* Sherry Hurwitz
= Review of ACTIONS =
* MSI-X issue: Patch has been committed
* Handling of functional degradation: James to work with his team to evaluate previous instances of such issues and propose specific solutions/patches to enable this to be done differently going forward
** James not on the call, leave until next time.
** Clarification by mail: more urgent things have pre-empted it.
* 4.3 Release (PVH status)
** Konrad updated George re status
** Mukesh should be reposting by the end of the week
** Was relying a bit on slip due to event channels to give breathing space.
** ACTION: Konrad to follow up with Mukesh + raise the possibility of a slip on list.
* Event Channel Scalability:
** Citrix platform team (Wei) have resumed work on the 3 level stuff
*** Favour the existing code over the proposed but unimplemented alternative for 4.3
*** Core stuff is ok, mostly discussion of config option names etc (probably not an issue for the freeze)
** James not on call so no news RE XenServer team and QUEUE/FIFO model resourcing.
** Clarification by mail: We're spinning up an internal project to reserve resource for this. I'll update after our resourcing meeting next week.
= Current technical challenges =
* AMD are investigating a performance regression of WinXP as a guest
** Discussion has been on list
** Time seems to run at half speed for the guest
** Probably also an issue in 4.2
** A changeset has been fingered but it is hard to see why this affects time.
** Investigation ongoing, this is a high priority for AMD.
= Coordination on current and future work =
None
= Next call =
Konrad volunteered to send out the Agenda for next time in my absence.
Thanks Konrad!
Category:Technical Coordination Team