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 this case:
Launch "Hyper-V Manager" -> Right-Click Virtual Machine -> "Settings..." ->
"Integration Services" -> Make sure "Guest Services" checkbox is Enabled)
- If the VM is already running, restart the VM, or you can run `systemctl start
hv_fcopy_daemon`.
But I noticed when I installed my own Ubuntu 20.04, 22.04. 24.04 test
machines on Windows 11, it appears that the prior mentioned "Guest
services" checkbox is *disabled* by default after using either "New..."
or "Quick Create..." when creating any virtual machine in latest Hyper-V
Manager.
This appears to be both the source of confusion for users and the
intended design according to microsoft's documentation, therefore
according to Microsoft, the ConditionPathExists is definitely needed:
Because those paths are dynamically craeted and destroyed whenever the
corresponding kernel module is inserted/removed (
`/dev/vmbus/{hv_kvp,hv_vss,hv_fcopy}` )
--
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
