[SOLVED] fio crashes on windows with virtio driver

[oz1cw7yymn]

Hi,

I am trying to run fio [1] in a windows server 2019 guest with the redhat virtio scsi pass-through driver. As soon as I run fio.exe it crashes and the event logger says this:

Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program fio.exe because of this error. Event ID 1005

Is this a known limitation? I've "googled" [2] trying to find anything about this without success.

[1] fio 3.20 from https://bsdio.com/fio/
[2] "duckduckgoing?"

 

[wolfgang]

Hi,

no this should normally work.
Which parameter do you use with fio.
What virtio driver version do you use?

 

[oz1cw7yymn]

Hi,

fio crashes even without any parameters (should show the help)

I'm using the virtio-win-0.1.171.iso. The device manager says version 100.77.007.17100 from 2019-04-12

 

[wolfgang]

fio crashes even without any parameters (should show the help)

then this is a fio binary problem and not blk driver problem.

 

[oz1cw7yymn]

I've now tried with the latest testing virtio (0.1.185) as well, same appcrash in the event log.

The same fio binary works on a bare metal win10 machine as well as a windows server hyper-v virtual machine.

I've now also tried booting the machine with the block device attached as IDE, SATA, VirtIO Block (didn't boot) in addition to VirtIO SCSI.

I've also tried with both powershell and cmd.

¯\_(ツ)_/¯

 

[wolfgang]

The binary corruption can occur are the copy process.
Compare the checksum of the working and the nonworking fio binary.

 

[oz1cw7yymn]

I tried (i) a new copy, (ii) installing it with the msi and (iii) running the exact same binary from the network share of the win10 client where it works.

I've also installed a new win10 client on pve using i440fx, an ide disk, rtl8139 network device and the hdd is on local-lvm. I've copied over fio, run it, it takes a few seconds and then I'm returned to the command line. In the event viewer, windows logs, application, I see an event id 1001, APPCRASH for fio.exe.

In other words, I get the same behaviour with different fio binaries but also without the virtio drivers. Another one of those frustrating mysteries.

 

[wolfgang]

I have tested it yesterday and it worked without any problems.
I downloaded the binaries from https://bsdio.com/fio/ in the current version 3.20

 

[oz1cw7yymn]

I'm so sorry, I've re-downloaded the file again and now it does work. Even though the same binary worked on bare metal and hyper-v machines, whatever corruption had happened crashed the app on two qemu machines. Very strange but problem is solved, thank you!