From: Paul Brook Subject: Re: [Qemu-devel] [PATCH 05/11] qemu: MSI-X support functions Date: Wed, 10 Jun 2009 20:04:13 +0100 Message-ID: <200906102004.17905.paul@codesourcery.com> References: <200906101830.21537.paul@codesourcery.com> <20090610180756.GM28601@redhat.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Cc: qemu-devel@nongnu.org, Carsten Otte , kvm@vger.kernel.org, Rusty Russell , virtualization@lists.linux-foundation.org, Blue Swirl , Christian Borntraeger , Avi Kivity To: "Michael S. Tsirkin" Return-path: Received: from mail.codesourcery.com ([65.74.133.4]:50088 "EHLO mail.codesourcery.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754395AbZFJTER (ORCPT ); Wed, 10 Jun 2009 15:04:17 -0400 In-Reply-To: <20090610180756.GM28601@redhat.com> Content-Disposition: inline Sender: kvm-owner@vger.kernel.org List-ID: > > If we can't start a new qemu with the same hardware configuration then we > > should not be allowing migration or loading of snapshots. > > OK, so I'll add an option in virtio-net to disable msi-x, and such > an option will be added in any device with msi-x support. > Will that address your concern? Yes, as long as migration fails when you try to migrate to the wrong kind of device. Paul