Commit 2c530bc4 authored by Guido Günther's avatar Guido Günther

New upstream version 1.4.1

parent 18e9fead
HACKING
=======
# HACKING
The following commands will be useful for anyone writing patches:
python setup.py test : Run local unit test suite
python setup.py pylint : Run a pylint script against the codebase
```sh
python setup.py test # Run local unit test suite
python setup.py pylint # Run a pylint script against the codebase
```
Any patches shouldn't change the output of 'test' or 'pylint'. The
'pylint' requires pylint and python-pep8 to be installed.
'pylint' requires `pylint` and `python-pep8` to be installed.
Our pylint script uses a blacklist rather than a whitelist approach,
so it could throw some false positives or useless messages. If you think
your patch exposes one of these, bring it up on the mailing list.
If 'python-coverage' is installed, you can run 'coverage -r' after
'python setup.py test' finished to see a code coverage report.
If `python-coverage` is installed, you can run `coverage -r` after
`python setup.py test` finished to see a code coverage report.
'test*' have a --debug option if you are hitting problems.
For more options, use 'python setup.py test --help'.
'test*' have a `--debug` option if you are hitting problems.
For more options, use `python setup.py test --help`.
One useful way to manually test virt-manager's UI is using libvirt's
unit test driver. From the source directory, Launch virt-manager like:
```sh
virt-manager --connect test://$PWD/tests/testdriver.xml
```
virt-manager --connect test://$PWD/tests/testdriver.xml
This testdriver has many fake XML definitions that can be used to see
each bit of virt-manager's UI. It also enables testing the various wizards
without having to alter your host virt config.
This testdriver has many fake XML definitions that can be used to see each bit
of virt-manager's UI. It also enables testing the various wizards without
having to alter your host virt config.
Also, there's a few standalone specialty tests:
```sh
python setup.py test_urls # Test fetching media from distro URLs
python setup.py test_initrd_inject # Test --initrd-inject
```
python setup.py test_urls : Test fetching media from distro URLs
python setup.py test_initrd_inject: Test --initrd-inject
We use glade-3 for building virt-manager's UI. It is recommended you have
a fairly recent version of glade-3: if a small UI change seems to rewrite the
entire glade file, you likely have a too old (or too new :) glade version.
We use [glade-3](https://glade.gnome.org/) for building virt-manager's UI.
It is recommended you have a fairly recent version of `glade-3`. If a small UI
change seems to rewrite the entire glade file, you likely have a too old
(or too new :) glade version.
Submitting patches
==================
## Submitting patches
Patches should be developed against a git checkout and _not_ a source
release. The git repo is at:
Patches should be developed against a git checkout and **not** a source
release(see [git repository](https://github.com/virt-manager/virt-manager)).
https://github.com/virt-manager/virt-manager
Patches should be sent to the
[mailing list](http://www.redhat.com/mailman/listinfo/virt-tools-list).
Patches should be sent to the mailing list (see README for details). Using
git format-patch/send-email is preferred, but an attachment with
Using git format-patch/send-email is preferred, but an attachment with
format-patch output is fine too.
Small patches are acceptable via github pull-request, but anything
non-trivial should be sent to the mailing list.
## Translations
Translations
============
Translations are handled at fedora.zanata.org. Please register for a Fedora
account and request access to a translation team, as described at:
http://fedoraproject.org/wiki/L10N/Translate_on_Zanata
And contribute to virt-manager at:
Translations are handled at `fedora.zanata.org`. Please register for a Fedora
account and request access to a translation team, as described at
[Translate on Zanata](http://fedoraproject.org/wiki/L10N/Translate_on_Zanata).
https://fedora.zanata.org/project/view/virt-manager/
And contribute to
[virt-manager at Zanata](https://fedora.zanata.org/project/view/virt-manager/).
Basic Install
=============
For starters, if you just want to run virt-manager/virt-install to test out
changes, it can be done from the source directory:
./virt-manager
To install the software into /usr/local (usually), you can do:
python setup.py install
To build an RPM, you can run:
python setup.py rpm
setup.py generally has all the build and install commands, for more info see:
python setup.py --help-commands
python setup.py install --help
http://docs.python.org/inst/standard-install.html
Pre-requisite software
======================
A detailed dependency list can be found in virt-manager.spec.in
Minimum version requirements of major components:
python >= 2.7
gtk3 >= 3.14
libvirt-python >= 0.6.0
pygobject3 >= 3.14
libosinfo >= 0.2.10
On Debian or Ubuntu based distributions, you need to install the
gobject-introspection bindings for some depedencies like libvirt-glib
and libosinfo. Look for package names that start with 'gir', for example
gir1.2-libosinfo-1.0
# Basic Install
For starters, if you just want to run `virt-manager/virt-install` to test out
changes, it can be done from the source directory:
```sh
./virt-manager
```
To install the software into `/usr/local` (usually), you can do:
```sh
python setup.py install
```
To build an RPM, you can run:
```sh
python setup.py rpm
```
`setup.py` generally has all the build and install commands, for more info see:
- `python setup.py --help-commands`
- `python setup.py install --help`
- [Python Standard Build and Install](https://docs.python.org/2/install/#standard-build-and-install)
## Pre-requisite software
A detailed dependency list can be found in
[virt-manager.spec.in](virt-manager.spec.in) file.
Minimum version requirements of major components:
- python >= 2.7
- gtk3 >= 3.14
- libvirt-python >= 0.6.0
- pygobject3 >= 3.14
- libosinfo >= 0.2.10
On Debian or Ubuntu based distributions, you need to install the
`gobject-introspection` bindings for some depedencies like `libvirt-glib`
and `libosinfo`. Look for package names that start with `'gir'`, for example
`gir1.2-libosinfo-1.0`.
# to be included/excluded from the tarball produced by sdist
include COPYING HACKING INSTALL NEWS README
include COPYING HACKING.md INSTALL.md NEWS.md README.md
include MANIFEST.in
include setup.py
include virt-*
......
This diff is collapsed.
Metadata-Version: 1.0
Name: virt-manager
Version: 1.4.0
Version: 1.4.1
Summary: UNKNOWN
Home-page: http://virt-manager.org
Author: Cole Robinson
......
Virtual Machine Manager
=======================
# Virtual Machine Manager
This application provides a graphical tool for managing virtual machines
via the libvirt library.
via the [libvirt](https://libvirt.org) library.
The front end of the application uses the GTK / Glade libraries for
all user interaction components. The back end uses libvirt for managing
......@@ -10,26 +9,18 @@ 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.
For dependency info and installation instructions, see the
[INSTALL.md](INSTALL.md) file.
## Contact
- All comments / suggestions / patches should be directed to the
[virt-tools-list](http://www.redhat.com/mailman/listinfo/virt-tools-list)
mailing list.
- For IRC we use #virt on OFTC.
- For bug reporting info, see
[BugReporting](http://virt-manager.org/page/BugReporting).
- There are further project details on the
[virt-manager](http://virt-manager.org/) website.
- See the [HACKING.md](HACKING.md) file for info about submitting patches or
contributing translations.
......@@ -25,7 +25,7 @@
</screenshot>
<screenshot>
<image>http://virt-manager.org/appdata/en_US/console.png</image>
<_caption>Graphical console connection for a virtual vachine</_caption>
<_caption>Graphical console connection for a virtual machine</_caption>
</screenshot>
</screenshots>
<url type="homepage">http://www.virt-manager.org/</url>
......
......@@ -88,6 +88,12 @@ for the new guest's virtual disk. If the original guest has multiple disks,
this parameter must be repeated multiple times, once per disk in the original
virtual machine.
=item B<--nvram> NVRAMFILE
Optional path to the new nvram VARS file, if no path is specified and the
guest has nvram the new nvram path will be auto-generated. If the guest
doesn't have nvram this option will be ignored.
=item B<--force-copy> TARGET
Force cloning the passed disk target ('hdc', 'sda', etc.). By default,
......
......@@ -41,8 +41,6 @@ guest storage (--disk or --filesystem), and an install option.
=over 4
=item B<-c> URI
=item B<--connect> URI
Connect to a non-default hypervisor. If this isn't specified, libvirt
......@@ -135,6 +133,24 @@ Specify resource partitioning for the guest.
Use --resource=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#resPartition>
=item B<--sysinfo> OPT=VAL,[...]
Configure sysinfo/SMBIOS values exposed to the guest OS. '--sysinfo host' can be used to expose the host's SMBIOS info to the VM, otherwise values can be manually specified.
Use --sysinfo=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsSysinfo>
=item B<--qemu-commandline> ARGS
Pass options directly to the qemu emulator. Only works for the libvirt qemu driver. The option can take a string of arguments, for example:
--qemu-commandline="-display gtk,gl=on"
Environment variables are specified with 'env', for example:
--qemu-commandline=env=DISPLAY=:0.1
Complete details about the libvirt feature: L<https://libvirt.org/drvqemu.html#qemucommand>
=item B<--vcpus> OPTIONS
Number of virtual cpus to configure for the guest. If 'maxvcpus' is specified,
......@@ -301,6 +317,8 @@ Use --pm=? to see a list of all available sub options. Complete details at L<htt
=over 4
=item B<-c> OPTIONS
=item B<--cdrom> OPTIONS
File or device used as a virtual CD-ROM device.
......@@ -991,7 +1009,7 @@ keyboard layout. If the special value 'local' is specified, virt-install
will attempt to configure to use the same keymap as the local system. A value
of 'none' specifically defers to the hypervisor. Default behavior is
hypervisor specific, but typically is the same as 'local'. This is used
by 'vnc'
by 'vnc' and 'spice'.
=item B<password>
......@@ -1004,6 +1022,10 @@ is used by 'vnc' and 'spice'
Whether to use OpenGl accelerated rendering. Value is 'yes' or 'no'. This is
used by 'spice'.
=item B<rendernode>
DRM render node path to use. This is used when 'gl' is enabled.
=back
Use --graphics=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsGraphics>
......@@ -1659,7 +1681,7 @@ booting from PXE, using VNC server/viewer, with virtio-scsi disk
--disk path=/dev/HostVG/DemoVM,bus=scsi \
--controller virtio-scsi \
--network network=default \
--virt-type qemu
--virt-type qemu \
--graphics vnc \
--os-variant fedora9
......
......@@ -338,6 +338,10 @@ Generate XML for a virtio console device and print it to stdout:
# virt-xml --build-xml --console pty,target_type=virtio
=head1 CAVEATS
Virtualization hosts supported by libvirt may not permit all changes that might seem possible. Some edits made to a VM's definition may be ignored. For instance, QEMU does not allow the removal of certain devices once they've been defined.
=head1 BUGS
Please see http://virt-manager.org/page/BugReporting
......
This diff is collapsed.
This source diff could not be displayed because it is too large. You can view the blob instead.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
......@@ -462,7 +462,7 @@ class TestBaseCommand(distutils.core.Command):
print "%s" % test
print
t = unittest.TextTestRunner(verbosity=1)
t = unittest.TextTestRunner(verbosity=self.debug and 2 or 1)
try:
result = t.run(tests)
......
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.