Try latest 17.Q3
You might need an update on your system, system BIOS, VCenter and so on. The 17.Q3 works just fine at our end as the 17.Q2.1
The Win7 is up to date.
The Bios of the R730 is up to date > 2.4.3
The vCenter > 184.108.40.20600
It's the same result after the update of the radeon driver with Vmware Blast and PCoIP.
Here is some environment info:
HP Proliant DL 380 G9
VM's OS Windows 10 Entreprise LTSB (1607)
VMware Horizon Agent 7.2 (220.127.116.1148532)
VMware Horizon Agent Direct-Connection Plugin 7.2 (18.104.22.16835293)
VMware Tools 10.1.5.5055683
VCenter 6.0 U3
ESXi Server 6.0.0 5572656
Installed on the ESXi server VIB 1.01 (certified)
The vib has been installed as in the procedure http://www2.ati.com/relnotes/setup-guide-mxgpu-setup-for-vmware.pdf
Install mode Auto with 7 Gpu / per card. In my case 14 Gpu = 1088 Mo
The AMD Driver who work for me is Radeon Pro Software 17.5.2
Release note full
Tips: Windows 10 RS1 = 1607 Anniversary Update
Release Note Short
Parameters in VM Settings
- Connect to VM in RDP
- Decompress radeon-pro-software-17.5.2-may24.exe
- Choose custom for the install
- Shut Down VM ( Not restart because the first connection the VM stuck and make BSOD as below)
First connection from Vmware Horizon Client: Black Screen / (Config PCoIP + Full screen)
Go to « VMware Vsphere Client or Web » and « Shut Down Guest » on the VM
Second Time from Vmware Horizon Client and all work / (Config PCoIP + Full screen)
Check if AMD is Blue ( All is OK)
Check Settings GPU-Z 2.2.0
Launch a test with Unigine_Heaven-4.0 (It's run without problem)
My colleague tested with Autodesk 3D MAP 2017 SP3 and it's OK for him.
A good new from fsadough today 4 août 2017 15:22
We will be offering a workaround for Linked Clones in 17.30 driver version.
I'm waiting for these new drivers
We got exactly the same problem with almost the same hardware config. We tried all ESXi VIB drivers and AMD mxGPU drivers. We finally got it working under Windows 10 and 17.5.2 driver. With Windows 7 we face a major issue: the VM are always consuming 30-35% of the CPU. This doesn't happen with Windows 10. We too are waiting for a workaround for VmWare View Linked Clones. Did you get finally get working?
For Linked Clone workaround PM me directly