Hi, i have installed qubes as a main machine, but i can’t open any app or programs , when i try to open any program it will give me error saying Failed to start , please help me to solve this issue
1 Like
What hardware did you install Qubes OS on?
Hi, Thank you for your great help , I can’t find the error running more /var/log/xen/console/gues-sys-net.log because there many lines, but when I run this command from dom0: xl dmesg | less, it show me these errors in the end:
(XEM) Dom0 has maximum 4 VCPUs
(XEM) initial low memory Virg Threshold set at 0x4000 pages.
(XEM) Scrubbing Free RAM in background
(XEM) std. Loglevel: Errors and warnings
(XEM) quest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEM) *** Serial input to DOM0 (type 'CTRL-a' three times to switch input)
(XEM) Freed 664KB init memory
If the problem comes from these errors Please help me to solve it by dom0 and qubes desktop, and I prefer dom0 if it possible.
By the way my device total memory is 16
Thank you
1 Like
Hi, Please what is the solution ?
1 Like
I do not have enough information.
Solution is only possible with more information about the problem.
Are you able to tell what hardware you have?
Do you know which options you chose during installation ? Did you change any of the options, or did you accept the configuration which was proposed ?
Most of the VMs require sys-net before they can start. Can you start a VM with network=‘none’ ? For example, did you try to start the Vault qube?
When you look at xl dmesg, it gives mostly information.
Do you see messages about the IOMMU ?
If there is no IOMMU, or no virtualization, then there may be a problem with the BIOS/UEFI configuration.
2 Likes
Hi, Thank you for your reply ,
Hardware:
intel N100 × 4
I choice fedora as default during the installation, no i didn’t changed any option but during the installation i accepted all the configuration .
Yes i can run vault qube and temporaries,
And by the this error it shows even every time when i turn on my qubes, thank you i believe that you can give me the solution
1 Like
I’m sorry, @John4 , I forgot… Did you make any progress?
It seems that the problem is only AppVMs which require network, because sys-net is not able to start, so the problem is with sys-net.
Probably it is because of the PCI devices, but we only know the type of your processor.
You can look at Settings for sys-net : in devices section, does it have some USB controllers, and the network controller attached to it?
Dom0 qvm-pci list command can tell you the same information, in the right column.
There may be some messages about “reset” of the PCI devices in the sys-net console logfile. You can try setting “no strict reset” for the usb controllers. There are instructions in the documentation. Maybe that is enough.
2 Likes
Thank you for your great info, ok harder model is: default string default string
Graphics is: intel Graphics (ADL_N)
Processor: intel N100 × 4
1 Like
Hi @phceac please write back to me , what i will do to solve it?
1 Like
Can you find it?
2 Likes
Yes i can find it, what i will do for it please? @phceac
1 Like
I can find usb controller on sys-net setting, but network controller option in different Menu call “Devices always connected to the qube”, please help me @phceac
1 Like
It is impossible to know, with so little information.
Write down the devices, try detaching some, until the qube can start, decide if the devices are necessary, decide if you can use separate sys-usb/sys-net, try adding some again, maybe use ‘no strict reset’, search this forum or the HCL…
1 Like