TKG 1.6 VMs vs 2.1... BIOS to EFI

1.6 TKG supported  BIOS booting by default

in newer TKG versions 2.1 , we support  EFI by default

EFI is required for PCI passthrough

PCI Passthrough is currently required to run GPU workloads on TKG

In any case,  as shown below there is a 

1.6 cluster on the left

and a 2.1 on the right

Clicking on the Boot options (click the vM, then go to Edit Settings -> Boot options) We can see 

1.6 default boots as bios

2.1 default boots as efi

Thus , the older Virtual machine

Note to self: Running image-builder for TKG , 2.1

In  tKG 2.1, we run Image-builder for GPU workloads.  Just a quick note to myself on the snippet for doing this the right way

TKG=/home/kubo/image-builder/TKG-Image-Builder-for-Kubernetes-v1.24.9-on-TKG-v2.1.0-master/TKG-Image-Builder-for-Kubernetes-v1_24_9---vmware_1-tkg_v2_1_0

 SOURCES=${TKG}/tkg.json

ROLES=${TKG}

### Ignoring goss will see if it works

#GOSS=

CUSTOMIZATIONS=$TKG/customizations.json

#CREDS=

COMMAND="build-node-ova-vsphere-ubuntu-2004"

docker run -it --rm \

-v /home/kubo/image-builder/TKG-Image-Builder-for-Kubernetes-v1.24.9-on-TKG-v2.1.0-master/TKG-Image-Builder-for-Kubernetes-v1_24_9---vmware_1-tkg_v2_1_0/tkg.json:/home/imagebuilder/tkg.json \

-v $ROLES:/home/imagebuilder/tkg/ \

-v $CUSTOMIZATIONS:/home/imagebuilder/customizations.json \

-v $TKG/credentials.json:/home/imagebuilder/credentials.json \

-v $TKG/goss/:/home/imagebuilder/goss \

--env PACKER_VAR_FILES="tkg.json customizations.json credentials.json" \

--env IB_OVFTOOL=1 \

projects.registry.vmware.com/tkg/image-builder:v0.1.13_vmware.2 build-node-ova-vsphere-ubuntu-2004