** Tags added: cscc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1709784
Title:
KVM on 16.04.3 throws an error
To manage notifications about this bug go to:
As this ticket only relates to Xenial and 4.4 kernel, marking as "Fix
Released".
** Changed in: ubuntu-power-systems
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
** Changed in: ubuntu-power-systems
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1709784
Title:
KVM on 16.04.3 throws an error
To manage notifications
** Changed in: linux (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1709784
Title:
KVM on 16.04.3 throws an error
To manage
Based on comments above, moving to "Fix Released". If this issue re-
occurs, please update with a new comment.
** Changed in: ubuntu-power-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@furmanek, Thanks for testing.
@Breno, Commit e47057151 was not applied to Xenial. It did not apply
cleanly because the following commit is already in Xenial as of
4.4.0-96(As Xenial SHA1 25e0720):
17d381054b1d6f4adc3db623b2066fff41b4dc1a
("KVM: PPC: Book3S HV: Reload HTM registers explicitly")
** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin16043
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1709784
Title:
KVM on 16.04.3 throws an error
To manage
Christian,
I am looking at 4.4 git repository and version -93 contains exactly the
problem described here, it contains the commit#
46a704f8409f79fd66567ad3f8a7304830a84293 (as
a97e978574f41ffcf1813c180aba2772d46fbb5b), but it does not include
commit# e47057151422a67ce08747176fa21cb3b526a2c9.
Confirmed workaround for OpenStack Ocata on Xenial:
### Nova compute host [hwe-edge kernel via MAAS]
ubuntu@node-mawhile:~$ uname -a
Linux node-mawhile 4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:18
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
### Nova guest [stock xenial ppc64el
Affects OpenStack on ppc64el. Marking other bug as duplicate (it has
logs/attachments fyi).
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1716469
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
There seems to be an update-regression in Artful.
Booting a recent Artful guest now again also throws:
[485006.367929] Facility 'TM' unavailable, exception at 0xd00021617f10,
MSR=90009033
[485006.367943] Oops: Unexpected facility unavailable exception, sig: 6 [#14]
[485006.367945]
@furmanek, The fix is in the Ubuntu-4.4.0-94 kernel, which is the
current -proposed kernel.
Would it be possible for you to test the proposed kernel and post back if it
resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.
**
I ran into this issue as well, and confirmed with the kernel built above
(http://kernel.ubuntu.com/~jsalisbury/lp1709784/xenial/) that things now
work again. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
There is commit 17d381054b1d6f4adc3db623b2066fff41b4dc1a ("KVM: PPC: Book3S HV:
Reload HTM registers explicitly") from
v4.4.80 series that is in Xenial master-next. I built a master-next test
kernel, which can be downloaded from:
Xenial: http://kernel.ubuntu.com/~jsalisbury/lp1709784/xenial/
** Changed in: linux (Ubuntu Zesty)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1709784
Title:
KVM on 16.04.3 throws an error
To manage notifications about
Thanks for testing. I'll submit SRU requests for both Zesty and Xenial.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1709784
Title:
KVM on 16.04.3 throws an error
To manage notifications about
I also tested xenial GA kernel:
sid ➜ ~ sudo uname -a
Linux sid 4.4.0-89-generic #112~lp1709784 SMP Thu Aug 10 19:39:43 UTC 2017
ppc64le ppc64le ppc64le GNU/Linux
sid ➜ ~ sudo virsh list
IdName State
2
I just tested zesty kernel and it worked fine:
# uname -a
Linux sid 4.10.0-30-generic #34~lp1709784 SMP Thu Aug 10 20:01:17 UTC 2017
ppc64le ppc64le ppc64le GNU/Linux
# sudo virsh list
IdName
** Changed in: ubuntu-power-systems
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1709784
Title:
KVM on 16.04.3 throws an error
To manage notifications about this
I built test kernels with a pick of commit e47057151422. The test
kernels can be downloaded from:
Xenial: http://kernel.ubuntu.com/~jsalisbury/lp1709784/xenial/
Zesty: http://kernel.ubuntu.com/~jsalisbury/lp1709784/zesty/
Can you test these kernels and see if they resolve this bug?
Thanks in
** Also affects: qemu (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
** Changed in: linux (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1709784
Title:
KVM on 16.04.3 throws an error
To manage notifications about this
Thanks Christian. Reassigning to kernel team.
** Changed in: ubuntu-power-systems
Assignee: Canonical Server Team (canonical-server) => Canonical Kernel
Team (canonical-kernel-team)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi,
there was a related case in bug 1664622.
The TL;DR of this was:
1. even with all qemu patches identified by IBM and upstream while working on
this the issue still showed up.
2. newer kernels (>=4.8, but also newer 4.4 kernels than those on the release
itself worked - that matches the report
** Also affects: qemu
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: qemu
** Changed in: ubuntu-power-systems
Assignee: (unassigned) => Canonical Server Team (canonical-server)
--
You received
** Also affects: ubuntu-power-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-power-systems
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
26 matches
Mail list logo
