As explained in previous tutorials, persistent memory (PMem) can be used in different ways:
To learn more about persistent memory (PMem) and simulate it (if you wish), refer to our tutorial: VMware ESXi 6.7 - Use persistent memory (PMem) via NVDIMMs modules.
To get started, right-click "New Virtual Machine" on the location (data center or folder) where you want to add your new virtual machine.
In the "New Virtual Machine" wizard that appears, select "Create a new virtual machine" and click Next.
Provide a name for your new virtual machine and select where you want to add it.
Select the compute resource corresponding to the VMware ESXi host where persistent memory (PMem) is located.
Next, leave the "Standard" option selected by default and select the datastore where you want to store this new virtual machine.
Select the compatibility level to use for this virtual machine.
Preferably, the one corresponding to the version of the VMware ESXi host used.
For the guest operating system, we chose "Microsoft Windows 8.x (64-bit)", because it is not supported for the use of vPMem (via NVDIMM modules).
Which will allow us to show you how to use persistent memory (PMem) when the guest operating system does not support vPMem.
For virtual hardware, first select the ISO file to install the desired guest operating system.
In our case: Windows 8.1 Pro x64.
If you click on the "Add New Device" button, you will see that the "NVDIMM" option is displayed.
However, given that we are using an operating system that does not support the use of vPMem (via NVDIMM modules), an error message will be displayed:
Plain Text
The guest OS does not support the device.
To benefit from persistent memory (PMem) performance with an operating system that does not support vPMem (via NVDIMM modules), you will first need to click on: Add New Device -> Hard Disk.
The newly added virtual hard disk appears.
To have the data on this virtual hard disk stored in persistent memory (PMem) on your VMware ESXi host, specify the size you want for it, and then select the VM storage policy: Host-local PMem Default Storage Policy.
As you can see in the "Disk Privisioning" line, this virtual hard disk will be stored in PMem and most of the options will be grayed out.
However, as you can see from the "Virtual Device Node" line, although the data will be stored in persistent memory (PMem), this virtual hard drive will be exposed to the guest operating system via a virtual SCSI controller.
If you click on the "i" next to the size of this virtual hard disk, VMware vCenter Server will clearly indicate that it will be stored in the PMem datastore (in other words: PMemDS-...).
As you can see in the summary that appears, the 2nd virtual hard drive will be stored in persistent memory (PMem), but will be accessible from the guest operating system via a virtual SCSI controller.
The created virtual machine appears.
If you look in the VM hardware of this new virtual machine, you will see that the location of hard drive 2 is "PMemDS-...".
Warning : in the case of simulated "persistent" memory (PMem), the identifier of this datastore "PMemDS-..." will change each time the VMware ESXi host concerned is started or restarted.
If you use actual persistent memory modules (PMem), you won't have this problem.
In the associated objects of this virtual machine, you will also find the "PMemDS-..." datastore used by this virtual machine.
Click on the name of this datastore "PMemDS-...".
Note: if this does not work, return to the page for this virtual machine and click this link a second time. Now it will work.
As you can see, this datastore "PMemDS-..." currently contains a folder with the name of the virtual machine of which one of these virtual hard disks is stored in persistent memory (PMem).
If you enter this folder, you will find the ".vmdk" file corresponding to the SCSI virtual hard disk for which you had chosen the "Host-local PMem Default Storage Policy" VM storage policy.
VMware 6/22/2022
VMware 3/10/2023
VMware 7/10/2024
VMware 1/17/2025
Pinned content
Contact
® InformatiWeb-Pro.net - InformatiWeb.net 2008-2022 - © Lionel Eppe - All rights reserved.
Total or partial reproduction of this site is prohibited and constitutes an infringement punishable by articles L.335-2 and following of the intellectual property Code.
You must be logged in to post a comment