From: Huang, Ying <ying.huang@intel.com>
To: lkp@lists.01.org
Subject: Re: qemu how-to?
Date: Wed, 05 Apr 2017 09:16:56 +0800 [thread overview]
Message-ID: <87bmsbhcvr.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <87bmsdlhob.fsf@dmlp.sw.ru>
[-- Attachment #1: Type: text/plain, Size: 1471 bytes --]
Dmitry Monakhov <dmonakhov@openvz.org> writes:
> Hi,
>
> lkp-test project has nice howto about local case. But I want to run
> lkp inside qemu in order to get beter resource utilization.
> Unfortunetly it is not obvious how to do that. I've tried
> #lkp split jobs/hackbench.yaml
> #lkp compile hackbench-50%-threads-socket.yaml > job.yaml.sh
> #lkp qemu -k $my-kernel//arch/x86/boot/bzImage job.yaml.sh
lkp qemu is mainly for boot test now. For performance test like
hackbench, you need to run lkp-tests inside the qemu. Something like,
start the qemu, login into the Linux in qemu, then
# cd $lkp-tests
# make install
# lkp install jobs/hackbench.yaml
# lkp run xxx.yaml # one split job
> It gives me a lot of errors and exit, It's looks like script expect some
> magic enviroment variables to be configured before run.
> Can you please explain how to do that, or share your autostart script.
>
> Can you please do that on clean enviroment debian enviroment (for
> example inside docker container), so very first commands are
> # docker run --rm -it --privileged debian:sid
> #$ apt-get update
> #$ apt-get install git make -y
> #$ git clone https://github.com/01org/lkp-tests
> #$ cd lkp-tests
> #$ make install
>
>
> BTW It would be nice to have this info in README file. Because IFAIU
> many people want to ask this question again and again.
Thanks for your suggestion. We will do that.
Best Regards,
Huang, Ying
next prev parent reply other threads:[~2017-04-05 1:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 13:55 qemu how-to? Dmitry Monakhov
2017-04-05 1:16 ` Huang, Ying [this message]
2017-04-05 7:34 ` Dmitry Monakhov
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=87bmsbhcvr.fsf@yhuang-dev.intel.com \
--to=ying.huang@intel.com \
--cc=lkp@lists.01.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.