sys-net cannot be started (shuts down very soon) after installation of 4.2.2 and 4.2.3 #9495
Labels
affects-4.2
This issue affects Qubes OS 4.2.
C: other
hardware support
needs diagnosis
Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed.
P: default
Priority: default. Default priority for new issues, to be replaced given sufficient information.
T: bug
Type: bug report. A problem or defect resulting in unintended behavior in something that exists.
Comments
sjvudp
added
P: default
|
Duplicate of #9440? |
andrewdavidwong
added
C: other
hardware support
needs diagnosis
Well, I read that, but an incorrect system time causing qubes to boot would be a very odd bug. Besides that, the BIOS clock may be off up to 2 hours (UTC vs. CEST). |
|
2h is not a problem; several weeks/months is |
|
What type of log (if any) would help to diagnose (and more importantly: fix) the problem? |
|
OK, I managed to mount the disk in my openSUSE system, so I can provide some more details. Inspecting "rpm -qa --last", the oldest package was installed at "Mon Oct 7 20:33:40 202" (that last on "Mon Oct 7 20:39:43 2024"), so the time/date should not be an issue. Inspecting the journal for unusual messages, I found these: ( I have a AD107GLM [RTX 2000 Ada Generation Laptop GPU] , BTW)
Messages in /var/log/libvirt/libxl/libxl-driver.log are: In /var/log/xen/console/guest-sys-net-dm.log I found: ... In var/log/xen/console/guest-sys-net.log I found: ... /var/log/xen/qmp-proxy-sys-net-dm.log is empty. The VG looks like this: The LVs look like this: The failure messages for the Debian-12 were like this: ... |
Interesting, this looks like the template root filesystem is broken/empty. But on lvs I see:
so, it isn't empty. Could it be maybe #4974 ? What
The message about MSI/MSI-X is not the interesting part. The device BDF is - 0x10000 is not a valid PCI domain. Is it maybe some built-in Intel RAID (more details) ? It isn't necessarily the source of the problems, but I'd still recommend disabling it in the firmware setup menu. |
First ... Fdisk reports for And for the Fedora LV: Besides the And just in case: The NVME module is in an Icy Box "IB-1817Ma-C31" using a Jmicron USB bridge (ID 152d:0562). |
Yes, this looks exactly like #4974 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
How to file a helpful issue
Qubes OS release
4.2.3
Brief summary
I installed Qubes OS 4.2.2 on an external NVME SSD connected via USB (I had used the same device successfully for n older Qubes OS on a different computer). After reboot there was an error displayed.
Installation finished, but
sys-netwould shutdown itself rather quickly, and withoutsys-netno qube can be started. Obviously anything fixable through a downloadable update would not work.Maybe it has to do with some disk that cannot be mounted, like this:
Maybe this message causes it, but I don't know:
I suspect that it might also be CPU-related, as the Laptop (Lenovo ThinkPad P16 Gen2) has an Intel i9-13980HX CPU.
As other Linux shows 32 CPUs, and the machine has 96GB RAM, it would be a nice machine to run Qubes OS, I guess.
Here are some more details:
After that I connected the NVME device to the other computer that ran Qubes OS before, but there also
sys-netwon't start, so maybe it's not really a CPU issue.The only difference was that I had to repartition the NVME for GPT (before it was MBR) as the new laptop does not support "legacy boot" any more.
After that I downloaded the latest 4.2.3 installation medium, installed Qubes OSagain, but the result was the very same:
sys-netterminates rather quickly.Steps to reproduce
Install Qubes OS
Expected behavior
Qubes OS starts after installation
Actual behavior
Qubes OS is unusable after installation.
The text was updated successfully, but these errors were encountered: