--- Comment From heinz-werner_se...@de.ibm.com 2019-04-29 03:46 EDT---
IBM Bugzilla status-> closed, Fix Released for all requested distros
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
--- Comment From pa...@de.ibm.com 2019-02-12 13:23 EDT---
(In reply to comment #22)
> Looks like this got pulled into mainline:
>
> $ git describe 2448a299ec416a80f699940a86f4a6d9a4f643b1
> v4.20-rc5-2-g2448a299ec41
>
> $ git describe 78b1a52e05c9db11d293342e8d6d8a230a04b4e7
>
--- Comment From pa...@de.ibm.com 2018-12-03 10:18 EDT---
Fixes available on the relevant Linux mailing lists. Connie posted a pull
request https://www.spinics.net/lists/kvm/msg175437.html some two months ago,
and pinged Michael last week. Hope the fixes will find their way into the
--- Comment From pa...@de.ibm.com 2018-08-31 05:28 EDT---
Colin, thanks for the input. Based on Christians realization, that your
hypervisor may have been 16.4 all along, and on the qemu version you stated, I
managed to reproduce the bug with upstream tag v2.5.0. From there I bisected to
--- Comment From cborn...@de.ibm.com 2018-08-30 11:27 EDT---
Ah ok. So you run an 18.04 guest under an 16.04 host?
Does the problem goes away with a newer QEMU? (e.g. from the cloud archive)
--
You received this bug notification because you are a member of Kernel
Packages, which is
--- Comment From pa...@de.ibm.com 2018-08-30 08:06 EDT---
I've tried to reproduce the issue but failed miserably. I installed a fresh
Ubuntu 18.04.1 made a cqow image essentially copying the filesystem for the
guest. That means I was running the 4.15.0-29-generic kernel (reported as
--- Comment From cborn...@de.ibm.com 2018-08-30 06:23 EDT---
Colin King,
it might also be a QEMU issue. Is there a chance to try a 16.04 host
instead of an 18.04 host?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
7 matches
Mail list logo
