Showing posts with label Virtualization. Show all posts
Showing posts with label Virtualization. Show all posts

Tuesday, September 30, 2008

Sharing a Wireless Connection with Virtual Server 2005 VMs

Here's an interesting item (to me anyway).  If you are running Virtual Server 2005 on a computer with a wireless connection, Virtual Server won't let you share that connection with VMs.  You can only share wired connections with VMs.  To get around this, you can install the Microsoft Loopback Adapter, and enable Internet Connection Sharing on your wireless connection.  Then you can create a Virtual Network using the Loopback Adapter, and assign your VMs to that.  One thing to remember though, and it may or may not matter depending on what your are doing with your VMs, is that ICS enables NAT and hands out IP addresses in 192.168.0.0/24 subnet, so your VMs will not be on the same subnet as your physical machine.

The instructions for setting all of this up are on Wade Wagner's blog.  Here is the direct link:

http://www.architectingwith.net/2006/11/30/SettingUpNetworkingOverWirelessWithVirtualServer2005R2.aspx

Friday, October 05, 2007

Clustering in VMware Workstation 6

UPDATE 02.15.08: I updated the last line of the VMX file in step 4 (Thanks for the heads up Jim!)

I have a need to build an Exchange 2007 single copy cluster on Server 2003 in VM environment. This is something I've done before with Microsoft Virtual Server, but haven't had the opportunity to do it with VMware Workstation (OK, I had the opportunity, but never needed to until now). Since VMware Workstation is a paid product, I assumed clustering and setting up a shared SCSI bus would be included and pretty straightforward. Wrong. No options in GUI exist for this, and the VMware help files and knowledgebase provide no assistance. I love VMware, but come on, no easy way to set up a cluster in a product that is meant for lab testing various configurations and applications?


Anyway, after poking around on the web for a while, I was able to compile a working method for setting this up. Here are the steps I took:


  1. Create two VMs with a single disk on SCSI bus 0, install Windows, get updates, etc.

  2. On one VM, add two new SCSI disks (one for data, one for quorum) on SCSI bus 1 (I put them on SCSI1:1 and SCSI1:2), make them independent, persistent, and fully allocate the drive space so that the VMs don't fight over expanding/managing the disk file size.

  3. On the second VM, add the two already created SCSI disks on SCSI bus 1 (again, I put them on SCSI1:1 and SCSI1:2), and again make them independent and persistent.

  4. Edit the .vmx files for each VM and add the following lines:

    scsi1.sharedbus = "Virtual"
    disk.locking = "false"
    diskLib.dataCacheMaxSize = "0"
    diskLib.dataCacheMaxReadAheadSize = "0"
    diskLib.dataCacheMinReadAheadSize = "0"
    diskLib.dataCachePageSize = "4096"
    diskLib.maxUnsyncedWrites = "0"

  5. Fire up the VMs and both should have two disks ready for formatting and clustering.

Admittedly, the lines added to the .vmx file came from Geert Baeke’s Blog, specifically his posting on clustering in VMWare Workstation 4.5 and higher. Also, he has another good post around clustering in VMware Workstation using iSCSI. Trying that out is already on my “to do” list.

As a side note, when you complete botch the configuration of your Windows Cluster (like I did) and want to start over, use this command from the C:\windows\cluster directory on each node, then reboot the node:

cluster node <node_name> /forcecleanup

Wednesday, June 27, 2007

VMware Workstation 6 on Vista

Ran into a “bug” with VMware Workstation 6 when running on Vista. Or, at least I thought it was a bug. When trying change the amount of system RAM that VMware as a whole can use (Edit – Preferences – Memory), or trying to change the memory swapping preferences on the same tab, VMware happily accepts your settings as you click OK. The problem is, the settings don’t change. Make the change, click OK, go back in – no change. Couldn’t find anything out on the net or VMware’s knowledge base.

After much agonizing, a light bulb went on over my head. User Account Control. When I modify my VMware shortcut to run as administrator, and accept the UAC prompt when launching, everything works fine. I know I had “run as administrator” turned on for VMware Workstation 5.5, but I must not have set it up after upgrading to Workstation 6.