[Bug 1905562] Re: Guest seems suspended after host freed memory for it using oom-killer

2021-07-09 Thread Launchpad Bug Tracker
[Expired for QEMU because there has been no activity for 60 days.] ** Changed in: qemu Status: Incomplete => Expired -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1905562 Title: Guest

[Bug 1905562] Re: Guest seems suspended after host freed memory for it using oom-killer

2021-05-09 Thread Thomas Huth
The QEMU project is currently moving its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting the bug state to "Incomplete" now. If the bug has already been fixed in the latest upstream version of QEMU, then

[Bug 1905562] Re: Guest seems suspended after host freed memory for it using oom-killer

2020-11-25 Thread James Harvey
Am I correct to expect the VM to continue successfully, after oom-killer successfully freed up memory? This journactl does show a calltrace which includes "vmx_vmexit", and I'm not sure what that function is for but looks a little worrisome. ** Attachment added: "section or journalctl from host,