Server 2008 R2 in a VM is an awful experience
- Ok I'm honestly wasting a lot of time just trying to get 1 2008 R2 full 64bit installed so I can setup the management gateway and try out the AD PowerShell cmdlets.
My Physical system is running Server 2008 R2 with Hyper-V
I have 2003 and 2008 SP2 servers installed no problem
Server 2008 R2 will not install for anything. I had an issue where my ISO is bad? Make no sense considering it was the same ISO i burned to DVD to do my install of server 2008 on my physical server. So after downloading it from technet again this time the install went further. Now when it get to the point of extract files it fails at 7% blue screen.
The same VM used the 2008 SP2 ISO and its almost done installing now, why is R2 in a VM such a pain? Maybe its my R2 as the Hyper-V host.... honestly its been acting odd since the install. I'm thinking of just redoing it and running with Server 2008 SP2 on my physical system rather than R2 nightmare I'm having Physical and Virtual.- 已變更類型Vincent HuMSFT, 版主Friday, 27 November, 2009 6:35
解答
- Ok I have to stand corrected, it was more of a hardware issue that wasn't easily apparent at first. After finally getting some reset I sat down to narrow down what the issue was.
Trust me having a bad ISO from technet is very odd considering it does the validation check after the download.
Anyways after runing a few different memory testing programs I narrowed that down to be the cause. I spend a bit more time working on getting those fixed, now that the memory apps are running without causing any errors I started from scratch again.
2008 R2 installed on the physical server finally without an issue. Before fixing the ram it was having many issues installed
All updates and patches / drivers installed without blue screening or rebooting!
Got Hyper-V installed and build two VM's. 1 SP2 and 1 R2 2008. Both this time installed without any issues and or rebooting the server.
**Sorry to blame the OS, but guess when your frustrated tends to be the first thing**
Either way a bit of troubleshooting and narrowing down the dump files, etc it was a memory issue.
Everything is working great now as I thought it should had from day one.- 已標示為解答VAs Hachi Roku Monday, 30 November, 2009 9:47
所有回覆
- I've also had the same problem. Tried to install with the same ISO as on another host, where it worked without a hitch, and it stopped right after "Start installation" saying "A required CD/DVD drive device driver is missing...". I verified the ISO with fciv with both MD5 and SHA1. Then I finally downloaded a new ISO and it worked.
Hi,
Have you checked the hash of the ISO file? How did you install the VM, from the physical DVD or mount an ISO file? I have many Windows Server 2008 R2 VMs installed on my Windows Server 2008 R2 Hyper-V host machine and never encounter this issue, I recommend that you download the ISO again, check the hash of the file after the download. By the way, if possible, please use the same ISO/DVD to create a new VM on other computer to check whether get the same issue.
Vincent Hu
- Hi,
Like Vincent, my host machine and my virtual machines are installed both in Windows Server 2008 R2.
I have never encountered this problem ... It's strange !
Download again the ISO by clicking on this link :
http://www.microsoft.com/windowsserver2008/en/us/trial-software.aspx
Tell us if the problem starts again ...
Good luck !
David Lachari · Hi,
Have you tried the suggestion? I want to see if the information provided was helpful. Your feedback is very useful for the further research. Please feel free to let me know if you have addition questions.
Best regards,
Vincent Hu
I'd suggest the ISO, as Vincent did. I've built many Windows Server 2008 R2 VMs and haven't had this problem.
- Ok I have to stand corrected, it was more of a hardware issue that wasn't easily apparent at first. After finally getting some reset I sat down to narrow down what the issue was.
Trust me having a bad ISO from technet is very odd considering it does the validation check after the download.
Anyways after runing a few different memory testing programs I narrowed that down to be the cause. I spend a bit more time working on getting those fixed, now that the memory apps are running without causing any errors I started from scratch again.
2008 R2 installed on the physical server finally without an issue. Before fixing the ram it was having many issues installed
All updates and patches / drivers installed without blue screening or rebooting!
Got Hyper-V installed and build two VM's. 1 SP2 and 1 R2 2008. Both this time installed without any issues and or rebooting the server.
**Sorry to blame the OS, but guess when your frustrated tends to be the first thing**
Either way a bit of troubleshooting and narrowing down the dump files, etc it was a memory issue.
Everything is working great now as I thought it should had from day one.- 已標示為解答VAs Hachi Roku Monday, 30 November, 2009 9:47
Hi,
Glad to hear that you have resolved the issue.
Most of time we will blame the OS if the system is not stable or something else, because most of us believe that the hardware is stable enough, so it’s understandable, however, you will find hardware is the culprit usually.
Vincent Hu
