2 This is the upstream QEMU issue tracker.
4 If you are able to, it will greatly facilitate bug triage if you attempt
5 to reproduce the problem with the latest qemu.git master built from
6 source. See https://www.qemu.org/download/#source for instructions on
9 QEMU generally supports the last two releases advertised on
10 https://www.qemu.org/. Problems with distro-packaged versions of QEMU
11 older than this should be reported to the distribution instead.
13 See https://www.qemu.org/contribute/report-a-bug/ for additional
16 If this is a security issue, please consult
17 https://www.qemu.org/contribute/security-process/
21 - Operating system: (Windows 10 21H1, Fedora 34, etc.)
22 - OS/kernel version: (For POSIX hosts, use `uname -a`)
23 - Architecture: (x86, ARM, s390x, etc.)
24 - QEMU flavor: (qemu-system-x86_64, qemu-aarch64, qemu-img, etc.)
25 - QEMU version: (e.g. `qemu-system-x86_64 --version`)
28 Give the smallest, complete command line that exhibits the problem.
30 If you are using libvirt, virsh, or vmm, you can likely find the QEMU
31 command line arguments in /var/log/libvirt/qemu/$GUEST.log.
34 ./qemu-system-x86_64 -M q35 -m 4096 -enable-kvm -hda fedora32.qcow2
37 ## Emulated/Virtualized environment
38 - Operating system: (Windows 10 21H1, Fedora 34, etc.)
39 - OS/kernel version: (For POSIX guests, use `uname -a`.)
40 - Architecture: (x86, ARM, s390x, etc.)
43 ## Description of problem
44 <!-- Describe the problem, including any error/crash messages seen. -->
53 ## Additional information
56 Attach logs, stack traces, screenshots, etc. Compress the files if necessary.
57 If using libvirt, libvirt logs and XML domain information may be relevant.
61 The line below ensures that proper tags are added to the issue.
62 Please do not remove it.