From: andy123 <ajs124.ajs124@gmail.com>
To: kvm@vger.kernel.org
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] problems with 1G hugepages and linux 3.12-rc3
Date: Sun, 6 Oct 2013 02:47:41 +0200 [thread overview]
Message-ID: <20131006024741.61cc8512@desk.lan> (raw)
Hi,
as the subject states, I have some problems with 1G hugepages with qemu(-vfio-git) on Linux 3.12-rc3.
I start qemu like this, for example:
"/usr/bin/qemu-system-x86_64 -enable-kvm -m 1024 -mem-path /dev/hugepages -drive file=/files/vm/arch.img,if=virtio,media=disk -monitor stdio"
where /dev/hugepages is "hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,mode=1770,gid=78,pagesize=1G,pagesize=1G)"
and the kernel is booted with "hugepagesz=1G hugepages=4".
This result in lots of error message in dmesg, as seen here: https://gist.github.com/ajs124/6842823 (starting at 18:04:28)
After starting and stopping multiple virtual machines, the hugepages seem to "fill up" and qemu outputs
"file_ram_alloc: can't mmap RAM pages: Cannot allocate memory", but works anyways.
With fill up, I mean that I can start qemu 2 time with "-m 2048" and 4 times with "-m 1024", before it fails to mmap.
This works without any problems in 3.11.x and also with 2M hugepages (umount /dev/hugepages && mount -t hugetlbfs -o pagesize=2048k /dev/hugepages).
I'm running this in arch linux and there has already been some discussion on the arch forums (https://bbs.archlinux.org/viewtopic.php?pid=1333469#p1333469) but I tried to add everything I wrote over there in this mail.
In case I missed something or you need more information, I'll happily supply it in order to get this resolved.
next reply other threads:[~2013-10-06 0:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-06 0:47 andy123 [this message]
2013-10-08 12:23 ` [Qemu-devel] problems with 1G hugepages and linux 3.12-rc3 Gleb Natapov
2013-10-10 0:22 ` Andrea Arcangeli
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=20131006024741.61cc8512@desk.lan \
--to=ajs124.ajs124@gmail.com \
--cc=kvm@vger.kernel.org \
--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).