VMware Communities
wayneicy
Contributor
Contributor
Jump to solution

In VMWare workstation 8.0.1, when playing the CTLite VM it starts and then immediately shuts down.

Hi

Host:Thinkpad x200,4G RAM, Windows 7 Ultimate, 64-bit Service Pack 1

guest:linux centos-64bit,2G RAM

vm:workstation 8.0.1

My issure is that when i start the guest vm ,it immediately shuts down. the flowing is the error message:

-----------------------------------------------------------------------------------------------------------------------------

2012-11-26T14:47:55.828+08:00| vmui| I120: CDWMThumbProxyWnd::OnActivate: Thumbnail activated, path:
2012-11-26T14:47:57.809+08:00| vmui| I120: CVMUIApp::OnCtxCurrentObj: D:\Program Files\CloudTestLite\CloudTest Lite.vmwarevm\CloudTest Lite.vmx
2012-11-26T14:47:57.830+08:00| vmui| I120: wui::control::MKSPanel::UpdateMKSLayout: MKS view is not initialized or not rendering.
2012-11-26T14:47:57.830+08:00| vmui| I120: wui::control::MKSPanel::UpdateMKSLayout: MKS view is not initialized or not rendering.
2012-11-26T14:47:57.830+08:00| vmui| I120: wui::control::MKSPanel::UpdateMKSLayout: MKS view is not initialized or not rendering.
2012-11-26T14:47:58.058+08:00| vmui| I120: wui::control::MKSPanel::UpdateMKSLayout: MKS view is not initialized or not rendering.
2012-11-26T14:47:58.058+08:00| vmui| I120: wui::control::MKSPanel::UpdateMKSLayout: MKS view is not initialized or not rendering.
2012-11-26T14:47:58.058+08:00| vmui| I120: wui::control::MKSPanel::UpdateMKSLayout: MKS view is not initialized or not rendering.
2012-11-26T14:47:58.157+08:00| vmui| I120: CVMUIFrame::OnGuestTopologyChanged: Passing main UI rect: 0x0 @ 0,0
2012-11-26T14:47:58.157+08:00| vmui| I120: cui::MKSScreenWindowCoordinator::HandleGuestTopologyChange: main UI rect: 0x0 @ 0,0
2012-11-26T14:47:58.157+08:00| vmui| I120: cui::MKSScreenWindowCoordinator::HandleGuestTopologyChange: Found 0 present screens
2012-11-26T14:47:58.157+08:00| vmui| I120: cui::MKSScreenWindowCoordinator::HandleGuestTopologyChange: Windows for extra guest monitors will not be shown
2012-11-26T14:47:58.157+08:00| vmui| I120: cui::MKSScreenWindowCoordinator::HandleGuestTopologyChange: setting main view to all displays
2012-11-26T14:48:00.542+08:00| vmui| I120: VMHSVMCbPower: D:\Program Files\CloudTestLite\CloudTest Lite.vmwarevm\CloudTest Lite.vmx, Setting state of VM to powerOn with option soft
2012-11-26T14:48:01.080+08:00| vmui| I120: D:\Program Files\CloudTestLite\CloudTest Lite.vmwarevm\CloudTest Lite.vmx: VMHSOnHostExecVMXSuccess: vmPath=/vm/#0c3b139090c83bc4/
2012-11-26T14:48:01.080+08:00| vmui| I120: VmdbAddConnection: cnxPath=/db/connection/#9c/, cnxIx=1
2012-11-26T14:48:01.180+08:00| vmui| I120: D:\Program Files\CloudTestLite\CloudTest Lite.vmwarevm\CloudTest Lite.vmx: Mounting virtual machine paths on connection: /db/connection/#9c/.
2012-11-26T14:48:01.219+08:00| vmui| I120: cui::MKS::OnVMStateChanged
2012-11-26T14:48:01.219+08:00| vmui| I120: cui::MKS::SetAttached
2012-11-26T14:48:01.219+08:00| vmui| I120: cui::MKS::OnSetAttachedCompleted
2012-11-26T14:48:01.220+08:00| vmui| I120: wui::control::MKSPanel::UpdateMKSLayout: MKS view is not initialized or not rendering.
2012-11-26T14:48:01.285+08:00| vmui| I120: D:\Program Files\CloudTestLite\CloudTest Lite.vmwarevm\CloudTest Lite.vmx: Mount VM completion for vm.
2012-11-26T14:48:01.285+08:00| vmui| I120: VigorClient_ConnectOnlineVmhs: Connecting to VMHS-managed VM at /vm/#0c3b139090c83bc4/
2012-11-26T14:48:01.285+08:00| vmui| I120: D:\Program Files\CloudTestLite\CloudTest Lite.vmwarevm\CloudTest Lite.vmx: Mount VM Complete: OK
2012-11-26T14:48:07.338+08:00| vmui| I120: VmdbPipeStreamsOvlError Couldn't read: (109) The pipe has been ended.
2012-11-26T14:48:07.338+08:00| vmui| I120: VmdbCnxDisconnect: Disconnect: closed pipe for sub cnx '/db/connection/#9c/' (-32)
2012-11-26T14:48:07.356+08:00| vmui| I120: D:\Program Files\CloudTestLite\CloudTest Lite.vmwarevm\CloudTest Lite.vmx: VMX status has been set.
2012-11-26T14:48:07.356+08:00| vmui| I120: D:\Program Files\CloudTestLite\CloudTest Lite.vmwarevm\CloudTest Lite.vmx: Disconnect check in progress.
2012-11-26T14:48:07.356+08:00| vmui| I120: D:\Program Files\CloudTestLite\CloudTest Lite.vmwarevm\CloudTest Lite.vmx: Unmounting the vm.
2012-11-26T14:48:07.357+08:00| vmui| I120: D:\Program Files\CloudTestLite\CloudTest Lite.vmwarevm\CloudTest Lite.vmx: VMDB unmount initiated.
2012-11-26T14:48:07.357+08:00| vmui| I120: D:\Program Files\CloudTestLite\CloudTest Lite.vmwarevm\CloudTest Lite.vmx: Unmounting VM complete.
2012-11-26T14:48:07.357+08:00| vmui| I120: D:\Program Files\CloudTestLite\CloudTest Lite.vmwarevm\CloudTest Lite.vmx: Pending unmount, deferring cleanup of "/vm/#0c3b139090c83bc4/vmx/execState/req/#9b/".
2012-11-26T14:48:07.377+08:00| vmui| I120: cui::MKS::OnVMStateChanged
2012-11-26T14:48:07.378+08:00| vmui| I120: cui::MKS::SetAttached
2012-11-26T14:48:07.378+08:00| vmui| I120: cui::MKS::OnSetAttachedCompleted
2012-11-26T14:48:07.379+08:00| vmui| I120: Internal VMDB error: Message has already been displayed
2012-11-26T14:48:07.426+08:00| vmui| I120: D:\Program Files\CloudTestLite\CloudTest Lite.vmwarevm\CloudTest Lite.vmx: Mount state values have changed.
2012-11-26T14:48:07.426+08:00| vmui| I120: VmdbDbRemoveCnx: Removing Cnx from Db for '/db/connection/#9c/'
2012-11-26T14:48:07.427+08:00| vmui| I120: D:\Program Files\CloudTestLite\CloudTest Lite.vmwarevm\CloudTest Lite.vmx: Mount state values have changed.
2012-11-26T14:48:07.427+08:00| vmui| I120: D:\Program Files\CloudTestLite\CloudTest Lite.vmwarevm\CloudTest Lite.vmx: Reloading config state.
2012-11-26T14:48:07.444+08:00| vmui| I120: VMHS: Transitioned vmx/execState/val to poweredOff
2012-11-26T14:48:07.538+08:00| vmui| I120: SnapshotTree: Populating (D:\Program Files\CloudTestLite\CloudTest Lite.vmwarevm\CloudTest Lite.vmx)
2012-11-26T14:48:07.538+08:00| vmui| I120: SnapshotTree: Emitting refresh (D:\Program Files\CloudTestLite\CloudTest Lite.vmwarevm\CloudTest Lite.vmx)
2012-11-26T14:48:07.549+08:00| vmui| I120: Setting power state poweredOff
2012-11-26T14:48:07.584+08:00| vmui| I120: Vix: [4076 foundryVM.c:10856]: FoundryVMMountStateChangeCallback: remount complete, set flag, VM = D:\Program Files\CloudTestLite\CloudTest Lite.vmwarevm\CloudTest Lite.vmx
2012-11-26T14:48:07.599+08:00| vmui| I120: Vix: [4076 foundryVMPowerOps.c:1012]: FoundryVMPowerStateChangeCallback: D:\Program Files\CloudTestLite\CloudTest Lite.vmwarevm\CloudTest Lite.vmx, vmx/execState/val = poweredOff.

