I have been testing in-place upgrades of three domain controllers (all virtual machines) with a colleague from server 2003 to server 2008. Two of the domain controllers reside on my mac which is using the latest version of parallels (build 5608) and the third resides on my colleague's windows desktop in which he is using Microsoft's virtual pc. Getting to the issue... When I start the upgrade process in Parallels from server 2003 to server 2008, I receive the following error provided in the screen shot below. In my troubleshooting of the issue, I have set the machine type to server 2003, vista, and server 2008 (experimental) and all leave me with the same error message regarding ACPI. I have also set the machine type to windows xp and used the "Prepare Windows Vista Upgrade..." option under the action menu. This provides an error message stating that there is no OS on the virtual machine and that the upgrade cannot be performed. In searching through the forum, I found a few threads on the ACPI issue but none that suited my needs. Any help would be greatly appreciated in troubleshooting this problem so I can continue my 2003 to 2008 transition testing.
As you can read in the sentence right below the screen shot, I have already done what you suggested and still received the error. Do you have any other ideas?
Sometimes it reverts to Windows XP(or so without CPU), open pvs file and check that OS type is set either to 137 or to 138 Also try to boot first in Windows 2003, let detect hardware finishes , the try to upgrade
I have tried manually setting the machine type by editing the pvs file like you had suggested and I still receive the same message regarding ACPI. I have attempted the upgrade using both the 137 and 138 machine type. I noticed that I neglected to share some possibly useful information previously... When I attempt to perform the upgrade, I am not booting the virtual machine from the installation CD/Image. I am booting into Server 2003 first, logging into the machine, then attempting to perform the upgrade from within Windows.
Thank you for provided information, I will try to reproduce situation, and will contact you back in a day or two
Ok, here we go. 1. I reproduced situation you described. 2. Workaround - Create new VM, with Windows 2008 selected as OS, - add hdd, from Windows 2003 - Windows repair, using CD with SP as installed in OS - Upgrade to Windows 2008
I will be able to try this solution within the next few days, but out of curiosity, what is Windows repair going to do? I also assume you mean to use the Windows repair utility from the Server 2003 installation cd since Server 2008 installation is the next step.
I also assume you mean to use the Windows repair utility from the Server 2003 installation cd since Server 2008 installation is the next step. Yes, in current situation, it will replace hal
