I have tested the mainline kernel provided with the compiled daemons form linux-next. In this case, the daemons do stop when the integration service is being disabled, but do not automatically start after we re- enable the integration service. Manually starting the service works fine. So the mainline is still affected by the second issue.
-- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
