So I thought that was a bit weird, so look below:
First, I wanted to see what was installed:
ubuntu@fesenkov:~$ apt-cache policy qemu-system-ppc*
qemu-system-ppcemb:
Installed: (none)
Candidate: (none)
Version table:
qemu-system-ppc: ###this is what I had installed, and I'm not entirely sure why
it was down-rev. I presume this is the package you mean... I did a dist-upgrade
on the node, so I'm not entirely sure why it was skipped before. Oh well, it's
upgraded now, I'll re-try.
Installed: 1:2.5+dfsg-5ubuntu10.11
Candidate: 1:2.5+dfsg-5ubuntu10.13
Version table:
1:2.5+dfsg-5ubuntu10.13 500
500 http://ports.ubuntu.com/ubuntu-ports xenial-proposed/main ppc64el
Packages
*** 1:2.5+dfsg-5ubuntu10.11 500
500 http://ports.ubuntu.com/ubuntu-ports xenial-updates/main ppc64el
Packages
500 http://ports.ubuntu.com/ubuntu-ports xenial-security/main ppc64el
Packages
100 /var/lib/dpkg/status
1:2.5+dfsg-5ubuntu10 500
500 http://ports.ubuntu.com/ubuntu-ports xenial/main ppc64el Packages
qemu-system-ppc64: ### I expected to see this installed, I didn't realize it
was now just a blank pointer to qemu-system-ppc
Installed: (none)
Candidate: (none)
Version table:
ubuntu@fesenkov:~$ sudo apt-get install qemu-system-ppc64
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'qemu-system-ppc' instead of 'qemu-system-ppc64'
Suggested packages:
samba vde2 openbios-ppc openhackware
The following packages will be upgraded:
qemu-system-ppc
1 upgraded, 0 newly installed, 0 to remove and 56 not upgraded.
Need to get 2,431 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://ports.ubuntu.com/ubuntu-ports xenial-proposed/main ppc64el
qemu-system-ppc ppc64el 1:2.5+dfsg-5ubuntu10.13 [2,431 kB]
Fetched 2,431 kB in 0s (12.0 MB/s)
(Reading database ... 79950 files and directories currently installed.)
Preparing to unpack .../qemu-system-ppc_1%3a2.5+dfsg-5ubuntu10.13_ppc64el.deb
...
Unpacking qemu-system-ppc (1:2.5+dfsg-5ubuntu10.13) over
(1:2.5+dfsg-5ubuntu10.11) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up qemu-system-ppc (1:2.5+dfsg-5ubuntu10.13) ...
So now I'll re-try as qemu-system-ppc is updated.
--
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/1656112
Title:
Power S822LC (8335-GTB) fails KVM guest cert test with kvm_init_vcpu
failed: Invalid argument
Status in linux package in Ubuntu:
Confirmed
Status in qemu package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Confirmed
Status in qemu source package in Xenial:
Fix Committed
Bug description:
[Impact]
* Some newer Power8 derivates fail to work correctly e.g. Power S822LC
(8335-GTB)
* This is a toleration change (no exploitation) for those HW releases
following the SRU policy of "For Long Term Support releases we
regularly want to enable new hardware. Such changes are appropriate
provided that we can ensure not to affect upgrades on existing
hardware."
* Without the Fix that hardware won't run Xenial guests under current
Xenials Qemu version
* The fix lets processors that support it run in PowerISA 2.07
compatibility mode (plus a few no-op changes as backport
dependencies)
[Test Case]
* Run a Xenial Guest in KVM on one of the specific HW revisions being
affected.
[Regression Potential]
* I'd rate the potential to regress low for powerpc and next to
impossible for other architectures, reasons:
* Changes are PPC only, so fallout should be contained to that
* Patches and were created by IBM and in Upstream qemu since 2.6
* The effective change is rather small, only allow to saner cpu model
versions (drop some HW dev trash that was left) and add the new types.
[Other Info]
* Needed for certifying this Hardware for Ubuntu
Upon running the virtualization test from the certification test
suite, the kvm guest test fails with the following error:
kvm_init_vcpu failed: Invalid argument
This same test works on multiple other IBM Power 8 and Openpower
servers. kvm-ok tells us that kvm virtualization is supported. I have
tried with SMT enabled and disabled. I have tried the latest cloud
image as well as previous onces we had saved. I have tried running the
qemu-system-ppc64 command found below manually with the same error.
The full output from the test is as follows:
Executing KVM Test
DEBUG:root:Starting KVM Test
DEBUG:root:Cloud image location specified:
http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img.
DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from
http://10.1.10.2
DEBUG:root:Creating cloud user-data
DEBUG:root:Creating cloud meta-data
I: -input-charset not specified, using utf-8 (detected in locale settings)
Total translation table size: 0
Total rockridge attributes bytes: 331
Total directory bytes: 0
Path table size(bytes): 10
Max brk space used 0
183 extents written (0 MB)
DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img
DEBUG:root:Attaching Cloud config disk
DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic
-net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::2222-:22
-enable-kvm -machine pseries,usb=off -cpu POWER8 -drive
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive
file=seed.iso,if=virtio
INFO:root:Storing VM console output in
/home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-59-generic 4.4.0-59.80
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic ppc64le
AlsaDevices:
total 0
crw-rw---- 1 root audio 116, 1 Jan 12 22:18 seq
crw-rw---- 1 root audio 116, 33 Jan 12 22:18 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: ppc64el
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
Date: Thu Jan 12 22:45:34 2017
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102
Pro
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard
and Mouse
Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
PciMultimedia:
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 astdrmfb
ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1
ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017
ProcLocks:
1: POSIX ADVISORY WRITE 3709 00:14:665 0 EOF
2: POSIX ADVISORY WRITE 3593 00:14:655 0 EOF
3: POSIX ADVISORY WRITE 1658 00:14:376 0 EOF
4: FLOCK ADVISORY WRITE 3560 00:14:637 0 EOF
5: POSIX ADVISORY WRITE 3571 00:14:640 0 EOF
ProcSwaps:
Filename Type Size Used Priority
/swap.img file 8388544 0 -1
ProcVersion: Linux version 4.4.0-59-generic (buildd@bos01-ppc64el-029) (gcc
version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #80-Ubuntu SMP Fri
Jan 6 17:35:59 UTC 2017
RelatedPackageVersions:
linux-restricted-modules-4.4.0-59-generic N/A
linux-backports-modules-4.4.0-59-generic N/A
linux-firmware 1.157.6
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
cpu_cores: Number of cores present = 20
cpu_coreson: Number of cores online = 20
cpu_dscr: DSCR is 0
cpu_freq:
min: 3.959 GHz (cpu 79)
max: 3.988 GHz (cpu 81)
avg: 3.974 GHz
cpu_runmode:
Could not retrieve current diagnostics mode,
No kernel interface to firmware
cpu_smt: SMT=8
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656112/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
