Vmware ESXI within Hyper-v (server 2012) networking issue

[remixedcat]

I am trying to get esxi running within hyper-v and it won't recognize the virtual switch even though I got it setup properly and it works with any other VMs on this system.

I only have one NIC but it works fine with other VMs.

[MaugerYohann]

I have the same problem, but not for all VMs.

Some works fine with other guests, host, and other computers, but some VMs don't works.

Try to put the line just after <global_settings> but no modification.

My xml configuration file (C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines\882CABDA-C584-4493-9B80-307BDAC84851) looks exactly like this:

[...]

<global_settings>

   <allow_promiscuous_mode type="boolean">TRUE</allow_promiscuous_mode>

   <device>

[...]

Modify the xml for all VMs don't work more.

[marsto]

I have successfully installed customized ESXi 5.1 with tulip driver within Hyper-V (Windows 8), but I have the same problem as you.

I can only connect the ESXi VM within Hyper-V from other machine. For some reason I cannot access ESXi VM from my Windows 8 "locally". Other linux based hosts VM within Hyper-V communicate with my Windows 8 "localy" with no problem. They use "tulip" module too, so why ESXi VM is accessible only from different machine on my network? 

ESXi VM get IP configuration from DHCP server properly. I can successfully ping from ESXi VM to outside eg. to some internet host. Only my Windows 8 station where I use Hyper-V I can't reach from ESXi VM. What is wrong with local networking in this case?

 

[luciobarreto]

