Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I read here that there is a way to shrink a guest machine's VDI hard disk image. However, its Linux guest instructions say that the method only works for ext3 filesystems. The article was written in 2009, probably why a method for ext4 was not mentioned. My virtual machines use ext4.
Is there a way to effectively shrink my Linux guest VDI in VirtualBox, perhaps similar to the method described in the linked article?
OK, I think I will try your suggestion and just take advantage of /dev/zero. However, the RHEL documentation (I presume it will work for Scientific Linux 6.2, and more or less for Fedora 17??) said there are three "recovery modes": rescue, single-user, and emergency.
Do you know which one is more appropriate for this attempt? I guess probably not single-user mode, because the documentation said "it does not give you the option to mount the file systems as read-only or not mount them at all" (from here). What about the other two?
Sorry, this thread got "lost" in my mail.
I don't understand your question. Log into the relevant guest, create a "big" zero-fill file, then delete it. Do it from a "normal" user should suffice I would think.
Shut the guest down, and try the compact run on the inactive guest.
Sorry, this thread got "lost" in my mail.
I don't understand your question. Log into the relevant guest, create a "big" zero-fill file, then delete it. Do it from a "normal" user should suffice I would think.
Shut the guest down, and try the compact run on the inactive guest.
Sorry about the confusion, what I meant was that the original instructions I saw (in the linked blog post from my original post), it said I should zero-fill my virtual hard disk inside the guest Linux system's recovery mode (instead of logged in as normal user).
Therefore I was wondering *which* recovery mode I should boot the guest system into, because RHEL/Fedora has *three* different recovery modes...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.