Hello everyone! I have been using qubes for a long time. Recently, especially for them, I purchased a new powerful PC, copying the fully certified nitro PC 2. MSI Z790P-wifi Intel i5 14600k And other spare parts. At the end of the installation, an error pops up, and then no cube is turned on. Tried different USB sticks, different ways to record from different PCs (windows, Mac, rufus, DD, BalenaEtcher) Tried installing with latest kernel. I tried to re-download and recheck the iso image. Please help! Screenshot are attached
Did you test the media before install in the Qubes OS installer? Was it successful?
It may sounds stupid, but set correct time before the installation (you can do that in the installer itself). Otherwise some files in the future will confuse installation scripts and kernel for qubes won’t get installed.
Related issue and similar cases just in case:
opened 04:36PM - 02 Jun 24 UTC
closed 11:32PM - 02 Jun 24 UTC
T: bug
P: default
R: self-closed
(The issue is *not* related to Intel 13th gen; but text is preserved just for re… ference.
The issue ended up being something wrong during install; a reinstallation helped.)
### Qubes OS release
4.2.1
### Brief summary
After clean installation of Qubes 4.2.1 on Intel i9 13th gen, HVM qubes (including `sys-net`) fail to start with:
```
libxl: libxl_dm.c:2857:stubdom_xswait_cb: Domain 15:Stubdom 16 for 15 startup: startup timed out
libxl: libxl_create.c:1975:domcreate_devmodel_started: Domain 15:device model did not start: -9
```
This must be related to software because I did have some earlier version of Qubes running fine on this same machine as well as on Intel NUC 13th gen.
It happens on HVM-type qubes; other work fine. Also it is not related to PCI; for test I removed all assigned devices from a HVM qube before attempting to start it.
An error similar/identical to this has already been reported in https://github.com/QubesOS/qubes-issues/issues/9150, but according to authoritative comment on it, that bug was related to (old) AMD processors and is not related to Intel.
### Steps to reproduce
1. Install Qubes 4.2.1 on 13th gen Intel i9-13980HX (possibly others). (Issue #9150 also mentions Intel NUC 13th gen)
2. Install will succeed and machine will reboot to finish installing templates etc.
3. The error about `sys-net` qube will show up
4. Same error happens on automatic start as well as on manual attempts
### Expected behavior
1. `sys-net` and any other HVM qubes to start normally
2. Other qubes depending on them to start normally
### Actual behavior
1. HVM qubes cannot start
2. Dependent qubes cannot start
### Other info
Seems at least partially related problem was also reported in https://forum.qubes-os.org/t/no-qubes-vms-boot-after-latest-updates/26033
Thanks.
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…
I tried qvm-sync-appmenus sys-usb. I get the error “Appmenus can be retrieved only from running VM.”
When I try to start sys-usb, I get the error: "has failed to start internal error: libxenlight has filed to create new domain ‘sys-usb’, see /var/log/libvirt/libxl/libxl-driver.log for details’
When I open that file, I these lines (among others):
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…
