Windows Server 2003 Std. change Uniprocessor to Multiprocessor
Hello everybody,
we have a problem with a virtual Maschine (Hyper-V) Windows Server 2003 Standard.
It is installed as a VM in Hyper-V and has only one processor configured in the Hyper-V VM Configuration. Now we wand to add 3 more processors to have the max. supported processors running within the Windows Server 2003 Standard.
What we did so far:
1. Just added more processores in Hyper-V config an restart Server:
-> Server did not boot anymore.
2. Changed the APCI-Driver in Device-Management of the Windows Server 2008 from Uniprocessor to APCI-Multiprocessor, shutdown the Server, added added more processores in Hyper-V config an restart Server:
-> Server did not boot anymore.
Is there anything else we have to take care?
We already spent so many time in trying and fail.
We never did this before and Google does not many informations about adding more processors to a already as uniprocessor running server.
I would be very thankful for any advices what to do.
Thanks in advance, Carsten
we have a problem with a virtual Maschine (Hyper-V) Windows Server 2003 Standard.
It is installed as a VM in Hyper-V and has only one processor configured in the Hyper-V VM Configuration. Now we wand to add 3 more processors to have the max. supported processors running within the Windows Server 2003 Standard.
What we did so far:
1. Just added more processores in Hyper-V config an restart Server:
-> Server did not boot anymore.
2. Changed the APCI-Driver in Device-Management of the Windows Server 2008 from Uniprocessor to APCI-Multiprocessor, shutdown the Server, added added more processores in Hyper-V config an restart Server:
-> Server did not boot anymore.
Is there anything else we have to take care?
We already spent so many time in trying and fail.
We never did this before and Google does not many informations about adding more processors to a already as uniprocessor running server.
I would be very thankful for any advices what to do.
Thanks in advance, Carsten
ASKER
Hi Drashiel,
thanks for your quick reply.
Is the first link not what we already tried?
Or do we have to do these settings in the boot.ini?
And link numer 2. If we would do the reapir install, would we have to add these more processors in Hyper-V config before the repair installation?
Best wishes, Carsten
thanks for your quick reply.
Is the first link not what we already tried?
Or do we have to do these settings in the boot.ini?
And link numer 2. If we would do the reapir install, would we have to add these more processors in Hyper-V config before the repair installation?
Best wishes, Carsten
On first case, changes are made on boot.ini.
On second, only add processors and reinstall. This works 100% for me on past.
On second, only add processors and reinstall. This works 100% for me on past.
Here is what you could do:
1. Reset the VM to one processor
2. Boot it, uninstall the Integration services, and shut it down
3. Add more virtual processors
4. Boot it again and re-install the integration services
I hope this will help
1. Reset the VM to one processor
2. Boot it, uninstall the Integration services, and shut it down
3. Add more virtual processors
4. Boot it again and re-install the integration services
I hope this will help
ASKER
Hi spaperov,
thanks for your reply.
What we did so far:
1. uninstalled the Integration services and shut down;
2. added more virtual processors (4);
3. rebooted the system;
The system boots up and we can loginto the system.
But the windows recognizes more processors and makes and update to ACPI-Multiprocessor driver and asks for a rebbot;
When we reboot the the start crashesafter some seconds of booting.
There must be something else to take care about.
Do you have any idea?
By the way: Drashiels second tip of reinstall did not work.
Thanks in advance, Carsten
thanks for your reply.
What we did so far:
1. uninstalled the Integration services and shut down;
2. added more virtual processors (4);
3. rebooted the system;
The system boots up and we can loginto the system.
But the windows recognizes more processors and makes and update to ACPI-Multiprocessor driver and asks for a rebbot;
When we reboot the the start crashesafter some seconds of booting.
There must be something else to take care about.
Do you have any idea?
By the way: Drashiels second tip of reinstall did not work.
Thanks in advance, Carsten
There in no a special procedure to follow to add additional processors. There is even no need of removing the integration services. Normally, when we add a second virtual processor, Windows updates it driver, reboots, and works without crashes….
What is the stop error (BSOD) that you receive?
Which release of Windows 2008 you have; did install the service packs?
What is the stop error (BSOD) that you receive?
Which release of Windows 2008 you have; did install the service packs?
ASKER
Hi spaperov,
its not a 2008, its a 2003.
And there is no BSOD with a stop error´.
It just stops loading WIndows, but the processor CPU usage stays at 12%. Thats it.
And uninstalling the intergarion services was your idea and helped that after adding more processors the server reboots at the first reboot. Only when Windows installs the Multiprocessor driver, then Windows does not start any more.
Any more ideas?
Thanks in advance, CArsten
its not a 2008, its a 2003.
And there is no BSOD with a stop error´.
It just stops loading WIndows, but the processor CPU usage stays at 12%. Thats it.
And uninstalling the intergarion services was your idea and helped that after adding more processors the server reboots at the first reboot. Only when Windows installs the Multiprocessor driver, then Windows does not start any more.
Any more ideas?
Thanks in advance, CArsten
Yes, I know that I suggested uninstalling the integration services because sometimes it helps.
Your Hyper-V server: is it Windows 2008, Windows 2008 R2 or the free Microsoft Hyper-V server? May be there are some updates for the host OS that could fix the problem.
Did you try to run the VM in Safe Mode?
Do you have other virtual machines on the host? Are they affected by the same problem?
Your Hyper-V server: is it Windows 2008, Windows 2008 R2 or the free Microsoft Hyper-V server? May be there are some updates for the host OS that could fix the problem.
Did you try to run the VM in Safe Mode?
Do you have other virtual machines on the host? Are they affected by the same problem?
ASKER
Hi spaperov,
the Host-Server is a Microsoft Windows Server 2008 R2 Enterprise x64.
16GB RAM, 2x Intel XEON Processors with 4 Cores.
The producitve VM of that Windows Termnal Server is running an Windows Server 2003 with 4GB RAM and 1 Processor.
We copied that VM to work in the background on that adding processors issue.
So yes, there is another VM running on that Server which does not have these problems.
After copy the producitive VM and not chaning the processors number the VM starts as well with no problems. Only after Windows is installing the Multiprocessor driver the start fails.
Maybe i should combine;
- uninstalling the integration services which helped in the first step;
- reboot server after adding more processors;
- install Multiprocessor driver;
- and then make repair install.
I have no other idea.
What do you think?
Best wishes, Carsten
the Host-Server is a Microsoft Windows Server 2008 R2 Enterprise x64.
16GB RAM, 2x Intel XEON Processors with 4 Cores.
The producitve VM of that Windows Termnal Server is running an Windows Server 2003 with 4GB RAM and 1 Processor.
We copied that VM to work in the background on that adding processors issue.
So yes, there is another VM running on that Server which does not have these problems.
After copy the producitive VM and not chaning the processors number the VM starts as well with no problems. Only after Windows is installing the Multiprocessor driver the start fails.
Maybe i should combine;
- uninstalling the integration services which helped in the first step;
- reboot server after adding more processors;
- install Multiprocessor driver;
- and then make repair install.
I have no other idea.
What do you think?
Best wishes, Carsten
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If doesn´t work, maybe a repair reinstall will fix it: http://support.microsoft.com/kb/816579/en-us