Xen on RHEL6, Scientific Linux 6, CentOS 6 howto
As any user of an EL6 distro would know, the basis of the EL6 packages are RHEL6. Sadly, Redhat dropped support for Xen in v6 – preferring KVM as their corporate solution. Personally, I don’t think this was the correct decision. This mini-howto will give the basics of setting up the Xen Dom0. From there, any Xen tutorial will cover the basics (and some more advanced) functionality of Xen guests (both Windows and Linux).
Support?
I run a mailing list on lists.wireless.org.au which is available for peer support and suggestions. I will also post announcements to this list on new builds and testing as new developments emerge.
NOTE: 32 bit packages are currently in testing… Feedback gladly accepted!
Step 1
Download and install your base OS. I personally use Scientific Linux 6. After downloading and burning the DVD, perform a minimal install adding packages you require.
Step 2
Install the bridge-utils package.
# yum install bridge-utils
Step 3
Enable my Xen Repo for x86_64:
# yum install http://www.crc.id.au/repo/x86_64/kernel-xen-release-6-3.noarch.rpm
Step 4
Install the Xen hypervisor and Dom0 Kernel:
# yum install kernel-xen xen
Step 5
Modify your /etc/grub.conf to firstly load the Xen hypervisor, then boot your OS. A correctly modified grub.conf should look something like the following:
title Scientific Linux (2.6.32-4.el6xen.x86_64)
root (hd0,0)
kernel /xen.gz dom0_mem=1024M cpufreq=xen dom0_max_vcpus=1 dom0_vcpus_pin
module /vmlinuz-2.6.32-4.el6xen.x86_64 ro root=/dev/mapper/RAID1-xenhost rd_LVM_LV=RAID1/xenhost rd_MD_UUID=afb92c19:b9b1e3ae:07af315d:738e38be rd_NO_LUKS rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us crashkernel=auto
module /initramfs-2.6.32-4.el6xen.x86_64.img
Step 6
Disable SELinux. While selinux is a great idea, it really screws with Xen. If there is anyone out there who wants to wade through what should be set for selinux to be enabled and still have Xen working, please email me! In the mean time, disable it by editing the following file:
/etc/sysconfig/selinux
# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
# enforcing - SELinux security policy is enforced.
# permissive - SELinux prints warnings instead of enforcing.
# disabled - No SELinux policy is loaded.
SELINUX=disabled
# SELINUXTYPE= can take one of these two values:
# targeted - Targeted processes are protected,
# mls - Multi Level Security protection.
SELINUXTYPE=targeted
Step 7
Reboot into your new Xen kernel and test:
# xm info
host : xenhost.lan.crc.id.au
release : 2.6.32-4.el6xen.x86_64
version : #1 SMP Fri Jul 8 01:19:26 EST 2011
machine : x86_64
nr_cpus : 4
nr_nodes : 1
cores_per_socket : 2
threads_per_core : 2
cpu_mhz : 3325
hw_caps : bfebfbff:28100800:00000000:00003f40:0298e3bf:00000000:00000001:00000000
virt_caps : hvm
total_memory : 7989
free_memory : 2113
free_cpus : 0
xen_major : 4
xen_minor : 1
xen_extra : .1
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 : dom0_mem=1024M cpufreq=xen dom0_max_vcpus=1 dom0_vcpus_pin
cc_compiler : gcc version 4.4.4 20100726 (Red Hat 4.4.4-13) (GCC)
cc_compile_by : root
cc_compile_domain : (none)
cc_compile_date : Thu Jun 30 18:11:34 EST 2011
xend_config_format : 4
Edit History:
2012-02-12 – Changed installation method to use kernel-xen-release package.
2012-02-18 – Changed note for 32 bit version. It should now work! Modified path to kernel-xen-release for new repo structure.
????????? XEN Dom0 ? CentOS 6.0 | ??? ???? says:
[...] ??? ?? ??????????, ? ????????? ?? ???? ? ????? Steven Haigh (http://www.crc.id.au/xen-on-rhel6-scientific-linux-6-centos-6-howto/), ? ??????? ???? ??????? ????????? XEN ?? ??? ??????? [...]
July 27, 2011, 9:12 pmLarry says:
After adding your repo with the given command I receive this when trying to install kernel-xen and xen:
Error: File contains no section headers.
August 1, 2011, 5:57 amfile: file://///etc/yum.repos.d/kernel-xen.repo, line: 1
‘\n’
Steven Haigh says:
Whoops! Looks like when I synced the repo, I accidentally deleted the kernel-xen.repo file! I’ve readded it to the repo and you should start this howto again (at the curl line).
August 1, 2011, 8:04 amLarry says:
Does your dom0 kernel allow for PVUSB?
August 2, 2011, 1:27 pmSteven Haigh says:
Hi Larry,
I can’t say I’ve tested PVUSB – but in theory – it should work.
August 2, 2011, 1:33 pmKim Quyen says:
I compile Kernel 3.0.0 on my CentOS, how about “kernel-xen”?
August 4, 2011, 4:02 pmSteven Haigh says:
I’m not quite sure what you are asking, but Kernel 3.0.0 won’t work as a Xen Dom0 out of the box. The kernel-xen packages are based off the long maintained kernel.org xen kernel source.
August 4, 2011, 4:49 pmPhoenix2life says:
Thanks for sharing these steps.
I have completed Step 3 successfully and
on Step 4, I am getting following message about repo file
[root@centos6host ~]# yum install kernel-xen xen
Loaded plugins: fastestmirror, refresh-packagekit
Config Error: File contains no section headers.
file: file://///etc/yum.repos.d/kernel-xen.repo, line: 1
‘\r\n’
Please help.
August 7, 2011, 4:12 pmSteven Haigh says:
Make sure that you put the entire command in step 3 on one line! You want to save the file to /etc/yum.repos.d/
August 7, 2011, 4:27 pmScott Meyers says:
Good job, Steve and thank you for sharing this with the community.
I was able to get the Kernel and Xen up and running on my i686 arch server following Pasi Kärkkäinen’s tutorial at:
August 14, 2011, 9:40 pmhttp://wiki.xensource.com/xenwiki/RHEL6Xen4Tutorial, but I am unable to
create DomU. The system hangs at the partitioning screen. I exit and try to destroy DomU, but the system won’t delete the domain. Do you think this is a bug in
Xen v4.1.1, or Xen won’t work on i686 arch, or something else? Any idea how can I get Xen to work properly without any
issues on i686 arch? Thank you
Steven Haigh says:
Hi Scott,
I don’t personally run any i686 Xen installs, but it should still work. If your hardware will run 64 bit mode, its a much better idea to run Dom0 as 64 bit. Not only does this help if you go above 4Gb of RAM (which is very likely running Xen), but it gives you the option of running both 64 and 32 bit DomUs.
I vary a bit in the way I set things up. I install a stock Scientific Linux install, then my xen and kernel-xen packages. From there, I create text configuration files in /etc/xen/. There are plenty of examples in there on how to set the file up – and its pretty straight forward. As such, I don’t actually run a GUI on Dom0.
That being said, to get the best performance, you would be better to adapt my guide on setting up Xen DomUs without partitioning anything – especially if you have the DomUs on RAID arrays…
August 15, 2011, 12:17 amScott Meyers says:
It is a kernel issue. When I try to create a DomU, the system get stuck at:
Waiting for required block device discovery
Waiting for 4 sda-like device(s)…
Two bug reports made about this error, but no solution yet. Is it possible to modify your 86_64 kernel for i686 arch? If so, can you email me a copy of the .config file to modify, or you can modify it, and I will compile it on my Dell PE1950 server. If every thing goes smoothly, you have the option to put a copy for i686 arch on your site. Thanks
August 21, 2011, 4:09 amSteven Haigh says:
Hi Scott, What kernel are you using for the DomU? If you run a supported PV enabled kernel (such as EL6), then you should be able to use the stock kernel. I would however pass xvda as your first disk, not sda. I assume you are using my kernel as the Dom0, then something else (hopefully stock!) for the DomU?
August 21, 2011, 11:46 amScott Meyers says:
I’ve been using kernel.org/pub/scm/linux/kernel/git/jeremy/
xen/stable-2.6.32.x origin/xen/stable-2.6.32.x. I modified its .config file and built a new kernel successfully. But I am unable to create DomU. It gets stuck at:
XENBUS: Timeout connecting to device: device/vbd/51713 (local state 3, remote state 1)
XENBUS: Timeout connecting to device: device/vbd/51714 (local state 3, remote state 1)
XENBUS: Device with no driver: device/console/0
Tried different disk methods: tap:aio:/ and phy:/ and file:/ with diskimage.img,xvda1,w but keep getting the same error message. I do not use LVM, though. I have 3 partitions: / and /boot and /vm on RAID1 machine.
August 22, 2011, 4:10 pmSteven Haigh says:
Hi Scott,
Have you tried an install of a proper DomU aware distribution such as Scientific Linux 6? These should work out of the box. This would also give you an indication if the problem is your kernel or not.
August 22, 2011, 4:21 pmSam says:
Hi Steven,
Thanks for sharing this. I had no problem till step 5. Since I am using SL 6.1, I modified grub.conf as below:
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/mapper/vg_uccshost6-lv_root
# initrd /initrd-[generic-]version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Scientific Linux (2.6.32.45-1.el6xen.x86_64)
root (hd0,0)
kernel /xen.gz dom0_mem=2048M cpufreq=xen dom0_max_vcpus=1 dom0_vcpus_pin
module /vmlinuz-2.6.32.45-1.el6xen.x86_64 ro root=/dev/mapper/vg_uccshost6-lv_root rd_LVM_LV=vg_uccshost6/lv_root rd_LVM_LV=vg_uccshost6/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us crashkernel=auto rhgb quiet
module /initramfs-2.6.32.45-1.el6xen.x86_64.img
title Scientific Linux (2.6.32-131.6.1.el6.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.32-131.6.1.el6.x86_64 ro root=/dev/mapper/vg_uccshost6-lv_root rd_LVM_LV=vg_uccshost6/lv_root rd_LVM_LV=vg_uccshost6/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us crashkernel=auto rhgb quiet
initrd /initramfs-2.6.32-131.6.1.el6.x86_64.img
However, after rebooting, with command #xm list, I got “Error: Unable to connect to xend: No such file or directory. Is xend running?”
Any idea about it?
Much appreciated.
August 24, 2011, 2:14 amSteven Haigh says:
Hi Sam,
Check to see if xend is in fact running. /etc/init.d/xend status will tell you. It should output something like:
If it isn’t running, try turning it on via chkconfig xend on and rebooting.
August 24, 2011, 2:32 amSam says:
xend is in fact running. But I still got the same message after command xm list.
August 24, 2011, 2:39 amRudi says:
I installed XEN as per your instructions and rebooted the server, but got the following error:
0e rip 10:0 error 10 cr2 0
Does anyone know what causes this?
September 2, 2011, 11:45 pmSteven Haigh says:
Hi Rudi,
I came across this on an old AMD Opteron based system that did not support HVM. I was unable to find a fix for it – however I am open to suggestions as to both the cause and any possible fixes for this. As of yet, while I know some systems can get this error and refuse to boot using the Xen kernel, I do not have any idea why this occurs.
September 3, 2011, 12:37 amIra says:
Have the same issue as Rudi on an Intel i2600 in a DQ67SW motherboard. Any fresh ideas? Setup is running bios raid0.
September 15, 2011, 2:13 pmSteven Haigh says:
Nothing at the moment. Can I suggest downloading the linux kernel source, building it up and seeing if it runs on your hardware?
As another idea, can you build the SRPM provided here on your hardware? Without having access to the hardware, its almost impossible to debug as its either a problem with the hardware (BIOS update maybe?), a bug in the linux kernel, or a problem with options that only seem to affect certain subset of hardware.
September 15, 2011, 9:51 pmcb says:
I tried
s> yum makecache
Here is what I am getting (see below) I do not think there is a H/W restriction but likely an issue with how the yum set up is on that machine. Can you look and provide pointers/advice — thanks in advance
September 16, 2011, 5:11 am###
s# yum install kernel-xen xen
Loaded plugins: fastestmirror, presto
Loading mirror speeds from cached hostfile
* base: updates.interworx.info
* extras: centos.mirror.lstn.net
* updates: mirror.ubiquityservers.com
Setting up Install Process
No package kernel-xen available.
No package xen available.
Error: Nothing to do
s# yum search xen
Loaded plugins: fastestmirror, presto
Loading mirror speeds from cached hostfile
* base: updates.interworx.info
* extras: centos.mirror.lstn.net
* updates: mirror.raystedman.net
======================================================== Matched: xen ========================================================
hunspell-eu.noarch : Basque hunspell dictionaries
python-virtinst.noarch : Python modules and utilities for installing virtual machines
virt-manager.noarch : Virtual Machine Manager
Steven Haigh says:
Hi cb. Looks like you had an issue with Step 3. From what I can see there, my kernel-xen repository is not being considered or looked at. Check to see if you have a file /etc/yum.repos.d/kernel-xen.repo and if so, try:
September 16, 2011, 10:24 amyum clean allyum install kernel-xen xen
cb says:
Steven thanks — here are the results:
s#yum clean all
Loaded plugins: fastestmirror, presto
Cleaning up Everything
Cleaning up list of fastest mirrors
0 delta-package files removed, by presto
s#yum install kernel-xen xen
Loaded plugins: fastestmirror, presto
Determining fastest mirrors
* base: mirrors.ecvps.com
* extras: mirror.ubiquityservers.com
* updates: mirror.anl.gov
base | 3.7 kB 00:00
base/primary_db | 3.3 MB 00:02
extras | 951 B 00:00
extras/primary | 201 B 00:00
kernel-xen | 1.3 kB 00:00
kernel-xen/primary | 4.7 kB 00:00
kernel-xen 13/13
updates | 3.5 kB 00:00
updates/primary_db | 3.1 MB 00:02
Setting up Install Process
No package kernel-xen available.
No package xen available.
Error: Nothing to do
What could be next steps? thanks for your time
September 16, 2011, 2:09 pmcb says:
also:
s#ls -l /etc/yum.repos.d/kernel-xen.repo
-rw-r–r–. 1 root root 87 Sep 15 19:56 /etc/yum.repos.d/kernel-xen.repo
s#more !$
September 16, 2011, 2:11 pmmore /etc/yum.repos.d/kernel-xen.repo
[kernel-xen]
name = kernel-xen
baseurl=http://www.crc.id.au/repo/
enabled=1
gpgcheck=0
Steven Haigh says:
That is really strange. It still shows for me.
Does anything show in the following:
# yum list kernel*You should see something like:
September 16, 2011, 9:15 pmcb says:
no joy (see below)
NOTE: If this would factor in: this is a CentOS 6 server install … If I can get specific details
beyond that let me know.
Did I miss a step to ingest a key or some step to get to your repository? Is there any specific tools needed to be installed in advance of using other repos? Is there a yum.conf change needed?
again my thanks for our dialog
September 17, 2011, 1:47 am# yum list kernel*Loaded plugins: fastestmirror, presto
Loading mirror speeds from cached hostfile
* base: mirrors.ecvps.com
* extras: mirror.ubiquityservers.com
* updates: mirror.anl.gov
base | 3.7 kB 00:00
extras | 951 B 00:00
kernel-xen | 1.3 kB 00:00
updates | 3.5 kB 00:00
Installed Packages
kernel.i686 2.6.32-71.el6 @anaconda-centos-201106051823.i386/6.0
kernel.i686 2.6.32-71.29.1.el6 @updates
kernel-firmware.noarch 2.6.32-71.29.1.el6 @updates
Available Packages
kernel-debug.i686 2.6.32-71.29.1.el6 updates
kernel-debug-devel.i686 2.6.32-71.29.1.el6 updates
kernel-devel.i686 2.6.32-71.29.1.el6 updates
kernel-doc.noarch 2.6.32-71.29.1.el6 updates
kernel-headers.i686 2.6.32-71.29.1.el6 updates
Steven Haigh says:
I wonder if CentOS does anything different by default that will ignore unsigned packages… If you try yum with the –nogpgcheck does it give you different results?
September 17, 2011, 9:33 amcb says:
Still no joy — I have to run home for dinner (MT) and will be back on line in a couple of hours
if you have other ideas
thanks for sticking with this
September 17, 2011, 10:22 amcb says:
Are there RPMs available? What access is there for that and process for install?
September 19, 2011, 10:02 amSteven Haigh says:
You can download the RPMs directly from http://www.crc.id.au/repo/
I did however just realise that you seem to be running a 32bit host OS. This is not supported. To use my RPMs you need a 64bit host OS.
Up the top of this article is the following note:
September 19, 2011, 11:22 amNOTE: This howto will *only* work on 64 bit systems. I am in the process of attempting builds of 32 bit packages, however most modern systems that are capable of running Xen correctly should be 64 bit.
cb says:
It is 32-bit — I will rebuild it — really^2 sorry about not reading/paying attention to your note. I was just happy to get XEN on CentOS.
Really am sorry for taking your time. I will update once I have the machine rebuilt on a 64-bit OS (will shoot for CentOS 6.0 again).
September 19, 2011, 12:06 pmcb says:
Given the change to KVM and your position on XEN — any update on the future for where the VMs on Linux are headed? I have had great success with xen to date and on first pass struggle with getting the networking on KVM set up the way I would like.
September 19, 2011, 12:09 pmSteven Haigh says:
From what I understand, the basics for using the stock 3.0 linux kernel as a Dom0 is in place. Xen is quickly becoming fully integrated into the stock kernel and should be just about complete before EL6.3 or so. At that point, the choice between KVM and Xen should be down to personal preference. The reason I continue to use 2.6.32.x as a base is that things seem to be a little more developed and it will take a while to get the same feature set in 3.x as already exists in 2.6.32.x.
September 19, 2011, 1:29 pmcb says:
thanks for the feedback — I am building the x86_64 OS onto the server now. I will send an update when that is in place.
My thanks for your time.
September 19, 2011, 1:46 pmcb says:
Steve,
UPDATE:
I got the machine to start the boot process last night. I am back on this after work today. There is a warning about xenstored not starting and the boot stopped at the xend daemon start. I might need to give it some time, though am off to work and will get back to it late this evening.
Thanks
September 20, 2011, 1:45 amcb says:
Interesting side note: I can ssh into the server but the boot console is holding at the init step of the xen daemon start.
I have had to put this lower in my queue while I try to work on a JBoss Seam issue …
When I make progress I will note it here if that works.
thanks
September 22, 2011, 9:00 amZiming says:
Steve, the yum installation procedure is stuck in primary.xml.gz with error performing checksum. Plz fix the integrity of that file….
September 28, 2011, 8:36 amSteven Haigh says:
Works ok here?
# yum check-update
kernel-xen | 1.3 kB 00:00
kernel-xen/primary | 4.8 kB 00:00
kernel-xen 13/13
Try the following:
September 29, 2011, 1:09 am# yum clean all# yum list kernel-xen*
Steven Haigh says:
Hi, As the title suggests, this is only for EL versions 6.x. This means it will not work on any other version.
September 29, 2011, 9:40 amSteve says:
Just in case anyone is having issues with xend hanging at boot on CentOS 6, I disabled SELinux and it appears to work for me now.
December 3, 2011, 10:29 amPatrick says:
I am trying this with a minimal CentOS 6 64bit, but it doesn’t seem to work for me.
# xm info
Error: Unable to connect to xend: No such file or directory. Is xend running?
Trying to start xend results in no info at all (no error message either), and the log (/var/log/xen/xend.log) is empty as well.
My grub.conf is pretty different though (although still loading xen, and booting without problems), perhaps that is the problem:
timeout 5
default 0
title CentOS Linux (2.6.32.50-1.el6xen.x86_64)
root (hd0,1)
kernel /vmlinuz-2.6.32.50-1.el6xen.x86_64 ro root=/dev/md2 SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=de
initrd /initramfs-2.6.32.50-1.el6xen.x86_64.img
title CentOS Linux (2.6.32-131.17.1.el6.x86_64)
root (hd0,1)
kernel /boot/vmlinuz-2.6.32-131.17.1.el6.x86_64 ro root=/dev/md2
initrd /boot/initrd-2.6.32-131.17.1.el6.x86_64.img
Any help appreciated!
December 11, 2011, 8:34 pmPatrick says:
Update:
Changed the first part of grub.conf to the following:
title CentOS Linux Xen (2.6.32.50-1.el6xen.x86_64)root (hd0,1)
kernel /xen.gz dom0_mem=1024M cpufreq=xen dom0_max_vcpus=1 dom0_vcpus_pin
module /vmlinuz-2.6.32.50-1.el6xen.x86_64 ro root=/dev/md2 SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=de crashkernel=auto
module /initramfs-2.6.32.50-1.el6xen.x86_64.img
And now it does work
December 11, 2011, 9:12 pmSteven Haigh says:
Hi Patrick,
Yep – you need to modify the grub config to load the Xen hypervisor first, then the kernel as you found out. You’ll need to do this on each kernel update. I’m looking for a way to make this work properly with the install to avoid manual configuration, but it looks like dracut doesn’t properly support this as yet. Any suggestions welcome!
December 12, 2011, 12:48 amKyle Brandt says:
My fix for the “Error: Unable to connect to xend: No such file or directory. Is xend running?” error was to disable SELinux.
December 17, 2011, 4:38 amSteven Haigh says:
Hi Kyle, You are correct. SELinux does cause a lot of problems with Xen. As such, I’ve modified the howto to mention this and how to disable it. It’s probably for the best!
December 17, 2011, 1:38 pmJorge Brito says:
Hi Steven Haigh,
I have a question, when i tried to install a guest S.O with: virt-install i get the error:
ERROR Host does not support any virtualization options
In the mainboard of PC i have enabled virtualization option.
I cheked if the service xend is running, and it is ok.
That could be happening?
December 21, 2011, 1:28 pmSteven Haigh says:
Hi Jorge,
What do you get from the output of ‘xm info’? You should see something like this:
December 21, 2011, 3:48 pmxen_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_64Sam, another one ;) says:
So far, the best tutorial on how to install Xen.
No problem for me with CentOS 6.2.
The only thing not described here, for this specific distro, was the bridge-utils rpm with is not good anymore. I had to use bridge-utils-1.2-9.fc13.x86_64.rpm (from Fedora Core 13), and it works like a charm !
Xen with Ubuntu was a nightmare, it’s much more easy with a RHEL6 based distro.
Thanks a lot Steve !!!
January 4, 2012, 4:34 amSteve says:
Hi Steven, Have you got any further with the build on 32bit systems? or it just a no-no?
I have 6 32bit only xen servers and would like to update to centos6, but need the xen built kernel for PV installs.
Thanks again for your efforts.
January 21, 2012, 9:53 amSteven Haigh says:
Sorry, I haven’t created any 32 binaries as yet – nor have I been able to create a successful build environment for it
January 21, 2012, 12:34 pmSteve says:
Well thanks Steven anyway.
just i can not find any reference to 32bit rpms for the 32 bit env at all.
If i were to rebuild the kernel, do you think it could work?
January 21, 2012, 9:58 pmSteven Haigh says:
It should work. If you grab the SRPM for the kernel and modify the config for a 32 bit host, it should work. I haven’t actually done this – however I’d love to hear how you go.
January 21, 2012, 10:15 pmAlcosmurf says:
Worked like charm. Thanks a lot.
January 27, 2012, 11:26 amJoe says:
Thank you Steve. This tutorial is very helpful. Following the listed steps, I successfully brings up CentOS 6.2 with Xen dom0.
However, xenbr0 did not get created because following errors:
# brctl show
bridge name bridge id STP enabled interfaces
virbr0 /sys/class/net/virbr0/bridge: No such file or directory
/sys/class/net/virbr0/bridge: No such file or directory
/sys/class/net/virbr0/bridge: No such file or directory
/sys/class/net/virbr0/bridge: No such file or directory
/sys/class/net/virbr0/bridge: No such file or directory
/sys/class/net/virbr0/bridge: No such file or directory
/sys/class/net/virbr0/bridge: No such file or directory
/sys/class/net/virbr0/bridge: No such file or directory
/sys/class/net/virbr0/bridge: No such file or directory
/sys/class/net/virbr0/bridge: No such file or directory
/sys/class/net/virbr0/bridge: No such file or directory
/sys/class/net/virbr0/bridge: No such file or directory
Did you run into this problem? How did you solve it?
January 28, 2012, 10:17 amSteven Haigh says:
Hi Joe, this is mentioned in previous comments. It is purely cosmetic and is not a problem, however if it does bug you it can be solved by installing the bridge-utils package from Fedora 13/14.
February 1, 2012, 8:06 am