Same here. I even tried downloading several different versions of Esxi. 5.0.0, 5.0.0 U1, U2, (those failed to install due to some error in the tulip.vip module) and 5.1.0 and 5.1.0 U1 (both 5.1.0 will install but don't see the VM hosts... they all see external devices).

It seems the promiscuous mode is really not working after adding the line to the xml. I wonder if Microsoft has done some changes within HyperV 2012.

Does anyone have any idea? I have some Windows 2000 that can't be decommissioned yet... since Hyper V 2012 no longer supports W2k, I thought that I could use VM... but I have HyperV with some vms installed in the same box, so I wanted to have them both...

Any help would be very much appreciated.

Lucio

[remixedcat]

Could you please show us screenshots of how your networking is setup. Thanks.

[luciobarreto]

In my Windows 2012 server? I did not installed any vm yet on the ESXi host since I can't connect to it with Vsphere...

Esxi will get an ip from the router... will ping the router, etc.

Only that it won't see the box that is hosting it...

[remixedcat]

Are the settings in your router configured correctly (Port forwarding, NAT, ETC)

[luciobarreto]

oh yeah.

The problem is internal... the same you mentioned that was solved adding the line:

<allow_promiscuous_mode type="boolean">TRUE</allow_promiscuous_mode>

to your virtual machine xml.

Curious that 2 other people had the same problem lately (posts above mine)... I wonder if something has changed and that line no longer works... that sucks

[remixedcat]

Did you run any updates????

[luciobarreto]

Still not clear why it has worked for people before and now it doesn't work for me..

All the last posts are related to the same problem, where esxi is not able to contact the hyperv host or the vms running within it. Although it gets ip from the dhcp and can ping router and other machines in the local network.

This sucks... went to far to give up 😕

Please help.

Lucio

[remixedcat]

When I go into the actual VM's config menus and I select "Test management network" it can ping IP addresses, however it cannot resolve hostnames.

I can use the internet in the windows 8 VM that's within esxi, however Windows won't activate or certain system services that require connectivity do not think there is an active connection.

This is as far as I can get.

[KSpeed]

Hi,

Hope someone (remixedcat ) can help.

I know earlier in the thread that jmattson mentions that nested VMs in ESXI can only be 32bit but has anyone been able to get a 64bit VM working. Reason I ask is that the link below is asking remixedcat the same question and the reply is a PM.

Thanks

http://www.neowin.net/forum/topic/1126196-for-those-wanting-to-run-esxi-within-hyper-v/?view=findpos...

[remixedcat]

HI, Sorry for the confusion. It was a 32 bit VM that was mentioned in the neowin PM.

[kirav]

worked but not network for me...
Once the network from virtual machines in HYPER-V in is not working properly.

Vmware ESXi pinged. But the virtual machines running on ESXi not.

tell me how to fix

tried <allow_promiscuous_mode type="boolean">TRUE</allow_promiscuous_mode>  - no effect

[ScottK1]

I'm really hoping someone can help me out here. Seems like I'm close, but have questions as to why it's not working.

My scenario:

• Hyper-V on 2012 server hosts several Windows VMs, most using static IP addresses.
  • One of the guest VMs was recently transferred in using VHD2Disk. This guest is a Windows 2008 R2 system with VMWare Workstation 9. This has a bridged connection (with a static IP) to the host and can see other hosts and the Internet fine.
    • The VMWare Workstation 9 installation has a legacy FreeBSD 6.2 install with a static IP address on a bridged connection to the Microsoft Hyper-V adapter. This nested VM/OS starts and operates fine other than it can only see it's host (the Windows 2008 R2 guest), and itself. It cannot ping the Internet, nor the default gateway, nor any other hosts on the network. The defaultrouter is set up in the /etc/rc.conf file to the correct default gateway.
  • The Windows 2008 R2 that is now a guest to Server 2012 Hyper-V was originally a physical box. The box and FreeBSD OS in VMWare Workstation 9 were both able to communicate with other hosts, each other, and the Internet.

So it seems either there is a disconnect with either the Microsoft Hyper-V adapter, or the VMWare adapter. Some things I have tried already:

• Disabling every single firewall between the Server 2012 host and the FreeBSD nested Guest.
• Setting Promiscuous Mode = TRUE  in the Server 2012 .xml for the Windows Server 2008 R2 Guest, but this did not seem to help, nor does there appear to be any indication that it's actually working or not other than it's contained within the .xml file.
• Switching to and configuring the Microsoft Legacy Network Adapter

I've also looked into using NAT instead through the VMWare network components but ultimately would like the FreeBSD OS to continue to have the same IP address that it had when it was a guest of the physical 2008 R2 box.

Any thoughts on next steps, things to try, or things I might have overlooked?

Thanks!

[remixedcat]

Did you try forcing the config with Static DHCP??? You may want to use it to bind the IP to the VMs MAC address. Please see your router's documentation on how to do this.

[ScottK1]

Thanks for the reply. I just tried that, but the FreeBSD host never gets an IP address from the DHCP server that way and ends up timing out.

[ScottK1]

I was able to resolve this, although in a round-about way:

It may have been in this thread, or somewhere else, I read about trying to put the Hyper-V machine and/or nic in promiscuous mode, but there really isn't a way to do that that works consistently for everyone. As such, it did not work for me.

What I did was downloaded VirtualBox and converted my VMWare based FreeBSD VM to the VirtualBox format and fired it up. I still had the same problem with being able to ping the guest host, and the guest host being able to ping the FreeBSD guest, but the FreeBSD guest could not ping the real (Hyper-V) host, default gateway, or anything else on the network.

Finally I exported the VM from the VirtualBox installation on the guest that also has the VMWare Workstation installation, and imported it into a VirtualBox installation on the Hyper-V host itself. This gets past the VMWare and Hyper-V situation of not playing nice together (or at all) on the same host, and the FreeBSD guest can now see everything on the network, and the network can see it.

[remixedcat]

Ouch that's a lot of work -_-

[Xuti]

I have tried to install ESXi 5.1 update01 customized with tulip.vib, but I get a black screen. I can see the load process (yellow bar) but just before to get the yellow screen, I only see black. I have tried to install it under Windows 8 Hyperv, Windows 2012 Hyperv, both with 2GB RAM and legacy network adapter.

In both servers I have several VM running fine. Any suggestions?

Thanks!

[admin]

Try setting up a virtual serial port to see if there is any enlightening output.