SlackwareThis Forum is for the discussion of Slackware Linux.
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 have been using Virtual Box for a couple of years to occasionally run a Windows XP client Virtual machine. Recently Windows has been very slow and issuing warnings that I am running out of room on C:.
Two questions in regard to this:
1. Will removing VBox Snapshots result in freeing up space and allowing C: to use more space ? (Seemed to do so when I removed one of the snapshots - there are a couple more I could remove).
2. Is there a method for increasing the size of the disk space allocated to the client VMs in Virtual Box?
This question isn't really slackware related, is it?
Google didn't pop-up with only one answer, since there's been a lot of versions and options of Vbox around. Anyway, I would suggest to do it like you would when it was a real computer: Add a new big harddrive (virtually, thus not by using real screwdrivers, cables and a real disk, but through VirtualBox configuration), use some clone software like Acronis or Ghost to move the data/installation from one small-virtualdisk to the other bigger-virtualdisk, remove the smaller one from the virtual system, and there you are.
The --resize option should be able to increase the size of your virtual HDD; you would then need to increase the size of the file system in exactly the same way as if it were a real computer. Assuming WXP is not natively able to grow its partitions and file systems, you would need to boot a partition and file system management tool in the VM, something like Boot IT Bare Metal.
A backup would be prudent but that is easy -- you simply make a copy of the .vdi file on the host.
Thanks to all who replied - looks like it's not so difficult, I just didn't find the answer within the various settings of the Virtual Machine, where I kind of expected to find it if it was simple. Some combination of the suggestions offered should do it. Complicated, I think, by the fact that I created the Virtual Machine in the first place using a pre-Version 4 VirtualBox whereas the utility referred to by some of these responses and links within them is a Version 4 utility I think.
Sorry to take up your time with stuff that is "not really Slackware related", but I usually find that Slackers are happy to help other Slackers here even when the Slackware system we are all running is not really the root of the problem.
Anyway: Upgrading to the last version of VBox isn't that hard. Maybe you must update the VBox tools inside your virtual machine before you can use the newer things that are available inside VBox 4 and not in the older VBox 3.x, but I only noticed slight changes in the CLI/GUI of Vbox and not inside the VirtualMachines them selves. Even without VBox tools installed you could/should be able to change most of the virtual-hardware configuration.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.