All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Laszlo Ersek \(Red Hat\)" <lersek@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1536487] Re: Unable to migrate pc-i440fx-2.4 KVM guest from QEMU 2.5.0 to QEMU 2.4.1
Date: Thu, 18 Feb 2016 19:34:36 -0000	[thread overview]
Message-ID: <20160218193436.24542.71754.malone@chaenomeles.canonical.com> (raw)
In-Reply-To: 20160121062724.15018.99449.malonedeb@wampee.canonical.com

sent a patch: http://thread.gmane.org/gmane.comp.emulators.qemu/395014

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1536487

Title:
  Unable to migrate pc-i440fx-2.4 KVM guest from QEMU 2.5.0 to QEMU
  2.4.1

Status in QEMU:
  New

Bug description:
  When migrating a pc-i440fc-2.4 KVM guest from QEMU 2.5.0 to QEMU
  2.4.1, the target QEMU errors out:

    qemu-system-x86_64: error while loading state for instance 0x0 of
  device 'fw_cfg'

  This appears to be related to the addition of a DMA interface to
  fw_cfg last October:

    http://lists.nongnu.org/archive/html/qemu-
  devel/2015-10/msg04568.html

  "info qtree" on the source QEMU shows that the DMA interface for
  fw_cfg had been enabled:

    bus: main-system-bus
      type System
      ...
      dev: fw_cfg_io, id ""
        iobase = 1296 (0x510)
        dma_iobase = 1300 (0x514)
        dma_enabled = true

  Incidentally, this guest had just undergone a migration from QEMU
  2.4.1 to QEMU 2.5.0, so it looks like DMA was enabled simply through
  the migration.

  It seems to me that the DMA interface for fw_cfg should only be
  enabled on pc-i440fx-2.5 machines or higher.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1536487/+subscriptions

  parent reply	other threads:[~2016-02-18 19:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-21  6:27 [Qemu-devel] [Bug 1536487] [NEW] Unable to migrate pc-i440fx-2.4 KVM guest from QEMU 2.5.0 to QEMU 2.4.1 Michael Chapman
2016-01-21  6:48 ` [Qemu-devel] [Bug 1536487] " Michael Chapman
2016-02-18 17:48 ` Alexandre Derumier
2016-02-18 18:12 ` Laszlo Ersek (Red Hat)
2016-02-18 19:34 ` Laszlo Ersek (Red Hat) [this message]
2016-02-19 13:51 ` Laszlo Ersek (Red Hat)
2016-03-01 12:26 ` Laszlo Ersek (Red Hat)
2016-06-21 16:35 ` T. Huth
2016-09-07  7:03 ` ChristianEhrhardt
2016-09-07  7:56 ` ChristianEhrhardt
2016-09-14  9:33 ` ChristianEhrhardt
2016-09-14 13:22   ` Serge Hallyn
2016-09-14 13:36 ` ChristianEhrhardt
2016-09-14 14:15   ` Serge Hallyn
2016-09-14 14:25 ` Paolo Bonzini
2016-09-15  7:24 ` ChristianEhrhardt
2016-09-15 11:35 ` ChristianEhrhardt

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=20160218193436.24542.71754.malone@chaenomeles.canonical.com \
    --to=lersek@redhat.com \
    --cc=1536487@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.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.