tag:blogger.com,1999:blog-555576322574773333.post4810560922379371481..comments2024-03-01T11:48:39.478+02:00Comments on Sysadmin Stories: VMware DirectPath I/O - adding passthrough PCI devices to VMrazzhttp://www.blogger.com/profile/15640437268011558371noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-555576322574773333.post-6249494682414186892016-06-03T10:31:48.800+03:002016-06-03T10:31:48.800+03:00yeah same problem here on 6, had to manually edit ...yeah same problem here on 6, had to manually edit the deviceid to match what i saw when looking at the client software, not the web, then i could power the vm<br /><br />billybillynoreply@blogger.comtag:blogger.com,1999:blog-555576322574773333.post-34723442958792630832016-04-08T00:03:20.435+03:002016-04-08T00:03:20.435+03:00Big thanks to this post, it lead me down the right...Big thanks to this post, it lead me down the right path.<br /><br />This issue still occurred in ESXi 6.0.0 (Build 3620759) and after some digging I saw that the Web UI was not correctly populated the device ID field (via VM->Edit Settings->VM Options->Advanced->Edit Configuration->pciPassthrough0.deviceId). Manually correcting it to the output from lspci -v allowed the machine to boot.<br /><br />Hope this helps.Adam Rankinnoreply@blogger.comtag:blogger.com,1999:blog-555576322574773333.post-14838534561443818142015-07-09T14:46:09.615+03:002015-07-09T14:46:09.615+03:00I had the exact same issues as RSZ mentioned, with...I had the exact same issues as RSZ mentioned, with the device ID being in decimal instead of hex. This caused the machines being unable to boot. Also the uuid was messed up. I also found out this by observing the differences between a vmx-file for a PowerCLI added PCI-device and a point-and-click added PCI-device.<br /><br />Thru PowerCLI I'm configuring View VM's for GRID K1 PCI passthrough, and it works when manually defining the device id, and using esxcli to get the correct VMHost uuid.<br /><br />Thanks for putting this information online.Anonymoushttps://www.blogger.com/profile/14975544096893267117noreply@blogger.comtag:blogger.com,1999:blog-555576322574773333.post-82667176101652177872015-04-05T01:44:27.475+03:002015-04-05T01:44:27.475+03:00Take a look at my project on Hackaday.io
https://...Take a look at my project on Hackaday.io<br /><br />https://hackaday.io/project/4927-hydra-multi-os-gaming-console-controllerAnonymoushttps://www.blogger.com/profile/03417018040285207327noreply@blogger.comtag:blogger.com,1999:blog-555576322574773333.post-15001840670288009672014-10-26T17:07:10.414+02:002014-10-26T17:07:10.414+02:00Hey Rob,
ideed: this bug still seems to be aroun...Hey Rob, <br /><br />ideed: this bug still seems to be around with the latest release of ESXi 5.5 / vCenter 5.5 (as of 26.10.2014). <br /><br />Also I get different deviceIds when using the .Net Client against the ESXi Host directly or the vCenter.<br /><br />vSphere Web Client does also produce crap in my tests. Best way of doing it seems to be editing the VMX file, unregister and re-register the VM.<br /><br />There are also differences when looking up the device ID in the client and the cli. CLI seems to use hex converted to bin notation (0x######) while the client (and perhaps the API) use full hex IDs e.g. 68b8).<br /><br />Another strange thing i noticed is that if one pci device has multiple passthrough components (e.g. a VGA that also has a audio chip) it will show up as one device with 2 child devices in the passthrough menu. The id of the second device (in my case the audio component) will end up with a negative deviceID (e.g. -256612) which seems kinda odd - maybe another bug?<br /><br />Adding the component using different VM hardware compability versions (e.g. 8 vs 10) also seems to have different outcome. <br /><br />oh boy - passthrough is a mess from what i've seen so far. out of 20 times it will work maybe 3 times - but once it works on a vm it works pretty stable.nonehttps://www.blogger.com/profile/10631887071218752475noreply@blogger.comtag:blogger.com,1999:blog-555576322574773333.post-46761276081704245812013-04-25T02:38:24.036+03:002013-04-25T02:38:24.036+03:00BTW, I'm using ESXi 5.1.0 patched through Mar ...BTW, I'm using ESXi 5.1.0 patched through Mar 31 2013.<br /><br />I can see my Quadro 4000 card in lspci -v, but don't see any devices with deviceId 1757<br /><br />00:06:00.0 VGA compatible controller Display controller: nVidia Corporation GF100 [Quadro 4000]<br /> Class 0300: 10de:06dd<br /><br />Rob Migliorehttps://www.blogger.com/profile/11116063456218601231noreply@blogger.comtag:blogger.com,1999:blog-555576322574773333.post-50810173730148386462013-04-25T02:31:26.096+03:002013-04-25T02:31:26.096+03:00When using the add-passthroughdevice command as yo...When using the add-passthroughdevice command as you instruct, I get the following error when I turn the VM on:<br /><br /><i>Power On virtual machine:The systemId does not match the current system or the deviceId, and the vendorId does not match the device currently at 006:00.0</i><br /><br />It works fine if I add the device via the GUI, so I inspected the .vmx files for 3 different cases: <br /><br /><br />VM E3D6 (host .62) has added via script add<br />ectswin7-e3D6/ectswin7-e3D6.vmx:pciPassthru0.deviceId = "1757"<br />ectswin7-e3D6/ectswin7-e3D6.vmx:pciPassthru0.vendorId = "10de"<br />ectswin7-e3D6/ectswin7-e3D6.vmx:pciPassthru0.systemId = "51150b2d-9a43-e109-7c74-78e7d163ee98"<br /><br />VM E7 (host .59) has added via GUI<br />ectswin7-e7/ectswin7-e7.vmx:pciPassthru0.deviceId = "6dd"<br />ectswin7-e7/ectswin7-e7.vmx:pciPassthru0.vendorId = "10de"<br />ectswin7-e7/ectswin7-e7.vmx:pciPassthru0.systemId = "515dad5b-c1c3-d9d2-1da4-78e7d16480f0"<br /><br />VM E8 (host .62) has added via GUI<br />ectswin7-e8/ectswin7-e8.vmx:pciPassthru0.deviceId = "6dd"<br />ectswin7-e8/ectswin7-e8.vmx:pciPassthru0.vendorId = "10de"<br />ectswin7-e8/ectswin7-e8.vmx:pciPassthru0.systemId = "51150b2d-9a43-e109-7c74-78e7d163ee98"<br /><br />It seems to get the wrong deviceId when adding via the GUI. Have you seen this?Rob Migliorehttps://www.blogger.com/profile/11116063456218601231noreply@blogger.com