Package Details: virtio-win 0.1.217.1-1

Git Clone URL: https://aur.archlinux.org/virtio-win.git (read-only, click to copy)
Package Base: virtio-win
Description: virtio drivers for Windows 7 and newer guests
Upstream URL: https://docs.fedoraproject.org/en-US/quick-docs/creating-windows-virtual-machines-using-virtio-drivers/index.html
Keywords: images iso qemu windows
Licenses: BSD-3-Clause
Submitter: jetm
Maintainer: jetm
Last Packager: jetm
Votes: 80
Popularity: 2.92
First Submitted: 2015-08-12 23:17 (UTC)
Last Updated: 2022-04-18 15:08 (UTC)

Pinned Comments

jetm commented on 2021-07-02 17:04 (UTC)

After the virtio-win 0.1.196 update, note these two changes:

  • ISO image is copied at /var/lib/libvirt/images

  • The Windows XP floppies are not distributed anymore as upstream remove the support

Latest Comments

solsticedhiver commented on 2022-01-27 20:43 (UTC)

virt-v2v expects virtio-win drivers (the iso is prefered) to be in /usr/share/virtio-win

The package could install a symlink towards the iso, there too ?

Note: I just created virt-v2v package and would like to include virtio-win as optdepends

softwarerat commented on 2021-09-22 14:09 (UTC)

@SamLukeYes I am aware that it's not included in upstream anymore, but i my opinion, you should download XP floppies from the last version where it was still available (0.1.190).

SamLukeYes commented on 2021-09-22 01:03 (UTC)

@softwarerat It is upstream that doesn't distribute XP floppies any more. If you want those floppies, you can simply download them from the release archive.

softwarerat commented on 2021-09-21 17:22 (UTC)

Please add Windows XP floppies again

jetm commented on 2021-08-28 18:46 (UTC)

@thisischrys Do you know this is voluntary work that is based on collaboration from others? Instead of being rude, could you be more helpful by providing which Windows versions are supported?

thisischrys commented on 2021-08-28 18:39 (UTC)

Older windows versions are not supported, please adjust Description accordingly to avoid wasting people's time.

jetm commented on 2021-07-02 17:04 (UTC)

After the virtio-win 0.1.196 update, note these two changes:

  • ISO image is copied at /var/lib/libvirt/images

  • The Windows XP floppies are not distributed anymore as upstream remove the support

chiphead commented on 2021-07-02 08:42 (UTC)

Is this supposed to be the stable or the latest? version does not match either.

shaybox commented on 2021-06-12 21:49 (UTC)

the images should probably be installed into the default image directory /var/lib/libvirt/images not a random directory

miss_barfin commented on 2020-10-12 10:51 (UTC) (edited on 2020-10-12 10:52 (UTC) by miss_barfin)

@ph3nix you should probably use "spice-guest-tools-windows" package for older than windows 8 oses

ph3nix commented on 2020-10-02 17:55 (UTC)

Either the package is broken or the description is inaccurate. Inserting the iso into a Windows 7 machine and trying to install fails with:

OS must be Windows 8, Windows Server 2012 or higher.

It seems like fedora dropped Windows 7 support? Which would seem odd because they still distribute Windows XP floppies. Not sure what is going on or where to report this issue.

jetm commented on 2020-02-01 01:55 (UTC)

@yan12125 Updated the license. Thanks!

yan12125 commented on 2020-01-31 10:06 (UTC)

Are those binaries are licensed under GPL2? From virtio-win_license.txt in virtio-win.iso, those files look like to be licensed with 3-clause BSD.

jetm commented on 2018-11-27 21:13 (UTC)

@dreieck: Thank you for the new URL. I have updated the package with the new URL.

dreieck commented on 2018-11-27 19:10 (UTC)

Please update the url to url=<https://docs.fedoraproject.org/en-US/quick-docs/creating-windows-virtual-machines-using-virtio-drivers/index.html>.

The current setting <https://fedoraproject.org/wiki/Windows_Virtio_Drivers> says

This page has been moved to /en-US/quick-docs/creating-windows-virtual-machines-using-virtio-drivers/index.html. You are encouraged to update your bookmark or link. You will automatically be redirected in 5 seconds.

commented on 2017-07-21 12:08 (UTC)

Can't get full memory stats from ballooning driver. Any suggestions? Yeah, I already set the statistics period, but: [code] virsh # qemu-monitor-command win7 '{ "execute": "qom-get", "arguments": { "path": "/machine/peripheral/balloon0", "property": "guest-stats" } }' {"return":{"stats":{"stat-swap-out":-1,"stat-available-memory":-1,"stat-free-memory":-1,"stat-minor-faults":-1,"stat-major-faults":-1,"stat-total-memory":-1,"stat-swap-in":-1},"last-update":1500637658},"id":"libvirt-471"} [/code]

jetm commented on 2017-01-18 01:36 (UTC)

Hi @eworm, @jevv and @TingPing: I uploaded a new revision that joins the version to the source filenames. It will avoid issues with makepkg and pacaur. The installation is kept unversioned to take advantage of what @jevv explained. Thank you all for the suggestion, feedback, and clarification. Much appreciated.

je-vv commented on 2017-01-18 00:34 (UTC)

understood! :-)

TingPing commented on 2017-01-17 23:17 (UTC)

@jevv You can install it unversioned, the point of downloading it versioned is so makepkg can handle updates sanely.

je-vv commented on 2017-01-17 23:15 (UTC)

