From: Scott Garman <scott.a.garman@intel.com>
To: yocto@yoctoproject.org
Subject: Re: running my qemu images with kvm
Date: Thu, 14 Jun 2012 13:07:58 -0700 [thread overview]
Message-ID: <4FDA449E.7040507@intel.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1206141400230.10611@oneiric>
On 06/14/2012 11:05 AM, Robert P. J. Day wrote:
>
> embarrassingly, i only just noticed that if i want my
> yocto-generated qemu images to take advantage of kvm, i should add the
> arg "kvm" to my "runqemu" invocation, is that correct?
Correct.
> if that's the case, might it be worth adding that note to the
> standard oe-init-build-env output at the bottom? or perhaps referring
> the user to the output of "runqemu -h" for available run-time options?
Since the oe-init-build-env script gets invoked for many scenarios that
don't involve running runqemu, I'm not convinced that the info is needed
- it might be nice to have, but we don't want to clutter the output with
too much info.
> at the moment, it seems awfully easy to run your qemu image without
> realizing you're not taking advantage of kvm. or am i misreading
> something?
I've been running my QEMU sessions without kvm and it hasn't been a big
deal. Since we do mention its use in the runqemu usage help, IMHO it's
appropriately documented.
I'm not sure what the status is of kvm support in the various
environments that Yocto is run in, so enabling kvm by default may not be
safe. Please correct me if I'm wrong.
Thanks for the feedback,
Scott
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
prev parent reply other threads:[~2012-06-14 20:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 18:05 running my qemu images with kvm Robert P. J. Day
2012-06-14 20:07 ` Scott Garman [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=4FDA449E.7040507@intel.com \
--to=scott.a.garman@intel.com \
--cc=yocto@yoctoproject.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 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.