mirror of
https://github.com/virt-manager/virt-manager.git
synced 2024-12-22 13:34:07 +03:00
9c45f4a2e9
Strip back the logic to: * Only try to toggle source_type=memfd and access_mode=shared * Disable the field if guest has any <numa> config * Disable the field if domcaps does not report virtiofs and memfd This is the simplest future proof case, though it will exclude some legit guest configs and some libvirt+qemu back compat. My feeling is the <numa> stuff in particular is pretty advanced, so if users have it configured they can toggle shared memory via the XML without too much trouble. Signed-off-by: Cole Robinson <crobinso@redhat.com> |
||
---|---|---|
.. | ||
__init__.py | ||
blkiotune.py | ||
clock.py | ||
cpu.py | ||
cputune.py | ||
features.py | ||
idmap.py | ||
keywrap.py | ||
launch_security.py | ||
memorybacking.py | ||
memtune.py | ||
metadata.py | ||
numatune.py | ||
os.py | ||
pm.py | ||
resource.py | ||
seclabel.py | ||
sysinfo.py | ||
vcpus.py | ||
xmlnsqemu.py |