Description of problem: Getting a failed message during boot concerning legacy modules: Failed to start Load legacy module configuration. See 'systemctl status fedora-loadmodules.service' for details. Upon running the suggested command, I get the following output. root@localhost ~]# systemctl status fedora-loadmodules.service fedora-loadmodules.service - Load legacy module configuration Loaded: loaded (/usr/lib/systemd/system/fedora-loadmodules.service; static) Active: failed (Result: exit-code) since Thu, 2013-04-25 10:59:12 PDT; 5min ago Process: 533 ExecStart=/lib/systemd/fedora-loadmodules (code=exited, status=1/FAILURE) CGroup: name=systemd:/system/fedora-loadmodules.service Apr 25 10:59:12 localhost.localdomain systemd[1]: Starting Load legacy module configuration... Apr 25 10:59:12 localhost.localdomain fedora-loadmodules[533]: Loading modules: nvram evdev evdev vboxguest Apr 25 10:59:12 localhost.localdomain fedora-loadmodules[533]: modprobe: ERROR: could not insert 'vboxguest': No such device Apr 25 10:59:12 localhost.localdomain systemd[1]: fedora-loadmodules.service: main process exited, code=exited, status=1/FAILURE Apr 25 10:59:12 localhost.localdomain systemd[1]: Failed to start Load legacy module configuration. Apr 25 10:59:12 localhost.localdomain systemd[1]: Unit fedora-loadmodules.service entered failed state There appears to be an issue with the vboxguest module. I checked and the package virtualbox-guest-additions is installed. However, I'm running Mageia directly bare metal, and not in a virtual machine. I don't think there should be an error message for two reasons. First, the guest-additions are installed, and second I'm not running a virtual machine. This doesn't appear to impact the functionality of the system, but is a spurious error. With that said, not sure if this a systemd problem or a virtualbox problem. I'll see the severity to minor since it's not critical. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Reproducible: Steps to Reproduce:
CC: (none) => thierry.vignaudSource RPM: (none) => systemd
You shouldn't have guest additions installed on a host, those are for VMs. On a host machine you should have dkms-virtualbox or virtualbox-kernel installed.
Status: NEW => RESOLVEDResolution: (none) => INVALID
I agree the guest additions shouldn't be installed given that I'm running on bare metal. However, they are installed automatically from the live CD as I did not install any virtualbox packages myself. Are their presence causing the error message above? Should I remove them?
Well I confirmed the guest additions were the culprit. Removing them removed the error message. Now I need to figure out why they were installed in the first place since I never installed them myself.
CC: (none) => icaro842000