regressions.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: regressions@lists.linux.dev,
	VMware Graphics <linux-graphics-maintainer@vmware.com>,
	Zack Rusin <zackr@vmware.com>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>
Subject: 5.18 vmwgfx seems to break booting VirtualBox VMs
Date: Mon, 11 Apr 2022 10:52:42 +0200	[thread overview]
Message-ID: <2bd4b06e-7577-d7d7-5f2e-264005b316a1@redhat.com> (raw)

Hi All,

Fedora has received a bug report here:

https://bugzilla.redhat.com/show_bug.cgi?id=2072556

That Fedora rawhide VMs no longer boot under the VirtualBox hypervisor
after the VM has been updated to a 5.18-rc# kernel.

Switching the emulated GPU from vmwaregfx to VirtualBoxSVGA fixes
this, so this seems to be a vmwgfx driver regression.

Note I've not investigated/reproduced this myself due to -ENOTIME.

Regards,

Hans


             reply	other threads:[~2022-04-11  8:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-11  8:52 Hans de Goede [this message]
2022-04-11 14:24 ` 5.18 vmwgfx seems to break booting VirtualBox VMs Zack Rusin
2022-05-09 10:57   ` Hans de Goede
2022-05-10  0:12     ` Zack Rusin
2022-05-10 11:06       ` Thorsten Leemhuis
2022-05-10 12:26         ` Zack Rusin
2022-05-10 12:44           ` Thorsten Leemhuis
2022-05-10 13:30             ` Zack Rusin
2022-05-10 13:49               ` Thorsten Leemhuis
2022-05-10 13:57                 ` Zack Rusin
2022-05-10 15:34 ` 5.18 vmwgfx seems to break booting VirtualBox VMs #forregzbot Thorsten Leemhuis
2022-05-14  3:45   ` Thorsten Leemhuis

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=2bd4b06e-7577-d7d7-5f2e-264005b316a1@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-graphics-maintainer@vmware.com \
    --cc=regressions@lists.linux.dev \
    --cc=zackr@vmware.com \
    /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).