Skip to content

Posts from the ‘Virtual PC/Server’ Category

Virtual Server Clustering with Virtual Server 2005 R2

Clustering options
VS2005 R2 offers three different clustering scenarios:

  • Virtual Machine Guest Clustering (iSCSI): Virtual Machines are clustered on different hosts.
  • Virtual Machine Guest Clustering (Shared SCSI): Virtual Machines are clustered on the same host.
  • Virtual Server Host Clustering: Virtual Servers are clustered on different hosts

With Virtual Machine Guest Clustering, each Virtual Machine (VM) is a cluster node. Cluster-aware applications that are running inside a guest are considered resource groups. If an application within a resource group fails or if the guest fails, the VM containing the failure will automatically failover to another VM on the same host or on a different host. This protects against application failure.

Virtual Server Host Clustering, on the other hand, protects against host failure. Should a VS2005 R2 host fail, the VMs running on the failed host can be automatically migrated to another host in the cluster.

Using iSCSI with Virtual Server 2005 R2

Comparing Host Clustering to Other Types of Clustering

What works and doesn’t work with Virtual PC/Virtual Server?

I found myself playing with quite  a few operating systems lately seeing that most of them run in a Virtual environment with Microsoft Virtualization Software. So I set out on a mission to try all of the operating systems that will work in a virtual environment… after viewing the list… I realize that it may take awhile to accomplish this goal…Here it is, take a look

P.S Microsoft’s support for 90% of Linux distributions pretty much is nonexistent. I would suggest using VMware for Linux, Solaris or any other UNIX based OS.

Error: Result Code: 8 Virtual Server Migration ToolKit (VSMT) Virtual Server 2005

A few weeks ago I was performing a few P2V (Physical to Virtual) Migrations on a contract for a company we will leave unnamed. using my laptop, Which I had ADS and Virtual Server installed on, I successfully captured 3 physical machines and ported them to virtual images for use in Virtual Server 2005. Server consolidation is amazing! but anyway, the last machine I was doing for them gave me quite a few problems, so I end up asking M$ for support. I knew the issue had something to do with a driver, and I narrowed it down to NIC or SCSI on my own. So after being on the phone with M.$ for 3 hours, they helped me determine what I had already known, and they were going to look into this further. while waiting for them to get back to me, I decided to try and find a work around. I noticed an EISA partition before the C:\ partition. I didn’t want to remove it, and even if I did… would it ever boot again? So my solution?

I worked around the problem by added an 80GB IDE Drive!

I used a disk cloning tool to clone the SCSI 36GB to the 80GB IDE. I then shutdown, removed the SCSI drives, booted onto the 80GB. While in Windows I modified the boot.ini to boot from the first partition, rebooted and pressed any key to boot from a the Windows 2003 CD… I removed the EISA drive during setup. Once the drive was removed, I reset and was able to successfully boot into Windows on the 80GB with no EISA drive!

After this was complete, I ran the “hwgather” to regenerate a new XML with the correct hardware info, regenerated the P2V files using VSMT, and the ADS deployment was 100% successful! Yay!

In order to get this done I had to rig up another ATX power supply (Jump pins 14 and 15) to power the IDE drive, so I took the server home to complete this, and it was much faster performing the disk capture over a GB Ethernet anyway
Unfortunately I realize my solution really didn’t help determine what the original problem was, but I’m more than sure we can chalk this up to the SCSI drivers or the ESRIA drive partition, after using 6+ different drivers that I had found on-line, I just gave up!
The error while trying to pull the migration was:
===>Remote job output:180
<===Remote job output
Error: Result Code: 8
Error occured, exiting (8)

Automatic Deployment Servers (ADS) & Virtual Server Migration Toolkit (VSMT) Step By Step

Step1 :
       Install Microsoft Virtual Server 2005.
Step2 :
       Install Automated Deployment Services in the same or different machine then Virtual Server 2005.
Step3 :
       Install Virtual Server Migration Toolkit.
Step4 :
       If you install the ADS on the same machine of DHCP Server you need configure ADS with this command:
           C:\Program Files\Microsoft ADS\bin\ADSdhcpconfig.wsf /add
Step 5 :
      On samples directory of you VSMT installation, execute the script CreateVirtualNetwork.vbs, to create VM0 network definition in your Virtual Server 2005.
All the executables below are in your VSMT installation directory:
Step 6 :
      Execute the command:  gatherhw.exe  on the machine that you will migrate, this command will generate one XML that will be used by VSMT; send the file to VSMT directory.
Step 7:
     Execute the command:  VMScript.exe /hwvalidate /hwinfofile:<Guest Server>.xml  , this will check for hardware compatibilities.
     If some incompatibility was found at this point, unfortunately you cannot continue.
Step 8:
     Execute the command:                 
    vmscript /hwGenerateP2V /hwInfoFile:<GuestMachine>.xml /name:<VirtualMachineName> /vmConfigPath:<Your VSMT Directory>\vmconfig
   /virtualDiskPath:d:\vmdisk /hwDestVS:<YourVSMcahine> /virtualDiskDynamic /vmMemory:256
Step 9:
    At this point all scripts was generated and we can start the migration process. You need check if your guest machine have support for PXE boot on the network card, if not, you can generate one RIS disk to try the boot.
    On VSMT server, start the command:
    C:\<VMST Directory>\p2v\<GuestMachine>\<GuestMachine>_Capture.cmd 
    Reboot your guest machine using PXE.
    When ADS finish the capture process, the server will shutdown guest machine.

Step 10:
    This step will create configuration file in Virtual Server 2005 machine.
    C:\<VSMT Directory>\p2v\<GuestMachinet>\<GuestMachine>_CreateVM.cmd
Step 11:
    This step will power on the virtual machine, connect to ADS and deploy the image created in step 9.
    C:\<VSMT Directory>\p2v\<GuestMachine>\<GuestMachine>_DeployVM.cmd
    After this step the migration is finished, you will have your “real machine” virtualized.
If some errors occur, is recommended restart the migration process using the command:
    C:\<VSMT Directory>\p2v\<GuestMachine>\<GuestMachine>_cleanupVM.cmd , run this command and back to step 9.

Some things to also keep in mind!

Downloads ADS 1.1 with VSMT

Virtual Server

ADS only supports 2003 Enterprise Edition, and it’s quite a bit easier to install Virtual Server on the same machine. Configure a static IP before installing ADS! for PXE boot.

Supported Guest Operating Systems are:

Windows NT 4.0 Server SP6a, Standard & Enterprise Editions, Windows 2000 Server SP 4, Windows Server 2003, Standard  & Enterprise Edition

Installing Virtual Machine Additions

If your using Virtual Server 2005, or Virtual PC, you’ll want to install your virtual machine additions for better performance.Once you’re logged in and you have the command prompt up, just enter d: then press enter, cd\windows enter, then setup.exeYou will not be presented with the Virtual Machines Additions GUI Installation wizard, install like you normally would, and reboot!

Installing AdditionsVirtual Machine Additions Installation