Hey there, Qubes OS community! It's the story of systemd-modules-load failing to load the kernel modules, ending in kernel panics at boot.
As I couldn't boot on my last install, I've wiped it with the same
configuration.
Some bugs have been reproduced at installation time, including systemd
failing to load the kernel modules.
**BIOS**
* VT-d is enabled.
* TPM v1.2 was enabled on the first install (v2.0 now)
* memory protection was enabled on the first install (disabled now)
* hyperthreading was enabled on the first install (disabled now)
**BASIC HARDWARE DESCRIPTION**
I run an x260 ThinkPad with an Intel i5-6300U CPU, 8 GB of RAM, and an
SSD.
**CONFIGURATION**
I've partitioned Qubes OS by using the default layout, with FDE.
I've configured Qubes OS to update the system and the VMs through Tor.
**BUGS**
* 1. As I've mentioned earlier, systemd fails to load the kernel modules.
The full message is:
[FAILED] Failed to start Load Kernel Modules.
See 'systemctl status systemd-modules-load.service' for details.
(I haven't used systemd for years, but I haven't found relevant info
with the systemctl output.)
* 2. During the postinstall (after Qubes' first reboot), Qubes OS crashes
4 times, leading to the computer rebooting. It doesn't seem normal.
After 3 reboots, Qubes OS enables me to run the userland I'm using to
send this email. Except the following message:
(I've had the same messages with whonix-ws-15 and fedora-30; there seem
to be the same line numbers on each respective message)
Configuring TemplateVM debian-10 failed:
['qvm-template-postprocess', '--really', '--post-install', 'debian-10',
'/var/lib/qubes/vm-templates/debian-10'] failed:
stdout: ""
stderr: "debian-10: Importing data
Traceback (most recent call last):
File "/usr/bin/qvm-template-postprocess", line 5, in <module>
sys.exit(main())
File "/usr/lib/python3.5/site-packages/qubesadmin/tools/
qvm_template_postprocess.py",
line 310, in main
loop.run_until_complete(post_install(args))
File "/usr/lib64/python3.5/asyncio/base_events.py", line 467, in
run_until_complete
return future.result()
File "/usr/lib64/python3.5/asyncio/futures.py", line 294, in result
raise self._exception
File "/usr/lib64/python3.5/asyncio/tasks.py", line 240, in _step result
= coro.send(None)
File "/usr/lib/python3.5/site-packages/qubesadmin/tools/
qvm_template_postprocess.py", line 235, in post_install
import_root_img(vm, args.dir)
File "/usr/lib/python3.5/site-packages/qubesadmin/tools/
qvm_template_postprocess.py", line 83, in import_root_img
root_size = get_root_img_size(source_dir)
File "/usr/lib/python3.5/site-packages/qubesadmin/tools/
qvm_template_postprocess.py", line 73, in get_root_img_size
raise qubesadmin.exc.QubesException('root.img not found')
qubesadmin.exc.QubesException: root.img not found
"
I suspect this might be a Qubes OS bug, but I'm not sure --
no disrespect to the Qubes OS developers.
I'd like to use Qubes OS nevertheless because thanks to it's UX it
seems safer to use than other security-focused operating systems, in my
big user hands. So many thanks to the Qubes OS developers and
contributors for their patience and for their hard work!
I may send this issue to GitHub, if this finally seems to be a Qubes OS
bug.
Thanks for developing and contributing to Qubes,
Nathan (this is a nickname)
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/nDvli5cG6Y5jiYQH0bS5cn5SXHsWkt9ZXOjReD03-giekyyXrJ0hks2uMKbeKoNEiJOQXhGbl6coq-aKdaq_POr1Jo8UJor5Qlu1oeUuApk%3D%40protonmail.ch.
publickey - [email protected] - 0xBA6C2D62.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
