Veritas Cluster Server Release Notes
Veritas⢠Cluster Server Release Notes: Linux - SORT - Symantec
Veritas⢠Cluster Server Release Notes: Linux - SORT - Symantec
- No tags were found...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>Veritas</strong> <strong>Cluster</strong> <strong>Server</strong> <strong>Release</strong> <strong>Notes</strong><br />
Known issues<br />
75<br />
Guest virtual machine may fail on RHEL 6.1 if KVM guest image<br />
resides on CVM-CFS [2659944]<br />
If a KVM guest image file resides on CVM-CFS, the migration of that guest virtual<br />
machine may fail with "Permission Denied" error on RHEL 6.1. This causes guest<br />
virtual machine to go in "shut-off" state on both source and destination node, and<br />
the associated VCS KVMGuest.<br />
Workaround: Make sure that the guest image file is having 777 permission.<br />
System panics after starting KVM virtualized guest or initiating<br />
KVMGuest resource online [2337626]<br />
System panics when the KVM guest is started or when the KVMGuest resource<br />
online is initiated. This issue is rarely observed.<br />
The issue is observed due to the file descriptor leak in the libvirtd process. The<br />
maximum file open limit of file descriptor for libvirtd process is 1024. You may<br />
sometimes observe that more than 1024 file descriptors are opened when the KVM<br />
guest is started. Therefore, if the maximum file open limit is crossed, any attempt<br />
to start the KVM guest or to open a new file causes the system to panic. VCS cannot<br />
control this behavior as it suspects a file descriptor leak in the libvirtd process.<br />
Workaround: There is no definite resolution for this issue; however, you can check<br />
the number of files opened by the libvirtd process in /proc//fd/.<br />
If the file count exceeds 1000, restart libvirtd with the following command:<br />
/etc/init.d/libvirtd restart<br />
Wizard, Dashboard, and Symantec High Availability tab specific<br />
issues<br />
The vCenter <strong>Server</strong> tasks shown in the vSphere Client may fail<br />
to display the correct status if the Symantec High Availability<br />
Guest Components installation fails<br />
This issue occurs in case of VMware vCenter <strong>Server</strong> version 5.1.<br />
If you choose to install the Symantec High Availability Guest Components using<br />
the vSphere Client menu and if the installation fails, then the vCenter <strong>Server</strong> task<br />
shown in the vSphere Client gets held-up at 10%. It however, does not display that<br />
the installation has failed. (2824900)<br />
Workaround:
Change language