4 files changed, 7 insertions, 7 deletions
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}
 
diff --git a/system/xen/xen.SlackBuild b/system/xen/xen.SlackBuild
index 71c4d2d3e8..3026e5c03e 100644
--- a/system/xen/xen.SlackBuild
+++ b/system/xen/xen.SlackBuild
@@ -23,7 +23,7 @@
 #  ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
 PRGNAM=xen
-VERSION=${VERSION:-4.1.0}
+VERSION=${VERSION:-4.1.1}
 BUILD=${BUILD:-1}
 TAG=${TAG:-_SBo}
 
diff --git a/system/xen/xen.info b/system/xen/xen.info
index 07066ded27..a38e68cf59 100644
--- a/system/xen/xen.info
+++ b/system/xen/xen.info
@@ -1,8 +1,8 @@
 PRGNAM="xen"
-VERSION="4.1.0"
+VERSION="4.1.1"
 HOMEPAGE="http://www.xen.org/"
-DOWNLOAD="http://bits.xensource.com/oss-xen/release/4.1.0/xen-4.1.0.tar.gz"
-MD5SUM="db3e1542b7719f375593b2b32b01a177"
+DOWNLOAD="http://bits.xensource.com/oss-xen/release/4.1.1/xen-4.1.1.tar.gz"
+MD5SUM="fab4bf74d73444ff9b43bced2e4fc5a2"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
 MAINTAINER="mario"