Switching from Oracle VM Server 2.2 to 3 is a big step. One of the reasons is because there is no upgrade path, only a complete fresh installation process. However, it can be worth while, for example the OVA support is pretty neat. Hardware support is also said to be better, something that really speaks to my mind after some issues on my VM 2.2 install.
So if you’re upgrading to VM Server 3 from a version 2 installation, there might be a few things to keep in mind (especially if you have a single node instance like me). One thing is that the installer doesn’t create a ocfs2 partition by default. If you’re happily “next-ing” through the installer you’ll miss something when the machine boots During the installation, review the partition layout, and don’t forget to add the ocfs2 partition (like me).
Secondly, although the hardware support is better, I noticed that the network is not completely set up out of the box. When I was done migrating some of my “2.2 VMs” on the new 3.0.3 installation, I couldn’t get them to start:
Error: Device 0 (vif) could not be connected. Could not find bridge device xenbr0
It seems that (at least in my case) the Xen bridge wasn’t started. Checking with
$ brctl show bridge name bridge id STP enabled interfaces
indeed shows no network bridge. This is a bit worrying because it should start automatically when the Xen deamon (xend) is started. Before we start manually adding network interfaces, bridges and adding routes: there is a script for that.
Run it as root on dom0:
cd /etc/xen/scripts ./network-bridge start
will add the bridge and pbond0 interface!
$ brctl show bridge name bridge id STP enabled interfaces bond0 8000.f46d0400dff8 no pbond0
I hacked the following at the end of /etc/rc.local to make it start at boot:
cd /etc/xen/scripts ./network-bridge start ./network-bridge status
It works after a reboot, but my Spider-Sense is telling me that there must be some nicer solution. If you happen to be a Xen expert, please leave a comment below
Note that the bridge name has changed since v2.2. If you’re familiar with VM Server 2.2: edit the vm.cfg to represent the correct bridge name after migration of your VMs.The Xen bridge in Oracle VM Server 3.0.3,