diff options
Diffstat (limited to 'results/classifier/105/device/2213')
| -rw-r--r-- | results/classifier/105/device/2213 | 28 |
1 files changed, 28 insertions, 0 deletions
diff --git a/results/classifier/105/device/2213 b/results/classifier/105/device/2213 new file mode 100644 index 00000000..4b4aefcb --- /dev/null +++ b/results/classifier/105/device/2213 @@ -0,0 +1,28 @@ +device: 0.935 +graphic: 0.929 +instruction: 0.897 +other: 0.825 +boot: 0.646 +vnc: 0.616 +semantic: 0.588 +mistranslation: 0.520 +socket: 0.471 +network: 0.346 +assembly: 0.175 +KVM: 0.031 + +QEMU fails with duplicate SaveStateEntry when using two legacy virtio input devices +Description of problem: +QEMU bails out when it is started with two virtio-input devices running in legacy virtio mode, using two different transports (like PCI and CCW on s390x). +Steps to reproduce: +``` +qemu-system-s390x -M s390-ccw-virtio-2.6 -cpu max -nographic -device virtio-multitouch-pci -device virtio-tablet-ccw +``` +fails with: +``` +qemu-system-s390x: -device virtio-tablet-ccw: savevm_state_handler_insert: Detected duplicate SaveStateEntry: id=virtio-input, instance_id=0x0 +``` +Additional information: +The problem does *not* occur if using modern virtio devices (which automatically happens for -M s390-ccw-virtio-2.7 and newer) or if using virtio-input devices with the same transport (e.g. two PCI devices instead of one PCI and one CCW). + +Also note that the problem only occurs since QEMU 8.1 since older versions did not check for duplicate SaveStateEntries (see commit caa91b3c44cdb2d2921e25 ). |