May 2, 201511 yr As pointed out by another user, the virtio drivers link for Windows based VMs just got updated again and are available for download from the fedora project. I have updated the link inside the wiki, and we will fix the link in the webgui in the next release. I'll update this thread later when I've had more time to read up on all the changes and experiment, but it seems like they've added new driver revisions specific for windows 8.1 amongst other things. The setup process for new VMs will also change a little bit, but nothing too crazy (the drivers are now broken out into folders based on the specific components, then by OS, then by bit architecture). Hope you guys have as much fun playing with new toys like this as I do!!
May 3, 201511 yr I applied the Network and Balloon drivers to both of my VMs. The updated Network driver on my Windows 7 Media Center VM locked it up after a reboot. I had to revert to the previous driver (0.1.100). The scsi driver said it didn't need an update.
May 3, 201511 yr Author I applied the Network and Balloon drivers to both of my VMs. The updated Network driver on my Windows 7 Media Center VM locked it up after a reboot. I had to revert to the previous driver (0.1.100). The scsi driver said it didn't need an update. Which driver version did you end up downloading? They have a stable and latest.
May 3, 201511 yr The wiki page here: https://fedoraproject.org/wiki/Windows_Virtio_Drivers has direct download links populated, which were not there last night when I was poking around... The stable release is 0.1.96. Latest release is going to 0.1.103.
May 3, 201511 yr I was unable to get any network drivers to work except 100 on my Windows 7 Media Center VM. Whenever the xBox 360 Media Extender started with any network drivers except 100, the VM locked up.
May 3, 201511 yr I've been seeing issues with 0.1.96 on W8 (not 8.1) and misc. lockups and VM reboots. Too early to tell if it's related to the virtio drivers or not as I haven't seen anything reproducible.
May 3, 201511 yr Author These are brand new drivers, so I'll need to experiment with them some more to see what's up.
May 4, 201511 yr Author Ok, couple of things on this: 1) When updating to the newer drivers, understand that there are "latest" and "stable" and the latest would be not considered "stable". 2) There are MULTIPLE drivers that will need to be updated. The VirtIO Balloon Driver, the Network Driver, and the Storage Controller driver each need their new versions respectively. 3) There is also a new QEMU Guest Agent which will help improve the ability for libvirt to get information from a running Windows guest and issue commands more natively than with emulation. All of this being said, these drivers are brand new, so until I've had a chance to experiment with them more, we're all kind of "flying blind" here on their actual impact. So far, my Windows 8.1 VM seems absolutely fine.
May 5, 201511 yr Ok, couple of things on this: 1) When updating to the newer drivers, understand that there are "latest" and "stable" and the latest would be not considered "stable". 2) There are MULTIPLE drivers that will need to be updated. The VirtIO Balloon Driver, the Network Driver, and the Storage Controller driver each need their new versions respectively. 3) There is also a new QEMU Guest Agent which will help improve the ability for libvirt to get information from a running Windows guest and issue commands more natively than with emulation. All of this being said, these drivers are brand new, so until I've had a chance to experiment with them more, we're all kind of "flying blind" here on their actual impact. So far, my Windows 8.1 VM seems absolutely fine. I've had success with the latest drivers version .100. I've had trouble with any of the newer latest network drivers with my Windows 7 Media Server VM. Over the weekend I got a Windows 8.1 running with GPU pass through using the latest version .100 drivers.
Archived
This topic is now archived and is closed to further replies.