| 1 | <!-- |
| 2 | This is the upstream QEMU issue tracker. |
| 3 | |
| 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 |
| 7 | how to do this. |
| 8 | |
| 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. |
| 12 | |
| 13 | See https://www.qemu.org/contribute/report-a-bug/ for additional |
| 14 | guidance. |
| 15 | |
| 16 | If this is a security issue, ensure this ticket is marked 'confidential' |
| 17 | before submission. See https://www.qemu.org/contribute/security-process/ |
| 18 | for additional guidance |
| 19 | --> |
| 20 | |
| 21 | ## Host environment |
| 22 | - Operating system: <!-- Windows 10 21H1, Fedora 37, etc. --> |
| 23 | - OS/kernel version: <!-- For POSIX hosts, use `uname -a` --> |
| 24 | - Architecture: <!-- x86, ARM, s390x, etc. --> |
| 25 | - QEMU flavor: <!-- qemu-system-x86_64, qemu-aarch64, qemu-img, etc. --> |
| 26 | - QEMU version: <!-- e.g. `qemu-system-x86_64 --version` --> |
| 27 | - QEMU command line: |
| 28 | <!-- |
| 29 | Give the smallest, complete command line that exhibits the problem. |
| 30 | |
| 31 | If you are using libvirt, virsh, or vmm, you can likely find the QEMU |
| 32 | command line arguments in /var/log/libvirt/qemu/$GUEST.log. |
| 33 | --> |
| 34 | ``` |
| 35 | ./qemu-system-x86_64 -M q35 -m 4096 -enable-kvm -hda fedora32.qcow2 |
| 36 | ``` |
| 37 | |
| 38 | ## Emulated/Virtualized environment |
| 39 | - Operating system: <!-- Windows 10 21H1, Fedora 37, etc. --> |
| 40 | - OS/kernel version: <!-- For POSIX guests, use `uname -a`. --> |
| 41 | - Architecture: <!-- x86, ARM, s390x, etc. --> |
| 42 | |
| 43 | |
| 44 | ## Description of problem |
| 45 | <!-- Describe the problem, including any error/crash messages seen. --> |
| 46 | |
| 47 | |
| 48 | ## Steps to reproduce |
| 49 | 1. |
| 50 | 2. |
| 51 | 3. |
| 52 | |
| 53 | <!-- |
| 54 | Note: if this issue was discovered with the assistance of automated |
| 55 | tooling LLM, static analysis, fuzzers), the reporter must disclose |
| 56 | that in the description. The steps to reproduce, and any other findings, |
| 57 | must be fully validated by the user of the tool prior to submission. |
| 58 | --> |
| 59 | |
| 60 | ## Additional information |
| 61 | |
| 62 | <!-- |
| 63 | Attach logs, stack traces, screenshots, etc. Compress the files if necessary. |
| 64 | If using libvirt, libvirt logs and XML domain information may be relevant. |
| 65 | |
| 66 | If attaching binary test cases you should describe where they were obtained |
| 67 | from, preferably linking to the original source. We greatly prefer test cases in |
| 68 | the form of source code that can be audited before compiling by the engineer. |
| 69 | --> |
| 70 | |
| 71 | <!-- |
| 72 | The line below ensures that proper tags are added to the issue. |
| 73 | Please do not remove it. |
| 74 | --> |
| 75 | /label ~"kind::Bug" |