From a93d4a9dc1aea6940886c85d4b09f21cbfc80969 Mon Sep 17 00:00:00 2001
From: "Richard W.M. Jones" <rjones@redhat.com>
Date: Mon, 27 Feb 2012 19:39:11 +0000
Subject: resize: Document steps to avoid UNMOUNTABLE_BOOT_VOLUME BSOD
 (RHBZ#797986).

(Thanks Grant Williamson for finding and fixing this problem)
---
 resize/virt-resize.pod | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/resize/virt-resize.pod b/resize/virt-resize.pod
index 313413a5..c0707d7e 100644
--- a/resize/virt-resize.pod
+++ b/resize/virt-resize.pod
@@ -663,6 +663,14 @@ after printing C<GRUB> on the console, try reinstalling grub.
 For more flexible guest reconfiguration, including if you need to
 specify other parameters to grub-install, use L<virt-rescue(1)>.
 
+=head2 WINDOWS UNMOUNTABLE_BOOT_VOLUME BSOD
+
+After sysprepping a Windows guest and then resizing it with
+virt-resize, you may see the guest fail to boot with an
+C<UNMOUNTABLE_BOOT_VOLUME> BSOD.  This error is caused by having
+C<ExtendOemPartition=1> in the sysprep.inf file.  Removing this line
+before sysprepping should fix the problem.
+
 =head1 ALTERNATIVE TOOLS
 
 There are several proprietary tools for resizing partitions.  We
-- 
cgit