On Wed, Jul 21, 2021 at 3:23 PM Chris Adams 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
NAMESIZE
vda 100G
├─vda1 600M
├─vda21
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 th
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 (
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
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:
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/libv
On 7/21/21 4:09 PM, Peter Boy wrote:
Am 21.07.2021 um 21:46 schrieb Robert Moskowitz :
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 actual
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 (na
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
> Am 21.07.2021 um 21:46 schrieb Robert Moskowitz :
>
>>> 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 par
On 7/21/21 3:38 PM, Peter Boy wrote:
Am 21.07.2021 um 21:29 schrieb Robert Moskowitz :
...
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
l
> Am 21.07.2021 um 21:29 schrieb Robert Moskowitz :
>
> ...
> 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
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-im
12 matches
Mail list logo
