VMware vSphere

 View Only

  • 1.  Windows Server 2008 R2 blue screen after import into vSphere.

    Posted May 05, 2010 12:31 AM

    Hi Fellow VM users,

    I'm reaching out to see if you have experienced anything similar. One of our engineers has created a Windows Server 2008 R2 box using workstation 7, and he asked me to import the VM into our ESX environment for additional testing. After using VM converter to import the VM, which was successful, it powers on and blue screens. Are there particular settings for the VM I should be checking?

    Thanks,

    Phil



  • 2.  RE: Windows Server 2008 R2 blue screen after import into vSphere.

    Posted May 05, 2010 05:32 AM

    Did they create VM as ESX compatible?


    ---

    MCSA, MCTS Hyper-V, VCP 3/4, VMware vExpert '2009

    http://blog.vadmin.ru



  • 3.  RE: Windows Server 2008 R2 blue screen after import into vSphere.

    Posted May 05, 2010 08:06 AM

    Most likely it is an issue with the assigned virtual disk controller.

    In the VM's settings do the following:

    - Make sure the OS is set to Windows Server 2008 R2

    - Set the HDD controller type to "LSI Logic SAS"

    I'm not 100% sure about the controller type for a converted machine. It could also be set to LSI Logic SAS and needs to be set to SCSI. This depends on how the conversion was done and which OS was set for the source VM.

    André



  • 4.  RE: Windows Server 2008 R2 blue screen after import into vSphere.

    Posted May 24, 2010 10:32 PM

    i have a very similar issue. My Conversion ovf sets the LSI controller to parallel, but the OS will Blue Screen upon boot. Changing it to LSI SAS fixes the issue. Question, what is the virtual driver name i can specify in the OVF file to have it recognize this upon deployment rather than relying on the user to go back and delete and re-add the correct controller. I see driver names for buslogic and lsilogic. I tried lsisas and lsisas1068 but neither of those work for importing the OVF.

    Regards,

    Nelson