The situation is a bit weird in this case, but I think the basic idea still holds: putting the OS files and the Virtual Memory Paging File (commonly known as a swap file) on the same partition is asking for trouble, if only because of fragmentation.

At the very least, I always try to create a seperate partition to use for swap, if not an actual seperate disk. The maximum wisdom in these matters is to divide your swap requirement over as much bus capacity as possible, but avoiding otherwise busy areas. So: not on the same partition as the OS. If there are two physical disks, then one-third on the disk that also has the OS and the rest on the other disk. Never on two partitions on the same disk; that would just make the head move around like mad and slow things down all around.

In this case, everything actually resides on the same file system on the same disk in the Host OS, so the logic hardly applies. My only reasons for creating a seperate virtual disk and using that is that the fragmentation issue is still relevant and that it is more manageable, in case I decide to expand the disk setup in future.

Like real ones, virtual disks can be swapped in and out of a system or replaced with bigger or smaller ones, but doing the same with partitions requires much more difficult procedures and low-level fiddling with tools like PartitionMagic. All in all, I would just a much avoid having to that altogether.

In the end, I formatted the (very much overcapacitated) swap drive and moved the swap file from the OS drive onto the swap drive.

As outlined earlier, I have moved the virtual disks to the hard drive of the host machine, my laptop. The assumption was that that would make a difference in performance. Well ... let's just say that my instincts were right: the Virtual machine with Server 2003 installed has been tuned down to 'merely' 384MB of RAM and it still starts up three times faster than it did when its disks were physically on the external drive.

Soon after trying to do the first thing that involved networking (connecting from the host to the guest using Remote Desktop, to be precise) I found out that networking was not operational.

The first thing that I did was to configure the VMWare networking subsystem. Sort of like a virtual machine provides a machine's hardware, there is a service installed that provides the machine's networking environment. This means a NIC inside the virtual machine, but also one or more NICs on the host. VMWare is able to act as a bridge, connecting the virtual 'internal' network to actual outside NICs, thus providing virtual machines with connectivity to the rest of the world, beyond the host.

I opted for host-only networking (which effectively disables outside access for the virtual machine; the concept is like plugging a cable into a router that is local to this small network.

To avoid confusion between the private IP range on my home network and the private IP range on the host-based network, I set the DHCP range to use the 10.0.0.0 network.

Apparently, newly configured Windows 2003 servers don't even bother looking for a DHCP server, so I changed the TCP/IP properties to 'Obtain an IP address auomatically'. I have often wondered why Microsoft don't just call this option 'Use DHCP when available', which would be a much more accurate description of what it actually does. Oh, well, it works anyway.

With the NIC disabled and re-enabled, Server01 has now got an IP address that is actually on the network it is on and I can ping the box from the host. Strangely enough, I couldn't seem to do that the other way around at first. Then it hit me that I usually have Norton Internet Security running, which is (among other things) a firewall, which undoubtly blocks incoming ICMP messages.

I say undoubtly, because making sure is just too much work to find out. I reckon I won't be using that product for very much longer, especially when XP SP2 comes out with its vastly improved built-in personal firewall. NIS seems to be wanting to do the right thing (configure all applications exactly according to their needs and only allowing incoming traffic when there is a corresponding application running) but the interface is so incredibly clunky that I can't seem to deal with it. Also, it appears to have a very hard time remembering settings. But that is the topic of another rant, another time.

After disabling the firewall and bouncing the host NIC (to get the right IP address from the reconfigured DHCP server) I had connectivity in two directions and I was able to set up a Remote Desktop session.

This setup really is too slow to work with and I can not help but think that the external disk is the biggest culprit. So there is nothing left to do but move the virtual disks (2 times 2GB, although on the actual host file system they are much smaller, following usage inside the guest) to the laptop's hard drive.

That does present me with a problem that I had really wanted to avoid having to solve: moving my MP3s off that disk, so that enough space is cleared up. Moving them in itself is not that big a deal: I have them backed up on the external drive as it is anyway and 99.9% of the time that I am playing music it is at home, with the laptop hooked up to a HiFi system anyway.

The only problem is that in my past experience and from what I have read on various fora, iTunes will do anything in its power that it can to treat moved files as new ones, thus losing play count and 'last played' dates. I have an intricate system of 'Smart Playlists' in use that depend on these two data items heavily and it has taken me literally months to get the whole Library sufficiently randomised for it to work--hardly something I want to give up easily. Time for a sub-project...

After restarting from the VMWare tools installation, at least the screen looks decent and the mouse pointer is responsive. Other than that, it is a very slow affair. It looks like I will have to shut down most or all of the activity on the host machine, in order to conserve CPU resource. This ought to be fun when I have two or even three of these running. :)

