* Re: [Qemu-devel] [OVMF+VIFO+QEMU] Large VM RAM allocation = Long Boot Times
[not found] <CAP2KGUnz+vLfSX9+9bgBohKhJ-JxZPQY253M3tPX=Zn3KUzdMg@mail.gmail.com>
@ 2018-11-15 10:34 ` Philippe Mathieu-Daudé
0 siblings, 0 replies; only message in thread
From: Philippe Mathieu-Daudé @ 2018-11-15 10:34 UTC (permalink / raw)
To: A Z, edk2-devel, QEMU Developers
Cc'ing qemu-devel@
On 15/11/18 6:58, A Z wrote:
> 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] only message in thread
only message in thread, other threads:[~2018-11-15 10:35 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <CAP2KGUnz+vLfSX9+9bgBohKhJ-JxZPQY253M3tPX=Zn3KUzdMg@mail.gmail.com>
2018-11-15 10:34 ` [Qemu-devel] [OVMF+VIFO+QEMU] Large VM RAM allocation = Long Boot Times Philippe Mathieu-Daudé
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).