I'm currently searching for a haswell-based i7 ESXi Setup like yours. I've found out that the Lynx-Point SATA-Controller is not able to be passed through in ESXi5.1.
My hope was for ESXi 5.5 that it will make it possible for the Lynx Point Controller. While makeing some research about that topic I've read that missing support for passthrough might be a BIOS problem and maybe the manufacturer can help with some BIOS Updates which will make passthrough possible.
On the other hand... because I'm preparing for a new setup: Is there any haswell based motherboard that uses a different onboard SATA controller which has support for passthrough in ESXi?
I am curious how the bios could be the cause of this problem, all other directpath / vt-d devices work fine from bios in esxi, so seems strange that this would be a bios problem.
Do any vmware experts understand exactly how directpath works and why sata controller may not be appearing ?
My theory is maybe the esxi/debian sata driver requires special code modification to add directpath support for esxi ?
Would be easy if someone from vmware can comment.
I am also having the same issue and would like a driver fix so I can do SATA passthrough on the Lynx Point AHCI controller
Would also like to see a solution for passthrough on the Lynx Point AHCI controller.
if anybody can help here, than here in this forum. I'd also like to use my onboard Lynx SATA of my DH87RL board for passthrough!
Hey VMware, can you please add support for this Lynx Point controller.
The pain trying to workaround the problem by using raw device mappings > 2tb now continues.
I would love a solution to this. My ESXi Whitebox AIO project is dead unless I can pass the lynx point controller or purchase an additional SAS card.
Please VMware, I'm begging you! Please add support for Lynx Point SATA AHCI controller! Need this for passthrough.
Hi VMware, can you please address this hardware since it is now very common in most Z87 series intel chipset.
I have hit a dead end in my server design since also there is a problem with > 2tb raw device mapping.
Any updates about this?
I made some custom changes to my /etc/vmware/esx.conf , but my system didn't startup properly afterwards. Displaying the usual "Press F2...", dark screen flashing, "Press F2...", dark screen flashing, ... It is also unreachable from network: Neither by vSphere nor by ping.
Intel DQ87PG Haswell Motherboard
Intel Core i5 4570
Old PCI SATA controller used for "root-device".
From: /device/000:000:31.2/vmkname = "vmhba0"
/device/000:000:31.2/owner = "passthru"
/device/000:000:31.2/device = "8c02"
/device/000:000:31.2/vendor = "8086"
I also tried to remove the AHCI driver:
~ # esxcli software vib remove -n sata-ahci
Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
Reboot Required: true
VIBs Removed: VMware_bootbank_sata-ahci_3.0-18vmw.5184.108.40.2063387
Tinkered with some other system files... No changes... It's not listed..
After the system crashed, I simply disabled the AHCI controller at the Intel VBIOS/EFI. This gave me the opportunity to boot the system properly, my changes were removed, as the controller is not available anymore.
It can be enabled afterwards to use it again.
I need to passthrough the controller, as using ZFS with raw-disk-mapping is not recommended. My drives are also greater than 2TB.
The controller works properly using Linux-KVM: Making use of modern vfio, I was able to passthrough the controller to a FreeBSD 10 machine, which booted directly off a drive on this controller, thanks to SeaBios. That is, it is technically possible!
I'll use Linux then. VMware really proofed its customer friendliness at this stage, by not fixing this issue.
EDIT: Using the latest version of ESXI: 5.5.0 #1 SMP Release build-1623387
just a short (first) post to tell I'd love that to be fixed haswell .
Mr VMWare, if you're listening... I'm really desperate I put 250€ in a core i5 of latest generation and a motherboard that can't passthrough its sata controller (and USB, but that will be solved with a Dlink DUB-1310 USB3 controller - tested, it works).
Have a nice day folks,
Ivan, from France.
I opened Support Request# 14496891806. I explained that there was no solution to a problem with hardware that is on the HCL. Also, that this thread has been open for almost a year.
I was unable to receive any assistance without an "active contract" for technical support. I refuse to use my employers contract to resolve a personal issue.
I was simply told to browse through tech papers, knowledge base, and pubs; also to repost to this forum.
Seems the solution is either to buy new hardware or not use vSphere.