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.

[admin]

32-bit nested VMs should work just fine.  64-bit nested VMs aren't going to work, since Hyper-V doesn't virtualize the hardware-assisted virtualization features of the physical CPU.

[BertP]

Everyone has issues activating Windows 8.  That is a new built in feature...

[BertP]

That sucks.  It essentially rules out creating VMs with Windows servers since Windows 2008 R2 and above are only available in a 64 bit version.

[admin]

Well, hardware-assisted virtualization or SLC64 is required for 64-bit guests.

[BertP]

This exercise brings up another question:  If I want to set up ESXi on its own hardware (not Hyper-V), do I need to be concerned about which CPU I run it on?  AMD seems to have some issues here so should I restrict my hardware choices to Intel processors?

[admin]

BertP wrote:

This exercise brings up another question:  If I want to set up ESXi on its own hardware (not Hyper-V), do I need to be concerned about which CPU I run it on?  AMD seems to have some issues here so should I restrict my hardware choices to Intel processors?

You should look for hardware that's on the ESXi Hardware Compatibility List.  There are AMD processors there as well as Intel processors.  When considering physical hardware, I wouldn't be swayed by the issues you are having running ESXi under Hyper-V.

[BertP]

OK, thanks.

[bord4kop]

Sadly it does not work for me.

Running HyperV 2012, I am trying to get things working using a customized ESXi 5.1 iso.

(after customizing it with the .vib from here, I got it past the 'select disk'  and select 'Keyboard layout' install option. But when ' scanning other hardware options'  it fails:

Error is that ESXi recognizes the CPU as an i5 but complains that it is reported as 'Microsoft'.

Did I miss top set an option somewhere? Or am I using the incorrect (e.g. latest) version of ESXi?

[admin]

Can you post a screenshot of the error message?

[bord4kop]

Hi,

Here you go:

Help is much appriciated.

Although I 've read on the Microsoft site, it will never run using this config

http://social.technet.microsoft.com/Forums/en-US/virtualmachingmgrhyperv/thread/aa10f817-5a46-4c5d-b...

HyperV does not support nested HyperVisors.. As they say.

Well we know that is not the case obviously

[admin]

It's unclear which VIB it's complaining about.  I don't believe the tulip VIB is tagged with "Hewlett Packard."  What virtual devices do you have attached to this VM?

[admin]

Just checking...You did customize a standard ESXi ISO image and not one from Hewlett Packard, right?

[bord4kop]

hmm, now you got me thinking indeed.

I am pretty sure I used the standard one, newest available from VMware. The machine is a HP laptop tho..

Well, I 'll make another customized ISO just to make sure I use the proper one.

[bord4kop]

Right.. used the wrong ISO :smileyblush:

Now, after this screen:

I got this one:

Press ENTER and voila!

It continues the install.

Thanks for the help

My bad, sorry

[bord4kop]

Another day, another problem;

ESXi 5.1 is up and running.

Notice the Processor Manufacturer

But when I try to start the Windows VM it gives me an error:

Is this because the VM is a 64-bit OS?

EDIT:

- Adding the line vmx nested helped!

- Yes, only 32 Bit supported when nesting..

Thanx for all the help, much appriciated!!

Message was edited by: bord4kop

[admin]

Well, you will only be able to run 32-bit nested guests, since Hyper-V doesn't virtualize VT-x/AMD-V.  However, this message is unrelated.  You should be able to work around this message by adding the following option to the nested VM's configuration file:

vmx.allowNested = TRUE

[MaugerYohann]

Hi all

I read every posts on this thread and still have the Network Issue.

I have customize the following ESXi ISO with the tulip.vib and ESXi-Customizer :

- VMware-VMvisor-Installer-5.1.0.update01-1065491.x86_64

- VMware-VMvisor-Installer-5.0.0.update01-623860.x86_64

- VMware-VMvisor-Installer-5.1.0-799733.x86_64

Don't work, still get the error message :

I really don't understand what's happening i use external, internal, and private configuration in VM's settings.

Any help will be welcome.

[admin]

DId you assign a legacy network adapter under Hyper-V?

[MaugerYohann]

Yeah, you're right, forgot to change the Network Adapter ....

Thanks a lot !

Go ahead next issues !

[Super169]

Thanks for the information here, I have successfully installed the ESXi 5.1 within Hyper-V (Windows 8).

However, I can only connect the Hyper-V server from other machine, I cannot use my host OS (Windows 😎 to connect the ESXi VM.
The IP address is correct, it can be connect via other workstation in the network, but I cannot do it from the host OS, and I cannot ping from the host OS also.  Inside the ESXi's netowok testing, I can ping the router, but no my host OS also.

I have read some post here that it can be solved by adding the following line in the XML under <global_settings>

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

But it doesn't work for me.  And I have tried to move this line to different position, e.g. under <device>, <connection>, .... all failed.

May I know how to change the setting to let my host OS connect to the ESXi VM?  Where should I put the following setting in the XML:

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