The changes were commited, I mean the vdi files lenght is 100GB and if a open it with gparted, it shows the partition as 100GB. But Ubuntu does not recognize the new size. I also tried to create a new partition and it is not recognized by Ubuntu.
Worked for me. Used the VBoxmanage command, then booted up Ubuntu 15 and used gparted to delete swap, delete ext partition, resize root and then recreate swap. Then used blkid on swap to get new UUID to update /etc/fstab. Reboot as safety precaution.
Parted Magic 6.5 - Partition Manager Live CD I686 64 Bit
1. My virtual machine referenced an existing disk that was of fixed size. I cloned this virtual machine to a dynamically-sized machine. Then I was able to resize this clone and deleted the original. 2. The newer versions of gparted did not work on my virtualbox. I used gparted-live-0.22.0-1-i586.iso and all worked fine.
Worked fine but with later versions of Linux and Gparted was able to turn swap off the partition when running the live version, then delete it build new partitions add the partition to the disc and then create a swap disc. all worked fine.. i just rebooted and all was well.. Thanks for the assistance..
There are also other use cases for type="uninstall", especially for specialized appliances. For containers one can often remove the package shadow (it is required to setup new user accounts) or any left over partitioning tools (parted or fdisk). All networking tools can be safely uninstalled in images for embedded devices without a network connection.
Tells a live ISO image the size of the COW file in MB. When using tools like live-grub-stick the live ISO will be copied as a file on the target device and a GRUB loopback setup is created there to boot the live system from file. In such a case the persistent write setup, which usually creates an extra write partition on the target, will fail in almost all cases because the target has no free and unpartitioned space available. Because of that a cow file(live_system.cow) instead of a partition is created. The cow file will be created in the same directory the live iso image file was read from by grub and takes the configured size or the default size of 500MB.
Specify if the spare partition should be the last one in the partition table. Can only be configured for the oem type with oem-resize switched off. By default the root partition is the last one and the spare partition lives before it. With this attribute that setup can be toggled. However, if the root partition is no longer the last one the oem repart/resize code can no longer work because the spare part would block it. Because of that moving the spare part at the end of the disk is only applied if oem-resize is switched off. There is a runtime check in the KIWI NG code to check this condition
The decision for the overlay vs. dmsquash dracut module depends on the features one wants to use. From a design perspective the overlay module is conceived for live ISO deployments on disk devices which allows the creation of a write partition or cow file. The dmsquash module is conceived as a generic mapping technology using device-mapper snapshots. The following list describes important live ISO features and their support status compared to the overlay and dmsquash modules.
Keep new data persistent on a writable storage device. This can be done with both modules but in different ways. The overlay module activates persistency with the kernel boot parameter rd.live.overlay.persistent. If the persistent setup cannot be created the fallback to the non persistent mode applies automatically. The overlay module auto detects if it is used on a disk or ISO scan loop booted from a file. If booted as disk, persistency is setup on a new partition of that disk. If loop booted from file, persistency is setup on a new cow file. The cow file/partition setup can be influenced with the kernel boot parameters: rd.live.overlay.cowfs and rd.live.cowfile.mbsize. The dmsquash module configures persistency through the rd.live.overlay option exclusively and does not support the automatic creation of a write partition in disk mode.
In KIWI NG all generated ISO images are created to be hybrid. This means, the image can be used as a CD/DVD or as a disk. This works because the ISO image also has a partition table embedded. With more and more computers delivered without a CD/DVD drive this becomes important.
In KIWI NG, all generated ISO images are created to be hybrid. This means, the image can be used as a CD/DVD or as a disk. This works because the ISO image also has a partition table embedded. With more and more computers delivered without a CD/DVD drive this becomes important. The deployment of such an image onto a disk like an USB stick normally destroys all existing data on this device. It is also not possible to use USB stick as a data storage device. Most USB sticks are pre-formatted with a FAT32 or exFAT Windows File System and to keep the existing data on the stick untouched a different deployment needs to be used. 2ff7e9595c
Comments