Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Xen block driver doesn't consider "backend" and hardcodes the backend path #1541

Open
TSnake41 opened this issue Jan 14, 2025 · 0 comments
Open

Comments

@TSnake41
Copy link

TSnake41 commented Jan 14, 2025

The block backend driver attempts to build the xenstore backend path using the backend-id entry instead of using the full path exposed in backend.

IOW, the path used by Illumos is /local/domain/<oeid>/backend/vbd/... (with oeid from backend-id) regardless of backend (usually in device/vbd/<id>/backend) which is directly the full path.

While it mostly works with QEMU blkback, it fails under XCP-ng and XenServer as blktap3 moved the "backend node" path to /local/domain/<oeid>/backend/vbd3/... (notice the vbd3), which causes the driver to fail as it's not using the right xenstore path

Seem to be the root cause of #1431.

@TSnake41 TSnake41 changed the title Xen block driver doesn't consider backend and hardcodes the backend path Xen block driver doesn't consider "backend" and hardcodes the backend path Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant