From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "QEMU Developers" <qemu-devel@nongnu.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Fam Zheng" <famz@redhat.com>
Subject: Re: [Qemu-devel] 'make vm-build-freebsd' &c don't work if KVM isn't enabled
Date: Mon, 30 Jul 2018 14:30:10 +0100 [thread overview]
Message-ID: <20180730133010.GK1626@redhat.com> (raw)
In-Reply-To: <CAFEAcA8yrNzEaL5_D79OjHCUUwPQnS4MnQhU9gumR7fpTThyuQ@mail.gmail.com>
On Mon, Jul 30, 2018 at 02:23:50PM +0100, Peter Maydell 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. The problem is that tests/vm/basevm.py always uses "-cpu host"
> in the QEMU options it uses to run the VM, and that only works if
> KVM is enabled. If the user can't run KVM then we correctly avoid
> passing it "-enable-kvm" but then QEMU doesn't run because "-cpu host"
> isn't supported...
>
> I guess the right fix here is to use "-cpu max" ?
Yes, sounds like exactly the kind of scenario that 'max' was intended
to support.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2018-07-30 13:30 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é [this message]
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
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=20180730133010.GK1626@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=famz@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 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.