I recently had to reinstall my Mageia 8. Although it was running quite happily, initramfs suddenly threw up an error message saying that a disk
it was trying to start, identified by UUID only, didn't exist, and
dropped me to a dracut shell. Since it was of no use looking for
something that wasn't there, and searching from a dracut shell produced
weird results (no /etc/fstab, although the boot procedure so far had
clearly found one), I stared again from scratch.
The fresh install went well, but now, I cannot start the VirtualBox
driver, no matter what I try. I gave up and decided to try KVM/QEMU.
The installation procedure from the Mageia wiki was O.K., but could be
made easier by an installer file. I am now at the stage of setting up
my "guest" distro.
Has anybody already done this? If not, could my experience help?
You did not specify what exactly the wrong happened with VirtualBox.
I recently had to reinstall my Mageia 8. Although it was running quite happily, initramfs suddenly threw up an error message saying that a disk
it was trying to start, identified by UUID only, didn't exist, and
dropped me to a dracut shell. Since it was of no use looking for
something that wasn't there, and searching from a dracut shell produced
weird results (no /etc/fstab, although the boot procedure so far had
clearly found one), I stared again from scratch.
The fresh install went well, but now, I cannot start the VirtualBox
driver, no matter what I try. I gave up and decided to try KVM/QEMU.
The installation procedure from the Mageia wiki was O.K., but could be
made easier by an installer file. I am now at the stage of setting up
my "guest" distro.
Has anybody already done this? If not, could my experience help?
On 11/12/22 03:55, Gilberto F da Silva wrote:
You did not specify what exactly the wrong happened with VirtualBox.
Sorry. VirtualBox failed to load the driver. This is the most common problem, and there is plenty of info on the Web about how to deal with
it. I tried a few:
* Uninstalling and reinstalling the RPM.
* Confirming that I had the dkms-virtualbox RPM installed (that fixed it last time.)
* Renaming the directory in ~/.config, forcing the creation of a new,
clean one.
* Most of the hints say to run vboxconfig, but it is no longer used. An alternative was given in one place, but didn't work.
Nothing worked, and everybody says that KVM is better, because it is
part of the Linux kernel, and shares resources. (Also, the girl in the
video is kinda cute and well-informed!)
Doug.
For the vb driver, you may have encountered https://bugs.mageia.org/show_bug.cgi?id=29830
in which case installing the dkms-virtualbox package should workaround the bug.
On 11/12/22 06:39, David W. Hodgins wrote:
For the vb driver, you may have encounteredI always add the dkms-virtualbox package. Virtualbox has now fixed
https://bugs.mageia.org/show_bug.cgi?id=29830
in which case installing the dkms-virtualbox package should workaround the >> bug.
itself, and starts normally. The only change to my system was to
install a swag of libraries recommended for Second Life. The list was
short, but the dependencies of the devel package were numerous.Maybe one
of those was missing for VB. Anyway, I will keep using VB and play
around with KVM.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 300 |
Nodes: | 16 (2 / 14) |
Uptime: | 37:19:45 |
Calls: | 6,707 |
Files: | 12,241 |
Messages: | 5,353,506 |