--- title: "Check Virtio Win and KVM guest agent (Windows)" slug: "server-ts-kvm-win-vpc" updated: 2026-09-17T09:17:55Z published: 2026-09-17T09:17:55Z canonical: "guide.ncloud-docs.com/server-ts-kvm-win-vpc" --- > ## Documentation Index > Fetch the complete documentation index at: https://guide.ncloud-docs.com/llms.txt > Use this file to discover all available pages before exploring further. # Check Virtio Win and KVM guest agent (Windows) Available in VPC If you have problems installing the agent or the service is not working properly, follow this guide to check and reinstall. ## Check KVM Guest Agent Note - To use the snapshot service in KVM environment, KVM Guest Agent must be installed. - This feature is only available for Windows VMs in a KVM environment. For more information on NTK, see [Check Ncloud Tool Kit (Windows)](/docs/en/server-ts-ntk-win-vpc). ### 1. Check KVM Guest Agent You can verify the KVM Guest Agent installation through the 2 following methods: - Method 1: check *QEMU Guest Agent* installation in Add/Remove programs menu. - Method 2: Check via Windows NTK. Run `C:\windows_ntk\windows_ntk.exe` and check through **VM Tool Status** in the **VM Tool tab**. **Example:** when the KVM Guest Agent is installed and service is running. ``` # Get VM Tool Status KVM Guest Agent is installed [Ok] ``` **Example:** when the KVM Guest Agent is not installed or is abnormal. ``` # Get VM Tool Status KVM Guest Agent is not installed [Not Ok] ``` ### 2. Reinstall KVM Guest Agent You can reinstall the KVM Guest Agent via Windows NTK. 1. If you have run **Diagnosis** by selecting **VM Tool Status** of the **VM Tool** tab, click **Repair** to proceed with reinstallation. If KVM Guest Agent is not installed or recognized as abnormal, reinstallation proceeds. When installation is complete, the following message appears in Repair Result: ``` # Set VM Tool Status KVM Guest Agent has been installed successfully. ``` 2. After installation, verify that **QEMU-GA** and **QEMU Guest Agent VSS Provider** services are created and **QEMU-GA** service is running properly using the following command: ``` PS C:\Users\Administrator\Desktop> Get-Service -Name 'QEMU-GA','QEMU Guest Agent VSS Provider' Status Name DisplayName ------ ---- ----------- Stopped QEMU Guest Agen... QEMU Guest Agent VSS Provider Running QEMU-GA QEMU Guest Agent ``` ### 3. Install KVM Guest Agent manually If you want to manually install KVM Guest Agent or if reinstallation through Windows NTK fails, you can install manually as follows: 1. Download the installation file. ``` # Download the latest version of KVM Guest Agent. Start-BitsTransfer -Source "http://init.ncloud.com/windows/virtio/qemu-ga-x86_64-latest.msi" -Destination "c:\qemu-ga-x86_64-latest.msi" ``` - Method 1: check the KVM Guest Agent information and download through [fedorapeople.org](https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-qemu-ga/). - Method 2: download the Guest Agent installation file through repo provided by NAVER Cloud Platform. 2. Run the downloaded file to proceed with installation. 3. After installation, verify that the **QEMU-GA** service is running properly using the following command: ``` PS C:\Users\Administrator\Desktop> Get-Service -Name QEMU-GA Status Name DisplayName ------ ---- ----------- Running QEMU-GA QEMU Guest Agent ``` ## Check Virtio Win Driver Caution - When removing the Virtio Win Driver, be aware that the network is not recognized. - Network may be disconnected during Virtio Win Driver reinstallation. - Before proceeding, create My server image or snapshot for backup. For more information, see [Server Image](/docs/en/server-serverimage-vpc) or [Snapshot](/docs/en/server-snapshot-create-vpc). ### 1. Check Virtio Win Driver You can verify the Virtio Win Driver installation through the 2 following methods: - Method 1: check *Virtio-win-driver-installer* installation in Add/Remove programs menu. - Method 2: Check via Windows NTK. Run `C:\windows_ntk\windows_ntk.exe` and check installation through the **VM Tool Status** feature in the **VM Tool tab**. **Example:** Virtio Win Driver version 0.1.240 result. ``` # Get VM Tool Status Virtio-win-driver-installer : 0.1.240 is installed [Ok] ``` ### 2. Download Virtio Win Driver file To upgrade to a new version of Virtio Win Driver, you can download the installation file through the 2 following methods: - Method 1: check Virtio Win Driver information and download through [fedorapeople.org](https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/). - Method 2: download the Virtio Win Driver installation file through a repo on NAVER Cloud Platform. ``` # Download the latest version of Virtio Win Driver Start-BitsTransfer -Source "http://init.ncloud.com/windows/virtio/virtio-win-latest.msi" -Destination "c:\virtio-win-latest.msi" ``` ### 3. Run Virtio Win Driver file Run the downloaded file to proceed with installation. - Server reboot is required during installation. When the popup window appears for confirmation, click **Yes** only if you can reboot the server. - If reboot is not possible, click **No** and complete the driver installation by rebooting when possible. - Reboot popup may not appear depending on the version. Installation is complete only after rebooting. ### 4. Run routing rule script Internal routing rules may disappear when you reinstall Virtio Win Driver. To set internal routing rules again, download and run the following execution files: ``` # Download routing rule script Start-BitsTransfer -Source "http://init.ncloud.com/windows/virtio/staticRoutekvm.exe" -Destination "c:\staticRoutekvm.exe" ``` Enter the `route print` command in CMD to verify that the routing rules for **169.254.0.0/16** are properly included in Persistent Routes and Active Routes. ``` C:\Users\Administrator> route print =========================================================================== Interface List 22...f2 20 af 08 ee bf ......Red Hat VirtIO Ethernet Adapter #2 26...f2 20 af a5 66 a1 ......Red Hat VirtIO Ethernet Adapter #3 1...........................Software Loopback Interface 1 =========================================================================== IPv4 Route Table =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 10.0.1.1 10.0.1.8 15 10.0.1.0 255.255.255.0 On-link 10.0.1.8 271 10.0.1.8 255.255.255.255 On-link 10.0.1.8 271 10.0.1.255 255.255.255.255 On-link 10.0.1.8 271 10.0.4.0 255.255.255.0 On-link 10.0.4.9 271 10.0.4.9 255.255.255.255 On-link 10.0.4.9 271 10.0.4.255 255.255.255.255 On-link 10.0.4.9 271 127.0.0.0 255.0.0.0 On-link 127.0.0.1 331 127.0.0.1 255.255.255.255 On-link 127.0.0.1 331 127.255.255.255 255.255.255.255 On-link 127.0.0.1 331 169.254.0.0 255.255.0.0 10.0.1.1 10.0.1.8 271 224.0.0.0 240.0.0.0 On-link 127.0.0.1 331 224.0.0.0 240.0.0.0 On-link 10.0.4.9 271 224.0.0.0 240.0.0.0 On-link 10.0.1.8 271 255.255.255.255 255.255.255.255 On-link 127.0.0.1 331 255.255.255.255 255.255.255.255 On-link 10.0.4.9 271 255.255.255.255 255.255.255.255 On-link 10.0.1.8 271 =========================================================================== Persistent Routes: Network Address Netmask Gateway Address Metric 169.254.0.0 255.255.0.0 10.0.1.1 Default =========================================================================== ```