From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56217) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dlA9i-00071u-Fe for qemu-devel@nongnu.org; Fri, 25 Aug 2017 04:39:55 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dlA9h-0000Bx-Rr for qemu-devel@nongnu.org; Fri, 25 Aug 2017 04:39:54 -0400 Received: from mail-oi0-x231.google.com ([2607:f8b0:4003:c06::231]:32913) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dlA9h-0000BM-MA for qemu-devel@nongnu.org; Fri, 25 Aug 2017 04:39:53 -0400 Received: by mail-oi0-x231.google.com with SMTP id t88so15645017oij.0 for ; Fri, 25 Aug 2017 01:39:52 -0700 (PDT) MIME-Version: 1.0 From: Sergei Dyshel Date: Fri, 25 Aug 2017 11:39:30 +0300 Message-ID: Content-Type: text/plain; charset="UTF-8" Subject: [Qemu-devel] Make NVME device "migratable" (savevm) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Hi all, >>From what I understand, I can't "savevm" a VM that uses NVME device because it has ".unmigratable = 1" in the code. What support must be implemented in order to make it "migratable"? -- Regards, Sergei Dyshel