...
To install these packages using yum:
No Format |
---|
yum install expat expat-devel gcc krb5-libs krb5-devel libxml2 libxml2-devel openssl openssl-devel perl-DBD-MySQL xmlseclxmlsec1-openssl -y |
...
Example: LSI SAS drivers commonly need to be downloaded and the hardware IDs need to be added to the sysprep.inf files in order for computers with LSI SAS controllers to boot.
Panel | |
---|---|
|
Panel |
---|
PCI\VEN_1000&DEV_0622 = "C:\Sysprep\Drivers\Storage\LSI-SAS\symmpi.inf" |
Wiki Markup |
Based on the contents of the .inf file, the following is added to the Windows XP and Windows Server 2003 sysprep.inf files under \[SysprepMassStorage\]:
<ac:structured-macro ac:name="panel" ac:schema-version="1" ac:macro-id="ae17da0b-1c15-471b-aca4-3316b10d7eda"><ac:rich-text-body>
<p>PCI\VEN_1000&DEV_0622 = "C:\Sysprep\Drivers\Storage\LSI-SAS\symmpi.inf" <br/>
DEV_ 06240626 = "C:\Sysprep\Drivers\Storage\LSI-SAS\symmpi.inf" <br/>
DEV_ 06260628 = "C:\Sysprep\Drivers\Storage\LSI-SAS\symmpi.inf" <br/>
DEV_ 06280030 = "C:\Sysprep\Drivers\Storage\LSI-SAS\symmpi.inf" <br/>
DEV_ 00300032 = "C:\Sysprep\Drivers\Storage\LSI-SAS\symmpi.inf" <br/>
DEV_ 00320050 = "C:\Sysprep\Drivers\Storage\LSI-SAS\symmpi.inf" <br/>
DEV_ 00500054 = "C:\Sysprep\Drivers\Storage\LSI-SAS\symmpi.inf" <br/>
DEV_ 00540058 = "C:\Sysprep\Drivers\Storage\LSI-SAS\symmpi.inf" <br/>
DEV_ 00580056 = "C:\Sysprep\Drivers\Storage\LSI-SAS\symmpi.inf" <br/>
DEV_ 00560640 = "C:\Sysprep\Drivers\Storage\LSI-SAS\symmpi.inf" <br/>
DEV_ 06400646 = "C:\Sysprep\Drivers\Storage\LSI-SAS\symmpi.inf" <br/>
DEV_ 06460062 = "C:\Sysprep\Drivers\Storage\LSI-SAS\symmpi.inf" <br/>
DEV _0062 =_0054&SUBSYS_1F041028 = "C:\Sysprep\Drivers\Storage\LSI-SAS\symmpi.inf" <br/> PCI
DEV_0054& amp;SUBSYS_ 1F0410281F051028 = "C:\Sysprep\Drivers\Storage\LSI-SAS\symmpi.inf" <br/>
DEV_0054& amp;SUBSYS_ 1F0510281F061028 = "C:\Sysprep\Drivers\Storage\LSI-SAS\symmpi.inf" <br/>
DEV_0054& amp;SUBSYS_ 1F0610281F071028 = "C:\Sysprep\Drivers\Storage\LSI-SAS\symmpi.inf" <br/>
DEV_0054& amp;SUBSYS_ 1F0710281F081028 = "C:\Sysprep\Drivers\Storage\LSI-SAS\symmpi.inf" <br/>
DEV_0054& amp;SUBSYS_ 1F0810281F091028 = "C:\Sysprep\Drivers\Storage\LSI-SAS\symmpi.inf" <br/>
DEV_ 00540058& amp;SUBSYS_ 1F0910281F0E1028 = "C:\Sysprep\Drivers\Storage\LSI-SAS\symmpi.inf" <br/> PCI
DEV_0058& amp;SUBSYS _1F0E1028 = "C:\Sysprep\Drivers\Storage\LSI-SAS\symmpi.inf"<br/> PCI\VEN_ 1000&DEV_0058&SUBSYS_1F0F1028 = "C:\Sysprep\Drivers\Storage\LSI-SAS\symmpi.inf" <br/>
DEV_0058& amp;SUBSYS_1F101028 = "C:\Sysprep\Drivers\Storage\LSI-SAS\symmpi.inf" </p></ac:rich-text-body></ac:structured-macro>If you have hardware using an LSI SAS controller (IBM HS21 blades), the section above can be copied and pasted into your sysprep.inf |
Panel |
---|
/usr/local/vcl/tools/Windows_XP/Utilities/Sysprep/sysprep.inf |
Panel |
---|
/usr/local/vcl/tools/Windows_Server_2003/Utilities/Sysprep/sysprep.inf |
NOTICE: The WSName.exe utility is no longer available. The set_computer_name.vbs script which calls WSName.exe will be rewritten for the 2.2 release of VCL. In the meantime, this script is being left intact in case you have a previously released version of WSName.exe or are able to obtain it from another source.
...
Panel |
---|
/usr/local/vcl/tools/Windows/Utilities/SPDrvScn/spdrvscn.exe |
To insure that the management node can SSH into your virtual machines without problems, you will need to edit the SSH client config for the root user:
No Format |
---|
vi /root/.ssh/config
|
Add the following lines to the top of the configuration file.
No Format |
---|
Host <vmhost> <vmhost ip>
UserKnownHostsFile /dev/null
StrictHostKeyChecking no
|
Where:
This will insure that new VM hosts will not hang on the known hosts prompts when the management node attempts to connect to them for the first time.
...