From: Linhaifeng <haifeng.lin@huawei.com>
To: qemu-devel@nongnu.org
Cc: liuyongan@huawei.com, lilijun <jerry.lilijun@huawei.com>
Subject: [Qemu-devel] is qemu-2.1 support 1G hugepage
Date: Fri, 24 Oct 2014 16:22:01 +0800 [thread overview]
Message-ID: <544A0C29.5050506@huawei.com> (raw)
Hi,
I run qemu2.1 with 1G hugepage and found that VM can't start (too slowly?) but can start with 2M hugepage quickly.
kernel version:3.10.0-123.6.3.el7.x86_64
command:qemu-kvm -name vm1 -enable-kvm -smp 2 -m 2048 -object memory-backend-file,id=mem,size=2048M,mem-path=/dev/hugepages,share=on -numa node,memdev=mem \
-chardev socket,id=chr0,path=/path/socket -netdev type=vhost-user,id=net0,chardev=chr0 -device virtio-net-pci,netdev=net0,mac=00:00:00:00:00:01
-drive file=/mnt/sdb/imgs/vm1.img -vnc :0
--
Regards,
Haifeng
next reply other threads:[~2014-10-24 8:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 8:22 Linhaifeng [this message]
2014-10-27 3:34 ` [Qemu-devel] is qemu-2.1 support 1G hugepage Michal Privoznik
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=544A0C29.5050506@huawei.com \
--to=haifeng.lin@huawei.com \
--cc=jerry.lilijun@huawei.com \
--cc=liuyongan@huawei.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).