58ac786b6b
We have this option --dry-run that should run through the
installation process but don't actually touch anything. Just
pretend the installation. And we have a test that uses it
heavily. However, the test is failing:
Traceback (most recent call last):
File "/home/zippy/work/virt-manager.git/tests/clitest.py", line 161, in _launch_command
ret = virtconvert.main(conn=conn)
File "virt-convert", line 111, in main
destdir=options.destination, dry=options.dry)
File "/home/zippy/work/virt-manager.git/virtconv/formats.py", line 314, in convert_disks
newpath)
RuntimeError: New path name '/var/lib/libvirt/images/fedora.qcow2' already exists
Problem is, even in test suite we really touch the host paths.
This in general will spit unpredictable results. Resolution
consists of making this specific part of the code fault tolerant
if ran under test suite.
Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
|
||
|---|---|---|
| data | ||
| man | ||
| po | ||
| tests | ||
| ui | ||
| virtManager | ||
| virtcli | ||
| virtconv | ||
| virtinst | ||
| .gitignore | ||
| .mailmap | ||
| COPYING | ||
| HACKING | ||
| INSTALL | ||
| MANIFEST.in | ||
| NEWS | ||
| README | ||
| setup.py | ||
| virt-clone | ||
| virt-convert | ||
| virt-install | ||
| virt-manager | ||
| virt-manager.spec.in | ||
| virt-xml | ||
README
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. For dependency info and installation instructions, see the INSTALL file Contact ======= All comments / suggestions / patches should be directed to the virt-tools-list mailing list: http://www.redhat.com/mailman/listinfo/virt-tools-list For IRC we use #virt on OFTC. For bug reporting info, see: http://virt-manager.org/page/BugReporting There are further project details on the website: http://virt-manager.org/ See the HACKING file for info about submitting patches or contributing translations.