Dan Newcome on technology

I'm bringing cyber back

Archive for January 2009

Thinkpad X200 Unboxing

leave a comment »

I just got my hands on the Thinkpad X200 that I ordered nearly 2 months ago.  I’m planning on writing a few posts on getting Ubuntu installed, but in the meantime I thought I’d be lame and do an unboxing since I’m so excited.

The box was pretty small, I was worried that they just shipped the accessories first.


Sure enough, though there was actually a laptop in there





That’s an ATT SIM card in the battery bay.  I don’t plan on using wireless broadband, so I hope I don’t have to de-activate this or anything.


The 9-cell battery is one of the things that sealed the deal on this laptop for me.  I’m sick of running out of battery after 2 hours or so.


The X200 is a bit smaller than my 14.1″ T61.  Hopefully not too small though.


Finally, the money shot.  A bit anti-climactic with all of the sticker spam.  I think that someone came up with a word for the stickers that they put all over laptops, but I can’t seem to find the blog post now.


That’s it for now.  I have already upgraded it with 4GB of 3rd-party RAM, which was not as uneventful as I would have thought.  After all, how much of a no-brainer is throwing more RAM into a machine (provided that you understand the difference between DDR2 and DDR3)?  I’ll have to save that story for another post.

Written by newcome

January 26, 2009 at 11:11 pm

Posted in Uncategorized

VirtualBox on Linux: my new workstation virtualization setup

leave a comment »

I just thought that I would make a quick note on a new virtualization solution that I have been using on Linux (and why I switched from VMware server).

VirtualBox was created by a company called Innotek.  Sun eventually bought the company and continued development of VirtualBox as a compliment to its own xVM virtualization solution.

Let me preface the following by saying that I have been a longtime user of VMware on both Windows and Linux platforms since the VMware GSX Server 3.x days.  Most of my VMs were for setting up testing or build environments.  Following the 1.0 beta release of the free VMware server product I switched completely to it from GSX Server.

Fast forward to a little over a year ago, when I wanted to consolidate all of my working environments onto my laptop, on which I run Ubuntu Linux.  I still needed a Windows environment for doing .NET development work, so I moved my development environment that was formerly on a dedicated machine over to a VMware instance on my laptop.  Following this move, I found myself spending sizable chunks of development time fully inside of a Windows VM running on VMware server for Linux, during which time I really started to notice that the VM was not nearly as responsive as the VMs I had running elsewhere on Windows Server hosts.

By running some (relatively unscientific) benchmarks I realized that CPU and memory speed seemed fine, but disk IO was abysmal.  I figured that I would be able to fix the problem by using a raw device for the VM disk, or by setting noatime on the filesystem that the .vmdk disk was on.  However, I found that no matter what I did, I couldn’t get the IO speeds up to where VMware Server for Windows was.   I could not get the responsiveness of my VMware virtual machines to be good enough to work in Visual Studio without wanting to cry every time I went to add a new library reference to the project that I was working on.

Following the frustration of not getting the performance that I was after using VMware and having committed to using virtualization for development work, I started looking around for other solutions.  I installed Xen, but I was turned off by the fact that I had to use a different kernel to use it.  My other options were KVM, qemu, and VirtualBox.  I had looked at all of these in passing before but I hadn’t evaluated them with the intent of actually deploying them as part of my workflow.  VirtualBox had just been bought by Sun and it seemed to have picked up a lot of steam, so I gave it the first shot.  I had installed an old version of VirtualBox previously and had already installed Windows under it, so in fairness I really didn’t give the others much of a chance.  I may revisit the others in time.

VirtualBox turns out to be less stable than VMware which is perhaps not surprising, given the maturity of VMware.   I have experienced some occasional crashes while performing network IO using Windows filesharing or Samba.  However, it did rings around VMware in terms of disk IO, which I think had an impact on my productivity.  I may dig up my numbers on this stuff if I have some time later, just to show some verification.  I may have sacrificed some CPU efficiency, but the user experience is definitely improved compared to my VMware VMs.

This post definitely went longer than I had anticipated.  Hopefully this helps someone out that is looking for a snappy VM environment under Linux.

Written by newcome

January 14, 2009 at 1:11 pm

Posted in Uncategorized