[Solved] Adjust The RAM Memory on VM

[KitchM]

I attempted to adjust the memory settings on my windows guest vm when it was not running. I looked into the settings for the VM from the VirtualBox interface screen. I looked under Settings>System>Motherboard, but there was no adjustment allowed because it was greyed out. The documentation did not appear to address that situation.

Any ideas how to raise the memory allocated?

Xubuntu 14.04 host 4GB/Windows ME guest 512MB (can't get video identified and working, nor shared folders)
VirtualBox Version 5.1.16 r113841 (Qt5.6.1) (download from VirtualBox.org)
Latest Guest Extensions (download from VirtualBox.org)

[socratis]

I attempted to adjust the memory settings on my windows guest vm when it was not running... there was no adjustment allowed because it was greyed out

The VM wasn't running, but it wasn't shutdown either. You had it either Paused or Saved state. That's similar to having the computer hibernate, not completely shut down.

[KitchM]

Thanks, socratis. That did the trick. Maybe that should be in the documentation under that subject.

[mpack]

Maybe that should be in the documentation under that subject.

https://www.virtualbox.org/manual/ch01. ... nfigbasics

The "Settings" button is disabled while a VM is either in the "running" or "saved" state. This is simply because the settings dialog allows you to change fundamental characteristics of the virtual computer that is created for your guest operating system, and this operating system may not take it well when, for example, half of its memory is taken away from under its feet. As a result, if the "Settings" button is disabled, shut down the current VM first.

[KitchM]

Good try but:

Maybe that should be in the documentation under that subject.

[socratis]

What "subject" would that be?
Because it is in Chapter 1 (as in "The Basics") under the title "1.11. Virtual machine configuration". I don't believe it can get more specific than that.

[KitchM]

4.9.1. Memory ballooning
3.4.1. "Motherboard" tab
among others

Any good writer will always put context-applicable notes where they belong. A documentor must not become fixated on worrying about duplicate notes.

[mpack]

The user manual can't repeat every small point on every occasion when a related subject comes up. The manual would be huge, and nobody would be able to understand it. There is a reason why such basic information is given up front, and why "it's chapter 1 guys" has become common parlance for things you are expected to know.

You failed to read the documentation, now you're rationalizing in order to avoid blaming yourself for your own error. Unfortunately it's an all too common behaviour on forums - and I'm sure that it has never fooled anyone. I am no saint, I've done similar things in the past, so with the advantage of experience I suggest to you that having the grace to admit your errors earns you more respect than does blaming others for them.

[KitchM]

@mpack
Unbelievable! Your ignorance of the situation comes from your obvious lack of understanding of what it is like on the other side of the issue. Your assumptions are what causes disrepute in this industry; the one I love.

I have fought for over thirty years to protect my customers from such short-sighted and thoughtless viewpoints, and I certainly will not stop now. Bad software is often viewed as such because of bad documentation. This is one good example.

I made no mistake. You have implied that VirtualBox is useless without reading and understanding the whole documentation for it. That's too bad. No software worth its salt should be viewed that way.

A president of an old software company once reminded me of the purpose of good software programming when he said that programmers forget the Maytag repairman. In other words, there should be no need of support because there should be no problems. The exact same thing can be said of documentation because it is intrinsic within proper intuitive design of the documentation that it should be clear at each point within it.

Obviously, you see no need to use the documentation as a reference work. You clearly imply that each user should always memorize the documentation in its entirety. That's just crazy. The only other possibility to you is to read it from the beginning every single time a question comes up. That is equally crazy. If that were the case, there would be no need of chapter or section divisions or even a table of contents or index. And I do not believe for an instant that you or anyone you know has memorized the user manuals, let along technical manuals, for every program they use on the computer.

This also shows the sad state of affairs in the computer support industry today. People who claim to want to help others really don't care for others. I, on the other hand, am never going to denigrate those who come to me for help. I am going to assume that I or someone else did not make something clear, and I am going to do all in my power to make sure that the one needing help goes away with the info they want and need.

As always, I stand ready to help with documentation any time anyone asks nicely. It is something that I understand very well. While I realize that there are many such as yourself who do not know how to do it correctly, I know of different ways to solve the problem I presented. Those who can't should get out of the way and allow those of us who can to get the job done.

[Perryg]

As always, I stand ready to help with documentation any time anyone asks nicely.

Since this is open source there is no one stopping you from contributing your expertise. If you want to re-write the manual please feel free as I am sure the DEVs would like nothing better. You can contact them to find out more on the dev mailing list, OR IRC and by all means please read the contrib section https://www.virtualbox.org/wiki/Contributor_information

Link to way to contact the DEVs https://www.virtualbox.org/wiki/Community

[socratis]

Just to correct a couple of mistaken assumptions, for future readers as well:

You clearly imply that each user should always memorize the documentation in its entirety. That's just crazy. The only other possibility to you is to read it from the beginning every single time a question comes up.

No one is expecting that. What *is* expected however, is that you do some basic search instead of posting a trivial question. So, if you search the PDF manual for "disabled", there are 46 references (as of 5.1.6). The first one says:

The settings are the same as would be available for the VM in the “Settings” dialog of the VirtualBox main window, but since that dialog is disabled while the VM is in the “running” or “saved” state, this extra menu saves you from having to shut down and restart the VM every time you want to change media.

and the 2nd one is from "Chapter 1.11 Virtual machine configuration" that mpack quoted. Are you still insisting about the lack of proper documentation?

This also shows the sad state of affairs in the computer support industry today.

You are definitely NOT in a support site. You are in a user's forum. If you were in a support forum your wallet would be a lot lighter, by at least 6100 $:

• We are not Oracle. We are simple users just like you.
• You are not a customer. You are a simple user just like us.

[KitchM]

@socratis
No mistaken assumption on my part.

No one is expecting that.

Of course that was the intent. Why the need to quibble? If the intent was to do a search, then that would have been stated.

So, if you search the PDF manual for "disabled", there are 46 references (as of 5.1.6).

Why would someone search for "disabled"? That in and of itself is presumptuous. Now you are going to condemn someone because they do not search as you would or even read the document in the format you would. Shame on you. If, on the other hand, that is the case, then your have made my point for me. Another flaw in the documentation. Further, quoting non-applicable references does not help your case, but it does indicate that someone did not understand the original request.

But, since we're on the subject, how much time should a person spend in searching? Would that be five minutes? Fifteen? Thirty? An hour? What if they still didn't find the answer? Should they then have read the whole manual over again? Where does your demand end? And just how do you define "basic"? Where do you state the words and/or phrases one should use in said search?

You are definitely NOT in a support site

Wrong again. Of course it is a support site. Another quibble. It is all a part of the support mechanism in the computer world. And, by the way, there isn't one person in 100,000 who would recognize any difference in support forum versus user forum. Another quibble, and without any basis whatsoever. And it doesn't have a damn bit to do with getting paid. Oh and by the way, there is no foundation for calling me a "customer". I certainly did not call you "Oracle". And no, you are not a user like me. You are a forum moderator who should know better.

Here is what people like yourselves do not understand. You should do it because you like to and because you wish to help others. It is clearly obvious that you come to the table with unfriendly bias. No one is forcing you to help. You weren't even required to answer this post. If you don't like it, move aside and let others. That is what a forum is all about.


@Perryg
Thank you for that direction. I will certainly document what I have learned here so that others can benefit. I trust that the powers that be have made it easy to do so.

[Perryg]

@Perryg
Thank you for that direction. I will certainly document what I have learned here so that others can benefit. I trust that the powers that be have made it easy to do so.

They have made it as easy as possible given it is cross platform and other factors. They do have specific instruction as to how to do it. It is not like a word document. It is compiled from xml, but is doable. Various reason for this as well because the documentation needs to be translated to various languages and is compatible to other vendors branding, Etc..

[KitchM]

I can appreciate all that. Well, let's give it a try and see how it goes. It is certainly worth a shot.

Thanks much.

[KitchM]

Perryg, I tried to go to the links you suggested. The second one did not seem to apply to documentation contributions. The first one did, but didn't link me to any pertinent place to submit or make changes. Maybe I'm missing something, but I don't see it. Please advise.