IT 专业人士的资源 >
论坛主页
>
Hyper-V
>
Windows Server 2000 does not start after Integration components instalation
Windows Server 2000 does not start after Integration components instalation
- Hi,
I've tried to install integration components (Hyper-V RTM) in Windows 2000 Server SP4 guest. Installation was successful but after restart the server hangs on Preparing Network Connection screen.
Than I can boot into safe mode only. I've tried to remove Network adapter, install Legacy adapter but nothing helped.
What can be wrong? Can somebody help?
Thanks in advance.
Peter
答案
Okay, that's helpful. This is a migration from Virtual Server, so I'm wondering if this is a HAL problem. Are you familiar with sysprep? If you run sysprep and it detects the new HAL needed by Hyper-V, maybe your problems would go away. Also, I would expect that if you used SCVMM to do the P2V, things would probably be okay.
- 已标记为答案Chang Yin 2008年7月15日 1:58
- Same situation here - any 2000 Server VM from VS2005 (NON SP1, just FYI since SP1 sucks on clusters (ie, doesnt work!)) experiences the hang on Plug and Play and basically a useless OS until Integration Services are removed. The VM's were migrated from VS2005 manually - removed VS Components from add/remove, shutdown clean, copied VHD, new Virtual Machine in HyperV using existing VHD file. These are all 2000 SP4 machines that were migrated to VS2005 via PlateSpin P2V tool originally, in case that helps in Microsoft's troubleshooting.
I've worked around this in an quite annoying way :)
- Uninstall Integration Tools if already installed
- Shutdown VM
- In the VM settings remove the Network Card
- In the VM settings, click Add Hardware on the top and add a Lecacy Network Card and set it up like usual
- Start the VM - Windows will auto install the drivers for the legacy nic
- Install Integration Tools as usual for mouse and video drivers!
- Reboot
- Rejoice!
If someone has a better way around this issue, I'll listen but this is working fine so far for me :)
Eric
全部回复
- Strange, as this isn't a known issue (I've tested this configuration). Do other VM's have the same behavior?
This posting is provided "AS IS" with no warranties, and confers no rights. - I have only 1 Windows 2000 VM. Other VM's (windows 2003, windows 2008) works OK.
I had to uninstall integration components from Windows 2000 VM, than everything works.
I made a test VM with copy of that Windows 2000 vhd. The logon dialog shows after aprox. 10 minutes, than I can logon, but there are many errors in the event log.
Immediately after eventlog starts:
Event ID: 7001
The DNS Client service depends on the TCP/IP Protocol Driver service which failed to start because of the following error:
A device attached to the system is not functioning.
Peter - I have tried to install clean Windows 2000 Server SP4 and it works OK with integration components Hyper-V RTM. Unfortunately the old W2k VM which was originaly created in Virtual Server 2005 doesn't work. So I have to transfer data and settings to this new VM.
Peter Okay, that's helpful. This is a migration from Virtual Server, so I'm wondering if this is a HAL problem. Are you familiar with sysprep? If you run sysprep and it detects the new HAL needed by Hyper-V, maybe your problems would go away. Also, I would expect that if you used SCVMM to do the P2V, things would probably be okay.
- 已标记为答案Chang Yin 2008年7月15日 1:58
I complete several notices:
- originaly the W2k VM was created with Windows Server 2005
- than it was migrated to Hyper-V RC0 and also used with RC1 - without integration components of course
- after upgrade Hyper-V guest to RTM I've installed integration components - during this installation the HAL was changed
and than begun the problems ...
Regards
Peter- I have the same or a similar issue with 2 windows 2000sp4 server guests. They are Acronis images of the physical machines converted to vhd's with Acronis. They boot fine with Hyper-V, but once I install the Integration tools they boot but almost no services start. After looking through the log It seems to be related to the plug and play service(it stalls,says starting), but I'm not sure. If I unistall the intergration services and reboot the VM's boot up normally. Any Ideas?
- Same situation here - any 2000 Server VM from VS2005 (NON SP1, just FYI since SP1 sucks on clusters (ie, doesnt work!)) experiences the hang on Plug and Play and basically a useless OS until Integration Services are removed. The VM's were migrated from VS2005 manually - removed VS Components from add/remove, shutdown clean, copied VHD, new Virtual Machine in HyperV using existing VHD file. These are all 2000 SP4 machines that were migrated to VS2005 via PlateSpin P2V tool originally, in case that helps in Microsoft's troubleshooting.
I've worked around this in an quite annoying way :)
- Uninstall Integration Tools if already installed
- Shutdown VM
- In the VM settings remove the Network Card
- In the VM settings, click Add Hardware on the top and add a Lecacy Network Card and set it up like usual
- Start the VM - Windows will auto install the drivers for the legacy nic
- Install Integration Tools as usual for mouse and video drivers!
- Reboot
- Rejoice!
If someone has a better way around this issue, I'll listen but this is working fine so far for me :)
Eric - Thanks for the response. However, this work around does not work for me. I have one of my 2000 VM's working, unfortunately I was not systematic enough in my changes to determine what made it work...and it's working with the standard network driver not the legacy. I'll continue to play with it as time permits...
Anybody have more insight?
Thanks. - Hi all. I've got the same problem as ScottCo. I also converted an physical (HP ML370G1) W2k-SP4-Server with Acronis into an vhd.file.
Without the Intigration Services all is running fine. But after IS installation the server comes up very slowly and many system and network services are'nt running.
In my case the main service which causes the problems because of the following service startup dependencies seems to be the workstation service.
It also doesnt let it start manually.
The discribed workauround doesnt work for me to. The guest OS runs also with the legacy nic into the same problem.
The only thing i'am not shure about is how to seperatly install Integration Services only for Mouse und Video as discribed?
The IS Components which can be chosen in the Hyper-V settings doesnt make any difference for Mouse/Video integration or to the discribed problem.
Is there anybody who solved this problem in the meantime? ScottCo maybe?
Thanks! - I haven't found the answer, haven't worked on the problem. I find it interesting that we both converted Compaq/HP machines, mine were both Compaq ML370G2's. Must be one of the compaq drivers that remain.
- I too am having an issue with a 2000 SP4 installation that was originally installed on a compaq. The PNP service hangs after installing integration services.
Initially I was experiencing the 0x7b boot problems, but ERD commander and some clever registry exporting/importing from a working installation solved the driver issue on boot.
I have done a repair over this working install, and still experience the same problems.
Any help or suggestions would be appreciated!
Jason - Hi all,
the problem has been occured again. I've found this workaround which worked for me:
http://www.vistax64.com/virtual-server/175367-hyper-v-integration-services-problem-windows-2000-server.html
It's neccessary to DISABLE "Windows Management Instrumentation Driver Extensions" service.
Regards Peter - I too have this problem. I've converted 8 Windows 2000 SP4 Compaq Servers, using Acronis, into .vhd for 2008 Hyper-V. I have run into various problematic services that don't want to start due to timeouts, etc.
I have discovered that Disabling the "Windows Management Instrumentation Driver Extensions" resolves the problem.
OR, removal of the Integration Services...
I wish there was a better fix!
Thanks,
Duane
