Well I got the client and installed it. Created a VM for WHS2011 (2Ghz cpu, 180GB disk and 2GB ram which is probably what my WHS install to this box was using day to day) and it took 1 hour to get to 31% of expanding files in the install process
. I cancelled and upped the cpu to 6Ghz and the ram to 8GB and it installed in 30 minutes. I have since throttled them back dow again and it seems to be running fine.
I also installed CentOS 6 minimal (200+MB download), installed wget, Java and Minecraft and the minecraft VM is running very happily although I have to sort out the iptables rules to let it through the firewall (could connect with iptables stopped but not when running).
This took me up to 1am this morning (up at 6:30 for work so not feeling so clever at the moment
).
Now comes the kicker in the sensitive bits....
The WHS2011 is acting as a NAS with around 11TB of data (5.5TB live and the same as backup) sitting on the host ready to be used by the WHS VM. I just need to just make these drives available to the VM and I can see them in ESXi. Well it seems to be able to pass through the the VM you need to support VT-d (direct IO to Virtulization).
That should be fine as my new shiny i5 2400 supports the VT command sets which is why I upgraded from the i3. Nope... it seems I also need a motherboard that supports it and my Asus P8H67-V doesn't
.
This is the third MB for this project, first was an old LGA775 board that could not support two 8 channel HBAs for connecting 16 drives. The second, an intel LGA775 server board, could support the HBAs and a PCI graphics card just not the PCI graphics card I bought as there was a little known hardware clash with that board and my graphics card chipset. This 3rd board was doing everything I wanted until now.
Thing is, I don't recall Virtual Box requiring anything in order to share my hosts drives directly to the virtual machine when used on my C2Q 9450 workstation. Is there seriously no way around this ?.
Apart from that I am pretty happy with ESXi (which doesn't use any sort of Linux kernel but a special VM kernel that looks remarkably like a custom compiled Linux kernel
). After I have sorted out the drive issue I can test network speed to make sure ESXi is not affected by the Linux kernel bug that causes my NIC IRQ to get disabled.
Thanks for all the pointers so far, has made it so much easier although finding the VI Client was really not so intuitive and not mentioned in the ESXi management guide I was reading (could have missed it or maybe it was outdated or the like).
RB

I also installed CentOS 6 minimal (200+MB download), installed wget, Java and Minecraft and the minecraft VM is running very happily although I have to sort out the iptables rules to let it through the firewall (could connect with iptables stopped but not when running).
This took me up to 1am this morning (up at 6:30 for work so not feeling so clever at the moment

Now comes the kicker in the sensitive bits....
The WHS2011 is acting as a NAS with around 11TB of data (5.5TB live and the same as backup) sitting on the host ready to be used by the WHS VM. I just need to just make these drives available to the VM and I can see them in ESXi. Well it seems to be able to pass through the the VM you need to support VT-d (direct IO to Virtulization).
That should be fine as my new shiny i5 2400 supports the VT command sets which is why I upgraded from the i3. Nope... it seems I also need a motherboard that supports it and my Asus P8H67-V doesn't

This is the third MB for this project, first was an old LGA775 board that could not support two 8 channel HBAs for connecting 16 drives. The second, an intel LGA775 server board, could support the HBAs and a PCI graphics card just not the PCI graphics card I bought as there was a little known hardware clash with that board and my graphics card chipset. This 3rd board was doing everything I wanted until now.
Thing is, I don't recall Virtual Box requiring anything in order to share my hosts drives directly to the virtual machine when used on my C2Q 9450 workstation. Is there seriously no way around this ?.
Apart from that I am pretty happy with ESXi (which doesn't use any sort of Linux kernel but a special VM kernel that looks remarkably like a custom compiled Linux kernel

Thanks for all the pointers so far, has made it so much easier although finding the VI Client was really not so intuitive and not mentioned in the ESXi management guide I was reading (could have missed it or maybe it was outdated or the like).
RB