Maybe you had some issue during installation.
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.
Try to install Qubes OS 4.2.2-rc1. Maybe you can also install it with kernel-latest option so you can test the latest kernel if the issue persists with stable kernel after reinstall.