If your virtual machine will not start, this may be due to over-allocated CPU resources. In other words, some virtual machines have been assigned more CPU resources than others. Since only those virtual machines that you have permissions to appear on the CPU Resource Allocation page, it is easy for someone to mistakenly over-allocate CPU resources to the virtual machines listed. This can prevent other virtual machines from turning on. The solution is to have a Virtual Server administrator open the CPU Resource Allocation page to verify the CPU allocation for all the virtual machines.

If your virtual machine will not start and you are using linked disks, verify that the physical linked disk is not being used. A virtual machine that uses a linked disk will not start if the linked physical disk is already in use.

When you attempt to start a guest operating system from a virtual disk, you might receive the following error message:

Stop 0x0000007B

In such cases, you have more than likely installed the virtual disk on the incorrect type of controller. You can correct the problem by reattaching the virtual disk to a different type of controller. For example, if the virtual disk is currently attached to a virtual IDE controller, attach it instead to a virtual SCSI controller.

You may also encounter problems with a virtual machine after renaming it. For example, if you rename a virtual machine through Windows Explorer, the name change will not appear on the Administration Web site. The solution to this is to use the Administration Web site, instead of Windows Explorer, to rename your virtual machines.

[tags]virtual server, r2[/tags]