Bug 731759
Summary: | SPICE: migration fails with warning: error while loading state section id 4 | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Lubos Kocman <lkocman> |
Component: | qemu-kvm | Assignee: | David Blechter <dblechte> |
Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.2 | CC: | cmeadors, juzhang, kraxel, lyarwood, mkenneth, mkrcmari, quintela, shuang, tburke, virt-maint |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-12-06 15:56:21 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Lubos Kocman
2011-08-18 14:53:15 UTC
I've reproduced as well, with same observation as described in original report: Guest moved used index from 9278 to 100582011-08-24 12:59:24.116: shutting down Does it happens without spice? Was this standard migration or a loadvm ? Can you please reproduce it again with all the recent components? hw/virtio.c: static int virtqueue_num_heads(VirtQueue *vq, unsigned int idx) { uint16_t num_heads = vring_avail_idx(vq) - idx; /* Check it isn't doing very strange things with descriptor numbers. */ if (num_heads > vq->vring.num) { fprintf(stderr, "Guest moved used index from %u to %u", idx, vring_avail_idx(vq)); exit(1); } return num_heads; } Doesn't look spice related at first glance. Might be memory corruption though. Same question as Dor: Does it happens without spice? Issue does not appear any more on qemu-kvm-0.12.1.2-2.189.el6.alon.729621.x86_64 libvirt-0.9.4-7.el6.x86_64 spice-server-0.8.2-3.el6.x86_64 vdsm-4.9-96.el6.x86_64 Proposing to close as current release Moving directly to VERIFIED. After talking to dblechte and doing some investigation, I am confident that there was a code change that fixed this bug, but unfortunately it is not possible to identify it under the current time constraints. The fact that two people could reproduce reinforces that the bug probably was not due to environment. I think this is better than CLOSED CURRENTRELEASE. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2011-1531.html |