Summary: | app-emulation/vmware-player-3.1.3.324285 with gentoo-sources-2.6.38-r1 - vmware-vmx invoked oom-killer | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | DaggyStyle <daggs> |
Component: | Current packages | Assignee: | Matt Whitlock <gentoo> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | CC: | vadimk, vmware+disabled |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
.config
crash log log crash |
Description
DaggyStyle
2011-03-30 18:15:44 UTC
Created attachment 267871 [details]
.config
Created attachment 267873 [details]
crash log
Are you allocating more memory to the virtual machine than the host machine has free? That will easily cause an OOM condition, which is to be expected. I don't see a kernel panic in your log, only an OOM kill. (In reply to comment #3) > Are you allocating more memory to the virtual machine than the host machine has > free? That will easily cause an OOM condition, which is to be expected. > well, intentionally no, I haven't configure it anywhere nor I know where to configure it. I'm currently use 2.6.38 and it works ok, when I switch to 2.6.38-r1, this happens, thus I assume it has something to do with the delta of these too releases. I'll try reemerging the kernel and test again. > I don't see a kernel panic in your log, only an OOM kill. mmmm right, I've assumed it is a panic because of the auto reboot it generates. Created attachment 268617 [details]
log crash
still occurring, system gets reboot after that.
(In reply to comment #5) > Created attachment 268617 [details] > log crash > > still occurring, system gets reboot after that. Please provide meminfo: cat /proc/meminfo cat /VMWARESTORAGE/VMNAME/VMNAME.vmx | grep mem |