-
Notifications
You must be signed in to change notification settings - Fork 75
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
VM: Automatic Windows driver support #1863
Comments
The Windows driver ISO link is at https://github.com/virtio-win/virtio-win-pkg-scripts/blob/master/README.md The direct link from that document is https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/stable-virtio/virtio-win.iso (for the stable version; there is a "latest" version too, which I guess is probably built from the main branch). There's also an EXE @ https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/latest-virtio/virtio-win-guest-tools.exe We could download (then cache for future VMs) and auto-mount the ISO when creating a Windows VM. Or we could copy the EXE into the Windows VM, like to the Desktop so it's easy to see, perhaps. The ISO one feels like that'd be more possible and less fragile. However, the EXE is 29 MB whereas the ISO is 692 MB, so if we can use the EXE, that'd be better. |
Reference for the steps required |
The Windows drivers I was talking about were more to make the graphics adaptable (so it resizes to the available size) than to have transparent desktop sharing. Adding the ISO as a disk that's mounted is likely possible, and copying the EXE (which is smaller in filesize than the ISO) over to the desktop or something like that is probably possible too. "WinFSB" is probably out of scope, but anything simple that can be done to make it easier or at least not get in the way of doing things like that would be good, of course. |
Originally posted by @Betonhaus in #680 (comment)
The text was updated successfully, but these errors were encountered: