From: Igor Mammedov <imammedo@redhat.com>
To: Yangming via <qemu-devel@nongnu.org>
Cc: Yangming <yangming73@huawei.com>,
"mst@redhat.com" <mst@redhat.com>,
"ani@anisinha.ca" <ani@anisinha.ca>,
"wangzhigang (O)" <wangzhigang17@huawei.com>,
"zhangliang (AG)" <zhangliang5@huawei.com>,
David Hildenbrand <david@redhat.com>
Subject: Re: VM crashed while hot-plugging memory
Date: Thu, 23 Feb 2023 20:32:41 +0100 [thread overview]
Message-ID: <20230223203241.28d38c29@imammedo.users.ipa.redhat.com> (raw)
In-Reply-To: <d9e62d4914a24b63af9f94a0e99b32c9@huawei.com>
On Fri, 10 Feb 2023 09:30:18 +0000
Yangming via <qemu-devel@nongnu.org> wrote:
> Hello all:
>
> I found VM crashed while hot-plugging memory.
>
> Base infomation:
> qemu version: qemu-master
> requirements: hugepages, virtio-gpu
>
> It happens by the following steps:
> 1. Booting a VM with hugepages and a virtio-gpu device.
> 2. Connecting VNC of the VM.
> 3. After the VM booted, hot-plugging 512G memory.
> 4. Then you can find that the image in vnc is blocked and the worse thing is that the VM crashed.
>
> Actually the vcpu is blocked because of dead lock.
>
> Analysis:
> As when hot-pluging the BQL is held, at the meanwhile, virtio-gpu is trying to hold the BQL for writing date. Then a vcpu is blocked waiting for hugepages hot-plugging, specifically, waiting for touching pages. If the blocked vcpu stops for several seconds, the soft lockup will happen, if it stops for a long time, e.g. 30s, the VM will crash.
>
> I am wandering if there are some ideas to avoid VM soft lockup and even VM crash ?
Maybe David can suggest something
(CCed)
>
> Thank you!
> kind regards!
next prev parent reply other threads:[~2023-02-23 19:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 9:30 VM crashed while hot-plugging memory Yangming via
2023-02-23 19:32 ` Igor Mammedov [this message]
2023-02-27 15:49 ` David Hildenbrand
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=20230223203241.28d38c29@imammedo.users.ipa.redhat.com \
--to=imammedo@redhat.com \
--cc=ani@anisinha.ca \
--cc=david@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wangzhigang17@huawei.com \
--cc=yangming73@huawei.com \
--cc=zhangliang5@huawei.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).