1391844 – [virtio-win][balloon][viorng][virtio-input] cannot install balloon, viorng and virtio-input driver successfully on win10-32 and win8.1-32(build 127)

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 1391844 - [virtio-win][balloon][viorng][virtio-input] cannot install balloon, viorng and virtio-input driver successfully on win10-32 and win8.1-32(build 127)

Summary: [virtio-win][balloon][viorng][virtio-input] cannot install balloon, viorng an...

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	virtio-win
Sub Component:
Version:	7.4
Hardware:	Unspecified
OS:	Unspecified
Priority:	high
Severity:	high
Target Milestone:	rc
Target Release:	7.4
Assignee:	Vadim Rozenfeld
QA Contact:	Virtualization Bugs
Docs Contact:
URL:
Whiteboard:
Depends On:	1392719
Blocks:	1395265 1401400
TreeView+	depends on / blocked

Reported:	2016-11-04 08:43 UTC by Yu Wang
Modified:	2017-08-01 12:53 UTC (History)
CC List:	8 users (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2017-08-01 12:53:08 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)
install_error (171.23 KB, image/png) 2016-11-04 08:43 UTC, Yu Wang	no flags	Details
setupapi.dev.log for win8-32 (37.80 KB, text/plain) 2016-11-10 06:08 UTC, Peixiu Hou	no flags	Details
setupapi.dev.log for win2008-32 (1.34 MB, text/plain) 2016-11-10 06:09 UTC, Peixiu Hou	no flags	Details
View All

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2017:2341	0	normal	SHIPPED_LIVE	virtio-win bug fix and enhancement update	2017-08-01 16:52:38 UTC

Description Yu Wang 2016-11-04 08:43:06 UTC

Created attachment 1217321 [details]
install_error

Description of problem:
cannot install balloon and viorng driver successfully

Version-Release number of selected component (if applicable):

Guest OS:win8.1-32 win10-32
virtio-win-prewhql-127
qemu-kvm-rhev-2.6.0-27.el7.x86_64
kernel-3.10.0-510.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1.boot with balloon/viorng device

/usr/libexec/qemu-kvm -name 127BLNW10D32OQI -enable-kvm -m 3G -smp 4 -uuid 71196d38-0b4a-4069-92cf-2118ade1e2bd -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/tmp/127BLNW10D32OQI,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=127BLNW10D32OQI,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_10_enterprise_version_1607_updated_jul_2016_x86_dvd_9060097.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=127BLNW10D32OQI.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 e1000,netdev=hostnet0,id=net0,mac=00:52:46:71:f5:98,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:0 -vga cirrus -object rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-pci,rng=rng0 -device virtio-balloon-pci,id=balloon0 -device pvpanic,id=pvpanic0,ioport=0x0505 -object iothread,id=thread0 -drive file=blk-disk.raw,if=none,id=drive-virtio-disk0,format=raw,serial=mike_cao,cache=none -device virtio-blk-pci,iothread=thread0,scsi=off,drive=drive-virtio-disk0,id=virtio-disk0 -device virtio-scsi-pci,id=scsi0,num_queues=4 -drive file=scsi-disk.raw,if=none,id=drive-scsi-disk0,format=raw,serial=mike_cao,cache=none -device scsi-hd,bus=scsi0.0,drive=drive-scsi-disk0,id=scsi-disk0 -device virtio-serial-pci,id=serial0 -chardev socket,id=serialchardev0,host=127.0.0.1,port=12345,server,nowait -device virtserialport,id=port0,chardev=serialchardev0,bus=serial0.0,name=com.redhat.rhevm.vdsm -netdev tap,script=/etc/qemu-ifup,downscript=no,id=hostnet1,vhost=on,queues=4 -device virtio-net-pci,netdev=hostnet1,id=net1,mac=00:52:3b:35:88:00,mq=on,vectors=10

2.install driver for balloon and rng device
3.

Actual results:

shows yellow bond in device manager and shows "Code 10" and "STATUS_DEVICE_POWER_FAILURE"
(refer to attachment)

Expected results:
no error

Additional info:

install success w/ build 125

Comment 1 Yu Wang 2016-11-04 09:08:03 UTC

Hi,

cannot install "virtio-input" driver successfully, too. The same error as comment#0

shows yellow bond in device manager and shows "Code 10" and "STATUS_DEVICE_POWER_FAILURE"

Thanks
Yu Wang

Comment 2 Peixiu Hou 2016-11-04 10:01:34 UTC

Hit same issue on win2008-32, win7-32/64.
Shows yellow bond in device manager and shows "Code 10".

Best Regards~
Peixiu Hou

Comment 5 Peixiu Hou 2016-11-09 04:50:24 UTC

Hit the same issue on win8-32/64 guest， shows yellow bond in device manager and shows "Code 10" and "STATUS_DEVICE_POWER_FAILURE"

On win2008-32, win7-32/64, also cannot install successfully,shows yellow bond in device manager and report error "This device cannot start(Code 10)".

Best Regards~
Peixiu Hou

