Bug 1765258
| Summary: | viostor not recognized by win 10 version 1903 spanish during windows installation | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Community] Virtualization Tools | Reporter: | blanch | ||||||||
| Component: | virtio-win | Assignee: | Vadim Rozenfeld <vrozenfe> | ||||||||
| Status: | CLOSED NOTABUG | QA Contact: | Virtualization Bugs <virt-bugs> | ||||||||
| Severity: | urgent | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | unspecified | CC: | agedosier, berrange, clalancette, crobinso, ghammer, haoliu, itamar, jforbes, juzhang, laine, libvirt-maint, lijin, veillard, virt-maint, vrozenfe, wyu, yvugenfi | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | All | ||||||||||
| OS: | Windows | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2019-11-20 17:40:32 UTC | Type: | Bug | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
wyu, Could you reproduce this issue? Thanks. Hi,
I cannot reproduce this issue on my env as below (q35 on RHEL8 host):
Guest img: es_windows_10_business_editions_version_1903_x64_dvd_8da6587a.iso
kernel-4.18.0-147.el8.x86_64
qemu-kvm-4.1.0-14.module+el8.1.0+4548+ed1300f4.x86_64
seabios-1.12.0-5.module+el8.1.0+4022+29a53beb.x86_64
virtio-win-prewhql-172
I tried windows 10 education/enterprise/pro/workstations version, but all can load driver successfully.
I cannot find the iso you mentioned, you can provide your iso to me for installing.
Boot cml:
MALLOC_PERTURB_=1 /usr/libexec/qemu-kvm \
-S \
-name 'avocado-vt-vm1' \
-machine q35 \
-nodefaults \
-device VGA,bus=pcie.0,addr=0x1 \
-chardev socket,id=qmp_id_qmpmonitor1,path=/var/tmp/avocado_t_s7ffrb1,server,nowait \
-mon chardev=qmp_id_qmpmonitor1,mode=control \
-chardev socket,id=qmp_id_catch_monitor,path=/var/tmp/avocado_t_s7ffrb1,server,nowait \
-mon chardev=qmp_id_catch_monitor,mode=control \
-device pvpanic,ioport=0x505,id=idUNPtJW \
-chardev socket,path=/var/tmp/avocado_t_s7ffrb1,server,id=chardev_serial0,nowait \
-device isa-serial,id=serial0,chardev=chardev_serial0 \
-chardev socket,id=seabioslog_id_20191111-105044-ZNc9OwDi,path=/var/tmp/avocado_t_s7ffrb1,server,nowait \
-device isa-debugcon,chardev=seabioslog_id_20191111-105044-ZNc9OwDi,iobase=0x402 \
-device pcie-root-port,id=pcie.0-root-port-2,slot=2,chassis=2,addr=0x2,bus=pcie.0 \
-device qemu-xhci,id=usb1,bus=pcie.0-root-port-2,addr=0x0 \
-drive id=drive_image1,if=none,snapshot=off,aio=native,cache=none,format=qcow2,file=/home/kvm_autotest_root/images/install.qcow2 \
-device pcie-root-port,id=pcie.0-root-port-3,slot=3,chassis=3,addr=0x3,bus=pcie.0 \
-device virtio-blk-pci,id=image1,drive=drive_image1,bootindex=0,serial=SYSTEM_DISK0,bus=pcie.0-root-port-3,addr=0x0 \
-device pcie-root-port,id=pcie.0-root-port-5,slot=5,chassis=5,addr=0x5,bus=pcie.0 \
-device virtio-net-pci,mac=9a:c5:c0:67:39:0b,id=idCGQDsf,netdev=idjiEFxQ,bus=pcie.0-root-port-5,addr=0x0 \
-netdev tap,id=idjiEFxQ,vhost=on \
-m 4096 \
-smp 4,maxcpus=4,cores=2,threads=1,dies=1,sockets=2 \
-cpu 'Skylake-Server',hv_stimer,hv_synic,hv_vpindex,hv_reset,hv_relaxed,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv-tlbflush,+kvm_pv_unhalt \
-drive id=drive_cd1,if=none,snapshot=off,aio=native,cache=none,media=cdrom,file=es_windows_10_business_editions_version_1903_x64_dvd_8da6587a.iso \
-device ide-cd,id=cd1,drive=drive_cd1,bootindex=2,bus=ide.0,unit=0 \
-drive id=drive_winutils,if=none,snapshot=off,aio=native,cache=none,media=cdrom,file=/home/kvm_autotest_root/iso/windows/virtio-win-prewhql-0.1-172.iso \
-device ide-cd,id=winutils,drive=drive_winutils,bootindex=3,bus=ide.1,unit=0 \
-device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1 \
-vnc :1 \
-rtc base=localtime,clock=host,driftfix=slew \
-boot order=cdn,once=d,menu=off,strict=off \
-enable-kvm \
-monitor stdio
I am finding a way to send you the ISO image. Standard procedures are not valid because of it's size In the meantime, could you share with me virtio-win-prewhql-172 ? best regards Josep Hi wyu I have found a way to sent you the ISO I did send an e-mail with a link to your private sharing portal ( compartir ) for unloading the ISO image Created attachment 1635987 [details]
viostor-driver-win10
Hi, I can reproduce this issue with the windows iso from Josep. steps: 1 boot guest with virtio-blk device as comment#2 2 try to load E:viostor\w10\amd64\viostor.inf during installation. It shows error the same as attachment "Print screen of wincdoes installation error" Guest img: SW_DVD9_Win_Pro_10_1903_64BIT_Spanish_Pro_Ent_EDU_N_MLF_X22-02936.ISO kernel-4.18.0-147.el8.x86_64 qemu-kvm-4.1.0-14.module+el8.1.0+4548+ed1300f4.x86_64 seabios-1.12.0-5.module+el8.1.0+4022+29a53beb.x86_64 virtio-win-prewhql-172 Thanks Yu Wang Created attachment 1637506 [details]
ide-screenshot
Hi blanch, Seems the iso you used is corrupted according to comment#11(it's only 530M in total), could you have a check? Thanks The iso was corrupted indeed Problem solved Now, Windows 10 Enterprise version 1903 Spanish, works fine, using virtio-win 0.1.172 on top of fedora 30 x64 (In reply to lijin from comment #13) > Hi blanch, > > Seems the iso you used is corrupted according to comment#11(it's only 530M > in total), could you have a check? > > Thanks The iso was corrupted indeed Problem solved Now, Windows 10 Enterprise version 1903 Spanish, works fine, using virtio-win 0.1.172 on top of fedora 30 x64 (In reply to lijin from comment #13) > Hi blanch, > > Seems the iso you used is corrupted according to comment#11(it's only 530M > in total), could you have a check? > > Thanks |
Created attachment 1628922 [details] Print screen of wincdoes installation error Description of problem: When creating a new Windows 10 VM on qcow2 image, Windows 10 does not recognize viostore driver ( 64 bit ) Windows asks for a driver, recognizes viostor as a valid one, but loading fails, and windoes asks for a valid driver again Version-Release number of selected component (if applicable): Windows 10 64 bit 1903 installa media SW_DVD9_Win_Pro_10_1903_64BIT_Spanish_Pro_Ent_EDU_N_MLF_X22-02936.iso virtio-win 0.1.172 How reproducible: 100% Steps to Reproduce: 1. create new vm with virt-manager from iso image 2. create empty disk image with virtio drive and format qcow2 3. proceed with installation when asked for a driver go to virtio-win amd64 viostor 4. windowes recognizes it as a valid driver 5 go ahead Actual results: loading driver fails ans windows stay in the same installation srep Expected results: loading driver succeeds and windows goes to the next installation step Additional info: