Originally Posted by
cjsmall
I installed the virtio-win-0.1.185.iso image and finally figured out how to update all the drivers*. The Ethernet is using the virtio device and Properties is now reporting 10Gbps. When I run a browser speed test, I'm getting around 300Mbps (which is 5-6 times faster than what i was getting before!), vs. another native Windows 10 machine hardwired to my network which gets 900+Mbps which is similar to my Xubuntu machine. Is this the kind of performance I should expect or do you think there is a problem and throughput should be higher than this?
Thanks for pointing me in the right direction regarding these drivers. I don't know why I never ran across this issue before. I didn't even know that upgrading like this was an option!
* It's a shame that this driver installation process cannot be better automated and installed as part of the native VM software. It's not too difficult once you've been through it and look back, but no single set of instructions matched my configuration, so there was a lot of work to do to figure out what was actually being described.
Upgrading like what? I'm confused? Do you mean picking better virtual hardware? That's normal for every hypervisor. The KVM performance tuning website spells out some other things that can be done to improve performance.
On the same physical host, I see 20Gbps+ using virtio drivers.
Code:
$ iperf3 -c hadar
Connecting to host hadar, port 5201
[ 5] local 172.22.22.3 port 35424 connected to 172.22.22.6 port 5201
....
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 27.0 GBytes 23.2 Gbits/sec 0 sender
[ 5] 0.00-10.00 sec 27.0 GBytes 23.2 Gbits/sec receiver
iperf Done.
I've seen 34Gbps when the host wasn't busy. It is transcoding some videos now.
With Windows, drivers are just too much hassle. When there is a boot issue, you'll consider whether using virtio was a smart choice. I sometimes wish I'd gone with PRO/1000 and SCSI drivers instead, because those are built-into Windows. When Windows won't boot, you'll need to load drivers, since MSFT hasn't decided that virtio drivers should be default. Every hypervisor supports them - well, perhaps whatever hypervisor MSFT makes doesn't, but all the others do.
Linux has virtio support built-in and has for 10 yrs or so. It is only a Microsoft OS problem and only Microsoft can fix it. Complain to them. While you are at it, complain that they don't provide ssh-copy-id too! It took them about 20 yrs to support ssh and they left off that tool?
In general, I don't have to install **any** VM specific stuff for my Linux VM systems to fly.
Bookmarks