qemu

FORK: QEMU emulator
git clone https://git.neptards.moe/neptards/qemu.git
Log | Files | Refs | Submodules | LICENSE

bug.md (1905B)

      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, please consult
     17 https://www.qemu.org/contribute/security-process/
     18 -->
     19 
     20 ## Host environment
     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`)
     26  - QEMU command line:
     27    <!--
     28    Give the smallest, complete command line that exhibits the problem.
     29 
     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.
     32    -->
     33    ```
     34    ./qemu-system-x86_64 -M q35 -m 4096 -enable-kvm -hda fedora32.qcow2
     35    ```
     36 
     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.)
     41 
     42 
     43 ## Description of problem
     44 <!-- Describe the problem, including any error/crash messages seen. -->
     45 
     46 
     47 ## Steps to reproduce
     48 1.
     49 2.
     50 3.
     51 
     52 
     53 ## Additional information
     54 
     55 <!--
     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.
     58 -->
     59 
     60 <!--
     61 The line below ensures that proper tags are added to the issue.
     62 Please do not remove it.
     63 -->
     64 /label ~"kind::Bug"