DisplayTopology_Set failed error message when trying to switch to Multi Monitor

[soaringeagle]

Occasionally when I try and switch VMware Workstation 6.5 into multi monitor mode, I get the following error messages,

Aug 18 13:22:04.078: vcpu-1| Guest display topology changed: numDisplays 1

Aug 18 13:22:04.078: vcpu-0| Guest: vmx_fb: SVGADBG: ready

Aug 18 13:22:04.109: mks| MKS switching absolute mouse on

Aug 18 13:22:05.031: vmx| ToolsSetDisplayTopology: Sending rpcMsg = DisplayTopology_Set 2 , 0 0 1600 1200 , 1600 0 1600 1200

Aug 18 13:22:05.140: vcpu-1| TOOLS call to DisplayTopology_Set failed.

VMware Workstation will try and switch into multi monitor but is unsuccessful. Some additional information,

• Screens are side by side

• It attempts to switch into multi monitor mode. End up with a single screen in the center.

• Restarting the virtual machine fixes the problem (leading me to think that it's a problem with VMware Workstation commanding VMware Tools to change resolutions)

• No errors other than the log are reported by VMware Workstation (i.e. normally VMware Workstation returns an error if you don't have your multi mon configuration right)

• This is a very intermittent problem. Happens to me once every week or so.

• Normally occurs when taking my laptop that has a running VM out of standby by and resuming it in my docking Station. I then try and switch VMware Workstation to multi monitor.

• Other than re-docking, no configuration changes take place on the Host or the Guest between when it works and then doesn't

Appreciate any assistance on this one

Kind Regards,

Paul

[soaringeagle]

Here is some more information from the log files. The issue has happened a few times since. Updating the resolution as well. It isn't enough just to restart the VM. You need to shut the VM down and restart VMware workstation, then you are able to enter multi monitor again. Note that nothing changes with the restart. Same monitor resolutions, same way that I'm trying to put it into multi monitor mode. Note that this issue only happens when I'm coming out of standby on my laptop.

My suspicion on what is happening here is that for some reason VMware workstation isn't picking up the current host resolution after resuming from standby and it takes a restart of VMware workstation to correctly identify the host resolutions.

Sep 22 11:17:21.781: vmx| ToolsSetDisplayTopology: Sending rpcMsg = DisplayTopology_Set 2 , 0 0 1600 1200 , 1600 0 1600 1200

Sep 22 11:17:22.093: mks| MKS switching absolute mouse off

Sep 22 11:17:22.109: vcpu-1| Guest: vmx_fb: Expected failsafe mode after 1st negative mode rejection!

Sep 22 11:17:22.203: mks| SVGA: enabling escape command

Sep 22 11:17:22.203: vcpu-1| Guest display topology changed: numDisplays 1

Sep 22 11:17:22.203: vcpu-1| Guest: vmx_fb: SVGADBG: ready

Sep 22 11:17:22.203: vcpu-1| Guest: vmx_fb: This is the primary surface: PPDEV e4e22010

Sep 22 11:17:22.203: vcpu-1| Guest: vmx_fb: Display Acceleration: DirectDraw:ok, Direct3D:ok.

Sep 22 11:17:22.203: vcpu-1| Guest: vmx_fb: Current hardware revision: 2.0.

Sep 22 11:17:22.203: vcpu-1| Guest: vmx_fb: Driver compiled against: 2.0.

Sep 22 11:17:22.203: vcpu-1| Guest: vmx_fb: DrvGetDirectDrawInfo: Overlay flags set

Sep 22 11:17:22.203: vcpu-1| Guest: vmx_fb: This is the primary surface: PPDEV e4e22010

Sep 22 11:17:22.203: vcpu-1| Guest: vmx_fb: Display Acceleration: DirectDraw:ok, Direct3D:ok.

Sep 22 11:17:22.203: vcpu-1| Guest: vmx_fb: Current hardware revision: 2.0.

Sep 22 11:17:22.203: vcpu-1| Guest: vmx_fb: Driver compiled against: 2.0.

Sep 22 11:17:22.203: vcpu-1| Guest: vmx_fb: DrvGetDirectDrawInfo: Overlay flags set

Sep 22 11:17:22.234: vcpu-1| Guest: vmx_fb: rejecting mode with screen position: (1600, 0, 3200, 1200) bpp 32, 1ST TIME

Sep 22 11:17:22.234: vcpu-1| Guest: vmx_fb: rejecting fail safe mode after negative position or inconsistent bpp request.

Sep 22 11:17:22.234: vcpu-1| Guest: vmx_fb: rejecting mode with screen position: (1600, 0, 2240, 480) bpp 8, 1ST TIME