mirror of
https://github.com/virt-manager/virt-manager.git
synced 2025-02-03 13:47:18 +03:00
f23b01be53
We're not including any input devices in the generated XML for s390x guests, and the results is that it's not possible to interact with them short of using the serial console or connecting through ssh, which is fine but probably not what is expected when graphics are present. USB input devices are not a good fit for s390x guests: USB requires PCI, and PCI is not widely available or used on s390x; VirtIO devices, on the other hand, are a perfect match since s390x guests use basically no emulated devices and rely on VirtIO for most functionality. https://bugzilla.redhat.com/show_bug.cgi?id=1683609 Signed-off-by: Andrea Bolognani <abologna@redhat.com>
Virtual Machine Manager
This application provides a graphical tool for managing virtual machines via the libvirt library.
The front end of the application uses the GTK / Glade libraries for all user interaction components. The back end uses libvirt for managing Qemu/KVM and Xen virtual machines, as well as LXC containers. The UI is primarily tested with KVM, but is intended to be reasonably portable to any virtualization backend libvirt supports.
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 XMLvirt-convert: Convert VMX or OVF configs to libvirt virtual machines
For dependency info and installation instructions, see the INSTALL.md file.
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 BugReporting.
- There are further project details on the virt-manager website.
- See the HACKING.md file for info about submitting patches or contributing translations.