From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Laurent Vivier <lvivier@redhat.com>,
Emanuele Giuseppe Esposito <eesposit@redhat.com>,
Thomas Huth <thuth@redhat.com>, Qin Wang <qinwang@rehdat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: [PATCH] libqtest: refuse QTEST_QEMU_BINARY=qemu-kvm
Date: Wed, 7 Apr 2021 11:45:11 +0100 [thread overview]
Message-ID: <20210407104511.343061-1-stefanha@redhat.com> (raw)
Some downstreams rename the QEMU binary to "qemu-kvm". This breaks
qtest_get_arch(), which attempts to parse the target architecture from
the QTEST_QEMU_BINARY environment variable.
Print an error instead of returning the architecture "kvm". Things fail
in weird ways when the architecture string is bogus.
Arguably qtests should always be run in a build directory instead of
against an installed QEMU. In any case, printing a clear error when this
happens is helpful.
Reported-by: Qin Wang <qinwang@rehdat.com>
Cc: Emanuele Giuseppe Esposito <eesposit@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
---
tests/qtest/libqtest.c | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/tests/qtest/libqtest.c b/tests/qtest/libqtest.c
index 71e359efcd..2fc249c0b5 100644
--- a/tests/qtest/libqtest.c
+++ b/tests/qtest/libqtest.c
@@ -910,6 +910,14 @@ const char *qtest_get_arch(void)
abort();
}
+ if (strcmp(end + 1, "kvm") == 0) {
+ fprintf(stderr, "QTEST_QEMU_BINARY must end with *-<arch>. If you are "
+ "using qemu-kvm, please create a symlink like ln -s "
+ "path/to/qemu-kvm qemu-system-x86_64 and use that "
+ "instead.\n");
+ abort();
+ }
+
return end + 1;
}
--
2.30.2
next reply other threads:[~2021-04-07 10:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 10:45 Stefan Hajnoczi [this message]
2021-04-08 10:37 ` [PATCH] libqtest: refuse QTEST_QEMU_BINARY=qemu-kvm Laurent Vivier
2021-04-08 16:04 ` Stefan Hajnoczi
2021-04-08 10:49 ` 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=20210407104511.343061-1-stefanha@redhat.com \
--to=stefanha@redhat.com \
--cc=eesposit@redhat.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qinwang@rehdat.com \
--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).