From 7265cfa85ab7659cb729d76c41d104fe472cdbd2 Mon Sep 17 00:00:00 2001 From: mario Date: Tue, 9 Aug 2011 09:44:28 -0300 Subject: system/xen: Updated for version 4.1.1. Signed-off-by: Niels Horn --- system/xen/dom0/README.dom0 | 4 ++-- system/xen/dom0/kernel-xen.sh | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) (limited to 'system/xen/dom0') diff --git a/system/xen/dom0/README.dom0 b/system/xen/dom0/README.dom0 index 9241dda1b3..b58639c949 100644 --- a/system/xen/dom0/README.dom0 +++ b/system/xen/dom0/README.dom0 @@ -34,10 +34,10 @@ and Xen VMM, and packages them up as a single file that looks like a bzImage Linux kernel. For example this is how mbootpack works: # cd /boot -# gzip -d -c /boot/xen-4.1.0.gz > /boot/xen-4.1.0 +# gzip -d -c /boot/xen-4.1.1.gz > /boot/xen-4.1.1 # gzip -d -c /boot/initrd-xen.gz > /boot/initrd-xen # mbootpack -o /boot/vmlinuz-2.6.34.7-xen -m /usr/src/linux-2.6.34.7-xen/vmlinux \ - -m /boot/initrd-xen /boot/xen-4.1.0 + -m /boot/initrd-xen /boot/xen-4.1.1 After a new kernel image is created, add something like the folowing to lilo.conf: diff --git a/system/xen/dom0/kernel-xen.sh b/system/xen/dom0/kernel-xen.sh index efbd6d9e01..75b4baff06 100644 --- a/system/xen/dom0/kernel-xen.sh +++ b/system/xen/dom0/kernel-xen.sh @@ -12,7 +12,7 @@ VERSION=${VERSION:-2.6.34.7} SVERSION=${SVERSION:-2.6.34-6} # Xen version -XVERSION=${XVERSION:-4.1.0} +XVERSION=${XVERSION:-4.1.1} BOOTLOADER=${BOOTLOADER:-lilo} -- cgit v1.2.3