No Operating System - No Images Available

[stefanscherer]

No Operating System - No Images Available

[cjbischoff]

Further poking around I found this -> http://jontriphan.com/windows-8-error-there-are-no-images-available-on-wmware/

Basically I disable the floppy and restart and it works, but it breaks auto-build since you are using the floppy

[StefanScherer]

@cjbischoff Just tried packer build --only=vmware-iso windows_2016.json and it doesn't hang here.
I'm using packer 0.12.0, Fusion Pro 8.5.3, but it should work without Pro as well.

You could try with debug output

PACKER_LOG=debug packer build --only=vmware-iso windows_2016.json

and link a gist of it.

[cjbischoff]

@StefanScherer Ok the debug is nice

==> vmware-iso: Waiting for WinRM to become available...
2016/12/16 09:40:07 packer: 2016/12/16 09:40:07 Lookup up IP information...
2016/12/16 09:40:07 packer: 2016/12/16 09:40:07 DHCP leases path: /var/db/vmware/vmnet-dhcpd-vmnet8.leases
2016/12/16 09:40:07 packer: 2016/12/16 09:40:07 IP lookup failed: open /var/db/vmware/vmnet-dhcpd-vmnet8.leases: no such file or directory

So something is up with network connectivity.

During your builds is your network set to Share with Mac or Private to Mac?

[StefanScherer]

I can see the same debug output while the guest does not have setup the network interface. The message still appears while the win-update script searches for the first Windows Updates.

I can see the following settings in the output*/*.vmx file

ethernet0.addresstype = "generated"
ethernet0.bsdname = "en0"
ethernet0.connectiontype = "nat"
ethernet0.displayname = "Ethernet"
ethernet0.linkstatepropagation.enable = "FALSE"
ethernet0.pcislotnumber = "33"
ethernet0.present = "TRUE"
ethernet0.virtualdev = "e1000"
ethernet0.wakeonpcktrcv = "FALSE"
ethernet0.generatedAddress = "00:0c:29:ed:de:30"
ethernet0.generatedAddressOffset = "0"

Just the normal settings.

[StefanScherer]

@cjbischoff Have you made any progress?

[StefanScherer]

I can reproduce the problem, but with the Windows 10 Insider 15002 ISO file. Seems that this ISO can't be used with the autounattend.xml as there is no selection needed.
OK, it seems to work - at least it's getting files ready for installation by removing the ProductKey and the InstallFrom sections in the autounattend.xml.
Do you use eg. the Win2016 essentials ISO file?

[StefanScherer]

Closing this as it seems to be a problem with the ISO itself. Rebuilt two boxes yesterday with latest ISO works. But if you still have problem, don't hesitate to reopen.