I have tested the kernel provided with commit ef754413085f5 and the bug persists. The daemons do not stop if the integration services are being disabled.
The kernel provided in comment #36 was not affected by the bug. That was the first good commit. Regarding comment #27, the kernel tested was reported as bad (the daemon still remains running after the integration service is being disabled). Just to make sure we got this right, there are 2 issues right now: 1. The daemons do not stop if the integration service is being disabled, they remain running in the process list, but are not functional. This issue is present in the kernels tested up to 4.4.0-2. This issue is NOT present in kernel 4.4.0-3, here the daemons processes do stop if the integration service is disabled. Regarding this issue, the kernel provided in comment #36 is a good kernel. 2. The daemons do not automatically start after the integration service is disabled and then enabled again. This is the initial bug discovered in 16.04 and 17.04. Kernel 4.4.0-3 does not have the first issue, but it has the second one. -- 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
