Bug 138744 - kernel with 4G/4G imcaompatible with Virtual PC 2004
kernel with 4G/4G imcaompatible with Virtual PC 2004
Status: CLOSED WONTFIX
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
3
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Dave Jones
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-11-10 18:11 EST by David Sanders
Modified: 2015-01-04 17:11 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-11-10 20:23:41 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Screenshot of FC3 under Virtual PC 2004 after kernel modification (137.28 KB, image/jpeg)
2004-11-10 18:16 EST, David Sanders
no flags Details

  None (edit)
Description David Sanders 2004-11-10 18:11:41 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5)
Gecko/20041107 Firefox/1.0

Description of problem:
The kernel patch for 4G/4G mode does not work within a Microsoft
Virtual PC 2004 virtual machine.  An identical kernel built without
4G/4G mode works fine.

Version-Release number of selected component (if applicable):
kernel-2.6.9-1.667

How reproducible:
Always

Steps to Reproduce:
1.  Install FC3
2.  Reboot

    

Actual Results:  Segmentation faults

Expected Results:  boot up normally

Additional info:

Work around instructions at:
http://www.sandersweb.net/david/virtualpc/FedoraCore3.hmtl
Comment 1 David Sanders 2004-11-10 18:14:57 EST
URL should be:
http://www.sandersweb.net/david/virtualpc/FedoraCore3.html
Comment 2 David Sanders 2004-11-10 18:16:38 EST
Created attachment 106455 [details]
Screenshot of FC3 under Virtual PC 2004 after kernel modification
Comment 3 Warren Togami 2004-11-10 20:23:41 EST
Sorry, this is not our responsibility.  As a workaround you can use
the i586 kernel.  It is unfortunate that only Microsoft can fix this.

Note You need to log in before you can comment on or make changes to this bug.