Public bug reported:

Issue description: Hyper-V daemons fail to start after disable/re-enable
VM integration services.

Platform: host independent
Affected daemons - KVP, FCOPY and VSS.

Distribution name and release: Ubuntu 16.04, Ubuntu 17.04
Kernel version: 4.11.0-rc7-next-20170421 (for Ubuntu 16.04), 4.10.0-19-generic 
(for Ubuntu 17.04)

Repro rate: 100%

Steps to reproduce:
1.      Start VM with Guest Services enabled (FCopy daemon starts automatically)
2.      Go to File > Settings > Integration Services, uncheck Guest Services 
and apply (FCopy daemon will stop at this point)
3.      Re-enable Guest Services from VM Settings (Fcopy daemon is not running).
This is the issue. systemd monitors for the service and if we have the hook for 
the Guest Service, it tries to start the daemon again.
systemd attempt to start any of the LIS daemons will fail, but manually 
executing the daemon binary, it will start the daemon.

Additional Info:
- the steps above can be repro'd with KVP / Data Exchange integration service 
as well.
- Manually starting hv_fcopy_daemon works fine.
- other distros (RHEL) does not have this behavior, the LIS daemons are started 
automatically by systemd once we re-enable the integration service.

On the upstream kernel and the upstream hv daemons, these messages are recorded 
in syslog, once we re-enable the Guest service:
HV_FCOPY: pread failed: Bad file descriptor
systemd[1]: hv-fcopy-daemon.service: Main process exited, code=exited, 
status=1/FAILURE
systemd[1]: hv-fcopy-daemon.service: Unit entered failed state.
systemd[1]: hv-fcopy-daemon.service: Failed with result 'exit-code'.

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: Confirmed


** Tags: hyper-v

** Changed in: linux (Ubuntu)
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701222

Title:
  [Hyper-V] LIS daemons fail to start after disable/re-enable VM
  integration services

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to