Description of problem: I hadn't time to verify more but seems that update VirtualBox-6.1.18 host breaks vboxvideo [1] my test [2] [1] https://bugzilla.rpmfusion.org/show_bug.cgi?id=5904 [2] [ 13.787882] QSGRenderThread[1049]: segfault at 0 ip 0000000000000000 sp 00007f10dbffea58 error 14 in sddm-greeter[55c882fec000+14000] [ 13.787890] Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
So I just ran the following test: -Host: Fedora 33, kernel 5.10.9, VirtualBox 6.1.16 (from rpmfusion) -Guest: Fedora 32, kernel 5.10.6, virtualbox-guest-addtions-6.1.18 from Fedora package, using vboxvideo as VGA card And everything works fine. Judging by: https://bugzilla.rpmfusion.org/show_bug.cgi?id=5904 which is complaining about a CentOS 8 guest crashing under a 6.1.18 VirtualBox host. And judging by the latest comments here: https://www.virtualbox.org/ticket/20055 It just seems to me that the 6.1.18 release is busted as a host, at least when running on top of a 5.10 kernel. Given that the 6.1.16 release from rpmfusion does work I assume that VirtualBox upstream made some mistake when fixing 5.10 support, where as the community provided 5.10 fixes which you added to the 6.1.16 rpmfusion pkg (I assume) do wotk fine with 5.10 . So you may want to look at the patches which you added to 6.1.16 to get it to work with the 5.10 kernel and see if any of them are missing or were applied wrongly by virtualbox upstream. Note I've not tried upgrading VirtualBox on the host side myself yet, due to lack of time for further testing, sorry.
VirtualBox 6.1.18 is in update-testing of rpmfusion
Hi, (In reply to Sergio Basto from comment #2) > VirtualBox 6.1.18 is in update-testing of rpmfusion I know, that doesn't change the fact that: a) My testing shows that guests with vboxvideo + a 5.10.x kernel + latest vboxguest-additions work fine with a 6.1.16 host on a 5.10.x kernel. Note I also tested with older guest additions. b) The reporter of the rpmfusion bug is seeing host crashes with a Centos guest; and 1. The host must never crash by something done in the VM; 2. So this is happening with different guests with much older kernels. IOW this seems to not be guest related at all. c) The reporter of the rpmfusion bug says that this also reproduces when running the 5.8 kernel on the host. So this also seems to be unrelated to the host kernel version (or at least it is not 5.10 specific). Tl;DR: with 6.1.16 everything works fine, with a 6.1.18 host multiple users are seeing crashes independent of the guest and independent of the host kernel version. Conclusion: upstream has foo-barred the 6.1.18 release. I really don't have time to investigate this further. vbox upstream broke this, vbox upstream should fix it. In the mean time I strongly suggest that you drop the 6.1.18 release from rpmfusion updates-testing. Regards, Hans
(In reply to Hans de Goede from comment #3) > Hi, > > (In reply to Sergio Basto from comment #2) > > VirtualBox 6.1.18 is in update-testing of rpmfusion > > I know, that doesn't change the fact that: > > a) My testing shows that guests with vboxvideo + a 5.10.x kernel + latest > vboxguest-additions work fine with a 6.1.16 host on a 5.10.x kernel. Note I > also tested with older guest additions. > > b) The reporter of the rpmfusion bug is seeing host crashes with a Centos > guest; and 1. The host must never crash by something done in the VM; 2. So > this is happening with different guests with much older kernels. IOW this > seems to not be guest related at all. > > c) The reporter of the rpmfusion bug says that this also reproduces when > running the 5.8 kernel on the host. So this also seems to be unrelated to > the host kernel version (or at least it is not 5.10 specific). > > Tl;DR: with 6.1.16 everything works fine, with a 6.1.18 host multiple users > are seeing crashes independent of the guest and independent of the host > kernel version. Conclusion: upstream has foo-barred the 6.1.18 release. > > I really don't have time to investigate this further. vbox upstream broke > this, vbox upstream should fix it. In the mean time I strongly suggest that > you drop the 6.1.18 release from rpmfusion updates-testing. OK , I understand , I just though in warning you ASAP.
well after downgrade virtualbox host and virtualbox to 6.1.16 , kernel host and kernel guest to 5.9 , still the same error , sddm crash on vm when 3D graphics are enabled . While gnome works well ... , so I deduce is a kde problem under VirtualBox , I don't know
(In reply to Sergio Basto from comment #5) > well after downgrade virtualbox host and virtualbox to 6.1.16 , kernel host > and kernel guest to 5.9 , still the same error , sddm crash on vm when 3D > graphics are enabled . > While gnome works well ... , so I deduce is a kde problem under VirtualBox , > I don't know I'm not sure what you mean with "when 3D graphics are enabled", is this a sddm setting or a virtualbox setting you are talking about? Can you provide some step by step instructions for creating a vm which reproducing this crash?
Hi, My VirtualBox host is version 6.1.16( or 18)_RPMFusion on Fedora 32 KDE without updates-testing , my vm guest have Fedora 33 KDE with updates-testing and with virtualbox-guest-additions from Fedora, all updated and without kwayland packages [1] "when 3D graphics are enabled" means, before boot vm, in settings -> display -> checkbox, enable 3D Acceleration, enabled . ATM when I'm writing this, disable 3D Acceleration , fix all problems and today I saw this thread https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org/thread/WHSMJXSM47UYC5PLYUV6UQ6NJSIQ22ZM/ , so more complains pointing to KDE ... Best regards, [1] dnf remove kwin-wayland kwayland-integration plasma-workspace-wayland plasma-wayland-protocols
another tip https://www.virtualbox.org/ticket/20163 kernel 5.10.11 panic at VM start, when CONFIG_DEBUG_SPINLOCK=y in kernel .config
> "when 3D graphics are enabled" means, before boot vm, in settings -> display -> checkbox, enable 3D Acceleration, enabled . Which virtual GPU is the VM configured to use ? The VMware vmwgfx GPU, or the VboxSVGA GPU ?
VMSVGA (VMware vmwgfx GPU) , now, we don't have any other option , the other options are marked was not optimal and they are reset on press OK. Anyway, I don't have any new reports, i.e. a few guys started fill reports everywhere, as something big happened but nothing happened , just KDE rendering was broke at same time , I guess .
I wonder if the fix https://www.virtualbox.org/ticket/19884 does not broke other things , I don't remember 3D problems for many times https://bugzilla.rpmfusion.org/show_bug.cgi?id=5857 https://bugzilla.rpmfusion.org/show_bug.cgi?id=5904 https://bugzilla.redhat.com/show_bug.cgi?id=1921523
the commit of this fix are (at least): https://github.com/sergiomb2/VirtualBox/commit/d454d87bc085f7612cdd11b1c641d20b862d8004 and https://github.com/sergiomb2/VirtualBox/commit/16bc7b276435b19cfabed71a2a0832b1f2fa0c81
I tried revert 3 patches related but no luck wget https://github.com/sergiomb2/VirtualBox/commit/af5924437a99519c53dea456cc13d2729769da7a.patch cat ../af5924437a99519c53dea456cc13d2729769da7a.patch | patch -p2 -R cat ../16bc7b276435b19cfabed71a2a0832b1f2fa0c81.patch | patch -p2 -R cat ../d454d87bc085f7612cdd11b1c641d20b862d8004.patch | patch -p2 -R
https://bugzilla.redhat.com/show_bug.cgi?id=1921523#c7 seems it is Mesa-20.3.x , my test also give the same result. Maybe we may close this bug and sorry for the noise ...
Thank you for figuring out that this is a mesa issue. And lets close this bug then.