From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=42008 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1P3c8F-0006iw-FC
	for qemu-devel@nongnu.org; Wed, 06 Oct 2010 18:06:42 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <alevy@redhat.com>) id 1P3c88-0005Dp-1o
	for qemu-devel@nongnu.org; Wed, 06 Oct 2010 18:06:33 -0400
Received: from mx3-phx2.redhat.com ([209.132.183.24]:38354
	helo=mx01.colomx.prod.int.phx2.redhat.com)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <alevy@redhat.com>) id 1P3c87-0005DV-Rt
	for qemu-devel@nongnu.org; Wed, 06 Oct 2010 18:06:32 -0400
Date: Wed, 6 Oct 2010 18:06:29 -0400 (EDT)
From: Alon Levy <alevy@redhat.com>
Message-ID: <2034188046.649571286402789227.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
In-Reply-To: <668252848.649521286402747765.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/2] USB CCID device
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>


----- "Anthony Liguori" <anthony@codemonkey.ws> wrote:

> On 10/06/2010 03:55 AM, Gerd Hoffmann wrote:
> > On 10/06/10 02:28, Alon Levy wrote:
> >>
> >>>
> >>> Does this work with live migration?  I can't see how it would.
> >>>
> >>
> >> No, it doesn't right now. It would require cooperation with the
> client,
> >> to tell it to reconnect to the target qemu (kind of like spice).
> >
> > I think until we have this migration should have pretty much the
> same 
> > effect as a chardev disconnect, i.e. detach the usb device (which
> the 
> > guest will see as unplug).
> 
> Better yet, mark the guest as unmigrateable and let the management
> tool 
> unplug the usb device before migration and replug it after migration.
> 
> It's the same principle behind device assignment.
> 

ok, I think I'll go this way.

> Regards,
> 
> Anthony Liguori
> 
> > Needs some code though, at minimum you'll have to xfer the connected
> 
> > state from the migration source and have some bits in post_load() 
> > which do attach/detach if needed.
> >
> > cheers,
> >   Gerd
> >