Yellow Bricks

by Duncan Epping

Impact of adding Persistent Memory / Optane Memory devices to your VM

Leave a Comment

I had some questions around this in the past month, so I figured I would share some details around this. As persistent memory (Intel Optane Memory devices for instance) is getting more affordable and readily available more and more customers are looking to use it. Some are already using it for very specific use cases, usually in situations where the OS and the App actually understand the type of device being presented. What does that mean? At VMworld 2018 there was a great session on this topic and I captured the session in a post. Let me copy/paste the important bit for you, which discusses the different modes in which a Persistent Memory device can be presented to a VM.

  • vPMEMDisk = exposed to guest as a regular SCSI/NVMe device, VMDKs are stored on PMEM Datastore
  • vPMEM = Exposes the NVDIMM device in a “passthrough manner, guest can use it as block device or byte addressable direct access device (DAX), this is the fastest mode and most modern OS’s support this
  • vPMEM-aware = This is similar to the mode above, but the difference is that the application understands how to take advantage of vPMEM

But what is the problem with this? What is the impact? Well when you expose a Persistent Memory device to the VM, it is not currently protected by vSphere HA, even though HA may be enabled on your cluster. Say what? Yes indeed, the VM which has the PMEM device presented to it will be disabled for vSphere HA! I had to dig deep to find this documented anywhere, and it is documented in this paper. (Page 47, at the bottom.) So what works and what not? Well if I understand it correctly:

  • vSphere HA >> Not supported on vPMEM enabled VMs, regardless of the mode
  • vSphere DRS >> Does not consider vPMEM enabled VMs, regardless of the mode
  • Migration of VM with vPMEM / vPMEM-aware >> Only possible when migrating to host which has PMEM
  • Migration of VM with vPMEMDISK >> Possible to a host without PMEM

Also note, as a result (data is not replicated/mirrored) a failure could potentially lead to loss of data. Although Persistent Memory is a great mechanism to increase performance, it is something that should be taken into consideration when you are thinking about introducing it into your environment.

Oh, if you are wondering why people are taking these risks in terms of availability, Niels Hagoort just posted a blog with a pointer to a new PMEM Perf paper which is worth reading.

 

 

DRS Advanced Setting IsClusterManaged

2 Comments

On Reddit, someone asked what DRS advanced setting IsClusterManaged does and if it is even legit. I can confirm it is legit, it is a setting which was introduced to prevent customers from disabling DRS while the cluster is managed by vCloud Director for instance. As disabling DRS would lead to deleting resource pools, which would be a very bad situation to find yourself in when you run vCloud Director as it leans on DRS Resource Pools heavily. So if you see the advanced setting IsClusterManaged in your environment for DRS, just leave it alone, it is there for a reason. (Most likely because you are using something like vCloud Director…)

Present Powerpoint slides in window instead of full screen

1 Comment

I just had to do a Zoom presentation (on a Macbook by the way) and one thing which always bugs me is that I need to run the presentation in full screen and can’t see the chat or Q&A. I like to address questions as I go during the presentation. I was going through the Powerpoint interface and noticed an option I had not noticed before. If you click on “Slideshow” and then “Set Up Slide Show” you can select “Browsed by an individual (window)”, this allows you to run the presentation within a window and have your chat and Q&A open next to the window. Very useful if you ask me. Figured I would share as it doesn’t seem common knowledge

MS Office autoupdate in constant loop on OSX / Mac

1 Comment

Oh man, this was driving me insane. I found myself in a situation where MS Office Autoupdate was in a loop, I think it ran about once an hour at least for 2 days. Each time, of course, it would tell me there were no updates. Frustrating for sure. I place it in to “Manual” mode but it would still open up every hour. This Autoupdate loop started to begin after an upgrade to MS Office 16.24 for Mac. I ended up doing the following to solve the problem. So far I have not seen the Autoupdate window anymore, so let’s hope it indeed solved it:

Open a terminal window and do the following:

cd ~/Library/Preferences

rm -rf com.microsoft.autoupdate*.plist

After the files have been deleted, manually run Autoupdate once. This solved the problem for me. One of my colleagues solved the problem by simply downloading the autoupdater for Mac from the MS website and manually update it. Just sharing this in case others are hitting the same problem.

I want vSphere HA to use a specific Management VMkernel interface

1 Comment

This comes up occasionally, customers have multiple Management VMkernel interfaces and see vSphere HA traffic on both of the interfaces, or on the incorrect interface. In some cases, customers use the IP address of the first management VMkernel interface to connect the host to vCenter and then set an isolation address that is on the network of the second management VMkernel so that HA uses that network. This is unfortunately not how it works. I wrote about this 6 years ago, but it never hurts to reiterate as it came up twice over the past couple of weeks. The “management” tickbox is all about HA traffic. Whether “Management” is enabled or not makes no difference for vCenter or SSH for instance. If you create a VMkernel interface without the Management tickbox enabled you can still connect to it over SSH and you can still use the IP to add it to vCenter Server. Yes, it is confusing, but that is how it works.

If you want the interface to not be used by vSphere HA, make sure to untick “Management”. Note, this is not the case for vSAN, with vSAN automatically the vSAN network is used by HA. This only pertains to traditional, non-vSAN based, infrastructures.