Plymouth seems to delay boot in AppVMs

[hdevalence]

Running systemd-analyze critical-chain in an AppVM gives a result like:

The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

multi-user.target @4.452s
└─qubes-misc-post.service @4.136s +314ms
  └─qubes-mount-dirs.service @3.951s +161ms
    └─basic.target @3.927s
      └─systemd-ask-password-plymouth.path @3.927s
        └─plymouth-start.service @558ms +3.367s
          └─systemd-udev-trigger.service @326ms +199ms
            └─systemd-udevd-control.socket @255ms
              └─-.slice @71ms

It would be good to optimize the boot of the default templates.

[marmarek]

Plymouth shouldn't be running there at all...

[marmarek]

Plymouth shouldn't be running there at all...