Deployment Guide

Deployment and configuration
34 VMware vSphere Bitfusion on Dell EMC PowerEdge servers | Deployment guide
6. Verify the network adapter 2 settings:
• IPv4 address–172.16.6.22
• CIDR–24
• MTU–9000
6.9 Edit the bitfusion-server-3 virtual machine hardware settings
Follow the steps:
1. Under the Virtual Hardware tab, verify the number of vCPUs is 8
• Minimum No. of vCPUs = 4x No. of GPU devices attached to the appliance. In this case, 4 x 2 GPUs
i.e. 8
2. Verify that the memory is set to 48GB and select the checkbox Reserve all guest memory.
• Minimum GB of memory = 1.5x aggregate total of GPU memory on all GPU cards passed through. In
this case, 1.5x 32GB i.e. 48GB
3. Click on Add New Device and add two PCIe devices. Select the PCI devices from the drop-down
menu.
• 0000:3b:00.0 | GV100GL Tesla V100 PCIe 16GB
• 0000:d8:00.0 | TU104GL Tesla T4
4. Click on Add New Device and select Network adapter. Browse and select the network pvrdma that
is created on the Bitfusion distributed switch earlier.
5. Select the Adapter Type as PVRDMA and the Device Protocol as RoCE v2
6. Under the Virtual Machine Options tab, select Advanced > Configuration parameters and then select
Edit Configuration. Edit the pciPassthru.64bitMMIOSizeGB parameter to 64.
• pciPassthru.64bitMMIOSizeGB= <n>, where n equals (num-cards * size-of-card-in-GB) rounded up to
NEXT power of 2. In this case, 2x 16 → 32, rounded to next power of 2 i.e. 64
7. Refrain from powering on the virtual machine. Click on Enable Bitfusion from the bitfusion-server-3
option and then select Actions > Bitfusion menu.
8. A window pops up listing the options to enable as a client or server. Select the For a server, this will
allow it to be used as a GPU server radio button and click on ENABLE. This adds guest variables
informing the server it is not the first GPU server in the Bitfusion cluster.
9. Power on the virtual machine and wait for the Bitfusion plugin UI to show the additional appliance and
additional GPUs added to the cluster.
Note: The hostname is shown as 'Unreachable' on the Bitfusion plugin GUI initially before showing the name
of the host that is part of the cluster.