On 10/25/17 13:26, '[799]' via qubes-users wrote:
Hello,
As at least one other Qubes user has the same problem, that VMs won't
start, I'll add this as special topic.
I've made a clean install of Qubes 4-rc2 but ~70% of the time I can't
boot the VMs.
This includes sys-net, sys-firewall, but also others.
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
I created an issue for my VM start problems:
https://github.com/QubesOS/qubes-issues/issues/3221
There is no libxenlight error, and I think the problem may be related to
the initial run of sys-net. Shutting down sys-net (and all VMs) and
starting it again seems to make a difference. Also, there is a RAM
allocation problem that (so far) hasn't shown up after I re-start sys-net.
Chris Laprise, tas...@posteo.net
https://github.com/tasket
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886
--
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/1ce1b0a4-5e39-a446-65c1-8ffa0b295f82%40posteo.net.
For more options, visit https://groups.google.com/d/optout.
