UEFI Boot Entry

apparatus · April 28, 2024, 6:14pm

There was a security patch in Xen recently that patched CPU bugs:

And this noticeable slowed down some old machines.
In some cases this caused inability to use Qubes OS on the machine:

github.com/QubesOS/qubes-issues

No Qubes/VMs starting - libxenlight failed to create new-domain in 4.2.1

opened 03:32PM - 24 Apr 24 UTC

closed 10:57PM - 26 Apr 24 UTC

scallyob

T: bug C: Xen P: major R: declined diagnosed affects-4.2

[How to file a helpful issue](https://www.qubes-os.org/doc/issue-tracking/) #…## Qubes OS release 4.2.1 ### Brief summary I did a full update on April 23 and rebooted April 24. First reboot since April 1. Now no Qubes/VMs will start. ### Steps to reproduce 1. Update dom0 and all VMs. 2. reboot ### Expected behavior VMs set to autostart start up ### Actual behavior "libxenlight failed to create new-domain" pop ups for sys-net, sys-firewall, etc qvm-ls - shows all VMs halted /var/log/libvirt/libxl/libxl-driver.log shows: > libxl: libxl_dm.c:2857:stubdom_xswait_cb: Domain 1: Stubdom 2 for 1 startup: startup timed out > libxl: libxl_create.c:1975: domcreate_devmodel_started: Domain 1:device model did not start -9 This repeats many times with the Domain # changing (there are also errors related to PCI device, but these are present for previous boots as well and are not new. The errors above do not appear until today in the log.)