mirror of
https://github.com/virt-manager/virt-manager.git
synced 2025-02-25 18:55:27 -06:00
b4189a925b
The virtiofs in domcapabilities is used as a proxy to tell us whether libvirt is new enough to allow bare memory access mode=shared', So We enable/disable this checkbox according to it. When we configure shared memory access, If the 'memfd' is available in domcaps, We configure VM to use it as memory backend because it doesn't need addtional host setup for vhost-user devices, Otherwise use 'file' as backend. If all of numa nodes explicitly defined memAccess=shared, We mark this checkbox as checked even if virtiofs isn't exposed in domcapabilities. In this case: - It doesn't matter what the value of access mode of memoryBacking is because access mode of memoryBacking will be overridden per numa node by memAccess attribute. - Although the checkbox is disabled, the checked checkbox presents actual status about shared memory access to users. Signed-off-by: Lin Ma <lma@suse.com>
Virtual Machine Manager
virt-manager is a graphical tool for managing virtual machines
via libvirt. Most usage is with QEMU/KVM
virtual machines, but Xen and libvirt LXC containers are well
supported. Common operations for any libvirt driver should work.
Several command line tools are also provided:
virt-install: Create new libvirt virtual machinesvirt-clone: Duplicate existing libvirt virtual machinesvirt-xml: Edit existing libvirt virtual machines/manipulate libvirt XML
For dependency info and installation instructions, see the INSTALL.md file. If you just want to quickly test the code from a git checkout, you can launch any of the commands like:
./virt-manager --debug ...
Contact
- Discussions and big patch series should go to the virt-tools-list mailing list.
- For IRC we use #virt on OFTC.
- For bug reporting info, see virt-manager bug reporting.
- There are further project details on the virt-manager website.
- See the CONTRIBUTING.md file for info about submitting patches or contributing translations.