As per instructions, I create the contoso.com domain name, which automatically sets the NetBIOS name of this box to CONTOSO. I let the install do whatever it feels like next, which seems to include a reboot. See you a bit later, then...

This is so nifty: it used to be that you had to do some tricky stuff with the interface and the OS, which would replace your floppy drive temporarily with a built-in virtual drive. All right, but it did require some manual actions on behalf of the user.

Now, it is just a menu option in the interface. A drive will appear within Windows and it will autorun the setup. I opt for the custom option, so that I can opt out of the SCSI acceleration (don't need it) and the host-guest file sharing option (don't want it, since I will be doing all kinds of network stuff on these boxes and I do not need surplus confusion).

Installing is a snap; a reboot is advised, so I do that.

Sure enough, the box rebooted by itself and I was able to log on. Now for the few initial pieces of setup and I will have sucessfully installed a Windows Server 2003 Enterprise Edition machine. :)

The OS rightly complains about a very low resolution and color setting. It offers to correct it automatically and I take the offer. Neverthelss, I should install VMWare tools first.

As per instructions, I configure the OS for the right keyboard and time zone. I also leave the network settings to 'not belonging in a domain, but part of workgroup 'WORKGROUP'.

I supply a password for the administrator account. The book says it will accept either very good paswords or total blanks. I tried something inbetween and sure enough, the thing complained about it. It did give me the option to proceed anyway, which might mean that the book is in error. I'll try that another time, for now I have just put in an acceptable password.

The installation continues with copying files and configuring the installation. It seems to take long times without any obvious activity, barring the small squares in the bottom right corner that light up in sequence. The timer claims something like 27 minutes to go, but the underlying algorithm does not seem to be very informed about the relation between time passed and the time needed to actually perform the tasks ahead.

Nevertheless, it is all sailing smoothly ahead.

As expected, with the Windows Server 2003 Enterprise Edition CD in the external drive, the Virtual Machine happily boots up and starts the setup procedure from CD.

Unlike I expected, the initial file transfer is taking a very long time. In fact, I have done more than a few installations of Windows 2000 from the four-floppy disk set that you can create, and in my recollection, that went through noticeably faster.

Maybe the problem is bus contention: the disk on which the virtual disks are stored is an external drive on a USB2.0 connection. fast enough for continuous drive oprations, but it eats system resources when multiple processes are accessing files, because unlike with an IDE controller, the OS must do a lot of work to manage the USB traffic.

I can't say for sure without doing the whole thing twice with a stopwatch, but killing eMule (which has dozens of files open on that same drive) seems to speed things up a little bit. Still darn slow, though.

As per the instructions in the book, modified for my situation, I configure the drives and partitions. I am leaving the swap partition unformatted for now; that can be done in Disk Administrator at a later time. Besides, there is no obvious option at this point to format both partitions.

I want to have a seperate disk to use as a swap drive for my virtual servers. That makes the total set of parameters:

• 788MB of RAM. I have 1GB in the host machine, so it is available. At the time when I will be running more than one server, it is easily enough decreased. Until that time, more RAM makes the VM a lot faster.
• The primary hard drive (master on IDE0) is a 2GB drive. The drive intended for swap is also 2GB, on IDE1.
• Networking is limited to the 'host-only' option, because even though there is hardly anything to damage on my network, I want to limit the networked exposure these servers get. It isn't too difficult to accidentally hook them up with a live Internet connection and these things are not patched at all. Given the time constraints that I am working under, a heavy worm or virus infection is just too much fun to be dealing with.
  I am assuming that the host-only option means that two virtual machines running on the same host will be able to communicate with each other. If not, settings are changed easily enough. (why people bother with real hardware, I don't know... :)

WIth everything I need downloaded, it is time to start the installation. A tad later than I had hoped (I had hoped for 10:00 am this morning :) but the night is still young and this process is going to take a fairly long time of waiting. It should blend in with the rest of my evening just fine.