I would reopen and add Affects: Bionic but I don't see a way to do so.
--
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/1701222
Title:
[Hyper-V] LIS daemons fail to start after
please reopen if this is still an issue
** Changed in: systemd (Ubuntu)
Status: New => Won't Fix
--
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/1701222
Title:
[Hyper-V] LIS
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Incomplete
** Changed in: linux (Ubuntu Zesty)
Status: In Progress => Incomplete
** Changed in: linux (Ubuntu Artful)
Status: In Progress => Incomplete
** Changed in: linux (Ubuntu)
Status: In Progress =>
Since it requires control of the host, this cannot be done in Azure.
Control of the host is rather restricted there.
--
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/1701222
Title:
The unit entered a failed state, and thus would not automatically started until
failed state clears.
Why does bouncing of the services result in the daemon exiting with an error
condition? Should that particular exit code result in a graceful shutdown of
the service, such that the unit can be
It is possible. I've added a systemd bug task.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
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/1701222
I have tested the proposed kernel, but with this version both bugs are
showing up.
Could it be that the bug is not in the kernel, but in systemd?
Below is a comparison of the strace command ran on RHEL 7.3 and Ubuntu 16.04.1,
when trying to re-enable the Data Exchange integration service:
Can you test a 3.19 based kernel:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/13366909
** Also affects: linux (Ubuntu Artful)
Importance: High
Assignee: Joseph Salisbury (jsalisbury)
Status: In Progress
--
You received this bug notification because you
I have tested Xenial back to 4.2.0-16 from here: https://launchpad.net
/~canonical-kernel-team/+archive/ubuntu/ppa/+build/8099555
The second issue is still present.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Thanks for the update. So the mainline kernel still has the second
issue and 4.4.0-2.16 also has the second issue. Presumably all the
kernel version in between these two also have the second issue.
To determine if the second issue is a regression, we should test further
back from 4.4.0-2.
Can
I have tested 4.4.0-2.16 from here:
https://launchpad.net/ubuntu/+source/linux/4.4.0-2.16/+build/8908724
In this case, the daemon remains running when the integration service is
being disabled. systemctl status shows the daemon running and active,
but the daemon is not working actually.
Ok, I reread the bug description and more importantly, comment #15. So
it sounds like the first issue has been fixed in all kernels since
kernel version 4.4.0-2, but that is when the second issue was
introduced. If that is the case, we should focus on the second issue,
where the daemons do not
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
Thanks for the clarification. Since there are two issues, we should
probably focus on one at a time. The test kernel posted in comment #36
sounds like it fixes the first issue, so lets handle that one first.
I'll ping the upstream patch author for that commit and get some
feedback. Before
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
Thanks for testing. We told the bisect commit 74caead was good per
comment #27, which led us down the wrong bisect path.
I can build the next test kernel after telling the bisect commit 74caead
was actually bad.
Before doing that, the last kernel before that we said was good was in
comment #17.
I have tested both kernels provided, and both exhibit the bug. In both
cases the daemon does not stop after the integration services is being
disabled.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Thanks for testing. To confirm we provided the correct input to the
bisect, can you test the following two kernels and confirm that they
were good or bad:
Commit 332e564(Should be BAD and exhibit bug):
http://kernel.ubuntu.com/~jsalisbury/lp1701222/332e564/
Commit 74caead(Should be GOOD and not
I have tested the above kernel. The daemon stops if the integration
service is being disabled, but does not automatically start after the
service is being enabled again (same behavior as 4.4.0-3).
--
You received this bug notification because you are a member of Kernel
Packages, which is
Xenial commit 332e5643b07(Mainline commit b521549a09ddfac) was reported
as the first bad commit. I built a Xenial test kernel with this commit
reverted. It can be downloaded from:
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1701222
Can you test that kernel
I have tested the above kernel build. The issue still occurs.
--
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/1701222
Title:
[Hyper-V] LIS daemons fail to start after disable/re-enable
I built the next test kernel, up to the following commit:
332e5643b07ad6f24fd86290b081fc43a2ece778
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1701222
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on
I have tested the above kernel build. The issue still occurs.
--
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/1701222
Title:
[Hyper-V] LIS daemons fail to start after disable/re-enable
I built the next test kernel, up to the following commit:
0cff5d394aaba1d6c75fe0036981b7a93a1c4b36
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1701222
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on
Tested the above kernel build. The issue still occurs.
--
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/1701222
Title:
[Hyper-V] LIS daemons fail to start after disable/re-enable VM
I built the next test kernel, up to the following commit:
2d796f537d26e54a7fdf87632f9b8ee811759bc9
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1701222
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on
Tested the above kernel build. The issue still occurs.
--
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/1701222
Title:
[Hyper-V] LIS daemons fail to start after disable/re-enable VM
I built the next test kernel, up to the following commit:
be636eeda2290c65f3283ee3bdc149a5d205a798
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1701222
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on
I have tested the kernel above. The daemon still remains running after
the integration service is being disabled.
--
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/1701222
Title:
[Hyper-V]
I built the next test kernel, up to the following commit:
74caeadc074b099b80abca86a19ab95003ca294e
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1701222
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on
I have tested the kernel above. The issue still occurs.
--
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/1701222
Title:
[Hyper-V] LIS daemons fail to start after disable/re-enable VM
I built the next test kernel, up to the following commit:
49594cb78e0decefdd60bf462a25d7f50e8d5239
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1701222
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on
I have tested the kernel provided. The issue still occurs.
--
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/1701222
Title:
[Hyper-V] LIS daemons fail to start after disable/re-enable VM
I built the next test kernel, up to the following commit:
501faf881377dc38998fe8603ee1767d61883cfb
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1701222
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on
I have tested the kernel provided. The issue still occurs.
--
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/1701222
Title:
[Hyper-V] LIS daemons fail to start after disable/re-enable VM
I built the next test kernel, up to the following commit:
c0e46ba65adcd94a49c2d66bb600e66a56ace491
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1701222
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on
I have tested the kernel provided in the link above. The issue still
occurs.
--
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/1701222
Title:
[Hyper-V] LIS daemons fail to start after
I built the next test kernel, up to the following commit:
c6f73b9f6bb9c8bf8e5beb31bbe4e18cb8c4b6d4
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1701222
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on
I have tested the kernel provided in the link above. The daemons do not
stop when the integration services are disabled.
--
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/1701222
Title:
I started a kernel bisect between Ubuntu 4.4.0-2 and Ubuntu 4.4.0-3. The
kernel bisect will require testing of about 7-10 test kernels.
I built the first test kernel, up to the following commit:
ef754413085f5ab7688989585f9223fec0ed7870
The test kernel can be downloaded from:
** Changed in: linux (Ubuntu Xenial)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Zesty)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Kernel
I have checked back to 4.2.0-16. It seems that 4.4.0-2 is the last
kernel where the daemons remain running even if integration services are
being disabled. Starting with 4.4.0-3 the daemons stop if the
integration services are disabled, but do not automatically start if the
integrations services
Let's try further back, can you test 4.4.0-10:
https://launchpad.net/ubuntu/+source/linux/4.4.0-10.25/+build/9287900
--
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/1701222
Title:
The same happens on 4.4.0-20 kernel.
--
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/1701222
Title:
[Hyper-V] LIS daemons fail to start after disable/re-enable VM
integration services
Can you see if the issue was happening back in 4.4.0-20:
https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/ppa/+build/9583414
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The same happens on 4.4.0-40 kernel, I think this goes with comment #6.
--
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/1701222
Title:
[Hyper-V] LIS daemons fail to start after
For example, here is an early 4.4.0-40 kernel:
https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/ppa/+build/10948005
--
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/1701222
Would it be possible to test some of the early 16.04 kernels to try and
figure out a last good kernel and first bad kernel?
--
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/1701222
Title:
>From what I was just told, no, they don't know when this started
happening.
--
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/1701222
Title:
[Hyper-V] LIS daemons fail to start after
Do you know the specific kernel version when this bug started happening
in 16.04? If not, we may have to test a few to narrow it down. All
16.04 kernels are available here:
https://launchpad.net/ubuntu/xenial/+source/linux
--
You received this bug notification because you are a member of
We verified anything between 14.04.0 and 15.10, the thing with those
releases is that even if we disable the Data Exchange integration
service, the KVP daemon remains running on the VM.
Only starting from 16.04 the KVP daemon stops when Data Exchange is disabled.
So 16.04 is the first version
Do we know which kernel version caused the regression? If so, I can
review the commits or perform a bisect if needed.
--
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/1701222
Title:
This is a regression, we did lots of work a year ago to ensure the
daemons handle bouncing integration services settings.
--
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/1701222
Title:
I took the v4.12 kernel and compiled the LIS daemons from those sources
as well.
Reloading the Data Exchange service, KVP will fail with the below message. This
is the same as initially reported, so nothing changed in the behavior.
Not sure on the regression part, only up to the point on
Also, do you know if this is a regression?
--
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/1701222
Title:
[Hyper-V] LIS daemons fail to start after disable/re-enable VM
integration
Hi Chris,
Can you give the 4.12 kernel a test:
] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Tags added: kernel-da-key
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** No longer
56 matches
Mail list logo
