VirtualPC2004 plus fedoraCore4

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Has anyone managed to install fedora core 4 within VirtualPC. For what it is
worth, Managed to install fedora 4 within VirtualPC, however upon the reboot
request not a great deal happened. Am I attempting to achieve the impossible
or have I missed a vital step?

Regards,

Mark G.
 
It is no coincidence that "Marxin said:
Has anyone managed to install fedora core 4 within VirtualPC. For what it
is
worth, Managed to install fedora 4 within VirtualPC, however upon the
reboot
request not a great deal happened. Am I attempting to achieve the
impossible
or have I missed a vital step?

Regards,

Mark G.


Did you remember to "release" the CD drive / .iso file on the reboot via the
menus?
 
I can only presume that I did, because the only options available to me upon
trying to boot my Fedora4 VirtualPC were:

Use Physical Drive E:
&
Capture ISO Image:

So... to try and fathom why the VirtualPC halted after about four automated
<CR> , I chose Use Physical Drive E:, re-inserted the install CD to attempt
to 'update' my installation. Boot info got as far as:

.......
running install.....
running /sbin/loader

at which point it froze. So, tried your suggestion 'releaseCD' , result was
umounting filesystems....

{final umount:} /selinux done
you may safely reboot your system

Then went to Action menu, initiated close (with install CD removed) then I
started the VirtualPC but was unfortunately greeted with the initial 5 lines
of boot info about primary/secondary devices, a clear screen, a flashing
underscore cursor which <CR> four times and then .... nothing

Any diagnostics I can use to analyse the attributes of a 'virtual' install ?

regards,

Mark G.
 
It is no coincidence that "Marxin said:
I can only presume that I did, because the only options available to me
upon
trying to boot my Fedora4 VirtualPC were:

Use Physical Drive E:
&
Capture ISO Image:

So... to try and fathom why the VirtualPC halted after about four
automated
<CR> , I chose Use Physical Drive E:, re-inserted the install CD to
attempt
to 'update' my installation. Boot info got as far as:

......
running install.....
running /sbin/loader

at which point it froze. So, tried your suggestion 'releaseCD' , result
was
umounting filesystems....

{final umount:} /selinux done
you may safely reboot your system

Then went to Action menu, initiated close (with install CD removed) then I
started the VirtualPC but was unfortunately greeted with the initial 5
lines
of boot info about primary/secondary devices, a clear screen, a flashing
underscore cursor which <CR> four times and then .... nothing

Any diagnostics I can use to analyse the attributes of a 'virtual' install
?

regards,

Mark G.



You could try giving the Virtual Machine a higher dosage of Ram eg 128 mb or
preferably higher. Lack of Ram can sometimes cause freezing up.


Click on 'Settings' for that particular virtual machine to change it.
 
It is no coincidence that "Jon said:
You could try giving the Virtual Machine a higher dosage of Ram eg 128 mb
or preferably higher. Lack of Ram can sometimes cause freezing up.


Click on 'Settings' for that particular virtual machine to change it.

Looks like it does require a fair amount of RAM, so that could well be the
cause.

According to this page 192 mb +

http://fedora.redhat.com/docs/release-notes/fc4/errata/

From the page......
4.3. Memory Requirements
This section lists the memory required to install Fedora Core 4.

This list is for 32-bit x86 systems:

a.. Minimum for text-mode: 64MB

b.. Minimum for graphical: 192MB

c.. Recommended for graphical: 256MB
 
Has anyone managed to install fedora core 4 within VirtualPC. For what it
is
worth, Managed to install fedora 4 within VirtualPC, however upon the
reboot
request not a great deal happened. Am I attempting to achieve the
impossible
or have I missed a vital step?

This isn't an XP OS issue.
 
Back
Top