I just verified the behavior on all Ubuntu Pro versions for 16.04,
18.04, 20.04, 22.04:
- The behavior works great on all of these provided that the user
remembers to check off "Guest services" in the Hyper-V Manager VM's
Settings. Additionally, hv-fcopy-daemon.service, hv-kvp-daemon.service,
and
Ah -- Please disregard what i said in my last comment about suggesting
any changes to how the hv_*.service units should starts dynamically,
because it actually already does this on `WantedBy=` when the
corresponding device for the kernel module is created; because a udev
rule already does this.
Ho
There's one extra thought I had that could perhaps make this experience
a lot better for users:
- If distros wanted to make units have WantedBy= on the same device they
are writing BindsTo= on, then systemd might be able to dynamically
start/stop the service automatically at runtime, whenever user
I was just looking into the hv_fcopy_daemon behavior for another reason
(trying to support this on Gentoo), and I stumbled on this bug.
Everything here mentioned above seems to be absolutely correct:
- Make sure the corresponding "Integration Services" setting is enabled in
Hyper-V Manager, in th
