Oracle Solaris Virtualization (LDOM and ZONES) (MOSC)

MOSC Banner

variable

in Oracle Solaris Virtualization (LDOM and ZONES) (MOSC) 2 commentsAnswered ✓

Hi,

In a DR with one T8-2 on primarys and one T8-2 on secondary i live migrated a ldom guest from primary to secondary.

Before migration ldm ls-bindings guest

VARIABLES
boot-device=rootdisk
multipath-boot?=true
network-boot-arguments=host-ip=172.18.182.212,router-ip=172.18.180.1,subnet-mask=255.255.252.0,hostname=s-m-sol06
nvramrc=devalias rootdisk1 /pci@304 /pci@1 /SUNW,qlc@0 /fp@0 ,0/disk@w524a937119d18f00 ,cf
devalias rootdisk /pci@304 /pci@1 /SUNW,qlc@0 ,1/fp@0 ,0/disk@w524a937119d18f03 ,cf

After migration this information is missing.Is there any reason?

In production how is the best to have auto-boot set?

I mean on primary and secondary auto-boot?=true and on guests auto-boot?=true and only if there is a dependency between applications that run on guests to set auto-boot?=false ?

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center