0 Kudos
1 Solution

Accepted Solutions
continuum
Immortal
Immortal
Jump to solution

see this part of the log:

[msg.cpuid.noLongmodeQuestion] This virtual machine is configured for 64-bit guest operating systems. However, 64-bit operation is not possible.
This host is VT-capable, but VT is disabled.                                                                                                   
VT might be disabled if it has been disabled in the BIOS settings or the host has not been power-cycled since changing this setting.           
(1) Verify that the BIOS settings enable VT and disable 'trusted execution.'                                                                   
(2) Power-cycle the host if either of these BIOS settings have been changed.                                                                   
(3) Power-cycle the host if you have not done so since installing VMware Workstation.                                                          
(4) Update the host's BIOS to the latest version.                                                                                              
For more detailed information, see http://vmware.com/info?id=152.                                                                              
Continue without 64-bit support?                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

View solution in original post

0 Kudos
6 Replies
continuum
Immortal
Immortal
Jump to solution

what is a CTLite VM ?

are you sure your vmnets are working correctly ?
the vmware.log would be useful


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

0 Kudos
wayneicy
Contributor
Contributor
Jump to solution

CTLite vm is a cloud testing product of soasta.

vmware.log is in attached file named vmware-ui-baiwei-3576.log.

there is some error happend, but i don't know what means of it....

