mirror of
git://code.qt.io/qt/qt5.git
synced 2026-04-25 22:27:49 +08:00
a1358676d3
MSVC 2019 version 16.6.2
MSVC 2019 Build Tools version 16.6.2
Virtio driver
Virtio Balloon driver
NetKVM driver
Task-number: QTQAINFRA-3818
Task-number: QTQAINFRA-3817
Change-Id: Id0edee66d4eb42730a70495dbb063a0d379f026c
Reviewed-by: Toni Saario <toni.saario@qt.io>
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
(cherry picked from commit ba4eb4929e)
Reviewed-by: Tony Sarajärvi <tony.sarajarvi@qt.io>
28 lines
1.3 KiB
Plaintext
28 lines
1.3 KiB
Plaintext
Install virtio
|
|
|
|
Our vanilla images are pre-installed in VMware where we have networking available. In KVM we can
|
|
use the VMware installed vmxnet3 NIC to fetch VirtIO drivers, install them, and only then switch
|
|
to using the VirtIO NIC in KVM.
|
|
|
|
* Download https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/stable-virtio/virtio-win-0.1.171.iso
|
|
* Mount virtio-win-0.1.171.iso by double clicking it.
|
|
* Right click 'E:\NetKVM\w10\amd64\netkvm.inf' and select Install
|
|
* Right click 'E:\Balloon\w10\amd64\balloon.inf' and select Install
|
|
|
|
* Right click 'E:\vioscsi\w10\amd64\vioscsi.inf' and select Install
|
|
|
|
Because vioscsi does not install the entries in windows registry before we actually
|
|
have a VirtIO device installed, and we can't boot with a VirtIO device before
|
|
the driver is installed, we have to blindly install the registry entries:
|
|
|
|
* Download https://bugreports.qt.io/secure/attachment/95685/95685_vioscsi.reg
|
|
|
|
However, we've seen that the Owner in the registry can be wrong. This entry
|
|
sets it to oem11.inf, but we've seen it be oem10.inf in one case and it has
|
|
to be corrected so that it will boot from the VirtIO driver. This was found out
|
|
by having 2 devices installed simultaneously and having the drivers install
|
|
properly into the registry.
|
|
|
|
* Eject the mounting
|
|
* Remove downloaded virtio-win-0.1.171.iso
|