According to this MS Documentation: https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/reference/integration-services
The hv_fcopy_daemon have a low impact on VM. The role of this daemon isn't necessary to a Azure VM, as you will not use it to copy files from/to VM (This could be necessary if you are directly on Hyper-V Console )
Looking into debian sources: https://sources.debian.org/src/linux/5.0.2-1~exp1/debian/hyperv-daemons.hv-fcopy-daemon.service/
You will see that a different condition exist to run this service daemon: ConditionPathExists=/dev/vmbus/hv_fcopy
So just add this extra condition to ubuntu service description on /lib/systemd/system/hv-fcopy-daemon.service
Restart your VM and you will see it is no more degraded.
According to this MS Documentation: /docs.microsoft .com/en- us/virtualizati on/hyper- v-on-windows/ reference/ integration- services
https:/
The hv_fcopy_daemon have a low impact on VM.
The role of this daemon isn't necessary to a Azure VM, as you will not use it to copy files from/to VM (This could be necessary if you are directly on Hyper-V Console )
Looking into debian sources: /sources. debian. org/src/ linux/5. 0.2-1~exp1/ debian/ hyperv- daemons. hv-fcopy- daemon. service/
https:/
You will see that a different condition exist to run this service daemon: ists=/dev/ vmbus/hv_ fcopy
ConditionPathEx
So just add this extra condition to ubuntu service description on system/ hv-fcopy- daemon. service
/lib/systemd/
Restart your VM and you will see it is no more degraded.