Qubes OS Installation Error: Cannot Cannot to Qrexec Agent for 60 Seconds

[Idkso]

I get an error at the end of the Qubes OS installation network setup as you can see in the picture. I can only click on the OK button and the system starts, everything works except the Qubes because I do not have the firewall and the network is not available or displayed because it failed during the installation.

I have often read that I have to get an Ethernet cable because some do this during the installation because otherwise I think no network is recognized, I have ordered one which should come in the next few days but until then someone can tell me if it can be simply fixed or if there are other possibilities.

['/usr/bin/qvm-start', 'sys-firewall'] failed:
stdout: ""
stderr: "Cannot connect to qrexec agent for 60 seconds, see /var/log/xen/console/guest-sys-net.log for details"

[solene]

What is your computer model and processor?

[phceac]

Welcome !

You can try to search for your error here in the forum.

For example, here are some helpful questions to another person with the same problem here:

@apparatus

Probably you have a problem with one of the PCI network controllers attached to sys-net.
Did you have correct time in BIOS when you installed Qubes OS? Not something like a month or more in the past.
Are you able to start vault qube?
Try to use fedora template for sys-net if you use debian template.
Remove the PCI network controllers attached to sys-net one by one and try to start sys-net to find out if it’s a problem with one specific PCI network controller.

If you can do the verifications and answer each question, then that may help resolve the problem.

[FranklyFlawless]

Provide the guest-sys-firewall log:

Qube troubleshooting

“Cannot connect to qrexec agent” error

If you face this error when starting a VM, look into the VM logs at /var/log/xen/console/guest-VMNAME.log. Common reasons that may be revealed are: too low memory, corrupted files or a VM crash on startup.

If the error occurs as a result of too little initial memory, increase the initial memory from 200MB to 400MB by navigating to VM settings » Advanced » Initial memory.

[Idkso]

How should I share the log if I cannot connect to the Internet to upload it somewhere?

[Idkso]

CPU is kinda bad, just an ASUS Vivobook with an AMD Ryzen 3 and 12GB of RAM.

[FranklyFlawless]

Manually type it. In addition, create an HCL report and manually type that here too:

How to use the hardware compatibility list (HCL)

Generating and Submitting New Reports

In order to generate an HCL report in Qubes, simply open a terminal in dom0 (Applications Menu > Terminal Emulator) and run qubes-hcl-report <qube-name>, where <qube-name> is the name of the qube in which the generated HCL files will be saved.

[phceac]

Maybe @FranklyFlawless is joking…

@FranklyFlawless

Manually type it.

but it is a possibility.

Before you start typing, are you able to verify that other qubes can start correctly?

• Are other qubes running?
• If you select the Q menu, does Terminal or file manager open in the Vault qube? Do you see errors?

If Vault does not work, then there is a more important problem than the network!

[FranklyFlawless]

If you have a better suggestion to share logs with a nonfunctional sys-firewall, provide it.

[phceac]

Sorry, @FranklyFlawless … I was just imagining someone trying to type out the whole log file!

There is the use of a removable USB device, if another network-connected device is available… but that would be best used with another qube.

OTOH, if Vault works, then my next steps would be:

• (maybe ) Does sys-net run? sys-usb? (I’m not sure why we are only seeing sys-firewall errors… is there only WiFi on USB? I have no possibility to see how such a configuration works)
• OP tries looking at the log file in Dom0
  • ‘tail ’ to look at the last few lines
  • ‘grep -i error ’ to search for lines containing the string “error”
  • ‘grep -i failure ’ to look for the string “failure”
  • ‘less ’ to look through the whole file

If nothing is obvious, then (from memory) connect a usb key to another qube - not Vault - with network=none, qvm-copy, transfer from qubes-incoming, and send.

If Vault doesn’t work… pretty sure I had a similar problem , and even went looking at sys-firewall, when my IOMMU was disabled due to a failed CMOS battery, so no qubes were starting at all.