Bug 28867 - Update request: virtualbox-6.1.22
Summary: Update request: virtualbox-6.1.22
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: MGA7TOO, MGA8-64-OK, MGA7-64-OK
Keywords: advisory, validated_update
Depends on: 28856
Blocks: 27433
  Show dependency treegraph
 
Reported: 2021-05-01 21:46 CEST by Thomas Backlund
Modified: 2021-05-05 18:17 CEST (History)
5 users (show)

See Also:
Source RPM: virtualbox
CVE:
Status comment:


Attachments

Description Thomas Backlund 2021-05-01 21:46:59 CEST
Upstream did a quick respin to close several regressions in 6.1.20:
https://www.virtualbox.org/wiki/Changelog-6.1#v22

I've also added the filechooser fix from opensuse:
https://bugs.mageia.org/show_bug.cgi?id=27433#c29
(only for mga8, please test if it works)


Mga8 rpms:
SRPMS:
virtualbox-6.1.22-1.mga8.src.rpm

i586:
virtualbox-6.1.22-1.mga8.i586.rpm
virtualbox-guest-additions-6.1.22-1.mga8.i586.rpm

x86_64:
dkms-virtualbox-6.1.22-1.mga8.x86_64.rpm
python-virtualbox-6.1.22-1.mga8.x86_64.rpm
virtualbox-6.1.22-1.mga8.x86_64.rpm
virtualbox-devel-6.1.22-1.mga8.x86_64.rpm
virtualbox-guest-additions-6.1.22-1.mga8.x86_64.rpm


Mga7 rpms:
SRPMS:
virtualbox-6.1.22-1.mga7.src.rpm

i586:
virtualbox-6.1.22-1.mga7.i586.rpm
virtualbox-guest-additions-6.1.22-1.mga7.i586.rpm

x86_64:
dkms-virtualbox-6.1.22-1.mga7.x86_64.rpm
python-virtualbox-6.1.22-1.mga7.x86_64.rpm
virtualbox-6.1.22-1.mga7.x86_64.rpm
virtualbox-devel-6.1.22-1.mga7.x86_64.rpm
virtualbox-guest-additions-6.1.22-1.mga7.x86_64.rpm



kmods will be built after kernel update in:
https://bugs.mageia.org/show_bug.cgi?id=28856

is validated / pushed.
Thomas Backlund 2021-05-01 21:48:00 CEST

Whiteboard: (none) => MGA7TOO
Blocks: (none) => 27433
Depends on: (none) => 28856

Comment 1 Guillaume Royer 2021-05-02 15:00:56 CEST
MGA 8 XFCE.

Update with QA repo and :

dkms-virtualbox-6.1.22-1.mga8.x86_64.rpm
python-virtualbox-6.1.22-1.mga8.x86_64.rpm
virtualbox-6.1.22-1.mga8.x86_64.rpm
virtualbox-devel-6.1.22-1.mga8.x86_64.rpm
virtualbox-guest-additions-6.1.22-1.mga8.x86_64.rpm

Launch VM ok no issues noticed.
use ok too

CC: (none) => guillaume.royer

Comment 2 Aurelien Oudelet 2021-05-02 18:46:29 CEST
MGA8 host on a x86_64 Intel Core i5 6600K, 16 GB DDR4-Ram

VM Linux OK, good drivers, opengl desktop OK.

VM Windows 10 seems to start.
On host journal:
mai 02 18:21:59 mageia.local kernel: SUPR0GipMap: fGetGipCpu=0x1b
mai 02 18:21:59 mageia.local kernel: vboxdrv: 000000001c17f92d VMMR0.r0
mai 02 18:21:59 mageia.local kernel: vboxdrv: 00000000bad91c75 VBoxDDR0.r0
mai 02 18:21:59 mageia.local kernel: VMMR0InitVM: eflags=246 fKernelFeatures=0x0 (SUPKERNELFEATURES_SMAP=0)

It does not seem to reboot by itself for a while. Note: No VirtualBox Client drivers installed... Only those provided by Microsoft...

Updating Windows 10 20H2 in the VM. Leaving this.


Note:
Bug https://bugs.mageia.org/show_bug.cgi?id=27433 is fixed by the openSUSE patch.

CC: (none) => ouaurelien

Comment 3 Thomas Backlund 2021-05-02 19:17:05 CEST
Mga8 kmods:

SRPM:
kmod-virtualbox-6.1.22-1.mga8.src.rpm

x86_64:
virtualbox-kernel-5.10.33-desktop-1.mga8-6.1.22-1.mga8.x86_64.rpm
virtualbox-kernel-5.10.33-server-1.mga8-6.1.22-1.mga8.x86_64.rpm
virtualbox-kernel-desktop-latest-6.1.22-1.mga8.x86_64.rpm
virtualbox-kernel-server-latest-6.1.22-1.mga8.x86_64.rpm


Mga7 kmods:

SRPM:
kmod-virtualbox-6.1.22-1.mga7.src.rpm

