The short question:
- should any magic be done on a XEN-virtualized OES 2 Linux server so that
the EVMS functionality of iPrint should work?

The long statement:
- I run a 2-node OES 2 Linux cluster
- one of the nodes is XEN-virtualized
- I created an iPrint cluster resource on the non-virtualized cluster node
based on
http://www.novell.com/documentation/..._iprintcluster
- the iPrint cluster resource loads well on the non-virtualized cluster
node
- unfortunately, the resource goes comatose on the virtualized cluster node
- though evmsgui shows exactly the same EVMS configuration (when the
cluster resource is off-line) on both cluster nodes, the EVMS container is
unable to be activated: I debugged the load script of the resource and
found its 'activate_evms_container ...' line to fail, I debugged
activate_evms_container and found its '/opt/novell/ncs/bin/ch_csm_attr
...' line to fail