All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: "Durrant, Paul" <pdurrant@amazon.co.uk>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [Xen-devel] live migration from 4.12 to 4.13 fails due to qemu-xen bug
Date: Mon, 17 Feb 2020 16:04:06 +0100	[thread overview]
Message-ID: <20200217160406.65aa2ed1.olaf@aepfle.de> (raw)
In-Reply-To: <580201e5daa849399b79641bd610ec93@EX13D32EUC003.ant.amazon.com>


[-- Attachment #1.1: Type: text/plain, Size: 920 bytes --]

Am Mon, 27 Jan 2020 11:54:37 +0000
schrieb "Durrant, Paul" <pdurrant@amazon.co.uk>:

> I suppose. Could we have "pc-i440fx" as the default, which libxl prefix matches against qemu's supported versions to select the latest? I guess that would work.

This can not be fixed in libxl because libxl can not possibly know what is inside the domU.

With '-machine xenfv' the PCI device is at 0000:00:02.0/platform, while with '-machine pc-i440fx-3.1,accel=xen -device xen-platform' the PCI device is somewhere else. As a result the receiving host rejects this approach:

qemu-system-i386: Unknown savevm section or instance '0000:00:02.0/platform' 0. Make sure that your current VM setup matches your saved VM setup, including any hotplugged devices

In my earlier testing I forced -machine pc-i440fx* on the sending side, and did not spot the flaw in this patch for libxl.

For short: we are doomed...


Olaf

[-- Attachment #1.2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 157 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

      parent reply	other threads:[~2020-02-17 15:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-13 10:36 [Xen-devel] live migration from 4.12 to 4.13 fails due to qemu-xen bug Olaf Hering
2020-01-13 17:26 ` Olaf Hering
2020-01-27 11:30 ` Olaf Hering
2020-01-27 11:54   ` Durrant, Paul
2020-01-27 12:59     ` Olaf Hering
2020-01-27 13:18       ` Durrant, Paul
2020-02-17 15:04     ` Olaf Hering [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200217160406.65aa2ed1.olaf@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=pdurrant@amazon.co.uk \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.