WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] cannot release un-aquired lock

To: Xen List <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] cannot release un-aquired lock
From: James Pifer <jep@xxxxxxxxxxxxxxxx>
Date: Mon, 03 May 2010 11:25:23 -0400
Delivery-date: Mon, 03 May 2010 08:26:52 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Two of my xen servers that have been running for 64 days both have this
error when I try to start a domU. It came up because I tried to restart
one. 

This one happened to be only running 5 domUs, so I was able to stop the
other four. Then I restarted the xend service. This seemed to clear up
the issue. The other server is running double the domUs so it will be
harder to do. 

dom0 has 2048M of ram assigned to it. The rest of the 32GB is for domUs.

Anyone know what causes this error? I found one thread that seemed to
indicate that dom0 was stuck, but didn't give any solutions are causes
other than restarting. 

Thanks,
James


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] cannot release un-aquired lock, James Pifer <=