[PCA 2.x] Some VM Network Interfaces Failed to Come Up When Booting Multiple VMs At The Same Time (Doc ID 2856149.1)

Last updated on JANUARY 12, 2025

Applies to:

Symptoms

When booting multiple VMs at the same time, some of the network interfaces (vNIC) on each VM could fail to come up on boot, but could still be manually bring up with 'ifup' or by restarting VM network service.
And when this happens, the following error message could be observed in VM system log:

localhost kernel: xenbus_probe_frontend: Device with no driver: device/vif/0
localhost kernel: xenbus_probe_frontend: Device with no driver: device/vif/1
localhost kernel: xenbus_probe_frontend: Device with no driver: device/vif/2
...
localhost kernel: xenbus_probe_frontend: Timeout connecting to device: device/vif/0 (local state 1, remote state 2)
localhost kernel: xenbus_probe_frontend: Timeout connecting to device: device/vif/1 (local state 1, remote state 2)
localhost kernel: xenbus_probe_frontend: Timeout connecting to device: device/vif/2 (local state 1, remote state 2)

This issue would not happen when starting the VMs one by one.
And increasing value of parameter 'gnttab_max_frames' and 'XENSTORED_ARGS' (per NOTE 2543042.1 and NOTE 2691205.1) does not fix this issue.

Changes

No changes.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.