Hello,
I’ve been using Qubes 4.0 on my laptop for about a month now and I’m very excited so far.
Now I want to take the step to install Qubes 4.1 on my desktop PC (first as dualboot for for testing).
The installation with provided alpha (Signed Q4.1 alpha iso) works fine, but at the first boot I get the error with default configuration of Qubes:
“Qubes initial configuration failed. Login to the system and check /var/log/salt/minion for details. You can retry configuration by calling ‘sudo qubesctl --all state.highstate’ in dom0 (you will get detailed state there)”.
Samsung SSD 980 Pro
Nvidia 1070 (conneceted to monitors)
AMD Radeon Vega 64 (intended for gpu passthroug)
Is there any information missing?
Thanks in advance!
Edit: I just noticed that secure boot was still enabled.
Now I am receiving
[Dom0] Error
Delfault DVM failed:
unsupported operand type(s) for +:‘NoneType’ and ‘str’
and no qubes are created.
Did you changed template selection earlier during installation (here)? If not, something went wrong at that stage, can you search for “qubes-template” in /var/log/anaconda and share logs that you find this way?
I don’t see a stage where templates are copied into the system. On successful install program.log contains near the end lines like this:
18:16:35,505 INF program: Running... /bin/sh /tmp/ks-script-nl7cqm5_
18:17:20,171 INF program: Unable to detect release version (use '--releasever' to specify release version)
18:17:20,174 INF program: Adding repo from: file:///tmp/installer.repo
18:17:20,174 INF program: Unable to detect release version (use '--releasever' to specify release version)
18:17:20,174 INF program: anaconda 36 MB/s | 1.1 MB 00:00
18:17:20,174 DBG program: Return code: 0
But I don’t see those in your logs. In a later version this output is saved to one of ks-script-*.log files, but it isn’t there neither in your install.
Honestly I have no idea what went wrong. I don’t see any relevant error message, installer simply skipped that step for some reason.
As for sharing logs, not sure. @deeplow is there any way to attach files directly here?
Is there a way to manually start the installation script (and get a proper log)? I am able to login but there exists only the Dom0 qube in the qube manager.
Edit: I installed it aigan and chose ‘Do not configure anything’. -> No error. But how do I configure the qubes? I just need the default settings.
You can check notably if in tmux session panes (CTRL-ALT-F1 or F2 if I remember correctly then you can switch tmux panes) there is issue at the end of the install process before reboot. Specifically it’s during post-script phase and you could check for what’s done for templates: https://github.com/QubesOS/qubes-anaconda/blob/master/30-qubes-templates.ks.
So i just excuted
dnf config-manager --add-repo /tmp/installer.repo
dnf download --downloaddir=/mnt/sysimage/var/lib/qubes/template-packages qubes-template-*
Were files already here before you executed the commands? Because if files were already here it’s the expected behavior. In a normal install you don’t need to do that manually of course.
Files are here because of repo setup and dnf download from it. Do you have templates shown at the firstboot screen now ? If yes, can you retry the same without any manual procedure please?
Honestly, I don’t see what’s wrong as I cannot reproduce it. If qubes-template-*.rpm files where in /mnt/sysimage/var/lib/qubes/template-packages, this is because a local repository has been added into anaconda running system. So there should be no consequence to add the repository again and downloading templates rpm again into freshly created /mnt/sysimage root system.
yes, there is. Currently enabled for .yaml files (for the HCLs). but we can add more file extensions. Which ones would be need? .log (not that file extensions mean a lot. Just the way discourse settings work). I’ll talk to the other mods.
I changed the installation media.
I doublechecked the old one.
I could verfiy the problem by test the installation media through the test and install option from the first bootscreen of the media: it said test failed and had this issue with broken VMs.
on the other media the test passed successfully and installation proceed without issues.
its not hosthardware related, because i had the issue on different computers.
