From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matt Ayres Subject: Re: device/udev problem Date: Fri, 27 Jan 2006 18:12:06 -0500 Message-ID: <43DAA8C6.6060305@tektonic.net> References: <983B408465C04C49B0344D51FA21C7553E75A8@trudi.intra.bpm.ch> <20051019122009.GE11567@tpkurt.pmc.nue.novell.com> <20051019131500.GK26910@leeni.uk.xensource.com> <43564D8A.8000308@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <43564D8A.8000308@suse.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: Gerd Knorr Cc: xen-devel@lists.xensource.com, Ewan Mellor , Kurt Garloff , =?ISO-8859-1?Q?Stephan_B=F6ni?= List-Id: xen-devel@lists.xenproject.org Gerd Knorr wrote: > Ewan Mellor wrote: >> On Wed, Oct 19, 2005 at 02:20:09PM +0200, Kurt Garloff wrote: >> >>> After some time, xenbus seems to get stuck however, and then the hotplug >>> events don't seem to get through any longer. >>> Rebooting helps against this. >> >> Do you issue xm block-detach commands? There is a known bug here that >> would >> cause such behaviour. If you are not doing this, I would be >> interested to >> know, because that would be an unknown bug, and would be worth >> tracking down. > > I see that behavior as well, after some time setting up block devices > stops working (maybe network too, can't test that due to vbd not working > and my domU's not booting any more). Restarting xend doesn't help. I > don't use "xm block-*" commands. > Was this using udev or hotplug for dom0 device manipulation?