Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 668707

Summary: "Guest moved used index from 0 to 580" occur when guest load to grub during reboot
Product: Red Hat Enterprise Linux 6 Reporter: Suqin Huang <shuang>
Component: seabiosAssignee: Gleb Natapov <gleb>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 6.1CC: khong, knoel, michen, ndai, tburke
Target Milestone: rcKeywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: seabios-0.6.1.2-1.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-19 13:04:43 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:
Bug Depends On:    
Bug Blocks: 580951    

Description Suqin Huang 2011-01-11 10:58:28 UTC 
Description of problem:
"Guest moved used index from 0 to 580" occur and guest quit when guest load to grub during reboot

Version-Release number of selected component (if applicable):
seabios-0.6.1-1.el6

How reproducible:
100%

Steps to Reproduce:
1. boot guest with cmd
/usr/libexec/qemu-kvm -monitor stdio -drive file='/usr/images/RHEL-Server-6.0-64-virtio.qcow2',index=0,if=none,id=drive-virtio-disk1,media=disk,cache=none,format=qcow2,aio=native \
-device virtio-blk-pci,bus=pci.0,addr=0x4,drive=drive-virtio-disk1,id=virtio-disk1 -device virtio-net-pci,netdev=idRD8S1a,mac=9a:2b:fa:d7:9e:f1,netdev=idRD8S1a,id=ndev00idRD8S1a,bus=pci.0,addr=0x3 -netdev tap,id=idRD8S1a,script='/usr/kvm/scripts/qemu-ifup-switch',downscript='no' \
-m 2048 -smp 2,cores=1,threads=1,sockets=2 -cpu cpu64-rhel6,+sse2,+x2apic -vnc :1 -rtc base=utc,clock=host,driftfix=none  -boot c -usbdevice tablet -no-kvm-pit-reinjection -enable-kvm

2. reboot guest
3.
  
Actual results:
"Guest moved used index from 0 to 580" occur and guest quit

Expected results:


Additional info:
1. host:
kernel: 2.6.32-94.el6.x86_64
qemu: qemu-kvm-0.12.1.2-2.129.el6.x86_64
cpu:

processor	: 3
vendor_id	: AuthenticAMD
cpu family	: 16
model		: 2
model name	: AMD Phenom(tm) 9600B Quad-Core Processor
stepping	: 3
cpu MHz		: 1150.000
cache size	: 512 KB
physical id	: 0
siblings	: 4
core id		: 3
cpu cores	: 4
apicid		: 3
initial apicid	: 3
fpu		: yes
fpu_exception	: yes
cpuid level	: 5
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nonstop_tsc extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs npt lbrv svm_lock
bogomips	: 4587.43
TLB size	: 1024 4K pages
clflush size	: 64
cache_alignment	: 64
address sizes	: 48 bits physical, 48 bits virtual
power management: ts ttp tm stc 100mhzsteps hwpstate


2. guest:
rhel6-64 (2.6.32-71.7.1.el6.x86_64)

3. can work with seabios-0.5.1-3.el6
Comment 2 Eduardo Habkost 2011-01-11 14:02:24 UTC 
(In reply to comment #0)
> 3. can work with seabios-0.5.1-3.el6

I am not sure I understand the above. Does this mean it was tested with seabios-0.5.1-3.el6 and it was working properly?
Comment 3 Eduardo Habkost 2011-01-11 14:30:23 UTC 
It looks like it was fixed upstream:

commit 0f67397152be77c30791c04ba5dd0267cac6754c
Author: Gleb Natapov <gleb>
Date:   Wed Sep 15 18:31:44 2010 +0200

    fix virtio-blk failure after reboot
    
    vring_virtqueue should be zeroed otherwise old values will be reused
    after reboot.
    
    Signed-off-by: Gleb Natapov <gleb>

:100644 100644 34d7863... 7a25826... M  src/virtio-blk.c


But this is not in the rel-0.6.1 release. I wonder if it is safer for us to just rebase to git master.
Comment 4 Miya Chen 2011-01-11 14:34:43 UTC 
(In reply to comment #2)
> (In reply to comment #0)
> > 3. can work with seabios-0.5.1-3.el6
> 
> I am not sure I understand the above. Does this mean it was tested with
> seabios-0.5.1-3.el6 and it was working properly?

yes, it work when I downgrade seabios to seabios-0.5.1-3.el6
Comment 8 Keqin Hong 2011-01-13 05:07:26 UTC 
Verified on seabios-0.6.1.2-1.el6, using steps mentioned in Comment 0. PASS.
Comment 10 errata-xmlrpc 2011-05-19 13:04:43 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0564.html