My Oracle Support Banner

OCI : KVM Pool Device Path Not Persistent On Reboot (Doc ID 2697484.1)

Last updated on AUGUST 17, 2020

Applies to:

Oracle Cloud Infrastructure - Version N/A to N/A [Release 1.0]
Information in this document applies to any platform.
Linux x86-64

Symptoms

A Bare Metal instance created using oci kvm image 1.5. A block volume has been attached and a storage pool created. Several other block volumes have now also been added. When the instance was rebooted the original disk was not allocated to the /dev/sdb1 device but to /dev/sdj1 instead. To try to make this persistent the command ' virsh pool-edit vmstore' was run to edit the device path to use a UUID instead. When the server was rebooted the reverted to /dev/sdb1. the block volume used as pool is not persistent across reboots.

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
Symptoms
Cause
Solution


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