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 users enable/disable the individual "Integration Services" settings checkboxes in Hyper-V Manager on the host. However, while this trick probably would work great for hv_kvp_daemon, hv_vss_daemon, and hv_fcopy_daemon on kernels LESS THAN 6.11; I discovered that on kernels GREATER OR EQUAL to 6.11, it appears that writing `ConditionPathExists=/dev/vmbus/hv_fcopy` is probably wrong now. This is due to the fact the driver for hv_fcopy has since been removed from Kernel 6.11 and has since been replaced with a uio driver located at `/sys/bus/vmbus/eb765408-105f-49b6-b4aa-c123b64d17d4/uio` : https://github.com/torvalds/linux/commit/ec314f61e4fc2d3dd6ea78aa18a5ac276eb1a8e3 https://github.com/torvalds/linux/commit/82b0945ce2c2d636d5e893ad50210875c929f257 So it appears that in Ubuntu releases that have Kernel 6.11, users may still be stumbling on this bugreport, precisely because ubuntu is incorrectly using `ConditionPathExists=/dev/vmbus/hv_fcopy` with the new `hv_fcopy_uio_daemon`. IMO, for now it might make sense to just set ConditionPathExists= on that new path, specifically on these newer kernels. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766300 Title: hv-fcopy-daemon service fails to start if /dev/vmbus/hv_fcopy doesn't exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766300/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
