I currently have 2 servers in the house... One of them is a NexentaStor storage appliance, and the other is a Windows 7 box (also running VMware Server 2.0 with a handful of VMs). I was interested in consolidating the two of them into a single server since neither box was being heavily utilized. After reading this page, I decided to base the single server off of VMware's ESXi product. The first VM would need to be the storage appliance, and then the rest of the VMs would NFS mount the storage appliance and boot from there. This setup should handle everything I need it to, and if there was a catastrophic failure, I could pull the drives and put into another ZFS system and recover the data.
VMware doesn't make it easy to create Raw Device Mappings using SATA disks. That's okay, ESXi has a feature which allows you to pass through hardware on the host machine directly to the guest. This sounds great. I planned on passing a couple of Intel SASMF8I LSI1068-based controllers to the storage VM. I have a Supermicro X8SAX motherboard, Intel i7-930 CPU, and 24GB of RAM (6x4GB DDR3).
In order to enable hardware passthrough, you have to go into the BIOS and enable Intel VT-d. Unfortunately, any time I enabled this feature ESXi refused to install. If I installed ESXi first and then enabled the feature, it refused to complete booting. I went through all sorts of BIOS settings, ACPI, Intel Virtualization technology, etc. and couldn't find a combination that worked. I upgraded the bios from 1.1a to 2.0 and that still didn't work. I tried ESXi 4.1 along with 4.1U1.
What finally worked was downgrading the BIOS all the way back to 1.0c! The only downside so far is that it only recognizes 20GB of RAM instead of 24GB. Other than that, the hardware passthrough works perfectly. 1.0c isn't available on Supermicro's website. Good luck in finding it... I grabbed it from some website in China after some extensive searching at google.
I've got an e-mail into Supermicro asking why. I'll edit this post if I get an explanation from them.
Hey dude - did you ever get VT-d working with bios 2.0 or full 24GB of RAM? I'm struggling with a similar situation here :(
I didn't. Even after vSphere 5 came out, I tried it again with some newer bios revisions and still had the same problem.
I'm still running 1.0c with 24GB of RAM, but the system only recognizes 20GB. *shrug*.
I know this is a long shot, but I'm in the same boat as what you describe. Any resolution?
I have a hardware raid controller. Does that mean I can simply disable Intel VT-d and suffer no issues?
If you're not trying to "pass-through" the hardware RAID card directly to a VM, then you should be fine. In my situation, I wanted to give a single VM full/direct access to that RAID card - and that is what drives the requirement for VT-d.
If you're going to pass all of your storage to VMware, and then dole out space to individual VMs from there, you don't need VT-d.
Good luck.
Super Micro Server might doesn't easy.