From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:40662) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WQIdr-0003mE-1p for qemu-devel@nongnu.org; Wed, 19 Mar 2014 11:42:59 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WQIdm-0006nH-3m for qemu-devel@nongnu.org; Wed, 19 Mar 2014 11:42:54 -0400 Received: from static.92.5.9.176.clients.your-server.de ([176.9.5.92]:38293 helo=hallynmail2) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WQIdl-0006mY-Ul for qemu-devel@nongnu.org; Wed, 19 Mar 2014 11:42:50 -0400 Date: Wed, 19 Mar 2014 16:42:47 +0100 From: "Serge E. Hallyn" Message-ID: <20140319154247.GA31501@mail.hallyn.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: [Qemu-devel] migrating instances from qemu-kvm to qemu List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Hi, at https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1291321 it was found that migrating running vms from a machine with qemu-kvm to one with qemu, migration fails due to some mismatches. The first one we usually hit is Length mismatch: vga.vram: 1000000 in != 800000 while the second one is network card (and I have not gone beyond that). The vga one can be handled on the command line by specifying the -global cirrus-vga.vrammem_mb=8. However that doesn't help with a libvirt migration. I guess this happens at ram_load() unfortunately - is there any good way that this could be detected at incoming migration time and the virtual hardware modified as needed for migration to continue? thanks, -serge