Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

One of our hardware vendors supplied us with a virtual appliance that they said needed to run inside VirtualBox. That's non-negotiable - as it's designed to run as an appliance, they need some way of accessing the host server for support and upgrades, and they've decided to use TeamViewer for this, which means I can't just convert their appliance. I thought I could spin up a vSphere VM running Server 2008 R2, install VirtualBox inside that VM, and then import their appliance, basically running a virtual inside a virtual. And while I was able to get the appliance running (read: powered up) on VirtualBox inside the vSphere VM, I'm having trouble with the networking.

The appliance came from the vendor configured with two network adapters: one on a NAT to the host OS, and a second bridged to the host. If it matters, it's running Debian. From inside the virtual host, I can ping the virtual guest via IP, and inside the virtual guest, I can ping the virtual host. However, the appliance is completely isolated from the rest of the network (except for DHCP); I can't ping it from outside the virtual host (ie., from the physical world), nor can the appliance ping outside of its virtual host. From the real world, the virtual host is accessible, and I even went so far as to disable the firewall entirely, with no effect. It seems like something in the routing won't let traffic through the hypervisor into the virtual host and from there into the guest appliance. There are no VLANs and everything is running on the same subnet. Is there any way to configure the networking to allow traffic all the way through from the real world into the vm running inside a vm?

share|improve this question
    
Check the NIC properties on the Windows 2008 R2 VM (you know, this window: i.stack.imgur.com/2iKfk.jpg) and tell us what type of drivers are in that list of checkboxes. My gut tells me that the VirtualBox driver might be interfering with the VMWare Tools driver. –  Kenny Rasschaert Aug 30 '12 at 19:58
    
The NIC itself is running as an Intel PRO/1000 MT. Other than that, it looks identical to the example you posted, except that I've got IPv6 turned off. Turning it on didn't seem to do anything, but I figured might as well, just to cover my bases. Shouldn't make a difference, but the appliance has a fixed IP address outside the DHCP range; the 2008 virtual host is using DHCP. –  mounty Aug 31 '12 at 13:36
    
Why does TeamViewer make it so you can't convert the VBox VM to vSphere? Granted, it may not be supported by the vendor - but I can't see why TeamViewer would force a virtualization choice. –  Goyuix Aug 31 '12 at 14:54
    
There's no good place to run TeamViewer except for someone's workstation, someone who's got the vSphere client installed. Since they can be logged in for up to an hour (occasionally longer if it's a complicated upgrade or troubleshooting session) I really can't afford to lose someone's workstation for that long. And putting up a box specifically for TeamViewer sessions kinda defeats one of the purposes for virtualizing in the first place. –  mounty Aug 31 '12 at 15:15
    
I still don't see why you can't convert the VirtualBox VM to a vSphere VM. Did you try and it failed? –  Goyuix Sep 3 '12 at 18:02

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.