From: Andrea Bolognani <abologna@redhat.com>
To: Andrew Jones <drjones@redhat.com>,
"Zhang, Lei" <zhang.lei@jp.fujitsu.com>
Cc: "Mizuma, Masayoshi" <masayoshi.mizuma@fujitsu.com>,
"Okamoto, Takayuki" <tokamoto@jp.fujitsu.com>,
"'qemu-devel@nongnu.org'" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v3 00/15] target/arm/kvm: enable SVE in guests
Date: Tue, 20 Aug 2019 10:45:11 +0200 [thread overview]
Message-ID: <31906efac93bec3cd5aceddcd79ff4e62bb64391.camel@redhat.com> (raw)
In-Reply-To: <20190820075328.ew6kfiozom2ptcjv@kamzik.brq.redhat.com>
On Tue, 2019-08-20 at 09:53 +0200, Andrew Jones wrote:
> On Tue, Aug 20, 2019 at 06:08:04AM +0000, Zhang, Lei wrote:
> > Hi Andrew,
> >
> > I have tested your patch on kernel- 5.2.7 + QEMU (4.0.94 + patch).
>
> Thanks for the testing! I guess it's time for me to get back to this
> series and spin a v4 (so we can test some more :-)
>
> > This patch series works fine for my tests when use qemu-system-aarch64 directly.
> > But I can't startup kvm when I use virsh[1].
> >
> > Command I executed.
> > # virsh start test1
> >
> > The error message is [internal error: CPU features not supported by hypervisor for aarch64 architecture.]
> > Do you have any ideas for this error?
>
> I've CC'ed Andrea.
I've specifically patched out that check in my series... Are you
sure you're using the modified libvirt version, and that your guest
is configured to use the modified QEMU binary?
Anyway, once v4 has been posted I'll respin the libvirt series as
well, since in the meantime conflicts have popped up and it no longer
applies cleanly on top of master.
--
Andrea Bolognani / Red Hat / Virtualization
next prev parent reply other threads:[~2019-08-20 8:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 6:08 [Qemu-devel] [PATCH v3 00/15] target/arm/kvm: enable SVE in guests Zhang, Lei
2019-08-20 7:53 ` Andrew Jones
2019-08-20 8:45 ` Andrea Bolognani [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-08-02 12:25 Andrew Jones
2019-08-15 8:31 ` Peter Maydell
2019-08-15 8:45 ` Andrew Jones
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=31906efac93bec3cd5aceddcd79ff4e62bb64391.camel@redhat.com \
--to=abologna@redhat.com \
--cc=drjones@redhat.com \
--cc=masayoshi.mizuma@fujitsu.com \
--cc=qemu-devel@nongnu.org \
--cc=tokamoto@jp.fujitsu.com \
--cc=zhang.lei@jp.fujitsu.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).