0

On a physical host running Ubuntu 12.04.4 LTS and serving as a hypervisor via qemu, hosting a single guest, I've issued:

swapoff -a

To the host, which hung for several minutes before kicking me out of the console. I was unable to get back onto the host, and found that it had rebooted, which required manual intervention via the DRAC.

I'm trying to run through the logs now to see what might have caused this, but not finding anything obvious - which is to say I'm not sure what to show here to you folks. I'm not finding oom_killer tomfoolery in dmesg, kern.log, or syslog.

When the host came back up, swap was properly off and there was no swapping occurring on the host.

enter image description here

  • What was the state of the memory before you run the command "swapoff -a" ? If you had not enough memory, this could be the issue. According to the graph "Memory Committed", it looks like the Total of RAM get divided by 2 suddenly (the line in red CommitLimit). How many swap did you allocate ? The total RAM allocated is still at 64GB and "CommitLimit" show 32GB. What kind of physical RAM are in this server ? Check if there are no issue with the physical RAM maybe. – perko Dec 11 '19 at 14:18

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.