十年网站开发经验 + 多家企业客户 + 靠谱的建站团队
量身定制 + 运营维护+专业推广+无忧售后,网站问题一站解决
场景说明:
创新互联是一家专业提供巴州企业网站建设,专注与成都网站建设、成都网站设计、H5开发、小程序制作等业务。10年已为巴州众多企业、政府机构等服务。创新互联专业网络公司优惠进行中。
指定Linux镜像之后,点击电源开始安装,安装完成之后,卸载ISO,进入BIOS,设置从硬盘启动。vmvare有提供快速安装的方式。当前的安装类似于手动安装,模拟真实的环境
操作步骤:
1)设置虚拟机的基本参数,包括虚拟机的基本磁盘和内存配额,存放地点等等
2)单击设置,进入设备,选择CD/DVD,装载Fedora.iso系统安装镜像。
3)配置完成之后,选择打开该虚拟机的电源
4)鼠标的焦点必须在虚拟机的中央,左手按下F2,右手鼠标点击中央,出现BIOS界面
5)选择从CD/DVD启动,
6)F10,保存退出
7)安装完成之后,请到设置中卸载Fedora.iso光盘,选择从硬盘启动,或者进入BIOS中,
选择从硬盘启动
后果:这个问题花费1天的时间,反馈的消息是为什么老是进入到安装的界面,(实际的环境是:安装和启动用的是同一个界面,由于安装完成之后和启动只是选择了不同的菜单项,所以在别人看来没有发生任何的变化,以为syslinux.cfg文件中的hiddenmenu注释掉之后无效。
1虚拟机进入BIOS设置
场景描述:当需要替换到虚拟机中硬盘的内容,需要使用fedaro启动系统,这个时候,出现
无法加载BIOS的情况,即使是按下F2按键。
曾经出现的情况:
鼠标的焦点必须在虚拟机的中央,否则无法选中。
2 Linux 修改系统的字符集为GBK,或者GB18等,导致系统启动异常
错误如下:
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