I say Resolved Mostly because the issue is resolved as far as the subject of the thread is concerned. The reason to pursue it is not resolved, but it's also not a Linux issue.
On 05/06/2014 05:59 PM, King Beowulf wrote: > On 05/06/2014 05:17 PM, Dick Steffens wrote: >> Has anyone had occasion to expand a vmdk file with a Linux host - >> preferably running Ubuntu, but any Linux flavor will help. > The host is not relevant: the Virtuabox commands are the same > (depending on who did the package, of course; some debian-esque > varieties leave out a bunch of symlinks to the '/opt/VirtualBox/VBox' > script): > > http://www.virtualbox.org/manual/ch08.html#vboxmanage-modifyvdi > > For safety, I would clone the VDMK image to VDI and modify the latter. On 05/07/2014 07:57 PM, Joe Shisei Niski wrote: > Thanks , Dick, for asking, and to KB for responding - it inspired me to > finally tackle the overdue chore of cloning my ancient 20GB fixed-size > VDI (created when storage was much more expen$ive) to a dynamic image, > which i can resize easily. The cloning process was a CPU-sucker but > seems to have worked. This article cuts to the chase with the VBoxManage > utility, which gets installed correctly on Ubuntu 12.04: > > https://brainwreckedtech.wordpress.com/2012/01/08/howto-convert-vdis-between-fixed-sized-and-dynamic-in-virtualbox/ Thanks to both of you. I successfully added disk space to my virtual machine. Not having had a reason to do this sort of thing often, once I had the expanded .vdi file I didn't know what to do next. But I found that at: https://blogs.oracle.com/oswald/entry/importing_a_vdi_in_virtualbox It's not so much importing it as creating a new VM with that hard drive image. Once that was done I fired it up but had no network connection. Turns out that the network settings for the new machine had to be changed from "NAT" to "Bridged Adapter". I was thinking that I was copying the old machine, but in fact I was creating a new machine, and that setting is not part of what was copied (apparently). Anyway, the process is straight forward: 1. Get the UUID of the old machine: $ vboxmanage list hdds 2. Clone the desired image as VDI: $ vboxmanage clonehd [UUID of source image] [name of output].vdi --format VDI 3. Resize the virtual hard disk space on the cloned image: $ vboxmanage [name of output].vdi --resize [new disk size in MB] 4. Create a new virtual machine using the newly cloned and resized image. 5. Change the network to bridged (at least, that's what my case needed) 6. Fire up new VM. 7. Use some partition editing tool to resize the old partition so that it uses up the new space. I used EaseUS. It says to use Merge Partitions, but that didn't work as advertised. Instead I used Resize/Move Partition. Grab the line between the old partition and the empty space and drag to take up all the empty partition. Close the EaseUS and reboot. Actually, reboot about three or four times until Win2k comes up the way it's supposed to. 8. Sure enough, the virtual Win2k sees a lot more disk space (I gave it 20 GB -- this is for video stuff). Alas, after all that, for whatever reason, the program I want to have access to more disk space doesn't see it. I suspect the better solution will be to start over and install Win2k fresh, with the amount of disk space I want, and then re-install WiRNS. WiRNS, by the way, is a program that interacts with my old ReplayTV PVR. It's only good for analog, but I can run the output of a VCR into it to digitize some old tapes. WiRNS can save those recordings to the machine on which it's running. -- Regards, Dick Steffens _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
