From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Kashyap Chamarthy <kchamart@redhat.com>,
"Richard W.M. Jones" <rjones@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Cubietruck: cannot create KVM guests: "kvm_init_vcpu failed: Invalid argument"
Date: Tue, 9 Dec 2014 12:33:22 +0000 [thread overview]
Message-ID: <20141209123321.GD5272@work-vm> (raw)
In-Reply-To: <CAFEAcA-tpBuXLj3HtjkyQKsU1cQ36C2Tyo99E_havSc8aEcxYg@mail.gmail.com>
* Peter Maydell (peter.maydell@linaro.org) wrote:
> On 9 December 2014 at 11:25, Richard W.M. Jones <rjones@redhat.com> wrote:
> > I really think that qemu should just "do the right thing" though.
>
> Tricky, because you have to use the same CPU as the host if
> you want to use KVM
That's an unusally strict requirement; is there no concept
of a common subset that will work on multiple CPUs?
Is that still true for v8? I can see it making it tricky for users
with piles of newer/older hosts.
Dave
> and that conflicts with wanting to do the
> same thing on all host platforms for a given set of command line
> options. If you have some concrete suggestions for improving
> things that don't break backwards-compatibility I'm happy to
> hear them, though.
>
> -- PMM
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2014-12-09 13:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-09 10:50 [Qemu-devel] Cubietruck: cannot create KVM guests: "kvm_init_vcpu failed: Invalid argument" Kashyap Chamarthy
2014-12-09 10:53 ` Peter Maydell
2014-12-09 11:27 ` Richard W.M. Jones
2014-12-09 12:15 ` Kashyap Chamarthy
2014-12-09 16:48 ` Kashyap Chamarthy
2014-12-09 11:25 ` Richard W.M. Jones
2014-12-09 11:42 ` Peter Maydell
2014-12-09 12:33 ` Dr. David Alan Gilbert [this message]
2014-12-09 13:48 ` 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=20141209123321.GD5272@work-vm \
--to=dgilbert@redhat.com \
--cc=kchamart@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rjones@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).