Comment 6 Vadim Rozenfeld 2016-11-09 05:48:01 UTC

(In reply to Peixiu Hou from comment #5)
> Hit the same issue on win8-32/64 guest， shows yellow bond in device manager
> and shows "Code 10" and "STATUS_DEVICE_POWER_FAILURE"
> 
> On win2008-32, win7-32/64, also cannot install successfully,shows yellow
> bond in device manager and report error "This device cannot start(Code 10)".
> 
> Best Regards~
> Peixiu Hou

can you please post setupapi.dev.log file?

Thank you,
Vadim.

Comment 7 Peixiu Hou 2016-11-10 06:08:31 UTC

Created attachment 1219180 [details]
setupapi.dev.log for win8-32

Hi vadim,

The setupapi.dev.log have uploaded, you can refer to attachments. for win8-32 guest and win2008-32 guest.

And also, on win2008-32. win7-32/64, there is an extra unknown device "SM Bus Controller" shows in device management after booting with q35. we don't have it's driver package. I'm not sure if this problem is impact this bug, if not, if I need to create a new one?

Best Regards~
Peixiu Hou

Comment 8 Peixiu Hou 2016-11-10 06:09:07 UTC

Created attachment 1219181 [details]
setupapi.dev.log for win2008-32

Comment 9 Vadim Rozenfeld 2016-11-10 07:32:35 UTC

(In reply to Peixiu Hou from comment #7)
> Created attachment 1219180 [details]
> setupapi.dev.log for win8-32
> 
> Hi vadim,
> 
> The setupapi.dev.log have uploaded, you can refer to attachments. for
> win8-32 guest and win2008-32 guest.
> 
> And also, on win2008-32. win7-32/64, there is an extra unknown device "SM
> Bus Controller" shows in device management after booting with q35. we don't
> have it's driver package. I'm not sure if this problem is impact this bug,
> if not, if I need to create a new one?

Sure,
Go ahead and open a new bug.
We can always close it as duplicate :)

Best regards,
Vadim.


> 
> Best Regards~
> Peixiu Hou

Comment 10 Vadim Rozenfeld 2016-11-10 07:41:42 UTC

(In reply to Peixiu Hou from comment #8)
> Created attachment 1219181 [details]
> setupapi.dev.log for win2008-32

Thanks,
In both logs errors look the same.

I will start debugging this problem shortly.


     sto:                {Configure Driver Package: exit(0x00000000)}
     dvi:                Install Device: Configuring device (oem1.inf:pci\ven_1af4&dev_1045&subsys_11001af4&rev_01,BALLOON_Device.NT). 00:56:28.671
     dvi:                Install Device: Configuring device completed. 00:56:28.702
     dvi:                Install Device: Restarting device. 00:56:28.718
     dvi:                Install Device: Restarting device completed. 00:56:32.374
!!!  dvi:                Device not started: Device has problem: 0x0a: CM_PROB_FAILED_START.
     ndv:                Device install status=0x00000000
     ndv:                Performing device install final cleanup...
!    ndv:                Queueing up error report since device has a PnP problem...


     dvi:                          Writing common driver property settings.
     dvi:                               DriverDescription=VirtIO RNG Device
     dvi:                               DeviceDisplayName=VirtIO RNG Device
     dvi:                          {Restarting Devices} 23:45:04.953
     dvi:                               Restart: PCI\VEN_1AF4&DEV_1044&SUBSYS_11001AF4&REV_01\4&21B224EC&0&0020
     dvi:                               Restart complete.
!!!  dvi:                               Device not started: Device has problem: 0x0a: CM_PROB_FAILED_START.

Comment 11 Peixiu Hou 2016-11-10 10:29:06 UTC

OK, thanks a lot, and for the problem mentioned in comment#9, I have submitted a new bug 1393772 to track.

Best Regards~
Peixiu Hou

Comment 12 Ladi Prosek 2016-11-14 10:33:43 UTC

This is bug 1392719. There is an uninitialized NTSTATUS variable in VirtioLib-WDF in build 128 which affects all WDF based drivers.

Comment 13 Ladi Prosek 2016-11-14 10:36:08 UTC

I was going to close this bug as a duplicate of 1392719 but it may be worth tracking separately. Please close or keep as you see fit. The fix will be in build 129.

Comment 14 Amnon Ilan 2016-11-17 12:19:14 UTC

Setting TestOnly based on comment#13

Comment 15 Yu Wang 2016-12-22 07:37:53 UTC

Hi,

Verify this bug on build 129, the driver could be installed successfully. So change status to verified.

guest tested
*win7-64
*win8.1-32
*win10-32

driver tested
* viorng
* balloon
* virtio-input
* vioser
* pvpanic

Thanks
Yu Wang

Comment 17 Danilo de Paula 2017-06-08 19:12:46 UTC

I'm taking out the TestOnly keywork. This prevents us from pushing the code to dist_git according to [1]

Comment 19 errata-xmlrpc 2017-08-01 12:53:08 UTC

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://access.redhat.com/errata/RHBA-2017:2341

Note You need to log in before you can comment on or make changes to this bug.