blob: fa191800f100d0ba8a2d5358d14c87e2de19694d (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
|
<think>
Okay, so I need to classify this bug report into one of the given categories. Let me read through the problem and see what's going on.
The user reported that QEMU v3.0.0-rc4 configure fails with --enable-mpath on CentOS 7.5 after a specific commit. The commit in question is using a new libmultipath API, which isn't available on their system. Reverting the commit fixes the issue.
Looking at the error message from config.log, it says there's an error because mpath_lib_init() was called with too few arguments. The function expects a struct udev*, but it wasn't provided. This suggests that the code is trying to use a newer API that requires additional parameters which aren't being passed correctly.
The problem arises when enabling multipath support, so the category should relate to how QEMU handles device or storage-related issues. Let's look at the possible categories: device, graphic, socket, network, KVM, etc. Since this is about multipath and device-mapper packages, it falls under 'device' because it's related to handling devices and their configurations.
I don't think it's a mistranslation or assembly issue because it's more about API usage. It's also not performance-related or a kernel/hypervisor problem directly. The core issue is with the libmultipath API change affecting device configuration in QEMU.
</think>
device
|