nyuuzyou/wikis huggingface dataset:
Books/pt-br

__NOTOC__
=== Livros sobre Xen ===
* The Book of Xen, de Chris Takemura e Luke S. Crawford, Outubro de 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 
* System Virtualization: Theory & Implementation ( Chinese) by Intel R&D Team 
* 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)
* 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)
* 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/pt-br
Category:Community/pt-br
Category:Users/pt-br
Category:Beginners/pt-br
Category:Developers/pt-br
Category:Languages/pt-br
Building XAPI for debian

#REDIRECT Compile the XCP toolstack from source
The easiest way to compile the XCP toolstack from source is to use the xapi-autobuilder. We usually run on a debian unstable or ubuntu 11.10 amd64 machine.
==Prerequisites==
Install the required packages:
apt-get install cowbuilder pbuilder debhelper dh-ocaml dh-autoreconf cdebootstrap python-debian git git-buildpackage omake ocaml-findlib
==Building==
First, clone the build scripts:
git clone https://github.com/jonludlam/xapi-autobuilder.git
cd xapi-autobuilder
The build scripts can build for several different distributions and architectures. To select, run 
export DIST=oneiric # or sid or precise
export ARCH=amd64 # or i386
Then run:
make
This will build all of the required packages for Xapi on Debian. Take a look at 'git-repos' to see which repositories are involved, and modify that to point to your own repositories if you plan on compiling your own code.
Building Xapi

= What is xapi ? =
= Who is this document for? =
# People wanting to compile xapi on Archlinux (I’m not talking about _running_ it, just compile it for now).
= Build from source prerequisites =
You will need:
# the normal build tools (yaourt -S base-devel, maybe more…)
# Xen 4.2 and blktap headers (yaourt -S xen blktap-git)
# the OCaml compiler (at least version 3.12.1)
# the OCaml package manager, OPAM
== Archlinux ==
 $ yaourt -S base-devel ocaml opam-git xen blktap-git
 $ opam-init
 $ opam remote add xen-dev git://github.com/xapi-project/opam-repo-dev
 $ opam install -y cdrom fd-send-recv forkexecd libvhd nbd netdev oclock ounit rpc ssl stdext syslog tapctl xen-api-libs-transitional xenctrl xenstore
 $ git clone git://github.com/vbmithr/xen-api.git
 $ git checkout archlinux
 $ git pull
 $ make
= Log =
* checkout branch ea-1254 from github.com:jonludlam/xen-api.git
* Add Arch in scripts/detect_distro.sh
* Use xenguest stubs from github.com:xapi-project/ocaml-xen-lowlevel-libs.git
Category:XAPI Category:HowToCategory:XAPI Devel
CD Rom Support in Xen

CDROM Support under Xen Guests
This page will give some information about CDROM support under Xen guests.
= PV Guest =
Currently, there's no paravirtual CDROM driver available. So in PV guest, you can only add a iso image as a disk and cannot change this disk at runtime. But as a workaround, you can detach it and re-attach another iso as the same frontend.
= HVM Guest =
== Adding CDROM to Guest ==
To add a physical CDROM drive or iso file as CDROM, you need to append ":cdrom" suffix to the target device name. Eg.
<nowiki>
disk = ['phy:/dev/sr0,hdc:cdrom,r']
disk = ['phy:/dev/hdc,hdc:cdrom,r']
disk = ['file:/test.iso,hdc:cdrom,r']
disk = ['phy:/dev/null,hdc:cdrom,r']
disk = [',hdc:cdrom,r']
</nowiki>
== Change CDROM for a running guest ==
If you attached a physical CDROM drive, the CDROM media in the guest will change automatically when you change it physically.
If it doesn't change, you can try a few things:
=== Reinsert cdrom from guest ===
Typically if the CDROM drive is not automatically detected by the guest it is due to the fact that eject / insert of the device is not propagated to the guest, this can be fixed, but to avoid dealing with that you can also just try to use the following commands from the guest:
To eject from the guest:
<nowiki>
# eject
</nowiki>
To detect the insertion of a new CD:
<nowiki>
# eject -t
</nowiki>
Playing with these two should in most cases resolve messaging issues.
=== Reinsert cdrom to guest from dom0 ===
Execute the following command in Dom0:
<nowiki>
# xl block-attach [DomID] "phy:/dev/hdc,hdc:cdrom,r"
</nowiki>
 or: 
<nowiki>
# xl block-attach [DomID] "file:/test.iso,hdc:cdrom,r"
</nowiki>
 if you want to bind an iso to a CDROM.
If you are using the SDL viewer, Inside the VM press the following key combination to get into the monitor:
<nowiki>
Ctrl-Alt-2
</nowiki>
And then use the following command to eject the CDROM:
<nowiki>
eject hdc [return]
</nowiki>
Now you should be able to eject the cd manually, and put in a different CD. Then type the following command to change CDROM for the guest:
<nowiki>
change hdb /dev/hdc [return]
</nowiki>
To get back to the VM gui, press:
<nowiki>
Ctrl-Alt-1
</nowiki>
The new disk should be ready for mounting.
== Booting from CDROM ==
To boot from CDROM, add config parameter "boot=c" to the vm configure file.
= Troubleshooting =
* Under certain circumstance, using /dev/cdrom, which is a symbol link to the actual device, doesn't work.
Category:Xen
Category:Users
Category:Beginners
Category:Overview
COLO - Coarse Grain Lock Stepping SLES

This page contaions detailed instractions on how to setup COLO on SLES11-SP3.
= Host installation =
On both primary and secondary hosts:
* Select "Xen Virtualization Host" when choosing host type.
* On package selection, please include build-essential packages like make, gcc and so on.
* After install the host OS, edit '/boot/grub/menu.lst', change the default booting option to Xen DOM0 kernel
* Uninstall xen-tools package:
yast2 --remove xen-tools
* Edit /etc/modprobe.d/unsupported-modules, add the following line:
allow_unsupported_modules 1
* Add the following package source by using yast2:
http://ftp5.gwdg.de/pub/opensuse/discontinued/distribution/11.3/repo/oss/suse/
http://occonnect.dk/repo/$RCE/SLE11-SDK-SP3-Pool/sle-11-x86_64
* Install git
yast2 --install git
* Download files that needed for next steps:
git clone https://github.com/wencongyang/colo-files
* Install RPMs under colo-files/libnl3
* compile and install act_mirred module:
#cd colo-files/act_mirred && make
#mkdir /lib/modules/3.0.76-0.11-xen/updates/
#cp act_mirred.ko /lib/modules/3.0.76-0.11-xen/updates/ && depmod
* Download and compile Xen
Checkout xen-colo source
#git clone https://github.com/wencongyang/xen
#cd xen && git checkout colo-v4-noheartbeat
Compile
#./configure
#make dist-xen; make dist-tools
Patch qemu and rebuild xen-tools
#cd tools/qemu-xen-dir/
#git am /path-to/colo-files/patch_for_qemu/0001-Introduce-xen-load-devices-state.patch
#cd ../../; make dist-tools
Install xen and xen-tools
#make install-xen; make install-tools
#chkconfig xencommons on
#reboot
NOTE: There might be some missing dependance, the main missing packages are the following, please install these first:
flex,python-devel, gettext-tools, dev86, libuuid-devel, libopenssl-devel, libyajl-devel, glib2-devel, libpixman-1-0-devel
* Compile and install colo agent (only needed on primary host)
#git clone https://github.com/wencongyang/colo-agent
#git checkout experimental
#make
#cp *.ko /lib/modules/3.0.76-0.11-xen/updates/ && depmod
= Guest installation =
Note the following steps should be done on primary host.
* Needed settings in Guest config file:
xen_platform_pci=0
* Select 'Physical Machine' when choosing host type.
= Run COLO =
Note the following steps should be done on primary host.
* Copy the new installed guest image to secondary host. Note that the image should be put in the same directory as it's in primary host.
* Load essential kernel modules:
modprobe ifb numifbs=10
modprobe sch_colo
modprobe sch_colo_ipv4
modprobe sch_colo_arp
modprobe sch_colo_icmp
modprobe sch_colo_tcp
modprobe sch_colo_udp
* Modify the guest config file:
** disk
disk = [ 'format=raw,devtype=disk,access=w,vdev=hda,backendtype=tap,filter=colo,filter-params=192.168.3.1:9000,target=/root/images/hvm/hvm_nopv/hvm.img' ]
** nic
vif = [ 'mac=00:16:4f:00:00:11, bridge=br0, model=e1000, forwarddev=eth0' ]
* Start guest
* Run COLO
xl remus -c -u <domname> <secondary host IP>
Category:High Availability
Category:Xen 4.5
CentOS 6 Virtual Machine installation on Xen

