Hot answers tagged virtio
KVM provides paravirtualization drivers for several bits of hardware; this particular one is the memory balloon driver. In particular, you should see virtio_net when using the virtio network drivers, and virtio_blk when using the block device (disk) driver. And in the latter case, your disk would be /dev/vda instead of /dev/sda. In your case, the virtio ...
As you can see you have: CONFIG_VIRTIO_BALLOON=m It means it is compiled as a module, hence visible via lsmod. Furthermore, you have: CONFIG_VIRTIO_BLK=y CONFIG_VIRTIO_NET=y It means that they are compiled within the kernel, hence lsmod does not report them. So your guest has the virtio drivers for: blk: block devices, aka disks; net: network ...
The virtio drivers are meant to provide paravirtualized hardware (acceleration) device drivers to virtual machine guests. As such, they are device drivers that are installed in the guest operating system, not on the host. You can find the virtio drivers for Windows from the KVM web site.
Yes, you can download the drivers from the upstream KVM project.
As @Michael Hampton pointed out, you can download the drivers from the offsite. The RPM is just a wrapper around a set of .vfd and .iso files, containing the drivers, it doesn't do anything on the host besides copying those files so they are available. In short, you don't really need the RPM.
Only top voted, non community-wiki answers of a minimum length are eligible