Veritas InfoScale™ 7.4.2 Virtualization Guide - Linux

Configuring multiple KVMGuest resources

If a VCS service group has more than one KVMGuest resource monitoring virtual machines and one of the virtual machines is migrated to another host, then a service group level concurrency violation occurs as the service group state goes into PARTIAL state on multiple nodes.

Veritas recommends configuring only one KVMGuest resource in a Service group. See the sample configurations below for reference.

Configuration 1:

group rhev_grp1 (

SystemList = { sys1 = 0, sys2 = 1 }
)

KVMGuest kvmres1 (

RHEVMInfo = { Enabled = 1,

URL = "https://rhevm-server.example.com:443",

User = "admin@internal"

Password = bncNfnOnkNphChdHe,

Cluster = dc2_cluster1,

UseManualRHEVMFencing=1 }

GuestName = rhevvm1

DelayAfterGuestOnline = 20

DelayAfterGuestOffline = 35

)

Configuration 2:

group rhev_grp1 (

SystemList = { sys1 = 0, sys2 = 1 }
)

KVMGuest kvmres1 (

RHEVMInfo = { Enabled = 1,

URL = "https://rhevm-server.example.com:443",

User = "admin@internal"

Password = bncNfnOnkNphChdHe,

Cluster = dc2_cluster1,

UseManualRHEVMFencing=0 }

GuestName = rhevvm1

DelayAfterGuestOnline = 20

DelayAfterGuestOffline = 35

)

group rhev_grp2 (

SystemList = { sys1 = 0, sys2 = 1 }
)

KVMGuest kvmres2 (

RHEVMInfo = { Enabled = 1,

URL = "https://rhevm-server.example.com:443",

User = "admin@internal"

Password = bncNfnOnkNphChdHe,

Cluster = dc2_cluster1,

UseManualRHEVMFencing=0 }

GuestName = rhevvm2

DelayAfterGuestOnline = 20

DelayAfterGuestOffline = 35

)