** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1856724
Title:
SB.PCI0.SMB0 device drivers unavailable
Status in QEMU:
Fix Released
Hi, although this isn't my area of expertise, the bug caught my eye.
Peter Maydell points out that there is a commit that addresses this
issue:
https://github.com/qemu/qemu/commit/aefcaf9d1b3ebb30981627bd08f595211a648a62
It just never made its way back here to launchpad.
** Changed in: qemu
I'm also having this issue on a Win 10 VM running on a unRaid server.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1856724
Title:
SB.PCI0.SMB0 device drivers unavailable
Status in QEMU:
New
Bu
Any progress? When will you provide a Windows driver for this and/or
ability to disable this device in Qemu?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1856724
Title:
SB.PCI0.SMB0 device drivers
I noticed this as well. Apparently it was introduced in the following
commit:
https://github.com/qemu/qemu/commit/ebe15582cafeb944a1c6e99aa526e81a1551c567
Saying:
---
pc: Add an SMB0 ACPI device to q35
This is so I2C devices can be found in the ACPI namespace. Currently
that's only IPMI, but d
what is this shit?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1856724
Title:
SB.PCI0.SMB0 device drivers unavailable
Status in QEMU:
New
Bug description:
QEMU 4.2 introduces new device wit
