Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | docs: mention migration issue of which credentials are used | Eric Blake | 2012-05-10 | 1 | -4/+18 |
| | | | | | | | | | | | | Based on a report by Seth Vidal. Just because _you_ can use virsh to connect to both source and destinations does not mean that libvirtd on the source (aka _root_) can likewise connect to the destination; this matters when setting up a peer-to-peer migration instead of a native one. * docs/migration.html.in: Mention that in peer-to-peer, the owner of the source libvirtd (usually root) must be able to connect to the destination. | ||||
* | virterror.c: Fix several spelling mistakes | Philipp Hahn | 2012-02-03 | 1 | -1/+1 |
| | | | | | | | | | compat{a->i}bility erron{->e}ous nec{c->}essary. Either "the" or "a". Signed-off-by: Philipp Hahn <hahn@univention.de> | ||||
* | Add documentation about migration. | Daniel P. Berrange | 2011-10-28 | 1 | -0/+601 |
This adds a page documenting many aspects of migration: - The types of migration (managed direct, p2p, unmanaged direct) - Data transports (native, tunnelled) - Migration URIs - Config file handling - Example scenarios * libvirt.css: Rules for data tables and diagrams * Makefile.am: Include extra png/fig files * migration-managed-direct.fig, migration-managed-direct.png, migration-managed-direct.png, migration-managed-p2p.png, migration-native.fig, migration-native.png, migration-tunnel.fig, migration-tunnel.png, migration-unmanaged-direct.fig, migration-unmanaged-direct.png: Diagrams of migration * migration.html.in, sitemap.html.in: New migration doc |