From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Wright Subject: First DomU started goes into a busy loop Date: Mon, 24 Sep 2012 16:31:27 +0100 Message-ID: <50607CCF.9050904@overnetdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On a 32 bit Xen 4.20 system with a 3.5.4 kernel around 40% of the time when the system starts up the first DomU to be started goes into a busy loop (always in state r----- which CPU constantly increasing) with no console output. If I destroy the DomU and restart it with identical settings, it starts correctly. I got the same happening with Xen 4.1 with a 3.5.3 kernel, but tried upgrading to see if that fixed it, but it didn't. If I connect to the console there's no output, and I can't get find any useful information in the logs or xl dmesg. The DomU is running a 3.3.2 32 bit linux kernel. Can you give me any suggestions how I might diagnose what's going on ? thanks, Anthony