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.
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.
Ouch that's a lot of work -_-
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?
Try setting up a virtual serial port to see if there is any enlightening output.
I have not been able to take any output using Debugging tools for Windows. I follow all the steps:
But when I click on Break, I have no response.
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.
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.
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.
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..
I believe this VIB will only work with ESXi 5.1.
I think so ESXi 5.1 with this VIB gone work..
I am trying this,
running Hyper-V on Windows 8.1
I got as far as customizing the ISO and setting up the VM.
When booting the VM, the installation starts, but freezes at
"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
I am trying that as we speak.
You do get beyond the Loading kernel freeze, but then it ends up with a black screen....
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.