I am having some trouble with the post installation “initial setup” GUI wizard, after installing Qubes-R4.3.1. Can anybody help me with these issues described here?
I am installing Qubes-R4.3.1 via a USB drive. I verified the signature on the downloaded ISO and then verified the signature again on the USB drive by dd if=/dev/… | gpg -v –verify … so I am confident in the integrity of the installation data. I have tried installing twice now, and have tried different options on the initial setup wizard. Both attempts have resulted in some kind of error.
Attempt 1
In the first attempt, I boot the system from the installation drive (using the “test media and install” option), and then install the system using the “automatic” disk setup. The “test” part of the boot sequence was successful. The installation goes fine, and then I reboot into the initial setup wizard. I only install the debian template, and set it to create the sys-net / sys-firewall / dispVM qubes (configured to be dispVMs). I don’t configure it to create application qubes, a USB qube, or to setup whonix. I set it to create the default “vm-pool”. I click “Done” and it succeeds up until the “setup networking” section. I see a popup with an error about “sys-firewall” failing to start within 60 seconds. I am still able to login and I see the sys-net and sys-firewall VMs have been created, but I am not sure if my system is in an incomplete or invalid state. I decide to try the installation again, in case this was a fluke.
Attempt 2
I re-check the integrity of the USB drive, and confirm that the signature is still good for the data on the drive. I run the installation again using the automatic disk setup (the “test” part of the boot sequence was successful again). The installation succeeds and I reboot to get to the initial setup wizard. Since the networking qubes caused problems previously, I try to go simpler with the wizard, just to see if I can get it to produce a base system without errors. This time I only ask it to install the debian template, and setup the default “vm-pool”. No sys-net, sys-firewall, sys-usb, whonix or application qubes. I click “Done” and it succeeds up until the “Executing qubes configuration” step, where I see a popup that with the following.
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).
When I check the log at /var/log/salt/minion I see content like the following (I’m copying the text by keyboard on another computer, so instead of copying the timestamp from the log I just write TIMESTAMP).
TIMESTAMP [salt.pillar ][CRITICAL] Specified ext_pillar interface qvm_features is unavailable
TIMESTAMP [salt.pillar ][CRITICAL] Specified ext_pillar interface qvm_prefs is unavailable
TIMESTAMP [salt.pillar ][CRITICAL] Specified ext_pillar interface qvm_tags is unavailable
TIMESTAMP [salt.pillar ][CRITICAL] Specified ext_pillar interface qvm_features is unavailable
TIMESTAMP [salt.pillar ][CRITICAL] Specified ext_pillar interface qvm_prefs is unavailable
TIMESTAMP [salt.pillar ][CRITICAL] Specified ext_pillar interface qvm_tags is unavailable
When I run sudo qubesctl --all state.highstate I get the following
local:
----------
ID: states
Function: no.None
Result: False
Comment: No Top file or master_tops data maches found. Please see master log for details.
Changes:
Summary for local
------------
Succeeded: 0
Failed: 1
------------
Total states run: 1
Total run time: 0.000 ms
DOM0 configuration failed, not continuing
The file at /var/log/salt/master (which is what I assume they are referencing when they say “master log”) exists but it is zero bytes.
When I look at the logs in journalctl of the initial setup wizard running, I can see that during the “Executing qubes configuration” stage, there are lines with the prefix org.fedoraproject.Anaconda.Addons.QubesInitialSetup[7303]:. At one point it says that its running qubesctl --all state.highstate, and then it has messages about that command failing. It prints the identital output as the output shown above for the command sudo qubesctl --all state.highstate, and the surrounding text is a bunch of exception handling call trace stuff. I can give more info about the logs if necessary, but for now I am just copying the stuff that looks important because I have to manually copy it over by typing.
Does anyone know what’s going wrong here? How can I get the initial setup to give me a correct qubes 4.3.1 system?