Bug 1433006

Summary:	iPXE timeout with e1000 on VMware 6.0.0
Product:	Red Hat Enterprise Linux 7	Reporter:	Evgeni Golov <egolov>
Component:	ipxe	Assignee:	Neil Horman <nhorman>
ipxe sub component:	ipxe-bootimgs	QA Contact:	Raviv Bar-Tal <rbartal>
Status:	CLOSED NOTABUG	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	arnaud.coquelet
Version:	7.2
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-08-17 13:04:46 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Evgeni Golov 2017-03-16 14:45:26 UTC

Description of problem:

VMware ESXi 6.0.0 5050593
Trying to boot a Satellite 6 bootdisk containing iPXE 20160127-5.git6366fa7a.el7 hangs during fetch of the kickstart file when E1000 NIC is used. Works fine on vmxnet3.

Version-Release number of selected component (if applicable):
ipxe-bootimgs-20160127-5.git6366fa7a.el7.noarch (from rhel-7-server-rpms)

How reproducible:
randomly

Steps to Reproduce:
1. generate a bootdisk in Sat6
2. boot it on vmware with e1000 nic

Actual results:
machine hangs when transfering data

Expected results:
data is fetched fine

Additional info:

Comment 2 Arnaud Coquelet 2017-05-12 21:19:26 UTC

Could that be related to that? https://access.redhat.com/solutions/1990993

Here is a copy of the content of that link,

Issue:
Trying to boot one of the bootdisks (host image or generic image) generated by Satellite in VMware does not work
Timeouts/hangs during early network communication with the Satellite/Capsule (e.g. while fetching the iPXE configuration, the kernel or the initrd)

Resolution:
VMXNET3 network cards should be used for the VMware guest system.

Root Cause:
gPXE sometimes has problems with various emulated E1000 and similar cards, compatible types should be used. Possibly other emulated VMware network cards are affected.

Comment 3 Neil Horman 2018-08-17 13:04:46 UTC

based on comment 3, this seems like notabug to me.  Please reopen if that is not the case.