Skip to Main Content

Infrastructure Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Secondary Domain : VIO configure request sent, but no valid response

DinajSep 4 2020 — edited Sep 8 2020

Hi,

When trying to create a vswitch I got following warning, but the vswitch was created. But the link status ( but the status  is down inside the ldom)

**********************************************************************

root@CBS-PROD-Node2-PDom # ldm add-vsw linkprop=phys-state inter-vnet-link=off net-dev=net6 secondary-backup-vsw0 secondary

Cannot validate network device net6 on service domain secondary.

VIO configure request sent, but no valid response received within 300 seconds

LDom secondary did not respond to request to configure VIO device

VIO device is considered to be allocated to LDom, but might not

be available to the guest OS

root@CBS-PROD-Node2-PDom #

***********************************************************************

When trying to delete vsw, following error occured.

root@CBS-PROD-Node2-PDom #

root@CBS-PROD-Node2-PDom # ldm rm-vsw secondary-backup-vsw0

VIO unconfigure request sent, but no valid response received within 300 seconds

LDom secondary did not respond to request to configure VIO device

VIO device is considered to be allocated to LDom, but might not

be available to the guest OS

Failed to remove virtual switch

root@CBS-PROD-Node2-PDom #

*******************************************************************

according to : Failure to Add Vdisk to Guest Domain: 'LDom {ldomname} did not respond to request to configure VIO device' (Doc ID 1538587.1)

I tried to restart the  "svc:/platform/sun4v/drd:default", but was not helpful.

*************************************************************************

root@CBS-PROD-Node2-PDom #

root@CBS-PROD-Node2-PDom # ldm -V

Logical Domains Manager (v 3.5.0.2.1)

        Hypervisor control protocol v 1.12

        Using Hypervisor MD v 1.4

System PROM:

        Hostconfig      v. 1.6.12       @(#)Hostconfig 1.6.12 2018/03/28 15:47

        Hypervisor      v. 1.15.12      @(#)Hypervisor 1.15.12 2018/03/28 15:19

        OpenBoot        v. 4.38.12      @(#)OpenBoot 4.38.12 2018/03/28 14:54

root@CBS-PROD-Node2-PDom #

===========================

root@CBS-PROD-Node2-PDom #

root@CBS-PROD-Node2-PDom # uname -a

SunOS CBS-PROD-Node2-PDom 5.11 11.3 sun4v sparc sun4v

root@CBS-PROD-Node2-PDom #

===========================

root@CBS-PROD-NODE2-SDOM:~#

root@CBS-PROD-NODE2-SDOM:~# uname -a

SunOS CBS-PROD-NODE2-SDOM 5.11 11.3 sun4v sparc sun4v

root@CBS-PROD-NODE2-SDOM:~#

Appreciate your input to solve this problem.

Best Regards,

Dinaj

Comments
Post Details
Added on Sep 4 2020
1 comment
458 views