All 29 tests in kvm-unit-test failed (timeouted) on i386

Bug #1822235 reported by Po-Hsu Lin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
Invalid
Undecided
Juerg Haefliger
linux (Ubuntu)
Invalid
Undecided
Juerg Haefliger
Bionic
Invalid
Undecided
Juerg Haefliger
Disco
Won't Fix
Undecided
Juerg Haefliger

Bug Description

All the available tests in kvm-unit-test have failed on Cosmic i386 with node "onza".
They all timeout with the default 90 second threshold.

 TESTNAME=smptest TIMEOUT=90s ACCEL= ./x86/run x86/smptest.flat -smp 2
 FAIL smptest (timeout; duration=90s)
 TESTNAME=smptest3 TIMEOUT=90s ACCEL= ./x86/run x86/smptest.flat -smp 3
 FAIL smptest3 (timeout; duration=90s)
 TESTNAME=vmexit_cpuid TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 1 -append 'cpuid'
 FAIL vmexit_cpuid (timeout; duration=90s)
 TESTNAME=vmexit_vmcall TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 1 -append 'vmcall'
 FAIL vmexit_vmcall (timeout; duration=90s)
 TESTNAME=vmexit_mov_from_cr8 TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 1 -append 'mov_from_cr8'
 FAIL vmexit_mov_from_cr8 (timeout; duration=90s)
 TESTNAME=vmexit_mov_to_cr8 TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 1 -append 'mov_to_cr8'
 FAIL vmexit_mov_to_cr8 (timeout; duration=90s)
 TESTNAME=vmexit_inl_pmtimer TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 1 -append 'inl_from_pmtimer'
 FAIL vmexit_inl_pmtimer (timeout; duration=90s)
 TESTNAME=vmexit_ipi TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 2 -append 'ipi'
 FAIL vmexit_ipi (timeout; duration=90s)
 TESTNAME=vmexit_ipi_halt TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 2 -append 'ipi_halt'
 FAIL vmexit_ipi_halt (timeout; duration=90s)
 TESTNAME=vmexit_ple_round_robin TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 1 -append 'ple_round_robin'
 FAIL vmexit_ple_round_robin (timeout; duration=90s)
 TESTNAME=vmexit_tscdeadline TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 1 -cpu qemu64,+x2apic,+tsc-deadline -append tscdeadline
 FAIL vmexit_tscdeadline (timeout; duration=90s)
 TESTNAME=vmexit_tscdeadline_immed TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 1 -cpu qemu64,+x2apic,+tsc-deadline -append tscdeadline_immed
 FAIL vmexit_tscdeadline_immed (timeout; duration=90s)
 TESTNAME=smap TIMEOUT=90s ACCEL= ./x86/run x86/smap.flat -smp 1 -cpu host
 FAIL smap (timeout; duration=90s)
 TESTNAME=eventinj TIMEOUT=90s ACCEL= ./x86/run x86/eventinj.flat -smp 1
 FAIL eventinj (timeout; duration=90s)
 TESTNAME=hypercall TIMEOUT=90s ACCEL= ./x86/run x86/hypercall.flat -smp 1
 FAIL hypercall (timeout; duration=90s)
 TESTNAME=msr TIMEOUT=90s ACCEL= ./x86/run x86/msr.flat -smp 1
 FAIL msr (timeout; duration=90s)
 TESTNAME=port80 TIMEOUT=90s ACCEL= ./x86/run x86/port80.flat -smp 1
 FAIL port80 (timeout; duration=90s)
 TESTNAME=realmode TIMEOUT=90s ACCEL= ./x86/run x86/realmode.flat -smp 1
 FAIL realmode (timeout; duration=90s)
 TESTNAME=s3 TIMEOUT=90s ACCEL= ./x86/run x86/s3.flat -smp 1
 FAIL s3 (timeout; duration=90s)
 TESTNAME=sieve TIMEOUT=90s ACCEL= ./x86/run x86/sieve.flat -smp 1
 FAIL sieve (timeout; duration=90s)
 TESTNAME=tsc TIMEOUT=90s ACCEL= ./x86/run x86/tsc.flat -smp 1 -cpu kvm64,+rdtscp
 FAIL tsc (timeout; duration=90s)
 TESTNAME=tsc_adjust TIMEOUT=90s ACCEL= ./x86/run x86/tsc_adjust.flat -smp 1 -cpu host
 FAIL tsc_adjust (timeout; duration=90s)
 TESTNAME=taskswitch TIMEOUT=90s ACCEL= ./x86/run x86/taskswitch.flat -smp 1
 FAIL taskswitch (timeout; duration=90s)
 TESTNAME=taskswitch2 TIMEOUT=90s ACCEL= ./x86/run x86/taskswitch2.flat -smp 1
 FAIL taskswitch2 (timeout; duration=90s)
 TESTNAME=kvmclock_test TIMEOUT=90s ACCEL= ./x86/run x86/kvmclock_test.flat -smp 2 --append "10000000 `date +%s`"
 FAIL kvmclock_test (timeout; duration=90s)
 TESTNAME=umip TIMEOUT=90s ACCEL= ./x86/run x86/umip.flat -smp 1 -cpu qemu64,+umip
 FAIL umip (timeout; duration=90s)
 TESTNAME=hyperv_synic TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_synic.flat -smp 2 -cpu kvm64,hv_vpindex,hv_synic -device hyperv-testdev
 FAIL hyperv_synic (timeout; duration=90s)
 TESTNAME=hyperv_connections TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_connections.flat -smp 2 -cpu kvm64,hv_vpindex,hv_synic -device hyperv-testdev
 FAIL hyperv_connections (timeout; duration=90s)
 TESTNAME=hyperv_stimer TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_stimer.flat -smp 2 -cpu kvm64,hv_vpindex,hv_time,hv_synic,hv_stimer -device hyperv-testdev
 FAIL hyperv_stimer (timeout; duration=90s)

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-16-generic 4.18.0-16.17
ProcVersionSignature: User Name 4.18.0-16.17-generic 4.18.20
Uname: Linux 4.18.0-16-generic i686
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116, 1 Mar 29 05:08 seq
 crw-rw---- 1 root audio 116, 33 Mar 29 05:08 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: i386
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
Date: Fri Mar 29 05:09:30 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: Dell Inc. PowerEdge R310
PciMultimedia:

