You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue is on line 907, there is a null exception if there's an RDM in the set of disks attached to a VM.
The workaround I used was to filter out RDMs: $vmDisk = $vm | Get-HardDisk | Where-Object { $_.DiskType -ne 'RawPhysical' } |Where-Object {$_.ExtensionData.backing.uuid.replace("-","") -eq $VMdiskSerialNumber.SerialNumber}
The text was updated successfully, but these errors were encountered:
To reproduce, attach both a vvol and an RDM to a VM and use Get-VmdkFromWindowsDisk.
The issue is on line 907, there is a null exception if there's an RDM in the set of disks attached to a VM.
The workaround I used was to filter out RDMs:
$vmDisk = $vm | Get-HardDisk | Where-Object { $_.DiskType -ne 'RawPhysical' } |Where-Object {$_.ExtensionData.backing.uuid.replace("-","") -eq $VMdiskSerialNumber.SerialNumber}
The text was updated successfully, but these errors were encountered: