public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
* [OVMF+VIFO+QEMU] Large VM RAM allocation = Long Boot Times
@ 2018-11-15  5:58 A Z
  2018-11-15 10:34 ` Philippe Mathieu-Daudé
  2018-11-15 10:39 ` Laszlo Ersek
  0 siblings, 2 replies; 3+ messages in thread
From: A Z @ 2018-11-15  5:58 UTC (permalink / raw)
  To: edk2-devel

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


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2018-11-15 10:39 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-11-15  5:58 [OVMF+VIFO+QEMU] Large VM RAM allocation = Long Boot Times A Z
2018-11-15 10:34 ` Philippe Mathieu-Daudé
2018-11-15 10:39 ` Laszlo Ersek

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox