KVM on 16.04.3 throws an error
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
The Ubuntu-power-systems project |
Fix Released
|
Critical
|
Canonical Kernel Team | ||
linux (Ubuntu) |
Fix Released
|
Critical
|
Ubuntu on IBM Power Systems Bug Triage | ||
Xenial |
Fix Released
|
Critical
|
Unassigned | ||
Zesty |
Invalid
|
Critical
|
Unassigned | ||
qemu (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Problem Description
=======
KVM on Ubuntu 16.04.3 throws an error when used
---uname output---
Linux bastion-1 4.4.0-89-generic #112-Ubuntu SMP Mon Jul 31 19:37:08 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
Machine Type = 8348-21C Habanero
---Steps to Reproduce---
Install 16.04.3
install KVM like:
apt-get install libvirt-bin qemu qemu-slof qemu-system qemu-utils
then exit and log back in so virsh will work without sudo
then run my spawn script
$ cat spawn.sh
#!/bin/bash
img=$1
qemu-system-ppc64 \
-machine pseries,
-display none -nographic \
-net nic -net user \
-drive "file=$img"
with a freshly downloaded ubuntu cloud image
sudo ./spawn.sh xenial-
And I get nothing on the output.
and errors in dmesg
ubuntu@bastion-1:~$ [ 340.180295] Facility 'TM' unavailable, exception at 0xd0000000148b7f10, MSR=90000000000
[ 340.180399] Oops: Unexpected facility unavailable exception, sig: 6 [#1]
[ 340.180513] SMP NR_CPUS=2048 NUMA PowerNV
[ 340.180547] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_
[ 340.181331] CPU: 46 PID: 5252 Comm: qemu-system-ppc Not tainted 4.4.0-89-generic #112-Ubuntu
[ 340.181382] task: c000001e34c30b50 ti: c000001e34ce4000 task.ti: c000001e34ce4000
[ 340.181432] NIP: d0000000148b7f10 LR: d000000014822a14 CTR: d0000000148b7e40
[ 340.181475] REGS: c000001e34ce77b0 TRAP: 0f60 Not tainted (4.4.0-89-generic)
[ 340.181519] MSR: 9000000000009033 <SF,HV,
[ 340.181629] CFAR: d0000000148b7ea4 SOFTE: 1
GPR00: d000000014822a14 c000001e34ce7a30 d0000000148cc018 c000001e37bc0000
GPR04: c000001db9ac0000 c000001e34ce7bc0 0000000000000000 0000000000000000
GPR08: 0000000000000001 c000001e34c30b50 0000000000000001 d0000000148278f8
GPR12: d0000000148b7e40 c00000000fb5b500 0000000000000000 000000000000001f
GPR16: 00003fff91c30000 0000000000800000 00003fffa8e34390 00003fff9242f200
GPR20: 00003fff92430010 000001001de5c030 00003fff9242eb60 00000000100c1ff0
GPR24: 00003fffc91fe990 00003fff91c10028 0000000000000000 c000001e37bc0000
GPR28: 0000000000000000 c000001db9ac0000 c000001e37bc0000 c000001db9ac0000
[ 340.182315] NIP [d0000000148b7f10] kvmppc_
[ 340.182357] LR [d000000014822a14] kvmppc_
[ 340.182394] Call Trace:
[ 340.182413] [c000001e34ce7a30] [c000001e34ce7ab0] 0xc000001e34ce7ab0 (unreliable)
[ 340.182468] [c000001e34ce7b70] [d000000014822a14] kvmppc_
[ 340.182522] [c000001e34ce7ba0] [d00000001481f674] kvm_arch_
[ 340.182581] [c000001e34ce7be0] [d000000014813918] kvm_vcpu_
[ 340.182634] [c000001e34ce7d40] [c0000000002fffa0] do_vfs_
[ 340.182678] [c000001e34ce7de0] [c0000000003003c4] SyS_ioctl+0xd4/0xf0
[ 340.182723] [c000001e34ce7e30] [c000000000009204] system_
[ 340.182766] Instruction dump:
[ 340.182788] e92d02a0 e9290a50 e9290108 792a07e3 41820058 e92d02a0 e9290a50 e9290108
[ 340.182863] 7927e8a4 78e71f87 40820ed8 e92d02a0 <7d4022a6> f9490ee8 e92d02a0 7d4122a6
[ 340.182938] ---[ end trace bc5080cb7d18f102 ]---
[ 340.276202]
This was with the latest ubuntu cloud image. I get the same thing when trying to use virt-install with an ISO image.
I have no way of loading a KVM on 16.04.3
== Comment: #2 - Jason M. Furmanek <email address hidden> - 2017-08-09 17:42:34 ==
I reinstalled with the HWE kernel (4.10).
I can install VM and see the console and eveything seems fine.
== Comment: #3 - Jason M. Furmanek <email address hidden> - 2017-08-09 17:44:03 ==
I had another system at 16.04.2 (4.4) and updated that one to the latest and it hit the same issue as above.
No qemu or libvirt updates were applied. Just kernel updates and a handful of other stuff.
Seems this issue is specific to the latest kernel
old version worked:
Linux fs7 4.4.0-83-generic #106
new version did not:
Linux fs7 4.4.0-89-generic #112-Ubuntu
== Comment: #4 - Gustavo Bueno Romero <email address hidden> - 2017-08-09 20:26:42 ==
Looks like 46a704f8409f79f
[gromero@localhost ubuntu-xenial]$ git remote -vv
origin git://kernel.
origin git://kernel.
[gromero@localhost ubuntu-xenial]$ git log Ubuntu-
a97e978 KVM: PPC: Book3S HV: Preserve userspace HTM state properly
[gromero@localhost ubuntu-xenial]$ git log Ubuntu-
[gromero@localhost ubuntu-xenial]$ git tag --contains a97e978574f41ff
Ubuntu-4.4.0-88.111
Ubuntu-4.4.0-89.112
Ubuntu-
Ubuntu-
Ubuntu-
Ubuntu-
So
https:/
tags: | added: architecture-ppc64le bugnameltc-157436 severity-critical targetmilestone-inin--- |
Changed in ubuntu: | |
assignee: | nobody → Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) |
affects: | ubuntu → linux (Ubuntu) |
Changed in ubuntu-power-systems: | |
importance: | Undecided → Critical |
no longer affects: | qemu |
Changed in ubuntu-power-systems: | |
assignee: | nobody → Canonical Server Team (canonical-server) |
Changed in linux (Ubuntu): | |
importance: | Undecided → Critical |
Changed in linux (Ubuntu Xenial): | |
status: | New → In Progress |
Changed in linux (Ubuntu Zesty): | |
status: | New → In Progress |
Changed in qemu (Ubuntu Xenial): | |
status: | New → Won't Fix |
no longer affects: | qemu (Ubuntu Zesty) |
no longer affects: | qemu (Ubuntu Xenial) |
Changed in linux (Ubuntu Xenial): | |
importance: | Undecided → Critical |
Changed in linux (Ubuntu Zesty): | |
importance: | Undecided → Critical |
Changed in linux (Ubuntu): | |
status: | New → In Progress |
Changed in linux (Ubuntu Xenial): | |
assignee: | nobody → Joseph Salisbury (jsalisbury) |
Changed in linux (Ubuntu Zesty): | |
assignee: | nobody → Joseph Salisbury (jsalisbury) |
Changed in ubuntu-power-systems: | |
status: | New → In Progress |
Changed in linux (Ubuntu Zesty): | |
status: | In Progress → Invalid |
tags: |
added: targetmilestone-inin16043 removed: targetmilestone-inin--- |
Changed in linux (Ubuntu Xenial): | |
status: | Fix Committed → Fix Released |
Changed in ubuntu-power-systems: | |
status: | Fix Released → Fix Committed |
tags: | added: cscc |
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 here)
3. the conclusion was that nothing can/has-to be done for qemu [1]
4. there was no way to fix the initial 16.04.0 iso, but that was considered ok since 16.04.2 worked
Mapping to this bug here it seems that a further update to 4.4 might have broken it "again" as identified by Gustavo in in this report.
I added all this to complete the context for everybody else, but for now qemu stays at won't fix for the reasons and assumptions haven't changed since our last check on this issue.
On the kernel surely if the identified two patches really need to go together a fix might be needed, but that is for the kernel Team to evaluate.
[1]: https:/ /bugs.launchpad .net/ubuntu/ +source/ qemu/+bug/ 1664622/ comments/ 27