Archive for January, 2010

Where Do Tablet PCs Fit in the Market?

The web is abuzz with all kinds of bloggers and other writers talking of how 2010 will be ‘the year of the tablet pc‘. I have to admit, these devices look really cool, but where do they fit in? I’m getting a bit confused about what these tablets are supposed to replace and what exact function they would serve in my life.

A conversation by the BBC with Microsoft CEO Steve Ballmer said it all for me. During the interview, Ballmer was talking about why the tablet would take off this year after years of trying. Ballmer did raise some good points about technology evolving, however, he raised a big question for me. During the interview he stated that, “These things are not replacement [devices] in every sense.” Meaning, one won’t replace their laptop or smartphone with a tablet. My problem is, where does that leave the tablet, then?

For me personally, I’m sick of having more gadgets. I’ve got a BlackBerry, an iPod, a MacBook, a Wii, a DVR, and a desktop computer. I’ve like the idea of having a Kindle and maybe a GPS device, but I’ve been turned off about the idea of having yet another device to throw into my backpack or pocket. If a tablet PC can’t replace one of my gadgets (hopefully a gadget that’s larger than the tablet), then it definitely has no place in my home. In addition to that, I’m not sure what economy these people are living in that we can afford all these devices plus purchase another one that doesn’t let us not purchase either a phone or a laptop.

The closest thing that I’ve heard of a tablet replacing is a netbook. That may be the case, only time will tell. The problem with that logic in my mind, however, is that the tablet PCs will likely be significantly higher-priced than netbooks have been so far which might make them cost-prohibitive as replacements for netbooks.

Of course, only time will tell, but I’m not yet convinced that these tablet PCs will see nearly the market share that we’re being led to believe. If Ballmer is right (I believe he is here) and these devices are just add-ons and not replacements for traditional laptops or smartphones, the tablet is doomed to be a niche product forever.

Tags: , ,
Filed under Tech Trends : Comments (0) : Jan 11th, 2010

Large Storage VMotion and a Little Patience

Whilst doing a little storage vMotion using VMware this week, I got a little lesson in patience from VMware and thought that I would share my experiences to help a few others who are looking at doing storage migrations of larger VM’s. My experiences are with VMware ESX 3.5 and Virtual Center 2.5. Not the most recent, I know, but we haven’t had time yet to upgrade to vSphere 4.

The point of my migration was to get a particular vmdk off a slower set of disks and only a faster set of disks. Due to the fact that ESX 3.5 doesn’t directly support moving only one vmdk at a time, I had to do a little dance to get the one vmdk that I wanted to move, moved. I had to move the virtual machine itself and ended up moving a couple of extra disks in order to to get it to move.

Near as I could figure, Storage vMotion (with ESX 3.5) has the following stipulations:

  1. The virtual machine files must move.
  2. The virtual machine files must move to a datastore that is large enough to hold the largest vmdk.
  3. Apparently, the host needs enough memory free as the size of memory allocated to the already-running virtual machine (during the move, memory usage spiked which caused all kinds of problems for me since this was a large virtual machine, but not really the point). I haven’t verified this requirement yet, but that’s what my initial thoughts are after seeing the behavior.

Seeing the migration options for vSphere 4, I wanted to cry on how difficult my life was made by these requirements, but that’s another story. We’ll be scheduling that upgrade shortly. :)
Anyway, I ran the Storage vMotion. At which point, I managed to bring the virtual machines on my host to a screeching halt, not knowing number 3 right off hand. After killing a few virtual machines and moving a few others away from this host, we were back under way.

Near the end of the Storage vMotion (at 90% to be specific), the interface stayed at the same percent for several minutes and I was greeted with this friendly error:

A general system error occurred: failed to reparent/commit disk(s) (vim.fault.Timedout)

Uh-oh. A quick Google serch found this VMware knowledgebase article.

Unfortunately, I missed the “Incorrectly” throws a timeout error message and panicked a bit. I started digging around in the destination and original datastores and found tons of “DMotion” files everywhere. While desperately looking for solutions around the web, my Virtual Center screen refreshed with the new datastores being associated with the disks and moved over. Yup, while I was freaking out, the whole thing just took care of itself.

Apparently, when working with Virtual Center, one must always have a bit of patience and remember to double-check timeouts inside Virtual Center with the ESX hosts directly. I suppose I should have known better as I’ve seen this kind of behavior while working with snapshots in the past. If you come across this post while searching for this error, take a few minutes to relax and let VMware do its thing in the background while Virtual Center shows stupid error.

Tags:
Filed under How-Tos / Tips : Comments (0) : Jan 11th, 2010

Newer Entries »