From: Timo Lindfors <timo.lindfors@iki.fi>
To: Salvatore Bonaccorso <carnil@debian.org>
Cc: Matt Marjanovic <maddog@mir.com>,
1054514@bugs.debian.org, Maxime Ripard <mripard@kernel.org>,
Alex Constantino <dreaming.about.electric.sheep@gmail.com>,
airlied@redhat.com, daniel@ffwll.ch,
dri-devel@lists.freedesktop.org, kraxel@redhat.com,
linux-kernel@vger.kernel.org, maarten.lankhorst@linux.intel.com,
regressions@lists.linux.dev, spice-devel@lists.freedesktop.org,
timo.lindfors@iki.fi, tzimmermann@suse.de,
virtualization@lists.linux-foundation.org
Subject: Re: Bug#1054514: linux-image-6.1.0-13-amd64: Debian VM with qxl graphics freezes frequently
Date: Wed, 10 Dec 2025 14:36:23 +0200 (EET) [thread overview]
Message-ID: <alpine.DEB.2.20.2512101433240.24105@mail.home> (raw)
In-Reply-To: <aTiTnENWsCoTbT3U@eldamar.lan>
On Tue, 9 Dec 2025, Salvatore Bonaccorso wrote:
>> This is back in trixie --- unsurprisingly, because the kernel commit which
Indeed. The reverst of the problematic commit was reverted in mainline
kernel. I have spent several days trying to understand the problem but
unfortunately I don't have enough time to troubleshoot this more.
I tried switching to virtio but for my use case of remote Linux desktops
it is not usable. If I scroll a fullscreen web page I can see how the
whole screen is redrawn every time,
Meanwhile I've switched from SPICE to RDP. GNOME in trixie supports
headless RDP sessions that make this very convenient. Client support is
also much better for RDP. I solved the authentication problem by isolating
each VM from each other on network level and then deployed rdpgw
(https://github.com/bolkedebruin/rdpgw) in front of everything with OpenID
authentication.
-Timo
next prev parent reply other threads:[~2025-12-11 1:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.2.20.2310242308150.28457@mail.home>
2023-10-24 21:09 ` Bug#1054514: linux-image-6.1.0-13-amd64: Debian VM with qxl graphics freezes frequently Salvatore Bonaccorso
2023-10-24 21:39 ` Timo Lindfors
2023-12-06 9:56 ` Linux regression tracking (Thorsten Leemhuis)
2024-03-08 1:08 ` [PATCH 0/1] drm/qxl: fixes qxl_fence_wait Alex Constantino
2024-03-08 1:08 ` [PATCH 1/1] " Alex Constantino
2024-03-08 8:58 ` Thorsten Leemhuis
2024-03-20 15:25 ` Linux regression tracking (Thorsten Leemhuis)
2024-03-27 13:27 ` Maxime Ripard
2024-04-04 18:14 ` [PATCH v2 0/1] Revert "drm/qxl: simplify qxl_fence_wait" Alex Constantino
2024-04-04 18:14 ` [PATCH v2 1/1] " Alex Constantino
2024-04-05 4:37 ` Greg KH
2024-04-05 13:13 ` (subset) " Maxime Ripard
2023-10-24 23:55 ` Bug#1054514: linux-image-6.1.0-13-amd64: Debian VM with qxl graphics freezes frequently Bagas Sanjaya
[not found] ` <b8b1497f-789e-4bb7-be17-9d3ebb30c143@mir.com>
2025-12-09 21:24 ` Salvatore Bonaccorso
2025-12-10 12:36 ` Timo Lindfors [this message]
2025-12-10 2:06 Avraham Hollander
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.20.2512101433240.24105@mail.home \
--to=timo.lindfors@iki.fi \
--cc=1054514@bugs.debian.org \
--cc=airlied@redhat.com \
--cc=carnil@debian.org \
--cc=daniel@ffwll.ch \
--cc=dreaming.about.electric.sheep@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kraxel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=maddog@mir.com \
--cc=mripard@kernel.org \
--cc=regressions@lists.linux.dev \
--cc=spice-devel@lists.freedesktop.org \
--cc=tzimmermann@suse.de \
--cc=virtualization@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).