New: warning on kvm_lapic_expired_hv_timer

https://bugzilla.kernel.org/show_bug.cgi?id=188371

            Bug ID: 188371
           Summary: warning on kvm_lapic_expired_hv_timer
           Product: Virtualization
           Version: unspecified
    Kernel Version: 4.8.9
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: kvm
          Assignee: [email protected]
          Reporter: [email protected]
        Regression: No

Not 100% sure if this is a bug but I figure that warnings shouldn't be issued. I've also found these on 4.8.3 hosts.

Getting the following warning:

[137293.792520] ------------[ cut here ]------------
[137293.797900] WARNING: CPU: 15 PID: 2750 at arch/x86/kvm/lapic.c:1369
kvm_lapic_expired_hv_timer+0x5e/0x80
[137293.808758] Modules linked in:
[137293.812456] CPU: 15 PID: 2750 Comm: CPU 0/KVM Tainted: G        W      
4.8.9-local.20161121-145358 #28
[137293.823173] Hardware name: Dell Inc. PowerEdge R730xd/0599V5, BIOS 2.0.1
02/12/2016
[137293.831945]  0000000000000286 000000004c9c69b2 ffffffff813c9dad
0000000000000000
[137293.840783]  0000000000000000 ffffffff8112f3ca ffff880780180000
ffff88084f066000
[137293.849636]  0000000000000000 0000000000000000 ffff880780180000
ffff880780180000
[137293.858483] Call Trace:
[137293.861407]  [<ffffffff813c9dad>] ? dump_stack+0x46/0x59
[137293.867538]  [<ffffffff8112f3ca>] ? __warn+0xba/0xe0
[137293.873277]  [<ffffffff81041ffe>] ? kvm_lapic_expired_hv_timer+0x5e/0x80
[137293.880962]  [<ffffffff8104f185>] ? handle_preemption_timer+0x5/0x10
[137293.888261]  [<ffffffff810581ce>] ? vmx_handle_exit+0xde/0x12d0
[137293.895105]  [<ffffffff8102a6a4>] ? kvm_arch_vcpu_ioctl_run+0x894/0x1500
[137293.902849]  [<ffffffff810248d2>] ? kvm_arch_vcpu_load+0x52/0x220
[137293.909902]  [<ffffffff81017b8e>] ? kvm_vcpu_ioctl+0x30e/0x550
[137293.916620]  [<ffffffff8125e656>] ? do_vfs_ioctl+0x96/0x5f0
[137293.923044]  [<ffffffff8101f1e2>] ? kvm_on_user_return+0x32/0x60
[137293.929954]  [<ffffffff8125ebe6>] ? SyS_ioctl+0x36/0x70
[137293.936017]  [<ffffffff819c1adf>] ? entry_SYSCALL_64_fastpath+0x17/0x93
[137293.944256] ---[ end trace fc47be1217dde2a6 ]---

* What cpu model (examples: Intel Core Duo, Intel Core 2 Duo, AMD Opteron 2210). See /proc/cpuinfo if you're not sure.

model name : Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz

* What kvm version you are using. If you're using git directly, provide the output of 'git describe'.

QEMU emulator version 2.7.0(Debian 1:2.7.0+dfsg-1+local8.1), Copyright (c) 2003-2016 Fabrice Bellard and the QEMU Project developers

* The host kernel version

Linux betelnut11 4.8.9-local.20161121-145358 #28 SMP PREEMPT Mon Nov 21 15:08:13 AEDT 2016 x86_64 GNU/Linux

* What host kernel arch you are using (i386 or x86_64)

x86_64

* What guest you are using, including OS type (Linux, Windows, Solaris, etc.), bitness (32 or 64), kernel version

Linux 4.8.[39], Debian, x86_64.

* The qemu command line you are using to start the guest

There are many so I'm not sure if this is the exact one but they're all clones of each other.

qemu-system-x86_64 -enable-kvm -name guest=guestname,debug-threads=on -S
-object
secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-11-guestname/master-key.aes
-machine pc-i440fx-2.6,accel=kvm,usb=off,dump-guest-core=off -cpu Haswell-noTSX,+vme,+ds,+acpi,+ss,+ht,+tm,+pbe,+dtes64,+monitor,+ds_cpl,+vmx,+smx,+est,+tm2,+xtpr,+pdcm,+dca,+osxsave,+f16c,+rdrand,+arat,+tsc_adjust,+xsaveopt,+pdpe1gb,+abm,-invtsc -m 512 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid
957e1982-3ab2-465b-ab5c-de3475a26be3 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-11-guestname/monitor.sock,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown
-boot menu=on,strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2
-drive
file=/dev/drbd/by-res/guestname,format=raw,if=none,id=drive-virtio-disk0,cache=none
-device
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
-drive
file=/home/kvmadmin/virt/dev/debian-cd.iso,format=raw,if=none,id=drive-ide0-0-0,readonly=on,cache=none
-device ide-cd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=2
-netdev tap,fd=32,id=hostnet0,vhost=on,vhostfd=34 -device
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:55:55:e7,bus=pci.0,addr=0x3
-netdev tap,fd=35,id=hostnet1,vhost=on,vhostfd=36 -device
virtio-net-pci,netdev=hostnet1,id=net1,mac=52:54:01:55:55:e7,bus=pci.0,addr=0x4
-chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0
-vnc 127.10.0.0:11 -device VGA,id=video0,vgamem_mb=1,bus=pci.0,addr=0x2 -device
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -smbios
type=3,manufacturer=X,serial=guestname,asset=autoconf:str -msg timestamp=on

* Whether the problem goes away if using the -no-kvm-irqchip or -no-kvm-pit switch.

Can't test. Live, customer-facing system.

* Whether the problem also appears with the -no-kvm switch.

Can't test. Live, customer-facing system.

You are receiving this mail because:
You are watching the assignee of the bug.