From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Andrew Jones <drjones@redhat.com>, Haibo Xu <haibo.xu@linaro.org>
Cc: Markus Armbruster <armbru@redhat.com>,
Thomas Huth <thuth@redhat.com>,
qemu-arm@nongnu.org, qemu-devel@nongnu.org,
Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: Core dump happened when starting a VM on arm64 server
Date: Wed, 17 Jun 2020 15:11:50 +0200 [thread overview]
Message-ID: <c1dee39b-39e1-0b56-eba6-8890f59a66f5@redhat.com> (raw)
In-Reply-To: <e47664d7-a13e-7f60-975d-97f085036067@redhat.com>
On 6/17/20 12:32 PM, Philippe Mathieu-Daudé wrote:
> On 6/17/20 10:23 AM, Philippe Mathieu-Daudé wrote:
>> On 6/11/20 11:14 AM, Andrew Jones wrote:
>>> On Thu, Jun 11, 2020 at 04:46:45PM +0800, Haibo Xu wrote:
>>>> Hi,
>>>>
>>>> I met a qemu core dump issue when starting a VM with cpu feature
>>>> "pmu=on" on an arm server.
>>>> The commands to start the machine is:
>>>>
>>>> ./qemu-system-aarch64 \
>>>> -cpu host,pmu=on -M virt,accel=kvm,gic-version=3 -nographic
>>>> -m 2048M \
>>>> -kernel ./Image \
>>>> -initrd /boot/initrd.img-5.6.0-rc2+ \
>>>> -append "root=/dev/vda rw console=ttyAMA0" -nodefaults -serial stdio\
>>>> -drive if=none,file=./xenial.rootfs.ext4,id=hd0,format=raw \
>>>> -device virtio-blk-device,drive=hd0
>>>>
>>>>
>>>> And here is the stack dump:
>>>>
>>>> Core was generated by `./qemu-system-aarch64 -cpu host,pmu=on -M
>>>> virt,accel=kvm,gic-version=3 -nograph'.
>>>> Program terminated with signal SIGSEGV, Segmentation fault.
>>>> #0 kvm_ioctl (s=0x0, type=type@entry=44547) at
>>>
>>> s=0x0 means cpu->kvm_state is NULL
>>>
>>>> The root cause is in the arm_get_pmu() operation which was introduced
>>>> in ae502508f83.
>>>
>>> Actually the root cause is d70c996df23f ("target/arm/kvm: Use
>>> CPUState::kvm_state in kvm_arm_pmu_supported()"). ae502508f83 used
>>> the machine kvm_state, not the cpu kvm_state, and that allows pmu=on
>>> to work. d70c996df23f changed that saying that "KVMState is already
>>> accessible via CPUState::kvm_state, use it.", but I'm not sure why,
>>> since kvm_init_vcpu() doesn't run until the vcpu thread is created.
>>>
>>> Philippe?
>>
>> Sorry for some reason I missed this email. I'll look at this today.
>
> Quick reproducer:
>
> $ qemu-system-aarch64 -cpu host,pmu=on -M virt,accel=kvm,gic-version=3
> Segmentation fault (core dumped)
Fix sent:
https://www.mail-archive.com/qemu-devel@nongnu.org/msg713249.html
prev parent reply other threads:[~2020-06-17 13:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 8:46 Core dump happened when starting a VM on arm64 server Haibo Xu
2020-06-11 9:14 ` Andrew Jones
2020-06-17 8:23 ` Philippe Mathieu-Daudé
2020-06-17 10:32 ` Philippe Mathieu-Daudé
2020-06-17 10:42 ` Thomas Huth
2020-06-17 12:19 ` Andrew Jones
2020-06-17 13:11 ` Philippe Mathieu-Daudé [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=c1dee39b-39e1-0b56-eba6-8890f59a66f5@redhat.com \
--to=philmd@redhat.com \
--cc=armbru@redhat.com \
--cc=drjones@redhat.com \
--cc=ehabkost@redhat.com \
--cc=haibo.xu@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--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).