locked
Error installing server 2012R2 on virtual machine RRS feed

  • Question

  • Using Hyper-V on server 2012R2 Data Center on Dell PowerEdge 2970 created a virtual machine.  Checked the box to install OS.  Pointed the OS install to the ISO file on the C drive on the host for the virtual machine.  After the virtual machine was created and showed up in hyper-v dashboard  pressed "start" and then "connect".

    In the windows boot manager screen got error 0xc0000017 "there isn't enough memory available to create a ramdisk device"

    read about a similar problem with 8.1 installs - ran windows updates and checked device manager for driver updates - no better.

    hmm....

    Friday, March 27, 2015 2:11 PM

Answers

All replies

  • Your VM must at least have 512 Mo of RAM.

    Regards, Samir Farhat Infrastructure and Virtualization Consultant || Virtualization, Cloud, Azure ? Follow and Ask here https://buildwindows.wordpress.com


    Friday, March 27, 2015 2:32 PM
  • Your VM must at least have 512 Mo of RAM.

    Regards, Samir Farhat Infrastructure and Virtualization Consultant || Virtualization, Cloud, Azure ? Follow and Ask here https://buildwindows.wordpress.com


    It recommended to have at least 1GB of RAM, otherwise you can encounter further issues.

    https://workinghardinit.wordpress.com/2014/09/05/fixing-windows-cannot-find-the-microsoft-software-license-terms-make-sure-the-installation-sources-are-valid-and-restart-the-installation-or-windows-installation-encountered-an-un/


    Regards, Samir Farhat Infrastructure and Virtualization Consultant || Virtualization, Cloud, Azure ? Follow and Ask here https://buildwindows.wordpress.com

    • Marked as answer by ADeanS Friday, March 27, 2015 4:19 PM
    Friday, March 27, 2015 2:38 PM
  • Thanks for the replies.  I was under the impression that the check box that allows the ram to be dynamically assigned by the OS would accommodate the changing needs.  However that must not be the case during installation.

    I changed the RAM allocation to 4Gb and left  the dynamic allocation on, and the installation worked.  Now when the machine is running I see memory allocations on the status window of between 600 Mb and 1 Gb.

    Friday, March 27, 2015 4:19 PM
  • You can use dynamic memory, but the important value is the "startup RAM".

    If your start-up RAM is too low, the installation may fails


    Regards, Samir Farhat Infrastructure and Virtualization Consultant || Virtualization, Cloud, Azure ? Follow and Ask here https://buildwindows.wordpress.com

    Friday, March 27, 2015 4:21 PM