On Wed, 2011-08-17 at 14:16 +0300, Timo Juhani Lindfors wrote: > Ian Campbell <[email protected]> writes: > >> That I might have indeed done during all the debugging. > > > > I think that's the root cause of your current issue (that's not to say > > there wasn't a different issue first). > > Rebooting indeed helps: > > KERNEL[1313579215.519543] add /devices/vbd-1-51712 (xen-backend) > KERNEL[1313579215.577535] add /devices/console-1-0 (xen-backend) > UDEV [1313579215.578056] add /devices/console-1-0 (xen-backend) > KERNEL[1313579215.713474] change /devices/virtual/block/loop0 (block) > UDEV [1313579215.774987] change /devices/virtual/block/loop0 (block) > UDEV [1313579215.782382] add /devices/vbd-1-51712 (xen-backend) > KERNEL[1313579303.011564] remove > /module/stap_ee54f81b78bb2fe50ce3cf32dc6cc35f_15387 (module) > UDEV [1313579303.011846] remove > /module/stap_ee54f81b78bb2fe50ce3cf32dc6cc35f_15387 (module) > > Thanks a lot for the quick feedback.
Does this mean the bug can be closed or was there still an underlying issue? > Would it be possible to detect this > error condition in xenstored somehow? Unfortunately xenstored has no knowledge of the backends and their watch requirements. Ian. -- Ian Campbell This is the ____LAST time I take travel suggestions from Ray Bradbury! -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
