From: Hans de Goede <hdegoede@redhat.com>
To: Zack Rusin <zackr@vmware.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, 9 May 2022 12:57:07 +0200 [thread overview]
Message-ID: <087a0754-422c-0d88-a5ed-c03f2b5906c2@redhat.com> (raw)
In-Reply-To: <84c30eb2dcdc330ea54aa1fedba9ae0eb0826068.camel@vmware.com>
Hi Zack,
On 4/11/22 16:24, Zack Rusin wrote:
> 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&data=04%7C01%7Czackr%40vmware.com%7C3664ddfe25334b16109108da1b98a6af%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637852639719382480%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=GpkMy6OuPW06f%2Fzj%2FBGzoq8xT8pNsE6KtH0MTvN5FoA%3D&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.
I somewhat understand where you are coming from, but this is not
how the kernels "no regressions" policy works. For the end user
a regression is a regression and as maintainers we are supposed
to make sure any regressions noticed are fixed before a new
kernel hits end user's systems.
At a minimum it would have been good if you had tried to at least
reproduce this bug by installing Fedora rawhide inside an actual
vmware VM. I've just spend a couple of hours debugging this and
the bug definitely impacts vmware VMs too; and thus very likely
also reproduces there.
I've a patch fixing this, which I will send out right after this
email.
Regards,
Hans
next prev parent reply other threads:[~2022-05-09 10:57 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
2022-05-09 10:57 ` Hans de Goede [this message]
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=087a0754-422c-0d88-a5ed-c03f2b5906c2@redhat.com \
--to=hdegoede@redhat.com \
--cc=Linux-graphics-maintainer@vmware.com \
--cc=dri-devel@lists.freedesktop.org \
--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).