August 2006 - Posts

As I mentioned in my previous post, Beta 2 of Microsoft Virtual Server 2005 R2 SP1 is out. One feature that others and I have wanted for a long time is the ability to mount a virtual hard disk (VHD) file without having to start a VM.

The VHDMount utility is a command-line tool that's automatically installed when you install the beta. However, if you look at the readme, you can extract it and install just this tool.

How doyou mount a disk? Well, before you get too eager, a few of notes:

  1. It's a beta. For now, I would keep backups of my important VHDs before I mount them—just in case.
  2. If you're running Windows XP, you'll have to first "plug-in" the virtual hard drive and then mount it via the Windows Disk Management tools.
    That said, I was unable to get a drive plugged in on my XP box.
  3. If you're running Windows Server 2003 (and supposedly Longhorn Server and/or Vista), you can both plug as well as mount (which effectively will plug the drive in and then mount it). When you choose to mount the drive, VHDMount will pick the next free drive letter. However, you can specify a drive letter if you wish.
  4. When you mount a drive, a warning dialog box will appear (see Figure 2 below). I'm assuming at this point this is a side affect of the beta.

Figure 1 displays the command-line to mount mount a VHD with the drive letter X: on a x86 Windows Server 2003 SP1 box.


Figure 1: Command to mount a VHD.
Note: You don't specify the colon, just the letter.


Figure 2 displays the warning dialog box you'll receive each time you mount a drive.


Figure 2: Warning Dialog

Figure 3 displays the results of the command issued in Figure 1.

Figure 3: Successful mount of a VHD.

Figure 4 displays the newly mounted drive in the Disk Management MMC.


Figure 4: The VHD mounted in Disk Management

Figure 5 shows the root of the drive in Windows Explorer.


Figure 5: The VHD mounted and accessible via Windows Explorer.

Finally, for the curious, yes, the drive is read-write. However, remember that Microsoft doesn't currently support offline patching of "real" machines and thus doesn't (yet?) support offline patching of virtual machines either.
Figure 6 shows the root of the drive in Windows Explorer with two files deleted from the root (compare Figure 6 to Figure 5).


Figure 6: The VHD mounted and accessible via Windows Explorer with two files deleted from the root.

When you're all done with the drive, you unmount it using the /u switch (see Figure 7):


Figure 7: Unmounting a VHD.

Figure 8 displays the command-line results of the unmount.


Figure 8: Successful unmounting of a VHD.

End of line.

Wahoo! A new release that's ready for the testing.

What's new you ask? How about:

  • Support for AMD® Virtualization Technology (Beta 1 only supported Intel)
  • Volume Shadow Service Support (backup VMs while they're running)
  • Offline VHD Mounting (this one's for you Mike!)
  • Active Directory integration and management features

Versions are available for x86 and x64. From where you ask? Go to the product page for details but you need to use Microsoft Connect to get the goods (immediate acceptance to the program if you're not already testing).

End of line.

I've have quite a few friends who have been smitten by the Mac bug (especially Intel Macs). In addition, others are considering moving that way (I won't "out" them just yet ;-) ).

Some, like John, run Parallels Desktop for Mac. Others, want to use BootCamp so they can run Vista, possibly with Aero Glass.

Today I learned about CrossOver Mac. It lets you run your Windows programs in a window without the need for VM software like VMWare for Mac or Parallels or the need to dual boot with BootCamp. In particular, with the disclaimer that I'm not a lawyer and I don't know anything yet about how CrossOver Mac works, it appears you don't need a Windows license to run a Windows program.

This is interesting indeed.

End of line.

This article from MSNBC has a sad quote [0]:

It wasn’t clear how long they would remain in effect, though Rep. Pete Hoekstra, R-Mich., said the situation “eliminates the days of carry-on baggage.”

No carry-on? Well, let's just kill international business travel. I'm sorry, but are we going a bit overboard here? I mean seriously, are we going to have to stop wearing clothes? As a person who travels for business and works on almost every flight, no carry-on for me means no flying for me.

I'd like to know if Rep. Hoekstra flies commerical? Does he really want to sit twiddling his thumbs while flying? Or does he not have to worry about it because he has a private jet?

End of line.

[0] http://www.msnbc.msn.com/id/14282396/

'nuff said.

End of line.

WF = Windows Workflow