All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 121711] New: KVM virtual machine using libvirtd crashes
Date: Fri, 08 Jul 2016 22:12:44 +0000	[thread overview]
Message-ID: <bug-121711-28872@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 121711
           Summary: KVM virtual machine using libvirtd crashes
           Product: Virtualization
           Version: unspecified
    Kernel Version: 4.6.2-1
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: kvm
          Assignee: virtualization_kvm@kernel-bugs.osdl.org
          Reporter: eric@ericbond.net
        Regression: No

I'm running a qemu/kvm stack with one windows 10 vm running. The vm will
eventually crash, though the crashes are random enough to happen anytime. 

After a crash, I attempt to force shutdown the vm using virsh stop. I receive
this output: 

error: Disconnected from qemu:///system due to keepalive timeout
error: Failed to destroy domain win7
error: internal error: connection closed due to keepalive timeout

and all virsh commands fail after that.

I attempt to restart the host linux machine, but receive this message when
shutting down:

------------[ cut here ]------------
kernel BUG at drivers/pci/msi.c:368!
invalid opcode: 0000 [#1] PREEMPT SMP 
Modules linked in: cdc_acm rfcomm xt_CHECKSUM ipt_MASQUERADE
nf_nat_masquerade_ipv4 tun xt_tcpudp ip6t_rpfilter ip6t_REJECT nf_reject_ipv6
ipt_REJECT nf_reject_ipv4 xt_conntrack ip_s
media snd_seq_device snd_hda_codec_realtek snd_hda_codec_generic nls_iso8859_1
nls_cp437 vfat fat iTCO_wdt iTCO_vendor_support nouveau intel_rapl
x86_pkg_temp_thermal intel_powercla
tpm_tis i2c_designware_platform i2c_designware_core tpm 8250_dw
spi_pxa2xx_platform acpi_pad processor button usbip_host usbip_core ip_tables
x_tables ext4 crc16 jbd2 mbcache dm_mod
CPU: 2 PID: 629 Comm: libvirtd Tainted: G        W       4.6.2-1-ARCH #1
Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z97 Extreme6, BIOS
P2.50 10/06/2015
task: ffff8808188ed580 ti: ffff8802c6364000 task.ti: ffff8802c6364000
RIP: 0010:[<ffffffff8134842b>]  [<ffffffff8134842b>] free_msi_irqs+0x5b/0x1c0
RSP: 0018:ffff8802c6367a30  EFLAGS: 00010282
RAX: ffff88027e48ac00 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000026 RDI: ffff88081f400158
RBP: ffff8802c6367a60 R08: ffff88081f400000 R09: 0000000000000001
R10: 0000000000000000 R11: 0000000000000000 R12: ffff88081b9c0298
R13: ffff88081b9c0000 R14: ffff880818945120 R15: ffff88081a7a1440
FS:  00007fb7f2a5e700(0000) GS:ffff88083fa80000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007facfd24f750 CR3: 0000000817908000 CR4: 00000000001406e0
Stack: 
ffff8802c6367a40 ffff88081b9c0000 0000000000000008 0000000000000008
0000000000000008 ffff88081a7a1440 ffff8802c6367ac8 ffffffff8134896a
ffff88081b9c0298 0000000000000008 ffff88081b9c0098 00000007a01948b7
Call Trace:
[<ffffffff8134896a>] pci_enable_msix+0x3da/0x450
[<ffffffff81348a0c>] pci_enable_msix_range+0x2c/0x60
[<ffffffffa0181b13>] xhci_run+0x183/0x740 [xhci_hcd]
[<ffffffffa00af112>] usb_add_hcd+0x332/0x9b0 [usbcore]
[<ffffffffa00c134f>] usb_hcd_pci_probe+0x1af/0x4a0 [usbcore]
[<ffffffffa01ee68c>] xhci_pci_probe+0x2c/0x220 [xhci_pci]
[<ffffffff8132e215>] local_pci_probe+0x45/0xa0
[<ffffffff8132e160>] ? pci_match_device+0xe0/0x110
[<ffffffff8132f419>] pci_device_probe+0x109/0x160
[<ffffffff814127dc>] driver_probe_device+0x22c/0x440
[<ffffffff81412b74>] __device_attach_driver+0x94/0x110
[<ffffffff81412ae0>] ? __driver_attach+0xf0/0xf0
[<ffffffff81410347>] bus_for_each_drv+0x67/0xb0
[<ffffffff8141243d>] __device_attach+0xdd/0x160
[<ffffffff814124d0>] device_attach+0x10/0x20
[<ffffffff81410d25>] bus_rescan_devices_helper+0x35/0x60
[<ffffffff81410dd2>] store_drivers_probe+0x32/0x60
[<ffffffff8140fe95>] bus_attr_store+0x25/0x30
[<ffffffff812749e7>] sysfs_kf_write+0x37/0x40
[<ffffffff81273f9c>] kernfs_fop_write+0x11c/0x170
[<ffffffff811f6397>] __vfs_write+0x37/0x100
[<ffffffff811f72a3>] vfs_write+0xa3/0x190
[<ffffffff811f8745>] SyS_write+0x55/0xc0
[<ffffffff815c7272>] entry_SYSCALL_64_fastpath+0x1a/0xa4
Code: 85 ff 74 29 41 8b 46 14 85 c0 74 21 31 db eb 0d 83 c3 01 41 39 5e 14 76
14 41 8b 7e 10 01 df e8 dc c9 d8 ff 48 83 78 70 00 74 e5 <0f> 0b 4d 8b 36 4d 39
f4 75 c7 49 8b bd 88 02
RIP  [<ffffffff8134842b>] free_msi_irqs+0x5b/0x1c0
RSP <ffff8802c6367a30>
---[ end trace 0df29045d094c8f4 ]---

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

             reply	other threads:[~2016-07-08 22:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-08 22:12 bugzilla-daemon [this message]
2016-07-09  5:50 ` [Bug 121711] KVM virtual machine using libvirtd crashes bugzilla-daemon
2016-07-09  5:58 ` bugzilla-daemon
2016-07-09  6:00 ` bugzilla-daemon
2016-07-09  6:04 ` bugzilla-daemon
2016-07-09  6:08 ` [Bug 121711] BUG_ON during PCI bus rescan bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-121711-28872@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=kvm@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.