On Thursday, August 16, 2018 at 7:35:26 PM UTC+2, Marcus Linsner wrote:
> $ cat /proc/meminfo
> MemTotal:        7454500 kB
> MemFree:         5635088 kB
> MemAvailable:    6574676 kB
> Buffers:           53832 kB
> Cached:          1094368 kB
> SwapCached:            0 kB
> Active:           724832 kB
> Inactive:         747696 kB
> Active(anon):     233816 kB
> Inactive(anon):    95768 kB
> Active(file):     491016 kB
> Inactive(file):   651928 kB
> Unevictable:       73568 kB
> Mlocked:           73568 kB
> SwapTotal:             0 kB
> SwapFree:              0 kB
> Dirty:               292 kB
> Writeback:             0 kB
> AnonPages:        398016 kB
> Mapped:            54320 kB
> Shmem:              5256 kB
> Slab:             134680 kB
> SReclaimable:      74124 kB
> SUnreclaim:        60556 kB
> KernelStack:        4800 kB
> PageTables:        10524 kB
> NFS_Unstable:          0 kB
> Bounce:                0 kB
> WritebackTmp:          0 kB
> CommitLimit:     3727248 kB
> Committed_AS:    1332236 kB
> VmallocTotal:   34359738367 kB
> VmallocUsed:           0 kB
> VmallocChunk:          0 kB
> HardwareCorrupted:     0 kB
> AnonHugePages:         0 kB
> ShmemHugePages:        0 kB
> ShmemPmdMapped:        0 kB
> CmaTotal:              0 kB
> CmaFree:               0 kB
> HugePages_Total:       0
> HugePages_Free:        0
> HugePages_Rsvd:        0
> HugePages_Surp:        0
> Hugepagesize:       2048 kB
> DirectMap4k:      327644 kB
> DirectMap2M:    14008320 kB
> DirectMap1G:           0 kB

I resumed the firefox compilation and noticed that the memory jumped back to 
14GB again - I was sure it was more than that 7.4GB before:

$ cat /proc/meminfo 
MemTotal:       14003120 kB
MemFree:         4602448 kB
MemAvailable:    6622252 kB
Buffers:          186220 kB
Cached:          1986192 kB
SwapCached:            0 kB
Active:          7482024 kB
Inactive:        1448656 kB
Active(anon):    6667828 kB
Inactive(anon):    95780 kB
Active(file):     814196 kB
Inactive(file):  1352876 kB
Unevictable:       73568 kB
Mlocked:           73568 kB
SwapTotal:             0 kB
SwapFree:              0 kB
Dirty:            306392 kB
Writeback:          4684 kB
AnonPages:       6811888 kB
Mapped:           199164 kB
Shmem:              5340 kB
Slab:             239524 kB
SReclaimable:     177620 kB
SUnreclaim:        61904 kB
KernelStack:        5968 kB
PageTables:        28612 kB
NFS_Unstable:          0 kB
Bounce:                0 kB
WritebackTmp:          0 kB
CommitLimit:     7001560 kB
Committed_AS:    8571548 kB
VmallocTotal:   34359738367 kB
VmallocUsed:           0 kB
VmallocChunk:          0 kB
HardwareCorrupted:     0 kB
AnonHugePages:         0 kB
ShmemHugePages:        0 kB
ShmemPmdMapped:        0 kB
CmaTotal:              0 kB
CmaFree:               0 kB
HugePages_Total:       0
HugePages_Free:        0
HugePages_Rsvd:        0
HugePages_Surp:        0
Hugepagesize:       2048 kB
DirectMap4k:      327644 kB
DirectMap2M:    14008320 kB
DirectMap1G:           0 kB


Oh man, I'm hitting that disk thrashing again after just a few minutes: 
202MiB/sec reading, 0.0 writing.

Paused qube, reading stopped.
Resumed qube sooner than before and it's still thrashing...

It'a a fedora 28 template-based VM.

I shut down another VM and I thought dom0 crashed because it froze for like 10 
sec before the notification message told me that that VM stopped.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/a0e7f45a-29fa-4330-ab43-eb4f31511bce%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to