Re: In kvm, a single process cannot allocate more than 3.6GB ram. Why?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 12/12/2009 12:11 PM, Tanel Kokk wrote:

[root@lu2-kvm-db1 ~]# cat /proc/meminfo
MemTotal:       10267308 kB
MemFree:          228944 kB
Buffers:           19680 kB
Cached:          6069524 kB
SwapCached:            0 kB
Active:          8175200 kB
Inactive:        1374884 kB
Active(anon):    3238044 kB
Inactive(anon):   544104 kB
Active(file):    4937156 kB
Inactive(file):   830780 kB
Unevictable:           0 kB
Mlocked:               0 kB
SwapTotal:             0 kB
SwapFree:              0 kB
Dirty:             15968 kB
Writeback:             0 kB
AnonPages:       3461108 kB
Mapped:           327816 kB
Slab:             171452 kB
SReclaimable:     121756 kB
SUnreclaim:        49696 kB
PageTables:       244268 kB
NFS_Unstable:          0 kB
Bounce:                0 kB
WritebackTmp:          0 kB
CommitLimit:     8727208 kB
Committed_AS:    6056168 kB
VmallocTotal:   34359738367 kB
VmallocUsed:       38180 kB
VmallocChunk:   34359645255 kB
DirectMap4k:        4032 kB
DirectMap2M:    10481664 kB

What guest kernel is this? What's the value of the guest's /proc/sys/vm/overcommit_memory?

--
error compiling committee.c: too many arguments to function

--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux