<?xml version="1.0" encoding="utf-8"?>
<!-- generator="FeedCreator 1.7.2-ppt DokuWiki" -->
<?xml-stylesheet href="http://docs.solstice.nl/dokuwiki/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="http://docs.solstice.nl/dokuwiki/feed.php">
        <title>docs xen</title>
        <description></description>
        <link>http://docs.solstice.nl/dokuwiki/</link>
        <image rdf:resource="http://docs.solstice.nl/dokuwiki/lib/images/favicon.ico" />
       <dc:date>2010-09-08T14:39:28+02:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="http://docs.solstice.nl/dokuwiki/doku.php?id=xen:cpu&amp;rev=1183232396"/>
                <rdf:li rdf:resource="http://docs.solstice.nl/dokuwiki/doku.php?id=xen:creation_of_a_domu&amp;rev=1207384739"/>
                <rdf:li rdf:resource="http://docs.solstice.nl/dokuwiki/doku.php?id=xen:domu_backup&amp;rev=1183366706"/>
                <rdf:li rdf:resource="http://docs.solstice.nl/dokuwiki/doku.php?id=xen:installation_of_dom0&amp;rev=1210358947"/>
                <rdf:li rdf:resource="http://docs.solstice.nl/dokuwiki/doku.php?id=xen:live-migration_infrastructure&amp;rev=1202122446"/>
                <rdf:li rdf:resource="http://docs.solstice.nl/dokuwiki/doku.php?id=xen:pass_devices_to_the_domu&amp;rev=1209284174"/>
                <rdf:li rdf:resource="http://docs.solstice.nl/dokuwiki/doku.php?id=xen:pass_devices_to_the_dumu&amp;rev=1189404799"/>
                <rdf:li rdf:resource="http://docs.solstice.nl/dokuwiki/doku.php?id=xen:paused_backups&amp;rev=1183231670"/>
                <rdf:li rdf:resource="http://docs.solstice.nl/dokuwiki/doku.php?id=xen:start&amp;rev=1209363461"/>
                <rdf:li rdf:resource="http://docs.solstice.nl/dokuwiki/doku.php?id=xen:vmware2xen&amp;rev=1208433069"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="http://docs.solstice.nl/dokuwiki/lib/images/favicon.ico">
        <title>docs</title>
        <link>http://docs.solstice.nl/dokuwiki/</link>
        <url>http://docs.solstice.nl/dokuwiki/lib/images/favicon.ico</url>
    </image>
    <item rdf:about="http://docs.solstice.nl/dokuwiki/doku.php?id=xen:cpu&amp;rev=1183232396">
        <dc:format>text/html</dc:format>
        <dc:date>2007-06-30T21:39:56+02:00</dc:date>
        <title>xen:cpu</title>
        <link>http://docs.solstice.nl/dokuwiki/doku.php?id=xen:cpu&amp;rev=1183232396</link>
        <description>Para-virtualisation works on all x86 CPU’s made in the last years. For full-virtualisation, hardware support is required.

(on the Xen mailinglist on 15 februari 2007, Mats Petersson from AMD)

	*  The “pacifica” which is now caled AMD-V is fairly easy to determine - if it uses Socket F, Socket AM2 then it’s AMD-V compatible, unless it’s a Sempron processor. Another key would be to look at the memory type, as all DDR2 processors (excluding Sempron’s again) are AMD-V capable. 
	*  Int…</description>
    </item>
    <item rdf:about="http://docs.solstice.nl/dokuwiki/doku.php?id=xen:creation_of_a_domu&amp;rev=1207384739">
        <dc:format>text/html</dc:format>
        <dc:date>2008-04-05T10:38:59+02:00</dc:date>
        <title>xen:creation_of_a_domu</title>
        <link>http://docs.solstice.nl/dokuwiki/doku.php?id=xen:creation_of_a_domu&amp;rev=1207384739</link>
        <description>Debian domU

Create stock rootfs

Install the debootstrap package on the dom0 if you don’t already have that package. Now create a minimal system installation in a subdirectory to bootstrap:
apt-get install debootstrap
mkdir -p /opt/xen/stock/deb-etch
debootstrap --arch amd64  etch /opt/xen/stock/deb-etch  ftp://ftp.debian.org/debian
(this will use the /etc/apt/sources.list file on the dom0 in order to be able to find the Debian repository) ’’’’’’</description>
    </item>
    <item rdf:about="http://docs.solstice.nl/dokuwiki/doku.php?id=xen:domu_backup&amp;rev=1183366706">
        <dc:format>text/html</dc:format>
        <dc:date>2007-07-02T10:58:26+02:00</dc:date>
        <title>xen:domu_backup</title>
        <link>http://docs.solstice.nl/dokuwiki/doku.php?id=xen:domu_backup&amp;rev=1183366706</link>
        <description>#!/bin/bash

#########################################

XENDIR=/opt/xen
XENUS=&quot;xenmail xenldap xenldns xenadm xenfw xenweb&quot;
VOLUME=vg00
MAILTO=backup@localhost
DATE=`date +%Y%m%d`
DOMNAME=`uname -n`
BACKUPDIR=/var/${DOMNAME}backup
LOGDIR=/var/log/${DOMNAME}backup
LOGFILE=${LOGDIR}/${DOMNAME}backup.log-${DATE}

#########################################

function infoevent {
  echo &quot;`date +%c` INFO    $1&quot; &gt;&gt; ${LOGFILE}
}

