LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Disk Space for VirtualBox Clients (https://www.linuxquestions.org/questions/slackware-14/disk-space-for-virtualbox-clients-927724/)

bogzab 02-05-2012 07:18 AM

Disk Space for VirtualBox Clients
 
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?

Thanks for any suggestions.

brianL 02-05-2012 07:33 AM

Found this:
http://www.webupd8.org/2011/02/how-t...x-40-hard.html

sjampoo 02-05-2012 07:36 AM

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.

Smarter ways are probably available, but you'd have to read the Vbox Manual and stuff, which is available at Virtualbox.org ( https://www.virtualbox.org/manual/UserManual.html )

catkin 02-05-2012 07:51 AM

From VboxManage --help output:
Code:

VBoxManage modifyhd        <uuid>|<filename>
                            [--type normal|writethrough|immutable|shareable|
                                    readonly|multiattach]
                            [--autoreset on|off]
                            [--compact]
                            [--resize <megabytes>|--resizebyte <bytes>]

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.

Woodsman 02-05-2012 01:02 PM

Try compacting the virtual disk:

https://www.linuxquestions.org/quest...9/#post4452409

catkin 02-06-2012 01:39 AM

Quote:

Originally Posted by Woodsman (Post 4594506)

AFAIK that technique works only on dynamically expanding virtual disks and does not change the size seen by the guest OS.

bogzab 02-06-2012 02:03 PM

Probably solved
 
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.

mrclisdue 02-06-2012 02:43 PM

I always start with the Slackers, and work down from there.

Starting from the top is always easier.

cheers,

sjampoo 02-07-2012 04:59 AM

It's not to nag, just that there is a separate section ( http://www.linuxquestions.org/questi...ualization-90/ ) you might not have noticed.

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.


All times are GMT -5. The time now is 07:28 AM.