Installation halted libxenlight domain sys-net

User Support Hardware Issues
, ,
1

Necessary Hardware info :
Msi b760m mortar max wifi with intel wifi 6E chipset
Intel i9-13900es1(q0d8) cpu
Crucial 48gb x 2 ddr5 memory
Crucial p5 2tb ssd

I’m currently struggling with my installation of qubes os, i’m attempting again and again to install but always stuck on the message :

Qube Status: sys-net
Qube sys-net has failed to start: internal error: libxenlight failed to create new domain ‘sys-net’

Problem always happen on ‘setup networking’ process, and after the error message installation process is being halted. So, i can see the qubes with working dom0, but i cannot execute any kind of application inside the qubes, when i attempted refreshing the qubes they started properly, but it didn’t give me any applications, so i cannot use backup qubes.

Once i started to search how to restart the installation process manually, but there are no document that is enoughly accessible(i cannot find it) via search. I once heard that if i disable wifi card then i can boot, but the io shield where card is located is cannot be removed. So i think i need to know how to disable the pcie device on the grub before installation process, or i need to (at least) know how to manually accomplish the configuration.

Intel VT-d enabled. I suspect that due to my processor(which is an engineering sample, extremely cheap with limited functionality), chances are the virtualization doesn’t work properly, but i think it’s rather not likely.

Any solutions or recommendations?

2

Try to install Qubes OS with kernel-latest. There is a separate GRUB menu entry for this in the Qubes OS installer:

720×396 3.85 KB

You can check the log to see the reason for sys-net failing in the /var/log/libvirt/libxl/libxl-driver.log in dom0.

You can uncheck the creation of the qubes (sys-net/sys-firewall/etc) in the Initial Setup and create them manually later:

1024×768 59.6 KB

You can also create the default qubes later using salt:

2 Likes
3

Thanks for providing me such a bunch of help! I’ll try it tomorrow.

Today i attempted to reinstall the qubes os regarding your guideline.
When i started installation with sys-net and sys-firewall disabled, i encountered the message that indicates there was an error installing default-dvm…

So i manually installed things. Template is properly installed, salt formula works well, but i cannot start any qubes at all.

I double-checked whether virtualization options are enabled, it is alright… I think my problem is my engineering sample cpu. I cannot find a legitimate information, but i saw some search result at reddit displayed in search engine, indicating intel engineering sample cpu doesn’t necessarily support virtualization.

4

You can try to install some general Linux OS and passthrough some PCI device to the KVM guest OS for a test.

5

I’ll test it out, but first i’ll attempt another methods before installing anything via network(i think my network is compromised)
I updated the bios and now following these guidelines >> Nvidia Troubleshooting Guide

My vault qubes itself boot well(although i cannot sync the application), which means lack of virtualization is not a problem but i can’t use neither sys-net nor sys-usb. Since i cannot boot sys-usb, if i add usb device to sys-usb qube and reboot it disables the keyboard/mouse input. Sys-usb and sys-net are both qubes using “provides network to other qubes”.

Chances are my dual nvidia p40 graphics are problem, i’m currently learning how to follow the guidelines but they are pretty hard to follow… I’ll come back soon.

Now i’m reading this :
Boot failure after GRUB menu / System freezes followed by reboot
Lack of video output during Nvidia driver installation

Especially lack of video output seems my problem, after i type sudo nano /boot/efi/EFI/qubes/xen.cfg i see literally nothing.

6

I encountered some sys-net writing error, but it was a mere sudo permission error.

7

VT-x could be working, but VT-d (that is needed for PCI passthrough) could be not working. This could be the reason for sys-net and sys-usb failing to start since they have PCI devices attached to them.

I don’t think it’s related.

You don’t have video output? I thought you only have an issue with the sys-net/sys-usb failing to start.

That part of the guide is outdated, you need to edit the Xen config GRUB_CMDLINE_XEN_DEFAULT in the GRUB file /etc/default/grub and then regenerate grub config with:

sudo grub2-mkconfig -o /boot/grub2/grub.cfg
1 Like
8

It seems i need to embrace that my engineering sample cpu does not support VT-d tech…

Thanks for providing such help.

9

Short question, today i turned on and off intel virtualization technology and vt-d options…
When i turn of one of them, installation process let me know that i’m using unsupported hardware.
Message pop up like “vt-x disabled” or “vt-d disabled” or etc.

