Migrating a VM with HD Audio devices connected fails with error "Device 'HD audio ' has a backing type that is not supported"

-

 

Migrating a VM with HD Audio devices connected fails with error "Device 'HD audio ' has a backing type that is not supported"


  • Attempting to vMotion a virtual machine fails with the error:
    Virtual machine is configured to use a device that prevents the opration: Device "HD Audio" has a backing type that is not supported. This is a general limitation of the virtual machines's compatibility with ESXi version of the selected host.
  • Virtual machine has HD audio device connected.
There is no resolution.  vMotion is not allowed when an audio device is connected. This is by design. 

Workaround:
To perform a migration, the device needs to be disconnected or the vm will need to be powered off.

To disconnect the HD Audio device, the vmx file needs to be manually edited :
  • Power off the VM
  • SSH to the ESXi where the VM is registered
  • Make a backup of the VMX file by copying it to another location
  • Remove audio-device from .vmx-file: 
          cd /vmfs/volumes/datastore/VMname
          vi VMname.vmx
  • Comment the following lines with # like below:
        #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
  • Reload configuration for the VM:     vim-cmd vmsvc/reload <Vmid-of-VM>
  • Power on the VM and attempt the migration again
Note: If unable to access via SSH, use the vSphere Client to access the VM's datastore and download the corresponding .vmx file. Once downloaded, use a text editor to make the above adjustments and then reupload the .vmx file with the changes into the datastore

Comments

Post a Comment

Popular posts from this blog

Extracting and using a modified VMWare Player BIOS or UEFI firmware

-
https://pete.akeo.ie/2011/06/extracting-and-using-modified-vmware.html Extracting and using a modified VMWare Player BIOS or UEFI firmware (updated 2016.05.17 for VMWare UEFI firmware extraction) One day or another, you may want to play with BIOS/UEFI firmware modification. But before jumping into physical motherboard flash alteration, where the consequences of a mishap can be difficult to salvage, experimenting with the BIOS/UEFI in a virtual environment sounds like a sound first step. You have of course the opportunity to do so using  bochs , however the ubiquitous nature and ease of use of the (freely available)  VMware Player  can turn the latter in a much better candidate for the job if you don't really care about the extra features that bochs brings in. This post details how one can extract the BIOS/UEFI firmwares used by the VMWare Player, and how to setup the player to use a modified one. Download and install VMware Player. The current version of VMwar...
Read more

Activate Synology Active Backup for Business for DSM 6

-
 Activate Synology Active Backup for Business with Xpenology DSM  https://gist.github.com/igresc/91e468f3d2ad5f2f7407262ba6f0dd56 Install the package and run the URL below on the browser . Active Backup for Business 1. Replace the IP, username, and password  http:// 192.168.0.1 :5000/webapi/auth.cgi?api=SYNO.API.Auth&method=Login&version=1&account= admin &passwd= password {"success":true} 2. Replace IP and Serial http:// 192.168.0.1 :5000/webapi/entry.cgi?api=SYNO.ActiveBackup.Activation&method=set&version=1&activated=true&serial_number= 1780PDN123456 {"data":{"activated":true},"success":true} Active Backup for G Suite 1. Replace IP http:// 192.168.0.1 :5000/webapi/entry.cgi?api=SYNO.ActiveBackupGSuite&method=get_activation&version=1 {"data":{"activated":false,"serial_number":"1780PDN123456"},"success":true} 2. Replace IP and Serial 1. Replace IP http:// 19...
Read more

Windows 11 internet/account bypass

-
Image
https://github.com/the-P1neapple/WinJS-Microsoft-Account-Bypass WinJS-Microsoft-Account-Bypass Overview This guide explains a method to bypass the Microsoft Account (MSA) requirement during the Windows 11 Out-Of-Box Experience (OOBE) by using the Developer Console to invoke a hidden local account setup screen. This method was discovered by examining the Windows 11 OOBE source code, which revealed an event listener for a hidden  _localAccountButton . Note A faster method has since been discovered using Command Prompt ( Source ), this repo was made 7 months prior to that discovery. The method I have documented is still the only known method for S-Mode installations. Following these steps, you can create a local account without needing to sign in with or create a Microsoft account. I also have a  Youtube Tutorial  that follows the same instructions below Steps to Bypass Microsoft Account Setup 1. Start Windows 11 Setup Begin the Windows 11 Setup Process. Select your region a...
Read more