From: Launchpad Bug Tracker <1902262@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1902262] Re: vmstate_load_state return error into virtio_load function
Date: Fri, 09 Jul 2021 04:17:20 -0000 [thread overview]
Message-ID: <162580424037.19936.6950295049267446483.malone@loganberry.canonical.com> (raw)
In-Reply-To: 160407285408.8291.17235632998408436942.malonedeb@soybean.canonical.com
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1902262
Title:
vmstate_load_state return error into virtio_load function
Status in QEMU:
Expired
Bug description:
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"
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1902262/+subscriptions
prev parent reply other threads:[~2021-07-09 4:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 15:47 [Bug 1902262] [NEW] vmstate_load_state return error into virtio_load function Jingtao
2021-05-09 14:24 ` [Bug 1902262] " Thomas Huth
2021-07-09 4:17 ` Launchpad Bug Tracker [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=162580424037.19936.6950295049267446483.malone@loganberry.canonical.com \
--to=1902262@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.