Installing Xen 3.3.1 from sources on Hardy or Lenny.

Installing Xen 3.3.1 from sources on Hardy or Lenny.

[Thiago Camargo Martins Cordeiro]

[-- Attachment #1.1: Type: text/plain, Size: 3707 bytes --]

Hi folks!

 This is how I install Xen from sources on Hardy, maybe it work for Lenny
too...

# Necessary packages to compile Xen (this packages can be purged after the
compilation of Xen):

aptitude install --without-recommends bcc bin86 build-essential comerr-dev
debhelper defoma diffstat dpkg-dev fontconfig fontconfig-config g++ g++-4.2
gawk gettext ghostscript graphviz gs-common gsfonts html2text
intltool-debian libc6-dev-i386 libc6-i386 libcairo2 libcupsimage2 libcupsys2
libcurl4-openssl-dev libdatrie0 libdrm2 libfontconfig1 libfreetype6
libgd2-noxpm libgl1-mesa-dev libgl1-mesa-glx libglib2.0-0 libglu1-mesa
libglu1-mesa-dev libglu1-xorg-dev libgraphviz4 libgs8 libice6 libidn11-dev
libjpeg62 libjpeg62-dev libkadm55 libkpathsea4 libkrb5-dev libldap2-dev
libltdl3 libncurses5-dev libpango1.0-0 libpango1.0-common libpaper1 libpcre3
libpixman-1-0 libpng12-0 libpoppler2 libpthread-stubs0 libpthread-stubs0-dev
libsdl1.2-dev libsm6 libssl-dev libstdc++6-4.2-dev libthai-data libthai0
libtiff4 libtimedate-perl libvncserver-dev libvncserver0 libx11-6
libx11-data libx11-dev libxau-dev libxau6 libxaw7 libxcb-xlib0
libxcb-xlib0-dev libxcb1 libxcb1-dev libxdamage1 libxdmcp-dev libxdmcp6
libxext6 libxfixes3 libxft2 libxml2-dev libxmu6 libxpm4 libxrender1 libxt6
libxxf86vm1 make mesa-common-dev mercurial patch pciutils-dev pkg-config
po-debconf python-all python-all-dev python2.4 python2.4-dev
python2.4-minimal quilt tex-common texinfo texlive-base texlive-base-bin
texlive-common texlive-doc-base texlive-fonts-recommended texlive-latex-base
texlive-latex-recommended transfig ttf-dejavu ttf-dejavu-core
ttf-dejavu-extra x11-common x11proto-core-dev x11proto-input-dev
x11proto-kb-dev xtrans-dev zlib1g-dev


mkdir ~/xen-sources && cd ~/xen-sources
wget -c http://bits.xensource.com/oss-xen/release/3.3.1/xen-3.3.1.tar.gz
tar xzf xen-3.3.1.tar.gz && cd xen-3.3.1
make dist
cd dist/ ; ./install.sh

# Necessary packages to run Xen after installing it:

aptitude install --without-recommends binutils binutils-static bridge-utils
debootstrap gcc gcc-4.2 libasound2 libbeecrypt6 libc6-dev
libconfig-inifiles-perl libcurl3 libdirectfb-1.0-0 libexpect-perl libgomp1
libio-pty-perl libio-stty-perl libneon27 librpm4.4 libsdl1.2debian
libsdl1.2debian-alsa libterm-readline-gnu-perl libterm-size-perl
libtext-template-perl libxml2 linux-libc-dev linux-restricted-modules-common
nvidia-kernel-common perl-doc python-dev python2.5-dev rinse rpm screen
sgml-base vnstat xen-shell xen-tools xfsprogs xml-core python-xml

# Python XML is obsolete will be removed soon, but for now, the Xen depends
on it.
echo oldxml >> /usr/lib/python2.5/site-packages/oldxml.pth

# Linux 2.6.18.8-xen does not have AppArmor.
/etc/init.d/apparmor stop
update-rc.d -f apparmor remove

# Update modules / make new initramfs image
depmod -a 2.6.18.8-xen
update-initramfs -k 2.6.18.8-xen -c -u

# Edit /boor/grub/menu.lst and configure you Xen boot options, if you wish.

#--- menu.lst ---
## Xen hypervisor options to use with the default Xen boot option
# xenhopt=dom0_mem=512M

## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0 nosmp
#--- menu.lst

# Update Grub's menu:
update-grub

# Configure the system to start Xen on every boot:
update-rc.d xend defaults 20 21
update-rc.d xendomains defaults 21 20

# Reboot into you new Hypervisor
reboot

# If you have a root file system of your dom0 on LVM (or even LVM on top of
raid1), you probaly can't boot your dom0.
# So, if you see this prompt:

(initramfs)

# Run the following command to continue the system boot at (initramfs)
prompt :
(initramfs) lvm vgchange -ay
(initramfs) exit

Welcome to your new hypervisor!

Regards,
Thiago

