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

[QUESTION] Plan to add Viosock driver to release #1185

Open
Iziram opened this issue Nov 8, 2024 · 3 comments
Open

[QUESTION] Plan to add Viosock driver to release #1185

Iziram opened this issue Nov 8, 2024 · 3 comments

Comments

@Iziram
Copy link

Iziram commented Nov 8, 2024

Hi there,
I'm building stuff on top of VSock and this driver makes it possible to use my project on both linux and windows.
For now i've been using it by bypassing the Driver Signatures but it can't be used in a production environment which is not great for my project.

Is there any plan to add the viosock drivers to the virtio-win release ? ( To have it signed properly and let windows auto install it )

@YanVugenfirer
Copy link
Collaborator

Hi, There are no plans for the next several months.

@foxtrotcz
Copy link

foxtrotcz commented Nov 10, 2024

I would also like for viosock driver to be included in the ISO release.
It would allow Incus to support Incus agent for Windows VM, which depends on viosock driver.
https://discuss.linuxcontainers.org/t/how-to-connect-to-remote-windows-vm/20210/15

@vrozenfe
Copy link
Collaborator

Definitely we can add Viosock driver to the virtio-win build and to the ISO layout.
But doubt that our (RH virtio-win) QE team will be able to verify or at least run
some preliminary WHQL and functional testing on this driver in the nearest future.

Anyway we will not be able to include Viosock binaries in the flowing public release
which should be ready in a couple of weeks or so, but I will try to make Viosock
binaries public asap.

Best,
Vadim.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants