From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: "Hart, Darren" <darren.hart@intel.com>,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] runqemu: Use correct kvm CPU options for qemux86* with kvm
Date: Thu, 26 Sep 2013 00:26:33 -0400 [thread overview]
Message-ID: <5243B779.3080607@windriver.com> (raw)
In-Reply-To: <1380142751.18603.344.camel@ted>
On 13-09-25 4:59 PM, Richard Purdie wrote:
> The existing -cpu host option caused kernel panics when people attempted to use
> the kvm option. After research and discussion, the best options appear to
> be the kvm32/kvm64 cpu types so lets use these instead. These resolve
> the kernel issues for me.
Late to the party, and discussion, but agreed. This change looks good
for this point in 1.5.
Cheers,
Bruce
>
> [YOCTO #3908]
>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> ---
> diff --git a/scripts/runqemu b/scripts/runqemu
> index efab1a2..12c58d9 100755
> --- a/scripts/runqemu
> +++ b/scripts/runqemu
> @@ -265,7 +265,11 @@ if [ "x$KVM_ENABLED" = "xyes" ]; then
> exit 1;
> fi
> if [ -w /dev/kvm -a -r /dev/kvm ]; then
> - SCRIPT_QEMU_OPT="$SCRIPT_QEMU_OPT -enable-kvm -cpu host"
> + if [ "x$MACHINE" = "xqemux86" ]; then
> + SCRIPT_QEMU_OPT="$SCRIPT_QEMU_OPT -enable-kvm -cpu kvm32"
> + elif [ "x$MACHINE" = "xqemux86-64" ]; then
> + SCRIPT_QEMU_OPT="$SCRIPT_QEMU_OPT -enable-kvm -cpu kvm64"
> + fi
> KVM_ACTIVE="yes"
> else
> echo "You have no rights on /dev/kvm."
>
>
prev parent reply other threads:[~2013-09-26 4:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 20:59 [PATCH] runqemu: Use correct kvm CPU options for qemux86* with kvm Richard Purdie
2013-09-25 21:05 ` Darren Hart
2013-09-25 21:09 ` Richard Purdie
2013-09-25 21:32 ` Darren Hart
2013-09-25 21:34 ` Khem Raj
2013-09-25 22:00 ` Richard Purdie
2013-09-25 22:05 ` Khem Raj
2013-09-26 4:26 ` Bruce Ashfield [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=5243B779.3080607@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=darren.hart@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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