Xentop is showing dom0 using 50-60% cpu on my laptop, all the time. It did
not always do this, but I don't know which update may have caused it.
Top within dom0 shows a few processes taking 5% or or less, so whatever is
causing the high cpu usage is either in the kernel, or in whatever Xen is
Xentop is showing dom0 using 50-60% cpu on my laptop, all the time. It did
not always do this, but I don't know which update may have caused it.
Top within dom0 shows a few processes taking 5% or or less, so whatever is
causing the high cpu usage is either in the kernel, or in whatever Xen is
Hi uman,
that was the reference in qubes-doc that I found before and that I could
not find today when I was writing this email. However, it does not
explain what the advantage of this two-switch-model is compared to just
run the services defined in the per-qube services tab/setting without
the
On Mon, Mar 27, 2023 at 03:48:15PM +0200, r.wiesb...@web.de wrote:
> Hi there,
>
> every VM/qube has a "services" tab in its settings window. It seems like
> Qubes is designed in a manner that requires two switches for a service:
> it needs to be enabled in the template *and* requires an entry in
Hi there,
every VM/qube has a "services" tab in its settings window. It seems like
Qubes is designed in a manner that requires two switches for a service:
it needs to be enabled in the template *and* requires an entry in
"services" tab.
My expectation was that when selected in the "services"
