Xen 3.3 install from source on centos 5.2

[David Brain]

Hi,

Are there any guides or pointers as to how to perform a 3.3 install  
from source install on Centos 5.2?  I'm having some issues and would  
really like to be able to find some docs on how this is supposed to be  
done.

Thanks,

David.





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

Here are my experiences:

I use xen 3.2.1 (3.3.0 seems to be too buggy). The hypervisor is 64bit
(some servers have more than 16GB of RAM), but all domains (including
dom0) are 32bit PAE, because a 64bit dom0 - for example - can't migrate
a 32bitdomU, but a 32bit domU can migrate a 64bit domU, AFAIK. So,
accordint to my experiences, 32bit PAE domains (with the original
xen.org kernels, if you can afford it) running on a 64bit hypervisor
seem to be the best soulution to utilize a beast like your machine. Xen
3.2.1 seems to be fast, and reliable.

I compiled xen the following way:
I downloaded the linux-2.6.18-xen-3.2.0 kernel and xen-3.2.1 separately,
and then first, i compiled the kernel by:

gzip -dc /proc/config.gz
make menuconfig
<SOME CONFIGURATION, especially don't forget to set "Processor type and
features" -> "High Memory Support" to 64GB in order to make it a PAE
kernel>
make
<During the building process, i watch this video:
http://www.youtube.com/watch?v=PLyTrsk1Ey8>
make install
make modules_install
mkinitrd <IN SOME WAY>

After compiling and installing the kernel, I compiled and installed xen,
but I didn't do a "make world" at all!! I did it the following way:

On a 64 bit machine, or by cross-compiling (i've personally never
tried), I build the hypervisor:

make xen #this creates only the hypervisor (/boot/xen-3.2.1.gz)
make install-xen
After installing, I copy the 64 bit hypervisor (/boot/xen-3.2.1.gz) to
the
32bit target dom0.

And finally I compile and install the tools on the (32bit, of course)
dom0:
make tools #this creates thigs like the xm command, hvm environment,
           #network scripts, etc.

make install-tools


Best regards,

Tamas

2008. 10. 1, szerda keltezéssel 10.09-kor David Brain ezt írta:

> Hi,
>
> Are there any guides or pointers as to how to perform a 3.3 install  
> from source install on Centos 5.2?  I'm having some issues and would  
> really like to be able to find some docs on how this is supposed to be  
> done.
>
> Thanks,
>
> David.
>
>
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@...
> http://lists.xensource.com/xen-users

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

[Joseph L. Casale]

>Are there any guides or pointers as to how to perform a 3.3 install
>from source install on Centos 5.2?

Lots in the archives, search markmail.
http://xen.markmail.org/

If your going to simply use the Stock CentOS Xen kernel:

# wget http://bits.xensource.com/oss-xen/release/3.3.0/xen-3.3.0.tar.gz
# tar -xvf xen-3.3.0.tar.gz
# cd xen-3.3.0
# make tools
# make xen
# make install-tools
# make install-xen

Then install deps, such as kernel-xen bridge-utils...
Edit grub, leave the kernel-xen vmlinuz, and change the hypervisor.

Maybe make a new initrd? I had issues getting certain modules to load
automagically, so I included them in my initrd.
# mkinitrd -f --preload=pciback --with=netbk --with=xenblk --with=blktap --with=blkbk --with=netloop /boot/initrd-$(uname -r).img $(uname -r)

Run #chkconfig xend on

HTH,
jlc


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

[Robert Dunkley]

I seem to be able to migrate 32bit and 64bit HVMs on my 64bit Centos 5.2 Xen 3.30 Dom 0s.

-----Original Message-----
From: xen-users-bounces@... [mailto:xen-users-bounces@...] On Behalf Of Nemeth, Tamas
Sent: 01 October 2008 15:18
To: xen-users@...
Cc: David Brain
Subject: Re: [Xen-users] Xen 3.3 install from source on centos 5.2

Here are my experiences:

I use xen 3.2.1 (3.3.0 seems to be too buggy). The hypervisor is 64bit
(some servers have more than 16GB of RAM), but all domains (including
dom0) are 32bit PAE, because a 64bit dom0 - for example - can't migrate
a 32bitdomU, but a 32bit domU can migrate a 64bit domU, AFAIK. So,
accordint to my experiences, 32bit PAE domains (with the original
xen.org kernels, if you can afford it) running on a 64bit hypervisor
seem to be the best soulution to utilize a beast like your machine. Xen
3.2.1 seems to be fast, and reliable.

