From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:45795) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WxF4y-0000TQ-O9 for qemu-devel@nongnu.org; Wed, 18 Jun 2014 08:35:12 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WxF4r-0001rf-3P for qemu-devel@nongnu.org; Wed, 18 Jun 2014 08:35:04 -0400 Received: from mx1.redhat.com ([209.132.183.28]:49876) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WxF4q-0001rU-QW for qemu-devel@nongnu.org; Wed, 18 Jun 2014 08:34:57 -0400 Date: Wed, 18 Jun 2014 15:35:21 +0300 From: "Michael S. Tsirkin" Message-ID: <20140618123521.GA31764@redhat.com> References: <20140618093334.GA12677@redhat.com> <20140618112958.GA13198@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] vhost-user: migration? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Nikolay Nikolaev Cc: Igor Mammedov , qemu-devel , Antonios Motakis On Wed, Jun 18, 2014 at 02:41:15PM +0300, Nikolay Nikolaev wrote: >=20 >=20 >=20 > On Wed, Jun 18, 2014 at 2:29 PM, Michael S. Tsirkin wr= ote: >=20 > On Wed, Jun 18, 2014 at 02:24:32PM +0300, Nikolay Nikolaev wrote: > > Hello, > > > > On Wed, Jun 18, 2014 at 12:33 PM, Michael S. Tsirkin > wrote: > > > > =A0 =A0 Just a query whether migration works for you > > =A0 =A0 guys with vhost-user and snabbswitch. > > > > > > I am not aware of anyone ever did such tests. > > > > > > =A0 =A0 vhost user code seems to have enough hooks in > > =A0 =A0 place to make it work, but was it tested > > =A0 =A0 in practice? > > > > > > > > Can you give some pointers of a simple/quick test scenario. Maybe= we'll > be able > > to set it up. >=20 >=20 > Basically migrate while doing networking :) >=20 > Does your vhost server have code to set bits in the memory log > when logging is enabled? >=20 >=20 > No - we didn't implement this feature. Interesting. In that case vhost user should for now block migration. You must also check log feature and return failure. >=20 > The log address is supplied to VHOST_SET_LOG_BASE and log_guest_add= r. >=20 >=20 > > > > > > =A0 =A0 -- > > =A0 =A0 MST > > > > > > regards, > > Nikolay Nikolaev >=20 >=20 > regards, > Nikolay Nikolaev