You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can also install the RPM manually from https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/stable-virtio/virtio-win.noarch.rpm
67
+
rpm -qa | grep -i virtio-win
68
+
ls -l /usr/share/virtio-win
65
69
66
70
67
71
For Debian-based distributions:
68
72
69
-
Ubuntu don’t seem to ship the virtio-win package with drivers, which causes virt-v2v not to convert the VMWare Windows guests to virtio profiles. This could result in slow IDE drives and Intel E1000 NICs. As a workaround, we can follow the below steps to install the package from the RPM on all KVM hosts running the virt-v2v:
73
+
Ubuntu does not always ship a ``virtio-win`` package with the Windows drivers, which causes virt-v2v not to convert
74
+
the VMware Windows guests to virtio profiles. This can result in slow IDE drives and Intel E1000 NICs. As a workaround,
75
+
download the Fedora RPM and convert it to a DEB on all KVM hosts running virt-v2v:
70
76
71
77
::
72
78
73
-
apt install virtio-win (if the package is not available, then manual steps will be required to install the virtio drivers for windows)
In addition to this, we need to install the below package as well to avoid the error “virt-v2v: error: One of rhsrvany.exe or pvvxsvc.exe is missing in /usr/share/virt-tools“.
86
+
In addition to this, install the package below to avoid the error
87
+
``virt-v2v: error: One of rhsrvany.exe or pvvxsvc.exe is missing in /usr/share/virt-tools``.
0 commit comments