1/2
Current system is not support virtio" — A vmTools Install Failure Fix That Might Save You an Hour
  

George Fady Lv2Posted 2026-Sep-01 18:45

Hello everyone, I'm George, Technical Support Engineer at Sangfor. Sharing a real troubleshooting case pattern I see often after VM migrations into HCI.
Why vmTools matters:

  • Boosts disk/network I/O by moving hardware emulation down into the hypervisor via virtio paravirtualized drivers (virtio_blk, virtio_net, virtio_balloon)

  • Without it, the platform gets VM telemetry (CPU/memory/IP) indirectly via QEMU rather than directly

  • Hot-add of CPU/memory/disk/NIC only works if vmTools is installed — easy to forget this dependency!

The failure case: After migrating a Linux VM, running the install script throws:

initrd file not find! Current system is not support virtio
Fix path:

  • Check if virtio drivers exist at all: find /usr/lib/ -name *virtio*

  • If they exist, check if they're loaded in the initrd: lsinitrd /boot/initramfs-$(uname -r).img | grep virtio

  • If missing from initrd, back up the current image, then rebuild it with virtio included:


bash
mkinitrd -f --with=virtio_pci --with=virtio_blk --with=virtio_console \   /boot/initramfs-$(uname -r).img $(uname -r)

  • Reboot and reinstall vmTools.

Discussion: Has anyone hit this specific "not support virtio" error on a migrated VM? What OS/kernel version were you on, and did the initrd rebuild fix it for you?

Like this topic? Like it or reward the author.

Creating a topic earns you 5 coins. A featured or excellent topic earns you more coins. What is Coin?

Enter your mobile phone number and company name for better service. Go