Ok, I recognize and greatly appreciate the tremendous contributions of open source software. I really do. I use it every day, and have done so for many years. I’m a Linux person from the word go. But, I work for a Windows Shop. All Windows, All The Time. So, to fill out my time sheet in order to get paid, or to follow all the Track Changes in a Microsoft 2007 proposal document, I have to run Windows, because the company I work for uses 100% Windows software to run their business.
I accept that. And to ensure that I can fill out my time sheet, and track all those changes in MS Word documents, I run Windows in a virtual machine. (As an aside, I also use Open Office, have done so for years, but OO is not 100% compatible with MS Word. It’s also not always too swift with track changes, and I cannot count the hours I have wasted trying to make an OO Presentation look like anything other than the dog’s dinner when viewed in MS Power Point.)
Back to the issue: for my virtual machine, I used to use VMWare, but I switched over to Sun (now Oracle) VirtualBox several years ago. Generally, I’ve been quite happy with VirtualBox. I run the latest patched version of Windows XP in it; it’s got 2-D hardware acceleration, sound, virtual networking etc., so you basically can’t tell that you’re on a virtual machine when you’re using it.
Today I ran up against one of those apparently persistent, long-lived bugs in VirtualBox that threatens to derail my productivity for at least a few more hours. Here’s the background: I created the VirtualBox VM that I am currently using about 3 years ago. At that time, it seemed like a good idea to use a fixed 10GB virtual disk drive for the XP C: drive in VirtualBox when I was building it. Don’t ask why, it just seemed like a good idea at the time.
It turns out though that in the three years that I’ve been using this virtual disk image, successive software installs and upgrades have filled my virtual drive C: all the way up to the brim. I noticed that my automatic SP2 upgrade to MS Office 2007 kept failing because there is not enough space left on the device. I needed a bigger virtual disk.
After a fairly extensive search, I found what appeared to be just the ticket. Someone else who had experience this problem figured out a fix and then took the time to write it up for others to use (thanks, Nick!) Here’s the link, which describes nicely how to copy a virtual system disk over to a larger virtual system disk.
Oh, and here’s the catch:
Remove any snapshots you may have – VirtualBox can go a bit wonky when re-sizing a VDI with snapshots attached (thanks to Darren for pointing this one out).
How’s that a catch, you ask? Well, it turns out that there has been a bug or two in VirtualBox for years that can (usually does, apparently) prevent a user from deleting snapshot files in virtual machine.
Yes, I use snapshots, why wouldn’t I? Snapshots allow you to roll back to a previous instantiation of your VM. Let’s say your Windows VM gets a virus. No problem: roll back to the snapshot you took a couple of weeks ago. No more virus. Now patch against that particular virus.
Bottom line: I’m now unable to successfully copy my too-small virtual drive C: over to a larger disk, because the resultant copy is, indeed, wonky.
Now, let me make it perfectly clear: I am not complaining about the maintainers of Sun (now Oracle) VirtualBox. It’s free software, I’m grateful to have it. It’s generally an excellent product. I’d like to point out from the perspective of being a developer and maintainer of free software myself (see this previous LJ article for a description of one of my FOSS packages): producing and maintaining Open Source Software is a royal pain in the Kazoo. You are always working with limited resources, and all you ever seem to hear is complaints.
Let me therefore say, “Thanks, VirtualBox developers and maintainers for getting us this far.” I'm sure you already have plenty of Kazoos to deal with. I’ll be happy to figure out a meatball surgery approach to get myself out of this latest Catch-22. And then I’ll write about the solution, too.
|Designing Electronics with Linux||May 22, 2013|
|Dynamic DNS—an Object Lesson in Problem Solving||May 21, 2013|
|Using Salt Stack and Vagrant for Drupal Development||May 20, 2013|
|Making Linux and Android Get Along (It's Not as Hard as It Sounds)||May 16, 2013|
|Drupal Is a Framework: Why Everyone Needs to Understand This||May 15, 2013|
|Home, My Backup Data Center||May 13, 2013|
- RSS Feeds
- Dynamic DNS—an Object Lesson in Problem Solving
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Designing Electronics with Linux
- Using Salt Stack and Vagrant for Drupal Development
- New Products
- A Topic for Discussion - Open Source Feature-Richness?
- Drupal Is a Framework: Why Everyone Needs to Understand This
- Validate an E-Mail Address with PHP, the Right Way
- What's the tweeting protocol?
- Kernel Problem
9 hours 51 min ago
- BASH script to log IPs on public web server
14 hours 18 min ago
17 hours 54 min ago
- Reply to comment | Linux Journal
18 hours 26 min ago
- All the articles you talked
20 hours 50 min ago
- All the articles you talked
20 hours 53 min ago
- All the articles you talked
20 hours 54 min ago
1 day 1 hour ago
- Keeping track of IP address
1 day 3 hours ago
- Roll your own dynamic dns
1 day 8 hours ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi
It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?