Cant start any vm other than dom0

Hello,

I just installed qubes os and get this error message when trying to launch firefox:

“Qube sys-net has failed to start: internal error: libxenlight failed to create new domain ‘sys-net’”

I also get the same message from all other vms i try to start.

I have virtualization enabled in bios.
How can i fix this?

Thanks

Do you have IOMMU / VT-d enabled in your BIOS?
Are you able to start vault qube?

Apparently i didnt have vt-d on, but now i get new error message:

"Qube Status: sys-net

Qube sys-net has failed to start: qrexec-daemon startup failed: 2024-09-28 21:53:35.403 qrexec-daemon [5955]: qrexec-daemon.c: 144:sigchld_parent_handler: Connection to the VM failed"

And the vault qube does start.

Check the sys-net log in dom0 in this file:
/var/log/xen/console/guest-sys-net.log
Maybe the kernel is crashing because of your network controller’s driver.
What network controllers do you have attached to sys-net?
You can check it using this command in dom0:

qvm-pci ls sys-net

I tried qvm-ls without that extra ls and it worked

My bad, it should be this:

qvm-pci ls sys-net

It has that no strict thing because i tried fixing other problem earlier using another quide online.

This network controller should work fine.
Check the sys-net log in dom0 in this file:
/var/log/xen/console/guest-sys-net.log
And maybe this one:
/var/log/xen/console/guest-sys-net-dm.log

Are you able to start sys-usb?

Is cat the right command to read those files?

Also im very new to qubes(and linux in general) so i dont know how to start sys-usb.

Thanks for your patience

Run this command in dom0 terminal:

journalctl -f -n0

Try to start sys-net.
Check the log in dom0 terminal after sys-net fails to start. Maybe there would be more info.

Do you have sys-usb qube in Qubes menu Q → SERVICE ->?

I dont see sys-usb when i do that. Only firewall, net and whonix

What’s in this log?
/var/log/xen/console/hypervisor.log

That log is very very long. This image is just the end of it

Seems that Xen is crashing for some reason. Maybe some hardware compatibility issue.
I think you’ll need to get this log file from dom0 and report this issue with attached log here:

So that developers can look into this issue and try to fix it.

Alright, thanks.