Bug 206880

Summary: Error when installing Fedora Core 6 Test 3 with VMWare 1.0.1-4 on Ubuntu 6.06
Product: [Fedora] Fedora Reporter: Sense Hofstede <sense.pc>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED CANTFIX QA Contact: Mike McLean <mikem>
Severity: medium Docs Contact:
Priority: medium    
Version: 6   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-09-18 17:54:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
20GB.vmdk, fedora.vmx, install01.png none

Description Sense Hofstede 2006-09-17 17:29:07 UTC
Description of problem:
When installing Fedora Core 6 Test 3 from the i386 DVD with VMWare 1.0.1-4 on
Ubuntu Dapper Drake 6.06, I get thid error:
ISOLINUX 3.11 2005-09-02 Copyright (C) 1994-2005 H. Peter Anvin
Unknown keyword in config file.
Missing parameter in config file.
Unknown keyword in config file.
Unknown keyword in config file.
Missing parameter in config file.
Missing parameter in config file.
Unknown keyword in config file.
Missing parameter in config file.
Unknown keyword in config file.
Missing parameter in config file.
Missing parameter in config file.
Unknown keyword in config file.
Unknown keyword in config file.
Could not find kernel image: linux
boot:

The second time I've got the same message. 


How reproducible:
Very easy.

Steps to Reproduce:
1.Download the attachment and the .iso of the Fedora Core 6 Test 3 DVD for i386
2.Use the .vmx, .vmdk and the .iso with VMPlayer.

In the attachment:
-20GB.vmdk
-fedora.vmx
-install01.png(a screenshot of the error.

Comment 1 Sense Hofstede 2006-09-17 17:29:08 UTC
Created attachment 136490 [details]
20GB.vmdk, fedora.vmx, install01.png

Comment 2 Jeremy Katz 2006-09-18 17:54:55 UTC
This looks like a vmware bios bug