Exalogic Virtual: Control vServer Restart Using "xm create" Command Fails With "Error: Device 768 (vbd) could not be connected" Error (Doc ID 2096259.1)

Last updated on APRIL 14, 2024

Applies to:

Oracle Exalogic Elastic Cloud Software - Version 2.0.6.0.0 and later
Linux x86-64
Oracle Virtual Server x86-64

Symptoms

In Exalogic Virtual racks, issue of Control vServer restart using "xm create" command failing with "Error: Device 768 (vbd) could not be connected" error is seen.

Below error is seen during startup of control stack vserver.

Changes

None

Cause

	To view full details, sign in with your My Oracle Support account.
	Don't have a My Oracle Support account? Click to get started!

In this Document

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

Exalogic Virtual: Control vServer Restart Using "xm create" Command Fails With "Error: Device 768 (vbd) could not be connected" Error (Doc ID 2096259.1)

Applies to:

Symptoms

Changes

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!