Bug 1412140 - RFE: support QEMU's 9p proxy driver
Summary: RFE: support QEMU's 9p proxy driver
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Virtualization Tools
Classification: Community
Component: libvirt
Version: unspecified
Hardware: All
OS: All
unspecified
unspecified
Target Milestone: ---
Assignee: Libvirt Maintainers
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-11 11:12 UTC by Leo Antunes
Modified: 2024-12-17 12:13 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-12-17 12:13:21 UTC
Embargoed:


Attachments (Terms of Use)

Description Leo Antunes 2017-01-11 11:12:21 UTC
Hi all,

Back in 2012 there were patch proposals by M. Mohan Kumar [0] to add support for QEMU's 9p proxy driver. These seem to have been forgotten. I couldn't find any more chatter about them on the lists and they apparently haven't been applied.

Did I miss something?

It would be nice to add support for this driver.


Cheers


[0] https://www.redhat.com/archives/libvir-list/2012-September/msg00444.html

Comment 1 Jiri Denemark 2017-01-11 11:39:36 UTC
The original author has never sent a new version of the patch and nobody else from the community seems to be interested in this topic enough to implement the feature.

I think the focus shifted from 9pfs to NFS over virtio-vsock, although this is not yet implemented in libvirt either.

Comment 2 Daniel Berrangé 2024-12-17 12:13:21 UTC
Thank you for reporting this issue to the libvirt project. Unfortunately we have been unable to resolve this issue due to insufficient maintainer capacity and it will now be closed. This is not a reflection on the possible validity of the issue, merely the lack of resources to investigate and address it, for which we apologise. If you none the less feel the issue is still important, you may choose to report it again at the new project issue tracker https://gitlab.com/libvirt/libvirt/-/issues The project also welcomes contribution from anyone who believes they can provide a solution.


Note You need to log in before you can comment on or make changes to this bug.