On 10/7/24 16:39, Michael Tokarev wrote:
I upgraded again to 9.1.0+ds-8, changed the video setting from QXL to
Virtio and fired up Windows. I ran it for over half an hour with no
freeze up, so it's something to do with the QXL video display. Does
this give you any ideas?
Not yet.. but there are other reports about QXL not working correctly in
windows, lemme find one.. for example, this one:
https://gitlab.com/qemu-project/qemu/-/issues/1628 - which says
there's an
error decoding graphics stream in a way so windows and qemu becomes
out of
sync. Unfortunately it received no attention, I come across it just
today
while researching this your issue. The bug mentioned there seems real.
I'll take a look.
I pinged the Windows VM after the display froze (using Video QXL) and
it actually responds. I got the IP address from 'virsh domifaddr
Windows10', I assume that's the right one to ping.
Hopefully yes, and it's rather interesting that your windows VM has ping
enabled. So you probably can log in to it remotely using rdp, from, say
a freerdp client, after enabling remote desktop in windows. That would
be interesting.
OK, I'll try to set this up.
This is what I was trying to find out - is it whole windows kernel who
frozen, or qemu, or just display. With the above details it looks like
it is the display (and yes, I used qxl in my testing too, and it is the
most often used display anyway - it works fine). Maybe it also driver-
dependent, but qxl drivers hasn't updated for a few years (since 2020
iirc).
Or maybe I should use qxl with stdvga windows driver.
QXL worked fine until the 9.1.x upgrade.
So we're with the qxl thing here (hopefully anyway - I still do have some
doubts about it), which I can't reproduce. I'm not sure what to do here.
Either I need a way to reproduce it locally, or you have to learn how to
do some git, compiling and bisecting, and quite some time to experiment
since the prob doesn't happen in a deterministic way. The
compiling/bisecting
isn't difficult but it requires a (relatively minor) setup first.
I"d be happy to do this but I have some other obligations in the next
two weeks so my progress will be sporadic.
Or you can just switch to another vga type and be done with this :)
It's the principle of the thing...
If you'll choose to help debugging/bisecting, it's better to have some
online
chat - over IRC or in a messenger - than to use bugtracker. I'm mjt
on freenode
and mjt0k on libera, if you're about irc.
I've never done irc. I'm willing to figure it out but I wouldn't object
to a Google Chat, Facetime, WhatsApp or even a Zoom chat. Let me know
what works. And I do have some Debian packaging infrastructure in place,
I recently tooled up to maintain a very minor package. I'm no wizard but
I am very stubborn...
Hank
--
Hank Knox, FRSC
Schulich School of Music of
McGill University (retired)
Montreal, QC
