Go to file
Lin Ma b4189a925b details: Add new checkbox to control shared memory access
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>
2022-01-25 12:26:14 -05:00
.github github: Update issue template 2021-05-28 15:47:10 -04:00
data Improve Secret Service interoperability 2021-04-06 18:30:08 -04:00
man virtinst: prefer cores when exposing topology to the guest 2022-01-20 14:16:38 -05:00
po Translated using Weblate (Portuguese (Brazil)) 2021-04-14 14:50:59 -04:00
tests guest: Remove the hyperv + uefi workaround for win7 + win2k8r2 2022-01-25 12:05:45 -05:00
ui details: Add new checkbox to control shared memory access 2022-01-25 12:26:14 -05:00
virtManager details: Add new checkbox to control shared memory access 2022-01-25 12:26:14 -05:00
virtinst domain: cpu: Add function all_shared_memAccess_cells() 2022-01-25 12:26:14 -05:00
.coveragerc tests: Add full test coverage for progress text output 2021-06-09 16:52:12 -04:00
.gitignore Add the translation catalog 2020-07-11 14:59:56 -04:00
.gitpublish git: add a git publish configuration file 2018-04-30 13:35:32 -04:00
.mailmap Add .mailmap 2013-04-03 18:13:25 -04:00
.pylintrc misc: fix spelling 2021-10-04 16:26:08 -04:00
CONTRIBUTING.md docs: Add github ISSUE_TEMPLATE 2020-09-20 14:35:05 -04:00
COPYING COPYING: use license file from gnu.org 2021-10-04 16:26:08 -04:00
DESIGN.md DESIGN: Hiding viewer menu bar has been rejected 2021-03-10 16:55:19 -05:00
INSTALL.md docs: Add github ISSUE_TEMPLATE 2020-09-20 14:35:05 -04:00
MANIFEST.in Add DESIGN.md 2020-01-26 12:14:18 -05:00
NEWS.md misc: trim excess whitespace 2021-10-04 16:26:08 -04:00
README.md README.md: clarify mailing list patch usage 2021-07-30 12:02:13 -04:00
setup.cfg setup: Add --tb=native to pytest options 2020-08-26 15:20:06 -04:00
setup.py Replace deprecated `imp` usage with `importlib` 2021-10-04 16:04:44 -04:00
virt-clone virt-*: invoke python3 using /usr/bin/env 2021-10-04 16:26:08 -04:00
virt-install virt-*: invoke python3 using /usr/bin/env 2021-10-04 16:26:08 -04:00
virt-manager virt-*: invoke python3 using /usr/bin/env 2021-10-04 16:26:08 -04:00
virt-manager.spec spec: Remove shebang fixup 2021-06-22 19:48:19 -04:00
virt-xml virt-*: invoke python3 using /usr/bin/env 2021-10-04 16:26:08 -04:00

README.md

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 machines
  • virt-clone: Duplicate existing libvirt virtual machines
  • virt-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