From: Simon <wei.guo.simon@gmail.com>
To: qemu-devel@nongnu.org
Subject: Does memory hotplug work when VFIO device already attached
Date: Sun, 17 May 2020 11:47:06 +0800 [thread overview]
Message-ID: <CAB3_kSXU1FUMuTD1ibo88hV0ja+PCmFTCB+JX6dXWoNORR-EYQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 629 bytes --]
Hi,
I am trying do memory hotplug(add new memory DIMM) in an VM attached with
VFIO device (host running with 4.9 kernel). What I observed is weird:
If my original VM is 10G (already occupies 10G RSS at host), and hotplug
add 30G DIMM to qemu, the RSS of qemu keeps growing until nearly 39G and
suddenly drops down to 10G or ever lower. Then the RSS grows again towards
40G. The free of host keeps decreasing and it triggers OOM at last.
My question is: is this scenario valid and ever supported? (maybe some bugs
in my environment). Is there any known problem to Qemu memory hotplug
(attached VFIO device)?
Thanks,
- Simon
[-- Attachment #2: Type: text/html, Size: 746 bytes --]
reply other threads:[~2020-05-17 3:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAB3_kSXU1FUMuTD1ibo88hV0ja+PCmFTCB+JX6dXWoNORR-EYQ@mail.gmail.com \
--to=wei.guo.simon@gmail.com \
--cc=qemu-devel@nongnu.org \
/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).