regressions.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Zack Rusin <zackr@vmware.com>
To: "hdegoede@redhat.com" <hdegoede@redhat.com>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
	Linux-graphics-maintainer <Linux-graphics-maintainer@vmware.com>
Subject: Re: 5.18 vmwgfx seems to break booting VirtualBox VMs
Date: Mon, 11 Apr 2022 14:24:26 +0000	[thread overview]
Message-ID: <84c30eb2dcdc330ea54aa1fedba9ae0eb0826068.camel@vmware.com> (raw)
In-Reply-To: <2bd4b06e-7577-d7d7-5f2e-264005b316a1@redhat.com>

On Mon, 2022-04-11 at 10:52 +0200, Hans de Goede wrote:
> Hi All,
> 
> Fedora has received a bug report here:
> 
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugzilla.redhat.com%2Fshow_bug.cgi%3Fid%3D2072556&amp;data=04%7C01%7Czackr%40vmware.com%7C3664ddfe25334b16109108da1b98a6af%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637852639719382480%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=GpkMy6OuPW06f%2Fzj%2FBGzoq8xT8pNsE6KtH0MTvN5FoA%3D&amp;reserved=0
> 
> 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.

Thanks for letting us know. Unfortunately we do not support vmwgfx on
VirtualBox. I'd be happy to review patches related to this, but it's
very unlikely we'd have to time to look at this ourselves.

z


  reply	other threads:[~2022-04-11 14:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-11  8:52 5.18 vmwgfx seems to break booting VirtualBox VMs Hans de Goede
2022-04-11 14:24 ` Zack Rusin [this message]
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=84c30eb2dcdc330ea54aa1fedba9ae0eb0826068.camel@vmware.com \
    --to=zackr@vmware.com \
    --cc=Linux-graphics-maintainer@vmware.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hdegoede@redhat.com \
    --cc=regressions@lists.linux.dev \
    /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).