Vadim Rozenfeld

@elderlabs Thank you for reporting the issue. Can you please tell what kind of tools did you use to discovery the memory leakage in viostor driver? Is it related to...

@vinod-melarkode Thank you for reporting the issue. Is there any way you can share the crash dump file? Best, Vadim.

@vinod-melarkode Please ping me on my work email [email protected] Best, Vadim.

@w123456w30w it's Intel [vrozenfe@virtowin qemu]$ lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order: Little Endian CPU(s): 40 On-line CPU(s) list: 0-39...

The latest virtio-gpu dod drive should be able to support resolutions in range from 800X600 up to 5120x2160  It will be included in the next virtio-win...

Yeah, that limit was mostly coming from the maximum frame buffer size allocated by driver. I can put attestation signed driver on my public share directory. Just let me know...

https://people.redhat.com/vrozenfe/viogpu247.zip Not fully tested yet. Use it on your own risk. It should work on Windows Server. (Actually WDDM Display Only Driver designed to run on the server platforms rather...

go to "Start"->"Device Manager"->"Display Adaptors" you should see in-box "Microsoft Basic Display Adaptor" driver installed by default. Right click on it and chose "Update Driver" the pop-up menu. Then click...

OK, then you can try updating this driver taking the same steps as described before. Or uninstall device including driver. Then go to "Action" -> "Scan for hardware changes" an...

Technically your issue the same as https://github.com/virtio-win/kvm-guest-drivers-windows/issues/560 So one of them should be closed :) Cheers, Vadim