# override display mode if machine cannot nicely run X
if display_mode not in ('t', 'c') and not flags.usevnc:
- needed_ram = isys.MIN_GUI_RAM + extra_ram
+ needed_ram = needed_ram + isys.GUI_INSTALL_EXTRA_RAM
if not within_available_memory(needed_ram):
complain = _("You do not have enough RAM to use the graphical "
diff --git a/isys/isys.c b/isys/isys.c
index 409170b..ca3fb0d 100644
--- a/isys/isys.c
+++ b/isys/isys.c
@@ -313,6 +313,7 @@ void init_isys(void) {
Good question! Simple answer: I tried and it is enough (more precisely:
I tried a GUI installation, over nfs, with LVM+encryption, on a 384 MB
virtual memory machine and got over the "Finding storage devices" step,
that's the most critical, because GUI is already up and we make the LVM
calls there)
More elaboratively: I had to increase the MIN_RAM couple weeks ago, see
fbe24fe21350eec043d3f8ad41c1908b0878114a on master (there's also a
similar patch for rhel6). The commit message shows some numbers too, but
all of that was only tested during text install. It's very difficult to
find out exactly how much X+metacity+gtk+other-desktop-crap will take
together. I assumed I'd keep that at 256 MB extra, but then Hans
complained he can install over http with GUI on 512 MB. So you will
notice that while I increased the MIN_RAM by 128 MB I am decreasing the
MIN_GUI_RAM by 128 MB now. This makes some sense: we are now running
network manager (and who knows what else) in both text and gui install
and that might use dynamic libraries that are later reused by the gui
components (while earlier those were only loaded when X/gtk started).
That's my theory anyways but my experience seems to support it.
Ales
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
05-17-2010, 07:46 PM
Dennis Gilmore
memory: decrease the GUI limits a bit.
On Monday 17 May 2010 03:42:04 am Ales Kozumplik wrote:
> On 05/14/2010 04:25 PM, Bill Nottingham wrote:
> > Ales Kozumplik (akozumpl@redhat.com) said:
> >> diff --git a/isys/isys.h b/isys/isys.h
> >> index e3cb1fc..811b51b 100644
> >> --- a/isys/isys.h
> >> +++ b/isys/isys.h
> >> @@ -21,8 +21,9 @@
> >>
> >> #define H_ISYS
> >>
> >> #define MIN_RAM 262144 // 256 MB
> >>
> >> -#define MIN_GUI_RAM 524288 // 512 MB
> >> +#define GUI_INSTALL_EXTRA_RAM 131072 // 128 MB
> >>
> >> #define URL_INSTALL_EXTRA_RAM 131072 // 128 MB
> >>
> >> +#define MIN_GUI_RAM MIN_RAM + GUI_INSTALL_EXTRA_RAM
> >>
> >> #define EARLY_SWAP_RAM 524288
> >
> > What evidence is there that this is enough?
> >
> > Bill
>
> Good question! Simple answer: I tried and it is enough (more precisely:
> I tried a GUI installation, over nfs, with LVM+encryption, on a 384 MB
> virtual memory machine and got over the "Finding storage devices" step,
> that's the most critical, because GUI is already up and we make the LVM
> calls there)
>
> More elaboratively: I had to increase the MIN_RAM couple weeks ago, see
> fbe24fe21350eec043d3f8ad41c1908b0878114a on master (there's also a
> similar patch for rhel6). The commit message shows some numbers too, but
> all of that was only tested during text install. It's very difficult to
> find out exactly how much X+metacity+gtk+other-desktop-crap will take
> together. I assumed I'd keep that at 256 MB extra, but then Hans
> complained he can install over http with GUI on 512 MB. So you will
> notice that while I increased the MIN_RAM by 128 MB I am decreasing the
> MIN_GUI_RAM by 128 MB now. This makes some sense: we are now running
> network manager (and who knows what else) in both text and gui install
> and that might use dynamic libraries that are later reused by the gui
> components (while earlier those were only loaded when X/gtk started).
>
> That's my theory anyways but my experience seems to support it.
>
> Ales
Not that it matters much i guess but doing a install on a sparc64 system with
384MB ram unless using a plan text install with the minimal package set i
always get the install failing with OOM errors. as soon as i use vnc even
with a minimal package set install fails
Dennis
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
05-18-2010, 06:42 AM
Ales Kozumplik
memory: decrease the GUI limits a bit.
On 05/17/2010 09:46 PM, Dennis Gilmore wrote:
Not that it matters much i guess but doing a install on a sparc64 system with
384MB ram unless using a plan text install with the minimal package set i
always get the install failing with OOM errors. as soon as i use vnc even
with a minimal package set install fails
Dennis
You are very right. We just discovered it yesterday with Zdenek Kabelac
that the memory requirements for different architectures are varying
tremendously! For instance PPC64 needs 1 gb to go through a gui install.
We didn't try on sparc but I am going to assume something similar
happens there if that's got 64 kbit pages. See
memory: decrease the GUI limits a bit.