ProcFB: 0 mgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=6aaa11f6-d386-4c0c-b4b8-38e6c408980a ro
RelatedPackageVersions:
 linux-restricted-modules-4.18.0-16-generic N/A
 linux-backports-modules-4.18.0-16-generic N/A
 linux-firmware 1.175.1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/18/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.11.0
dmi.board.name: 05XKKK
dmi.board.vendor: Dell Inc.
dmi.board.version: A05
dmi.chassis.type: 23
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.11.0:bd09/18/2012:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA05:cvnDellInc.:ct23:cvr:
dmi.product.name: PowerEdge R310
dmi.sys.vendor: Dell Inc.

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
summary: - All 29 tests in kvm-unit-test failed (timeouted) on C i386
+ All 29 tests in kvm-unit-test failed (timeouted) on i386
description: updated
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Could be found on other kernels as well, for X/T the test will failed to build.
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1798007

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Changed in linux (Ubuntu Bionic):
status: New → Confirmed
Changed in linux (Ubuntu Cosmic):
status: New → Confirmed
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Bump the timeout threshold to 360 seconds for each test, they're still failing.

Po-Hsu Lin (cypressyew)
Changed in ubuntu-kernel-tests:
status: New → Confirmed
Po-Hsu Lin (cypressyew)
tags: added: ubuntu-kvm-unit-tests
Juerg Haefliger (juergh)
Changed in linux (Ubuntu Disco):
assignee: nobody → Juerg Haefliger (juergh)
Changed in linux (Ubuntu Cosmic):
assignee: nobody → Juerg Haefliger (juergh)
Changed in linux (Ubuntu Bionic):
assignee: nobody → Juerg Haefliger (juergh)
Changed in ubuntu-kernel-tests:
assignee: nobody → Juerg Haefliger (juergh)
Changed in linux (Ubuntu):
assignee: nobody → Juerg Haefliger (juergh)
Juerg Haefliger (juergh)
no longer affects: linux (Ubuntu Cosmic)
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

For node pepe with D-i386, only those vmexit_* tests would fail.

Revision history for this message
Juerg Haefliger (juergh) wrote :

For the record, onza is having problems running qemu-system-i386 on a 32-bit host kernel. It's stuck in a busy loop before loading/executing the kernel/test. The fact that pepe (same machine: Dell PowerEdge R310) doesn't exhibit that problem points to an onza hardware issue.

FWIW, onza works fine when using a 64-bit host kernel.

Still looking at it...

Revision history for this message
Juerg Haefliger (juergh) wrote :

So it seems something in 5.0.0-30 fixed this. 32-bit qemu hangs with 5.0.0-29 but runs just fine with 5.0.0-30 both on onza and pepe.

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

For the kvm-unit-tests in this cycle with a Bionic kernel (4.15.0-66.75)
i386 node pepe has failed with on 12 tests:
  * msr
  * tsc
  * vmexit* (10 tests)

http://10.246.72.4/test-results/4.15.0-66.75-generic/pepe__4.15.0-66.75__2019-10-03_14-25-00/ubuntu_kvm_unit_tests-test-suite.html

Steve Langasek (vorlon)
Changed in linux (Ubuntu Disco):
status: Confirmed → Won't Fix
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

As for X/T i386 this test cannot be built (bug 1798007)
For Bionic i386 it's not failing on all the tests (comment #8)
For Bionic 5.4 i386, it's failing with vmexit* and hyperv_*

Thus it's not failing with all the tests for now, I will close this bug.
Maybe we will re-open it in the future when we can test X/T

Changed in ubuntu-kernel-tests:
status: Confirmed → Invalid
Changed in linux (Ubuntu):
status: Confirmed → Invalid
Changed in linux (Ubuntu Bionic):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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