Hide Forgot
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.
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
Created attachment 1241119 [details] SM Bus Controller
Created attachment 1241120 [details] SM Bus Controller hardwate id SM Bus Controller hardware id as picture~
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
Created attachment 1255569 [details] Detail error message
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
(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.
PreWHQL build is ready: https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=559240
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
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