VxRail: vMotion Device 'HD audio ' has a backing type that is not supported.
Summary: Unable to migrate one or more Virtual machines (VMs) to a host. This is a general limitation of the virtual machine's compatibility with the ESXi version of the selected host.
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Symptoms
Unable to migrate one or more VMs from a host with an error:
Virtual machine is configured to use a device that prevents the operation: Device 'HD audio ' has a backing type that is not supported. This is a general limitation of the virtual machine's compatibility with the ESXi version of the selected host.This may also happen using any other automated migrations like DRS:
"Incompatible due to Virtual machine is configured to use a device that prevents the operation: Device 'HD audio ' has a backing type that is not supported. This is a general limitation of the virtual machine's compatibility with the ESXi version of the selected host." VM (Name) has no compatible host within cluster to VMotion to.
Cause
Incompatibility: The VM is configured to use a device that prevents the operation: Device 'HD audio' has a backing type that is not supported.
Resolution
There are a couple of solutions/workarounds.
- Power off the VM and migrate it to the wanted host then power the VM back on.
- Remove the device in the VM settings (Or edit the vmx file to remove it).
- Snapshot the VM and check that Veeam or the Backup software has a copy of the VM (if there was emergency).
- Shut down the VM
- SSH to the ESXi-host
- Remove audio-device from .vmx-file:
vi <path-to-vm>\VMname.vmx
- Delete lines with sound, put your cursor on the applicable line with the arrow keys and press dd:
sound.autoDetect = "TRUE" sound.virtualDev = "hdaudio" sound.fileName = "-1" sound.present = "TRUE" sound.pciSlotNumber = "35"
- Find the Vmid for the affected VM:
vim-cmd vmsvc/getallvms | grep <vm name>
- For example:
vim-cmd vmsvc/getallvms | grep RANDOM-VM-04 20 RANDOM-VM-04 [VxRail-Virtual-SAN-Datastore] f859685d-e61f-6b23-2ae9-e4434b819160/RANDOM-VM-04.vmx
- In the above example the vmid 20, is the vmid.
- Reload configuration for the VM:
vim-cmd vmsvc/reload <Vmid-of-VM
- For example:
vim-cmd vmsvc/reload 20
- Done
- Refresh the vCenter UI and confirm that the device is now missing from the VM's settings.
- Start the VM and vMotion the VM to another host.
Affected Products
VxRail Appliance FamilyProducts
Pivotal Ready Architecture, VxRail 460 and 470 Nodes, VxRail Appliance Family, VxRail Appliance Series, VxRail G410, VxRail E Series Nodes, VxRail E460, VxRail E560, VxRail E560 VCF, VxRail E560F, VxRail E560F VCF, VxRail E560N, VxRail E560N VCF
, VxRail G560, VxRail G560 VCF, VxRail G560F, VxRail G560F VCF, VxRail Gen2 Hardware, VxRail P Series Nodes, VxRail P470, VxRail P570, VxRail P570 VCF, VxRail P570F, VxRail P570F VCF, VxRail P580N, VxRail P580N VCF, VxRail S Series Nodes, VxRail S470, VxRail S570, VxRail S570 VCF, VxRail Software, VxRail V Series Nodes, VxRail V470, VxRail V570, VxRail V570 VCF, VxRail V570F, VxRail V570F VCF
...
Article Properties
Article Number: 000173168
Article Type: Solution
Last Modified: 08 Sept 2025
Version: 5
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.