I built a fresh install of PVE 1.4 and installed Server 2003 R2 as client. When I reboot in windows the PVE status goes to Stopped and the client will not restart on its own. I can restart from PVE and don't see any obvious errors. This may be only a newbie setting issue, but I can't find it.
2003 client reboot halts & needs restarted in PVE
- Thread starter pgervais
- Start date
Did you try to reboot your server from an RDP session? We often have problems rebooting Win2003 (all editions, 32bit) from an RDP session. MS is aware of this, see
http://support.microsoft.com/kb/930045
However the proposed hotfix does not help. The problem remains.
It does not seem to be related to PVE as this happens on our physical servers too. But with PVE I do not have to walk to the server room
http://support.microsoft.com/kb/930045
However the proposed hotfix does not help. The problem remains.
It does not seem to be related to PVE as this happens on our physical servers too. But with PVE I do not have to walk to the server room
No, this did not work. I already have all MS updates and remote shutdown works fine. When I applied the updates I was using the non-upgraded e1000 driver and it may have corrupted an update or something. Since this is a non-production system I will try another install.
The lockup is related to number of CPU core allowance. I am running an Intel i7 (1 socket, 8 virtual cores) and PVE sees it as 8 cores. To simulate my server environment I alloted 4 cores to the 2003 vm before I applied my MS updates. Durring the MS updates I started having the reboot problems.
For testing I built another 2003 client with only 1 core and applied the MS updates and everything worked fine. On the first vm with 4 cores I reduced it to 2 cores and now the reboot also works fine. To make sure I set it back to 4 cores and again have a reboot problem.
For fun I set the second VM to 4 cores and it reboots fine.
Not sure what this means, but it looks like if you are using the i7 CPU & PVE 1.4 then you should not add more than 2 cores until you have completed your MS updates. Hope this helps someone!
For testing I built another 2003 client with only 1 core and applied the MS updates and everything worked fine. On the first vm with 4 cores I reduced it to 2 cores and now the reboot also works fine. To make sure I set it back to 4 cores and again have a reboot problem.
For fun I set the second VM to 4 cores and it reboots fine.
Not sure what this means, but it looks like if you are using the i7 CPU & PVE 1.4 then you should not add more than 2 cores until you have completed your MS updates. Hope this helps someone!