From: Eric Blake <eblake@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Michael S . Tsirkin" <mst@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [RFC PATCH 1/2] libqtest: add qtest_accel() to avoid warnings when kvm is not available
Date: Tue, 15 Aug 2017 13:13:50 -0500 [thread overview]
Message-ID: <a2773ebe-e841-4f3f-0234-d89e48811336@redhat.com> (raw)
In-Reply-To: <20170815163959.6632-2-f4bug@amsat.org>
[-- Attachment #1: Type: text/plain, Size: 563 bytes --]
On 08/15/2017 11:39 AM, Philippe Mathieu-Daudé wrote:
> only warn once about it.
>
> - kernel without kvm:
>
> # make check-qtest-x86_64
> GTESTER check-qtest-x86_64
> Could not access KVM kernel module: No such device
> qemu-system-x86_64: failed to initialize KVM: No such device
> qemu-system-x86_64: Back to tcg accelerator
How does this differ from what commit 2f6b38d1 was trying to do?
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]
next prev parent reply other threads:[~2017-08-15 18:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-15 16:39 [Qemu-devel] [RFC PATCH 0/2] tests: avoid kvm accel when it is not accessible Philippe Mathieu-Daudé
2017-08-15 16:39 ` [Qemu-devel] [RFC PATCH 1/2] libqtest: add qtest_accel() to avoid warnings when kvm is not available Philippe Mathieu-Daudé
2017-08-15 18:13 ` Eric Blake [this message]
2017-08-15 18:27 ` Philippe Mathieu-Daudé
2017-08-15 18:39 ` Peter Maydell
2017-08-15 19:10 ` Philippe Mathieu-Daudé
2017-08-15 18:40 ` Eric Blake
2017-08-15 18:51 ` Eric Blake
2017-08-15 19:08 ` Philippe Mathieu-Daudé
2017-08-15 16:39 ` [Qemu-devel] [PATCH 2/2] tests: use qtest_accel() Philippe Mathieu-Daudé
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=a2773ebe-e841-4f3f-0234-d89e48811336@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=f4bug@amsat.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/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).