summary refs log tree commit diff stats
path: root/results/classifier/zero-shot/105/graphic/1585971
blob: f2764c93a2d06d4f4020dfe037f19ca4b2b661e6 (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
graphic: 0.887
device: 0.840
other: 0.821
instruction: 0.750
boot: 0.712
semantic: 0.703
socket: 0.646
network: 0.643
mistranslation: 0.625
vnc: 0.556
KVM: 0.507
assembly: 0.319

Host system crashes on qemu with DMA remapping

Hy,

the host system crashes completely, when i try to pass an physical device without boot option intel_iommu=on set. In older kernel versions you didn't have to pass that option.

I wonder if this can be easily checked by asking iommu state, avoiding a crash of the complete system.

My data:
cpu model: Intel(R) Core(TM) i7 CPU
qemu version: 2.4.1-r2
kernel version: 4.1.2 x86_64
command line: 
qemu-system-x86_64 -enable-kvm -drive file=/vms/prod/fw/fw.iso,if=virtio,format=raw -drive file=/vms/prod/fw/swap,if=virtio,format=raw -drive file=/vms/prod/fw/fwdata.iso,if=virtio,format=raw -m 512 -nographic -kernel /data/kernels/vmlinuz-2.6.36-gentoo-r8 -append "root=/dev/vda console=ttyS0 earlyprintk=serial" -net nic,model=virtio,macaddr=DE:AD:BE:EF:2D:AD -net tap,ifname=tapfw0,script=/etc/qemu/qemu-ifup -device pci-assign,host=03:00.0

There are also more detailed informations (if needed) here:
https://forums.gentoo.org/viewtopic-p-7923976.html

Thanks,
Antonios.

Sorry, i have to cancel this report.

The problem seems to be somewhere else. After some reboots the same issue came up again.

Triaging old bug tickets ... Can you still reproduce the issue with the latest version of QEMU and the kernel, or could we close this bug nowadays?

[Expired for QEMU because there has been no activity for 60 days.]