README VERSION: 1.1
DATE: 2025-04-03

FIXES APPLIED FOR PRODUCTS:
---------------------------
VRTSvxvm 8.0

PACKAGES:  
PATCH NAME: Patch_8_0_00010_0_4188998
SUPERSEDED PATCHES: NONE
REQUIRED PATCHES: NONE
PATCH CATEGORY:  CORRUPTION
PATCH CRITICALITY       : OPTIONAL
HAS KERNEL COMPONENT    : NO
ID                      : NONE
REBOOT REQUIRED: YES

OS: w2k16X64,w2k19X64

INSTALL/UNINSTALL INSTRUCTIONS:
-------------------------------
This package contains self-extracting files that are specific to the processor architecture and operating system version.
Choose the appropriate file for your computer's configuration.
======================================================================================
Operating System    Platform    File Name

----------------------------------------------------------------------------------------
Download the appropriate hotfix executable to a temporary location on your system.
You can install this hotfix using the GUI or from the command line. Instructions for both options are provided below.This package contains self-extracting files that are specific to the processor architecture and operating system version. Download the appropriate hotfix executable to a temporary location on your system. You can install this hotfix using the GUI or the CLI. Instructions for both these options are provided below. To install the hotfix on server systems using the GUI ------------------------------------------------------------------------- 1. Double-click the hotfix executable file to extract its contents to a default location on the cluster node. By default, the files are extracted to: '%programfiles(x86)%\Common Files\Veritas Shared\WxRTPrivates' The Hotfix Installer Wizard is automatically launched after the files are extracted. 2. Click 'Next' on the Welcome screen. The 'Hotfix Installation Task' screen lists the tasks that are performed by the installer. 3. Click 'Install Hotfix' to begin the hotfix installation. The status of each installation task is updated as it completes. 4. After the tasks are complete, click 'Next' and then click 'Finish' to complete the installation process. 5. If this is a clustered configuration (VCS or MSCS), perform steps 1-4 on all additional nodes in the cluster. To install the hotfix on server systems using the CLI ------------------------------------------------------------------------ 1. Navigate to the following location at the command prompt: 'C:\temp' 2. Run one of the following commands to extract the hotfix files to the default location: <Hotfix_BuildVersion_IncidentNumber_OS_Platform> .exe /x or <Hotfix_BuildVersion_IncidentNumber_OS_Platform> .exe /extract 3. Navigate to the default location where the hotfix files are extracted. By default, the files are extracted to: '%programfiles(x86)%\Common Files\Veritas Shared\WxRTPrivates\<Hotfix_BuildVersion_IncidentNumber> ' 4. Run the following command to install the hotfix: VxHF.exe /install:<Hotfix_BuildVersion_IncidentNumber> /silent Here, <Hotfix_BuildVersion_IncidentNumber> is the name of the hotfix file excluding the OS, platform, and .exe extension. 5. To complete the hotfix installation, follow the instructions that are displayed at the command prompt. 6. If this is a clustered configuration (VCS or MSCS), perform steps 1-5 on all additional nodes in the cluster.

To confirm the installation of a hotfix, run the following command: vxhf.exe /list On server systems, vxhf.exe is located at: '%programfiles(x86)%\Common Files\Veritas Shared\WxRTPrivates\<Hotfix_BuildVersion_IncidentNumber> ' The output of this command lists the hotfixes installed on a system. - The hotfix installer (vxhf.exe) creates and stores logs at: '%allusersprofile%\Application Data\Veritas\VxHF' - For general information about the hotfix installer (vxhf.exe), refer to the following technote: http://www.veritas.com/docs/000039694 - To view a list of hotfixes already installed on a system, refer to the steps mentioned in the following technote: http://www.veritas.com/docs/000039691 - For information on uninstalling a hotfix, refer to the steps mentioned in the following technote: http://www.veritas.com/docs/000039693

SUMMARY OF FIXED ISSUES:
-----------------------------------------

 PATCH ID:Patch_8_0_00010_0_4188998

4188998 (3958763)  VXIO thread sleeps when the value mentioned in IRQL_DISPATCH_LEVEL is achieved, which triggers a bug check function or results in a system 
crash. 

SUMMARY OF KNOWN ISSUES:
-----------------------------------------
NONE 

FIXED INCIDENTS:
----------------

 PATCH ID:Patch_8_0_00010_0_4188998

 * INCIDENT NO:4188998     TRACKING ID:3958763

SYMPTOM: VXIO thread sleeps when the value mentioned in IRQL_DISPATCH_LEVEL is achieved, which triggers a bug check function or results in a system crash. 

DESCRIPTION: When Windows Server runs under low available PTE conditions, the memory mapping request may fail. In such a situation, when the VXIO driver calls 
the MmGetSystemAddressForMdlSafe function, the operation fails. When a processor is at a value greater than or equal to the one defined in IRQL_DISPATCH_LEVEL, 
a wait or a sleep action is not recommended. These actions may result in undefined behavior like a bug check or a BSOD. A code path in the VXIO module calls the 
MmGetSystemAddressForMdlSafe function to map the physical address of the system to a virtual address in the MDL. If the virtual address is not available, PTE 
entries are created. If the PTE is low on availability, the mapping of a virtual address to a physical address fails. In this case, another attempt is made to 
get the virtual address. However, the VXIO process sleeps for 10 ms if the value defined in IRQL_DISPATCH_LEVEL is achieved before it makes the attempt. Thus, 
it triggers a bug check or results in a BSOD. 

RESOLUTION: This hotfix updates the VXIO module so that the memory mapping failure thread sleeps only if the IRQL level is less than the value of 
IRQL_DISPATCH_LEVEL. Otherwise, the thread proceeds with the failure. The VXIO driver then handles this failure. FILE / VERSION: vxio.sys / 8.0.10.1 , vxio_msgs.dll / 8.0.10.1 

KNOWN INCIDENTS:
----------------
NONE

INCIDENTS FROM OLD PATCHES:
---------------------------
NONE

DISCLAIMER: This fix is provided without warranty of any kind including the warranties of title or implied warranties of merchantability, fitness for a particular purpose and non-infringement. Veritas disclaims all liability relating to or arising out of this fix. It is recommended that the fix be evaluated in a test environment before implementing it in your production environment. When the fix is incorporated into an InfoScale for Windows maintenance release, the resulting Hotfix or Service Pack must be installed as soon as possible. Veritas Technical Services will notify you when the maintenance release (Hotfix or Service Pack) is available if you sign up for notifications from the Veritas support site http://www.veritas.com/support and/or from Services Operations Readiness Tools (SORT) http://sort.veritas.com.