In general, updating the flexVDI packages when a new version is published is as easy as running
yum update on your hosts. However, updating some packages can cause the guest virtual machines to be stopped. Read on for more details.
Although they seldom change, updating ocfs2-tools-* packages will restart the ocfs2/o2cb service. This, in turn, will remount your shared storage volumes, killing any virtual machine that was using a virtual disk image in any of these volumes. So, better cleanly stop your virtual machines, or migrate them to another host before updating these packages. Then you can run:
# yum update ocfs2-tools ocfs2-tools-o2cb
Updating the host kernel
One of the components of flexVDI suite is a kernel module called kmod-ocfs2-flexvdi.
In Red Hat based Linux distributions where flexVDI software is installed, the kernel package is special because several versions of it can be installed at the same time on the same machine. Almost every other package can only have one single version installed at a given time, and kmod-ocfs2-flexvdi is no exception. But kernel modules, like kmod-ocfs2-flexvdi, are developed for one specific kernel version. To be able to have several kmod-ocfs2-flexvdi installed at the same time for different kernels, we publish kmod-ocfs2-flexvdi-k514.x86_64, kmod-ocfs2-flexvdi-k693.x86_64, kmod-ocfs2-flexvdi-k862.x86_64, ... as different packages, instead of being different versions of the same package.
If you update your kernel, you have to manually install the appropriate kmod-ocfs2-flexvdi package as explained above, because it is not automatically updated. Failing to do so may leave guest disk images inaccessible to the host.
Updating all packages except kernel and ocfs2-tools
As updating kernel or ocfs2-tools will always cause the host to temporarily stop servicing guest machines, you may be interested in updating the rest of the packages. You can do this with: