Editing the Launch Options for an Instance
You can tune the compatibility and performance of virtual machine (VM) instances by changing the networking type or the boot volume attachment type.
For permissions, see Required IAM Policy for Working with Instances.
Networking Launch Types
The networking interface handles functions such as disk input/output and network communication.
The following networking types are available:
- Paravirtualized networking: For general purpose workloads such as enterprise applications, microservices, and small databases. Paravirtualized networking also provides increased flexibility to use the same image across different hardware platforms. Linux images with paravirtualized networking support live migration during infrastructure maintenance.
- Hardware-assisted (SR-IOV) networking: Single root input/output virtualization. For low-latency workloads such as video streaming, real-time applications, and large or clustered databases. Hardware-assisted (SR-IOV) networking uses the VFIO driver framework.
To use a particular networking type, both the shape and the image must support that networking type.
Shapes: The following table lists the default and supported networking types for VM shapes.
| Shape | Default Networking Type | Supported Networking Types |
|---|---|---|
| VM.Standard1 series | SR-IOV | Paravirtualized, SR-IOV |
| VM.Standard2 series | Paravirtualized | Paravirtualized, SR-IOV |
| VM.Standard3.Flex | Paravirtualized | Paravirtualized, SR-IOV |
| VM.Standard.E2 series | Paravirtualized | Paravirtualized only |
| VM.Standard.E3.Flex |
Paravirtualized |
Paravirtualized, SR-IOV |
| VM.Standard.E4.Flex |
Paravirtualized |
Paravirtualized, SR-IOV |
| VM.Standard.E5.Flex |
Paravirtualized |
Paravirtualized, SR-IOV |
| VM.Standard.A1.Flex1 | Paravirtualized | Paravirtualized, SR-IOV |
| VM.DenseIO1 series | SR-IOV | Paravirtualized, SR-IOV |
| VM.DenseIO2 series | Paravirtualized | Paravirtualized, SR-IOV |
| VM.DenseIO.E4.Flex | Paravirtualized | Paravirtualized, SR-IOV |
| VM.GPU2 series | SR-IOV | Paravirtualized, SR-IOV |
| VM.GPU3 series | SR-IOV | Paravirtualized, SR-IOV |
| VM.GPU.A10 series | SR-IOV | Paravirtualized, SR-IOV |
| VM.Optimized3.Flex |
Paravirtualized |
Paravirtualized, SR-IOV |
Images: Paravirtualized networking is supported on these platform images:
- Oracle Linux 9, Oracle Linux 8, Oracle Autonomous Linux 8.x, Oracle Autonomous Linux 7.x, Oracle Linux Cloud Developer 8: All images.
- Oracle Linux 7, Oracle Linux 6: Images published in March 2019 or later.
- CentOS Stream 8, CentOS 7: Images published in July 2019 or later.
- Ubuntu 22.04, Ubuntu 20.04: All images.
- Ubuntu 18.04: Images published in March 2019 or later.
- Windows Server 2022, Windows Server 2019: All images.
- Windows Server 2016, Windows Server 2012 R2: Images published in August 2019 or later.
SR-IOV networking is supported on all platform images, with the following exceptions:
- Images for Arm-based shapes do not support SR-IOV networking.
- On Windows Server 2019 and Windows Server 2022, when launched using a shape in the VM.Standard2 series, SR-IOV networking is not supported.
- On Windows Server 2012 R2, SR-IOV networking is supported on platform images released in April 2021 or later.
- The Server Core installation option for Windows Server does not support SR-IOV networking.
Boot Volume Attachment Types
The following boot volume attachment types are available:
-
iSCSI: A TCP/IP-based standard used for communication between a volume and attached instance.
-
Paravirtualized: A virtualized attachment available for VMs. This is the default for boot volumes and remote block storage volumes on platform images.
Supported Shapes
You can edit the launch options for instances that use these shapes:
- VM.Standard1 series
- VM.Standard.B1 series
- VM.Standard2 series
- VM.Standard3.Flex
- VM.Standard.E2 series
- VM.Standard.E3.Flex
- VM.Standard.E4.Flex
- VM.Standard.E5.Flex
- VM.Standard.A1.Flex
- VM.DenseIO1 series
- VM.DenseIO2 series
- VM.GPU3 series
- VM.GPU.A10 series
- VM.Optimized3.Flex
These shapes cannot be edited:
- VM.Standard.E2.1.Micro
- VM.DenseIO.E4.Flex
- VM.GPU2 series
- VM instances that run on dedicated virtual machine hosts
Limitations and Considerations
Some instances might not function properly if you change the networking type or the boot volume attachment type. This happens due to shape and image compatibility and driver support. After the instance reboots and is running, connect to it. If the connection fails or the OS doesn't behave as expected, the changes are not supported. Revert the instance to the original settings.
Before you change the networking type or the boot volume attachment type, you must ensure that paravirtualized drivers are installed on the image. The steps depend on the image:
Paravirtualized drivers are installed on platform images.
The Oracle VirtIO Drivers for Microsoft Windows must be installed on platform images.
- To determine whether the drivers are installed, connect to the instance using a Remote Desktop connection. Then, do either of the following things:
- Open Control Panel, and then open Program and Features. If Oracle Windows VirtIO Drivers is installed, note the version number.
- In Registry Editor, go to HKEY_LOCAL_MACHINE\\Software\\Wow6432Node\\Oracle Corporation\\Oracle Windows VirtIO Drivers. If the drivers are installed, note the version number.
-
If the drivers are not installed, do the following:
- Download the Oracle VirtIO Drivers for Microsoft Windows.
- Install the drivers and then restart the instance.
For platform images, connect to the instance using a Secure Shell (SSH) connection. Then, run the following commands:
sudo bash
cd /boot/efi
echo "fs0:\EFI\redhat\grub.efi"> startup.nsh
chmod 500startup.nsh
syncTo verify that your system has paravirtualized drivers installed, run the following command:
lsinitrd | grep virtio- If paravirtualized drivers are installed, you will see multiple files listed
with paths similar to
lib/modules/4.4.21-69-default/kernel/drivers/block/virtio_blk.ko. - If no files are listed, your system either does not support paravirtualized drivers, or does not have paravirtualized drivers installed. Refer to the documentation for your operating system for more information.
Before You Begin
- Detach (delete) all secondary VNICs and detach all block volumes. The primary VNIC and boot volume should remain attached.
Using the Console
- Open the navigation menu and click Compute. Under Compute, click Instances.
- Click the instance that you're interested in.
- Click More Actions, and then click Edit.
- Click Show advanced options. The Launch options tab displays.
- To change the networking type, in the Networking type section, select from the following options:
- Hardware-assisted (SR-IOV) networking: Single root input/output virtualization. For low-latency workloads such as video streaming, real-time applications, and large or clustered databases.
- Paravirtualized networking: For general purpose workloads such as enterprise applications, microservices, and small databases. The image must have paravirtualized drivers, as described in Limitations and Considerations.
- To change the boot volume attachment type, in the Boot volume attachment type
section, select from the following options:
- iSCSI: A TCP/IP-based standard used for communication between a volume and attached instance.
- Paravirtualized: A virtualized attachment available for VMs. This is the default for boot volumes and remote block storage volumes on platform images.
- Click Save changes.
If the instance is running, it is rebooted. Confirm when prompted.
- Connect to the instance after it reboots and is running. If the connection fails or the OS doesn't behave as expected, the changes are not supported. Revert the instance to the original settings.
- If necessary, reattach any secondary VNICs and block volumes.
Using the API
For information about using the API and signing requests, see REST API documentation and Security Credentials. For information about SDKs, see SDKs and the CLI.
Use this API operation to edit the launch options for an instance: