From mboxrd@z Thu Jan 1 00:00:00 1970 From: Charles Duffy Subject: Timing out waiting for vbd device *only when xend started with trace_start* Date: Mon, 14 Nov 2005 05:31:00 -0600 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com Cc: xen-users@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Since this issue was obviously happening only for me, I went looking for potential causes specific to my configuration. My init scripts start xend with trace_start. I backed this out (to just use "start"), rebooted, and everything came up normally. Rebooted again, likewise. Changed it back to trace_start, rebooted again, same failure as described in the thread this should be attached to. Changed it to start again, works. So -- for the initial issue, I have a workaround by way of avoiding trace_start, but I'd argue that it's quite certainly a bug that trace_start has side effects of this variety. Should I file a bug, or does someone else have it?