Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upIf meminfo-writer/qmemman needs to be disabled for VMs with PCI devices, it should be done by dom0 and not by the VM for PCI hotplug #3248
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
This is a duplicate of #3207 |
marmarek
closed this
Oct 28, 2017
andrewdavidwong
added
the
duplicate
label
Oct 28, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
qubesuser commentedOct 28, 2017
Currently /usr/lib/qubes/init/qubes-sysinit.sh disables meminfo-writer if it finds a non-Qemu PCI device upon initialization.
However, this behavior obviously doesn't work properly with PCI hotplug, so it should be qmemman that doesn't balance memory on domains with PCI devices attached rather than the VM deciding to not run meminfo-writer.
Also, I'm not sure why this is needed at all: if all qmemman does is cause Xen balloon inflation, why would having PCI devices attached matter?