VMware Cloud Community
AlaskanGeek
Contributor
Contributor
Jump to solution

Modifing ESXi

I have a Promise Fasttrack TX-4310 RAID SATA card.

How do I add support so ESXi will use this card?

The PCI ID is 105a for vendor and 3515 for device.

Now I followed this

Using the USB method...so what do I enter into the simple.map, pci.ids, and the oem.tzg?

I want to learn, and I want to conquor this. Smiley Happy

Thanks.

Reply
0 Kudos
1 Solution

Accepted Solutions
Dave_Mishchenko
Immortal
Immortal
Jump to solution

In simple.map you would add this line -

105a:3515 0000:0000 storage sata_promise

and in pci.ids you would add something like the below in the 105a Promise Technology, Inc. section -

3515 Promise Fasttrack TX-4310

The pci.ids file just determines what will be displayed in the VI client so that could be 3515 Bob's Your Uncle and it would be OK. The important entry is in simple..map as that instructs ESXi on which driver to load. And on that thought, this method only works if the sata_promise driver will work with TX-4310. If the controller uses a different driver than the rest of the models that ESXi will recognize, then you would have to wait for an updated driver which would have to come from VMware / Promise (or if you can develop drivers then you could potentially create your own).

View solution in original post

Reply
0 Kudos
5 Replies
Dave_Mishchenko
Immortal
Immortal
Jump to solution

In simple.map you would add this line -

105a:3515 0000:0000 storage sata_promise

and in pci.ids you would add something like the below in the 105a Promise Technology, Inc. section -

3515 Promise Fasttrack TX-4310

The pci.ids file just determines what will be displayed in the VI client so that could be 3515 Bob's Your Uncle and it would be OK. The important entry is in simple..map as that instructs ESXi on which driver to load. And on that thought, this method only works if the sata_promise driver will work with TX-4310. If the controller uses a different driver than the rest of the models that ESXi will recognize, then you would have to wait for an updated driver which would have to come from VMware / Promise (or if you can develop drivers then you could potentially create your own).

Reply
0 Kudos
AlaskanGeek
Contributor
Contributor
Jump to solution

Thanks!

Yep, I will have to wait for drivers to be released, but now I understand how to make the modifications.

Thanks again.

Reply
0 Kudos
joluinfante
Contributor
Contributor
Jump to solution

Hi!

This solution is not working.

When I did load the module (sata_promise.o) I can see this messages in /var/log/messages:

Dec 6 14:54:13 vmkernel: 0:00:00:16.316 cpu0:1244)Mod: 936: Starting load for module: sata_promise R/O length...

Dec 6 14:54:13 vmkernel: 0:00:00:16.525 cpu0:1244)Mod: 1373: Module sata_promise: initFunc: ....

Dec 6 14:54:13 vmkernel: 0:00:00:16.526 cpu0:1244)Mod: 1389: modLoaderHeap avail before:...

Dec 6 14:54:13 vmkernel: 0:00:00:16.526 cpu0:1244)Initial heap size : 1048576, max heap size: ...

Dec 6 14:54:13 vmkernel: 0:00:00:16.526 cpu0:1244)<7>libata version 1.20 loaded

Dec 6 14:54:12 vmkernel: 0:00:00:11.402 cpu0:1237)PCI: driver Promise IDE is looking for devices

Dec 6 14:54:12 vmkernel: 0:00:00:11.402 cpu0:1237)PCI: Trying 00:02.0

Dec 6 14:54:12 vmkernel: 0:00:00:11.402 cpu0:1237)PCI: Announcing 00:02.0

Dec 6 14:54:12 vmkernel: 0:00:00:11.402 cpu0:1237)PCI: Trying 00:1d.0

Dec 6 14:54:12 vmkernel: 0:00:00:11.402 cpu0:1237)PCI: Trying 00:1d.1

Dec 6 14:54:12 vmkernel: 0:00:00:11.402 cpu0:1237)PCI: Trying 00:1d.7

Dec 6 14:54:12 vmkernel: 0:00:00:11.402 cpu0:1237)PCI: Trying 00:1f.1