[-- Attachment #1.2: Type: text/html, Size: 4038 bytes --]

[-- Attachment #2: Type: text/plain, Size: 137 bytes --]

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Re: Installing Xen 3.3.1 from sources on Hardy or Lenny.

[Dulloor]

[-- Attachment #1.1: Type: text/plain, Size: 4331 bytes --]

Have you verified this with stubdom ?
stubdom still doesn't work for me (on hardy) with any vif configuration
(please see my other mail). Without a vif, there is no problem. Any ideas ?

-dulloor

On Sun, Feb 22, 2009 at 1:22 PM, Thiago Camargo Martins Cordeiro <
thiagocmartinsc@gmail.com> wrote:

> Hi folks!
>
>  This is how I install Xen from sources on Hardy, maybe it work for Lenny
> too...
>
> # Necessary packages to compile Xen (this packages can be purged after the
> compilation of Xen):
>
> aptitude install --without-recommends bcc bin86 build-essential comerr-dev
> debhelper defoma diffstat dpkg-dev fontconfig fontconfig-config g++ g++-4.2
> gawk gettext ghostscript graphviz gs-common gsfonts html2text
> intltool-debian libc6-dev-i386 libc6-i386 libcairo2 libcupsimage2 libcupsys2
> libcurl4-openssl-dev libdatrie0 libdrm2 libfontconfig1 libfreetype6
> libgd2-noxpm libgl1-mesa-dev libgl1-mesa-glx libglib2.0-0 libglu1-mesa
> libglu1-mesa-dev libglu1-xorg-dev libgraphviz4 libgs8 libice6 libidn11-dev
> libjpeg62 libjpeg62-dev libkadm55 libkpathsea4 libkrb5-dev libldap2-dev
> libltdl3 libncurses5-dev libpango1.0-0 libpango1.0-common libpaper1 libpcre3
> libpixman-1-0 libpng12-0 libpoppler2 libpthread-stubs0 libpthread-stubs0-dev
> libsdl1.2-dev libsm6 libssl-dev libstdc++6-4.2-dev libthai-data libthai0
> libtiff4 libtimedate-perl libvncserver-dev libvncserver0 libx11-6
> libx11-data libx11-dev libxau-dev libxau6 libxaw7 libxcb-xlib0
> libxcb-xlib0-dev libxcb1 libxcb1-dev libxdamage1 libxdmcp-dev libxdmcp6
> libxext6 libxfixes3 libxft2 libxml2-dev libxmu6 libxpm4 libxrender1 libxt6
> libxxf86vm1 make mesa-common-dev mercurial patch pciutils-dev pkg-config
> po-debconf python-all python-all-dev python2.4 python2.4-dev
> python2.4-minimal quilt tex-common texinfo texlive-base texlive-base-bin
> texlive-common texlive-doc-base texlive-fonts-recommended texlive-latex-base
> texlive-latex-recommended transfig ttf-dejavu ttf-dejavu-core
> ttf-dejavu-extra x11-common x11proto-core-dev x11proto-input-dev
> x11proto-kb-dev xtrans-dev zlib1g-dev
>
>
> mkdir ~/xen-sources && cd ~/xen-sources
> wget -c http://bits.xensource.com/oss-xen/release/3.3.1/xen-3.3.1.tar.gz
> tar xzf xen-3.3.1.tar.gz && cd xen-3.3.1
> make dist
> cd dist/ ; ./install.sh
>
> # Necessary packages to run Xen after installing it:
>
> aptitude install --without-recommends binutils binutils-static bridge-utils
> debootstrap gcc gcc-4.2 libasound2 libbeecrypt6 libc6-dev
> libconfig-inifiles-perl libcurl3 libdirectfb-1.0-0 libexpect-perl libgomp1
> libio-pty-perl libio-stty-perl libneon27 librpm4.4 libsdl1.2debian
> libsdl1.2debian-alsa libterm-readline-gnu-perl libterm-size-perl
> libtext-template-perl libxml2 linux-libc-dev linux-restricted-modules-common
> nvidia-kernel-common perl-doc python-dev python2.5-dev rinse rpm screen
> sgml-base vnstat xen-shell xen-tools xfsprogs xml-core python-xml
>
> # Python XML is obsolete will be removed soon, but for now, the Xen depends
> on it.
> echo oldxml >> /usr/lib/python2.5/site-packages/oldxml.pth
>
> # Linux 2.6.18.8-xen does not have AppArmor.
> /etc/init.d/apparmor stop
> update-rc.d -f apparmor remove
>
> # Update modules / make new initramfs image
> depmod -a 2.6.18.8-xen
> update-initramfs -k 2.6.18.8-xen -c -u
>
> # Edit /boor/grub/menu.lst and configure you Xen boot options, if you wish.
>
> #--- menu.lst ---
> ## Xen hypervisor options to use with the default Xen boot option
> # xenhopt=dom0_mem=512M
>
> ## Xen Linux kernel options to use with the default Xen boot option
> # xenkopt=console=tty0 nosmp
> #--- menu.lst
>
> # Update Grub's menu:
> update-grub
>
> # Configure the system to start Xen on every boot:
> update-rc.d xend defaults 20 21
> update-rc.d xendomains defaults 21 20
>
> # Reboot into you new Hypervisor
> reboot
>
> # If you have a root file system of your dom0 on LVM (or even LVM on top of
> raid1), you probaly can't boot your dom0.
> # So, if you see this prompt:
>
> (initramfs)
>
> # Run the following command to continue the system boot at (initramfs)
> prompt :
> (initramfs) lvm vgchange -ay
> (initramfs) exit
>
> Welcome to your new hypervisor!
>
> Regards,
> Thiago
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>

[-- Attachment #1.2: Type: text/html, Size: 4959 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: Installing Xen 3.3.1 from sources on Hardy or Lenny.

[Dulloor]

[-- Attachment #1.1: Type: text/plain, Size: 9522 bytes --]

syslog output :
Feb 22 17:23:26 billthepony kernel: PM: Adding info for xen-backend:vfb-9-0
Feb 22 17:23:26 billthepony kernel: PM: Adding info for xen-backend:vif-9-0
Feb 22 17:23:27 billthepony kernel: PM: Adding info for
xen-backend:console-9-0
Feb 22 17:23:27 billthepony logger: /etc/xen/scripts/vif-nat: online
XENBUS_PATH=backend/vif/9/0
Feb 22 17:23:27 billthepony logger: /etc/xen/scripts/vif-nat: Successful
vif-nat online for vif9.0.
Feb 22 17:23:27 billthepony logger: /etc/xen/scripts/vif-nat: Writing
backend/vif/9/0/hotplug-status connected to xenstore.
Feb 22 17:23:28 billthepony kernel: PM: Adding info for
xen-backend:vkbd-10-0
Feb 22 17:23:28 billthepony kernel: PM: Adding info for xen-backend:vfb-10-0
Feb 22 17:23:28 billthepony kernel: PM: Adding info for
xen-backend:vbd-10-768
Feb 22 17:23:28 billthepony kernel: PM: Adding info for
xen-backend:vbd-10-5632
Feb 22 17:23:28 billthepony kernel: PM: Adding info for xen-backend:vif-10-0
Feb 22 17:23:28 billthepony kernel: PM: Adding info for xen-backend:vif-10-1
Feb 22 17:23:28 billthepony logger: /etc/xen/scripts/vif-nat: online
XENBUS_PATH=backend/vif/10/0
Feb 22 17:23:28 billthepony logger: /etc/xen/scripts/block: add
XENBUS_PATH=backend/vbd/10/768
Feb 22 17:23:28 billthepony logger: /etc/xen/scripts/vif-nat: online
XENBUS_PATH=backend/vif/10/1
Feb 22 17:23:28 billthepony logger: /etc/xen/scripts/block: add
XENBUS_PATH=backend/vbd/10/5632
Feb 22 17:23:28 billthepony kernel: PM: Adding info for
xen-backend:console-10-0
Feb 22 17:23:28 billthepony logger: /etc/xen/scripts/block: Writing
backend/vbd/10/768/node /dev/loop0 to xenstore.
Feb 22 17:23:28 billthepony logger: /etc/xen/scripts/block: Writing
backend/vbd/10/768/physical-device 7:0 to xenstore.
Feb 22 17:23:28 billthepony logger: /etc/xen/scripts/block: Writing
backend/vbd/10/768/hotplug-status connected to xenstore.
Feb 22 17:23:28 billthepony logger: /etc/xen/scripts/vif-nat: Successful
vif-nat online for vif10.0.
Feb 22 17:23:28 billthepony logger: /etc/xen/scripts/vif-nat: Writing
backend/vif/10/0/hotplug-status connected to xenstore.
Feb 22 17:23:28 billthepony logger: /etc/xen/scripts/block: Writing
backend/vbd/10/5632/node /dev/loop1 to xenstore.
Feb 22 17:23:28 billthepony logger: /etc/xen/scripts/block: Writing
backend/vbd/10/5632/physical-device 7:1 to xenstore.
Feb 22 17:23:28 billthepony logger: /etc/xen/scripts/block: Writing
backend/vbd/10/5632/hotplug-status connected to xenstore.
Feb 22 17:23:28 billthepony logger: /etc/xen/scripts/vif-nat: Writing
backend/vif/10/1/hotplug-error ip route add 10.0.0.1 dev vif10.1 src
10.0.0.128 failed backend/vif/10/1/hotplug-status error to xenstore.
Feb 22 17:23:28 billthepony logger: /etc/xen/scripts/vif-nat: ip route add
10.0.0.1 dev vif10.1 src 10.0.0.128 failed
Feb 22 17:23:29 billthepony logger: /etc/xen/scripts/block: remove
XENBUS_PATH=backend/vbd/10/5632
Feb 22 17:23:29 billthepony logger: /etc/xen/scripts/vif-nat: offline
XENBUS_PATH=backend/vif/10/0
Feb 22 17:23:29 billthepony kernel: PM: Removing info for
xen-backend:vkbd-10-0
Feb 22 17:23:29 billthepony kernel: PM: Removing info for
xen-backend:vfb-10-0
Feb 22 17:23:29 billthepony kernel: PM: Removing info for
xen-backend:console-10-0
Feb 22 17:23:29 billthepony kernel: PM: Removing info for
xen-backend:vbd-10-768
Feb 22 17:23:29 billthepony kernel: PM: Removing info for
xen-backend:vbd-10-5632
Feb 22 17:23:29 billthepony logger: /etc/xen/scripts/xen-hotplug-cleanup:
XENBUS_PATH=backend/vbd/10/5632
Feb 22 17:23:29 billthepony kernel: PM: Removing info for
xen-backend:vif-10-0
Feb 22 17:23:29 billthepony logger: /etc/xen/scripts/vif-nat: ifconfig
vif10.0 down failed
Feb 22 17:23:29 billthepony logger: /etc/xen/scripts/vif-nat: Successful
vif-nat offline for vif10.0.
Feb 22 17:23:29 billthepony kernel: PM: Removing info for
xen-backend:vif-10-1
Feb 22 17:23:29 billthepony logger: /etc/xen/scripts/xen-hotplug-cleanup:
XENBUS_PATH=backend/vkbd/10/0
Feb 22 17:23:29 billthepony logger: /etc/xen/scripts/vif-nat: offline
XENBUS_PATH=backend/vif/10/1
Feb 22 17:23:29 billthepony logger: /etc/xen/scripts/block: remove
XENBUS_PATH=backend/vbd/10/768
Feb 22 17:23:29 billthepony logger: /etc/xen/scripts/xen-hotplug-cleanup:
XENBUS_PATH=backend/console/10/0
Feb 22 17:23:29 billthepony logger: /etc/xen/scripts/xen-hotplug-cleanup:
XENBUS_PATH=backend/vif/10/0
Feb 22 17:23:29 billthepony logger: /etc/xen/scripts/xen-hotplug-cleanup:
XENBUS_PATH=backend/vfb/10/0
Feb 22 17:23:29 billthepony logger: /etc/xen/scripts/xen-hotplug-cleanup:
XENBUS_PATH=backend/vbd/10/768
Feb 22 17:23:29 billthepony logger: /etc/xen/scripts/vif-nat: ifconfig
vif10.1 down failed
Feb 22 17:23:29 billthepony logger: /etc/xen/scripts/vif-nat: Successful
vif-nat offline for vif10.1.
Feb 22 17:23:29 billthepony logger: /etc/xen/scripts/xen-hotplug-cleanup:
XENBUS_PATH=backend/vif/10/1
Feb 22 17:23:37 billthepony kernel: vif9.0: no IPv6 routers present


I have turned off avahi-daemon, which didn't matter anyway.

-dulloor

On Sun, Feb 22, 2009 at 4:36 PM, Dulloor <dulloor@gmail.com> wrote:

> Have you verified this with stubdom ?
> stubdom still doesn't work for me (on hardy) with any vif configuration
> (please see my other mail). Without a vif, there is no problem. Any ideas ?
>
> -dulloor
>
> On Sun, Feb 22, 2009 at 1:22 PM, Thiago Camargo Martins Cordeiro <
> thiagocmartinsc@gmail.com> wrote:
>
>> Hi folks!
>>
>>  This is how I install Xen from sources on Hardy, maybe it work for Lenny
>> too...
>>
>> # Necessary packages to compile Xen (this packages can be purged after the
>> compilation of Xen):
>>
>> aptitude install --without-recommends bcc bin86 build-essential comerr-dev
>> debhelper defoma diffstat dpkg-dev fontconfig fontconfig-config g++ g++-4.2
>> gawk gettext ghostscript graphviz gs-common gsfonts html2text
>> intltool-debian libc6-dev-i386 libc6-i386 libcairo2 libcupsimage2 libcupsys2
>> libcurl4-openssl-dev libdatrie0 libdrm2 libfontconfig1 libfreetype6
>> libgd2-noxpm libgl1-mesa-dev libgl1-mesa-glx libglib2.0-0 libglu1-mesa
>> libglu1-mesa-dev libglu1-xorg-dev libgraphviz4 libgs8 libice6 libidn11-dev
>> libjpeg62 libjpeg62-dev libkadm55 libkpathsea4 libkrb5-dev libldap2-dev
>> libltdl3 libncurses5-dev libpango1.0-0 libpango1.0-common libpaper1 libpcre3
>> libpixman-1-0 libpng12-0 libpoppler2 libpthread-stubs0 libpthread-stubs0-dev
>> libsdl1.2-dev libsm6 libssl-dev libstdc++6-4.2-dev libthai-data libthai0
>> libtiff4 libtimedate-perl libvncserver-dev libvncserver0 libx11-6
>> libx11-data libx11-dev libxau-dev libxau6 libxaw7 libxcb-xlib0
>> libxcb-xlib0-dev libxcb1 libxcb1-dev libxdamage1 libxdmcp-dev libxdmcp6
>> libxext6 libxfixes3 libxft2 libxml2-dev libxmu6 libxpm4 libxrender1 libxt6
>> libxxf86vm1 make mesa-common-dev mercurial patch pciutils-dev pkg-config
>> po-debconf python-all python-all-dev python2.4 python2.4-dev
>> python2.4-minimal quilt tex-common texinfo texlive-base texlive-base-bin
>> texlive-common texlive-doc-base texlive-fonts-recommended texlive-latex-base
>> texlive-latex-recommended transfig ttf-dejavu ttf-dejavu-core
>> ttf-dejavu-extra x11-common x11proto-core-dev x11proto-input-dev
>> x11proto-kb-dev xtrans-dev zlib1g-dev
>>
>>
>> mkdir ~/xen-sources && cd ~/xen-sources
>> wget -c http://bits.xensource.com/oss-xen/release/3.3.1/xen-3.3.1.tar.gz
>> tar xzf xen-3.3.1.tar.gz && cd xen-3.3.1
>> make dist
>> cd dist/ ; ./install.sh
>>
>> # Necessary packages to run Xen after installing it:
>>
>> aptitude install --without-recommends binutils binutils-static
>> bridge-utils debootstrap gcc gcc-4.2 libasound2 libbeecrypt6 libc6-dev
>> libconfig-inifiles-perl libcurl3 libdirectfb-1.0-0 libexpect-perl libgomp1
>> libio-pty-perl libio-stty-perl libneon27 librpm4.4 libsdl1.2debian
>> libsdl1.2debian-alsa libterm-readline-gnu-perl libterm-size-perl
>> libtext-template-perl libxml2 linux-libc-dev linux-restricted-modules-common
>> nvidia-kernel-common perl-doc python-dev python2.5-dev rinse rpm screen
>> sgml-base vnstat xen-shell xen-tools xfsprogs xml-core python-xml
>>
>> # Python XML is obsolete will be removed soon, but for now, the Xen
>> depends on it.
>> echo oldxml >> /usr/lib/python2.5/site-packages/oldxml.pth
>>
>> # Linux 2.6.18.8-xen does not have AppArmor.
>> /etc/init.d/apparmor stop
>> update-rc.d -f apparmor remove
>>
>> # Update modules / make new initramfs image
>> depmod -a 2.6.18.8-xen
>> update-initramfs -k 2.6.18.8-xen -c -u
>>
>> # Edit /boor/grub/menu.lst and configure you Xen boot options, if you
>> wish.
>>
>> #--- menu.lst ---
>> ## Xen hypervisor options to use with the default Xen boot option
>> # xenhopt=dom0_mem=512M
>>
>> ## Xen Linux kernel options to use with the default Xen boot option
>> # xenkopt=console=tty0 nosmp
>> #--- menu.lst
>>
>> # Update Grub's menu:
>> update-grub
>>
>> # Configure the system to start Xen on every boot:
>> update-rc.d xend defaults 20 21
>> update-rc.d xendomains defaults 21 20
>>
>> # Reboot into you new Hypervisor
>> reboot
>>
>> # If you have a root file system of your dom0 on LVM (or even LVM on top
>> of raid1), you probaly can't boot your dom0.
>> # So, if you see this prompt:
>>
>> (initramfs)
>>
>> # Run the following command to continue the system boot at (initramfs)
>> prompt :
>> (initramfs) lvm vgchange -ay
>> (initramfs) exit
>>
>> Welcome to your new hypervisor!
>>
>> Regards,
>> Thiago
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>>
>>
>

[-- Attachment #1.2: Type: text/html, Size: 10634 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: [Xen-devel] Installing Xen 3.3.1 from sources on Hardy or Lenny.

[Thiago Camargo Martins Cordeiro]

[-- Attachment #1.1: Type: text/plain, Size: 4616 bytes --]

Yeah, sure! I have sutbdom working on this setup, here is my domU
configurarion files:

Attached to this mail.

-
Thiago

2009/2/22 Dulloor <dulloor@gmail.com>

> Have you verified this with stubdom ?
> stubdom still doesn't work for me (on hardy) with any vif configuration
> (please see my other mail). Without a vif, there is no problem. Any ideas ?
>
> -dulloor
>
> On Sun, Feb 22, 2009 at 1:22 PM, Thiago Camargo Martins Cordeiro <
> thiagocmartinsc@gmail.com> wrote:
>
>> Hi folks!
>>
>>  This is how I install Xen from sources on Hardy, maybe it work for Lenny
>> too...
>>
>> # Necessary packages to compile Xen (this packages can be purged after the
>> compilation of Xen):
>>
>> aptitude install --without-recommends bcc bin86 build-essential comerr-dev
>> debhelper defoma diffstat dpkg-dev fontconfig fontconfig-config g++ g++-4.2
>> gawk gettext ghostscript graphviz gs-common gsfonts html2text
>> intltool-debian libc6-dev-i386 libc6-i386 libcairo2 libcupsimage2 libcupsys2
>> libcurl4-openssl-dev libdatrie0 libdrm2 libfontconfig1 libfreetype6
>> libgd2-noxpm libgl1-mesa-dev libgl1-mesa-glx libglib2.0-0 libglu1-mesa
>> libglu1-mesa-dev libglu1-xorg-dev libgraphviz4 libgs8 libice6 libidn11-dev
>> libjpeg62 libjpeg62-dev libkadm55 libkpathsea4 libkrb5-dev libldap2-dev
>> libltdl3 libncurses5-dev libpango1.0-0 libpango1.0-common libpaper1 libpcre3
>> libpixman-1-0 libpng12-0 libpoppler2 libpthread-stubs0 libpthread-stubs0-dev
>> libsdl1.2-dev libsm6 libssl-dev libstdc++6-4.2-dev libthai-data libthai0
>> libtiff4 libtimedate-perl libvncserver-dev libvncserver0 libx11-6
>> libx11-data libx11-dev libxau-dev libxau6 libxaw7 libxcb-xlib0
>> libxcb-xlib0-dev libxcb1 libxcb1-dev libxdamage1 libxdmcp-dev libxdmcp6
>> libxext6 libxfixes3 libxft2 libxml2-dev libxmu6 libxpm4 libxrender1 libxt6
>> libxxf86vm1 make mesa-common-dev mercurial patch pciutils-dev pkg-config
>> po-debconf python-all python-all-dev python2.4 python2.4-dev
>> python2.4-minimal quilt tex-common texinfo texlive-base texlive-base-bin
>> texlive-common texlive-doc-base texlive-fonts-recommended texlive-latex-base
>> texlive-latex-recommended transfig ttf-dejavu ttf-dejavu-core
>> ttf-dejavu-extra x11-common x11proto-core-dev x11proto-input-dev
>> x11proto-kb-dev xtrans-dev zlib1g-dev
>>
>>
>> mkdir ~/xen-sources && cd ~/xen-sources
>> wget -c http://bits.xensource.com/oss-xen/release/3.3.1/xen-3.3.1.tar.gz
>> tar xzf xen-3.3.1.tar.gz && cd xen-3.3.1
>> make dist
>> cd dist/ ; ./install.sh
>>
>> # Necessary packages to run Xen after installing it:
>>
>> aptitude install --without-recommends binutils binutils-static
>> bridge-utils debootstrap gcc gcc-4.2 libasound2 libbeecrypt6 libc6-dev
>> libconfig-inifiles-perl libcurl3 libdirectfb-1.0-0 libexpect-perl libgomp1
>> libio-pty-perl libio-stty-perl libneon27 librpm4.4 libsdl1.2debian
>> libsdl1.2debian-alsa libterm-readline-gnu-perl libterm-size-perl
>> libtext-template-perl libxml2 linux-libc-dev linux-restricted-modules-common
>> nvidia-kernel-common perl-doc python-dev python2.5-dev rinse rpm screen
>> sgml-base vnstat xen-shell xen-tools xfsprogs xml-core python-xml
>>
>> # Python XML is obsolete will be removed soon, but for now, the Xen
>> depends on it.
>> echo oldxml >> /usr/lib/python2.5/site-packages/oldxml.pth
>>
>> # Linux 2.6.18.8-xen does not have AppArmor.
>> /etc/init.d/apparmor stop
>> update-rc.d -f apparmor remove
>>
>> # Update modules / make new initramfs image
>> depmod -a 2.6.18.8-xen
>> update-initramfs -k 2.6.18.8-xen -c -u
>>
>> # Edit /boor/grub/menu.lst and configure you Xen boot options, if you
>> wish.
>>
>> #--- menu.lst ---
>> ## Xen hypervisor options to use with the default Xen boot option
>> # xenhopt=dom0_mem=512M
>>
>> ## Xen Linux kernel options to use with the default Xen boot option
>> # xenkopt=console=tty0 nosmp
>> #--- menu.lst
>>
>> # Update Grub's menu:
>> update-grub
>>
>> # Configure the system to start Xen on every boot:
>> update-rc.d xend defaults 20 21
>> update-rc.d xendomains defaults 21 20
>>
>> # Reboot into you new Hypervisor
>> reboot
>>
>> # If you have a root file system of your dom0 on LVM (or even LVM on top
>> of raid1), you probaly can't boot your dom0.
>> # So, if you see this prompt:
>>
>> (initramfs)
>>
>> # Run the following command to continue the system boot at (initramfs)
>> prompt :
>> (initramfs) lvm vgchange -ay
>> (initramfs) exit
>>
>> Welcome to your new hypervisor!
>>
>> Regards,
>> Thiago
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>>
>>
>

[-- Attachment #1.2: Type: text/html, Size: 5538 bytes --]

[-- Attachment #2: vsrvMODELO-dm --]
[-- Type: application/octet-stream, Size: 242 bytes --]

kernel = "/usr/lib/xen/boot/ioemu-stubdom.gz"
vif = [ '', 'bridge=xenbr0,mac=00:01:64:da:f2:6d']
disk = [ 'file:/dados/distros/jeos-8.04.1-jeos-i386.iso,hdc:cdrom,r', 'phy:/dev/mapper/HyperVG01-vsrvMODELO--disk1,hda,w' ]
vfb = [ 'type=vnc' ]

[-- Attachment #3: vsrvMODELO-stubdom --]
[-- Type: application/octet-stream, Size: 12226 bytes --]

#  -*- mode: python; -*-
#============================================================================
# Python configuration setup for 'xm create'.
# This script sets the parameters used when a domain is created using 'xm create'.
# You use a separate script for each domain you want to create, or 
# you can set the parameters for the domain on the xm command line.
#============================================================================
#
# This is a version using a stubdomain for device model, see
# xmexample.hvm-dm and README.stubdom for more details
# The differences with xmexample.hvm are marked with "STUBDOM"

#----------------------------------------------------------------------------
# Kernel image file.
kernel = "/usr/lib/xen/boot/hvmloader"

# The domain build function. HVM domain uses 'hvm'.
builder='hvm'

# Initial memory allocation (in megabytes) for the new domain.
#
# WARNING: Creating a domain with insufficient memory may cause out of
#          memory errors. The domain needs enough memory to boot kernel
#          and modules. Allocating less than 32MBs is not recommended.
memory = 512

# Shadow pagetable memory for the domain, in MB.
# If not explicictly set, xend will pick an appropriate value.  
# Should be at least 2KB per MB of domain memory, plus a few MB per vcpu.
# shadow_memory = 8

# A name for your domain. All domains must have different names.
name = "vsrvMODELO"

# 128-bit UUID for the domain.  The default behavior is to generate a new UUID
# on each call to 'xm create'.
#uuid = "06ed00fe-1162-4fc4-b5d8-11993ee4a8b9"

#-----------------------------------------------------------------------------
# The number of cpus guest platform has, default=1
vcpus=1

# Enable/disable HVM guest PAE, default=1 (enabled)
#pae=1

# Enable/disable HVM guest ACPI, default=1 (enabled)
#acpi=1

# Enable/disable HVM APIC mode, default=1 (enabled)
# Note that this option is ignored if vcpus > 1
#apic=1

# List of which CPUS this domain is allowed to use, default Xen picks
#cpus = ""         # leave to Xen to pick
#cpus = "0"        # all vcpus run on CPU0
#cpus = "0-3,5,^1" # all vcpus run on cpus 0,2,3,5
#cpus = ["2", "3"] # VCPU0 runs on CPU2, VCPU1 runs on CPU3
cpus = "0"

# Optionally define mac and/or bridge for the network interfaces.
# Random MACs are assigned if not given.
#vif = [ 'type=ioemu, mac=00:16:3e:00:00:11, bridge=xenbr0, model=ne2k_pci' ]
# type=ioemu specify the NIC is an ioemu device not netfront
#vif = [ 'type=ioemu, bridge=xenbr0' ]
#vif = [ 'bridge=xenbr0, mac=00:01:64:64:3d:5c' ]

#----------------------------------------------------------------------------
# Define the disk devices you want the domain to have access to, and
# what you want them accessible as.
# Each disk entry is of the form phy:UNAME,DEV,MODE
# where UNAME is the device, DEV is the device name the domain will see,
# and MODE is r for read-only, w for read-write.
#
# STUBDOM: do not put it here but in stubdom-ExampleHVMDomain

#disk = [ 'phy:hda1,hda1,r' ]
#disk = [ 'file:/var/images/min-el3-i386.img,hda,w', ',hdc:cdrom,r' ]

#----------------------------------------------------------------------------
# Configure the behaviour when a domain exits.  There are three 'reasons'
# for a domain to stop: poweroff, reboot, and crash.  For each of these you
# may specify:
#
#   "destroy",        meaning that the domain is cleaned up as normal;
#   "restart",        meaning that a new domain is started in place of the old
#                     one;
#   "preserve",       meaning that no clean-up is done until the domain is
#                     manually destroyed (using xm destroy, for example); or
#   "rename-restart", meaning that the old domain is not cleaned up, but is
#                     renamed and a new domain started in its place.
#
# In the event a domain stops due to a crash, you have the additional options:
#
#   "coredump-destroy", meaning dump the crashed domain's core and then destroy;
#   "coredump-restart', meaning dump the crashed domain's core and the restart.
#
# The default is
#
#   on_poweroff = 'destroy'
#   on_reboot   = 'restart'
#   on_crash    = 'restart'
#
# For backwards compatibility we also support the deprecated option restart
#
# restart = 'onreboot' means on_poweroff = 'destroy'
#                            on_reboot   = 'restart'
#                            on_crash    = 'destroy'
#
# restart = 'always'   means on_poweroff = 'restart'
#                            on_reboot   = 'restart'
#                            on_crash    = 'restart'
#
# restart = 'never'    means on_poweroff = 'destroy'
#                            on_reboot   = 'destroy'
#                            on_crash    = 'destroy'

#on_poweroff = 'destroy'
#on_reboot   = 'restart'
#on_crash    = 'restart'

#============================================================================

# Device Model to be used
#
# STUBDOM: this is a script that creates the stub domain running the device
# model
device_model = '/usr/lib/xen/bin/stubdom-dm'

#-----------------------------------------------------------------------------
# boot on floppy (a), hard disk (c), Network (n) or CD-ROM (d) 
# default: hard disk, cd-rom, floppy
boot="d"

#-----------------------------------------------------------------------------
#  write to temporary files instead of disk image files
#snapshot=1

#----------------------------------------------------------------------------
# enable SDL library for graphics, default = 0
# 
# STUBDOM: always disable since the stub domain doesn't have direct X access
sdl=0

#----------------------------------------------------------------------------
# enable OpenGL for texture rendering inside the SDL window, default = 1
# valid only if sdl is enabled.
# 
# STUBDOM: always disable for the same reason
opengl=0

#----------------------------------------------------------------------------
# enable VNC library for graphics, default = 1
vnc=0

#----------------------------------------------------------------------------
# address that should be listened on for the VNC server if vnc is set.
# default is to use 'vnc-listen' setting from /etc/xen/xend-config.sxp
#vnclisten="10.1.10.213"

#----------------------------------------------------------------------------
# set VNC display number, default = domid
#vncdisplay=1

#----------------------------------------------------------------------------
# try to find an unused port for the VNC server, default = 1
#vncunused=1

#----------------------------------------------------------------------------
# enable spawning vncviewer for domain's console
# (only valid when vnc=1), default = 0
#vncconsole=0

#----------------------------------------------------------------------------
# set password for domain's VNC console
# default is depents on vncpasswd in xend-config.sxp
#vncpasswd=''

#----------------------------------------------------------------------------
# no graphics, use serial port
#nographic=0

#----------------------------------------------------------------------------
# enable stdvga, default = 0 (use cirrus logic device model)
stdvga=0

#-----------------------------------------------------------------------------
#   serial port re-direct to pty deivce, /dev/pts/n 
#   then xm console or minicom can connect
# 
# STUBDOM: always disable as the stub domain doesn't have access to dom0's
# ptys
#serial='pty'


#-----------------------------------------------------------------------------
#   Qemu Monitor, default is disable
#   Use ctrl-alt-2 to connect
#monitor=1


#-----------------------------------------------------------------------------
#   enable sound card support, [sb16|es1370|all|..,..], default none
# 
# STUBDOM: not supported
#soundhw='sb16'


#-----------------------------------------------------------------------------
#    set the real time clock to local time [default=0 i.e. set to utc]
#localtime=1


#-----------------------------------------------------------------------------
#    set the real time clock offset in seconds [default=0 i.e. same as dom0]
#rtc_timeoffset=3600

#-----------------------------------------------------------------------------
#    start in full screen
#full-screen=1   


#-----------------------------------------------------------------------------
#   Enable USB support (specific devices specified at runtime through the
#			monitor window)
#usb=1

#   Enable USB mouse support (only enable one of the following, `mouse' for
#			      PS/2 protocol relative mouse, `tablet' for
#			      absolute mouse)
#usbdevice='mouse'
#usbdevice='tablet'

#-----------------------------------------------------------------------------
#   Set keyboard layout, default is en-us keyboard. 
#keymap='ja'

#-----------------------------------------------------------------------------
#   Configure guest CPUID responses:
#
#cpuid=[ '1:ecx=xxxxxxxxxxx00xxxxxxxxxxxxxxxxxxx,
#           eax=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx' ]
# - Unset the SSE4 features (CPUID.1[ECX][20-19])
# - Default behaviour for all other bits in ECX And EAX registers.
# 
# Each successive character represent a lesser-significant bit:
#  '1' -> force the corresponding bit to 1
#  '0' -> force to 0
#  'x' -> Get a safe value (pass through and mask with the default policy)
#  'k' -> pass through the host bit value
#  's' -> as 'k' but preserve across save/restore and migration
# 
#   Expose to the guest multi-core cpu instead of multiple processors
# Example for intel, expose a 8-core processor :
#cpuid=['1:edx=xxx1xxxxxxxxxxxxxxxxxxxxxxxxxxxx,
#          ebx=xxxxxxxx00010000xxxxxxxxxxxxxxxx',
#     '4,0:eax=001111xxxxxxxxxxxxxxxxxxxxxxxxxx']
#  - CPUID.1[EDX][HT] : Enable HT
#  - CPUID.1[EBX] : Number of vcpus * 2
#  - CPUID.4,0[EAX] : Number of vcpus * 2 - 1
#vcpus=8
#
# Example for amd, expose a 5-core processor :
# cpuid = ['1:ebx=xxxxxxxx00001010xxxxxxxxxxxxxxxx,
#             edx=xxx1xxxxxxxxxxxxxxxxxxxxxxxxxxxx',
# '0x80000001:ecx=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx1x',
# '0x80000008:ecx=xxxxxxxxxxxxxxxxxxxxxxxxxx001001']
#   - CPUID.1[EBX] : Threads per Core * Cores per Socket (2 * #vcpus)
#   - CPUID.1[EDX][HT] : Enable HT
#   - CPUID.0x80000001[CmpLegacy] : Use legacy method
#   - CPUID.0x80000008[ECX] : #vcpus * 2 - 1
#vcpus=5
#
#  Downgrade the cpuid to make a better compatibility for migration :
# Look like a generic 686 :
# cpuid = [ '0:eax=0x3,ebx=0x0,ecx=0x0,edx=0x0',
#           '1:eax=0x06b1,
#              ecx=xxxxxxxxxx0000xx00xxx0000000xx0,
#              edx=xx00000xxxxxxx0xxxxxxxxx0xxxxxx',
#           '4:eax=0x3,ebx=0x0,ecx=0x0,edx=0x0',
#  '0x80000000:eax=0x3,ebx=0x0,ecx=0x0,edx=0x0']
#  with the highest leaf
#  - CPUID.0[EAX] : Set the highest leaf
#  - CPUID.1[EAX] : 686 
#  - CPUID.1[ECX] : Mask some features
#  - CPUID.1[EDX] : Mask some features
#  - CPUID.4 : Reply like the highest leaf, in our case CPUID.3
#  - CPUID.0x80000000 : No extension we are on a Pentium III, reply like the
#  highest leaf (CPUID.3).
#
#   Configure host CPUID consistency checks, which must be satisfied for this
#   VM to be allowed to run on this host's processor type:
#cpuid_check=[ '1:ecx=xxxxxxxxxxxxxxxxxxxxxxxxxx1xxxxx' ]
# - Host must have VMX feature flag set
#
# The format is similar to the above for 'cpuid':
#  '1' -> the bit must be '1'
#  '0' -> the bit must be '0'
#  'x' -> we don't care (do not check)
#  's' -> the bit must be the same as on the host that started this VM


#-----------------------------------------------------------------------------
#   Configure PVSCSI devices:
#
#vscsi=[ 'PDEV, VDEV' ]
#
#   PDEV   gives physical SCSI device to be attached to specified guest
#          domain by one of the following identifier format.
#          - XX:XX:XX:XX (4-tuples with decimal notation which shows
#                          "host:channel:target:lun")
#          - /dev/sdxx or sdx
#          - /dev/stxx or stx
#          - /dev/sgxx or sgx
#          - result of 'scsi_id -gu -s'.
#            ex. # scsi_id -gu -s /block/sdb
#                  36000b5d0006a0000006a0257004c0000
#
#   VDEV   gives virtual SCSI device by 4-tuples (XX:XX:XX:XX) as 
#          which the specified guest domain recognize.
#

#vscsi = [ '/dev/sdx, 0:0:0:0' ]

[-- Attachment #4: Type: text/plain, Size: 137 bytes --]

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Re: Installing Xen 3.3.1 from sources on Hardy or Lenny.

[Dulloor]

[-- Attachment #1.1: Type: text/plain, Size: 5217 bytes --]

I had "vif" option(identical entries) set both in config-stubdom and
config-dm file and that was the problem. "ip route" error was because of
clashing entries (syslog showed it).

There was nothing in stubdom/readme to suggest this (although it was
explicitly mentioned for disk and pty assignments), but I should have
figured it out :(

Thanks Thiago :)

-dulloor

On Sun, Feb 22, 2009 at 5:57 PM, Thiago Camargo Martins Cordeiro <
thiagocmartinsc@gmail.com> wrote:

> Yeah, sure! I have sutbdom working on this setup, here is my domU
> configurarion files:
>
> Attached to this mail.
>
> -
> Thiago
>
> 2009/2/22 Dulloor <dulloor@gmail.com>
>
> Have you verified this with stubdom ?
>> stubdom still doesn't work for me (on hardy) with any vif configuration
>> (please see my other mail). Without a vif, there is no problem. Any ideas ?
>>
>> -dulloor
>>
>> On Sun, Feb 22, 2009 at 1:22 PM, Thiago Camargo Martins Cordeiro <
>> thiagocmartinsc@gmail.com> wrote:
>>
>>>  Hi folks!
>>>
>>>  This is how I install Xen from sources on Hardy, maybe it work for Lenny
>>> too...
>>>
>>> # Necessary packages to compile Xen (this packages can be purged after
>>> the compilation of Xen):
>>>
>>> aptitude install --without-recommends bcc bin86 build-essential
>>> comerr-dev debhelper defoma diffstat dpkg-dev fontconfig fontconfig-config
>>> g++ g++-4.2 gawk gettext ghostscript graphviz gs-common gsfonts html2text
>>> intltool-debian libc6-dev-i386 libc6-i386 libcairo2 libcupsimage2 libcupsys2
>>> libcurl4-openssl-dev libdatrie0 libdrm2 libfontconfig1 libfreetype6
>>> libgd2-noxpm libgl1-mesa-dev libgl1-mesa-glx libglib2.0-0 libglu1-mesa
>>> libglu1-mesa-dev libglu1-xorg-dev libgraphviz4 libgs8 libice6 libidn11-dev
>>> libjpeg62 libjpeg62-dev libkadm55 libkpathsea4 libkrb5-dev libldap2-dev
>>> libltdl3 libncurses5-dev libpango1.0-0 libpango1.0-common libpaper1 libpcre3
>>> libpixman-1-0 libpng12-0 libpoppler2 libpthread-stubs0 libpthread-stubs0-dev
>>> libsdl1.2-dev libsm6 libssl-dev libstdc++6-4.2-dev libthai-data libthai0
>>> libtiff4 libtimedate-perl libvncserver-dev libvncserver0 libx11-6
>>> libx11-data libx11-dev libxau-dev libxau6 libxaw7 libxcb-xlib0
>>> libxcb-xlib0-dev libxcb1 libxcb1-dev libxdamage1 libxdmcp-dev libxdmcp6
>>> libxext6 libxfixes3 libxft2 libxml2-dev libxmu6 libxpm4 libxrender1 libxt6
>>> libxxf86vm1 make mesa-common-dev mercurial patch pciutils-dev pkg-config
>>> po-debconf python-all python-all-dev python2.4 python2.4-dev
>>> python2.4-minimal quilt tex-common texinfo texlive-base texlive-base-bin
>>> texlive-common texlive-doc-base texlive-fonts-recommended texlive-latex-base
>>> texlive-latex-recommended transfig ttf-dejavu ttf-dejavu-core
>>> ttf-dejavu-extra x11-common x11proto-core-dev x11proto-input-dev
>>> x11proto-kb-dev xtrans-dev zlib1g-dev
>>>
>>>
>>> mkdir ~/xen-sources && cd ~/xen-sources
>>> wget -c http://bits.xensource.com/oss-xen/release/3.3.1/xen-3.3.1.tar.gz
>>> tar xzf xen-3.3.1.tar.gz && cd xen-3.3.1
>>> make dist
>>> cd dist/ ; ./install.sh
>>>
>>> # Necessary packages to run Xen after installing it:
>>>
>>> aptitude install --without-recommends binutils binutils-static
>>> bridge-utils debootstrap gcc gcc-4.2 libasound2 libbeecrypt6 libc6-dev
>>> libconfig-inifiles-perl libcurl3 libdirectfb-1.0-0 libexpect-perl libgomp1
>>> libio-pty-perl libio-stty-perl libneon27 librpm4.4 libsdl1.2debian
>>> libsdl1.2debian-alsa libterm-readline-gnu-perl libterm-size-perl
>>> libtext-template-perl libxml2 linux-libc-dev linux-restricted-modules-common
>>> nvidia-kernel-common perl-doc python-dev python2.5-dev rinse rpm screen
>>> sgml-base vnstat xen-shell xen-tools xfsprogs xml-core python-xml
>>>
>>> # Python XML is obsolete will be removed soon, but for now, the Xen
>>> depends on it.
>>> echo oldxml >> /usr/lib/python2.5/site-packages/oldxml.pth
>>>
>>> # Linux 2.6.18.8-xen does not have AppArmor.
>>> /etc/init.d/apparmor stop
>>> update-rc.d -f apparmor remove
>>>
>>> # Update modules / make new initramfs image
>>> depmod -a 2.6.18.8-xen
>>> update-initramfs -k 2.6.18.8-xen -c -u
>>>
>>> # Edit /boor/grub/menu.lst and configure you Xen boot options, if you
>>> wish.
>>>
>>> #--- menu.lst ---
>>> ## Xen hypervisor options to use with the default Xen boot option
>>> # xenhopt=dom0_mem=512M
>>>
>>> ## Xen Linux kernel options to use with the default Xen boot option
>>> # xenkopt=console=tty0 nosmp
>>> #--- menu.lst
>>>
>>> # Update Grub's menu:
>>> update-grub
>>>
>>> # Configure the system to start Xen on every boot:
>>> update-rc.d xend defaults 20 21
>>> update-rc.d xendomains defaults 21 20
>>>
>>> # Reboot into you new Hypervisor
>>> reboot
>>>
>>> # If you have a root file system of your dom0 on LVM (or even LVM on top
>>> of raid1), you probaly can't boot your dom0.
>>> # So, if you see this prompt:
>>>
>>> (initramfs)
>>>
>>> # Run the following command to continue the system boot at (initramfs)
>>> prompt :
>>> (initramfs) lvm vgchange -ay
>>> (initramfs) exit
>>>
>>> Welcome to your new hypervisor!
>>>
>>> Regards,
>>> Thiago
>>>
>>>
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@lists.xensource.com
>>> http://lists.xensource.com/xen-devel
>>>
>>>
>>
>

[-- Attachment #1.2: Type: text/html, Size: 6366 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel