George V. Reilly



Picture this.

An external USB hard drive plugged in to a machine running Win64. The OS has vir­tu­al­ized the underlying transport so that it’s es­sen­tial­ly in­dis­tin­guish­able from an internal IDE, SCSi, or SATA drive. Call the machine, Boss, and the USB drive, L:.

Boss is running Virtual PC, which is hosting a 32-bit virtual machine on top of Boss’s 64-bit OS. Let’s call the 32-bit VM, Sidekick.

Sidekick is not only a VM, but a virtual network host. Boss is bridging con­nec­tions to Sidekick, and Sidekick and Boss both appear on the LAN as separate network hosts.

The USB drive has several ISO images, which Sidekick wants to use. Sidekick connects to \MasterL$ over the virtual network, and uses a tool like VcdTool to mount the remote ISO on a virtual CD drive.

Amazingly enough, it all just worked for me last night.

I’m trying to set up an en­vi­ron­ment where I can build Vim with various 32-bit and 64-bit Microsoft compilers and, more im­por­tant­ly, run the Win64 binary. I have a set of VM images with distinct flavors of MSVC, which was necessary to update INSTALLpc.txt and to keep Make_mvc.mak building.

In previous iterations, I got Remote Desktop access to a colleague’s Win64 machine, but that was at Atlas, so it’s no longer an option. I bought a new AMD64 desktop system a few months ago and over the weekend set it up to dual boot.

blog comments powered by Disqus
Review: The Lion, The Witch and the Wardrobe » « Er, er