vSRX

IMPORTANT MODERATION NOTICE

This community is currently under full moderation, meaning  all posts will be reviewed before appearing in the community. Please expect a brief delay—there is no need to post multiple times. If your post is rejected, you'll receive an email outlining the reason(s). We've implemented full moderation to control spam. Thank you for your patience and participation.



Expand all | Collapse all

Juniper WRL Error :- Attempted double use of PCI slot

  • 1.  Juniper WRL Error :- Attempted double use of PCI slot

    Posted 24 days ago
    Team,

    Context :- vSRX upgrade using command "request system software add <19.x.> no-validate un-link"

    Issue :- Upgrade Fails & the VM never boots UP.

    Troubleshooting Done :-
    - Console to the VM shows the same stuck at WRL localhost prompt.
    - Logging into it further and analyzing the libvirt logs within WRL it reveals the following error :-

    2021-09-15 13:42:44.776+0000: 1280: error : qemuDomainPCIAddressReserveAddr:19955
     : XML error: Attempted double use of PCI slot 0000:00:03.0 (may need "multifuncc
    tion='on'" for device on function 0)
    - Quick Google shows error could relate to if the XML is for some reason using same PCI for 2 usecase, maybe 2 discs or ports but the XML for the VNF is clean with all unique pci address.

    Ask :- Any idea on this error ?

    ------------------------------
    Rahul
    ------------------------------


  • 2.  RE: Juniper WRL Error :- Attempted double use of PCI slot

     
    Posted 24 days ago
    Hi,
    which release are you upgrading from? (show version brief)
    which release are you upgrading to? (exact file name)
    which hypervisor are you using?
    why no-validate? What happens if you use it?
    Regards
    Ulf


  • 3.  RE: Juniper WRL Error :- Attempted double use of PCI slot

    Posted 22 days ago
    Ulf,
    Thanks for responding !

    It was a minor upgrade within 19.3
    Running on a CPE - NFX250
    no-validate -- that is a knob to exclude the config validation to the new version.

    Between, the issue seems to be a memory issue. Will next clean up space and retry.


    ------------------------------
    Rahul
    ------------------------------