VMware Cloud Community
remixedcat
Contributor
Contributor

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

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.

http://i.imgur.com/4rCA3.png

Hyper-V-Virtual-Switch-Issue-421.PNG

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

191 Replies
Xuti
Contributor
Contributor

Hello,

I have not been able to take any output using Debugging tools for Windows. I follow all the steps:

How to live debug a VM in Hyper-V - Ask the Core Team - Site Home - TechNet Blogs

But when I click on Break, I have no response.

Thanks


Reply
0 Kudos
admin
Immortal
Immortal

Since ESX is not Windows, those steps are not entirely relevant.

You should connect the virtual serial port of the ESX VM to a named pipe, and then you need a client to read from the named pipe.  Windows doesn't make that easy, but some googling suggests that it may be fairly straightforward to write a python script that will do it.

Reply
0 Kudos
ghodgins
Contributor
Contributor

Ahmad, did you ever get this working?  How was performance?

I have a very similar situation where we are trying to run a SCO Unix 5.0.6 ESX image in a Hyper-V environment.  We've been able to get this working within VMWare Workstation 9/10 installed directly on the Windows 2012 server where the Hyper-V role is installed as well as in a Hyper-V VM.  We have full functionality but the performance is about 1/2 to 1/3 of that of the same VM running directly on ESX 4.1.  We've tried numerous disk driver configurations in SCO as well as tuning/tweaking Workstation.  We've even tried fresh 5.0.6 and 5.0.7 SCO installs with IDE and SCSI drivers and basic file creation (dd) and cp operations of 512MB file demonstrate this showstopping performance degradation that appears to translate to the application when tested further.

I'm basically wondering whether ESX might be expected to provide any better performance in this scenario before investing too much more time in this already exhausting effort.

Any information is much appreciated.

Thanks.

Reply
0 Kudos
admin
Immortal
Immortal

Nested VMs under Hyper-V are going to exhibit very poor performance.  Since even the management OS runs in a VM under Hyper-V, you are always running Workstation VMs nested under Hyper-V whenever the Hyper-V role is installed, even if Workstation is running "directly" on the Windows 2012 host.  For increased performance of Workstation VMs on Windows 2012, disable the Hyper-V role.

Reply
0 Kudos
JA50N
Contributor
Contributor

In building a custom ISO I think I'm missing some libraries or the tulip.vib I've used is not compatible the base ISO but not sure how to determine exactly what to do.  I customized the 5.0 driver rollup ISO with this tulip.vib (posted on this thread).  Boots and installation gets quite far through but it ends up with the attached message (first part also copied below).

I have also tried the 5.5 ISO with the same tulip.vib but that locks up during boot - right after "loading kernel".

5.0 error message:

  "Could not obtain module order from esximage db"

  "The installation profile could not be validated due to the following errors:"

  "VIB community_bootbank_net-tulip_1.1.15-1OEM.510.0.0.00000 requires vmkapi_2_1_8_8, but the requirement cannot be satisfied within the ImageProfile.

The message is really detailed and looks extremely helpful but I haven't had any luck in working out next step.. 

esxi.png

Reply
0 Kudos
admin
Immortal
Immortal

I believe this VIB will only work with ESXi 5.1.

Reply
0 Kudos
TommyFreddy
Enthusiast
Enthusiast

I think so ESXi 5.1 with this VIB gone work..

Reply
0 Kudos
JSpoor
Contributor
Contributor

I am trying this,

running Hyper-V on Windows 8.1

I got as far as customizing the ISO and setting up the VM.

Using VMware-VMvisor-Installer-5.5.0-1331820.x86_64.iso

When booting the VM, the installation starts, but freezes at

Loading /imgpayld.tgz

"Relocating modules and starting up the kernel..."

Using VMware-VMvisor-Installer-5.1.0.update01-1065491.x86_64.iso or VMware-VMvisor-Installer-5.0.0.update03-1311175.x86_64.iso

When booting the VM, the installation starts and ends up in a black screen...

Dell Lattitude 6530

Intel(R) Core(TM) i7-3540M CPU @ 3.00 GHz

Installed Memory 16 GB

500 GB SSD Drive

VM Setup with two "Legacy Network Adapter"s

Tried 1 GB Memory, Tried 2 GB Memory

Tried 4 Procs, Tried 2 Procs.

Help would be appreciated

Reply
0 Kudos
JSpoor
Contributor
Contributor

I am trying that as we speak.

You do get beyond the Loading kernel freeze, but then it ends up with a black screen....

Reply
0 Kudos
RonMcDon
Contributor
Contributor

Guys, I've managed to get ESXi 5.1 installed with the tulip driver but I cannot connect or ping to it.

Oddly it is picking up a DHCP address from my DHCP server but I can neither ping the DHCP server from ESX or ping ESX from the DHCP server ???

Firewall is disabled on my DHCP server and on ESX. Anyone else experienced this? Any fixes? Im tearing my hair out.

