See for details: https://github.com/virtio-win/kvm-guest-drivers-windows/pull/1474

Previously, when the requested resolution required more memory than the pre-allocated framebuffer segment, the driver would:

• Destroy the existing working framebuffer
• Fail to create the new larger framebuffer
• Leave the display inactive with no way to recover

Actual behavior:
Once the resolution reaches a certain threshold (exceeding framebuffer capacity), the screen goes black. Reducing the resolution does not restore the display. The only recovery method is to restart the viogpu driver.

Expected behavior:
The display should either maintain the current resolution or gracefully reject unsupported resolutions.