Description of problem:
when initiate a virtio-blk-pci device,guest prompt a error message as attached.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.boot win2012R2 guest with OVMF:
/usr/libexec/qemu-kvm -name 103RNG2012R2ZAY -enable-kvm -m 4G -smp 4 -uuid d4c87374-40d9-4201-a6f3-374b5f2ba6f8 -nodefconfig -nodefaults -drive file=OVMF-test/OVMF_CODE.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=OVMF-test/OVMF_VARS.fd,if=pflash,format=raw,unit=1 -drive id=cdrom1,if=none,cache=none,snapshot=off,aio=threads,file=OVMF-test/UefiShell.iso,media=cdrom -chardev socket,id=charmonitor,path=/tmp/103RNG2012R2ZAY,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -boot order=cd,menu=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=103BLK-testst.raw,if=none,id=drive-ide0-0-0,format=raw,serial=mike_cao,cache=none -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -drive file=en_windows_server_2012_r2_x64_dvd_2707946.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive file=103RNG2012R2ZAY.vfd,if=none,id=drive-fdc0-0-0,format=raw,cache=none -global isa-fdc.driveA=drive-fdc0-0-0 -netdev tap,script=/etc/qemu-ifup,downscript=no,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=00:52:11:1d:00:00,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=isa_serial0 -device usb-tablet,id=input0 -vnc 0.0.0.0:5 -vga cirrus -monitor stdio -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -drive file=test.raw,if=none,cache=none,id=drive11 -device virtio-blk-pci,drive=drive11,id=disk11
2.install virtio block driver
3.in disk management,initiate the data disk as GPT
4.create new volume on the disk
after step3,disk management prompt "The operation failed to complete because the disk management console view is not up-to-date.Refresh the view by using the refresh task.If the problem persists close the disk management console,then restart disk management or restart the computer"(please check the first attachment);After right click "disk management",then select "Refresh",disk was initiated as GPT already.
after step4,a virtual disk manager window prompt "Incorrect function"(please check the second attachment);Still,after right click "disk management",then select "Refresh",disk volume was created without driver letter.
disk can be initiated smoothly without any error,and without any extra refresh work
virtio scsi does not hit this issue,disk can be initiated without any error
Is this specific to OVMF? If you do the exact same installation & configuration procedure with SeaBIOS, is the warning absent?
I'm asking because I have no idea how this could be caused by OVMF. This should be assigned to virtio-win; the windows devs at least know how to narrow down such issues. I got no clue about windows.
Also -- I think you may have forgotten to upload some screenshots.
Moving to virtio-win due to comment 1.
Of course I could be wrong, and OVMF could be the culprit, but I'll need help from windows developers even to determine that. Thanks.
Created attachment 1015163 [details]
Created attachment 1015164 [details]
create volume screenshot
(In reply to Laszlo Ersek from comment #1)
> Is this specific to OVMF? If you do the exact same installation &
> configuration procedure with SeaBIOS, is the warning absent?
> I'm asking because I have no idea how this could be caused by OVMF. This
> should be assigned to virtio-win; the windows devs at least know how to
> narrow down such issues. I got no clue about windows.
We did not hit this issue when using seabios.
Lijin confirmed that so such issue using virtio-scsi as well
Is it reproducible with drivers from build 100?
Created attachment 1017299 [details]
install win2k12R2 guest with viostor system disk
1.cannot reproduce this issue with build 100,disk can be formatted correctly.
2.BTW,install win2k12R2 guest with virtio-blk-pci SYSTEM disk,load viostor driver when required and then chose the system disk to install,guest installation can NOT continue(please check the screenshot).
Also cannot reproduce this issue with build100 and seabios,maybe the same issue with this bug
3.Our build 103 viostor whql job "Flush Test" is failed due to this bug.
*** Bug 1224441 has been marked as a duplicate of this bug. ***
please check it with the latest driver, available at
Reproduced this issue on build 103
Verified this issue on build 104
steps same as comment #0
on build 103, errors prompt when initialize virtio-blk disk as GPT
on build 104, virtio-blk disk can be initialize as GPT and can create volume correctly
Based on above ,this issue has been fixed already.
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.