Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Waiting for the VM to receive an address... #92

Open
gowthamshankar05 opened this issue Jun 19, 2023 · 1 comment
Open

Waiting for the VM to receive an address... #92

gowthamshankar05 opened this issue Jun 19, 2023 · 1 comment

Comments

@gowthamshankar05
Copy link

I've tried using spox/ubuntu-arm and that works fine
but when I tried using jacobw/fedora35-arm64 it got stuck with the following error.

Bringing machine 'default' up with 'vmware_desktop' provider...
==> default: Cloning VMware VM: 'jacobw/fedora35-arm64'. This can take some time...
==> default: Checking if box 'jacobw/fedora35-arm64' version '3.6.8' is up to date...
==> default: Verifying vmnet devices are healthy...
==> default: Preparing network adapters...
==> default: Starting the VMware VM...
==> default: Waiting for the VM to receive an address...

and my mac got stuck here and I'm using the latest version vagrant-vmware-desktop (3.0.3).

@friesoft
Copy link

friesoft commented Jul 5, 2023

I'm having the same problem on Fedora 37/38 using a custom centos/7 based box
vagrant-vmware-desktop: 3.0.3
vagrant-vmware-utility: 1.0.22
vmware workstation pro: 17.0.2 build-21581411

In /var/log/messages I see the following output:

Jul  5 20:26:54 pc122275 vagrant-vmware-utility[52735]: 2023-07-05T20:26:54.723+0200 [DEBUG] vagrant-vmware-utility.api.api: starting request: request-id=0xc000436300
Jul  5 20:26:54 pc122275 vagrant-vmware-utility[52735]: 2023-07-05T20:26:54.723+0200 [INFO]  vagrant-vmware-utility.api.api.handler: request start: method=GET path=/vmnet/vmnet8/dhcplease/00:0c:29:f2:c4:a5 request-id=0xc00026a380
Jul  5 20:26:54 pc122275 vagrant-vmware-utility[52735]: 2023-07-05T20:26:54.723+0200 [DEBUG] vagrant-vmware-utility.api.api.handler: vmnet dhcp lease request: device=vmnet8 mac=00:0c:29:f2:c4:a5
Jul  5 20:26:54 pc122275 vagrant-vmware-utility[52735]: 2023-07-05T20:26:54.723+0200 [INFO]  vagrant-vmware-utility.api.dhcpd-leases: loading VMware style DHCP lease file: path=/etc/vmware/vmnet8/dhcpd/dhcpd.leases
Jul  5 20:26:54 pc122275 vagrant-vmware-utility[52735]: 2023-07-05T20:26:54.723+0200 [DEBUG] vagrant-vmware-utility.api.dhcpd-leases: loading DHCP lease file: path=/etc/vmware/vmnet8/dhcpd/dhcpd.leases
Jul  5 20:26:54 pc122275 vagrant-vmware-utility[52735]: 2023-07-05T20:26:54.739+0200 [DEBUG] vagrant-vmware-utility.api.dhcpd-leases: loaded active leases: path=/etc/vmware/vmnet8/dhcpd/dhcpd.leases leases=0
Jul  5 20:26:54 pc122275 vagrant-vmware-utility[52735]: 2023-07-05T20:26:54.740+0200 [DEBUG] vagrant-vmware-utility.api.networking-file: loaded: num.adapters=4 num.dhcpres=0 num.portfwds=0 path=/etc/vmware/networking
Jul  5 20:26:54 pc122275 vagrant-vmware-utility[52735]: 2023-07-05T20:26:54.740+0200 [DEBUG] vagrant-vmware-utility.api.api.handler: vmnet dhcp lease lookup error: error="No entry found for MAC 00:0c:29:f2:c4:a5"
Jul  5 20:26:54 pc122275 vagrant-vmware-utility[52735]: 2023-07-05T20:26:54.740+0200 [DEBUG] vagrant-vmware-utility.api.api.handler: request error: code=400 message="No entry found for MAC 00:0c:29:f2:c4:a5"
Jul  5 20:26:54 pc122275 vagrant-vmware-utility[52735]: 2023-07-05T20:26:54.740+0200 [INFO]  vagrant-vmware-utility.api.api.handler: request complete: code=400 request-id=0xc00026a380
Jul  5 20:26:54 pc122275 vagrant-vmware-utility[52735]: 2023-07-05T20:26:54.740+0200 [DEBUG] vagrant-vmware-utility.api.api: completed request: request-id=0xc000436300 headers=map[Content-Type:[application/vnd.hashicorp.vagrant.vmware.rest-v1+json]]

The mentioned file /etc/vmware/vmnet8/dhcpd/dhcpd.leases is populated with currently 20 entries but the mac address it is trying to fetch is indeed missing from the file.

Neither restarting the vagrant-vmware-utility nor rebooting solves this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants