On Wed, Aug 22, 2018 at 8:22 PM, Kelly Dean <[email protected]> wrote:
> System is otherwise idle. Almost no disk I/O. Pausing my app qubes makes no
> difference. xentop shows only dom0 is really busy (CPU usage fluctuates from
> 105% to 120%). top in dom0 shows only xenstored is busy (80%). Reserved
> memory for xenstored is stable, and only 3496 kB. There are two CPU cores,
> one of which is idle, and the system is usable. The system has been this way
> for more than 4 hours. Only thing I did before that was update and reboot,
> then start my usual working set of qubes. There were some fedora-28 updates,
> but no dom0 updates.
>
> Running 4.0 final release.
>
> What's the easiest way to find out what xenstored is doing?
A few methods, in rough order of ease:
1. See if anything interesting in `systemctl status xenstored`
2. If you are likely to be able to reproduce the behavior, enable
tracing by defining XENSTORED_TRACE to non-empty string at top of
/etc/xen/scripts/launch-xenstore and check
/var/log/xen/xenstored-trace.log when it happens again.
3. Check what your xenstored is doing:
$ sudo qubes-dom0-update xen-debuginfo
$ sudo gdb xenstored $(pgrep xenstored)
(gdb) bt
...
Warning: attaching gdb to a suspect process exposes a large attack
surface. You may not want to do this on a live machine if it is
sensitive. Dump a core file and do offline analysis in an unpriveleged
environment instead.
--
You received this message because you are subscribed to the Google Groups
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-devel/CABQWM_CJmPnEhLG8WsdYuySLPsbcZ0rAuYZCvs5eaQ%3DQ6vkwvg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
