From: Diego Viola <1882851@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1882851] Re: QEMU video freezes with "Guest disabled display" (virtio driver)
Date: Fri, 12 Jun 2020 15:23:53 -0000 [thread overview]
Message-ID: <159197543361.7707.16090372527322896903.malone@gac.canonical.com> (raw)
In-Reply-To: 159174217343.32241.17743917589333297614.malonedeb@gac.canonical.com
Sway log after the crash.
** Attachment added: "swaylog.txt"
https://bugs.launchpad.net/qemu/+bug/1882851/+attachment/5383276/+files/swaylog.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1882851
Title:
QEMU video freezes with "Guest disabled display" (virtio driver)
Status in QEMU:
New
Bug description:
I am using Arch Linux as my Guest and Host OS, after starting qemu
with the following command:
$ qemu-system-x86_64 -enable-kvm -hda arch-zoom.qcow2 -m 4G -vga
virtio
and waiting for a screen blank, I get this message:
Guest disabled display
And nothing happens after that, I can move the mouse or hit any key,
and the message is still there.
I can still reboot the VM but that's not optimal.
I can reproduce this with the latest QEMU release (5.0.0) or git master,
I also tried this with older releases (4.0.0, 3.0.0) and the issue is still there.
I can't reproduce this with other video drivers (std, qxl).
With std/qxl the screen will blank a bit and then continue as normal.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1882851/+subscriptions
next prev parent reply other threads:[~2020-06-12 15:32 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 22:36 [Bug 1882851] [NEW] QEMU video freezes with "Guest disabled display" (virtio driver) Diego Viola
2020-06-09 23:20 ` [Bug 1882851] " Diego Viola
2020-06-09 23:24 ` Diego Viola
2020-06-10 0:02 ` Diego Viola
2020-06-10 17:55 ` Diego Viola
2020-06-11 8:27 ` Gerd Hoffmann
2020-06-11 10:24 ` Diego Viola
2020-06-11 10:28 ` Diego Viola
2020-06-11 19:40 ` Diego Viola
2020-06-11 22:33 ` Diego Viola
2020-06-12 5:40 ` Diego Viola
2020-06-12 5:41 ` Diego Viola
2020-06-12 6:10 ` Diego Viola
2020-06-12 15:15 ` Diego Viola
2020-06-12 15:23 ` Diego Viola [this message]
2020-06-12 17:26 ` Diego Viola
2020-06-12 17:44 ` Diego Viola
2020-07-15 16:16 ` Diego Viola
2020-09-14 6:45 ` Diego Viola
2020-09-15 10:26 ` Thomas Huth
2020-06-12 11:13 [PATCH] drm/virtio: fix unblank Gerd Hoffmann
2020-06-12 11:13 ` Gerd Hoffmann
2020-06-12 11:13 ` Gerd Hoffmann
2020-06-12 11:13 ` [Bug 1882851] " Gerd Hoffmann
2020-08-07 10:54 Gerd Hoffmann
2020-08-07 10:54 ` Gerd Hoffmann
2020-08-07 10:54 ` Gerd Hoffmann
2020-08-07 10:54 ` [Bug 1882851] " Gerd Hoffmann
2020-08-07 13:09 ` Daniel Vetter
2020-08-07 13:09 ` Daniel Vetter
2020-08-07 13:09 ` Daniel Vetter
2020-08-17 9:03 ` Gerd Hoffmann
2020-08-17 9:03 ` Gerd Hoffmann
2020-08-17 9:03 ` Gerd Hoffmann
2020-08-17 9:03 ` [Bug 1882851] " Gerd Hoffmann
2020-08-17 10:19 ` Gerd Hoffmann
2020-08-17 10:19 ` Gerd Hoffmann
2020-08-17 10:19 ` Gerd Hoffmann
2020-08-17 10:19 ` [Bug 1882851] " Gerd Hoffmann
2020-08-18 7:25 [PATCH 0/2] " Gerd Hoffmann
2020-08-18 7:25 ` [PATCH 1/2] " Gerd Hoffmann
2020-08-18 7:25 ` Gerd Hoffmann
2020-08-18 7:25 ` Gerd Hoffmann
2020-08-18 7:25 ` [Bug 1882851] " Gerd Hoffmann
2020-08-24 7:24 ` Jiri Slaby
2020-08-24 7:24 ` Jiri Slaby
2020-08-28 11:27 ` Gerd Hoffmann
2020-08-28 11:27 ` Gerd Hoffmann
2020-08-28 11:27 ` Gerd Hoffmann
2020-08-28 11:27 ` [Bug 1882851] " Gerd Hoffmann
2020-09-01 7:34 ` Daniel Vetter
2020-09-01 7:34 ` Daniel Vetter
2020-09-01 7:34 ` Daniel Vetter
2020-09-01 10:20 ` Daniel Vetter
2020-09-01 10:20 ` Daniel Vetter
2020-09-01 10:20 ` Daniel Vetter
2020-08-18 7:25 ` [PATCH 2/2] drm/virtio: drop virtio_gpu_output->enabled Gerd Hoffmann
2020-08-18 7:25 ` Gerd Hoffmann
2020-08-18 7:25 ` Gerd Hoffmann
2020-08-25 21:56 ` [PATCH] drm/virtio: fix unblank Diego Viola
2020-08-25 21:56 ` Diego Viola
2020-08-25 21:56 ` [Bug 1882851] " Diego Viola
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=159197543361.7707.16090372527322896903.malone@gac.canonical.com \
--to=1882851@bugs.launchpad.net \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.