From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wayne Gong Subject: Why I cannot reconnect blk backend Date: Wed, 19 Nov 2008 17:41:05 +0800 Message-ID: <4923DF31.5010703@oracle.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1666724195==" Return-path: 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 List-Id: xen-devel@lists.xenproject.org This is a multi-part message in MIME format. --===============1666724195== Content-Type: multipart/alternative; boundary="------------020204010004050009050107" This is a multi-part message in MIME format. --------------020204010004050009050107 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi, I am implementing save/restore feature for windows pv driver. After system resumed, my frontend blk driver cannot connect backend. Here is my work flow: 1, Set frontend state to XenbusStateClosing, then set state to XenbusStateClosed. At the end, set frontend state to XenbusStateInitiazing. 2, Release blk device relevant memory. 3, Shutdown xenbus and release relevant memory. 4, Call hypercall to let system suspend. ...... (resume) 5. Reinit xenbus. 6. Get grant table, init share ring, allocate event channel for blk device. 7. Set frontend state to XenbusStateConnected. <-- got issue here. When set frontend state to connect, my backend state watcher tell me that backend state changed to closing and then closed. I am not very family with blk backend driver, so I want to know which scenarios cause blk backend state change to closing/closed. Any info I gave to xenstore is wrong? I use xen 3.1.3, win2k3. I can provide me info if you need. Thanks Wayne --------------020204010004050009050107 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi, I am implementing save/restore feature for windows pv driver. After system resumed, my frontend blk driver cannot connect backend. Here is my work flow: 1, Set frontend state to XenbusStateClosing, then set state to XenbusStateClosed. At the end, set frontend state to XenbusStateInitiazing. 2, Release blk device relevant memory. 3, Shutdown xenbus and release relevant memory. 4, Call hypercall to let system suspend. ...... (resume) 5. Reinit xenbus. 6. Get grant table, init share ring, allocate event channel for blk device. 7. Set frontend state to XenbusStateConnected. <-- got issue here. When set frontend state to connect, my backend state watcher tell me that backend state changed to closing and then closed. I am not very family with blk backend driver, so I want to know which scenarios cause blk backend state change to closing/closed. Any info I gave to xenstore is wrong? I use xen 3.1.3, win2k3. I can provide me info if you need. Thanks Wayne --------------020204010004050009050107-- --===============1666724195== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============1666724195==--