DomU on dm-multipath'ed FC LUN

[Max from BPC]

Hello!

My problem - DomU on dm-multipath'ed FC LUN

Configuration :

ProLiant HP DL360G5
OS SLES 11 - Dom0
kernel 2.6.27.37-0.1-xen
OS SLES 10 SP3 - DomU

HBA QLogic Dual port Fibre Channel HBA
Driver version 8.03.00.08.11.0

Storage HP EVA 8000
Entire LUN 1 presented to Dom0 with following partitions:
Part 1 Volume Label lv_boot
Part 2 Volume Label lv_root
Part 3 Volume Label lv_swap
and "visible" for DomU as phy:/dev/mapper/mpathb

VM XEN xen-3.3.1_18546_12-3.1

Versions of packages:
device-mapper-1.02.27-8.7.2
multipath-tools-0.4.8-40.6.1

Problem :

SLES 11 installed as Dom0 on local hard drive...
SLES 10 SP3 installed on DomU on LUN 1...

If we use device-mapper multipathing on Dom0 - VM don't boot : xend.err "Boot loader didn't return any data!"

Confing VM
...
builder="linux"
bootloader="/usr/lib/xen/boot/domUloader.py"
bootargs="--entry=xvda1:/boot/vmlinuz-xenpae,/boot/initrd-xenpae"
extra=" "
disk=[ 'phy:/dev/mapper/mpathb,xvda,w', 'file:/usr/local/src/SLES-10-SP3-DVD-i386-GM-DVD1.iso,xvdb:cdrom,r', ]
...

If we don't use multipathing on Dom0 - VM boot successfuly (Just devices as /dev/sd[]).
All works fine but we don't have redundant FC connections.

Confing VM
...
builder="linux"
bootloader="/usr/lib/xen/boot/domUloader.py"
bootargs="--entry=xvda1:/boot/vmlinuz-xenpae,/boot/initrd-xenpae"
extra=" "
disk=[ 'phy:/dev/sda,xvda,w', 'file:/usr/local/src/SLES-10-SP3-DVD-i386-GM-DVD1.iso,xvdb:cdrom,r', ]
...


xm log:

[2009-11-05 11:16:37 5158] DEBUG (XendDomainInfo:2068) XendDomainInfo.constructDomain
[2009-11-05 11:16:37 5158] DEBUG (balloon:151) Balloon: 132608 KiB free; need 2048; done.
[2009-11-05 11:16:37 5158] DEBUG (XendDomain:450) Adding Domain: 7
[2009-11-05 11:16:37 5158] DEBUG (XendDomainInfo:2232) XendDomainInfo.initDomain: 7 256
[2009-11-05 11:16:37 24015] DEBUG (XendBootloader:117) Launching bootloader as [\047/usr/lib/xen/boot/domUloader.py\047, \047--args= \047, \047--output=/var/run/xend/boot/xenbl.26261\047, \047--entry=xvda1:/boot/vmlinuz-xenpae,/boot/initrd-xenpae\047, \047/dev/mapper/mpathb\047].
[2009-11-05 11:16:37 5158] ERROR (XendBootloader:188) Boot loader didn\047t return any data!
[2009-11-05 11:16:37 5158] ERROR (XendDomainInfo:470) VM start failed
Traceback (most recent call last):
File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 450, in start
XendTask.log_progress(31, 60, self._initDomain)
File "/usr/lib64/python2.6/site-packages/xen/xend/XendTask.py", line 209, in log_progress
retval = func(*args, **kwds)
File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 2234, in _initDomain
self._configureBootloader()
File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 2653, in _configureBootloader
bootloader_args, kernel, ramdisk, args)
File "/usr/lib64/python2.6/site-packages/xen/xend/XendBootloader.py", line 189, in bootloader
raise VmError, msg
VmError: Boot loader didn\047t return any data!
[2009-11-05 11:16:37 5158] DEBUG (XendDomainInfo:2446) XendDomainInfo.destroy: domid=7
[2009-11-05 11:16:37 5158] DEBUG (XendDomainInfo:1976) No device model
[2009-11-05 11:16:37 5158] DEBUG (XendDomainInfo:1978) Releasing devices

IMHO this is problem in phyton scripts of xen-3.3.1 of SLES11.

Any ideas?

[Siert Zijl]

Please, supply your multipath conf.