Hello Patrik,
On 07/26/2017 04:24 PM, Patrik Hagara wrote:
On 07/26/2017 11:07 AM, 'P R' via qubes-users wrote:
Any idea where to look further and was is happening exactly
between "qrexec done" and "guid done"?
Try running
systemd-analyze blame
in the DispVM for both old and new template, maybe some service is
misbehaving.
Thank your for the hint, I've run 'systemd-analyze blame' in the dvm,
which was based on the fedora-23-image and launches firefox within 15
seconds.
I've also run 'systemd-analyze blame' in my fedora-25 based dvm, which
is currently launching firefox in 62 seconds (vs. 15 seconds with a
fedora-23 dvm)
I've compared the output of systemd-analyse blame in both dvms and the
greatest difference is within the last few lines (I have attached the
full output at the bottom of this email):
Fedora-25 DVM: starting a disposable Firefox within 60-70 seconds = very
slow!
1min 41.053s qubes-update-check.service
20.913s qubes-dvm.service
17.748s ldconfig.service
8.011s dev-xvdd.device
3.482s systemd-hwdb-update.service
Fedora-23 DVM: starting a disposable Firefox within 15 seconds
16.052s qubes-dvm.service
15.864s ldconfig.service
6.085s dev-xvdd.device
2.774s systemd-hwdb-update.service
As such my conclusion:
1) qubes-dvm.service seems to eat up more time compared to the fedora-23dvm
2) an additional service "qubes-update-check.service" seems to be
running in the fedora-25 dvm which is not included in the fedora-23 dvm.
Someone has more ideas where to look further.
Is the timestamp the starting time of the service? If so,
qubes-dvm.service runs much much longer in the fedora-25 dvm.
More important question: what are the options to fix this?
-------
Output of systemd-analyse blame in my fedora-23 DVM:
16.052s qubes-dvm.service
15.864s ldconfig.service
6.085s dev-xvdd.device
2.774s systemd-hwdb-update.service
2.549s systemd-udevd.service
2.464s dev-xvdb.device
1.899s qubes-mount-dirs.service
1.819s qubes-sysinit.service
1.747s systemd-tmpfiles-setup-dev.service
958ms systemd-journal-flush.service
951ms abrtd.service
527ms auditd.service
505ms systemd-fsck-root.service
435ms qubes-db.service
427ms abrt-ccpp.service
400ms qubes-iptables.service
359ms upower.service
327ms polkit.service
312ms qubes-misc-post.service
259ms systemd-udev-trigger.service
251ms systemd-tmpfiles-setup.service
238ms proc-xen.mount
236ms systemd-journal-catalog-update.service
233ms dev-mqueue.mount
230ms kmod-static-nodes.service
221ms fedora-readonly.service
219ms systemd-logind.service
201ms systemd-sysctl.service
195ms systemd-vconsole-setup.service
177ms systemd-journald.service
176ms cups.service
166ms systemd-remount-fs.service
162ms systemd-sysusers.service
157ms [email protected]
149ms fedora-loadmodules.service
124ms tmp.mount
121ms iio-sensor-proxy.service
106ms systemd-hostnamed.service
101ms udisks2.service
99ms sys-kernel-debug.mount
94ms qubes-meminfo-writer.service
92ms systemd-user-sessions.service
83ms systemd-modules-load.service
79ms rtkit-daemon.service
77ms dev-xvdc1.swap
67ms xendriverdomain.service
61ms qubes-gui-agent.service
60ms sys-fs-fuse-connections.mount
48ms systemd-random-seed.service
47ms systemd-update-utmp.service
38ms dracut-shutdown.service
36ms qubes-qrexec-agent.service
17ms systemd-update-done.service
17ms sys-kernel-config.mount
14ms systemd-update-utmp-runlevel.service
Output of systemd-analyse blame in my fedora-25 DVM:
1min 41.053s qubes-update-check.service
20.913s qubes-dvm.service
17.748s ldconfig.service
8.011s dev-xvdd.device
3.482s systemd-hwdb-update.service
3.183s qubes-mount-dirs.service
3.059s systemd-udevd.service
2.431s dev-xvdb.device
2.001s qubes-sysinit.service
1.901s systemd-tmpfiles-setup-dev.service
1.683s systemd-journal-flush.service
1.448s qubes-db.service
1.170s qubes-misc-post.service
1.068s systemd-fsck-root.service
1.039s systemd-random-seed.service
880ms xendriverdomain.service
858ms systemd-logind.service
813ms fedora-readonly.service
795ms abrt-ccpp.service
668ms polkit.service
588ms abrtd.service
503ms systemd-sysctl.service
501ms systemd-journald.service
463ms auditd.service
453ms systemd-tmpfiles-setup.service
440ms qubes-iptables.service
404ms systemd-journal-catalog-update.service
364ms [email protected]
357ms fedora-loadmodules.service
336ms tmp.mount
320ms sys-kernel-debug.mount
314ms iio-sensor-proxy.service
289ms systemd-modules-load.service
286ms dev-mqueue.mount
242ms proc-xen.mount
216ms upower.service
179ms cups.service
172ms systemd-udev-trigger.service
168ms rtkit-daemon.service
156ms systemd-sysusers.service
150ms systemd-remount-fs.service
145ms kmod-static-nodes.service
145ms dev-xvdc1.swap
115ms udisks2.service
113ms systemd-update-utmp-runlevel.service
94ms systemd-update-utmp.service
84ms systemd-vconsole-setup.service
72ms systemd-user-sessions.service
71ms qubes-gui-agent.service
60ms systemd-hostnamed.service
35ms qubes-meminfo-writer.service
33ms dracut-shutdown.service
17ms systemd-update-done.service
16ms sys-kernel-config.mount
8ms qubes-qrexec-agent.service
- PhR
--
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 [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-users/40a40778-841e-bd21-b461-d7434a9bd0b8%40googlemail.com.
For more options, visit https://groups.google.com/d/optout.
