Latest revision as of 05:24, 1 July 2020

[edit] Servers

[edit] Server Problems

• Failed Server

[edit] Installing Servers

[edit] Windows 10 or Windows 2016 Hangs On Install

On the node that tried to install the Windows 2016 server, run this:

grep 'unhandled rdmsr' /var/log/messages

If you see a line like this:

kvm: 21390: cpu0 unhandled rdmsr: 0x3a

Edit the server's provision script (/shared/provision/<server_name>.xml) and add the following to the end of the last line:

 --cpu Nehalem,+fsgsbase

TODO: Show a diff

If you see any other '--cpu ...' line, delete is. Save the changes and then re-run the provision script.

Note: This script is only part of the provision process. Once you run it, Striker will detect it and recognise that it isn't fully added yet. You will be presented with a button to complete the setup.

/shared/provision/<server_name>.xml

TODO: Show output

[edit] Windows 2019 Hangs on Reboot

The CPU needs to be configured as such in the definition file;

  <cpu mode='custom' match='exact'>
    <model fallback='allow'>Nehalem</model>
    <feature policy='force' name='fsgsbase'/>
  </cpu>