Hi Vincent,
I think the systemd service is working as intended. Other than the
output you pasted, running `systemctl enable qemu-guest-agent` prints
the following:
[...]
Possible reasons for having this kind of units are:
• A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
qemu-guest-agent falls in the third case, and it's activate by the udev
rule defined in:
/lib/udev/rules.d/60-qemu-guest-agent.rules
which is installed by the same package.
I'm setting the status to Incomplete for the moment. If my reply is not
enough to solve your issue and you believe you found a bug in Ubuntu
please explain the problem you are facing more in detail, possibly with
steps to reproduce it, then change the report status back to New and
we'll look at it again. Thanks!
** Changed in: qemu (Ubuntu)
Status: Invalid => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883009
Title:
qemu-guest-agent / systemctl enable failure
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1883009/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
