We have built a software appliance based upon k3os, and have use-cases where the installation requires boot-from-SAN (i.e., multipath support). These changes are the basis for how we have met these requirements. For installation, we boot into the live installer without multipath enabled and install to any one of the available paths. Upon reboot into the installed system, we enable multipath while in MODE=disk before pivot_root and calling init with MODE=local. The end result is such that our root fs is mounted on the multipath device / partition as seen below:
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/mpatha-part1 4.6G 1.1G 3.3G 25% /
Since not everyone would want this built in, maybe we could/should make these changes optional based on some build-time paramater(s).
We have built a software appliance based upon k3os, and have use-cases where the installation requires boot-from-SAN (i.e., multipath support). These changes are the basis for how we have met these requirements. For installation, we boot into the live installer without multipath enabled and install to any one of the available paths. Upon reboot into the installed system, we enable multipath while in
MODE=diskbeforepivot_rootand callinginitwithMODE=local. The end result is such that our root fs is mounted on the multipath device / partition as seen below:Since not everyone would want this built in, maybe we could/should make these changes optional based on some build-time paramater(s).