>> I've made a clean install of Qubes 4-rc2
>> but ~70% of the time I can't boot the VMs

After 2h troubleshooting I deleted my whole setup and reinstalled, again 
running into problems when trying to create new VMs.
... Ahrk. I. Hate. Linux. (From time to time).

Seriously, I burned now ~2h trying to get Qubes 4 running. Can't be that hard 
for a user who is running Qubes for ~2y.

Question:
Can we get an information on which laptops/Modells Qubes 4-rc2 has been tested?
Currently I don't know if I just to dumb to get things up and running or if my 
hardware has a problem.
As I have already invested lots of time in Qubes 4 rc1 before abandoning it and 
go back to 3.2, I just don't want to burn any time in case that my hardware is 
a dead horse.

Having the information on which laptops Qubes 4 "should" run or even more where 
it is running (Dev Users?) would help.
The HCL https://www.qubes-os.org/hcl/ does not help me, as it has no 
information if 4.x is ok for the X230.

As mentioned before I am running Coreboot, should I go back to stock ROM?

[799]
I need to

. > > This includes sys-net, sys-firewall, but also . > > > > I tried to check 
the logs but I don't get any valuable information. > > See screenshot. > > > > 
I started the following command in dom0: > > > > watch -n 1 xl list > > > > 
When I try to launch a VM I can see that the VMs appears in the xl list output, 
but the State is ------ and the Time(s) is 0.0. > > After ~30sec the start is 
aborted with error message: Cannot execute qrexec-daemon. > > > > Questions: > 
> 1) is anyone running Qubes 4.0-rc2 on a Lenovo X230? > > 2) is someone 
additionaly running Coreboot? > > 3) I am running the Qubes Installation with 
the default settings, any options to tweak on the Grub command line > > > > 
[799] > > > > > > > > > > > > Gesendet von ProtonMail mobile > Set pci strict 
reset on sys-net and sys-usb to false and try again. If that doesn't help set 
virt_mode to pv. If that helps it means your laptop does not meet minimum 
system requirements Same for me. It worked after a lot of restarting and 
changing settings. Sys-firewall started after I set initial ram higher. The 
others on debug mode with no network-vm set in settings. Not immediately 
though, try it, even change templates, and restart the templates a few times. I 
didn't get the qrexec logs from the qubes-applet and didn't bother to check 
further since it worked after several retries. -- You received this message 
because you are subscribed to the Google Groups "qubes-users" group. To 
unsubscribe from this group and stop receiving emails from it, send an email to 
qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to 
qubes-users@googlegroups.com. To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/0326dd36-a12e-45f3-ad4e-ce89ad688772%40googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/-eRgdQDQFTTwNdHXLhB497Flh6HWeMHUfuTBAA87lVz-poaDrd2zQ03XH6EDMtIkEogtZwdx9nU07fLR3bmdjeM7oBjZui01iRGyQAZ7WCA%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to