Upstream did a quick respin to close several regressions in 6.1.20:
I've also added the filechooser fix from opensuse:
(only for mga8, please test if it works)
kmods will be built after kernel update in:
is validated / pushed.
MGA 8 XFCE.
Update with QA repo and :
Launch VM ok no issues noticed.
use ok too
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.
Bug https://bugs.mageia.org/show_bug.cgi?id=27433 is fixed by the openSUSE patch.
Advisory, added to svn:
subject: Updated virtualbox packages fixes upstream regressions
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)
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.
I don't keep installs past the end of support so have not encountered the
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
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.
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.
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
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...
MGA7TOO, MGA8-64-OK, MGA7-64-OKCC:
An update for this issue has been pushed to the Mageia Updates repository.