You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The block backend driver attempts to build the xenstore backend path using the
backend-id
entry instead of using the full path exposed inbackend
.IOW, the path used by Illumos is
/local/domain/<oeid>/backend/vbd/...
(with oeid frombackend-id
) regardless ofbackend
(usually indevice/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 thevbd3
), which causes the driver to fail as it's not using the right xenstore pathSeem to be the root cause of #1431.
The text was updated successfully, but these errors were encountered: