Hackery Xen 4.0.1-rc1 source & kernels packaged for Ubuntu Lucid @Virtualusr Site up to 4.0.1-rc3

Following bellow is attempt to debianize Xen 4.0.1-rc3,in other words to build debian packages been installed on recent Ubuntu 10.04 (9.10) servers set corresponding version of Hypervisor up. We follow closely posting [1], attempting to fix errors in patching of current version of /etc/init.d/xend.

wget http://virtualusr.files.wordpress.com/2010/06/mk-xen40x6.doc
catdoc mk-xen40x6.doc > mk-xen40x.sh
sh mk-xen40x.sh

Then
# gunzip xen-4.0_4.0.1rc1-0ubuntu1.diff.gz
Edit xen-4.0_4.0.1rc1-0ubuntu1.diff and replace line 835
+xen-4.0 (4.0.1rc1-0ubuntu1) karmic; urgency=low
by
+xen-4.0 (4.0.1rc3-0ubuntu1) karmic; urgency=low

# cp xen-4.0_4.0.1rc1-0ubuntu1.diff xen-4.0_4.0.1rc3-0ubuntu1.diff
# gzip xen-4.0_4.0.1rc3-0ubuntu1.diff
# ./packageXen40x.sh 4.0.1-rc3

Build succeed:-
root@ServerLDX:/usr/src/build# find . -name “*.deb” -print
./400/xen-docs-4.0_4.0.1rc3-0ubuntu1_all.deb
./400/libxen4-dev_4.0.1rc3-0ubuntu1_amd64.deb
./400/libxen4_4.0.1rc3-0ubuntu1_amd64.deb
./400/xen-hypervisor-4.0_4.0.1rc3-0ubuntu1_amd64.deb
./400/xen-utils-4.0_4.0.1rc3-0ubuntu1_amd64.deb
./400/python-xen-4.0_4.0.1rc3-0ubuntu1_amd64.deb
*******************************************************************************************************************************************
UPDATE 06/22/2010 Due to new errors followed by update “Xen 4.0.1-rc2 … source & kernels packaged for Ubuntu”

Xen 4.0.1-rc2 … source & kernels packaged for Ubuntu


I’ve uploaded to launchpad.net the most recent xen-4.0_4.0.1rc3-0ubuntu1.diff.gz correct version ( per User Virtual )
** Patch added: “xen-4.0_4.0.1rc3-0ubuntu1.diff.gz” http://launchpadlibrarian.net/50750244/xen-4.0_4.0.1rc3-0ubuntu1.diff.gz Packages may be built via original version packageXen40x.sh :-
# ./packageXen40x.sh 4.0.1-rc3
*******************************************************************************************************************************************
Install debian packages been built and load 2.6.32.15 ( which requires rc2) under Xen 4.0.1-rc3 Hypervisor

Make sure:-

root@ServerLNX:/dev/xen# ls -l
total 0
crw-rw---- 1 root root 10, 60 2010-06-17 16:15 evtchn
crw-rw---- 1 root root 10, 59 2010-06-17 16:15 gntdev

It’s a fair . Udevd created evtchn device required for successful xend start under pvops 2.6.32.15. Edit xend, removing attempt to load xen-evtchn module, which in best case scenario would do nothing in worst
case crash xend.

# /etc/init.d/xend start

root@ServerLNX:~# xm info
host : ServerLNX
release : 2.6.32.15
version : #8 SMP Sun Jun 13 14:34:17 MSD 2010
machine : x86_64
nr_cpus : 2
nr_nodes : 1
cores_per_socket : 2
threads_per_core : 1
cpu_mhz : 2999
hw_caps : bfebfbff:20100800:00000000:00000940:0008e3fd:00000000:00000001:00000000
virt_caps : hvm
total_memory : 8191
free_memory : 1666
node_to_cpu : node0:0-1
node_to_memory : node0:1666
node_to_dma32_mem : node0:805
max_node_id : 0
xen_major : 4
xen_minor : 0
xen_extra : .1-rc3
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : unavailable
xen_commandline :
cc_compiler : gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5)
cc_compile_by : root
cc_compile_domain :
cc_compile_date : Thu Jun 17 15:24:31 MSD 2010
xend_config_format : 4

root@ServerLNX:~# brctl show
bridge name bridge id STP enabled interfaces
eth1 8000.00221563f99f no peth1
virbr0 8000.000000000000 yes

root@ServerLNX:~# virsh version
Compiled against library: libvir 0.8.1
Using library: libvir 0.8.1
Using API: Xen 3.0.1
Running hypervisor: Xen 4.0.0


References
1. http://virtualusr.wordpress.com/2010/05/26/xen-4-0-1-rc1-source-kernels-packaged-for-ubuntu/

One Response to Hackery Xen 4.0.1-rc1 source & kernels packaged for Ubuntu Lucid @Virtualusr Site up to 4.0.1-rc3

  1. www says:

    I just could not leave your website before suggesting that I extremely loved the standard information a person
    provide for your visitors? Is going to be again continuously to investigate cross-check new posts

Leave a comment