From the OpenShift web console:
- Select Workloads > Virtualization > Create Virtual Machine > New with Wizard.
Note: Ensure that the project value is set to vm-home.
- Specify the Name, Operating System, and Boot Source:
- Set the Operating System to Red Hat Enterprise Linux 8.0 or higher
- Set Boot Source to URL (adds disk).
- Click the highlighted Red Hat Enterprise Linux download page under URL to download a sample rhel 8.2 qcow2 image. Then:
- Copy the downloaded image and make it available using http. Specify the http link to the qcow2 image under URL.
- Link directly to the Red Hat Enterprise Linux 8.2 qcow image by copying the direct download link to the image from the Red Hat portal.
- Set Flavor to Tiny and Workload Profile to desktop.
- Click Next.
Note: Red Hat login credentials are required to retrieve Red Hat Enterprise Linux images for VMs.
- In Networking options, click Add Network Interface.
Note: Skip this step if an SR-IOV network attachment definition is not required.
- Specify the Type as SR-IOV and select the Network Attachment Definition from the Network drop-down menu.
- Click Add and Next.
- In Storage options, click the icon next to rootdisk.
- Select Edit and specify the storage class that you created in Storage specification.
- Select Advanced and set the Access Mode and Volume Mode as required.
Note: Ensure that the storage provider supports Access Mode and Volume Mode.
- Click Save and Next.
- In Advanced options under Cloud-init, provide any custom start-up script that needs to be run when the VM boots. Click Next.
The startup script contains a default user login and password.
- Review the options that you specified. If they are correct, select Start virtual machine on creation and click Create Virtual Machine.
- Using the Console tab, log in using the username and password information that is provided in the startup script.
- To test the SR-IOV interface, manually assign the appropriate IP using nmcli commands. For more information, see the Red Hat document CONFIGURING IP NETWORKING WITH NMCLI.
Note: Skip this step if there is no SR-IOV network attached to the VM.
The SR-IOV interface IP must be reachable from the switch to which the physical NIC is connected.
- Ping the IP address manually to ensure that the virtual function is assigned successfully to the VM.