0 Kudos
continuum
Immortal
Immortal
Jump to solution

you attached the UI-log - please attach the vmware.log from inside the VMs directory


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

0 Kudos
wayneicy
Contributor
Contributor
Jump to solution

oh,sorry,i missunderstand....

i find no file named vmware.log in my workstation8.0.1's path. but i find a file in vm image's directory named vmware ,it is a txt file.

here is the vmware.log which i found.

0 Kudos
continuum
Immortal
Immortal
Jump to solution

see this part of the log:

[msg.cpuid.noLongmodeQuestion] This virtual machine is configured for 64-bit guest operating systems. However, 64-bit operation is not possible.
This host is VT-capable, but VT is disabled.                                                                                                   
VT might be disabled if it has been disabled in the BIOS settings or the host has not been power-cycled since changing this setting.           
(1) Verify that the BIOS settings enable VT and disable 'trusted execution.'                                                                   
(2) Power-cycle the host if either of these BIOS settings have been changed.                                                                   
(3) Power-cycle the host if you have not done so since installing VMware Workstation.                                                          
(4) Update the host's BIOS to the latest version.                                                                                              
For more detailed information, see http://vmware.com/info?id=152.                                                                              
Continue without 64-bit support?                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

0 Kudos
wayneicy
Contributor
Contributor
Jump to solution

Thanks a lot ,it works~

0 Kudos