I don't see a problem by not naming the iso with its version on the unpacked SW. You will notice version changes when updating any ways... See, if you have the iso always mounted on the win guest, then it's pretty convenient to have it always named the same way. But beyond that, what purpose would it serve, if any ways one will get only one iso at a time, and if in need to know the version pacman -Qs will provide the answer? If the maintainer decides to go that way, I'd suggest keeping a link from the versioned iso to a non versioned link that needs no change every time there's a new version available.

eworm commented on 2017-01-17 21:53 (UTC)

Please update the source array from: source=("${_url}/${pkgname}-${_pkgver}/${pkgname}.iso" ... to: source=("${pkgname}-${_pkgver}.iso::${_url}/${pkgname}-${_pkgver}/${pkgname}.iso" ... That saves the source files with version in filename and makes sure new versions are downloaded properly.

gps1539 commented on 2016-06-26 18:51 (UTC)

Thanks jetm, I was using pacaur. Removing the previous binaries solved the issue.

jetm commented on 2016-06-18 17:11 (UTC)

I could reproduce this issue by using pacaur, but I could solve it. If pacaur is used, remove the previous binary files under ~/.cache/virtio-win directory and build again: rm -rf /home/javier/.cache/pacaur/virtio-win pacaur -S virtio-win

severach commented on 2016-06-18 05:16 (UTC)

Delete those files in your build folder so they get downloaded again. Yaourt works because it doesn't save anything.

jetm commented on 2016-06-17 22:48 (UTC)

Hello gps1539, I installed with yaourt and I didn't got this error. What are you using for AUR to install virtio-win?

gps1539 commented on 2016-06-17 22:42 (UTC)

failing to validate sha256sums Validating source files with sha256sums... virtio-win.iso ... FAILED virtio-win_amd64.vfd ... FAILED virtio-win_x86.vfd ... FAILED ==> ERROR: One or more files did not pass the validity check!

jetm commented on 2016-06-16 21:58 (UTC)

Bump up virtio-win 0.1.118-2. Changelog: - Update to qemu-ga-win-7.3.2-1

jetm commented on 2016-06-06 19:22 (UTC) (edited on 2016-06-16 21:57 (UTC) by jetm)

Bump up virtio-win 0.1.118-1. Changelog: - Update to virtio-win-prewhql-0.1-118 - BZ#1293249: Fix IOCTL_GET_INFORMATION regression - Enable RSC - Fix IPv6 offload support with SLIRP - Fix MPE HCK test problems

jetm commented on 2016-05-13 15:46 (UTC)

@TingPing: Thanks for the feedback. I will remove the install file for next virtio-win release.

TingPing commented on 2016-05-13 06:57 (UTC)

You should probably remove the install file; It does nothing of use and it just adds extra work on users to audit each update. Surely they know how to use their package manager to see what files a package contains.

jetm commented on 2016-04-12 23:35 (UTC)

Bump up virtion-win 0.1.117. Changelog: - Update to virtio-win-prewhql-0.1-117 - Bug 1321903 [vioscsi] Windows 10 Installer stuck at Getting files ready for installation with Virtio SCSI - Trying out the new build system. - vioserial - code rework and cleanup - General - switching signing back to SHA-1

jetm commented on 2016-03-24 14:50 (UTC)

From virtion-win 0.1.113 Windows 10 drivers were put in .vfd images. It has been tested and it works fine with Windows 10.

jetm commented on 2015-12-23 15:25 (UTC) (edited on 2015-12-25 13:58 (UTC) by jetm)

Bump up virtio-win 0.1.112.1-1. Changelog: - Update to virtio-win-prewhql-0.1-112 - BZ 1284769: [viostor] Windows XP installer stucks installing with virtio-drivers - BZ 1245957: [viostor] [WHQL][viostor][data-plane]it could not generate dump file on WIN2008-32/64 via WLK while running Crash Dump job - BZ 1289406: [vioser] Cannot install vioser driver successfully Thanks @DonOregano for letting me know. I still have not found a proper way to know when a new virtio-win release came out.

jetm commented on 2015-10-15 13:53 (UTC)

Bump up virtio-win 0.1.110.2-1. To see changelog: $ pacman -Qc virtio-win

severach commented on 2015-09-14 07:36 (UTC)

Upstream version checking is available in my git-aurcheck (AUR).

jetm commented on 2015-09-13 14:48 (UTC)

@melvinvermeeren thanks! Package updated. I have been looking for a way to know when a new version has been released. If you know, let me know and I will try to update quicker.

melvinvermeeren commented on 2015-09-13 09:29 (UTC)

Looks like 0.1.109-2 is out. - Update to qemu-ga-win-7.2.1-1 Thanks!

jetm commented on 2015-08-24 00:01 (UTC) (edited on 2016-04-12 23:36 (UTC) by jetm)

Bump up virtio-win 0.1.109.1-7. One change: - Change qemu as optional dependency, instead of a required dependency. @argymeg: thank you for suggestion.

argymeg commented on 2015-08-23 00:34 (UTC)

I don't think qemu should be listed as a dependency, the drivers work fine with VirtualBox guests.

jetm commented on 2015-08-14 16:27 (UTC)

Bump from revision 1 to 6. These are the changes: * Change license to GPL2. * Add virtio-win changelog. To see virtio changelog use: pacman -Qc virtio-win * Add post install message to show where are image installed. * Change architecture to any. * Reduce build time by no extracting images files.

jetm commented on 2015-08-13 16:00 (UTC)

@melvinvermeeren: You're welcome!

melvinvermeeren commented on 2015-08-13 15:45 (UTC)

Thanks a lot for maintaining this, makes running the latest driver much easier!