Reply
0 Kudos
remixedcat
Contributor
Contributor

I am having the same. Internet works, however pings and such don't work. Even changed routers.

Reply
0 Kudos
RonMcDon
Contributor
Contributor

Forgot to note, I cannot connect to the web interface or use vsphere due to this.

Cannot figure out how it receives a DHCP address but they cannot ping each other??

Reply
0 Kudos
remixedcat
Contributor
Contributor

Same here about the DHCP.

I can connect thru vsphere though.

Reply
0 Kudos
dbutch1976
Hot Shot
Hot Shot

JSpoor wrote:

I am trying this,

running Hyper-V on Windows 8.1

I got as far as customizing the ISO and setting up the VM.

Using VMware-VMvisor-Installer-5.5.0-1331820.x86_64.iso

When booting the VM, the installation starts, but freezes at

Loading /imgpayld.tgz

"Relocating modules and starting up the kernel..."

Using VMware-VMvisor-Installer-5.1.0.update01-1065491.x86_64.iso or VMware-VMvisor-Installer-5.0.0.update03-1311175.x86_64.iso

When booting the VM, the installation starts and ends up in a black screen...

Dell Lattitude 6530

Intel(R) Core(TM) i7-3540M CPU @ 3.00 GHz

Installed Memory 16 GB

500 GB SSD Drive

VM Setup with two "Legacy Network Adapter"s

Tried 1 GB Memory, Tried 2 GB Memory

Tried 4 Procs, Tried 2 Procs.

Help would be appreciated

Hi JSpoor,

I am running Windows 8.1 with hyper-V.  I am attempting to run ESXi 5.5 nesting by booting from my autodeploy environment.  I got the same error you did and was able to get past it by following this link:

http://robwillis.info/2014/01/dell-cs24-esxi-5-5-install-stuck-relocating-modules-and-starting-up-th...

It appears to be a video driver issue, but modifying the boot options worked for me.

ignoreHeadless=TRUE

I'm stuck again because in order to make this work I need to install a Legacy Network Adapter in order to boot from LAN, (which oddly enough allows me to begin booting ESXi) however eventually I get the error:

"No network drivers were detected."

I'm going to attempt to package the NIC drivers into the image and see what happens.  I'll let you know my result.

Reply
0 Kudos
BPlarry
Contributor
Contributor

I have followed this discussion and was able to make Vsphere 5.1 work inside of Hyper-V (as a VM) on a Windows 2012 R2 server.

However I would now like to use the Virtual Fibre HBA so that I can present a virtual volume from an HP 3PAR array directly to the ESX server VM.

The problem I am seeing is that ESX does not "see" the Virtual Fibre HBA.

Anyone have any Ideas on how I can get  the ESX VM to work with the Hyper-V virtual HBA ?

Thanks

LB

Reply
0 Kudos
admin
Immortal
Immortal

BPlarry wrote:

Anyone have any Ideas on how I can get  the ESX VM to work with the Hyper-V virtual HBA ?

Thanks

LB

You would probably have to write a driver for it.  If there's a Linux driver to start from, the work is much easier, but it's not for the faint of heart.

Reply
0 Kudos
EvgenijSmirnovB
Contributor
Contributor

Hi,

can anyone confirm running esxi 5.5 in Windows 8.1 Hyper-V? I have got it to install using the tulip.vib and the ignoreHeadless but still having problems with network connectivity.

  • all VM are on the same private vSwitch
  • another VM on the same vSwitch provides DHCP for the network segment
  • when the ESXi VM boots up, it will get an IP config from DHCP but still remain unreachable
  • same thing happens if I provide a valid static config
  • I went to another Windows VM on the same vSwitch and did a ping -t <IP of ESXi VM> in one CMD window while booting up ESXi VM and doing arp -a  from another CMD window. For a couple of second the MAC / IP pair of the ESXi VM appeared on the list (ping still didn't get through) and then it disappeared
  • MAC spoofing is enabled on VM per Set-VMNetworkAdapter -VMName ESX01 -MacAdressSpoofing On to no avail
  • Promiscuous mode set in the XML (under <global_Settings>) to no avail

Before I break out network monitoring tools and start digging deeper it would be good to know that somebody already got it to work so any insight will be greatly appreciated.

Thanks a lot

Evgenij

Reply
0 Kudos
admin
Immortal
Immortal

The tulip VIB was intended for ESXi 5.1, and quite likely does not work with ESXi 5.5.

Reply
0 Kudos
EvgenijSmirnovB
Contributor
Contributor

OK, tried ESXi 5.1U2. Since the result I am getting is *exactly* the same, I suppose the problem lies with the host after all. Will dig deeper and see if I get it to work.

Reply
0 Kudos
dbutch1976
Hot Shot
Hot Shot

http://www.virtuallyghetto.com/2013/11/why-is-promiscuous-mode-forged.html

What are the setting on your vSwitches?  Have you tried allowing forged transmits and promiscuous mode?

Reply
0 Kudos