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.
DescriptionDr. David Alan Gilbert
2016-10-25 15:46:00 UTC
Description of problem:
I've got a win2012r2 guest (same image as https://bugzilla.redhat.com/show_bug.cgi?id=1376806), I added a new disk to it and tried to partition it and got the error 'Failed to initialize disk - Unspecified error'.
Version-Release number of selected component (if applicable):
qemu-kvm-rhev-2.3.0-31.el7_2.23
The image I have has a driver date of 3/10/2015 62.72.104.10200 for the VirtIO SCSI controller.
How reproducible:
100%
Steps to Reproduce:
1. Add a 2nd qcow2 disk
2. On the server manager dashboard select 'File and storage services'->Volumes->Disks
3. Select the new disk
4. Right click and select initialise
5. Say yes to GPT partitioning
6. Wait a few seconds
Actual results:
'Failed to initialize disk - Unspecified Error. Extended information: The drive cannot find the sector requested'. Once I saw a log where it was complaining about sector 0x1fffffff but I'm not sure that's the same and can't see it now.
Expected results:
A ready to use disk.
Additional info:
/usr/libexec/qemu-kvm -name guest=cbitwin2k12r2,debug-threads=on -S -machine pc-i440fx-rhel7.2.0,accel=kvm,usb=off,vmport=off -cpu IvyBridge -m 16384 -realtime mlock=off -smp 4,sockets=4,cores=1,threads=1 -uuid 8358e334-c8b8-4f9c-97eb-fa5d22a20b0b -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-19-cbitwin2k12r2/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/home/vms/cloudbaseit-windows_server_2012_r2_standard_eval_kvm_20151021.qcow2,format=qcow2,if=none,id=drive-virtio-disk0,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=26,id=hostnet0,vhost=on,vhostfd=28 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:7d:3b:18,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -device usb-tablet,id=input1,bus=usb.0,port=1 -vnc 127.0.0.1:0 -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -incoming defer -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -msg timestamp=on
This works fine with the latest virtio-win drivers and has been bisected to
commit ecab9d19e5fa19ca1aabdb5c45e523aab8595526
Author: Vadim Rozenfeld <vrozenfe>
Date: Fri Apr 24 22:52:36 2015 +1000
[viostor] bugfix for 1067225 and 1195487 - Windows guest performing out-of-bounds accesses on virtio device
The fix is in virtio-win version 104. I am closing this BZ as a duplicate of bug 1067225. Vadim, please double-check.
*** This bug has been marked as a duplicate of bug 1067225 ***
(In reply to Ladi Prosek from comment #3)
> This works fine with the latest virtio-win drivers and has been bisected to
>
> commit ecab9d19e5fa19ca1aabdb5c45e523aab8595526
> Author: Vadim Rozenfeld <vrozenfe>
> Date: Fri Apr 24 22:52:36 2015 +1000
>
> [viostor] bugfix for 1067225 and 1195487 - Windows guest performing
> out-of-bounds accesses on virtio device
>
>
> The fix is in virtio-win version 104. I am closing this BZ as a duplicate of
Right, the problem was fixed in build virtio-win-prewhql-0.1-104.
Vadim.
> bug 1067225. Vadim, please double-check.
>
> *** This bug has been marked as a duplicate of bug 1067225 ***
Created attachment 1215654[details]
initialize disk failed
Hi,
This issue can be reproduced with virtio-win build 102 on win2012r2. When initialize the new added disk, report error message 'Failed to initialize disk - Unspecified error,Extended information: The drive cannot find the sector requested'. Details please refer to the attached picture.
Steps as comment#0
Versions:
qemu-kvm-rhev-2.3.0-31.el7_2.23
virtio-win-prewhql-102
It cannot be reproduced with virtio-win build 126 on win2012r2. Initialize the new added disk successfully.
Best Regards~
Peixiu Hou