mirror of
https://github.com/virt-manager/virt-manager.git
synced 2025-02-25 18:55:27 -06:00
7547905d79
This was proposed here: https://www.redhat.com/archives/virt-tools-list/2019-June/msg00117.html """ * UI maxmem and maxcpu notions, and related memballoon and cpu hotplug operations. These have been in the UI forever but I'm not sure people actually use them. cpu hotplug has always been a mess, and unless the user plans ahead by setting a high maxmem value ballooning is only good for reducing memory. These all sound like advanced usage to me that just confuses the typical usecase of adding more mem or vcpus to an offline VM. And the hotplug operations with virsh are simple to invoke. So I'd like to drop this from the UI """ The remaining field sets both max and current memory in the inactive XML Signed-off-by: Cole Robinson <crobinso@redhat.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
- All comments / suggestions / patches should be directed 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.