Aerohive VMWare to Hyper-V conversion

  • 1
  • Question
  • Updated 12 months ago
  • Answered
Hi everyone,

I have a problem with converting HM to Hyper-V format.

I’ve used your image files and instructions to make a conversion to Hyper-V format.
The conversion worked and I was able to start the VM in Hyper-V but when I do that I always get an error report that eth0 FAILED to initialize and when the HM starts I don’t have any network connection. The IP Address, Netmask, Default Gateway and DNS are all set correctly, but I can’t ping the HM from the host machine or anywhere from network, and I can’t ping out from the HM.
I tried different network settings in Windows Server 2012 and in Hyper-V with Virtual Switch settings but I didn’t managed to make it work.
Then I downloaded the VM Ware Workstation and made the conversion from 64bit version Virtual Disk, and it worked exactly the same way as the other one. No network connection.
What can be the cause of the problem?
I am using HP Proliant DL360 G5 Server with 6GB RAM and Windows 2012 with Hyper-V on it.
Can you please help me solving this issue?

Thanks and Best Regards,

Photo of Slobodan Simovic

Slobodan Simovic

  • 11 Posts
  • 0 Reply Likes

Posted 4 years ago

  • 1
Photo of Gary Smith

Gary Smith, Official Rep

  • 298 Posts
  • 61 Reply Likes
Hi Slobodan,

I am going from memory here but - you need to configure the eth0 in "legacy"mode. I will try to dig out the details but if you can try it and let us know if that helps that would be great.

Kind Regards,
Gary Smith
Photo of Slobodan Simovic

Slobodan Simovic

  • 11 Posts
  • 0 Reply Likes
Thanks for your Help Gary it worked perfectly.
Photo of Stefan van der Wal

Stefan van der Wal, Champ

  • 70 Posts
  • 24 Reply Likes
Time to awake an old topic, I have to install Hivemanager on a Hyper-V machine and I have absolutely no idea how to get this done. As I've only done VMware installations. Does anybody have any instructions on converting the .ova to something Hyper-V compatible?

Many thanks,

Photo of Jonathan Hurtt

Jonathan Hurtt

  • 98 Posts
  • 48 Reply Likes
Officially Hivemanager is not supported on Hyper-V, while it has worked in the past I do believe that changes in Hyper-V have caused instability. I would recommend using only the supported HyperVisor (VMware).
Photo of Stefan van der Wal

Stefan van der Wal, Champ

  • 70 Posts
  • 24 Reply Likes
Yeah, I would. But the customer is insistent and knows the risks. I managed to convert the disk, make the ethernet port legacy and can thereby support the 30 AP's this customer has.

Furthermore I completely agree with you and I'll need to have a chat with the person that told the customer this was an option. Thank you for the info.

Best regards,

Photo of Luke Harris

Luke Harris

  • 265 Posts
  • 18 Reply Likes
Sorry to resurrect an old thread. But are there any caveats I should know of regarding running Hivemanager (On-Prem) on Hyper-V or would it be more prudent to opt for the HMOL version? 
Photo of Mark Ford

Mark Ford

  • 3 Posts
  • 1 Reply Like
We've been running HM On-Prem for some over 3 years on a Win Server 2012. The only thing we encounter is CMOS Clock slippage (common for Linux on Hyper-v). We have to reboot the server, probably once a week. All other functions work fine. If we could get root level access and change to an external NTP sync service all would be good. The admin level CLI does not allow this to be set.
Photo of Christian


  • 1 Post
  • 0 Reply Likes
Do you use DHCP for the server? We have the problem that we can not use static IP with Hyper-V.