Description of problem: Within the past week, all three of my Cauldron VirtualBoxes (XFCE, MATE, LXDE) began to not shutdown or reboot. I have one Mageia 8 VirtualBox (LXDE) where shutdown/reboot is successful. Mageia 8 is the host OS with VirtualBox 6.1.38 installed. All of the VirtualBoxes have virtualbox-guest-additions installed. With the Cauldron VBoxes, the desktop logs me out and eventually displays the blue Mageia splash screen and it ends there. I have to go to the individual VirtualBox File menu, click Close, then turn off the machine, in order to fully exit them. Source RPM is enpty, since I do not know which package is causing this, but as stated, this behavior began within the past week.
Thank you for this report. To summarise: Host: Mageia 8 with VirtualBox 6.1.38 installed Cauldron guests (with VB additions): the problem reported *** Mageia 8 guest: OK, a useful 'control'.
Assignee: bugsquad => kernelSource RPM: (none) => virtualboxSummary: Cauldron VirtualBoxes not shutting down or rebooting => Cauldron VirtualBoxes (guests) not shutting down or rebooting
My Mageia 8 install just received VirtualBox 6.1.40. The output indicated that certain modules were not found on the currently-installed kernel (5.15.74). Should these modules be installing every time the kernel is updated? If this is to occur automatically, it doesn't appear to be happening. I did not see any of this from urpmi when the kernel updated to 5.15.74. -------- Uninstall Beginning -------- Module: virtualbox Version: 6.1.38-1.2.mga8 Kernel: 5.15.74-desktop-1.mga8 (x86_64) ------------------------------------- Status: Before uninstall, this module version was ACTIVE on this kernel. vboxdrv.ko.xz: - Uninstallation - Deleting from: /lib/modules/5.15.74-desktop-1.mga8/dkms-binary/3rdparty/vbox/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. vboxnetflt.ko.xz: - Uninstallation - Deleting from: /lib/modules/5.15.74-desktop-1.mga8/dkms-binary/3rdparty/vbox/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. vboxnetadp.ko.xz: - Uninstallation - Deleting from: /lib/modules/5.15.74-desktop-1.mga8/dkms-binary/3rdparty/vbox/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. depmod........... DKMS: uninstall Completed. 2/4: removing virtualbox-kernel-5.15.74-desktop-1.mga8-6.1.38-1.6.mga8.x86_64 ########################################################################### 3/4: removing virtualbox-kernel-desktop-latest-6.1.38-1.6.mga8.x86_64 ########################################################################### 4/4: removing virtualbox-guest-additions-6.1.38-1.2.mga8.x86_64 ########################################################################### vboxdrv.ko.xz: - Installation - Installing to /lib/modules/5.15.74-desktop-1.mga8/dkms-binary/3rdparty/vbox/ vboxnetflt.ko.xz: - Installation - Installing to /lib/modules/5.15.74-desktop-1.mga8/dkms-binary/3rdparty/vbox/ vboxnetadp.ko.xz: - Installation - Installing to /lib/modules/5.15.74-desktop-1.mga8/dkms-binary/3rdparty/vbox/ depmod...... DKMS: install Completed. virtualbox, 6.1.40-1.mga8, 5.15.74-desktop-1.mga8, x86_64: installed-binary from 5.15.74-desktop-1.mga8 + /usr/sbin/rmmod vboxnetflt + /usr/sbin/rmmod vboxnetadp + /usr/sbin/rmmod vboxdrv + /usr/sbin/modprobe vboxdrv + /usr/sbin/modprobe vboxnetflt + /usr/sbin/modprobe vboxnetadp + :
After this update, the three Cauldron VirtualBoxes are still not shutting down or restarting. They still hang at the blue Mageia splash screen.
Try hitting ESC to the splash screen and see how far the console messages get. You should at least get to "Reached target reboot/shutdown" and that should eventually be followed by a message about "waiting on (something)". I see this a lot on real hardware with the Plasma DE, and usually what it's waiting on is something called osspd (if I've remembered that correctly). It will eventually complete after several minutes, but being an impatient sort I usually resort to ALT-SysRQ-E to kill it and complete the reboot.
CC: (none) => ftg
(In reply to Frank Griffin from comment #4) > Try hitting ESC to the splash screen and see how far the console messages > get. You should at least get to "Reached target reboot/shutdown" and that > should eventually be followed by a message about "waiting on (something)". > > I see this a lot on real hardware with the Plasma DE, and usually what it's > waiting on is something called osspd (if I've remembered that correctly). > It will eventually complete after several minutes, but being an impatient > sort I usually resort to ALT-SysRQ-E to kill it and complete the reboot. In the LXDE VirtualBox, it displayed: [OK] Stopped CUPS Scheduler [OK] Stopped Shorewall IPv4 firewall [OK] Stopped target Network is Online [OK] Statted Show Plymouth Reboot Screen\ [(red bar)] A stop job is running for Session c1 of user epp (1 min 29 sec / 1 min 30 sec) Then, messages appeared quite fast scrolling down the screen, then it rebooted.