x86_64:
virtualbox-kernel-5.10.33-desktop-1.mga7-6.1.22-1.mga7.x86_64.rpm
virtualbox-kernel-5.10.33-server-1.mga7-6.1.22-1.mga7.x86_64.rpm
virtualbox-kernel-desktop-latest-6.1.22-1.mga7.x86_64.rpm
virtualbox-kernel-server-latest-6.1.22-1.mga7.x86_64.rpm
Comment 4 Thomas Backlund 2021-05-02 19:30:57 CEST
Advisory, added to svn:

type: bugfix
subject: Updated virtualbox packages fixes upstream regressions
src:
  8:
   core:
     - virtualbox-6.1.22-1.mga8
     - kmod-virtualbox-6.1.22-1.mga8
  7:
   core:
     - virtualbox-6.1.22-1.mga7
     - kmod-virtualbox-6.1.22-1.mga7
description: |
  This update provides the upstream 6.1.22 maintenance release that adds
  fixes for stability and various regressions. See the referenced changelog
  for more details about the fixes.
  
  This update also adds a better fix for the non-working file selection
  dialog with Plasma (Mageia 8 only, mga#27433)
references:
 - https://bugs.mageia.org/show_bug.cgi?id=28867
 - https://bugs.mageia.org/show_bug.cgi?id=27433
 - https://www.virtualbox.org/wiki/Changelog-6.1#v22

Keywords: (none) => advisory

Comment 5 Giuseppe Ghibò 2021-05-04 13:58:00 CEST
Anyone got problems with older created virtual machine in 6.1.22? E.g. I had a VM guest of mageia6 that boot perfectly in 6.1.18, but no longer in 6.1.20 and 6.1.22.

CC: (none) => ghibomgx

Comment 6 Dave Hodgins 2021-05-05 09:24:50 CEST
I don't keep installs past the end of support so have not encountered the
problem.

The most likely problem I can think of is that the virtualbox guest additions
installed in the guest are not compatible with the host's version of
VirtualBox.

Try booting a Mageia 8 live iso in that guest, mount the guest's hard drives
and use systemd-nspawn to get access to the guest. Then use rpm to
uninstall the guest additions. It will remove some functionality but may
make it bootable again.

See "man systemd-nspawn" if you're not familiar with it's use.

CC: (none) => davidwhodgins

Comment 7 Giuseppe Ghibò 2021-05-05 11:22:32 CEST
Well, usually the role of an emulator is to allow possibly to run ancient software also. In this case the problem is not a mageia6 itself, but the fact that when there are this kind of problems from two subsequents release of the emulator, usually something deeper or hidden in the emulator might occur (maybe it's an upstream emulation problem at CPU level or there are further regressions). And mageia6 it's just triggering it. So better to keep the "radar on". Of course downgrading to vbox 6.1.18 indeed fixes the problems. Also doesn't occur using mageia8 as guest. What is particular is that the problem doesn't occur at a cold boot, i.e. you run mageia6 as the first thing inside virtuabox, it works. It triggers while for instance you ran a VM guest with mageia8 first and then mageia6 later. Also doesn't seems a problem of the guest additions or at desktop level, but much before, at VM kernel probing, a couple of seconds after the boot, the boot stops after: 

[drm] initialized vboxvideo 1.0.0 20130823 for 0000:00:02.0 on minor 0
cryptd: max_cpu_len set to 1000
AVX2 version of gcm_enc/dec engaged
AES CTR mode by8 optimization level enabled

and then the whole machine is hanged. You can't even power down the guest machine, but have to kill the corresponding virtualbox processes manually.
It also happens either choosing VBOXVGA (inheirted from the older machine) as well as newer SVGA as driver video.
Comment 8 Giuseppe Ghibò 2021-05-05 12:17:28 CEST
Hmmm, I just found that playing with the menu System/Acceleration/Paravirtualization Interface, corresponding to the entry: <Paravirt provider="..."> in the .vbox config file, would let sometimes mageia6 VM boot; here is the result with the various entries:

None -> hangs
Default -> hangs
Legacy -> sometimes works or sometimes hangs
Minimal -> hangs
Hyper-V -> sometimes works or sometimes hangs
KVM -> sometimes works or sometimes hangs
Comment 9 Thomas Backlund 2021-05-05 14:40:30 CEST
ok,
as it's not a regression in 6.1.22 compared to the 6.1.20 update we already released... I will go ahead and validate this one



Please open a separate bugreport to track the regression and potential fixes, but do realize that in that mga6 guest you either need matching guest additions installed (or none at all) before upstream will probably even consider debugging it...
Thomas Backlund 2021-05-05 17:15:18 CEST

Keywords: (none) => validated_update
Whiteboard: MGA7TOO => MGA7TOO, MGA8-64-OK, MGA7-64-OK
CC: (none) => sysadmin-bugs

Comment 10 Mageia Robot 2021-05-05 18:17:18 CEST
An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2021-0105.html

Resolution: (none) => FIXED
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.