Hyper-V on the Dell Optiplex

Posted on 15 CommentsPosted in hyper-v, virtual server, virtualisation, windows server

With the correct BIOS settings enabled on a E8500 processor (see http://processorfinder.intel.com/ for the processors that support EM64T, Virtualisation and Execute Disable which is needed for Hyper-V to work), and with them and the Trusted Execution property set to On in the BIOS I got the following errors with Hyper-V RC1 on Windows 2008 Enterprise Server RTM (running Server Core):

  • Hyper-V launch failed; Either VMX not present or not enabled in BIOS.
  • Hyper-V launch failed; at least one of the processors in the system does not appear to provide a virtualization platform supported by Hyper-V.

Fixed this by rebooting and pressing F2 to enter the BIOS and disabling the following settings

  • Security > Execute Disable (set to Off)
  • Performance > Virtualization (set to Off)
  • Performance > VT for Direct I/O Access (set to Off)
  • Performance > Trusted Execution (set to Off)

Press Esc and save settings. When the server reboots do a hard power off. Power on, and then in the BIOS again ensure that the following is set:

  • Security > Execute Disable (set to On)
  • Performance > Virtualization (set to On)
  • Performance > VT for Direct I/O Access (set to On)
  • Performance > Trusted Execution (set to Off)

Press Esc and save settings. Hard power off again once the server reboots. Turn power on and let computer boot normally.

At this point I got an Hyper-V error in that the entries in the event log above did not appear anymore, but were replaced by an error indicating that Hyper-V was not installed.

So I removed Hyper-V by running:

  • ocsetup Microsoft-Hyper-V /uninstall

and reboot.

Reinstall Hyper-V by downloading the latest build and install it using:

  • wusa <filename_of_download.msu>

or if you have the latest build already installed, then reinstall using:

  • ocsetup Microsoft-Hyper-V

ERROR_REPLICA_SYNC_FAILED_THE TARGET PRINCIPAL NAME IS INCORRECT

Posted on Leave a commentPosted in 2003, 2007, active directory, error, exchange, kerberos, virtual pc, virtual server

This rather imposing message is found if you try to force replication between to Active Directory Domain Controllers when one of the controllers machine account password is out of sync with the password as stored on the other domain controller.

I have seen this a number of times on Virtual PC or Virtual Server Active Directory deployments with more than one DC in the virtual environment.

So, how do you fix it:

  1. On the DC that is broken (the one that when using replmon reports the error above) set the Kerberos Key Distribution Center Service to manual and stop the service.
  2. From a command prompt on the broken DC enter the following:
    netdom resetpwd /s:name_of_working_DC /ud:domain\user /pd:*
    where domain\user is an administrator of the domain in the domain_name\user_name format. You will be prompted to enter your password.
  3. Upon pressing Enter, if the command fails then restart the broken DC and repeat the above command (this restart clears the Kerberos ticket cache and so clears the broken credential attempts that it has stored).
  4. Upon successful completion of the command in step 2 restart the broken DC. You must do this even if done already in step 3.
  5. Check that replication is working, and if so restart the Kerberos Key Distribution Center Service and set the service back to automatic.

This is a summary of Microsoft Knowledgebase Article 325850, with some more specific detail mentioned.

Virtual PC’s Crashing With IntelPPM.sys and Processor.sys

Posted on Leave a commentPosted in virtual server

Today I booted a virtual machine that was provided for me by a client so that I could prep a training course, but I could not log into the virtual machine because it blue-screened with a driver called intelppm.sys failing (and supposedly processr.sys can cause the same problem, but I have not experienced that one yet). Note that the virtual machine might just reboot rather than blue-screen because that is what it is configured to do.

The blue-screen is due to the virtual machine running on an AMD K8 or Centrino platform and the above device driver attempting a unsupported command that was supported on the platform that the virtual machine was originally created under. You can disable these drivers without issue in the virtual machine – just you cannot login to disable them!

So you need to use Safe Mode. Press the F8 key repeatedly as the virtual machine boots and then choose Safe Mode from the on-screen menu. Once you have logged in run these two commands from a command prompt (note that where the spaces are is important):

sc config processor start= disabled
sc config intelppm start= disabled

You should get a SUCCESS message returned. Once you do you can shutdown the virtual machine (and commit changes if you are have undo disks enabled) and then start the machine up normally.

This problem has been fixed under Virtual Server 2005 R2, but is still an issue with Virtual PC 2004 and Virtual Server 2005.

VSWebApp and 404

Posted on Leave a commentPosted in virtual server, virtualisation

When I have started too many virtual machines in Microsoft Virtual Server 2005 I find that the administration application (http://server/virtualserver/VSWebApp.exe) stops working.

To get it to restart, change the authentication settings on the IIS virtual directory to something other than what you have already (but not anonomyous). For example if it is Basic and Integrated set it to Basic only.

Open the admin page again and you will be prompted for authentication and it will now work.

Mouse Pointer Delays in Virtual Server

Posted on Leave a commentPosted in virtual pc, virtual server, virtualisation

I am running Microsoft Virtual Server 2005 and every 10 seconds or so I get a pause in the mouse movement on the screen – very annoying.

Examining the performance logs of the server I see that the Virtual Server service “vsssrv” goes to 0% CPU utilisation when this happens – so something is interupting the service.

Stopping my anti-virus software solves the problem, but introduces another problem in that my computer is now unprotected, so I will post back here later my results on not have the AV software (McAfee Managed Anti-Virus) from scanning the filesystem where my virtual machines are installed and the vsssvc.exe application (“C:\Program Files\Microsoft Virtual Server” folder).