blob: 18c1d3ef45cbe0337b8c75975292449c570ebd45 (
plain) (
blame)
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
|
KVM: 0.903
kernel: 0.794
graphic: 0.741
semantic: 0.630
user-level: 0.626
architecture: 0.603
hypervisor: 0.592
device: 0.587
arm: 0.577
mistranslation: 0.576
performance: 0.556
x86: 0.531
network: 0.520
peripherals: 0.498
socket: 0.491
virtual: 0.488
permissions: 0.483
PID: 0.478
register: 0.465
ppc: 0.388
files: 0.382
boot: 0.348
debug: 0.347
i386: 0.325
assembly: 0.322
risc-v: 0.282
TCG: 0.245
VMM: 0.225
vnc: 0.192
Armitage crashes KVM guest with Kali2016.2 for QXL video
I recently got a strange bug which seems to be related to qemu-kvm and QXL. I came here via the hints of the KVM web-site for KVM/qemu bug tracking. But, I am not sure whether this is the right bug-tracker at all. Please advise me if I placed the report wrongly.
I installed Kali2016.2 as a KVM guest on a Opensuse Leap 42.1 host (fully updated). The KVM guest machine was configured to use a spice display and QXL video. Everything OK with the installation with the exception of one major application with a Java interface - Armitage.
Armitage is correctly configured and starts (with some minor Java errors) and opens its interface (msf console, target window etc.) Trying to open the 2 specific menu points "Hosts" or "Attack" in the menu bar leads to something very strange: The screen flickers, then the whole login session is stopped and a standard login window opens. This happens independently of the setting for the type of Armitage target window (graphical or table like)
Why do I report this bug here?
Because it happens with the QXL graphical video interface ONLY - not with video=vga or vmvga ! Neither does the bug occur when Armitage is started in a ssh (-X) session from the host.
So, it is closely related to qemu-kvm AND QXL and the Java interaction with both.
I really wonder what in the world can make 2 specific menu points of a Java application crash a KVM guest and restart a login shell in Kali only when QXL is used?
qemu-kvm version : 2.3.1
Kernel version of OS LEAP 42.1: Linux 4.1.31-30-default
I have described the bug also to the Kali people - see https://bugs.kali.org/view.php?id=3698
Please inform me what further data are required - if this is relevant in this bug-tracker at all.
If it's related to QXL, you should likely rather report this bug to the Spice people instead of QEMU. See https://www.spice-space.org/support.html for more information.
Is this still an issue with the latest version? Did you ever report it to the Spice project?
Can be closed - did not happen in later versions
Ok, thanks for your answer, so I'm closing this ticket now.
|