[clug] KVM VM error: SLUB: unable to allocate memory on node -1

Edward C. Lang edlang at edlang.org
Wed Feb 1 04:40:35 MST 2012


On 01/02/2012 21:34, Steve Walsh wrote:
> I've seen this when the SLUB allocator can't allocate swap space (for
> whatever reason). Maybe run "mkswap -c" across your swap partition to
> check for bad blocks, etc?

root at shallot:~# grep swap /etc/fstab
# swap was on /dev/vda5 during installation
UUID=6fe61c6d-f31e-40b8-bcd2-f7669061f7ab none            swap    sw 
           0       0
root at shallot:~# ls -l /dev/vda5
brw-rw---- 1 root disk 253, 5 2012-01-22 18:06 /dev/vda5
root at shallot:~# mkswap -c /dev/vda5
/dev/vda5: Device or resource busy
root at shallot:~# free
              total       used       free     shared    buffers     cached
Mem:        375036     370460       4576          0       8052     275704
-/+ buffers/cache:      86704     288332
Swap:       436220      25788     410432
root at shallot:~# swapoff /dev/vda5
root at shallot:~# mkswap -c /dev/vda5
Setting up swapspace version 1, size = 436220 KiB
no label, UUID=d981c8a2-018f-46f3-9a1b-ad81800d46ab
root at shallot:~# free
              total       used       free     shared    buffers     cached
Mem:        375036     239612     135424          0       2388     132828
-/+ buffers/cache:     104396     270640
Swap:            0          0          0

So, no errors...

> Another issue may be the old bugbear that Ubuntu server 10.04 shipped
> with Plymouth (not sure why, they do nothing with it). Depending on the
> video driver, that may be causing issues. Does a "grep drm
> /var/log/syslog" or a "grep vga /var/log/syslog" show anything amiss?

This particular VM is running Ubuntu Server 11.10. Still:

root at shallot:~# egrep 'drm|vga' /var/log/syslog.1
root at shallot:~# egrep 'drm|vga' /var/log/syslog
root at shallot:~#

My initial web search turned up people with issues similar to the one 
you mentioned -- but looking at the kernel trace, and on the basis that 
it's a headless server VM, I think it's more likely to have been 
triggered by network gar. Which is why I wondered if something might 
show up in the host's view of the guest's network interface... but it 





More information about the linux mailing list