You are correct, in this Dockerfile, I am building the latest code from git. Add the following line after the git clone if you want to use a specific version:
RUN cd fio && git checkout tags/fio-3.11
Or whatever tagged version you think is best :)
Regards,
Mark
Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
Mark.Beierl@xxxxxxxx
On 2018-10-11, 15:28, "Eliezer Nebab" <eliezer@integritech.solutions> wrote:
[EXTERNAL EMAIL]
Please report any suspicious attachments, links, or requests for sensitive information.
Excellent update to this thread.
Thanks Sitsofe and Mark!
I’ll try this and hope to be able to run fio the way you outlined. I see youre also using latest version 3.11.
I hope to update this thread with some good news. If I could get this working, it will address a lot of performance questions from admins that are on ESXi environments.
Regards,
Eliezer
> On Oct 11, 2018, at 8:42 AM, Beierl, Mark <Mark.Beierl@xxxxxxxx> wrote:
>
> Hey all, and special thanks to Sitsofe for pointing me at the github fio issue 464.
>
> I have fio working on my ESXi 6.5 server. Here is the procedure I used. Install Docker and use this Dockerfile:
>
> =============================
> FROM multiarch/alpine:x86_64-v3.6
>
> RUN apk --no-cache add --update \
> git \
> alpine-sdk \
> coreutils \
> linux-headers \
> libaio \
> libaio-dev \
> zlib-dev
>
> RUN git config --global http.sslVerify false
> RUN git clone http://git.kernel.dk/fio.git fio
> RUN cd fio && ./configure --esx
> RUN cd fio && EXTFLAGS="-static" make -j $(grep -c ^processor /proc/cpuinfo) install
> =============================
>
> Then, start the docker container with a dummy command (I’m sure there are better ways to do this, but it works, so hey)
> $ docker run -d fio sleep 600
>
> Note the ID that it spits out. Use that ID in the next command:
> $ docker cp 69e64de38659d350fb07e45b5d7d2d4098c642ec1ca81a6eb18a9b34e622082f:/fio/fio .
>
> You can now scp that fio to your ESXi server and execute it there.
>
> [root@R156U37ESXI:/vmfs/volumes/5a611782-2d14bf65-c453-246e96146f88/testdir] ~/fio test.fio
> file1: (g=0): rw=randrw, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, ioengine=psync, iodepth=16
> fio-3.11-6-gee6ce
> Starting 1 thread
> file1: Laying out IO file (1 file / 1024MiB)
> Jobs: 1 (f=1): [f(1)][100.0%][r=1346KiB/s,w=899KiB/s][r=336,w=224 IOPS][eta 00m:00s]
> ....
>
> Hope this works for you, Eliezer!
>
> Regards,
> Mark
>
> Mark Beierl
> SW System Sr Principal Developer
> Dell EMC | Cloud & Communication Service Provider Solution
> Mark.Beierl@xxxxxxxx
>
> On 2018-10-11, 01:34, "Sitsofe Wheeler" <sitsofe@xxxxxxxxx> wrote:
>
>
> [EXTERNAL EMAIL]
> Please report any suspicious attachments, links, or requests for sensitive information.
>
>
> Hi,
>
> The question of how to compile fio for ESXi comes up every few years
> and as Mark suggested it IS doable by building a static fio binary
> from an appropriate real distro but there are a few gotchas. You can't
> take a "regular" distro's fio because the ESXi environment simply
> doesn't match that of the regular distro (for example things like a
> glibc are compiled with different options, libraries are missing etc).
>
> The last time it was asked about was over on Github (see
> https://github.com/axboe/fio/issues/464 ) where I mentioned the steps
> I used to get it going for ESXi 6.0 but note that I no longer have
> access to ESXi these days so I can't say what's needed for modern
> environments (but the general idea should be the same).
>
>> On Wed, 10 Oct 2018 at 21:00, Beierl, Mark <Mark.Beierl@xxxxxxxx> wrote:
>>
>> Ya, sorry I could not be of more help.
>>
>> I doubt that FIO could be compiled on raw ESXi as there is no compiler available on that from what I can tell. A statically linked one should work, but I really don’t know enough to be able to say why it could not start a job.
>>
>> I do know that ESXi can pass a full device (raw disk) to a VM and that VM takes full ownership of it. So you could load a VM with CentOS or something and have FIO profile the raw device, but that is probably not going to be useful. Chances are you are looking to something a little more advanced like profile vSAN or some other form of software defined storage?
>>
>> Regards,
>> Mark
>>
>> Mark Beierl
>> SW System Sr Principal Developer
>> Dell EMC | Cloud & Communication Service Provider Solution
>> Mark.Beierl@xxxxxxxx
>>
>> On 2018-10-10, 15:56, "Eliezer Nebab" <eliezer@integritech.solutions> wrote:
>>
>>
>> [EXTERNAL EMAIL]
>> Please report any suspicious attachments, links, or requests for sensitive information.
>>
>>
>> Thanks for the quick response Mark.
>>
>> Yes, I was looking for documentation or guide on if fio can be compiled or installed on esxi servers.
>>
>> From your response it looks like (compile or precompiled) neither works.
>>
>> Thank you.
>>
>> Eliezer
>>
>>
>>> On Oct 10, 2018, at 2:05 PM, Beierl, Mark <Mark.Beierl@xxxxxxxx> wrote:
>>>
>>> Are you asking if FIO can be built or run on the hypervisor itself, like via ssh?
>>>
>>> I have tried a test before where I statically compiled FIO and copied it to an ESXi server, but I was never able to get any jobs to start. Not sure if the kernel supports the fork() or whatever call FIO uses to spawn the job processes. So, I’m not sure it can be done. ESXi is not a general purpose OS, so it lacks some features.
>>>
>>> Regards,
>>> Mark
>>>
>>> Mark Beierl
>>> SW System Sr Principal Developer
>>> Dell EMC | Cloud & Communication Service Provider Solution
>>> Mark.Beierl@xxxxxxxx
>>>
>>> On 2018-10-10, 14:24, "fio-owner@xxxxxxxxxxxxxxx on behalf of eliezer@integritech.solutions" <fio-owner@xxxxxxxxxxxxxxx on behalf of eliezer@integritech.solutions> wrote:
>>>
>>>
>>> [EXTERNAL EMAIL]
>>> Please report any suspicious attachments, links, or requests for sensitive information.
>>>
>>>
>>> Is fio supported on vmware esxi 5 and 6 servers? Does anyone have any
>>> helpful guides as to how to install it on vmware? I've searched google but
>>> could not find any. The only reference to fio+vmware is Disable libaio for
>>> ESXi build - bug#80
>>>
>>> Thank you in advance.
>>>
>>> Regards,
>>> Eliezer
>
> --
> Sitsofe | http://sucs.org/~sits/
>
>
