packer stuck on Starting virtual machine...

[baulinss]

Community Note

Overview of the Issue

packer stuck on Starting virtual machine...

Reproduction Steps

If i run 'packer build', packer started VMware Workstation and packer stuck on Starting virtual machine...

PS C:\Packer_Vmware_Workstation> Get-Process -ProcessName 'vmware'
Get-Process : Cannot find a process with the name "vmware". Verify the process name and call the cmdlet again.
At line:1 char:1

• Get-Process -ProcessName 'vmware'

•   + CategoryInfo          : ObjectNotFound: (vmware:String) [Get-Process], ProcessCommandException
    + FullyQualifiedErrorId : NoProcessFoundForGivenName,Microsoft.PowerShell.Commands.GetProcessCommand
  
  

PS C:\Packer_Vmware_Workstation> .\test.ps1
test.vmware-iso.test: output will be in this color.

==> test.vmware-iso.test: Retrieving ISO
==> test.vmware-iso.test: Trying C:/ISO/test.iso
==> test.vmware-iso.test: Trying file://C:/ISO/test.iso?checksum=sha256%3Aee5aff905d14082b1f9e5b6a5a0359f8bed31f5dd855ed14f1abe0e033482ead
==> test.vmware-iso.test: file://C:/ISO/test.iso?checksum=sha256%3Aee5aff905d14082b1f9e5b6a5a0359f8bed31f5dd855ed14f1abe0e033482ead => C:/ISO/test.iso
==> test.vmware-iso.test: Configuring output and export directories...
==> test.vmware-iso.test: Creating temporary RSA SSH key for instance...
==> test.vmware-iso.test: Creating required virtual machine disks
==> test.vmware-iso.test: Building and writing VMX file
==> test.vmware-iso.test: Starting HTTP server on port 8425
==> test.vmware-iso.test: Starting virtual machine...

VM running and i see GNU GRUB, but packer stuck on Starting virtual machine...

---

If i started VMware Workstation and after that run 'packer build' - it`s ok

PS C:\Packer_Vmware_Workstation> Get-Process -ProcessName 'vmware'

Handles NPM(K) PM(K) WS(K) CPU(s) Id SI ProcessName

---

529      50    22784      57268       1,00  33544   2 vmware

PS C:\Packer_Vmware_Workstation> .\test.ps1
test.vmware-iso.test: output will be in this color.

==> test.vmware-iso.test: Retrieving ISO
==> test.vmware-iso.test: Trying C:/ISO/test.iso
==> test.vmware-iso.test: Trying file://C:/ISO/test.iso?checksum=sha256%3Aee5aff905d14082b1f9e5b6a5a0359f8bed31f5dd855ed14f1abe0e033482ead
==> test.vmware-iso.test: file://C:/ISO/test.iso?checksum=sha256%3Aee5aff905d14082b1f9e5b6a5a0359f8bed31f5dd855ed14f1abe0e033482ead => C:/ISO/test.iso
==> test.vmware-iso.test: Configuring output and export directories...
==> test.vmware-iso.test: Creating temporary RSA SSH key for instance...
==> test.vmware-iso.test: Creating required virtual machine disks
==> test.vmware-iso.test: Building and writing VMX file
==> test.vmware-iso.test: Starting HTTP server on port 8425
==> test.vmware-iso.test: Starting virtual machine...
==> test.vmware-iso.test: Connecting to VNC...
==> test.vmware-iso.test: Waiting 5s for boot...

Packer version

Packer v1.11.2

Simplified Packer Template

Operating system and Environment details

Windows 10 Pro
Version 22H2 (OS Build 19045.5247)

VMware® Workstation 17 Pro
17.5.1 build-23298084

Log Fragments and crash.log files

PACKER_LOG=1
==> test.vmware-iso.test: Starting virtual machine...
packer-plugin-vmware_v1.1.0_x5.0_windows_amd64.exe plugin: Found available port: 5994 on IP: 127.0.0.1
packer-plugin-vmware_v1.1.0_x5.0_windows_amd64.exe plugin: Found available VNC port: 127.0.0.1:5994
packer-plugin-vmware_v1.1.0_x5.0_windows_amd64.exe plugin: Writing VMX to: output-test\test.vmx
packer-plugin-vmware_v1.1.0_x5.0_windows_amd64.exe plugin: Executing: C:/Program Files (x86)/VMware/VMware Workstation/vmrun.exe -T ws start output-test\test.vmx gui

Ctrl + C
packer.exe plugin: Received interrupt signal (count: 1). Ignoring.
packer.exe plugin: Received interrupt signal (count: 1). Ignoring.
Cancelling builder after context cancellation context canceled
Cancelling build after receiving interrupt
packer-plugin-vmware_v1.1.0_x5.0_windows_amd64.exe plugin: Received interrupt signal (count: 1). Ignoring.

[HackedRico]

Hey,

I faced a similar issue, however this thread helped. #982 (comment)

TLDR: It is an issue with the define "guest_os_type"