I compiled xen the following way:
I downloaded the linux-2.6.18-xen-3.2.0 kernel and xen-3.2.1 separately,
and then first, i compiled the kernel by:

gzip -dc /proc/config.gz
make menuconfig
<SOME CONFIGURATION, especially don't forget to set "Processor type and
features" -> "High Memory Support" to 64GB in order to make it a PAE
kernel>
make
<During the building process, i watch this video:
http://www.youtube.com/watch?v=PLyTrsk1Ey8>
make install
make modules_install
mkinitrd <IN SOME WAY>

After compiling and installing the kernel, I compiled and installed xen,
but I didn't do a "make world" at all!! I did it the following way:

On a 64 bit machine, or by cross-compiling (i've personally never
tried), I build the hypervisor:

make xen #this creates only the hypervisor (/boot/xen-3.2.1.gz)
make install-xen
After installing, I copy the 64 bit hypervisor (/boot/xen-3.2.1.gz) to
the
32bit target dom0.

And finally I compile and install the tools on the (32bit, of course)
dom0:
make tools #this creates thigs like the xm command, hvm environment,
           #network scripts, etc.

make install-tools


Best regards,

Tamas

2008. 10. 1, szerda keltezéssel 10.09-kor David Brain ezt írta:

> Hi,
>
> Are there any guides or pointers as to how to perform a 3.3 install  
> from source install on Centos 5.2?  I'm having some issues and would  
> really like to be able to find some docs on how this is supposed to be  
> done.
>
> Thanks,
>
> David.
>
>
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@...
> http://lists.xensource.com/xen-users

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

The SAQ Group
Registered Office: 18 Chapel Street, Petersfield, Hampshire. GU32 3DZ
SEMTEC Limited trading as SAQ is Registered in England & Wales
Company Number: 06481952

http://www.saqnet.co.uk AS29219
SAQ Group Delivers high quality, honestly priced communication and I.T. services to UK Business.
DSL : Domains : Email : Hosting : CoLo : Servers : Racks : Transit : Backups : Managed Networks : Remote Support.

Find us in http://www.thebestof.co.uk/petersfield


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

Then it may be fixed now. Former versions were positively unable to do
so.

2008. 10. 1, szerda keltezéssel 15.19-kor Robert Dunkley ezt írta:

> I seem to be able to migrate 32bit and 64bit HVMs on my 64bit Centos 5.2 Xen 3.30 Dom 0s.
>
> -----Original Message-----
> From: xen-users-bounces@... [mailto:xen-users-bounces@...] On Behalf Of Nemeth, Tamas
> Sent: 01 October 2008 15:18
> To: xen-users@...
> Cc: David Brain
> Subject: Re: [Xen-users] Xen 3.3 install from source on centos 5.2
>
> Here are my experiences:
>
> I use xen 3.2.1 (3.3.0 seems to be too buggy). The hypervisor is 64bit
> (some servers have more than 16GB of RAM), but all domains (including
> dom0) are 32bit PAE, because a 64bit dom0 - for example - can't migrate
> a 32bitdomU, but a 32bit domU can migrate a 64bit domU, AFAIK. So,
> accordint to my experiences, 32bit PAE domains (with the original
> xen.org kernels, if you can afford it) running on a 64bit hypervisor
> seem to be the best soulution to utilize a beast like your machine. Xen
> 3.2.1 seems to be fast, and reliable.
>
> I compiled xen the following way:
> I downloaded the linux-2.6.18-xen-3.2.0 kernel and xen-3.2.1 separately,
> and then first, i compiled the kernel by:
>
> gzip -dc /proc/config.gz
> make menuconfig
> <SOME CONFIGURATION, especially don't forget to set "Processor type and
> features" -> "High Memory Support" to 64GB in order to make it a PAE
> kernel>
> make
> <During the building process, i watch this video:
> http://www.youtube.com/watch?v=PLyTrsk1Ey8>
> make install
> make modules_install
> mkinitrd <IN SOME WAY>
>
> After compiling and installing the kernel, I compiled and installed xen,
> but I didn't do a "make world" at all!! I did it the following way:
>
> On a 64 bit machine, or by cross-compiling (i've personally never
> tried), I build the hypervisor:
>
> make xen #this creates only the hypervisor (/boot/xen-3.2.1.gz)
> make install-xen
> After installing, I copy the 64 bit hypervisor (/boot/xen-3.2.1.gz) to
> the
> 32bit target dom0.
>
> And finally I compile and install the tools on the (32bit, of course)
> dom0:
> make tools #this creates thigs like the xm command, hvm environment,
>            #network scripts, etc.
>
> make install-tools
>
>
> Best regards,
>
> Tamas
>
> 2008. 10. 1, szerda keltezéssel 10.09-kor David Brain ezt írta:
> > Hi,
> >
> > Are there any guides or pointers as to how to perform a 3.3 install  
> > from source install on Centos 5.2?  I'm having some issues and would  
> > really like to be able to find some docs on how this is supposed to be  
> > done.
> >
> > Thanks,
> >
> > David.
> >
> >
> >
> >
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@...
> > http://lists.xensource.com/xen-users
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@...
> http://lists.xensource.com/xen-users
>
> The SAQ Group
> Registered Office: 18 Chapel Street, Petersfield, Hampshire. GU32 3DZ
> SEMTEC Limited trading as SAQ is Registered in England & Wales
> Company Number: 06481952
>
> http://www.saqnet.co.uk AS29219
> SAQ Group Delivers high quality, honestly priced communication and I.T. services to UK Business.
> DSL : Domains : Email : Hosting : CoLo : Servers : Racks : Transit : Backups : Managed Networks : Remote Support.
>
> Find us in http://www.thebestof.co.uk/petersfield
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@...
> http://lists.xensource.com/xen-users

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

