All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 215317] New: Unable to launch QEMU Linux guest VM - "Guest has not initialized the display (yet)"
Date: Mon, 13 Dec 2021 01:38:39 +0000	[thread overview]
Message-ID: <bug-215317-28872@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=215317

            Bug ID: 215317
           Summary: Unable to launch QEMU Linux guest VM - "Guest has not
                    initialized the display (yet)"
           Product: Virtualization
           Version: unspecified
    Kernel Version: 5.16.0-rc4
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: kvm
          Assignee: virtualization_kvm@kernel-bugs.osdl.org
          Reporter: rherbert@sympatico.ca
        Regression: No

Something changed between kernel 5.16.0-rc3 and -rc4, and remains unfixed
between -rc4 and -rc5. Attempting to start a QEMU VM, the display is stuck at
"Guest has not initialized the display (yet)". The QEMU version I'm trying is
6.2.0-rc4, but QEMU version 6.1.0 has also been tried. I noticed many changes
in the KVM code between Linux 5.16.0-rc3 and 5.16.0-rc4, and I apologize for
not being able to narrow it down.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2021-12-13  1:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-13  1:38 bugzilla-daemon [this message]
2021-12-14  4:25 ` [Bug 215317] Unable to launch QEMU Linux guest VM - "Guest has not initialized the display (yet)" bugzilla-daemon
2021-12-14  9:10 ` [Bug 215317] New: " Thorsten Leemhuis
2021-12-14  9:10 ` [Bug 215317] " bugzilla-daemon
2021-12-14 16:30 ` bugzilla-daemon
2021-12-20  3:41 ` bugzilla-daemon
2021-12-20  5:32 ` bugzilla-daemon

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=bug-215317-28872@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=kvm@vger.kernel.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.