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.
Description of problem:
Boot a win2012r2 guest with 256 virtio-scsi target (1 controller, 1 LUN), and then reboot guest, qemu quit with "Guest moved used index from 10122 to 10253". Boot up with 1 scsi target, no problem.
Version-Release number of selected component (if applicable):
kernel-2.6.32-491.el6.x86_64
qemu-kvm-0.12.1.2-2.432.el6.x86_64
virtio-win-prewhql-87 (for virtio-scsi driver)
How reproducible:
Always
Steps to Reproduce:
1. # cat 256-target.sh
cli="/usr/libexec/qemu-kvm -machine rhel6.6.0,dump-guest-core=off -m 24G -smp 12 -cpu Westmere -vnc :10 -vga std -monitor stdio -boot menu=on -monitor unix:/tmp/monitor,server,nowait -drive file=/root/scalability/win2012-r2.qcow2,if=none,id=blk1 -device virtio-blk-pci,scsi=off,drive=blk1,id=blk-disk1,bootindex=1 -netdev tap,id=netdev1,vhost=on,script=/etc/qemu-ifup -device virtio-net-pci,netdev=netdev1,mac=02:03:04:05:06:00,id=net-pci1"
cli="$cli -device virtio-scsi-pci,id=scsi0"
count=$((${1:-1}-1))
for i in $(seq 0 $count)
do
echo $i
cli="$cli -drive file=/home/disk/disk$i,if=none,id=disk$i"
cli="$cli -device scsi-hd,bus=scsi0.0,drive=disk$i,id=target$i,scsi-id=$i,lun=0"
done
$cli
# sh 256-target.sh 256
2. Check whether the 256 scsi disk could be detected and used.
3. Reboot guest
Actual results:
After step 3:
(qemu) Guest moved used index from 10122 to 10253/etc/qemu-ifdown: could not launch network script
Expected results:
Guest should reboot successfully
Additional info:
This bug could be reproduced on qemu-kvm-0.12.1.2-2.432.el6.x86_64 with >= 129 virtio scsi target.
Also test the rhel6.5 released version qemu-kvm-0.12.1.2-2.415.el6.x86_64 with 129 and 130 virtio scsi target, can not reproduce. So this should be a regression.
Qunfang, can you reproduce with 433 or later? It has a new fix on virtio-scsi (bug 1123698).
Please test with the latest build if possible.
Thanks,
Fam
(In reply to Fam Zheng from comment #4)
> Qunfang, can you reproduce with 433 or later? It has a new fix on
> virtio-scsi (bug 1123698).
>
> Please test with the latest build if possible.
>
> Thanks,
> Fam
Hi, Fam
I just tested qemu-kvm-0.12.1.2-2.435.el6.x86_64, this issue still exists.
Thanks,
Qunfang
(In reply to Fam Zheng from comment #11)
> Close since the bug is fixed in latest virtio-win build as comment 9.
This build hasn't shipped to customers ,pls keep this bug open
(In reply to Fam Zheng from comment #15)
> Mike, would you please take care of this bug's erratum accordingly, or maybe
> close it if there is already a bug for the virtio-win update?
>
> Thanks,
> Fam
Virtio-win is something complex compared w/ other component ,it contains 3 component ,namely ,virtio-win, virtio-win-prewhql, qemu-ga-win , we ship virtio-win at last ,
Actually This bug is fixed on virtio-win-prewhql-89 build ,but the fix does not plan to included in virtio-win yet that's why we did not add the bug to advisory
I will take care of this bug when developer make the decision (add it to erratum or propose to next release althrough it is in ON_QA/VERIFIED status
Mike
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.
https://rhn.redhat.com/errata/RHBA-2015-2513.html
Description of problem: Boot a win2012r2 guest with 256 virtio-scsi target (1 controller, 1 LUN), and then reboot guest, qemu quit with "Guest moved used index from 10122 to 10253". Boot up with 1 scsi target, no problem. Version-Release number of selected component (if applicable): kernel-2.6.32-491.el6.x86_64 qemu-kvm-0.12.1.2-2.432.el6.x86_64 virtio-win-prewhql-87 (for virtio-scsi driver) How reproducible: Always Steps to Reproduce: 1. # cat 256-target.sh cli="/usr/libexec/qemu-kvm -machine rhel6.6.0,dump-guest-core=off -m 24G -smp 12 -cpu Westmere -vnc :10 -vga std -monitor stdio -boot menu=on -monitor unix:/tmp/monitor,server,nowait -drive file=/root/scalability/win2012-r2.qcow2,if=none,id=blk1 -device virtio-blk-pci,scsi=off,drive=blk1,id=blk-disk1,bootindex=1 -netdev tap,id=netdev1,vhost=on,script=/etc/qemu-ifup -device virtio-net-pci,netdev=netdev1,mac=02:03:04:05:06:00,id=net-pci1" cli="$cli -device virtio-scsi-pci,id=scsi0" count=$((${1:-1}-1)) for i in $(seq 0 $count) do echo $i cli="$cli -drive file=/home/disk/disk$i,if=none,id=disk$i" cli="$cli -device scsi-hd,bus=scsi0.0,drive=disk$i,id=target$i,scsi-id=$i,lun=0" done $cli # sh 256-target.sh 256 2. Check whether the 256 scsi disk could be detected and used. 3. Reboot guest Actual results: After step 3: (qemu) Guest moved used index from 10122 to 10253/etc/qemu-ifdown: could not launch network script Expected results: Guest should reboot successfully Additional info: