Bug 1391844

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

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

Best Regards~
Peixiu Hou

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

(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.

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

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

(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

(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.

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

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

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.

Setting TestOnly based on comment#13

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

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

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