Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Failure sending boot commands to RHEL/CentOS builds as of Workstation 17.6#330

Copy link
Copy link
@AdamRichman

Description

@AdamRichman
Issue body actions

Community Note

  • Please vote on this issue by adding a 馃憤 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

When filing a bug, please include the following headings if possible. Any
example text in this template can be deleted.

Overview

VMware ISO builds for RHEL and CentOS (for Broadcom VMware Workstation 17.6+) fail to send in boot_commands or any interactions to the virtual machine during initial boot.

I have been running into this issue consistently with VMware ISO builds - either JSON or HCL build files - since the migration to Broadcom VMware Workstation 17.6. Irrespective of any boot_commands I add, nothing seems to ever register in the VM itself. This means that any version of for BIOS builds or arrow commands and "e" for EFI builds ever register. My build.json files worked for every prior version of VMware Workstation Pro from 15 on and I have seen this issue from older versions of Packer (1.8.6) and the most current version (including the most recent VMware Windows plugin). I have been able to reproduce this issue on three different machines (thus feel this is not a workstation issue). I have stripped my old (then-working) build.json files down to the most rudimentary and it never successfully sends the or anything else to interrupt the build to send in my kickstart files.

Reproduction Steps

Using a very simplified build.json file, run packer build .\CentOS-9-build.json
Note the tab will never register in VMware Workstation (17.6) to interrupt and replace the base instruction with the build's ks.cfg instrutction. CentOS will simply run through its 59s count-down to start and start and subsequently hang on the language selection.

Packer version

1.12.0

Simplified Packer Template

https://github.com/AdamRichman/packer_issue/tree/main

Operating system and Environment details

Windows 11
Version 10.0.26100 Build 26100

Log Fragments and crash.log files

https://github.com/AdamRichman/packer_issue/blob/main/Extended-Build-log.txt

Zachary-Richman

Metadata

Metadata

Assignees

Type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions

    Morty Proxy This is a proxified and sanitized view of the page, visit original site.