qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
	pbonzini@redhat.com, qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Marcel Apfelbaum <marcel.a@redhat.com>,
	Laurent Vivier <lvivier@redhat.com>,
	David Gibson <dgibson@redhat.com>
Subject: Re: [Qemu-devel] kvm test warnings
Date: Fri, 9 Sep 2016 21:24:45 +0200	[thread overview]
Message-ID: <718d4b1f-2b2f-fefb-1175-73f07d962343@redhat.com> (raw)
In-Reply-To: <20160909220057-mutt-send-email-mst@kernel.org>

On 09.09.2016 21:03, Michael S. Tsirkin wrote:
> I am running make test on a box without kvm, and I am seeing these warnings:
> 
> GTESTER check-qtest-ppc64
> "kvm" accelerator not found.
> "kvm" accelerator not found.
> GTESTER check-qtest-x86_64
> Could not access KVM kernel module: No such file or directory
> failed to initialize KVM: No such file or directory
> Back to tcg accelerator.
> Could not access KVM kernel module: No such file or directory
> failed to initialize KVM: No such file or directory
> Back to tcg accelerator.
> 
> This is with
> commit c2a57aae9a1c3dd7de77daf5478df10379aeeebf
> Merge: 5f31bbf f8042de
> Author: Peter Maydell <peter.maydell@linaro.org>
> Date:   Fri Sep 9 12:49:41 2016 +0100
> 
> I originally thought this is due to Marcel's test change,
> but it triggers without ask well.
> 
> Help will be appreciated.

See this thread here:

https://lists.gnu.org/archive/html/qemu-devel/2016-07/msg05809.html

It's not so easy to avoid this warning ... suggestions are welcome...

 Thomas

  reply	other threads:[~2016-09-09 19:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-09 19:03 [Qemu-devel] kvm test warnings Michael S. Tsirkin
2016-09-09 19:24 ` Thomas Huth [this message]
2016-09-09 21:31   ` Michael S. Tsirkin
2016-09-29 15:16     ` Laurent Vivier
2016-09-29 15:28       ` Thomas Huth

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=718d4b1f-2b2f-fefb-1175-73f07d962343@redhat.com \
    --to=thuth@redhat.com \
    --cc=dgibson@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=marcel.a@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --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).