On 04/11/2014 17:14, Igor Mammedov wrote: >> > Note that option ROM BARs (which are usually mapped only by firmware, >> > but also when accessed via sysfs) and device assignment both consume >> > memory slots. Slots occupied by pflash can also come and go, depending >> > on whether the flash is visible as ROM or in programming mode. > Then there is a bigger problem, once KVM slots are saturated QEMU will crash > if one of above actions from guest happens, and we can't even error out on > them.
Yes. I wish I had a better idea than checking for free memslots manually in all of them. Paolo
