mirror of
https://github.com/xemu-project/xemu.git
synced 2024-12-11 05:23:58 +00:00
62a830b688
Migration with ivshmem needs to be carefully orchestrated to work. Exactly one peer (the "master") migrates to the destination, all other peers need to unplug (and disconnect), migrate, plug back (and reconnect). This is sort of documented in qemu-doc. If peers connect on the destination before migration completes, the shared memory can get messed up. This isn't documented anywhere. Fix that in qemu-doc. To avoid messing up register IVPosition on migration, the server must assign the same ID on source and destination. ivshmem-spec.txt leaves ID assignment unspecified, however. Amend ivshmem-spec.txt to require the first client to receive ID zero. The example ivshmem-server complies: it always assigns the first unused ID. For a bit of additional safety, enforce ID zero for the master. This does nothing when we're not using a server, because the ID is zero for all peers then. Signed-off-by: Markus Armbruster <armbru@redhat.com> Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com> Message-Id: <1458066895-20632-40-git-send-email-armbru@redhat.com> |
||
|---|---|---|
| .. | ||
| acpi_cpu_hotplug.txt | ||
| acpi_mem_hotplug.txt | ||
| acpi_pci_hotplug.txt | ||
| edu.txt | ||
| fw_cfg.txt | ||
| ivshmem-spec.txt | ||
| parallels.txt | ||
| pci-ids.txt | ||
| pci-serial.txt | ||
| pci-testdev.txt | ||
| ppc-spapr-hcalls.txt | ||
| ppc-spapr-hotplug.txt | ||
| pvpanic.txt | ||
| qcow2.txt | ||
| qed_spec.txt | ||
| rocker.txt | ||
| standard-vga.txt | ||
| vhost-user.txt | ||
| vmw_pvscsi-spec.txt | ||