I have placed my configuration here on this website http://mbaldwin.clarify-it.com/d/vanjx6
I am running the VirtualBox Images of OVMManager and OVMServer (3.2.1) and I am not able to ping the network Gateway (192.168.1.1) from the virtual machine I created. I am able to ssh into that machine from the vmserver and test.
Any comments are really appreciated.
Thank you... Use Cases I am trying to achieve:
1) External clients outside of dom0 should be able to talk to the domU managed virtual machines. (The VBoxes are bridged now)
2) domU virtual machines should be able to talk to the internet
The "real" issue is that my domU guests need to go through the dom0 interface via the bridge defined in OVM Manager networking.
With all of the workflow changes in the product it is very difficult to see what needs to be done to accomplish the task as compared to OVM 2.* which was all driven by running scripts. These
changes plus the noise surrounding the related xen discussions on the internet makes it very difficult to get the issue sorted out. I have updated the link above with some additional screen shots.
I have looked at changing to NAT on dom0 and then port forwarding via iptables to the internet ..is this the correct method? I am just not really clear.
This is a very similar case: https://forums.oracle.com/thread/2360694 I can now get to the virtual machine...however I am still not able to access the LAN FROM the virtual machine.
If you are installing Oracle VM Server on Oracle VM VirtualBox and you want to create a VM (domainU) with Oracle VM Server and to connect with this VM to the world, this is not permitted and your VM (domainU) can't access to network, this is because using Oracle VM Server (hypervisor) on Oracle VM VirtualBox and not problem with the NAT, IP Address or default gateway.