From: Avi Kivity <avi@qumranet.com>
To: Karl Rister <kmr@us.ibm.com>
Cc: kvm-devel@lists.sourceforge.net, Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: problems running many guests
Date: Wed, 07 May 2008 10:56:34 +0300 [thread overview]
Message-ID: <482160B2.5090006@qumranet.com> (raw)
In-Reply-To: <200805052040.23253.kmr@us.ibm.com>
Karl Rister wrote:
> On Thursday 01 May 2008 7:16:53 pm Marcelo Tosatti wrote:
>
>> Does -no-kvm-irqchip or -no-kvm-pit makes a difference? If not, please
>> grab kvm_stat --once output when that happens.
>>
>
> Per some suggestions I have moved up to kvm-68 which is better, but still
> having problems. Replicating the problem with only one guest spinning has
> proven quite difficult, but attempting to boot a large smp guest can reliably
> recreate the problem. Using -no-kvm-pit did not help the large guest
> and -no-kvm-irqchip made it seize up even earlier with only 1 cpu spinning
> instead of all of them.
>
>
Can you try the many-uniprocessor-guests scenario, with each guest
pinned to a cpu?
taskset $(( 1 << (RANDOM % 32) )) qemu ...
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
next prev parent reply other threads:[~2008-05-07 7:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-01 23:00 problems running many guests Karl Rister
2008-05-02 0:16 ` Marcelo Tosatti
2008-05-02 19:19 ` Karl Rister
2008-05-06 1:40 ` Karl Rister
2008-05-06 16:16 ` Marcelo Tosatti
2008-05-07 7:56 ` Avi Kivity [this message]
2008-05-04 8:41 ` Avi Kivity
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=482160B2.5090006@qumranet.com \
--to=avi@qumranet.com \
--cc=kmr@us.ibm.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=mtosatti@redhat.com \
/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