Enhance multipathing documentation for XCP-ng#462
Open
manfuin wants to merge 1 commit into
Open
Conversation
Added information about multipath management in XCP-ng to clarify the expectations when verifying visible paths on host Signed-off-by: Andrii Salnikov <manfuin@gmail.com>
thomas-dkmt
approved these changes
May 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi! This PR is aimed to add information about multipath management in XCP-ng to clarify the expectations when verifying visible paths on host.
I spend quite a time to understand why the multipath device is not created on the host despite the default config has
find_multipathsset toyes. I hope this small extra info notice in the documentation can save time for other people like me.I used to the practice that I have to check that multipath is operational before I am going to do something with multipath device from generic Linux experience.
This assumption is clearly wrong in Storage Manager case, and Storage Manager source code is clearly shows it is managing
wwidsand basically all aspects of multipath management on its own and not relying on paths auto-assembly by multipathd. I trully believe this is important to know at the start.Kind regards,
Andrii