I have been using Sun’s (now Oracle’s) VirtualBox to run Ubuntu 10.04 as a guest operating system inside a Windows 7 host. I’ve also tried Windows 7 inside an Ubuntu host, but I’m doing it the other way ’round now since I end up using so many Windows-specific applications.
Anyway, what started out as an experiment has become a routine setup for me. Unfortunately, when I set up the Ubuntu guest, I didn’t give it much virtual disk space. So I’m confronted with cloning and enlarging the virtual disk I use for Ubuntu.
After reading many out-dated accounts of how to do this that don’t take into account the UUID and grub problems that could result in simply cloning the contents of disks, I think I have a solution. Here is what I tried using VirtualBox 3.2.2:
- Create a new virtual disk (vdi) the size you want using the tools in virtualbox (File -> Virtual Media Manager).
- Set the new vdi as slave in the specified Virtualbox (Machine -> Settings -> Storage).
- Download (if needed) and attach the latest .iso for Clonezilla (Settings -> Storage).
- Check that the boot order will pick up the CD before the hard drives.
- Use Virtualbox to boot from Clonezilla.
- Follow Clonezilla prompts to copy the old hard drive (vdi) to the new hard drive (vdi). Naturally, make sure you get order correct. Use the disk-to-disk option and allow Clonezilla to use grub when done.
- When done, use Virtualbox to dismount the Clonezille iso.
- If any adjustments are needed in the partitions on the new disk, you can download (if needed) the gparted live iso (the one you can boot from) and use virtualbox to boot from it. I had to do that to adjust the sizes of the partitions.
- After the new disk is just how you want it, dismount any iso from the cd drive, remove the original vdi drive, and reassign the new vdi drive the the top boot order (IDE primary master, e.g.).
- Now boot from virtualbox.
- If all goes well, give yourself a nice beverage.
I am exploring using virtualbox on my Windows 7 64-bit machine to run Ubuntu 10.04 as a guest operating system. Ok, its a little geeky, but I just can’t get along without a little linux once in a while. I’ve used virtualbox before, but mostly on linux host machines running windows operating systems as guests.
Virtualbox 3.2.2 was an easy install on the windows host. The installation of the guest additions (used to more fully integrate the mouse, keyboard, and file systems) was a little flaky, but they seem to be working ok.
I defined a shared folder in virtualbox so I could access my windows documents folder in ubuntu. Then I attempted to mount the shared folder in ubuntu. The command I’ve used for that before is
sudo mount -t vboxfs <sharename> <mountpoint>
vboxfs stands for ‘virtualbox file system’ I always assumed, so its easy to remember.
This has worked before for me, but after several failed attempts, I started reading documentation. Some documents suggested using -F rather than -t, but that didn’t work either. One private web page I found showed “-t vboxsf” rather than “-t vboxfs”. I assumed it was a typo when I read it, but it actually worked for me. Did some Sun (now Oracle) employee make a typo in the new virtualbox?
I hosed the nvidia configuration on my linux box when I tried to set up a second monitor. I kept trying to fix things by reinistalling the driver and running “nvidia-xconfig” like a prompt in nvidia-settings told me. But each time I tried to run nvidia-settings, it told me that it did not appear I had the nvidia driver loaded. When I needed to do was run “sudo nvidia-xconfig”, then run “sudo nvidia-settings”. Once everything was set up, I was able to save the new configuration file (since I was su now).
Ubuntu wanted to update some CUPS programs and maybe some others. I didn’t pay that much attention to the auto update message before I clicked on it to go ahead. After the updates, none of which were kernel updates, my windows xp guest wouldn’t start correctly. It would make it to a black screen and just hang with no useful information in sight.
I shut down the guest, then removed all the options I could under settings. That allowed Windows XP to boot. I then shut down XP and enabled all the settings I needed and reboot XP. All was well.
This has happened to me a couple of times after a kernel update on linux. After the linux kernel is updated, run the command “/etc/init.d/vboxdrv setup” and that should recompile the VirtualBox kernel module and, hopefully, take care of the problem.