From: Fam Zheng <famz@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "QEMU Developers" <qemu-devel@nongnu.org>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [Qemu-devel] 'make vm-build-freebsd' &c don't work if KVM isn't enabled
Date: Thu, 2 Aug 2018 13:47:32 +0800 [thread overview]
Message-ID: <20180802054732.GB11859@lemon.usersys.redhat.com> (raw)
In-Reply-To: <CAFEAcA-iB7_hU2KNUS3rra4FD_P7PzXtXW1BaP37zp=OKZkv3w@mail.gmail.com>
On Mon, 07/30 16:20, Peter Maydell wrote:
> On 30 July 2018 at 14:40, Peter Maydell <peter.maydell@linaro.org> wrote:
> > On 30 July 2018 at 14:36, Peter Maydell <peter.maydell@linaro.org> wrote:
> >> On 30 July 2018 at 14:23, Peter Maydell <peter.maydell@linaro.org> wrote:
> >>> The tests in tests/vm/ seem to make some attempt to cope with the
> >>> host system not allowing the user to use KVM, but it doesn't quite
> >>> work.
> >>
> >> Also, passing V=1 to the outer make command like:
> >> make vm-build-freebsd J=16 V=1
> >> isn't propagated through to the VM: test output looks like
> >> GTESTER check-qtest-aarch64
> >> GTESTER check-qtest-alpha
> >> instead of the proper verbose output with a line per subtest.
> >
> > Nor is the J=16 option passed through to "make check":
>
> Patches for these things on the way, once I've completed a test run.
All good catches! Looking forward to the fixes. Thanks.
Fam
next prev parent reply other threads:[~2018-08-02 5:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 13:23 [Qemu-devel] 'make vm-build-freebsd' &c don't work if KVM isn't enabled Peter Maydell
2018-07-30 13:30 ` Daniel P. Berrangé
2018-07-30 13:36 ` Peter Maydell
2018-07-30 13:40 ` Peter Maydell
2018-07-30 15:20 ` Peter Maydell
2018-08-02 5:47 ` Fam Zheng [this message]
2018-08-02 19:13 ` Philippe Mathieu-Daudé
2018-08-02 20:37 ` Peter Maydell
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=20180802054732.GB11859@lemon.usersys.redhat.com \
--to=famz@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).