Sign in
Microsoft.com
 
Windows Server TechCenter
 
 
 
Windows Server TechCenter > Windows Server Forums > Hyper-V > Hyper-V on 2008-R2 - Host Blue Screens
Ask a questionAsk a question
Search Forums:
 

AnswerHyper-V on 2008-R2 - Host Blue Screens

  • Thursday, October 22, 2009 9:04 PMUnder Dog Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    A very peculiar issue I am having.  I have a Dell PowerEdge 1950 with 32 GB RAM running 2008 R2 Standard Edition with all the latest updates as of 10.22.09.  I have the Hyper-V role installed and working.  I can create guest machines with no issues and I can install Integration components from a newly created guest with no issues.  However - when I copy a VHD from a different host server OR when I delete the guest on this server and recreate it using the same VHD the server will Blue Screen during the boot up of that guest server ONLY after I install Integration Services on that guest. 

    I have read other posts about long names, etc and I have very short names with short paths G:\VHDISKS\XP.vhd for the disk and G:\VCONFIGS\XP for the configuation data.  I also have the latest BIOS for this 1950 server and the latest drivers.  This is a fresh install of the OS.  I have NOT tried re-installing the OS but may try that next.

    To be clear - the HOST is getting the BSOD, not the Guest.  It Blue Screens with a Stop Error of: Stop 0x0000001e...

    I have the Guest set to NOT automatically start when the host starts so that the Host won't continue to BSOD once the guest starts again.

    Any ideas?
     

Answers

  • Monday, October 26, 2009 12:23 PMUnder Dog Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    An update:
    I setup another Hyper-V system on 2008 R2 and the previously mentioned guests run fine on this other system with the same configuration setup and settings.  Thus - without an answer I am leaning towards reloading that box.  One thing to mention is - that host is also setup as a DC / DNS / DHCP server.

    Thanks for any further input.

    -Dave
    -David Miller
     

All Replies

  • Thursday, October 22, 2009 9:59 PMBrianEhMVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Do any of these VMs have differencing disks?

    Are you using Export from Hyper-V v1 and then Import to Hyper-V R2?

    Or is this specific to the host and not necessarily a v1 to R2 issue?
    Brian Ehlert (hopefully you have found this useful)
     
  • Friday, October 23, 2009 8:09 AMVincent HuMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Hi,

     

    I’d like to confirm the type of your drive G:\, is it on a local disk or mapped from a network share. I have seen a post in this forum, the guy encountered the BSOD issue on host machine when he install updates inside the VM(he stored VHDs in a network share instead of local disk).

     

    By the way, according to the description, we find it seems to be system crash issue and we need to analyze the crash dump file to narrow down the root cause of the issue. Unfortunately, it is not effective for us to debug the crash dump file here in the forum. Therefore, I would like to suggest that you contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request.

     

    To obtain the phone numbers for specific technology request please take a look at the web site listed below:

     

    http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607

     

    Hope the issue will be resolved soon.

     

     

    Best Regards,

    Vincent Hu

     

     
  • Friday, October 23, 2009 1:03 PMUnder Dog Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Hi Brian - thanks for your response.  Here are my answers:

    No - the disks I have been using are dynamic disks. 

    I am not using export / import.

    1 of the VHD's that I am experiencing the BSOD with was created on the very machine that receives the BSOD.  In this case I created the machine from scratch - installed integration components and it worked fine.  Then I deleted it and recreated it using the same VHD.  Upon boot of the guest - the host BSOD's.

    The other VHD's I tried were created on Virtual Server 2005 R2.  In those cases - I uninstalled the 2005 components (VM Additions) from the virtual guest and then shut it down.  Copied it over to the 2008 R2 server and booted it up without incident.  The new HAL installed fine but then when the actual Integration Components installed - the host BSOD's.

    Thanks for your help!

     
  • Friday, October 23, 2009 1:16 PMUnder Dog Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Hi Vincent.

    The G drive is an iSCSI drive attached to my MD3000i array.

    I am hoping to dig a bit further before having to spend money on the call to MS.

    Thanks,

    Dave
     
  • Monday, October 26, 2009 12:23 PMUnder Dog Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    An update:
    I setup another Hyper-V system on 2008 R2 and the previously mentioned guests run fine on this other system with the same configuration setup and settings.  Thus - without an answer I am leaning towards reloading that box.  One thing to mention is - that host is also setup as a DC / DNS / DHCP server.

    Thanks for any further input.

    -Dave
    -David Miller