== Xen4 CentOS6 ==
* Release Announcement
* Release Notes
* Quickstart Guide
== CentOS Versions prior to 6.4 ==
* CentOS 6 Virtual Machine installation on Xen (32 bit)
* CentOS 6 Virtual Machine installation on Xen (64 bit)
Category:Xen
Category:Users
Category:Beginners
Category:HowTo
Category:Guest Install
Category:RefToExternalArticle
Category:CentOS
Ceph

From the Ceph documentation:
"Whether you want to provide Ceph Object Storage and/or Ceph Block Device services to Cloud Platforms, deploy a Ceph Filesystem or use Ceph for another purpose, all Ceph Storage Cluster deployments begin with setting up each Ceph Node, your network and the Ceph Storage Cluster. A Ceph Storage Cluster requires at least one Ceph Monitor and at least two Ceph OSD Daemons. The Ceph Metadata Server is essential when running Ceph Filesystem clients."
Ceph can be used with the Xen Project Hypervisor.
== DOCUMENTATION ==
* Using libvirt with Ceph RBD from the Ceph
* Ceph Wikipedia entry
== PRESENTATIONS ==
To see a video from Xen Project User Summit 2013 about Ceph architecture and using Ceph with Xen Project, see Ceph, Xen, and CloudStack: Semper Melior by Patrick McGarry (check out the slides here).
== PROJECTS ==
* Florian Heigl has created a project to provide simplified Ceph support
== HOWTOs ==
* Using Ceph on DomUs
* A mailing list post on configuring QDISK RBD/Ceph backend parameters
* The technology preview for Ceph and XenServer using libvirt
* A generic article on configuring The RADOS Object Store and Ceph Filesystem for virtualization (including Xen Project) and cloud
* A generic article on Turning Ceph RBD Images into San Storage Devices
Category:Ceph
Category:Integration
Checklist/Approving Ecosystem Listings

= When is it Needed? =
The Ecosystem pages on xenproject.org allow users to create listings. These need to be approved by an Administrator/Moderator
= Steps an Administrator/Moderator Needs to Perform =
== Step 1: Log into the web backend ==
Administrators will be told how to do this
== Step 2: Go to Mosets Trees ==
== Step 3: Chose Listing for Approval ==
== Step 4: Sanity Check, Fix errors and Approve (or Reject) ==
== Step 5: Find submitting user ==
== Step 6: Add user to vendor group ==
== Step 7: Update AcyMailing Vendor Mailing List ==
There are two parts to this step: first update the AcyMailing user database from the Joomla database, then update the Vendor Mailing List from the updated AcyMailing database.
From Joomla menu: select Component > AcyMailing > Users
Click the "Import" icon.
Select "Joomla Users"; do NOT select any list to subscribe - this is to update the AcyMailing User Database only
Click the "Import" icon.
It should give you a number of users added. Should be non-zero.
From the AcyMailing menus on the page: select Lists > Filters
Click "Add Vendors to Vendor List"
Click "Process" icon.
== Promotion on twitter ==
Make a note on twitter and let the community know that new vendor (you may need to go to their web page to check their twitter ID) is new on the ecosystem directory, linking to it. The tweet should include #xen and is intended to get more vendors to sign up.
Category:Community
Category:Checklist
Checklist/Creating Events

