5 virt-resize - Resize a virtual machine disk
9 virt-resize [--resize /dev/sdaN=[+/-]<size>[%]]
10 [--expand /dev/sdaN] [--shrink /dev/sdaN]
11 [--ignore /dev/sdaN] [--delete /dev/sdaN] [...] indisk outdisk
15 Virt-resize is a tool which can resize a virtual machine disk, making
16 it larger or smaller overall, and resizing or deleting any partitions
19 Virt-resize B<cannot> resize disk images in-place. Virt-resize
20 B<should not> be used on live virtual machines - for consistent
21 results, shut the virtual machine down before resizing it.
23 If you are not familiar with the associated tools:
24 L<virt-filesystems(1)> and L<virt-df(1)>, we recommend you go and read
25 those manual pages first.
33 Copy C<olddisk> to C<newdisk>, extending one of the guest's partitions
34 to fill the extra 5GB of space.
36 virt-filesystems --long -h --all -a olddisk
38 truncate -r olddisk newdisk
39 truncate -s +5G newdisk
41 # Note "/dev/sda2" is a partition inside the "olddisk" file.
42 virt-resize --expand /dev/sda2 olddisk newdisk
46 As above, but make the /boot partition 200MB bigger, while giving the
47 remaining space to /dev/sda2:
49 virt-resize --resize /dev/sda1=+200M --expand /dev/sda2 \
54 As in the first example, but expand a logical volume as the final
55 step. This is what you would typically use for Linux guests that use
58 virt-resize --expand /dev/sda2 --LV-expand /dev/vg_guest/lv_root \
63 As in the first example, but the output format will be qcow2 instead
66 qemu-img create -f qcow2 newdisk.qcow2 15G
67 virt-resize --expand /dev/sda2 olddisk newdisk.qcow2
73 =head2 EXPANDING A VIRTUAL MACHINE DISK
77 =item 1. Shut down the virtual machine
79 =item 2. Locate input disk image
81 Locate the input disk image (ie. the file or device on the host
82 containing the guest's disk). If the guest is managed by libvirt, you
83 can use C<virsh dumpxml> like this to find the disk image name:
85 # virsh dumpxml guestname | xpath /domain/devices/disk/source
88 <source dev="/dev/vg/lv_guest" />
90 =item 3. Look at current sizing
92 Use L<virt-filesystems(1)> to display the current partitions and
95 # virt-filesystems --long --parts --blkdevs -h -a /dev/vg/lv_guest
97 /dev/sda1 partition 101M /dev/sda
98 /dev/sda2 partition 7.9G /dev/sda
99 /dev/sda device 8.0G -
101 (This example is a virtual machine with an 8 GB disk which we would
102 like to expand up to 10 GB).
104 =item 4. Create output disk
106 Virt-resize cannot do in-place disk modifications. You have to have
107 space to store the resized output disk.
109 To store the resized disk image in a file, create a file of a suitable
113 # truncate -s 10G outdisk
115 Or use L<lvcreate(1)> to create a logical volume:
117 # lvcreate -L 10G -n lv_name vg_name
119 Or use L<virsh(1)> vol-create-as to create a libvirt storage volume:
122 # virsh vol-create-as poolname newvol 10G
126 virt-resize takes two mandatory parameters, the input disk (eg. device
127 or file) and the output disk. The output disk is the one created in
130 # virt-resize indisk outdisk
132 This command just copies disk image C<indisk> to disk image C<outdisk>
133 I<without> resizing or changing any existing partitions. If
134 C<outdisk> is larger, then an extra, empty partition is created at the
135 end of the disk covering the extra space. If C<outdisk> is smaller,
136 then it will give an error.
138 More realistically you'd want to expand existing partitions in the
139 disk image by passing extra options (for the full list see the
140 L</OPTIONS> section below).
142 L</--expand> is the most useful option. It expands the named
143 partition within the disk to fill any extra space:
145 # virt-resize --expand /dev/sda2 indisk outdisk
147 (In this case, an extra partition is I<not> created at the end of the
148 disk, because there will be no unused space).
150 L</--resize> is the other commonly used option. The following would
151 increase the size of /dev/sda1 by 200M, and expand /dev/sda2
152 to fill the rest of the available space:
154 # virt-resize --resize /dev/sda1=+200M --expand /dev/sda2 \
157 If the expanded partition in the image contains a filesystem or LVM
158 PV, then if virt-resize knows how, it will resize the contents, the
159 equivalent of calling a command such as L<pvresize(8)>,
160 L<resize2fs(8)>, L<ntfsresize(8)> or L<btrfs(8)>. However virt-resize
161 does not know how to resize some filesystems, so you would have to
162 online resize them after booting the guest.
164 Other options are covered below.
168 Thoroughly test the new disk image I<before> discarding the old one.
170 If you are using libvirt, edit the XML to point at the new disk:
172 # virsh edit guestname
174 Change E<lt>source ...E<gt>, see
175 L<http://libvirt.org/formatdomain.html#elementsDisks>
177 Then start up the domain with the new, resized disk:
179 # virsh start guestname
181 and check that it still works. See also the L</NOTES> section below
182 for additional information.
184 =item 7. Resize LVs etc inside the guest
186 (This can also be done offline using L<guestfish(1)>)
188 Once the guest has booted you should see the new space available, at
189 least for filesystems that virt-resize knows how to resize, and for
190 PVs. The user may need to resize LVs inside PVs, and also resize
191 filesystem types that virt-resize does not know how to expand.
195 =head2 SHRINKING A VIRTUAL MACHINE DISK
197 Shrinking is somewhat more complex than expanding, and only an
198 overview is given here.
200 Firstly virt-resize will not attempt to shrink any partition content
201 (PVs, filesystems). The user has to shrink content before passing the
202 disk image to virt-resize, and virt-resize will check that the content
203 has been shrunk properly.
205 (Shrinking can also be done offline using L<guestfish(1)>)
207 After shrinking PVs and filesystems, shut down the guest, and proceed
208 with steps 3 and 4 above to allocate a new disk image.
210 Then run virt-resize with any of the I<--shrink> and/or I<--resize>
213 =head2 IGNORING OR DELETING PARTITIONS
215 virt-resize also gives a convenient way to ignore or delete partitions
216 when copying from the input disk to the output disk. Ignoring a
217 partition speeds up the copy where you don't care about the existing
218 contents of a partition. Deleting a partition removes it completely,
219 but note that it also renumbers any partitions after the one which is
220 deleted, which can leave some guests unbootable.
222 =head2 QCOW2 AND NON-SPARSE RAW FORMATS
224 If the input disk is in qcow2 format, then you may prefer that the
225 output is in qcow2 format as well. Alternately, virt-resize can
226 convert the format on the fly. The output format is simply determined
227 by the format of the empty output container that you provide. Thus to
228 create qcow2 output, use:
230 qemu-img create [-c] -f qcow2 outdisk [size]
232 instead of the truncate command (use I<-c> for a compressed disk).
234 Similarly, to get non-sparse raw output use:
236 fallocate -l size outdisk
238 (on older systems that don't have the L<fallocate(1)> command use
239 C<dd if=/dev/zero of=outdisk bs=1M count=..>)
249 =item B<--alignment N>
251 Set the alignment of partitions to C<N> sectors. The default in
252 virt-resize E<lt> 1.13.19 was 64 sectors, and after that is 128
255 Assuming 512 byte sector size inside the guest, here are some
256 suitable values for this:
260 =item I<--alignment 1> (512 bytes)
262 The partitions would be packed together as closely as possible, but
263 would be completely unaligned. In some cases this can cause very poor
264 performance. See L<virt-alignment-scan(1)> for further details.
266 =item I<--alignment 8> (4K)
268 This would be the minimum acceptable alignment for reasonable
269 performance on modern hosts.
271 =item I<--alignment 128> (64K)
273 This alignment provides good performance when the host is using high
276 =item I<--alignment 2048> (1M)
278 This is the standard alignment used by all newly installed guests
287 Enable debugging messages.
289 =item B<--delete part>
291 Delete the named partition. It would be more accurate to describe
292 this as "don't copy it over", since virt-resize doesn't do in-place
293 changes and the original disk image is left intact.
295 Note that when you delete a partition, then anything contained in the
296 partition is also deleted. Furthermore, this causes any partitions
297 that come after to be I<renumbered>, which can easily make your guest
300 You can give this option multiple times.
302 =item B<--expand part>
304 Expand the named partition so it uses up all extra space (space left
305 over after any other resize changes that you request have been done).
307 If virt-resize knows how, it will expand the direct content of the
308 partition. For example, if the partition is an LVM PV, it will expand
309 the PV to fit (like calling L<pvresize(8)>). Virt-resize leaves any
310 other content it doesn't know about alone.
312 Currently virt-resize can resize:
318 ext2, ext3 and ext4 filesystems.
322 NTFS filesystems, if libguestfs was compiled with support for NTFS.
324 The filesystem must have been shut down consistently last time it was
325 used. Additionally, L<ntfsresize(8)> marks the resized filesystem as
326 requiring a consistency check, so at the first boot after resizing
327 Windows will check the disk.
331 LVM PVs (physical volumes). virt-resize does not usually resize
332 anything inside the PV, but see the I<--LV-expand> option. The user
333 could also resize LVs as desired after boot.
337 Btrfs filesystems, if libguestfs was compiled with support for btrfs.
341 Note that you cannot use I<--expand> and I<--shrink> together.
343 =item B<--format> raw
345 Specify the format of the input disk image. If this flag is not
346 given then it is auto-detected from the image itself.
348 If working with untrusted raw-format guest disk images, you should
349 ensure the format is always specified.
351 Note that this option I<does not> affect the output format.
352 See L</QCOW2 AND NON-SPARSE RAW FORMATS>.
354 =item B<--ignore part>
356 Ignore the named partition. Effectively this means the partition is
357 allocated on the destination disk, but the content is not copied
358 across from the source disk. The content of the partition will be
359 blank (all zero bytes).
361 You can give this option multiple times.
363 =item B<--LV-expand logvol>
365 This takes the logical volume and, as a final step, expands it to fill
366 all the space available in its volume group. A typical usage,
367 assuming a Linux guest with a single PV C</dev/sda2> and a root device
368 called C</dev/vg_guest/lv_root> would be:
370 virt-resize indisk outdisk \
371 --expand /dev/sda2 --LV-expand /dev/vg_guest/lv_root
373 This would first expand the partition (and PV), and then expand the
374 root device to fill the extra space in the PV.
376 The contents of the LV are also resized if virt-resize knows how to do
377 that. You can stop virt-resize from trying to expand the content by
378 using the option I<--no-expand-content>.
380 Use L<virt-filesystems(1)> to list the filesystems in the guest.
382 You can give this option multiple times, I<but> it doesn't
383 make sense to do this unless the logical volumes you specify
384 are all in different volume groups.
386 =item B<--machine-readable>
388 This option is used to make the output more machine friendly
389 when being parsed by other programs. See
390 L</MACHINE READABLE OUTPUT> below.
396 Print a summary of what would be done, but don't do anything.
398 =item B<--no-copy-boot-loader>
400 By default, virt-resize copies over some sectors at the start of the
401 disk (up to the beginning of the first partition). Commonly these
402 sectors contain the Master Boot Record (MBR) and the boot loader, and
403 are required in order for the guest to boot correctly.
405 If you specify this flag, then this initial copy is not done. You may
406 need to reinstall the boot loader in this case.
408 =item B<--no-extra-partition>
410 By default, virt-resize creates an extra partition if there is any
411 extra, unused space after all resizing has happened. Use this option
412 to prevent the extra partition from being created. If you do this
413 then the extra space will be inaccessible until you run fdisk, parted,
414 or some other partitioning tool in the guest.
416 Note that if the surplus space is smaller than 10 MB, no extra
417 partition will be created.
419 =item B<--no-expand-content>
421 By default, virt-resize will try to expand the direct contents
422 of partitions, if it knows how (see I<--expand> option above).
424 If you give the I<--no-expand-content> option then virt-resize
425 will not attempt this.
427 =item B<--ntfsresize-force>
429 Pass the I<--force> option to L<ntfsresize(8)>, allowing resizing
430 even if the NTFS disk is marked as needing a consistency check.
431 You have to use this option if you want to resize a Windows
432 guest multiple times without booting into Windows between each
435 =item B<--output-format> raw
437 Specify the format of the output disk image. If this flag is not
438 given then it is auto-detected from the image itself.
440 If working with untrusted raw-format guest disk images, you should
441 ensure the format is always specified.
443 Note that this option I<does not create> the output format. This
444 option just tells libguestfs what it is so it doesn't try to guess it.
445 You still need to create the output disk with the right format. See
446 L</QCOW2 AND NON-SPARSE RAW FORMATS>.
452 Don't print the summary.
454 =item B<--resize part=size>
456 Resize the named partition (expanding or shrinking it) so that it has
459 C<size> can be expressed as an absolute number followed by
460 b/K/M/G to mean bytes, Kilobytes, Megabytes, or Gigabytes;
461 or as a percentage of the current size;
462 or as a relative number or percentage.
465 --resize /dev/sda2=10G
467 --resize /dev/sda4=90%
469 --resize /dev/sda2=+1G
471 --resize /dev/sda2=-200M
473 --resize /dev/sda1=+128K
475 --resize /dev/sda1=+10%
477 --resize /dev/sda1=-10%
479 You can increase the size of any partition. Virt-resize will expand
480 the direct content of the partition if it knows how (see I<--expand>
483 You can only I<decrease> the size of partitions that contain
484 filesystems or PVs which have already been shrunk. Virt-resize will
485 check this has been done before proceeding, or else will print an
486 error (see also I<--resize-force>).
488 You can give this option multiple times.
490 =item B<--resize-force part=size>
492 This is the same as I<--resize> except that it will let you decrease
493 the size of any partition. Generally this means you will lose any
494 data which was at the end of the partition you shrink, but you may not
495 care about that (eg. if shrinking an unused partition, or if you can
496 easily recreate it such as a swap partition).
498 See also the I<--ignore> option.
500 =item B<--shrink part>
502 Shrink the named partition until the overall disk image fits in the
503 destination. The named partition B<must> contain a filesystem or PV
504 which has already been shrunk using another tool (eg. L<guestfish(1)>
505 or other online tools). Virt-resize will check this and give an error
506 if it has not been done.
508 The amount by which the overall disk must be shrunk (after carrying
509 out all other operations requested by the user) is called the
510 "deficit". For example, a straight copy (assume no other operations)
511 from a 5GB disk image to a 4GB disk image results in a 1GB deficit.
512 In this case, virt-resize would give an error unless the user
513 specified a partition to shrink and that partition had more than a
514 gigabyte of free space.
516 Note that you cannot use I<--expand> and I<--shrink> together.
522 Display version number and exit.
526 =head1 MACHINE READABLE OUTPUT
528 The I<--machine-readable> option can be used to make the output more
529 machine friendly, which is useful when calling virt-resize from other
532 There are two ways to use this option.
534 Firstly use the option on its own to query the capabilities of the
535 virt-resize binary. Typical output looks like this:
537 $ virt-resize --machine-readable
544 A list of features is printed, one per line, and the program exits
547 Secondly use the option in conjunction with other options to make the
548 regular program output more machine friendly.
550 At the moment this means:
556 Progress bar messages can be parsed from stdout by looking for this
563 The calling program should treat messages sent to stdout (except for
564 progress bar messages) as status messages. They can be logged and/or
565 displayed to the user.
569 The calling program should treat messages sent to stderr as error
570 messages. In addition, virt-resize exits with a non-zero status code
571 if there was a fatal error.
575 Versions of the program prior to 1.13.9 did not support the
576 I<--machine-readable> option and will return an error.
580 =head2 "Partition 1 does not end on cylinder boundary."
582 Virt-resize aligns partitions to multiples of 128 sectors (see the
583 I<--alignment> parameter). Usually this means the partitions will not
584 be aligned to the ancient CHS geometry. However CHS geometry is
585 meaningless for disks manufactured since the early 1990s, and doubly
586 so for virtual hard drives. Alignment of partitions to cylinders is
587 not required by any modern operating system.
589 =head2 RESIZING WINDOWS VIRTUAL MACHINES
591 In Windows Vista and later versions, Microsoft switched to using a
592 separate boot partition. In these VMs, typically C</dev/sda1> is the
593 boot partition and C</dev/sda2> is the main (C:) drive. We have not
594 had any luck resizing the boot partition. Doing so seems to break the
595 guest completely. However expanding the second partition (ie. C:
598 Windows may initiate a lengthy "chkdsk" on first boot after a resize,
599 if NTFS partitions have been expanded. This is just a safety check
600 and (unless it find errors) is nothing to worry about.
602 =head2 GUEST BOOT STUCK AT "GRUB"
604 If a Linux guest does not boot after resizing, and the boot is stuck
605 after printing C<GRUB> on the console, try reinstalling grub. This
606 sometimes happens on older (RHEL 5-era) guests, for reasons we don't
607 fully understand, although we think is to do with partition alignment.
609 guestfish -i -a newdisk
610 ><fs> cat /boot/grub/device.map
611 # check the contents of this file are sensible or
612 # edit the file if necessary
613 ><fs> grub-install / /dev/vda
616 For more flexible guest reconfiguration, including if you need to
617 specify other parameters to grub-install, use L<virt-rescue(1)>.
619 =head1 ALTERNATIVE TOOLS
621 There are several proprietary tools for resizing partitions. We
622 won't mention any here.
624 L<parted(8)> and its graphical shell gparted can do some types of
625 resizing operations on disk images. They can resize and move
626 partitions, but I don't think they can do anything with the contents,
627 and they certainly don't understand LVM.
629 L<guestfish(1)> can do everything that virt-resize can do and a lot
630 more, but at a much lower level. You will probably end up
631 hand-calculating sector offsets, which is something that virt-resize
632 was designed to avoid. If you want to see the guestfish-equivalent
633 commands that virt-resize runs, use the I<--debug> flag.
637 Libvirt guest names can contain arbitrary characters, some of which
638 have meaning to the shell such as C<#> and space. You may need to
639 quote or escape these characters on the command line. See the shell
640 manual page L<sh(1)> for details.
644 This program returns 0 if successful, or non-zero if there was an
649 L<virt-filesystems(1)>,
667 L<virt-alignment-scan(1)>,
668 L<http://libguestfs.org/>.
672 Richard W.M. Jones L<http://people.redhat.com/~rjones/>
676 Copyright (C) 2010-2011 Red Hat Inc.
678 This program is free software; you can redistribute it and/or modify
679 it under the terms of the GNU General Public License as published by
680 the Free Software Foundation; either version 2 of the License, or
681 (at your option) any later version.
683 This program is distributed in the hope that it will be useful,
684 but WITHOUT ANY WARRANTY; without even the implied warranty of
685 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
686 GNU General Public License for more details.
688 You should have received a copy of the GNU General Public License
689 along with this program; if not, write to the Free Software
690 Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.