Desktop tool for managing virtual machines via libvirt
Go to file
Cole Robinson 227d6982ae virtManager: Drop macvtap 'source mode' UI
Some related bits were discussed here:
https://www.redhat.com/archives/virt-tools-list/2019-June/msg00117.html

"""
  * macvtap is kinda problematic in general because it doesn't provide
    out of the box host<->guest communication, and it requires a
    special XML option just to get working ipv6. Users that know they
    want it usually know this distinction, but if someone chooses it
    without understanding the implications it can cause confusion.
    This puts it hovering the intermediate/advanced user line which
    makes me want to not advertise it as prominently as we currently do,
    with an explicit list of host interfaces
"""

Part of this is that the only source_mode that will work in a useful
way for the vast majority of users is mode=bridge. Any of the other
modes either require special hardware, permissions, or other
configuration. Default to bridge mode. The XML editor is there for
anyone that knows they need something different

Signed-off-by: Cole Robinson <crobinso@redhat.com>
2020-01-26 11:39:34 -05:00
data data: appstream: add keywords and translations link 2019-06-14 16:09:29 -04:00
man cli: Clarify that --controller address= is not the preferred pattern 2020-01-25 14:30:07 -05:00
po Prep for release 2.2.1 2019-07-03 20:25:19 -04:00
tests virtManager: Drop macvtap 'source mode' UI 2020-01-26 11:39:34 -05:00
ui virtManager: Drop macvtap 'source mode' UI 2020-01-26 11:39:34 -05:00
virtinst cli: Clarify that --controller address= is not the preferred pattern 2020-01-25 14:30:07 -05:00
virtManager virtManager: Drop macvtap 'source mode' UI 2020-01-26 11:39:34 -05:00
.coveragerc virtinst: Add full test coverage for xml*.py files 2019-06-09 19:00:03 -04:00
.gitignore Remove virt-convert 2020-01-24 17:04:29 -05: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
CONTRIBUTING.md docs: Multiple updates 2019-05-16 16:31:27 -04:00
COPYING Refresh GPL text with latest FSF address & fix spec file license tag 2007-11-20 11:12:20 -05:00
INSTALL.md INSTALL.md: We enforce python >= 3.4, not >= 3.3 2019-06-18 09:55:08 -04:00
MANIFEST.in Remove virt-convert 2020-01-24 17:04:29 -05:00
NEWS.md Prep for release 2.2.1 2019-07-03 20:25:19 -04:00
pylintrc Move tests/pylint.cfg to pylintrc 2019-01-30 17:25:14 -05:00
README.md Remove virt-convert 2020-01-24 17:04:29 -05:00
setup.cfg setup.cfg: Drop unicode, it upsets CI 2019-01-30 18:01:20 -05:00
setup.py Remove virt-convert 2020-01-24 17:04:29 -05:00
virt-clone Switch to more traditional logging structure 2019-06-17 00:12:31 -04:00
virt-install cli: Default lxc:/// memory to 1024, and print it 2020-01-15 11:07:42 -05:00
virt-manager pollhelpers: Kill old style polling 2020-01-24 17:04:18 -05:00
virt-manager.spec.in Remove virt-convert 2020-01-24 17:04:29 -05:00
virt-xml virt-xml: fix defined_xml_is_unchanged 2019-12-03 13:04:37 +01:00

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