Setup RAM Disk on Hyper-V Hypervisor or inside VM?

Initiator (iSCSI, FCoE, AoE, iSER and NVMe over Fabrics), iSCSI accelerator and RAM disk

Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)

Post Reply
Posts: 1
Joined: Tue Jul 29, 2014 7:54 pm

Tue Jul 29, 2014 8:04 pm

For best practices, flexibility, reliability and performance, should RAM Disk(s) be created on the Windows Server 2012 R2 Hypervisor (the physical machine's operating system) or inside each individual Virtual Machine?

If on the Hypervisor, after a reboot of the physical machine, will the RAM Disks be created early enough to be recognized by the restarting VM's?

Is RAMDisk compatible (supported/will it install) with WS2012 R2 Core?

It appears RAMDisk hasn't been updated since 2012, is it still fully compatible and stable with WS2012 R2?
Is RAMDisk intended to be used in Production environments?

User avatar
anton (staff)
Site Admin
Posts: 4010
Joined: Fri Jun 18, 2004 12:03 am
Location: British Virgin Islands

Tue Jul 29, 2014 9:35 pm

For performance reasons RAM disk should be created inside hypervisor (parent partition) and not inside every VM (ballooning, paging out etc).

Yes, storage stacks starts before VMs are powered up so you'll get access to RAM disk from your VMs.

Yes, GUI-less setup is supported (it's just a driver you can control from the command line interface).

That's discontinued product. It does work but we don't support it and never supported for any production.
Anton Kolomyeytsev

Chief Technology Officer & Chief Architect, StarWind Software

Post Reply