[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [Bug 1536487] Re: Unable to migrate pc-i440fx-2.4 KVM guest
From: |
Laszlo Ersek \(Red Hat\) |
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: |
Tue, 01 Mar 2016 12:26:53 -0000 |
Fix committed in e6915b5f3a874a467a9a65f7ec1d6ef8d251a51a.
** Changed in: qemu
Status: In Progress => Fix Committed
--
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:
Fix Committed
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
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Qemu-devel] [Bug 1536487] Re: Unable to migrate pc-i440fx-2.4 KVM guest from QEMU 2.5.0 to QEMU 2.4.1,
Laszlo Ersek \(Red Hat\) <=