= Who can add events? =
Registered users of xenproject.org can add entries to the Event List. You should only add listings for:
a) CFP's for your project
b) If are giving a Xen related talk at an open source or industru event 
= Steps to Perform to add a listing =
== Step 1: Log into the website and go to the events list ==
* Log into xenproject.org
* Go to the Event List
== Step 2: Create an Event ==
== Step 3: Chose Event Details ==
Then save.
=== Notes ===
* If you advertise a CFP, make sure you include the Event Title and Looking for Xen submissions (or more specific to the title)
* If you advertise a Xen talk at an event, make sure you link to the actual talk (not the event)
* Also, please use the syntax for the button as highlighted above
 <a class="btn btn-info btn-big" href="Add URL HERE">More Info ...</a>
* Make sure you set the correct timezone and approximate the time to the closest 15 minutes as possible
= Once you created an event=
You can
* Change the image
* Edit the event
* Create an event from one of your existing events
Category:Community
Category:Checklist
Checklist/Invoicing the Xen Project

This page outlines the process of
* Quotes for the Xen Project
* Getting quotes approved
* Invoicing the Xen Project
== What needs to be on a quote and invoice ==
The billing address for the Xen Project is
The Linux Foundation
660 York Street, Suite 102
San Francisco, CA 94110
The quote/bill needs to contain a reference to the Xen Project, e.g.
Food bill for social event for Xen Project Hackathon
...
Items with cost breakdown underneath
Or
GNOME Outreach Program for Women summer 2014 session sponsor – Includer level for the Xen Project
== Getting Quotes ==
Community members (=requester of a quote) may act on behalf of the project and obtain quotes from vendors. Please make sure that quotes are structured in the way listed above.
Once the requester is happy with the quote, he/she will contact the community manager and ask for a board vote for approval.
== Approval ==
All Xen Project expenditure needs to be approved by the :Category:Advisory Board. The community manager will make a proposal for an expenditure to the Advisory Board and link it to an item in the budget. The board will approve in line with its voting rules.
The community manager, will keep track of approved expenditure in the project's budget
== Where to send invoices to (after approval) ==
E-mail your invoice to 
* the requester of the invoice (this is the person who acts on behalf of the Xen Project)
* AND the community manager: via community dot manager at xenproject dot org
The invoice will then be passed on to the right person such that it can get processed
Category:Checklist
Category:Advisory Board
Checklist/Kicking off Test Days

