Failed to start Load Kernel Modules

[ghost]

Qubes OS version (e.g., R3.2):

R3.2

Affected TemplateVMs (e.g., fedora-23, if applicable):

---

Expected behavior:

System should start without giving any errors.

Actual behavior:

The system works fine but every time i start it i get the following error since i installed it fot the first time: "Failed to start Load Kernel Modules".

Steps to reproduce the behavior:

Simply start the system.

General notes:

$ systemctl status systemd-modules-load -l
  ● systemd-modules-load.service - Load Kernel Modules
  Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static; vendor preset: disabled)
  Active: failed (Result: exit-code) since dom 2017-02-12 02:35:48 CET; 30min ago
  Docs: man:systemd-modules-load.service(8)
  man:modules-load.d(5)
  Process: 1098 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)
  Main PID: 1098 (code=exited, status=1/FAILURE)

  feb 12 02:35:47 dom0 systemd-modules-load[1098]: Module 'xen_evtchn' is builtin
  feb 12 02:35:47 dom0 systemd-modules-load[1098]: Module 'xen_gntdev' is builtin
  feb 12 02:35:47 dom0 systemd-modules-load[1098]: Module 'xen_gntalloc' is builtin
  feb 12 02:35:48 dom0 systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
  feb 12 02:35:48 dom0 systemd[1]: Failed to start Load Kernel Modules.
  feb 12 02:35:48 dom0 systemd[1]: systemd-modules-load.service: Unit entered failed state.
  feb 12 02:35:48 dom0 systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.

---

Related issues:

[DimSKho]

I actually encountered the same issue issue as it looks like took place previously.

It was an attempt to run Qubes 3.2 in a VM using vmWare Workstation pro, once installed and rebooted, i barely had enough time to take this SS.

The VM seems to be configured according to the requirements.

Please let me know what im doing wrong or how it would be possible to resolve the issue?

[DimSKho]

I actually encountered the same issue issue as it looks like took place previously.

It was an attempt to run Qubes 3.2 in a VM using vmWare Workstation pro, once installed and rebooted, i barely had enough time to take this SS.

The VM seems to be configured according to the requirements.

Please let me know what im doing wrong or how it would be possible to resolve the issue?

[andrewdavidwong]

@DimSKho: Please note that Qubes is not intended to run in a VM under another hypervisor. Of course, if you can get it to work, or if someone can provide the information you need, that's great! I just wouldn't want you to be under the impression that it's "supposed" to work.

[andrewdavidwong]

@DimSKho: Please note that Qubes is not intended to run in a VM under another hypervisor. Of course, if you can get it to work, or if someone can provide the information you need, that's great! I just wouldn't want you to be under the impression that it's "supposed" to work.

[aidecoe]

I've hit the same issue on first boot of freshly installed QubesOS 3.2 on a real hardware.

[aidecoe]

I've hit the same issue on first boot of freshly installed QubesOS 3.2 on a real hardware.

[Malumake]

Same issue, fresh install QubesOS 3.2 on HP Proliant DL380 Gen9 .

[Malumake]

Same issue, fresh install QubesOS 3.2 on HP Proliant DL380 Gen9 .

[alpharou]

same issue here in 3.2, it seems PC independent.

[alpharou]

same issue here in 3.2, it seems PC independent.

[sporkmonger]

Same issue in 3.2 on Dell 7520.

[sporkmonger]

Same issue in 3.2 on Dell 7520.

[danieleiba]

Same issue on MacBook Air

[danieleiba]

Same issue on MacBook Air

[jupiter126]

Same issue on 4.0rc2 on asus z10pe d16ws

[jupiter126]

Same issue on 4.0rc2 on asus z10pe d16ws

[mannp]

Same issue on macbook air 5,2 with all testing updated applied after v4rc3

[mannp]

Same issue on macbook air 5,2 with all testing updated applied after v4rc3

[unman]

@andrewdavidwong This has been an issue for some time, and it's been reported on mailing lists also.
But it is, I think, spurious. Whenever I have looked at the logs (as instructed) I see the modules-load service active since boot time, with the process exiting SUCCESS. I'll warrant that the same applies in every report here.
@danieleiba @jupiter126 @mannp - Can you please check the service status and view the process outcome?

I suggest that we close this with an entry in the FAQ

[unman]

@andrewdavidwong This has been an issue for some time, and it's been reported on mailing lists also.
But it is, I think, spurious. Whenever I have looked at the logs (as instructed) I see the modules-load service active since boot time, with the process exiting SUCCESS. I'll warrant that the same applies in every report here.
@danieleiba @jupiter126 @mannp - Can you please check the service status and view the process outcome?

I suggest that we close this with an entry in the FAQ

[andrewdavidwong]

@unman:

This has been an issue for some time, and it's been reported on mailing lists also.
But it is, I think, spurious. Whenever I have looked at the logs (as instructed) I see the modules-load service active since boot time, with the process exiting SUCCESS. I'll warrant that the same applies in every report here.

Wouldn't that entail that the "Failed to start Load Kernel Modules" message is false? If so, that's the bug here. The message should be prevented, hidden, or suppressed.

[andrewdavidwong]

@unman:

This has been an issue for some time, and it's been reported on mailing lists also.
But it is, I think, spurious. Whenever I have looked at the logs (as instructed) I see the modules-load service active since boot time, with the process exiting SUCCESS. I'll warrant that the same applies in every report here.

Wouldn't that entail that the "Failed to start Load Kernel Modules" message is false? If so, that's the bug here. The message should be prevented, hidden, or suppressed.

[unman]

On Sat, Dec 09, 2017 at 01:48:08AM +0000, Andrew David Wong wrote: @unman: > This has been an issue for some time, and it's been reported on mailing lists also. But it is, I think, spurious. Whenever I have looked at the logs (as instructed) I see the modules-load service active since boot time, with the process exiting SUCCESS. I'll warrant that the same applies in every report here. Wouldn't that entail that the "Failed to start Load Kernel Modules" message is false? If so, that's the bug here. The message should be prevented, hidden, or suppressed.

This would be an upstream bug. In fact, with the latest dom0 updates I think the issue disappears completely in 3.2 - anyone else confirm? And report situation in 4rc3?

[unman]

On Sat, Dec 09, 2017 at 01:48:08AM +0000, Andrew David Wong wrote: @unman: > This has been an issue for some time, and it's been reported on mailing lists also. But it is, I think, spurious. Whenever I have looked at the logs (as instructed) I see the modules-load service active since boot time, with the process exiting SUCCESS. I'll warrant that the same applies in every report here. Wouldn't that entail that the "Failed to start Load Kernel Modules" message is false? If so, that's the bug here. The message should be prevented, hidden, or suppressed.

This would be an upstream bug. In fact, with the latest dom0 updates I think the issue disappears completely in 3.2 - anyone else confirm? And report situation in 4rc3?

[mannp]

@unman wifi and thunderbolt ethernet are not compatible with qubes on my laptop so I have removed qubes for Arch, so am unable to feedback.

[mannp]

@unman wifi and thunderbolt ethernet are not compatible with qubes on my laptop so I have removed qubes for Arch, so am unable to feedback.

[githubnub6]

I can confirm dom0 update fixed it for me. I had the exact same "failed to start Load Kernel Modules" after fresh install of 3.2 and by updating dom0 (using the current-testing repo) it stopped showing it. This was only for legacy boot however.

This was NOT the case for when I had 3.2 installed in UEFI mode. The annoying red error at the top of the log"failed to start Load Kernel Modules" when booting persists after updating dom0 and even showed up when I tried installing 4.0rc3.

There should really be some warnings somewhere thats says if you try and install Qubes using UEFI then you might not have a good time.*

*might be because of my AMD gpu that I cant for the life of me figure out why iommu wont activate. Its a "mullins" model amd APU

[githubnub6]

I can confirm dom0 update fixed it for me. I had the exact same "failed to start Load Kernel Modules" after fresh install of 3.2 and by updating dom0 (using the current-testing repo) it stopped showing it. This was only for legacy boot however.

This was NOT the case for when I had 3.2 installed in UEFI mode. The annoying red error at the top of the log"failed to start Load Kernel Modules" when booting persists after updating dom0 and even showed up when I tried installing 4.0rc3.

There should really be some warnings somewhere thats says if you try and install Qubes using UEFI then you might not have a good time.*

*might be because of my AMD gpu that I cant for the life of me figure out why iommu wont activate. Its a "mullins" model amd APU

[e6lk7dqzm83p]

I have this on a brand new 4.0 install; unable to tell if it is affecting anything due to other issues (sys-net not loading).

[e6lk7dqzm83p]

I have this on a brand new 4.0 install; unable to tell if it is affecting anything due to other issues (sys-net not loading).