• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

Re: Fedora 9: install attempts freeze

D

David Sanders

#1
dryii wrote:

> I'm attempting to create a new virtual machine in Virtual PC 2007
> (6.0.156.0) for Fedora 9. I downloaded the DVD ISO last night. I
> created a new VM with 1GB of memory and 16GB disk. I can boot the VM
> and have successfully booted off the ISO image.
>
> The problem? No matter what options I put for booting (text vs GUI
> doesn't matter, either) the load stops around the following area:
> system 00:0c: iomem range 0x0-0x0 could not be reserved
>
> It doesn't stop on that line every time, but near/around that part of
> the boot process. When it hits the freeze, I have to reset the VM.
> CTRL-ALT-DEL doesn't work. I'm not getting the "unrecoverable
> processor error", but I did try adding the 'noreplace-paravirt'. It
> didn't help.
>
> Any suggestions on what I might try to get this loaded?
(1) Have you checked the sha1sum of the file you downloaded? Sounds
like a corrupt iso.
(2) Are you using Fedora-9-i386-DVD.iso or Fedora-9-i386-netinst.iso ?
(3) Whichever you are using, try the other one.
(4) It works here, but only with the noreplace-paravirt boot parameter.
You will need the same.
Good luck. David
 

My Computer

B

Bob Babcock

#2
dryii wrote:

> I'm attempting to create a new virtual machine in Virtual PC 2007
> (6.0.156.0) for Fedora 9. I downloaded the DVD ISO last night. I
> created a new VM with 1GB of memory and 16GB disk. I can boot the VM
> and have successfully booted off the ISO image.
>
> The problem? No matter what options I put for booting (text vs GUI
> doesn't matter, either) the load stops around the following area:
> system 00:0c: iomem range 0x0-0x0 could not be reserved
What type of CPU do you have? I ran into the same problems with an Athlon
64 X2 5600+ (dual-core), but it seems to be working on an Athlon XP-A 2800+
(single-core). (Packages are being installed as I type this.) I did use
the noreplace-paravirt boot parameter. Assuming the install finishes, I'll
copy the VM to my dual-core machine and see if it works there.
 

My Computer

B

Bob Babcock

#3
Having built a Fedora 9 VM on a single-core AMD system, I find that I can
run it on my dual-core system without needing to provide any special boot
parameters. I have no idea why I can't do the install with dual-core, or
if that is even what causes the failure.

It's not quite right; video is messed up most places where the VM should be
in text mode.
 

My Computer

D

David Sanders

#4
Bob Babcock wrote:

> dryii wrote:

>> I'm attempting to create a new virtual machine in Virtual PC 2007
>> (6.0.156.0) for Fedora 9. I downloaded the DVD ISO last night. I
>> created a new VM with 1GB of memory and 16GB disk. I can boot the VM
>> and have successfully booted off the ISO image.
>>
>> The problem? No matter what options I put for booting (text vs GUI
>> doesn't matter, either) the load stops around the following area:
>> system 00:0c: iomem range 0x0-0x0 could not be reserved
>
> What type of CPU do you have? I ran into the same problems with an Athlon
> 64 X2 5600+ (dual-core), but it seems to be working on an Athlon XP-A 2800+
> (single-core). (Packages are being installed as I type this.) I did use
> the noreplace-paravirt boot parameter. Assuming the install finishes, I'll
> copy the VM to my dual-core machine and see if it works there.
I have a Pentium D. For an AMD processor I don't think you need
noreplace-paravirt, but I'm not sure.
 

My Computer

B

Bob Babcock

#5
David Sanders <news@xxxxxx> wrote in
news:OUToYy2EJHA.1268@xxxxxx:

> I have a Pentium D. For an AMD processor I don't think you need
> noreplace-paravirt, but I'm not sure.
Perhaps not. I just tried booting the Fedora 9 install DVD on my single-
core AMD system and it works with default parameters. Noreplace-paravirt
may change exactly where the dual-core system hangs the installer, but it
certainly doesn't make it work.
 

My Computer

B

Bob Babcock

#6
Bob Babcock <wssddc@xxxxxx> wrote in
news:Xns9B15E2F64593Awssddcgisnet@xxxxxx:

> David Sanders <news@xxxxxx> wrote in
> news:OUToYy2EJHA.1268@xxxxxx:
>

>> I have a Pentium D. For an AMD processor I don't think you need
>> noreplace-paravirt, but I'm not sure.
>
> Perhaps not. I just tried booting the Fedora 9 install DVD on my
> single- core AMD system and it works with default parameters.
> Noreplace-paravirt may change exactly where the dual-core system hangs
> the installer, but it certainly doesn't make it work.
I made a list of valid boot parameters that I found in a Google search and
tried various combinations. I find that either
ide0=noprobe
or clock=pit
(or both) allow the installer to start. I cannot explain why these
seemingly very different parameters both work, nor can I explain why only
the installer needs them. I did not do an install, but I did take it
several screens into the GUI.
 

My Computer

S

Silver1882

#7
Thanks for the Ideal to get this to install
"Bob Babcock" wrote:

> Bob Babcock <wssddc@xxxxxx> wrote in
> news:Xns9B15E2F64593Awssddcgisnet@xxxxxx:
>

> > David Sanders <news@xxxxxx> wrote in
> > news:OUToYy2EJHA.1268@xxxxxx:
> >

> >> I have a Pentium D. For an AMD processor I don't think you need
> >> noreplace-paravirt, but I'm not sure.
> >
> > Perhaps not. I just tried booting the Fedora 9 install DVD on my
> > single- core AMD system and it works with default parameters.
> > Noreplace-paravirt may change exactly where the dual-core system hangs
> > the installer, but it certainly doesn't make it work.
>
> I made a list of valid boot parameters that I found in a Google search and
> tried various combinations. I find that either
> ide0=noprobe
> or clock=pit
> (or both) allow the installer to start. I cannot explain why these
> seemingly very different parameters both work, nor can I explain why only
> the installer needs them. I did not do an install, but I did take it
> several screens into the GUI.
>
 

My Computer