Troubleshooting LDom Error Messages "Timeout receiving packet from LDC" & "Communication error with Virtual Disk Server"
(Doc ID 1507770.1)
Last updated on MARCH 11, 2020
Applies to:Solaris Operating System - Version 10 3/05 HW2 and later
Oracle Solaris on x86-64 (64-bit)
Oracle Solaris on SPARC (64-bit)
This document 1507770.1 merged similar content of 1554607.1 and 1509069.1:
In Ldom MPXIO setup guest domain is no longer accessible after SRU 8.5 upgrade (Doc ID 1509069.1)
Guest ldom(s) fail to boot with: WARNING: /virtual-devices@100/channel-devices@200/disk@0: Communication error with Virtual Disk Server using Port 0. Retrying. (Doc ID 1554607.1)
This document describes ways to troubleshoot LDom error messages like "Timeout receiving packet from LDC ..." or "Communication error with Virtual Disk Server ..."
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
|Identify the underlying backing store for a vdisk of a particular Guest|
|Example 1: A guest domain is no longer able to boot from vdisk after renaming of a ZVOL on the service domain|
|Example 2: The control domain had MPxIO configured for mpt_sas driver|
|Example 3: After the primary domain has been upgraded to Solaris 11 SRU 8.5, guest domains are getting error messages and unable to boot:|
|Example 4: A crash of the service domain might have left the vdisks in a hung state|
|Example 5: OVM Manager agent (ovs-agent) might have disabled vds/vsw on primay domain|