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

Steve Walsh steve at nerdvana.org.au
Wed Feb 1 03:34:53 MST 2012


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?

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?


On 02/01/2012 01:05 AM, Edward C. Lang wrote:
> Hi,
>
> I just noticed this error in one of my KVM VMs on a stock HP Microserver
> N40L:
>
> edlang at shallot:/var/log$ grep SLUB syslog | tail -1
> Feb  1 00:35:20 shallot kernel: [800962.944409] SLUB: Unable to allocate memory on node -1 (gfp=0x20)
> edlang at shallot:/var/log$ grep SLUB syslog | wc -l
> 10
> edlang at shallot:/var/log$ grep SLUB syslog.* | wc -l
> 0
> edlang at shallot:/var/log$ free -m
>               total       used       free     shared    buffers     cached
> Mem:           366        360          5          0         24        243
> -/+ buffers/cache:         93        272
> Swap:          425         19        406
> edlang at shallot:/var/log$ uname -a
> Linux shallot 3.0.0-15-server #25-Ubuntu SMP Mon Jan 2 19:14:55 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
>
> There's lots of angriness from the kernel:
>
>      http://pastebin.com/S18Du5yj
>
> Nothing untoward appears in the host:
>
> edlang at lettuce:/var/log$ uname -a
> Linux lettuce 3.0.0-15-server #25-Ubuntu SMP Mon Jan 2 19:14:55 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
> edlang at lettuce:/var/log$ free -m
>               total       used       free     shared    buffers     cached
> Mem:          1975       1909         65          0          2       1011
> -/+ buffers/cache:        896       1078
> Swap:         1903         58       1845
> edlang at lettuce:/var/log$ grep '00:35:20' syslog
> edlang at lettuce:/var/log$ virsh dominfo shallot
> Id:             2
> Name:           shallot
> UUID:           0af41027-52a5-eb5c-d480-777e4d1a40bf
> OS Type:        hvm
> State:          running
> CPU(s):         1
> CPU time:       32614.5s
> Max memory:     393216 kB
> Used memory:    393216 kB
> Persistent:     yes
> Autostart:      enable
> Security model: apparmor
> Security DOI:   0
> Security label: libvirt-0af41027-52a5-eb5c-d480-777e4d1a40bf (enforcing)
> edlang at lettuce:/var/log$ virsh domifstat shallot vnet1
> vnet1 rx_bytes 30722038882
> vnet1 rx_packets 19773652
> vnet1 rx_errs 0
> vnet1 rx_drop 0
> vnet1 tx_bytes 31181762611
> vnet1 tx_packets 16977624
> vnet1 tx_errs 0
> vnet1 tx_drop 0
> edlang at lettuce:/var/log$ virsh domblkinfo shallot /var/lib/libvirt/images/shallot-root.img
> Capacity:       5368709120
> Allocation:     3401949184
> Physical:       3401949184
> edlang at lettuce:/var/log$ sudo grep '00:35:20' libvirt/libvirtd.log
> edlang at lettuce:/var/log$
>
>
> Any suggestions as to what may have caused this before I search further
> afield?
>
> Regards,
>
> Edward.
>

-- 
--==--
Steve Walsh, RHCE
Some random guy who does things with linux and conference networks



More information about the linux mailing list