From: Gleb Natapov <gleb@redhat.com>
To: Conrad Wood <linux-kvm@conradwood.net>
Cc: kvm@vger.kernel.org
Subject: Re: cpu hotplug
Date: Sun, 19 Sep 2010 13:13:58 +0200 [thread overview]
Message-ID: <20100919111358.GP3008@redhat.com> (raw)
In-Reply-To: <1284894579.9521.185.camel@frechmops.schnuffi.conrad.localdomain>
On Sun, Sep 19, 2010 at 01:09:39PM +0200, Conrad Wood wrote:
> On Sun, 2010-09-19 at 12:46 +0200, Gleb Natapov wrote:
> [...]
> > > But... why does the command "info cpus" in the monitor report all cpus
> > > apart from CPU0 as (halted) ?
> > >
> > Because they are halted? Run multiple cpu hogs in the guest and see if
> > cpus will still be halted as reported by monitor. Also kvm-72 is so
> > ancient that I am not sure it reports cpu state correctly in monitor at
> > all.
> >
> > --
> fair enough, upgraded to 0.12.5, same results.
>
> tried a cpu-hog (small loop forking 5 times and each fork doing some
> integer arithmetics for a while) - no change in info cpus
>
> thank you, but I still don't get it ;-)
>
At what rip are they halted? Try to run without kvm and see if the
result is the same. Can you provide output of "info cpus" here?
Are you using qemu-kvm or qemu BTW?
--
Gleb.
next prev parent reply other threads:[~2010-09-19 11:14 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-17 21:39 cpu hotplug Conrad Wood
2010-09-18 14:32 ` Kevin O'Connor
2010-09-18 15:14 ` Conrad Wood
2010-09-18 18:27 ` Conrad Wood
2010-09-19 6:38 ` Gleb Natapov
2010-09-19 10:41 ` Conrad Wood
2010-09-19 10:46 ` Gleb Natapov
2010-09-19 11:09 ` Conrad Wood
2010-09-19 11:13 ` Gleb Natapov [this message]
2010-09-19 11:32 ` Conrad Wood
2010-09-19 11:39 ` Gleb Natapov
2010-09-19 11:51 ` Conrad Wood
2010-09-19 11:59 ` Gleb Natapov
2010-09-19 12:18 ` Conrad Wood
2010-09-19 15:20 ` Avi Kivity
2010-09-19 15:22 ` Gleb Natapov
2010-09-19 13:26 ` Kevin O'Connor
2010-09-19 13:29 ` Conrad Wood
2010-09-19 13:31 ` Gleb Natapov
2010-09-19 13:35 ` Conrad Wood
2010-09-19 13:40 ` Gleb Natapov
2010-09-19 13:46 ` Kevin O'Connor
2010-09-19 13:50 ` Gleb Natapov
2010-09-19 14:07 ` Conrad Wood
2010-09-19 14:14 ` Kevin O'Connor
2010-09-19 14:36 ` Gleb Natapov
2010-09-19 15:16 ` Conrad Wood
2010-09-19 15:19 ` Gleb Natapov
2010-09-19 15:37 ` Conrad Wood
2010-09-19 15:41 ` Gleb Natapov
2010-09-19 15:44 ` Conrad Wood
2010-09-19 15:53 ` Gleb Natapov
2010-09-19 16:04 ` Kevin O'Connor
2010-09-19 16:12 ` Gleb Natapov
2010-09-19 22:03 ` Kevin O'Connor
2010-09-20 6:50 ` Gleb Natapov
2010-09-21 1:07 ` Kevin O'Connor
2010-09-21 6:42 ` Gleb Natapov
2010-09-21 9:38 ` Gleb Natapov
2010-09-19 16:24 ` Conrad Wood
2010-09-19 21:57 ` Kevin O'Connor
2010-09-20 6:48 ` Gleb Natapov
2010-09-19 13:38 ` Kevin O'Connor
2010-09-19 13:39 ` Conrad Wood
-- strict thread matches above, loose matches on Subject: below --
2017-01-01 10:03 CPU HOTPLUG Ozgur O Kilic
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=20100919111358.GP3008@redhat.com \
--to=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kvm@conradwood.net \
/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.