Our environment:
- two xen servers sles11 sp2 and HA-EXT
- both attached to an ibm fibre channel ds4300 san storage with two controller (active/passive)
- multipathing is configured
- on both servers we have the same san luns:

mpatha_harley_sys (3600axxxxxxxxxxxxxxxxxxxxxxxabea4) dm-1 IBM,1722-600
size=30G features='1 queue_if_no_path' hwhandler='1 rdac' wp=rw
|-+- policy='round-robin 0' prio=6 status=active
| `- 2:0:0:0 sdb 8:16 active ready running
`-+- policy='round-robin 0' prio=1 status=enabled
`- 2:0:1:0 sde 8:64 active ghost running

When I start the installation via the vm-install command the domu is going active and starts the installation on the san volume. After the first reboot during the installation the domu is reading the kernel and the initrd but the domu is not able to access the xvda device (the configured san volume).

What I found out:
After the first reboot during the installation of the vm, the partitioning of the multipath device comes viewable on the dom0 server, then the domu cannot access to this device any more.

When I remove the partitioning on the dom0 server with the following command:

kpartx -d -v -p "_part" /dev/mapper/mpath_harley_sys

I can continue the installation of the vm with a new reboot. When the new vm is active and I will call the partprobe command on the dom0 server the partitioning of the vm will not be viewable. When I shutdown the vm and call again the partprobe command on the dom0 server, the partitioning comes viewable but the vm will not start again.

Seems there is a device mapper problem.

Our VM configuration file:
name="vm-harley"
description="None"
uuid="58c72121-bcb7-77a8-2584-0d5f251adea5"
memory=2048
maxmem=4096
vcpus=1
on_poweroff="destroy"
on_reboot="restart"
on_crash="destroy"
localtime=0
keymap="de"
builder="linux"
bootloader="/usr/bin/pygrub"
boextra=""
disk=[ 'phy:/dev/mapper/mpath_harley_sys,xvda,w', ]
vif=[ 'mac=00:16:3e:7a:9d:f2,bridge=br1', ]
vfb=['type=vnc,vncunused=1']otargs=""

This configuration runs well on SLES11 SP1
I have also tested the patched xen kernel form April 23 rd, same result.
I reported this also as a bug to novell, any ideas.

Rainer