ubuntu-kernel-tests

All 12 tests in kvm-unit-test failed (timeouted) on X s390x KVM

Bug #1822542 reported by Po-Hsu Lin on 2019-04-01

This bug affects 1 person

	Status	Importance	Assigned to
ubuntu-kernel-tests	Triaged	Undecided	Unassigned
linux (Ubuntu)	Incomplete	Undecided	Unassigned
Xenial	Incomplete	Undecided	Unassigned

Bug Description

I think this bug is just a place holder, as the nested KVM is out-of-scope especially on s390x

TESTNAME=selftest-setup TIMEOUT=90s ACCEL= ./s390x/run s390x/selftest.elf -smp 1 -append 'test 123'
FAIL selftest-setup (timeout; duration=90s)
TESTNAME=intercept TIMEOUT=90s ACCEL= ./s390x/run s390x/intercept.elf -smp 1
FAIL intercept (timeout; duration=90s)
TESTNAME=emulator TIMEOUT=90s ACCEL= ./s390x/run s390x/emulator.elf -smp 1
FAIL emulator (timeout; duration=90s)
TESTNAME=sieve TIMEOUT=600 ACCEL= ./s390x/run s390x/sieve.elf -smp 1
FAIL sieve (timeout; duration=600)
TESTNAME=sthyi TIMEOUT=90s ACCEL= ./s390x/run s390x/sthyi.elf -smp 1
FAIL sthyi (timeout; duration=90s)
TESTNAME=skey TIMEOUT=90s ACCEL= ./s390x/run s390x/skey.elf -smp 1
FAIL skey (timeout; duration=90s)
TESTNAME=diag10 TIMEOUT=90s ACCEL= ./s390x/run s390x/diag10.elf -smp 1
FAIL diag10 (timeout; duration=90s)
TESTNAME=pfmf TIMEOUT=90s ACCEL= ./s390x/run s390x/pfmf.elf -smp 1
FAIL pfmf (timeout; duration=90s)
TESTNAME=cmm TIMEOUT=90s ACCEL= ./s390x/run s390x/cmm.elf -smp 1
FAIL cmm (timeout; duration=90s)
TESTNAME=vector TIMEOUT=90s ACCEL= ./s390x/run s390x/vector.elf -smp 1
FAIL vector (timeout; duration=90s)
TESTNAME=gs TIMEOUT=90s ACCEL= ./s390x/run s390x/gs.elf -smp 1
FAIL gs (timeout; duration=90s)
TESTNAME=iep TIMEOUT=90s ACCEL= ./s390x/run s390x/iep.elf -smp 1
FAIL iep (timeout; duration=90s)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-145-generic 4.4.0-145.171
ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176
Uname: Linux 4.4.0-145-generic s390x
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: s390x
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
CurrentDmesg:

Date: Mon Apr 1 03:04:02 2019
HibernationDevice: RESUME=UUID=ca468a9c-9563-442c-85c6-6055e800a66e
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lspci:

Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:

ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
ProcKernelCmdLine: root=UUID=b65b756a-ba4e-4c53-aa32-0db2bdb50bb3 crashkernel=196M
RelatedPackageVersions:
linux-restricted-modules-4.4.0-145-generic N/A
linux-backports-modules-4.4.0-145-generic N/A
linux-firmware 1.157.21
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Po-Hsu Lin (cypressyew) wrote on 2019-04-01:

AudioDevicesInUse.txt Edit (1.2 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.9 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.3 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.3 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (300 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (4.8 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (25.2 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (534.1 KiB, text/plain; charset="utf-8")

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2019-04-01: Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1822542

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status:	New → Incomplete
Changed in linux (Ubuntu Xenial):
status:	New → Incomplete

Revision history for this message

Dimitri John Ledkov (xnox) wrote on 2019-04-01:

nested kvm is disabled by default on s390x. One can force-enable that by booting with kernel cmdline kvm.nested=1 in /etc/zipl.conf and rerun $ sudo zipl; and reboot.

However, I'm confused why this is filed, when this is the expected default behaviour and has been previously raised and discussed in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1732162

Is there a testsuite expectation missmatch that expects nested-kvm by default, which is no longer provided by default?

Po-Hsu Lin (cypressyew) on 2019-09-16

tags:

added: ubuntu-kvm-unit-tests

Revision history for this message

Po-Hsu Lin (cypressyew) wrote on 2021-07-15:

Maybe we can close this if we don't have Xenial ESM for s390x anymore.

Changed in ubuntu-kernel-tests:
assignee:	nobody → Po-Hsu Lin (cypressyew)
status:	New → In Progress

Revision history for this message

Po-Hsu Lin (cypressyew) wrote on 2021-07-15:

We still have s390x for Xenial ESM https://ubuntu.com/blog/ubuntu-16-04-lts-transitions-to-extended-security-maintenance-esm

But since this is for s390x KVM, which is not working with MAAS deployment for the moment, I will put this bug into triage.

Changed in ubuntu-kernel-tests:
assignee:	Po-Hsu Lin (cypressyew) → nobody
status:	In Progress → Triaged

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.