NovaCustom V54 sys-net not starting

[nestire]

Qubes OS release

Qubes 4.2.3
Dasharo 0.9.0

Brief summary

After default install with fedora-40 as template sys-net fails to start the libxl-driver.log shows:

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

dmesg in dom0 shows a bunch of:

[Firmware Bug]: CPU 1: APIC ID mismatch. CPUID: 0x0001 APIC 0x0021
[Firmware Bug]: CPU 1: APIC ID mismatch. Firmware: 0x0010 APIC 0x0021

they differ in the Hex value

thats maybe related.

unfortunately sys-usb does also not start so i can't get the complete log in a easy way

Steps to reproduce

Default install Qubes 4.2.3 on a V54 with Dasharo 0.9.0

Expected behavior

works

Actual behavior

Does not start

[marmarek]

dmesg in dom0 shows a bunch of:

[Firmware Bug]: CPU 1: APIC ID mismatch. CPUID: 0x0001 APIC 0x0021
[Firmware Bug]: CPU 1: APIC ID mismatch. Firmware: 0x0010 APIC 0x0021

That's unrelated to this issue. See https://lore.kernel.org/xen-devel/20240405123434.24822-3-jgross@suse.com/

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

Some more info from the stubdom log (/var/log/xen/console/guest-sys-net-dm.log) would be useful. But my guess is that system time was wrong (way in the past) during installation - unfortunately, installer fails to install some files if their time is in the future (package time in the future compared to system time). The easiest solution is to set correct system time and reinstall.
If my guess is correct, this is duplicate of #9440

[nestire]

thx indeed setting the correct time before install fixed it. so closing this as duplicate #9440

[github-actions]

This issue has been closed as a "duplicate." This means that another issue exists that is very similar to or subsumes this one. If any useful information on this issue is not already present on the other issue, please add it in a comment on the other issue. Here are some common cases of duplicate issues:

• The other issue is closed. The other issue being closed does not prevent this issue from duplicating it. We will examine the closed issue and, if appropriate, reopen it.
• The other issue is for a different Qubes release. We usually maintain only one issue for all affected Qubes releases.
• The other issue is very old. The mere age of an issue is not, by itself, a relevant factor when determining duplicates.

By default, the newer issue will be closed in favor of the older issue. However, we make exceptions when we determine that it would be significantly more useful to keep the newer issue open instead of the older one.

We respect the time and effort you have taken to file this issue, and we understand that this outcome may be unsatisfying. Please accept our sincere apologies and know that we greatly value your participation and membership in the Qubes community.

If anyone reading this believes that this issue was closed in error or that the resolution of "duplicate" is not accurate, please leave a comment below saying so, and we will review this issue again. For more information, see How issues get closed.