I think you'll find that nested kvm and ksm will be a worst-case
scenario w.r.t memory swap-out. KSM actively scans the hosts memory for
pages it can unmap , which means when a guest (level 1) or nested guest
(level 2) needs to write to that memory, then you incur a page table
walk (Guest virtual
I have a different VM that has crashed (also nested nova compute), this
one had ksm disabled. See log attached.
** Attachment added: soft-lockup-different-node.log
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1413540/+attachment/4303814/+files/soft-lockup-different-node.log
** Changed
Any information about the physical host running the L1 guest?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1413540
Title:
issues with KSM enabled for nested KVM VMs
To manage
** Summary changed:
- qemu-kvm package enables KSM on VMs
+ issues with KSM enabled for nested KVM VMs
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1413540
Title:
issues with KSM
