Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: linux-azure (Ubuntu Artful)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: linux (Ubuntu Artful)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
@ebonato
in focal, the service fails because of that condition:
$ systemctl status hv-fcopy-daemon.service
● hv-fcopy-daemon.service - Hyper-V File Copy Protocol Daemon
Loaded: loaded (/lib/systemd/system/hv-fcopy-daemon.service; enabled;
vendor preset: enabled)
Active: inactive (dead)
** Tags added: cscc
--
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
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
Hi Folks,
I can confirm that bug still on Latest kernel 4.18.
~$ sudo dpkg -l | grep azure
ii linux-azure 4.18.0.1013.12
amd64Complete Linux kernel for Azure systems.
ii linux-azure-cloud-tools-4.15.0-1036 4.15.0-1036.38
** Tags added: id-5ade0192d153661ecfa15e63
--
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 notif
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Trus
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[