From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Re: No shutdown of domU: xenbus_dev_shutdown: device/console/0: Initialising != Connected, skipping Date: Wed, 17 Nov 2010 13:57:47 -0800 Message-ID: <4CE44FDB.7000508@goop.org> References: <1341501057.20101117132828@eikelenboom.it> <1945713192.20101117212227@eikelenboom.it> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1945713192.20101117212227@eikelenboom.it> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Sander Eikelenboom Cc: Ian Campbell , Ian Jackson , "Xen-devel@lists.xensource.com" , Keir Fraser List-Id: xen-devel@lists.xenproject.org On 11/17/2010 12:22 PM, Sander Eikelenboom wrote: > Ah yes, 2.6.18 does contain the following line in xenbus_probe.c and 2.6.37-rc2 not: > > - if (!strcmp(type, "console")) > - return 0; > It seems to be changed, > > > There seems to have been a patch http://lists.xensource.com/archives/html/xen-devel/2009-11/msg01072.html but it seems it's not applied to xenbus in linux upstream. And does this patch fix things for you? But I have to say that's pretty gross. Is it really the right thing to do? J