Differences

This shows you the differences between two versions of the page.

--- computing:virtmanagerhell [2021/11/17 15:40] – oemb1905
+++ computing:virtmanagerhell [2022/08/08 06:41] – oemb1905
@@ Line 60: / Line 60: @@
 At this point, I would probably reboot and then from within the VM, ping 8.8.8.8, and then ping google.com to ensure you have link and upstream DNS.  Everything should be rosy ;>.  Some folks might be concerned about ARP and such, but virt-manager handles that with the gateway entry combined with the bridge, so no need to alter proc and pass traffic, etc.  Of course, replace Google's DNS if you so choose, but I had reliability problems with Level 3 during testing myself (sad).
 -- Below, are notes from when I shrunk an .img file / expanded an .img file (cannot remember lol) --
@@ Line 92: / Line 93: @@
   mv /var/lib/libvirt/images/outdisk /var/lib/libvirt/images/putnameofimagehere.img
- --- //[[jonathan@haacksnetworking.org|oemb1905]] 2021/11/17 08:39//
+Made yet another attempt to do by command line in 2022. Install packages required for resizing virtual hard disks and for listing partitions inside virtual hard disks.
+  apt install qemu-img kpartx
+Add 50G of size to the emulated physical hard disk. This is not to be confused with adding space to, or extending, the partition inside it.
+  qemu-img resize debian10.img +50G
+Mount the image file in the present directory, and show all of its mappings.
+  kpartx -v -a debian10.img
+Now, it is time to extend the partition. Your loops might have different #s after, use tab to find the right one (prolly largest #).
+  parted /dev/loopXX print
+You will get output like this:
+  Model: Unknown (unknown)
+  Disk /dev/loopXX: 142GB
+  Sector size (logical/physical): 512B/512B
+  Partition Table: loop
+  Disk Flags:
+  Number  Start  End    Size   File system  Flags
+      0.00B  142GB  142GB  ext4
+Remove the appropriate mapping. In my case, I am extending the boot volume of a virtual machine, so it was entry 1.
+  parted /dev/loopXX rm 1
+Extend the partition from the start of the mapping you removed to the upper size limit listed in Disk.
+  parted /dev/loopXX mkpart primary ext4 0.00B 142GB
+Verify the new mapping.
+  parted /dev/loopXX print
+Run fsck before resizing the file system. You here appending "p1" to the name in order to make a new partition or mapping.
+  e2fsck -f /dev/mapper/loopXXp1
+Extend the file system inside the partition to the entirety of the partition table.
+  resize2fs /dev/mapper/loopXXp1
+Unmount the image
+  kpartx -d debian10.img
+After messing around with this, and succeeding 1 time in resizing the drive this way, I decided that just issuing ''apt install qemu-img kpartx'' and then expanding within the VM's gparted GUI was far easier. It does require moving and/or deprecating swap (or other earlier partitions) or you cannot merge the file system.
+ --- //[[jonathan@haacksnetworking.org|oemb1905]] 2022/08/08 00:37//

Haack's Wiki

User Tools

Site Tools

Differences

Page Tools