Ubuntu 14.04 Host and Guest Error involving 'rc=VERR_NO_MEM'

[Boring]

Hi,

As the title suggests, I'm running ubuntu 14.04 as both the host and guest. My guest keeps being aborted with the following in the log:

01:11:53.814786 VGA Sequencer (3C5): SR index 3C4:04
01:11:53.814788 SR00:03 SR01:00 SR02:0F SR03:00 SR04:0A
01:11:53.814798 !!
01:11:53.814798 !! {vgatext}
01:11:53.814799 !!
01:11:53.814801 Not in text mode!
01:11:53.814802 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
01:11:53.814840 emR3Debug: rc=VERR_NO_MEMORY
01:11:54.815637 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'
01:11:54.815673 Console: Machine state changed to 'GuruMeditation'
01:15:54.310203 Console: Machine state changed to 'Stopping'


I've searched around and haven't found anyone with the same situation, and I thought it might be helpful to come here for input.

Thanks!!

[Perryg]

Post the guests log file ( as an attachment )

[Boring]

Post the guests log file ( as an attachment )

I only posted the last 500 lines due to the size limit.

[Boring]

Post the guests log file ( as an attachment )

It's probably worth noting that this kept happening when I tried to do a large rsync from a remote server to the guest.

I left the guest running last night with no rsync running, and it's still kicking without going into the aborted state.

[Perryg]

Well the last lines don't tell me anything. I bet if you compressed it the whole file would fit. Did you try that?

[Boring]

Well the last lines don't tell me anything. I bet if you compressed it the whole file would fit. Did you try that?

You are correct! Attached.

[Perryg]

Humm.

Well you have a few things you can do and I'll post them below. From the looks of it you are hitting a memory ceiling and trying to go beyond it. I checked your processor and it can handle the memory you have but that does not mean the chipset, or bios will. For that you would need to check with your MB manufacture. It may be possible the the msr VBox chooses can't deal with your processor and memory usage either.

1) decrease the guests memory
2) check for new bios and update it.
3) post a ticket at bugtracker and see what the DEVs have to say (don't forget the log file ).

Just out of curiosity, why so much memory ( 235 GB ) in the Linux guest?

[Boring]

Humm.

Well you have a few things you can do and I'll post them below. From the looks of it you are hitting a memory ceiling and trying to go beyond it. I checked your processor and it can handle the memory you have but that does not mean the chipset, or bios will. For that you would need to check with your MB manufacture. It may be possible the the msr VBox chooses can't deal with your processor and memory usage either.

1) decrease the guests memory
2) check for new bios and update it.
3) post a ticket at bugtracker and see what the DEVs have to say (don't forget the log file ).

Just out of curiosity, why so much memory ( 235 GB ) in the Linux guest?

I deal with bioinformatics programs that can use all the resources they can get. I also deal with very large databases. Configuration for a specific workflow pipeline is a problem, since configurations between workflow pipelines can conflict with each other, and in some cases, threaten the OS integrity. I was interested in creating an image with all the databases needed and with a clean OS, then converting it to a multiattach-moded image and using that image as a base for each VM dedicated to each pipeline.

[Perryg]

Thanks for the explanation.

[Boring]

Thanks for the explanation.

I've created ticket 14318. thanks!

[Perryg]

Thank you. Below is the direct link

https://www.virtualbox.org/ticket/14318