All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 65081] New: Starting a second guest with -smp 2 makes the first guest very slow and the second one hang (or also very slow)
Date: Sat, 16 Nov 2013 15:17:17 +0000	[thread overview]
Message-ID: <bug-65081-28872@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 65081
           Summary: Starting a second guest with -smp 2 makes the first
                    guest very slow and the second one hang (or also very
                    slow)
           Product: Virtualization
           Version: unspecified
    Kernel Version: 3.12
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: kvm
          Assignee: virtualization_kvm@kernel-bugs.osdl.org
          Reporter: d.haid@gogi.tv
        Regression: No

I think this first occured when I upgraded the kernel to 3.11 and qemu to
1.6.1. I am now running kernel version 3.12 and the problem still exists.

If I start a first KVM guest with -smp 2 it runs fine. As soon as I start
another KVM guest on the same host also with -smp 2, the first one gets
extremely slow. I can type one character per second via ssh. I do not see any
messages from the second guest, so it seems to hang or is very slow.

If I start the second kVM guest without -smp 2 both guests seem to work fine.

I get the following messages on the host, but I do not know whether they are
relevant.

kvm: SMP vm created on host with unstable TSC; guest TSC will not be reliable

qemu-system-x86: sending ioctl 5326 to a partition!
qemu-system-x86: sending ioctl 80200204 to a partition!

kvm [409]: vcpu0 unhandled rdmsr: 0xc0010001
kvm [409]: vcpu0 unhandled rdmsr: 0x3a

-

It is likely that this is not enough information to find the bug, so I would
appreciate any help on what I can do to obtain more information about what
might be happening here.

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

             reply	other threads:[~2013-11-16 15:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-16 15:17 bugzilla-daemon [this message]
2013-11-16 19:00 ` [Bug 65081] Starting a second guest with -smp 2 makes the first guest very slow and the second one hang (or also very slow) bugzilla-daemon
2014-04-21 16:01 ` bugzilla-daemon
2014-04-21 17:06 ` bugzilla-daemon
2014-04-21 18:28 ` bugzilla-daemon
2015-04-27 13:08 ` bugzilla-daemon
2015-04-27 13:39 ` 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-65081-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.