From: Paolo Bonzini <pbonzini@redhat.com>
To: Xiong Zhou <xzhou@redhat.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: Starting kvm/qemu guest crash kernel linux-next 0221 tree
Date: Wed, 22 Feb 2017 09:28:21 +0100 [thread overview]
Message-ID: <e59d5584-fa25-a925-65b8-7394f51c0390@redhat.com> (raw)
In-Reply-To: <20170222015243.bzcnin2xbygak4wl@XZHOUW.usersys.redhat.com>
On 22/02/2017 02:52, Xiong Zhou wrote:
> Hi,
>
> Starting a guest begin to crash kernel on 0221 -next tree.
>
> It's fine on 0220 tree.
Can you try commits a26d553400b30b6e0389f5c723c0fc6f7ea473da (0221) and
b95234c840045b7c72380fd14c59416af28fcb02 (0220)?
What is the guest and the QEMU command line?
Paolo
next prev parent reply other threads:[~2017-02-22 8:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 1:52 Starting kvm/qemu guest crash kernel linux-next 0221 tree Xiong Zhou
2017-02-22 8:28 ` Paolo Bonzini [this message]
2017-02-22 13:55 ` Xiong Zhou
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=e59d5584-fa25-a925-65b8-7394f51c0390@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=xzhou@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