== Preparation ==
Make sure you are an OP for the #xentest day channel (asked one of the other OPs to change your status)
== Announcement ==
Well in advance, create a test day instruction page in the form: Xen_#.#_RC#_test_instructions. If this is not the first RC for the release, cut and paste text from the earlier RC as a starting point.
Make an announcement on the relevant mailing lists a few days before, stating the date and linking to
- Test Instructions
- Test Day page
Example: 
Make sure that a header such as
{{InfoLeft|The next [[Xen Project Test Days|Xen Project Test Day]] for [[Xen 4.3 RC2 test instructions|Xen 4.3]] is on May 22nd 2013}}
is added to Main Page and Xen Project Test Days. 
Add information about the next Test Day to the #xentest IRC channel title
Add event to XenProject.org Events.
Add event to Xen Facebook and Google+ pages.
== On the Day ==
=== Step 1: Main Page and Xen Project Test Days===
Add 
{{InfoLeft|[[Xen Project Test Days|Xen Project Test Day]] is today. See [[Xen 4.3 RC2 test instructions|Xen 4.3 RC2 test instructions]]}}
to Main Page and Xen Project Test Days
=== Step 2: Update topic of #xentest IRC channel ===
* Make sure that the headline states that today is test day
* You need to be a channel OP or ask a channel OP to do this
=== Step 3: Reminder mail ===
Send a reminder to the appropriate developer and user lists
=== Step 4: Remind people on IRC ===
* Join #xentest channel
* Remind people on relevant IRC channels (typically ##xen, #xen-api and #xen-devel)
* You will need to do this 2-3 times with an hour in between
== The day after ==
* Send a thank you mail
* Remove banners from Main Page and Xen Project Test Days or set to next Test Day
* Change #xentest channel title to the next known test day date
Category:Checklist
Category:Community
Checklist/Kicking off Xen Docs Days

== Initial Preparation ==
Make sure you are an OP for the #xendocs day channel (asked one of the other OPs to change your status)
== Announcement ==
Make an announcement on the relevant mailing lists a few days before, stating the date and linking to
- Docs Day TODO list
- Docs Day page
Make sure that a header such as
{{InfoLeft|The next [[Xen Project Document Days]] for is on May 28th 2013}}
is added to Main Page and Xen Project Document Days. 
Add information about the next Docs Day to the #xendocs IRC channel title
Add events to Facebook and Google+ pages.
Add event to XenProject.org Events section.
== Monthly Preparation ==
Find top contributors from past Doc Days. Contact them to thank them and encourage them to contribute again. Find out what they want to work on. Modify the TODO list to reflect same.
See what swag is available to reward top contributors for the upcoming Doc Day.
== On the Day ==
=== Step 1: Main Page and Xen Project Document Days===
Add 
{{InfoLeft|[[Xen Project Document Days]] is today. }}
to Main Page and Xen Project Document Days
=== Step 2: Update topic of #xendcos IRC channel ===d
* Make sure that the headline states that today is docs day
* You need to be a channel OP or ask a channel OP to do this
=== Step 3: Reminder mail ===
Send a reminder to the appropriate developer and user lists
=== Step 4: Remind people on IRC ===
* Join #xendocs channel
* Remind people on relevant IRC channels (typically ##xen, #xen-api and #xen-devel)
* You will need to do this 2-3 times with an hour in between
== The day after ==
* Add top contributors to Wall of Fame
* Send thank you email, announcing Wall of Fame additions, and recipients of swag
* Remove banners from Main Page and Xen Project Document Days or set to next Docs Day
* Change #xendocs channel title to the next known docs day date
Category:Checklist
Category:Community
Checklist/XenHypervisorRelease

This page is a checklist for Xen developers doing a release.
= Release checklist for release candidates =
= Disabling debug =
Sometime after the initial RCs, and before the final RC, disable debug by default:
In Config.mk, change
debug ?= y
to
debug ?= n
= Checklist for branching a release =
Here ${V} will be the version to be released, and ${V+1} stands for the next release. For example, ${V} might be 4.3, and ${V+1} would be 4.4.
== Create new branch for git and mercurial ==
* Create staging-${V} and stable-${V} branches in the main git repo
[Detailed instructions here]
== Update version numbers in the development branch ==
* Change the version number in xen/Makefile by setting XEN_VERSION and XEN_SUBVERSION appropriately.
* Update the ASCII art version in README
* Re-enable debug ?= y in Config.mk
== Update version numbers in the release branch ==
* Change the version number in xen/Makefile by setting XEN_VERSION and XEN_SUBVERSION appropriately.
* Remove '-rc' from the ASCII art in README
* Update url for qemu trees
In Config.mk, modify both instances of QEMU_UPSTREAM_URL and both instances of QEMU_REMOTE, replacing -unstable with -${V}
= Checklist for the final release =
Everything on this list must be done in advance of any public press release, preferably one week ahead of time, to allow for the announcement to be postponed if necessary.
* Create release tags for qemu
Create the tag qemu-xen-${V} for qemu-xen, and xen-${V} for qemu-traditional
* Update the qemu tags from a hash to a tag
In Config.mk, modify QEMU_UPSTREAM_REVISION and QEMU_TAG to the release tag for qemus (see above for exact names).
Category:Checklist
Clipboard sharing protocol

This protocol allows an in-guest agent to share clipboard data with dom0, so that it could be integrated with an emulated frame buffer, such as that exposed by qemu over VNC.
= Status =
Status: version 0.1 (early draft)
= Overview =
The protocol is intended to be used over a 'channel' with name: org.xenproject.guest.clipboard.0.1
The protocol is a subset of the VNC RFB protocol (http://www.realvnc.com/docs/rfbproto.pdf). Since the main expected use is to integrate with a qemu VNC frame buffer, RFB primitives should be readily available in the implementation.
We use only the following messages:
* ProtocolVersion
* SecurityVersion
* SecurityResult
* ClientInit
* ServerInit
* ClientCutText
* ServerCutText
= Protocol =
The backend acts as the RFB server, the guest acts as the RFB client.
* The server sends 'ProtocolVersion' with RFB protocol version 3.8
* The client sends 'ProtocolVersion' with RFB protocol version 3.8
* The server sends a single security type: None
* The server sends a 'SecurityResult' indicating success
* The client sends a 'ClientInit' message with shared = 1
* The server sends a 'ServerInit' message with the frame buffer size set to (0, 0) and any valid pixel format
We now consider the connection established. The following messages are now possible:
* The server sends a 'ServerCutText' when it wants to push data into the guest's cut buffer
* The client sends a 'ClientCutText' when it wants to push data into the server's cut buffer
Category:Development
Category:XAPI Devel
CloudStack

From the Apache CloudStack Documentation:
"CloudStack is an open source software platform that pools computing resources to build public, private, and hybrid Infrastructure as a Service (IaaS) clouds. CloudStack manages the network, storage, and compute nodes that make up a cloud infrastructure. Use CloudStack to deploy, manage, and configure cloud computing environments."
== DOCUMENTATION ==
* Using XenServer on Apache CloudStack from the Apache CloudStack documentation
* CloudStack Wikipedia entry
== PRESENTATIONS ==
* Ceph, Xen, and CloudStack as delivered at Xen Project User Summit 2013
== REFERENCES ==
* Proposal to provide direct support for Xen Project on CloudStack
Category:CloudStack
Category:Integration
Community Call

== When ==
1st Thu of each month @ 16:00 British Time, unless there is a major holiday
Look for announcements with Community Call in the title (posted on xen-devel@)
== I want to get notified of meetings and minutes ==
Sign up to our sign-up-sheet
== Dial-in details ==
Web: https://meet.jit.si/XenProjectCommunityCall
Dial-in info and pin can be found here:
https://meet.jit.si/static/dialInInfo.html?room=XenProjectCommunityCall
== Minutes ==
Can be found here or on xen-devel@
Category:Developers
Category:Events
Category:Community Meetings
Compile Mirage

This page describes how to use Mirage to build a xen kernel.
= Before you begin =
You need:
* a 64-bit Linux host (any modern distro should work)
* basic C compiler and tools (e.g. 'build-essential' on Debian)
* an OCaml compiler (any version)
Next you need to install OCaml and the OPAM package manager. Check out the OPAM Quick Install guide.
= Building the build environment =
First initialise opam
 opam init
Next, make sure you have OCaml 4.00.1 as your active compiler. If your compiler is out of date, just run opam switch to have it locally install the right version for you.
 $ ocaml -version
If the version is not 4.00.1 then run
 $ opam switch 4.00.1
 $ eval `opam config env`
At this point consider adding the 'eval' line to your shell's startup.
Finally, install the mirage-xen libraries and the build helper tool (Mirari)
 $ opam install mirage-xen mirari
= Building example kernels =
There are a number of example kernels in the mirage-skeleton repository. You can build them as follows:
 $ git clone git://github.com/mirage/mirage-skeleton
 $ cd mirage-skeleton
 $ make