From: A Z <adam@zegelin.com>
To: edk2-devel@lists.01.org
Subject: [OVMF+VIFO+QEMU] Large VM RAM allocation = Long Boot Times
Date: Wed, 14 Nov 2018 21:58:01 -0800 [thread overview]
Message-ID: <CAP2KGUnz+vLfSX9+9bgBohKhJ-JxZPQY253M3tPX=Zn3KUzdMg@mail.gmail.com> (raw)
This is an issue that involves a combination of different software
packages, so my apologies in advance if this is the wrong list to post on.
I'm experiencing terrible boot times when I assign a large amount of RAM to
a VM when used in combination with VIFO/PCI-passthrough.
On a VM with a Nvidia GTX 970 + USB controller and 24GiB of RAM assigned,
the time to the TianoCore splash screen is ~5 minutes. It's then ~30
seconds before Windows 10 begins to boot (spinning dots). During this time,
the QEMU CPU core threads are 100% busy.
According to `perf`, the QMU CPU core threads are spending most of their
time waiting on a spinlock over kvm->mmu_lock that's created by
kvm_zap_gfn_range.
I'm fairly certain that ~1 year ago (if not longer) the same configuration
didn't take this long to boot.
Regards,
Adam
next reply other threads:[~2018-11-15 5:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 5:58 A Z [this message]
2018-11-15 10:34 ` [OVMF+VIFO+QEMU] Large VM RAM allocation = Long Boot Times Philippe Mathieu-Daudé
2018-11-15 10:39 ` Laszlo Ersek
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-list 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='CAP2KGUnz+vLfSX9+9bgBohKhJ-JxZPQY253M3tPX=Zn3KUzdMg@mail.gmail.com' \
--to=devel@edk2.groups.io \
/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