From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wayne Gong Subject: Re: Why I cannot reconnect blk backend Date: Thu, 20 Nov 2008 13:56:58 +0800 Message-ID: <4924FC2A.5030903@oracle.com> References: <4923DF31.5010703@oracle.com> <49242404.7020005@oracle.com> 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 Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org > All I can suggest is that your turn on the logging in xenstore and watch > what happens - looking for differences between what happens then xenvbd > first starts up and when it resumes. blkback: ring-ref 335, event-channel 5, protocol 1 (unspecified, assuming native) vbd vbd-3-768: 1 mapping ring-ref 335 port 5 blkback: ring-ref 335, event-channel 5, protocol 1 (unspecified, assuming native) vbd vbd-3-768: 1 mapping ring-ref 335 port 5 blkback: ring-ref 335, event-channel 5, protocol 1 (unspecified, assuming native) vbd vbd-3-768: 1 mapping ring-ref 335 port 5 What's this mean? I guess when vbd device resume, I use a mapped ring-ref to initialize device. When vbd device resume, I allocate some new memory and call SHARED_RING_INIT to init them and then save the ring-ref to xenstore. After that, xenstore pops a warning as above. How can I release that ring-ref when suspend vbd device, or how to reallocate a new ring-ref for vbd device? Thanks Wayne