For pretty much everything that needs doing i’d recommend using this link: here
One of the primary reasons for the creation of the xen box would be the inclusion of solaris domU’s, these generally would be for testing and general usage etc..
Google Open solaris and again you’re faced with a plethora of scraps and tid-bits of information with regards to creating and more importantly troubleshooting a solaris domU. This was originally the most upto date and comprehensive guide with troubleshooting that I found –> here. However this would start to load and then present me with a kernel panic in the domU, this was a quick fix though as it was down to the kernel and ramdisk being 32bit.
‘A quick change in the extraction of the kernel and ramdisk, just make sure that you pop into the 64bit directory where the 32bit kernel is and grab that one if you’re on a 64bit box. ‘
On grabbing those you’ll find that starting your domU presents you with this:
Started domain solaris-a
SunOS Release 5.11 Version xen-nv66-2007-06-24 64-bit
Copyright 1983-2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
WARNING: Found xen v3.1.0 but need xen v3.0.4-1-sun
WARNING: The kernel may not function correctly
Ignore the version problem, doesn’t appear to cause any sort of issue. Once the domU is using the correct kernel etc. it will work as any normal native install does.
Not that we needed justification, however football, rugby, tennis and motorsport..
It’s a joke, these people earn more money in a week than an average family earns in nearly three years. I’d expect them to at least look like they were trying for the 90 minutes they have some work to do …
Searching the internet for solutions for the strangeness created by xen’s networking solution really comes up with snippets from email chains or highly over complicated network diagrams, why? i’m not entirely sure. The default method for networking with Xen consists of a collection of ‘pokey’ scripts that seem to get (at least on my system) 90% of the way there. I assume this again may be a ‘Gentoo’ issue however here are the steps (From a simplistic view) that are taken to create Xen networking:
- Original system consisted of eth0 and lo, eth0 has an ip of 10.0.0.1 etc.
- Once the system comes up and xen starts its scripts using brctl create a network bridge, this is then used to bridge the physical interface (currently still eth0 and virtual interfaces, called vifs)
- xend, the xen daemon uses brctl to create a bridge called xenbr0 then things get a bit random.
- eth0 is renamed peth0 (peth = phystical ethernet)
- The ip information is taken from peth0 and peth0 is then added to xenbr0
- Once the peth0 is added to xenbr0 the ip information is taken from peth0 and applied to xenbr0
- Any xen domU that is created afterwards creates a vif which it uses, this vif is then added to the xenbr0 allowing it to communicate on the network
This is a very sparse/dumbed down version of events, however it gives an idea of whats happening. The problem that occured with Gentoo is that step 5. never happens.
What this results in is that Gentoo comes up, brings eth0 up and we have network activity for a few seconds until xen starts to get it’s claws into the network configuration. However the most simple method for repairing this involves a small configuration change in /etc/conf.d/local.start
# 00/00/00 -- IP Allocation to Xenbr0
ifconfig xenbr0 10.0.0.1 netmask 255.255.255.0
route add default gw 10.0.0.254
This is an example taken from mine, you’ll need to alter the gateway and ip address information, but put simply this will execute after every other service has been started, resulting on your domO being visible and network aware etc…
Recently I managed to finally build and configure the Xen Hypervisor and put together a bunch of virtual machines all together. I forked out for a new box (quad core, 4Gb Ram) two months ago and getting to point that we’re at now has been a lot of tweaking, googling, patching and the odd bit of botching.
My original plan was a straight forward Vmware esx install, however it turns out that Vmware are obviously working tightly with harware vendors so it wouldnt use any old disk controller i.e. the one i have on my motherboard.
Then after a bit of deliberation it was decided that Xen would be best method to use to host virtual machines. Gentoo was selected as i decided that the ability to hand-tailor my kernel compile etc. would allow me that extra speed advantage, a bit over the top in hindsight. The build process is all well documented on the gentoo wiki -> here
Once completed the initial Gentoo install using the emerge tool took care of most of the xen install etc.. following the HOW-TO gentoo-xen guide in the wiki pretty much covers all -> here
Once the reboot was complete the box came up and then the shortfalls in the how-to became apparent:
- the network-bridge script never worked correctly
- finding alternate documentation is pretty hard work
- networking once up needs tweaking for some domU’s (TCP checksums)
- there is barely any documentation on enabling console anywhere
More to follow …