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.

Bug 1393772

Summary: New unknown device "SM Bus Controller" shows in system device manager after booting with q35
Product: Red Hat Enterprise Linux 7 Reporter: Peixiu Hou <phou>
Component: virtio-winAssignee: Sameeh Jubran <sjubran>
virtio-win sub component: virtio-win-prewhql QA Contact: Virtualization Bugs <virt-bugs>
Status: CLOSED ERRATA Docs Contact:
Severity: unspecified    
Priority: unspecified CC: ailan, chayang, jinzhao, juzhang, knoel, lijin, lmiksik, lprosek, phou, virt-maint, yvugenfi
Version: 7.3   
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-01 12:55:38 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:
Description Flags
SM Bus Controller
none
SM Bus Controller hardwate id
none
Detail error message none

Description Peixiu Hou 2016-11-10 10:20:24 UTC 
Description of problem:
An new unknown device "SM Bus Controller" show in system device manager after booting with q35, connot install driver automatic, and we don't have it's driver package.

OS:
Win2008-32/64
Win7-32/64

Version-Release number of selected component (if applicable):
kernel-3.10.0-518.el7.x86_64
qemu-kvm-rhev-2.6.0-27.el7.x86_64
seabios-1.9.1-5.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. boot cli:
/usr/libexec/qemu-kvm -name 127BLN200864GV1 -enable-kvm -m 3G -smp 4 -uuid a45536aa-c20d-42f9-b24a-a7fec987fdb5 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/tmp/127BLN2008329IU,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 -drive file=127BLN200864GV1,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_2008_datacenter_enterprise_standard_sp2_x86_dvd_342333.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=127BLN2008329IU.vfd,if=floppy,id=drive-fdc0-0-0,format=raw,cache=none -netdev tap,script=/etc/qemu-ifup,downscript=no,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=00:52:0e:49:68:72 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=isa_serial0 -device usb-tablet,id=input0 -vnc 0.0.0.0:1 -M q35 -vga cirrus -monitor stdio

2. Open the system device management
3. Check in other devices.

Actual results:
Unknown device "SM Bus Controller" shows

Expected results:
No unknown device

Additional info:
Booted with pc, none "SM Bus Controller" device.
Comment 2 Marcel Apfelbaum 2017-01-12 13:41:54 UTC 
Hi,

Can you please attach a screenshot?
Can you please right-click on it -> properties and select Details?
What is the hardware ID value, is it ACPI\QEMU0002?

Thanks,
Marcel
Comment 3 Peixiu Hou 2017-01-16 06:58:10 UTC 
Created attachment 1241119 [details]
SM Bus Controller
Comment 4 Peixiu Hou 2017-01-16 07:01:20 UTC 
Created attachment 1241120 [details]
SM Bus Controller hardwate id

SM Bus Controller hardware id as picture~
Comment 14 Peixiu Hou 2017-02-20 03:14:09 UTC 
Hi Yan,

I tried to install the inf for "SM Bus Controller", occurred an error message:
-------------------------------------------------------------------------------
Windows found driver software for your device but encountered an error while attempting to install it.

An error occurred during the installation of the deviceļ¼š
The driver installation file for this device is missing a necessary entry. This may be because the INF was written for Windows 95 or later. Contact your hardware vendor.
--------------------------------------------------------------------------------
And after flashed the inf for "SM Bus controller" device, the device name changed to "Unknown device".

Details pls refer to the attached picture.


Best Regards~
Peixiu Hou
Comment 15 Peixiu Hou 2017-02-20 03:16:03 UTC 
Created attachment 1255569 [details]
Detail error message
Comment 21 Ladi Prosek 2017-05-16 08:12:42 UTC 
Sameeh, are you also going to add the new driver to the packaging scripts? For upstream it should be a one-line change, see:
https://github.com/crobinso/virtio-win-pkg-scripts/commit/97b12214b2818bf51996e73a00b7faf87c646dcf
Comment 22 Sameeh Jubran 2017-05-22 07:42:19 UTC 
(In reply to Ladi Prosek from comment #21)
> Sameeh, are you also going to add the new driver to the packaging scripts?
> For upstream it should be a one-line change, see:
> https://github.com/crobinso/virtio-win-pkg-scripts/commit/
> 97b12214b2818bf51996e73a00b7faf87c646dcf

Yes, I have already created a pull request.
Comment 23 Yvugenfi@redhat.com 2017-05-22 07:45:37 UTC 
PreWHQL build is ready: https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=559240
Comment 24 Peixiu Hou 2017-05-23 08:07:24 UTC 
Verified this bug with virtio-win-prewhql-138. 
On Win2008-32/64, the SM Bus driver can be installed successfully, and whql test on both guests passed.
On Win7-32/64, this SM Bus device does not show in device management currently.

Used version:
kernel-3.10.0-634.el7.x86_64
qemu-kvm-rhev-2.9.0-3.el7.x86_64
seabios-1.10.2-2.el7.x86_64


Best Regards~
Peixiu
Comment 27 errata-xmlrpc 2017-08-01 12:55:38 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