1 files changed, 83 insertions, 0 deletions
diff --git a/results/classifier/118/device/1902262 b/results/classifier/118/device/1902262
new file mode 100644
index 00000000..dac01d9a
--- /dev/null
+++ b/results/classifier/118/device/1902262
@@ -0,0 +1,83 @@
+device: 0.873
+graphic: 0.782
+files: 0.762
+mistranslation: 0.747
+virtual: 0.742
+user-level: 0.738
+peripherals: 0.721
+performance: 0.682
+architecture: 0.669
+hypervisor: 0.666
+PID: 0.644
+semantic: 0.642
+network: 0.626
+kernel: 0.616
+permissions: 0.602
+vnc: 0.599
+VMM: 0.564
+KVM: 0.557
+ppc: 0.534
+x86: 0.530
+i386: 0.501
+risc-v: 0.497
+assembly: 0.481
+arm: 0.475
+register: 0.473
+socket: 0.450
+TCG: 0.440
+boot: 0.435
+debug: 0.402
+
+vmstate_load_state return error into virtio_load function
+
+Qemu version 4.2.1
+
+In the function of virtio_load, the vmstate_load_state will return error in the following case.
+
+The virtio is legacy mode(disable-modern=on,disable-legacy=off), virtio_device is in reset state. 
+
+In the the function of "vmstate_load_state", it will load all subsection. For the vmstate_virtio_extra_state subsection. 
+It will execute:
+vmstate_load_state   -->
+          ret = field->info->get(f, curr_elem, size, field);    line 143  vmstate.c.
+           -->virtio_pci_load_extra_state
+                        -->  vmstate_load_state
+                                 -->qemu_peek_byte
+But if the f->buf_index is same with buf_size, qemu_peek_byte function will set "-EIO" error. 
+the field->info->get will return 0, then it will get the error "ret = qemu_file_get_error(f);". then the vmstate_load_state will return error.
+
+It output is "Failed to load virtio/extra_state:extra_state"
+
+Can you also reproduce this with the latest version of QEMU? Anyway:
+The QEMU project is currently moving its bug tracking to another system.
+For this we need to know which bugs are still valid and which could be
+closed already. Thus we are setting the bug state to "Incomplete" now.
+
+If the bug has already been fixed in the latest upstream version of QEMU,
+then please close this ticket as "Fix released".
+
+If it is not fixed yet and you think that this bug report here is still
+valid, then you have two options:
+
+1) If you already have an account on gitlab.com, please open a new ticket
+for this problem in our new tracker here:
+
+    https://gitlab.com/qemu-project/qemu/-/issues
+
+and then close this ticket here on Launchpad (or let it expire auto-
+matically after 60 days). Please mention the URL of this bug ticket on
+Launchpad in the new ticket on GitLab.
+
+2) If you don't have an account on gitlab.com and don't intend to get
+one, but still would like to keep this ticket opened, then please switch
+the state back to "New" or "Confirmed" within the next 60 days (other-
+wise it will get closed as "Expired"). We will then eventually migrate
+the ticket automatically to the new system (but you won't be the reporter
+of the bug in the new system and thus you won't get notified on changes
+anymore).
+
+Thank you and sorry for the inconvenience.
+
+
+[Expired for QEMU because there has been no activity for 60 days.]
+