[Libguestfs] [PATCH 6/9] Documentation: Update virt-v2v man page

Matthew Booth mbooth at redhat.com
Fri Feb 12 15:41:42 UTC 2010


On 12/02/10 13:16, Richard W.M. Jones wrote:
> On Fri, Feb 12, 2010 at 09:39:19AM +0000, Matthew Booth wrote:
>> +Since version 0.8.3, virt-manager(1) can also create and manage bridges.
> 
> Should be L<virt-manager(1)>.

Indeed. I've fixed a few others too.

>> +You can avoid having to specify replacement kernels by ensuring that the guest
>> +has a fully virt kernel installed prior to conversion. Note that it doesn't have
>> +to be the default kernel.
> 
> Do you think it's clear enough to people what terms like 'fully virt
> kernel' mean?  It might be worth mentioning that kernels installed
> from the 'kernel-xen-*' RPMs are Xen PV kernels, and kernels installed
> from the 'kernel-*' RPMs are the full virt kernels.

How about:

It is possible to avoid specifying replacement kernels in the virt-v2v
config
file by ensuring that the guest has an appropriate kernel installed prior to
conversion. If your guest uses a Xen paravirtualised kernel (it would be
called
something like kernel-xen or kernel-xenU), you can install a regular kernel,
which won't reference a hypervisor in its name, along side it. You shouldn't
make this newly installed kernel your default kernel because the chances are
Xen will not boot it. virt-v2v will make it the default during conversion.

Matt
-- 
Matthew Booth, RHCA, RHCSS
Red Hat Engineering, Virtualisation Team

M:       +44 (0)7977 267231
GPG ID:  D33C3490
GPG FPR: 3733 612D 2D05 5458 8A8A 1600 3441 EA19 D33C 3490




More information about the Libguestfs mailing list