1 files changed, 0 insertions, 43 deletions

diff --git a/gitlab/issues/target_i386/host_missing/accel_missing/2594.toml b/gitlab/issues/target_i386/host_missing/accel_missing/2594.toml
deleted file mode 100644
index f0e56e49..00000000
--- a/gitlab/issues/target_i386/host_missing/accel_missing/2594.toml
+++ /dev/null
@@ -1,43 +0,0 @@
-id = 2594
-title = "Migration fails with 'get_pci_config_device: Bad config data: i=0x9a read: 2 device: 3 cmask: ff wmask: 0 w1cmask:0' after hotplugging a CPU"
-state = "closed"
-created_at = "2024-09-26T14:57:34.774Z"
-closed_at = "2025-01-27T17:13:01.907Z"
-labels = ["Migration", "device: PCI", "device:virtio", "target: i386"]
-url = "https://gitlab.com/qemu-project/qemu/-/issues/2594"
-host-os = "Ubuntu 24.04 LTS (also tested on Ubuntu 22.04 LTS)"
-host-arch = "x86-64"
-qemu-version = "QEMU emulator version 9.1.50 (v9.1.0-475-ga53b931645) (compiled from source)"
-guest-os = "-"
-guest-arch = "x86"
-description = """After hotplugging a CPU and finishing a migration from node 1 to node 2, the instance on node 2 crashes when virtio block devices are used:
-```
-qemu-system-x86_64: get_pci_config_device: Bad config data: i=0x9a read: 2 device: 3 cmask: ff wmask: 0 w1cmask:0
-qemu-system-x86_64: Failed to load PCIDevice:config
-qemu-system-x86_64: Failed to load virtio-blk:virtio
-qemu-system-x86_64: error while loading state for instance 0x0 of device '0000:00:04.0/virtio-blk'
-qemu-system-x86_64: load of migration failed: Invalid argument
-```
-
-I found the problem also exhibits when using `scsi-hd` in combination with `virtio-scsi`, but not when using IDE hard disks or SCSI disks with an LSI controller. VMs with network cards aren't affected either, as are VMs without virtio disks.
-
-
-Interestingly, the latest QEMU version shipped with Ubuntu 20.04 (4.2.1-Debian 1:4.2-3ubuntu6.29) is able to migrate this VM just fine."""
-reproduce = """1. Start a VM using the first command line
-2. Start another VM using the second command line
-3. Hotplug a CPU in QMP:
-   ```
-   {"execute":"device_add","arguments":{"node-id":0,"socket-id":0,"core-id":2,"thread-id":0,"id":{},"driver":"qemu64-x86_64-cpu"}}
-   ```
-4. Start a migration by executing the following QMP command (again substituting `<ip:port>` with the IP:port combination of node 2
-   ```
-   {"execute":"migrate","arguments":{"uri":"tcp:127.0.0.1:1234"}}
-   ```
-
-(For steps 3 and 4 I used this):
-```
-echo '{"execute":"qmp_capabilities"}
-{"execute":"device_add","arguments":{"node-id":0,"socket-id":0,"core-id":2,"thread-id":0,"id":{},"driver":"qemu64-x86_64-cpu"},"id":1}
-{"execute":"migrate","arguments":{"uri":"tcp:127.0.0.1:1234"},"id":2}' | nc -U /tmp/vm1.sock
-```"""
-additional = """"""