blob: 809e724b7838d2e0ac9b1c9326231e46a8d8da9f (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
|
<think>
Okay, I need to classify this bug report into one of the given categories. Let me read through the report carefully.
The user is using QEMU with an iSCSI backend for drive-backup. When the iSCSI server crashes or network is interrupted, the VM's disk stops responding and becomes unresponsive. The problem occurs both in the query-block command and within the guest OS.
Looking at the categories: Mistranslation relates to incorrect mapping from source to target but this isn't a user-mode issue. Assembly lowering isn't relevant here either. Other categories like device, network, KVM, etc., are possible.
The bug involves an iSCSI connection loss causing VM issues. The drive is connected via virtio-blk-pci, which relates to devices and peripherals. So the main issue seems to be with the block device or storage handling when the backend (iSCSI) fails.
Therefore, this is likely a 'device' category issue because it's about how QEMU handles storage devices when the underlying storage connection is lost.
</think>
device
|