[Joseph L. Casale]

>I use xen 3.2.1 (3.3.0 seems to be too buggy).
>Xen 3.2.1 seems to be fast, and reliable.

Yeah, I agree but I understand current tree has many fixes, no time to mess around yet.

>I compiled xen the following way:
>I downloaded the linux-2.6.18-xen-3.2.0 kernel and xen-3.2.1 separately,
>and then first, i compiled the kernel by:

><During the building process, i watch this video:
>http://www.youtube.com/watch?v=PLyTrsk1Ey8>

Hilarious...

>make install
>make modules_install
>mkinitrd <IN SOME WAY>

Hrm, make modules_install? I wonder if this has anything to do with my method
posted above using the stock CentOS Xen Kernel and modules not loading w/o putting
them in the initrd? After a reboot they don't reload on their own so I had to build
the initrd as I stated.

Thanks!
jlc

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

[bomparto]

Hello list,

On a DELL PE 1430 with 2 quad core Intel CPU and 8 Go RAM we're running xen 3.3 over a Debian Etch with an iSCSI SAN using LVM on iscsi disks.

We have several DomU runnin on it :

•  Win2k3 rc2 HVM running GLPV drivers
• slackware PV Domu running samba 3
• ect..

We're encounting some pb :

• Win2k3 time out wen it tries to use network between himsel and the samba Domu (no pb with other physical machine or linux Domu and linux domU)
• We cannot mount a second drive on our Win2k3 Domu (like a drive D: )
• We can't boot on a VISTA_Business DVD iso file

Here are my DomU config files :

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Win2K3 :

import os, re
arch = os.uname()[4]
if re.search('64', arch):
    arch_libdir = 'lib64'
else:
    arch_libdir = 'lib'


kernel = "/usr/lib/xen/boot/hvmloader"
builder='hvm'

memory = 2048

name = "W2k3-TSE"

dhcp = 'dhcp'

pae=0
acpi=1
apic=1

vcpus = 2
cpus = "4-5"

vif = [ 'mac=00:16:3c:00:00:11' ]
disk = [ 'phy:/dev/SAN-1/win2k3_prod,ioemu:hda,w', 'phy:/dev/SAN-1/win2k3-data,ioemu:hdb,w' ]

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

device_model = '/usr/lib/xen/bin/qemu-dm'
boot='c'

sdl = 0
vnc=1
vnclisten="0.0.0.0"
vncdisplay=1
vncunused=1
vncviewer = 0
nographic = 0
stdvga = 0

serial='pty'
audio = 0
localtime=1
usb=1
keymap='fr'


Slackware SAMBA :

kernel = "/boot/vmlinuz-2.6.18.8-xenU"
memory = 256
name = "PROD-OXA"
cpus = "6-7"
vcpus = 2
apic = 1
acpi = 1

vif = [ '' ]

