From: Auger Eric <eric.auger@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
Prakash B <bjsprakash.linux@gmail.com>
Cc: Marc Zyngier <marc.zyngier@arm.com>,
bprakash@caviumnetworks.com,
QEMU Developers <qemu-devel@nongnu.org>,
"Kumar, Vijaya" <Vijaya.Kumar@cavium.com>,
qemu-arm <qemu-arm@nongnu.org>,
sgoutham@cavium.com,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
Christoffer Dall <christoffer.dall@linaro.org>
Subject: Re: [Qemu-devel] Aarch64: Qemu master or 2.9.0-rc1 breaks compatibility with 4.10 kernel.
Date: Tue, 28 Mar 2017 13:59:11 +0200 [thread overview]
Message-ID: <43d097e6-a74a-ed22-0b28-3f151d3e51fb@redhat.com> (raw)
In-Reply-To: <CAFEAcA-kKvS_6OZE1mKbFYgCzm4wPK2XJi_A03nFxu+K3ZA4hQ@mail.gmail.com>
Hi Peter,
On 28/03/2017 13:29, Peter Maydell wrote:
> On 28 March 2017 at 12:22, Prakash B <bjsprakash.linux@gmail.com> wrote:
>> Qemu master or v2.9.0-rc1 doesn't launch guest when host kernel
>> version 4.10 or lower on Aarch64 (cavium ThunderX), its failing with
>> abort "qemu-system-aarch64: KVM_GET_DEVICE_ATTR failed: No such
>> device or address"
>>
>> "GICv3 live migration support" patch breaks the compatibility b/w
>> kernel and qemu.
>>
>> Is this expected behaviour, can we provide a fix without breaking
>> compatibility b/w kernel and qemu .
>
> This is indeed not supposed to happen. Eric, can you take a look?
Yes I start the investigations.
Thanks
Eric
>
> thanks
> -- PMM
>
prev parent reply other threads:[~2017-03-28 11:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 11:22 [Qemu-devel] Aarch64: Qemu master or 2.9.0-rc1 breaks compatibility with 4.10 kernel Prakash B
2017-03-28 11:29 ` Peter Maydell
2017-03-28 11:59 ` Auger Eric [this message]
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=43d097e6-a74a-ed22-0b28-3f151d3e51fb@redhat.com \
--to=eric.auger@redhat.com \
--cc=Vijaya.Kumar@cavium.com \
--cc=bjsprakash.linux@gmail.com \
--cc=bprakash@caviumnetworks.com \
--cc=christoffer.dall@linaro.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=marc.zyngier@arm.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sgoutham@cavium.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).