Things have been 'quiet' here, working away, but I need a bit of help....
I have a 10G Fedora image that is now too small. I need to grow it.
I have shutdown the image in VMM, and quite VMM.
I backed up the image, /var/lib/libvirt/images/fedora21.qcow2 to a USB drive.
Then I ran:
qemu-img resize fedora21.qcow2 +10G
and
qemu-img info fedora21.qcow2 image: fedora21.qcow2 file format: qcow2 virtual size: 20 GiB (21474836480 bytes) disk size: 10 GiB cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: true refcount bits: 16 corrupt: false
That seems to be the easy part. But now the instructions I am finding seem to offer different approachs, and might not be for running on Fedora. What is the 'best' approach forward?
thanks
Am 21.07.2021 um 21:29 schrieb Robert Moskowitz rgm@htt-consult.com:
... qemu-img info fedora21.qcow2 image: fedora21.qcow2 file format: qcow2 virtual size: 20 GiB (21474836480 bytes) disk size: 10 GiB cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: true refcount bits: 16 corrupt: false
That seems to be the easy part.
Seems to be OK, You should be able to continue to use it.
But now the instructions I am finding seem to offer different approachs, and might not be for running on Fedora. What is the 'best' approach forward?
To what instructions do you refer?
On 7/21/21 3:38 PM, Peter Boy wrote:
Am 21.07.2021 um 21:29 schrieb Robert Moskowitz rgm@htt-consult.com:
... qemu-img info fedora21.qcow2 image: fedora21.qcow2 file format: qcow2 virtual size: 20 GiB (21474836480 bytes) disk size: 10 GiB cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: true refcount bits: 16 corrupt: false
That seems to be the easy part.
Seems to be OK, You should be able to continue to use it.
But now the instructions I am finding seem to offer different approachs, and might not be for running on Fedora. What is the 'best' approach forward?
To what instructions do you refer?
How do I actually increase the partitions within the image?
I have looked at instructions at:
https://dnaeon.github.io/resizing-a-kvm-disk-image-on-lvm-the-hard-way/ https://unix.stackexchange.com/questions/349586/resize-qcow2-root-parition https://unix.stackexchange.com/questions/615216/how-to-increase-the-root-par...
But am really cautious on what to do next to actually have the larger partitions.
I tried
parted -l fedora21.qcow2
As the next step, put it just showed my physical drives.
Am 21.07.2021 um 21:46 schrieb Robert Moskowitz rgm@htt-consult.com:
But now the instructions I am finding seem to offer different approachs, and might not be for running on Fedora. What is the 'best' approach forward?
To what instructions do you refer?
How do I actually increase the partitions within the image?
You have (re)start the virtual machine and increase and reorganise your storage from inside the virtual machine the same way as your would do it with a physical machine.
The details depend on the current structure of your (virtual) disk. How did you originally create your VMs disk image?
Usually you may have: Partition 1: biosboot or efi Partition 2: Linux file system /boot Partition 3: either (a) a filesystem containing all your data or (b) a LVM VG, containing a logical volume with a file system for root.
What is your storage structure?
You may find some Fedora specific into at:
https://docs.fedoraproject.org/en-US/fedora-server/virtualization-vmcloud/
Is it possible for you to keep the backup for now?
If so run the following commands: 1) Keep the backup # mv /var/lib/libvirt/images/fedora21.qcow2 /var/lib/libvirt/images/fedora21.qcow2.orig 2) Copy the resized qcow2 from thumb drive to /var/lib/libvirt/images/fedora21.qcow2 3) Boot up the VM and provide the following output: # fdisk -l # pvdisplay # lvdisplay # vgdisplay
Once this info is provided we can advise on how to expand the filesystem.
Regards, -Jamie
On Wed, Jul 21, 2021 at 4:10 PM Peter Boy pboy@uni-bremen.de wrote:
Am 21.07.2021 um 21:46 schrieb Robert Moskowitz rgm@htt-consult.com:
But now the instructions I am finding seem to offer different
approachs, and might not be for running on Fedora. What is the 'best' approach forward?
To what instructions do you refer?
How do I actually increase the partitions within the image?
You have (re)start the virtual machine and increase and reorganise your storage from inside the virtual machine the same way as your would do it with a physical machine.
The details depend on the current structure of your (virtual) disk. How did you originally create your VMs disk image?
Usually you may have: Partition 1: biosboot or efi Partition 2: Linux file system /boot Partition 3: either (a) a filesystem containing all your data or (b) a LVM VG, containing a logical volume with a file system for root.
What is your storage structure?
You may find some Fedora specific into at:
https://docs.fedoraproject.org/en-US/fedora-server/virtualization-vmcloud/
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
On 7/21/21 4:28 PM, Jamie Fargen wrote:
Is it possible for you to keep the backup for now?
If so run the following commands:
- Keep the backup
# mv /var/lib/libvirt/images/fedora21.qcow2 /var/lib/libvirt/images/fedora21.qcow2.orig 2) Copy the resized qcow2 from thumb drive to /var/lib/libvirt/images/fedora21.qcow2 3) Boot up the VM and provide the following output: # fdisk -l # pvdisplay
--- Physical volume --- PV Name /dev/vda2 VG Name fedora PV Size 19.51 GiB / not usable 2.00 MiB Allocatable yes PE Size 4.00 MiB Total PE 4994 Free PE 2570 Allocated PE 2424 PV UUID YmdEGp-gb7o-Gqm4-qfUG-Emi1-92hX-uoXKd8
# lvdisplay
--- Logical volume --- LV Path /dev/fedora/swap LV Name swap VG Name fedora LV UUID wcCMpc-LjV4-ahaQ-dLnZ-rIfx-5MBS-yGrGPT LV Write Access read/write LV Creation host, time localhost, 2014-12-31 10:29:38 -0500 LV Status available # open 2 LV Size 1.00 GiB Current LE 256 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:1
--- Logical volume --- LV Path /dev/fedora/root LV Name root VG Name fedora LV UUID k5Iqpt-dGBC-V4jJ-2UPn-sG2w-dwc5-npzUHl LV Write Access read/write LV Creation host, time localhost, 2014-12-31 10:29:41 -0500 LV Status available # open 1 LV Size 8.47 GiB Current LE 2168 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:0
# vgdisplay
--- Volume group --- VG Name fedora System ID Format lvm2 Metadata Areas 1 Metadata Sequence No 4 VG Access read/write VG Status resizable MAX LV 0 Cur LV 2 Open LV 2 Max PV 0 Cur PV 1 Act PV 1 VG Size 19.51 GiB PE Size 4.00 MiB Total PE 4994 Alloc PE / Size 2424 / 9.47 GiB Free PE / Size 2570 / 10.04 GiB VG UUID SEGNhI-DBMm-dnsm-fFRT-ZfPA-0403-EKmNJG
Once this info is provided we can advise on how to expand the filesystem.
gparted increased the partition size of vga2, but now I need to grow the root in it. It has been too many years since I use to do this stuff. :(
Regards, -Jamie
On Wed, Jul 21, 2021 at 4:10 PM Peter Boy <pboy@uni-bremen.de mailto:pboy@uni-bremen.de> wrote:
> Am 21.07.2021 um 21:46 schrieb Robert Moskowitz <rgm@htt-consult.com <mailto:rgm@htt-consult.com>>: > >>> But now the instructions I am finding seem to offer different approachs, and might not be for running on Fedora. What is the 'best' approach forward? >> To what instructions do you refer? > > How do I actually increase the partitions within the image? > You have (re)start the virtual machine and increase and reorganise your storage from inside the virtual machine the same way as your would do it with a physical machine. The details depend on the current structure of your (virtual) disk. How did you originally create your VMs disk image? Usually you may have: Partition 1: biosboot or efi Partition 2: Linux file system /boot Partition 3: either (a) a filesystem containing all your data or (b) a LVM VG, containing a logical volume with a file system for root. What is your storage structure? You may find some Fedora specific into at: https://docs.fedoraproject.org/en-US/fedora-server/virtualization-vmcloud/ <https://docs.fedoraproject.org/en-US/fedora-server/virtualization-vmcloud/> _______________________________________________ users mailing list -- users@lists.fedoraproject.org <mailto:users@lists.fedoraproject.org> To unsubscribe send an email to users-leave@lists.fedoraproject.org <mailto:users-leave@lists.fedoraproject.org> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ <https://docs.fedoraproject.org/en-US/project/code-of-conduct/> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines <https://fedoraproject.org/wiki/Mailing_list_guidelines> List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org <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 <https://pagure.io/fedora-infrastructure>
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
Looks the next step is:
lvextend -r -l +100%FREE /dev/vga2/root
?
this is from:
https://computingforgeeks.com/extending-root-filesystem-using-lvm-linux/
On 7/21/21 4:39 PM, Robert Moskowitz wrote:
On 7/21/21 4:28 PM, Jamie Fargen wrote:
Is it possible for you to keep the backup for now?
If so run the following commands:
- Keep the backup
# mv /var/lib/libvirt/images/fedora21.qcow2 /var/lib/libvirt/images/fedora21.qcow2.orig 2) Copy the resized qcow2 from thumb drive to /var/lib/libvirt/images/fedora21.qcow2 3) Boot up the VM and provide the following output: # fdisk -l # pvdisplay
--- Physical volume --- PV Name /dev/vda2 VG Name fedora PV Size 19.51 GiB / not usable 2.00 MiB Allocatable yes PE Size 4.00 MiB Total PE 4994 Free PE 2570 Allocated PE 2424 PV UUID YmdEGp-gb7o-Gqm4-qfUG-Emi1-92hX-uoXKd8
# lvdisplay
--- Logical volume --- LV Path /dev/fedora/swap LV Name swap VG Name fedora LV UUID wcCMpc-LjV4-ahaQ-dLnZ-rIfx-5MBS-yGrGPT LV Write Access read/write LV Creation host, time localhost, 2014-12-31 10:29:38 -0500 LV Status available # open 2 LV Size 1.00 GiB Current LE 256 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:1
--- Logical volume --- LV Path /dev/fedora/root LV Name root VG Name fedora LV UUID k5Iqpt-dGBC-V4jJ-2UPn-sG2w-dwc5-npzUHl LV Write Access read/write LV Creation host, time localhost, 2014-12-31 10:29:41 -0500 LV Status available # open 1 LV Size 8.47 GiB Current LE 2168 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:0
# vgdisplay
--- Volume group --- VG Name fedora System ID Format lvm2 Metadata Areas 1 Metadata Sequence No 4 VG Access read/write VG Status resizable MAX LV 0 Cur LV 2 Open LV 2 Max PV 0 Cur PV 1 Act PV 1 VG Size 19.51 GiB PE Size 4.00 MiB Total PE 4994 Alloc PE / Size 2424 / 9.47 GiB Free PE / Size 2570 / 10.04 GiB VG UUID SEGNhI-DBMm-dnsm-fFRT-ZfPA-0403-EKmNJG
Once this info is provided we can advise on how to expand the filesystem.
gparted increased the partition size of vga2, but now I need to grow the root in it. It has been too many years since I use to do this stuff. :(
Regards, -Jamie
On Wed, Jul 21, 2021 at 4:10 PM Peter Boy <pboy@uni-bremen.de mailto:pboy@uni-bremen.de> wrote:
> Am 21.07.2021 um 21:46 schrieb Robert Moskowitz <rgm@htt-consult.com <mailto:rgm@htt-consult.com>>: > >>> But now the instructions I am finding seem to offer different approachs, and might not be for running on Fedora. What is the 'best' approach forward? >> To what instructions do you refer? > > How do I actually increase the partitions within the image? > You have (re)start the virtual machine and increase and reorganise your storage from inside the virtual machine the same way as your would do it with a physical machine. The details depend on the current structure of your (virtual) disk. How did you originally create your VMs disk image? Usually you may have: Partition 1: biosboot or efi Partition 2: Linux file system /boot Partition 3: either (a) a filesystem containing all your data or (b) a LVM VG, containing a logical volume with a file system for root. What is your storage structure? You may find some Fedora specific into at: https://docs.fedoraproject.org/en-US/fedora-server/virtualization-vmcloud/ <https://docs.fedoraproject.org/en-US/fedora-server/virtualization-vmcloud/> _______________________________________________ users mailing list -- users@lists.fedoraproject.org <mailto:users@lists.fedoraproject.org> To unsubscribe send an email to users-leave@lists.fedoraproject.org <mailto:users-leave@lists.fedoraproject.org> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ <https://docs.fedoraproject.org/en-US/project/code-of-conduct/> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines <https://fedoraproject.org/wiki/Mailing_list_guidelines> List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org <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 <https://pagure.io/fedora-infrastructure>
users mailing list --users@lists.fedoraproject.org To unsubscribe send an email tousers-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
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
On 7/21/21 4:50 PM, Robert Moskowitz wrote:
Looks the next step is:
lvextend -r -l +100%FREE /dev/vga2/root
that is /dev/vda2/root
and did not work:
ah...
]# lvextend -r -l +100%FREE /dev/fedora/root Size of logical volume fedora/root changed from 8.47 GiB (2168 extents) to 18.51 GiB (4738 extents). Logical volume root successfully resized resize2fs 1.42.12 (29-Aug-2014) Filesystem at /dev/mapper/fedora-root is mounted on /; on-line resizing required old_desc_blocks = 1, new_desc_blocks = 2 The filesystem on /dev/mapper/fedora-root is now 4851712 (4k) blocks long.
and that worked. Will reboot before doing anything else.
?
this is from:
https://computingforgeeks.com/extending-root-filesystem-using-lvm-linux/
On 7/21/21 4:39 PM, Robert Moskowitz wrote:
On 7/21/21 4:28 PM, Jamie Fargen wrote:
Is it possible for you to keep the backup for now?
If so run the following commands:
- Keep the backup
# mv /var/lib/libvirt/images/fedora21.qcow2 /var/lib/libvirt/images/fedora21.qcow2.orig 2) Copy the resized qcow2 from thumb drive to /var/lib/libvirt/images/fedora21.qcow2 3) Boot up the VM and provide the following output: # fdisk -l # pvdisplay
--- Physical volume --- PV Name /dev/vda2 VG Name fedora PV Size 19.51 GiB / not usable 2.00 MiB Allocatable yes PE Size 4.00 MiB Total PE 4994 Free PE 2570 Allocated PE 2424 PV UUID YmdEGp-gb7o-Gqm4-qfUG-Emi1-92hX-uoXKd8
# lvdisplay
--- Logical volume --- LV Path /dev/fedora/swap LV Name swap VG Name fedora LV UUID wcCMpc-LjV4-ahaQ-dLnZ-rIfx-5MBS-yGrGPT LV Write Access read/write LV Creation host, time localhost, 2014-12-31 10:29:38 -0500 LV Status available # open 2 LV Size 1.00 GiB Current LE 256 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:1
--- Logical volume --- LV Path /dev/fedora/root LV Name root VG Name fedora LV UUID k5Iqpt-dGBC-V4jJ-2UPn-sG2w-dwc5-npzUHl LV Write Access read/write LV Creation host, time localhost, 2014-12-31 10:29:41 -0500 LV Status available # open 1 LV Size 8.47 GiB Current LE 2168 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:0
# vgdisplay
--- Volume group --- VG Name fedora System ID Format lvm2 Metadata Areas 1 Metadata Sequence No 4 VG Access read/write VG Status resizable MAX LV 0 Cur LV 2 Open LV 2 Max PV 0 Cur PV 1 Act PV 1 VG Size 19.51 GiB PE Size 4.00 MiB Total PE 4994 Alloc PE / Size 2424 / 9.47 GiB Free PE / Size 2570 / 10.04 GiB VG UUID SEGNhI-DBMm-dnsm-fFRT-ZfPA-0403-EKmNJG
Once this info is provided we can advise on how to expand the filesystem.
gparted increased the partition size of vga2, but now I need to grow the root in it. It has been too many years since I use to do this stuff. :(
Regards, -Jamie
On Wed, Jul 21, 2021 at 4:10 PM Peter Boy <pboy@uni-bremen.de mailto:pboy@uni-bremen.de> wrote:
> Am 21.07.2021 um 21:46 schrieb Robert Moskowitz <rgm@htt-consult.com <mailto:rgm@htt-consult.com>>: > >>> But now the instructions I am finding seem to offer different approachs, and might not be for running on Fedora. What is the 'best' approach forward? >> To what instructions do you refer? > > How do I actually increase the partitions within the image? > You have (re)start the virtual machine and increase and reorganise your storage from inside the virtual machine the same way as your would do it with a physical machine. The details depend on the current structure of your (virtual) disk. How did you originally create your VMs disk image? Usually you may have: Partition 1: biosboot or efi Partition 2: Linux file system /boot Partition 3: either (a) a filesystem containing all your data or (b) a LVM VG, containing a logical volume with a file system for root. What is your storage structure? You may find some Fedora specific into at: https://docs.fedoraproject.org/en-US/fedora-server/virtualization-vmcloud/ <https://docs.fedoraproject.org/en-US/fedora-server/virtualization-vmcloud/> _______________________________________________ users mailing list -- users@lists.fedoraproject.org <mailto:users@lists.fedoraproject.org> To unsubscribe send an email to users-leave@lists.fedoraproject.org <mailto:users-leave@lists.fedoraproject.org> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ <https://docs.fedoraproject.org/en-US/project/code-of-conduct/> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines <https://fedoraproject.org/wiki/Mailing_list_guidelines> List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org <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 <https://pagure.io/fedora-infrastructure>
users mailing list --users@lists.fedoraproject.org To unsubscribe send an email tousers-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
users mailing list --users@lists.fedoraproject.org To unsubscribe send an email tousers-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
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
A couple of comments... if this VM is managed by libvirt (recent enough version is several years old IIRC), you don't need to shut the VM down or ever touch the image file directly.
To resize a running VM image, you can do: virsh blockresize vmname /var/lib/libvirt/images/vmname.qcow2 20G
If the VM is using virtio or virtio-scsi drivers, it should see the change immediately.
If you are running LVM, on recent enough Fedora (I don't know, at least the last several years), you can then resize without a reboot too. Find the partition (usually 2 on BIOS or 3 for UEFI boot systems with a fairly default setup) and device (usually /dev/vda for virtio or /dev/sda for virtio-scsi), and do (adjusting dev/part): parted /dev/vda resizepart 2 100% quit pvresize /dev/vda2
Then you need to know your filesystem LV name (like "fedora/root") and filesystem type (usually ext4, could be xfs if a Server install) and do: lvresize -l +100%FREE fedora/root resize2fs /dev/fedora/root -or- xfs_growfs /
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. There's also the possibility of LVM set up with thin pools... can't remember if that works the same or needs additional steps.
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
On 7/21/21 4:09 PM, Peter Boy wrote:
Am 21.07.2021 um 21:46 schrieb Robert Moskowitz rgm@htt-consult.com:
But now the instructions I am finding seem to offer different approachs, and might not be for running on Fedora. What is the 'best' approach forward?
To what instructions do you refer?
How do I actually increase the partitions within the image?
You have (re)start the virtual machine and increase and reorganise your storage from inside the virtual machine the same way as your would do it with a physical machine.
I guess I was overly caution about starting the image.
The details depend on the current structure of your (virtual) disk. How did you originally create your VMs disk image?
I think I used an iso install image and build with defaults.
I went into pgarted and resized the root partition. But it is still showing the same old.
I am now going to reboot the image and see....
Usually you may have: Partition 1: biosboot or efi Partition 2: Linux file system /boot Partition 3: either (a) a filesystem containing all your data or (b) a LVM VG, containing a logical volume with a file system for root.
What is your storage structure?
You may find some Fedora specific into at:
https://docs.fedoraproject.org/en-US/fedora-server/virtualization-vmcloud/
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
On Wed, 21 Jul 2021 15:46:30 -0400 Robert Moskowitz wrote:
How do I actually increase the partitions within the image?
I have sometimes mounted a virtual image inside a different KVM so I could run gparted inside the new KVM in order to modify the system disk partitions from a different KVM (naturally the different KVM needs to be shut down during this process).
-
Chris Adams -
Chris Murphy -
Jamie Fargen -
Peter Boy -
Robert Moskowitz -
Tom Horsley