prlctl only tells me the IPv4 address of a machine after a >10 mins delay

Discussion in 'General Questions' started by ParallelsU591, Mar 10, 2021.

  1. ParallelsU591

    ParallelsU591 Junior Member

    Messages:
    10
    I run the following command to get the IP address of a VM when it boots:
    Code:
    prlctl list <vm> --all --no-header -o ip
    This code returns with the ipv6 addresses very quickly, but then takes some time to start displaying the ipv4 address. When I go into the VM console I can see the VM got a DHCP ipv4 address almost immediately. Unfortunately I need the IP address outside of the VM in order to automate an ssh login to the VM so this results in a long delay in my workflow.
    Is there any work-around for this?
     
  2. Maria@Parallels

    Maria@Parallels Problem solver

    Messages:
    8,121
    Hi, are you using the Bridged network mode?
     
  3. ParallelsU591

    ParallelsU591 Junior Member

    Messages:
    10
    No, this is shared network on one NIC, and host-only on the other.
     
  4. ParallelsU591

    ParallelsU591 Junior Member

    Messages:
    10
    Just to add, if it was bridged I would not expect Parallels to have any knowledge of the IP address, since it never supplied it to the VM and was supplied by my router/dhcp server instead.
     
  5. Maria@Parallels

    Maria@Parallels Problem solver

    Messages:
    8,121
    Please sorry for the misunderstanding.
    Could you reproduced the issue and collect tech report right after that please?
    Looking forward to your reply and tech report ID.
     
  6. ParallelsU591

    ParallelsU591 Junior Member

    Messages:
    10
    Hi Maria, I have opened a support ticket instead, FYI, the report is 364488709 (when I get the problem), I will continue with the support ticket and report back here if I find a solution, thanks for your help.
     

Share This Page