mirrors/libguestfs
1
0
Fork 0
mirror of https://github.com/libguestfs/libguestfs.git synced 2026-03-21 22:53:37 +00:00
Code Issues Packages Projects Releases Wiki Activity

virt-resize: Add notes about Windows and disk consistency (RHBZ#975753).

Browse Source 
Also group the Windows-related notes together.
This commit is contained in:
Richard W.M. Jones
2013-06-20 09:13:41 +01:00
parent b730bc0c46
commit a7aa47f4de
1 changed files with 27 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

40
resize/virt-resize.pod
View File

@@ -635,19 +635,6 @@ meaningless for disks manufactured since the early 1990s, and doubly
so for virtual hard drives. Alignment of partitions to cylinders is
not required by any modern operating system.
=head2 RESIZING WINDOWS VIRTUAL MACHINES
In Windows Vista and later versions, Microsoft switched to using a
separate boot partition. In these VMs, typically C</dev/sda1> is the
boot partition and C</dev/sda2> is the main (C:) drive. Resizing the
first (boot) partition causes the bootloader to fail with
C<0xC0000225> error. Resizing the second partition (ie. C: drive)
should work.
Windows may initiate a lengthy "chkdsk" on first boot after a resize,
if NTFS partitions have been expanded. This is just a safety check
and (unless it find errors) is nothing to worry about.
=head2 GUEST BOOT STUCK AT "GRUB"
If a Linux guest does not boot after resizing, and the boot is stuck
@@ -663,6 +650,27 @@ 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 RESIZING WINDOWS BOOT PARTITIONS
In Windows Vista and later versions, Microsoft switched to using a
separate boot partition. In these VMs, typically C</dev/sda1> is the
boot partition and C</dev/sda2> is the main (C:) drive. Resizing the
first (boot) partition causes the bootloader to fail with
C<0xC0000225> error. Resizing the second partition (ie. C: drive)
should work.
=head2 WINDOWS CHKDSK
Windows disks which use NTFS must be consistent before virt-resize can
be used. If the ntfsresize operation fails, try booting the original
VM and running C<chkdsk /f> on all NTFS partitions, then shut down the
VM cleanly. For further information see:
L<https://bugzilla.redhat.com/show_bug.cgi?id=975753>
I<After resize> Windows may initiate a lengthy "chkdsk" on first boot
if NTFS partitions have been expanded. This is just a safety check
and (unless it find errors) is nothing to worry about.
=head2 WINDOWS UNMOUNTABLE_BOOT_VOLUME BSOD
After sysprepping a Windows guest and then resizing it with
@@ -671,6 +679,12 @@ 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.
=head2 WINDOWS 8
Windows 8 "fast startup" can prevent virt-resize from resizing NTFS
partitions. See
L<guestfs(3)/WINDOWS HIBERNATION AND WINDOWS 8 FAST STARTUP>.
=head2 SPARSE COPYING
You must create a fresh, zeroed target disk image for virt-resize to