Reboot is no problem, machine reset will reset qxl too. With wayland allocating two buffers and flipping between them you'll probably see only every other frame. The 'create primary surface' also defines where the surface is located in video memory, so when skipping this page-flipping will not work correctly.

Try switching the video mode via xrandr with the patched kms driver, I suspect you'll get a dis-sorted display. > that implicitly and it can be dropped wholesale?)

> make sure qemu is given fresh state on fresh boots, but maybe qemu handles > 1) that destroying the primary is actually necessary at all (i assume so to > destroying the primary on non-initial setcrtc calls. > So the above patch attempts to fix the problem kernel side. > drm/qxl: only create primary on first SetCrtc call (In reply to Ray Strode from comment #14)

it looks like that previously that variable was left over cruft that hitched its way into the initial import, but would be good to make sure i'm not missing anything.ĥ) Also, I don't think there's any locking concerns for the qxl_device struct, but would be good to make sure. would that approach be better?Ĥ) i'm storing state on the 'primary_created' boolean in the qxl_device struct. Some things to double-check in review:ġ) that destroying the primary is actually necessary at all (i assume so to make sure qemu is given fresh state on fresh boots, but maybe qemu handles that implicitly and it can be dropped wholesale?)Ģ) that skipping the destroy is okay for subsequent calls (no security implications?)ģ) another alternative might be to save the cursor from the old primary and restore it in the new one. Needs review, since I don't know much about this code. It avoids destroying the primary on non-initial setcrtc calls. So the above patch attempts to fix the problem kernel side. Drm/qxl: only create primary on first SetCrtc call

Ubuntu virtualbox mouse disappears