Skip to content

Use a network adapter based on guest os and hypervisor cpu architecture #260

@der-eismann

Description

@der-eismann

Overview of the Issue

I thought I was going crazy. I tried to create a box with Fedora 40 and most settings on default, however it always had a kernel panic when booting. But when I create the VM via the GUI it worked fine. I tried to find the issue for ~30 mins until I saw that this plugin used the e1000 network adapter as default while the GUI used e1000e as default.
IMHO e1000e should be the default because as VMware says

Emulated version of the Intel 82574 Gigabit Ethernet NIC. E1000E is the default adapter for Windows 8 and Windows Server 2012.

Both OSes were released over 10 years ago and are not even supported anymore. Using a default that may not even work on modern systems is not good.
But if we don't want to change the default, at least mention e1000e in the docs.

Reproduction Steps

  1. Execute packer build

Plugin and Packer version

packer 1.11.2 & plugin 1.1.0

Simplified Packer Buildfile

source "vmware-iso" "fedora-vmware-arm64" {
  guest_os_type    = "arm-fedora-64"
  version          = 21
  iso_checksum     = "690731ac6abba81413d97517baa80841cb122d07b296ec3f2935848be45be8fe"
  iso_url          = "https://download.fedoraproject.org/pub/fedora/linux/releases/40/Server/aarch64/iso/Fedora-Server-netinst-aarch64-40-1.14.iso"
  usb              = true
  vmx_data = {
    "usb_xhci.present" = "true"
  }
  cdrom_adapter_type = "sata"
  disk_adapter_type  = "nvme"
  # try with and without the next line
  # network_adapter_type = "e1000e"
}

Operating system and Environment details

macOS 15.1 as host with VMware Fusion 13.6.1 and Fedora 40 as guest

Log Fragments and crash.log files

None

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions