Memory and swap history on fedora 23 host

[Lizzie]

I am running windows 8.1 on VB. I have a program that is constantly failing due to "low memory". When I check VB, it shows that I have 2.93 GB of RAM and 20.4 GB of free drive space. When I use System Monitor to check the host, it shows that I I am using 85% or 4.9 GB of my memory 5.7 GB memory. I am also using 8.3 MB of 5.7 GB of my swap space. is it possible to increase the memory available and if so how? I have 811 GB of hard drive space available. Mys host system is Fedora 23.

[Perryg]

Moved to Windows guest

[Lizzie]

Moved to Windows guest

Excuse me!! How is increasing the HOST memory a guest problem?????

[Perryg]

There is only one way to increase the host memory. Adding more memory. Swap will not help because the guests memory allocated must be actual memory. It appears from what you posted that the guest is having the issue and that is why I moved to to where a Windows person can help you. If you prefer I will move it back but given your issue I thought you would be better served here.

[mpack]

First of all: please be precise about the warning message you saw. Even provide a screenshot. Make it clear whether "memory" refers to RAM or disk space? You mention both, but the warning will be specific to one or the other.

If the guest OS doesn't have enough RAM then you have to change the VM recipe to add more. Note however that you can only give the VM more RAM if the host can afford it, and you've given us no information on that.

To give us solid information please post a VM log file. With the VM fully shut down, right click and "Show Log" in the GUI, save "VBox.log" (ONLY) to a zip, and attach the zip here.

[Lizzie]

Here are the exact error messages I am receiving.

Error: One factory fails for the operations "stream" Your computer has run out of memory. Please close the application and then start it up again to continue. This followed by an OK button. After I click OK, the same message comes up again. The third message is as follows: Corrupt Image. Unable to display image. The image file has probably been corrupted. do you want to ge a new copy from the from server? YES No Details

I have uploaded the details in the file "Indexing error message details" and the VBox.log. Both of them should be in LogFile.zip

[mpack]

This sounds like an guest application error, so nothing to do with VirtualBox at all.

I've looked at the log and 2GB RAM allocated to the guest is fine for your host, so it is not the host which has a RAM problem. As to disk space, a 40GB drive seems good to me, and I see nothing in the log say that it couldn't allocate corresponding disk space on the host, so again that means a guest problem which again has nothing to do with VirtualBox.

You are missing the screenshot I asked for. In addition to the text this would have given me the context of the error. I have no idea how to use an ODT file.

[Lizzie]

An .odt file is from LibreOffice. I have changed it to a .docx file so it can be read with MS Word. also in the zip file is now the screen shot. I am really hoping that this is an application error and not a VB error as it then becomes someone else's responsibility to fix and not mine.

[mpack]

If LibreOffice is reporting the error then it's an application error. A a rule of thumb, it's a VirtualBox error only if the error is reported by the VirtualBox process on the host.

I have deleted your second attachment, most of which seemed to be redundant: I already had the VBox log, and I didn't actually ask to see the contents of the ODT, since I know it isn't a VirtualBox log. I retained your screenshot - after cropping it to the useful portion.

To me this looks like an application bug. A runaway function is allocating memory in a loop until it runs out. Adding memory will not fix such a problem. Running in a VM is not relevant to such a problem. You should ask about this is in a LibreOffice forum, and explain exactly what was being done at the time.

[Lizzie]

Finally figured out what the problem was. It was indeed a memory problem. My trash on the host would not empty. After i went in and individually deleted every file, there were some very large ones, i no longer had the problem.

Lizzie