虛擬機使用鏡像文件安裝系統(tǒng)

場景說明：

        指定Linux鏡像之后，點擊電源開始安裝，安裝完成之后，卸載ISO，進(jìn)入BIOS，設(shè)置從硬盤啟動。vmvare有提供快速安裝的方式。當(dāng)前的安裝類似于手動安裝，模擬真實的環(huán)境

操作步驟：

1）設(shè)置虛擬機的基本參數(shù)，包括虛擬機的基本磁盤和內(nèi)存配額，存放地點等等

2）單擊設(shè)置，進(jìn)入設(shè)備，選擇CD/DVD，裝載Fedora.iso系統(tǒng)安裝鏡像。

3）配置完成之后，選擇打開該虛擬機的電源

4）鼠標(biāo)的焦點必須在虛擬機的中央，左手按下F2，右手鼠標(biāo)點擊中央，出現(xiàn)BIOS界面

5）選擇從CD/DVD啟動，

6）F10,保存退出

7）安裝完成之后，請到設(shè)置中卸載Fedora.iso光盤，選擇從硬盤啟動，或者進(jìn)入BIOS中，

選擇從硬盤啟動

后果：這個問題花費1天的時間，反饋的消息是為什么老是進(jìn)入到安裝的界面，（實際的環(huán)境是：安裝和啟動用的是同一個界面，由于安裝完成之后和啟動只是選擇了不同的菜單項，所以在別人看來沒有發(fā)生任何的變化，以為syslinux.cfg文件中的hiddenmenu注釋掉之后無效。

1虛擬機進(jìn)入BIOS設(shè)置

場景描述：當(dāng)需要替換到虛擬機中硬盤的內(nèi)容，需要使用fedaro啟動系統(tǒng)，這個時候，出現(xiàn)

無法加載BIOS的情況，即使是按下F2按鍵。

曾經(jīng)出現(xiàn)的情況：

鼠標(biāo)的焦點必須在虛擬機的中央，否則無法選中。

2 Linux 修改系統(tǒng)的字符集為GBK，或者GB18等，導(dǎo)致系統(tǒng)啟動異常

錯誤如下：

2016-08-06T09:15:49.237+08:00| vmui| I120: Vix_InitializeGlobalState: enableExternalThreadInterface = TRUE

2016-08-06T09:15:49.237+08:00| vmui| I120: Vix_InitializeGlobalState: enableVigor = FALSE

2016-08-06T09:15:49.237+08:00| vmui| I120: LOCALE GBK -> zh_CN User=804 System=804

2016-08-06T09:15:49.237+08:00| vmui| I120: Msg_SetLocaleEx: HostLocale=GBK UserLocale=zh_CN

2016-08-06T09:15:49.277+08:00| vmui| I120: VixHost_ConnectEx: version -1, hostType 3, hostName (null), hostPort 0, options 8707

2016-08-06T09:15:49.278+08:00| vmui| I120: REM-USB: Protocol version min:15 current:16. hostId:44 45 4c 4c 51 00 10 38-80 51 c2 c0 4f 48 59 31

2016-08-06T09:15:49.278+08:00| vmui| I120: REM-USB: Initializing 'Generic' backend

2016-08-06T09:15:49.285+08:00| vmui| I120: DictionaryLoad: Cannot open file "C:\Users\Administrator\AppData\Roaming\VMware\preferences-private.ini": The system cannot find the file specified.

2016-08-06T09:15:49.351+08:00| vmui| I120: CDS: Initializing a CDS updater client 1.0 for product ws-windows, version 11.0.0 (workspace C:\Users\Administrator\AppData\Local\VMware\vmware-custData-1398)

2016-08-06T09:15:49.351+08:00| vmui| I120: LOCALE GBK -> zh_CN User=804 System=804

2016-08-06T09:15:49.393+08:00| vmui| I120: CDS: Initializing a CDS updater client 1.0 for product ws-windows, version 11.0.0.2305329 (workspace C:\Users\Administrator\AppData\Local\VMware\vmware-download-1398)

2016-08-06T09:15:49.393+08:00| vmui| I120: LOCALE GBK -> zh_CN User=804 System=804

2016-08-06T09:15:49.394+08:00| vmui| I120: cui::ComponentMgrCDS::RefreshComponentListWithDefaults: CDS_UNKNOWN_PRODUCT_ERROR for product player-linux

2016-08-06T09:15:49.394+08:00| vmui| I120: CDS: CdsUtil_QueryMsiByProductCode: {A53A11EA-0095-493F-86FA-A15E8A86A405} is unknown in the MSI database.

2016-08-06T09:15:49.394+08:00| vmui| I120: CDS: CdsUtil_QueryMsiByProductCode: {313C6E9F-180C-46C3-8CB1-A2AFB34DF643} is unknown in the MSI database.

2016-08-06T09:15:49.416+08:00| vmui| I120: CDS error: CdsUtil_QueryMsiPropertyByProductCode: MsiViewFetch failed: 259.

2016-08-06T09:15:49.431+08:00| vmui| I120: CDS error: CdsUtil_QueryMsiPropertyByProductCode: MsiViewFetch failed: 259.

2016-08-06T09:15:49.444+08:00| vmui| I120: CDS error: CdsUtil_QueryMsiPropertyByProductCode: MsiViewFetch failed: 259.

2016-08-06T09:15:49.457+08:00| vmui| I120: CDS error: CdsUtil_QueryMsiPropertyByProductCode: MsiViewFetch failed: 259.

2016-08-06T09:15:49.470+08:00| vmui| I120: CDS error: CdsUtil_QueryMsiPropertyByProductCode: MsiViewFetch failed: 259.

2016-08-06T09:15:49.476+08:00| vmui| I120: CDS error: CdsUtil_QueryMsiPropertyByProductCode: MsiViewFetch failed: 259.

2016-08-06T09:15:49.477+08:00| vmui| I120: cui::ComponentMgrCDS::RefreshComponentListWithDefaults: CDS_UNKNOWN_PRODUCT_ERROR for product ws-linux