1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
|
other: 0.974
graphic: 0.974
device: 0.953
performance: 0.911
semantic: 0.898
permissions: 0.836
debug: 0.783
network: 0.776
KVM: 0.763
files: 0.744
socket: 0.700
vnc: 0.695
boot: 0.632
PID: 0.628
SB.PCI0.SMB0 device drivers unavailable
QEMU 4.2 introduces new device with this code:
static void build_smb0(Aml *table, I2CBus *smbus, int devnr, int func)
{
Aml *scope = aml_scope("_SB.PCI0");
Aml *dev = aml_device("SMB0");
aml_append(dev, aml_name_decl("_HID", aml_eisaid("APP0005")));
aml_append(dev, aml_name_decl("_ADR", aml_int(devnr << 16 | func)));
build_acpi_ipmi_devices(dev, BUS(smbus), "\\_SB.PCI0.SMB0");
aml_append(scope, dev);
aml_append(table, scope);
}
It is detected by Windows 10 as 'Unknown Device' and there is no driver available.
Please provide a working Windows driver or give ability to disable this device.
what is this shit?
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 devices can be easily added now.
Adding the devices required some PCI information, and the bus itself
to be added to the PCMachineState structure.
Note that this only works on Q35, the ACPI for PIIX4 is not capable
of handling an SMBus device.
Cc: Michael S. Tsirkin <email address hidden>
Cc: Igor Mammedov <email address hidden>
Signed-off-by: Corey Minyard <email address hidden>
Reviewed-by: Paolo Bonzini <email address hidden>
---
Any progress? When will you provide a Windows driver for this and/or ability to disable this device in Qemu?
I'm also having this issue on a Win 10 VM running on a unRaid server.
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.
|