Difference between revisions of "Preparing a Windows 2008 Server to be used as an openQRM Hyper-V Host"
From openQRM
Line 51: | Line 51: | ||
== Known Bugs == | == Known Bugs == | ||
− | Hyper-V 2008 does not support all CPUs. [https://support.microsoft.com/en-us/kb/2568088 Refer to Windows Support] | + | |
+ | # Hyper-V 2008 does not support all CPUs. [https://support.microsoft.com/en-us/kb/2568088 Refer to Windows Support] | ||
There is a known workaround with the AMD CPU AVX bug: | There is a known workaround with the AMD CPU AVX bug: | ||
− | If you | + | If you receive this error message: |
[[File:13 Windows 2008 Hyper-V Server.png|none|thumb|390x390px]] | [[File:13 Windows 2008 Hyper-V Server.png|none|thumb|390x390px]] | ||
Navigate to the Processor settings for that respective VM and change the values to the following: | Navigate to the Processor settings for that respective VM and change the values to the following: | ||
− | [[File:14 Windows 2008 Hyper-V Server.png|none| | + | [[File:14 Windows 2008 Hyper-V Server.png|none|alt=|frame]] |
# | # |
Revision as of 09:57, 30 October 2020
Hyper-V PowerShell cmdlet
http://pshyperv.codeplex.com/releases
In the Server configuration wizard, enable .NET
In the Server Roles window, start Hyper-V
Download Hyper-V cmdlet and extract the files.
Install the cmdlet. Be sure to run the terminal as Administrator
When a Registry Editor warning pops up, click 'Yes'
If you get the message pictured here after installation, Close PowerShell and proceed:
Import the module and test it's function. This is done by opening PowerShell and inputting:
Import-Module 'C:\Program Files\Modules\Hyperv\Hyperv.psd1
Create a profile to auto start the cmdlet:
New-Item -path $profile -type file -force
Insert this line into the document and save it:
Import-Module 'C:\Program Files\Modules\Hyperv\Hyperv.psd1'
Import-Module 'C:\Program Files\Modules\Hyperv\Hyperv.psd1'
Known Bugs
- Hyper-V 2008 does not support all CPUs. Refer to Windows Support
There is a known workaround with the AMD CPU AVX bug:
If you receive this error message:
Navigate to the Processor settings for that respective VM and change the values to the following: