Windows Vista and Windows 7 topology changes might fail unexpectedly
Article ID: 324676
Updated On:
Products
VMware
Issue/Introduction
Symptoms:
When changing the topology of a Windows Vista or Windows 7 VM to large resolution or switching to multiple monitors with high resolution, the topology change may fail and the VM remains at the original resolution. In the vmware.log file, you see entries similar to:
When changing the topology of a Windows Vista or Windows 7 VM to large resolution or switching to multiple monitors with high resolution, the topology change may fail and the VM remains at the original resolution. In the vmware.log file, you see entries similar to:
2019-07-31T14:00:37.827-07:00| vcpu-0| I125: Guest: vm3d: Memory required for all screens exceeds maximum FB (required=160546816 max=134217728)
Cause
The WDDM graphics driver enforces that the requested topology will fit in guest graphics memory. An incorrect check is used when Aero is disabled in the guest.
When Aero is enabled, the topology check is correctly enforced - and prior topology changes that appeared to work (but resulted in Aero being disabled by Windows), no longer work.
When Aero is enabled, the topology check is correctly enforced - and prior topology changes that appeared to work (but resulted in Aero being disabled by Windows), no longer work.
Resolution
Currently, there is no resolution.
Workaround:
To work around this issue, set the following configuration option in the VM config file:
guestInfo.svga.wddm.topologyFBMemoryChecks = "FALSE"
If Aero is enabled, switch to a non-Aero theme before attempting a topology change with the above configuration option.
Workaround:
To work around this issue, set the following configuration option in the VM config file:
guestInfo.svga.wddm.topologyFBMemoryChecks = "FALSE"
If Aero is enabled, switch to a non-Aero theme before attempting a topology change with the above configuration option.
Feedback
Yes
No
Powered by
