Package Details: virtio-win 0.1.266.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: 108
Popularity: 2.84
First Submitted: 2015-08-12 23:17 (UTC)
Last Updated: 2024-11-19 16:16 (UTC)

Dependencies (1)

Required by (1)

Sources (1)

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

« First ‹ Previous 1 2 3 4 5 Next › Last »

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!

« First ‹ Previous 1 2 3 4 5 Next › Last »