[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[Libguestfs] [PATCH 1/2] v2v: document Debian/Ubuntu support



---
 v2v/virt-v2v.pod | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)

diff --git a/v2v/virt-v2v.pod b/v2v/virt-v2v.pod
index 4c7204b..ba91851 100644
--- a/v2v/virt-v2v.pod
+++ b/v2v/virt-v2v.pod
@@ -227,6 +227,10 @@ And hence L<virsh(1)>, L<virt-manager(1)>, and similar tools.
 
 =item OpenSUSE 10 and up
 
+=item Debian 6 and up
+
+=item Ubuntu 10.04, 12.04, 14.04, 16.04, and up
+
 =item Windows XP to Windows 8.1 / Windows Server 2012 R2
 
 We use Windows internal version numbers, see
@@ -758,6 +762,10 @@ below.
  
  OpenSUSE 10    kernel >= 2.6.25.5-1.1
 
+ Debian 6+      All versions support virtio
+
+ Ubuntu 10.04+  All versions support virtio
+
  Windows        Drivers are installed from the directory pointed to by
                 "VIRTIO_WIN" environment variable
                 (/usr/share/virtio-win by default) if present
@@ -792,6 +800,18 @@ RHEL 6, so you will need to update to any version E<ge> 6.3 before
 performing the conversion.  See also
 L<https://bugzilla.redhat.com/show_bug.cgi?id=1374232>
 
+=head1 DEBIAN AND UBUNTU
+
+=head2 "warning: could not determine a way to update the configuration of Grub2"
+
+Currently, virt-v2v has no way to set the default kernel in Debian
+and Ubuntu guests using GRUB 2 as bootloader.  This means that
+virt-v2v will not change the default kernel used for booting, even
+in case it is not the best kernel available on the guest.
+A recommended procedure is, before using virt-v2v, to check that the
+boot kernel is the best kernel available in the guest (for example
+by making sure the guest is up-to-date).
+
 =head1 WINDOWS
 
 =head2 Windows E<ge> 8 Fast Startup is incompatible with virt-v2v
-- 
2.9.3


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]