VMware Cloud Community
stevenfoo
Contributor
Contributor

CentOS 6.0 VM screen stop at vsphere console .... nothing works

Hi

We make a copy of our production VM running on linux centos 6.0 and restore it to another production vsphere 6.5 host.

Restore is working and we change the mac address and boot it up without LAN connected.

The boot was fine until the CentOS  6 screen and then it stop there without anything else.

We have tried to restore to another vsphere host, it still have the same issue. Anyone have any idea ?

linux-console-stop.jpg

Below are some of the vmware.log information at the end of the page.

2019-03-28T08:01:02.255Z| vcpu-0| I125: pciBridge7:3: ISA/VGA decoding enabled (ctrl 0004)

2019-03-28T08:01:02.255Z| vcpu-0| I125: pciBridge7:4: ISA/VGA decoding enabled (ctrl 0004)

2019-03-28T08:01:02.255Z| vcpu-0| I125: pciBridge7:5: ISA/VGA decoding enabled (ctrl 0004)

2019-03-28T08:01:02.255Z| vcpu-0| I125: pciBridge7:6: ISA/VGA decoding enabled (ctrl 0004)

2019-03-28T08:01:02.255Z| vcpu-0| I125: pciBridge7:7: ISA/VGA decoding enabled (ctrl 0004)

2019-03-28T08:01:02.733Z| vcpu-0| I125: KEYBOARD: Invalid mouse sample rate 102 Hz, using 100 instead

2019-03-28T08:01:02.986Z| svga| I125: SVGA hiding SVGA

2019-03-28T08:01:02.991Z| svga| I125: SVGA enabling SVGA

2019-03-28T08:01:03.587Z| vcpu-0| I125: CDROM: Emulate GET CONFIGURATION RT 0 starting feature 0

2019-03-28T08:01:03.587Z| vcpu-0| I125: CDROM: Emulate GET CONFIGURATION RT 0 starting feature 0

2019-03-28T08:01:04.364Z| vcpu-2| I125: HBACommon: First write on scsi0:0.fileName='/vmfs/volumes/5614d379-779a7417-90f0-3cfdfe019c40/UPGEATR/PENEATR.vmdk'

2019-03-28T08:01:04.364Z| vcpu-2| I125: DDB: "longContentID" = "29bd477e07ba591b654831450b3afb54" (was "a217529594250f92d4af7b61542a3a7b")

2019-03-28T08:01:04.391Z| vcpu-2| I125: DISKLIB-CHAIN : DiskChainUpdateContentID: old=0x542a3a7b, new=0xb3afb54 (29bd477e07ba591b654831450b3afb54)

2019-03-28T08:01:07.521Z| mks| I125: SOCKET 3 (144) Creating VNC remote connection.

2019-03-28T08:01:07.609Z| mks| W115: VNCENCODE 3 failed to allocate VNCBackBuffer

2019-03-28T08:01:07.969Z| vmx| I125: Tools_SetGuestResolution: Sending rpcMsg = Resolution_Set 1242 485

2019-03-28T08:01:11.876Z| vcpu-1| I125: CDROM: Emulate GET CONFIGURATION RT 0 starting feature 0

2019-03-28T08:01:11.876Z| vcpu-1| I125: CDROM: Emulate GET CONFIGURATION RT 0 starting feature 0

2019-03-28T08:01:18.038Z| vcpu-0| I125: Guest: toolbox: Version: build-2068191

2019-03-28T08:01:18.038Z| vcpu-0| W115: GuestRpc: application toolbox, changing channel 65535 -> 0

2019-03-28T08:01:18.038Z| vcpu-0| I125: GuestRpc: Channel 0, guest application toolbox.

2019-03-28T08:01:18.044Z| vcpu-0| I125: TOOLS autoupgrade protocol version 2

2019-03-28T08:01:18.044Z| vcpu-0| I125: TOOLS Received tools.set.version rpc call, version = 2147483647.

2019-03-28T08:01:18.044Z| vcpu-0| I125: TOOLS setting legacy tools version to '2147483647', manifest status is 8

2019-03-28T08:01:18.044Z| vcpu-0| I125: ToolsSetVersionWork: Updating the Tools Version in the disk

2019-03-28T08:01:18.071Z| vcpu-0| I125: ToolsSetVersionWork: Done updating the Tools Version in the disk

2019-03-28T08:01:18.071Z| vcpu-0| I125: VMXVmdb_SetToolsVersionStatus: status value set to 'unmanaged', 'unmanaged', install possible

2019-03-28T08:01:18.104Z| vmx| A100: ConfigDB: Setting extendedConfigFile = "PENEATR.vmxf"

2019-03-28T08:01:18.306Z| vcpu-2| I125: TOOLS state change 3 returned status 1

2019-03-28T08:01:18.306Z| vcpu-2| I125: Vix: [3044316 mainDispatch.c:4210]: VMAutomationReportPowerStateChange: Reporting power state change (opcode=2, err=0).

2019-03-28T08:01:20.398Z| vcpu-1| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 0

2019-03-28T08:01:20.398Z| vcpu-0| I125: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 0

2019-03-28T08:01:20.473Z| vcpu-2| I125: VMMouse: CMD Read ID

2019-03-28T08:01:20.473Z| vcpu-2| I125: VMMouse: CMD Disable

2019-03-28T08:01:20.473Z| vcpu-2| I125: VMMouse: Disabling VMMouse mode

2019-03-28T08:01:55.668Z| vmx| I125: GuestRpcSendTimedOut: message to toolbox-dnd timed out.

2019-03-28T08:02:07.971Z| vmx| I125: GuestRpcSendTimedOut: message to toolbox-dnd timed out.

2019-03-28T08:02:18.120Z| vmx| I125: GuestRpcSendTimedOut: message to toolbox-dnd timed out.

2019-03-28T08:02:47.797Z| vmx| I125: Tools_SetGuestResolution: Sending rpcMsg = Resolution_Set 1242 698

2019-03-28T08:03:47.799Z| vmx| I125: GuestRpcSendTimedOut: message to toolbox-dnd timed out.

2019-03-28T08:03:47.799Z| vmx| I125: Tools_SetGuestResolution: Sending rpcMsg = Resolution_Set 1242 485

2019-03-28T08:04:47.802Z| vmx| I125: GuestRpcSendTimedOut: message to toolbox-dnd timed out.

Reply
0 Kudos
1 Reply
stevenfoo
Contributor
Contributor

Just to update that I also restore to another vsphere host 6.7 U1, also I am seeing the same issue.

The screen stop there and there is nothing can't be done.

Reply
0 Kudos