Gitco is providing http://www.gitco.de/repo/src/xen-3.3.1-0.src.rpm for free download. It gives an immediate option to back port Pygrub ZFS support from Xen 3.4-testing mercurial tree. Raw content of CSs 19322,19323 is supposed to be placed into patch files under /usr/src/redhat/SOURCES.
File /usr/src/redhat/SPECS/xen-3.3.1.spec gets updated to process two more patches added to SOURCES. The last step is to run rpmbuild to create RPMS with patches to be installed instead of original ones from http://gitco.de. Details follow bellow:-
# yum -y install transfig texi2html tetex-latex gtk2-devel libaio-devel gnutls-devel
# yum update ecryptfs-utils
[root@ServerXen ~]# wget http://www.gitco.de/repo/src/xen-3.3.1-0.src.rpm
--16:03:02-- http://www.gitco.de/repo/src/xen-3.3.1-0.src.rpm
Resolving www.gitco.de... 78.47.43.57
Connecting to www.gitco.de|78.47.43.57|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 11381385 (11M) [application/x-redhat-package-manager]
Saving to: `xen-3.3.1-0.src.rpm'
100%[========================================================>] 11,381,385 82.0K/s in 97s
16:04:39 (115 KB/s) - `xen-3.3.1-0.src.rpm' saved [11381385/11381385]
[root@ServerXen ~]# rpm -iv xen-3.3.1-0.src.rpm
Edit correspondently:-
# vi /etc/yum.conf
gpgcheck=0
# vi /etc/yum.repos.d/XEN.repo
[xen]
name=CentOS-$releasever - XEN
baseurl=http://www.gitco.de/repo/xen3.3.1
gpgcheck=0
Change directory to /usr/src/redhat and add required change sets to SOURCES as patches
[root@ServerXen redhat]# ls -l
total 40
drwxr-xr-x 3 root root 4096 Jun 7 13:07 BUILD
drwxr-xr-x 4 root root 4096 Jan 28 15:54 RPMS
drwxr-xr-x 2 root root 4096 Jun 7 13:01 SOURCES
drwxr-xr-x 2 root root 4096 Jun 7 13:06 SPECS
drwxr-xr-x 2 root root 4096 Jun 7 13:19 SRPMS
[root@ServerXen redhat]# cd SOURCES
[root@ServerXen SOURCES]# ls -l
total 11116
-rw-r--r-- 1 root root 1296 Jan 21 00:47 xen-3.3.1-config.patch
-rw-r--r-- 1 root root 1779 Jan 21 00:47 xen-3.3.1-dumpdir.patch
-rw-r--r-- 1 root root 1335 Jun 7 13:01 xen-3.3.1-hg19322.patch
-rw-r--r-- 1 root root 1392 Jun 7 13:01 xen-3.3.1-hg19323.patch
-rw-r--r-- 1 root root 2229 Jan 21 00:47 xen-3.3.1-hotplug-locking-rhel.patch
-rw-r--r-- 1 root root 7063 Jan 21 00:47 xen-3.3.1-initscripts.patch
-rw-r--r-- 1 root root 11329774 Jan 5 15:28 xen-3.3.1.tar.gz
-rwx------ 1 root root 325 Aug 26 2008 xen.sysconfig
[root@ServerXen SOURCES]# cd ../SPECS
[root@ServerXen SPECS]# ls -l
total 36
-rw-r--r-- 1 root root 35130 Jun 7 13:06 xen-3.3.1.spec
Modify spec file correspondently :-
[root@ServerXen SPECS]# vi xen-3.3.1.spec
. . . . .
Patch1: %{name}-%{version}-initscripts.patch
Patch2: %{name}-%{version}-hotplug-locking-rhel.patch
Patch3: %{name}-%{version}-dumpdir.patch
Patch4: %{name}-%{version}-config.patch
Patch5: %{name}-%{version}-hg19322.patch
Patch6: %{name}-%{version}-hg19323.patch
. . . . . . . . . . .
%patch1 -p1 -b .init
%patch2 -p1
%patch3 -p1
%patch4 -p1
%patch5 -p1
%patch6 -p1
:wq
Now build
[root@ServerXen SOURCES]# rpmbuild -ba ./xen-3.3.1.spec
When done install ( or reinstall patched RPMS)
[root@ServerXen SPECS]# cd ../RPMS/x86_64
[root@ServerXen x86_64]# ls -l
total 9724
-rwxr-xr-x 1 root root 131 Jun 7 13:38 install.sh
-rw-r--r-- 1 root root 9268378 Jun 7 13:19 xen-3.3.1-0.x86_64.rpm
-rw-r--r-- 1 root root 228948 Jun 7 13:19 xen-debuginfo-3.3.1-0.x86_64.rpm
-rw-r--r-- 1 root root 260567 Jun 7 13:19 xen-devel-3.3.1-0.x86_64.rpm
-rw-r--r-- 1 root root 161287 Jun 7 13:19 xen-libs-3.3.1-0.x86_64.rpm
[root@ServerXen x86_64]# cat install.sh
yum install xen-3.3.1-0.x86_64.rpm \
xen-debuginfo-3.3.1-0.x86_64.rpm \
xen-devel-3.3.1-0.x86_64.rpm \
xen-libs-3.3.1-0.x86_64.rpm
[root@ServerXen x86_64]# ./install.sh
OpenSolaris 2009.06 PV DomU running at Xen 3.3.1 Dom0 on CentOS 5.2 :-





OpenSolaris 2009.06 PV DomU running at Xen 3.3.1 Dom0 on CentOS 5.3.
Gitco’s system completely reinstalled with patched rpms:-

SSH connection to Xen 3.3.1 Dom0:-

June 7, 2009 at 7:12 pm |
Thanks for the good info, but why would I want to backport to 3.3 instead of using the 3.4 rpms ?
June 7, 2009 at 7:27 pm |
It’s just an option :-/.
Customers sometimes are a bit conservative regarding Xen Hypervisor upgrade. Personally, i would also be very careful upgrading any non-development system to 3.4.
Stubdom seems to be OK now. Take a look at the date of the most recent CS dealing with pv-grub.
June 12, 2009 at 9:28 am |
> Thanks for the good info, but why would I want to
> backport to 3.3 instead of using the 3.4 rpms ?
View:-
http://www.redhat.com/archives/fedora-virt/2009-June/msg00034.html
Quote :-
>Oh yes – Gerd Hoffman has pushed a xen-3.4.0 update to F-11:
Pushed to rawhide. F-11 will follow, but most likely after the 3.4.1 bugfix release.