Dec 6 14:54:12 vmkernel: 0:00:00:11.402 cpu0:1237)PCI: Trying 02:04.0

Dec 6 14:54:12 vmkernel: 0:00:00:11.402 cpu0:1237)PCI: Announcing 02:04.0

Dec 6 14:54:12 vmkernel: 0:00:00:11.403 cpu0:1237)PCI: Trying 03:07.0

Dec 6 14:54:12 vmkernel: 0:00:00:11.403 cpu0:1237)PCI: Announcing 03:07.0

Dec 6 14:54:12 vmkernel: 0:00:00:11.403 cpu0:1237)PCI: Trying 04:03.0

Dec 6 14:54:12 vmkernel: 0:00:00:11.403 cpu0:1237)PCI: Trying 04:0d.0

Dec 6 14:54:12 vmkernel: 0:00:00:11.403 cpu0:1237)PCI: Announcing 04:0d.0

Dec 6 14:54:12 vmkernel: 0:00:00:11.403 cpu0:1237)PCI: driver Promise IDE claimed 0 device

I'm thinking we have a problem with chipset of 4310.

The solution is recompile the sources in VMware-eesx-drivers-public-source-3.5.0-xxxxx.tar.gz

But, I can't to do the build-vmdkdrivers.sh, because I have a lot of errors messages. I'm think I need a specific platform to do the compile.

I did try with a rhel4. Do you have information about the correct environment?

TIA

jorge infante

rosario - santa fe - argentina

Reply
0 Kudos
joluinfante
Contributor
Contributor
Jump to solution

Hi!

More feedback:

In a rhel4 smp machine, the errors are:

development VMware-esx-drivers-public-source-3.5.0-103909> sh ./build-vmkdrivers.sh 2>&1| more

    • Compiling drivers/block/cciss/cciss.c

In file included from src/include/linux/module.h:11,

from src/drivers/block/cciss/cciss.c:24:

src/include/linux/spinlock.h:124: error: syntax error before '*' token <--- This error, because we don't have a spinlock_t definition

src/include/linux/spinlock.h: In function `vmk_spin_is_locked_by_my_cpu':

src/include/linux/spinlock.h:126: error: `lock' undeclared (first use in this fu

nction)

src/include/linux/spinlock.h:126: error: (Each undeclared identifier is reported

only once

src/include/linux/spinlock.h:126: error: for each function it appears in.)

In file included from src/include/linux/module.h:11,

from src/drivers/block/cciss/cciss.c:24:

src/include/linux/spinlock.h: At top level:

src/include/linux/spinlock.h:230: error: syntax error before "spinlock_t"

In file included from src/include/linux/module.h:11,

from src/drivers/block/cciss/cciss.c:24:

In a suse9 smp machine:

umbriel:/tmp/vmware/VMware-esx-drivers-public-source-3.5.0-103909 # sh ./build-vmkdrivers.sh 2>&1 | more

    • Compiling drivers/block/cciss/cciss.c

In file included from src/include/linux/spinlock.h:113,

from src/include/linux/module.h:11,

from src/drivers/block/cciss/cciss.c:24:

/usr/include/asm/spinlock.h:10: error: syntax error before "int"

In file included from src/include/linux/module.h:11,

from src/drivers/block/cciss/cciss.c:24:

src/include/linux/spinlock.h: In function `vmk_spin_is_locked_by_my_cpu':

src/include/linux/spinlock.h:126: error: structure has no member named `cpu'

In file included from /usr/include/asm/math_emu.h:4,

from /usr/include/asm/processor.h:13,

from src/include/linux/prefetch.h:13,

from src/include/linux/list.h:6,

from src/include/linux/module.h:12,

from src/drivers/block/cciss/cciss.c:24:

Can any person help me with the operating system for the compilation?

TIA

jorge infante

Reply
0 Kudos
nka
Contributor
Contributor
Jump to solution

Did you manage to get the card (FastTrak TX-4310) working with ESXi ? I tried to mod the oem.tgz, but it still don't work... Smiley Sad

Reply
0 Kudos