Skip to content

Conversation

@jandryuk
Copy link
Contributor

@jandryuk jandryuk commented Feb 1, 2024

The Xen 4.14 uprev dropped libxl blktap integration. The data path became:
blkfront <-> blkback <-> /dev/xen/blktap-2/tapdevX <-> tapdisk <-> vhd

This PR introduces upstream-able libxl patches to switch to:
blkfront <-> tapdisk <-> .vhd

Goes with OpenXT/manager#209

We patch blktap to use blktap-control as the misc device name since
upstream blktap uses blktap/control.  Change our linux patch to use
blktap/control and drop our blktap patching to align with upstream.

refpolicy needs an additional fixup to label /dev/blktap/control
properly.

Signed-off-by: Jason Andryuk <[email protected]>
tapback is making a comeback!  We'll run it in dom0 to directly provide
the tapdisk backends.

This reverts commit 7151b14.

Signed-off-by: Jason Andryuk <[email protected]>
Add patches for libxl compatibility.

Pass --libxl flag to tapback for compatibility mode.

Signed-off-by: Jason Andryuk <[email protected]>
Add patches for libxl to directly support vbd3 without going through
blkback.

Signed-off-by: Jason Andryuk <[email protected]>
tapdisk exposes its disks over NBD, and libxl uses that to configure
QEMU's access in dom0.  We need to re-enabled NBD support for the
non-stubdom case to access the disks.

Signed-off-by: Jason Andryuk <[email protected]>
QEMU needs to connect to the tapdisk unix socket to access the exported
disk images.  Allow it.

Signed-off-by: Jason Andryuk <[email protected]>
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

Successfully merging this pull request may close these issues.

1 participant