Archive for March, 2009

Last minute crash

Posted by Mike Taber on March 23rd, 2009

Well, at 5:05pm on Friday (go figure on the time problems started), my computer was acting flaky so I decided to do the normal thing and reboot. Unfortunately, my desktop at the office decided to flake out entirely and for some reason decided it no longer wanted to be part of the Moon River domain. To top it off, the local passwords weren’t working either, so I couldn’t log in and do anything about it. I left it for the weekend and decided to deal with it on Monday when I got back.

So now it’s Monday and things have gotten worse. My PC has decided that it doesn’t like the filesystem on my boot drive and disk checks claim it is corrupted. My data drive is still perfectly intact, but the boot drive thinks there are now two partitions instead of just one and that neither of them is bootable. I think I’m going to have to resort to reinstalling the OS, which I always hate to do because of the fact that it’s just such a pain in the neck to reinstall all of my applications.

The only bright spot is that I’m pretty good about keeping non-essential data off my main PC and keeping backups of that data on an external drive and maintain regular backups of that external drive on my NAS server. I’m guessing that the odds of me having any essential data on that drive is pretty low, although I could be mistaken. I do tend to keep text files of notes I’ve taken about different phone calls on my desktop until I get a chance to enter them into our CRM system.

In other news, I’ve started on a new series of articles on how to build a consulting company. I expect to have the first article out the door sometime next week. It would be sooner, but I have a small computer problem to deal with.

Read More »

Repeated Characters in VMWare

Posted by Mike Taber on March 2nd, 2009

For those of you who experience occasional typing problems with your VMWare machines, there’s still hope. Over the past few years, I’ve run into this problem several times, and every time the symptoms are basically the same.

When you’re using a remote console to access a virtual machine, as you start typing the characters will start repeating themselves on the screen. Most of the time, typing and then seeing those characters on the screen is exactly what you expect. Until you hit go to type ‘root’ into a Linux VMWare image and it comes out as ‘rrrooooooooootttt’. Typing very slow sometimes gets around the problem, but not always. Typing a password becomes especially difficult as you have no idea whether extra characters are appearing and depending on how your machine is configured, you might lock out an account. Rebooting the image will sometimes make the issue go away for a little while, but it often returns at the worst possible time.

I used to think this was a low memory related problem, caused by the host using too large a pagefile, thus causing delays and screwing with the low level interrupts. I came to this conclusion mainly as a result of running VMWare Server on a Windows 2003 server with about 4GB of RAM. After overcommitting the memory, this bug tended to surface quite a bit, so I started offloading the virtual images and only running a few when it was absolutely necessary. It turns out this isn’t solely related to memory.

There’s a VMWare KB article that explains how to address this issue and states that it happens due to low bandwidth situations. I beg to differ on the bandwidth situations, as I’m running gigabit on my network and lets face it. My network really isn’t that big. I have at most 2 hops between any given location and it’s generally limited geographically to about 10 feet.

Basically, their fix is as follows: power off the virtual machine and modify the .vmx file for the image you’re having problems with to include the following line:

keyboard.typematicMinDelay = "2000000"

Once you’ve done that, there will be a 2 second delay introduced to prevent single characters from repeating themselves numerous times. Unfortunately, I found this recommended fix didn’t work as well as I would have liked. You see, 2 seconds is a long time for computers. And after you’ve done this, the Backspace key becomes pretty much useless. After some trial and error, I found that cutting this value by 75% seemed to work pretty well.

keyboard.typematicMinDelay = "500000"

Since I added this line to each of my .vmx files, I’ve yet to run into this issue again using any of the remote administration tools provided by VMWare.

Read More »
Twitter Delicious Facebook Digg Stumbleupon Favorites More