Virtualization of OMV3 in Virtual Box == HOWTO

Question

Hi,
I published a solution on my company's blog in order to test OVM3 with virtual box, for example if you don't have servers :
*[http://blog.easyteam.fr/2012/01/03/oracle-vm-3-0-reussir-la-virtualisation-doracle-vm-dans-virtualbox/]*
These are the big steps  :_
1) I get an .xml file information on a physical CM server with the command : ovs-agent-rpc discover_hardware > info.xml OR python /opt/ovs-agent-3.0/do_rpc discover_hardware > info.xml
You will find a working info.xml file at the bottom of my blog's.
2) Install the OVM manager in a virtual server in Virtual Box
3) Install the VM servers in a virtual server in Virtual Box
4) On the virtual servers, modify the following lines in the file /opt/ovs-agent-3.0/OVSDiscoverHardware.py (at the bottom of the file) :
result = response.replace(whole_marker, scsi_response)
lock.release()
f = open('/opt/ovs-agent-3.0/info.xml','r')
result = f.read()
f.close()
return result
5) On the virtual servers, copy the file info.xml we generated in the /opt/ovs-agent-3.0 directory
6) On the virtual servers, execute the following commands :
service ovs-agent stop
rm OVSDiscoverHardware.pyc
rm OVSDiscoverHardware.pyo
service ovs-agent start
7) now you can discover the VM servers from the VM Manager.
this intent article is pedagogic only. It is obvious we must not use this proceed for production or for performance tests._
Edited by: EasyVM on Jan 12, 2012 5:53 AM
Edited by: EasyVM on Jan 12, 2012 5:54 AM
Edited by: EasyVM on Jan 12, 2012 6:06 AM

Answer 1

EasyVM wrote:
I published a solution on my company's blog in order to test OVM3 with virtual box, for example if you don't have servers :Note that Oracle VM 3.1 will run in VirtualBox unmodified. This is only required for Oracle VM 3.0 -- also, your process will only work for a single Oracle VM Server. If you wanted to create a pool of servers, there are additional steps that you would need to do in order for the discovery process to see them as unique entities.
Also, the XML file is probably quite invalid for a VirtualBox guest, and may lead to additional issues/problems as you're referencing hardware that might not exist inside the VirtualBox guest, or PCI devices that could be in a different place.