dekroon
asked on
disk.sys BSOD on Windows Server 2003 Hyper-V
Environment
Host: Windows Server 2012 R2 Datacenter
VM OS: Windows Server 2003 R2 Enterprise 64-bit
I recently converted a VMWare VM to Hyper-V and was using the legacy NIC to get everything up and running and install Hyper-V Integration Services.
I had a few occasional blue screens on the VM but after removing VMWare integration services and some other unnecessary services/applications it seemed my VM was stable. I finally got to the point where I could replace the legacy NIC with the synthetic Hyper-V NIC. It seems that after that the VM started to blue screen frequently. It is stable in safe mode. I have just reverted to the legacy NIC to verify it is stable.
Notes about the virtual NIC:
- I tried both with SR-IOV and without - bsod with both.
- The hardware NIC is an Intel Gigabit ET Quad Port. I've tried two different ports.
Any help is much appreciated.
Thx!
Joe
Host: Windows Server 2012 R2 Datacenter
VM OS: Windows Server 2003 R2 Enterprise 64-bit
I recently converted a VMWare VM to Hyper-V and was using the legacy NIC to get everything up and running and install Hyper-V Integration Services.
I had a few occasional blue screens on the VM but after removing VMWare integration services and some other unnecessary services/applications it seemed my VM was stable. I finally got to the point where I could replace the legacy NIC with the synthetic Hyper-V NIC. It seems that after that the VM started to blue screen frequently. It is stable in safe mode. I have just reverted to the legacy NIC to verify it is stable.
Notes about the virtual NIC:
- I tried both with SR-IOV and without - bsod with both.
- The hardware NIC is an Intel Gigabit ET Quad Port. I've tried two different ports.
Any help is much appreciated.
Thx!
Joe
ASKER
yes - all devices specific to vmware were removed (it was a VM, not a physical server)
yes - i've been changing virtual NICs by removing and restarting. I verified the system is stable in safe mode and also stable in normal mode with the legacy Hyper-V NIC but not with the synthetic Hyper-V NIC.
I use Symantec System State Restore with "Restore to Different Hardware" for all my VM conversions. Works very consistently with many different guest OS versions.
Latest thing I'm trying is to disable NIC offloading, as I've read about network connectivity issues that can be remedied by doing that. Don't know if it addresses stability, though. . .
yes - i've been changing virtual NICs by removing and restarting. I verified the system is stable in safe mode and also stable in normal mode with the legacy Hyper-V NIC but not with the synthetic Hyper-V NIC.
I use Symantec System State Restore with "Restore to Different Hardware" for all my VM conversions. Works very consistently with many different guest OS versions.
Latest thing I'm trying is to disable NIC offloading, as I've read about network connectivity issues that can be remedied by doing that. Don't know if it addresses stability, though. . .
ASKER
I disabled NIC offloading as per http://support.microsoft.com/default.aspx?scid=kb;EN-US;904946
Time will tell, but since I did this some 4 hours ago I've experienced no BSOD.
Time will tell, but since I did this some 4 hours ago I've experienced no BSOD.
Good for you. Hope it lasts and works well.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Self-discovered solution worked.
Also remove the legacy network adapter driver, restart, then try to add the other one.
Btw what toold did you use to convert P2V?