From mboxrd@z Thu Jan 1 00:00:00 1970 From: Juergen Gross Subject: Re: [Xen-devel] [PATCH 2/4] Introduce xen-scsifront module Date: Mon, 30 Jun 2014 15:51:03 +0200 Message-ID: <53B16B47.4050102@suse.com> References: <1403879676-25431-1-git-send-email-jgross@suse.com> <1403879676-25431-3-git-send-email-jgross@suse.com> <53B167B5.7070104@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from cantor2.suse.de ([195.135.220.15]:44269 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752193AbaF3NvH (ORCPT ); Mon, 30 Jun 2014 09:51:07 -0400 In-Reply-To: <53B167B5.7070104@citrix.com> Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: David Vrabel , jgross@suse.com, JBottomley@parallels.com, linux-scsi@vger.kernel.org, xen-devel@lists.xen.org On 06/30/2014 03:35 PM, David Vrabel wrote: > On 27/06/14 15:34, jgross@suse.com wrote: >> >> +/* .resume = scsifront_resume, */ > > Following on from the recent discussion on migration with front/backends > I thought I'd review how this new driver does it. "New" is an attribute I wouldn't use in this case. The driver was introduced in 2008, this is just a rework to be able to put it in the upstream kernel. > Is there an expectation that a VM with a PV scsi device cannot be > restored or migrated? It has been so in the past. To change this is on my todo list, but that's not top priority. Juergen