Does qubes has an ability to identify whether bios option is turned on?
Or it maybe the problem of iommu?

10

I guess it can detect if virtualization/iommu is available in the system. But whether it works or not is another question.
I still suggest you to check if you can passthrough the PCI device to a VM in some other OS using KVM/VirtualBox/etc to rule out some Qubes OS specific issue.

11

IMG_20240724_221156_155
IMG_20240724_221156_1554080×3072 1.16 MB

Claude suggested these commands, and it responded :
Iommu is present but seems to be disabled for graphics
“Dmar : skip iommu disabling for graphics”
Ommu is active : “iommu : default domain type : translated”
Vt-d is active for GFX Access : “VTd active for gfx access”

Cpu virtualization support :
Grep command for vmx|svm in /proc/cpuinfo returned no result.
Iommu group :
The command to find iommu groups returned no results, suggesting iommu groups are not properly set up.
Kernel command line:
Output shows a placeholder, but doesn’t include any iommu-related parameters.
Iommu module status :
Cat command for the intel_iommu parameters returns a korean message wgich translates to “the file or directory doed not exist”
Virt-host-validate : no visible output

Conclusions :
Vt-d appears to be active, at least partially
Iommu is present but may not be fullt enabled or cobfigured
Cpu virtualization flags are not detected, which is concerning.
Iommu groups are not properly set up.

I’ll add “intel_iommu=on” and "iommu=pt"tomy kernel parameter, in /etc/default/grub. With the line starting GRUB_CMDLINE_XEN_DEFAULT.
And typing
grub2-mkconfig -o /boot/grub2/grub.cfg

12

IMG_20240724_224404_039
IMG_20240724_224404_0394080×3072 3.12 MB

IMG_20240724_224411_608
IMG_20240724_224411_6084080×3072 2.6 MB

IMG_20240724_224515_898
IMG_20240724_224515_8984080×3072 2.17 MB

IMG_20240724_224630_596
IMG_20240724_224630_5964080×3072 2.91 MB

This is example of journalctl, it seems the problem of /usr/lib64/security/pam.sss.so is constantly repeating…

13

It’s not related and should be harmless:

Check the content of this file in dom0 to see the reason for sys-net start failing:

sudo cat /var/log/libvirt/libxl/libxl-driver.log
14

IMG_20240725_120104_949
IMG_20240725_120104_9494080×3072 2.84 MB

IMG_20240725_121326_634
IMG_20240725_121326_6344080×3072 2.22 MB

I’m reading this thread to know how to resolve the peoblem, same happens in my computer.

15

libxl: libxl_dm.c:2857:stubdom_xswait_cb:domain 5:Stubdom 6 for 5 startup: startup timed out.
libxl_create.c:1975:domcreate_devmodel_started: Domain 5:device model did not start: -9

Check /var/log/xen/console/guest-sys-net-dm.log log.

16

IMG_20240725_131513_037
IMG_20240725_131513_0374080×3072 2.28 MB

IMG_20240725_131523_345
IMG_20240725_131523_3454080×3072 2.54 MB

IMG_20240725_131532_182
IMG_20240725_131532_1824080×3072 1.97 MB

IMG_20240725_131540_289
IMG_20240725_131540_2894080×3072 1.91 MB

IMG_20240725_131547_469
IMG_20240725_131547_4694080×3072 1.9 MB

IMG_20240725_131554_782
IMG_20240725_131554_7824080×3072 1.21 MB

IMG_20240725_131603_721
IMG_20240725_131603_7214080×3072 1.9 MB

IMG_20240725_131612_561
IMG_20240725_131612_5614080×3072 1.31 MB

17

qemu: -append only allowed with -kernel option

Seems to be the same problem with kernel as described in the github issue.
Try to reinstall the Qubes OS and make sure to test the media before install to make sure that it’s not corrupted.

18

I tried more than 10 times installing qubes os, veryfied iso with both .asc and .digests fils, tried installation with other computer(whoch worked well)… I cannot figure out does it helps…anyway, i’ll try again.

19

Did you test the media before install to make sure that your ISO was written correctly on your installation media?

I guess you can report the issue here so it’ll be reopened and try to debug it further there:

20

For future reference, this issue is caused by wrong system time:

So update the system time (e.g. in BIOS) to fix it.

1 Like