disk = ['phy:/dev/RAID-1/slack_prod-1_root,sda1,w','phy:/dev/RAID-1/slack_prod-1_usr,sda2,w','phy:/dev/RAID-1/slack_prod-1_var,sda3,w','phy:/dev/SAN-1/data-prod_oxa,sdb1,w', 'phy:/dev/RAID-1/slack_prod-1_swap,sda4,w' ]
root = "/dev/sda1 ro"

boot='c'

vnc=1
vnclisten="0.0.0.0"
vncdisplay=1
vncunused=1

stdvga=0
keymap='fr'

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

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Thank's for help

Olivier

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

2008. 10. 1, szerda keltezéssel 09.22-kor Joseph L. Casale ezt írta:
> >I use xen 3.2.1 (3.3.0 seems to be too buggy).
> >Xen 3.2.1 seems to be fast, and reliable.
>
> Yeah, I agree but I understand current tree has many fixes, no time to mess around yet.

How to do that? I assume, some utility, called "mercurial" is necessary,
but where can I find information about getting and using it?


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

[Joseph L. Casale]

>How to do that? I assume, some utility, called "mercurial" is necessary,
>but where can I find information about getting and using it?

Yeah, rpmforge has mercurial.
#yum install mercurial

Then the readme shows how to pull a fresh clone.

jlc


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

[Andrew Lyon]

On Wed, Oct 1, 2008 at 4:46 PM, Olivier Bompart <obompart@...> wrote:

> Hello list,
>
> On a DELL PE 1430 with 2 quad core Intel CPU and 8 Go RAM we're running xen
> 3.3 over a Debian Etch with an iSCSI SAN using LVM on iscsi disks.
>
> We have several DomU runnin on it :
>
>  Win2k3 rc2 HVM running GLPV drivers
> slackware PV Domu running samba 3
> ect..
>
> We're encounting some pb :
>
> Win2k3 time out wen it tries to use network between himsel and the samba
> Domu (no pb with other physical machine or linux Domu and linux domU)
> We cannot mount a second drive on our Win2k3 Domu (like a drive D: )
> We can't boot on a VISTA_Business DVD iso file
>
> Here are my DomU config files :
>
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> Win2K3 :
>
> import os, re
> arch = os.uname()[4]
> if re.search('64', arch):
>     arch_libdir = 'lib64'
> else:
>     arch_libdir = 'lib'
>
>
> kernel = "/usr/lib/xen/boot/hvmloader"
> builder='hvm'
>
> memory = 2048
>
> name = "W2k3-TSE"
>
> dhcp = 'dhcp'
>
> pae=0
> acpi=1
> apic=1
>
> vcpus = 2
> cpus = "4-5"
>
> vif = [ 'mac=00:16:3c:00:00:11' ]
> disk = [ 'phy:/dev/SAN-1/win2k3_prod,ioemu:hda,w',
> 'phy:/dev/SAN-1/win2k3-data,ioemu:hdb,w' ]
>
> on_poweroff = 'destroy'
> on_reboot   = 'restart'
> on_crash    = 'restart'
>
> device_model = '/usr/lib/xen/bin/qemu-dm'
> boot='c'
>
> sdl = 0
> vnc=1
> vnclisten="0.0.0.0"
> vncdisplay=1
> vncunused=1
> vncviewer = 0
> nographic = 0
> stdvga = 0
>
> serial='pty'
> audio = 0
> localtime=1
> usb=1
> keymap='fr'
>
>
> Slackware SAMBA :
>
> kernel = "/boot/vmlinuz-2.6.18.8-xenU"
> memory = 256
> name = "PROD-OXA"
> cpus = "6-7"
> vcpus = 2
> apic = 1
> acpi = 1
>
> vif = [ '' ]
>
> disk =
> ['phy:/dev/RAID-1/slack_prod-1_root,sda1,w','phy:/dev/RAID-1/slack_prod-1_usr,sda2,w','phy:/dev/RAID-1/slack_prod-1_var,sda3,w','phy:/dev/SAN-1/data-prod_oxa,sdb1,w',
> 'phy:/dev/RAID-1/slack_prod-1_swap,sda4,w' ]

Change the sdX to hdX and you will probably find your problem solved.

Andy

> root = "/dev/sda1 ro"
>
> boot='c'
>
> vnc=1
> vnclisten="0.0.0.0"
> vncdisplay=1
> vncunused=1
>
> stdvga=0
> keymap='fr'
>
> on_poweroff = 'destroy'
> on_reboot   = 'restart'
> on_crash    = 'restart'
>
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Thank's for help
>
> Olivier
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@...
> http://lists.xensource.com/xen-users
>

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