function warnevent {
  echo &quot; `date +%c` WARNING   $1&quot; &gt;&gt; ${LOGFILE}
  echo …</description>
    </item>
    <item rdf:about="http://docs.solstice.nl/dokuwiki/doku.php?id=xen:installation_of_dom0&amp;rev=1210358947">
        <dc:format>text/html</dc:format>
        <dc:date>2008-05-09T20:49:07+02:00</dc:date>
        <title>xen:installation_of_dom0</title>
        <link>http://docs.solstice.nl/dokuwiki/doku.php?id=xen:installation_of_dom0&amp;rev=1210358947</link>
        <description>Debian Etch (current)

Core OS and hypervisor

create a bootable system

With the availability of 64-bit hardware in mind, we only use the AMD64 port of Debian Etch in order to create Xen enabled servers. There are several reasons for this decision, one of them is to avoid the TLS-issue’s with the 32-bit Xen hypervisor on x86 CPU’s.’’’’’’’</description>
    </item>
    <item rdf:about="http://docs.solstice.nl/dokuwiki/doku.php?id=xen:live-migration_infrastructure&amp;rev=1202122446">
        <dc:format>text/html</dc:format>
        <dc:date>2008-02-04T11:54:06+02:00</dc:date>
        <title>xen:live-migration_infrastructure</title>
        <link>http://docs.solstice.nl/dokuwiki/doku.php?id=xen:live-migration_infrastructure&amp;rev=1202122446</link>
        <description>shared storage

In order to be able to do a live migration of a Xen guest from one cluster member to another, some sort of shared storage is required. As the Xen guest won’t run on more than one cluster member at a time, a cluster filesystem is not required. That is, as long as you configure Xen to access the Xen guest by a physical device, not a file.’’’’’’’’’’’</description>
    </item>
    <item rdf:about="http://docs.solstice.nl/dokuwiki/doku.php?id=xen:pass_devices_to_the_domu&amp;rev=1209284174">
        <dc:format>text/html</dc:format>
        <dc:date>2008-04-27T10:16:14+02:00</dc:date>
        <title>xen:pass_devices_to_the_domu</title>
        <link>http://docs.solstice.nl/dokuwiki/doku.php?id=xen:pass_devices_to_the_domu&amp;rev=1209284174</link>
        <description>For example, you want to use a tape device in a domU. Therefore you need a PCI adapter, which is not used in the dom0. Then pass this device (entirely) to the domU.

First find out the numbers.

Second, use pciback.hide in grub.conf (on you dom0) to hide your SCSI card.</description>
    </item>
    <item rdf:about="http://docs.solstice.nl/dokuwiki/doku.php?id=xen:pass_devices_to_the_dumu&amp;rev=1189404799">
        <dc:format>text/html</dc:format>
        <dc:date>2007-09-10T08:13:19+02:00</dc:date>
        <title>xen:pass_devices_to_the_dumu</title>
        <link>http://docs.solstice.nl/dokuwiki/doku.php?id=xen:pass_devices_to_the_dumu&amp;rev=1189404799</link>
        <description>For example, you want to use a tape device in a domU. Therefore you need a PCI adapter, which is not used in the dom0. Then pass this device (entirely) to the domU.

First find out the numbers.

Second, use pciback.hide in grub.conf (on you dom0) to hide your SCSI card.</description>
    </item>
    <item rdf:about="http://docs.solstice.nl/dokuwiki/doku.php?id=xen:paused_backups&amp;rev=1183231670">
        <dc:format>text/html</dc:format>
        <dc:date>2007-06-30T21:27:50+02:00</dc:date>
        <title>xen:paused_backups</title>
        <link>http://docs.solstice.nl/dokuwiki/doku.php?id=xen:paused_backups&amp;rev=1183231670</link>
        <description>#!/bin/bash

#########################################

DOMNAME=`uname -n`
XENDIR=/opt/xen
BACKUPDIR=/var/xen/paused-backups/
DATE=`date +%Y%m%d`
MAILTO=backup@localhost
LOGDIR=/var/log/xen
LOGFILE=${LOGDIR}/paused-backup.log

#########################################

function infoevent {
  echo &quot;`date +%c` INFO    $1&quot;| tee -a ${LOGFILE}
}

function warnevent {
  echo &quot; `date +%c` WARNING   $1&quot;| tee -a ${LOGFILE}
  echo &quot;$1 on ${DATE}&quot; | /usr/bin/mailx -s &quot;$1&quot; ${MAILTO}
}

cd ${XENDIR}
rm -f ${…</description>
    </item>
    <item rdf:about="http://docs.solstice.nl/dokuwiki/doku.php?id=xen:start&amp;rev=1209363461">
        <dc:format>text/html</dc:format>
        <dc:date>2008-04-28T08:17:41+02:00</dc:date>
        <title>xen:start</title>
        <link>http://docs.solstice.nl/dokuwiki/doku.php?id=xen:start&amp;rev=1209363461</link>
        <description>Xen namespace:

One of the reasons we use Xen based virtualization is to create a scalable and flexible development and test platform for the Hannibal system stack. Check the Hannibal section of this wiki for more information. 



Topics:

Base:

	*  installation of dom0
	*  creation of a domU</description>
    </item>
    <item rdf:about="http://docs.solstice.nl/dokuwiki/doku.php?id=xen:vmware2xen&amp;rev=1208433069">
        <dc:format>text/html</dc:format>
        <dc:date>2008-04-17T13:51:09+02:00</dc:date>
        <title>xen:vmware2xen</title>
        <link>http://docs.solstice.nl/dokuwiki/doku.php?id=xen:vmware2xen&amp;rev=1208433069</link>
        <description>Migration of image files

VMware to xen migration

German original: &lt;http://www.eisxen.org/49.html&gt;

To convert a Linux VMWare Image to a normal image, below the most important commands: 

	*  install qemu
	*  convert the VMware image to a RAW-Image
’</description>
    </item>
</rdf:RDF>
