The /dev/vmbus/hv_fcopy device won't be created unless the 'Guest
Service Interface' integration service is enabled in the VM.  It isn't
enabled by default.  This can be checked with the following PowerShell
command on the Hyper-V server:

  Get-VMIntegrationService 'Guest Service Interface' -VMName FOO

where 'FOO' is the name of the virtual machine.  Look for the 'Enabled'
column in the output.  If it says 'False', it can be enabled using the
following PowerShell command:

  Enable-VMIntegrationService 'Guest Service Interface' -VMName FOO

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1614618

Title:
  hv-fcopy-daemon.service system failed start

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  I booted a  yakkety system on azure, and saw

  $ systemctl status hv-fcopy-daemon.service --no-pager --full 
  ● hv-fcopy-daemon.service - Hyper-V File Copy Protocol Daemon
     Loaded: loaded (/lib/systemd/system/hv-fcopy-daemon.service; enabled; 
vendor preset: enabled)
     Active: failed (Result: exit-code) since Thu 2016-08-18 16:01:51 UTC; 
32min ago
   Main PID: 2291 (code=exited, status=1/FAILURE)

  Aug 18 16:01:51 ubuntu systemd[1]: Started Hyper-V File Copy Protocol Daemon.
  Aug 18 16:01:51 ubuntu systemd[1]: hv-fcopy-daemon.service: Main process 
exited, code=exited, status=1/FAILURE
  Aug 18 16:01:51 ubuntu systemd[1]: hv-fcopy-daemon.service: Unit entered 
failed state.
  Aug 18 16:01:51 ubuntu systemd[1]: hv-fcopy-daemon.service: Failed with 
result 'exit-code'.

  Also, random information but surprising none the less:
  $ systemd-analyze 
  Startup finished in 5min 14.289s (kernel) + 1min 43.164s (userspace) = 6min 
57.454s

  $ systemd-analyze critical-chain 
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  graphical.target @1min 43.124s
  └─multi-user.target @1min 43.124s
    └─ephemeral-disk-warning.service @1min 42.888s +235ms
      └─cloud-final.service @1min 39.480s +3.407s
        └─cloud-config.service @1min 2.517s +36.961s
          └─network-online.target @1min 2.464s
            └─cloud-init.service @35.453s +26.967s
              └─networking.service @32.799s +2.622s
                └─network-pre.target @32.766s
                  └─cloud-init-local.service @12.044s +20.690s
                    └─local-fs.target @12.030s
                      └─mnt.mount @1min 29.655s
                        └─dev-sdb1.device @1min 8.310s

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-cloud-tools-common 4.4.0-34.53
  ProcVersionSignature: User Name 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  AlsaDevices:
   total 0
   crw-rw---- 1 root audio 116,  1 Aug 18 16:01 seq
   crw-rw---- 1 root audio 116, 33 Aug 18 16:01 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Aug 18 16:31:54 2016
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  PackageArchitecture: all
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=314ea127-227e-4b64-b5b4-d70ab0fb7eb7 ro console=tty1 console=ttyS0 
earlyprintk=ttyS0 rootdelay=300
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware                            1.160
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/23/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090006
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1614618/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to