kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 92291] New: kvm/guest crashes when smp > 1 with AMD FX8300; with host kernel oops from abrt as well
Date: Thu, 29 Jan 2015 14:35:36 +0000	[thread overview]
Message-ID: <bug-92291-28872@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 92291
           Summary: kvm/guest crashes when smp > 1 with AMD FX8300; with
                    host kernel oops from abrt as well
           Product: Virtualization
           Version: unspecified
    Kernel Version: 3.18.3-201.fc21.x86_64 [host], 3.13.0-39-generic
                    [ubuntu guest]
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: kvm
          Assignee: virtualization_kvm@kernel-bugs.osdl.org
          Reporter: kernelbugzilla.org.Markie1@dfgh.net
        Regression: No

Created attachment 165171
  --> https://bugzilla.kernel.org/attachment.cgi?id=165171&action=edit
kvm register dumps

Overview
========
Whenever I launch a kvm guest in qemu-system-x86_64 with -smp > 1 [-cpu host
-enable-kvm of course], the guest kernel crashes at some stage; I've seen the
kernel crash before completing boot-up, giving the recognizable kernel crash
trace, as well as during 'normal' operation when the guest simply 'freezes'.
The host kernel gives me an oops as well, although abrt won't let me report it
now as I've got Nvidia proprietary drivers 'tainting' the kernel
The bug seems non-specific to guest OS, though mainly it's been *buntu guests,
with various different kernels including lowlatency, I even think I've seen the
bug with a Windows guest. I've tried building qemu from git sources, no
particularly noticeable difference;

Steps to reproduce
==================

1) Start linux guest on a multicore system [AMD FX8* series CPU?] with
$ qemu-system-x86_64 -m 2G -cpu host -smp 4 -enable-kvm -hda [image_file] -vga
vmware

2) wait until the guest kernel crashes; virtually every time in less than 10
minutes

Actual results
==============
guest kernel crashes, host kernel gives an oops too, presumably as a result of
kvm passthrough

Expected results
================
guest virtual machine should work normally then keep working normally

it would be good to try to pipe dmesg from the guest to the host serial
connection, in case that would assist?

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

             reply	other threads:[~2015-01-29 14:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-29 14:35 bugzilla-daemon [this message]
2015-01-29 14:36 ` [Bug 92291] kvm/guest crashes when smp > 1 with AMD FX8300; with host kernel oops from abrt as well bugzilla-daemon
2015-01-29 14:37 ` bugzilla-daemon
2015-01-29 14:38 ` bugzilla-daemon
2015-02-06 14:12 ` bugzilla-daemon
2015-02-06 14:43 ` bugzilla-daemon
2015-02-10 16:50 ` bugzilla-daemon
2015-02-10 17:29 ` bugzilla-daemon
2015-02-11 12:46 ` bugzilla-daemon
2015-02-11 12:46 ` bugzilla-daemon
2015-02-12 18:22 ` 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-92291-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).