Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

PCI pass through device is lost on hardware version upgrade (70668)

Last Updated: 2/27/2024Categories: InformationalTotal Views: 9808Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

When upgrading hardware version of a Virtual Machine(VM) to 13 and above the PCI passthrough devices disappear from the VM.

hostd.log
2019-05-16T22:34:08.938Z info hostd[123456] [Originator@6876 sub=Vimsvc.TaskManager opID=ABCD-528-auto-ep-h5:1234-10-f3-ce6c user=vpxuser:SSO.Domain\Administrator] Task Created : haTask-4-vim.VirtualMachine.upgradeVirtualHardware-1234567
2019-05-16T22:34:08.938Z info hostd[12345667] [Originator@6876 sub=Vimsvc.ha-eventmgr opID=ABCD-528-auto-ep-h5:1234-10-f3-ce6c user=vpxuser:SSO.Domain\Administrator] Event 112 : Upgrading virtual machine compatibility of PCI_PASS in ha-datacenter to vmx-00
2019-05-16T22:34:08.938Z info hostd[12345667] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/DATASTORE/VMNAME/VMNAME.vmx opID=ABCD-528-auto-ep-h5:1234-10-f3-ce6c user=vpxuser:SSO.Domain\Administrator] State Transition (VM_STATE_OFF -> VM_STATE_UPGRADING)
2019-05-16T22:34:08.940Z info hostd[12345667] [Originator@6876 sub=Libs opID=ABCD-528-auto-ep-h5:1234-10-f3-ce6c user=vpxuser:SSO.Domain\Administrator] UpgradeVM_AddRemoveDevice: Option:[pciPassthru0.present] removed:ADAPTER
2019-05-16T22:34:08.940Z info hostd[12345667] [Originator@6876 sub=Libs opID=ABCD-528-auto-ep-h5:1234-10-f3-ce6c user=vpxuser:SSO.Domain\Administrator] UpgradeVM_AddRemoveDevice: Option:[pciPassthru1.present] removed:ADAPTER
2019-05-16T22:34:08.940Z info hostd[12345667] [Originator@6876 sub=Libs opID=ABCD-528-auto-ep-h5:1234-10-f3-ce6c user=vpxuser:SSO.Domain\Administrator] UpgradeVM_AddRemoveDevice: Device:[SMBIOS compatibility] added
2019-05-16T22:34:08.940Z info hostd[12345667] [Originator@6876 sub=Libs opID=ABCD-528-auto-ep-h5:1234-10-f3-ce6c user=vpxuser:SSO.Domain\Administrator] UpgradeVM_AddRemoveDevice: Device:[VMware Pointing Device compatibility] added
2019-05-16T22:34:08.940Z info hostd[12345667] [Originator@6876 sub=Libs opID=ABCD-528-auto-ep-h5:1234-10-f3-ce6c user=vpxuser:SSO.Domain\Administrator] UpgradeVM_AddRemoveDevice: Device:[Vmxnet3 compatibility] added
2019-05-16T22:34:08.950Z info hostd[12345667] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/DATASTORE/VMNAME/VMNAME.vmx opID=ABCD-528-auto-ep-h5:1234-10-f3-ce6c user=vpxuser:SSO.Domain\Administrator] SetVmxVersion: switching environment browser to vmx version 'vmx-14'
2019-05-16T22:34:08.950Z info hostd[12345667] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/DATASTORE/VMNAME/VMNAME.vmx opID=ABCD-528-auto-ep-h5:1234-10-f3-ce6c user=vpxuser:SSO.Domain\Administrator] Send config update invoked
2019-05-16T22:34:08.956Z info hostd[12345667] [Originator@6876 sub=Vimsvc.ha-eventmgr opID=ABCD-528-auto-ep-h5:1234-10-f3-ce6c user=vpxuser:SSO.Domain\Administrator] Event 113 : Virtual machine compatibility upgraded to ESXi 6.7 and later (VM version 14)

Note: Tenant name and date are specific to the environment.

Cause

Passed through device of a VM before upgrading the H/W version.
Hardware version:
[root@is-tse-d128:/vmfs/volumes/5cd351f4-f5e70727-c637-549f3515c866/PCI_PASS] cat PCI_PASS.vmx | grep version
config.version = "8"
virtualHW.version = "10"

[root@is-tse-d128:/vmfs/volumes/5cd351f4-f5e70727-c637-549f3515c866/PCI_PASS] cat PCI_PASS.vmx | grep pciPassthru
migrate.hostLog = "PCI_PASS-124cad75.hlog"
pciPassthru0.id = "00000:002:00.0"
pciPassthru0.deviceId = "0x165f"
pciPassthru0.vendorId = "0x14e4"
pciPassthru0.systemId = "5cd3519c-a12d-052d-3eb7-549f3515c866"
pciPassthru0.present = "TRUE" <---------------------------------------------------------
pciPassthru1.id = "00000:002:00.0"
pciPassthru1.deviceId = "0x165f"
pciPassthru1.vendorId = "0x14e4"
pciPassthru1.systemId = "5cd3519c-a12d-052d-3eb7-549f3515c866"
pciPassthru1.present = "TRUE" <---------------------------------------------------------

After upgrading hardware version for the VM to 13
[root@is-tse-d128:/vmfs/volumes/5cd351f4-f5e70727-c637-549f3515c866/PCI_PASS] cat PCI_PASS.vmx | grep version
config.version = "8"
virtualHW.version = "13"

Passed through device:
[root@is-tse-d128:/vmfs/volumes/5cd351f4-f5e70727-c637-549f3515c866/PCI_PASS] cat PCI_PASS.vmx | grep pciPassthru
migrate.hostLog = "PCI_PASS-124cad75.hlog"
pciPassthru0.id = "00000:002:00.0"
pciPassthru0.deviceId = "0x165f"
pciPassthru0.vendorId = "0x14e4"
pciPassthru0.systemId = "5cd3519c-a12d-052d-3eb7-549f3515c866"
pciPassthru0.present = "FALSE" <----------------------------------------------------------  Change to false
pciPassthru1.id = "00000:002:00.0"
pciPassthru1.deviceId = "0x165f"
pciPassthru1.vendorId = "0x14e4"
pciPassthru1.systemId = "5cd3519c-a12d-052d-3eb7-549f3515c866"
pciPassthru1.present = "FALSE" <-----------------------------------------------------------  Change to false

Resolution

This is a known issue with Esxi 6.5 build 4887370 and Esxi 6.7.

This issue is resolved in ESXi 6.5 Patch 4, available at Download Patches . For more information, see the VMware ESXi 6.5, Patch Release ESXi650-201912002

This issue is resolved in ESXi 6.7 Update 3, available at Customer Connect. For more information, see the

VMware ESXi 6.7 Update 3 Release Notes

Workaround

Workaround# 1
Edit the VMX file for the effected VM, change the value for "pciPassthru1.present " from False to True and reload the VM.

Workaround# 2
Before upgrading the Hardware version for the VM, update the vmx with  "pciPassthru0.virtualDev = pciExpress"

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
コンプライアンス スコアが、vRealize Operations Manager 7.5 の分析ノードによって異なる (70665)

KB
•
如何调整 vRealize Automation postgres 数据库 ebs_event 表的清除时间间隔 (70759)

KB
•
Enterprise PKS 与 vRealize Log Insight 集成后，发现 CPU 利用率很高 (70647)

KB
•
vCenter Server Appliance 6.5 的 VMDK 列表 - 大小、挂载点和用途 (70624)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

Related Versions:

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.5

Take Our Survey

Support Assistant