Scanning for new disks attached using virtio

I'd like to start with a note that you should avoid using virsh attach-disk with its limited amount of options. Instead, I'd suggest to specify the exact disk format you prefer in a separate, temporary XML file or by using the virt-manager GUI application (for the latter, skip the first step).

1. Create a temporary file with a disk definition like this one below.

   adjust the properties to fit your situation

   <disk type='file' device='disk'>
     <driver name='qemu' type='qcow2'/>
     <source file='/path/to/disk-image.img'/>
     <target dev='vdb' bus='virtio'/>
   </disk>
   

   Tip: Peek into your current XML domain configuration and copy a <disk> section from there.

   virsh dumpxml <domainname>
   

2. Now, before adding the disk to a current domain, make sure the required hotplug kernel modules are loaded in the guest.

   Some Linux distributions like recent CentOS/RHEL/Fedora have this built-in in the kernel. In this case, check for CONFIG_HOTPLUG_PCI_ACPI. If it's y, then you're all set and you can skip this step.

   modprobe acpiphp
   modprobe pci_hotplug
   

   Consider adding these two modules to /etc/modules if you want them to be loaded on boot by default.

3. Add the disk it to the running VM using

   virsh attach-device <domain name> /path/to/disk.xml
   

   Optionally, add the --persistent option to let Libvirt update the domain XML definition 'persistent'.

4. Finally, check inside the guest if the disk was indeed hotplug-inserted. The kernel should be triggered, as can be checked with dmesg:

   [  321.946440] virtio-pci 0000:00:06.0: using default PCI settings
   [...]
   [  321.952782]  vdb: vdb1 vdb2
   

   In the above example I've added a disk as vdb with two partitions in the partition table.

References

• Linux-KVM wiki - Using PCI Hotplug Support
• similar question "Adding Virtio block devices at runtime in Libvirt KVM"

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 disk and network drivers are compiled into the kernel, rather than as modules, so you would not see them with lsmod.

CONFIG_VIRTIO_BLK=y
CONFIG_VIRTIO_NET=y

Several other less important virtio drivers also exist on your system and are compiled directly into the kernel (such as VIRTIO_PCI, the paravirtualized PCI bus).