From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: Need help with fixing the Xen waitqueue feature Date: Wed, 23 Nov 2011 23:12:36 +0000 Message-ID: References: <20111123223049.GA14423@aepfle.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20111123223049.GA14423@aepfle.de> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Olaf Hering Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 23/11/2011 22:30, "Olaf Hering" wrote: > After the vcpu hung I killed the guest and tried to start a new one. > Oddly enough I wasnt able to fully kill the guest, it remained in --p--d > state. Most vcpus were in paused state before that. Dying but kept as a zombie by memory references... > In another attempt I was able to run firefox in a guest. But after > trying to open all "latest headlines" in tabs the guest crashed. qemu-dm > log had alot of this (but nothing in xen dmesg): > track_dirty_vram(f0000000, 12c) failed (-1, 3) > > xl vcpu-list shows > (null) 1 0 - --p 47.3 any cpu > (null) 1 1 12 --- 13.4 any cpu > (null) 1 2 - --p 4.3 any cpu > (null) 1 3 - --p 7.8 any cpu > (null) 1 4 - --p 3.5 any cpu > (null) 1 5 - --p 1.9 any cpu > (null) 1 6 - --p 1.6 any cpu > (null) 1 7 - --p 1.4 any cpu > > Hmm, qemu-dm doesnt get killed in all cases, killing it destroys the guest.. > I have seen that before already. ...from qemu-dm. Problem is that toolstack is not killing qemu-dm, or qemu-dm is not responding to some shutdown signal. > I will provide more test results tomorrow. Thanks. -- Keir