qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Yangming via <qemu-devel@nongnu.org>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"mst@redhat.com" <mst@redhat.com>,
	"imammedo@redhat.com" <imammedo@redhat.com>,
	"ani@anisinha.ca" <ani@anisinha.ca>
Cc: "wangzhigang (O)" <wangzhigang17@huawei.com>,
	"zhangliang (AG)" <zhangliang5@huawei.com>
Subject: VM crashed while hot-plugging memory
Date: Fri, 10 Feb 2023 09:30:18 +0000	[thread overview]
Message-ID: <d9e62d4914a24b63af9f94a0e99b32c9@huawei.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 948 bytes --]

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 ?

Thank you!
kind regards!

[-- Attachment #2: Type: text/html, Size: 6252 bytes --]

             reply	other threads:[~2023-02-10  9:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-10  9:30 Yangming via [this message]
2023-02-23 19:32 ` VM crashed while hot-plugging memory Igor Mammedov
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=d9e62d4914a24b63af9f94a0e99b32c9@huawei.com \
    --to=qemu-devel@nongnu.org \
    --cc=ani@anisinha.ca \
    --cc=imammedo@redhat.com \
    --cc=mst@redhat.com \
    --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).