From: Igor Mammedov <imammedo@redhat.com>
To: Paul Schlacter <wlfightup@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] hot plug cpu report error
Date: Tue, 10 Oct 2017 14:44:47 +0200 [thread overview]
Message-ID: <20171010144447.5cadff7f@nial.brq.redhat.com> (raw)
In-Reply-To: <CADak6y7ZKX5oJv+oqFG1Kz2_mVArsnM18mw3uqAd3ei-s3JYVw@mail.gmail.com>
On Mon, 9 Oct 2017 20:21:12 +0800
Paul Schlacter <wlfightup@gmail.com> wrote:
> report error:
>
> intel_rapl: no valid rapl domains found in package 0
>
> intel_rapl: no valid rapl domains found in package 0
>
>
> and then will shutdown after in a moment of time
>
>
> qemu log :
>
> qemu: qemu_mutex_lock: Invalid argument
> 2017-10-09 09:27:34.781+0000: shutting down, reason=crashed
>
>
> Find a solution
that's not enough information to even guess,
please provide exact steps to reproduce issue including
used versions (qemu, kernel(host|guest)), qemu command line,
console logs
prev parent reply other threads:[~2017-10-10 12:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 12:21 [Qemu-devel] hot plug cpu report error Paul Schlacter
2017-10-10 12:44 ` Igor Mammedov [this message]
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=20171010144447.5cadff7f@nial.brq.redhat.com \
--to=imammedo@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wlfightup@gmail.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;
as well as URLs for NNTP newsgroup(s).