To avoid this ambiguity, please use the access path by-path. This can be specified during the installation
when the mount points are defined.
The above restriction does not apply for SLES10 SP2 (which has fix for Problem-ID 34345 and 43704),
if you have the z/VM PTF for APAR VM64273, with which z/VM provides a unique identifier that
allows to distinguish between virtual disks on the same real device. Udev rules that provide both old and
new /dev/disk/by-id paths are included. To use the new IDs in your multipath setup, please replace the
getuid_callout "/sbin/dasdinfo -u -b %n" with "/sbin/dasdinfo -x -b %n" in your multipath configuration
for DASD devices. Please see the man page for the dasdinfo tool for additional information.
• Local Mounts of iSCSI Shares
An iSCSI shared device should never be mounted directly on the local machine. In an OCFS2
environment, doing so causes all hardware to hard hang.
• Restriction When Using cpint/hcp (zSeries)
When using the cpint/hcp interface with z/VM 5.1 or earlier, the guest should not have more than 2
GByte of storage. If the guest has more storage, the command may fail.
• HP sx1000- and sx2000-based systems and multiple VGA adapters
HP sx1000- and sx2000-based systems, including rx7620, rx8620, rx7640, rx8640 and all Superdomes,
only support the use of a single VGA device per hard partition. The usage of more than one VGA card
causes a system hang or crash on all of this systems.
To prevent this on machines with more than one VGA adapter, either do not install the X server at all
or configure it manually to use only a single VGA device.
• YaST2 CD-Creator and YUM installation sources
The YaST2 CD-Creator module does not support YUM installation sources like our update server
provides. For this reason, it is not possible to create a medium with updates included. If you want to
create a medium with updates included, use YaST2 Product-Creator.
YaST2 Product-Creator is a successor of YaST2 CD-Creator. It includes a GUI for the kiwi imaging
system. This way it is also possible to create a Live-CD, XEN image, etc. from the same configuration
used in the CD Creator. The Product-Creator will get shipped together with the SDK.
• glibc-debuginfo package on POWER
The glibc-debuginfo package doesn't set up the debug information files for certain processor-optimized
versions of the libraries. This affects glibc debugging on the following POWER processors: POWER4,
PPC970, POWER5+, POWER6x. To fix the problem, one needs to manually create the missing
symbolic links using a sequence of commands like this:
Obtain root priviledges:
$ /bin/su -
Go to the 32-bit debuginfo directory:
# cd /usr/lib/debug/lib
Known Issues
20
Need help?
Do you have a question about the SP2 - RELEASE NOTES and is the answer not in the manual?
Questions and answers