set VM to allow migrations between different CPU types

Dec 12, 2009 at 6:25 AM

Is it possible to configure a VM to allow migrations between different CPU types with the library?  how?


thank you,



Dec 12, 2009 at 10:29 PM

Not directly , however you can do this

$procsSettingData=Get-VMCpuCount <MyVm>
$procsSettingData.LimitProcessorFeatures = $true
Set-VMRASD -vm  $vm -rasd $procsSettingData

<myVM>can be a variable containing a VM object or the name of a VM




Dec 14, 2009 at 6:27 PM

thank you for the reply.  this is what I have and what I am getting.  any ideas? 


"Creating VM"

 $myVM = (New-VM $vmName)
 set-vmMemory   $myVM $Memory
 set-VMCPUCount $myVM $cpuCount

(minor VM config here, removed to keep it short and simple for this post)

# set CPU to allow migrations between different CPU types
 $procsSettingData=Get-VMCpuCount $myVM
 $procsSettingData.LimitProcessorFeatures = $true
 Set-VMRASD -vm  $MyVM -rasd $procsSettingData

...start VM,

returning this error:

The term 'Set-VMRASD' is not recognized as the name of a cmdlet, function, scri
pt file, or operable program. Check the spelling of the name, or if a path was
included, verify that the path is correct and try again.
At C:\cns\ProvisionSDCAVM.ps1:31 char:12
+  Set-VMRASD <<<<  -vm  $MyVM -rasd $procsSettingData
    + CategoryInfo          : ObjectNotFound: (Set-VMRASD:String) [], CommandN
    + FullyQualifiedErrorId : CommandNotFoundException




Dec 15, 2009 at 1:56 PM
Edited Dec 15, 2009 at 1:57 PM

Barry,  sorry I made an assumption which is probably going to turn out to be the wrong one . This needs running the V2 (module) version, Set-VMRASD isn't in V1 - the all in one PS1 file.

I'm pretty sure the feature works ONLY with Hyper-V R2 so you should have PowerShell V2 and be able to use the new version of the library.


Dec 16, 2009 at 12:01 AM

awesome, thank you much