We haven't seen it in Xenial, but we managed to reproduce it back to the
daily Bionic build from the 2nd of March. We haven't tested Bionic daily
builds before the 2nd of March, nor did I try to reproduce it on Zesty
or or Artful.
--
You received this bug notification because you are a member of
I have opened a different bug for the first issue:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779640
Regarding the second issue, as mentioned in comment #13, the tested
kernels did not exhibit issue #2.
** Description changed:
While testing Bionic daily build with kernel 4.15.0-20-g
I have tested this on kernel 4.15.0-24.26 and linux-cloud-tools
4.15.0-24.26 and the issue persists.
--
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/1779640
Title:
[Hyper-V] KVP daemon cr
** Package changed: linux-azure (Ubuntu) => linux (Ubuntu)
--
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/1779640
Title:
[Hyper-V] KVP daemon crashes at startup
Status in linux package
Public bug reported:
While testing Bionic daily build with kernel 4.15.0-20-generic we saw
the following issue with the KVP daemon:
KVP daemon crashes after approximatively 2 minutes of uptime and it enters in a
failed state. The daemon can be manually started and it enters back in active
(runn
Regarding comment #11:
I have tested both kernels provided with the following results:
- 4.14 Bionic kernel (4.14.0-16-generic) does NOT exhibit issue #2
(missing files), but it does exhibit issue #1 (KVP daemon failure after
boot). Linux-cloud-tools version installed is 4.14.0-16.19.
- 4.15 Bion
I have tested Bionic with kernel 4.15.0-22-generic, linux-cloud-
tools-4.15.0-22.24 and linux-tools-4.15.0-22.24 and both issues still
occur.
While testing the above mentioned kernel, I saw the following behavior:
1. Right after booting the system the KVP daemon reports it is active
(running). Th
I tested back to the daily build from 2nd of March and I can confirm the
second issue (regarding the binaries path), but not the first one
(regarding the daemon crash). On the build from the 2nd of March the
linux-tools and linux-cloud-tools version is 4.15.0-10.11
--
You received this bug notifi
Public bug reported:
While testing Bionic daily build with kernel 4.15.0-20-generic we saw
that there are 2 issues with the KVP daemon:
1. KVP daemon crashes after approximatively 2 minutes of uptime and it enters
in a failed state. The daemon can be manually started and it enters back in
activ
Public bug reported:
Issue description: Memory demand increases very fast up to the maximum
available memory, call traces show up in /var/log/syslog, the VM becomes
unresponsive during the memory consumption, but it becomes responsive
right after stress-ng ends its execution, therefore we can say
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:
http:/
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.
https://
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. Re-enablin
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 mainli
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 re
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.
https://bugs.launchpad
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 subscrib
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 VM
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 VM
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
inte
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
inte
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 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
int
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 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 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 disab
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:
[Hy
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 ar
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
29 matches
Mail list logo
