The installation of Qubes on a new laptop fails. Help is needed!

At the very end of the installation, a message appears:
[‘/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”

After this, all cubes using sys-firewall and sys-net do not work.

The system has a vault cube that does not use sys-firewall and sys-net. And that’s why it starts without errors. I tried to attach a flash drive to it to rewrite the logs. The flash drive is attached to the cube, which is confirmed by pop-up messages on the screen, but the flash drive is not displayed in the file manager. Therefore, I don’t know how to copy the corresponding logs.
I am not well versed in Linux, and I use Qubes only as a simple user, in everyday work.

I would appreciate any ideas to solve the problem.

Do you have sys-usb qube? Does it start successfully?

Based on this I guess your sys-usb works.
You need to mount the disk using terminal:

What error do you see when you try to start sys-net qube?

When I try to launch any cube running using sys-net and sys-firewall, I see the following errors on the screen:

Qube Status: sys-net
Qube sys-net has failed to start: Cannot connect to qrexec agent for 60 seconds, see /var/log/xen/console/guest-sys-net.log for details

Qube Status: sys-firewall
Qube sys-firewall has failed to start: Cannot connect to qrexec agent for 60 seconds, see /var/log/xen/console/guest-sys-net.log for details

Try detaching the usb from the qube in the dropdown (qui-devices) and then attach it again to the same qube. I sometimes have this issue where it doesn’t show up in file manager on the first try

Need to see the logs in /var/log/xen/console/guest-sys-net.log and /var/log/xen/console/guest-sys-net-dm.log to know what’s wrong with sys-net.
Maybe one of the PCI devices attached to sys-net is causing this problem. You can try to disconnect the PCI devices from sys-net one by one in its Settings → Devices tab and try to start the qube to see which device is causing this.

1 Like

Before opening this topic, I tried many times different options for installing Qubes OS on my laptop. I tried connecting and disconnecting the flash drive many times (the result is the same - the system reports that it is connected, and I see it in the sys-usb drop-down menu, but it does not appear in the file manager).
I bought this laptop a week ago. This is an i5 with 12 cores, with 64G DDR 4 RAM, and an M.2 2280 2T PCIe-4.0 SSD, 7400MB/s read. Integrated graphics MX450 (Qubes defines it as Iris Xe Graphics).
I spent several days reading posts from the community on a similar topic, but did not find a single one that ended with success in solving a problem similar to mine.
And this worries me a lot.
This topic is my last hope…

You need to mount the attached disk manually in the terminal as stated in the linked guide:

Then you can use file manager to copy the files in the mounted directory.

The guest-sys-net.log and guest-sys-net-dm.log files are quite large - there are thousands of lines.
I will try to connect the USB flash drive according to your recommendations and copy them to post here, since I am not sure that I can correctly identify the problem on my own.
I am very grateful for your support.
I’ll be back a little later.

I assume you are attaching the USB to vault or something similar based on fedora.

Open terminal in the qube type

sudo fdisk -l

Does the drive show in the list ?

Is it located at

/run/media/user

?

You can also open terminal in sys-usb and run

Sudo fdisk -l

I launched Qube “vault”, opened a terminal, entered Sudo fdisk -l , and among others, the resulting list actually includes a flash drive!
Disk /dev/xvdi: 3.82 Gib

I’m not sure about the /run/media/user path. How to see it?

1 Like

Using your recommendations, I was able to connect the flash drive. Now I see it in the file manager. But the system does not allow anything to be written to it.
I open the “properties” of the flash drive. In the “permissions” section there is a “read only” label. All my attempts to change this setting to “read & write” have failed. I close “properties”, then open it again, and the changes are not saved. Read only is still available.
For this reason, I still cannot write logs.

Format it in gparted so that you can write to it.

You need to attach the USB device (not block device) to vault

Add gparted to applications in vault settings/Applications

Open gparted

Device, create partition table - msdos

New partition - fat 32

Green checkmark

Run the format

What do you have on this flash drive?
Is it the flash drive containing Qubes OS installer? In that case it’s a read-only partition.
Format the USB disk in your current main OS (Windows?) and then try again.

The flash drive is formatted in Windows OS.
It is not bootable. I use it to transfer files between computers that are not connected over a network.

Try to copy the file in the terminal using sudo e.g.:

sudo cp /path/to/log.txt /home/user/mnt/

Your idea that another PCI device was interfering with sys-net pointed me to where to look for the problem. And I discovered that this harmful device is the Wifi/BT module in my laptop. As soon as I turn it off, the whole system comes to life!
But now there is another problem - I need a WiFi module in my laptop.

Experimenting with the settings, I ruined the system. That’s why I’ll reinstall it today.

Now the main task is to “defeat” WiFi so that it lives in the system “without disturbing others.”

I don’t know which PCI error do you have, but it could be an issue with PCI reset.
Try to add the no-strict-reset option to your WiFi device:

I found the main problem and ruined the system. Today I will install it again.
The ultimate goal is to install Windows 11 and Qubes on my laptop, so that I can work in either Windows or Qubes if necessary.
I have never tried installing 2 systems on 1 computer before. Therefore, I would be very grateful for any recommendations / links to guides.

Thank you, Apparatus!
You can’t even imagine how grateful I am to you. I was ready to put my laptop up for sale. I was ready to believe that I had made a mistake and my laptop did not support Qubes.
I’ll try to reinstall the system today so that I can continue to “repair” it according to your recommendations.
By the way, maybe you have ready-made instructions on how to properly install 2 OS on a laptop - Win11 and Qubes?

Tomorrow I won’t have time to work on my laptop - I’ll be busy with urgent work all day. I can get back to my laptop a day later.
Therefore, I will try to do as much as possible today.

I think the easiest way would be to boot from some Live USB and create 2 partitions:

  • first one for Qubes OS e.g. 1.5 TB
  • second one for Windows with remaining 0.5 TB

Then remove the first partition so you’ll have the free space in its place.
Then install Qubes OS using all this 1.5 TB free space.
After installing Qubes OS remove the empty 0.5 TB partition that was placeholder for Windows.
Now install WIndows using this 0.5 TB free space.