mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2025-02-22 11:22:23 +00:00
qemu: Reduce memlock limit after detaching PCI hostdev
We increase the limit before plugging in a PCI hostdev or a memory module because some memory might need to be locked due to eg. VFIO. Of course we should do the opposite after unplugging a device: this was already the case for memory modules, but not for PCI hostdevs.
This commit is contained in:
parent
65909c7996
commit
b583e80cb8
@ -3051,6 +3051,10 @@ qemuDomainRemoveHostDevice(virQEMUDriverPtr driver,
|
|||||||
switch ((virDomainHostdevSubsysType) hostdev->source.subsys.type) {
|
switch ((virDomainHostdevSubsysType) hostdev->source.subsys.type) {
|
||||||
case VIR_DOMAIN_HOSTDEV_SUBSYS_TYPE_PCI:
|
case VIR_DOMAIN_HOSTDEV_SUBSYS_TYPE_PCI:
|
||||||
qemuDomainRemovePCIHostDevice(driver, vm, hostdev);
|
qemuDomainRemovePCIHostDevice(driver, vm, hostdev);
|
||||||
|
/* QEMU might no longer need to lock as much memory, eg. we just
|
||||||
|
* detached the last VFIO device, so adjust the limit here */
|
||||||
|
if (qemuDomainAdjustMaxMemLock(vm) < 0)
|
||||||
|
VIR_WARN("Failed to adjust locked memory limit");
|
||||||
break;
|
break;
|
||||||
case VIR_DOMAIN_HOSTDEV_SUBSYS_TYPE_USB:
|
case VIR_DOMAIN_HOSTDEV_SUBSYS_TYPE_USB:
|
||||||
qemuDomainRemoveUSBHostDevice(driver, vm, hostdev);
|
qemuDomainRemoveUSBHostDevice(driver, vm, hostdev);
|
||||||
@ -3076,6 +3080,7 @@ qemuDomainRemoveHostDevice(virQEMUDriverPtr driver,
|
|||||||
networkReleaseActualDevice(vm->def, net);
|
networkReleaseActualDevice(vm->def, net);
|
||||||
virDomainNetDefFree(net);
|
virDomainNetDefFree(net);
|
||||||
}
|
}
|
||||||
|
|
||||||
ret = 0;
|
ret = 0;
|
||||||
|
|
||||||
cleanup:
|
cleanup:
|
||||||
|
Loading…
x
Reference in New Issue
Block a user