vCenter Convert 6.2转换的linux虚拟机找不到硬盘无法启动

问题遇到的现象和发生背景

将原Red Hat linux服务器通过vCenter Convert 6.2 虚拟化到宿主Exsi 6.7主机上,打开虚拟后的虚拟机时,虚拟机里无法找到虚拟后的硬盘。

操作环境、软件版本等信息

vCenter Convert 6.2 在win7下转换远程的linux服务器,虚拟机宿主服务器Exsi 6.7.

尝试过的解决方法

尝试新建SCSI驱动器,更改硬盘配置;将wmdk文件从厚置模式转换成精简模式;

我想要达到的结果

目标是,将转换后的虚拟机能够找到硬盘,正确引导进入系统。
以下是虚拟机启动电源后的关键日志部分:


```bash
2022-10-21T00:33:11.595Z| vmx| I125: OvhdMem: memsize 65536 MB VMK fixed 3462 pages var(mem) 529 pages var(cpu) 8 cbrcOverhead 0 pages total 37532 pages
2022-10-21T00:33:11.595Z| vmx| I125: VMMEM: Maximum Reservation: 645MB (MainMem=65536MB) VMK=146MB
2022-10-21T00:33:11.603Z| vmx| I125: Tools: ToolsRunningStatus_Exit, delayedRequest is 0xE4F5EA5660
2022-10-21T00:33:11.603Z| vmx| I125: SVMotion_PowerOff: Not running Storage vMotion. Nothing to do
2022-10-21T00:33:11.617Z| vmx| I125:** Destroying virtual dev for scsi0:0 vscsi=8223**
2022-10-21T00:33:11.617Z| vmx| I125: VMMon_VSCSIStopVports: No such target on adapter
2022-10-21T00:33:11.619Z| vmx| I125: MKS thread was already stopped
2022-10-21T00:33:11.619Z| mks| I125: MKS-RenderMain: Stopping MKSBasicOps
2022-10-21T00:33:11.619Z| mks| I125: MKS PowerOff
2022-10-21T00:33:11.619Z| mks| I125: MKS thread is exiting
2022-10-21T00:33:11.620Z| vmx| I125: SVMotion_PowerOff: Not running Storage vMotion. Nothing to do
2022-10-21T00:33:11.620Z| vmx| I125: scsi0:0: numIOs = 0 numMergedIOs = 0 numSplitIOs = 0 ( 0.0%)
2022-10-21T00:33:11.620Z| vmx| I125: Closing disk 'scsi0:0'
2022-10-21T00:33:11.621Z| vmx| I125: DISKLIB-VMFS  : "/vmfs/volumes/6318250f-2fdc6244-75ce-70e2842310c4/mixX/mixX-flat.vmdk" : closed.
2022-10-21T00:33:11.625Z| vmx| I125: Vix: [mainDispatch.c:1180]: VMAutomationPowerOff: Powering off.
2022-10-21T00:33:11.637Z| vmx| I125: WORKER: asyncOps=1 maxActiveOps=1 maxPending=0 maxCompleted=0
2022-10-21T00:33:11.666Z| vmx| I125: Vix: [mainDispatch.c:4239]: VMAutomation_ReportPowerOpFinished: statevar=1, newAppState=1873, success=1 additionalError=0
2022-10-21T00:33:11.666Z| vmx| I125: Vix: [mainDispatch.c:4258]: VMAutomation: Ignoring ReportPowerOpFinished because the VMX is shutting down.
2022-10-21T00:33:11.667Z| vmx| A100: ConfigDB: Setting cleanShutdown = "TRUE"
2022-10-21T00:33:11.679Z| vmx| I125: Vix: [mainDispatch.c:4239]: VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1870, success=1 additionalError=0
2022-10-21T00:33:11.679Z| vmx| I125: Vix: [mainDispatch.c:4258]: VMAutomation: Ignoring ReportPowerOpFinished because the VMX is shutting down.
2022-10-21T00:33:11.679Z| vmx| I125: Transitioned vmx/execState/val to poweredOff
2022-10-21T00:33:11.679Z| vmx| I125: Vigor_ClientRequestCb: failed to do op=3 on unregistered device 'Tools' (cmd=queryFields)
2022-10-21T00:33:11.679Z| vmx| I125: VMX idle exit
2022-10-21T00:33:11.709Z| vmx| I125: Vix: [mainDispatch.c:832]: VMAutomation_LateShutdown()
2022-10-21T00:33:11.709Z| vmx| I125: Vix: [mainDispatch.c:781]: VMAutomationCloseListenerSocket. Closing listener socket.
2022-10-21T00:33:11.710Z| vmx| I125: Flushing VMX VMDB connections
2022-10-21T00:33:11.710Z| vmx| I125: VigorTransport_ServerCloseClient: Closing transport E4F5BC6C80 (err = 0)
2022-10-21T00:33:11.710Z| vmx| I125: VigorTransport_ServerDestroy: server destroyed.
2022-10-21T00:33:11.711Z| vmx| I125: VMX exit (0).
2022-10-21T00:33:11.712Z| vmx| I125: OBJLIB-LIB: ObjLib cleanup done.
2022-10-21T00:33:11.712Z| vmx| I125: AIOMGR-S : stat o=3 r=21 w=1 i=0 br=106992 bw=128
2022-10-21T00:33:11.712Z| vmx| W115: VMX has left the building: 0.


```

检查一下虚拟机文件,看一下编辑设置里面硬盘状态