Joseph Mocker wrote: > Hello, > > Does anyone have any suggestion on how to manage migrations, live or > otherwise, with domains installed on iSCSI targets between different > physical hosts? > > The problem I see is that you cannot be guaranteed that the device name > that the iSCSI target gets mapped to on each system will be the same. In > my test rig, for example, I see: > > > on host1: /dev/rdsk/c2t010000144F40979800002A0048D97F70d0s2 > on host2: /dev/rdsk/c4t010000144F40979800002A0048D97F70d0s2 > > (Notice the controller number differs.)
I have some changes in a stale local gate where you can do something like the following.. disk = [ phy:iscsi:[static]/<targetid>/<lun>/[serverIpAddr] ] e.g. disk = ['phy:iscsi:static/iqn.1986-03.com.sun:02:17f34578-00a9-ef69-f3e9-b8a2896a4915/0/192.168.0.70,0,w'] if the mapping is static, the hotplug scripts will dynamically add the target to dom0 on guest boot and remove it on shutdown. I need to refresh the code and clean it up.. If anyone has any options or further enhancements in mind, I'd be interested in hearing them. MRJ > I was hoping that devfsadm might have some (easy) way to force enforce > uniformity, but so far I don't see anything there. > > For now, I have worked around this with the use of symlinks to the > devices which are then specified in the domain config rather than these > dev links above. > > It isn't horrible, but its another step in the process. > > Anyone doing migration with domains iSCSI? How are you doing it? > > > _______________________________________________ > xen-discuss mailing list > [email protected] _______________________________________________ xen-discuss mailing list [email protected]
