From e680c3de999c14d62c06e11951144ebd55ab77a7 Mon Sep 17 00:00:00 2001 From: Andrew Sorensen Date: Sun, 4 May 2014 22:28:55 +0000 Subject: [PATCH] ResizeDiskImage changed Minor edits to template disk image --- ResizeDiskImage.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/ResizeDiskImage.md b/ResizeDiskImage.md index 218ce158..450cb62f 100644 --- a/ResizeDiskImage.md +++ b/ResizeDiskImage.md @@ -80,11 +80,11 @@ If you want install a lot of software in your TemplateVM, you may need to increa 1. Make sure that all the VMs based on this template are shut off (including netvms etc). 2. Sanity check: verify that none of loop device are pointing at this template root.img: `sudo losetup -a` -3. Resize root.img file using `truncate -s ` (root.img path you can obtain from qvm-prefs). +3. Resize root.img file using `truncate -s ` (the root.img path can be obtained from qvm-prefs). 4. If any netvm/proxyvm used by this template is based on it, set template netvm to none. 5. Start the template. -6. Now you can execute `sudo resize2fs /dev/mapper/dmroot` in the template. -7. Verify available space in the template. +6. Execute `sudo resize2fs /dev/mapper/dmroot` in the template. +7. Verify available space in the template using `df -h` 8. Shutdown the template. 9. Restore original netvm setting (if changed), check firewall settings (setting netvm to none causes firewall reset to "block all")