Vadim Rozenfeld
Vadim Rozenfeld
@bryantclcqq Honestly, I'm really surprised that spice comes with virtio-gpu drivers, and especially with ARM64 version signed with Microsoft Windows Third Party Component signature. I need to confirm with our...
@amezin currently 3840x1912x32bit is too big https://github.com/virtio-win/kvm-guest-drivers-windows/blob/master/viogpu/viogpudo/viogpudo.cpp#L2263 I'm going to fix this problem along with https://bugzilla.redhat.com/show_bug.cgi?id=1923886 btw, I wouldn't suggest using this repository https://gitlab.freedesktop.org/spice/win32/virtio-gpu-wddm-dod/ anymore. Windows virtio-gpu driver has been...
@jwatt Win10 currently (latest-build 204) works with up to 16MB (2KB x 2KB x 32bpp) surface. I still have a plan to make it bigger (up to 256 MB) but...
@amezin I will try too support the bigger resolutions soon.
@Lilith2208 currently we pre-allocate 16MB buffer on Win10 and 8MB on Win8/8.1 https://github.com/virtio-win/kvm-guest-drivers-windows/blob/master/viogpu/viogpudo/viogpudo.cpp#L2368 16MB should be enough to handle 2048x2048 resolution in 32bit per pixel mode. 2560x1600x4 requires even a...
@BentHaase Technically, it should be possible on Win10. 2560x1600x4 a git more than 14 MB while the memory, allocated to backup the frame buffer is 16MB.
@BentHaase you need to pass the following parameters to qemu "-device virtio-vga,edid=on,xres=2560,yres=1600" to make the new resolution to be recognisable by the guest/viogpudo driver  Alternatively, you...
@BentHaase It has to be "-device virtio-vga,edid=on,xres=2560,yres=1440" of course, but let me check if it works fine with the recent drivers.
@BentHaase, What kind of viewer do you use? The Windows virtio-gpu driver is not integrated with spice and vnc. And honestly, we don't have any technical requirements to address this...
Just for the record. Tested it again on QEMU with relatively recent driver. It works fine on my setup. We even don't need to enable EDID, just specify resolutions "-device...