FCP devices allow the 'Add' of swap devices directly, so they are valid targets in HVM, however not sure how the /dev/dasd devices should be handled, or even included in the available listing. When you create a dasd partition, that particular dasd will no longer appear on the list.
When adding a /dev/dasd based swap device, HVM yields an error:
GINSP00005E: Error creating a swap device. GINSP00013E: Unable to activate swap device. swapon: /dev/dasdc: read swap header failed: Invalid argument
A similar error is generated when the same operation is done manually:
[root@zs93k2 dev]# mkswap /dev/dasdb Setting up swapspace version 1, size = 7212236 KiB no label, UUID=b8acf04e-cf3c-4467-aa99-38872f08595e
[root@zs93k2 dev]# swapon /dev/dasdc swapon: /dev/dasdc: read swap header failed: Invalid argument
Apparently dasd devices do not support swap devices directly, but do so on a dasd partition.
[root@zs93k2 dev]# fdasd /dev/dasdc [root@zs93k2 dev]# swapon /dev/dasdc1
FCP devices allow the 'Add' of swap devices directly, so they are valid targets in HVM, however not sure how the /dev/dasd devices should be handled, or even included in the available listing. When you create a dasd partition, that particular dasd will no longer appear on the list.