I have installed and configured OVS 2.2 and OVM Manager 2.2 and had all working and had everything running fine (I am having to use these versions to be compliant with the templates I wish to install)
I then shut down everything and moved the server to its new location in the rack, plugged it all in and restarted and now I can no longer browse to the OVM Manager.
I know very little about linux and oracle vm but assumed as I can no longer ping the Manager vm that it wasnt started, when I look in the /var/log/xen/qemu-dm-pid.log I see the following
Warning: vlan 0 is not connected to host network
as the first line.
The only network change that I am aware of is the host machine now has multiple network cards connected where it only had one connected on initial setup.
Any pointers on where to start are welcome...
ok I found out that I needed to so a xm create on vm.cfg to start the manager vm - this is now started and I can ssh to the console on the correct IP and can browse to the manager console.
All looks to be working now.
Create symbolic link to the "vm.cfg" in "/etc/xen/auto" e.g.
ln -s /OVS/vm-name/vm.cfg /etc/xen/auto/vm-name
[root@ovm222 ~]# cat /etc/ovs-release
Oracle VM server release 2.2.2
[root@ovm222 ~]# chkconfig --list xendomains
xendomains 0:off 1:off 2:off 3:on 4:on 5:on 6:off
[root@ovm222 ~]# grep ^XENDOMAINS_AUTO= /etc/sysconfig/xendomains
FYI XENDOMAINS_SAVE should be undefined unless you want to save on shutdown e.g.
[root@denovm22 ~]# grep ^#XENDOMAINS_SAVE /etc/sysconfig/xendomains