[Pkg-libvirt-commits] [libguestfs] 13/36: v2v: Document 7B boot problems with Windows Group Policy.

[Hilko Bengen]

This is an automated email from the git hooks/post-receive script.

bengen pushed a commit to annotated tag upstream/1.29.47
in repository libguestfs.

commit dafb4bf28378707c1f1f224d2a895e3e80bbe382
Author: Richard W.M. Jones <rjones at redhat.com>
Date:   Sat Jun 13 22:21:28 2015 +0100

    v2v: Document 7B boot problems with Windows Group Policy.
---
 v2v/virt-v2v.pod | 28 ++++++++++++++++++++++++++++
 1 file changed, 28 insertions(+)

diff --git a/v2v/virt-v2v.pod b/v2v/virt-v2v.pod
index f48ede1..b49de61 100644
--- a/v2v/virt-v2v.pod
+++ b/v2v/virt-v2v.pod
@@ -804,6 +804,34 @@ loaded.
 
 =back
 
+=head2 OpenStack and Windows reactivation
+
+OpenStack does not offer stable device / PCI addresses to guests.
+Every time it creates or starts a guest, it regenerates the libvirt
+XML for that guest from scratch.  The libvirt XML will have no
+E<lt>addressE<gt> fields.  Libvirt will then assign addresses to
+devices, in a predictable manner.  Addresses may change if any of the
+following are true:
+
+=over 4
+
+=item *
+
+A new disk or network device has been added or removed from the guest.
+
+=item *
+
+The version of OpenStack or (possibly) libvirt has changed.
+
+=back
+
+Because Windows does not like "hardware" changes of this kind, it may
+trigger Windows reactivation.
+
+This can also prevent booting with a 7B error [see previous section]
+if the guest has group policy containing
+C<Device Installation Restrictions>.
+
 =head1 UEFI
 
 VMware allows you to present UEFI firmware to guests (instead of the

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-libvirt/libguestfs.git