We changed default video RAM sizes in https://bugzilla.redhat.com/1275539 to more suitable values in current environments. It might be additionally useful to permit the users to override those values in osinfo. This way, the user could set his own values for different guest OSes and cluster versions if needed. There should be basically three values adjusted: vram, ram and vgamem. Each of them may or may not depend on number of heads of a single-PCI device. Please note that: - Video RAM is currently configured on device changes. As the user can change the parameters in osinfo, the video RAM should be probably reconfigured on each VM start. - The question is how to handle VMs transferred from 3.5 clusters to newer clusters with respect to different video RAM sizes for different cluster version. (The question applies even in the current state, without the changeable osinfo properties.) - It should be considered whether the configuration for particular environment should be specified as a single osinfo parameter or multiple osinfo parameters.
Do we really expect the users to know what the right values are? I'd expect them actually to choose number of monitors and requested resolution, and we'll do the math behind the scenes for them.
(In reply to Yaniv Kaul from comment #1) > Do we really expect the users to know what the right values are? > I'd expect them actually to choose number of monitors and requested > resolution, and we'll do the math behind the scenes for them. Most users should expect and have exactly that, but we'd like to have means to tweak the settings in case some advanced user has special arrangements or needs.
(In reply to Yaniv Kaul from comment #1) a need for changing the values came up couple of times before, so I do expect there are cases when it would be helpful even now, despite our "math" is a bit better than before.
did not make 4.1