diff options
| author | Richard W.M. Jones <rjones@redhat.com> | 2012-02-27 19:39:11 +0000 |
|---|---|---|
| committer | Richard W.M. Jones <rjones@redhat.com> | 2012-02-27 19:39:43 +0000 |
| commit | a93d4a9dc1aea6940886c85d4b09f21cbfc80969 (patch) | |
| tree | f5f029ce5eba6b1e1f886fa98d360ef9652d3d07 | |
| parent | d1711dae9dbd7f516469f88807604894c1304228 (diff) | |
| download | libguestfs-a93d4a9dc1aea6940886c85d4b09f21cbfc80969.tar.gz libguestfs-a93d4a9dc1aea6940886c85d4b09f21cbfc80969.tar.xz libguestfs-a93d4a9dc1aea6940886c85d4b09f21cbfc80969.zip | |
resize: Document steps to avoid UNMOUNTABLE_BOOT_VOLUME BSOD (RHBZ#797986).
(Thanks Grant Williamson for finding and fixing this problem)
| -rw-r--r-- | resize/virt-resize.pod | 8 |
1 files changed, 8 insertions, 0 deletions
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 |