[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fedora-list
Subject:    Re: resizing qemu image
From:       Chris Murphy <lists () colorremedies ! com>
Date:       2021-07-26 19:44:37
Message-ID: CAJCQCtR7HEMaVm9WdkAWSzAUUQTOzKV4sf9B4r8chp5rff0qGg () mail ! gmail ! com
[Download RAW message or body]

On Wed, Jul 21, 2021 at 3:23 PM Chris Adams <linux@cmadams.net> wrote:

> And you have more space!  I do this all the time with libvirt-managed
> Linux VMs.  I haven't yet gone through th necessary steps for the more
> recent btrfs setup.

Guest:
# lsblk -o NAME,SIZE
NAME    SIZE
vda     100G
├─vda1  600M
├─vda2    1G
└─vda3 98.4G


Host:
$ sudo virsh blockresize uefivm
/var/lib/libvirt/images/f34w-uefi-defaultbtrfs.raw 200G
Block device '/var/lib/libvirt/images/f34w-uefi-defaultbtrfs.raw' is resized

Guest:
# lsblk -o NAME,SIZE
vda     200G
├─vda1  600M
├─vda2    1G
└─vda3 98.4G

(gdisk requires three changes: move the secondary GPT to the end of
the disk, then delete vda3 partition, and recreate it max size, which
is the default behavior)

# partprobe
# lsblk -o NAME,SIZE
vda      200G
├─vda1   600M
├─vda2     1G
└─vda3 198.4G
# btrfs fi resize max /
Resize device id 1 (/dev/vda3) from 98.41GiB to max


Single device btrfs resize is straightforward. But with multiple
device Btrfs, you need to specify the devid you want resized,
otherwise it defaults to devid 1.


--
Chris Murphy
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

[prev in list] [next in list] [prev in thread] [next in thread]