From: Kaspar Schiess <eule@space.ch>
To: kvm@vger.kernel.org
Subject: SMP trouble with Solaris 10u8 as guest on Ubuntu
Date: Fri, 11 Jun 2010 10:32:37 +0200 [thread overview]
Message-ID: <hussb5$e44$1@dough.gmane.org> (raw)
Hi folks,
We're running Solaris 10u8 64bit on Ubuntu/KVM. The Solaris guest feels
sluggish when I assign it more than one VCPU. With a single VCPU things
fly and everything works fine.
By feels sluggish I mean:
- occasional ssh freezes
- slow typing
- high system (spends its time doing kernel stuff)
- Sometimes hangs while booting
These symptoms ALL go away when I limit the VM to one VCPU.
Here are the versions I can confirm this with: (from apt-show-versions |
egrep "kvm|qemu")
Host 1:
kvm/lucid uptodate 1:84+dfsg-0ubuntu16+0.12.3+noroms+0ubuntu9
qemu-common/lucid uptodate 0.12.3+noroms-0ubuntu9
qemu-kvm/lucid uptodate 0.12.3+noroms-0ubuntu9
Host 2:
kvm/karmic-updates uptodate 1:84+dfsg-0ubuntu16+0.11.0+0ubuntu6.3
qemu-kvm/karmic-updates uptodate 0.11.0-0ubuntu6.3
Old Bug? New Feature? Should I report this? Anyone seen this? Any
suggestions?
Thanks in advance,
kaspar
reply other threads:[~2010-06-11 8:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='hussb5$e44$1@dough.gmane.org' \
--to=eule@space.ch \
--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