Fixes issue hashicorp#10973: checks that VMMS WMI reference is null & throws appropriately
This commit is contained in:
parent
cca36d91ed
commit
6caa7bfa86
|
@ -355,6 +355,9 @@ function Report-ErrorVagrantVMImport {
|
||||||
)
|
)
|
||||||
|
|
||||||
$ManagementService = Get-WmiObject -Namespace 'root\virtualization\v2' -Class 'Msvm_VirtualSystemManagementService'
|
$ManagementService = Get-WmiObject -Namespace 'root\virtualization\v2' -Class 'Msvm_VirtualSystemManagementService'
|
||||||
|
if($null -eq $ManagementService) {
|
||||||
|
throw 'The Hyper-V Virtual Machine Management Service (VMMS) is not running.'
|
||||||
|
}
|
||||||
|
|
||||||
# Relative path names will fail when attempting to import a system
|
# Relative path names will fail when attempting to import a system
|
||||||
# definition so always ensure we are using the full path to the
|
# definition so always ensure we are using the full path to the
|
||||||
|
|
Loading…
Reference in New Issue