diff options
Diffstat (limited to 'gitlab/issues_text/target_missing/host_missing/accel_missing')
1755 files changed, 45131 insertions, 0 deletions
diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/100 b/gitlab/issues_text/target_missing/host_missing/accel_missing/100 new file mode 100644 index 000000000..78bf9ef69 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/100 @@ -0,0 +1 @@ +GDB context is inconsistent after "monitor system_reset" diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1000 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1000 new file mode 100644 index 000000000..6e85abef2 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1000 @@ -0,0 +1,4 @@ +Can qemu support different core on one machine? +Description of problem: +I want to build a machine, including three core which is different types, arm Cortex-M3 core, cortex-m33 core, contex-a53 core, communicate through mailbox. I checked the current implementation of QEMU and saw that a machine uses a core, such as mps2.c virt.c . I want to know whether the QEMU strategy supports different types of cores on one machine and can communicate with each other. +Thanks. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1001 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1001 new file mode 100644 index 000000000..fbb5ab4da --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1001 @@ -0,0 +1 @@ +query the current cursor position with QMP diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1005 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1005 new file mode 100644 index 000000000..6ba080cc3 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1005 @@ -0,0 +1,177 @@ +blockdev-del doesn't work after blockdev-backup with incremental, which using dirty-bitmap +Description of problem: +After incremental backup with bitmap, blockdev-del doesn't work at target node. +Because of this, incremental backup cannot rebase to base node. +I refered this. https://qemu-project.gitlab.io/qemu/interop/bitmaps.html#example-incremental-push-backups-without-backing-files +Steps to reproduce: +1. `blockdev-add` incremental backup node +``` +echo '{"execute":"qmp_capabilities"}{"execute":"blockdev-add","arguments":{"driver":"qcow2","node-name":"incre0","file":{"driver":"file","filename":"/mnt/7b12fe9c-fa0f-4f2a-82b1-3a6cd4e15ae8/temp/incre0.qcow2"}}}' | nc -U /mnt/7b12fe9c-fa0f-4f2a-82b1-3a6cd4e15ae8/temp/qmp.sock -N + +{ + "return": { + } +} +``` +2. `blockdev-backup` with `vda` to target `incre0` node +``` +echo '{"execute":"qmp_capabilities"}{"execute":"blockdev-backup", "arguments": {"device": "vda", "bitmap":"bitmap0", "target": "incre0", "sync": "incremental", "job-id": "incre0-job", "speed": 536870912}}' | nc -U /mnt/7b12fe9c-fa0f-4f2a-82b1-3a6cd4e15ae8/temp/qmp.sock -N + +{ + "timestamp": { + "seconds": 1651050066, + "microseconds": 848370 + }, + "event": "JOB_STATUS_CHANGE", + "data": { + "status": "created", + "id": "incre0-job" + } +} +{ + "timestamp": { + "seconds": 1651050066, + "microseconds": 848431 + }, + "event": "JOB_STATUS_CHANGE", + "data": { + "status": "running", + "id": "incre0-job" + } +} +{ + "timestamp": { + "seconds": 1651050066, + "microseconds": 848464 + }, + "event": "JOB_STATUS_CHANGE", + "data": { + "status": "paused", + "id": "incre0-job" + } +} +{ + "timestamp": { + "seconds": 1651050066, + "microseconds": 848485 + }, + "event": "JOB_STATUS_CHANGE", + "data": { + "status": "running", + "id": "incre0-job" + } +} +{ + "return": { + } +} + +``` +3. `query-block-jobs` check `incre0-job` is done +``` +echo '{"execute":"qmp_capabilities"}{"execute":"query-block-jobs"}' | nc -U /mnt/7b12fe9c-fa0f-4f2a-82b1-3a6cd4e15ae8/temp/qmp.sock -N + +{ + "return": { + } +} +{ + "return": [ + ] +} +``` +4. To release write lock (need to rebase in incre0.qcow2), `blockdev-del` +``` +echo '{"execute":"qmp_capabilities"}{"execute":"blockdev-del","arguments":{"node-name":"incre0"}' | nc -U /mnt/7b12fe9c-fa0f-4f2a-82b1-3a6cd4e15ae8/temp/qmp.sock -N + +{ + "return": { + } +} +``` +5. `qemu-img rebase` +``` +qemu-img rebase -b base.qcow2 -u incre0.qcow2 + +qemu-img: Could not open 'incre0.qcow2': Failed to get "write" lock +Is another process using the image [incre0.qcow2]? +``` + +6. check `query-named-block-nodes` after `blockdev-del` +``` +{ + "return": [ + { + "iops_rd": 0, + "detect_zeroes": "off", + "image": { + "virtual-size": 53687091200, + "filename": "/mnt/7b12fe9c-fa0f-4f2a-82b1-3a6cd4e15ae8/temp/incre0.qcow2", + "cluster-size": 65536, + "format": "qcow2", + "actual-size": 241340416, + "format-specific": { + "type": "qcow2", + "data": { + "compat": "1.1", + "compression-type": "zlib", + "lazy-refcounts": false, + "refcount-bits": 16, + "corrupt": false, + "extended-l2": false + } + }, + "dirty-flag": false + }, + "iops_wr": 0, + "ro": false, + "node-name": "incre0", + "backing_file_depth": 0, + "drv": "qcow2", + "iops": 0, + "bps_wr": 0, + "write_threshold": 0, + "encrypted": false, + "bps": 0, + "bps_rd": 0, + "cache": { + "no-flush": false, + "direct": false, + "writeback": true + }, + "file": "/mnt/7b12fe9c-fa0f-4f2a-82b1-3a6cd4e15ae8/temp/incre0.qcow2" + }, + { + "iops_rd": 0, + "detect_zeroes": "off", + "image": { + "virtual-size": 240451584, + "filename": "/mnt/7b12fe9c-fa0f-4f2a-82b1-3a6cd4e15ae8/temp/incre0.qcow2", + "format": "file", + "actual-size": 241340416, + "dirty-flag": false + }, + "iops_wr": 0, + "ro": false, + "node-name": "#block412", + "backing_file_depth": 0, + "drv": "file", + "iops": 0, + "bps_wr": 0, + "write_threshold": 0, + "encrypted": false, + "bps": 0, + "bps_rd": 0, + "cache": { + "no-flush": false, + "direct": false, + "writeback": true + }, + "file": "/mnt/7b12fe9c-fa0f-4f2a-82b1-3a6cd4e15ae8/temp/incre0.qcow2" + }, + ...... + ] +} +``` +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1006 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1006 new file mode 100644 index 000000000..5375c480f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1006 @@ -0,0 +1,3 @@ +qga: add get disk stats of guest interface +Additional information: +just for linux diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1007 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1007 new file mode 100644 index 000000000..bf3829fe4 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1007 @@ -0,0 +1 @@ +qemu-user: add execveat syscall support diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1010 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1010 new file mode 100644 index 000000000..35c82409d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1010 @@ -0,0 +1,78 @@ +Errors on 9p mounts +Description of problem: +I'm trying to run Docker VMs with [Lima](https://github.com/lima-vm/lima), which uses QEMU. I'm trying to expose my home directory on macOS to the Ubuntu VM using `9p`. This is how the mount point looks like inside the Ubuntu VM: + +``` +root@lima-docker:~# mount | grep Users +mount0 on /Users/carlos type 9p (rw,relatime,dirsync,fscache,cachetag=4294894070,access=user,trans=virtio,version=9p2000.u) +root@lima-docker:~# +``` + +The problem I'm seeing is that doing an `ls -l /Users/carlos` gives a "Timer expired" error, and no output: + +``` +root@lima-docker:~# ls -l /Users/carlos +ls: reading directory '/Users/carlos': Timer expired +total 0 +``` + +Under `strace`, it seems that the timer error is raised by the `getdents64` system call: + +``` +root@lima-docker:~# strace -f ls -l /Users/carlos +[..] +openat(AT_FDCWD, "/Users/carlos", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = 3 +newfstatat(3, "", {st_mode=S_IFDIR|0755, st_size=1984, ...}, AT_EMPTY_PATH) = 0 +mmap(NULL, 135168, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xffffa16bf000 +getdents64(3, 0xffffa16bf040, 131072) = -1 ETIME (Timer expired) +[..] +``` + +I've also tried the `9p2000.L` protocol instead, and the results are a bit better. I do get a directory listing, but I see "xxx" errors: + +``` +root@lima-docker:~# ls -l /Users/carlos +ls: /Users/carlos: Network dropped connection on reset +ls: /Users/carlos/Music: Network dropped connection on reset +ls: /Users/carlos/Pictures: Network dropped connection on reset +ls: /Users/carlos/Desktop: Network dropped connection on reset +ls: /Users/carlos/Library: Network dropped connection on reset +ls: /Users/carlos/Public: Network dropped connection on reset +ls: /Users/carlos/Movies: Network dropped connection on reset +ls: /Users/carlos/Applications: Network dropped connection on reset +ls: /Users/carlos/Dropbox: Network dropped connection on reset +ls: /Users/carlos/Maildir: Network dropped connection on reset +ls: /Users/carlos/Documents: Network dropped connection on reset +ls: /Users/carlos/Downloads: Network dropped connection on reset +total 0 +drwx------ 5 carlos dialout 160 Dec 6 10:31 Applications +drwx------ 4 carlos dialout 128 Apr 28 14:40 Desktop +drwx------ 12 carlos dialout 384 Apr 30 08:44 Documents +drwx------ 164 carlos dialout 5248 Apr 29 13:50 Downloads +drwx------ 8 carlos dialout 256 Sep 4 2021 Dropbox +drwx------ 82 carlos dialout 2624 Apr 8 14:05 Library +drwxr-xr-x 3 carlos dialout 96 Nov 12 12:28 Maildir +drwx------ 4 carlos dialout 128 Jul 19 2021 Movies +drwx------ 4 carlos dialout 128 Aug 19 2021 Music +drwx------ 4 carlos dialout 128 Jul 19 2021 Pictures +drwxr-xr-x 4 carlos dialout 128 Jul 19 2021 Public +``` + +The errors in this case seem to come from the `lgetxattr`system call: + +``` +root@lima-docker:~# strace -f ls -l /Users/carlos +[..] +statx(AT_FDCWD, "/Users/carlos/Downloads", AT_STATX_SYNC_AS_STAT|AT_SYMLINK_NOFOLLOW, STATX_MODE|STATX_NLINK|STATX_UID|STATX_GID|STATX_MTIME|STATX_SIZE, {stx_mask=STATX_BASIC_STATS|STATX_MNT_ID, stx_attributes=0, stx_mode=S_IFDIR|0700, stx_size=5248, ...}) = 0 +lgetxattr("/Users/carlos/Downloads", "security.selinux", 0xaaaaec72da70, 255) = -1 ENETRESET (Network dropped connection on reset) +write(2, "ls: ", 4ls: ) = 4 +write(2, "/Users/carlos/Downloads", 23/Users/carlos/Downloads) = 23 +write(2, ": Network dropped connection on "..., 37: Network dropped connection on reset) = 37 +[..] +``` + +I've reported this to the Lima folks at https://github.com/lima-vm/lima/issues/831, and they suggested opening an issue here. Any ideas? +Steps to reproduce: +1. If you have Lima installed (I'm using version 0.10.0): `limactl start --name=docker ./lima-templates/docker.yaml` +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1012 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1012 new file mode 100644 index 000000000..b0aa424cd --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1012 @@ -0,0 +1,41 @@ +9p: newfstatat behaves differently than fstat causing ENOENT for here-documents +Description of problem: +After recent gnulib and coreutils update bash here-documents stopped to work producing `cat: -: No such file or directory` error. +Steps to reproduce: +1. I have file `a` with: +``` +cat <<EOF +x +EOF +``` +2. User visible error inside VM: +``` +root@x86_64:~# grep 9p /proc/mounts +/dev/root / 9p rw,dirsync,relatime,loose,access=any,msize=262144,trans=virtio 0 0 +root@x86_64:~# bash a +cat: -: No such file or directory +``` +3. `strace -fyv bash a` shows: +``` + [pid 291] newfstatat(1</dev/ttyS0>, "", {st_dev=makedev(0, 0x5), st_ino=85, st_mode=S_IFCHR|0600, st_nlink=1, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_rdev=makedev(0x4, 0x40), st_atime=1651577553 /* 2022-05-03T11:32:33.969984203+0000 */, +st_atime_nsec=969984203, st_mtime=1651577553 /* 2022-05-03T11:32:33.969984203+0000 */, st_mtime_nsec=969984203, st_ctime=1651577069 /* 2022-05-03T11:24:29.969984203+0000 */, st_ctime_nsec=969984203}, AT_EMPTY_PATH) = 0 + [pid 291] newfstatat(0</usr/src/tmp/sh-thd.420UUL (deleted)>, "", 0x7ffd1b96a3a0, AT_EMPTY_PATH) = -1 ENOENT (No such file or directory) + [pid 291] write(2</dev/ttyS0>, "cat: ", 5cat: ) = 5 + [pid 291] write(2</dev/ttyS0>, "-", 1-) = 1 + [pid 291] write(2</dev/ttyS0>, ": No such file or directory", 27: No such file or directory) = 27 + [pid 291] write(2</dev/ttyS0>, "\n", 1 +``` +Additional information: +In comparison, `strace -fyv bash a` in the old system w/o gnulib/coreutils update shows: +``` + [pid 283] fstat(1</dev/ttyS0>, {st_dev=makedev(0, 0x5), st_ino=85, st_mode=S_IFCHR|0600, st_nlink=1, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_rdev=makedev(0x4, 0x40), st_atime=1651577784 /* 2022-05-03T11:36:24.238343204+0000 */, st_atime_nsec=238343204, +st_mtime=1651577784 /* 2022-05-03T11:36:24.238343204+0000 */, st_mtime_nsec=238343204, st_ctime=1651577774 /* 2022-05-03T11:36:14.238343204+0000 */, st_ctime_nsec=238343204}) = 0 + [pid 283] fstat(0</usr/src/tmp/sh-thd.3xuISC (deleted)>, {st_dev=makedev(0, 0x14), st_ino=17926519, st_mode=S_IFREG|0600, st_nlink=0, st_uid=502, st_gid=502, st_blksize=262144, st_blocks=0, st_size=2, st_atime=1651577786 /* 2022-05-03T11:36:26.295302472+0000 */, +st_atime_nsec=295302472, st_mtime=1651577785 /* 2022-05-03T11:36:25+0000 */, st_mtime_nsec=0, st_ctime=1651577785 /* 2022-05-03T11:36:25+0000 */, st_ctime_nsec=0}) = 0 + [pid 283] fadvise64(0</usr/src/tmp/sh-thd.3xuISC (deleted)>, 0, 0, POSIX_FADV_SEQUENTIAL) = 0 + [pid 283] mmap(NULL, 270336, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f715f13e000 + [pid 283] read(0</usr/src/tmp/sh-thd.3xuISC (deleted)>, "x\n", 262144) = 2 + [pid 283] write(1</dev/ttyS0>, "x\n", 2x +``` + +So it seems that they started to use `newfstatat` instead of `fstat`, which behaves differently. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1013 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1013 new file mode 100644 index 000000000..4f5449d10 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1013 @@ -0,0 +1 @@ +[Bug] user input is not sanitized in QEMU_Elf_init and can lead to buffer overflow diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1014 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1014 new file mode 100644 index 000000000..d853ec92b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1014 @@ -0,0 +1,3 @@ +Make -chardev, -serial and others accept stderr like they accept stdio +Additional information: +It's not clear what should happen when the guest tries to read from (instead of write to) the character device. On the other hand, I don't think the specific behavior matters very much. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1015 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1015 new file mode 100644 index 000000000..6d8e325f1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1015 @@ -0,0 +1 @@ +qemu-7.0 there is no device "hostdev0" defined diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1016 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1016 new file mode 100644 index 000000000..6cb6a7cc7 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1016 @@ -0,0 +1,3 @@ +In-process sandboxing of the majority of QEMU via WebAssembly or similar +Additional information: +This would be in addition to other sandboxes, such as sVirt. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1018 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1018 new file mode 100644 index 000000000..77835c67f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1018 @@ -0,0 +1,23 @@ +virtio-scsi-pci with iothread results in 100% CPU in qemu 7.0.0 +Description of problem: +Top reports constant 100% host CPU usage by `qemu-system-x86`. I have narrowed the issue down to the following section of the config: +``` + -object iothread,id=t0 \ + -device virtio-scsi-pci,iothread=t0,num_queues=4 \ +``` +If this is replaced by +``` + -device virtio-scsi-pci \ +``` +Then CPU usage is normal (near 0%). + +This problem doesn't appear with qemu 6.2.0 where CPU usage is near 0% even with iothread in the qemu options. +Steps to reproduce: +1. Download Kubuntu 22.04 LTS ISO (https://cdimage.ubuntu.com/kubuntu/releases/22.04/release/kubuntu-22.04-desktop-amd64.iso), +2. Create a root virtual drive for the guest with 'qemu-img create -f qcow2 -o cluster_size=4k kubuntu.img 256G', +3. Start the guest with the config given above, +4. Connect to the guest (using spicy for example, password 'p'), select "try kubuntu" in grub menu AND later in the GUI, let it boot to plasma desktop, monitor host CPU usage using 'top'. + +(there could be a faster way to reproduce it) +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1019 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1019 new file mode 100644 index 000000000..86d951f9c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1019 @@ -0,0 +1,13 @@ +Cannot create a shared directory between Ubuntu 20.04 host and (sparc) NetBSD 8.2 guest +Description of problem: +I am currently trying to set up a shared directory between the Ubuntu 20.04 LTS host and the QEMU guest. However, the error messages that I receive from QEMU immediately are the following, but unfortunately I don't know the proper way to do this given the host and guest OS. +``` +qemu-system-sparc: warning: hub port hub0port1 has no peer +qemu-system-sparc: warning: hub 0 with no nics +qemu-system-sparc: warning: netdev hub0port1 has no peer +qemu-system-sparc: warning: requested NIC (#net276, model virtio) was not created (not supported by this machine?) +``` +Steps to reproduce: +1. Installed `samba` on the host with `sudo apt install samba` +2. Created `/home/rflint/shared_dir` on the host +3. Ran the command indicated at the top of the page. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/102 b/gitlab/issues_text/target_missing/host_missing/accel_missing/102 new file mode 100644 index 000000000..170116192 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/102 @@ -0,0 +1 @@ +Mouse stops working when connected usb-storage-device diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1020 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1020 new file mode 100644 index 000000000..96cc115d6 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1020 @@ -0,0 +1,16 @@ +Display mode 0x6 doubles lines +Description of problem: +When developing https://github.com/korneliuszo/ne2000xt I've occured problem with double lines in mode 0x06 of VGA display, problem doesn't exist in mode 0x05 +Steps to reproduce: +1. Call int 0x10, to setup video mode +2. put data into video ram (./cga.py -i 192.168.1.102 -I ~/a.png) +3. bad display +Additional information: +Bad display: + + +Same data, but in mode 0x05 + + +Same script as in bad display but run under 86Box + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1024 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1024 new file mode 100644 index 000000000..115880f72 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1024 @@ -0,0 +1,10 @@ +Unable to build QEMU with dbus display support on Windows +Description of problem: +When building QEMU on Windows with `./configure --enable-dbus-display --enable-modules`, the following error appears: + +`ERROR: Modules are not available for Windows` +Steps to reproduce: +1. Attempt to build QEMU on Windows (MSYS2 MinGW) with dbus display support +Additional information: +Attempting to build with only `--enable-dbus-display` does not work either, as it requires `--enable-modules`, which does not work on Windows: +`../meson.build:1598:0: ERROR: Feature dbus_display cannot be enabled: -display dbus requires --enable-modules` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1025 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1025 new file mode 100644 index 000000000..b6c9ac52e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1025 @@ -0,0 +1,3 @@ +qemu-img create will silently overwrite existing image +Description of problem: +If file exists, it is silently overwritten, causing loss of data. oups. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1026 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1026 new file mode 100644 index 000000000..b840d2c4f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1026 @@ -0,0 +1,116 @@ +Backup with large RBD disk is slow since QEMU 6.2.0 (since commit 0347a8fd) +Description of problem: +Since commit 0347a8fd4c ("block/rbd: implement bdrv_co_block_status"), there is a big slowdown for large RBD images for backup. +Steps to reproduce: +I used the following script +``` +root@pve701 ~ # cat rbdbackup.sh +#!/bin/bash +rbd create emptytestA -p rbdkvm --size $2 +rbd create emptytestB -p rbdkvm --size $2 +$1 \ + -qmp stdio \ + -drive file=rbd:rbdkvm/emptytestA:conf=/etc/pve/ceph.conf:id=admin:keyring=/etc/pve/priv/ceph/rbdkvm.keyring,if=none,id=driveA,format=raw \ + -drive file=rbd:rbdkvm/emptytestB:conf=/etc/pve/ceph.conf:id=admin:keyring=/etc/pve/priv/ceph/rbdkvm.keyring,if=none,id=driveB,format=raw \ +<<EOF +{"execute": "qmp_capabilities"} +{"execute": "blockdev-backup", + "arguments": { "device": "driveA", + "sync": "full", + "target": "driveB" } } +EOF +rbd -p rbdkvm rm emptytestA +rbd -p rbdkvm rm emptytestB +``` +with 200G and 500G images respectively and QEMU binaries built from current master (i.e. 10c2a0c5e7d48e590d945c017b5b8af5b4c89a3c) and from current master with fc176116cdea816ceb8dd969080b2b95f58edbc0, 9e302f64bb407a9bb097b626da97228c2654cfee and 0347a8fd4c3faaedf119be04c197804be40a384b reverted. + + +Timings: +``` +200G master: 92s +200G master+reverts: 57s +500G master: 526s +500G master+reverts: 142s +``` + +I checked how long a single call to `rbd_diff_iterate2()` in `block/rbd.c` takes, and it seems to take about linearly more time the bigger the image is. But it is also called linearly more often, resulting in about quadratic slowdown overall. +Additional information: +Full commands/output: +``` +root@pve701 ~ # ./rbdbackup.sh ./qemu-upstream/10c2a0c5e7d48e590d945c017b5b8af5b4c89a3c/qemu-system-x86_64 200G +{"QMP": {"version": {"qemu": {"micro": 50, "minor": 0, "major": 7}, "package": "v7.0.0-981-g10c2a0c5e7"}, "capabilities": ["oob"]}} +VNC server running on 127.0.0.1:5900 +{"return": {}} +{"timestamp": {"seconds": 1652695629, "microseconds": 651397}, "event": "JOB_STATUS_CHANGE", "data": {"status": "created", "id": "driveA"}} +{"timestamp": {"seconds": 1652695629, "microseconds": 651447}, "event": "JOB_STATUS_CHANGE", "data": {"status": "running", "id": "driveA"}} +{"timestamp": {"seconds": 1652695629, "microseconds": 651464}, "event": "JOB_STATUS_CHANGE", "data": {"status": "paused", "id": "driveA"}} +{"timestamp": {"seconds": 1652695629, "microseconds": 651490}, "event": "JOB_STATUS_CHANGE", "data": {"status": "running", "id": "driveA"}} +{"return": {}} +{"timestamp": {"seconds": 1652695721, "microseconds": 415892}, "event": "JOB_STATUS_CHANGE", "data": {"status": "waiting", "id": "driveA"}} +{"timestamp": {"seconds": 1652695721, "microseconds": 416066}, "event": "JOB_STATUS_CHANGE", "data": {"status": "pending", "id": "driveA"}} +{"timestamp": {"seconds": 1652695721, "microseconds": 416197}, "event": "BLOCK_JOB_COMPLETED", "data": {"device": "driveA", "len": 214748364800, "offset": 214748364800, "speed": 0, "type": "backup"}} +{"timestamp": {"seconds": 1652695721, "microseconds": 416239}, "event": "JOB_STATUS_CHANGE", "data": {"status": "concluded", "id": "driveA"}} +{"timestamp": {"seconds": 1652695721, "microseconds": 416265}, "event": "JOB_STATUS_CHANGE", "data": {"status": "null", "id": "driveA"}} +^Cqemu-system-x86_64: terminating on signal 2 +{"timestamp": {"seconds": 1652695727, "microseconds": 145031}, "event": "SHUTDOWN", "data": {"guest": false, "reason": "host-signal"}} +Removing image: 100% complete...done. +Removing image: 100% complete...done. +./rbdbackup.sh 200G 81.15s user 6.31s system 89% cpu 1:38.21 total +root@pve701 ~ # ./rbdbackup.sh ./qemu-upstream/10c2a0c5e7d48e590d945c017b5b8af5b4c89a3c-with-rbd-reverts/qemu-system-x86_64 200G +{"QMP": {"version": {"qemu": {"micro": 50, "minor": 0, "major": 7}, "package": "v7.0.0-984-g20a19f8eae"}, "capabilities": ["oob"]}} +VNC server running on 127.0.0.1:5900 +{"return": {}} +{"timestamp": {"seconds": 1652695737, "microseconds": 444734}, "event": "JOB_STATUS_CHANGE", "data": {"status": "created", "id": "driveA"}} +{"timestamp": {"seconds": 1652695737, "microseconds": 444818}, "event": "JOB_STATUS_CHANGE", "data": {"status": "running", "id": "driveA"}} +{"timestamp": {"seconds": 1652695737, "microseconds": 444860}, "event": "JOB_STATUS_CHANGE", "data": {"status": "paused", "id": "driveA"}} +{"timestamp": {"seconds": 1652695737, "microseconds": 444885}, "event": "JOB_STATUS_CHANGE", "data": {"status": "running", "id": "driveA"}} +{"return": {}} +{"timestamp": {"seconds": 1652695794, "microseconds": 437168}, "event": "JOB_STATUS_CHANGE", "data": {"status": "waiting", "id": "driveA"}} +{"timestamp": {"seconds": 1652695794, "microseconds": 437248}, "event": "JOB_STATUS_CHANGE", "data": {"status": "pending", "id": "driveA"}} +{"timestamp": {"seconds": 1652695794, "microseconds": 437341}, "event": "BLOCK_JOB_COMPLETED", "data": {"device": "driveA", "len": 214748364800, "offset": 214748364800, "speed": 0, "type": "backup"}} +{"timestamp": {"seconds": 1652695794, "microseconds": 437368}, "event": "JOB_STATUS_CHANGE", "data": {"status": "concluded", "id": "driveA"}} +{"timestamp": {"seconds": 1652695794, "microseconds": 437381}, "event": "JOB_STATUS_CHANGE", "data": {"status": "null", "id": "driveA"}} +^Cqemu-system-x86_64: terminating on signal 2 +{"timestamp": {"seconds": 1652695803, "microseconds": 242148}, "event": "SHUTDOWN", "data": {"guest": false, "reason": "host-signal"}} +Removing image: 100% complete...done. +Removing image: 100% complete...done. +./rbdbackup.sh 200G 40.68s user 111.12s system 228% cpu 1:06.47 total +root@pve701 ~ # ./rbdbackup.sh ./qemu-upstream/10c2a0c5e7d48e590d945c017b5b8af5b4c89a3c/qemu-system-x86_64 500G +{"QMP": {"version": {"qemu": {"micro": 50, "minor": 0, "major": 7}, "package": "v7.0.0-981-g10c2a0c5e7"}, "capabilities": ["oob"]}} +VNC server running on 127.0.0.1:5900 +{"return": {}} +{"timestamp": {"seconds": 1652695970, "microseconds": 663752}, "event": "JOB_STATUS_CHANGE", "data": {"status": "created", "id": "driveA"}} +{"timestamp": {"seconds": 1652695970, "microseconds": 663892}, "event": "JOB_STATUS_CHANGE", "data": {"status": "running", "id": "driveA"}} +{"timestamp": {"seconds": 1652695970, "microseconds": 663920}, "event": "JOB_STATUS_CHANGE", "data": {"status": "paused", "id": "driveA"}} +{"timestamp": {"seconds": 1652695970, "microseconds": 663980}, "event": "JOB_STATUS_CHANGE", "data": {"status": "running", "id": "driveA"}} +{"return": {}} +{"timestamp": {"seconds": 1652696496, "microseconds": 556219}, "event": "JOB_STATUS_CHANGE", "data": {"status": "waiting", "id": "driveA"}} +{"timestamp": {"seconds": 1652696496, "microseconds": 556386}, "event": "JOB_STATUS_CHANGE", "data": {"status": "pending", "id": "driveA"}} +{"timestamp": {"seconds": 1652696496, "microseconds": 556497}, "event": "BLOCK_JOB_COMPLETED", "data": {"device": "driveA", "len": 536870912000, "offset": 536870912000, "speed": 0, "type": "backup"}} +{"timestamp": {"seconds": 1652696496, "microseconds": 556536}, "event": "JOB_STATUS_CHANGE", "data": {"status": "concluded", "id": "driveA"}} +{"timestamp": {"seconds": 1652696496, "microseconds": 556555}, "event": "JOB_STATUS_CHANGE", "data": {"status": "null", "id": "driveA"}} +^Cqemu-system-x86_64: terminating on signal 2 +{"timestamp": {"seconds": 1652696786, "microseconds": 408273}, "event": "SHUTDOWN", "data": {"guest": false, "reason": "host-signal"}} +Removing image: 100% complete...done. +Removing image: 100% complete...done. +./rbdbackup.sh 500G 453.34s user 28.30s system 58% cpu 13:36.48 total +root@pve701 ~ # ./rbdbackup.sh ./qemu-upstream/10c2a0c5e7d48e590d945c017b5b8af5b4c89a3c-with-rbd-reverts/qemu-system-x86_64 500G +{"QMP": {"version": {"qemu": {"micro": 50, "minor": 0, "major": 7}, "package": "v7.0.0-984-g20a19f8eae"}, "capabilities": ["oob"]}} +VNC server running on 127.0.0.1:5900 +{"return": {}} +{"timestamp": {"seconds": 1652695810, "microseconds": 648931}, "event": "JOB_STATUS_CHANGE", "data": {"status": "created", "id": "driveA"}} +{"timestamp": {"seconds": 1652695810, "microseconds": 649012}, "event": "JOB_STATUS_CHANGE", "data": {"status": "running", "id": "driveA"}} +{"timestamp": {"seconds": 1652695810, "microseconds": 649057}, "event": "JOB_STATUS_CHANGE", "data": {"status": "paused", "id": "driveA"}} +{"timestamp": {"seconds": 1652695810, "microseconds": 649080}, "event": "JOB_STATUS_CHANGE", "data": {"status": "running", "id": "driveA"}} +{"return": {}} +{"timestamp": {"seconds": 1652695952, "microseconds": 13070}, "event": "JOB_STATUS_CHANGE", "data": {"status": "waiting", "id": "driveA"}} +{"timestamp": {"seconds": 1652695952, "microseconds": 13144}, "event": "JOB_STATUS_CHANGE", "data": {"status": "pending", "id": "driveA"}} +{"timestamp": {"seconds": 1652695952, "microseconds": 13210}, "event": "BLOCK_JOB_COMPLETED", "data": {"device": "driveA", "len": 536870912000, "offset": 536870912000, "speed": 0, "type": "backup"}} +{"timestamp": {"seconds": 1652695952, "microseconds": 13233}, "event": "JOB_STATUS_CHANGE", "data": {"status": "concluded", "id": "driveA"}} +{"timestamp": {"seconds": 1652695952, "microseconds": 13249}, "event": "JOB_STATUS_CHANGE", "data": {"status": "null", "id": "driveA"}} +^Cqemu-system-x86_64: terminating on signal 2 +{"timestamp": {"seconds": 1652695955, "microseconds": 692599}, "event": "SHUTDOWN", "data": {"guest": false, "reason": "host-signal"}} +Removing image: 100% complete...done. +Removing image: 100% complete...done. +./rbdbackup.sh 500G 99.49s user 277.78s system 258% cpu 2:25.78 total +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1027 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1027 new file mode 100644 index 000000000..51c51dd98 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1027 @@ -0,0 +1,15 @@ +Executables should have embedded plist on macOS +Description of problem: +QEMU binaries on macOS should have an embedded property list (`plist`). + +The bundle identifier of an application, as well as many other settings, are usually not set programmatically but through an `Info.plist` file found within the application bundle (`.app`) which is a property list (basically a settings file in XML format). + +When liking a command line binary, you can tell the linker to embed such a property list inside the binary and the system will respect that when loading the binary. Having an embedded `Info.plist` is highly recommended for all macOS applications, even command line tools, as many system features will not work correctly (or are not even possible) unless they have one (not in all places the binary name will work instead of a bundle identifier). + +All you need to do is writing a [plist file by hand](https://docs.transifex.com/formats/apple-plist) (for a list of available keys, see [Apple's documentation](https://developer.apple.com/library/archive/documentation/General/Reference/InfoPlistKeyReference/Introduction/Introduction.html)) and then tell the liker to embed it into the binary: + +``` +-sectcreate __TEXT __info_plist YourPlistFile.plist +``` + +This makes it far easier to set app specific settings correctly, as in #334 for example. Also things like sudden termination can be disabled completely that way without a single line of code. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/103 b/gitlab/issues_text/target_missing/host_missing/accel_missing/103 new file mode 100644 index 000000000..30a41471d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/103 @@ -0,0 +1 @@ +9pfs does not honor open file handles on unlinked files diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1032 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1032 new file mode 100644 index 000000000..039b57fd4 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1032 @@ -0,0 +1,16 @@ +Slow random performance of virtio-blk +Steps to reproduce: +1. Download Virtualbox Windows 11 image from https://developer.microsoft.com/en-us/windows/downloads/virtual-machines/ +2. Download virtio-win-iso: `wget https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.215-2/virtio-win-0.1.215.iso` +3. Extract WinDev*.zip `unzip WinDev2204Eval.VirtualBox.zip`and import the extracted Ova in VirtualBox (import WinDev with the option "conversion to vdi" clicked) +4. `qemu-img convert -f vdi -O raw <YourVirtualBoxVMFolder>/WinDev2204Eval-disk001.vdi<YourQemuImgFolder>/WinDev2204Eval-disk001.img` +5. Start Windows 11 in Qemu: +``` +qemu-system-x86_64 -enable-kvm -cpu host -device virtio-blk-pci,scsi=off,drive=WinDevDrive,id=virtio-disk0,bootindex=0 -drive file=<YourQemuImgFolder>/WinDev2204Eval-disk001.img,if=none,id=WinDevDrive,format=raw -net nic -net user,hostname=windowsvm -m 8G -monitor stdio -name "Windows" -usbdevice tablet -device virtio-serial -chardev spicevmc,id=vdagent,name=vdagent -device virtserialport,chardev=vdagent,name=com.redhat.spice.0 -cdrom <YourDownloadFolder>/virtio-win-0.1.215.iso +``` +6. Win 11 won't boot and will go into recovery mode (even the safeboot trick doesn't work here), please follow that [answer](https://superuser.com/questions/1057959/windows-10-in-kvm-change-boot-disk-to-virtio#answer-1200899) to load the viostor driver over recovery cmd +7. Reboot the VM and it should start +2. Install CrystalDiskMark +3. Execute CrystalDiskMark Benchmark +Additional information: +# diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1033 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1033 new file mode 100644 index 000000000..b10dce179 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1033 @@ -0,0 +1,27 @@ +fakeroot under qemu fails with 'semop(1): encountered an error: Function not implemented' +Description of problem: +Appears to be the same issue as that discussed and reportedly fixed in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965109 + +Running raspberry pi os in a chroot (using schroot). Execution of fakeroot as part of dpkg-buildpackage results in: + +``` +dpkg-buildpackage: info: source package clementine +dpkg-buildpackage: info: source version 1.4.0rc1-836-g4665916ba~bullseye +dpkg-buildpackage: info: source distribution bullseye +dpkg-buildpackage: info: source changed by David Sansome <me@davidsansome.com> +dpkg-buildpackage: info: host architecture armhf + dpkg-source --before-build . + fakeroot debian/rules clean +semop(1): encountered an error: Function not implemented +dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit status 1 +``` + +This is the same error as reported in bug 965109, but I'm running the most recent version of qemu - I built it from the git repo, so it should include the fix for 965109. +Steps to reproduce: +1. Setup (s)chroot with arm architecture (although the architecture may not matter) +2. Run fakeroot in the chroot +3. Observe the failure related to the semop syscall +Additional information: +- Not sure what other information I can provide to be helpful. +- The command line listed above is what I gather from ps; it's how qemu-arm-static is called by schroot. I've not been able to figure out _how_ schroot calls qemu-arm-static, I only know it does. +- I compiled qemu from source using my own user id, and ran into an issue with make install, so I manually used install to deploy the executable to /usr/local/bin... And then had to symlink that to /usr/bin as schroot apparently hardcodes the location of qemu-arm-static (at least it did not pick up the version I'd placed in /usr/local/bin). diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1036 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1036 new file mode 100644 index 000000000..b34f0dc20 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1036 @@ -0,0 +1,15 @@ +QEMU immediately exits when combining a GL-enabled SDL display with SPICE +Description of problem: +Running QEMU with the given command line results in QEMU immediately exiting with this line being printed, and no other output: + +``` +qemu-system-x86_64: Display spice is incompatible with the GL context +``` + +I am unsure whether this is a supported mode of setting up QEMU, but QEMU 6.2.0 ran just fine with it (or, to be more precise, it wasn't an issue until ac32b2fff127843355b4f7e7ac9f93dd4a395adf). + +The issue does not happen with `-display sdl,gl=off`, as GL is presumably not involved at all in that case. +Steps to reproduce: +1. Run `./qemu-system-x86_64 -display sdl,gl=on -spice port=5930`. +Additional information: +This issue has been reproduced on other distributions, including Ubuntu 20.04 and Ubuntu 22.04. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1037 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1037 new file mode 100644 index 000000000..e76727941 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1037 @@ -0,0 +1 @@ +Let's encrypt certificate for *.qemu.org has expired diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/104 b/gitlab/issues_text/target_missing/host_missing/accel_missing/104 new file mode 100644 index 000000000..3ca97e105 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/104 @@ -0,0 +1 @@ +Cursor jumps on shape change with vmware vga diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1044 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1044 new file mode 100644 index 000000000..724a1be81 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1044 @@ -0,0 +1 @@ +Warning: libevent-loop-base.a the table of contents is empty diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1048 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1048 new file mode 100644 index 000000000..4cb7b98ce --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1048 @@ -0,0 +1,6 @@ +usb/ohci does not reset HccaPad1 after frame number update. +Description of problem: +When the OHCI controller's framenumber is incremented, HccaPad1 register should be set to zero. Ref OHCI Spec 4.4.1. +Relevant code section: https://gitlab.com/qemu-project/qemu/-/blob/master/hw/usb/hcd-ohci.c#L1201 + +ReactOS uses hccaPad1 to determine if the OHCI hardware is running, consequently it fails this check in current qemu master. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1049 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1049 new file mode 100644 index 000000000..c687090c1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1049 @@ -0,0 +1 @@ +Have DeviceRealize return boolean indicating error diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1052 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1052 new file mode 100644 index 000000000..ca8602dec --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1052 @@ -0,0 +1,79 @@ +QEMU monitor hangs after "stop" QMP command called in postcopy-paused migration state +Description of problem: +QEMU monitor hangs when I try to pause virtual CPUs using "stop" QMP command +on the destination host once migration enters postcopy-paused (after it was +paused using "migrate-pause" QMP command on the source host). QEMU just does +not send any reply to the "stop" command. +Steps to reproduce: +1. start migration +2. wait for the first iteration to finish +3. switch to post-copy using "migrate-start-postcopy" +3. break migration with "migrate-pause" +4. send "stop" to the destination monitor +Additional information: +Unfortunately I haven't been able to get a stack trace as gdb just hangs when +I try to attach it to QEMU after step 4. I can see threads getting SIGUSR1 +after the "stop" command, but I cannot get to gdb prompt afterwards: + +``` +(gdb) c +Continuing. +[New Thread 0x7f41ec9be640 (LWP 1112)] +[New Thread 0x7f41d7fff640 (LWP 1113)] +Thread 4 "CPU 0/KVM" received signal SIGUSR1, User defined signal 1. +Thread 5 "CPU 1/KVM" received signal SIGUSR1, User defined signal 1. +Thread 4 "CPU 0/KVM" received signal SIGUSR1, User defined signal 1. +Thread 5 "CPU 1/KVM" received signal SIGUSR1, User defined signal 1. +Thread 4 "CPU 0/KVM" received signal SIGUSR1, User defined signal 1. +Thread 5 "CPU 1/KVM" received signal SIGUSR1, User defined signal 1. +Thread 4 "CPU 0/KVM" received signal SIGUSR1, User defined signal 1. +Thread 5 "CPU 1/KVM" received signal SIGUSR1, User defined signal 1. +Thread 4 "CPU 0/KVM" received signal SIGUSR1, User defined signal 1. +Thread 5 "CPU 1/KVM" received signal SIGUSR1, User defined signal 1. +Thread 4 "CPU 0/KVM" received signal SIGUSR1, User defined signal 1. +Thread 4 "CPU 0/KVM" received signal SIGUSR1, User defined signal 1. +``` + +I was able to attach strace to it though (in case it is at least a bit +useful). The first line corresponds to the final '}' of the +{"execute":"stop","id":"libvirt-413"} QMP comamnd: + +``` +[pid 72970] recvmsg(20, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="}", iov_len=1}], msg_iovlen=1, msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 1 +[pid 72970] write(4, "\1\0\0\0\0\0\0\0", 8) = 8 +[pid 72949] <... ppoll resumed>) = 1 ([{fd=4, revents=POLLIN}], left {tv_sec=0, tv_nsec=513181335}) +[pid 72970] write(19, "\1\0\0\0\0\0\0\0", 8 <unfinished ...> +[pid 72949] read(4, <unfinished ...> +[pid 72970] <... write resumed>) = 8 +[pid 72949] <... read resumed>"\1\0\0\0\0\0\0\0", 512) = 8 +[pid 72970] write(19, "\1\0\0\0\0\0\0\0", 8 <unfinished ...> +[pid 72949] ppoll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=8, events=POLLIN}, {fd=9, events=POLLIN}, {fd=11, events=POLLIN}, {fd=12, events=POLLIN}, {fd=23, events=POLLIN}, {fd=24, events=POLLIN}, {fd=29, events=POLLIN}, {fd=30, events=POLLIN}, {fd=31, events=POLLIN}, {fd=32, events=POLLIN}, {fd=33, events=POLLIN}, {fd=34, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40, events=POLLIN}, {fd=41, events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}, {fd=44, events=POLLIN}, {fd=45, events=POLLIN}, {fd=46, events=POLLIN}, {fd=47, events=POLLIN}, {fd=48, events=POLLIN}, {fd=49, events=POLLIN}, {fd=50, events=POLLIN}, {fd=51, events=POLLIN}, {fd=52, events=POLLIN}, {fd=53, events=POLLIN}, {fd=54, events=POLLIN}, {fd=55, events=POLLIN}, {fd=56, events=POLLIN}, ...], 74, {tv_sec=0, tv_nsec=0}, NULL, 8 <unfinished ...> +[pid 72970] <... write resumed>) = 8 +[pid 72949] <... ppoll resumed>) = 0 (Timeout) +[pid 72970] write(19, "\1\0\0\0\0\0\0\0", 8 <unfinished ...> +[pid 72949] write(8, "\1\0\0\0\0\0\0\0", 8 <unfinished ...> +[pid 72970] <... write resumed>) = 8 +[pid 72949] <... write resumed>) = 8 +[pid 72970] write(19, "\1\0\0\0\0\0\0\0", 8 <unfinished ...> +[pid 72949] ppoll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=8, events=POLLIN}, {fd=9, events=POLLIN}, {fd=11, events=POLLIN}, {fd=12, events=POLLIN}, {fd=23, events=POLLIN}, {fd=24, events=POLLIN}, {fd=29, events=POLLIN}, {fd=30, events=POLLIN}, {fd=31, events=POLLIN}, {fd=32, events=POLLIN}, {fd=33, events=POLLIN}, {fd=34, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40, events=POLLIN}, {fd=41, events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}, {fd=44, events=POLLIN}, {fd=45, events=POLLIN}, {fd=46, events=POLLIN}, {fd=47, events=POLLIN}, {fd=48, events=POLLIN}, {fd=49, events=POLLIN}, {fd=50, events=POLLIN}, {fd=51, events=POLLIN}, {fd=52, events=POLLIN}, {fd=53, events=POLLIN}, {fd=54, events=POLLIN}, {fd=55, events=POLLIN}, {fd=56, events=POLLIN}, ...], 74, {tv_sec=0, tv_nsec=0}, NULL, 8 <unfinished ...> +[pid 72970] <... write resumed>) = 8 +[pid 72949] <... ppoll resumed>) = 1 ([{fd=8, revents=POLLIN}], left {tv_sec=0, tv_nsec=0}) +[pid 72970] poll([{fd=18, events=POLLIN}, {fd=19, events=POLLIN}, {fd=20, events=0}], 3, -1 <unfinished ...> +[pid 72949] rt_sigprocmask(SIG_BLOCK, ~[], <unfinished ...> +[pid 72970] <... poll resumed>) = 1 ([{fd=19, revents=POLLIN}]) +[pid 72949] <... rt_sigprocmask resumed>[BUS USR1 ALRM IO], 8) = 0 +[pid 72970] read(19, <unfinished ...> +[pid 72949] getpid() = 72949 +[pid 72970] <... read resumed>"\5\0\0\0\0\0\0\0", 16) = 8 +[pid 72949] tgkill(72949, 72971, SIGUSR1 <unfinished ...> +[pid 72970] poll([{fd=18, events=POLLIN}, {fd=19, events=POLLIN}, {fd=20, events=0}], 3, -1 <unfinished ...> +[pid 72949] <... tgkill resumed>) = 0 +[pid 72949] rt_sigprocmask(SIG_SETMASK, [BUS USR1 ALRM IO], NULL, 8) = 0 +[pid 72949] rt_sigprocmask(SIG_BLOCK, ~[], [BUS USR1 ALRM IO], 8) = 0 +[pid 72949] getpid() = 72949 +[pid 72949] tgkill(72949, 72972, SIGUSR1) = 0 +[pid 72949] rt_sigprocmask(SIG_SETMASK, [BUS USR1 ALRM IO], NULL, 8) = 0 +[pid 72949] futex(0x5606f6cb73a8, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, NULL, FUTEX_BITSET_MATCH_ANY +``` + +And that's it, the last futex never returns. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1055 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1055 new file mode 100644 index 000000000..ea9150ede --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1055 @@ -0,0 +1,16 @@ +QEMU does not close listening socket for incoming migration when post-copy migration breaks +Description of problem: +QEMU keeps listening on the incoming port even after breaking a post-copy +migration using "migrate-pause" QMP command. And even once migration is +finished after recovering it "migrate-recover" using a different port number. +If "migrate-recover" is called with a URI specifying the original port (which +is still in LISTEN state), QEMU reports "Failed to find an available port: +Address already in use". +Steps to reproduce: +1. start migration +2. wait for the first iteration to finish +3. switch to post-copy using "migrate-start-postcopy" +3. break migration with "migrate-pause" +4. check lsof -p $QEMU_PID +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/106 b/gitlab/issues_text/target_missing/host_missing/accel_missing/106 new file mode 100644 index 000000000..c39e83c1e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/106 @@ -0,0 +1 @@ +qemu-git gravis ultrasound not working diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1063 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1063 new file mode 100644 index 000000000..e055770f1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1063 @@ -0,0 +1,9 @@ +qemu: could not load PC BIOS 'bios-256k.bin' +Description of problem: +I cloned latest QEMU and build in Ubuntu 18.04, when I run QEMU to start a vm, it tells me `could not load PC BIOS 'bios-256k.bin' + + +Steps to reproduce: +1. Clone latest QEMU in Ubuntu18.04 +2. build QEMU +3. Use QEMU and libvirt to start a virtual machine. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1064 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1064 new file mode 100644 index 000000000..897c85afe --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1064 @@ -0,0 +1,43 @@ +aarch64:qemu6.2.0 compile error +Description of problem: + +Steps to reproduce: +1. download qemu source package +`wget http://mirrors.163.com/centos-vault/centos/8-stream/AppStream/Source/SPackages/qemu-kvm-6.2.0-12.module_el8.7.0%2b1140%2bff0772f9.src.rpm` +2. install qemu source package +`rpm -ivh qemu-*.rpm` +3. build qemu +` rpmbuild --define "_topdir /xxx/src_qemu6.2.0" -bb SPECS/qemu-kvm.spec` +4. error message: +``` +In function 'dump_receive_iov', + inlined from 'filter_dump_receive_iov' at ../net/dump.c:157:5: +../net/dump.c:89:9: error: 'writev' specified size 18446744073709551600 exceeds maximum object size 9223372036854775807 [-Werror=stringop-overflow=] + 89 | if (writev(s->fd, dumpiov, cnt + 1) != sizeof(hdr) + caplen) { + | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +In file included from /home/xxx/src_qemu6.2.0/BUILD/qemu-kvm-6.2.0/include/qemu/osdep.h:108, + from ../net/dump.c:25: +../net/dump.c: In function 'filter_dump_receive_iov': +/usr/include/sys/uio.h:52:16: note: in a call to function 'writev' declared with attribute 'read_only (2, 3)' + 52 | extern ssize_t writev (int __fd, const struct iovec *__iovec, int __count) + | ^~~~~~ +cc1: all warnings being treated as errors +``` +**gcc version** +``` +# gcc --version +gcc (GCC) 10.3.1 +Copyright (C) 2020 Free Software Foundation, Inc. +This is free software; see the source for copying conditions. There is NO +warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. +``` +``` +[root]# meson -v +0.62.1 +[root]# ninja -v +ninja: error: loading 'build.ninja': No such file or directory +[root@vm77 src_qemu6.2.0]# ninja --version +1.8.2 +``` +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1066 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1066 new file mode 100644 index 000000000..366dcf0ed --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1066 @@ -0,0 +1,32 @@ +virtfs fails to access contents of non-readable directories +Description of problem: +Attempting to access a directory inside a non-readable directory via virtfs fails. +Steps to reproduce: +On host: +1. `mkdir -p test/foo/bar` +2. `echo hello world >test/foo/bar/baz.txt` +3. `chmod -r test/foo` + +The following works on host: + +``` +$ ls test +foo +$ ls test/foo +ls: cannot open directory 'test/foo': Permission denied +$ ls test/foo/bar +baz.txt +``` + +However on guest: + +``` +bash-5.1# ls /test/ +foo +bash-5.1# ls /test/foo/ +ls: cannot open directory '/test/foo/': Permission denied +bash-5.1# ls /test/foo/bar/ +ls: cannot access '/test/foo/bar/': Permission denied +``` +Additional information: +I am guessing virtfs attempts to check rights (via access?) on the directory itself when obtaining an inode to give to the guest, however not having read access doesn't mean something can't be executed, especially for directories. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/107 b/gitlab/issues_text/target_missing/host_missing/accel_missing/107 new file mode 100644 index 000000000..d102e979b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/107 @@ -0,0 +1 @@ +qemu-img fixed vhd issues diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1070 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1070 new file mode 100644 index 000000000..09648ccdf --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1070 @@ -0,0 +1,10 @@ +gdbstub XML generation for ARM is done for every CPU +Description of problem: +- As arm_cpu_register_gdb_regs_for_features is called from the device + realize stage for each vCPU in user mode we end up uselessly + regenerating the XML for every new thread. Once you get up to 100 + threads this starts exceeding the large maps done for QHT and PageDesc +Steps to reproduce: +See above command line, valgrind picks it up +Additional information: +See also #866, #967 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1071 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1071 new file mode 100644 index 000000000..114db7ec4 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1071 @@ -0,0 +1,12 @@ +Cannot passthrough two network devices (Mellanox ConnectX-3) to VM. +Description of problem: +Cannot passthrough two network devices (Mellanox ConnectX-3) to VM. + +It generated me an error: +[ 6322.674602] genirq: Flags mismatch irq 16. 00000000 (vfio-intx(0000:05:00.0)) vs. 00000000 (vfio-intx(0000:88:00.0)) + +Passthrough only one device to VM goes well. +Steps to reproduce: +1. Add a first passthrough network device. +2. Add a second passthrough network device. +3. Run VM. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1072 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1072 new file mode 100644 index 000000000..28ad202e0 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1072 @@ -0,0 +1,24 @@ +different behavior when remote debugger is used +Description of problem: +I found Qemu shows different behavior when I run Qemu with hello-world (statically linked binary enclosed) directly or run it through remote debugger. I need help to understand the following: + +1. Is this intended behavior? +1. Any way to make the two approaches have consistent behavior (I prefer the behavior shown in the 2nd approach described below) +1. If it is intended behavior, any explanation why or suggestions how to dig further to root cause the difference. + +The corresponding source code is the line 86 in [filedoalloc.c](https://code.woboq.org/userspace/glibc/libio/filedoalloc.c.html#86). It tests if the file (stdout) is char special device (S_ISCHR) +The preprocessed code is as follows: + if (((((st.st_mode)) & 0170000) == (0020000))) + +I then compared two different approaches to run Qemu: + +1. I used the following command line to collect the trace: qemu_aarch64 -strace -plugin $QEMU_ROOT/build/contrib/plugins/libexeclog.so -d plugin hello.a64. This one tests False for S_ISCHR +1. when I used gdb to connect to Qemu and single-step the instructions, S_ISCHR tests True, which is different from running qemu directly (approach 1). + +Thanks! +Steps to reproduce: +1.[hello.a64](/uploads/4b4ccae8c1e4b045c39ceae6a094d55a/hello.a64) +2. +3. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1074 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1074 new file mode 100644 index 000000000..5fc475cb8 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1074 @@ -0,0 +1,18 @@ +File under symlink gets corrupted when directory is mounted as FAT32 drive +Description of problem: +When mouting a directory as a FAT32 drive, the symlinked BOOTx64.EFI inside gets corrupted after booting it. +Steps to reproduce: +1. mkdir -p fat_dir/EFI/BOOT/ +2. ln -s BOOTx64.EFI fat_dir/EFI/BOOT/BOOTx64.EFI +3. md5sum BOOTx64.EFI +4. Run qemu with arguments like above. +5. md5sum BOOTx64.EFI should print out different hash, confirming corruption. +Additional information: +[BOOTx64.EFI](/uploads/d0a6e899ec9331461179f8dc82fbc421/BOOTx64.EFI) + +The issue was not visible on earlier versions, but I don't know which one exactly was it.\ +I can only say, it was still working in April and it was possible that I was using Fedora 36 Beta. + +Copying the file instead of using a symlink can be used as a workaround. + +The binary should print some debug stuff, like avaliable memory regions and end with an infinite halt-loop. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1075 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1075 new file mode 100644 index 000000000..a49998621 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1075 @@ -0,0 +1,16 @@ +Unable to create a cluster using ppc64le specific kind binary on x86 host architecture +Description of problem: + +Steps to reproduce: +1. docker run --rm --privileged multiarch/qemu-user-static --reset -p yes +2. wget https://github.com/kubernetes-sigs/kind/releases/download/v0.14.0/kind-linux-ppc64le +3. chmod u+x kind-linux-ppc64le +4. curl -LO https://storage.googleapis.com/kubernetes-release/release/$(curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt)/bin/linux/ppc64le/kubectl +5. chmod +x kubectl +6. sudo cp kubectl /usr/local/bin/ +7. KUBECONFIG="${HOME}/kind-test-config" +8. export KUBECONFIG +9. ./kind-linux-ppc64le create cluster --image quay.io/mayurwaghmode111/node-ppc64le:ppc64le -v=3 --wait 1m --retain +10. ./kind-linux-ppc64le export logs +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1076 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1076 new file mode 100644 index 000000000..c2684f4aa --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1076 @@ -0,0 +1,12 @@ +AC97+DirectSound only polls for audio every 10ms with no way to change it +Description of problem: +The AC97 device emulation, at least in combination with the DirectSound backend, only polls for audio every 10ms, meaning that DMA interrupts are received at a maximum frequency of 100Hz. This applies regardless of how large the buffers in the AC97's buffer list are, meaning that if one buffer takes less than 10ms to play, glitches can be heard with no possible mitigations on the host system. + +I came across this when fiddling with Serenity's own latencies in the AC97 driver and userland mixer. As soon as less than 512-sample buffers are used, audio becomes glitchy. Based on timing tests, kernel and userland processing of audio combined takes less than 200μs for one buffer, while the lowest average rate that DMA interrupts are received at is almost exactly 10ms. + +No changes to the dsound latency option, as listed [here](https://www.qemu.org/docs/master/system/invocation.html?highlight=dsound), made any difference; I tried as low as 2ms: `-audiodev dsound,id=snd0,latency=2000`. As far as I can tell there are no IRQ- or latency-related options for the AC97 emulation. +Steps to reproduce: +1. Use SerenityOS as of the above commit. +2. Before building, include an audio file in Base/home/anon; most ordinary FLAC, WAV and MP3 files created without options with ffmpeg should work. +3. Boot Serenity in QEMU on Windows without any special run configuration. +4. Play the audio file with `aplay <filename>`, hear glitches. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1077 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1077 new file mode 100644 index 000000000..6b2d7336a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1077 @@ -0,0 +1 @@ +Qemu - Can't connect to ESXi guest diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1079 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1079 new file mode 100644 index 000000000..d54f05b1a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1079 @@ -0,0 +1,32 @@ +qemu: uncaught target signal 11 (Segmentation fault) - core dumped +Description of problem: +I am trying to build `arm64` image on my `x86_64` machine using `buildx` and I have encountered `qemu: uncaught target signal 11 (Segmentation fault) - core dumped` Error. <br> +# +Steps to reproduce: +1. Create a Dockerfile +``` +FROM python:3.8-slim + +ENV PYTHONDONTWRITEBYTECODE=1 + +# Install packages +RUN apt update +RUN apt-get install -y python3-pip +``` +2. Run binfmt container +``` +docker run --privileged --rm tonistiigi/binfmt --install all +``` +3. Setup new builder +``` +$ docker buildx create --name mybuilder +$ docker buildx use mybuilder +$ docker buildx inspect --bootstrap +``` +4. Build Image +``` +$ docker buildx build --platform linux/amd64,linux/arm64 --push -t user/failure-case . +``` +# +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/108 b/gitlab/issues_text/target_missing/host_missing/accel_missing/108 new file mode 100644 index 000000000..57326b337 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/108 @@ -0,0 +1 @@ +Windows ME falsely detects qemu's videocards as Number Nine Imagine 128 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1080 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1080 new file mode 100644 index 000000000..24ae089bb --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1080 @@ -0,0 +1 @@ +Qemu build fails on Ubuntu diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1081 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1081 new file mode 100644 index 000000000..2c8768b8b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1081 @@ -0,0 +1 @@ +A issue for QLIST_INSERT_BEFORE in include/qemu/queue.h diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1082 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1082 new file mode 100644 index 000000000..cdadc7285 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1082 @@ -0,0 +1,92 @@ +Unable to compile QEMU in Ubuntu 22.04 LTS - libcommon.fa.p +Description of problem: +Since a couple of months ago I can not compile QEMU from its official GIT location anymore. +I do everything described in the guide: https://wiki.qemu.org/Hosts/Linux + +After the configure, the building resturn me this issue: +``` +1155/9661] Compiling C object libcommon.fa.p/ui_vdagent.c.o +FAILED: libcommon.fa.p/ui_vdagent.c.o +cc -m64 -mcx16 -Ilibcommon.fa.p -I../common-user/host/x86_64 -I../linux-user/include/host/x86_64 -I../linux-user/include -I../slirp -I../slirp/src -I/usr/include/pixman-1 -I/usr/include/libpng16 -I/usr/local/include/spice-1 -I/usr/include/p11-kit-1 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gio-unix-2.0 -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/x86_64-linux-gnu -I/usr/include/vte-2.91 -fdiagnostics-color=auto -Wall -Winvalid-pch -Werror -std=gnu11 -O2 -g -isystem /home/andrea/qemu/linux-headers -isystem linux-headers -iquote . -iquote /home/andrea/qemu -iquote /home/andrea/qemu/include -iquote /home/andrea/qemu/disas/libvixl -iquote /home/andrea/qemu/tcg/i386 -pthread -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fno-common -fwrapv -Wold-style-declaration -Wold-style-definition -Wtype-limits -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body -Wnested-externs -Wendif-labels -Wexpansion-to-defined -Wimplicit-fallthrough=2 -Wno-missing-include-dirs -Wno-shift-negative-value -Wno-psabi -fstack-protector-strong -fPIE -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DNCURSES_WIDECHAR=1 -MD -MQ libcommon.fa.p/ui_vdagent.c.o -MF libcommon.fa.p/ui_vdagent.c.o.d -o libcommon.fa.p/ui_vdagent.c.o -c ../ui/vdagent.c +../ui/vdagent.c:82:6: error: ‘VD_AGENT_CAP_SPARSE_MONITORS_CONFIG’ undeclared here (not in a function); did you mean ‘VD_AGENT_CAP_MONITORS_CONFIG’? + 82 | [VD_AGENT_CAP_SPARSE_MONITORS_CONFIG] = "sparse-monitors-config", + | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + | VD_AGENT_CAP_MONITORS_CONFIG +../ui/vdagent.c:82:6: error: array index in initializer not of integer type +../ui/vdagent.c:82:6: note: (near initialization for ‘cap_name’) +../ui/vdagent.c:83:6: error: ‘VD_AGENT_CAP_GUEST_LINEEND_LF’ undeclared here (not in a function) + 83 | [VD_AGENT_CAP_GUEST_LINEEND_LF] = "guest-lineend-lf", + | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +../ui/vdagent.c:83:6: error: array index in initializer not of integer type +../ui/vdagent.c:83:6: note: (near initialization for ‘cap_name’) +../ui/vdagent.c:84:6: error: ‘VD_AGENT_CAP_GUEST_LINEEND_CRLF’ undeclared here (not in a function) + 84 | [VD_AGENT_CAP_GUEST_LINEEND_CRLF] = "guest-lineend-crlf", + | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +../ui/vdagent.c:84:6: error: array index in initializer not of integer type +../ui/vdagent.c:84:6: note: (near initialization for ‘cap_name’) +../ui/vdagent.c:85:6: error: ‘VD_AGENT_CAP_MAX_CLIPBOARD’ undeclared here (not in a function); did you mean ‘VD_AGENT_CAP_CLIPBOARD’? + 85 | [VD_AGENT_CAP_MAX_CLIPBOARD] = "max-clipboard", + | ^~~~~~~~~~~~~~~~~~~~~~~~~~ + | VD_AGENT_CAP_CLIPBOARD +../ui/vdagent.c:85:6: error: array index in initializer not of integer type +../ui/vdagent.c:85:6: note: (near initialization for ‘cap_name’) +../ui/vdagent.c:86:6: error: ‘VD_AGENT_CAP_AUDIO_VOLUME_SYNC’ undeclared here (not in a function) + 86 | [VD_AGENT_CAP_AUDIO_VOLUME_SYNC] = "audio-volume-sync", + | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +../ui/vdagent.c:86:6: error: array index in initializer not of integer type +../ui/vdagent.c:86:6: note: (near initialization for ‘cap_name’) +../ui/vdagent.c:87:6: error: ‘VD_AGENT_CAP_MONITORS_CONFIG_POSITION’ undeclared here (not in a function); did you mean ‘VD_AGENT_CAP_MONITORS_CONFIG’? + 87 | [VD_AGENT_CAP_MONITORS_CONFIG_POSITION] = "monitors-config-position", + | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + | VD_AGENT_CAP_MONITORS_CONFIG +../ui/vdagent.c:87:6: error: array index in initializer not of integer type +../ui/vdagent.c:87:6: note: (near initialization for ‘cap_name’) +../ui/vdagent.c:88:6: error: ‘VD_AGENT_CAP_FILE_XFER_DISABLED’ undeclared here (not in a function) + 88 | [VD_AGENT_CAP_FILE_XFER_DISABLED] = "file-xfer-disabled", + | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +../ui/vdagent.c:88:6: error: array index in initializer not of integer type +../ui/vdagent.c:88:6: note: (near initialization for ‘cap_name’) +../ui/vdagent.c:89:6: error: ‘VD_AGENT_CAP_FILE_XFER_DETAILED_ERRORS’ undeclared here (not in a function) + 89 | [VD_AGENT_CAP_FILE_XFER_DETAILED_ERRORS] = "file-xfer-detailed-errors", + | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +../ui/vdagent.c:89:6: error: array index in initializer not of integer type +../ui/vdagent.c:89:6: note: (near initialization for ‘cap_name’) +../ui/vdagent.c:109:6: error: ‘VD_AGENT_FILE_XFER_START’ undeclared here (not in a function) + 109 | [VD_AGENT_FILE_XFER_START] = "file-xfer-start", + | ^~~~~~~~~~~~~~~~~~~~~~~~ +../ui/vdagent.c:109:6: error: array index in initializer not of integer type +../ui/vdagent.c:109:6: note: (near initialization for ‘msg_name’) +../ui/vdagent.c:110:6: error: ‘VD_AGENT_FILE_XFER_STATUS’ undeclared here (not in a function) + 110 | [VD_AGENT_FILE_XFER_STATUS] = "file-xfer-status", + | ^~~~~~~~~~~~~~~~~~~~~~~~~ +../ui/vdagent.c:110:6: error: array index in initializer not of integer type +../ui/vdagent.c:110:6: note: (near initialization for ‘msg_name’) +../ui/vdagent.c:111:6: error: ‘VD_AGENT_FILE_XFER_DATA’ undeclared here (not in a function) + 111 | [VD_AGENT_FILE_XFER_DATA] = "file-xfer-data", + | ^~~~~~~~~~~~~~~~~~~~~~~ +../ui/vdagent.c:111:6: error: array index in initializer not of integer type +../ui/vdagent.c:111:6: note: (near initialization for ‘msg_name’) +../ui/vdagent.c:112:6: error: ‘VD_AGENT_CLIENT_DISCONNECTED’ undeclared here (not in a function) + 112 | [VD_AGENT_CLIENT_DISCONNECTED] = "client-disconnected", + | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ +../ui/vdagent.c:112:6: error: array index in initializer not of integer type +../ui/vdagent.c:112:6: note: (near initialization for ‘msg_name’) +../ui/vdagent.c:113:6: error: ‘VD_AGENT_MAX_CLIPBOARD’ undeclared here (not in a function); did you mean ‘VD_AGENT_CAP_CLIPBOARD’? + 113 | [VD_AGENT_MAX_CLIPBOARD] = "max-clipboard", + | ^~~~~~~~~~~~~~~~~~~~~~ + | VD_AGENT_CAP_CLIPBOARD +../ui/vdagent.c:113:6: error: array index in initializer not of integer type +../ui/vdagent.c:113:6: note: (near initialization for ‘msg_name’) +../ui/vdagent.c:114:6: error: ‘VD_AGENT_AUDIO_VOLUME_SYNC’ undeclared here (not in a function) + 114 | [VD_AGENT_AUDIO_VOLUME_SYNC] = "audio-volume-sync", + | ^~~~~~~~~~~~~~~~~~~~~~~~~~ +../ui/vdagent.c:114:6: error: array index in initializer not of integer type +../ui/vdagent.c:114:6: note: (near initialization for ‘msg_name’) +``` + +I come from a Windows world, so I have no idea what is the "libcommon.fa.p" about. +Can someone help here? +Steps to reproduce: +1. Follow the instruction in https://wiki.qemu.org/Hosts/Linux to compile QEMU +Expected result: QEMU would compile correctly +Observed result: Compilation errors. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1083 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1083 new file mode 100644 index 000000000..5b52ed3a0 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1083 @@ -0,0 +1 @@ +Qemu on Windows - Emulate 64Bit CPU diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1085 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1085 new file mode 100644 index 000000000..585355465 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1085 @@ -0,0 +1,40 @@ +QEMU 7.0.0 - NSIS installer issue +Description of problem: +Misisng info in QEMU.nsi file +Steps to reproduce: +The exe installer exe file properties has a lot of porpeties missing + + + +This is casued by mssing instruction like + +VIAddVersionKey "ProductName" "" +VIAddVersionKey "ProductVersion" "" +VIAddVersionKey "Comments" "" +VIAddVersionKey "CompanyName" "" +VIAddVersionKey "LegalTrademarks" "" +VIAddVersionKey "LegalCopyright" "" +VIAddVersionKey "FileVersion" "" +VIAddVersionKey "FileDescription" "" + +VIAddVersionKey "InternalName" "" +VIAddVersionKey "OriginalFilename" "" + +In Windows program òlist about uninstalle + +the QEMU icon is not right (generic icon) +The Is missing teh publisg + + + +This si due error on + +!define MUI_UNICON "${SRCDIR}\pc-bios\qemu-nsis.ico" + +that probably point to an icon file not available + +and an misisng line that set Publisher info for uninstalelr + +WriteRegStr HKLM "${UNINST_KEY}" "Publisher" "" + +Thanks. KR. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1088 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1088 new file mode 100644 index 000000000..17c4f9a08 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1088 @@ -0,0 +1 @@ +QEMU 7.0.0 fails to build with linker that does not support --dynamic-list diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1089 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1089 new file mode 100644 index 000000000..7a714c809 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1089 @@ -0,0 +1,24 @@ +when I use memory balloon,the qemu process memory usage is displayed incorrectly +Description of problem: +My vm memory is 4GB,and use the balloon driver,the balloon value is also 4GB. +I run a soft to consume memory in vm,I can see the memory usage rate is 15% in host. When I stop the soft in vm,the memory of free info in host and vm +become normal,but use "top -d 3 -Hp $qemu_pid" to query in host,the memory usage rate is also 15%.I need to modify the balloon value in a smaller values,the memory usage rate will reduce. why? + +Steps to reproduce: +1.run a soft to consume memory in vm,and query top info,the qemu process memory usage:15% + + +2.query free info in host and vm (reduce) + + +3.stop sort in vm + + +4.query free info in host and vm (recover) + + +5.query top info again (also 15%) + + + +6.modify the balloon value in a smaller (modify the balloon value in a smaller values,the memory usage rate will reduce) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/109 b/gitlab/issues_text/target_missing/host_missing/accel_missing/109 new file mode 100644 index 000000000..0c69162b5 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/109 @@ -0,0 +1 @@ +Make Uninstall Rule Requested diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1090 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1090 new file mode 100644 index 000000000..fd38030c2 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1090 @@ -0,0 +1,15 @@ +can't create rocker device because setting device array properties on the command line is broken +Description of problem: +it does not accept the prop_array parameter: + +``` +qemu-system-x86_64 -enable-kvm -m 1g -cpu host -netdev socket,id=dev0,udp=10.10.10.227:30042,localaddr=:30042 -device rocker,len-ports=4,name=sw,len-ports=2,ports[0]=dev0 +qemu-system-x86_64: -device rocker,len-ports=4,name=sw,len-ports=2,ports[0]=dev0: Property 'rocker.ports[0]' not found +``` +Steps to reproduce: +1. just run the command +Additional information: +the latest qemu i find working is 6.1.1... if you start a fedora vm and `dnf install kernel-modules-internal` then the rocker ports appear and work properly... + +thanks, +cs diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1094 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1094 new file mode 100644 index 000000000..5233e3d4c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1094 @@ -0,0 +1,8 @@ +Ubuntu's 22.04 Qemu high RAM usage (memory leak maybe) +Description of problem: +After starting/using my VM for a while, RAM fills up to the 32gb maximum, and firefox starts closing tabs and etc. This didn't happen in ubuntu 21.10 or earlier ubuntus. I've been using virt-manager + qemu for years and only had this after upgrading to ubuntu 22.04. +Steps to reproduce: +1. Launch virt-manager ubuntu VM with 12gb ram maximum (as an example) +2. RAM entire 32gb gets filled but nothing in gnome-system-monitor shows what is using all that RAM +3. Firefox starts closing tabs because RAM is full. Remember that only a 12gb RAM vm and firefox with a few tabs are running, and it fills all 32gb of RAM. Ram starts filling slowly and in 1 hour it fills the entire 32gb. For some reason htop shows a smaller usage, but I'm pretty sure all 32gb are being used as the computer starts freezing and almost crashing (I think swap is being used so it slows down but do not crash) +4. have to restart the computer for RAM to get normal again diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1095 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1095 new file mode 100644 index 000000000..a60021ed4 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1095 @@ -0,0 +1 @@ +[QUESTION] What IF.... diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1096 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1096 new file mode 100644 index 000000000..7608ebd8c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1096 @@ -0,0 +1 @@ +New warning with GCC 13 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1099 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1099 new file mode 100644 index 000000000..306b3e6c6 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1099 @@ -0,0 +1 @@ +zlib: Concurrent modification is unsafe diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1100 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1100 new file mode 100644 index 000000000..fb77d8199 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1100 @@ -0,0 +1 @@ +It riscv64 platform support user model?? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1101 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1101 new file mode 100644 index 000000000..9b6272638 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1101 @@ -0,0 +1,12 @@ +QEMU 7.0.0 corrupts VHDX and VHD (VPC) files on write. +Description of problem: +QEMU writes to VHDX and VHD (VPC) files produce a corrupt/non-compliant image. +QEMU appears to be able to read VHDX and VHD images correctly. + +This problem manifests in at least two cases +1. When attaching a VHDX/VHD file to a QEMU machine. A previously working OS image created using the Hyper-V and imaging tools boots properly, but writes that normally occur in the running VM are not written out correctly. The image will fail to boot the next time due to corruption. +2. Image conversion operations *TO* VHDX/VHD fail. (note that QEMU correctly converts *FROM* VHDX/VHD assuming a well formed input image). This implies that reads to VHDX/VHD are OK, but writes to VHDX/VHD are NOT OK. +Steps to reproduce: +1. See Above. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1102 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1102 new file mode 100644 index 000000000..ef455a73b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1102 @@ -0,0 +1,38 @@ +qemu-user: zero_bss might raise segfault when segment is not writable +Description of problem: +When a PT_LOAD segment with the following attributes presented in the user program, +* MemSiz > FileSiz +* NOT Writable + +qemu-aarch64 will crash with segment fault running it. + + + + +in [linux-user/elfload.c: bss_zero](https://gitlab.com/qemu-project/qemu/-/blob/master/linux-user/elfload.c#L2097), the exceeded part is zero'ed without checking if it is writable +``` + if (host_start < host_map_start) { + memset((void *)host_start, 0, host_map_start - host_start); + } +``` +Steps to reproduce: +1. ./qemu-aarch64 ./X.so +Additional information: +readelf output of X.so +``` +Program Headers: + Type Offset VirtAddr PhysAddr FileSiz MemSiz Flags Align + PHDR 0x0000000000000040 0x0000000000000040 0x0000000000000040 0x0000000000000230 0x0000000000000230 R E 0x8 + LOAD 0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000110270 0x00000000001c94e0 R E 0x10000 + LOAD 0x0000000000129bd0 0x00000000001d9bd0 0x00000000001d9bd0 0x0000000000000438 0x00000000000004c0 RW 0x10000 + LOAD 0x000000000013a008 0x00000000001ea008 0x00000000001ea008 0x0000000000017bd0 0x0000000000017bd0 RW 0x10000 + LOAD 0x0000000000161bd8 0x0000000000211bd8 0x0000000000211bd8 0x000000000000f740 0x000000000000f740 RW 0x10000 + DYNAMIC 0x0000000000161e60 0x0000000000211e60 0x0000000000211e60 0x00000000000001e0 0x00000000000001e0 RW 0x8 + INTERP 0x0000000000089410 0x0000000000089410 0x0000000000089410 0x0000000000000015 0x0000000000000015 R 0x1 + [Requesting program interpreter: /system/bin/linker64] + NOTE 0x000000000013dbc8 0x00000000001edbc8 0x00000000001edbc8 0x0000000000000011 0x0000000000000011 R 0x1 + GNU_EH_FRAME 0x00000000001c86a4 0x00000000001c86a4 0x00000000001c86a4 0x00000000000002dc 0x00000000000002dc R 0x4 + GNU_STACK 0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000 RW 0x10 +``` + +X.so: https://drive.google.com/file/d/1A7mkWRcK2BKkpeevt8T6FVLg-t6mWdgi/view?usp=sharing diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1106 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1106 new file mode 100644 index 000000000..50faffbc1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1106 @@ -0,0 +1,9 @@ +undefined address access cause failure +Description of problem: +Hi, +I used serial device as below: +qemu/hw/char/serial.c +It defines only support 8 registers address space(offset 0x00-0x32). And in guest os, the hardware is synopsys dw_apb_uart which is compatible with 16550. +when it access low 8 registers, it works ok. but it may access high address(0x8c) which serial.c not defined, then fail occur. + +Is there anyway to handle this, access address which device not defined, expect it no handle, but not cause system crash. like read is zero and write ignore. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1107 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1107 new file mode 100644 index 000000000..20015cf1d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1107 @@ -0,0 +1,24 @@ +Virtual monitor heads are not "connected" until viewed in a front end +Description of problem: +When you attach a virtual GPU to a guest, qemu appears to only "attach" a virtual monitor to an output port when that virtual display is +viewed using the GUI. For example, when you boot using the above command line, there will be four displays in ```/sys/class/drm/``` on the guest, +```card0-Virtual-1``` through to ```card0-Virtual-4```. In each of these directories, there is an "enabled" file, which contains either +"enabled" or "disabled". These contain "disabled" until you switch tab/view to look at it using the GUI, at which point they change to "enabled". + +This causes a problem for us because Weston will not initialise displays that do not have a monitor attached, meaning the system we are trying +to boot fails because not all the Weston display surfaces are available. + +There does not appear to be a command line option to force virtual monitors to be attached to virtual displays immediately. Looking through the +Gtk user interface code (and the other front ends) there does not appear to be a call into the qemu core that requests the connection of a virtual +monitor to the virtual displays - my guess is that qemu only connects a monitor when a render request first happens (or similar), but I have not followed the code paths deeper than the source files in ```QEMU/ui/```. + +I also tried using the ```screengrab``` command to screenshot each head, but this does not need sufficient to cause the display to be marked +enabled in the guest. + +While we could possibly automate the GUI using some external tool, we ultimately need to run this in a CI environment using +```egl-headless``` or similar. +Steps to reproduce: +1. Launch qemu with virtio-gpu-gl setting max_outputs > 1 +2. On guest, ```cat /sys/drm/class/card0-Virtual-2``` - it reads "disabled" +3. On host, switch the view to look at the second display ("virtio-gpu-gl-pci.1") +4. On guest, ```cat /sys/drm/class/card0-Virtual-2``` - it now reads "enabled" diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1108 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1108 new file mode 100644 index 000000000..e6ea9c681 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1108 @@ -0,0 +1 @@ +D-Bus display does fails to build if libgdm is not detected diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/111 b/gitlab/issues_text/target_missing/host_missing/accel_missing/111 new file mode 100644 index 000000000..c0763e638 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/111 @@ -0,0 +1 @@ +[OSS-Fuzz] Assertion Failure: !in6_zero(&ip_addr) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1110 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1110 new file mode 100644 index 000000000..a73239c45 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1110 @@ -0,0 +1,3 @@ +Add vhost-user-gpu support for cross architecture emulation +Additional information: +host:Android 12 with Linux kernel 4.14.186+ diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1111 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1111 new file mode 100644 index 000000000..8548a6ee4 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1111 @@ -0,0 +1,18 @@ +Calling FUTEX_LOCK_PI with qemu-x86_64-static caused ENOSYS error. +Description of problem: +When I executed the command "perf bench futex lock-pi" in amd64 docker image on s390x, I got the following error. +``` +perf: thread 2: Could not lock pi-lock for 0x40006c4480 (-1): Function not implemented +perf: thread 2: Could not lock pi-lock for 0x40006c4480 (-1): Function not implemented +perf: thread 2: Could not lock pi-lock for 0x40006c4480 (-1): Function not implemented +perf: thread 2: Could not lock pi-lock for 0x40006c4480 (-1): Function not implemented +``` + +I searched for this error message in the source code of perf-bench. I think that the following system call caused ENOSYS error. +` syscall(SYS_futex, uaddr, FUTEX_LOCK_PI | opflags, val, timeout, uaddr2, val3)` +Steps to reproduce: +1. Execute the command "perf bench futex lock-pi" in amd64 docker image on s390x +2. +3. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1112 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1112 new file mode 100644 index 000000000..721cca9ff --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1112 @@ -0,0 +1 @@ +Heap-overflow in scsi_disk_emulate_write_same diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1113 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1113 new file mode 100644 index 000000000..cc38e8288 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1113 @@ -0,0 +1,14 @@ +TMPDIR is not usable for snapshot-blockdevs, if not root +Description of problem: +for using static disk-content we're using `snapshot`-flag for certain disks and set `TMPDIR` to a VM-specific path. + +when started as root, all is ok. + +when started as non-root, `getenv(TMPDIR)` in function `get_tmp_filename()` in file `block.c` return `NULL`, because glibc handles `TMPDIR` as `UNSECURE_ENVVAR` (glibc-src: `sysdeps/generic/unsecvars.h`) + +well, we could compile qemu by ourself, but then we might miss important updates, so maybe this can be solved in main-source? + +possible solutions: +- additionally look at another var like `QEMU_TMPDIR`, if `getenv("TMPDIR")` results in `NULL` +- add a global option to qemu like `--tmpdir=...` +- add a device-specific option like `snapshotdir=...` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1114 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1114 new file mode 100644 index 000000000..21ee8c56d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1114 @@ -0,0 +1 @@ +Non-deterministic hang in libvfio-user:functional/test-client-server test causing timeout in CentOS 8 CI job diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1116 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1116 new file mode 100644 index 000000000..96bd5fed4 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1116 @@ -0,0 +1,18 @@ +qemu/build/qemu-bundle/var/local/run is linked to qemu/qga/run which doesn't exist after building qemu +Description of problem: +A file qemu/build/qemu-bundle/var/local/run is generated after building qemu and this file is linked to qemu/qga/run which doesn't exist. + +[root@b49691d8db1c local]# ls /home/lxy/qemu/build/qemu-bundle/var/local -hl +total 0 +lrwxrwxrwx. 1 root root 22 Jul 22 00:06 run -> /home/lxy/qemu/qga/run +[root@b49691d8db1c local]# ls -hl /home/lxy/qemu/qga/run +ls: cannot access '/home/lxy/qemu/qga/run': No such file or directory +Steps to reproduce: +1. git clone https://gitlab.com/qemu-project/qemu.git +2. cd qemu/ +3. ./configure --target-list=x86_64-softmmu --enable-kvm +4. make -j100 && make install +5. ls ./build/qemu-bundle/var/local -hl +6. ls -hl ./qga/run +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1117 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1117 new file mode 100644 index 000000000..28648ef95 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1117 @@ -0,0 +1,95 @@ +migration corrupts qcow2 metadata when "backing file: json:{" is involve +Description of problem: +the bug happens when you have a qcow2 with backing file in json format +image: 2.qcow2 +[...] +backing file: json:{"driver": "qcow2", "file": { "driver": "file", "filename": "1.qcow2"}} +backing file format: qcow2 +[...] +if you want to migrate a VM that have that kind of qcow2 attached, the migration is gonna corrupted qcow2 metadata in memory and info block will look like this +json:{\"backing\": {\"backing\": {\"driver\": \"qcow2\", \"file\": {\"driver\": \"file\", \"filename\": \"0.qcow2\"}}, \"driver\": \"qcow2\", \"file\": {\"driver\": \"file\", \"filename\": \"1.qcow2\"}}, \"driver\": \"qcow2\", \"file\": {\"driver\": \"file\", \"filename\": \"2.qcow2\"}} +later if you execute blockdev-snapshot-sync, the corrupt json will be write to the new qcow2 resulting with a unusable qcow2 +Steps to reproduce: +/opt/qemu-7.0.0/bin/qemu-img create -f qcow2 0.qcow2 64G +/opt/qemu-7.0.0/bin/qemu-img create -F qcow2 -f qcow2 -b 'json:{"driver": "qcow2", "file": { "driver": "file", "filename": "0.qcow2"}}' 1.qcow2 +/opt/qemu-7.0.0/bin/qemu-img create -F qcow2 -f qcow2 -b 'json:{"driver": "qcow2", "file": { "driver": "file", "filename": "1.qcow2"}}' 2.qcow2 + +#VM1 +/opt/qemu-7.0.0/bin/qemu-system-x86_64 -enable-kvm -drive if=virtio,file=2.qcow2,node-name=drive0 -qmp stdio -display none + +#VM2 +/opt/qemu-7.0.0/bin/qemu-system-x86_64 -enable-kvm -drive if=virtio,file=2.qcow2,node-name=drive0 -qmp stdio -display none -incoming tcp::8082 + + +#VM1 INFO BLOCK +{"QMP": {"version": {"qemu": {"micro": 0, "minor": 0, "major": 7}, "package": ""}, "capabilities": ["oob"]}} +{ "execute": "qmp_capabilities" } +{"return": {}} +{ "execute": "human-monitor-command", "arguments": {'command-line': 'info block'} } +{"return": "virtio0 (drive0): 2.qcow2 (qcow2)\r\n Attached to: /machine/peripheral-anon/device[0]/virtio-backend\r\n Cache mode: writethrough\r\n Backing file: 1.qcow2 (chain depth: 2)\r\n\r\nide1-cd0: [not inserted]\r\n Attached to: /machine/unattached/device[24]\r\n Removable device: not locked, tray closed\r\n\r\nfloppy0: [not inserted]\r\n Attached to: /machine/unattached/device[17]\r\n Removable device: not locked, tray closed\r\n\r\nsd0: [not inserted]\r\n Removable device: not locked, tray closed\r\n"} + +#VM1 MIGRATE +{ "execute": "migrate", "arguments": { "uri": "tcp:localhost:8082" } } +{"return": {}} +{"timestamp": {"seconds": 1658491019, "microseconds": 233177}, "event": "STOP"} + + +#VM2 INFO BLOCK +{"QMP": {"version": {"qemu": {"micro": 0, "minor": 0, "major": 7}, "package": ""}, "capabilities": ["oob"]}} +{ "execute": "qmp_capabilities" } +{"return": {}} +{ "execute": "human-monitor-command", "arguments": {'command-line': 'info block'} } +{"return": "virtio0 (drive0): 2.qcow2 (qcow2)\r\n Attached to: /machine/peripheral-anon/device[0]/virtio-backend\r\n Cache mode: writeback\r\n Backing file: 1.qcow2 (chain depth: 2)\r\n\r\nide1-cd0: [not inserted]\r\n Attached to: /machine/unattached/device[24]\r\n Removable device: not locked, tray closed\r\n\r\nfloppy0: [not inserted]\r\n Attached to: /machine/unattached/device[17]\r\n Removable device: not locked, tray closed\r\n\r\nsd0: [not inserted]\r\n Removable device: not locked, tray closed\r\n"} + +#VM2 MIGRATE +{"timestamp": {"seconds": 1658491019, "microseconds": 249760}, "event": "RESUME"} + +#VM2 MIGRATION DONE, INFO BLOCK +{ "execute": "human-monitor-command", "arguments": {'command-line': 'info block'} } +{"return": "virtio0 (drive0): json:{\"backing\": {\"backing\": {\"driver\": \"qcow2\", \"file\": {\"driver\": \"file\", \"filename\": \"0.qcow2\"}}, \"driver\": \"qcow2\", \"file\": {\"driver\": \"file\", \"filename\": \"1.qcow2\"}}, \"driver\": \"qcow2\", \"file\": {\"driver\": \"file\", \"filename\": \"2.qcow2\"}} (qcow2)\r\n Attached to: /machine/peripheral-anon/device[0]/virtio-backend\r\n Cache mode: writethrough\r\n Backing file: json:{\"backing\": {\"driver\": \"qcow2\", \"file\": {\"driver\": \"file\", \"filename\": \"0.qcow2\"}}, \"driver\": \"qcow2\", \"file\": {\"driver\": \"file\", \"filename\": \"1.qcow2\"}} (chain depth: 2)\r\n\r\nide1-cd0: [not inserted]\r\n Attached to: /machine/unattached/device[24]\r\n Removable device: not locked, tray closed\r\n\r\nfloppy0: [not inserted]\r\n Attached to: /machine/unattached/device[17]\r\n Removable device: not locked, tray closed\r\n\r\nsd0: [not inserted]\r\n Removable device: not locked, tray closed\r\n"} + + +#VM2 SNAPSHOT AFTER MIGRATION +{ "execute": "blockdev-snapshot-sync", "arguments": { "format": "qcow2", "snapshot-file": "3.qcow2", "node-name": "drive0", "snapshot-node-name": "drive0-snap" }} +Formatting '3.qcow2', fmt=qcow2 cluster_size=65536 extended_l2=off compression_type=zlib size=68719476736 backing_file=json:{"backing": {"backing": {"driver": "qcow2",, "file": {"driver": "file",, "filename": "0.qcow2"}},, "driver": "qcow2",, "file": {"driver": "file",, "filename": "1.qcow2"}},, "driver": "qcow2",, "file": {"driver": "file",, "filename": "2.qcow2"}} backing_fmt=qcow2 lazy_refcounts=off refcount_bits=16 +{"return": {}} + + +#VM2 INFO BLOCK AFTER SNAPSHOT +{ "execute": "human-monitor-command", "arguments": {'command-line': 'info block'} } +{"return": "virtio0 (drive0-snap): 3.qcow2 (qcow2)\r\n Attached to: /machine/peripheral-anon/device[0]/virtio-backend\r\n Cache mode: writethrough\r\n Backing file: json:{\"backing\": {\"backing\": {\"driver\": \"qcow2\", \"file\": {\"driver\": \"file\", \"filename\": \"0.qcow2\"}}, \"driver\": \"qcow2\", \"file\": {\"driver\": \"file\", \"filename\": \"1.qcow2\"}}, \"driver\": \"qcow2\", \"file\": {\"driver\": \"file\", \"filename\": \"2.qcow2\"}} (chain depth: 3)\r\n\r\nide1-cd0: [not inserted]\r\n Attached to: /machine/unattached/device[24]\r\n Removable device: not locked, tray closed\r\n\r\nfloppy0: [not inserted]\r\n Attached to: /machine/unattached/device[17]\r\n Removable device: not locked, tray closed\r\n\r\nsd0: [not inserted]\r\n Removable device: not locked, tray closed\r\n"} + + + +#INFO +/opt/qemu-7.0.0/bin/qemu-img info --backing-chain 3.qcow2 +qemu-img: Could not open 'json:{"backing": {"backing": {"driver": "qcow2", "file": {"driver": "file", "filename": "0.qcow2"}}, "driver": "qcow2", "file": {"driver": "file", "filename": "1.qcow2"}}, "driver": "qcow2", "file": {"driver": "file", "filename": "2.qcow2"}}': Block format 'qcow2' does not support the option 'backing.backing.driver' +Additional information: +Even if the bug is scary it's very simple to fix it + +/opt/qemu-7.0.0/bin/qemu-img info --backing-chain 3.qcow2 +qemu-img: Could not open 'json:{"backing": {"backing": {"driver": "qcow2", "file": {"driver": "file", "filename": "0.qcow2"}}, "driver": "qcow2", "file": {"driver": "file", "filename": "1.qcow2"}}, "driver": "qcow2", "file": {"driver": "file", "filename": "2.qcow2"}}': Block format 'qcow2' does not support the option 'backing.backing.driver' + +root@lenovo2:/data# /opt/qemu-7.0.0/bin/qemu-img rebase -f qcow2 -F qcow2 -u -b 2.qcow2 3.qcow2 +root@lenovo2:/data# /opt/qemu-7.0.0/bin/qemu-img info --backing-chain 3.qcow2 +image: 3.qcow2 +file format: qcow2 +virtual size: 64 GiB (68719476736 bytes) +disk size: 24 KiB +cluster_size: 65536 +backing file: 2.qcow2 +backing file format: qcow2 +Format specific information: + compat: 1.1 + compression type: zlib + lazy refcounts: false + refcount bits: 16 + corrupt: false + extended l2: false + +image: 2.qcow2 +file format: qcow2 +virtual size: 64 GiB (68719476736 bytes) +disk size: 24 KiB +cluster_size: 65536 +[..........] diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1119 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1119 new file mode 100644 index 000000000..3c2c584f1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1119 @@ -0,0 +1,15 @@ +end_code set incorrectly +Description of problem: +https://github.com/qemu/qemu/blob/c99e34e537f13a431a80e3e414e5904e9dd0a116/linux-user/flatload.c#L811 + +This line says: + +``` +info->end_code = libinfo[0].start_code = libinfo[0].text_len; +``` + +but should be + +``` +info->end_code = libinfo[0].start_code + libinfo[0].text_len; +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/112 b/gitlab/issues_text/target_missing/host_missing/accel_missing/112 new file mode 100644 index 000000000..5c0547166 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/112 @@ -0,0 +1 @@ +setting unsupported timeout for i6300esb watchdog causes hw reset diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1120 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1120 new file mode 100644 index 000000000..fd36aa92a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1120 @@ -0,0 +1,12 @@ +Multiboot direct loading broken. +Description of problem: +This is my kernel and it's multiboot loader. It passed the check of `grub-file`, but QEMU could not load it. +``` +qemu-system-i386: Error loading uncompressed kernel without PVH ELF Note +``` + +When I add `-machine type=pc-i440fx-3.1`, QEMU shows `qemu: linux kernel too old to load a ram disk` or `qemu: invalid kernel header`. + +The multiboot file is linked with `ld.lld -s -o`. + +[toop](/uploads/7f230dc39d6a3a8c43c4c720d31878c6/toop)[multiboot](/uploads/59faa4607dc2837b54c89b35db6f206a/multiboot) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1125 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1125 new file mode 100644 index 000000000..9e8e624fb --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1125 @@ -0,0 +1,3 @@ +error on run qemu-system-aarch64 -smp 2 +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1128 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1128 new file mode 100644 index 000000000..ebd6be401 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1128 @@ -0,0 +1,24 @@ +PPC: `spr_write_xer` doesn't set flag bits in `cpu_xer` +Description of problem: +`spr_write_xer()` does not set the `ca`, `ov`, `so`, `ca32`, `ov32` etc. flag bits in the `cpu_xer` variable. + +In fact it copies all bits from the source `GPR` and _excludes_ each flag bit. + +This is not a problem for execution since `spr_read_xer()` gets the flag bits from `cpu_ca/ov/so...` and not from `cpu_xer`. + +Nonetheless it is problem for tools which trace the execution in QEMU (e.g. https://github.com/BinaryAnalysisPlatform/qemu). + +A fix would be to remove the `~` in https://gitlab.com/qemu-project/qemu/-/blob/master/target/ppc/translate.c#L481 +Steps to reproduce: +Haven't found out yet how to debug QEMU so the TCGv values can be investigated. But in general one need to: + +- Execute a binary which executes something like: +``` +r4 = 0xffffffffffffffff +mtxer r4 +``` +and check the `cpu_xer` value after the `xer` write. + +Checking the debug logs (`in_asm,cpu`) doesn't work, since the `xer` value in the logs is not taken directly from `cpu_xer`. +Additional information: +Code ref: https://gitlab.com/qemu-project/qemu/-/blob/master/target/ppc/translate.c#L480-L483 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1129 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1129 new file mode 100644 index 000000000..a2ad2f240 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1129 @@ -0,0 +1,23 @@ +aarch64:qemu7.0.0 static compile error +Description of problem: +I'm trying to static compile qemu so I can chroot into different architectures and use podman for simulating amd64 containers. +However, when I tried to configure using the command above, I got the following error: + +``` +FAILED: qemu-aarch64_be +c++ -o qemu-aarch64_be libcommon.fa.p/cpus-common.c.o libcommon.fa.p/page-vary-common.c.o libcommon.fa.p/disas_arm-a64.cc.o libcommon.fa.p/disas_libvixl_vixl_a64_decoder-a64.cc.o libcommon.fa.p/disas_libvixl_vixl_a64_disasm-a64.cc.o libcommon.fa.p/disas_libvixl_vixl_a64_instructions-a64.cc.o libcommon.fa.p/disas_libvixl_vixl_compiler-intrinsics.cc.o libcommon.fa.p/disas_libvixl_vixl_utils.cc.o libcommon.fa.p/disas_arm.c.o libcommon.fa.p/hw_core_cpu-common.c.o libcommon.fa.p/hw_core_machine-smp.c.o libcommon.fa.p/accel_accel-user.c.o libcommon.fa.p/common-user_safe-syscall.S.o libcommon.fa.p/common-user_safe-syscall-error.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_aarch64_signal.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_aarch64_cpu_loop.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_cpu.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_crypto_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_debug_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_gdbstub.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_iwmmxt_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_m_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_mve_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_neon_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_op_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_tlb_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_translate.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_translate-m-nocp.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_translate-mve.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_translate-neon.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_translate-vfp.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_vec_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_vfp_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_cpu_tcg.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_kvm-stub.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_cpu64.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_gdbstub64.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_helper-a64.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_mte_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_pauth_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_sve_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_translate-a64.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_translate-sve.c.o libqemu-aarch64_be-linux-user.fa.p/trace_control-target.c.o libqemu-aarch64_be-linux-user.fa.p/cpu.c.o libqemu-aarch64_be-linux-user.fa.p/disas.c.o libqemu-aarch64_be-linux-user.fa.p/gdbstub.c.o libqemu-aarch64_be-linux-user.fa.p/page-vary.c.o libqemu-aarch64_be-linux-user.fa.p/semihosting_arm-compat-semi.c.o libqemu-aarch64_be-linux-user.fa.p/tcg_optimize.c.o libqemu-aarch64_be-linux-user.fa.p/tcg_region.c.o libqemu-aarch64_be-linux-user.fa.p/tcg_tcg.c.o libqemu-aarch64_be-linux-user.fa.p/tcg_tcg-common.c.o libqemu-aarch64_be-linux-user.fa.p/tcg_tcg-op.c.o libqemu-aarch64_be-linux-user.fa.p/tcg_tcg-op-gvec.c.o libqemu-aarch64_be-linux-user.fa.p/tcg_tcg-op-vec.c.o libqemu-aarch64_be-linux-user.fa.p/fpu_softfloat.c.o libqemu-aarch64_be-linux-user.fa.p/accel_accel-common.c.o libqemu-aarch64_be-linux-user.fa.p/accel_tcg_tcg-all.c.o libqemu-aarch64_be-linux-user.fa.p/accel_tcg_cpu-exec-common.c.o libqemu-aarch64_be-linux-user.fa.p/accel_tcg_cpu-exec.c.o libqemu-aarch64_be-linux-user.fa.p/accel_tcg_tcg-runtime-gvec.c.o libqemu-aarch64_be-linux-user.fa.p/accel_tcg_tcg-runtime.c.o libqemu-aarch64_be-linux-user.fa.p/accel_tcg_translate-all.c.o libqemu-aarch64_be-linux-user.fa.p/accel_tcg_translator.c.o libqemu-aarch64_be-linux-user.fa.p/accel_tcg_user-exec.c.o libqemu-aarch64_be-linux-user.fa.p/accel_tcg_user-exec-stub.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_elfload.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_exit.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_fd-trans.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_linuxload.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_main.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_mmap.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_signal.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_strace.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_syscall.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_thunk.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_uaccess.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_uname.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_flatload.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_semihost.c.o libqemu-aarch64_be-linux-user.fa.p/meson-generated_.._aarch64_be-linux-user-gdbstub-xml.c.o -Wl,--as-needed -Wl,--no-undefined -pie -Wl,--whole-archive libhwcore.fa libqom.fa -Wl,--no-whole-archive -Wl,--warn-common -Wl,-z,relro -Wl,-z,now -static-pie -fstack-protector-strong -march=armv8-a -O2 -pipe -fstack-protector-strong -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security -fstack-clash-protection -Wp,-D_GLIBCXX_ASSERTIONS -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now -Wl,--start-group libqemuutil.a libhwcore.fa libqom.fa /usr/lib/libz.a -lrt -lutil -lm -pthread -lgthread-2.0 -lglib-2.0 -lpcre -lsysprof-capture-4 -lstdc++ -Wl,--end-group +/usr/bin/ld: /usr/lib/gcc/aarch64-unknown-linux-gnu/12.1.0/../../../../lib/libglib-2.0.a(gutils.c.o): in function `g_get_user_database_entry': +gutils.c:(.text+0x324): warning: Using 'getpwuid' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking +/usr/bin/ld: gutils.c:(.text+0xf4): warning: Using 'getpwnam_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking +/usr/bin/ld: gutils.c:(.text+0xe0): warning: Using 'getpwuid_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking +/usr/lib/gcc/aarch64-unknown-linux-gnu/12.1.0/../../../../lib/libc.a(init-first.o): in function `__libc_init_first': +(.text+0x10): relocation truncated to fit: R_AARCH64_LD64_GOTPAGE_LO15 against symbol `__environ' defined in .bss section in /usr/lib/gcc/aarch64-unknown-linux-gnu/12.1.0/../../../../lib/libc.a(environ.o) +/usr/bin/ld: (.text+0x10): warning: too many GOT entries for -fpic, please recompile with -fPIC +collect2: error: ld returned 1 exit status +ninja: build stopped: subcommand failed. +make: *** [Makefile:163: run-ninja] Error 1 +``` +Same error for both mentioned kernels in different aarch64 hardwares. +Steps to reproduce: +1. Download the tarball from version 7.0.0 +2. Run the configure as mentioned on the above command diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/113 b/gitlab/issues_text/target_missing/host_missing/accel_missing/113 new file mode 100644 index 000000000..516a4e0ca --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/113 @@ -0,0 +1 @@ +missing manpage for bridge.conf diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1134 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1134 new file mode 100644 index 000000000..e24cc8aa1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1134 @@ -0,0 +1,3 @@ +Make ivshmem more generic not only a PCI device +Additional information: +It will also benefit from making it more portable, see https://gitlab.com/qemu-project/qemu/-/issues/666 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1138 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1138 new file mode 100644 index 000000000..ff7c5c3b9 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1138 @@ -0,0 +1 @@ +Not able to get KVM in qemu-system-s390x built from 6.2.0 source on Fedora 31 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1139 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1139 new file mode 100644 index 000000000..09b4e7c5b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1139 @@ -0,0 +1,78 @@ +block/nbd.c and drive backup to a remote nbd server +Description of problem: +Good afternoon! + +I trying to copy attached drive content to remote NBD server via drive-backup QMP method. I'he tested two very similar ways but with very different performance. First is a backuping to exported NBD at another server. Second way is a backuping to same server but with connecting to /dev/nbd*. + +Exporting qcow2 via nbd: +``` +(nbd) ~ # qemu-nbd -p 12345 -x backup --cache=none --aio=native --persistent -f qcow2 backup.qcow2 + +(qemu) ~ # qemu-img info nbd://10.0.0.1:12345/backup +image: nbd://10.0.0.1:12345/backup +file format: raw +virtual size: 10 GiB (10737418240 bytes) +disk size: unavailable +``` + +Starting drive backuping via QMP: + +``` +{ + "execute": "drive-backup", + "arguments": { + "device": "disk", + "sync": "full", + "target": "nbd://10.0.0.1:12345/backup", + "mode": "existing" + } +} +``` + +With process starting qemu notifying about warning: + +> warning: The target block device doesn't provide information about the block size and it doesn't have a backing file. The default block size of 65536 bytes is used. If the actual block size of the target exceeds this default, the backup may be unusable + +And backup process is limited by speed around 30MBps, watched by iotop + + +Second way to creating backup + +Exporting qcow2 via nbd: +``` +(nbd) ~ # qemu-nbd -p 12345 -x backup --cache=none --aio=native --persistent -f qcow2 backup.qcow2 +``` + +``` +(qemu) ~ # qemu-img info nbd://10.0.0.1:12345/backup +image: nbd://10.0.0.1:12345/backup +file format: raw +virtual size: 10 GiB (10737418240 bytes) +disk size: unavailable +(qemu) ~ # qemu-nbd -c /dev/nbd0 nbd://10.0.0.1:12345/backup +(qemu) ~ # qemu-img info /dev/nbd0 +image: /dev/nbd0 +file format: raw +virtual size: 10 GiB (10737418240 bytes) +disk size: 0 B +``` + +Starting drive backuping via QMP to local nbd device: + +``` +{ + "execute": "drive-backup", + "arguments": { + "device": "disk", + "sync": "full", + "target": "/dev/nbd0", + "mode": "existing" + } +} +``` + +Backup process started without previous warning, and speed limited around 100MBps (network limit) + +So I have question: how I can get same performance without connection network device to local block nbd device at the qemu host? + +Kind regards diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/114 b/gitlab/issues_text/target_missing/host_missing/accel_missing/114 new file mode 100644 index 000000000..5d5f6f1d3 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/114 @@ -0,0 +1 @@ +the help message of the set_password subcommand of the qemu monitor isn't usable diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1140 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1140 new file mode 100644 index 000000000..eaa00ccc1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1140 @@ -0,0 +1 @@ +High CPU usage on AMD after migrating guests diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1142 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1142 new file mode 100644 index 000000000..a4b690029 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1142 @@ -0,0 +1,46 @@ +Measurements fail with direct kernel boot for AMD SEV confidential virtualization with 7.1 machine type +Description of problem: +When booting the QEMU with the 'kernel-hashes:true' property set for 'sev-guest' confidential virtualization, the contents of the `-kernel` file are measured by the firmware. + +A remote tenant can then validate the measurement against its expected contents to see if the boot was trustworthy. + +With the pc-q35-7.1 machine type the measurement always fails to validate against expected state. + +Making the following code change + +``` +diff --git a/hw/i386/pc.c b/hw/i386/pc.c +index 7280c02ce3..3a4bf5cba3 100644 +--- a/hw/i386/pc.c ++++ b/hw/i386/pc.c +@@ -1899,6 +1899,8 @@ static void pc_machine_class_init(ObjectClass *oc, void *data) + pcmc->rsdp_in_ram = true; + pcmc->smbios_defaults = true; + pcmc->smbios_uuid_encoded = true; ++ pcmc->legacy_no_rng_seed = true; ++ + pcmc->gigabyte_align = true; + pcmc->has_reserved_memory = true; + pcmc->kvmclock_enabled = true; +``` + +results in successfully validating the measurement. + +THis is not surprising, the RNG seed patch introduced in + +``` +commit 67f7e426e53833a5db75b0d813e8d537b8a75bd2 +Author: Jason A. Donenfeld <Jason@zx2c4.com> +Date: Thu Jul 21 14:56:36 2022 +0200 + + hw/i386: pass RNG seed via setup_data entry +``` + +intentionally modifies the contents of the kernel image before passing it to the firmware, to inject a random seed. This will ensure the boot measuremnts are different every time. + +This RNG seed functionality must NOT be used when AMD SEV is active. +Steps to reproduce: +1. Create an AMD SEV guest with kernel-hashes=true and pc-q35-7.1 machine type +2. Attempt to validate the boot measurement +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1144 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1144 new file mode 100644 index 000000000..d1efc6313 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1144 @@ -0,0 +1,13 @@ +Cannot install on ArcoLinux +Description of problem: +I tried to install with my package manager +``` +paru -S qemu-git +``` +and got these errors +``` +qemu-git: /usr/share/qemu/bios-microvm.bin exists in filesystem (owned by seabios) +qemu-git: /usr/share/qemu/vgabios-ati.bin exists in filesystem (owned by seabios) +``` + +I tried searching around for a solution but I can't seem to find anything relevant to my situation. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1148 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1148 new file mode 100644 index 000000000..936dea8e5 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1148 @@ -0,0 +1,271 @@ +Support Octal SPI mode and commands for NOR SPI devices +Additional information: +A good example of the Octal SPI (OPI) protocol use is in https://www.st.com/resource/en/application_note/dm00407776-octospi-interface-on-stm32-microcontrollers-stmicroelectronics.pdf + +It is also supported by the concrete drivers in Linux kernel: +- `drivers/mtd/spi-nor/core.c` +- `drivers/mtd/spi-nor/micron-st.c` +- `drivers/mtd/spi-nor/spansion.c` + +I tried to extract the Octal SPI part from that commit and got something like this, though obviously needs more cleaning up/improving: +```patch +--- + hw/block/m25p80.c | 93 ++++++++++++++++++++++++++++++++++------------- + 1 file changed, 68 insertions(+), 25 deletions(-) + +diff --git a/hw/block/m25p80.c b/hw/block/m25p80.c +index 7d3d8b12e0..0aa46bf280 100644 +--- a/hw/block/m25p80.c ++++ b/hw/block/m25p80.c +@@ -361,6 +361,8 @@ typedef enum { + READ4 = 0x13, + FAST_READ = 0x0b, + FAST_READ4 = 0x0c, ++ O_FAST_READ = 0x9d, ++ O_FAST_READ4 = 0xfc, + DOR = 0x3b, + DOR4 = 0x3c, + QOR = 0x6b, +@@ -369,6 +371,11 @@ typedef enum { + DIOR4 = 0xbc, + QIOR = 0xeb, + QIOR4 = 0xec, ++ OOR = 0x8b, ++ OOR4 = 0x8c, ++ OOR4_MT35X = 0x7c, /* according mt35x datasheet */ ++ OIOR = 0xcb, ++ OIOR4 = 0xcc, + + PP = 0x02, + PP4 = 0x12, +@@ -379,6 +386,8 @@ typedef enum { + RDID_90 = 0x90, + RDID_AB = 0xab, + AAI_WP = 0xad, ++ OPP = 0x82, ++ OPP4 = 0x84, + + ERASE_4K = 0x20, + ERASE4_4K = 0x21, +@@ -422,6 +431,7 @@ typedef enum { + STATE_COLLECTING_DATA, + STATE_COLLECTING_VAR_LEN_DATA, + STATE_READING_DATA, ++ DUMMY_CYCLE_WAIT, + } CMDState; + + typedef enum { +@@ -654,12 +664,16 @@ static inline int get_addr_length(Flash *s) + case QPP_4: + case READ4: + case QIOR4: ++ case OIOR4: + case ERASE4_4K: + case ERASE4_32K: + case ERASE4_SECTOR: + case FAST_READ4: ++ case O_FAST_READ4: + case DOR4: + case QOR4: ++ case OOR4: ++ case OOR4_MT35X: + case DIOR4: + return 4; + default: +@@ -670,6 +684,7 @@ static inline int get_addr_length(Flash *s) + static void complete_collecting_data(Flash *s) + { + int i, n; ++ bool dummy_state = false; + + n = get_addr_length(s); + s->cur_addr = (n == 3 ? s->ear : 0); +@@ -689,9 +704,12 @@ static void complete_collecting_data(Flash *s) + case DPP: + case QPP: + case QPP_4: ++ case OPP: + case PP: ++ s->state = STATE_PAGE_PROGRAM; ++ break; ++ case OPP4: + case PP4: +- case PP4_4: + s->state = STATE_PAGE_PROGRAM; + break; + case AAI_WP: +@@ -702,16 +720,27 @@ static void complete_collecting_data(Flash *s) + case READ: + case READ4: + case FAST_READ: +- case FAST_READ4: ++ case O_FAST_READ: + case DOR: +- case DOR4: + case QOR: +- case QOR4: ++ case OOR: + case DIOR: +- case DIOR4: + case QIOR: ++ case OIOR: ++ case FAST_READ4: ++ case O_FAST_READ4: ++ case DOR4: ++ case QOR4: ++ case OOR4: ++ case OOR4_MT35X: ++ case DIOR4: + case QIOR4: +- s->state = STATE_READ; ++ case OIOR4: ++ if (dummy_state == false) { ++ s->state = STATE_READ; ++ } else { ++ s->state = DUMMY_CYCLE_WAIT; ++ } + break; + case ERASE_4K: + case ERASE4_4K: +@@ -744,7 +773,6 @@ static void complete_collecting_data(Flash *s) + s->write_enable = false; + } + break; +- case BRWR: + case EXTEND_ADDR_WRITE: + s->ear = s->data[0]; + break; +@@ -1038,6 +1066,7 @@ static void decode_qio_read_cmd(Flash *s) + s->needed_bytes += 3; + break; + default: ++ s->needed_bytes += 5; + break; + } + s->pos = 0; +@@ -1066,28 +1095,39 @@ static void decode_new_cmd(Flash *s, uint32_t value) + "M25P80: Invalid cmd within AAI programming sequence"); + } + ++ s->needed_bytes = 0; ++ + switch (value) { + ++ case ERASE4_SECTOR: ++ if (s->four_bytes_address_mode == false) { ++ s->needed_bytes += 1; ++ } + case ERASE_4K: +- case ERASE4_4K: + case ERASE_32K: +- case ERASE4_32K: + case ERASE_SECTOR: +- case ERASE4_SECTOR: ++ case OPP: + case PP: +- case PP4: ++ case QOR: ++ case OOR: ++ case FAST_READ: ++ case O_FAST_READ: ++ case DOR: + case DIE_ERASE: + case RDID_90: + case RDID_AB: +- s->needed_bytes = get_addr_length(s); ++ s->needed_bytes += get_addr_length(s); + s->pos = 0; + s->len = 0; + s->state = STATE_COLLECTING_DATA; + break; +- case READ: + case READ4: ++ if (s->four_bytes_address_mode == false) { ++ s->needed_bytes += 1; ++ } ++ case READ: + if (get_man(s) != MAN_NUMONYX || numonyx_mode(s) == MODE_STD) { +- s->needed_bytes = get_addr_length(s); ++ s->needed_bytes += get_addr_length(s); + s->pos = 0; + s->len = 0; + s->state = STATE_COLLECTING_DATA; +@@ -1098,7 +1138,7 @@ static void decode_new_cmd(Flash *s, uint32_t value) + break; + case DPP: + if (get_man(s) != MAN_NUMONYX || numonyx_mode(s) != MODE_QIO) { +- s->needed_bytes = get_addr_length(s); ++ s->needed_bytes += get_addr_length(s); + s->pos = 0; + s->len = 0; + s->state = STATE_COLLECTING_DATA; +@@ -1110,8 +1150,11 @@ static void decode_new_cmd(Flash *s, uint32_t value) + case QPP: + case QPP_4: + case PP4_4: ++ if (s->four_bytes_address_mode == false) { ++ s->needed_bytes += 1; ++ } + if (get_man(s) != MAN_NUMONYX || numonyx_mode(s) != MODE_DIO) { +- s->needed_bytes = get_addr_length(s); ++ s->needed_bytes += get_addr_length(s); + s->pos = 0; + s->len = 0; + s->state = STATE_COLLECTING_DATA; +@@ -1121,11 +1164,9 @@ static void decode_new_cmd(Flash *s, uint32_t value) + } + break; + +- case FAST_READ: + case FAST_READ4: + decode_fast_read_cmd(s); + break; +- case DOR: + case DOR4: + if (get_man(s) != MAN_NUMONYX || numonyx_mode(s) != MODE_QIO) { + decode_fast_read_cmd(s); +@@ -1134,14 +1175,13 @@ static void decode_new_cmd(Flash *s, uint32_t value) + "QIO mode\n", s->cmd_in_progress); + } + break; +- case QOR: + case QOR4: +- if (get_man(s) != MAN_NUMONYX || numonyx_mode(s) != MODE_DIO) { +- decode_fast_read_cmd(s); +- } else { +- qemu_log_mask(LOG_GUEST_ERROR, "M25P80: Cannot execute cmd %x in " +- "DIO mode\n", s->cmd_in_progress); +- } ++ case OOR4: ++ case OOR4_MT35X: ++ s->needed_bytes += 4; ++ s->pos = 0; ++ s->len = 0; ++ s->state = STATE_COLLECTING_DATA; + break; + + case DIOR: +@@ -1265,6 +1305,7 @@ static void decode_new_cmd(Flash *s, uint32_t value) + s->four_bytes_address_mode = false; + break; + case BRRD: ++ s->data_read_loop = false; + case EXTEND_ADDR_READ: + s->data[0] = s->ear; + s->pos = 0; +@@ -1475,6 +1516,8 @@ static uint32_t m25p80_transfer8(SSIPeripheral *ss, uint32_t tx) + } + break; + ++ case DUMMY_CYCLE_WAIT: ++ break; + default: + case STATE_IDLE: + decode_new_cmd(s, (uint8_t)tx); +-- +``` +There is also missing **0xfd** command for the DDR Octal I/O Fast Read for Micron MT35X chips. I am not sure if it's the same as the **0xfc** command in the Xilinx code though. + +Since I am not the author of the original commit, maybe Xilinx folks could take my patch, update/improve it and send to the mailing list. It will reduce the amount of the changes you have to apply in your fork as well :smile: + +cc @alistair23 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1149 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1149 new file mode 100644 index 000000000..6f71d610e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1149 @@ -0,0 +1,9 @@ +Micron Xccela (MT35x) NOR Flash wrong implementation in `hw/block/m25p80.c` +Additional information: +I see that in the fork they introduced a new entry - `MAN_MICRON_OCTAL`: - https://github.com/Xilinx/qemu/blob/master/hw/block/m25p80.c + +Would be nice to make it more generic, probably to call just `MAN_MICRON` and set octal mode like quad mode in other flash implementations - via the configuration register flags, especially since they could be enabled and disabled on the fly. + +Also the 256 configuration registers: https://github.com/Xilinx/qemu/commit/9b2fe1e36bfd8849bb3538161279cdff6efea325 + +cc @alistair23 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1150 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1150 new file mode 100644 index 000000000..3fa3ef7c8 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1150 @@ -0,0 +1,84 @@ +guest Linux Kernel hangs and reports CPU lockup/stuck (Qemu >= 6.0.1 regression) +Description of problem: +Since at least [qemu-6.0.1](https://download.qemu.org/qemu-6.0.1.tar.xz) my VM guest is having CPU problems. It looks like [qemu-6.0.0](https://download.qemu.org/qemu-6.0.0.tar.xz) is fine, but I can't confirm this 100 %. + +Problem: The guest hangs for about 30 seconds and dmesg reports errors. + +<details> +<summary>dmesg</summary> + +``` +[ 310.791732] watchdog: BUG: soft lockup - CPU#1 stuck for 25s! [swapper/1:0] +[ 310.791753] Modules linked in: ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_state xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c iptable_filter bpfilter af_packet iscsi_ibft iscsi_boot_sysfs rfkill dm_crypt essiv authenc pktcdvd intel_rapl_msr intel_rapl_common kvm_intel kvm cirrus drm_kms_helper irqbypass cec pcspkr joydev rc_core syscopyarea sysfillrect sysimgblt virtio_balloon fb_sys_fops i2c_piix4 button nls_iso8859_1 nls_cp437 vfat fat drm fuse configfs ip_tables x_tables ext4 crc16 mbcache jbd2 hid_generic usbhid sd_mod t10_pi virtio_scsi virtio_net net_failover virtio_blk failover sr_mod cdrom ata_generic crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd xhci_pci xhci_pci_renesas xhci_hcd cryptd serio_raw ehci_pci uhci_hcd ehci_hcd usbcore ata_piix ahci libahci virtio_pci virtio_pci_modern_dev libata floppy qemu_fw_cfg dm_mirror dm_region_hash dm_log dm_mod sg scsi_mod +[ 310.792102] Supported: Yes +[ 310.792108] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.14.21-150400.22-default #1 SLE15-SP4 0b6a6578ade2de5c4a0b916095dff44f76ef1704 +[ 310.792121] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014 +[ 310.792127] RIP: 0010:__do_softirq+0x6e/0x2bc +[ 310.792146] Code: 8b 70 2c 81 60 2c ff f7 ff ff 89 74 24 14 c7 44 24 10 0a 00 00 00 48 c7 c0 c0 30 03 00 65 66 c7 00 00 00 fb 66 0f 1f 44 00 00 <bb> ff ff ff ff 41 0f bc de 83 c3 01 89 1c 24 0f 84 92 00 00 00 49 +[ 310.792154] RSP: 0018:ffffb9a8c00d0f98 EFLAGS: 00000206 +[ 310.792163] RAX: 00000000000330c0 RBX: ffffb9a8c0093e18 RCX: 0000000034b47837 +[ 310.792169] RDX: ffff9835c02dd100 RSI: 0000000004200042 RDI: 0000000000000040 +[ 310.792175] RBP: 0000000000000022 R08: ffffb9a8c0093e18 R09: 0000000000000001 +[ 310.792180] R10: 0000000000000002 R11: 0000000000000283 R12: 0000000000000001 +[ 310.792185] R13: 0000000000000000 R14: 0000000000000040 R15: 0000000000000000 +[ 310.792191] FS: 0000000000000000(0000) GS:ffff9836f7d00000(0000) knlGS:0000000000000000 +[ 310.792197] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 +[ 310.792203] CR2: 000055ed8cffbaf8 CR3: 00000001025c0001 CR4: 0000000000170ee0 +[ 310.792216] Call Trace: +[ 310.792247] <IRQ> +[ 310.792284] irq_exit_rcu+0x9c/0xc0 +[ 310.792305] common_interrupt+0x5d/0xa0 +[ 310.792331] </IRQ> +[ 310.792335] <TASK> +[ 310.792339] asm_common_interrupt+0x1e/0x40 +[ 310.792358] RIP: 0010:native_safe_halt+0xb/0x10 +[ 310.792368] Code: f0 80 48 02 20 48 8b 00 a8 08 74 82 eb c1 cc eb 07 0f 00 2d 89 f3 5f 00 f4 c3 0f 1f 44 00 00 eb 07 0f 00 2d 79 f3 5f 00 fb f4 <c3> cc cc cc cc 0f 1f 44 00 00 65 8b 15 14 ee 60 69 0f 1f 44 00 00 +[ 310.792375] RSP: 0018:ffffb9a8c0093ec8 EFLAGS: 00000212 +[ 310.792382] RAX: ffffffff96a0ca50 RBX: 0000000000000001 RCX: ffff9835c49c3700 +[ 310.792387] RDX: 00000000001df31e RSI: 0000000000000000 RDI: ffff9835c02a8000 +[ 310.792392] RBP: ffffffff97d47120 R08: 00000000001df31e R09: 0000000000029800 +[ 310.792397] R10: ffffb9a8c164bbe0 R11: 0000000000000198 R12: 0000000000000000 +[ 310.792402] R13: 0000000000000000 R14: ffffffffffffffff R15: ffff9835c02a8000 +[ 310.792409] ? __sched_text_end+0x5/0x5 +[ 310.792425] default_idle+0xa/0x10 +[ 310.792434] default_idle_call+0x2d/0xe0 +[ 310.792441] do_idle+0x1ec/0x2d0 +[ 310.792452] cpu_startup_entry+0x19/0x20 +[ 310.792460] start_secondary+0x11c/0x160 +[ 310.792475] secondary_startup_64_no_verify+0xc2/0xcb +[ 310.792501] </TASK> +``` + +``` +[ 435.511342] BUG: workqueue lockup - pool cpus=1 node=0 flags=0x0 nice=0 stuck for 30s! +[ 435.511374] Showing busy workqueues and worker pools: +[ 435.511377] workqueue events: flags=0x0 +[ 435.511380] pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=1/256 refcnt=2 +[ 435.511385] pending: vmstat_shepherd +[ 435.511395] workqueue events_power_efficient: flags=0x80 +[ 435.511398] pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=2/256 refcnt=3 +[ 435.511402] pending: neigh_periodic_work, neigh_periodic_work +[ 435.511411] workqueue events_freezable_power_: flags=0x84 +[ 435.511414] pwq 2: cpus=1 node=0 flags=0x0 nice=0 active=1/256 refcnt=2 +[ 435.511417] in-flight: 4783:disk_events_workfn +[ 435.511425] workqueue mm_percpu_wq: flags=0x8 +[ 435.511428] pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=1/256 refcnt=2 +[ 435.511431] pending: vmstat_update +[ 435.511440] workqueue writeback: flags=0x4a +[ 435.511443] pwq 4: cpus=0-1 flags=0x4 nice=0 active=1/256 refcnt=3 +[ 435.511447] pending: wb_workfn +[ 435.511453] workqueue kblockd: flags=0x18 +[ 435.511455] pwq 3: cpus=1 node=0 flags=0x0 nice=-20 active=3/256 refcnt=4 +[ 435.511459] pending: blk_mq_timeout_work, blk_mq_timeout_work, blk_mq_timeout_work +[ 435.511475] workqueue ata_sff: flags=0x8 +[ 435.511479] pwq 2: cpus=1 node=0 flags=0x0 nice=0 active=1/512 refcnt=2 +[ 435.511482] pending: ata_sff_pio_task [libata] +[ 435.511538] pool 2: cpus=1 node=0 flags=0x0 nice=0 hung=30s workers=3 idle: 349 51 +``` + +</details> + +It looks like the problem mostly appears if SSH is being used over a "user" network connection. A typical situation is when editing a file in Vim (compiled with X support) via SSH and using the X clipboard (`"+y"`). But the problem also happens in other situations with SSH, e. g. when using SSHFS. +The type of NIC doesn't seem to make a difference (tested `virtio` and `e1000`). But "tap" network connections don't show a problem. + + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1156 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1156 new file mode 100644 index 000000000..8937c8c1e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1156 @@ -0,0 +1 @@ +Incorrect implementation of vmsumudm instruction diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1157 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1157 new file mode 100644 index 000000000..ba2be02ad --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1157 @@ -0,0 +1,13 @@ +aarch64: enabling MMU causes instruction abort +Description of problem: +The title describes the problem pretty accurately, we get an instruction abort when enabling the MMU with a pretty simple set of page tables. This has been regressed from qemu 6.x. +Steps to reproduce: +1. Run the provided Kernel binary with the command line specified above. +2. Notice the hang after 'Initialize MMU'. I traced it down to being an instructions abort after the write to the SCTLR_EL1 register. +3. Try to run with qemu 6.x, and notice that it works. +Additional information: +This does work on actual hardware, so it has to be a qemu bug. + +A binary of the Serenity Kernel has been attached to the issue. The source of that binary can be found at commit ca0e32e59fcf67a662e5d3a994d44cd7c941624a of [SerenityOS](https://github.com/SerenityOS/serenity). + +[Kernel](/uploads/f731edbf81d8e575035e9693b0a51dbf/Kernel) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1158 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1158 new file mode 100644 index 000000000..fe02e26bf --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1158 @@ -0,0 +1 @@ +Error in setting VNC password diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1159 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1159 new file mode 100644 index 000000000..6275e1d5c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1159 @@ -0,0 +1,32 @@ +Strange invalid access errors for very basic OS +Description of problem: +Currently I'm studying OS development. I found numerous guides on that topic, however [this one](https://github.com/cfenollosa/os-tutorial/tree/master/01-bootsector-barebones) is most close to what I have been doing. +When `.bin` file is launched with `-d guest_errors` flag, before any OS output exactly 512 error messages appear in logs, that look like that: +``` +Invalid access at addr 0xFEBB0000, size 1, region '(null)', reason: rejected +Invalid access at addr 0x0, size 1, region '(null)', reason: rejected +Invalid access at addr 0xFEBB0001, size 1, region '(null)', reason: rejected +Invalid access at addr 0x1, size 1, region '(null)', reason: rejected +Invalid access at addr 0xFEBB0002, size 1, region '(null)', reason: rejected +... +and it goes up to +... +Invalid access at addr 0xFEBB00FE, size 1, region '(null)', reason: rejected +Invalid access at addr 0xFE, size 1, region '(null)', reason: rejected +Invalid access at addr 0xFEBB00FF, size 1, region '(null)', reason: rejected +Invalid access at addr 0xFF, size 1, region '(null)', reason: rejected +``` +Apparently, the OS boots normally after that. Should I be concerned about these messages or Should I just ignore them? +That looks strange and confusing, not a piece of my code calls these addresses. Maybe I'm doing something wrong? +Steps to reproduce: +1. Install `nasm` compiler (nasm package for apt) +2. Create a file named `os.asm` with exactly four lines: +```asm +loop: + jmp loop +times 510-($-$$) db 0 +dw 0xaa55 +``` +3. Build it with `nasm -f bin os.asm -o os.bin` +4. Run it with `qemu-system-i386 -d guest_errors -drive format=raw,file=./os.bin` +5. ...enjoy error messages. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1161 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1161 new file mode 100644 index 000000000..f780b76f7 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1161 @@ -0,0 +1 @@ +revise docs/interop/virtio-balloon-stats.rst diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1162 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1162 new file mode 100644 index 000000000..a895e5756 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1162 @@ -0,0 +1,12 @@ +`./configure` gives `big/little test failed` error when attempting to statically link on Fedora 36 +Description of problem: +I'm having trouble attempting to build the QEMU System emulator statically linked. The error `./configure` gives `big/little test failed` with nothing else. I couldn't find any information relating to this. I'm not sure where to start fixing this. If anyone can help me with this, thanks! +Steps to reproduce: +1. `git clone https://gitlab.com/qemu-project/qemu.git` +2. `cd qemu` +3. `git submodule init` +4. `git submodule update` +5. `./configure --enable-kvm --enable-vnc --enable-vhost-net --enable-avx2 --enable-avx512f --target-list=x86_64-softmmu --static` +6. Observe build error +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1165 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1165 new file mode 100644 index 000000000..639feea50 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1165 @@ -0,0 +1,3 @@ +About support LoongArch architecture +Additional information: +Start from Linux 5.19, maybe can find the compatible source code for LoongArch in the Linux Kernel source code archive. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1169 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1169 new file mode 100644 index 000000000..af6a093a6 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1169 @@ -0,0 +1,3 @@ +rename snapshot by qemu-img +Additional information: +I have no idea to rename a snapshot which created by `qemu-img snapshot -c`, I think it is a useful function diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/117 b/gitlab/issues_text/target_missing/host_missing/accel_missing/117 new file mode 100644 index 000000000..29bca8631 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/117 @@ -0,0 +1 @@ +nested 9p filesystem with security_model=mapped-xattr diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1170 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1170 new file mode 100644 index 000000000..ba43d33dd --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1170 @@ -0,0 +1,56 @@ +Unable to compile in Ubuntu 22.04, at compiling linux-user_arm_nwfpe_double_cpdo.c.o +Description of problem: +Compiling of QEMU 7.1.0-rc3 stops here for me: +``` +[7172/9855] Compiling C object libqemu-armeb-linux-user.fa.p/linux-user_arm_nwfpe_double_cpdo.c.o +FAILED: libqemu-armeb-linux-user.fa.p/linux-user_arm_nwfpe_double_cpdo.c.o +cc -m64 -mcx16 -Ilibqemu-armeb-linux-user.fa.p -I. -I.. -Itarget/arm -I../target/arm -I../common-user/host/x86_64 -I../linux-user/include/host/x86_64 -I../linux-user/include -Ilinux-user -I../linux-user -Ilinux-user/arm -I../linux-user/arm -Iqapi -Itrace -Iui -Iui/shader -I/usr/include/capstone -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -fdiagnostics-color=auto -Wall -Winvalid-pch -std=gnu11 -O2 -g -isystem /home/andrea/Downloads/qemu-7.1.0-rc3/linux-headers -isystem linux-headers -iquote . -iquote /home/andrea/Downloads/qemu-7.1.0-rc3 -iquote /home/andrea/Downloads/qemu-7.1.0-rc3/include -iquote /home/andrea/Downloads/qemu-7.1.0-rc3/tcg/i386 -pthread -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fno-common -fwrapv -Wold-style-declaration -Wold-style-definition -Wtype-limits -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body -Wnested-externs -Wendif-labels -Wexpansion-to-defined -Wimplicit-fallthrough=2 -Wno-missing-include-dirs -Wno-shift-negative-value -Wno-psabi -fstack-protector-strong -fPIE -isystem../linux-headers -isystemlinux-headers -DNEED_CPU_H '-DCONFIG_TARGET="armeb-linux-user-config-target.h"' '-DCONFIG_DEVICES="armeb-linux-user-config-devices.h"' -MD -MQ libqemu-armeb-linux-user.fa.p/linux-user_arm_nwfpe_double_cpdo.c.o -MF libqemu-armeb-linux-user.fa.p/linux-user_arm_nwfpe_double_cpdo.c.o.d -o libqemu-armeb-linux-user.fa.p/linux-user_arm_nwfpe_double_cpdo.c.o -c ../linux-user/arm/nwfpe/double_cpdo.c +during RTL pass: expand +../linux-user/arm/nwfpe/double_cpdo.c: In function ‘DoubleCPDO’: +../linux-user/arm/nwfpe/double_cpdo.c:232:1: internal compiler error: Segmentation fault + 232 | } + | ^ +0x7fe5b824251f ??? + ./signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0 +0x7fe5b8229d8f __libc_start_call_main + ../sysdeps/nptl/libc_start_call_main.h:58 +0x7fe5b8229e3f __libc_start_main_impl + ../csu/libc-start.c:392 +Please submit a full bug report, +with preprocessed source if appropriate. +Please include the complete backtrace with any bug report. +See <file:///usr/share/doc/gcc-11/README.Bugs> for instructions. +ninja: build stopped: subcommand failed. +make[1]: *** [Makefile:162: run-ninja] Error 1 +make[1]: Leaving directory '/home/andrea/Downloads/qemu-7.1.0-rc3/build' +make: *** [GNUmakefile:11: all] Error 2 +``` + +Configure Output: +[Configure_Output.txt](/uploads/40055846573b79cc2817d5cb338e18c1/Configure_Output.txt) + +Compiles on 7.0.0. +Steps to reproduce: +1. Run 'sudo apt purge qemu-kvm qemu-utils libvirt-daemon-system libvirt-clients bridge-utils virt-manager ovmf' +2. Run 'sudo apt-get install git libglib2.0-dev libfdt-dev libpixman-1-dev zlib1g-dev ninja-build' ([Wiki](https://wiki.qemu.org/Hosts/Linux)) +3. Additional Packages: +``` +sudo apt-get install git-email +sudo apt-get install libaio-dev libbluetooth-dev libcapstone-dev libbrlapi-dev libbz2-dev +sudo apt-get install libcap-ng-dev libcurl4-gnutls-dev libgtk-3-dev +sudo apt-get install libibverbs-dev libjpeg8-dev libncurses5-dev libnuma-dev +sudo apt-get install librbd-dev librdmacm-dev +sudo apt-get install libsasl2-dev libsdl2-dev libseccomp-dev libsnappy-dev libssh-dev +sudo apt-get install libvde-dev libvdeplug-dev libvte-2.91-dev libxen-dev liblzo2-dev +sudo apt-get install valgrind xfslibs-dev + +sudo apt-get install libnfs-dev libiscsi-dev +``` +4. Build instructions for QEMU: +``` +wget https://download.qemu.org/qemu-7.1.0-rc3.tar.xz +tar xvJf qemu-7.1.0-rc3.tar.xz +cd qemu-7.1.0-rc3 +./configure +make +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1171 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1171 new file mode 100644 index 000000000..65d6dc5fa --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1171 @@ -0,0 +1,3 @@ +tulip: DMA reentrancy issue leads to stack overflow (CVE-2022-2962) +Description of problem: +A DMA reentrancy issue was found in the tulip emulation. When tulip reads or writes to rx/tx descriptor ( tulip_desc_read/write ) or copies rx/tx frame(tulip_copy_rx_bytes / tulip_copy_tx_buffers), it doesn't check whether the destination address is its own MMIO address. A malicious guest could use this flaw to crash the QEMU process on the host, resulting in a denial of service condition or, potentially, executing arbitrary code within the context of the QEMU process on the host. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1172 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1172 new file mode 100644 index 000000000..0d241fafd --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1172 @@ -0,0 +1,59 @@ +Make pixman an optional dependency +Additional information: +Only these files use pixman functions (excluding tests, of course): +``` +meson.build +contrib/vhost-user-gpu/vhost-user-gpu.c +contrib/vhost-user-gpu/meson.build +chardev/meson.build +include/ui/spice-display.h +include/ui/sdl2.h +include/ui/gtk.h +include/ui/qemu-pixman.h +include/ui/console.h +include/hw/display/xlnx_dp.h +include/hw/virtio/virtio-gpu.h +include/hw/virtio/virtio-gpu-pixman.h +hw/display/vga.c +hw/display/ramfb.c +hw/display/vhost-user-gpu.c +hw/display/virtio-gpu-gl.c +hw/display/virtio-gpu-udmabuf.c +hw/display/xenfb.c +hw/display/ati_2d.c +hw/display/meson.build +hw/display/vmware_vga.c +hw/display/qxl-render.c +hw/display/xlnx_dp.c +hw/display/bochs-display.c +hw/display/sm501.c +hw/display/virtio-gpu.c +hw/vfio/display.c +hw/s390x/meson.build +ui/cocoa.m +ui/console-gl.c +ui/vnc.c +ui/qemu-pixman.c +ui/gtk.c +ui/console.c +ui/trace-events +ui/meson.build +ui/dbus-listener.c +ui/vnc-enc-tight.c +ui/vnc.h +ui/spice-display.c +ui/dbus-display1.xml +ui/sdl2-2d.c +``` + +This code in `meson.build` always require **pixman** for building system emulators: +```meson +pixman = not_found +if have_system or have_tools + pixman = dependency('pixman-1', required: have_system, version:'>=0.21.8', + method: 'pkg-config', kwargs: static_kwargs) +endif +``` +https://gitlab.com/qemu-project/qemu/-/blob/master/meson.build#L520 + +Most of the code could work without it. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1175 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1175 new file mode 100644 index 000000000..6f70a9e55 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1175 @@ -0,0 +1,8 @@ +Crash / Assert in VVFAT.c while installaling WinXP from QEMU 7.0 running in Raspberry OS +Description of problem: +- Windows XP installation crashes QEMU with : +qemu-system-i386: ../block/vvfat.c:103: array_get: Assertion `index < array->next' failed. +Steps to reproduce: +Use command line above and run WindowsXP installation +Additional information: +Execution also leads to many "Invalid file name" being reported by QEMU diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1176 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1176 new file mode 100644 index 000000000..faa57b62c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1176 @@ -0,0 +1,7 @@ +VVFAT :rw writes from guest (ReactOS, windowsXP) not visible by host +Description of problem: +As described in https://jira.reactos.org/browse/CORE-18327 +While ./LMS is mounted as a :rw VVFAT drive, guest OS (ReactOS) is able to read files BUT when files are "written" from the guest, they are not visible on host side. +QEMU execution is also massively polluted by "invalid file name" messages coming from https://git.qemu.org/?p=qemu.git;a=blob_plain;f=block/vvfat.c;hb=HEAD (but this is not specific to the use with ReactOS, as this is also observed with other guest : WXP, ...) + +See attached screenshot showing WXPSP3 as guest with file created in VVFAT drive while guest misses the newly created file. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1179 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1179 new file mode 100644 index 000000000..8375ca844 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1179 @@ -0,0 +1,65 @@ +qemu-img snapshot would break win8.1's system disk data +Description of problem: +`qemu-img snapshot` will cause a damage on windows 8.1 virtual machine +Steps to reproduce: +1.shutdown the virtual machine + +2.exec command +``` +$ qemu-img snapshot -d standard /media/user/SSD_VM/disk/win8_1.qcow2 +... +ERROR cluster 554329 refcount=0 reference=1 +ERROR cluster 554330 refcount=0 reference=1 +ERROR cluster 554331 refcount=0 reference=1 +ERROR cluster 554332 refcount=0 reference=1 +ERROR cluster 554333 refcount=0 reference=1 +ERROR cluster 554334 refcount=0 reference=1 +ERROR cluster 554335 refcount=0 reference=1 +Leaked cluster 557183 refcount=2 reference=1 +Leaked cluster 557472 refcount=2 reference=1 +Leaked cluster 564785 refcount=2 reference=1 +... +Leaked cluster 580393 refcount=2 reference=1 +Leaked cluster 580434 refcount=2 reference=1 +Leaked cluster 580713 refcount=2 reference=1 +Leaked cluster 580718 refcount=2 reference=1 +Leaked cluster 580726 refcount=2 reference=1 +Leaked cluster 580965 refcount=2 reference=1 +Leaked cluster 581268 refcount=2 reference=1 +Leaked cluster 581280 refcount=2 reference=1 +Leaked cluster 581367 refcount=2 reference=1 +Leaked cluster 582743 refcount=2 reference=1 +Leaked cluster 582938 refcount=2 reference=1 +Leaked cluster 583026 refcount=2 reference=1 +Leaked cluster 583027 refcount=2 reference=1 +Leaked cluster 583028 refcount=2 reference=1 +Leaked cluster 583029 refcount=2 reference=1 +Rebuilding refcount structure +Repairing cluster 547917 refcount=1 reference=0 +Repairing cluster 547936 refcount=1 reference=0 +Repairing cluster 547955 refcount=1 reference=0 +Repairing cluster 548069 refcount=1 reference=0 +Repairing cluster 548092 refcount=1 reference=0 +Repairing cluster 548115 refcount=1 reference=0 +Repairing cluster 548125 refcount=1 reference=0 +Repairing cluster 548128 refcount=1 reference=0 +Repairing cluster 548130 refcount=1 reference=0 +Repairing cluster 548144 refcount=1 reference=0 +Repairing cluster 548146 refcount=1 reference=0 +Repairing cluster 548150 refcount=1 reference=0 +Repairing cluster 548199 refcount=1 reference=0 +Repairing cluster 548201 refcount=1 reference=0 +Repairing cluster 548226 refcount=1 reference=0 +Repairing cluster 548234 refcount=1 reference=0 +Repairing cluster 548236 refcount=1 reference=0 +Repairing cluster 557073 refcount=1 reference=0 +Repairing cluster 557074 refcount=1 reference=0 +... + +``` + +3.start the virtual machine , it shows blue screen error: +`UNEXPECTED_STORE_EXCPETION` + +Additional information: +the windows virtual machine will automatically fix the damage that qemu-img caused on next restart . diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/118 b/gitlab/issues_text/target_missing/host_missing/accel_missing/118 new file mode 100644 index 000000000..9f79476a5 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/118 @@ -0,0 +1 @@ +USB device 1.1 not correctly passedthru from Linux host to Windows guest diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1180 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1180 new file mode 100644 index 000000000..6a2961f27 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1180 @@ -0,0 +1,166 @@ +Assertion failure in usb_cancel_packet() +Description of problem: +When I ran hcd-ohci with dev-storage, I found an assertion failure in +usb_cancel_packet() [1] due to p->state == USB_PACKET_COMPLETE. This is due to +the inconsistency when resetting device. + +``` c +static inline bool usb_packet_is_inflight(USBPacket *p) +{ + return (p->state == USB_PACKET_QUEUED || + p->state == USB_PACKET_ASYNC); +} + +void usb_cancel_packet(USBPacket * p) +{ + bool callback = (p->state == USB_PACKET_ASYNC); + assert(usb_packet_is_inflight(p)); // <------------------------------- [1] + usb_packet_set_state(p, USB_PACKET_CANCELED); + QTAILQ_REMOVE(&p->ep->queue, p, queue); + if (callback) { + usb_device_cancel_packet(p->ep->dev, p); + } +} +``` +Steps to reproduce: +Step 1: download the prepared rootfs and the image. + +https://drive.google.com/file/d/1B95zWWcomvZt1wms31Ddc9Xwlq-bfqhq/view?usp=sharing + +https://drive.google.com/file/d/1pxFzn49MKYmMMIIsaL9aUkzebRSYfq3J/view?usp=sharing + +Step 2: run the following script. + +``` bash +QEMU_PATH=../../../qemu/build/qemu-system-x86_64 +KERNEL_PATH=./bzImage +ROOTFS_PATH=./rootfs.ext2 +$QEMU_PATH \ + -M q35 -m 1G \ + -kernel $KERNEL_PATH \ + -drive file=$ROOTFS_PATH,if=virtio,format=raw \ + -append "root=/dev/vda console=ttyS0" \ + -net nic,model=virtio -net user \ + -usb \ + -device pci-ohci,num-ports=6 \ + -drive file=null-co://,if=none,format=raw,id=disk0 \ + -device usb-storage,port=1,drive=disk0 \ + -nographic +``` + +Step 3: with spawned shell (the user is root and the password is empty), run +`ohci-03`. +Additional information: +1 With crafted ED and TD, we can have the ohci->usb_packet's status to be +USB_RET_ASYNC [5]. And thus ohci->async_td is not NULL anymore [2]. + +``` +ed0 = { flags = 0x685f0900, tail = 0x0, head = &td0, next = 0 } + +td0 = { flags = 0x0, cbp = 0x1b8ffc, next = 0, be = 0x1b901a } +# data from cbp to be +55 53 42 43 00 00 00 00 00 00 00 00 00 00 00 03 USBC............ +e8 56 20 40 e8 56 20 40 e8 56 20 40 e8 56 20 + +ed1 = { flags = 0x08303080, tail = 0x0, head = &td1, next = 0 } + +td1 = { flags = 0x90000000, cbp = 0x19affc, next = 0, be = 0x19b01a } +# data from cbp to be +55 53 42 43 00 00 00 00 00 00 00 00 00 00 00 03 USBC............ +e8 56 20 40 e8 56 20 40 e8 56 20 40 e8 56 20 +``` + +``` c +static int ohci_service_td(OHCIState *ohci, struct ohci_ed *ed) +{ + // ... + usb_handle_packet(dev, &ohci->usb_packet); // <------------------- [4] + if (ohci->usb_packet.status == USB_RET_ASYNC) { + usb_device_flush_ep_queue(dev, ep); + ohci->async_td = addr; // <----------------------------------- [2] + return 1; + } +``` + +At the same time, the dev-storage will ref the current usb_packet +(ohci->usb_packet) [4][3]. + +``` +static void usb_msd_handle_data(USBDevice *dev, USBPacket *p) { + // ... + s->packet = p; // <----------------------------------------------- [3] + p->status = USB_RET_ASYNC; // <----------------------------------- [5] + // ... +} +``` + +2 We can first issue `MMIO_WRITE, 0xe0000054, 0x4, 0x4e33b4bf` to reset +the dev-storage device. This will mark the state of ohci->usb_packet to +USB_PACKET_COMPLETE and clear s->packet. + +``` +ohci_mem_write + ohci_port_set_status + usb_device_reset + usb_device_handle_reset + usb_msd_handle_reset + usb_msd_packet_complete + usb_packet_complete +``` + +3 We can then issue `MMIO_WRITE, 0xe0000004, 0x4, 0x3d8d323a` to reset the +roothub and this will invoke ohci_stop_endpoints() where usb_cancel_packet() +is invoked and thus [1] fails as the state of ohci->usb_packet has been changed +to USB_PACKET_COMPLETE. + +``` +ohci_set_ctl + ohci_roothub_reset + ohci_stop_endpoints + if (ohci->async_td != NULL) usb_cancel_packet(&ohci->usb_packet); + assert(usb_packet_is_inflight(p)); // boom +``` + +The above callstack are simplified. The complete callstack is in the following. + +``` +ohci_set_ctl + ohci_roothub_reset + usb_port_reset + usb_detach + ohci_detach + ohci_child_detach // <-------------------------------- [8] + usb_device_reset // <----------------------------------------- [6] + usb_device_handle_reset + usb_msd_handle_reset + usb_msd_packet_complete + usb_packet_complete + ohci_stop_endpoints // <------------------------------------------ [7] + if (ohci->async_td != NULL) usb_cancel_packet(&ohci->usb_packet); + assert(usb_packet_is_inflight(p)); // boom +``` + +Interestingly, in ohci_roothub_reset(), usb_device_reset() is also invoked [6] +just like what in step 2. I adjusted my PoC by removing step 2. However, I +cannot reproduce this assertion failure. Therefore, there is something different +bewteen [6] and step 2. + +Then, I found at [8], ohci_child_detach() cancels the ohci->usb_packet and reset +ohci->async_td. With step 2, as the status of the ohci->usb_packet has changed +to USB_PACKET_COMPLETE, usb_cancel_packet() will not be invoked. Without step 2, +as the status of the ohci->usb_packet is still USB_PACKET_ASYNC, +usb_cancel_packet() will be invoked and thus everything goes fine. + +``` +static void ohci_child_detach(USBPort *port1, USBDevice *dev) +{ + OHCIState *ohci = port1->opaque; + + if (ohci->async_td && + usb_packet_is_inflight(&ohci->usb_packet) && + ohci->usb_packet.ep->dev == dev) { + usb_cancel_packet(&ohci->usb_packet); + ohci->async_td = 0; + } +} +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1181 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1181 new file mode 100644 index 000000000..5fdbf4aa7 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1181 @@ -0,0 +1 @@ +Question for AVR experts... diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1182 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1182 new file mode 100644 index 000000000..8f3a85413 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1182 @@ -0,0 +1,69 @@ +Hotplug device(device_add) immediately after starting a virtual machine triggers deadlock. +Description of problem: +Sometimes, hotplug device(device_add) immediately after starting a virtual machine triggers deadlock. + +Related commits: [7bed8995](https://gitlab.com/qemu-project/qemu/-/commit/7bed89958bfbf40df9ca681cefbdca63abdde39d) +Steps to reproduce: +1. start a virtual machine + +2. hotplug some device immediately(24 virtio-blk device etc.) + +3. repert step 1 and step 2 for several times, as I tried, deadlock will happen within 100 times. +Additional information: +I found similar problem [Issues 650](https://gitlab.com/qemu-project/qemu/-/issues/650)，but problem seems different. + +When qemu_main_loop deal with qmp_device_add command which will add a bottom half structure to qemu_aio_context's bh_list. + +At the same time, UEFI loader writing something to pflash device, address_space_write function get rcu_read_lock and poll aio request. + +Then, it will get the bottom half structure added by qemu_main_loop and go to qmp_device_add function. qmp_device_add function call drain_call_rcu function which will wait for all readers exit. Then it caused a deadlock. + + + +dead lock thread stack + +``` +#0 0x0000ffffb11e8ee4 in syscall () from target:/usr/lib64/libc.so.6 +#1 0x0000aaaadab2ce80 in qemu_futex_wait (val=<optimized out>, f=<optimized out>) at /Images/jdx/code/qemu/include/qemu/futex.h:29 +#2 qemu_event_wait (ev=ev@entry=0xffff87bfd890) at ../util/qemu-thread-posix.c:429 +#3 0x0000aaaadab35ed0 in drain_call_rcu () at ../util/rcu.c:347 +#4 0x0000aaaada55fa94 in qmp_device_add (qdict=<optimized out>, ret_data=<optimized out>, errp=<optimized out>) at ../softmmu/qdev-monitor.c:866 +#5 0x0000aaaadab1f01c in do_qmp_dispatch_bh (opaque=0xffffaf987ec8) at ../qapi/qmp-dispatch.c:128 +#6 0x0000aaaadab3d1b4 in aio_bh_call (bh=0xffff382d8190) at ../util/async.c:150 +#7 aio_bh_poll (ctx=ctx@entry=0xaaaaf8836ac0) at ../util/async.c:178 +#8 0x0000aaaadab29010 in aio_poll (ctx=ctx@entry=0xaaaaf8836ac0, blocking=blocking@entry=true) at ../util/aio-posix.c:712 +#9 0x0000aaaadaa060e8 in bdrv_poll_co (s=0xffff87bfda58) at /Images/jdx/code/qemu/block/block-gen.h:44 +#10 0x0000aaaadaa07134 in blk_pwrite (blk=0xaaaaf8b82400, offset=offset@entry=197120, bytes=bytes@entry=512, buf=0xffff87c30200, flags=flags@entry=0) at block/block-gen.c:685 +#11 0x0000aaaada35c330 in pflash_update (pfl=pfl@entry=0xaaaaf8b474f0, offset=197120, offset@entry=197124, size=size@entry=4) at ../hw/block/pflash_cfi01.c:395 +#12 0x0000aaaada35e1f8 in pflash_write (be=0, width=4, value=299045890, offset=197124, pfl=0xaaaaf8b474f0) at ../hw/block/pflash_cfi01.c:523 +#13 pflash_mem_write_with_attrs (opaque=0xaaaaf8b474f0, addr=197124, value=299045890, len=4, attrs=...) at ../hw/block/pflash_cfi01.c:682 +#14 0x0000aaaada918cbc in access_with_adjusted_size (addr=addr@entry=197124, value=value@entry=0xffff87bfdbf8, size=4, access_size_min=<optimized out>, access_size_max=<optimized out>, + access_fn=access_fn@entry=0xaaaada91b260 <memory_region_write_with_attrs_accessor>, mr=0xaaaaf8b478b0, attrs=...) at ../softmmu/memory.c:554 +#15 0x0000aaaada91cfc4 in memory_region_dispatch_write (mr=mr@entry=0xaaaaf8b478b0, addr=197124, data=<optimized out>, op=MO_32, attrs=attrs@entry=...) at ../softmmu/memory.c:1520 +#16 0x0000aaaada9245ec in flatview_write_continue (fv=fv@entry=0xffff38492110, addr=addr@entry=67305988, attrs=attrs@entry=..., ptr=ptr@entry=0xffffb1e13028, len=len@entry=4, addr1=<optimized out>, l=<optimized out>, + mr=0xaaaaf8b478b0) at /Images/jdx/code/qemu/include/qemu/host-utils.h:166 +#17 0x0000aaaada924844 in flatview_write (fv=0xffff38492110, addr=addr@entry=67305988, attrs=attrs@entry=..., buf=buf@entry=0xffffb1e13028, len=len@entry=4) at ../softmmu/physmem.c:2867 +#18 0x0000aaaada92825c in address_space_write (len=4, buf=0xffffb1e13028, attrs=..., addr=67305988, as=0xaaaadb4a4670 <address_space_memory>) at ../softmmu/physmem.c:2963 +#19 address_space_rw (as=0xaaaadb4a4670 <address_space_memory>, addr=67305988, attrs=attrs@entry=..., buf=buf@entry=0xffffb1e13028, len=4, is_write=<optimized out>) at ../softmmu/physmem.c:2973 +#20 0x0000aaaada9c7754 in kvm_cpu_exec (cpu=cpu@entry=0xaaaaf8c80530) at ../accel/kvm/kvm-all.c:2954 +#21 0x0000aaaada9c8adc in kvm_vcpu_thread_fn (arg=arg@entry=0xaaaaf8c80530) at ../accel/kvm/kvm-accel-ops.c:49 +#22 0x0000aaaadab2ba98 in qemu_thread_start (args=<optimized out>) at ../util/qemu-thread-posix.c:504 +#23 0x0000ffffb118718c in ?? () from target:/usr/lib64/libc.so.6 +#24 0x0000ffffb11ed15c in ?? () from target:/usr/lib64/libc.so.6 + +``` + +call_rcu_thread stack +``` +Thread 2 (Thread 0xffffb0196900 (LWP 1018210) "qemu-system-aar"): +#0 0x0000ffffb11e8ee4 in syscall () from target:/usr/lib64/libc.so.6 +#1 0x0000aaaadab2ce80 in qemu_futex_wait (val=<optimized out>, f=<optimized out>) at /Images/jdx/code/qemu/include/qemu/futex.h:29 +#2 qemu_event_wait (ev=ev@entry=0xaaaadb4c3bb8 <rcu_gp_event>) at ../util/qemu-thread-posix.c:429 +#3 0x0000aaaadab35ce8 in wait_for_readers () at ../util/rcu.c:138 +#4 synchronize_rcu () at ../util/rcu.c:174 +#5 0x0000aaaadab36160 in call_rcu_thread (opaque=opaque@entry=0x0) at ../util/rcu.c:268 +#6 0x0000aaaadab2ba98 in qemu_thread_start (args=<optimized out>) at ../util/qemu-thread-posix.c:504 +#7 0x0000ffffb118718c in ?? () from target:/usr/lib64/libc.so.6 +#8 0x0000ffffb11ed15c in ?? () from target:/usr/lib64/libc.so.6 + +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1183 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1183 new file mode 100644 index 000000000..fe5df95f9 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1183 @@ -0,0 +1,131 @@ +KVM crash due to qcow2 out of space condition during virsh-snapshot creation +Description of problem: +virsh snapshot failed due to out of space condition (into the qcow2 image ?) + +libvirt log: + +``` +2022-08-27T06:41:41.164368Z qemu-kvm-one: terminating on signal 15 from pid 1782 (/usr/sbin/libvirtd) +2022-08-27T06:41:41.172667Z qemu-kvm-one: Failed to flush the L2 table cache: Input/output error +2022-08-27T06:41:41.172692Z qemu-kvm-one: Failed to flush the refcount block cache: Input/output error +``` +Steps to reproduce: +1. not possible for that moment - i did resize/increase the qcow2 image - +now its running again. +Additional information: +as i saw - there was a very old qemu-snapshot, which was not properly deleted. +After removing this snapshot, i did reszie the image. +I do suppose, this could be one reason the image (qcow2) got full ? + +Because all is THIN i was not aware of it (fs level ok, storage layer ok). +Is there any tool, how free space in a thin qcow2 file can be monitored ? + + + +``` +PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin \ +HOME=/var/lib/libvirt/qemu/domain-13-one-89 \ +XDG_DATA_HOME=/var/lib/libvirt/qemu/domain-13-one-89/.local/share \ +XDG_CACHE_HOME=/var/lib/libvirt/qemu/domain-13-one-89/.cache \ +XDG_CONFIG_HOME=/var/lib/libvirt/qemu/domain-13-one-89/.config \ +QEMU_AUDIO_DRV=none \ +/usr/bin/qemu-kvm-one \ +-name guest=one-89,debug-threads=on \ +-S \ +-object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-13-one-89/master-key.aes \ +-machine pc-i440fx-rhel7.6.0,accel=kvm,usb=off,dump-guest-core=off \ +-cpu qemu64 \ +-m 8192 \ +-overcommit mem-lock=off \ +-smp 4,sockets=4,cores=1,threads=1 \ +-uuid 8c920c7f-f687-4c47-bfc7-671425c7436b \ +-no-user-config \ +-nodefaults \ +-chardev socket,id=charmonitor,fd=40,server,nowait \ +-mon chardev=charmonitor,id=monitor,mode=control \ +-rtc base=utc \ +-no-shutdown \ +-boot strict=on \ +-device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 \ +-device virtio-scsi-pci,id=scsi0,num_queues=1,bus=pci.0,addr=0x4 \ +-device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 \ +-blockdev '{"driver":"file","filename":"/var/lib/one//xxxx/disk.0","aio":"threads","node-name":"libvirt-3-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ +-blockdev '{"node-name":"libvirt-3-format","read-only":false,"discard":"unmap","cache":{"direct":false,"no-flush":false},"driver":"qcow2","file":"libvirt-3-storage","backing":null}' \ +-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,device_id=drive-scsi0-0-0-0,drive=libvirt-3-format,id=scsi0-0-0-0,bootindex=1,write-cache=off \ +-blockdev '{"driver":"file","filename":"/var/lib/one//xxxx/disk.1","aio":"threads","node-name":"libvirt-2-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ +-blockdev '{"node-name":"libvirt-2-format","read-only":false,"discard":"unmap","cache":{"direct":false,"no-flush":false},"driver":"qcow2","file":"libvirt-2-storage","backing":null}' \ +-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=1,lun=0,device_id=drive-scsi0-0-1-0,drive=libvirt-2-format,id=scsi0-0-1-0,write-cache=off \ +-blockdev '{"driver":"file","filename":"/var/lib/one//xxxx/disk.2","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' \ +-blockdev '{"node-name":"libvirt-1-format","read-only":true,"driver":"raw","file":"libvirt-1-storage"}' \ +-device ide-cd,bus=ide.0,unit=0,drive=libvirt-1-format,id=ide0-0-0 \ +-netdev tap,fd=42,id=hostnet0 \ +-device e1000,netdev=hostnet0,id=net0,mac=02:00:c0:a8:02:17,bus=pci.0,addr=0x3 \ +-chardev socket,id=charchannel0,fd=43,server,nowait \ +-device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ +-vnc 0.0.0.0:89 \ +-device cirrus-vga,id=video0,bus=pci.0,addr=0x2 \ +-device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 \ +-sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ +-msg timestamp=on +``` + +as the time of the crash the qcow2 status was: +(so i'm not sure the issue is about a space problem or a bug in qemu): + +``` +qemu-img info xxx/0/xxx +image: xxx/0/xxx +file format: qcow2 +virtual size: 1.46 TiB (1610612736000 bytes) +disk size: 988 GiB +cluster_size: 65536 +Snapshot list: +ID TAG VM SIZE DATE VM CLOCK ICOUNT +112 snap-111 0 B 2022-03-11 01:59:15 49:07:53.846 +282 snap-281 0 B 2022-08-20 01:59:17538:16:30.416 +283 snap-282 0 B 2022-08-21 01:59:16562:10:40.759 +284 snap-283 0 B 2022-08-22 01:59:16585:59:16.170 +285 snap-284 0 B 2022-08-23 01:59:16609:51:44.825 +286 snap-285 0 B 2022-08-24 01:59:16633:45:32.243 +287 snap-286 0 B 2022-08-25 01:59:16657:36:44.718 +288 snap-287 0 B 2022-08-26 01:59:16681:29:00.793 +Format specific information: + compat: 1.1 + compression type: zlib + lazy refcounts: false + refcount bits: 16 + corrupt: false + extended l2: false +root@proxpve1:~# qemu-img check xxxx/0/xxx +No errors were found on the image. +15252433/24576000 = 62.06% allocated, 6.32% fragmented, 0.00% compressed clusters +Image end offset: 1062936117248 + +1rst (OS) Disk on the VM: +------------------------------------------ +file format: qcow2 +virtual size: 100 GiB (107374182400 bytes) +disk size: 190 GiB +cluster_size: 65536 +Snapshot list: +ID TAG VM SIZE DATE VM CLOCK ICOUNT +282 snap-281 7.66 GiB 2022-08-20 01:59:17538:16:30.416 +283 snap-282 7.6 GiB 2022-08-21 01:59:16562:10:40.759 +284 snap-283 7.62 GiB 2022-08-22 01:59:16585:59:16.170 +285 snap-284 7.65 GiB 2022-08-23 01:59:16609:51:44.825 +286 snap-285 7.62 GiB 2022-08-24 01:59:16633:45:32.243 +287 snap-286 7.63 GiB 2022-08-25 01:59:16657:36:44.718 +288 snap-287 7.65 GiB 2022-08-26 01:59:16681:29:00.793 +Format specific information: + compat: 1.1 + compression type: zlib + lazy refcounts: false + refcount bits: 16 + corrupt: false + extended l2: false + + +No errors were found on the image. +782257/1638400 = 47.75% allocated, 22.16% fragmented, 0.00% compressed clusters +Image end offset: 315680292864 +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1185 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1185 new file mode 100644 index 000000000..8a9054020 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1185 @@ -0,0 +1,5 @@ +./configure has unprefixed calls to pkg-config and clang breaking cross-compilation +Description of problem: +The configure script (as generated) includes some calls to the toolchain without including cross compiler prefixes. This can very easily break cross compilation. Here are the locations: + +# diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1186 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1186 new file mode 100644 index 000000000..5d75aa246 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1186 @@ -0,0 +1,17 @@ +qos-test fails when built with LTO and gcc-12 +Description of problem: +The issue is already discussed here [1]. I'm simply building latest QEMU release and running the test suite. I thought the issue was fixed in 7.0 but it has resurfaced. Do QEMU dev's not build with LTO? I'm not able to debug this but I can test any proposed fixes etc. Thanks. + +[1] https://lore.kernel.org/all/1d3bbff9e92e7c8a24db9e140dcf3f428c2df103.camel@suse.com/ +Steps to reproduce: +1. Build QEMU with gcc-12 and LTO enabled +2. Run make check +3. Observe test suite failures in qos-test +Additional information: +``` +Summary of Failures: + + 2/265 qemu:qtest+qtest-aarch64 / qtest-aarch64/qos-test ERROR 0.59s killed by signal 6 SIGABRT + 3/265 qemu:qtest+qtest-i386 / qtest-i386/qos-test ERROR 0.22s killed by signal 6 SIGABRT + 7/265 qemu:qtest+qtest-x86_64 / qtest-x86_64/qos-test ERROR 0.40s killed by signal 6 SIGABRT +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1187 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1187 new file mode 100644 index 000000000..6322ce707 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1187 @@ -0,0 +1 @@ +can not handler real-time signal (signal number > 30) by sigqueue on linux user mode diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1188 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1188 new file mode 100644 index 000000000..6cb0f38e2 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1188 @@ -0,0 +1,4 @@ +qapi: add support to default value for optional members +Additional information: +This is a proposal to the QAPI spec itself to have a simple way to express that +an absent member defaults to a value. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1189 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1189 new file mode 100644 index 000000000..6ac75b296 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1189 @@ -0,0 +1 @@ +Cannot Resolve Names When Host Is Running Systemd-Resolved diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/119 b/gitlab/issues_text/target_missing/host_missing/accel_missing/119 new file mode 100644 index 000000000..883011717 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/119 @@ -0,0 +1 @@ +USB assert failure on hcd-uhci.c diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1190 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1190 new file mode 100644 index 000000000..b388b857c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1190 @@ -0,0 +1 @@ +compiling v7.1 with --static fails with "/usr/bin/ld: cannot find -lmount" diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1191 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1191 new file mode 100644 index 000000000..e5acab8c1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1191 @@ -0,0 +1,9 @@ +AC97+CoreAudio no audio when out frequency not 44,1KHz & always forces host to use 44,1KHz (or less if frequency not supported) +Description of problem: +AC97+CoreAudio outputs no audio when output frequency not 44,1KHz. Also always forces host to use 44,1KHz (or less if frequency not supported on host output) +Steps to reproduce: +1. Boot any OS with (only) AC97 audio on macOS +2. Attempt to play audio with output frequency in guest set to 48KHz +3. Observe lack of output +Additional information: +I'm using QEMU to test a Custom OS written by me, but this shouldn't be a code issue on our side, rather an issue with QEMU itself, if this is mistaken, please inform us. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1192 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1192 new file mode 100644 index 000000000..2400b01e8 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1192 @@ -0,0 +1,135 @@ +Abort in xhci_find_stream() +Description of problem: +I triggered an abort in xhci_find_stream() [1]. This is because the +secondary stream arrays is enabled by setting linear stream array (LSA) bit (in +endpoint context) to 0. We may show warnings and drop this operation. + +``` c +static XHCIStreamContext *xhci_find_stream(XHCIEPContext *epctx, + unsigned int streamid, + uint32_t *cc_error) +{ + // ... + if (epctx->lsa) { + // ... + } else { + FIXME("secondary streams not implemented yet"); // <----------- [1] + } + // ... +``` +Steps to reproduce: +Step 1: download the prepared rootfs and the image. + +https://drive.google.com/file/d/10C2110VH-GrwACiPebC8-Vgcf5_Ny8Sd/view?usp=sharing +https://drive.google.com/file/d/1jAMf8rtTM8p88gamhNk4HC5Z34XtjUHw/view?usp=sharing + +Step 2: run the following script. + +``` bash +QEMU_PATH=../../../qemu/build/qemu-system-x86_64 +KERNEL_PATH=./bzImage +ROOTFS_PATH=./rootfs.ext2 +$QEMU_PATH \ + -M q35 -m 1G \ + -kernel $KERNEL_PATH \ + -drive file=$ROOTFS_PATH,if=virtio,format=raw \ + -append "root=/dev/vda console=ttyS0" \ + -net nic,model=virtio -net user \ + -drive file=null-co://,if=none,format=raw,id=disk0 \ + -device qemu-xhci,id=xhci -device usb-storage,drive=disk0 \ + -device usb-bot -device usb-tablet,bus=xhci.0 \ + -chardev null,id=cd0 -chardev null,id=cd1 \ + -device usb-braille,chardev=cd0 -device usb-ccid -device usb-ccid \ + -device usb-kbd -device usb-mouse -device usb-serial,chardev=cd1 \ + -device usb-tablet -device usb-wacom-tablet -device usb-audio \ + -nographic +``` + +Step 3: with spawned shell (the user is root and the password is empty), run +`xhci-00`. +Additional information: +``` +root@5b4fda3ee725:~/videzzo/videzzo_qemu/out-san# DEFAULT_INPUT_MAXSIZE=10000000 /root/videzzo/videzzo_qemu/out-san/qemu-videzzo-i386-target-videzzo-fuzz-xhci -max_len=10000000 -detect_leaks=0 poc-qemu-videzzo-i386-target-videzzo-fuzz-xhci-crash-4a11736abb111efe4b29a6931f403561f9a0f9ec +==71545==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases! +INFO: found LLVMFuzzerCustomMutator (0x55e05e05e640). Disabling -len_control by default. +INFO: Running with entropic power schedule (0xFF, 100). +INFO: Seed: 2668437424 +INFO: Loaded 1 modules (423456 inline 8-bit counters): 423456 [0x55e0606e8000, 0x55e06074f620), +INFO: Loaded 1 PC tables (423456 PCs): 423456 [0x55e060071ae0,0x55e0606e7ce0), +/root/videzzo/videzzo_qemu/out-san/qemu-videzzo-i386-target-videzzo-fuzz-xhci: Running 1 inputs 1 time(s) each. +INFO: Reading pre_seed_input if any ... +INFO: Executing pre_seed_input if any ... +Matching objects by name , *capabilities*, *operational*, *runtime*, *doorbell*, *usb3 port* +This process will fuzz the following MemoryRegions: + * usb3 port #1[0] (size 10) + * usb3 port #4[0] (size 10) + * capabilities[0] (size 40) + * usb3 port #3[0] (size 10) + * operational[0] (size 400) + * usb3 port #2[0] (size 10) + * runtime[0] (size 220) + * doorbell[0] (size 820) +This process will fuzz through the following interfaces: + * clock_step, EVENT_TYPE_CLOCK_STEP, 0xffffffff +0xffffffff, 255,255 + * capabilities, EVENT_TYPE_MMIO_READ, 0xe0000000 +0x40, 4,4 + * capabilities, EVENT_TYPE_MMIO_WRITE, 0xe0000000 +0x40, 4,4 + * operational, EVENT_TYPE_MMIO_READ, 0xe0000040 +0x400, 4,8 + * operational, EVENT_TYPE_MMIO_WRITE, 0xe0000040 +0x400, 4,8 + * runtime, EVENT_TYPE_MMIO_READ, 0xe0001000 +0x220, 4,8 + * runtime, EVENT_TYPE_MMIO_WRITE, 0xe0001000 +0x220, 4,8 + * doorbell, EVENT_TYPE_MMIO_READ, 0xe0002000 +0x820, 4,4 + * doorbell, EVENT_TYPE_MMIO_WRITE, 0xe0002000 +0x820, 4,4 + * usb3 port #4, EVENT_TYPE_MMIO_READ, 0xe0000470 +0x10, 4,4 + * usb3 port #4, EVENT_TYPE_MMIO_WRITE, 0xe0000470 +0x10, 4,4 + * usb3 port #1, EVENT_TYPE_MMIO_READ, 0xe0000440 +0x10, 4,4 + * usb3 port #1, EVENT_TYPE_MMIO_WRITE, 0xe0000440 +0x10, 4,4 + * usb3 port #2, EVENT_TYPE_MMIO_READ, 0xe0000450 +0x10, 4,4 + * usb3 port #2, EVENT_TYPE_MMIO_WRITE, 0xe0000450 +0x10, 4,4 + * usb3 port #3, EVENT_TYPE_MMIO_READ, 0xe0000460 +0x10, 4,4 + * usb3 port #3, EVENT_TYPE_MMIO_WRITE, 0xe0000460 +0x10, 4,4 +INFO: A corpus is not provided, starting from an empty corpus +#2 INITED cov: 3 ft: 4 corp: 1/1b exec/s: 0 rss: 197Mb +Running: poc-qemu-videzzo-i386-target-videzzo-fuzz-xhci-crash-4a11736abb111efe4b29a6931f403561f9a0f9ec +../hw/usb/hcd-xhci.c:1099:25: runtime error: shift exponent 156 is too large for 32-bit type 'int' +SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior ../hw/usb/hcd-xhci.c:1099:25 in +FIXME xhci_find_stream:998 secondary streams not implemented yet +==71545== ERROR: libFuzzer: deadly signal + #0 0x55e05a7f874e in __sanitizer_print_stack_trace /root/llvm-project/compiler-rt/lib/asan/asan_stack.cpp:86:3 + #1 0x55e05a7473c1 in fuzzer::PrintStackTrace() /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerUtil.cpp:210:38 + #2 0x55e05a720c06 in fuzzer::Fuzzer::CrashCallback() (.part.0) /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:235:18 + #3 0x55e05a720cd2 in fuzzer::Fuzzer::CrashCallback() /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:207:1 + #4 0x55e05a720cd2 in fuzzer::Fuzzer::StaticCrashSignalCallback() /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:206:19 + #5 0x7fa0b025c41f (/lib/x86_64-linux-gnu/libpthread.so.0+0x1441f) + #6 0x7fa0b006e00a in __libc_signal_restore_set /build/glibc-SzIz7B/glibc-2.31/signal/../sysdeps/unix/sysv/linux/internal-signals.h:86:3 + #7 0x7fa0b006e00a in raise /build/glibc-SzIz7B/glibc-2.31/signal/../sysdeps/unix/sysv/linux/raise.c:48:3 + #8 0x7fa0b004d858 in abort /build/glibc-SzIz7B/glibc-2.31/stdlib/abort.c:79:7 + #9 0x55e05a828c9a in __wrap_abort /root/videzzo/videzzo_qemu/qemu/build-san-6/../tests/qtest/videzzo/less_crashes_wrappers.c:24:12 + #10 0x55e05bd528c3 in xhci_find_stream /root/videzzo/videzzo_qemu/qemu/build-san-6/../hw/usb/hcd-xhci.c:998:9 + #11 0x55e05bd46ca5 in xhci_kick_epctx /root/videzzo/videzzo_qemu/qemu/build-san-6/../hw/usb/hcd-xhci.c:1922:17 + #12 0x55e05bd7d7ff in xhci_kick_ep /root/videzzo/videzzo_qemu/qemu/build-san-6/../hw/usb/hcd-xhci.c:1838:5 + #13 0x55e05bd94ab9 in xhci_doorbell_write /root/videzzo/videzzo_qemu/qemu/build-san-6/../hw/usb/hcd-xhci.c:3163:13 + #14 0x55e05cfed443 in memory_region_write_accessor /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/memory.c:492:5 + #15 0x55e05cfecd81 in access_with_adjusted_size /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/memory.c:554:18 + #16 0x55e05cfeb68c in memory_region_dispatch_write /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/memory.c:1514:16 + #17 0x55e05d0760be in flatview_write_continue /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/physmem.c:2825:23 + #18 0x55e05d06443b in flatview_write /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/physmem.c:2867:12 + #19 0x55e05d063ef8 in address_space_write /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/physmem.c:2963:18 + #20 0x55e05a83813b in qemu_writel /root/videzzo/videzzo_qemu/qemu/build-san-6/../tests/qtest/videzzo/videzzo_qemu.c:1072:5 + #21 0x55e05a8365b5 in dispatch_mmio_write /root/videzzo/videzzo_qemu/qemu/build-san-6/../tests/qtest/videzzo/videzzo_qemu.c:1197:28 + #22 0x55e05e059fff in videzzo_dispatch_event /root/videzzo/videzzo.c:1122:5 + #23 0x55e05e05137b in __videzzo_execute_one_input /root/videzzo/videzzo.c:272:9 + #24 0x55e05e051250 in videzzo_execute_one_input /root/videzzo/videzzo.c:313:9 + #25 0x55e05a83f17c in videzzo_qemu /root/videzzo/videzzo_qemu/qemu/build-san-6/../tests/qtest/videzzo/videzzo_qemu.c:1472:12 + #26 0x55e05e05e8e2 in LLVMFuzzerTestOneInput /root/videzzo/videzzo.c:1891:18 + #27 0x55e05a72173d in fuzzer::Fuzzer::ExecuteCallback(unsigned char*, unsigned long) /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:589:17 + #28 0x55e05a7044c4 in fuzzer::RunOneTest(fuzzer::Fuzzer*, char const*, unsigned long) /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:323:21 + #29 0x55e05a70f43e in fuzzer::FuzzerDriver(int*, char***, int (*)(unsigned char*, unsigned long)) /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:882:19 + #30 0x55e05a6fba46 in main /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerMain.cpp:20:30 + #31 0x7fa0b004f082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16 + #32 0x55e05a6fba9d in _start (/root/videzzo/videzzo_qemu/out-san/qemu-videzzo-i386-target-videzzo-fuzz-xhci+0x265aa9d) + +NOTE: libFuzzer has rudimentary signal handlers. + Combine libFuzzer with AddressSanitizer or similar for better crash reports. +SUMMARY: libFuzzer: deadly signal +MS: 0 ; base unit: 0000000000000000000000000000000000000000 +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1193 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1193 new file mode 100644 index 000000000..67f62c2ad --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1193 @@ -0,0 +1,16 @@ +io_uring / iothread regression 7.1.0 +Description of problem: +After upgrading to 7.1.0, some of my libvirt VM's failed to boot. I have narrowed down the issue to the combination of: + +- io_uring +- iothread +Steps to reproduce: +1. set up a VM with iothread and io_uring +2. try to boot and watch it "hang" +Additional information: +Here's the relevant command line from the libvirt log: +``` +-blockdev '{"driver":"file","filename":"/mnt/data/VMs/Arch-Linux-x86_64-basic.qcow2","aio":"io_uring","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' \ +-blockdev '{"node-name":"libvirt-1-format","read-only":false,"driver":"qcow2","file":"libvirt-1-storage","backing":null}' \ +-device '{"driver":"virtio-blk-pci","iothread":"iothread1","bus":"pci.4","addr":"0x0","drive":"libvirt-1-format","id":"virtio-disk0","bootindex":1 }' \ +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1194 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1194 new file mode 100644 index 000000000..65eb7ea2d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1194 @@ -0,0 +1,15 @@ +Initialization of device virtio-net-pci failed: failed to find romfile "efi-virtio.rom" +Description of problem: +After executing the below command inside adb shell +qemu-system-aarch64 -enable-kvm -nographic \ +-kernel Image -initrd ramdisk.img -m 512 -M virt -cpu host \ + +I am getting the below error +"qemu-system-aarch64: Initialization of device virtio-net-pci failed: failed to find romfile "efi-virtio.rom"" +Steps to reproduce: +1. adb Push qemu-system-aarch64 inside system/bin +2. Run +qemu-system-aarch64 -enable-kvm -nographic \ +-kernel Image -initrd ramdisk.img -m 512 -M virt -cpu host \ +Additional information: +Kindly help me to proceed further diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1195 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1195 new file mode 100644 index 000000000..51cbde9ba --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1195 @@ -0,0 +1,18 @@ +Race condition during QEMU exit cleanup can lead to deadlock +Description of problem: +During the cleanup phase of QEMU exiting, there is a small race condition window that can lead QEMU to lock up completely: +In the main QEMU thread, during the exit, the thread will execute the 'qemu_cleanup' function, which calls 'do_vm_stop', which calls 'pause_all_vcpus'. This method tries to (as the name suggests) stop/pause all the vcpu threads. At the same time, the vcpu thread might have just existed it's main mttcg exec loop, which means it will enter 'qemu_wait_io_event'. At this point, the following race condition can occur: +- vcpu_thread - cpus.c:416 <= enters qemu_wait_io_event +- shutdown_thread - cpus.c:555 <= enters pause_all_vcpus +- vcpu_thread - cpus.c:418 <= cpu_thread_is_idle returns true, cpu->stop not set yet +- shutdown_thread - cpus.c:560/561 <= sets cpu->stop and kicks the vcpu, but it's not waiting on cpu->halt_cond yet, so nothing happens +- vcpu_thread - cpus.c:423 <= starts waiting on cpu->halt_cond +- shutdown_thread - cpus.c:570 <= not all vcpus paused, so enters while loop +- shutdown_thread - cpus.c:571 <= starts waiting on qemu_pause_cond +- **deadlock** + +In my case, my plugin registers qemu_plugin_vcpu_idle_cb, so the race window is extended significantly in the vcpu thread (cpus.c:421) but I believe it can happen with the smaller race window as well. + +Note that this explanation is just based on my understanding of the code, and the final state of QEMU during the deadlock after I attached: The main thread (thread 1) was waiting on qemu_pause_cond in pause_all_vcpus, and the vcpu was waiting on cpu->halt_cond in qemu_wait_io_event, with no one else to wake either of them up. (This was following an exit that was triggered by a timeout signal) +Steps to reproduce: +This is a race condition, so I don't have a reliable reproducer. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1196 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1196 new file mode 100644 index 000000000..7862ffe21 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1196 @@ -0,0 +1,12 @@ +Guest could not enable pci AtomicOp requests for passthrough device +Description of problem: +Guest could not enable pci AtomicOp requests for passthrough device. + +sudo setpci -v -d *:706t 8c.b=40 // enable pci AtomicOp requests bit in the guest os. + +Host could not see the bit by command "sudo lspci -vvv -s 03:00.0". +Steps to reproduce: +1. sudo setpci -v -d *:706t 8c.b=40 // in the guest os +2. sudo lspci -vvv -s 03:00.0 // in the host os +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1197 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1197 new file mode 100644 index 000000000..148786946 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1197 @@ -0,0 +1,815 @@ +Use libvirt to create a Windows virtual machine and load NVIDIA's GPU. Installing NVIDIA driver causes the physical machine to restart +Description of problem: +As described in the title, When I created a Windows virtual machine and used NVIDIA's GPU and installed NVIDIA's driver in Windows VM, however, the physical machine will be restart. In the same create time, if it is a linux VM, It's ok! I don't know if there is a problem with my creation process or if the windows virtual machine is incompatible with NVIDIA graphics card. + + +GPU INFO: +``` +81:00.0 VGA compatible controller: NVIDIA Corporation GP106GL [Quadro P2000] (rev a1) +81:00.1 Audio device: NVIDIA Corporation GP106 High Definition Audio Controller (rev a1) +``` + + +BR！ +Steps to reproduce: +1. +2. +3. +Additional information: +qemu info: +``` +libvirt-daemon-driver-qemu-4.5.0-36.el7_9.5.x86_64 +ipxe-roms-qemu-20180825-3.git133f4c.el7.noarch +qemu-kvm-common-1.5.3-175.el7_9.6.x86_64 +qemu-kvm-1.5.3-175.el7_9.6.x86_64 +qemu-img-1.5.3-175.el7_9.6.x86_64 +``` + + + +``` +<domain type="kvm"> + <name>win</name> + <uuid>a5efd8ed-fa6f-693c-2202-93183ec18b5e</uuid> + <description>None</description> + <memory unit="KiB">5242880</memory> + <currentMemory unit="KiB">5242880</currentMemory> + <vcpu placement="static">4</vcpu> + <os> + <type arch="x86_64" machine="pc-i440fx-rhel7.0.0">hvm</type> + <boot dev="hd"/> + <boot dev="cdrom"/> + <bootmenu enable="yes"/> + </os> + <features> + <acpi/> + <apic/> + <pae/> + </features> + <cpu mode="host-passthrough" check="none"/> + <clock offset="utc"/> + <on_poweroff>destroy</on_poweroff> + <on_reboot>restart</on_reboot> + <on_crash>restart</on_crash> + <devices> + <emulator>/usr/libexec/qemu-kvm</emulator> + <disk type="file" device="disk"> + <driver name="qemu" type="qcow2"/> + <source file="/opt/panafs/1374467833802939042/win.img"/> + <target dev="sda" bus="sata"/> + <address type="drive" controller="0" bus="0" target="0" unit="0"/> + </disk> + <disk type="file" device="cdrom"> + <driver name="qemu" type="raw"/> + <source file="/opt/panafs/13680547561012925528/cn_windows_10_consumer_edition_version_1803_updated_aug_2018_x64_dvd_2cf38490.iso"/> + <target dev="hda" bus="ide"/> + <readonly/> + <address type="drive" controller="0" bus="1" target="0" unit="1"/> + </disk> + <disk type="file" device="cdrom"> + <driver name="qemu" type="raw"/> + <source file="/var/lib/libvirt/images/virtio-win-0.1.217.iso"/> + <target dev="hdb" bus="ide"/> + <readonly/> + <address type="drive" controller="0" bus="0" target="0" unit="1"/> + </disk> + <controller type="usb" index="0" model="piix3-uhci"> + <address type="pci" domain="0x0000" bus="0x00" slot="0x01" function="0x2"/> + </controller> + <controller type="pci" index="0" model="pci-root"/> + <controller type="ide" index="0"> + <address type="pci" domain="0x0000" bus="0x00" slot="0x01" function="0x1"/> + </controller> + <controller type="sata" index="0"> + <address type="pci" domain="0x0000" bus="0x00" slot="0x04" function="0x0"/> + </controller> + <controller type="virtio-serial" index="0"> + <address type="pci" domain="0x0000" bus="0x00" slot="0x05" function="0x0"/> + </controller> + <interface type="network"> + <mac address="52:54:00:1d:d8:7d"/> + <source network="default"/> + <model type="virtio"/> + <address type="pci" domain="0x0000" bus="0x00" slot="0x03" function="0x0"/> + </interface> + <interface type="network"> + <mac address="52:54:00:09:bc:30"/> + <source network="default"/> + <model type="e1000"/> + <address type="pci" domain="0x0000" bus="0x00" slot="0x09" function="0x0"/> + </interface> + <serial type="pty"> + <target type="isa-serial" port="0"> + <model name="isa-serial"/> + </target> + </serial> + <console type="pty"> + <target type="serial" port="0"/> + </console> + <channel type="unix"> + <target type="virtio" name="org.qemu.guest_agent.0"/> + <address type="virtio-serial" controller="0" bus="0" port="2"/> + </channel> + <input type="mouse" bus="ps2"/> + <input type="tablet" bus="usb"> + <address type="usb" bus="0" port="1"/> + </input> + <input type="keyboard" bus="ps2"/> + <graphics type="vnc" port="-1" autoport="yes"> + <listen type="address"/> + </graphics> + <video> + <model type="cirrus" vram="16384" heads="1" primary="yes"/> + <address type="pci" domain="0x0000" bus="0x00" slot="0x02" function="0x0"/> + </video> + <hostdev mode="subsystem" type="pci" managed="yes"> + <source> + <address domain="0x0000" bus="0x81" slot="0x00" function="0x0"/> + </source> + <address type="pci" domain="0x0000" bus="0x00" slot="0x07" function="0x0"/> + </hostdev> + <hostdev mode="subsystem" type="pci" managed="yes"> + <source> + <address domain="0x0000" bus="0x81" slot="0x00" function="0x1"/> + </source> + <address type="pci" domain="0x0000" bus="0x00" slot="0x08" function="0x0"/> + </hostdev> + <memballoon model="virtio"> + <address type="pci" domain="0x0000" bus="0x00" slot="0x06" function="0x0"/> + </memballoon> + </devices> +</domain> +``` + + + +part log of VM: + +``` +2022-09-05 07:12:51.328+0000: starting up libvirt version: 4.5.0, package: 36.el7_9.5 (CentOS BuildSystem <http://bugs.centos.org>, 2021-04-28-13:32:22, x86-01.bsys.centos.org), qemu version: 1.5.3 (qemu +-kvm-1.5.3-175.el7_9.6), kernel: 3.10.0-1160.el7.x86_64, hostname: localhost.localdomain +LC_ALL=C \ +PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin \ +QEMU_AUDIO_DRV=none \ +/usr/libexec/qemu-kvm \ +-name win \ +-S \ +-machine pc-i440fx-rhel7.0.0,accel=kvm,usb=off,dump-guest-core=off \ +-cpu host \ +-m 5120 \ +-realtime mlock=off \ +-smp 4,sockets=4,cores=1,threads=1 \ +-uuid 49f538e1-4042-bbc4-1b2c-10f02219bba5 \ +-no-user-config \ +-nodefaults \ +-chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-3-win/monitor.sock,server,nowait \ +-mon chardev=charmonitor,id=monitor,mode=control \ +-rtc base=utc \ +-no-shutdown \ +-boot menu=on,strict=on \ +-device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 \ +-device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x4 \ +-device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 \ +-drive file=/opt/panafs/1374467833802939042/win.img,format=qcow2,if=none,id=drive-scsi0-0-0-0 \ +-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=1 \ +-drive file=/opt/panafs/13680547561012925528/cn_windows_10_consumer_edition_version_1803_updated_aug_2018_x64_dvd_2cf38490.iso,format=raw,if=none,id=drive-ide0-1-1,readonly=on \ +-device ide-cd,bus=ide.1,unit=1,drive=drive-ide0-1-1,id=ide0-1-1,bootindex=2 \ +-netdev tap,fd=28,id=hostnet0,vhost=on,vhostfd=30 \ +-device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:78:1a:32,bus=pci.0,addr=0x3 \ +-chardev pty,id=charserial0 \ +-device isa-serial,chardev=charserial0,id=serial0 \ +-chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-3-win/org.qemu.guest_agent.0,server,nowait \ +-device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ +-device usb-tablet,id=input1,bus=usb.0,port=1 \ +-vnc 0.0.0.0:0 \ +-vga cirrus \ +-device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 \ +-msg timestamp=on +2022-09-05 07:12:51.328+0000: Domain id=3 is tainted: host-cpu +char device redirected to /dev/pts/4 (label charserial0) +qemu: terminating on signal 15 from pid 3723 +2022-09-05 07:14:02.309+0000: shutting down, reason=destroyed +2022-09-05 07:14:35.696+0000: starting up libvirt version: 4.5.0, package: 36.el7_9.5 (CentOS BuildSystem <http://bugs.centos.org>, 2021-04-28-13:32:22, x86-01.bsys.centos.org), qemu version: 1.5.3 (qemu +-kvm-1.5.3-175.el7_9.6), kernel: 3.10.0-1160.el7.x86_64, hostname: localhost.localdomain +LC_ALL=C \ +PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin \ +QEMU_AUDIO_DRV=none \ +/usr/libexec/qemu-kvm \ +-name win \ +-S \ +-machine pc-i440fx-rhel7.0.0,accel=kvm,usb=off,dump-guest-core=off \ +-cpu host \ +-m 5120 \ +-realtime mlock=off \ +-smp 4,sockets=4,cores=1,threads=1 \ +-uuid abcbac3c-fd61-57ac-f1ad-60387881c0a6 \ +-no-user-config \ +-nodefaults \ +-chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-4-win/monitor.sock,server,nowait \ +-mon chardev=charmonitor,id=monitor,mode=control \ +-rtc base=utc \ +-no-shutdown \ +-boot menu=on,strict=on \ +-device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 \ +-device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 \ +-drive file=/opt/panafs/1374467833802939042/win.img,format=qcow2,if=none,id=drive-virtio-disk0 \ +-device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 \ +-drive file=/opt/panafs/13680547561012925528/cn_windows_10_consumer_edition_version_1803_updated_aug_2018_x64_dvd_2cf38490.iso,format=raw,if=none,id=drive-ide0-1-1,readonly=on \ +-device ide-cd,bus=ide.1,unit=1,drive=drive-ide0-1-1,id=ide0-1-1,bootindex=2 \ +-netdev tap,fd=28,id=hostnet0,vhost=on,vhostfd=30 \ +-device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:94:04:a7,bus=pci.0,addr=0x3 \ +-chardev pty,id=charserial0 \ +-device isa-serial,chardev=charserial0,id=serial0 \ +-chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-4-win/org.qemu.guest_agent.0,server,nowait \ +-device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ +-device usb-tablet,id=input1,bus=usb.0,port=1 \ +-vnc 0.0.0.0:0 \ +-vga cirrus \ +-device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 \ +-msg timestamp=on +2022-09-05 07:14:35.696+0000: Domain id=4 is tainted: host-cpu +char device redirected to /dev/pts/4 (label charserial0) +qemu: terminating on signal 15 from pid 3723 +2022-09-05 07:15:54.690+0000: shutting down, reason=destroyed +2022-09-05 07:16:18.098+0000: starting up libvirt version: 4.5.0, package: 36.el7_9.5 (CentOS BuildSystem <http://bugs.centos.org>, 2021-04-28-13:32:22, x86-01.bsys.centos.org), qemu version: 1.5.3 (qemu +-kvm-1.5.3-175.el7_9.6), kernel: 3.10.0-1160.el7.x86_64, hostname: localhost.localdomain +LC_ALL=C \ +PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin \ +QEMU_AUDIO_DRV=none \ +/usr/libexec/qemu-kvm \ +-name win \ +-S \ +-machine pc-i440fx-rhel7.0.0,accel=kvm,usb=off,dump-guest-core=off \ +-cpu host \ +-m 5120 \ +-realtime mlock=off \ +-smp 4,sockets=4,cores=1,threads=1 \ +-uuid a5efd8ed-fa6f-693c-2202-93183ec18b5e \ +-no-user-config \ +-nodefaults \ +-chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-5-win/monitor.sock,server,nowait \ +-mon chardev=charmonitor,id=monitor,mode=control \ +-rtc base=utc \ +-no-shutdown \ +-boot menu=on,strict=on \ +-device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 \ +-device ahci,id=sata0,bus=pci.0,addr=0x4 \ +-device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 \ +-drive file=/opt/panafs/1374467833802939042/win.img,format=qcow2,if=none,id=drive-sata0-0-0 \ +-device ide-hd,bus=sata0.0,drive=drive-sata0-0-0,id=sata0-0-0,bootindex=1 \ +-drive file=/opt/panafs/13680547561012925528/cn_windows_10_consumer_edition_version_1803_updated_aug_2018_x64_dvd_2cf38490.iso,format=raw,if=none,id=drive-ide0-1-1,readonly=on \ +-device ide-cd,bus=ide.1,unit=1,drive=drive-ide0-1-1,id=ide0-1-1,bootindex=2 \ +-netdev tap,fd=28,id=hostnet0,vhost=on,vhostfd=30 \ +-device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:1d:d8:7d,bus=pci.0,addr=0x3 \ +-chardev pty,id=charserial0 \ +-device isa-serial,chardev=charserial0,id=serial0 \ +-chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-5-win/org.qemu.guest_agent.0,server,nowait \ +-device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ +-device usb-tablet,id=input1,bus=usb.0,port=1 \ +-vnc 0.0.0.0:0 \ +-vga cirrus \ +-device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 \ +-msg timestamp=on +2022-09-05 07:16:18.098+0000: Domain id=5 is tainted: host-cpu +char device redirected to /dev/pts/4 (label charserial0) +qemu: terminating on signal 15 from pid 3723 +2022-09-05 07:33:42.873+0000: shutting down, reason=destroyed +2022-09-05 07:37:05.200+0000: starting up libvirt version: 4.5.0, package: 36.el7_9.5 (CentOS BuildSystem <http://bugs.centos.org>, 2021-04-28-13:32:22, x86-01.bsys.centos.org), qemu version: 1.5.3 (qemu +-kvm-1.5.3-175.el7_9.6), kernel: 3.10.0-1160.el7.x86_64, hostname: localhost.localdomain +LC_ALL=C \ +PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin \ +QEMU_AUDIO_DRV=none \ +/usr/libexec/qemu-kvm \ +-name win \ +-S \ +-machine pc-i440fx-rhel7.0.0,accel=kvm,usb=off,dump-guest-core=off \ +-cpu host \ +-m 5120 \ +-realtime mlock=off \ +-smp 4,sockets=4,cores=1,threads=1 \ +-uuid a5efd8ed-fa6f-693c-2202-93183ec18b5e \ +-no-user-config \ +-nodefaults \ +-chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-6-win/monitor.sock,server,nowait \ +-mon chardev=charmonitor,id=monitor,mode=control \ +-rtc base=utc \ +-no-shutdown \ +-boot menu=on,strict=on \ +-device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 \ +-device ahci,id=sata0,bus=pci.0,addr=0x4 \ +-device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 \ +-drive file=/opt/panafs/1374467833802939042/win.img,format=qcow2,if=none,id=drive-sata0-0-0 \ +-device ide-hd,bus=sata0.0,drive=drive-sata0-0-0,id=sata0-0-0,bootindex=1 \ +-drive file=/opt/panafs/13680547561012925528/cn_windows_10_consumer_edition_version_1803_updated_aug_2018_x64_dvd_2cf38490.iso,format=raw,if=none,id=drive-ide0-1-1,readonly=on \ +-device ide-cd,bus=ide.1,unit=1,drive=drive-ide0-1-1,id=ide0-1-1,bootindex=2 \ +-netdev tap,fd=30,id=hostnet0,vhost=on,vhostfd=32 \ +-device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:1d:d8:7d,bus=pci.0,addr=0x3 \ +-chardev pty,id=charserial0 \ +-device isa-serial,chardev=charserial0,id=serial0 \ +-chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-6-win/org.qemu.guest_agent.0,server,nowait \ +-device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ +-device usb-tablet,id=input1,bus=usb.0,port=1 \ +-vnc 0.0.0.0:0 \ +-vga cirrus \ +-device vfio-pci,host=81:00.0,id=hostdev0,bus=pci.0,addr=0x7 \ +-device vfio-pci,host=81:00.1,id=hostdev1,bus=pci.0,addr=0x8 \ +-device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 \ +-msg timestamp=on +2022-09-05 07:37:05.200+0000: Domain id=6 is tainted: host-cpu +char device redirected to /dev/pts/4 (label charserial0) +qemu: terminating on signal 15 from pid 3723 +2022-09-05 07:37:37.578+0000: shutting down, reason=destroyed +2022-09-05 07:37:44.799+0000: starting up libvirt version: 4.5.0, package: 36.el7_9.5 (CentOS BuildSystem <http://bugs.centos.org>, 2021-04-28-13:32:22, x86-01.bsys.centos.org), qemu version: 1.5.3 (qemu +-kvm-1.5.3-175.el7_9.6), kernel: 3.10.0-1160.el7.x86_64, hostname: localhost.localdomain +LC_ALL=C \ +PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin \ +QEMU_AUDIO_DRV=none \ +/usr/libexec/qemu-kvm \ +-name win \ +-S \ +-machine pc-i440fx-rhel7.0.0,accel=kvm,usb=off,dump-guest-core=off \ +-cpu host \ +-m 5120 \ +-realtime mlock=off \ +-smp 4,sockets=4,cores=1,threads=1 \ +-uuid a5efd8ed-fa6f-693c-2202-93183ec18b5e \ +-no-user-config \ +-nodefaults \ +-chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-7-win/monitor.sock,server,nowait \ +-mon chardev=charmonitor,id=monitor,mode=control \ +-rtc base=utc \ +-no-shutdown \ +-boot menu=on,strict=on \ +-device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 \ +-device ahci,id=sata0,bus=pci.0,addr=0x4 \ +-device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 \ +-drive file=/opt/panafs/1374467833802939042/win.img,format=qcow2,if=none,id=drive-sata0-0-0 \ +-device ide-hd,bus=sata0.0,drive=drive-sata0-0-0,id=sata0-0-0,bootindex=1 \ +-drive file=/opt/panafs/13680547561012925528/cn_windows_10_consumer_edition_version_1803_updated_aug_2018_x64_dvd_2cf38490.iso,format=raw,if=none,id=drive-ide0-1-1,readonly=on \ +-device ide-cd,bus=ide.1,unit=1,drive=drive-ide0-1-1,id=ide0-1-1,bootindex=2 \ +-netdev tap,fd=30,id=hostnet0,vhost=on,vhostfd=32 \ +-device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:1d:d8:7d,bus=pci.0,addr=0x3 \ +-netdev tap,fd=33,id=hostnet1 \ +-device e1000,netdev=hostnet1,id=net1,mac=52:54:00:09:bc:30,bus=pci.0,addr=0x9 \ +-chardev pty,id=charserial0 \ +-device isa-serial,chardev=charserial0,id=serial0 \ +-chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-7-win/org.qemu.guest_agent.0,server,nowait \ +-device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ +-device usb-tablet,id=input1,bus=usb.0,port=1 \ +-vnc 0.0.0.0:0 \ +-vga cirrus \ +-device vfio-pci,host=81:00.0,id=hostdev0,bus=pci.0,addr=0x7 \ +-device vfio-pci,host=81:00.1,id=hostdev1,bus=pci.0,addr=0x8 \ +-device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 \ +-msg timestamp=on +2022-09-05 07:37:44.799+0000: Domain id=7 is tainted: host-cpu +char device redirected to /dev/pts/4 (label charserial0) +qemu: terminating on signal 15 from pid 3723 +2022-09-05 07:49:11.497+0000: shutting down, reason=destroyed +2022-09-05 07:49:34.883+0000: starting up libvirt version: 4.5.0, package: 36.el7_9.5 (CentOS BuildSystem <http://bugs.centos.org>, 2021-04-28-13:32:22, x86-01.bsys.centos.org), qemu version: 1.5.3 (qemu +-kvm-1.5.3-175.el7_9.6), kernel: 3.10.0-1160.el7.x86_64, hostname: localhost.localdomain +LC_ALL=C \ +PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin \ +QEMU_AUDIO_DRV=none \ +/usr/libexec/qemu-kvm \ +-name win \ +-S \ +-machine pc-i440fx-rhel7.0.0,accel=kvm,usb=off,dump-guest-core=off \ +-cpu host \ +-m 5120 \ +-realtime mlock=off \ +-smp 4,sockets=4,cores=1,threads=1 \ +-uuid a5efd8ed-fa6f-693c-2202-93183ec18b5e \ +-no-user-config \ +-nodefaults \ +-chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-8-win/monitor.sock,server,nowait \ +-mon chardev=charmonitor,id=monitor,mode=control \ +-rtc base=utc \ +-no-shutdown \ +-boot menu=on,strict=on \ +-device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 \ +-device ahci,id=sata0,bus=pci.0,addr=0x4 \ +-device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 \ +-drive file=/opt/panafs/1374467833802939042/win.img,format=qcow2,if=none,id=drive-sata0-0-0 \ +-device ide-hd,bus=sata0.0,drive=drive-sata0-0-0,id=sata0-0-0,bootindex=1 \ +-drive file=/opt/panafs/13680547561012925528/cn_windows_10_consumer_edition_version_1803_updated_aug_2018_x64_dvd_2cf38490.iso,format=raw,if=none,id=drive-ide0-1-1,readonly=on \ +-device ide-cd,bus=ide.1,unit=1,drive=drive-ide0-1-1,id=ide0-1-1,bootindex=2 \ +-netdev tap,fd=30,id=hostnet0,vhost=on,vhostfd=32 \ +-device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:1d:d8:7d,bus=pci.0,addr=0x3 \ +-netdev tap,fd=33,id=hostnet1 \ +-device e1000,netdev=hostnet1,id=net1,mac=52:54:00:09:bc:30,bus=pci.0,addr=0x9 \ +-chardev pty,id=charserial0 \ +-device isa-serial,chardev=charserial0,id=serial0 \ +-chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-8-win/org.qemu.guest_agent.0,server,nowait \ +-device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ +-device usb-tablet,id=input1,bus=usb.0,port=1 \ +-vnc 0.0.0.0:0 \ +-vga cirrus \ +-device vfio-pci,host=81:00.0,id=hostdev0,bus=pci.0,addr=0x7 \ +-device vfio-pci,host=81:00.1,id=hostdev1,bus=pci.0,addr=0x8 \ +-device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 \ +-msg timestamp=on +2022-09-05 07:49:34.883+0000: Domain id=8 is tainted: host-cpu +char device redirected to /dev/pts/4 (label charserial0) +2022-09-05 08:08:31.206+0000: starting up libvirt version: 4.5.0, package: 36.el7_9.5 (CentOS BuildSystem <http://bugs.centos.org>, 2021-04-28-13:32:22, x86-01.bsys.centos.org), qemu version: 1.5.3 (qemu +-kvm-1.5.3-175.el7_9.6), kernel: 3.10.0-1160.el7.x86_64, hostname: localhost.localdomain +LC_ALL=C \ +PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin \ +QEMU_AUDIO_DRV=none \ +/usr/libexec/qemu-kvm \ +-name win \ +-S \ +-machine pc-i440fx-rhel7.0.0,accel=kvm,usb=off,dump-guest-core=off \ +-cpu host \ +-m 5120 \ +-realtime mlock=off \ +-smp 4,sockets=4,cores=1,threads=1 \ +-uuid a5efd8ed-fa6f-693c-2202-93183ec18b5e \ +-no-user-config \ +-nodefaults \ +-chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-1-win/monitor.sock,server,nowait \ +-mon chardev=charmonitor,id=monitor,mode=control \ +-rtc base=utc \ +-no-shutdown \ +-boot menu=on,strict=on \ +-device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 \ +-device ahci,id=sata0,bus=pci.0,addr=0x4 \ +-device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 \ +-drive file=/opt/panafs/1374467833802939042/win.img,format=qcow2,if=none,id=drive-sata0-0-0 \ +-device ide-hd,bus=sata0.0,drive=drive-sata0-0-0,id=sata0-0-0,bootindex=1 \ +-drive file=/opt/panafs/13680547561012925528/cn_windows_10_consumer_edition_version_1803_updated_aug_2018_x64_dvd_2cf38490.iso,format=raw,if=none,id=drive-ide0-1-1,readonly=on \ +-device ide-cd,bus=ide.1,unit=1,drive=drive-ide0-1-1,id=ide0-1-1,bootindex=2 \ +-netdev tap,fd=26,id=hostnet0,vhost=on,vhostfd=28 \ +-device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:1d:d8:7d,bus=pci.0,addr=0x3 \ +-netdev tap,fd=29,id=hostnet1 \ +-device e1000,netdev=hostnet1,id=net1,mac=52:54:00:09:bc:30,bus=pci.0,addr=0x9 \ +-chardev pty,id=charserial0 \ +-device isa-serial,chardev=charserial0,id=serial0 \ +-chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-1-win/org.qemu.guest_agent.0,server,nowait \ +-device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ +-device usb-tablet,id=input1,bus=usb.0,port=1 \ +-vnc 0.0.0.0:0 \ +-vga cirrus \ +-device vfio-pci,host=81:00.0,id=hostdev0,bus=pci.0,addr=0x7 \ +-device vfio-pci,host=81:00.1,id=hostdev1,bus=pci.0,addr=0x8 \ +-device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 \ +-msg timestamp=on +2022-09-05 08:08:31.206+0000: Domain id=1 is tainted: host-cpu +char device redirected to /dev/pts/1 (label charserial0) +qemu: terminating on signal 15 from pid 15043 +2022-09-06 02:39:26.089+0000: shutting down, reason=destroyed +2022-09-06 02:39:32.783+0000: starting up libvirt version: 4.5.0, package: 36.el7_9.5 (CentOS BuildSystem <http://bugs.centos.org>, 2021-04-28-13:32:22, x86-01.bsys.centos.org), qemu version: 1.5.3 (qemu +-kvm-1.5.3-175.el7_9.6), kernel: 3.10.0-1160.el7.x86_64, hostname: localhost.localdomain +LC_ALL=C \ +PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin \ +QEMU_AUDIO_DRV=none \ +/usr/libexec/qemu-kvm \ +-name win \ +-S \ +-machine pc-i440fx-rhel7.0.0,accel=kvm,usb=off,dump-guest-core=off \ +-cpu host \ +-m 5120 \ +-realtime mlock=off \ +-smp 4,sockets=4,cores=1,threads=1 \ +-uuid a5efd8ed-fa6f-693c-2202-93183ec18b5e \ +-no-user-config \ +-nodefaults \ +-chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-7-win/monitor.sock,server,nowait \ +-mon chardev=charmonitor,id=monitor,mode=control \ +-rtc base=utc \ +-no-shutdown \ +-boot menu=on,strict=on \ +-device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 \ +-device ahci,id=sata0,bus=pci.0,addr=0x4 \ +-device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 \ +-drive file=/opt/panafs/1374467833802939042/win.img,format=qcow2,if=none,id=drive-sata0-0-0 \ +-device ide-hd,bus=sata0.0,drive=drive-sata0-0-0,id=sata0-0-0,bootindex=1 \ +-drive file=/var/lib/libvirt/images/virtio-win-0.1.217.iso,format=raw,if=none,id=drive-sata0-0-1,media=cdrom,readonly=on \ +-device ide-cd,bus=sata0.1,drive=drive-sata0-0-1,id=sata0-0-1,bootindex=2 \ +-drive file=/opt/panafs/13680547561012925528/cn_windows_10_consumer_edition_version_1803_updated_aug_2018_x64_dvd_2cf38490.iso,format=raw,if=none,id=drive-ide0-1-1,readonly=on \ +-device ide-cd,bus=ide.1,unit=1,drive=drive-ide0-1-1,id=ide0-1-1 \ +-netdev tap,fd=31,id=hostnet0,vhost=on,vhostfd=33 \ +-device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:1d:d8:7d,bus=pci.0,addr=0x3 \ +-netdev tap,fd=34,id=hostnet1 \ +-device e1000,netdev=hostnet1,id=net1,mac=52:54:00:09:bc:30,bus=pci.0,addr=0x9 \ +-chardev pty,id=charserial0 \ +-device isa-serial,chardev=charserial0,id=serial0 \ +-chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-7-win/org.qemu.guest_agent.0,server,nowait \ +-device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ +-device usb-tablet,id=input1,bus=usb.0,port=1 \ +-vnc 0.0.0.0:0 \ +-vga cirrus \ +-device vfio-pci,host=81:00.0,id=hostdev0,bus=pci.0,addr=0x7 \ +-device vfio-pci,host=81:00.1,id=hostdev1,bus=pci.0,addr=0x8 \ +-device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 \ +-msg timestamp=on +2022-09-06 02:39:32.783+0000: Domain id=7 is tainted: host-cpu +char device redirected to /dev/pts/1 (label charserial0) +qemu: terminating on signal 15 from pid 15043 +2022-09-06 02:40:52.065+0000: shutting down, reason=destroyed +2022-09-06 02:41:03.281+0000: starting up libvirt version: 4.5.0, package: 36.el7_9.5 (CentOS BuildSystem <http://bugs.centos.org>, 2021-04-28-13:32:22, x86-01.bsys.centos.org), qemu version: 1.5.3 (qemu +-kvm-1.5.3-175.el7_9.6), kernel: 3.10.0-1160.el7.x86_64, hostname: localhost.localdomain +LC_ALL=C \ +PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin \ +QEMU_AUDIO_DRV=none \ +/usr/libexec/qemu-kvm \ +-name win \ +-S \ +-machine pc-i440fx-rhel7.0.0,accel=kvm,usb=off,dump-guest-core=off \ +-cpu host \ +-m 5120 \ +-realtime mlock=off \ +-smp 4,sockets=4,cores=1,threads=1 \ +-uuid a5efd8ed-fa6f-693c-2202-93183ec18b5e \ +-no-user-config \ +-nodefaults \ +-chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-8-win/monitor.sock,server,nowait \ +-mon chardev=charmonitor,id=monitor,mode=control \ +-rtc base=utc \ +-no-shutdown \ +-boot menu=on,strict=on \ +-device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 \ +-device ahci,id=sata0,bus=pci.0,addr=0x4 \ +-device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 \ +-drive file=/opt/panafs/1374467833802939042/win.img,format=qcow2,if=none,id=drive-sata0-0-0 \ +-device ide-hd,bus=sata0.0,drive=drive-sata0-0-0,id=sata0-0-0,bootindex=1 \ +-drive file=/opt/panafs/13680547561012925528/cn_windows_10_consumer_edition_version_1803_updated_aug_2018_x64_dvd_2cf38490.iso,format=raw,if=none,id=drive-ide0-1-1,readonly=on \ +-device ide-cd,bus=ide.1,unit=1,drive=drive-ide0-1-1,id=ide0-1-1,bootindex=2 \ +-drive file=/var/lib/libvirt/images/virtio-win-0.1.217.iso,format=raw,if=none,id=drive-ide0-0-1,readonly=on \ +-device ide-cd,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1 \ +-netdev tap,fd=31,id=hostnet0,vhost=on,vhostfd=33 \ +-device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:1d:d8:7d,bus=pci.0,addr=0x3 \ +-netdev tap,fd=34,id=hostnet1 \ +-device e1000,netdev=hostnet1,id=net1,mac=52:54:00:09:bc:30,bus=pci.0,addr=0x9 \ +-chardev pty,id=charserial0 \ +-device isa-serial,chardev=charserial0,id=serial0 \ +-chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-8-win/org.qemu.guest_agent.0,server,nowait \ +-device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ +-device usb-tablet,id=input1,bus=usb.0,port=1 \ +-vnc 0.0.0.0:0 \ +-vga cirrus \ +-device vfio-pci,host=81:00.0,id=hostdev0,bus=pci.0,addr=0x7 \ +-device vfio-pci,host=81:00.1,id=hostdev1,bus=pci.0,addr=0x8 \ +-device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 \ +-msg timestamp=on +2022-09-06 02:41:03.281+0000: Domain id=8 is tainted: host-cpu +char device redirected to /dev/pts/1 (label charserial0) +2022-09-06 03:08:33.510+0000: starting up libvirt version: 4.5.0, package: 36.el7_9.5 (CentOS BuildSystem <http://bugs.centos.org>, 2021-04-28-13:32:22, x86-01.bsys.centos.org), qemu version: 1.5.3 (qemu +-kvm-1.5.3-175.el7_9.6), kernel: 3.10.0-1160.el7.x86_64, hostname: localhost.localdomain +LC_ALL=C \ +PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin \ +QEMU_AUDIO_DRV=none \ +/usr/libexec/qemu-kvm \ +-name win \ +-S \ +-machine pc-i440fx-rhel7.0.0,accel=kvm,usb=off,dump-guest-core=off \ +-cpu host \ +-m 5120 \ +-realtime mlock=off \ +-smp 4,sockets=4,cores=1,threads=1 \ +-uuid a5efd8ed-fa6f-693c-2202-93183ec18b5e \ +-display none \ +-no-user-config \ +-nodefaults \ +-chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-1-win/monitor.sock,server,nowait \ +-mon chardev=charmonitor,id=monitor,mode=control \ +-rtc base=utc \ +-no-shutdown \ +-boot menu=on,strict=on \ +-device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 \ +-device ahci,id=sata0,bus=pci.0,addr=0x4 \ +-device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 \ +-drive file=/opt/panafs/1374467833802939042/win.img,format=qcow2,if=none,id=drive-sata0-0-0 \ +-device ide-hd,bus=sata0.0,drive=drive-sata0-0-0,id=sata0-0-0,bootindex=1 \ +-drive file=/opt/panafs/13680547561012925528/cn_windows_10_consumer_edition_version_1803_updated_aug_2018_x64_dvd_2cf38490.iso,format=raw,if=none,id=drive-ide0-1-1,readonly=on \ +-device ide-cd,bus=ide.1,unit=1,drive=drive-ide0-1-1,id=ide0-1-1,bootindex=2 \ +-drive file=/var/lib/libvirt/images/virtio-win-0.1.217.iso,format=raw,if=none,id=drive-ide0-0-1,readonly=on \ +-device ide-cd,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1 \ +-netdev tap,fd=26,id=hostnet0,vhost=on,vhostfd=28 \ +-device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:1d:d8:7d,bus=pci.0,addr=0x3 \ +-netdev tap,fd=29,id=hostnet1 \ +-device e1000,netdev=hostnet1,id=net1,mac=52:54:00:09:bc:30,bus=pci.0,addr=0x9 \ +-chardev pty,id=charserial0 \ +-device isa-serial,chardev=charserial0,id=serial0 \ +-chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-1-win/org.qemu.guest_agent.0,server,nowait \ +-device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ +-device usb-tablet,id=input1,bus=usb.0,port=1 \ +-device vfio-pci,host=81:00.0,id=hostdev0,bus=pci.0,addr=0x7 \ +-device vfio-pci,host=81:00.1,id=hostdev1,bus=pci.0,addr=0x8 \ +-device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 \ +-msg timestamp=on +2022-09-06 03:08:33.510+0000: Domain id=1 is tainted: host-cpu +char device redirected to /dev/pts/1 (label charserial0) +qemu: terminating on signal 15 from pid 15135 +2022-09-06 03:09:18.992+0000: shutting down, reason=destroyed +2022-09-06 03:09:52.805+0000: starting up libvirt version: 4.5.0, package: 36.el7_9.5 (CentOS BuildSystem <http://bugs.centos.org>, 2021-04-28-13:32:22, x86-01.bsys.centos.org), qemu version: 1.5.3 (qemu +-kvm-1.5.3-175.el7_9.6), kernel: 3.10.0-1160.el7.x86_64, hostname: localhost.localdomain +LC_ALL=C \ +PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin \ +QEMU_AUDIO_DRV=spice \ +/usr/libexec/qemu-kvm \ +-name win \ +-S \ +-machine pc-i440fx-rhel7.0.0,accel=kvm,usb=off,dump-guest-core=off \ +-cpu host \ +-m 5120 \ +-realtime mlock=off \ +-smp 4,sockets=4,cores=1,threads=1 \ +-uuid a5efd8ed-fa6f-693c-2202-93183ec18b5e \ +-no-user-config \ +-nodefaults \ +-chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-2-win/monitor.sock,server,nowait \ +-mon chardev=charmonitor,id=monitor,mode=control \ +-rtc base=utc \ +-no-shutdown \ +-boot menu=on,strict=on \ +-device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 \ +-device ahci,id=sata0,bus=pci.0,addr=0x4 \ +-device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 \ +-drive file=/opt/panafs/1374467833802939042/win.img,format=qcow2,if=none,id=drive-sata0-0-0 \ +-device ide-hd,bus=sata0.0,drive=drive-sata0-0-0,id=sata0-0-0,bootindex=1 \ +-drive file=/opt/panafs/13680547561012925528/cn_windows_10_consumer_edition_version_1803_updated_aug_2018_x64_dvd_2cf38490.iso,format=raw,if=none,id=drive-ide0-1-1,readonly=on \ +-device ide-cd,bus=ide.1,unit=1,drive=drive-ide0-1-1,id=ide0-1-1,bootindex=2 \ +-drive file=/var/lib/libvirt/images/virtio-win-0.1.217.iso,format=raw,if=none,id=drive-ide0-0-1,readonly=on \ +-device ide-cd,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1 \ +-netdev tap,fd=26,id=hostnet0,vhost=on,vhostfd=28 \ +-device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:1d:d8:7d,bus=pci.0,addr=0x3 \ +-netdev tap,fd=29,id=hostnet1 \ +-device e1000,netdev=hostnet1,id=net1,mac=52:54:00:09:bc:30,bus=pci.0,addr=0x9 \ +-chardev pty,id=charserial0 \ +-device isa-serial,chardev=charserial0,id=serial0 \ +-chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-2-win/org.qemu.guest_agent.0,server,nowait \ +-device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ +-device usb-tablet,id=input1,bus=usb.0,port=1 \ +-spice port=5900,addr=127.0.0.1,disable-ticketing,seamless-migration=on \ +-device vfio-pci,host=81:00.0,id=hostdev0,bus=pci.0,addr=0x7 \ +-device vfio-pci,host=81:00.1,id=hostdev1,bus=pci.0,addr=0x8 \ +-device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 \ +-msg timestamp=on +2022-09-06 03:09:52.805+0000: Domain id=2 is tainted: host-cpu +char device redirected to /dev/pts/1 (label charserial0) + +(process:102539): Spice-WARNING **: 11:09:53.755: display-channel.c:2435:display_channel_validate_surface: canvas address is 0x55603dfbbb08 for 0 (and is NULL) + + +(process:102539): Spice-WARNING **: 11:09:53.755: display-channel.c:2436:display_channel_validate_surface: failed on 0 + +(process:102539): Spice-WARNING **: 11:09:53.755: red-worker.c:553:destroy_primary_surface: double destroy of primary surface + +(process:102539): Spice-WARNING **: 11:09:53.756: display-channel.c:2159:display_channel_create_surface: condition `!surface->context.canvas' failed +main_channel_link: add main channel client +main_channel_client_handle_pong: net test: latency 0.784000 ms, bitrate 50996015 bps (48.633590 Mbps) +red_qxl_set_cursor_peer: +inputs_connect: inputs channel client create +qemu: terminating on signal 15 from pid 15135 +2022-09-06 03:10:27.167+0000: shutting down, reason=destroyed +2022-09-06 03:10:39.556+0000: starting up libvirt version: 4.5.0, package: 36.el7_9.5 (CentOS BuildSystem <http://bugs.centos.org>, 2021-04-28-13:32:22, x86-01.bsys.centos.org), qemu version: 1.5.3 (qemu +-kvm-1.5.3-175.el7_9.6), kernel: 3.10.0-1160.el7.x86_64, hostname: localhost.localdomain +LC_ALL=C \ +PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin \ +QEMU_AUDIO_DRV=none \ +/usr/libexec/qemu-kvm \ +-name win \ +-S \ +-machine pc-i440fx-rhel7.0.0,accel=kvm,usb=off,dump-guest-core=off \ +-cpu host \ +-m 5120 \ +-realtime mlock=off \ +-smp 4,sockets=4,cores=1,threads=1 \ +-uuid a5efd8ed-fa6f-693c-2202-93183ec18b5e \ +-no-user-config \ +-nodefaults \ +-chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-3-win/monitor.sock,server,nowait \ +-mon chardev=charmonitor,id=monitor,mode=control \ +-rtc base=utc \ +-no-shutdown \ +-boot menu=on,strict=on \ +-device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 \ +-device ahci,id=sata0,bus=pci.0,addr=0x4 \ +-device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 \ +-drive file=/opt/panafs/1374467833802939042/win.img,format=qcow2,if=none,id=drive-sata0-0-0 \ +-device ide-hd,bus=sata0.0,drive=drive-sata0-0-0,id=sata0-0-0,bootindex=1 \ +-drive file=/opt/panafs/13680547561012925528/cn_windows_10_consumer_edition_version_1803_updated_aug_2018_x64_dvd_2cf38490.iso,format=raw,if=none,id=drive-ide0-1-1,readonly=on \ +-device ide-cd,bus=ide.1,unit=1,drive=drive-ide0-1-1,id=ide0-1-1,bootindex=2 \ +-drive file=/var/lib/libvirt/images/virtio-win-0.1.217.iso,format=raw,if=none,id=drive-ide0-0-1,readonly=on \ +-device ide-cd,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1 \ +-netdev tap,fd=26,id=hostnet0,vhost=on,vhostfd=28 \ +-device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:1d:d8:7d,bus=pci.0,addr=0x3 \ +-netdev tap,fd=29,id=hostnet1 \ +-device e1000,netdev=hostnet1,id=net1,mac=52:54:00:09:bc:30,bus=pci.0,addr=0x9 \ +-chardev pty,id=charserial0 \ +-device isa-serial,chardev=charserial0,id=serial0 \ +-chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-3-win/org.qemu.guest_agent.0,server,nowait \ +-device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ +-device usb-tablet,id=input1,bus=usb.0,port=1 \ +-vnc 127.0.0.1:0 \ +-vga cirrus \ +-device vfio-pci,host=81:00.0,id=hostdev0,bus=pci.0,addr=0x7 \ +-device vfio-pci,host=81:00.1,id=hostdev1,bus=pci.0,addr=0x8 \ +-device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 \ +-msg timestamp=on +2022-09-06 03:10:39.556+0000: Domain id=3 is tainted: host-cpu +char device redirected to /dev/pts/1 (label charserial0) +qemu: terminating on signal 15 from pid 15135 +2022-09-06 03:50:33.032+0000: shutting down, reason=destroyed +2022-09-06 03:54:03.923+0000: starting up libvirt version: 4.5.0, package: 36.el7_9.5 (CentOS BuildSystem <http://bugs.centos.org>, 2021-04-28-13:32:22, x86-01.bsys.centos.org), qemu version: 1.5.3 (qemu +-kvm-1.5.3-175.el7_9.6), kernel: 3.10.0-1160.el7.x86_64, hostname: localhost.localdomain +LC_ALL=C \ +PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin \ +QEMU_AUDIO_DRV=none \ +/usr/libexec/qemu-kvm \ +-name win \ +-S \ +-machine pc-i440fx-rhel7.0.0,accel=kvm,usb=off,dump-guest-core=off \ +-cpu host \ +-m 5120 \ +-realtime mlock=off \ +-smp 4,sockets=4,cores=1,threads=1 \ +-uuid a5efd8ed-fa6f-693c-2202-93183ec18b5e \ +-no-user-config \ +-nodefaults \ +-chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-6-win/monitor.sock,server,nowait \ +-mon chardev=charmonitor,id=monitor,mode=control \ +-rtc base=utc \ +-no-shutdown \ +-boot menu=on,strict=on \ +-device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 \ +-device ahci,id=sata0,bus=pci.0,addr=0x4 \ +-device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 \ +-drive file=/opt/panafs/1374467833802939042/win.img,format=qcow2,if=none,id=drive-sata0-0-0 \ +-device ide-hd,bus=sata0.0,drive=drive-sata0-0-0,id=sata0-0-0,bootindex=1 \ +-drive file=/opt/panafs/13680547561012925528/cn_windows_10_consumer_edition_version_1803_updated_aug_2018_x64_dvd_2cf38490.iso,format=raw,if=none,id=drive-ide0-1-1,readonly=on \ +-device ide-cd,bus=ide.1,unit=1,drive=drive-ide0-1-1,id=ide0-1-1,bootindex=2 \ +-drive file=/var/lib/libvirt/images/virtio-win-0.1.217.iso,format=raw,if=none,id=drive-ide0-0-1,readonly=on \ +-device ide-cd,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1 \ +-netdev tap,fd=31,id=hostnet0,vhost=on,vhostfd=36 \ +-device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:1d:d8:7d,bus=pci.0,addr=0x3 \ +-netdev tap,fd=37,id=hostnet1 \ +-device e1000,netdev=hostnet1,id=net1,mac=52:54:00:09:bc:30,bus=pci.0,addr=0x9 \ +-chardev pty,id=charserial0 \ +-device isa-serial,chardev=charserial0,id=serial0 \ +-chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-6-win/org.qemu.guest_agent.0,server,nowait \ +-device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ +-device usb-tablet,id=input1,bus=usb.0,port=1 \ +-vnc 127.0.0.1:0 \ +-vga cirrus \ +-device vfio-pci,host=81:00.0,id=hostdev0,bus=pci.0,addr=0x7 \ +-device vfio-pci,host=81:00.1,id=hostdev1,bus=pci.0,addr=0x8 \ +-device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 \ +-msg timestamp=on +2022-09-06 03:54:03.923+0000: Domain id=6 is tainted: host-cpu +char device redirected to /dev/pts/1 (label charserial0) +2022-09-06 04:16:48.831+0000: starting up libvirt version: 4.5.0, package: 36.el7_9.5 (CentOS BuildSystem <http://bugs.centos.org>, 2021-04-28-13:32:22, x86-01.bsys.centos.org), qemu version: 1.5.3 (qemu +-kvm-1.5.3-175.el7_9.6), kernel: 3.10.0-1160.el7.x86_64, hostname: localhost.localdomain +LC_ALL=C \ +PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin \ +QEMU_AUDIO_DRV=none \ +/usr/libexec/qemu-kvm \ +-name win \ +-S \ +-machine pc-i440fx-rhel7.0.0,accel=kvm,usb=off,dump-guest-core=off \ +-cpu host \ +-m 5120 \ +-realtime mlock=off \ +-smp 4,sockets=4,cores=1,threads=1 \ +-uuid a5efd8ed-fa6f-693c-2202-93183ec18b5e \ +-no-user-config \ +-nodefaults \ +-chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-1-win/monitor.sock,server,nowait \ +-mon chardev=charmonitor,id=monitor,mode=control \ +-rtc base=utc \ +-no-shutdown \ +-boot menu=on,strict=on \ +-device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 \ +-device ahci,id=sata0,bus=pci.0,addr=0x4 \ +-device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 \ +-drive file=/opt/panafs/1374467833802939042/win.img,format=qcow2,if=none,id=drive-sata0-0-0 \ +-device ide-hd,bus=sata0.0,drive=drive-sata0-0-0,id=sata0-0-0,bootindex=1 \ +-drive file=/opt/panafs/13680547561012925528/cn_windows_10_consumer_edition_version_1803_updated_aug_2018_x64_dvd_2cf38490.iso,format=raw,if=none,id=drive-ide0-1-1,readonly=on \ +-device ide-cd,bus=ide.1,unit=1,drive=drive-ide0-1-1,id=ide0-1-1,bootindex=2 \ +-drive file=/var/lib/libvirt/images/virtio-win-0.1.217.iso,format=raw,if=none,id=drive-ide0-0-1,readonly=on \ +-device ide-cd,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1 \ +-netdev tap,fd=26,id=hostnet0,vhost=on,vhostfd=28 \ +-device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:1d:d8:7d,bus=pci.0,addr=0x3 \ +-netdev tap,fd=30,id=hostnet1 \ +-device e1000,netdev=hostnet1,id=net1,mac=52:54:00:09:bc:30,bus=pci.0,addr=0x9 \ +-chardev pty,id=charserial0 \ +-device isa-serial,chardev=charserial0,id=serial0 \ +-chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-1-win/org.qemu.guest_agent.0,server,nowait \ +-device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ +-device usb-tablet,id=input1,bus=usb.0,port=1 \ +-vnc 127.0.0.1:0 \ +-vga cirrus \ +-device vfio-pci,host=81:00.0,id=hostdev0,bus=pci.0,addr=0x7 \ +-device vfio-pci,host=81:00.1,id=hostdev1,bus=pci.0,addr=0x8 \ +-device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 \ +-msg timestamp=on +2022-09-06 04:16:48.831+0000: Domain id=1 is tainted: host-cpu +char device redirected to /dev/pts/1 (label charserial0) +qemu: terminating on signal 15 from pid 15130 +2022-09-06 07:52:07.759+0000: shutting down, reason=destroyed + + + + +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1199 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1199 new file mode 100644 index 000000000..ac6eaef18 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1199 @@ -0,0 +1,10 @@ +Prevent virtual machine memory leakage +Description of problem: +The data written in the virtual machine does not clear the memory after the virtual machine is shut down. When the virtual machine with large memory is started, it may access the data of the previous virtual machine +Steps to reproduce: +1. create a virtual machine with large size memory( 80% of the host's Physical memory) +2. Request all free memory and write the characteristic string in vm +3. restart the vm +4. Request all free memory and query the last character string written +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/120 b/gitlab/issues_text/target_missing/host_missing/accel_missing/120 new file mode 100644 index 000000000..64b1f1f6b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/120 @@ -0,0 +1 @@ +Please provide an option to print the default hardware configuration as command-line options, to make -nodefaults easier to use diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1200 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1200 new file mode 100644 index 000000000..f04478dd9 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1200 @@ -0,0 +1,25 @@ +always zero when query-dirty-rate +Description of problem: +The creation of VM works well(by virt-install), and I can enter it by 'virsh console or ssh'. + +Now, I try to use qemu's feature: calc-dirty-rate. + +But, always get '"dirty-rate":0' when 'query-dirty-rate', occasionally '"dirty-rate":2'. + +At the same time, I run 'mbw'(mbw -t0 -n 1000000 1024 -q) in vm, a memcpy-intensive benchmark. + + +I'm not sure if some configurations of QEMU/KVM are not enabled. + +looking forward to your reply! +Steps to reproduce: +``` +1. virsh qemu-monitor-command centos-huazhang '{"execute":"calc-dirty-rate", "arguments": {"calc-time": 1}}' + + {"return":{},"id":"libvirt-16"} + +2. virsh qemu-monitor-command centos-huazhang1 '{"execute":"query-dirty-rate"}' + + {"return":{"status":"measured","sample-pages":512,"dirty-rate":0,"mode":"page-sampling","start-time":607266,"calc-time":1},"id":"libvirt-17"} + +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1201 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1201 new file mode 100644 index 000000000..92b926cd1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1201 @@ -0,0 +1,10 @@ +Qemu with Windows 10 +Description of problem: +I see a colored screen with flashing cursor and cannot complete Windows installation. +Steps to reproduce: +1. Install `qemu-w64-setup-20220831.exe` on Windows 10 Pro for Workstations 21H2. +2. `cd C:\Program Files\qemu` +3. `qemu-img.exe create -f raw win.img 25600M` +4. `qemu-system-i386w.exe -boot c -m 4096 -hda win.img -cdrom "C:\Users\me\Downloads\Win10_21H2_English_x64.iso"` +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1203 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1203 new file mode 100644 index 000000000..915e51d06 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1203 @@ -0,0 +1,45 @@ +migrate with block-dirty-bitmap (disk size is big enough) can't be finished +Description of problem: +when disk size is big enough(this case using the 4T,related to the bandwith of migration), migrate the VM with block-dirty-bitmap , +the migration will not be finished! +Steps to reproduce: +1. **Start up the source VM,using the commands**: + +/usr/libexec/qemu-kvm -name guest=i-00001C,debug-threads=on -machine pc,accel=kvm,usb=off,dump-guest-core=off -cpu qemu64,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff -m 4096 -smp 4,sockets=1,cores=4,threads=1 -uuid 991c2994-e1c9-48c0-9554-6b23e43900eb -smbios type=1,manufacturer=data,serial=7C1A9ABA-02DD-4E7D-993C-E1CDAB47A19B,family="Virtual Machine" -no-user-config -nodefaults -device sga -rtc base=2022-09-09T02:54:38,clock=host,driftfix=slew -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot menu=on,splash-time=0,strict=on -device pci-bridge,chassis_nr=1,id=pci.1,bus=pci.0,addr=0x6 -device pci-bridge,chassis_nr=2,id=pci.2,bus=pci.0,addr=0xa -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0xb -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0xc -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0xd -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0xe -device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x5 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 -drive if=none,id=drive-ide0-1-1,readonly=on -device ide-cd,bus=ide.1,unit=1,drive=drive-ide0-1-1,id=ide0-1-1,bootindex=2 -drive if=none,id=drive-fdc0-0-0,readonly=on -drive file=/datastore/e88e2b29-cd39-4b21-9629-5ef2458f7ddd/c08fee8e-caf4-4217-ab4d-351a021c2c3d,format=qcow2,if=none,id=drive-virtio-disk0,cache=none -device virtio-blk-pci,scsi=off,num-queues=1,bus=pci.1,addr=0x1,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1,write-cache=on -device usb-tablet,id=input0,bus=usb.0,port=1 -device intel-hda,id=sound0,bus=pci.0,addr=0x3 -device hda-micro,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -sandbox off -device pvpanic,ioport=1285 -msg timestamp=on -qmp tcp:127.0.0.1:4444,server,nowait + +**Start the dst VM using commands as:** + +/usr/libexec/qemu-kvm -name guest=i-00001C,debug-threads=on -machine pc,accel=kvm,usb=off,dump-guest-core=off -cpu qemu64,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff -m 4096 -smp 4,sockets=1,cores=4,threads=1 -uuid 991c2994-e1c9-48c0-9554-6b23e43900eb -smbios type=1,manufacturer=data,serial=7C1A9ABA-02DD-4E7D-993C-E1CDAB47A19B,family="Virtual Machine" -no-user-config -nodefaults -device sga -rtc base=2022-09-09T02:54:38,clock=host,driftfix=slew -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot menu=on,splash-time=0,strict=on -device pci-bridge,chassis_nr=1,id=pci.1,bus=pci.0,addr=0x6 -device pci-bridge,chassis_nr=2,id=pci.2,bus=pci.0,addr=0xa -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0xb -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0xc -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0xd -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0xe -device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x5 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 -drive if=none,id=drive-ide0-1-1,readonly=on -device ide-cd,bus=ide.1,unit=1,drive=drive-ide0-1-1,id=ide0-1-1,bootindex=2 -drive if=none,id=drive-fdc0-0-0,readonly=on -drive file=/datastore/e88e2b29-cd39-4b21-9629-5ef2458f7ddd/c08fee8e-caf4-4217-ab4d-351a021c2c3d,format=qcow2,if=none,id=drive-virtio-disk0,cache=none -device virtio-blk-pci,scsi=off,num-queues=1,bus=pci.1,addr=0x1,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1,write-cache=on -device usb-tablet,id=input0,bus=usb.0,port=1 -device intel-hda,id=sound0,bus=pci.0,addr=0x3 -device hda-micro,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -sandbox off -device pvpanic,ioport=1285 -msg timestamp=on -qmp tcp:127.0.0.1:4444,server,nowait -incoming tcp:0:3333 + +2. **image info as:** + +image: /datastore/e88e2b29-cd39-4b21-9629-5ef2458f7ddd/c08fee8e-caf4-4217-ab4d-351a021c2c3d + +file format: qcow2 +virtual size: 4.0T (4380866641920 bytes) +disk size: 1.0M +cluster_size: 65536 + +Format specific information: + compat: 1.1 + lazy refcounts: false + refcount bits: 16 + corrupt: false + +3. **Add the bitmap :** {"execute":"block-dirty-bitmap-add","arguments":{"node":"drive-virtio-disk0", "name":"bitmap-2022-09-09-16-10-23"}} +4. **set the dirty-bitmaps capability** :{ "execute": "migrate-set-capabilities" , "arguments":{"capabilities":[ {"capability":"dirty-bitmaps","state": true }]}} +5. **start migrate ** { "execute": "migrate", "arguments": { "uri": "tcp:10.49.35.23:3333" } } +6. **quert migrate parameters** {"execute":"query-migrate-parameters"} the retrun message : +{"return": {"cpu-throttle-tailslow": false, "xbzrle-cache-size": 67108864, "cpu-throttle-initial": 20, "announce-max": 550, "decompress-threads": 2, "compress-threads": 8, "compress-level": 1, "multifd-channels": 2, "multifd-zstd-level": 1, "announce-initial": 50, "block-incremental": false, "compress-wait-thread": true, "downtime-limit": 300, "tls-authz": "", "multifd-compression": "none", "announce-rounds": 5, "announce-step": 100, "tls-creds": "", "multifd-zlib-level": 1, "max-cpu-throttle": 99, "max-postcopy-bandwidth": 0, "tls-hostname": "", "throttle-trigger-threshold": 50, "max-bandwidth": 134217728, "x-checkpoint-delay": 20000, "cpu-throttle-increment": 10}} + +7. **query-migrate-capabilities** ： +{"execute":"query-migrate-capabilities"} the retrun message : +{"return": [{"state": false, "capability": "xbzrle"}, {"state": false, "capability": "rdma-pin-all"}, {"state": false, "capability": "auto-converge"}, {"state": false, "capability": "zero-blocks"}, {"state": false, "capability": "compress"}, {"state": false, "capability": "events"}, {"state": false, "capability": "postcopy-ram"}, {"state": false, "capability": "x-colo"}, {"state": false, "capability": "release-ram"}, {"state": false, "capability": "return-path"}, {"state": false, "capability": "pause-before-switchover"}, {"state": false, "capability": "multifd"}, {"state": true, "capability": "dirty-bitmaps"}, {"state": false, "capability": "postcopy-blocktime"}, {"state": false, "capability": "late-block-activate"}, {"state": false, "capability": "x-ignore-shared"}, {"state": false, "capability": "validate-uuid"}, {"state": false, "capability": "background-snapshot"}]} + +8. **query the info of migrate** using the command {"execute":"query-migrate"} +{"return": {"expected-downtime": 0, "status": "active", "setup-time": 64, "total-time": 1320361, "ram": {"total": 4295499776, "postcopy-requests": 0, "dirty-sync-count": 7909410, "multifd-bytes": 0, "pages-per-second": 80, "page-size": 4096, "remaining": 0, "mbps": 3.5006399999999998, "transferred": 430971236, "duplicate": 1048569, "dirty-pages-rate": 66, "skipped": 0, "normal-bytes": 357560320, "normal": 87295}}} + +**the state of migrate is always active ,no matter how long it takes.** +The bug is : migration with big block dirty bitmap can not be finished +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1205 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1205 new file mode 100644 index 000000000..0c3acf8c7 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1205 @@ -0,0 +1,7 @@ +Cannot use `-serial stdio` on macbook pro, apple silicon +Description of problem: +When I run the command above, it will show below: +``` +(qemu) qemu-system-aarch64: -serial stdio: cannot use stdio by multiple character devices +qemu-system-aarch64: -serial stdio: could not connect serial device to character backend 'stdio' +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1207 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1207 new file mode 100644 index 000000000..b12c9f6cb --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1207 @@ -0,0 +1,3 @@ +Cannot use qcow2 to create a VM on apple silicon macbook +Description of problem: +Nothing to output when I input the command above. And it seems not to boot successfully. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1209 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1209 new file mode 100644 index 000000000..f581594cb --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1209 @@ -0,0 +1,5 @@ +Optionally do not clear the screen when starting a VM +Additional information: +``` +QEMU emulator version 6.2.0 (qemu-6.2.0-14.fc36) +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/121 b/gitlab/issues_text/target_missing/host_missing/accel_missing/121 new file mode 100644 index 000000000..4ebd41b96 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/121 @@ -0,0 +1 @@ +multiprocess program gets incorrect results with qemu arm-linux-user diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1210 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1210 new file mode 100644 index 000000000..9211b62f4 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1210 @@ -0,0 +1,8 @@ +qemu segfaults on PNG screendump +Description of problem: +Attempting to produce a screendump via the monitor in the PNG format leads to a segmentation fault (but the screen dump is produced correctly). +Steps to reproduce: +1. Launch QEMU +2. Go to the monitoring screen () +3. execute the command: `screendump /tmp/dump.png -f png` +4. observe the crash (segfault) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1211 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1211 new file mode 100644 index 000000000..e8504f789 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1211 @@ -0,0 +1,7 @@ +Bad fonts in "cirrus" VGA card. +Description of problem: +Similar to #988. Fixed by set "no_bitblt" and "sw_cursor" in XF86Config file. +Steps to reproduce: +Similar to #988. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1212 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1212 new file mode 100644 index 000000000..8a1230572 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1212 @@ -0,0 +1,9 @@ +A NULL pointer dereference issue in elf2dmp +Description of problem: +SIGSEGV in get_pml4e for it didn't handle NULL result properly. +Steps to reproduce: +1.launch qemu and running "gab attach -p $QEMU_PID", run "gcore" inside gdb to generate coredump +2../elf2dmp ./core.111 ./out.dmp +3.get segemantation fault +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1213 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1213 new file mode 100644 index 000000000..d9a485e7e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1213 @@ -0,0 +1,43 @@ +7.1.0 - NSIS Installer file issues +Description of problem: + + +Please check the screenshot relative to Window program list + +**Problem n. 1 (standard icon)** + +The icon rlative to QEMU is not graphic icon but starndrd udenfiend icon + +**Problem n. 2 (author missing)** + +Author info is missing + +**Problem n. 3 (installer date is not updated)** + +When you upgrade QEM the installation date not reflect last update but first installation (ex. version 7.1.0 with date of 2021). + +Note: all issues are relative to NSIS installer script. + +**Uninstaller icon** + +It seems that + +**!define MUI_UNICON "${SRCDIR}\pc-bios\qemu-nsis.ico"**__ + +didn't work. + +Please check here + +https://nsis.sourceforge.io/Add_uninstall_information_to_Add/Remove_Programs + +Please try to add in uninsaller section + + WriteRegStr HKLM "${UNINST_KEY}" "DisplayIcon" "${SRCDIR}\pc-bios\qemu-nsis.ico" + +**Missing author info in uninstall view** + + ; Write the uninstall keys for Windows + WriteRegStr HKLM "${UNINST_KEY}" "DisplayName" "QEMU" + WriteRegStr HKLM "${UNINST_KEY}" "Publisher" "QEMU crew" + +Replace "QEMU crew" with text that you like. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1214 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1214 new file mode 100644 index 000000000..b547d0d5d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1214 @@ -0,0 +1 @@ +qemu-riscv64 mmap will exhaust all physical memory diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1215 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1215 new file mode 100644 index 000000000..f8467f765 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1215 @@ -0,0 +1,72 @@ +block-stream qmp command regression in 7.1.0 +Description of problem: +After `block-stream` qmp commands, guest was hanged when using `iothread` option. +According to b1e1af3, there are some change at drain blockdev subtree and strong reference to base node. +We couldn't produce this issue when we reverted the commit. +It seems to be raised by racing acquiring aio_lock between iothread and main thread. +Steps to reproduce: +1. Start Guest with upper command. +2. After started, operate `block-stream` command to qmp socket +``` +echo '{"execute":"qmp_capabilities"}{ + "execute":"block-stream", + "arguments":{ + "job-id":"hangTest", + "device":"vdaFile" + } +}' | sudo nc -U /var/run/monitor_a9b43742-9117-4aae-8887-24bdb017ec20 -N +``` +Additional information: +- gdb debug stack +``` +Thread 1 (Thread 0x7fcfaed84600 (LWP 162409) "qemu-system-x86"): +#0 0x00007fcfaf108e7e in __ppoll (fds=0x5634a9b6b240, nfds=1, timeout=<optimized out>, timeout@entry=0x0, sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:42 +#1 0x00005634a7be22dd in ppoll (__ss=0x0, __timeout=0x0, __nfds=<optimized out>, __fds=<optimized out>) at /usr/include/x86_64-linux-gnu/bits/poll2.h:64 +#2 0x00005634a7bc02c9 in fdmon_poll_wait (ctx=0x5634a990eec0, ready_list=0x7ffcb2ce4fb8, timeout=-1) at ../util/fdmon-poll.c:80 +#3 0x00005634a7bbf9c9 in aio_poll (ctx=ctx@entry=0x5634a990eec0, blocking=blocking@entry=true) at ../util/aio-posix.c:660 +#4 0x00005634a7ac849d in bdrv_parent_drained_end_single (c=c@entry=0x5634a9b4bb30) at ../block/io.c:76 +#5 0x00005634a7a98240 in bdrv_replace_child_noperm (childp=0x5634a9b61240, new_bs=0x0, free_empty_child=<optimized out>) at ../block.c:2910 +#6 0x00005634a7a987fe in bdrv_replace_child_tran (childp=<optimized out>, new_bs=<optimized out>, tran=<optimized out>, free_empty_child=<optimized out>) at ../block.c:2444 +#7 0x00005634a7a988bc in bdrv_remove_file_or_backing_child (bs=bs@entry=0x5634a9b5d1f0, child=child@entry=0x5634a9b4bb30, tran=tran@entry=0x5634aa415fc0) at ../block.c:5155 +#8 0x00005634a7a9fac6 in bdrv_remove_file_or_backing_child (tran=0x5634aa415fc0, child=0x5634a9b4bb30, bs=0x5634a9b5d1f0) at ../block.c:5133 +#9 bdrv_set_file_or_backing_noperm (parent_bs=parent_bs@entry=0x5634a9b5d1f0, child_bs=child_bs@entry=0x0, is_backing=is_backing@entry=true, tran=tran@entry=0x5634aa415fc0, errp=errp@entry=0x7ffcb2ce5150) at ../block.c:3412 +#10 0x00005634a7a9fd04 in bdrv_set_backing_noperm (errp=0x7ffcb2ce5150, tran=0x5634aa415fc0, backing_hd=0x0, bs=0x5634a9b5d1f0) at ../block.c:3449 +#11 bdrv_set_backing_hd (bs=bs@entry=0x5634a9b5d1f0, backing_hd=backing_hd@entry=0x0, errp=errp@entry=0x7ffcb2ce5150) at ../block.c:3461 +#12 0x00005634a7b25e19 in stream_prepare (job=0x5634a9e83da0) at ../block/stream.c:85 +#13 0x00005634a7aa922e in job_prepare (job=0x5634a9e83da0) at ../job.c:837 +#14 job_txn_apply (fn=<optimized out>, job=0x5634a9e83da0) at ../job.c:158 +#15 job_do_finalize (job=0x5634a9e83da0) at ../job.c:854 +#16 0x00005634a7aa9726 in job_exit (opaque=0x5634a9e83da0) at ../job.c:941 +#17 0x00005634a7bd26b4 in aio_bh_call (bh=0x7fcfa0824010) at ../util/async.c:150 +#18 aio_bh_poll (ctx=ctx@entry=0x5634a990eec0) at ../util/async.c:178 +#19 0x00005634a7bbf602 in aio_dispatch (ctx=0x5634a990eec0) at ../util/aio-posix.c:421 +#20 0x00005634a7bd22f2 in aio_ctx_dispatch (source=<optimized out>, callback=<optimized out>, user_data=<optimized out>) at ../util/async.c:320 +#21 0x00007fcfaf3c0d1b in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 +#22 0x00005634a7bde7c0 in glib_pollfds_poll () at ../util/main-loop.c:297 +#23 os_host_main_loop_wait (timeout=114194793) at ../util/main-loop.c:320 +#24 main_loop_wait (nonblocking=nonblocking@entry=0) at ../util/main-loop.c:596 +#25 0x00005634a784fdc3 in qemu_main_loop () at ../softmmu/runstate.c:734 +#26 0x00005634a769f9e0 in qemu_main (argc=<optimized out>, argv=<optimized out>, envp=<optimized out>) at ../softmmu/main.c:38 +--Type <RET> for more, q to quit, c to continue without paging-- +#27 0x00007fcfaf019d90 in __libc_start_call_main (main=main@entry=0x5634a769b0c0 <main>, argc=argc@entry=56, argv=argv@entry=0x7ffcb2ce54c8) at ../sysdeps/nptl/libc_start_call_main.h:58 +#28 0x00007fcfaf019e40 in __libc_start_main_impl (main=0x5634a769b0c0 <main>, argc=56, argv=0x7ffcb2ce54c8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffcb2ce54b8) at ../csu/libc-start.c:392 +#29 0x00005634a769f905 in _start () +``` +- iothread gdb stack +``` +Thread 3 (Thread 0x7fcfae47e640 (LWP 162411) "IO iothread1"): +#0 futex_wait (private=0, expected=2, futex_word=0x5634a9b49620) at ../sysdeps/nptl/futex-internal.h:146 +#1 __GI___lll_lock_wait (futex=futex@entry=0x5634a9b49620, private=0) at ./nptl/lowlevellock.c:49 +#2 0x00007fcfaf0880dd in lll_mutex_lock_optimized (mutex=0x5634a9b49620) at ./nptl/pthread_mutex_lock.c:48 +#3 ___pthread_mutex_lock (mutex=mutex@entry=0x5634a9b49620) at ./nptl/pthread_mutex_lock.c:128 +#4 0x00005634a7bc25b8 in qemu_mutex_lock_impl (mutex=0x5634a9b49620, file=0x5634a7da2997 "../util/async.c", line=682) at ../util/qemu-thread-posix.c:88 +#5 0x00005634a7bd24a5 in aio_context_acquire (ctx=0x5634a9b495c0) at ../util/async.c:682 +#6 co_schedule_bh_cb (opaque=0x5634a9b495c0) at ../util/async.c:520 +#7 0x00005634a7bd26b4 in aio_bh_call (bh=0x5634a9b494a0) at ../util/async.c:150 +#8 aio_bh_poll (ctx=ctx@entry=0x5634a9b495c0) at ../util/async.c:178 +#9 0x00005634a7bbf754 in aio_poll (ctx=0x5634a9b495c0, blocking=blocking@entry=true) at ../util/aio-posix.c:712 +#10 0x00005634a7a9392a in iothread_run (opaque=opaque@entry=0x5634a9998700) at ../iothread.c:67 +#11 0x00005634a7bc21d1 in qemu_thread_start (args=<optimized out>) at ../util/qemu-thread-posix.c:504 +#12 0x00007fcfaf084b43 in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:442 +#13 0x00007fcfaf116a00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1216 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1216 new file mode 100644 index 000000000..4aed8f366 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1216 @@ -0,0 +1,9 @@ +System crashes/hangs when running qemu-img convert +Description of problem: +**Upon running the above command, the Virtual Machine simply crashes and is irrecoverable** +Steps to reproduce: +1. **Start Ubuntu 20.04 or SIFT Workstation** +2. **sudo apt-get install qemu** +3. **qemu-img convert -O raw JEA.vmdk JEA.vmdk.raw** +Additional information: +I have also run this on macOS and it just hangs and never completes diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1218 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1218 new file mode 100644 index 000000000..a96678445 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1218 @@ -0,0 +1,20 @@ +bitmap lost when create snapshot using blockdev-snapshot-sync function +Description of problem: +bitmap will be lost when using the blockdev-snapshot-sync qmp command to create external snapshot. +if we create snapshot with the bitmap ,we have to start our incremental backup chain from a new full-backup. +Steps to reproduce: +1. start the qemu : +qemu-system-x86_64 -name guest=i-00001C,debug-threads=on -machine pc,dump-guest-core=off -cpu qemu64,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff -m 4096 -smp 4,sockets=1,cores=4,threads=1 -uuid 991c2994-e1c9-48c0-9554-6b23e43900eb -smbios type=1,manufacturer=data,serial=7C1A9ABA-02DD-4E7D-993C-E1CDAB47A19B,family="Virtual Machine" -no-user-config -nodefaults -device sga -rtc base=2022-09-09T02:54:38,clock=host,driftfix=slew -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot menu=on,splash-time=0,strict=on -device pci-bridge,chassis_nr=1,id=pci.1,bus=pci.0,addr=0x6 -device pci-bridge,chassis_nr=2,id=pci.2,bus=pci.0,addr=0xa -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x8 -device ich9-usb-ehci1,id=usb1,bus=pci.0,addr=0x9 -device piix4-usb-uhci,id=usb2,bus=pci.0,addr=0xb -device qemu-xhci,id=usb3,bus=pci.0,addr=0xc -device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x5 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 -drive if=none,id=drive-ide0-1-1,readonly=on -device ide-cd,bus=ide.1,unit=1,drive=drive-ide0-1-1,id=ide0-1-1,bootindex=2 -drive if=none,id=drive-fdc0-0-0,readonly=on -drive file=/datastore//c08fee8e-caf4-4217-ab4d-351a021c2c3d,format=qcow2,if=none,id=drive-virtio-disk0,cache=none -device virtio-blk-pci,scsi=off,num-queues=1,bus=pci.1,addr=0x1,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1,write-cache=on -device usb-tablet,id=input0,bus=usb.0,port=1 -device intel-hda,id=sound0,bus=pci.0,addr=0x3 -device hda-micro,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -sandbox off -device pvpanic,ioport=1285 -msg timestamp=on -qmp tcp:127.0.0.1:4444,server,nowait + +2. {"execute":"block-dirty-bitmap-add","arguments":{"node":"drive-virtio-disk0", "name":"bitmap-2022-09-19-16-10-23"}} + +3. {"execute":"query-block"} and the result: + {"return": [{"io-status": "ok", "device": "drive-ide0-1-1", "locked": false, "removable": true, "qdev": "ide0-1-1", "tray_open": false, "type": "unknown"}, {"device": "drive-fdc0-0-0", "locked": false, "removable": true, "type": "unknown"}, {"io-status": "ok", "device": "drive-virtio-disk0", "locked": false, "removable": false, "inserted": {"iops_rd": 0, "detect_zeroes": "off", "image": {"virtual-size": 21474836480, "filename": "/datastore//c08fee8e-caf4-4217-ab4d-351a021c2c3d", "cluster-size": 65536, "format": "qcow2", "actual-size": 200704, "format-specific": {"type": "qcow2", "data": {"compat": "1.1", "compression-type": "zlib", "lazy-refcounts": false, "refcount-bits": 16, "corrupt": false, "extended-l2": false}}, "dirty-flag": false}, "iops_wr": 0, "ro": false, "node-name": "#block173", "backing_file_depth": 0, "drv": "qcow2", "iops": 0, "bps_wr": 0, "write_threshold": 0, "**dirty-bitmaps**": [{"name": "bitmap-2022-09-19-16-10-23", "recording": true, "persistent": false, "busy": false, "granularity": 65536, "count": 0}], "encrypted": false, "bps": 0, "bps_rd": 0, "cache": {"no-flush": false, "direct": true, "writeback": true}, "file": "/datastore//c08fee8e-caf4-4217-ab4d-351a021c2c3d"}, "qdev": "/machine/peripheral/virtio-disk0/virtio-backend", "type": "unknown"}]} + +4. {"execute":"blockdev-snapshot-sync","arguments":{"device": "drive-virtio-disk0", "snapshot-file": "/datastore/c08fee8e-caf4-4217-ab4d-351a021c2c3d-actice", "format": "qcow2"}} +5. {"execute":"query-block"} and the result: + {"return": [{"io-status": "ok", "device": "drive-ide0-1-1", "locked": false, "removable": true, "qdev": "ide0-1-1", "tray_open": false, "type": "unknown"}, {"device": "drive-fdc0-0-0", "locked": false, "removable": true, "type": "unknown"}, {"io-status": "ok", "device": "drive-virtio-disk0", "locked": false, "removable": false, "inserted": {"iops_rd": 0, "detect_zeroes": "off", "image": {"backing-image": {"virtual-size": 21474836480, "filename": "/datastore//c08fee8e-caf4-4217-ab4d-351a021c2c3d", "cluster-size": 65536, "format": "qcow2", "actual-size": 200704, "format-specific": {"type": "qcow2", "data": {"compat": "1.1", "compression-type": "zlib", "lazy-refcounts": false, "refcount-bits": 16, "corrupt": false, "extended-l2": false}}, "dirty-flag": false}, "backing-filename-format": "qcow2", "virtual-size": 21474836480, "filename": "/datastore/c08fee8e-caf4-4217-ab4d-351a021c2c3d-actice", "cluster-size": 65536, "format": "qcow2", "actual-size": 200704, "format-specific": {"type": "qcow2", "data": {"compat": "1.1", "compression-type": "zlib", "lazy-refcounts": false, "refcount-bits": 16, "corrupt": false, "extended-l2": false}}, "full-backing-filename": "/datastore//c08fee8e-caf4-4217-ab4d-351a021c2c3d", "backing-filename": "/datastore//c08fee8e-caf4-4217-ab4d-351a021c2c3d", "dirty-flag": false}, "iops_wr": 0, "ro": false, "node-name": "#block618", "backing_file_depth": 1, "drv": "qcow2", "iops": 0, "bps_wr": 0, "write_threshold": 0, "backing_file": "/datastore//c08fee8e-caf4-4217-ab4d-351a021c2c3d", "encrypted": false, "bps": 0, "bps_rd": 0, "cache": {"no-flush": false, "direct": true, "writeback": true}, "file": "/datastore/c08fee8e-caf4-4217-ab4d-351a021c2c3d-actice"}, "qdev": "/machine/peripheral/virtio-disk0/virtio-backend", "type": "unknown"}]} + +we lost the bitmap bitmap-2022-09-19-16-10-23 +Additional information: +the bitmap attach the active bs, when changing the active bs ,the bitmap will be lost... diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1219 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1219 new file mode 100644 index 000000000..f6afdc782 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1219 @@ -0,0 +1,13 @@ +--enable-kvm not work for riscv64-softmmu +Description of problem: +I want to enable kvm for qemu-system-riscv64, so I compile it with `--enable-kvm` as above. But the log shows + +```sh + Targets and accelerators + KVM support : NO +``` + +And also compiled qemu-system-riscv64 does not support kvm. +Steps to reproduce: +1. clone the repo +2. `./configure --target-list=riscv64-softmmu --enable-kvm` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/122 b/gitlab/issues_text/target_missing/host_missing/accel_missing/122 new file mode 100644 index 000000000..ed08f19f1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/122 @@ -0,0 +1 @@ +linux-user does not check PROT_EXEC diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1220 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1220 new file mode 100644 index 000000000..e84c71773 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1220 @@ -0,0 +1,16 @@ +when migrate,I unplugged the disk, why can't I force cancel the job task use qmp +Description of problem: +when migrate,I unplugged the disk,the block job will hung,but why can't I force cancel the job task +Steps to reproduce: +1.migrate a guset to another host with non-share disk (iscsi) + +2.unplug the disk + +3.then force cancel the block job task + + +but it not work,the cancle handle is not work + + + + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1221 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1221 new file mode 100644 index 000000000..f0c3614d9 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1221 @@ -0,0 +1,29 @@ +qga return "frozen" when vm just been created from snapfile +Steps to reproduce: +1. virsh create lisa.xml +Domain lisa created from lisa.xml + +2. virsh domblklist lisa + vda /mnt/a/b/srv.qcow2 + +3. virsh snapshot-create-as lisa --disk-only --diskspec vda,file=/tmp/f1,snapfile=/tmp/sp1 --no-metadata --quiesce +Domain snapshot 20220919165217 created + +4. virsh shutdown lisa +Domain lisa is being shutdown + +5. modify lisa.xml: replace /mnt/a/b/srv/qcow2 with /tmp/sp1 + +6. virsh create lisa.xml +Domain lisa created from lisa.xml + +7. virsh domblklist lisa + vda /tmp/sp1 + +8. virsh qemu-agent-command lisa '{"execute":"guest-fsfreeze-status"}' +{"return":"frozen"} + +9. virsh snapshot-create-as lisa --disk-only --diskspec vda,file=/tmp/f2,snapfile=/tmp/sp2 --no-metadata --quiesce +error: internal error: unable to execute QEMU agent command 'guest-fsfreeze-freeze': The command guest-fsfreeze-freeze has been disabled for this instance +Additional information: +Is "frozen" a normal value in step8? If not, what's the best way to avoid this? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1222 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1222 new file mode 100644 index 000000000..ed22b50b8 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1222 @@ -0,0 +1,21 @@ +/proc/self/exe not handled in execve +Description of problem: +I am submitting this issue to track an issue for which it seems there have been a couple of patchsets (unsuccessfully) submitted. I am not able to give a detailed analysis of the problem as I am not aware of exactly what the issue is - I am raising this issue to attempt to bring one of these changes upstream as it seems there is a genuine bug here (hence multiple attempts to fix) but no tracking bug or attention. It's also causing my project to require a custom fork of qemu just for this. + +My (laymans) understanding of the bug is that golang can escape the emulation environment when it execs something to do with `execve /proc/self/exe`. Here is an excerpt from my internal docs from someone who has left the project, sorry I cannot be of more use... + +> Unfortunately, to run podman/buildah/skopeo using qemu-user (which just runs a single binary +> emulated, as opposed to qemu-system which runs an entire system but is harder to automate in +> toolchains) we need these patches because of a peculiar thing many golang applications do. They +> re-execute themselves using the execve syscall using /proc/self/exe as the executable. In +> non-emulated contexts this is fine, but in emulated contexts /proc/self/exe is actually the +> top-level emulator process and _not_ podman/buildah/skopeo. This causes all container storage +> operations to mysteriously fail, because the wrong binary is being executed. This issue was quite +> difficult to root cause. +Additional information: +Old patchsets that seem to be trying to fix this: +- http://next.patchew.org/QEMU/20210531055019.10149-1-yamamoto@midokura.com/20210531055019.10149-2-yamamoto@midokura.com/ +- https://patchew.org/QEMU/20190916155545.29928-1-olivier.dion@polymtl.ca/ +- https://patchew.org/QEMU/20190807135458.32440-1-dion@linutronix.de/ + +It seems that this github issue: https://github.com/golang/go/issues/42080 references the same issue. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1223 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1223 new file mode 100644 index 000000000..e4710f8d9 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1223 @@ -0,0 +1,11 @@ +When the disk is offline, why does the migration not time out and the virtual machine keeps hanging +Description of problem: +I want to the migrate end auto after the disk is offline +Steps to reproduce: +1.migrate to other host + +2.Manually construct disk offline when migrating + +3.the vm is hangs,and migrate wait for the disk recovery,i need to it timeout and report the failed migration +rather than hangs ,what should i do + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1225 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1225 new file mode 100644 index 000000000..bc74c022f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1225 @@ -0,0 +1 @@ +Can't update to Windows 11 22H2 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1226 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1226 new file mode 100644 index 000000000..affb40aab --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1226 @@ -0,0 +1,25 @@ +wheel-axis=false does not get applied at hardware init stage +Description of problem: +`-device virtio-tablet,id=touch0,wheel-axis=false` does not get applied at initalization stage, causing android to see it and treat the device as a pointer instead of a tablet. it seems to look for the prop at init stage, I have verified that this is an issue by fixing it with a quick hack below. ~~setting `-device virtio-tablet,id=touch0,wheel-axis=true` will still work fine and cause android to pick it up as a pointer again~~ + + +EDIT: It does not seem to work actually. if set when the default is set to false +Steps to reproduce: +1. Boot android based VM +2. test an app that forces touch only over pointer +Additional information: +``` +diff --git a/hw/input/virtio-input-hid.c b/hw/input/virtio-input-hid.c +index a7a244a95d..3175f9c7d5 100644 +--- a/hw/input/virtio-input-hid.c ++++ b/hw/input/virtio-input-hid.c +@@ -477,7 +477,7 @@ static struct virtio_input_config virtio_tablet_config_v2[] = { + }; + + static Property virtio_tablet_properties[] = { +- DEFINE_PROP_BOOL("wheel-axis", VirtIOInputHID, wheel_axis, true), ++ DEFINE_PROP_BOOL("wheel-axis", VirtIOInputHID, wheel_axis, false), + DEFINE_PROP_END_OF_LIST(), + }; + +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1227 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1227 new file mode 100644 index 000000000..468b8b045 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1227 @@ -0,0 +1 @@ +Guest Agent not waiting for Linux services to stop during shutdown diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1228 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1228 new file mode 100644 index 000000000..42eb259b0 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1228 @@ -0,0 +1,43 @@ +-display curses only recognizes escape characters if pressed very quickly +Description of problem: +The system start and runs perfectly fine, but when I try to exit the escape commands does not seem to work. + +I have tried all the ones from here: +https://www.qemu.org/docs/master/system/keys.html +https://www.qemu.org/docs/master/system/mux-chardev.html + +When using the graphical display, the escape characters works as expected but when using -display curses, they do not. +Steps to reproduce: +1. Start qemu with the command provided +2. Try to exit using ctrl + x a - Not working +3. Try to exit using alt + 2 - Not working + +The same issues occurs when running qemu on a Linux machine (Ubunt) via Visual Studio Code / ssh. + +I'm guessing this is a macOS specific issue or maybe something to do with my Locale (sv-SE). +Additional information: +Linux 0.01 build: +https://github.com/mariuz/linux-0.01 + +**Tests using showkey** + +Alt + 2 from mobile ssh client (Terminus) -> Ubuntu machine +``` +^[2 27 0033 0x1b + 50 0062 0x32 +``` + +Option + 2 from macOS Terminal + ssh -> Ubuntu machine +``` +@ 64 0100 0x40 +``` + +Esc + 2 from macOS Terminal + ssh -> Ubuntu machine +``` +^[ 27 0033 0x1b +2 50 0062 0x32 +``` + +**Update** + +It seems to work if I press ESC + 2 at exactly the same time. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1229 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1229 new file mode 100644 index 000000000..dec12cd14 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1229 @@ -0,0 +1,9 @@ +there is no Makefile.objs in migration dir，how can I do if I need to edit it? +Description of problem: + +Steps to reproduce: +1. +2. +3. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/123 b/gitlab/issues_text/target_missing/host_missing/accel_missing/123 new file mode 100644 index 000000000..8071656b6 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/123 @@ -0,0 +1 @@ +qemu-cris segfaults upon loading userspace binary diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1231 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1231 new file mode 100644 index 000000000..a60b19106 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1231 @@ -0,0 +1,13 @@ +Loading migration of VM in debug state fails (with potential solution) +Description of problem: +``` +qemu-system-x86_64: invalid runstate transition: 'inmigrate' -> 'debug' +Aborted (core dumped) +``` +Steps to reproduce: +1. Start VM with gdbstub +2. Pause VM via gdbstub +3. Save migration snapshot via HMP: `migrate "exec: gzip -c > foo.gz"` +4. Start new QEMU instance from snapshot by adding these args to whatever you used to launch QEMU: `-incoming "exec: gzip -c -d foo.gz"` +Additional information: +This can be fixed by adding `{ RUN_STATE_INMIGRATE, RUN_STATE_DEBUG },` to `runstate_transitions_def` in `softmmu/runstate.c`. It's not clear if there are any negative ramifications of this, but it seems to work for me? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1232 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1232 new file mode 100644 index 000000000..78c2bc960 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1232 @@ -0,0 +1,13 @@ +AArch64 virt can't write to memory related to gicv3 +Description of problem: +According to the info in generated dtb, the memory-mapped registers of gicv3-distributor have a base addr, which is `0x0800_0000`. +And I have checked the validity by reading `gicd_typer`, which means the base addr is right. + +But when I want to configure the gicv3-distributor (like changing `gicd_ctlr`), the value is not changed, keeping the default value. The same thing happens on any register of GICD in my machine. + +**Even I write to this memory by gdb `set` command, the value is also unchangeable.** + +The addr of `gicd_ctlr` should be `0x0800_0000`(offset=0), which should be readable and writable, isn't it? + +I try to modify the value of this addr in assembly as soon as the **machine starts, without enabling MMU**. +This problem should be easier to reproduce. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1233 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1233 new file mode 100644 index 000000000..2f5c1c83e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1233 @@ -0,0 +1 @@ +is there a roadmap about when riscv-v extension will be implemented?? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1234 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1234 new file mode 100644 index 000000000..11ee92120 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1234 @@ -0,0 +1,3 @@ +Migration: Device state not saved for msmouse/chardevs +Additional information: +This missing feature was discovered while fixing msmouse here: https://patchew.org/QEMU/20220908173120.16779-1-arwed.meyer@gmx.de/20220908173120.16779-2-arwed.meyer@gmx.de/ diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1235 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1235 new file mode 100644 index 000000000..1ee5585af --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1235 @@ -0,0 +1,180 @@ +Using packer and plugin qemu in the json file to create a RHEL 8.4 guest kvm vm, but ssh timeout error coming, but it is running fine in RHEL 7.9 +Description of problem: +I have RHEL 8.5 as the KVM host. I want to create a guest vm of RHEL 8.4 through packer type qemu and have a json file where all the configurations are mentioned. + +{ + +“builders”: [ + +{ + +“type”: “qemu”, + +“iso_url”: “/var/lib/libvirt/images/test.iso”, + +“iso_checksum”: “md5:3959597d89e8c20d58c4514a7cf3bc7f”, + +“output_directory”: “/var/lib/libvirt/images/iso-dir/test”, + +“disk_size”: “55G”, + +“headless”: “true”, + +“qemuargs”: [ + + [ + + "-m", + + "4096" + + ], + + [ + + "-smp", + + "2" + + ] +], + +“format”: “qcow2”, + +“shutdown_command”: “echo ‘nonrootuser’ | sudo -S shutdown -P now”, + +“accelerator”: “kvm”, + +“ssh_username”: “nonrootuser”, + +“ssh_password”: “********”, + +“ssh_timeout”: “20m”, + +“vm_name”: “test”, + +“net_device”: “virtio-net”, + +“disk_interface”: “virtio”, + +“http_directory”: “/home/azureuser/http”, + +“boot_wait”: “10s”, + +“boot_command”: [ + +“e inst.ks=http://{{ .HTTPIP }}:{{ .HTTPPort }}/anaconda-ks.cfg” + +] + +} + +], + +“provisioners”: + +[ + +{ + + "type": "file", + + "source": "/home/azureuser/service_status_check.sh", + + "destination": "/tmp/service_status_check.sh" + +}, + +{ + + "type": "file", + + "source": "/home/azureuser/service_check.sh", + + "destination": "/tmp/service_check.sh" + +}, + +{ + + "type": "file", + + "source": "/home/azureuser/azure.sh", + + "destination": "/tmp/azure.sh" + +}, + +{ + + + "type": "file", + + "source": "/home/azureuser/params.cfg", + + "destination": "/tmp/params.cfg" + +}, + + + +{ + + "type": "shell" , + + + + "execute_command": "echo 'siedgerexuser' | {{.Vars}} sudo -E -S bash '{{.Path}}'", + + + + "inline": [ +"echo copying" , "cp /tmp/params.cfg /root/", + "sudo ls -lrt /root/params.cfg", + "sudo ls -lrt /opt/scripts/" + ], + + + "inline_shebang": "/bin/sh -x" + +}, + +{ + + "type": "shell", + + "pause_before": "5s", + "expect_disconnect": true , + + "inline": [ + "echo runningconfigurescript" , "sudo sh /opt/scripts/configure-env.sh" + + ] + +}, + +{ + + "type": "shell", + + "pause_before": "200s", + + "inline": [ + + "sudo sh /tmp/service_check.sh", + "sudo sh /tmp/azure.sh" + + ] + +} +] + +} + +It is working fine in rhel 7.9, but the same thing giving ssh timeout error in RHEL 8.4. + +But when i am creating guest vm with virt-install it is able to create a vm and i am able to see it in cockpit web ui, but when i initiate packer build with qemu plugin then giving ssh timeout error it is not visible in cockpit UI, so not able to see where the guest vm created get stuck. + +Can anyone please help me to fix this issue where why vm not able to come up and also why qemu created vm not visible in cockpit web ui as that will be really helpful while debugging +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1236 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1236 new file mode 100644 index 000000000..4247eab73 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1236 @@ -0,0 +1,46 @@ +blockdev fixed vhdx trying to reserve space, also misleading error, Could not open file: Invalid argument +Description of problem: +The qemu-storage-daemon/other qemu commands will not start and will choke on requiring vhdx driver for the blockdev layer. +Opening a fixed-virtual-disk like fixed-vhdx should not reserve extra space, and should only overwrite as all blocks are already allocated. +Steps to reproduce: +1. Ensure that a partition size is such that after deciding a fixed-vhdx size, the remainder space after creation of fixed-vhdx is less than the fixed-vhdx. +2. Create a fixed-vhdx file +3. Try to start an nbd server with it +the qemu-storage-daemon will not start +Additional information: +I want to mention that I am testing qemu-storage-daemon under windows/hyperv + +So far, I want to report that it has **worked** for rawimg and qcow2-fixed. +See comment of 20220926 https://github.com/cloudbase/wnbd/issues/63#issuecomment-1257148849 + +The driver parameter ```vhdx``` to the blockdev argument seems to struggle with it. + +I wanted to check if the vhdx blockdev driver has the same VHDX-related-bugs as qemu-nbd +- #727 VHDX is corrupted on expansion. +- #806 Fixed VHDX inflates beyond its fixed size when data is copied onto it and also corrupts + +Even the the blockdev reference entries seem to have VHDX all over the place +- pg 318 https://readthedocs.org/projects/qemu/downloads/pdf/latest/ +- https://www.qemu.org/docs/master/system/qemu-block-drivers.html +- except conspicuously here !! https://www.qemu.org/docs/master/interop/qemu-storage-daemon-qmp-ref.html?highlight=blockdev#qapidoc-265 + + +``` +C:\Windows\System32>qemu-storage-daemon --version +qemu-storage-daemon version 7.1.0 (v7.1.0-11925-g4ec481870e-dirty) + +C:\Windows\System32>qemu-storage-daemon --blockdev driver=file,node-name=file,filename=H:\gkpics01.vhdx --blockdev driver=vhdx,node-name=vhdx,file=file --nbd-server addr.type=inet,addr.host=127.0.0.1,addr.port=10809 --export type=nbd,id=export,node-name=vhdx,name=gkpics01,writable=on +qemu-storage-daemon: --blockdev driver=vhdx,node-name=vhdx,file=file: Could not open 'H:\gkpics01.vhdx': Invalid argument + +C:\Windows\System32>qemu-storage-daemon --blockdev driver=file,node-name=file,filename=H:\gkpics01.vhdx --blockdev driver=vhdx,node-name=vhdx,file=file,subformat=fixed --nbd-server addr.type=inet,addr.host=127.0.0.1,addr.port=10809 --export type=nbd,id=export,node-name=vhdx,name=gkpics01,writable=on +qemu-storage-daemon: --blockdev driver=vhdx,node-name=vhdx,file=file,subformat=fixed: Parameter 'subformat' is unexpected + +C:\Windows\System32>dir H:\gkpics01.vhdx + Volume in drive H is CPERF0 + Volume Serial Number is F196-DB9E + Directory of H:\ +09/29/2022 08:55 PM 99,727,966,208 gkpics01.vhdx + 1 File(s) 99,727,966,208 bytes + 0 Dir(s) 4,312,399,872 bytes free +``` +## diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1237 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1237 new file mode 100644 index 000000000..b8fd87238 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1237 @@ -0,0 +1 @@ +after OS upgrade usb-redir connection broken during migration and qemu-kvm: terminating on signal 15 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1239 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1239 new file mode 100644 index 000000000..e9bf61593 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1239 @@ -0,0 +1,36 @@ +The help document of qemu-img misses some options +Description of problem: +The "--help" option of qemu-img misses the option "skip-broken-bitmaps" for convert , "image-opts" for bench, "object" for dd and "force-share" for measure. +Steps to reproduce: +1. For the option "skip-broken-bitmaps", the following code appears during option parsing for convert and modifies the skip_broken in qemu-img.c:2377-2379. + +``` + case OPTION_SKIP_BROKEN: + skip_broken = true; + break; +``` + +2. For the option "image-opts", the following code appears during option parsing for bench and modifies the image_opts in qemu-img.c:4511-4513. + +``` + case OPTION_IMAGE_OPTS: + image_opts = true; + break; +``` +3. For the option "object", the following code appears during option parsing for dd and calls the user_creatable_process_cmdline in qemu-img.c:4980-4982. + +``` + case OPTION_OBJECT: + user_creatable_process_cmdline(optarg); + break; +``` +4. For the option "force-share", the following code appears during option parsing for measure and modifies the force_share in qemu-img.c:5237-5239. +``` + case 'U': + force_share = true; + break; +``` +Additional information: +But they do not appear in the document provided by "--help". + +It may prevent users from using the relevant function. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1240 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1240 new file mode 100644 index 000000000..24616c629 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1240 @@ -0,0 +1,15 @@ +The help document of qemu-nbd misses an option +Description of problem: +The "--help" option of qemu-nbd misses the option "tls-hostname". +Steps to reproduce: +1. For the option "tls-hostname", the following code appears during option parsing and modifies the tlshostname in qemu-nbd.c:760-762. + +``` + case QEMU_NBD_OPT_TLSHOSTNAME: + tlshostname = optarg; + break; +``` +Additional information: +But it does not appear in the document provided by "--help". + +It may prevent users from using the relevant function. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1242 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1242 new file mode 100644 index 000000000..c5fd1c755 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1242 @@ -0,0 +1 @@ +unable to build in mac diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1243 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1243 new file mode 100644 index 000000000..30c1604c3 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1243 @@ -0,0 +1 @@ +Floating-point-exception in ide_set_sector diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1244 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1244 new file mode 100644 index 000000000..cc9f0a5cd --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1244 @@ -0,0 +1,45 @@ +macOS 12.x ld: warning: -undefined dynamic_lookup may not work with chained fixups +Description of problem: +Not sure if this is a serious or negligible problem and if it has any significant runtime implications but reporting it anyway: + +``` +$ ld -v +@(#)PROGRAM:ld PROJECT:ld64-819.6 +BUILD 14:58:44 Aug 5 2022 +configured to support archs: armv6 armv7 armv7s arm64 arm64e arm64_32 i386 x86_64 x86_64h armv6m armv7k armv7m armv7em +LTO support using: LLVM version 14.0.0, (clang-1400.0.29.102) (static support for 29, runtime is 29) +TAPI support using: Apple TAPI version 14.0.0 (tapi-1400.0.11) + +$ ninja -C build +ninja: Entering directory `build' +[314/2946] Linking static target libevent-loop-base.a +warning: /Library/Developer/CommandLineTools/usr/bin/ranlib: archive library: libevent-loop-base.a the table of contents is empty (no object file members in the library define global symbols) +[2044/2946] Generating qemu-system-aarch64 with a custom command +qemu-system-aarch64.tmp: replacing existing signature +[2584/2946] Linking target tests/plugin/libempty.dylib +ld: warning: -undefined dynamic_lookup may not work with chained fixups +[2585/2946] Linking target tests/plugin/libbb.dylib +ld: warning: -undefined dynamic_lookup may not work with chained fixups +[2588/2946] Linking target tests/plugin/libinsn.dylib +ld: warning: -undefined dynamic_lookup may not work with chained fixups +[2589/2946] Linking target tests/plugin/libmem.dylib +ld: warning: -undefined dynamic_lookup may not work with chained fixups +[2592/2946] Linking target tests/plugin/libsyscall.dylib +ld: warning: -undefined dynamic_lookup may not work with chained fixups +[2946/2946] Linking target tests/qtest/test-arm-mptimer +``` + +I saw a similar discussions in Bazel building system, CPython, and Ruby: +- https://github.com/bazelbuild/bazel/issues/16413 +- https://github.com/python/cpython/issues/97524 +- https://github.com/ruby/ruby/pull/6193 +- https://issues.guix.gnu.org/issue/57849 +Steps to reproduce: +1. ` ./configure --target-list=aarch64-softmmu,arm-softmmu --enable-cocoa --enable-plugins` (note that target list is not that important in this case though) +2. `ninja -C build` +3. Observe the warnings +Additional information: +See "New Features" subsection under "Linking" section for chained fixup +https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes for more information: + +> All programs and dylibs built with a deployment target of macOS 12 or iOS 15 or later now use the chained fixups format. This uses different load commands and LINKEDIT data, and won’t run or load on older OS versions. (49851380) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1246 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1246 new file mode 100644 index 000000000..228a147ba --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1246 @@ -0,0 +1 @@ +Win11_22H2_English_x64.iso won't boot diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1249 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1249 new file mode 100644 index 000000000..f413b9707 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1249 @@ -0,0 +1 @@ +qemu-edid Division By Zero -- by misuse of the option "-d" diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1250 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1250 new file mode 100644 index 000000000..1cbbb1c9a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1250 @@ -0,0 +1,3 @@ +[RFE] on windows, attach any storport disk directly, not just physicaldrives +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1252 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1252 new file mode 100644 index 000000000..4298d3240 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1252 @@ -0,0 +1,17 @@ +Debian Raspberry Pi images do not boot with version 7 and higher +Description of problem: +The Debian Bullseye RPi4 4GB image [here](https://raspi.debian.net/tested-images/) does not boot with versions 7 and higher, while it does boot with v6.2.0. The Bookworm image works with v7. +Steps to reproduce: +0. `export DEB_VERS=5.10.0-11` +1. `wget https://raspi.debian.net/tested/20220121_raspi_4_bullseye.img.xz` +2. `dd if=/dev/null of=disk-$DEB_VERS.img bs=1M seek=10240` + * NB: This creates a 10 GB file +3. `xzcat $RPI_IMG | dd of=disk-$DEB_VERS.img conv=notrunc status=progress` +4. `partx -a -v disk-$DEB_VERS.img` +5. `mount /dev/loop0p1 /mnt` +6. `cp /mnt/initrd.img-$DEB_VERS-arm64 .` +7. `cp /mnt/vmlinuz-$DEB_VERS-arm64 .` +8. `umount /mnt` +9. `qemu-system-aarch64 -M virt -m 4096 -cpu max -drive format=raw,file=disk-$DEB_VERS.img -nographic -append "console=tty0 console=ttyAMA0,115200 console=ttyS1,115200 root=LABEL=RASPIROOT rw fsck.repair=yes net.ifnames=0 cma=64M rootwait" -initrd initrd.img-$DEB_VERS-arm64 -kernel vmlinuz-$DEB_VERS-arm64` +Additional information: +The URL for the image in step 1 has been known to change, so if you get a 404, go to the URL above and find the correct one. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1253 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1253 new file mode 100644 index 000000000..b3e0d5b18 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1253 @@ -0,0 +1 @@ +pull mirroring diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1254 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1254 new file mode 100644 index 000000000..4b1c1cdcb --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1254 @@ -0,0 +1,55 @@ +hw: misc: edu: two off-by-one errors +Description of problem: +In `hw/misc/edu.c`, `edu_check_range()` fails for boundary conditions where `size2 == 0` and `size2 == size1`. +Steps to reproduce: +Two ways to reproduce (attached test program, [foo.c](/uploads/9cbef4f72d175b8336b58f607e262d7b/foo.c)) + +error: +1. `gcc -o foo foo.c` +2. `./foo` + +fix: +1. `gcc -DFIXED -o foo foo.c` +2. `./foo` + +Using `qtest`: (see "QEMU command line" above). +Additional information: +(output of `foo` without fix): +``` +EDU: DMA range 0x0000000000000000-0x0000000000000fff out of bounds (0x0000000000000000-0xffffffffffffffff)! +EDU: DMA range 0x0000000000000000-0x0000000000000fff out of bounds (0x0000000000000000-0x0000000000000fff)! +``` + +Output of `qtest` without the fix: +``` +qemu: hardware error: EDU: DMA range 0x0000000000000000-0x0000000000000fff out of bounds (0x0000000000040000-0x0000000000040fff)! +CPU #0: +EAX=00000000 EBX=00000000 ECX=00000000 EDX=00000663 +ESI=00000000 EDI=00000000 EBP=00000000 ESP=00000000 +EIP=0000fff0 EFL=00000002 [-------] CPL=0 II=0 A20=1 SMM=0 HLT=0 +ES =0000 00000000 0000ffff 00009300 +CS =f000 ffff0000 0000ffff 00009b00 +SS =0000 00000000 0000ffff 00009300 +DS =0000 00000000 0000ffff 00009300 +FS =0000 00000000 0000ffff 00009300 +GS =0000 00000000 0000ffff 00009300 +LDT=0000 00000000 0000ffff 00008200 +TR =0000 00000000 0000ffff 00008b00 +GDT= 00000000 0000ffff +IDT= 00000000 0000ffff +CR0=60000010 CR2=00000000 CR3=00000000 CR4=00000000 +DR0=00000000 DR1=00000000 DR2=00000000 DR3=00000000 +DR6=ffff0ff0 DR7=00000400 +EFER=0000000000000000 +FCW=037f FSW=0000 [ST=0] FTW=00 MXCSR=00001f80 +FPR0=0000000000000000 0000 FPR1=0000000000000000 0000 +FPR2=0000000000000000 0000 FPR3=0000000000000000 0000 +FPR4=0000000000000000 0000 FPR5=0000000000000000 0000 +FPR6=0000000000000000 0000 FPR7=0000000000000000 0000 +XMM00=0000000000000000 0000000000000000 XMM01=0000000000000000 0000000000000000 +XMM02=0000000000000000 0000000000000000 XMM03=0000000000000000 0000000000000000 +XMM04=0000000000000000 0000000000000000 XMM05=0000000000000000 0000000000000000 +XMM06=0000000000000000 0000000000000000 XMM07=0000000000000000 0000000000000000 +``` + +Patch has been submitted to `qemu-devel` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1256 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1256 new file mode 100644 index 000000000..c6d4767f3 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1256 @@ -0,0 +1,22 @@ +Building installer fails on Windows 10 Msys2 +Description of problem: +build fails with: +``` +make[2]: Leaving directory '/c/Users/sxlga/source/repos/qemu/build' +Traceback (most recent call last): + File "C:\Users\sxlga\source\repos\qemu\scripts\nsis.py", line 89, in <module> + main() + File "C:\Users\sxlga\source\repos\qemu\scripts\nsis.py", line 34, in main + with open( +OSError: [Errno 22] Invalid argument: 'C:/Users/sxlga/AppData/Local/Temp/tmpinyvlwkoC:/msys64/qemu/system-emulations.nsh' +ninja: build stopped: subcommand failed. +make[1]: *** [Makefile:165: run-ninja] Error 1 +make[1]: Leaving directory '/c/Users/sxlga/source/repos/qemu/build' +make: *** [GNUmakefile:11: installer] Error 2 +``` +Steps to reproduce: +1. ./configure --target-list=arm-softmmu,aarch64-softmmu +2. make all +3. make installer +Additional information: +following https://wiki.qemu.org/Hosts/W32#Native_builds_with_MSYS2 to set up toolchain diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1257 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1257 new file mode 100644 index 000000000..7a79743a1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1257 @@ -0,0 +1,3 @@ +Windows guest agent shutdown requires user response to complete +Additional information: +The shutdown operation triggered by the Windows Guest Agent should prevent the system from waiting for a user response concerning unsaved work of open desktop applications. Instead, applications and services should be closed as gracefully as possible automatically, in advance of the power down event on the emulated hardware. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/126 b/gitlab/issues_text/target_missing/host_missing/accel_missing/126 new file mode 100644 index 000000000..dae4b3c5f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/126 @@ -0,0 +1 @@ +qemu-input: Mouse stops working in Windows guest diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1262 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1262 new file mode 100644 index 000000000..387d66138 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1262 @@ -0,0 +1 @@ +avocado test framework fails to report when QEMU exits unexpectedly diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1264 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1264 new file mode 100644 index 000000000..d604b2f5d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1264 @@ -0,0 +1 @@ +socket chardev loses data when remote end closes the connection diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1265 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1265 new file mode 100644 index 000000000..02df9d3a4 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1265 @@ -0,0 +1 @@ +avocado should log all the guest console output until QEMU exits, not disconnect early diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1266 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1266 new file mode 100644 index 000000000..728b93d1f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1266 @@ -0,0 +1 @@ +Assert in resettable_phase_enter through virtio-scsi diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1268 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1268 new file mode 100644 index 000000000..b7762eb6f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1268 @@ -0,0 +1 @@ +erst: undefined-behavior in memcpy in write_erst_record diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1270 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1270 new file mode 100644 index 000000000..b8f168bf9 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1270 @@ -0,0 +1,14 @@ +Guest freezes if memory backing using memfd/shared/ +Description of problem: +Guest VM freezes with the following memory backing is set. Required to for virtiofs, but just setting the following the guest will freeze in around 2hours, no logs or errors generate. + + <memoryBacking> + <source type='memfd'/> + <access mode='shared'/> + </memoryBacking> +Steps to reproduce: +1. +2. +3. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1272 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1272 new file mode 100644 index 000000000..65da43011 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1272 @@ -0,0 +1,50 @@ +qemu 7.1: assertion faillure with virtio-scsi in `blk_set_enable_write_cache` +Description of problem: +During the guest boot qemu crashes with the following error: + +> qemu-system-x86_64: ../src/block/block-backend.c:1949: blk_set_enable_write_cache: Assertion `qemu_in_main_thread()' failed. +Steps to reproduce: +1. Start a windows guest +Additional information: +Stacktrace: + +``` +#0 0x00007fd6c3515ce1 in raise () from /lib/x86_64-linux-gnu/libc.so.6 +#1 0x00007fd6c34ff537 in abort () from /lib/x86_64-linux-gnu/libc.so.6 +#2 0x00007fd6c34ff40f in ?? () from /lib/x86_64-linux-gnu/libc.so.6 +#3 0x00007fd6c350e662 in __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6 +#4 0x000056149e2cea03 in blk_set_enable_write_cache (wce=true, blk=0x5614a01c27f0) at ../src/block/block-backend.c:1949 +#5 0x000056149e2d0a67 in blk_set_enable_write_cache (blk=0x5614a01c27f0, wce=<optimized out>) at ../src/block/block-backend.c:1951 +#6 0x000056149dfe9c59 in scsi_disk_apply_mode_select (p=0x7fd6b400c00e "\004", page=<optimized out>, s=<optimized out>) at ../src/hw/scsi/scsi-disk.c:1520 +#7 mode_select_pages (change=true, len=18, p=0x7fd6b400c00e "\004", r=0x7fd6b4001ff0) at ../src/hw/scsi/scsi-disk.c:1570 +#8 scsi_disk_emulate_mode_select (inbuf=<optimized out>, r=0x7fd6b4001ff0) at ../src/hw/scsi/scsi-disk.c:1640 +#9 scsi_disk_emulate_write_data (req=0x7fd6b4001ff0) at ../src/hw/scsi/scsi-disk.c:1934 +#10 0x000056149e18ff16 in virtio_scsi_handle_cmd_req_submit (req=<optimized out>, req=<optimized out>, s=0x5614a12f16b0) at ../src/hw/scsi/virtio-scsi.c:719 +#11 virtio_scsi_handle_cmd_vq (vq=0x7fd6bab92140, s=0x5614a12f16b0) at ../src/hw/scsi/virtio-scsi.c:761 +#12 virtio_scsi_handle_cmd (vq=<optimized out>, vdev=<optimized out>) at ../src/hw/scsi/virtio-scsi.c:775 +#13 virtio_scsi_handle_cmd (vdev=0x5614a12f16b0, vq=0x7fd6bab92140) at ../src/hw/scsi/virtio-scsi.c:765 +#14 0x000056149e1a8aa6 in virtio_queue_notify_vq (vq=0x7fd6bab92140) at ../src/hw/virtio/virtio.c:2365 +#15 0x000056149e3ccea5 in aio_dispatch_handler (ctx=ctx@entry=0x5614a01babe0, node=<optimized out>) at ../src/util/aio-posix.c:369 +#16 0x000056149e3cd868 in aio_dispatch_ready_handlers (ready_list=0x7fd6c09b2680, ctx=0x5614a01babe0) at ../src/util/aio-posix.c:399 +#17 aio_poll (ctx=0x5614a01babe0, blocking=blocking@entry=true) at ../src/util/aio-posix.c:713 +#18 0x000056149e2a7796 in iothread_run (opaque=opaque@entry=0x56149ffde500) at ../src/iothread.c:67 +#19 0x000056149e3d0859 in qemu_thread_start (args=0x7fd6c09b26f0) at ../src/util/qemu-thread-posix.c:504 +#20 0x00007fd6c36b9ea7 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 +#21 0x00007fd6c35d9aef in clone () from /lib/x86_64-linux-gnu/libc.so.6 +``` + +The crash was bisected to: + +``` +commit b1c073490553f80594b903ceedfc7c1aef6b1b19 +Author: Hanna Reitz <hreitz@redhat.com> +Date: Tue Mar 29 11:35:45 2022 +0200 + + main-loop: Disable GLOBAL_STATE_CODE() assertions +``` + +I have not been able to reproduce the bug with a linux guest nor with a fresh windows installation. + +The crashes appears with either `writethrough` and `directsync` cache modes but not with `writeback` `none` and `unsafe`. + +Note: if needed I can extract (privately) provide a disk image demonstrating the behavior diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1273 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1273 new file mode 100644 index 000000000..46b1a7e51 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1273 @@ -0,0 +1 @@ +QEMU log problem diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1275 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1275 new file mode 100644 index 000000000..3b816433c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1275 @@ -0,0 +1,9 @@ +javac command stuck forever in qemu vm which does not use hardware virtualization +Description of problem: + +Steps to reproduce: +1. +2. +3. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1276 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1276 new file mode 100644 index 000000000..aacb6a834 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1276 @@ -0,0 +1,15 @@ +[SDL] Fractional scaling is blurry +Description of problem: +The display looks blurry +Steps to reproduce: +1. Use a Wayland compositor (eg. Sway) with scale set to `1.25` +2. Launch an Ubuntu guest with the SDL display +3. Notice blurryness +Additional information: +https://github.com/libsdl-org/SDL/issues/6438 + +Blurry display https://user-images.githubusercontent.com/67585967/197484538-fde750aa-8982-4ac2-9d83-3861f6411a31.png + +Display with 1.00 scale https://user-images.githubusercontent.com/67585967/197484417-afd1d1c5-5ea1-46ce-82c5-fa8d9b2df459.png + +It was suggested in the SDL issue (https://github.com/libsdl-org/SDL/issues/6438#issuecomment-1289513402) that it's caused by the `SDL_WINDOW_ALLOW_HIGHDPI` not being set. However, after setting that flag, the display is sharp again but it's not scaled properly (boxed) https://github.com/libsdl-org/SDL/issues/6438#issuecomment-1291663284, no idea what other changes need to be made. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1277 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1277 new file mode 100644 index 000000000..b0573cccb --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1277 @@ -0,0 +1 @@ +two instructions has executed twice diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1278 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1278 new file mode 100644 index 000000000..9285e4ed8 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1278 @@ -0,0 +1,6 @@ +Error creating encrypted qcow2 disk using qemu-img +Description of problem: +Error creating encrypted qcow2 disk using qemu-img:No crypto library supporting PBKDF in this build: Function not implemented + +Steps to reproduce: +1.qemu-img create --object secret,id=sec0,data=123456 -f qcow2 -o encrypt.format=luks,encrypt.key-secret=sec0 base.qcow2 1G diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/128 b/gitlab/issues_text/target_missing/host_missing/accel_missing/128 new file mode 100644 index 000000000..7ebb0a81e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/128 @@ -0,0 +1 @@ +man page is missing suboptions for "-display" diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1282 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1282 new file mode 100644 index 000000000..798e77278 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1282 @@ -0,0 +1,3 @@ +sdhci: DMA reentrancy issue leads to an infinite loop +Description of problem: +When sdhci transfers multiple blocks, it doesnot check if the dma-write buffer pointer overlaps with its MMIO region, crafted content can cause DoS because of infinite loop and CPU consumption. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1283 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1283 new file mode 100644 index 000000000..4d2105257 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1283 @@ -0,0 +1,82 @@ +Live migration cause scsi_req_unref: Assertion `req->refcount > 0' failed +Description of problem: +During live migration, copy file from one folder to another. Migration can succeed. After a while, copy can't finish and in target host qemu crash: +``` +qemu-system-x86_64: ../hw/scsi/scsi-bus.c:1366: scsi_req_unref: Assertion `req->refcount > 0' failed. +2022-10-28 03:22:54.948+0000: shutting down, reason=crashed +``` +libvirt configure related: +``` + <disk type='file' device='disk'> + <driver name='qemu' type='qcow2'/> + <source file='/images/gen-l-vrt-295-008/swx-jd01-001-new.img'/> + <target dev='sda' bus='scsi'/> + <alias name='ua-box-volume-0'/> + <address type='drive' controller='0' bus='0' target='0' unit='0'/> + </disk> + <controller type='scsi' index='0' model='lsilogic'> + <address type='pci' domain='0x0000' bus='0x03' slot='0x01' function='0x0'/> + </controller> +``` +If change `bus='scsi'` to `bus='sata'`, same test steps can pass. +Steps to reproduce: +1. Inside VM +``` +fallocate -l 10G /tmp/test.img +cp /tmp/test.img / +``` +2. Same time, migrate VM to another server +``` +virsh migrate --verbose --live --persistent swx-jd01-001 qemu+ssh://gen-l-vrt-294/system --unsafe --auto-converge --auto-converge-initial 60 --auto-converge-increment 20 + +``` +3. After a while, cp can't finish and qemu crash on destination server with assert fail. +Additional information: +stack traces: +``` +#0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140544841483840) at ./nptl/pthread_kill.c:44 +#1 __pthread_kill_internal (signo=6, threadid=140544841483840) at ./nptl/pthread_kill.c:78 +#2 __GI___pthread_kill (threadid=140544841483840, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 +#3 0x00007fd3284f9476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 +#4 0x00007fd3284df7f3 in __GI_abort () at ./stdlib/abort.c:79 +#5 0x00007fd3284df71b in __assert_fail_base + (fmt=0x7fd328694150 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x55791c97acbb "req->refcount > 0", file=0x55791c97ac7f "../hw/scsi/scsi-bus.c", line=1366, function=<optimized out>) + at ./assert/assert.c:92 +#6 0x00007fd3284f0e96 in __GI___assert_fail + (assertion=assertion@entry=0x55791c97acbb "req->refcount > 0", file=file@entry=0x55791c97ac7f "../hw/scsi/scsi-bus.c", line=line@entry=1366, function=function@entry=0x55791c97b2a0 <__PRETTY_FUNCTION__.14> "scsi_req_unref") at ./assert/assert.c:101 +#7 0x000055791c499a2e in scsi_req_unref (req=<optimized out>) at ../hw/scsi/scsi-bus.c:1366 +#8 0x000055791c49b61f in scsi_device_purge_requests (sdev=sdev@entry=0x55791e6e0c00, sense=...) at ../hw/scsi/scsi-bus.c:1639 +#9 0x000055791c49d704 in scsi_disk_reset (dev=0x55791e6e0c00) at ../hw/scsi/scsi-disk.c:2336 +#10 0x000055791c72a6ed in qdev_reset_one (dev=<optimized out>, opaque=<optimized out>) at ../hw/core/qdev.c:254 +#11 0x000055791c726fa9 in qbus_walk_children + (bus=<optimized out>, pre_devfn=0x55791c728770 <qdev_prereset>, pre_busfn=0x55791c7286a0 <qbus_prereset>, post_devfn=0x55791c72a6e0 <qdev_reset_one>, post_busfn=0x55791c728ae0 <qbus_reset_one>, opaque=0x0) at ../hw/core/bus.c:54 +#12 0x000055791c72a790 in qdev_walk_children + (opaque=0x0, post_busfn=0x55791c728ae0 <qbus_reset_one>, post_devfn=0x55791c72a6e0 <qdev_reset_one>, pre_busfn=0x55791c7286a0 <qbus_prereset>, pre_devfn=0x55791c728770 <qdev_prereset>, dev=0x55791ed2a430) at ../hw/core/qdev.c:413 +#13 qdev_reset_all (dev=0x55791ed2a430) at ../hw/core/qdev.c:272 +#14 0x000055791c688134 in memory_region_write_accessor (mr=mr@entry=0x55791ed2ae60, addr=20, value=value@entry=0x7fd32559f618, size=size@entry=1, shift=<optimized out>, mask=mask@entry=255, attrs=...) + at ../softmmu/memory.c:492 +#15 0x000055791c6858c6 in access_with_adjusted_size + (addr=addr@entry=20, value=value@entry=0x7fd32559f618, size=size@entry=1, access_size_min=<optimized out>, access_size_max=<optimized out>, access_fn=0x55791c6880b0 <memory_region_write_accessor>, mr=0x55791ed2ae60, attrs=...) at ../softmmu/memory.c:554 +#16 0x000055791c689bf2 in memory_region_dispatch_write (mr=mr@entry=0x55791ed2ae60, addr=20, data=<optimized out>, op=<optimized out>, attrs=attrs@entry=...) at ../softmmu/memory.c:1521 +#17 0x000055791c690cf0 in flatview_write_continue (fv=fv@entry=0x55791e729ac0, addr=addr@entry=4257226772, attrs=..., + attrs@entry=..., ptr=ptr@entry=0x7fd328d36028, len=len@entry=1, addr1=<optimized out>, l=<optimized out>, mr=0x55791ed2ae60) at /opt/qemu/include/qemu/host-utils.h:166 +#18 0x000055791c690fb0 in flatview_write (fv=0x55791e729ac0, addr=addr@entry=4257226772, attrs=attrs@entry=..., buf=buf@entry=0x7fd328d36028, len=len@entry=1) at ../softmmu/physmem.c:2867 +#19 0x000055791c694799 in address_space_write (len=1, buf=0x7fd328d36028, attrs=..., addr=4257226772, as=0x55791d08a740 <address_space_memory>) at ../softmmu/physmem.c:2963 +#20 address_space_rw (as=0x55791d08a740 <address_space_memory>, addr=4257226772, attrs=attrs@entry=..., buf=buf@entry=0x7fd328d36028, len=1, is_write=<optimized out>) at ../softmmu/physmem.c:2973 +#21 0x000055791c71d19e in kvm_cpu_exec (cpu=cpu@entry=0x55791dc9d890) at ../accel/kvm/kvm-all.c:2954 +#22 0x000055791c71e6c5 in kvm_vcpu_thread_fn (arg=arg@entry=0x55791dc9d890) at ../accel/kvm/kvm-accel-ops.c:49 +#23 0x000055791c885be1 in qemu_thread_start (args=<optimized out>) at ../util/qemu-thread-posix.c:504 +#24 0x00007fd32854bb43 in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:442 +#25 0x00007fd3285dcbb4 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:100 +``` +Guest disk partition +``` +root@swx-jd01-001:~# lsblk +NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT +sda 8:0 0 64G 0 disk +├─sda1 8:1 0 512M 0 part /boot/efi +├─sda2 8:2 0 1K 0 part +└─sda5 8:5 0 63.5G 0 part + ├─vgwin--dbausdhrjgi-root 253:0 0 62.6G 0 lvm / + └─vgwin--dbausdhrjgi-swap_1 253:1 0 980M 0 lvm [SWAP] +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1284 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1284 new file mode 100644 index 000000000..a59cb93f6 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1284 @@ -0,0 +1,14 @@ +macOS QXL VGA not available +Description of problem: +``` +qemu-system-aarch64: QXL VGA not available +``` +``` +qemu-system-aarch64: -device qxl-vga: 'qxl-vga' is not a valid device model name +``` +Steps to reproduce: +1. Build QEMU on macOS with SPICE support (meson) +2. Run commands listed above +3. Observe QXL not working +Additional information: +I'm wiring up QEMU SPICE support on Darwin for Nixpkgs. The same issue can be observed in macports qemu builds with spice. Could this be a packaging issue? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1285 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1285 new file mode 100644 index 000000000..1d54d4bc1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1285 @@ -0,0 +1,20 @@ +Can't use spice-app on macOS because GIO can't find handler for spice+unix scheme +Description of problem: +``` +qemu-system-aarch64: info: Launching display with URI: spice+unix:///tmp/.U96NU1/spice.sock +qemu-system-aarch64: warning: GLib-GIO: No default handler found for url scheme 'spice+unix'. +qemu-system-aarch64: warning: GLib-GIO: No default handler found for url scheme 'spice+unix'. +qemu-system-aarch64: Failed to launch spice+unix:///tmp/.U96NU1/spice.sock URI: Operation not supported +qemu-system-aarch64: You need a capable Spice client, such as virt-viewer 8.0 +``` + +``` +$ virt-viewer --version +virt-viewer version 11.0 +``` +Steps to reproduce: +1. Have virt-viewer in $PATH +2. Run command above +3. Observe error above +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1286 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1286 new file mode 100644 index 000000000..2c2a847b7 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1286 @@ -0,0 +1 @@ +netdev tftp option docs don't mention that the TFTP server is read-only diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1287 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1287 new file mode 100644 index 000000000..bd5cb113c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1287 @@ -0,0 +1,10 @@ +qemu-img info foo.qcow2 tries to get write lock +Description of problem: +When trying to run qemu-img info on an image which is used by QEMU qemu-img tries to acquire a write lock. Ideally this would not attempt to acquire a write lock and let qemu-img info succeed. +``` +[jelle@t14s][/tmp]%qemu-img info /var/tmp/cockpit-qr_j3e_m.qcow2 +qemu-img: Could not open '/var/tmp/cockpit-qr_j3e_m.qcow2': Failed to get shared "write" lock +Is another process using the image [/var/tmp/cockpit-qr_j3e_m.qcow2]? +``` +Steps to reproduce: +1. Run qemu-img on an image used by a QEMU process. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1288 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1288 new file mode 100644 index 000000000..2da59d857 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1288 @@ -0,0 +1,9 @@ +GPU passing through guest crashes +Description of problem: +First and foremost, I don't know if this is a QEMU, KVM or GPU driver issue. +I began emailing libvirt project and they advised me to contact you, then KVM and then GPU driver developer(NVIDIA). +Host is crashing from time to time. I have guest's kernel dumps(~2GB each). +Steps to reproduce: +Unfortunately, I don't have steps to reproduce. +Additional information: +I'm aware I'm not running the latest qmeu version but I'm willing to install developer version and try to reproduce or test patch if developer requires it. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1289 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1289 new file mode 100644 index 000000000..9a7e3266f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1289 @@ -0,0 +1 @@ +plugin get registers diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/129 b/gitlab/issues_text/target_missing/host_missing/accel_missing/129 new file mode 100644 index 000000000..73556468d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/129 @@ -0,0 +1,12 @@ +Build failure due to conflicts with the C++20 version header +Steps to reproduce: +qemu 5.2.0: +``` +brew install -s qemu +``` + +qemu 6.0.0: +``` +wget https://raw.githubusercontent.com/Homebrew/homebrew-core/02107501a48cc9d08480913ee1c79866dc60c23a/Formula/qemu.rb +brew install -s qemu.rb +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1290 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1290 new file mode 100644 index 000000000..b89932ef7 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1290 @@ -0,0 +1 @@ +IO alignment probing delivers incorrect results on Linux when used with e.g. dm-crypt diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1291 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1291 new file mode 100644 index 000000000..749609a22 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1291 @@ -0,0 +1 @@ +--enable-jemalloc configure option is not covered in CI diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1292 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1292 new file mode 100644 index 000000000..3a8f71db0 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1292 @@ -0,0 +1,3 @@ +Default jemalloc config doesn't work on Asahi Linux +Description of problem: +M1 Macs use 16KB pages, jemalloc builds with 4KB page by default. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1294 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1294 new file mode 100644 index 000000000..3f1c562ec --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1294 @@ -0,0 +1 @@ +pflash size check appears to be incompatible with OVMF on x86 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1295 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1295 new file mode 100644 index 000000000..2a587c593 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1295 @@ -0,0 +1,27 @@ +configure script can fail if compiler flag `-Wunused-parameter` is enabled +Description of problem: +`configure` fails with an error message: + +``` +ERROR: SafeStack is only supported by the coroutine backend ucontext +``` +Steps to reproduce: +1. Run `./configure --cross-prefix=x86_64-w64-mingw32- --disable-werror --extra-cflags=-Wunused-parameter` +Additional information: +Last part of `config.log`: + +``` +x86_64-w64-mingw32-gcc -m64 -mcx16 -I/mingw64/include -Wunused-parameter -fno-pie -mthreads -std=gnu11 -Wall -fno-pie -no-pie -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fno-common -fwrapv -Wold-style-declaration -Wold-style-definition -Wtype-limits -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body -Wnested-externs -Wendif-labels -Wexpansion-to-defined -Wimplicit-fallthrough=2 -Wno-missing-include-dirs -Wno-shift-negative-value -Wno-psabi -Werror -o config-temp/qemu-conf.exe config-temp/qemu-conf.c -L/mingw64/lib -no-pie +config-temp/qemu-conf.c: In function ‘main’: +config-temp/qemu-conf.c:1:14: error: unused parameter ‘argc’ [-Werror=unused-parameter] + 1 | int main(int argc, char *argv[]) + | ~~~~^~~~ +config-temp/qemu-conf.c:1:26: error: unused parameter ‘argv’ [-Werror=unused-parameter] + 1 | int main(int argc, char *argv[]) + | ~~~~~~^~~~~~ +cc1: all warnings being treated as errors +``` + +The configure script fails because it tries to compile small C programs with a main function which is declared with arguments `argc` and `argv` although those arguments are unused. + +Using the same compiler flag for a native build (`./configure --disable-werror --extra-cflags=-Wunused-parameter`) shows the same errors in `config.log`, but surprisingly does not fail. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1296 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1296 new file mode 100644 index 000000000..97f9ca2b5 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1296 @@ -0,0 +1,8 @@ +qemu hangs on start with a bridged NIC +Description of problem: +qemu hangs on start with a bridged NIC. And there is no difference exists the bridge or not. At the same with a user NIC (`-nic user`) everything works flawlessly. Also I tried to add `-enable-kvm` key and had no luck. +Steps to reproduce: +1. Run qemu with the specified command line. +Additional information: +I ran the strace: `strace -s 1024 -tt -ff -y -o qemu_bridge -- qemu-system-x86_64 -nic bridge` +Here are the logs: [qemu-bridge-strace.zip](/uploads/ecf8a2ba9133279fdd6f88fda5dd9ff3/qemu-bridge-strace.zip) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1300 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1300 new file mode 100644 index 000000000..ae8179051 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1300 @@ -0,0 +1,11 @@ +Build failure when configuring CONFIG_VHOST_USER_FS/CONFIG_VIRTIO +Description of problem: +Attempting to configure CONFIG_VHOST_USER_FS or CONFIG_VIRTIO results in a build failure. Complete build log (with configure output) is attached. +Steps to reproduce: +1. Add `CONFIG_VIRTIO` and `CONFIG_VHOST_USER_FS` (`y` *or* `n`) to `configs/devices/x86_64-softmmu/gentoo.mak` (done via the [ebuild](https://github.com/gentoo/gentoo/blob/master/app-emulation/qemu/qemu-7.1.0.ebuild)) +2. Configure with `--with-devices-x86_64=gentoo` +3. Attempt building +Additional information: +[build.log](/uploads/72fc1284f5245d9384e521d3b1c65953/build.log) + +Reported downstream [here](https://bugs.gentoo.org/873190). diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1302 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1302 new file mode 100644 index 000000000..808f37726 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1302 @@ -0,0 +1,17 @@ +Per-thread logging flag must be made immutable +Description of problem: +The problem is that the code assumes it isn't possible to switch from global logging to per-thread logging and vice-versa per design, but it lags appropriate checks to enforce it. Enabling or disabling per-thread logging at runtime from the monitor causes unexpected results. +Steps to reproduce: +Enabling per-thread logging at runtime: + +1. Start QEMU : `./qemu-system-x86_64 -S -monitor stdio -D qemu.log.%d` +2. Enable per-thread logging from the HMP monitor : `(qemu) log tid` +3. Fails with `Filename template with '%d' required for 'tid'` even though such a template was passed with `-D`. + +Disabling per-thread logging at runtime: + +1. Start QEMU : `./qemu-system-x86_64 -S -monitor stdio -D qemu.log.%d -d tid,cpu_reset` +2. Disable per-thread logging from the HMP monitor: `(qemu) log cpu_reset` +3. QEMU creates a log file with a bogus `qemu.log.%d` name. +Additional information: +[Series](https://patchew.org/QEMU/20221104120059.678470-1-groug@kaod.org/) posted and already reviewed by @rth7680 . diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1304 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1304 new file mode 100644 index 000000000..e17491e1e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1304 @@ -0,0 +1,9 @@ +loadvm for arm vexpress-a9 +Description of problem: + +Steps to reproduce: +1. savevm test +2. loadvm test +3. After I execute savevm and loadvm,the guest is not responding +Additional information: +I have read this issue(https://github.com/panda-re/panda/issues/643). If secure is set to off,the guest works well. But I need to use security extensions,so secure cannot be set to off.What do I need to do to solve this problem？ diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1305 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1305 new file mode 100644 index 000000000..044848f0c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1305 @@ -0,0 +1,14 @@ +qemu will detach usbredir if backend chardev socket disconnect +Description of problem: +When using the usbredir device in the VM, initiate a hot migration to the VM. +After the migration is completed, the drive letter of the usb in the VM has changed. +Actually the device has been unplugged and re-plugged in the VM. +I think we should keep the plugged state of the device after the migration? +Steps to reproduce: +1. Start a usbredirserver `usbredirserver -p 7000 -v 4 5-2`; +2. Start a VM with a usbredir device attached to it; +3. Mount the usb device in the VM; +4. Migrate the VM, after the migration done, wait a minute，the drive letter of the usb in the VM has changed. +Additional information: +I've found this bug https://bugzilla.redhat.com/show_bug.cgi?id=1254971, this is just to allow the chardev to be reconnected in time when it is disconnected. +Can we make chardev reconnect without unpluging the usbredir device? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1307 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1307 new file mode 100644 index 000000000..9e90d8ad4 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1307 @@ -0,0 +1,72 @@ +query-named-block-nodes, without flat=true, is massively slow as number of block nodes increases +Description of problem: +The query-named-block-nodes command is insanely slow with deep backing chains when the flat=true arg is NOT given. + +``` +qemu-img create demo0.qcow2 1g +j=0 +for i in `seq 1 199` +do + qemu-img create -f qcow2 -o backing_file=demo$j.qcow2 -o backing_fmt=qcow2 demo$i.qcow2 + j=$i +done +``` + +Now configure libvirt with + +``` + <disk type='file' device='disk'> + <driver name='qemu' type='qcow2' discard='unmap'/> + <source file='/var/lib/libvirt/images/demo199.qcow2'/> + <target dev='vdb' bus='virtio'/> + <address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> + </disk> +``` + +This results in `-blockdev` args + +``` +-blockdev '{"driver":"file","filename":"/var/lib/libvirt/images/demo0.qcow2","node-name":"libvirt-201-storage","auto-read-only":true,"discard":"unmap"}' \ +-blockdev '{"node-name":"libvirt-201-format","read-only":true,"discard":"unmap","driver":"qcow2","file":"libvirt-201-storage","backing":null}' \ +-blockdev '{"driver":"file","filename":"/var/lib/libvirt/images/demo1.qcow2","node-name":"libvirt-200-storage","auto-read-only":true,"discard":"unmap"}' \ +-blockdev '{"node-name":"libvirt-200-format","read-only":true,"discard":"unmap","driver":"qcow2","file":"libvirt-200-storage","backing":"libvirt-201-format"}' \ +-blockdev '{"driver":"file","filename":"/var/lib/libvirt/images/demo2.qcow2","node-name":"libvirt-199-storage","auto-read-only":true,"discard":"unmap"}' \ +-blockdev '{"node-name":"libvirt-199-format","read-only":true,"discard":"unmap","driver":"qcow2","file":"libvirt-199-storage","backing":"libvirt-200-format"}' \ +...snip... +-blockdev '{"driver":"file","filename":"/var/lib/libvirt/images/demo197.qcow2","node-name":"libvirt-4-storage","auto-read-only":true,"discard":"unmap"}' \ +-blockdev '{"node-name":"libvirt-4-format","read-only":true,"discard":"unmap","driver":"qcow2","file":"libvirt-4-storage","backing":"libvirt-5-format"}' \ +-blockdev '{"driver":"file","filename":"/var/lib/libvirt/images/demo198.qcow2","node-name":"libvirt-3-storage","auto-read-only":true,"discard":"unmap"}' \ +-blockdev '{"node-name":"libvirt-3-format","read-only":true,"discard":"unmap","driver":"qcow2","file":"libvirt-3-storage","backing":"libvirt-4-format"}' \ +-blockdev '{"driver":"file","filename":"/var/lib/libvirt/images/demo199.qcow2","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' \ +-blockdev '{"node-name":"libvirt-1-format","read-only":false,"discard":"unmap","driver":"qcow2","file":"libvirt-1-storage","backing":"libvirt-3-format"}' \ +-device '{"driver":"virtio-blk-pci","bus":"pci.7","addr":"0x0","drive":"libvirt-1-format","id":"virtio-disk1"}' \ +``` + +Now stop libvirt + +``` +systemctl stop libvirtd +``` + +And speak directly to QMP + +``` +$ time socat UNIX:/var/lib/libvirt/qemu/domain-158-fedora38/monitor.sock - > /dev/null +{ "execute": "qmp_capabilities", "arguments": { "enable": ["oob"] } } +{ "execute": "query-named-block-nodes"} +{ "execute": "quit" } + +real 2m19.276s +user 0m0.006s +sys 0m0.014s +``` + +If we save the 'query-named-block-nodes' output instead of sending it to /dev/null, we get a 86 MB file for the QMP response. This will break all known client apps since they limit QMP reply size. + +It appears to have a combinatorial expansion of block nodes in the output. + +Blocking the main event loop for 2 minutes is obviously not good either. + +If we use '"flat": true' parameter to query-named-block-nodes, the command completes in just 15 seconds, and produces a large, but more manageable 2.7 MB + +Since the non-flat query-named-block-nodes output is so incredibly non-scalable, I think we should deprecate non-flat mode, and eventually make flat the mandatory option. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1308 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1308 new file mode 100644 index 000000000..cffbaa939 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1308 @@ -0,0 +1 @@ +Qemu headless build process is stopped, complaining about a missing pixman.h diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1309 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1309 new file mode 100644 index 000000000..b5c69d10b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1309 @@ -0,0 +1 @@ +Heap-overflow in virtio_net_queue_enable diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1310 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1310 new file mode 100644 index 000000000..c07d208dd --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1310 @@ -0,0 +1,190 @@ +qemu-nbd export img and detect block if is zero with libnbd +Description of problem: +In our project,we use qemu-nbd to export a img,and use libnbd to read/write data.if the img is preallocated,we wonder the data block if is zero,we use api nbd_block_status in libnbd to get the block status,but it shows server does not support structured replies: Operation not supported.I know our qemu is too old.so,i want to know how can i know if the block in preallocated is zero or not in nbd client. +Steps to reproduce: +1.qemu-nbd -p 8889 -f raw a.img + +2.the nbd client use libnbd,code is: +```c +#include <config.h> + +#include <stdio.h> +#include <stdlib.h> +#include <string.h> +#include <unistd.h> +#include <assert.h> +#include <stdbool.h> +#include <errno.h> + +#include <libnbd.h> + +static const char *bitmap; + +struct data { + bool req_one; /* input: true if req_one was passed to request */ + int count; /* input: count of expected remaining calls */ + bool fail; /* input: true to return failure */ + bool seen_base; /* output: true if base:allocation encountered */ + bool seen_dirty; /* output: true if qemu:dirty-bitmap encountered */ +}; + +static int +cb (void *opaque, const char *metacontext, uint64_t offset, + uint32_t *entries, size_t len, int *error) +{ + struct data *data = opaque; + + /* libnbd does not actually verify that a server is fully compliant + * to the spec; the asserts marked [qemu-nbd] are thus dependent on + * the fact that qemu-nbd is compliant. Furthermore, qemu 5.2 and + * 6.0 disagree on whether base:allocation includes the hole bit for + * the zeroes at 512k (both answers are compliant); but we care more + * that the zeroes show up in the dirty bitmap + */ + assert (offset == 0); + assert (!*error || (data->fail && data->count == 1 && *error == EPROTO)); + assert (data->count-- > 0); /* [qemu-nbd] */ + + if (strcmp (metacontext, LIBNBD_CONTEXT_BASE_ALLOCATION) == 0) { + assert (!data->seen_base); /* [qemu-nbd] */ + data->seen_base = true; + if (data->req_one) + assert (len == 2); /* [qemu-nbd] */ + else + assert ((len & 1) == 0 && len > 2); /* [qemu-nbd] */ + + /* Data block offset 0 size 128k */ + assert (entries[0] == 131072); assert (entries[1] == 0); + if (!data->req_one) { + if (len == 4) { + /* hole|zero offset 128k size 896k */ + assert (entries[2] == 917504); + assert (entries[3] == (LIBNBD_STATE_HOLE| + LIBNBD_STATE_ZERO)); + } + else { + assert (len == 8); + /* hole|zero offset 128k size 384k */ + assert (entries[2] == 393216); + assert (entries[3] == (LIBNBD_STATE_HOLE| + LIBNBD_STATE_ZERO)); + /* allocated zero offset 512k size 64k */ + assert (entries[4] == 65536); + assert (entries[5] == LIBNBD_STATE_ZERO); + /* hole|zero offset 576k size 448k */ + assert (entries[6] == 458752); + assert (entries[7] == (LIBNBD_STATE_HOLE| + LIBNBD_STATE_ZERO)); + } + } + } + else if (strcmp (metacontext, bitmap) == 0) { + assert (!data->seen_dirty); /* [qemu-nbd] */ + data->seen_dirty = true; + assert (len == (data->req_one ? 2 : 10)); /* [qemu-nbd] */ + + assert (entries[0] == 65536); assert (entries[1] == 0); + if (!data->req_one) { + /* dirty block offset 64K size 64K */ + assert (entries[2] == 65536); assert (entries[3] == 1); + assert (entries[4] == 393216); assert (entries[5] == 0); + /* dirty block offset 512K size 64K */ + assert (entries[6] == 65536); assert (entries[7] == 1); + assert (entries[8] == 458752); assert (entries[9] == 0); + } + } + else { + fprintf (stderr, "unexpected context %s\n", metacontext); + exit (EXIT_FAILURE); + } + + if (data->fail) { + /* Something NBD servers can't send */ + *error = data->count == 1 ? EPROTO : ECONNREFUSED; + return -1; + } + return 0; +} + +int +main (int argc, char *argv[]) +{ + struct nbd_handle *nbd; + int64_t exportsize; + struct data data; + char c; + + if (argc < 3) { + fprintf (stderr, "%s bitmap qemu-nbd [args ...]\n", argv[0]); + exit (EXIT_FAILURE); + } + bitmap = argv[1]; + + nbd = nbd_create (); + if (nbd == NULL) { + fprintf (stderr, "%s\n", nbd_get_error ()); + exit (EXIT_FAILURE); + } + + nbd_add_meta_context (nbd, LIBNBD_CONTEXT_BASE_ALLOCATION); + nbd_add_meta_context (nbd, bitmap); + + if (nbd_connect_tcp (nbd, argv[2],argv[3]) == -1) { + fprintf (stderr, "%s\n", nbd_get_error ()); + exit (EXIT_FAILURE); + } + + exportsize = nbd_get_size (nbd); + if (exportsize == -1) { + fprintf (stderr, "%s\n", nbd_get_error ()); + exit (EXIT_FAILURE); + } + + data = (struct data) { .count = 2, }; + if (nbd_block_status (nbd, exportsize, 0, + (nbd_extent_callback) { .callback = cb, .user_data = &data }, + 0) == -1) { + fprintf (stderr, "%s\n", nbd_get_error ()); + exit (EXIT_FAILURE); + } + assert (data.seen_base && data.seen_dirty); + + data = (struct data) { .req_one = true, .count = 2, }; + if (nbd_block_status (nbd, exportsize, 0, + (nbd_extent_callback) { .callback = cb, .user_data = &data }, + LIBNBD_CMD_FLAG_REQ_ONE) == -1) { + fprintf (stderr, "%s\n", nbd_get_error ()); + exit (EXIT_FAILURE); + } + assert (data.seen_base && data.seen_dirty); + + /* Trigger a failed callback, to prove connection stays up. */ + data = (struct data) { .count = 2, .fail = true, }; + if (nbd_block_status (nbd, exportsize, 0, + (nbd_extent_callback) { .callback = cb, .user_data = &data }, + 0) != -1) { + fprintf (stderr, "unexpected block status success\n"); + exit (EXIT_FAILURE); + } + assert (nbd_get_errno () == EPROTO && nbd_aio_is_ready (nbd)); + assert (data.seen_base && data.seen_dirty); + + if (nbd_pread (nbd, &c, 1, 0, 0) == -1) { + fprintf (stderr, "%s\n", nbd_get_error ()); + exit (EXIT_FAILURE); + } + + if (nbd_shutdown (nbd, 0) == -1) { + fprintf (stderr, "%s\n", nbd_get_error ()); + exit (EXIT_FAILURE); + } + + nbd_close (nbd); + + exit (EXIT_SUCCESS); +} + +``` +3. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1311 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1311 new file mode 100644 index 000000000..382158be9 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1311 @@ -0,0 +1 @@ +riscv-qemu can't record interrupt diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1312 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1312 new file mode 100644 index 000000000..883708f95 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1312 @@ -0,0 +1,11 @@ +TCP performance problems - GSO/TSO, MSS, 8139 related (Ignores lower MTU from PMTUD/MSS) +Description of problem: +MTU handling on guests using an RTL8139 virtualized NIC is broken; net/hw/8139.c works with a static MTU of 1500b for TCP offloading, leading to low throughput when clients connect from sub 1500MTU networks. PMTUD is ignored, and locking to a lower MTU in the OS mitigates the issue. +Steps to reproduce: +1. Create a guest with an RTL8139 nic +2. Try to retrieve a file from a client behind a sub 1500 MTU link +3. Observe low bandwidth due to retransmits +Additional information: +I just debugged this issue for an NGO which, for whatever reason, had an RTL8139 NIC in their guest. After i finally traced this to the RTL8139, i found this qemu-devel/netdev thread from six years ago, which apparently already debugged this issue and proposed a patch: https://lore.kernel.org/all/20161114162505.GD26664@stefanha-x1.localdomain/ + +I did not test the patch proposed there, but note that `net/hw/8139.c` still looks as discussed in that qemu-devel/netdev thread. As i haven't found a bug report in the archives, i figured you might want to know. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1315 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1315 new file mode 100644 index 000000000..d4be1d04b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1315 @@ -0,0 +1 @@ +Assertion failure in vmxnet3_activate_device diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1316 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1316 new file mode 100644 index 000000000..95571fb6b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1316 @@ -0,0 +1 @@ +qemu.qmp.protocol.ConnectError: Failed to establish connection: AF_UNIX path too long (on Darwin) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1317 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1317 new file mode 100644 index 000000000..1b4026575 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1317 @@ -0,0 +1,49 @@ +"make-check avocado" doesn't work in ubuntu 1804 because of older versions of pip and setuputils +Description of problem: +make check-avocado tests don't run in Ubuntu 18.04, I get an error: + +`Command "python setup.py egg_info" failed with error code 1 in /qemu/python/` + +It looks like pip and setuputils are too old in 18.04 (which is still an active lts version supposedly). +Steps to reproduce: +Compile qemu in Ubuntu 18.04. This is an ad-hoc example with docker but I reproduced it in Ubuntu 18.04 VM too +1. Create docker from Dockerfile [Dockerfile](/uploads/a5748cabca5319f467cbc0b803ed9104/Dockerfile): + +<code>FROM ubuntu:18.04 +RUN apt update +RUN apt-get install -y git libglib2.0-dev libfdt-dev libpixman-1-dev zlib1g-dev ninja-build git-email libaio-dev libbluetooth-dev libcapstone-dev libbrlapi-dev libbz2-dev libcap-ng-dev libcurl4-gnutls-dev libgtk-3-dev libibverbs-dev libjpeg8-dev libncurses5-dev libnuma-dev librbd-dev librdmacm-dev libsasl2-dev libsdl2-dev libseccomp-dev libsnappy-dev libssh-dev libvde-dev libvdeplug-dev libvte-2.91-dev libxen-dev liblzo2-dev valgrind xfslibs-dev python3-venv</code> + +`docker build -t 1804qemuavocado .` + +2. Run shell inside of docker: + +`docker run -it 1804qemuavocado bash` + +3. Clone QEMU: + +`git clone --depth 1 https://github.com/qemu/qemu.git` + +4. Build QEMU (targets and parameters should not matter much): + +<code>cd qemu +mkdir build +cd build +../configure --target-list=x86_64-softmmu +ninja</code> + +5. Attempt to run tests: + +`make check-avocado` + +6. Get an error: + +<code>/usr/bin/python3 -B /qemu/meson/meson.py introspect --targets --tests --benchmarks | /usr/bin/python3 -B scripts/mtest2make.py > Makefile.mtest + GIT ui/keycodemapdb meson tests/fp/berkeley-testfloat-3 tests/fp/berkeley-softfloat-3 dtc + GIT ui/keycodemapdb meson tests/fp/berkeley-testfloat-3 tests/fp/berkeley-softfloat-3 dtc + VENV /qemu/build/tests/venv + VENVPIP install -e /qemu/python/ +Command "python setup.py egg_info" failed with error code 1 in /qemu/python/ +/qemu/tests/Makefile.include:115: recipe for target '/qemu/build/tests/venv' failed +make: *** [/qemu/build/tests/venv] Error 1</code> +Additional information: +As far as I understand, upgrading pip in system won't help, because venv creates an environment with base pip version (9 in case of Ubuntu 18.04). I tried creating a small patch [patch.diff](/uploads/0ae4883106773f0ea940d27b74219732/patch.diff) for tests/Makefile.include, that upgrades pip and setuputils in venv to the latest version, and it seem to help, but I don't know if it's the right solution to always have the latest version. Probably some LTS version should be chosen, if such thing exists for pip. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1318 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1318 new file mode 100644 index 000000000..768b14086 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1318 @@ -0,0 +1,19 @@ +vsock device fails with "qemu-system-x86_64: vhost_set_features failed: Operation not supported (95)" when queue_reset=true +Description of problem: +Immediately after guest vsock driver initialize, qemu prints error messages. I'm not able to connect to the guest with vsock: + +``` +[ 0.654463] Run /init as init process +[ 0.679778] NET: Registered PF_VSOCK protocol family +qemu-system-x86_64: vhost_set_features failed: Operation not supported (95) +qemu-system-x86_64: Error starting vhost: 95 +ssh-keygen: generating new host keys: RSA DSA ECDSA ED25519 +# +``` +Steps to reproduce: +1. Clone `git://passt.top/passt` +2. In `passt/test`, run `make mbuto.img` +3. Run `qemu-system-x86_64 -enable-kvm -m 2048 -kernel KERNEL -initrd mbuto.img -nographic -serial stdio -nodefaults -append "console=ttyS0" -device vhost-vsock-pci,guest-cid=31415,queue_reset=true` replacing KERNEL with the host kernel image. +Additional information: +- Problem goes away if `queue_reset=false`, which means it goes away with default options prior to `69e1c14aa222` ("virtio: core: vq reset feature negotation support") +- Occurs both with and without KVM diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1319 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1319 new file mode 100644 index 000000000..79f105948 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1319 @@ -0,0 +1,13 @@ +Build warnings when building qemu with 'disable-tcg' for ppc64-softmmu target +Description of problem: +Building recent upstream qemu (HEAD 2c8311241d) for 'ppc64-softmmu' target is failing due to following build warnings: + +<snip> + ../target/ppc/cpu_init.c:7018:13: error: 'ppc_restore_state_to_opc' defined but not used [-Werror=unused-function] + 7018 | static void ppc_restore_state_to_opc(CPUState *cs, +<snip> +Steps to reproduce: +1. $ git clone --recurse-submodules https://gitlab.com/qemu-project/qemu.git +2. ./configure --target-list=ppc64-softmmu --disable-tcg && make +Additional information: +Patch for this issue has been posted and reviewed at https://lore.kernel.org/all/20221116131743.658708-1-vaibhav@linux.ibm.com/ diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1321 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1321 new file mode 100644 index 000000000..613214ecd --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1321 @@ -0,0 +1,8 @@ +qemu-system-i386 runs slow after upgrading legacy project from qemu 2.9.0 to 7.1.0 +Description of problem: +Using several custom serial and irq devices including timers. +The same code (after some customisation in order to compile with new 7.1.0 API and meson build system runs about 50% slower. +We had to remove "-icount 4" switch which worked fine with 2.9.0 just to get to this point. +Even running with multi-threaded tcg did not help. +We don't use the new ptimer API but rather the old QEMUTimer. +Any suggestions to why we encounter this vast performance degradation? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1322 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1322 new file mode 100644 index 000000000..9c5b8c362 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1322 @@ -0,0 +1 @@ +Unknown protocol 'ssh' diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1329 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1329 new file mode 100644 index 000000000..355cd0e0d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1329 @@ -0,0 +1,12 @@ +Screen doesn't update until mouse pointer moves over it +Description of problem: +When changing the color scheme in CDE, the screen should change +color everywhere at once, but doesn't do so. It only updates +in the area where the mouse moves. And there it does so over +the whole width of the screen . +Steps to reproduce: +1. Change color scheme in CDE +2. Move around mouse pointer +Additional information: +Screen capture of the problem +https://youtu.be/qZJzACIxSuk diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/133 b/gitlab/issues_text/target_missing/host_missing/accel_missing/133 new file mode 100644 index 000000000..3f5ebd11c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/133 @@ -0,0 +1 @@ +Chardev websocket might not support pasting more than a few chars diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1330 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1330 new file mode 100644 index 000000000..2fa32996c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1330 @@ -0,0 +1,182 @@ +qemu-img finishes successfully while having errors in commit or bitmaps operations +Description of problem: +Problem raises when trying to merge two images with the top image almost +full, and base image having stale bitmaps (bitmaps missing from +the top image). +In our usercase, the size of the LV that contains the base image is not +accounting for the stale bitmaps, and therefore, when we run `commit` or +`bitmap --merge`, it fails with: +``` +qcow2_free_clusters failed: No space left on device +qemu-img: Lost persistent bitmaps during inactivation of node '#block308': Failed to write bitmap 'stale-bitmap-002' to file: No space left on device +qemu-img: Failed to flush the refcount block cache: No space left on device +``` +However, in both cases `qemu-img` returned successfully, +while having logs printed to `stderr`, and failing the merge. + +For commit operation, the data was commited successfully, it failed as it +was adding the bitmaps. +Still, the process exit with success. + +On the other hand, for bitmaps operation, since its main purpose is to +manipulate bitmaps, and it failed, it should not return with code 0. +The process shall return with error code. +Also, bitmaps in the base image are left with the `in-use` flag set. +Steps to reproduce: +1. Create these lvs and chown them to the user +``` +sudo lvcreate --name base.qcow2 --size 128m storage +sudo chown $USER:$USER /dev/mapper/storage-base.qcow2 +sudo lvcreate --name top.qcow2 --size 128m storage +sudo chown $USER:$USER /dev/mapper/storage-top.qcow2 +``` +2. Run this python script. Note the `STALE_BITMAPS` counter. Using 6, 11, or 13 stale + bitmaps, the `commit`, or the `bitmaps` operations shall fail. +``` +# Reproduce ENOSPC error when merging into base image with lot of bitmaps. + +import json +import subprocess + +IMG_SIZE = 1 << 30 +LV_SIZE = 128 << 20 + +# Testing shows that we can merge successfully with 13 bitmaps, and require +# size calculation is more strict, allowing up to 11 bitamps. +STALE_BITMAPS = 11 + +def run(*cmd): + subprocess.run(cmd, check=True) + +def output(cmd): + cp = subprocess.run(cmd, stdout=subprocess.PIPE, check=True) + return json.loads(cp.stdout) + +def info(img): + return output(["qemu-img", "info", "--output", "json", img]) + +def measure(img): + return output(["qemu-img", "measure", "-f", "qcow2", "-O", "qcow2", "--output", "json", img]) + +def check(img): + cmd = ["qemu-img", "check", "-f", "qcow2", "--output", "json", img] + cp = subprocess.run(cmd, stdout=subprocess.PIPE) + if cp.returncode not in (0, 3): + raise RuntimeError(f"Check failed") + + return json.loads(cp.stdout) + +def indent(info): + return json.dumps(info, indent=2) + +base = "/dev/mapper/storage-base.qcow2" +top = "/dev/mapper/storage-top.qcow2" + +# Start with clean lvs by discarding current data. +run("blkdiscard", base) +run("blkdiscard", top) + +print("Creating base") +run("qemu-img", "create", "-f", "qcow2", base, str(IMG_SIZE)) + +# Simulate stale bitmaps - missing in top. +for i in range(STALE_BITMAPS): + bitmap = f"stale-bitmap-{i:03d}" + print(f"Creating stale bitmap {bitmap}") + run("qemu-img", "bitmap", "--add", base, bitmap) + +print("Info base before merge") +base_info = info(base) +print(indent(base_info)) + +print("Check base before merge") +base_check = check(base) +print(indent(base_check)) + +print("Measure base before merge") +base_measure = measure(base) +print(indent(base_measure)) + +print("Creating top") +run("qemu-img", "create", "-f", "qcow2", "-b", base, "-F", "qcow2", top) + +print("Adding good bitmap to top") +run("qemu-img", "bitmap", "--add", top, "good-bitmap") + +print("Writing data to top") +cmd = f"write -P {ord('B')} 0 126m" +run("qemu-io", "-f", "qcow2", "-c", cmd, top) + +print("Info top before merge") +top_info = info(top) +print(indent(top_info)) + +print("Check top before merge") +top_check = check(top) +print(indent(top_check)) + +print("Measure top before merge") +top_measure = measure(top) +print(indent(top_measure)) + +print("Commit top into base") +run("qemu-img", "commit", "-f", "qcow2", "-t", "none", "-b", base, "-d", "-p", top) + +print("Add good bitmap to base") +run("qemu-img", "bitmap", "--add", base, "good-bitmap") + +print("Merge good bitmap from top to base") +run("qemu-img", "bitmap", "--merge", "good-bitmap", "-F", "qcow2", "-b", top, base, "good-bitmap") + +print("Info base after merge") +print(indent(info(base))) + +print("Check base after merge") +print(indent(check(base))) + +print("Measure base after merge") +print(indent(measure(base))) +``` +Additional information: +Example output of the script with 6 stale bitmaps: +``` +Commit top into base + (100.00/100%) +Image committed. +Add good bitmap to base +Merge good bitmap from top to base +qcow2_free_clusters failed: No space left on device +qemu-img: Lost persistent bitmaps during inactivation of node '#block159': Failed to write bitmap 'good-bitmap' to file: No space left on device +qemu-img: Failed to flush the refcount block cache: No space left on device +Info base after merge +{ + "virtual-size": 1073741824, + "filename": "/dev/mapper/storage-base.qcow2", + "cluster-size": 65536, + "format": "qcow2", + "actual-size": 0, + "format-specific": { + "type": "qcow2", + "data": { + "compat": "1.1", + "compression-type": "zlib", + "lazy-refcounts": false, + "bitmaps": [ + ... + { + "flags": [ + "in-use", + "auto" + ], + "name": "good-bitmap", + "granularity": 65536 + } + ], + "refcount-bits": 16, + "corrupt": false, + "extended-l2": false + } + }, + "dirty-flag": false +} +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1334 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1334 new file mode 100644 index 000000000..3b2cd3443 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1334 @@ -0,0 +1 @@ +qemu-img map qcow2 image,but can't get right zero area diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1335 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1335 new file mode 100644 index 000000000..23416da40 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1335 @@ -0,0 +1 @@ +hot to dump bitmap to disk diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1336 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1336 new file mode 100644 index 000000000..e115cff70 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1336 @@ -0,0 +1 @@ +QEMU qxl_phys2virt Unsafe Address Translation Lead to OOB Read diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1337 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1337 new file mode 100644 index 000000000..43bfefaa9 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1337 @@ -0,0 +1,16 @@ +Incorrect warnings when using vhost without numa +Description of problem: +Part A: Misleading error message. Running the above command for any architecture fails to initialize vhost, and prints the following, incorrect advice +``` +qemu-system-mips: Failed initializing vhost-user memory map, consider using -object memory-backend-file share=on +qemu-system-mips: vhost_set_mem_table failed: Invalid argument (22) +qemu-system-mips: Error starting vhost: 22 +``` + +Since the command line already contains `-object memory-backend-file,id=mem1,mem-path=/tmp/mem,size=256M,share=on` this error message should not be printed. For x86_64, this can be resolved by adding `-numa node,memdev=mem0` to the command line. As such, I think this error message should instead guide a user to adding that argument. + +Part B: No documented configuration to run vhost-user for machines that don't support numa. +The mips malta machine does not support the `-numa` flag. It is unclear if this means that `vhost` cannot be used with this platform or if a non-numa configuration with a memory-backend-file can be used. +Steps to reproduce: +1. Run `vhost-user-vsock --socket=/tmp/vhost4.socket --uds-path=/tmp/foo` from https://github.com/rust-vmm/vhost-device. +1. Run the above QEMU command diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1338 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1338 new file mode 100644 index 000000000..33ec60752 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1338 @@ -0,0 +1 @@ +Remove gprof diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1340 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1340 new file mode 100644 index 000000000..e1ac8a56c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1340 @@ -0,0 +1,66 @@ +Static build fail with native aarch64 toolchain (ld failure at linking aarch64_be target) +Description of problem: +Do a static build on aarch64, with ArchlinuxARM native toolchain (gcc 12.1.0, binutils 2.38) +Steps to reproduce: +Do a static build using the following configs: + +``` +./configure \ + --prefix=/usr \ + --sysconfdir=/etc \ + --libexecdir=/usr/lib/qemu \ + --enable-attr \ + --enable-linux-user \ + --enable-tcg \ + --disable-bpf \ + --disable-bsd-user \ + --disable-capstone \ + --disable-docs \ + --disable-fdt \ + --disable-gcrypt \ + --disable-glusterfs \ + --disable-gnutls \ + --disable-gtk \ + --disable-install-blobs \ + --disable-kvm \ + --disable-libiscsi \ + --disable-libnfs \ + --disable-libssh \ + --disable-linux-io-uring \ + --disable-nettle \ + --disable-opengl \ + --disable-qom-cast-debug \ + --disable-sdl \ + --disable-system \ + --disable-tools \ + --disable-tpm \ + --disable-vde \ + --disable-vhost-crypto \ + --disable-vhost-kernel \ + --disable-vhost-net \ + --disable-vhost-user \ + --disable-vnc \ + --disable-werror \ + --disable-xen \ + --disable-zstd \ + --static +``` + +The build failure looks like this: + +``` +[466/2962] Linking target qemu-aarch64_be +FAILED: qemu-aarch64_be +c++ -o qemu-aarch64_be libcommon.fa.p/hw_core_cpu-common.c.o libcommon.fa.p/hw_core_machine-smp.c.o libcommon.fa.p/cpus-common.c.o libcommon.fa.p/page-vary-common.c.o libcommon.fa.p/accel_accel-user.c.o libcommon.fa.p/common-user_safe-syscall.S.o libcommon.fa.p/common-user_safe-syscall-error.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_aarch64_signal.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_aarch64_cpu_loop.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_cpu.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_crypto_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_debug_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_gdbstub.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_iwmmxt_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_m_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_mve_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_neon_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_op_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_tlb_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_translate.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_translate-m-nocp.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_translate-mve.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_translate-neon.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_translate-vfp.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_vec_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_vfp_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_cpu_tcg.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_kvm-stub.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_cpu64.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_gdbstub64.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_helper-a64.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_mte_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_pauth_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_sve_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_sme_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_translate-a64.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_translate-sve.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_translate-sme.c.o libqemu-aarch64_be-linux-user.fa.p/trace_control-target.c.o libqemu-aarch64_be-linux-user.fa.p/cpu.c.o libqemu-aarch64_be-linux-user.fa.p/disas.c.o libqemu-aarch64_be-linux-user.fa.p/gdbstub.c.o libqemu-aarch64_be-linux-user.fa.p/page-vary.c.o libqemu-aarch64_be-linux-user.fa.p/semihosting_guestfd.c.o libqemu-aarch64_be-linux-user.fa.p/semihosting_syscalls.c.o libqemu-aarch64_be-linux-user.fa.p/semihosting_arm-compat-semi.c.o libqemu-aarch64_be-linux-user.fa.p/tcg_optimize.c.o libqemu-aarch64_be-linux-user.fa.p/tcg_region.c.o libqemu-aarch64_be-linux-user.fa.p/tcg_tcg.c.o libqemu-aarch64_be-linux-user.fa.p/tcg_tcg-common.c.o libqemu-aarch64_be-linux-user.fa.p/tcg_tcg-op.c.o libqemu-aarch64_be-linux-user.fa.p/tcg_tcg-op-gvec.c.o libqemu-aarch64_be-linux-user.fa.p/tcg_tcg-op-vec.c.o libqemu-aarch64_be-linux-user.fa.p/fpu_softfloat.c.o libqemu-aarch64_be-linux-user.fa.p/accel_accel-common.c.o libqemu-aarch64_be-linux-user.fa.p/accel_tcg_tcg-all.c.o libqemu-aarch64_be-linux-user.fa.p/accel_tcg_cpu-exec-common.c.o libqemu-aarch64_be-linux-user.fa.p/accel_tcg_cpu-exec.c.o libqemu-aarch64_be-linux-user.fa.p/accel_tcg_tcg-runtime-gvec.c.o libqemu-aarch64_be-linux-user.fa.p/accel_tcg_tcg-runtime.c.o libqemu-aarch64_be-linux-user.fa.p/accel_tcg_translate-all.c.o libqemu-aarch64_be-linux-user.fa.p/accel_tcg_translator.c.o libqemu-aarch64_be-linux-user.fa.p/accel_tcg_user-exec.c.o libqemu-aarch64_be-linux-user.fa.p/accel_tcg_user-exec-stub.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_elfload.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_exit.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_fd-trans.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_linuxload.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_main.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_mmap.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_signal.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_strace.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_syscall.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_thunk.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_uaccess.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_uname.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_flatload.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_semihost.c.o libqemu-aarch64_be-linux-user.fa.p/meson-generated_.._aarch64_be-linux-user-gdbstub-xml.c.o -Wl,--as-needed -Wl,--no-undefined -pie -Wl,--whole-archive libhwcore.fa libqom.fa -Wl,--start-group libevent-loop-base.a -Wl,--no-whole-archive -Wl,--warn-common -Wl,-z,relro -Wl,-z,now -static-pie -fstack-protector-strong -march=armv8-a -O2 -pipe -fstack-protector-strong -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security -fstack-clash-protection -Wp,-D_GLIBCXX_ASSERTIONS -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now libqemuutil.a libhwcore.fa libqom.fa /usr/lib/libz.a -lrt -lm -pthread -lgthread-2.0 -lglib-2.0 -lpcre2-8 -lsysprof-capture-4 -lstdc++ -Wl,--end-group +/usr/bin/ld: /usr/lib/gcc/aarch64-unknown-linux-gnu/12.1.0/../../../../lib/libglib-2.0.a(gutils.c.o): in function `g_get_user_database_entry': +(.text+0x324): warning: Using 'getpwuid' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking +/usr/bin/ld: (.text+0xf4): warning: Using 'getpwnam_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking +/usr/bin/ld: (.text+0xe0): warning: Using 'getpwuid_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking +/usr/lib/gcc/aarch64-unknown-linux-gnu/12.1.0/../../../../lib/libc.a(init-first.o): in function `__libc_init_first': +(.text+0x10): relocation truncated to fit: R_AARCH64_LD64_GOTPAGE_LO15 against symbol `__environ' defined in .bss section in /usr/lib/gcc/aarch64-unknown-linux-gnu/12.1.0/../../../../lib/libc.a(environ.o) +/usr/bin/ld: (.text+0x10): warning: too many GOT entries for -fpic, please recompile with -fPIC +collect2: error: ld returned 1 exit status +distcc[61410] ERROR: compile (null) on localhost failed +``` +Additional information: +Full [meson-log.txt](/uploads/05059722cb81b10bd9977a17fd51f048/meson-log.txt) and [config.log](/uploads/1cbd8a5fe5c48c3af83e1cbba6a89ce8/config.log) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1341 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1341 new file mode 100644 index 000000000..f30172c01 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1341 @@ -0,0 +1,78 @@ +Static build failure with clang (clang 14.0.6) +Description of problem: +Static build failure with redefinition of 'iovec'. + +The configure looks like this: + +``` + export CC=clang + ../$pkgbase-$pkgver/configure \ + --prefix=/usr \ + --sysconfdir=/etc \ + --libexecdir=/usr/lib/qemu \ + --enable-attr \ + --enable-linux-user \ + --enable-tcg \ + --disable-bpf \ + --disable-bsd-user \ + --disable-capstone \ + --disable-docs \ + --disable-fdt \ + --disable-gcrypt \ + --disable-glusterfs \ + --disable-gnutls \ + --disable-gtk \ + --disable-install-blobs \ + --disable-kvm \ + --disable-libiscsi \ + --disable-libnfs \ + --disable-libssh \ + --disable-linux-io-uring \ + --disable-nettle \ + --disable-opengl \ + --disable-qom-cast-debug \ + --disable-sdl \ + --disable-system \ + --disable-tools \ + --disable-tpm \ + --disable-vde \ + --disable-vhost-crypto \ + --disable-vhost-kernel \ + --disable-vhost-net \ + --disable-vhost-user \ + --disable-vnc \ + --disable-werror \ + --disable-xen \ + --disable-zstd \ + --static +``` + +The compiling failure looks like this: +``` +FAILED: libqom.fa.p/qom_object.c.o +clang -Ilibqom.fa.p -I. -I../qemu-7.1.0 -Iqapi -Itrace -Iui/shader -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/sysprof-4 -fcolor-diagnostics -Wall -Winvalid-pch -std=gnu11 -O2 -g -isystem /home/adam/qemu-user-static/src/qemu-7.1.0/linux-headers -isystem linux-headers -iquote . -iquote /home/adam/qemu-user-static/src/qemu-7.1.0 -iquote /home/adam/qemu-user-static/src/qemu-7.1.0/include -iquote /home/adam/qemu-user-static/src/qemu-7.1.0/tcg/aarch64 -pthread -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fno-common -fwrapv -Wold-style-definition -Wtype-limits -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body -Wnested-externs -Wendif-labels -Wexpansion-to-defined -Wno-initializer-overrides -Wno-missing-include-dirs -Wno-shift-negative-value -Wno-string-plus-int -Wno-typedef-redefinition -Wno-tautological-type-limit-compare -Wno-psabi -Wno-missing-braces -march=armv8-a -O2 -pipe -fstack-protector-strong -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security -fstack-clash-protection -fPIE -MD -MQ libqom.fa.p/qom_object.c.o -MF libqom.fa.p/qom_object.c.o.d -o libqom.fa.p/qom_object.c.o -c ../qemu-7.1.0/qom/object.c +distcc[94580] (dcc_build_somewhere) Warning: failed to distribute, running locally instead +clang-14: warning: argument unused during compilation: '-fstack-clash-protection' [-Wunused-command-line-argument] +In file included from ../qemu-7.1.0/qom/object.c:13: +/home/adam/qemu-user-static/src/qemu-7.1.0/include/qemu/osdep.h:517:8: error: redefinition of 'iovec' +struct iovec { + ^ +/usr/include/bits/types/struct_iovec.h:26:8: note: previous definition is here +struct iovec + ^ +In file included from ../qemu-7.1.0/qom/object.c:13: +/home/adam/qemu-user-static/src/qemu-7.1.0/include/qemu/osdep.h:524:9: warning: 'IOV_MAX' macro redefined [-Wmacro-redefined] +#define IOV_MAX 1024 + ^ +/usr/include/bits/xopen_lim.h:66:10: note: previous definition is here +# define IOV_MAX __IOV_MAX + ^ +1 warning and 1 error generated. +distcc[94580] ERROR: compile ../qemu-7.1.0/qom/object.c on localhost failed +ninja: build stopped: subcommand failed. +``` +Steps to reproduce: +1. Compile qemu using above configure and use clang as the compiler +Additional information: +Full meson log: +[meson-log.txt](/uploads/a63d609852148140e8fa7210c6912982/meson-log.txt) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1342 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1342 new file mode 100644 index 000000000..47664e458 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1342 @@ -0,0 +1,24 @@ +Default machine setting of force-legacy=true causes problems for any modern VirtIO device using MMIO +Description of problem: +The default causes problems if you enable any non-legacy VirtIO device which has the VIRTIO_F_VERSION_1 feature bit will not properly read all feature bits. This is because reading VIRTIO_MMIO_VERSION returns VIRT_VERSION_LEGACY which in turn results in the driver not reading all feature bits, e.g. the qtest access: + +``` +static uint64_t qvirtio_mmio_get_features(QVirtioDevice *d) +{ + QVirtioMMIODevice *dev = container_of(d, QVirtioMMIODevice, vdev); + uint64_t lo; + uint64_t hi = 0; + + qtest_writel(dev->qts, dev->addr + QVIRTIO_MMIO_HOST_FEATURES_SEL, 0); + lo = qtest_readl(dev->qts, dev->addr + QVIRTIO_MMIO_HOST_FEATURES); + + if (dev->version >= 2) { + qtest_writel(dev->qts, dev->addr + QVIRTIO_MMIO_HOST_FEATURES_SEL, 1); + hi = qtest_readl(dev->qts, dev->addr + QVIRTIO_MMIO_HOST_FEATURES); + } + + return (hi << 32) | lo; +} +``` +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1345 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1345 new file mode 100644 index 000000000..8a3593383 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1345 @@ -0,0 +1 @@ +qemu-img manpage and is missing info on compression_type option diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1346 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1346 new file mode 100644 index 000000000..5a4bee368 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1346 @@ -0,0 +1,35 @@ +simulate x86_64 virtio-gpu-gl qemu report error +Description of problem: +when I run the below command, it can run ok, and myos can get the virtio-gpu feature,but it less 3d feature. + ``` + ./qemu-system-x86_64 -nographic -M q35 -m 1024 -cpu Nehalem -smp 8 -kernel myos -device virtio-gpu + ``` +so I delete ```-nographic``` and modify the device to : +``` +-device virtio-gpu-gl -display sdl,gl=on +``` +but qemu tells me ERROR: +``` +qemu-system-x86_64: ../ui/console-gl.c:105: surface_gl_update_texture: Assertion `gls' failed. +``` +Additional information: +I modify the code qemu/ui/sdl2-gl.c function sdl2_gl_switch(): + +` +#if 0 +if (is_placeholder(new_surface) && qemu_console_get_index(dcl->con)) { + qemu_gl_fini_shader(scon->gls); + scon->gls = NULL; + sdl2_window_destroy(scon); + return; + } +#endif +` +and, qemu can run myos with ```-nographic```, and i can get 3d feature: + ``` + ./qemu-system-x86_64 -nographic -M q35 -m 1024 -cpu Nehalem -smp 8 -kernel myos -device virtio-gpu-gl -display sdl,gl=on + ``` + +I think there is something bug. + +thanks diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1349 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1349 new file mode 100644 index 000000000..af885029f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1349 @@ -0,0 +1,7 @@ +Windows Installer Error +Description of problem: +Windows Installer Barfs +Steps to reproduce: +1. Either run exe installer or do ```scoop update -g "qemu" ``` +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/135 b/gitlab/issues_text/target_missing/host_missing/accel_missing/135 new file mode 100644 index 000000000..f25fee502 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/135 @@ -0,0 +1 @@ +Cant compile qemu from source, get error about static declaration of memfd_create following non-static declaration diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1351 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1351 new file mode 100644 index 000000000..a8a260030 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1351 @@ -0,0 +1,5 @@ +qemu-system-x86_64 run win7 qcow2 got an exception +Description of problem: +when qemu-system-X86-64 run the win7 qcow2, qemu got an exception + +\*\* ERROR:../target/i386/tcg/sysemu/excp_helper.c:517:raise_stage2: code should not be reached Aborted (核心已转储) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1352 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1352 new file mode 100644 index 000000000..a7049fdd0 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1352 @@ -0,0 +1 @@ +Building hw-display-virtio-*-gl modules with empty source set diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1354 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1354 new file mode 100644 index 000000000..212863b6e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1354 @@ -0,0 +1 @@ +-device usb-tablet not working on android guest. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1355 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1355 new file mode 100644 index 000000000..109368528 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1355 @@ -0,0 +1 @@ +qemu-system-x86_64: Issue while setting TUNSETSTEERINGEBPF: Invalid argument with fd: 13, prog_fd: -1 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1356 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1356 new file mode 100644 index 000000000..d4e62b2db --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1356 @@ -0,0 +1,17 @@ +"-set device" doesn't work with device specified in json +Description of problem: +The above QEMU command line results in: +``` +qemu-system-x86_64: -set device.ua-igd.x-igd-gms=1: there is no device "ua-igd" defined +``` +While the following command works: +``` +qemu-system-x86_64 -accel kvm -m 8192 -nodefaults -display none -net none -device vfio-pci,host=0000:00:02.0,id=ua-igd -set device.ua-igd.x-igd-gms=1 +``` +libvirt has moved to the json device specification, therefore I can no longer associate use a <qemu:commandline> section to set driver options for a specific device with this broken id association. +Steps to reproduce: +1. Create a device with an ID and use -set device.$ID to set a driver option for the device +2. Note failure when using json device format vs legacy device specification +3. Profit +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1357 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1357 new file mode 100644 index 000000000..dbfcf7530 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1357 @@ -0,0 +1,9 @@ +qemu-img should generate VMDK with an EOS marker when `has_marker` flag enabled +Additional information: +I generate a empty volume with capacity 1G and try to deploy it as a part of OVF. This would fail. + +But when I append an EOS marker to that VMDK, which is actually a zeroed sector, the deployed procedure succeeded. + +This case merely happened if VMDK has data, since `qemu-img` always write at least one grain(64 KB). So the padding part will be recognized as EOS marker. + +I have written a temporary patch for this and it works fine for me. I'm glad to send it for review. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1358 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1358 new file mode 100644 index 000000000..d7e54c547 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1358 @@ -0,0 +1 @@ +Remove CPUState::trace_dstate diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1359 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1359 new file mode 100644 index 000000000..793aa8fe6 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1359 @@ -0,0 +1 @@ +open virtual format diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/136 b/gitlab/issues_text/target_missing/host_missing/accel_missing/136 new file mode 100644 index 000000000..7670ccaa6 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/136 @@ -0,0 +1 @@ +windows qemu-img create vpc/vhdx error diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1360 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1360 new file mode 100644 index 000000000..1a5771e75 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1360 @@ -0,0 +1,19 @@ +Starting using WSL fails even if the same image is valid when starting qemu directly from windows +Description of problem: +I'm trying to follow a rust tutorial on writing a custom OS in rust. https://os.phil-opp.com/minimal-rust-kernel/ +The problem occurse when trying to run qemu from wsl. If I run qemu from a windows command line everything works as expected. +If I run the os calling qemu (installed on windows) from wsl it fails with + +``` +ERROR:../../../block.c:1715:bdrv_open_driver: assertion failed: (is_power_of_2(bs->bl.request_alignment)) +Bail out! ERROR:../../../block.c:1715:bdrv_open_driver: assertion failed: (is_power_of_2(bs->bl.request_alignment)) +``` + +I also found an old bug report that seemed to be the same issue in the old issue tracker: https://bugs.launchpad.net/qemu/+bug/1893807 +Steps to reproduce: +1. Sample code can be found at `https://github.com/phil-opp/blog_os` branch: `post-02` +2. create wsl environment +3. run `cargo install bootimage` only required on the once to install bootimage +4. run `cargo build` +5. run `cargo bootimage` to create the image +6. `qemu-system-x86_64 -drive format=raw,file=target/x86_64-blog_os/debug/bootimage-blog-os.bin` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1362 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1362 new file mode 100644 index 000000000..4e8e4c4a9 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1362 @@ -0,0 +1,75 @@ +BLKZEROOUT ioct/write requests getting split a weird boundary (and for no apparent reason?) +Description of problem: +i was investigating into some performance weirdness with passthrough/directly-mapped SAS vs. SATA disk, which seems to relate to detect_zeroes feature (see https://forum.proxmox.com/threads/disk-passthrough-performance-weirdness.118943/#post-516599 ). + +apparently, writing zeroes to passtrough/direct-mapped sas disk ( ST4000NM0034 ) in virtual machine is MUCH slower then sata disk ( HGST HDN728080AL ). + +with detect_zeroes=on (default in proxmox) , qemu converts writes of zeroes into BLKZEROOUT ioctl issued to the target disk, and my sas disk is much much slower with this (<80MB/s in comparison to the sata disk with 200MB/s). + +i found that the sas disk needs 0.01s on average for this ioctl to finish, whereas sata disk needs 0.004s. + +writing zeroes to the device directly is at about 200MB/s for both of them, so having detect_zeroes=on a default does not seem to be an advantage on all circumstances. + +anyway, i have made a weird observation during analysis: + +inside the virtual machine, i'm writing to the virtual disk like this: + +``` +dd if=/dev/zero of=/dev/disk/by-id/scsi-0QEMU_QEMU_HARDDISK_drive-scsi1 bs=1024k count=1024 oflag=direct + +(scsi-0QEMU_QEMU_HARDDISK_drive-scsi1 mapped to scsi-35000c500836b1c73 / SAS on the host, scsi-0QEMU_QEMU_HARDDISK_drive-scsi2 mapped to ata-HGST_HDN728080ALE604_VJGDNX5X ) + +``` + +on the HOST i'm attaching to the kvm process with strace , every time i issue the above dd inside VM, kvm/qemu process issues BLKZEROOUT to the device in a different way, i.e. either + +- within a single ioctl at originating 1048576 byte size (=1024k) +or +- split into 2 ioctl with 1040384+8192(=1048576) +or +- split into 2 ioctl with 1044480+4096(=1048576) + + +why does kvm/qemu sometimes split the write request and sometimes not ? and why at such a weird boundary just below 1Mb? + + +i don't know if this is a bug, but at least it looks weird to me, that's why i'm reporting + +``` + +root@pve:~/util-linux/sys-utils# strace -T -f -p 18897 -e trace=all 2>&1 |grep BLK|head +[pid 65413] ioctl(19, BLKZEROOUT, [0, 1048576] <unfinished ...> +[pid 65412] ioctl(19, BLKZEROOUT, [1048576, 1048576] <unfinished ...> +[pid 65366] ioctl(19, BLKZEROOUT, [2097152, 1048576] <unfinished ...> +[pid 65413] ioctl(19, BLKZEROOUT, [3145728, 1048576] <unfinished ...> +[pid 65412] ioctl(19, BLKZEROOUT, [4194304, 1048576]) = 0 <0.011287> +[pid 65366] ioctl(19, BLKZEROOUT, [5242880, 1048576]) = 0 <0.012025> +[pid 65413] ioctl(19, BLKZEROOUT, [6291456, 1048576]) = 0 <0.011377> +[pid 65412] ioctl(19, BLKZEROOUT, [7340032, 1048576] <unfinished ...> +[pid 65366] ioctl(19, BLKZEROOUT, [8388608, 1048576] <unfinished ...> +[pid 65413] ioctl(19, BLKZEROOUT, [9437184, 1048576]) = 0 <0.011705> + +# strace -T -f -p 18897 -e trace=all 2>&1 |grep BLK|head +[pid 65878] ioctl(19, BLKZEROOUT, [0, 1040384] <unfinished ...> +[pid 65413] ioctl(19, BLKZEROOUT, [1040384, 8192] <unfinished ...> +[pid 65366] ioctl(19, BLKZEROOUT, [1048576, 1040384] <unfinished ...> +[pid 65878] ioctl(19, BLKZEROOUT, [2088960, 8192] <unfinished ...> +[pid 65413] ioctl(19, BLKZEROOUT, [2097152, 1040384] <unfinished ...> +[pid 65366] ioctl(19, BLKZEROOUT, [3137536, 8192] <unfinished ...> +[pid 65413] ioctl(19, BLKZEROOUT, [3145728, 1040384] <unfinished ...> +[pid 65878] ioctl(19, BLKZEROOUT, [4186112, 8192] <unfinished ...> +[pid 65366] ioctl(19, BLKZEROOUT, [4194304, 1040384] <unfinished ...> +[pid 65413] ioctl(19, BLKZEROOUT, [5234688, 8192] <unfinished ...> + +root@pve:~/util-linux/sys-utils# strace -T -f -p 18897 -e trace=all 2>&1 |grep BLK|head +[pid 66591] ioctl(19, BLKZEROOUT, [0, 1044480] <unfinished ...> +[pid 66592] ioctl(19, BLKZEROOUT, [1044480, 4096] <unfinished ...> +[pid 66593] ioctl(19, BLKZEROOUT, [1048576, 1044480] <unfinished ...> +[pid 66584] ioctl(19, BLKZEROOUT, [2093056, 4096] <unfinished ...> +[pid 66585] ioctl(19, BLKZEROOUT, [2097152, 1044480] <unfinished ...> +[pid 66565] ioctl(19, BLKZEROOUT, [3141632, 4096] <unfinished ...> +[pid 66591] ioctl(19, BLKZEROOUT, [3145728, 1044480] <unfinished ...> +[pid 66592] ioctl(19, BLKZEROOUT, [4190208, 4096] <unfinished ...> +[pid 66584] ioctl(19, BLKZEROOUT, [4194304, 1044480] <unfinished ...> +[pid 66593] ioctl(19, BLKZEROOUT, [5238784, 4096] <unfinished ... +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1365 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1365 new file mode 100644 index 000000000..5a53908fd --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1365 @@ -0,0 +1,24 @@ +qemu on m1 mac loses network connection after some time running +Description of problem: +While running qemu with podman machine on m1 mac, after a while the network connections will stop answering. +When running with the console window dmesg will start showing the following messages +``` +uq: 0x1, name: output.0, 2263286224 uses ago +[37689.0770611 virtio_net virtioo emposi: TX timeout on queue: 0, sq: output.o, uq: 0x1, name: output.0, 2268226224 uses ago +[37693.7877481 virtio_net virtio@ emposi: TX timeout on queue: 0, sq: output.o, uq: 0x1, name: output.0, 2273326224 uses ago +[37698.3116991 virtio_net virtioo emposi: TX timeout on queue: 0, sq: output.o, uq: 0x1, name: output.0, 2278226224 uses ago +[37702.9616661 virtio_net virtioo emposi: TX timeout on queue: 0, sq: output.o, uq: 0x1, name: output.0, 2283266224 uses ago +[37707.5462551 virtio_net virtiod empos1: IX timeout on queue: 0, sq: output.O, ug: Ox1, name: output.O, 2288226224 usecs ago +[37712.205242) virtio_net virtio@ enposI: IX timeout on queue: 0, sq: output.o, uq: 0x1, name: output. 0, 2293276224 uses ago +[37716.7708171 virtio_net virtiod enpOsi: IX timeout on queue: 0, sq: output.o, uq: 0x1, name: output. 0, 2298226224 uses ago + +``` +Steps to reproduce: +1. Run `/opt/homebrew/bin/qemu-system-aarch64 -m 12048 -smp 8 -fw_cfg name=opt/com.coreos/config,file=$HOME/.config/containers/podman/machine/qemu/podman-machine-default.ign -qmp unix:$TEMP/podman/qmp_podman-machine-default.sock,server=on,wait=off -netdev socket,id=vlan,fd=3 -device virtio-net-pci,netdev=vlan,mac=5a:94:ef:e4:0c:ee -device virtio-serial -chardev socket,path=$TEMP/podman/podman-machine-default_ready.sock,server=on,wait=off,id=apodman-machine-default_ready -device virtserialport,chardev=apodman-machine-default_ready,name=org.fedoraproject.port.0 -pidfile $TEMP/podman/podman-machine-default_vm.pid -accel hvf -accel tcg -cpu host -M virt,highmem=on -drive file=/opt/homebrew/share/qemu/edk2-aarch64-code.fd,if=pflash,format=raw,readonly=on -drive file=$HOME/.local/share/containers/podman/machine/qemu/podman-machine-default_ovmf_vars.fd,if=pflash,format=raw -virtfs local,path=$HOME,mount_tag=vol0,security_model=mapped-xattr -drive if=virtio,file=$HOME/.local/share/containers/podman/machine/qemu/podman-machine-default_fedora-coreos-37.20221127.2.0-qemu.aarch64.qcow2` +2. Keep using the system and eventually `ssh localhost +3. +Additional information: +network configuration + + +I will try to add more info as I get them diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1366 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1366 new file mode 100644 index 000000000..b75affe75 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1366 @@ -0,0 +1,84 @@ +Data inconsistency on LVM logical volume mounted as partition on ubuntu guest, when the written file's size is equal or greater than 27G. +Description of problem: +On the guest, writing a 27Gib file or larger result in inconsistent file checksum upon subsequent read. +Steps to reproduce: +**On the host** + +0. Create a LVM logical volume on a Linux RAID 1 (with 1 disk only) + +``` + --- Logical volume --- + LV Path /dev/davidahw2-vg4/lv0 + LV Name lv0 + VG Name davidahw2-vg4 + LV UUID 5FbDcl-eSDe-7cXL-22tj-Lg6O-79AL-4Gq7gx + LV Write Access read/write + LV Creation host, time davida-hw2, 2021-12-06 16:45:00 +0800 + LV Status available + # open 1 + LV Size <7.28 TiB + Current LE 1907688 + Segments 1 + Allocation inherit + Read ahead sectors auto + - currently set to 256 + Block device 253:4 + + --- Segments --- + Logical extents 0 to 1907687: + Type linear + Physical volume /dev/md4 + Physical extents 0 to 1907687 +``` + +1. Format the logical volume as ext4 + +``` +mkfs -t ext4 /dev/davidahw2-vg4/lv0 +``` + +2. Create a libvirt x86 64bits Ubuntu 22.04 machine mounting a LVM logical volume + +``` +<controller type='scsi' index='1' model='virtio-scsi'><driver queues='8' iothread='2'/></controller> + + +<disk type='block' device='disk'> + <driver name='qemu' type='raw'/> + <source dev='/dev/davidahw2-vg4/lv0'/> + <target dev='sdd' bus='scsi'/> + <blockio logical_block_size='512' physical_block_size='4096'/> + <address type='drive' controller='1' bus='0' target='1' unit='0'/> +</disk> +``` + + +**On the guest** + +3. Mount libvirt/qemu provided block device /dev/sdd as ext4 partition + +``` +mount /dev/sdd /mnt/test +``` + +4. Write **27G file** or larger **on the guest** causing the **2nd checksum to be different** + +``` +sync; head -c 27G </dev/urandom >myfile; sha256sum myfile; sha256sum myfile +8d3b4b263961d2c510390f99879be89b4b9134dc588139ede75573be1590115b myfile +a8e886b3c39d9b4721e582c5e2ca25c76ff6561750ac6dc7aa7e70404661d1cf myfile <== ERROR: Inconsistent checksum +``` + +5. Write **26G file** or larger **on the guest** and **both checksum are the same** + +``` +sync; head -c 26G </dev/urandom >myfile; sha256sum myfile; sha256sum myfile +598ac5da9b5bfa14d0ee664ae2590e09da772cba64cbc83ec049a656223c9401 myfile +598ac5da9b5bfa14d0ee664ae2590e09da772cba64cbc83ec049a656223c9401 myfile <== CORRECT: Consistent checksum +``` + +**Important**: +- With the VM shutdown, the same commands on the same mounted ext4 partition **on the host** has consistent checksum every time for file sizes from 20G to 40G. +- The disk has no sign of failure (no badblocks reported to the filesystem, MD raid reports a healthy raid setup, smart reports on error) +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1367 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1367 new file mode 100644 index 000000000..eafc569f4 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1367 @@ -0,0 +1,5 @@ +Support MMIO devices in VFIO +Additional information: +- https://lore.kernel.org/qemu-devel/cover.1667542066.git.john.g.johnson@oracle.com/ +- https://github.com/nutanix/libvfio-user +- It also *somewhat* related to supporting non-PCI devices in `ivshmem`: https://gitlab.com/qemu-project/qemu/-/issues/1134 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1369 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1369 new file mode 100644 index 000000000..9ae06b912 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1369 @@ -0,0 +1 @@ +'make vm-build-openbsd' fails to notice when QEMU fails to start diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/137 b/gitlab/issues_text/target_missing/host_missing/accel_missing/137 new file mode 100644 index 000000000..d51a9649a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/137 @@ -0,0 +1 @@ +Incompatibility with future VTE will breaks qemu monitor (::commit signal) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1378 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1378 new file mode 100644 index 000000000..39d0c151b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1378 @@ -0,0 +1,20 @@ +iSCSI causes memory corruption +Description of problem: +This is a compound problem, which most likely involves a combination of how TrueNAS SCALE handles iSCSI triggering a problem **and** some memory-handling issue in QEMU leading to a crash. In short any Linux machine started with iSCSI handled by QEMU directly leads to a hard crash within 30s-1h. I was able to find a pattern in logs: + +1. First, a message like `QEMU[53139]: kvm: iSCSI Busy/TaskSetFull/TimeOut (retry #1 in 0 ms): TASK_SET_FULL` is logged + - it is always `TASK_SET_FULL` + - it is always `retry #1 in ... ms`, where only number of miliseconds varies + - the line is repeated multiple times, sometimes 5x and sometimes >200x +2. It is followed by a single line with one of the following: + - `double free or corruption (out)` + - `double free or corruption (!prev)` + - `kvm: ../block/block-backend.c:1567: blk_aio_write_entry: Assertion `!qiov || qiov->size == acb->bytes' failed.` + - `kvm: malloc.c:2379: sysmalloc: Assertion `(old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)' failed.` + - `kvm: iSCSI CheckCondition: SENSE KEY:UNIT_ATTENTION(6) ASCQ:BUS_RESET(0x2900)` + - `malloc(): invalid size (unsorted)` +3. The virtual machine crashes +Steps to reproduce: +I don't have a specific concrete steps, only clues really. This problem started happening after TrueNAS SCALE updated their iSCSI code in Bluefin release to a new upstream version. That iSCSI server still works when iSCSI is mounted by the kernel and QEMU uses a normal `/dev` entry. While there's probably some problem with it, QEMU shouldn't probably crash with memory errors. +Additional information: +While I'm a software developer, I don't code in C on a daily basis. However, looking at the errors, I have a suspicion the problem may be somewhere in the `iscsi_co_generic_cb()`, as it seems the struct is getting damaged (out of bound write?) and causes explosion somewhere down the line. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1379 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1379 new file mode 100644 index 000000000..1702d6a67 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1379 @@ -0,0 +1 @@ +dump memory read write operations diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/138 b/gitlab/issues_text/target_missing/host_missing/accel_missing/138 new file mode 100644 index 000000000..d0741e2e1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/138 @@ -0,0 +1 @@ +Exclude keys from grab diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1380 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1380 new file mode 100644 index 000000000..d6721cf6d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1380 @@ -0,0 +1,4 @@ +vdagent is not working properly after live migration +Additional information: +when validating on windows server 2016 Datacenter Evaluation, i found that if vdagent process or vdservice is restarted, copy/paste from host to guest or reverse will work again. i am wondering if we should send something(eg, a event?) to guest to let it reopen the port after live migration? + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1381 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1381 new file mode 100644 index 000000000..cd14a192f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1381 @@ -0,0 +1,3 @@ +plugins: plugin_mem_cbs is not consistently NULL'ed when returning from execution +Description of problem: +This is an invariant that we should have been checking for; when returning from execution, cpu->plugin_mem_cbs should be NULL. Otherwise we open a door for a use-after-free; admittedly this door isn't that large (it requires a tb_flush to occur while we have the dangling plugin_mem_cbs), but at least one plugin user has encountered this problem: https://lists.nongnu.org/archive/html/qemu-devel/2022-11/msg02703.html diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1384 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1384 new file mode 100644 index 000000000..c9c3085e3 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1384 @@ -0,0 +1 @@ +Update libvfio-user to latest upstream diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1385 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1385 new file mode 100644 index 000000000..db55d6411 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1385 @@ -0,0 +1 @@ +-net option doesn't work diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1386 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1386 new file mode 100644 index 000000000..8cb217760 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1386 @@ -0,0 +1,628 @@ +Qemu 7.2.0 - Failed compilation under Windows with MSYS (MINGW64) +Description of problem: +I follow the faq here + +https://wiki.qemu.org/Hosts/W32#Debian_based_cross_builds + +to compile qemu source under Windows with MSYS2 (MINGW64). +Steps to reproduce: +Follow the FAQ guide and I get + +``` +xxxx@DESKTOP-NBACH6G MINGW64 ~/qemu +$ ./configure --enable-sdl --enable-gtk +Using './build' as the directory for build output +ln: failed to create symbolic link 'aarch64-softmmu/qemu-system-aarch64.exe': No such file or directory +ln: failed to create symbolic link 'alpha-softmmu/qemu-system-alpha.exe': No such file or directory +ln: failed to create symbolic link 'arm-softmmu/qemu-system-arm.exe': No such file or directory +ln: failed to create symbolic link 'avr-softmmu/qemu-system-avr.exe': No such file or directory +ln: failed to create symbolic link 'cris-softmmu/qemu-system-cris.exe': No such file or directory +ln: failed to create symbolic link 'hppa-softmmu/qemu-system-hppa.exe': No such file or directory +ln: failed to create symbolic link 'i386-softmmu/qemu-system-i386.exe': No such file or directory +ln: failed to create symbolic link 'loongarch64-softmmu/qemu-system-loongarch64.exe': No such file or directory +ln: failed to create symbolic link 'm68k-softmmu/qemu-system-m68k.exe': No such file or directory +ln: failed to create symbolic link 'microblaze-softmmu/qemu-system-microblaze.exe': No such file or directory +ln: failed to create symbolic link 'microblazeel-softmmu/qemu-system-microblazeel.exe': No such file or directory +ln: failed to create symbolic link 'mips-softmmu/qemu-system-mips.exe': No such file or directory +ln: failed to create symbolic link 'mips64-softmmu/qemu-system-mips64.exe': No such file or directory +ln: failed to create symbolic link 'mips64el-softmmu/qemu-system-mips64el.exe': No such file or directory +ln: failed to create symbolic link 'mipsel-softmmu/qemu-system-mipsel.exe': No such file or directory +ln: failed to create symbolic link 'nios2-softmmu/qemu-system-nios2.exe': No such file or directory +ln: failed to create symbolic link 'or1k-softmmu/qemu-system-or1k.exe': No such file or directory +ln: failed to create symbolic link 'ppc-softmmu/qemu-system-ppc.exe': No such file or directory +ln: failed to create symbolic link 'ppc64-softmmu/qemu-system-ppc64.exe': No such file or directory +ln: failed to create symbolic link 'riscv32-softmmu/qemu-system-riscv32.exe': No such file or directory +ln: failed to create symbolic link 'riscv64-softmmu/qemu-system-riscv64.exe': No such file or directory +ln: failed to create symbolic link 'rx-softmmu/qemu-system-rx.exe': No such file or directory +ln: failed to create symbolic link 's390x-softmmu/qemu-system-s390x.exe': No such file or directory +ln: failed to create symbolic link 'sh4-softmmu/qemu-system-sh4.exe': No such file or directory +ln: failed to create symbolic link 'sh4eb-softmmu/qemu-system-sh4eb.exe': No such file or directory +ln: failed to create symbolic link 'sparc-softmmu/qemu-system-sparc.exe': No such file or directory +ln: failed to create symbolic link 'sparc64-softmmu/qemu-system-sparc64.exe': No such file or directory +ln: failed to create symbolic link 'tricore-softmmu/qemu-system-tricore.exe': No such file or directory +ln: failed to create symbolic link 'x86_64-softmmu/qemu-system-x86_64.exe': No such file or directory +ln: failed to create symbolic link 'xtensa-softmmu/qemu-system-xtensa.exe': No such file or directory +ln: failed to create symbolic link 'xtensaeb-softmmu/qemu-system-xtensaeb.exe': No such file or directory +The Meson build system +Version: 0.64.1 +Source dir: C:/msys64/home/Roberto/qemu +Build dir: C:/msys64/home/Roberto/qemu/build +Build type: native build +Project name: qemu +Project version: 7.2.50 +C compiler for the host machine: cc -m64 -mcx16 (gcc 12.2.0 "cc (Rev6, Built by MSYS2 project) 12.2.0") +C linker for the host machine: cc -m64 -mcx16 ld.bfd 2.39 +Host machine cpu family: x86_64 +Host machine cpu: x86_64 +Program scripts/symlink-install-tree.py found: YES (C:/msys64/mingw64/bin/python.exe C:/msys64/home/Roberto/qemu/scripts/symlink-install-tree.py) +Program sh found: YES (C:\msys64\usr\bin/sh.EXE) +Program python3 found: YES (C:/msys64/mingw64/bin/python.exe) +Program bzip2 found: YES (C:\msys64\mingw64\bin/bzip2.EXE) +Program iasl found: NO +Compiler for C supports link arguments -Wl,-z,relro: NO +Compiler for C supports link arguments -Wl,-z,now: NO +Compiler for C supports link arguments -Wl,--no-seh: YES +Compiler for C supports link arguments -Wl,--nxcompat: YES +C++ compiler for the host machine: c++ -m64 -mcx16 (gcc 12.2.0 "c++ (Rev6, Built by MSYS2 project) 12.2.0") +C++ linker for the host machine: c++ -m64 -mcx16 ld.bfd 2.39 +Compiler for C++ supports link arguments -Wl,--warn-common: YES +Program cgcc found: NO +Library m found: YES +Run-time dependency threads found: YES +Library util found: NO +Program midl found: NO +Program widl found: YES +Library pathcch found: YES +Library ws2_32 found: YES +Library winmm found: YES +Windows resource compiler: GNU windres (GNU Binutils) 2.39 +Has header "WinHvPlatform.h" : YES +Has header "WinHvEmulation.h" : YES +Run-time dependency appleframeworks found: NO (tried framework) +Found pkg-config: C:\msys64\mingw64\bin/pkg-config.EXE (1.8.0) +Run-time dependency gio-2.0 found: YES 2.74.3 +Program C:/msys64/mingw64/bin/gdbus-codegen found: YES (C:/msys64/mingw64/bin/gdbus-codegen.exe) +Run-time dependency gio-unix-2.0 found: NO (tried pkgconfig) +Run-time dependency pixman-1 found: YES 0.42.2 +Run-time dependency zlib found: YES 1.2.13 +Has header "libaio.h" : NO +Run-time dependency liburing found: NO (tried pkgconfig) +Run-time dependency libnfs found: YES 5.0.2 +Has header "attr/xattr.h" : NO +Run-time dependency appleframeworks found: NO (tried framework) +Run-time dependency appleframeworks found: NO (tried framework) +Run-time dependency libseccomp found: NO (tried pkgconfig) +Has header "cap-ng.h" : NO +Run-time dependency xkbcommon found: NO (tried pkgconfig) +Run-time dependency slirp found: YES 4.7.0 +Has header "libvdeplug.h" : NO +Run-time dependency jack found: NO (tried pkgconfig) +Run-time dependency sndio found: NO (tried pkgconfig) +Run-time dependency spice-protocol found: YES 0.14.4 +Run-time dependency spice-server found: YES 0.15.1 +Library rt found: NO +Run-time dependency libiscsi found: NO (tried pkgconfig) +Run-time dependency libzstd found: YES 1.5.2 +Run-time dependency virglrenderer found: NO (tried pkgconfig) +Run-time dependency blkio found: NO (tried pkgconfig) +Run-time dependency libcurl found: YES 7.86.0 +Run-time dependency ncurses found: NO (tried pkgconfig) +Run-time dependency ncursesw found: YES 6.3.20211021 +Has header "brlapi.h" : NO +Run-time dependency sdl2 found: YES 2.26.1 +Run-time dependency sdl2_image found: YES 2.6.2 +Library rados found: NO +Has header "rbd/librbd.h" : NO +Run-time dependency glusterfs-api found: NO (tried pkgconfig) +Run-time dependency libssh found: YES 0.10.4 +Has header "bzlib.h" : YES +Library bz2 found: YES +Has header "lzfse.h" : NO +Has header "sys/soundcard.h" : NO +Has header "dsound.h" : YES +Run-time dependency epoxy found: YES 1.5.10 +Has header "epoxy/egl.h" with dependency epoxy: NO +Run-time dependency gnutls found: YES 3.7.8 +Run-time dependency gmp found: YES 6.2.1 +Run-time dependency gtk+-3.0 found: YES 3.24.35 +Run-time dependency gtk+-x11-3.0 found: NO (tried pkgconfig) +Run-time dependency vte-2.91 found: NO (tried pkgconfig) +Run-time dependency libpng found: YES 1.6.39 +Run-time dependency libjpeg found: YES 2.1.4 +Has header "sasl/sasl.h" : YES +Library sasl2 found: YES +Has header "security/pam_appl.h" : NO +Has header "snappy-c.h" : YES +Library snappy found: YES +Has header "lzo/lzo1x.h" : YES +Library lzo2 found: YES +Has header "numa.h" : NO +Library ibumad found: NO +Has header "rdma/rdma_cma.h" : NO +Library ibverbs found: NO +Run-time dependency xencontrol found: NO (tried pkgconfig) +Library xenstore found: NO +Library xenctrl found: NO +Library xendevicemodel found: NO +Library xenforeignmemory found: NO +Library xengnttab found: NO +Library xenevtchn found: NO +Library xentoolcore found: NO +Run-time dependency libcacard found: NO (tried pkgconfig) +Run-time dependency u2f-emu found: NO (tried pkgconfig) +Run-time dependency canokey-qemu found: NO (tried pkgconfig) +Run-time dependency libusbredirparser-0.5 found: YES 0.8.0 +Run-time dependency libusb-1.0 found: YES 1.0.26 +Run-time dependency libpmem found: NO (tried pkgconfig) +Run-time dependency libdaxctl found: NO (tried pkgconfig) +Run-time dependency libtasn1 found: YES 4.19.0 +Run-time dependency libkeyutils found: NO (tried pkgconfig) +Checking for function "gettid" : NO +Run-time dependency libselinux found: NO (tried pkgconfig) +Run-time dependency fuse3 found: NO (tried pkgconfig) +Run-time dependency libbpf found: NO (tried pkgconfig) +Checking for function "pthread_fchdir_np" : NO +Has header "sys/epoll.h" : NO +Has header "linux/magic.h" : NO +Has header "valgrind/valgrind.h" : NO +Has header "linux/btrfs.h" : NO +Has header "libdrm/drm.h" : NO +Has header "pty.h" : NO +Has header "sys/disk.h" : NO +Has header "sys/ioccom.h" : NO +Has header "sys/kcov.h" : NO +Has header "afunix.h" : YES +Checking for function "close_range" : NO +Checking for function "accept4" : NO +Checking for function "clock_adjtime" : NO +Checking for function "dup3" : NO +Checking for function "fallocate" : NO +Checking for function "posix_fallocate" : NO +Checking for function "posix_memalign" : NO +Checking for function "_aligned_malloc" : YES +Checking for function "valloc" : NO +Checking for function "memalign" : NO +Checking for function "ppoll" : NO +Checking for function "preadv" : NO +Checking for function "pthread_fchdir_np" : NO (cached) +Checking for function "sendfile" : NO +Checking for function "setns" : NO +Checking for function "syncfs" : NO +Checking for function "sync_file_range" : NO +Checking for function "timerfd_create" : NO +Checking for function "copy_file_range" : NO +Checking for function "getifaddrs" : NO +Checking for function "openpty" with dependency -lutil: NO +Checking for function "strchrnul" : NO +Checking for function "system" : YES +Header "byteswap.h" has symbol "bswap_32" : NO +Header "sys/epoll.h" has symbol "epoll_create1" : NO +Header "linux/falloc.h" has symbol "FALLOC_FL_PUNCH_HOLE" : NO +Header "linux/falloc.h" has symbol "FALLOC_FL_ZERO_RANGE" : NO +Has header "linux/fiemap.h" : NO +Checking for function "getrandom" : NO +Header "sys/inotify.h" has symbol "inotify_init" : NO +Header "sys/inotify.h" has symbol "inotify_init1" : NO +Header "machine/bswap.h" has symbol "bswap32" : NO +Header "sys/prctl.h" has symbol "PR_SET_TIMERSLACK" : NO +Header "linux/rtnetlink.h" has symbol "IFLA_PROTO_DOWN" : NO +Header "sys/sysmacros.h" has symbol "makedev" : NO +Header "getopt.h" has symbol "optreset" : NO +Header "netinet/in.h" has symbol "IPPROTO_MPTCP" : NO +Header "sys/mount.h" has symbol "FSCONFIG_SET_FLAG" : NO +Checking whether type "struct sigevent" has member "sigev_notify_thread_id" : NO +Checking whether type "struct stat" has member "st_atim" : NO +Checking for type "struct iovec" : NO +Checking for type "struct utmpx" : NO +Checking for type "struct mmsghdr" : NO +Header "linux/vm_sockets.h" has symbol "AF_VSOCK" : NO +Has header "vscoordint.h" : NO +Checking if "_lock_file and _unlock_file" : links: YES +Program scripts/minikconf.py found: YES (C:/msys64/mingw64/bin/python.exe C:/msys64/home/Roberto/qemu/scripts/minikconf.py) +Configuring aarch64-softmmu-config-target.h using configuration +Configuring aarch64-softmmu-config-devices.mak with command +Reading depfile: C:/msys64/home/Roberto/qemu/build/meson-private/aarch64-softmmu-config-devices.mak.d +Configuring aarch64-softmmu-config-devices.h using configuration +Configuring alpha-softmmu-config-target.h using configuration +Configuring alpha-softmmu-config-devices.mak with command +Reading depfile: C:/msys64/home/Roberto/qemu/build/meson-private/alpha-softmmu-config-devices.mak.d +Configuring alpha-softmmu-config-devices.h using configuration +Configuring arm-softmmu-config-target.h using configuration +Configuring arm-softmmu-config-devices.mak with command +Reading depfile: C:/msys64/home/Roberto/qemu/build/meson-private/arm-softmmu-config-devices.mak.d +Configuring arm-softmmu-config-devices.h using configuration +Configuring avr-softmmu-config-target.h using configuration +Configuring avr-softmmu-config-devices.mak with command +Reading depfile: C:/msys64/home/Roberto/qemu/build/meson-private/avr-softmmu-config-devices.mak.d +Configuring avr-softmmu-config-devices.h using configuration +Configuring cris-softmmu-config-target.h using configuration +Configuring cris-softmmu-config-devices.mak with command +Reading depfile: C:/msys64/home/Roberto/qemu/build/meson-private/cris-softmmu-config-devices.mak.d +Configuring cris-softmmu-config-devices.h using configuration +Configuring hppa-softmmu-config-target.h using configuration +Configuring hppa-softmmu-config-devices.mak with command +Reading depfile: C:/msys64/home/Roberto/qemu/build/meson-private/hppa-softmmu-config-devices.mak.d +Configuring hppa-softmmu-config-devices.h using configuration +Configuring i386-softmmu-config-target.h using configuration +Configuring i386-softmmu-config-devices.mak with command +Reading depfile: C:/msys64/home/Roberto/qemu/build/meson-private/i386-softmmu-config-devices.mak.d +Configuring i386-softmmu-config-devices.h using configuration +Configuring loongarch64-softmmu-config-target.h using configuration +Configuring loongarch64-softmmu-config-devices.mak with command +Reading depfile: C:/msys64/home/Roberto/qemu/build/meson-private/loongarch64-softmmu-config-devices.mak.d +Configuring loongarch64-softmmu-config-devices.h using configuration +Configuring m68k-softmmu-config-target.h using configuration +Configuring m68k-softmmu-config-devices.mak with command +Reading depfile: C:/msys64/home/Roberto/qemu/build/meson-private/m68k-softmmu-config-devices.mak.d +Configuring m68k-softmmu-config-devices.h using configuration +Configuring microblaze-softmmu-config-target.h using configuration +Configuring microblaze-softmmu-config-devices.mak with command +Reading depfile: C:/msys64/home/Roberto/qemu/build/meson-private/microblaze-softmmu-config-devices.mak.d +Configuring microblaze-softmmu-config-devices.h using configuration +Configuring microblazeel-softmmu-config-target.h using configuration +Configuring microblazeel-softmmu-config-devices.mak with command +Reading depfile: C:/msys64/home/Roberto/qemu/build/meson-private/microblazeel-softmmu-config-devices.mak.d +Configuring microblazeel-softmmu-config-devices.h using configuration +Configuring mips-softmmu-config-target.h using configuration +Configuring mips-softmmu-config-devices.mak with command +Reading depfile: C:/msys64/home/Roberto/qemu/build/meson-private/mips-softmmu-config-devices.mak.d +Configuring mips-softmmu-config-devices.h using configuration +Configuring mips64-softmmu-config-target.h using configuration +Configuring mips64-softmmu-config-devices.mak with command +Reading depfile: C:/msys64/home/Roberto/qemu/build/meson-private/mips64-softmmu-config-devices.mak.d +Configuring mips64-softmmu-config-devices.h using configuration +Configuring mips64el-softmmu-config-target.h using configuration +Configuring mips64el-softmmu-config-devices.mak with command +Reading depfile: C:/msys64/home/Roberto/qemu/build/meson-private/mips64el-softmmu-config-devices.mak.d +Configuring mips64el-softmmu-config-devices.h using configuration +Configuring mipsel-softmmu-config-target.h using configuration +Configuring mipsel-softmmu-config-devices.mak with command +Reading depfile: C:/msys64/home/Roberto/qemu/build/meson-private/mipsel-softmmu-config-devices.mak.d +Configuring mipsel-softmmu-config-devices.h using configuration +Configuring nios2-softmmu-config-target.h using configuration +Configuring nios2-softmmu-config-devices.mak with command +Reading depfile: C:/msys64/home/Roberto/qemu/build/meson-private/nios2-softmmu-config-devices.mak.d +Configuring nios2-softmmu-config-devices.h using configuration +Configuring or1k-softmmu-config-target.h using configuration +Configuring or1k-softmmu-config-devices.mak with command +Reading depfile: C:/msys64/home/Roberto/qemu/build/meson-private/or1k-softmmu-config-devices.mak.d +Configuring or1k-softmmu-config-devices.h using configuration +Configuring ppc-softmmu-config-target.h using configuration +Configuring ppc-softmmu-config-devices.mak with command +Reading depfile: C:/msys64/home/Roberto/qemu/build/meson-private/ppc-softmmu-config-devices.mak.d +Configuring ppc-softmmu-config-devices.h using configuration +Configuring ppc64-softmmu-config-target.h using configuration +Configuring ppc64-softmmu-config-devices.mak with command +Reading depfile: C:/msys64/home/Roberto/qemu/build/meson-private/ppc64-softmmu-config-devices.mak.d +Configuring ppc64-softmmu-config-devices.h using configuration +Configuring riscv32-softmmu-config-target.h using configuration +Configuring riscv32-softmmu-config-devices.mak with command +Reading depfile: C:/msys64/home/Roberto/qemu/build/meson-private/riscv32-softmmu-config-devices.mak.d +Configuring riscv32-softmmu-config-devices.h using configuration +Configuring riscv64-softmmu-config-target.h using configuration +Configuring riscv64-softmmu-config-devices.mak with command +Reading depfile: C:/msys64/home/Roberto/qemu/build/meson-private/riscv64-softmmu-config-devices.mak.d +Configuring riscv64-softmmu-config-devices.h using configuration +Configuring rx-softmmu-config-target.h using configuration +Configuring rx-softmmu-config-devices.mak with command +Reading depfile: C:/msys64/home/Roberto/qemu/build/meson-private/rx-softmmu-config-devices.mak.d +Configuring rx-softmmu-config-devices.h using configuration +Configuring s390x-softmmu-config-target.h using configuration +Configuring s390x-softmmu-config-devices.mak with command +Reading depfile: C:/msys64/home/Roberto/qemu/build/meson-private/s390x-softmmu-config-devices.mak.d +Configuring s390x-softmmu-config-devices.h using configuration +Configuring sh4-softmmu-config-target.h using configuration +Configuring sh4-softmmu-config-devices.mak with command +Reading depfile: C:/msys64/home/Roberto/qemu/build/meson-private/sh4-softmmu-config-devices.mak.d +Configuring sh4-softmmu-config-devices.h using configuration +Configuring sh4eb-softmmu-config-target.h using configuration +Configuring sh4eb-softmmu-config-devices.mak with command +Reading depfile: C:/msys64/home/Roberto/qemu/build/meson-private/sh4eb-softmmu-config-devices.mak.d +Configuring sh4eb-softmmu-config-devices.h using configuration +Configuring sparc-softmmu-config-target.h using configuration +Configuring sparc-softmmu-config-devices.mak with command +Reading depfile: C:/msys64/home/Roberto/qemu/build/meson-private/sparc-softmmu-config-devices.mak.d +Configuring sparc-softmmu-config-devices.h using configuration +Configuring sparc64-softmmu-config-target.h using configuration +Configuring sparc64-softmmu-config-devices.mak with command +Reading depfile: C:/msys64/home/Roberto/qemu/build/meson-private/sparc64-softmmu-config-devices.mak.d +Configuring sparc64-softmmu-config-devices.h using configuration +Configuring tricore-softmmu-config-target.h using configuration +Configuring tricore-softmmu-config-devices.mak with command +Reading depfile: C:/msys64/home/Roberto/qemu/build/meson-private/tricore-softmmu-config-devices.mak.d +Configuring tricore-softmmu-config-devices.h using configuration +Configuring x86_64-softmmu-config-target.h using configuration +Configuring x86_64-softmmu-config-devices.mak with command +Reading depfile: C:/msys64/home/Roberto/qemu/build/meson-private/x86_64-softmmu-config-devices.mak.d +Configuring x86_64-softmmu-config-devices.h using configuration +Configuring xtensa-softmmu-config-target.h using configuration +Configuring xtensa-softmmu-config-devices.mak with command +Reading depfile: C:/msys64/home/Roberto/qemu/build/meson-private/xtensa-softmmu-config-devices.mak.d +Configuring xtensa-softmmu-config-devices.h using configuration +Configuring xtensaeb-softmmu-config-target.h using configuration +Configuring xtensaeb-softmmu-config-devices.mak with command +Reading depfile: C:/msys64/home/Roberto/qemu/build/meson-private/xtensaeb-softmmu-config-devices.mak.d +Configuring xtensaeb-softmmu-config-devices.h using configuration +Program scripts/make-config-poison.sh found: YES (sh C:/msys64/home/Roberto/qemu/scripts/make-config-poison.sh) +Run-time dependency capstone found: YES 4.0.2 +Library fdt found: NO +Configuring config-host.h using configuration +Program scripts/hxtool found: YES (sh C:/msys64/home/Roberto/qemu/scripts/hxtool) +Program scripts/shaderinclude.pl found: YES (perl C:/msys64/home/Roberto/qemu/scripts/shaderinclude.pl) +Program scripts/qapi-gen.py found: YES (C:/msys64/mingw64/bin/python.exe C:/msys64/home/Roberto/qemu/scripts/qapi-gen.py) +Program scripts/qemu-version.sh found: YES (sh C:/msys64/home/Roberto/qemu/scripts/qemu-version.sh) +Program scripts/decodetree.py found: YES (C:/msys64/mingw64/bin/python.exe C:/msys64/home/Roberto/qemu/scripts/decodetree.py) +Program ../scripts/modules/module_block.py found: YES (C:/msys64/mingw64/bin/python.exe C:/msys64/home/Roberto/qemu/block/../scripts/modules/module_block.py) +Program ../scripts/block-coroutine-wrapper.py found: YES (C:/msys64/mingw64/bin/python.exe C:/msys64/home/Roberto/qemu/block/../scripts/block-coroutine-wrapper. +py) +Program scripts/modinfo-collect.py found: YES (C:/msys64/mingw64/bin/python.exe C:/msys64/home/Roberto/qemu/scripts/modinfo-collect.py) +Program scripts/modinfo-generate.py found: YES (C:/msys64/mingw64/bin/python.exe C:/msys64/home/Roberto/qemu/scripts/modinfo-generate.py) +Program nm found: YES +Program scripts/undefsym.py found: YES (C:/msys64/mingw64/bin/python.exe C:/msys64/home/Roberto/qemu/scripts/undefsym.py) +Program scripts/feature_to_c.sh found: YES (sh C:/msys64/home/Roberto/qemu/scripts/feature_to_c.sh) +Compiler for C supports link arguments -fstack-protector-all: YES +Compiler for C supports link arguments -fstack-protector-strong: YES +Compiler for C supports link arguments -Wl,--add-stdcall-alias: YES +Compiler for C supports link arguments -Wl,--enable-stdcall-fixup: YES +Library ole32 found: YES +Library oleaut32 found: YES +Library shlwapi found: YES +Library uuid found: YES +Library intl found: YES +Program wixl found: NO +Configuring 50-edk2-i386-secure.json using configuration +Configuring 50-edk2-x86_64-secure.json using configuration +Configuring 60-edk2-aarch64.json using configuration +Configuring 60-edk2-arm.json using configuration +Configuring 60-edk2-i386.json using configuration +Configuring 60-edk2-x86_64.json using configuration +Program qemu-keymap found: NO +Program sphinx-build found: YES (C:\msys64\mingw64\bin/sphinx-build.EXE) +../docs/meson.build:74: WARNING: Project targets '>=0.61.3' but uses feature deprecated since '0.60.0': install_subdir with empty directory. It worked by accide +nt and is buggy. Use install_emptydir instead. +Program diff found: YES (C:\msys64\usr\bin/diff.EXE) +Program dbus-daemon found: NO +Did not find CMake 'cmake' +Found CMake: NO +Run-time dependency gvnc-1.0 found: NO (tried pkgconfig and cmake) +Program initrd-stress.sh found: YES (sh C:/msys64/home/Roberto/qemu/tests/migration/initrd-stress.sh) +Program xgettext found: YES (C:\msys64\mingw64\bin/xgettext.EXE) +Program msgfmt found: YES (C:\msys64\mingw64\bin/msgfmt.EXE) +Program msginit found: YES (C:\msys64\mingw64\bin/msginit.EXE) +Program msgmerge found: YES (C:\msys64\mingw64\bin/msgmerge.EXE) +Program xgettext found: YES (C:\msys64\mingw64\bin/xgettext.EXE) +Program scripts/nsis.py found: YES (C:/msys64/mingw64/bin/python.exe C:/msys64/home/Roberto/qemu/scripts/nsis.py) +Build targets in project: 639 +WARNING: Deprecated features used: + * 0.60.0: {'install_subdir with empty directory'} + +qemu 7.2.50 + + Directories + Install prefix : C:/msys64/qemu + BIOS directory : share/ + firmware path : share/qemu-firmware + binary directory : C:/msys64/qemu/. + library directory : C:/msys64/qemu/lib + module directory : lib/ + libexec directory : C:/msys64/qemu/libexec + include directory : C:/msys64/qemu/include + config directory : C:/msys64/qemu/etc + local state directory : queried at runtime + Doc directory : C:/msys64/qemu/share/doc + Build directory : C:/msys64/home/xxx/qemu/build + Source path : C:/msys64/home/xxx/qemu + GIT submodules : ui/keycodemapdb tests/fp/berkeley-testfloat-3 tests/fp/berkeley-softfloat-3 dtc + + Host binaries + git : git + make : make + python : C:/msys64/mingw64/bin/python.exe (version: 3.10) + sphinx-build : C:\msys64\mingw64\bin/sphinx-build.EXE + gdb : /mingw64/bin/gdb-multiarch + iasl : NO + genisoimage : + wixl : NO + smbd : NO + + Configurable features + Documentation : YES + system-mode emulation : YES + user-mode emulation : NO + block layer : YES + Install blobs : YES + module support : NO + fuzzing support : NO + Audio drivers : dsound sdl + Trace backends : log + D-Bus display : NO + QOM debugging : NO + vhost-kernel support : NO + vhost-net support : NO + vhost-user support : NO + vhost-user-crypto support : NO + vhost-user-blk server support: NO + vhost-vdpa support : NO + build guest agent : YES + + Compilation + host CPU : x86_64 + host endianness : little + C compiler : cc -m64 -mcx16 + Host C compiler : cc -m64 -mcx16 + C++ compiler : c++ -m64 -mcx16 + CFLAGS : -O2 -g + CXXFLAGS : -O2 -g + QEMU_CFLAGS : -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fno-pie -no-pie -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prot +otypes -Wredundant-decls -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fno-common -fwrapv -Wold-style-declaration -Wold-style-definition -W +type-limits -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body -Wnested-externs -Wendif-labels -Wexpansion-to-defined -Wimplicit-fallt +hrough=2 -Wno-missing-include-dirs -Wno-shift-negative-value -Wno-psabi -fstack-protector-strong + QEMU_CXXFLAGS : -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fno-pie -no-pie -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wundef -Wwri +te-strings -fno-strict-aliasing -fno-common -fwrapv -Wtype-limits -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body -Wendif-labels -W +expansion-to-defined -Wimplicit-fallthrough=2 -Wno-missing-include-dirs -Wno-shift-negative-value -Wno-psabi -fstack-protector-strong + QEMU_OBJCFLAGS : -Wold-style-declaration -Wold-style-definition -Wtype-limits -Winit-self -Wempty-body -Wnested-externs -Wendif-labels -Wexpan +sion-to-defined -Wimplicit-fallthrough=2 -Wno-missing-include-dirs -Wno-shift-negative-value -Wno-psabi + QEMU_LDFLAGS : -fstack-protector-strong -Wl,--no-seh -Wl,--nxcompat -Wl,--warn-common + profiler : NO + link-time optimization (LTO) : NO + PIE : NO + static build : NO + malloc trim support : NO + membarrier : NO + debug stack usage : NO + mutex debugging : NO + memory allocator : system + avx2 optimization : YES + avx512f optimization : NO + gprof enabled : NO + gcov : NO + thread sanitizer : NO + CFI support : NO + strip binaries : NO + sparse : NO + mingw32 support : YES + + Cross compilers + x86_64 : cc + + Targets and accelerators + KVM support : NO + HAX support : YES + HVF support : NO + WHPX support : YES + NVMM support : NO + Xen support : NO + TCG support : YES + TCG backend : native (x86_64) + TCG plugins : NO + TCG debug enabled : NO + target list : aarch64-softmmu alpha-softmmu arm-softmmu avr-softmmu cris-softmmu hppa-softmmu i386-softmmu loongarch64-softmmu m68k-softmmu + microblaze-softmmu microblazeel-softmmu mips-softmmu mips64-softmmu mips64el-softmmu mipsel-softmmu nios2-softmmu or1k-softmmu ppc-softmmu ppc64-softmmu riscv3 +2-softmmu riscv64-softmmu rx-softmmu s390x-softmmu sh4-softmmu sh4eb-softmmu sparc-softmmu sparc64-softmmu tricore-softmmu x86_64-softmmu xtensa-softmmu xtensae +b-softmmu + default devices : YES + out of process emulation : NO + vfio-user server : NO + + Block layer support + coroutine backend : win32 + coroutine pool : YES + Block whitelist (rw) : + Block whitelist (ro) : + Use block whitelist in tools : NO + VirtFS support : NO + build virtiofs daemon : NO + Live block migration : YES + replication support : YES + bochs support : YES + cloop support : YES + dmg support : YES + qcow v1 support : YES + vdi support : YES + vvfat support : YES + qed support : YES + parallels support : YES + FUSE exports : NO + VDUSE block exports : NO + + Crypto + TLS priority : NORMAL + GNUTLS support : YES 3.7.8 + GNUTLS crypto : YES + libgcrypt : NO + nettle : NO + AF_ALG support : NO + rng-none : NO + Linux keyring : NO + + Dependencies + SDL support : YES + SDL image support : YES 2.6.2 + GTK support : YES + pixman : YES 0.42.2 + VTE support : NO + slirp support : YES 4.7.0 + libtasn1 : YES 4.19.0 + PAM : NO + iconv support : YES + curses support : YES + virgl support : NO + blkio support : NO + curl support : YES 7.86.0 + Multipath support : NO + PNG support : YES 1.6.39 + VNC support : YES + VNC SASL support : YES + VNC JPEG support : YES 2.1.4 + DirectSound support : YES + JACK support : NO + brlapi support : NO + vde support : NO + netmap support : NO + l2tpv3 support : NO + Linux AIO support : NO + Linux io_uring support : NO + ATTR/XATTR support : NO + RDMA support : NO + PVRDMA support : NO + fdt support : internal + libcap-ng support : NO + bpf support : NO + spice protocol support : YES 0.14.4 + spice server support : YES 0.15.1 + rbd support : NO + smartcard support : NO + U2F support : NO + libusb : YES 1.0.26 + usb net redir : YES 0.8.0 + OpenGL support (epoxy) : NO + GBM : NO + libiscsi support : NO + libnfs support : YES 5.0.2 + QGA VSS support : YES + seccomp support : NO + GlusterFS support : NO + TPM support : NO + libssh support : YES 0.10.4 + lzo support : YES + snappy support : YES + bzip2 support : YES + lzfse support : NO + zstd support : YES 1.5.2 + NUMA host support : NO + capstone : YES 4.0.2 + libpmem support : NO + libdaxctl support : NO + libudev : NO + FUSE lseek : NO + selinux : NO + + User defined options + Native files : config-meson.cross + bindir : + prefix : C:/msys64/qemu + werror : true + b_pie : false + gtk : enabled + qemu_suffix : + sdl : enabled + vfio_user_server : disabled + +Found ninja-1.11.1 at C:/msys64/mingw64/bin/ninja.exe +Running postconf script 'C:/msys64/mingw64/bin/python.exe C:/msys64/home/Roberto/qemu/scripts/symlink-install-tree.py' +--- stdout --- + +--- stderr --- +error making symbolic link C:/msys64/qemu/share/trace-events-all +Traceback (most recent call last): + File "C:\msys64\home\Roberto\qemu\scripts\symlink-install-tree.py", line 33, in <module> + raise e + File "C:\msys64\home\Roberto\qemu\scripts\symlink-install-tree.py", line 29, in <module> + os.symlink(source, bundle_dest) +OSError: [WinError 1314] Il privilegio richiesto non appartiene al client: 'C:/msys64/home/Roberto/qemu/build/trace/trace-events-all' -> 'qemu-bundle/msys64/qem +u/share/trace-events-all' +``` +Additional information: +The line below ensures that proper tags are added to the issue. +Please do not remove it. +--> diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1387 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1387 new file mode 100644 index 000000000..c1bdaaa66 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1387 @@ -0,0 +1,9 @@ +QEMU - Add in the FAQ info how to compile Windows x86/x64 installer under Linux Ubuntu +Description of problem: +Please add in the FAQ + +https://wiki.qemu.org/Hosts/W32#Debian_based_cross_builds + +detailed info step by stepo how to create windows x86 and x64 instalelr under Ubuntu +Steps to reproduce: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1388 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1388 new file mode 100644 index 000000000..f9e002372 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1388 @@ -0,0 +1,14 @@ +QEMU 7.2.0 - Update file repository with x86/x64 Windows installer +Description of problem: +In file repository + +https://qemu.weilnetz.de/w32/ +https://qemu.weilnetz.de/w64/ + +are not availble Windows installer for x86 and x64 platform and QEMU final 7.2.0. + +The latest version is 7.2.0.RC4 (08.12.2022). + +Thanks. +Steps to reproduce: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1389 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1389 new file mode 100644 index 000000000..1dfcb22b2 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1389 @@ -0,0 +1,61 @@ +Qemu 7.2.0 My hobbby bootloader seemed to stop working +Description of problem: +I wrote a BIOS bootloader and OS, but updated to QEMU 7.2.0 and now I get an exception in my bootloader. +Specifically I am getting a page fault on the first line of map_pd: +``` +next_pdpt: + ; PDPT + mov [0xa000 + rdx * 8], rax ; PDPT[rdx] -> PD + and al, 0xfc ;; clear bits 1 and 2 + + mov rcx, 0 +map_pd: + mov [rax + rcx * 8], rdi ; PD[rcx] -> rax + add rdi, 0x200000 ; maps first 512 * 0x200000 or 1 GiB + sub rsi, 1 + cmp rsi, 0 + je done_map_rest + + add rcx, 1 + cmp rcx, 512 + jb map_pd + + add rdx, 1 ; do next GiB + add rax, 0x1000 ; next PD + or rax, (1 | 2) + + jmp next_pdpt +``` +I am getting the exception: +``` +check_exception old: 0xffffffff new 0xe + 0: v=0e e=0002 i=0 cpl=0 IP=0008:0000000000001311 pc=0000000000001311 SP=0010:0000000000007bf8 CR2=000000000020c000 +RAX=000000000020c000 RBX=00000000000b8040 RCX=0000000000000000 RDX=0000000000000201 +RSI=000000000003fe00 RDI=0000008040000083 RBP=0000000000000008 RSP=0000000000007bf8 +R8 =0000000000000000 R9 =0000000000000000 R10=0000000000000000 R11=0000000000000000 +R12=0000000000000000 R13=0000000000000000 R14=0000000000000000 R15=0000000000000000 +RIP=0000000000001311 RFL=00000046 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0 +ES =0010 0000000000000000 00000000 00009300 DPL=0 DS [-WA] +CS =0008 0000000000000000 00000000 00209a00 DPL=0 CS64 [-R-] +SS =0010 0000000000000000 00000000 00009300 DPL=0 DS [-WA] +DS =0010 0000000000000000 00000000 00009300 DPL=0 DS [-WA] +FS =0010 0000000000000000 00000000 00009300 DPL=0 DS [-WA] +GS =0010 0000000000000000 00000000 00009300 DPL=0 DS [-WA] +LDT=0000 0000000000000000 0000ffff 00008200 DPL=0 LDT +TR =0000 0000000000000000 0000ffff 00008b00 DPL=0 TSS64-busy +GDT= 0000000000001888 00000018 +IDT= 0000000090909000 00000000 +CR0=80000011 CR2=000000000020c000 CR3=0000000000009000 CR4=00000020 +DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 +DR6=00000000ffff0ff0 DR7=0000000000000400 +CCS=0000000000000200 CCD=0000000000000000 CCO=LOGICB +EFER=0000000000000500 +``` + +I am able to read the 0x20c000 address with gdb +Steps to reproduce: +1. clone and build https://github.com/darbysauter/myOS +2. run with `make run` on 7.0.0 +3. run with `make run` on 7.2.0 and there is an exception +Additional information: +I looked through the changelogs from 7.1 and 7.2 and nothing stood out to me. Not sure if some behaviour changed or some default changed. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/139 b/gitlab/issues_text/target_missing/host_missing/accel_missing/139 new file mode 100644 index 000000000..0295590c2 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/139 @@ -0,0 +1 @@ +kvm rbd driver (and maybe others, i.e. qcow2, qed and so on) does not report DISCARD-ZERO flag diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1391 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1391 new file mode 100644 index 000000000..b601002c7 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1391 @@ -0,0 +1,28 @@ +virtio-blk: BDRV_REQ_REGISTERED_BUF optimization hint crashes on macOS +Description of problem: +When using QEMU 7.2.0 on macOS with the virtio-blk drive, the process will exit and QMP shows a `BLOCK_IO_ERROR` event. This appears to be caused by this line: https://gitlab.com/qemu-project/qemu/-/blob/master/hw/block/virtio-blk.c#L405 introduced in https://gitlab.com/qemu-project/qemu/-/commit/baf422684d73c7bf38e2c18815e18d44fcf395b6 + +Commenting that line out fixes the issue. +Steps to reproduce: +1. Run the QEMU command above with a Ubuntu 22.04 server ISO image. +2. Follow the installer and try to get to the end. +3. The process will crash before you can finish installing. +Additional information: +Following event appears on QMP: +``` +{ + data = { + action = report; + device = "drive437EC806-41A4-4CCE-A747-713352E7C27C"; + "node-name" = "#block785"; + nospace = 0; + operation = write; + reason = "Invalid argument"; + }; + event = "BLOCK_IO_ERROR"; + timestamp = { + microseconds = 808474; + seconds = 1671867673; + }; +} +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1392 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1392 new file mode 100644 index 000000000..c0dd7085a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1392 @@ -0,0 +1,14 @@ +qemu 7.2.0 almalinux 9.1 guest vda io error +Description of problem: +after update the qemu from 7.1.0 to 7.2.0 guest almalinux 9.1 have disk io error ,log : +```log +Dec 24 00:17:39 rlh1 kernel: I/O error, dev vda, sector 109770720 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 +Dec 24 00:17:42 rlh1 kernel: dm-0: writeback error on inode 33585275, offset 4096, sector 33359840 +Dec 24 00:17:42 rlh1 kernel: I/O error, dev vda, sector 109770776 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 +Dec 24 00:17:42 rlh1 kernel: dm-0: writeback error on inode 33585275, offset 4096, sector 33359896 +Dec 24 00:17:42 rlh1 kernel: I/O error, dev vda, sector 109770832 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 +``` + +then I switch back to version 7.1.0 it work as normal +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1393 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1393 new file mode 100644 index 000000000..5f535120b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1393 @@ -0,0 +1,65 @@ +Abort in audio_calloc() of ac97 +Description of problem: +Section 5.10.2 of the AC97 specification (https://hands.com/~lkcl/ac97_r23.pdf) +shows the feasibility to support for rates other than 48kHZ. Specifically, +AC97_PCM_Front_DAC_Rate (reg 2Ch) should be from 8kHZ to 48kHZ. + + +An adversary can leverage this to crash QEMU. + +A nornal 48kHZ setting is like this. + +``` +ac97_realize + open_voice + as->freq = 0xbb80 # 0xbb80=48000 + AUD_open_out + audio_pcm_create_voice_pair_out (sw is NULL) + audio_pcm_sw_init_out + sw->info.freq = as->freq (in audio_pcm_init_info()) + sw->ratio = ((int64_t) sw->hw->info.freq << 32) / sw->info.freq + samples = ((int64_t) sw->HWBUF->size << 32) / sw->ratio (in audio_pcm_sw_alloc_resources_out()) +``` + +A non-48kHZ setting is like this. Since `as->freq` is too small, `sw->ratio` is +too large. Finally, `samples` is zero, failing the audio_calloc() in +audio_pcm_sw_alloc_resources_out(). + +``` +nam_writew + open_voice + as->freq = 0x6 + AUD_open_out + audio_pcm_sw_init_out (sw is not NULL) + sw->info.freq = as->freq (in audio_pcm_init_info()) + sw->ratio = ((int64_t) sw->hw->info.freq << 32) / sw->info.freq + samples = ((int64_t) sw->HWBUF->size << 32) / sw->ratio (in audio_pcm_sw_alloc_resources_out()) + audio_calloc(.., samples, ) (in audio_pcm_sw_alloc_resources_out()) +``` +Steps to reproduce: +1. download the prepared rootfs and the image. + + https://drive.google.com/file/d/1IfVCvn76HY-Eb4AZU7yvuyPzM3QC1q10/view?usp=sharing + https://drive.google.com/file/d/1JN6JgvOSI5aSLIdTEFKiskKbrGWFo0BO/view?usp=sharing + +2. run the following script. + +``` bash +QEMU_PATH=../../../qemu-devel/build/x86_64-softmmu/qemu-system-x86_64 +KERNEL_PATH=./bzImage +ROOTFS_PATH=./rootfs.ext2 +$QEMU_PATH \ + -M q35 -m 1G \ + -kernel $KERNEL_PATH \ + -drive file=$ROOTFS_PATH,if=virtio,format=raw \ + -append "root=/dev/vda console=ttyS0" \ + -net nic,model=virtio -net user \ + -device ac97,audiodev=snd0 -audiodev none,id=snd0 \ + -nographic +``` + +3. with spawned shell (the user is root and the password is empty), run +`ac97-00`. +Additional information: +In the latest QEMU, this issue was generally fixed by 12f4abf6a245c43d8411577fd400373c85f08c6b and 0cbc8bd4694f32687bf47c6da48efa48fac35fd2 that remove abort() from the source code. Even though, I still plan to send a +patch so that the warning about the invalid freq will be gone. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1397 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1397 new file mode 100644 index 000000000..00aac1814 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1397 @@ -0,0 +1 @@ +riscv: break, hbreak does not set a breakpoint on the correct address when providing symbols diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/140 b/gitlab/issues_text/target_missing/host_missing/accel_missing/140 new file mode 100644 index 000000000..4a7ae0afa --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/140 @@ -0,0 +1 @@ +linux-user clone() can't handle glibc posix_spawn() (causes locale-gen to assert) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1401 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1401 new file mode 100644 index 000000000..288ef050c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1401 @@ -0,0 +1,20 @@ +configure uses break outside loop +Description of problem: +When running `configure` in version 7.2.0, the following message is printed multiple times: + +``` +qemu/configure: line 1885: break: only meaningful in a `for', `while', or `until' loop +``` +Steps to reproduce: +Running `configure` should be enough. My complete configure command is: + +``` +/bin/bash ./configure \ + --prefix=$PREFIX/qemu --sysconfdir=/etc$PREFIX/qemu \ + --includedir=$PREFIX/qemu/include --bindir=$PREFIX/qemu/bin \ + --sbindir=$PREFIX/qemu/sbin --libdir=$PREFIX/qemu/lib/amd64 \ + --libexecdir=$PREFIX/qemu/libexec/amd64 \ + --localstatedir=/var$PREFIX/qemu +``` +Additional information: +The `configure` script has `break;` in a conditional, where `:` would suffice (or the conditional could just be negated) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1403 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1403 new file mode 100644 index 000000000..b43800f98 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1403 @@ -0,0 +1 @@ +qemu 7.2: test-io-channel-command fails sporadically diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1404 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1404 new file mode 100644 index 000000000..1c1807490 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1404 @@ -0,0 +1,14 @@ +qemu-7.2: virtio-blk-pci I/O errors with detect-zeroes=unmap +Description of problem: +Since upgrading from qemu-7.1 to qemu-7.2 I have seen many anomalies with VMs that use the virtio-blk-pci device for the root filesystem and the `detect-zeroes=unmap` option, typically in the form of I/O errors or huge decreases in read/write performance. This has been observed for both pre-existing Linux & Windows systems using the QCOW2 disk format, and a freshly created Linux system. + +* For an existing x86_64 Windows-10 guest system, hosted on Debian-11, the guest system takes many minutes to boot and Task Manager shows the virtual disk showing read/write latencies measured in seconds rather than milliseconds. +* Attempts to create a new x86_64 Debian-11 guest on a Debian-11 host produce an input/output error when trying to partition the QCOW2 hard disk /dev/vda (as per attached screenshot)  +* Using a pre-existing Debian-11 guest that works perfectly with qemu-7.1, fails to format a basic ext3 /dev/loop filesystem when this guest is booted with qemu-7.2, giving `mke2fs: Input/output error while writing out and closing file system` +Steps to reproduce: +(installer error) +1. Create fresh QCOW2 image: `qemu-img create -f qcow2 deb11.img 8G` +2. Run standard Debian-11 installer from ISO image and virtio-blk-pci drive and options `-drive if=none,media=disk,id=drive0,file=deb11.img,cache=writeback,discard=unmap,detect-zeroes=unmap` +3. Use default options with "guided partitioning" +Additional information: +I'm not aware of any changes to the setup of my system that would account for these problems, and have successfully tried many similar experiments with QEMU version up to and including version 7.1. Obviously, I'm hoping there's some trivial configuration error I've overlooked in qemu-7.2 - any suggestions would be much appreciated. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1405 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1405 new file mode 100644 index 000000000..188dc33c1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1405 @@ -0,0 +1,121 @@ +linux-user: calling SYS_get_thread_area and SYS_get_thread_area has incorrent result on multithread environment +Description of problem: + +Steps to reproduce: +1. Compile test.out by Command and source code: +``` +gcc -m32 -g test.c -lpthread -o test.out +``` +``` +#include <sys/syscall.h> +#include <unistd.h> +#include <stdio.h> +#include <pthread.h> +#include <asm/ldt.h> + +static inline int set_thread_area( struct user_desc *ptr ) +{ + return syscall( SYS_set_thread_area, ptr ); +} + +static inline int get_thread_area( struct user_desc *ptr ) +{ + return syscall( SYS_get_thread_area, ptr ); +} + +static unsigned int entry_number; + +static void* start_routine(void* ptr) +{ + struct user_desc user_desc0 = { entry_number }; + struct user_desc user_desc1 = { entry_number }; + struct user_desc user_desc2 = { entry_number }; + get_thread_area(&user_desc0); + printf("child thread: %u\n", user_desc0.base_addr); + + user_desc1.base_addr = 2; + user_desc1.limit = 0xFFF; + user_desc1.seg_32bit = 1; + set_thread_area( &user_desc1 ); + + get_thread_area(&user_desc2); + printf("child thread: %u\n", user_desc2.base_addr); + return NULL; +} + +int main(void) { + struct user_desc user_desc0 = { -1 }, user_desc1 = { 0 }, user_desc2 = { 0 }; + user_desc0.seg_32bit = 1; + user_desc0.useable = 1; + set_thread_area( &user_desc0 ); + + entry_number = user_desc0.entry_number; + + user_desc1.entry_number = entry_number; + user_desc1.base_addr = 1; + user_desc1.limit = 0xFFF; + user_desc1.seg_32bit = 1; + set_thread_area( &user_desc1 ); + + pthread_t thread_id; + pthread_create(&thread_id, NULL, &start_routine, NULL); + pthread_join(thread_id, NULL); + + user_desc2.entry_number = entry_number; + get_thread_area(&user_desc2); + printf("main thread: %u\n", user_desc2.base_addr); // main thread: 1 + return 0; +} + ``` +2. Correct Result: +``` +child thread: 1 +child thread: 2 +main thread: 1 +``` +qemu-i386 Print Result: +``` +child thread: 1 +child thread: 2 +main thread: 2 +``` +Additional information: +patch for fix the bug: + +https://lists.nongnu.org/archive/html/qemu-devel/2023-02/msg02203.html + +CPUX86State::gdt::base on differect threads must have different vaules, but it points to same memory. +value of CPUX86State::gdt::base must be copied when clone thread. + +https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/x86/kernel/tls.c + +SYS_set_thread_area call do_set_thread_area in kernel, it set user_desc to different memroy area on differernt threads. tls_array is in thread local memory. + +``` +static void set_tls_desc(struct task_struct *p, int idx, + const struct user_desc *info, int n) +{ + struct thread_struct *t = &p->thread; + struct desc_struct *desc = &t->tls_array[idx - GDT_ENTRY_TLS_MIN]; + int cpu; + + /* + * We must not get preempted while modifying the TLS. + */ + cpu = get_cpu(); + + while (n-- > 0) { + if (LDT_empty(info) || LDT_zero(info)) + memset(desc, 0, sizeof(*desc)); + else + fill_ldt(desc, info); + ++info; + ++desc; + } + + if (t == ¤t->thread) + load_TLS(t, cpu); + + put_cpu(); +} +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1406 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1406 new file mode 100644 index 000000000..9db9f7b37 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1406 @@ -0,0 +1 @@ +WANTED: Schematics, Service, Tech Notes, .pdf IBM Power4 970MP/FX Apple PowerMac G5 Early/Late 2005 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1409 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1409 new file mode 100644 index 000000000..a4c15d627 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1409 @@ -0,0 +1 @@ +make check failed about qemu@7.2.0on suse15_aarch64 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1411 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1411 new file mode 100644 index 000000000..3cf45ac32 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1411 @@ -0,0 +1,455 @@ +QEMU 7.2.0 - Failed compilation under MacOS +Description of problem: +I downloaded and tried to build QEMU from git following the instructions from here: +https://www.qemu.org/download/ + +(I successfully installed QEMU with homebrew later, but I still want to figure out why my compilation failed.) +Steps to reproduce: +``` +git clone https://gitlab.com/qemu-project/qemu.git +cd qemu +git submodule init +git submodule update --recursive +./configure +make +``` +Additional information: +With `./configure` I got: + +``` +Using './build' as the directory for build output +Disabling PIE due to missing toolchain support +The Meson build system +Version: 0.61.5 +Source dir: /Users/xxx/qemu +Build dir: /Users/xxx/qemu/build +Build type: native build +Project name: qemu +Project version: 7.2.50 +C compiler for the host machine: cc (clang 14.0.0 "Apple clang version 14.0.0 (clang-1400.0.29.202)") +C linker for the host machine: cc ld64 820.1 +Host machine cpu family: aarch64 +Host machine cpu: arm64 +Program scripts/symlink-install-tree.py found: YES (/opt/homebrew/opt/python@3.10/bin/python3.10 /Users/xxx/qemu/scripts/symlink-install-tree.py) +Program sh found: YES (/bin/sh) +Program python3 found: YES (/opt/homebrew/opt/python@3.10/bin/python3.10) +Program bzip2 found: YES (/usr/bin/bzip2) +Program iasl found: NO +Compiler for C supports link arguments -Wl,-z,relro: NO +Compiler for C supports link arguments -Wl,-z,now: NO +C++ compiler for the host machine: c++ (clang 14.0.0 "Apple clang version 14.0.0 (clang-1400.0.29.202)") +C++ linker for the host machine: c++ ld64 820.1 +Compiler for C++ supports link arguments -Wl,--warn-common: NO +Objective-C compiler for the host machine: clang (clang 14.0.0) +Objective-C linker for the host machine: clang ld64 820.1 +Program cgcc found: NO +Library m found: YES +Run-time dependency threads found: YES +Library util found: YES +Run-time dependency appleframeworks found: YES (CoreFoundation) +Run-time dependency appleframeworks found: YES (IOKit) +Run-time dependency appleframeworks found: YES (Hypervisor) +Found pkg-config: /opt/homebrew/bin/pkg-config (0.29.2) +Run-time dependency gio-2.0 found: YES 2.74.4 +Program /opt/homebrew/Cellar/glib/2.74.4/bin/gdbus-codegen found: YES (/opt/homebrew/Cellar/glib/2.74.4/bin/gdbus-codegen) +Run-time dependency gio-unix-2.0 found: YES 2.74.4 +Run-time dependency pixman-1 found: YES 0.42.2 +Run-time dependency zlib found: YES 1.2.11 +Has header "libaio.h" : NO +Run-time dependency liburing found: NO (tried pkgconfig) +Run-time dependency libnfs found: NO (tried pkgconfig) +Has header "attr/xattr.h" : NO +Run-time dependency appleframeworks found: YES (Cocoa, CoreVideo) +Run-time dependency appleframeworks found: YES (vmnet) +Header <vmnet/vmnet.h> has symbol "VMNET_BRIDGED_MODE" with dependency appleframeworks: YES +Run-time dependency libseccomp found: NO (tried pkgconfig) +Has header "cap-ng.h" : NO +Run-time dependency xkbcommon found: NO (tried pkgconfig) +Run-time dependency slirp found: NO (tried pkgconfig) +Has header "libvdeplug.h" : NO +Run-time dependency jack found: NO (tried pkgconfig) +Run-time dependency sndio found: NO (tried pkgconfig) +Run-time dependency spice-protocol found: NO (tried pkgconfig) +Run-time dependency spice-server found: NO (tried pkgconfig) +Library rt found: NO +Run-time dependency libiscsi found: NO (tried pkgconfig) +Run-time dependency libzstd found: NO (tried pkgconfig) +Run-time dependency virglrenderer found: NO (tried pkgconfig) +Run-time dependency blkio found: NO (tried pkgconfig) +Run-time dependency libcurl found: YES 7.84.0 +Run-time dependency ncursesw found: YES 5.7.20081102 +Has header "brlapi.h" : NO +sdl2-config found: NO +Run-time dependency sdl2 found: NO (tried pkgconfig, config-tool and framework) +Library rados found: NO +Has header "rbd/librbd.h" : NO +Run-time dependency glusterfs-api found: NO (tried pkgconfig) +Run-time dependency libssh found: NO (tried pkgconfig) +Has header "bzlib.h" : YES +Library bz2 found: YES +Has header "lzfse.h" : NO +Has header "sys/soundcard.h" : NO +Run-time dependency appleframeworks found: YES (CoreAudio) +Run-time dependency epoxy found: NO (tried pkgconfig) +Has header "epoxy/egl.h" with dependency epoxy: NO +Run-time dependency gnutls found: NO (tried pkgconfig) +Run-time dependency gnutls found: NO (tried pkgconfig) +libgcrypt-config found: NO need ['>=1.8'] +Run-time dependency libgcrypt found: NO (tried config-tool) +Run-time dependency nettle found: NO (tried pkgconfig) +Run-time dependency gmp found: NO (tried pkgconfig) +Run-time dependency gtk+-3.0 found: NO (tried pkgconfig) +Run-time dependency libpng found: NO (tried pkgconfig) +Run-time dependency libjpeg found: NO (tried pkgconfig) +Has header "sasl/sasl.h" : YES +Library sasl2 found: YES +Has header "security/pam_appl.h" : YES +Library pam found: YES +Has header "snappy-c.h" : NO +Has header "lzo/lzo1x.h" : NO +Has header "numa.h" : NO +Library ibumad found: NO +Has header "rdma/rdma_cma.h" : NO +Library ibverbs found: NO +Run-time dependency xencontrol found: NO (tried pkgconfig) +Library xenstore found: NO +Library xenctrl found: NO +Library xendevicemodel found: NO +Library xenforeignmemory found: NO +Library xengnttab found: NO +Library xenevtchn found: NO +Library xentoolcore found: NO +Run-time dependency libcacard found: NO (tried pkgconfig) +Run-time dependency u2f-emu found: NO (tried pkgconfig) +Run-time dependency canokey-qemu found: NO (tried pkgconfig) +Run-time dependency libusbredirparser-0.5 found: NO (tried pkgconfig) +Run-time dependency libusb-1.0 found: NO (tried pkgconfig) +Run-time dependency libpmem found: NO (tried pkgconfig) +Run-time dependency libdaxctl found: NO (tried pkgconfig) +Run-time dependency libkeyutils found: NO (tried pkgconfig) +Checking for function "gettid" : NO +Run-time dependency libselinux found: NO (tried pkgconfig) +Run-time dependency fuse3 found: NO (tried pkgconfig) +Run-time dependency libbpf found: NO (tried pkgconfig) +Has header "IOKit/storage/IOMedia.h" : YES +Checking for function "pthread_fchdir_np" : YES +Has header "sys/epoll.h" : NO +Has header "linux/magic.h" : NO +Has header "valgrind/valgrind.h" : NO +Has header "linux/btrfs.h" : NO +Has header "libdrm/drm.h" : NO +Has header "pty.h" : NO +Has header "sys/disk.h" : YES +Has header "sys/ioccom.h" : YES +Has header "sys/kcov.h" : NO +Checking for function "close_range" : NO +Checking for function "accept4" : NO +Checking for function "clock_adjtime" : NO +Checking for function "dup3" : NO +Checking for function "fallocate" : NO +Checking for function "posix_fallocate" : NO +Checking for function "posix_memalign" : YES +Checking for function "_aligned_malloc" : NO +Checking for function "valloc" : YES +Checking for function "memalign" : NO +Checking for function "ppoll" : NO +Checking for function "preadv" : YES +Checking for function "pthread_fchdir_np" : YES (cached) +Checking for function "sendfile" : YES +Checking for function "setns" : NO +Checking for function "syncfs" : NO +Checking for function "sync_file_range" : NO +Checking for function "timerfd_create" : NO +Checking for function "copy_file_range" : NO +Checking for function "getifaddrs" : YES +Checking for function "openpty" with dependency -lutil: YES +Checking for function "strchrnul" : NO +Checking for function "system" : YES +Header <byteswap.h> has symbol "bswap_32" : NO +Header <sys/epoll.h> has symbol "epoll_create1" : NO +Header <linux/falloc.h> has symbol "FALLOC_FL_PUNCH_HOLE" : NO +Header <linux/falloc.h> has symbol "FALLOC_FL_ZERO_RANGE" : NO +Has header "linux/fiemap.h" : NO +Checking for function "getrandom" : NO +Header <sys/inotify.h> has symbol "inotify_init" : NO +Header <sys/inotify.h> has symbol "inotify_init1" : NO +Header <machine/bswap.h> has symbol "bswap32" : NO +Header <sys/prctl.h> has symbol "PR_SET_TIMERSLACK" : NO +Header <linux/rtnetlink.h> has symbol "IFLA_PROTO_DOWN" : NO +Header <sys/sysmacros.h> has symbol "makedev" : NO +Header <getopt.h> has symbol "optreset" : YES +Header <netinet/in.h> has symbol "IPPROTO_MPTCP" : NO +Header <sys/mount.h> has symbol "FSCONFIG_SET_FLAG" : NO +Checking whether type "struct sigevent" has member "sigev_notify_thread_id" : NO +Checking whether type "struct stat" has member "st_atim" : NO +Checking for type "struct iovec" : YES +Checking for type "struct utmpx" : YES +Checking for type "struct mmsghdr" : NO +Header <linux/vm_sockets.h> has symbol "AF_VSOCK" : NO +Program scripts/minikconf.py found: YES (/opt/homebrew/opt/python@3.10/bin/python3.10 /Users/xxx/qemu/scripts/minikconf.py) +Configuring x86_64-softmmu-config-target.h using configuration +Configuring x86_64-softmmu-config-devices.mak with command +Reading depfile: /Users/xxx/qemu/build/meson-private/x86_64-softmmu-config-devices.mak.d +Configuring x86_64-softmmu-config-devices.h using configuration +Program scripts/make-config-poison.sh found: YES (/Users/xxx/qemu/scripts/make-config-poison.sh) +Run-time dependency capstone found: NO (tried pkgconfig) +Library fdt found: NO +Configuring config-host.h using configuration +Program scripts/hxtool found: YES (/Users/xxx/qemu/scripts/hxtool) +Program scripts/shaderinclude.pl found: YES (/usr/bin/env perl /Users/xxx/qemu/scripts/shaderinclude.pl) +Program scripts/qapi-gen.py found: YES (/opt/homebrew/opt/python@3.10/bin/python3.10 /Users/xxx/qemu/scripts/qapi-gen.py) +Program scripts/qemu-version.sh found: YES (/Users/xxx/qemu/scripts/qemu-version.sh) +Program scripts/decodetree.py found: YES (/opt/homebrew/opt/python@3.10/bin/python3.10 /Users/xxx/qemu/scripts/decodetree.py) +Program ../scripts/modules/module_block.py found: YES (/opt/homebrew/opt/python@3.10/bin/python3.10 /Users/xxx/qemu/block/../scripts/modules/module_block.py) +Program ../scripts/block-coroutine-wrapper.py found: YES (/opt/homebrew/opt/python@3.10/bin/python3.10 /Users/xxx/qemu/block/../scripts/block-coroutine-wrapper.py) +Configuring qemu-plugins-ld64.symbols with command +Program scripts/modinfo-collect.py found: YES (/Users/xxx/qemu/scripts/modinfo-collect.py) +Program scripts/modinfo-generate.py found: YES (/Users/xxx/qemu/scripts/modinfo-generate.py) +Program nm found: YES +Program scripts/undefsym.py found: YES (/opt/homebrew/opt/python@3.10/bin/python3.10 /Users/xxx/qemu/scripts/undefsym.py) +Program scripts/feature_to_c.sh found: YES (/bin/sh /Users/xxx/qemu/scripts/feature_to_c.sh) +Program scripts/entitlement.sh found: YES (/Users/xxx/qemu/scripts/entitlement.sh) +Configuring 50-edk2-i386-secure.json using configuration +Configuring 50-edk2-x86_64-secure.json using configuration +Configuring 60-edk2-aarch64.json using configuration +Configuring 60-edk2-arm.json using configuration +Configuring 60-edk2-i386.json using configuration +Configuring 60-edk2-x86_64.json using configuration +Program qemu-keymap found: NO +Program sphinx-build-3 sphinx-build found: NO +Program bash found: NO found 3.2.57 but need: '>= 4.0' (/bin/bash) +Message: bash >= v4.0 not available ==> Disabled the qemu-iotests. +Program diff found: YES (/usr/bin/diff) +Program dbus-daemon found: NO +Did not find CMake 'cmake' +Found CMake: NO +Run-time dependency gvnc-1.0 found: NO (tried pkgconfig, framework and cmake) +Program initrd-stress.sh found: YES (/Users/xxx/qemu/tests/migration/initrd-stress.sh) +Build targets in project: 499 + +qemu 7.2.50 + + Directories + Install prefix : /usr/local + BIOS directory : share/qemu + firmware path : share/qemu-firmware + binary directory : /usr/local/bin + library directory : /usr/local/lib + module directory : lib/qemu + libexec directory : /usr/local/libexec + include directory : /usr/local/include + config directory : /usr/local/etc + local state directory : /var/local + Manual directory : /usr/local/share/man + Doc directory : /usr/local/share/doc + Build directory : /Users/xxx/qemu/build + Source path : /Users/xxx/qemu + GIT submodules : ui/keycodemapdb meson tests/fp/berkeley-testfloat-3 tests/fp/berkeley-softfloat-3 dtc + + Host binaries + git : git + make : make + python : /opt/homebrew/opt/python@3.10/bin/python3.10 (version: 3.10) + sphinx-build : NO + iasl : NO + genisoimage : + + Configurable features + Documentation : NO + system-mode emulation : YES + user-mode emulation : NO + block layer : YES + Install blobs : YES + module support : NO + fuzzing support : NO + Audio drivers : coreaudio + Trace backends : log + D-Bus display : NO + QOM debugging : NO + vhost-kernel support : NO + vhost-net support : NO + vhost-user support : NO + vhost-user-crypto support : NO + vhost-user-blk server support: NO + vhost-vdpa support : NO + build guest agent : NO + + Compilation + host CPU : aarch64 + host endianness : little + C compiler : cc + Host C compiler : cc + C++ compiler : c++ + Objective-C compiler : clang + CFLAGS : -O2 -g + CXXFLAGS : -O2 -g + OBJCFLAGS : -O2 -g + QEMU_CFLAGS : -DOS_OBJECT_USE_OBJC=0 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fno-common -fwrapv -Wold-style-definition -Wtype-limits -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body -Wnested-externs -Wendif-labels -Wexpansion-to-defined -Wno-initializer-overrides -Wno-missing-include-dirs -Wno-shift-negative-value -Wno-string-plus-int -Wno-typedef-redefinition -Wno-tautological-type-limit-compare -Wno-psabi -Wno-gnu-variable-sized-type-not-at-end -fstack-protector-strong + QEMU_CXXFLAGS : -DOS_OBJECT_USE_OBJC=0 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wundef -Wwrite-strings -fno-strict-aliasing -fno-common -fwrapv -Wtype-limits -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body -Wendif-labels -Wexpansion-to-defined -Wno-initializer-overrides -Wno-missing-include-dirs -Wno-shift-negative-value -Wno-string-plus-int -Wno-typedef-redefinition -Wno-tautological-type-limit-compare -Wno-psabi -Wno-gnu-variable-sized-type-not-at-end -fstack-protector-strong + QEMU_OBJCFLAGS : -Wold-style-definition -Wtype-limits -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body -Wnested-externs -Wendif-labels -Wexpansion-to-defined -Wno-initializer-overrides -Wno-missing-include-dirs -Wno-shift-negative-value -Wno-string-plus-int -Wno-typedef-redefinition -Wno-tautological-type-limit-compare -Wno-psabi -Wno-gnu-variable-sized-type-not-at-end + QEMU_LDFLAGS : -fstack-protector-strong + profiler : NO + link-time optimization (LTO) : NO + PIE : NO + static build : NO + malloc trim support : NO + membarrier : NO + debug stack usage : NO + mutex debugging : NO + memory allocator : system + avx2 optimization : NO + avx512f optimization : NO + gprof enabled : NO + gcov : NO + thread sanitizer : NO + CFI support : NO + strip binaries : NO + sparse : NO + mingw32 support : NO + + Targets and accelerators + KVM support : NO + HAX support : NO + HVF support : NO + WHPX support : NO + NVMM support : NO + Xen support : NO + TCG support : YES + TCG backend : native (aarch64) + TCG plugins : YES + TCG debug enabled : NO + target list : x86_64-softmmu + default devices : YES + out of process emulation : NO + vfio-user server : NO + + Block layer support + coroutine backend : sigaltstack + coroutine pool : YES + Block whitelist (rw) : + Block whitelist (ro) : + Use block whitelist in tools : NO + VirtFS support : YES + build virtiofs daemon : NO + Live block migration : YES + replication support : YES + bochs support : YES + cloop support : YES + dmg support : YES + qcow v1 support : YES + vdi support : YES + vvfat support : YES + qed support : YES + parallels support : YES + FUSE exports : NO + VDUSE block exports : NO + + Crypto + TLS priority : NORMAL + GNUTLS support : NO + libgcrypt : NO + nettle : NO + AF_ALG support : NO + rng-none : NO + Linux keyring : NO + + Dependencies + Cocoa support : YES + vmnet.framework support : YES + SDL support : NO + SDL image support : NO + GTK support : NO + pixman : YES 0.42.2 + VTE support : NO + slirp support : NO + libtasn1 : NO + PAM : YES + iconv support : YES + curses support : YES + virgl support : NO + blkio support : NO + curl support : YES 7.84.0 + Multipath support : NO + PNG support : NO + VNC support : YES + VNC SASL support : YES + VNC JPEG support : NO + CoreAudio support : YES + JACK support : NO + brlapi support : NO + vde support : NO + netmap support : NO + l2tpv3 support : NO + Linux AIO support : NO + Linux io_uring support : NO + ATTR/XATTR support : NO + RDMA support : NO + PVRDMA support : NO + fdt support : internal + libcap-ng support : NO + bpf support : NO + spice protocol support : NO + rbd support : NO + smartcard support : NO + U2F support : NO + libusb : NO + usb net redir : NO + OpenGL support (epoxy) : NO + GBM : NO + libiscsi support : NO + libnfs support : NO + seccomp support : NO + GlusterFS support : NO + TPM support : YES + libssh support : NO + lzo support : NO + snappy support : NO + bzip2 support : YES + lzfse support : NO + zstd support : NO + NUMA host support : NO + capstone : NO + libpmem support : NO + libdaxctl support : NO + libudev : NO + FUSE lseek : NO + selinux : NO + + User defined options + Native files : config-meson.cross + prefix : /usr/local + b_pie : false + vfio_user_server : disabled + +Found ninja-1.11.1 at /opt/homebrew/bin/ninja +Running postconf script '/opt/homebrew/opt/python@3.10/bin/python3.10 /Users/xxx/qemu/scripts/symlink-install-tree.py' +``` + + +With `make` I got: + +``` +changing dir to build for /Library/Developer/CommandLineTools/usr/bin/make ""... + GIT ui/keycodemapdb meson tests/fp/berkeley-testfloat-3 tests/fp/berkeley-softfloat-3 dtc +[1/75] Generating qemu-version.h with a custom command (wrapped by meson to capture output) +changing dir to build for /Library/Developer/CommandLineTools/usr/bin/make ""... + GIT ui/keycodemapdb meson tests/fp/berkeley-testfloat-3 tests/fp/berkeley-softfloat-3 dtc +[1/75] Generating qemu-version.h with a custom command (wrapped by meson to capture output) +changing dir to build for /Library/Developer/CommandLineTools/usr/bin/make ""... +/opt/homebrew/bin/ninja build.ninja && touch build.ninja.stamp +ninja: no work to do. +/opt/homebrew/bin/python3 -B /Users/xxx/qemu/meson/meson.py introspect --targets --tests --benchmarks | /opt/homebrew/bin/python3 -B scripts/mtest2make.py > Makefile.mtest + GIT ui/keycodemapdb meson tests/fp/berkeley-testfloat-3 tests/fp/berkeley-softfloat-3 dtc + GIT ui/keycodemapdb meson tests/fp/berkeley-testfloat-3 tests/fp/berkeley-softfloat-3 dtc +[1/2455] Generating config-poison.h with a custom command (wrapped by meson to capture output) +[2/2455] Compiling C object libfdt.a.p/dtc_libfdt_fdt.c.o +[3/2455] Compiling C object libfdt.a.p/dtc_libfdt_fdt_ro.c.o +[4/2455] Compiling C object libfdt.a.p/dtc_libfdt_fdt_wip.c.o +[5/2455] Compiling C object libfdt.a.p/dtc_libfdt_fdt_sw.c.o +... (no error) +[2455/2455] Linking target tests/qtest/readconfig-test +changing dir to build for /Library/Developer/CommandLineTools/usr/bin/make ""... + GIT ui/keycodemapdb meson tests/fp/berkeley-testfloat-3 tests/fp/berkeley-softfloat-3 dtc +[1/48] Generating qemu-version.h with a custom command (wrapped by meson to capture output) +[2/34] Generating tests/include/QAPI test (include) with a custom command +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1413 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1413 new file mode 100644 index 000000000..a2f985fdd --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1413 @@ -0,0 +1,22 @@ +I tried to use qemu-nbd in the shell script, but it seems that qemu-nbd has some delay. +Description of problem: + +Steps to reproduce: +1. +``` +cat ~/test.sh +#!/bin/bash +qemu-nbd -c /dev/nbd0 $1 +mount -t ntfs3 -o uid=1000,gid=1000 /dev/disk/by-label/OS /mnt/OS +``` +2. +``` +sudo ~/test.sh ~/VM/win7_i386.qcow2 +mount: /mnt/OS: special device /dev/disk/by-label/OS does not exist. + dmesg(1) may have more information after failed mount system call. + +``` +Additional information: +But when I added a one-second delay between qemu-nbd and mount commands, the problem was solved. + +The qemu-img convert command also has a similar problem. It seems that these commands have a certain delay. Is this in line with expectations? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1414 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1414 new file mode 100644 index 000000000..67c49498f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1414 @@ -0,0 +1,20 @@ +Configure script fix for glib version +Description of problem: +Script "configure" uses "pkg-config" directly, at line 2420: https://gitlab.com/qemu-project/qemu/-/blob/f9f0e6173e1d570847930abfe2b4560c7b6a964a/configure#L2420 + +Because of it, GLIB_VERSION in "config-host.mak" can be taken from host system, under some circumstances (if PKG_CONFIG_PATH is not defined). + +In case of cross-compilation, "**$pkg_config**" should be used instead of "pkg-config", to use pkg-config from cross-compilation toolchain and to take GLIB_VERSION of cross-compiled glib (as it is **correctly used at line 1476**: https://gitlab.com/qemu-project/qemu/-/blob/f9f0e6173e1d570847930abfe2b4560c7b6a964a/configure#L1476 ). +Steps to reproduce: +1. Do not define PKG_CONFIG_PATH environment variable, use PKG_CONFIG variable instead. +2. Try to ./configure with cross-compiled glib. +3. GLIB_VERSION in config-host.mak will be from host glib. +Additional information: +Change lihe 2420:<br> +https://gitlab.com/qemu-project/qemu/-/blob/f9f0e6173e1d570847930abfe2b4560c7b6a964a/configure#L2420 +<br> +echo "GLIB_VERSION=$(**pkg-config** --modversion glib-2.0)" >> $config_host_mak +<br>to:<br> +echo "GLIB_VERSION=$(**\$pkg_config** --modversion glib-2.0)" >> $config_host_mak + +P.s. Sorry for posting the patch here, GitLab requires signing with a key to push the commit, it's too complicated to post 2-bytes fix. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1418 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1418 new file mode 100644 index 000000000..16faa1d86 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1418 @@ -0,0 +1,87 @@ +Underflow in xlnx_dp_aux_pop_tx_fifo() +Description of problem: +Pop from s->tx_fifo but s->tx_fifo has zero element. +Steps to reproduce: +``` +export QEMU=/path/to/qemu-system-aarch64 + +cat << EOF | $QEMU \ +-machine xlnx-zcu102 -monitor none -serial none \ +-display none -nodefaults -qtest stdio +writel 0xfd4a0100 0x19c4406f +EOF +``` +Additional information: +``` ++ DEFAULT_INPUT_MAXSIZE=10000000 ++ ./qemu-videzzo-aarch64-target-videzzo-fuzz-xlnx-dp -max_len=10000000 -detect_leaks=0 ./crash-c15714102f0b894dea5c22f38852311567380926.minimized +==14660==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases! +INFO: found LLVMFuzzerCustomMutator (0x55db5cf9b840). Disabling -len_control by default. +INFO: Running with entropic power schedule (0xFF, 100). +INFO: Seed: 1977030529 +INFO: Loaded 1 modules (618603 inline 8-bit counters): 618603 [0x55db600fa000, 0x55db6019106b), +INFO: Loaded 1 PC tables (618603 PCs): 618603 [0x55db5f788d60,0x55db600f9410), +./qemu-videzzo-aarch64-target-videzzo-fuzz-xlnx-dp: Running 1 inputs 1 time(s) each. +INFO: Reading pre_seed_input if any ... +INFO: Executing pre_seed_input if any ... +Matching objects by name , *.core*, *.v_blend*, *.av_buffer_manager*, *.audio* +This process will fuzz the following MemoryRegions: + * xlnx.v-dp.core[0] (size 3b0) + * xlnx.v-dp.v_blend[0] (size 1e0) + * xlnx.v-dp.audio[0] (size 50) + * xlnx.v-dp.av_buffer_manager[0] (size 238) +This process will fuzz through the following interfaces: + * clock_step, EVENT_TYPE_CLOCK_STEP, 0xffffffff +0xffffffff, 255,255 + * xlnx.v-dp.core, EVENT_TYPE_MMIO_READ, 0xfd4a0000 +0x3b0, 4,4 + * xlnx.v-dp.core, EVENT_TYPE_MMIO_WRITE, 0xfd4a0000 +0x3b0, 4,4 + * xlnx.v-dp.v_blend, EVENT_TYPE_MMIO_READ, 0xfd4aa000 +0x1e0, 4,4 + * xlnx.v-dp.v_blend, EVENT_TYPE_MMIO_WRITE, 0xfd4aa000 +0x1e0, 4,4 + * xlnx.v-dp.av_buffer_manager, EVENT_TYPE_MMIO_READ, 0xfd4ab000 +0x238, 4,4 + * xlnx.v-dp.av_buffer_manager, EVENT_TYPE_MMIO_WRITE, 0xfd4ab000 +0x238, 4,4 + * xlnx.v-dp.audio, EVENT_TYPE_MMIO_READ, 0xfd4ac000 +0x50, 1,4 + * xlnx.v-dp.audio, EVENT_TYPE_MMIO_WRITE, 0xfd4ac000 +0x50, 1,4 +INFO: A corpus is not provided, starting from an empty corpus +#2 INITED cov: 3 ft: 4 corp: 1/1b exec/s: 0 rss: 488Mb +Running: ./crash-c15714102f0b894dea5c22f38852311567380926.minimized +aarch64: xlnx_dp_aux_pop_tx_fifo: TX_FIFO underflow +==14660== ERROR: libFuzzer: deadly signal + #0 0x55db5837410e in __sanitizer_print_stack_trace /root/llvm-project/compiler-rt/lib/asan/asan_stack.cpp:86:3 + #1 0x55db582c2d81 in fuzzer::PrintStackTrace() /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerUtil.cpp:210:38 + #2 0x55db5829bcb6 in fuzzer::Fuzzer::CrashCallback() (.part.0) /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:236:18 + #3 0x55db5829bd82 in fuzzer::Fuzzer::CrashCallback() /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:208:1 + #4 0x55db5829bd82 in fuzzer::Fuzzer::StaticCrashSignalCallback() /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:207:19 + #5 0x7f98a612541f (/lib/x86_64-linux-gnu/libpthread.so.0+0x1441f) + #6 0x7f98a5f3700a in __libc_signal_restore_set /build/glibc-SzIz7B/glibc-2.31/signal/../sysdeps/unix/sysv/linux/internal-signals.h:86:3 + #7 0x7f98a5f3700a in raise /build/glibc-SzIz7B/glibc-2.31/signal/../sysdeps/unix/sysv/linux/raise.c:48:3 + #8 0x7f98a5f16858 in abort /build/glibc-SzIz7B/glibc-2.31/stdlib/abort.c:79:7 + #9 0x55db583a465a in __wrap_abort /root/videzzo/videzzo_qemu/qemu/build-san-6/../tests/qtest/videzzo/less_crashes_wrappers.c:24:12 + #10 0x55db58cce4d8 in xlnx_dp_aux_pop_tx_fifo /root/videzzo/videzzo_qemu/qemu/build-san-6/../hw/display/xlnx_dp.c:476:9 + #11 0x55db58cc9ee7 in xlnx_dp_aux_set_command /root/videzzo/videzzo_qemu/qemu/build-san-6/../hw/display/xlnx_dp.c:524:22 + #12 0x55db58cc6a92 in xlnx_dp_write /root/videzzo/videzzo_qemu/qemu/build-san-6/../hw/display/xlnx_dp.c:800:9 + #13 0x55db5bf4eec3 in memory_region_write_accessor /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/memory.c:492:5 + #14 0x55db5bf4e801 in access_with_adjusted_size /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/memory.c:554:18 + #15 0x55db5bf4d126 in memory_region_dispatch_write /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/memory.c:1514:16 + #16 0x55db5bfdb2de in flatview_write_continue /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/physmem.c:2825:23 + #17 0x55db5bfc941b in flatview_write /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/physmem.c:2867:12 + #18 0x55db5bfc8ed8 in address_space_write /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/physmem.c:2963:18 + #19 0x55db583b40cb in qemu_writel /root/videzzo/videzzo_qemu/qemu/build-san-6/../tests/qtest/videzzo/videzzo_qemu.c:1088:5 + #20 0x55db583b2544 in dispatch_mmio_write /root/videzzo/videzzo_qemu/qemu/build-san-6/../tests/qtest/videzzo/videzzo_qemu.c:1229:28 + #21 0x55db5cf971ff in videzzo_dispatch_event /root/videzzo/videzzo.c:1122:5 + #22 0x55db5cf8e57b in __videzzo_execute_one_input /root/videzzo/videzzo.c:272:9 + #23 0x55db5cf8e450 in videzzo_execute_one_input /root/videzzo/videzzo.c:313:9 + #24 0x55db583bb10c in videzzo_qemu /root/videzzo/videzzo_qemu/qemu/build-san-6/../tests/qtest/videzzo/videzzo_qemu.c:1504:12 + #25 0x55db5cf9bae2 in LLVMFuzzerTestOneInput /root/videzzo/videzzo.c:1891:18 + #26 0x55db5829c826 in fuzzer::Fuzzer::ExecuteCallback(unsigned char*, unsigned long) /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:594:17 + #27 0x55db5827f454 in fuzzer::RunOneTest(fuzzer::Fuzzer*, char const*, unsigned long) /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:323:21 + #28 0x55db5828a3fe in fuzzer::FuzzerDriver(int*, char***, int (*)(unsigned char*, unsigned long)) /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:885:19 + #29 0x55db582769e6 in main /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerMain.cpp:20:30 + #30 0x7f98a5f18082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16 + #31 0x55db58276a3d in _start (/root/bugs/metadata/xlnx_dp-06/qemu-videzzo-aarch64-target-videzzo-fuzz-xlnx-dp+0x3291a3d) + +NOTE: libFuzzer has rudimentary signal handlers. + Combine libFuzzer with AddressSanitizer or similar for better crash reports. +SUMMARY: libFuzzer: deadly signal +MS: 0 ; base unit: 0000000000000000000000000000000000000000 +0x1,0x9,0x0,0x1,0x4a,0xfd,0x0,0x0,0x0,0x0,0x4,0x0,0x0,0x0,0x6f,0x40,0xc4,0x19,0x0,0x0,0x0,0x0, +\x01\x09\x00\x01J\xfd\x00\x00\x00\x00\x04\x00\x00\x00o@\xc4\x19\x00\x00\x00\x00 +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1419 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1419 new file mode 100644 index 000000000..52b8ea548 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1419 @@ -0,0 +1,92 @@ +Overflow in xlnx_dp_aux_push_rx_fifo() +Description of problem: +Pushing stuff into s->rx_fifo many times make s->rx_fifo overflow. +Steps to reproduce: +``` +export QEMU=/path/to/qemu-system-aarch64 + +cat << EOF | $QEMU \ +-machine xlnx-zcu102 -monitor none -serial none \ +-display none -nodefaults -qtest stdio +writel 0xfd4a0100 0x7fb141e6 +writel 0xfd4a0100 0x7fb141e6 +writel 0xfd4a0100 0x7fb141e6 +EOF +``` +Additional information: +``` +root@3728b1f90dbd:~/bugs/metadata/xlnx_dp-03# bash -x xlnx_dp-03.videzzo ++ DEFAULT_INPUT_MAXSIZE=10000000 ++ ./qemu-videzzo-aarch64-target-videzzo-fuzz-xlnx-dp -max_len=10000000 -detect_leaks=0 poc-qemu-videzzo-aarch64-target-videzzo-fuzz-xlnx-dp-crash-a6a2bd23ff0408dd50652670fdcdf9f5ceaab95d.minimized +==767==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases! +INFO: found LLVMFuzzerCustomMutator (0x55d36d8b3870). Disabling -len_control by default. +INFO: Running with entropic power schedule (0xFF, 100). +INFO: Seed: 1781001818 +INFO: Loaded 1 modules (618604 inline 8-bit counters): 618604 [0x55d370a12000, 0x55d370aa906c), +INFO: Loaded 1 PC tables (618604 PCs): 618604 [0x55d3700a0ce0,0x55d370a113a0), +./qemu-videzzo-aarch64-target-videzzo-fuzz-xlnx-dp: Running 1 inputs 1 time(s) each. +INFO: Reading pre_seed_input if any ... +INFO: Executing pre_seed_input if any ... +Matching objects by name , *.core*, *.v_blend*, *.av_buffer_manager*, *.audio* +This process will fuzz the following MemoryRegions: + * xlnx.v-dp.core[0] (size 3b0) + * xlnx.v-dp.v_blend[0] (size 1e0) + * xlnx.v-dp.audio[0] (size 50) + * xlnx.v-dp.av_buffer_manager[0] (size 238) +This process will fuzz through the following interfaces: + * clock_step, EVENT_TYPE_CLOCK_STEP, 0xffffffff +0xffffffff, 255,255 + * xlnx.v-dp.core, EVENT_TYPE_MMIO_READ, 0xfd4a0000 +0x3b0, 4,4 + * xlnx.v-dp.core, EVENT_TYPE_MMIO_WRITE, 0xfd4a0000 +0x3b0, 4,4 + * xlnx.v-dp.v_blend, EVENT_TYPE_MMIO_READ, 0xfd4aa000 +0x1e0, 4,4 + * xlnx.v-dp.v_blend, EVENT_TYPE_MMIO_WRITE, 0xfd4aa000 +0x1e0, 4,4 + * xlnx.v-dp.av_buffer_manager, EVENT_TYPE_MMIO_READ, 0xfd4ab000 +0x238, 4,4 + * xlnx.v-dp.av_buffer_manager, EVENT_TYPE_MMIO_WRITE, 0xfd4ab000 +0x238, 4,4 + * xlnx.v-dp.audio, EVENT_TYPE_MMIO_READ, 0xfd4ac000 +0x50, 1,4 + * xlnx.v-dp.audio, EVENT_TYPE_MMIO_WRITE, 0xfd4ac000 +0x50, 1,4 +INFO: A corpus is not provided, starting from an empty corpus +#2 INITED cov: 3 ft: 4 corp: 1/1b exec/s: 0 rss: 492Mb +Running: poc-qemu-videzzo-aarch64-target-videzzo-fuzz-xlnx-dp-crash-a6a2bd23ff0408dd50652670fdcdf9f5ceaab95d.minimized +qemu-videzzo-aarch64-target-videzzo-fuzz-xlnx-dp: ../util/fifo8.c:43: void fifo8_push_all(Fifo8 *, const uint8_t *, uint32_t): Assertion `fifo->num + num <= fifo->capacity' failed. +==767== ERROR: libFuzzer: deadly signal + #0 0x55d368c8c10e in __sanitizer_print_stack_trace /root/llvm-project/compiler-rt/lib/asan/asan_stack.cpp:86:3 + #1 0x55d368bdad81 in fuzzer::PrintStackTrace() /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerUtil.cpp:210:38 + #2 0x55d368bb3cb6 in fuzzer::Fuzzer::CrashCallback() (.part.0) /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:236:18 + #3 0x55d368bb3d82 in fuzzer::Fuzzer::CrashCallback() /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:208:1 + #4 0x55d368bb3d82 in fuzzer::Fuzzer::StaticCrashSignalCallback() /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:207:19 + #5 0x7f9897d8741f (/lib/x86_64-linux-gnu/libpthread.so.0+0x1441f) + #6 0x7f9897b9900a in __libc_signal_restore_set /build/glibc-SzIz7B/glibc-2.31/signal/../sysdeps/unix/sysv/linux/internal-signals.h:86:3 + #7 0x7f9897b9900a in raise /build/glibc-SzIz7B/glibc-2.31/signal/../sysdeps/unix/sysv/linux/raise.c:48:3 + #8 0x7f9897b78858 in abort /build/glibc-SzIz7B/glibc-2.31/stdlib/abort.c:79:7 + #9 0x7f9897b78728 in __assert_fail_base /build/glibc-SzIz7B/glibc-2.31/assert/assert.c:92:3 + #10 0x7f9897b89fd5 in __assert_fail /build/glibc-SzIz7B/glibc-2.31/assert/assert.c:101:3 + #11 0x55d36d56bff3 in fifo8_push_all /root/videzzo/videzzo_qemu/qemu/build-san-6/../util/fifo8.c:43:5 + #12 0x55d3695e64d3 in xlnx_dp_aux_push_rx_fifo /root/videzzo/videzzo_qemu/qemu/build-san-6/../hw/display/xlnx_dp.c:436:5 + #13 0x55d3695e1e9a in xlnx_dp_aux_set_command /root/videzzo/videzzo_qemu/qemu/build-san-6/../hw/display/xlnx_dp.c:513:13 + #14 0x55d3695dea92 in xlnx_dp_write /root/videzzo/videzzo_qemu/qemu/build-san-6/../hw/display/xlnx_dp.c:805:9 + #15 0x55d36c866ef3 in memory_region_write_accessor /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/memory.c:492:5 + #16 0x55d36c866831 in access_with_adjusted_size /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/memory.c:554:18 + #17 0x55d36c865156 in memory_region_dispatch_write /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/memory.c:1514:16 + #18 0x55d36c8f330e in flatview_write_continue /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/physmem.c:2825:23 + #19 0x55d36c8e144b in flatview_write /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/physmem.c:2867:12 + #20 0x55d36c8e0f08 in address_space_write /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/physmem.c:2963:18 + #21 0x55d368ccc0cb in qemu_writel /root/videzzo/videzzo_qemu/qemu/build-san-6/../tests/qtest/videzzo/videzzo_qemu.c:1088:5 + #22 0x55d368cca544 in dispatch_mmio_write /root/videzzo/videzzo_qemu/qemu/build-san-6/../tests/qtest/videzzo/videzzo_qemu.c:1229:28 + #23 0x55d36d8af22f in videzzo_dispatch_event /root/videzzo/videzzo.c:1122:5 + #24 0x55d36d8a65ab in __videzzo_execute_one_input /root/videzzo/videzzo.c:272:9 + #25 0x55d36d8a6480 in videzzo_execute_one_input /root/videzzo/videzzo.c:313:9 + #26 0x55d368cd310c in videzzo_qemu /root/videzzo/videzzo_qemu/qemu/build-san-6/../tests/qtest/videzzo/videzzo_qemu.c:1504:12 + #27 0x55d36d8b3b12 in LLVMFuzzerTestOneInput /root/videzzo/videzzo.c:1891:18 + #28 0x55d368bb4826 in fuzzer::Fuzzer::ExecuteCallback(unsigned char*, unsigned long) /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:594:17 + #29 0x55d368b97454 in fuzzer::RunOneTest(fuzzer::Fuzzer*, char const*, unsigned long) /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:323:21 + #30 0x55d368ba23fe in fuzzer::FuzzerDriver(int*, char***, int (*)(unsigned char*, unsigned long)) /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:885:19 + #31 0x55d368b8e9e6 in main /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerMain.cpp:20:30 + #32 0x7f9897b7a082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16 + #33 0x55d368b8ea3d in _start (/root/bugs/metadata/xlnx_dp-03/qemu-videzzo-aarch64-target-videzzo-fuzz-xlnx-dp+0x3291a3d) + +NOTE: libFuzzer has rudimentary signal handlers. + Combine libFuzzer with AddressSanitizer or similar for better crash reports. +SUMMARY: libFuzzer: deadly signal +MS: 0 ; base unit: 0000000000000000000000000000000000000000 +0x1,0x9,0x0,0x1,0x4a,0xfd,0x0,0x0,0x0,0x0,0x4,0x0,0x0,0x0,0xe6,0x41,0xb1,0x7f,0x0,0x0,0x0,0x0,0x1,0x9,0x0,0x1,0x4a,0xfd,0x0,0x0,0x0,0x0,0x4,0x0,0x0,0x0,0xe6,0x41,0xb1,0x7f,0x0,0x0,0x0,0x0,0x1,0x9,0x0,0x1,0x4a,0xfd,0x0,0x0,0x0,0x0,0x4,0x0,0x0,0x0,0xe6,0x41,0xb1,0x7f,0x0,0x0,0x0,0x0, +\x01\x09\x00\x01J\xfd\x00\x00\x00\x00\x04\x00\x00\x00\xe6A\xb1\x7f\x00\x00\x00\x00\x01\x09\x00\x01J\xfd\x00\x00\x00\x00\x04\x00\x00\x00\xe6A\xb1\x7f\x00\x00\x00\x00\x01\x09\x00\x01J\xfd\x00\x00\x00\x00\x04\x00\x00\x00\xe6A\xb1\x7f\x00\x00\x00\x00 +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/142 b/gitlab/issues_text/target_missing/host_missing/accel_missing/142 new file mode 100644 index 000000000..a348f4bee --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/142 @@ -0,0 +1 @@ +qemu -readconfig/-writeconfig cannot handle quotes in values diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1420 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1420 new file mode 100644 index 000000000..0ae97e282 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1420 @@ -0,0 +1,39 @@ +Missing path for pkg-config on amd64 debian based distros +Description of problem: +This error occurs when attempting to configure qemu from git : +```error +ERROR: glib-2.56 gthread-2.0 is required to compile QEMU +``` + +Although it seems to be as simple as "_just install the dev lib!!!_" it is not that simple. + +1. First of all, my system already has the library installed : + ```sh + dpkg -l | grep libglib2.0-dev + ii libglib2.0-dev:amd64 2.74.4-1 amd64 Development files for the GLib library + ii libglib2.0-dev-bin 2.74.4-1 amd64 Development utilities for the GLib library + ``` +1. Second, the file required by _pkg-config_ does exist aswell : + ```sh + ls /usr/lib/x86_64-linux-gnu/pkgconfig/gthread-2.0.pc -l + -rw-r--r-- 1 root root 240 dez 27 20:42 /usr/lib/x86_64-linux-gnu/pkgconfig/gthread-2.0.pc + ``` +1. Finally, the real problem is that pkg-config is not able to identify it **unless** you specify the _x86-64_ dir : + - Default usage. It fails. + ```sh + pkg-config --modversion gthread-2.0 + Package gthread-2.0 was not found in the pkg-config search path. + Perhaps you should add the directory containing `gthread-2.0.pc' + to the PKG_CONFIG_PATH environment variable + Package 'gthread-2.0', required by 'virtual:world', not found + ``` + - Fixed usage (temp) + ```sh + env PKG_CONFIG_PATH="$PKG_CONFIG_PATH:/usr/lib/x86_64-linux-gnu/pkgconfig/" pkg-config --modversion gthread-2.0 + 2.74.4 + ``` +Steps to reproduce: +1. clone qemu (master) +2. try to run _configure_ +Additional information: +Of course it seems to be a problem related to the program _pkg-config_ itself, or even by the distro's package, but it totally prevents any build of qemu in a debian-based distro, with architecture _amd64_. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1423 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1423 new file mode 100644 index 000000000..495d48ce2 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1423 @@ -0,0 +1,13 @@ +QEMU 6.2.0 fullscreen problem +Description of problem: +After running the command above, clicking on "Try Ubuntu" and adjusting the guest display resolution in GNOME to the native resolution, pressing ctrl+alt+f yields a "fullscreen" that only covers the QEMU window but not the entire host screen. This is not the case when switching to fullscreen while the boot screen is active or running `qemu-system-x86_64 -display gtk,full-screen=on`. + +The problem also occurs when replacing `-device qxl-vga` by `-device VGA,vgamem_mb=64`. The problem however does not occur when using `-device virtio-vga` instead of `-device qxl-vga` or `-display sdl` instead of `-display gtk`. +Steps to reproduce: +1. Run the command above +2. Click "Try Ubuntu" +3. Set guest resolution to native resolution (1920x1200 in my case) +4. Move the window a bit off the corners to observe the effect +5. Press ctrl+alt+f +Additional information: +The bug has also been [reported here](https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2000739). diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1426 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1426 new file mode 100644 index 000000000..72b5cdd9b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1426 @@ -0,0 +1,38 @@ +On windows, display spice-app is not able to initialize, start spice-server and consequently can't use spice-client +Description of problem: +I want to try windows spice-client / virt-viewer.exe (v11.0.256) instead of gtk client. +Windows spice client virtviewer won't start like it does under Linux. +The error message indicaes that the spice-server itself failed to open spice sockets +The registry to handle ```spice://``` URI handler is configured. +Steps to reproduce: +1. just run command +Additional information: +URI handler in registry is configure using a regestry import file ```spiceproto.reg``` +``` +Windows Registry Editor Version 5.00 + +[HKEY_CLASSES_ROOT\spice] +"URL Protocol"="" + +[HKEY_CLASSES_ROOT\spice\DefaultIcon] +@="C:\\Program Files\\VirtViewer v11.0-256\\bin\\remote-viewer.exe,1" + +[HKEY_CLASSES_ROOT\spice\Extensions] +[HKEY_CLASSES_ROOT\spice\shell] +[HKEY_CLASSES_ROOT\spice\shell\open] +[HKEY_CLASSES_ROOT\spice\shell\open\command] +@="\"C:\\Program Files\\VirtViewer v11.0-256\\bin\\remote-viewer.exe\" \"%1\"" + +[HKEY_CLASSES_ROOT\spice+unix] +"URL Protocol"="" + +[HKEY_CLASSES_ROOT\spice+unix\DefaultIcon] +@="C:\\Program Files\\VirtViewer v11.0-256\\bin\\remote-viewer.exe,1" + +[HKEY_CLASSES_ROOT\spice+unix\Extensions] +[HKEY_CLASSES_ROOT\spice+unix\shell] +[HKEY_CLASSES_ROOT\spice+unix\shell\open] +[HKEY_CLASSES_ROOT\spice+unix\shell\open\command] +@="\"C:\\Program Files\\VirtViewer v11.0-256\\bin\\remote-viewer.exe\" \"%1\"" +``` +This URI handler is working, and can be seen to work by typing ```spice://abcdefg``` in firefox. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1429 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1429 new file mode 100644 index 000000000..17918bae2 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1429 @@ -0,0 +1,55 @@ +Out of bounds in xilinx_spips_write() +Description of problem: +The size of TYPE_XILINX_SPIPS's and TYPE_XILINX_QSPIPS's memory regions is +0x100, but it is set to 0x200. UBSAN captures Out of bounds accesses. +Steps to reproduce: +``` +export QEMU=/path/to/qemu-system-aarch64 +export UBSAN_OPTIONS=halt_on_error=1:symbolize=1:print_stacktrace=1 + +cat << EOF | $QEMU \ +-machine xlnx-zcu102 -monitor none -serial none \ +-display none -nodefaults -qtest stdio +writew 0xff050108 0x29be +EOF +``` +Additional information: +``` +==852678==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases! +[I 0.000001] OPENED +pulseaudio: set_sink_input_volume() failed +pulseaudio: Reason: Invalid argument +pulseaudio: set_sink_input_mute() failed +pulseaudio: Reason: Invalid argument +qemu-system-aarch64: warning: nic cadence_gem.0 has no peer +qemu-system-aarch64: warning: nic cadence_gem.1 has no peer +qemu-system-aarch64: warning: nic cadence_gem.2 has no peer +qemu-system-aarch64: warning: nic cadence_gem.3 has no peer +[R +0.323364] writew 0xff050108 0x29be +../hw/ssi/xilinx_spips.c:1031:22: runtime error: index 66 out of bounds for type 'uint32_t [64]' + #0 0x55b7450b6895 in xilinx_spips_write /home/liuqiang/project-videzzo/qemu-devel/build/../hw/ssi/xilinx_spips.c:1031:22 + #1 0x55b747b29790 in memory_region_write_accessor /home/liuqiang/project-videzzo/qemu-devel/build/../softmmu/memory.c:493:5 + #2 0x55b747b28c2d in access_with_adjusted_size /home/liuqiang/project-videzzo/qemu-devel/build/../softmmu/memory.c:555:18 + #3 0x55b747b268f4 in memory_region_dispatch_write /home/liuqiang/project-videzzo/qemu-devel/build/../softmmu/memory.c:1515:16 + #4 0x55b747c1a071 in flatview_write_continue /home/liuqiang/project-videzzo/qemu-devel/build/../softmmu/physmem.c:2825:23 + #5 0x55b747c00d92 in flatview_write /home/liuqiang/project-videzzo/qemu-devel/build/../softmmu/physmem.c:2867:12 + #6 0x55b747c007b8 in address_space_write /home/liuqiang/project-videzzo/qemu-devel/build/../softmmu/physmem.c:2963:18 + #7 0x55b747c49f31 in qtest_process_command /home/liuqiang/project-videzzo/qemu-devel/build/../softmmu/qtest.c:528:13 + #8 0x55b747c42f6e in qtest_process_inbuf /home/liuqiang/project-videzzo/qemu-devel/build/../softmmu/qtest.c:802:9 + #9 0x55b747c5b783 in qtest_read /home/liuqiang/project-videzzo/qemu-devel/build/../softmmu/qtest.c:814:5 + #10 0x55b748c6b602 in qemu_chr_be_write_impl /home/liuqiang/project-videzzo/qemu-devel/build/../chardev/char.c:201:9 + #11 0x55b748c6b74a in qemu_chr_be_write /home/liuqiang/project-videzzo/qemu-devel/build/../chardev/char.c:213:9 + #12 0x55b748c81f6a in fd_chr_read /home/liuqiang/project-videzzo/qemu-devel/build/../chardev/char-fd.c:72:9 + #13 0x55b7481cbe66 in qio_channel_fd_source_dispatch /home/liuqiang/project-videzzo/qemu-devel/build/../io/channel-watch.c:84:12 + #14 0x7fbad3de404d in g_main_context_dispatch (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x5204d) + #15 0x55b74923a917 in glib_pollfds_poll /home/liuqiang/project-videzzo/qemu-devel/build/../util/main-loop.c:297:9 + #16 0x55b749238017 in os_host_main_loop_wait /home/liuqiang/project-videzzo/qemu-devel/build/../util/main-loop.c:320:5 + #17 0x55b749237967 in main_loop_wait /home/liuqiang/project-videzzo/qemu-devel/build/../util/main-loop.c:606:11 + #18 0x55b745858753 in qemu_main_loop /home/liuqiang/project-videzzo/qemu-devel/build/../softmmu/runstate.c:739:9 + #19 0x55b74304cf34 in qemu_default_main /home/liuqiang/project-videzzo/qemu-devel/build/../softmmu/main.c:37:14 + #20 0x55b74304cfd0 in main /home/liuqiang/project-videzzo/qemu-devel/build/../softmmu/main.c:48:12 + #21 0x7fbad227a082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16 + #22 0x55b742fa271d in _start (/home/liuqiang/project-videzzo/qemu-devel/build/qemu-system-aarch64+0x3dc371d) + +SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior ../hw/ssi/xilinx_spips.c:1031:22 in +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/143 b/gitlab/issues_text/target_missing/host_missing/accel_missing/143 new file mode 100644 index 000000000..b0e822d91 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/143 @@ -0,0 +1 @@ +xhci HCIVERSION register read emulation incorrectly handled diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1430 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1430 new file mode 100644 index 000000000..18ec2faf4 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1430 @@ -0,0 +1,110 @@ +Underflow in xlnx_dp_aux_push_rx_fifo() +Description of problem: +Pop two times from s->tx_fifo[2] but there is one element left. Since the fifo +is not empty, the check at [1] will fail. + +``` +static void xilinx_spips_flush_txfifo(XilinxSPIPS *s) +{ + // ... + for (;;) { + // ... + if (fifo8_is_empty(&s->tx_fifo)) { // ---------------> [1] + xilinx_spips_update_ixr(s); + return; + } else if (s->snoop_state == SNOOP_STRIPING || + s->snoop_state == SNOOP_NONE) { + for (i = 0; i < num_effective_busses(s); ++i) { + tx_rx[i] = fifo8_pop(&s->tx_fifo); // ---------> [2] + } + stripe8(tx_rx, num_effective_busses(s), false); + } else if (s->snoop_state >= SNOOP_ADDR) { + // ... +``` +Steps to reproduce: +``` +export QEMU=/path/to/qemu-system-aarch64 + +cat << EOF | $QEMU \ +-machine xlnx-zcu102 -monitor none -serial none \ +-display none -nodefaults -qtest stdio +writel 0xff0f00a0 0x74b13699 +readl 0xc1af068c +EOF +``` +Additional information: +``` +==64457==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases! +INFO: found LLVMFuzzerCustomMutator (0x55f8037f3440). Disabling -len_control by default. +INFO: Running with entropic power schedule (0xFF, 100). +INFO: Seed: 1864808059 +INFO: Loaded 1 modules (600775 inline 8-bit counters): 600775 [0x55f806e06000, 0x55f806e98ac7), +INFO: Loaded 1 PC tables (600775 PCs): 600775 [0x55f8064dab90,0x55f806e05800), +/root/videzzo/videzzo_qemu/out-san/qemu-videzzo-aarch64-target-videzzo-fuzz-xlnx-zynqmp-qspips: Running 1 inputs 1 time(s) each. +INFO: Reading pre_seed_input if any ... +INFO: Executing pre_seed_input if any ... +Matching objects by name , *spi*, *lqspi* +This process will fuzz the following MemoryRegions: + * spi[0] (size 200) + * spi[0] (size 200) + * lqspi[0] (size 2000000) + * spi[0] (size 200) +This process will fuzz through the following interfaces: + * clock_step, EVENT_TYPE_CLOCK_STEP, 0xffffffff +0xffffffff, 255,255 + * spi, EVENT_TYPE_MMIO_READ, 0xff050000 +0x200, 1,4 + * spi, EVENT_TYPE_MMIO_WRITE, 0xff050000 +0x200, 1,4 + * spi, EVENT_TYPE_MMIO_READ, 0xff040000 +0x200, 1,4 + * spi, EVENT_TYPE_MMIO_WRITE, 0xff040000 +0x200, 1,4 + * spi, EVENT_TYPE_MMIO_READ, 0xff0f0000 +0x200, 1,4 + * spi, EVENT_TYPE_MMIO_WRITE, 0xff0f0000 +0x200, 1,4 + * lqspi, EVENT_TYPE_MMIO_READ, 0xc0000000 +0x2000000, 4,4 + * lqspi, EVENT_TYPE_MMIO_WRITE, 0xc0000000 +0x2000000, 4,4 +INFO: A corpus is not provided, starting from an empty corpus +#2 INITED cov: 3 ft: 4 corp: 1/1b exec/s: 0 rss: 509Mb +Running: /root/videzzo/videzzo_qemu/out-san/poc-qemu-videzzo-aarch64-target-videzzo-fuzz-xlnx-zynqmp-qspips-crash-a2dce6d03fde8dc9cb50fb0c8708f307ca93d7c2.minimized +qemu-videzzo-aarch64-target-videzzo-fuzz-xlnx-zynqmp-qspips: ../util/fifo8.c:62: uint8_t fifo8_pop(Fifo8 *): Assertion `fifo->num > 0' failed. +==64457== ERROR: libFuzzer: deadly signal + #0 0x55f7fecb90fe in __sanitizer_print_stack_trace /root/llvm-project/compiler-rt/lib/asan/asan_stack.cpp:86:3 + #1 0x55f7fec07d71 in fuzzer::PrintStackTrace() /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerUtil.cpp:210:38 + #2 0x55f7febe0ca6 in fuzzer::Fuzzer::CrashCallback() (.part.0) /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:236:18 + #3 0x55f7febe0d72 in fuzzer::Fuzzer::CrashCallback() /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:208:1 + #4 0x55f7febe0d72 in fuzzer::Fuzzer::StaticCrashSignalCallback() /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:207:19 + #5 0x7f67ea63a41f (/lib/x86_64-linux-gnu/libpthread.so.0+0x1441f) + #6 0x7f67ea44c00a in __libc_signal_restore_set /build/glibc-SzIz7B/glibc-2.31/signal/../sysdeps/unix/sysv/linux/internal-signals.h:86:3 + #7 0x7f67ea44c00a in raise /build/glibc-SzIz7B/glibc-2.31/signal/../sysdeps/unix/sysv/linux/raise.c:48:3 + #8 0x7f67ea42b858 in abort /build/glibc-SzIz7B/glibc-2.31/stdlib/abort.c:79:7 + #9 0x7f67ea42b728 in __assert_fail_base /build/glibc-SzIz7B/glibc-2.31/assert/assert.c:92:3 + #10 0x7f67ea43cfd5 in __assert_fail /build/glibc-SzIz7B/glibc-2.31/assert/assert.c:101:3 + #11 0x55f803645699 in fifo8_pop /root/videzzo/videzzo_qemu/qemu/out-san/../util/fifo8.c:62:5 + #12 0x55f8009d1ded in xilinx_spips_flush_txfifo /root/videzzo/videzzo_qemu/qemu/out-san/../hw/ssi/xilinx_spips.c:623:28 + #13 0x55f8009dc092 in lqspi_load_cache /root/videzzo/videzzo_qemu/qemu/out-san/../hw/ssi/xilinx_spips.c:1194:9 + #14 0x55f8009da069 in lqspi_read /root/videzzo/videzzo_qemu/qemu/out-san/../hw/ssi/xilinx_spips.c:1231:5 + #15 0x55f80294a61a in memory_region_read_with_attrs_accessor /root/videzzo/videzzo_qemu/qemu/out-san/../softmmu/memory.c:464:9 + #16 0x55f802908961 in access_with_adjusted_size /root/videzzo/videzzo_qemu/qemu/out-san/../softmmu/memory.c:555:18 + #17 0x55f8029060d8 in memory_region_dispatch_read1 /root/videzzo/videzzo_qemu/qemu/out-san/../softmmu/memory.c:1431:16 + #18 0x55f802905468 in memory_region_dispatch_read /root/videzzo/videzzo_qemu/qemu/out-san/../softmmu/memory.c:1458:9 + #19 0x55f802983a6d in flatview_read_continue /root/videzzo/videzzo_qemu/qemu/out-san/../softmmu/physmem.c:2892:23 + #20 0x55f802985078 in flatview_read /root/videzzo/videzzo_qemu/qemu/out-san/../softmmu/physmem.c:2934:12 + #21 0x55f802984b38 in address_space_read_full /root/videzzo/videzzo_qemu/qemu/out-san/../softmmu/physmem.c:2947:18 + #22 0x55f7fecebb51 in address_space_read /root/videzzo/videzzo_qemu/qemu/include/exec/memory.h:2873:18 + #23 0x55f7fecebb51 in qemu_readl /root/videzzo/videzzo_qemu/qemu/out-san/../tests/qtest/videzzo/videzzo_qemu.c:1037:5 + #24 0x55f7fece9c16 in dispatch_mmio_read /root/videzzo/videzzo_qemu/qemu/out-san/../tests/qtest/videzzo/videzzo_qemu.c:1051:35 + #25 0x55f8037ee8bf in videzzo_dispatch_event /root/videzzo/videzzo.c:1140:5 + #26 0x55f8037e5c3d in __videzzo_execute_one_input /root/videzzo/videzzo.c:288:9 + #27 0x55f8037e59e4 in videzzo_execute_one_input /root/videzzo/videzzo.c:329:9 + #28 0x55f7fed0108c in videzzo_qemu /root/videzzo/videzzo_qemu/qemu/out-san/../tests/qtest/videzzo/videzzo_qemu.c:1520:12 + #29 0x55f8037f370b in LLVMFuzzerTestOneInput /root/videzzo/videzzo.c:1910:18 + #30 0x55f7febe1816 in fuzzer::Fuzzer::ExecuteCallback(unsigned char*, unsigned long) /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:594:17 + #31 0x55f7febc4444 in fuzzer::RunOneTest(fuzzer::Fuzzer*, char const*, unsigned long) /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:323:21 + #32 0x55f7febcf3ee in fuzzer::FuzzerDriver(int*, char***, int (*)(unsigned char*, unsigned long)) /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:885:19 + #33 0x55f7febbb9d6 in main /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerMain.cpp:20:30 + #34 0x7f67ea42d082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16 + #35 0x55f7febbba2d in _start (/root/videzzo/videzzo_qemu/out-san/qemu-videzzo-aarch64-target-videzzo-fuzz-xlnx-zynqmp-qspips+0x3454a2d) + +NOTE: libFuzzer has rudimentary signal handlers. + Combine libFuzzer with AddressSanitizer or similar for better crash reports. +SUMMARY: libFuzzer: deadly signal +MS: 0 ; base unit: 0000000000000000000000000000000000000000 +0x1,0xd,0xa0,0x0,0xf,0xff,0x0,0x0,0x0,0x0,0x4,0x0,0x0,0x0,0x99,0x36,0xb1,0x74,0x0,0x0,0x0,0x0,0x0,0xe,0x8c,0x6,0xaf,0xc1,0x0,0x0,0x0,0x0,0x4,0x0,0x0,0x0, +\x01\x0d\xa0\x00\x0f\xff\x00\x00\x00\x00\x04\x00\x00\x00\x996\xb1t\x00\x00\x00\x00\x00\x0e\x8c\x06\xaf\xc1\x00\x00\x00\x00\x04\x00\x00\x00 +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1431 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1431 new file mode 100644 index 000000000..f1d70adb4 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1431 @@ -0,0 +1,50 @@ +qemu spice support opengl +Steps to reproduce: +I wan to use spice support opengl, but my qemu seems not support,what can i do to support opengl for spice? + +qemu configure: +``` +./configure --target-list=x86_64-softmmu --enable-kvm --enable-debug --enable-spice --enable-numa --enable-libusb --enable-curl --enable-usb-redir --enable-libiscsi --enable-virglrenderer --enable-opengl --enable-gtk --prefix="/usr" +``` + +xml: +```xml +<domain type='kvm'> + <name>test</name> + <memory>1048576</memory> + <currentMemory>1048576</currentMemory> + <vcpu>1</vcpu> + <os> + <type arch='x86_64' machine='pc'>hvm</type> + </os> + <cpu mode='custom' match='exact' check='full'> + <topology sockets='1' dies='1' cores='1' threads='1'/> + </cpu> + <features> + <acpi/> + <apic/> + <pae/> + </features> + <clock offset='localtime'/> + <on_poweroff>destroy</on_poweroff> + <on_reboot>restart</on_reboot> + <on_crash>destroy</on_crash> + <devices> + <emulator>/usr/bin/qemu-system-x86_64</emulator> + <disk type='file' device='disk'> + <driver name='qemu' type='qcow2'/> + <source file='/root/kk.img'/> + <target dev='hda' bus='ide'/> + </disk> + <input type='mouse' bus='ps2'/> + <graphics type='spice'> + <listen type='none'/> + <gl enable='yes' rendernode='/dev/dri/renderD128'/> + </graphics> + </devices> +</domain> +``` + +error report: + + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1432 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1432 new file mode 100644 index 000000000..241e8e814 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1432 @@ -0,0 +1,24 @@ +meson prints "Unknown TAP version. The first line MUST be `TAP version <int>`. Assuming version 12." for every test +Description of problem: +Run 'make check V=1' and observe that every test causes an warning message about an unknown TAP version + +``` +>>> G_TEST_SRCDIR=/home/berrange/src/virt/qemu/tests/unit MALLOC_PERTURB_=61 G_TEST_BUILDDIR=/home/berrange/src/virt/qemu/build/tests/unit /home/berrange/src/virt/qemu/build/tests/unit/test-shift128 --tap -k +▶ 22/44 /host-utils/test_lshift OK +▶ 22/44 /host-utils/test_rshift OK +22/44 qemu:unit / test-shift128 OK 0.01s 2 subtests passed + +Unknown TAP version. The first line MUST be `TAP version <int>`. Assuming version 12. + +``` + +This message comes from inside meson + +``` +$ rpm -ql meson | xargs grep 'Unknown TAP version' 2>/dev/null +/usr/lib/python3.11/site-packages/mesonbuild/mtest.py: self.warnings.append('Unknown TAP version. The first line MUST be `TAP version <int>`. Assuming version 12.') +``` + +This is with meson-1.0.0-1.fc38.noarch +Steps to reproduce: +1. make check V=1 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1433 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1433 new file mode 100644 index 000000000..2e880f510 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1433 @@ -0,0 +1,157 @@ +Abort in lan9118_16bit_mode_[read|write]() +Description of problem: +[read|write][w|l] are allowed but [read|write]b are not allowed when mode_16bit is enabled. +Steps to reproduce: +``` +export QEMU=/path/to/qemu-system-arm + +cat << EOF | $QEMU \ +-machine smdkc210 -monitor none -serial none \ +-display none -qtest stdio +readb 0x5000070 +EOF +``` +Additional information: +``` +==1940==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases! +INFO: found LLVMFuzzerCustomMutator (0x5654b8eede90). Disabling -len_control by default. +INFO: Running with entropic power schedule (0xFF, 100). +INFO: Seed: 3248453476 +INFO: Loaded 1 modules (601357 inline 8-bit counters): 601357 [0x5654bbdd8000, 0x5654bbe6ad0d), +INFO: Loaded 1 PC tables (601357 PCs): 601357 [0x5654bb4aa340,0x5654bbdd7410), +./qemu-videzzo-arm-target-videzzo-fuzz-lan9118: Running 1 inputs 1 time(s) each. +INFO: Reading pre_seed_input if any ... +INFO: Executing pre_seed_input if any ... +INFO: -max_len is not provided; libFuzzer will not generate inputs larger than 4096 bytes +Matching objects by name , *lan9118-mmio* +This process will fuzz the following MemoryRegions: + * lan9118-mmio[0] (size 100) +This process will fuzz through the following interfaces: + * clock_step, EVENT_TYPE_CLOCK_STEP, 0xffffffff +0xffffffff, 255,255 + * lan9118-mmio, EVENT_TYPE_MMIO_READ, 0x5000000 +0x100, 1,4 + * lan9118-mmio, EVENT_TYPE_MMIO_WRITE, 0x5000000 +0x100, 1,4 +INFO: A corpus is not provided, starting from an empty corpus +#2 INITED cov: 3 ft: 4 corp: 1/1b exec/s: 0 rss: 221Mb +Running: ./crash-663e5408ee573b1e9d073c796ffbaaae9bd583cb +qemu: hardware error: lan9118_read: Bad size 0x1 + +CPU #0: +R00=00000000 R01=00000000 R02=00000000 R03=00000000 +R04=00000000 R05=00000000 R06=00000000 R07=00000000 +R08=00000000 R09=00000000 R10=00000000 R11=00000000 +R12=00000000 R13=00000000 R14=00000000 R15=00000000 +PSR=400001d3 -Z-- A svc32 +s00=00000000 s01=00000000 d00=0000000000000000 +s02=00000000 s03=00000000 d01=0000000000000000 +s04=00000000 s05=00000000 d02=0000000000000000 +s06=00000000 s07=00000000 d03=0000000000000000 +s08=00000000 s09=00000000 d04=0000000000000000 +s10=00000000 s11=00000000 d05=0000000000000000 +s12=00000000 s13=00000000 d06=0000000000000000 +s14=00000000 s15=00000000 d07=0000000000000000 +s16=00000000 s17=00000000 d08=0000000000000000 +s18=00000000 s19=00000000 d09=0000000000000000 +s20=00000000 s21=00000000 d10=0000000000000000 +s22=00000000 s23=00000000 d11=0000000000000000 +s24=00000000 s25=00000000 d12=0000000000000000 +s26=00000000 s27=00000000 d13=0000000000000000 +s28=00000000 s29=00000000 d14=0000000000000000 +s30=00000000 s31=00000000 d15=0000000000000000 +s32=00000000 s33=00000000 d16=0000000000000000 +s34=00000000 s35=00000000 d17=0000000000000000 +s36=00000000 s37=00000000 d18=0000000000000000 +s38=00000000 s39=00000000 d19=0000000000000000 +s40=00000000 s41=00000000 d20=0000000000000000 +s42=00000000 s43=00000000 d21=0000000000000000 +s44=00000000 s45=00000000 d22=0000000000000000 +s46=00000000 s47=00000000 d23=0000000000000000 +s48=00000000 s49=00000000 d24=0000000000000000 +s50=00000000 s51=00000000 d25=0000000000000000 +s52=00000000 s53=00000000 d26=0000000000000000 +s54=00000000 s55=00000000 d27=0000000000000000 +s56=00000000 s57=00000000 d28=0000000000000000 +s58=00000000 s59=00000000 d29=0000000000000000 +s60=00000000 s61=00000000 d30=0000000000000000 +s62=00000000 s63=00000000 d31=0000000000000000 +FPSCR: 00000000 +CPU #1: +R00=00000000 R01=00000000 R02=00000000 R03=00000000 +R04=00000000 R05=00000000 R06=00000000 R07=00000000 +R08=00000000 R09=00000000 R10=00000000 R11=00000000 +R12=00000000 R13=00000000 R14=00000000 R15=00000000 +PSR=400001d3 -Z-- A svc32 +s00=00000000 s01=00000000 d00=0000000000000000 +s02=00000000 s03=00000000 d01=0000000000000000 +s04=00000000 s05=00000000 d02=0000000000000000 +s06=00000000 s07=00000000 d03=0000000000000000 +s08=00000000 s09=00000000 d04=0000000000000000 +s10=00000000 s11=00000000 d05=0000000000000000 +s12=00000000 s13=00000000 d06=0000000000000000 +s14=00000000 s15=00000000 d07=0000000000000000 +s16=00000000 s17=00000000 d08=0000000000000000 +s18=00000000 s19=00000000 d09=0000000000000000 +s20=00000000 s21=00000000 d10=0000000000000000 +s22=00000000 s23=00000000 d11=0000000000000000 +s24=00000000 s25=00000000 d12=0000000000000000 +s26=00000000 s27=00000000 d13=0000000000000000 +s28=00000000 s29=00000000 d14=0000000000000000 +s30=00000000 s31=00000000 d15=0000000000000000 +s32=00000000 s33=00000000 d16=0000000000000000 +s34=00000000 s35=00000000 d17=0000000000000000 +s36=00000000 s37=00000000 d18=0000000000000000 +s38=00000000 s39=00000000 d19=0000000000000000 +s40=00000000 s41=00000000 d20=0000000000000000 +s42=00000000 s43=00000000 d21=0000000000000000 +s44=00000000 s45=00000000 d22=0000000000000000 +s46=00000000 s47=00000000 d23=0000000000000000 +s48=00000000 s49=00000000 d24=0000000000000000 +s50=00000000 s51=00000000 d25=0000000000000000 +s52=00000000 s53=00000000 d26=0000000000000000 +s54=00000000 s55=00000000 d27=0000000000000000 +s56=00000000 s57=00000000 d28=0000000000000000 +s58=00000000 s59=00000000 d29=0000000000000000 +s60=00000000 s61=00000000 d30=0000000000000000 +s62=00000000 s63=00000000 d31=0000000000000000 +FPSCR: 00000000 +==1940== ERROR: libFuzzer: deadly signal + #0 0x5654b48090fe in __sanitizer_print_stack_trace /root/llvm-project/compiler-rt/lib/asan/asan_stack.cpp:86:3 + #1 0x5654b4757d71 in fuzzer::PrintStackTrace() /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerUtil.cpp:210:38 + #2 0x5654b4730ca6 in fuzzer::Fuzzer::CrashCallback() (.part.0) /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:236:18 + #3 0x5654b4730d72 in fuzzer::Fuzzer::CrashCallback() /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:208:1 + #4 0x5654b4730d72 in fuzzer::Fuzzer::StaticCrashSignalCallback() /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:207:19 + #5 0x7fb6db17941f (/lib/x86_64-linux-gnu/libpthread.so.0+0x1441f) + #6 0x7fb6daf8b00a in __libc_signal_restore_set /build/glibc-SzIz7B/glibc-2.31/signal/../sysdeps/unix/sysv/linux/internal-signals.h:86:3 + #7 0x7fb6daf8b00a in raise /build/glibc-SzIz7B/glibc-2.31/signal/../sysdeps/unix/sysv/linux/raise.c:48:3 + #8 0x7fb6daf6a858 in abort /build/glibc-SzIz7B/glibc-2.31/stdlib/abort.c:79:7 + #9 0x5654b483964a in __wrap_abort /root/videzzo/videzzo_qemu/qemu/build-san-6/../tests/qtest/videzzo/less_crashes_wrappers.c:24:12 + #10 0x5654b6a64d84 in hw_error /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/cpus.c:128:5 + #11 0x5654b5ac50c7 in lan9118_16bit_mode_read /root/videzzo/videzzo_qemu/qemu/build-san-6/../hw/net/lan9118.c:1319:5 + #12 0x5654b7ee045b in memory_region_read_accessor /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/memory.c:440:11 + #13 0x5654b7ea0761 in access_with_adjusted_size /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/memory.c:554:18 + #14 0x5654b7e9db2c in memory_region_dispatch_read1 /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/memory.c:1424:16 + #15 0x5654b7e9d268 in memory_region_dispatch_read /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/memory.c:1457:9 + #16 0x5654b7f1946d in flatview_read_continue /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/physmem.c:2892:23 + #17 0x5654b7f1aa78 in flatview_read /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/physmem.c:2934:12 + #18 0x5654b7f1a538 in address_space_read_full /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/physmem.c:2947:18 + #19 0x5654b483a7ea in address_space_read /root/videzzo/videzzo_qemu/qemu/include/exec/memory.h:2869:18 + #20 0x5654b483a7ea in qemu_readb /root/videzzo/videzzo_qemu/qemu/build-san-6/../tests/qtest/videzzo/videzzo_qemu.c:1010:5 + #21 0x5654b483997e in dispatch_mmio_read /root/videzzo/videzzo_qemu/qemu/build-san-6/../tests/qtest/videzzo/videzzo_qemu.c:1034:35 + #22 0x5654b8ee984f in videzzo_dispatch_event /root/videzzo/videzzo.c:1122:5 + #23 0x5654b8ee0bcb in __videzzo_execute_one_input /root/videzzo/videzzo.c:272:9 + #24 0x5654b8ee0aa0 in videzzo_execute_one_input /root/videzzo/videzzo.c:313:9 + #25 0x5654b48500fc in videzzo_qemu /root/videzzo/videzzo_qemu/qemu/build-san-6/../tests/qtest/videzzo/videzzo_qemu.c:1497:12 + #26 0x5654b8eee132 in LLVMFuzzerTestOneInput /root/videzzo/videzzo.c:1891:18 + #27 0x5654b4731816 in fuzzer::Fuzzer::ExecuteCallback(unsigned char*, unsigned long) /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:594:17 + #28 0x5654b4714444 in fuzzer::RunOneTest(fuzzer::Fuzzer*, char const*, unsigned long) /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:323:21 + #29 0x5654b471f3ee in fuzzer::FuzzerDriver(int*, char***, int (*)(unsigned char*, unsigned long)) /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:885:19 + #30 0x5654b470b9d6 in main /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerMain.cpp:20:30 + #31 0x7fb6daf6c082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16 + #32 0x5654b470ba2d in _start (/root/videzzo/videzzo_qemu/out-san/qemu-videzzo-arm-target-videzzo-fuzz-lan9118+0x300da2d) + +NOTE: libFuzzer has rudimentary signal handlers. + Combine libFuzzer with AddressSanitizer or similar for better crash reports. +SUMMARY: libFuzzer: deadly signal +MS: 0 ; base unit: 0000000000000000000000000000000000000000 +0x4,0x2,0x29,0x92,0xa,0x0,0x0,0x0,0x0,0x0,0x0,0x8,0x70,0x0,0x0,0x5,0x0,0x0,0x0,0x0,0x1,0x0,0x0,0x0,0x1,0x9,0x48,0x0,0x0,0x5,0x0,0x0,0x0,0x0,0x4,0x0,0x0,0x0,0x29,0x1f,0x8e,0x23,0x0,0x0,0x0,0x0, +\x04\x02)\x92\x0a\x00\x00\x00\x00\x00\x00\x08p\x00\x00\x05\x00\x00\x00\x00\x01\x00\x00\x00\x01\x09H\x00\x00\x05\x00\x00\x00\x00\x04\x00\x00\x00)\x1f\x8e#\x00\x00\x00\x00 +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1438 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1438 new file mode 100644 index 000000000..88ef2cda4 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1438 @@ -0,0 +1,7 @@ +Allow to use QEMU sockets as a CAN bus backend +Additional information: +Good possible example how it can be done is via UDP multicast in `python-can` library: +- https://python-can.readthedocs.io/en/master/interfaces/udp_multicast.html + +Another option, with less features is using a simple serial/character device like in: +- https://python-can.readthedocs.io/en/master/interfaces/serial.html diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1439 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1439 new file mode 100644 index 000000000..d3b6abb5e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1439 @@ -0,0 +1,11 @@ +QEMU crashes when there is an "[accel]" section in the config file +Description of problem: +QEMU crashes with a segmentation fault if there is a "[accel]" section in the config file with a type="kvm" entry. It would be maybe still be OK if there was an error message instead, but it should certainly not crash. +Steps to reproduce: +``` +$ cat > /tmp/config <<EOF +[accel] +type = "kvm" +EOF +$ qemu-system-x86_64 -readconfig /tmp/config +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/144 b/gitlab/issues_text/target_missing/host_missing/accel_missing/144 new file mode 100644 index 000000000..9a0915ae8 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/144 @@ -0,0 +1 @@ +Passthrough USB Host Keyboard doesn't work on Q35 platform on boot-up diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1440 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1440 new file mode 100644 index 000000000..1e505afbd --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1440 @@ -0,0 +1 @@ +block/curl.c uses curl features deprecated in curl 7.55.0 and 7.85.0 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1442 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1442 new file mode 100644 index 000000000..4dc69b57a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1442 @@ -0,0 +1 @@ +RISC-V qemu, get cpu tick diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1443 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1443 new file mode 100644 index 000000000..fc03f8a03 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1443 @@ -0,0 +1 @@ +site download.qemu.org | non-adequate function applied for sorting by date-time diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1445 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1445 new file mode 100644 index 000000000..bdebf6252 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1445 @@ -0,0 +1,127 @@ +Negative-size-param in nand_blk_load_512() +Description of problem: +Found a way to trigger negative-size-param when calling memcpy in +nand_blk_load_512() called by nand_getio(). Specifically, the offset can +be larger than NAND_PAGE_SIZE + OOB_SIZE, e.g., 0x211. + +``` c + if (s->blk) { + // ... + } else { + memcpy(s->io, s->storage + PAGE_START(s->addr) + + // offset=0x211 + offset, NAND_PAGE_SIZE + OOB_SIZE - offset); + s->ioaddr = s->io; + } +``` +Steps to reproduce: +``` +export QEMU=/path/to/qemu-system-arm + +cat << EOF | $QEMU \ +-machine tosa -monitor none -serial none \ +-display none -qtest stdio +write 0x10000104 0x1 0x7f +write 0x10000111 0x1 0x52 +read 0x10005200 0x1 +read 0x10005200 0x1 +read 0x10005200 0x1 +read 0x10005200 0x1 +read 0x10005200 0x1 +read 0x10005200 0x1 +read 0x10005200 0x1 +read 0x10005200 0x1 +read 0x10005200 0x1 +read 0x10005200 0x1 +read 0x10005200 0x1 +read 0x10005200 0x1 +read 0x10005200 0x1 +read 0x10005200 0x1 +read 0x10005200 0x1 +read 0x10005200 0x1 +write 0x10005204 0x1 0x15 +write 0x10005201 0x1 0x70 +write 0x10005202 0x1 0x50 +read 0x10005203 0x1 +read 0x10005203 0x1 +EOF +``` +Additional information: +``` +=20435==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases! +INFO: found LLVMFuzzerCustomMutator (0x5645f46c0ac0). Disabling -len_control by default. +INFO: Running with entropic power schedule (0xFF, 100). +INFO: Seed: 3601248722 +INFO: Loaded 1 modules (601321 inline 8-bit counters): 601321 [0x5645f75ae000, 0x5645f7640ce9), +INFO: Loaded 1 PC tables (601321 PCs): 601321 [0x5645f6c801e0,0x5645f75ad070), +/root/videzzo/videzzo_qemu/out-san/qemu-videzzo-arm-target-videzzo-fuzz-tc6393xb: Running 1 inputs 1 time(s) each. +INFO: Reading pre_seed_input if any ... +INFO: Executing pre_seed_input if any ... +Matching objects by name , *tc6393xb* +This process will fuzz the following MemoryRegions: + * tc6393xb.vram[0] (size 100000) + * tc6393xb[0] (size 10000) +This process will fuzz through the following interfaces: + * clock_step, EVENT_TYPE_CLOCK_STEP, 0xffffffff +0xffffffff, 255,255 + * tc6393xb.vram, EVENT_TYPE_MMIO_READ, 0x10100000 +0x100000, 1,4 + * tc6393xb.vram, EVENT_TYPE_MMIO_WRITE, 0x10100000 +0x100000, 1,4 + * tc6393xb, EVENT_TYPE_MMIO_READ, 0x10000000 +0x10000, 1,1 + * tc6393xb, EVENT_TYPE_MMIO_WRITE, 0x10000000 +0x10000, 1,1 +INFO: A corpus is not provided, starting from an empty corpus +#2 INITED cov: 3 ft: 4 corp: 1/1b exec/s: 0 rss: 280Mb +Running: poc-qemu-videzzo-arm-target-videzzo-fuzz-tc6393xb-crash-55c2b01921c18ce020fa35319af4632834e116be.minimized +================================================================= +==20435==ERROR: AddressSanitizer: negative-size-param: (size=-1) + #0 0x5645effd2656 in __asan_memcpy /root/llvm-project/compiler-rt/lib/asan/asan_interceptors_memintrinsics.cpp:22:3 + #1 0x5645f040b342 in nand_blk_load_512 /root/videzzo/videzzo_qemu/qemu/build-san-6/../hw/block/nand.c:794:9 + #2 0x5645f03f1f64 in nand_getio /root/videzzo/videzzo_qemu/qemu/build-san-6/../hw/block/nand.c:601:9 + #3 0x5645f08acc9a in tc6393xb_nand_readb /root/videzzo/videzzo_qemu/qemu/build-san-6/../hw/display/tc6393xb.c:359:20 + #4 0x5645f08a53fc in tc6393xb_readb /root/videzzo/videzzo_qemu/qemu/build-san-6/../hw/display/tc6393xb.c:500:21 + #5 0x5645f36b308b in memory_region_read_accessor /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/memory.c:440:11 + #6 0x5645f3673391 in access_with_adjusted_size /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/memory.c:554:18 + #7 0x5645f367075c in memory_region_dispatch_read1 /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/memory.c:1424:16 + #8 0x5645f366fe98 in memory_region_dispatch_read /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/memory.c:1457:9 + #9 0x5645f36ec09d in flatview_read_continue /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/physmem.c:2892:23 + #10 0x5645f36ed6a8 in flatview_read /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/physmem.c:2934:12 + #11 0x5645f36ed168 in address_space_read_full /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/physmem.c:2947:18 + #12 0x5645f000e7ea in address_space_read /root/videzzo/videzzo_qemu/qemu/include/exec/memory.h:2869:18 + #13 0x5645f000e7ea in qemu_readb /root/videzzo/videzzo_qemu/qemu/build-san-6/../tests/qtest/videzzo/videzzo_qemu.c:1017:5 + #14 0x5645f000d97e in dispatch_mmio_read /root/videzzo/videzzo_qemu/qemu/build-san-6/../tests/qtest/videzzo/videzzo_qemu.c:1041:35 + #15 0x5645f46bc47f in videzzo_dispatch_event /root/videzzo/videzzo.c:1122:5 + #16 0x5645f46b37fb in __videzzo_execute_one_input /root/videzzo/videzzo.c:272:9 + #17 0x5645f46b36d0 in videzzo_execute_one_input /root/videzzo/videzzo.c:313:9 + #18 0x5645f00240fc in videzzo_qemu /root/videzzo/videzzo_qemu/qemu/build-san-6/../tests/qtest/videzzo/videzzo_qemu.c:1504:12 + #19 0x5645f46c0d62 in LLVMFuzzerTestOneInput /root/videzzo/videzzo.c:1891:18 + #20 0x5645eff05816 in fuzzer::Fuzzer::ExecuteCallback(unsigned char*, unsigned long) /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:594:17 + #21 0x5645efee8444 in fuzzer::RunOneTest(fuzzer::Fuzzer*, char const*, unsigned long) /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:323:21 + #22 0x5645efef33ee in fuzzer::FuzzerDriver(int*, char***, int (*)(unsigned char*, unsigned long)) /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:885:19 + #23 0x5645efedf9d6 in main /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerMain.cpp:20:30 + #24 0x7fbc03b97082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16 + #25 0x5645efedfa2d in _start (/root/videzzo/videzzo_qemu/out-san/qemu-videzzo-arm-target-videzzo-fuzz-tc6393xb+0x300ea2d) + +0x7fbbf45ffa11 is located 529 bytes inside of 69206016-byte region [0x7fbbf45ff800,0x7fbbf87ff800) +allocated by thread T0 here: + #0 0x5645effd36cf in malloc /root/llvm-project/compiler-rt/lib/asan/asan_malloc_linux.cpp:145:3 + #1 0x7fbc04e4ee98 in g_malloc (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x57e98) + #2 0x5645f3a1bdcb in device_set_realized /root/videzzo/videzzo_qemu/qemu/build-san-6/../hw/core/qdev.c:553:13 + #3 0x5645f3a53a6b in property_set_bool /root/videzzo/videzzo_qemu/qemu/build-san-6/../qom/object.c:2273:5 + #4 0x5645f3a4c99d in object_property_set /root/videzzo/videzzo_qemu/qemu/build-san-6/../qom/object.c:1408:5 + #5 0x5645f3a60329 in object_property_set_qobject /root/videzzo/videzzo_qemu/qemu/build-san-6/../qom/qom-qobject.c:28:10 + #6 0x5645f3a4d6fd in object_property_set_bool /root/videzzo/videzzo_qemu/qemu/build-san-6/../qom/object.c:1477:15 + #7 0x5645f3a0d5c2 in qdev_realize /root/videzzo/videzzo_qemu/qemu/build-san-6/../hw/core/qdev.c:333:12 + #8 0x5645f03f3f30 in nand_init /root/videzzo/videzzo_qemu/qemu/build-san-6/../hw/block/nand.c:646:5 + #9 0x5645f08a44c2 in tc6393xb_init /root/videzzo/videzzo_qemu/qemu/build-san-6/../hw/display/tc6393xb.c:558:16 + #10 0x5645f27b7822 in tosa_init /root/videzzo/videzzo_qemu/qemu/build-san-6/../hw/arm/tosa.c:250:12 + #11 0x5645f05dc5d7 in machine_run_board_init /root/videzzo/videzzo_qemu/qemu/build-san-6/../hw/core/machine.c:1400:5 + #12 0x5645f2269aab in qemu_init_board /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/vl.c:2485:5 + #13 0x5645f22697bc in qmp_x_exit_preconfig /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/vl.c:2581:5 + #14 0x5645f2270d3f in qemu_init /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/vl.c:3584:9 + #15 0x5645f00223f3 in LLVMFuzzerInitialize /root/videzzo/videzzo_qemu/qemu/build-san-6/../tests/qtest/videzzo/videzzo_qemu.c:1761:5 + #16 0x5645efeeffab in fuzzer::FuzzerDriver(int*, char***, int (*)(unsigned char*, unsigned long)) /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:664:29 + #17 0x5645efedf9d6 in main /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerMain.cpp:20:30 + #18 0x7fbc03b97082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16 + +SUMMARY: AddressSanitizer: negative-size-param /root/llvm-project/compiler-rt/lib/asan/asan_interceptors_memintrinsics.cpp:22:3 in __asan_memcpy +==20435==ABORTING +MS: 0 ; base unit: 0000000000000000000000000000000000000000 +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1446 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1446 new file mode 100644 index 000000000..10797d6d7 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1446 @@ -0,0 +1,175 @@ +Heap buffer overflow in nand_blk_write_512() +Description of problem: +I captured the negative-size-param (memcpy) in nand_blk_load_512() like below. + +``` +diff --git a/hw/block/nand.c b/hw/block/nand.c +index 8bc80e351..f68b23d05 100644 +--- a/hw/block/nand.c ++++ b/hw/block/nand.c +@@ -790,6 +790,10 @@ static void glue(nand_blk_load_, NAND_PAGE_SIZE)(NANDFlashState *s, + s->ioaddr = s->io + (PAGE_START(addr) & 0x1ff) + offset; + } + } else { ++ int size = NAND_PAGE_SIZE + OOB_SIZE - offset; ++ if (size < 0) { ++ return; ++ } + memcpy(s->io, s->storage + PAGE_START(s->addr) + + offset, NAND_PAGE_SIZE + OOB_SIZE - offset); + s->ioaddr = s->io; + +``` + +Then, I triggered an integer overflow in nand_blk_write_512() resulting in a +heap buffer overflow. Specifically, s->iolen is a signed integer[1], but based +on the function signature of mem_and(), s->iolen will be casted to an unsigned +integer[2]. Asan then captures a heap buffer overflow[3]. + +``` +static void glue(nand_blk_write_, NAND_PAGE_SIZE)(NANDFlashState *s) +{ + // ... + if (!s->blk) { + mem_and(s->storage + PAGE_START(s->addr) + (s->addr & PAGE_MASK) + + s->offset, s->io, s->iolen); // <--------------- [1] + } else if (s->mem_oob) { + // ... + +static void mem_and(uint8_t *dest, const uint8_t *src, size_t n) // <--- [2] +{ + int i; + for (i = 0; i < n; i++) { + dest[i] &= src[i]; // <----------------------------------------- [3] + } +} +``` +Steps to reproduce: +Please patch your hw/block/nand.c first. + +``` +export QEMU=/path/to/qemu-system-arm + +cat << EOF | $QEMU \ +-machine tosa -monitor none -serial none \ +-display none -qtest stdio +write 0x10000111 0x1 0xca +write 0x10000104 0x1 0x47 +write 0x1000ca04 0x1 0xd7 +write 0x1000ca01 0x1 0xe0 +write 0x1000ca04 0x1 0x71 +write 0x1000ca00 0x1 0x50 +write 0x1000ca04 0x1 0xd7 +read 0x1000ca02 0x1 +write 0x1000ca01 0x1 0x10 +EOF +``` +Additional information: +``` +==15750==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases! +INFO: found LLVMFuzzerCustomMutator (0x560e65814d70). Disabling -len_control by default. +INFO: Running with entropic power schedule (0xFF, 100). +INFO: Seed: 4218744906 +INFO: Loaded 1 modules (601336 inline 8-bit counters): 601336 [0x560e68702000, 0x560e68794cf8), +INFO: Loaded 1 PC tables (601336 PCs): 601336 [0x560e67dd42a0,0x560e68701220), +/root/videzzo/videzzo_qemu/out-san/qemu-videzzo-arm-target-videzzo-fuzz-tc6393xb: Running 1 inputs 1 time(s) each. +INFO: Reading pre_seed_input if any ... +INFO: Executing pre_seed_input if any ... +Matching objects by name , *tc6393xb* +This process will fuzz the following MemoryRegions: + * tc6393xb.vram[0] (size 100000) + * tc6393xb[0] (size 10000) +This process will fuzz through the following interfaces: + * clock_step, EVENT_TYPE_CLOCK_STEP, 0xffffffff +0xffffffff, 255,255 + * tc6393xb.vram, EVENT_TYPE_MMIO_READ, 0x10100000 +0x100000, 1,4 + * tc6393xb.vram, EVENT_TYPE_MMIO_WRITE, 0x10100000 +0x100000, 1,4 + * tc6393xb, EVENT_TYPE_MMIO_READ, 0x10000000 +0x10000, 1,1 + * tc6393xb, EVENT_TYPE_MMIO_WRITE, 0x10000000 +0x10000, 1,1 +INFO: A corpus is not provided, starting from an empty corpus +#2 INITED cov: 3 ft: 4 corp: 1/1b exec/s: 0 rss: 281Mb +Running: /root/videzzo/videzzo_qemu/out-san/poc-qemu-videzzo-arm-target-videzzo-fuzz-tc6393xb-crash-35f3f537422c4e74ce65177b3d6369045e60b47f.minimized +================================================================= +==15750==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x61f000000de0 at pc 0x560e61557210 bp 0x7ffcfc4a59f0 sp 0x7ffcfc4a59e8 +READ of size 1 at 0x61f000000de0 thread T0 + #0 0x560e6155720f in mem_and /root/videzzo/videzzo_qemu/qemu/build-san-6/../hw/block/nand.c:101:20 + #1 0x560e6155ac9c in nand_blk_write_512 /root/videzzo/videzzo_qemu/qemu/build-san-6/../hw/block/nand.c:663:9 + #2 0x560e61544200 in nand_command /root/videzzo/videzzo_qemu/qemu/build-san-6/../hw/block/nand.c:293:13 + #3 0x560e6153cc83 in nand_setio /root/videzzo/videzzo_qemu/qemu/build-san-6/../hw/block/nand.c:520:13 + #4 0x560e61a0a69e in tc6393xb_nand_writeb /root/videzzo/videzzo_qemu/qemu/build-san-6/../hw/display/tc6393xb.c:380:13 + #5 0x560e619f9bf7 in tc6393xb_writeb /root/videzzo/videzzo_qemu/qemu/build-san-6/../hw/display/tc6393xb.c:524:9 + #6 0x560e647c7d03 in memory_region_write_accessor /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/memory.c:492:5 + #7 0x560e647c7641 in access_with_adjusted_size /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/memory.c:554:18 + #8 0x560e647c5f66 in memory_region_dispatch_write /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/memory.c:1514:16 + #9 0x560e6485409e in flatview_write_continue /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/physmem.c:2825:23 + #10 0x560e648421eb in flatview_write /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/physmem.c:2867:12 + #11 0x560e64841ca8 in address_space_write /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/physmem.c:2963:18 + #12 0x560e61170162 in qemu_writeb /root/videzzo/videzzo_qemu/qemu/build-san-6/../tests/qtest/videzzo/videzzo_qemu.c:1080:5 + #13 0x560e6116eef7 in dispatch_mmio_write /root/videzzo/videzzo_qemu/qemu/build-san-6/../tests/qtest/videzzo/videzzo_qemu.c:1227:28 + #14 0x560e6581072f in videzzo_dispatch_event /root/videzzo/videzzo.c:1122:5 + #15 0x560e65807aab in __videzzo_execute_one_input /root/videzzo/videzzo.c:272:9 + #16 0x560e65807980 in videzzo_execute_one_input /root/videzzo/videzzo.c:313:9 + #17 0x560e611780fc in videzzo_qemu /root/videzzo/videzzo_qemu/qemu/build-san-6/../tests/qtest/videzzo/videzzo_qemu.c:1504:12 + #18 0x560e65815012 in LLVMFuzzerTestOneInput /root/videzzo/videzzo.c:1891:18 + #19 0x560e61059816 in fuzzer::Fuzzer::ExecuteCallback(unsigned char*, unsigned long) /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:594:17 + #20 0x560e6103c444 in fuzzer::RunOneTest(fuzzer::Fuzzer*, char const*, unsigned long) /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:323:21 + #21 0x560e610473ee in fuzzer::FuzzerDriver(int*, char***, int (*)(unsigned char*, unsigned long)) /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:885:19 + #22 0x560e610339d6 in main /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerMain.cpp:20:30 + #23 0x7f79587d0082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16 + #24 0x560e61033a2d in _start (/root/videzzo/videzzo_qemu/out-san/qemu-videzzo-arm-target-videzzo-fuzz-tc6393xb+0x300fa2d) + +0x61f000000de0 is located 0 bytes to the right of 3424-byte region [0x61f000000080,0x61f000000de0) +allocated by thread T0 here: + #0 0x560e611276cf in malloc /root/llvm-project/compiler-rt/lib/asan/asan_malloc_linux.cpp:145:3 + #1 0x7f7959a87e98 in g_malloc (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x57e98) + #2 0x560e64b98871 in object_new /root/videzzo/videzzo_qemu/qemu/build-san-6/../qom/object.c:749:12 + #3 0x560e64b5d1a1 in qdev_new /root/videzzo/videzzo_qemu/qemu/build-san-6/../hw/core/qdev.c:153:19 + #4 0x560e61547ea5 in nand_init /root/videzzo/videzzo_qemu/qemu/build-san-6/../hw/block/nand.c:639:11 + #5 0x560e619f8772 in tc6393xb_init /root/videzzo/videzzo_qemu/qemu/build-san-6/../hw/display/tc6393xb.c:558:16 + #6 0x560e6390bad2 in tosa_init /root/videzzo/videzzo_qemu/qemu/build-san-6/../hw/arm/tosa.c:250:12 + #7 0x560e61730887 in machine_run_board_init /root/videzzo/videzzo_qemu/qemu/build-san-6/../hw/core/machine.c:1400:5 + #8 0x560e633bdd5b in qemu_init_board /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/vl.c:2485:5 + #9 0x560e633bda6c in qmp_x_exit_preconfig /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/vl.c:2581:5 + #10 0x560e633c4fef in qemu_init /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/vl.c:3584:9 + #11 0x560e611763f3 in LLVMFuzzerInitialize /root/videzzo/videzzo_qemu/qemu/build-san-6/../tests/qtest/videzzo/videzzo_qemu.c:1761:5 + #12 0x560e61043fab in fuzzer::FuzzerDriver(int*, char***, int (*)(unsigned char*, unsigned long)) /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:664:29 + #13 0x560e610339d6 in main /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerMain.cpp:20:30 + #14 0x7f79587d0082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16 + +SUMMARY: AddressSanitizer: heap-buffer-overflow /root/videzzo/videzzo_qemu/qemu/build-san-6/../hw/block/nand.c:101:20 in mem_and +Shadow bytes around the buggy address: + 0x0c3e7fff8160: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 + 0x0c3e7fff8170: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 + 0x0c3e7fff8180: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 + 0x0c3e7fff8190: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 + 0x0c3e7fff81a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +=>0x0c3e7fff81b0: 00 00 00 00 00 00 00 00 00 00 00 00[fa]fa fa fa + 0x0c3e7fff81c0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa + 0x0c3e7fff81d0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa + 0x0c3e7fff81e0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa + 0x0c3e7fff81f0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa + 0x0c3e7fff8200: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa +Shadow byte legend (one shadow byte represents 8 application bytes): + Addressable: 00 + Partially addressable: 01 02 03 04 05 06 07 + Heap left redzone: fa + Freed heap region: fd + Stack left redzone: f1 + Stack mid redzone: f2 + Stack right redzone: f3 + Stack after return: f5 + Stack use after scope: f8 + Global redzone: f9 + Global init order: f6 + Poisoned by user: f7 + Container overflow: fc + Array cookie: ac + Intra object redzone: bb + ASan internal: fe + Left alloca redzone: ca + Right alloca redzone: cb + Shadow gap: cc +==15750==ABORTING +MS: 0 ; base unit: 0000000000000000000000000000000000000000 +0x1,0xb,0x12,0x1,0x0,0x10,0x0,0x0,0x0,0x0,0x1,0x0,0x0,0x0,0xca,0x4f,0x4d,0x5f,0x0,0x0,0x0,0x0,0x1,0xb,0x4,0x1,0x0,0x10,0x0,0x0,0x0,0x0,0x1,0x0,0x0,0x0,0x47,0xf0,0xc8,0x58,0x0,0x0,0x0,0x0,0x1,0xb,0x4,0xa1,0x0,0x10,0x0,0x0,0x0,0x0,0x1,0x0,0x0,0x0,0xd7,0x38,0xfc,0x29,0x0,0x0,0x0,0x0,0x1,0xb,0x1,0x9a,0x0,0x10,0x0,0x0,0x0,0x0,0x1,0x0,0x0,0x0,0xe0,0xb0,0x63,0x62,0x0,0x0,0x0,0x0,0x1,0xb,0x4,0x8a,0x0,0x10,0x0,0x0,0x0,0x0,0x1,0x0,0x0,0x0,0x71,0xaa,0x20,0x60,0x0,0x0,0x0,0x0,0x1,0xb,0x0,0x5,0x0,0x10,0x0,0x0,0x0,0x0,0x1,0x0,0x0,0x0,0x50,0x9f,0x0,0x40,0x0,0x0,0x0,0x0,0x1,0xb,0x4,0xa1,0x0,0x10,0x0,0x0,0x0,0x0,0x1,0x0,0x0,0x0,0xd7,0x38,0xfc,0x29,0x0,0x0,0x0,0x0,0x0,0xa,0x2,0x24,0x0,0x10,0x0,0x0,0x0,0x0,0x1,0x0,0x0,0x0,0x1,0xb,0x1,0xc5,0x0,0x10,0x0,0x0,0x0,0x0,0x1,0x0,0x0,0x0,0x10,0x8b,0x36,0x70,0x0,0x0,0x0,0x0, +\x01\x0b\x12\x01\x00\x10\x00\x00\x00\x00\x01\x00\x00\x00\xcaOM_\x00\x00\x00\x00\x01\x0b\x04\x01\x00\x10\x00\x00\x00\x00\x01\x00\x00\x00G\xf0\xc8X\x00\x00\x00\x00\x01\x0b\x04\xa1\x00\x10\x00\x00\x00\x00\x01\x00\x00\x00\xd78\xfc)\x00\x00\x00\x00\x01\x0b\x01\x9a\x00\x10\x00\x00\x00\x00\x01\x00\x00\x00\xe0\xb0cb\x00\x00\x00\x00\x01\x0b\x04\x8a\x00\x10\x00\x00\x00\x00\x01\x00\x00\x00q\xaa `\x00\x00\x00\x00\x01\x0b\x00\x05\x00\x10\x00\x00\x00\x00\x01\x00\x00\x00P\x9f\x00@\x00\x00\x00\x00\x01\x0b\x04\xa1\x00\x10\x00\x00\x00\x00\x01\x00\x00\x00\xd78\xfc)\x00\x00\x00\x00\x00\x0a\x02$\x00\x10\x00\x00\x00\x00\x01\x00\x00\x00\x01\x0b\x01\xc5\x00\x10\x00\x00\x00\x00\x01\x00\x00\x00\x10\x8b6p\x00\x00\x00\x00 +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/145 b/gitlab/issues_text/target_missing/host_missing/accel_missing/145 new file mode 100644 index 000000000..64f67892c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/145 @@ -0,0 +1 @@ +Issues with qemu-img, libgfapi, and encryption at rest diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1450 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1450 new file mode 100644 index 000000000..da42fe2ce --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1450 @@ -0,0 +1 @@ +ERROR: meson setup failed diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1451 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1451 new file mode 100644 index 000000000..fad830051 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1451 @@ -0,0 +1 @@ +Assertion failure: virtio_net_get_subqueue(nc)->async_tx.elem failed. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1455 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1455 new file mode 100644 index 000000000..c32a78bc0 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1455 @@ -0,0 +1,3 @@ +copy-paste not working +Description of problem: +copy-paste not working under Sway (wayland - wlroots) when I use `-display gtk`. This was broken recently. I have `spice-vdagent` as well as `spice-vdagentd` running properly in the guest, still copy-paste not working. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1457 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1457 new file mode 100644 index 000000000..ac0548f1c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1457 @@ -0,0 +1 @@ +ide: assertion `bmdma->bus->retry_unit != (uint8_t)-1' failed. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1458 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1458 new file mode 100644 index 000000000..7a8b493c9 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1458 @@ -0,0 +1,27 @@ +ns16550a reg-shift incorrect for qemu-system-riscv64 +Description of problem: +Missing reg-shift 0 on the ns16550n in qemu-system-riscv64 creates an impossible assumption case. +Steps to reproduce: +1. qemu-system-riscv64 -M virt,dumpdtb=dtb +2. dtc dtb | less + + serial@10000000 { + interrupts = <0x0a>; + interrupt-parent = <0x03>; + clock-frequency = "\08@"; + reg = <0x00 0x10000000 0x00 0x100>; + compatible = "ns16550a"; + }; + +Generally, ns16550a has a default reg-shift of 0 on x86,x86_64 for compatibility reasons. All other architectures have an assumed reg-shift of 2 (or having the reg-shift assumption overridden by fdt providing a reg-shift property) + +Beyond the above, anything non-standard is assumed to be specified by the "reg-shift" property fdt. + +qemu-system-riscv64 seems to "assume" a reg-shift of 0. Other riscv64 devices don't supply "reg-shift" (SiFive Unmatched) and "assume" 2. +The above means driver writers don't actually know what to "assume" on riscv64 ns16550a when no reg-shift is present. + + +Essentially, qemu-system-riscv64 needs to do one of the following: + +* If serial ns16550a with a uart reg-shift of 0 is intentional, qemu needs to advertise the deviance via "reg-shift 0" +* If serial ns16550a with a uart reg-shift of 0 is unintentional, it needs updated to 2 so drivers can assume 2 on riscv64. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1459 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1459 new file mode 100644 index 000000000..3f5312c05 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1459 @@ -0,0 +1,35 @@ +analyze-migration.py doesn't account for saved blocks +Description of problem: + +Steps to reproduce: +1. Make a migration snapshot that includes incremental block device (from HMP: `migrate -i "exec: cat > snap"`) +2. Load the snapshot: `scripts/analyze-migration.py -f snap` + + +``` +Traceback (most recent call last): + File "scripts/analyze-migration.py", line 605, in <module> + dump.read(dump_memory = args.memory) + File "scripts/analyze-migration.py", line 539, in read + classdesc = self.section_classes[section_key] +KeyError: ('block', 0) +``` +Additional information: +Here's pseudocode derived from `block_load` in `migration/block.c`: + +``` +N blocks of the following: + + read 64 bits: sector number and flags + (blk->sector << BDRV_SECTOR_BITS) | flags + + if flags & BLK_MIG_FLAG_EOS: + break + if flags & BLK_MIG_FLAG_PROGRESS + continue + if flags & BLK_MIG_FLAG_DEVICE_BLOCK + byte: name length + length bytes: device name string + if not flags & BLK_MIG_FLAG_ZERO_BLOCK: + read (1 << 20) bytes +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/146 b/gitlab/issues_text/target_missing/host_missing/accel_missing/146 new file mode 100644 index 000000000..052c97f56 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/146 @@ -0,0 +1 @@ +macOS Guest Reading USB 3.0 Bus as USB 2.0 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1460 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1460 new file mode 100644 index 000000000..fe07e0d50 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1460 @@ -0,0 +1,5 @@ +block_load fails if last block is included in snapshot and block device isn't multiple of BLK_MIG_BLOCK_SIZE +Description of problem: +The `block_load` function in `migration/block.c` has a bug where `blk_pwrite` or `blk_pwrite_zeroes` always write `cluster_size` bytes. If the underlying device is not a multiple of `BLK_MIG_BLOCK_SIZE`, the write will fail with -EIO when trying to write past the end of the device, as `blk_check_byte_request` checks the length of the device. + +This can be fixed by ensuring that `cur_addr` + write length passed to `blk_pwrite`/`blk_pwrite_zeroes` never exceeds the total length of the block device. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1461 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1461 new file mode 100644 index 000000000..461178478 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1461 @@ -0,0 +1 @@ +Virgl on Upstream windows builds? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1463 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1463 new file mode 100644 index 000000000..89f7ce3b1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1463 @@ -0,0 +1,41 @@ +VM with ivshmem and host pci device does not boot +Description of problem: +The boot aborts early if ivshmem and host-pci devices are used at the same time. +Steps to reproduce: +1. use a recent host kernel => 6.1.8 +2. use qemu from bullseye-backports (7.2) +3. use a recent edk2 bios with 4M secure boot + SMM +4. add ivshmem with e.g.: -chardev socket,path=/tmp/shared_mem,id=shared_mem -device ivshmem-doorbell,chardev=shared_mem,vectors=1 +5. add a host-pci device to the VM +6. try to boot he VM +Additional information: +Observations: +always add ivshmem with: -chardev socket,path=/tmp/shared_mem,id=shared_mem -device ivshmem-doorbell,chardev=shared_mem,vectors=1 +- a) no host-pci device + edk2 with secure boot => works +- b) with host-pci device + non edk2 => works +- c) with host-pci device + edk2 with secure boot => does not work +- d) with host-pci device + edk2 with secure boot + but without ivshmem => works + + +I have compiled a debug version of qemu und added some prints to the linux kernel. + +Qemu log shows: +``` +2023-01-25T23:30:47.128716Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument +2023-01-25T23:30:47.128741Z qemu-system-x86_64: vfio_dma_map(0x55cee4bf7b20, 0x385000000000, 0x2000000, 0x7fd7253ff000) = -2 (No such file or directory) +qemu: hardware error: vfio: DMA mapping failed, unable to continue +``` + +Kernel log prints in vfio_iommu_iova_dma_valid@drivers/vfio/vfio_iommu_type1.c - if (start >= node->start && end <= node->end): +``` +[ 1156.241294] DEBUG valid 1048576 >= 0 && 2147483647 <= 4276092927 +[ 1156.269472] DEBUG valid 1048576 >= 0 && 2130706431 <= 4276092927 +[ 1156.477577] DEBUG valid 3221225472 >= 0 && 3229614079 <= 4276092927 +[ 1156.478889] DEBUG valid 3254779904 >= 0 && 3254845439 <= 4276092927 +[ 1156.481226] DEBUG valid 3254779904 >= 0 && 3255042047 <= 4276092927 +[ 1156.482864] DEBUG valid 3221225472 >= 0 && 3229614079 <= 4276092927 +[ 1156.502867] DEBUG valid 61916248539136 >= 0 && 61916282093567 <= 4276092927 +[ 1156.502870] DEBUG valid 61916248539136 >= 4277141504 && 61916282093567 <= 549755813887 +``` + +The vfio_dma_map ioctl request from qemu to the kernel seems to fail because 0x385000000000 from qemu is not in any iova range known by the kernel. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1464 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1464 new file mode 100644 index 000000000..c2dafd10e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1464 @@ -0,0 +1,3 @@ +qemu-img resize fails due to inconsistent bitmap(s) +Additional information: +This is on a oVirt env diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1465 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1465 new file mode 100644 index 000000000..02ee7049e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1465 @@ -0,0 +1 @@ +MBR/Partition table corruption/loss , probably related to virtual sata disks and backup diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1466 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1466 new file mode 100644 index 000000000..3d15787ef --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1466 @@ -0,0 +1,7 @@ +GTK: mouse position incorrect in HiDPI environment +Description of problem: +With `usb-tablet` mode the guest cursor position should be consistent with the host cursor since QEMU can position the mouse absolutely. +The guest position is off from the host cursor position, it seems the position is not being divided by the scaling factor before it is passed on to the guest. +Steps to reproduce: +1. Run any guest with a graphical interface (e.g. Fedora Workstation or Windows 10) +2. Notice how the guest mouse is not consistent with the host mouse at all diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1467 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1467 new file mode 100644 index 000000000..7481f23f8 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1467 @@ -0,0 +1 @@ +guest agent file filtering diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1468 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1468 new file mode 100644 index 000000000..342b9d951 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1468 @@ -0,0 +1,6 @@ +qemu hangs on white windows when connecting to virtual port using -serial option when using Windows OS +Description of problem: +I was trying to connect windbg with a qemu vm. +First I try using named pipes but all the tutorials I found online result in the qemu windows not even showing. So I give up and trying to use virtual COMs to connect the qemu machine with windbg over serial port. So I created using professional Virtual come driver a link between COM2 and COM4. Now I run qemu with -serial COM2 and I do not run windbg than it run correctly and no problem is present. As soon as I run windbg qemu hangs at startup just after the main window is created. The qemu window remains white and windows shows the normal "The application is not responding". It's like the program is in a infinite loop situation. +Also I noted that If I run qemu and not windbg as soon as the other COM port is connected qemu would stop working and remain frozed. Again showing the "The application is not responding". +If instead of qemu I use other "commercial" software with the same setup (of course there I could use named pipes anyway) I can connect windbg with the machine and do the debug session. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1469 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1469 new file mode 100644 index 000000000..f7f2b8855 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1469 @@ -0,0 +1,48 @@ +QEMU 7.2.0 - make install fail +Description of problem: +`[10055/10057] Generating docs/QEMU manual with a custom command +[10056/10057] Generating docs/QEMU man pages with a custom command +[10056/10057] Installing files. +Traceback (most recent call last): + File "/home/clive/.local/bin/meson", line 5, in <module> + from mesonbuild.mesonmain import main +ModuleNotFoundError: No module named 'mesonbuild' +FAILED: meson-internal__install +/home/clive/.local/bin/meson install --no-rebuild +ninja: build stopped: subcommand failed. +make: *** [Makefile:165: run-ninja] Error 1 +[clive@localhost build]$ +` +Steps to reproduce: +1. as user in shell +2. `wget https://download.qemu.org/qemu-7.2.0.tar.xz` +2. `tar xvJf qemu-7.2.0.tar.xz` +3. `cd qemu-7.2.0` +4. `./configure` +5. `make install` +Additional information: +installed meson via `pip3 --user` + +`pip3 --list` **Output** `meson version 1.0.0` + +**Using** - python version 3.11.1 + +`ninja-build` installed via package manager `dnf` + +**Using** - ninja-build version 1.8.2 + +Used `dnf builddep` on `ninja-build`, `meson`, and `qemu-kvm` before and after installation confirming I have dependencies. + + File "/home/clive/.local/bin/meson" contains +``` +#!/usr/local/bin/python3.11 +# -*- coding: utf-8 -*- +import re +import sys +from mesonbuild.mesonmain import main +if __name__ == '__main__': + sys.argv[0] = re.sub(r'(-script\.pyw|\.exe)?$', '', sys.argv[0]) + sys.exit(main()) + + +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/147 b/gitlab/issues_text/target_missing/host_missing/accel_missing/147 new file mode 100644 index 000000000..74677b797 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/147 @@ -0,0 +1 @@ +Interacting with NetBSD serial console boot blocks no longer works diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1470 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1470 new file mode 100644 index 000000000..675b1dace --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1470 @@ -0,0 +1,9 @@ +Mouse cursor disappeared for WfW 3.11 +Description of problem: +I've been using the "GD5434 v1.25f, 1280x1024x64K Smlfnt" driver (from sp2904.exe, https://archive.org/download/Windows-3.1-WING-doom inside cirrus.zip) with Fedora's qemu build for years, which is the best version of that driver that I could find, and which works quite nicely apart from a font problem right after startup, and is a lot faster than the standard (patched) SVGA driver. Opening and closing File Manager will get rid of the font corruption. After an upgrade to Fedora 37, I noticed that the mouse cursor was not displayed anymore, which I bisected to this git commit: cb8962c146 +Steps to reproduce: +1. Run the image (boots right into Windows) +2. Note the missing cursor +3. +Additional information: +Image for easy testing (IBM DOS 5, 1024x768) is here: https://drive.google.com/file/d/1_5-gGXEahPOPvgG436WbKM9dnOr7Z8zo/view?usp=sharing (4.4 MB) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1474 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1474 new file mode 100644 index 000000000..8949d1e4e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1474 @@ -0,0 +1,8 @@ +qemu stuck at creating vm when enabling sgx feature +Description of problem: +After execute the command line, qemu stucked. + + + + +After the info in the png, qemu clear the screen and then nothing happend. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1475 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1475 new file mode 100644 index 000000000..9e5b4268e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1475 @@ -0,0 +1,14 @@ +qemu-img: GLib: g_hash_table_foreach_remove: assertion 'hash_table != NULL' failed +Description of problem: +Mixing driver=https with an http URL gives this assert fail in glib2: + +``` +$ ~/d/qemu/build/qemu-img convert -p -W -f qcow2 'json:{ "file.readahead": 67108864, "file.driver": "https", "file.url": "http://web/tmp/jammy-server-cloudimg-amd64.qcow2", "file.timeout":2000 }' -O raw jammy-server-cloudimg-amd64.img.raw +qemu-img: GLib: g_hash_table_foreach_remove: assertion 'hash_table != NULL' failed +qemu-img: GLib: g_hash_table_destroy: assertion 'hash_table != NULL' failed +qemu-img: Could not open 'json:{ "file.readahead": 67108864, "file.driver": "https", "file.url": "http://web/tmp/jammy-server-cloudimg-amd64.qcow2", "file.timeout":2000 }': https curl driver cannot handle the URL 'http://oirase.annexia.org/tmp/jammy-server-cloudimg-amd64.qcow2' (does not start with 'https://') +``` + +(It seems to be a warning rather than a crash) +Steps to reproduce: +1. Run the command above. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1477 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1477 new file mode 100644 index 000000000..e5c65e3a9 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1477 @@ -0,0 +1,291 @@ +hot-plugged interface are not working after live migration +Description of problem: +After a live migration are perform for a vm then hot-plug interface pci didn't show up, but did found a SCSI storage controller is created. I checked libvirt did send qmp command to qemu `[pid 320011] 1673945683.378537 write(42, "{"execute":"device_add","arguments":{"driver":"virtio-net-pci","netdev":"hostua-test","id":"ua-test","mac":"00:e0:4c:6a:3b:51","bus":"pci.7","addr":"0x0"},"id":"libvirt-200"}rn", 176) = 176 +` +Steps to reproduce: +1. Perform a live migration by issue command `virsh migrate --live --persistent --verbose --unsafe --p2p demo-vm qemu+tls://node8/system?pkipath=/etc/pki/libvirt/private/` +2. Then on the destination node that vm moved, create a bridge deivce `ip link add br-test1 type bridge` +3. Create a tap.xml file with following code + ``` + <interface type='bridge'> + <mac address='00:e0:4c:6a:3b:51'/> + <source bridge='br-test1'/> + <model type="virtio"/> + <alias name='ua-test'/> + </interface> + ``` +4. Save origin pci information +``` +$ virsh console demo-vm +# Save origin pci information +[root@demo-vm ~]# lshw > before +``` +5. Hot-plug an interface `virsh attach-device demo-vm tap.xml-backup --live --config` +6. Dumpxml of demo-vm +``` +<domain type='kvm' id='226'> + <name>demo-vm</name> + <uuid>cc74b867-3fb4-5e4f-bbce-33df21a89416</uuid> + <metadata> + <kubevirt xmlns="http://kubevirt.io"> + <uid>79db3d82-ce8f-44e8-96a5-940cc37c0064</uid> + <graceperiod> + <deletionGracePeriodSeconds>30</deletionGracePeriodSeconds> + </graceperiod> + </kubevirt> + </metadata> + <maxMemory slots='16' unit='KiB'>134217728</maxMemory> + <memory unit='KiB'>1048576</memory> + <currentMemory unit='KiB'>1048576</currentMemory> + <vcpu placement='static' current='1'>128</vcpu> + <iothreads>1</iothreads> + <resource> + <partition>/machine</partition> + </resource> + <sysinfo type='smbios'> + <system> + <entry name='uuid'>cc74b867-3fb4-5e4f-bbce-33df21a89416</entry> + </system> + </sysinfo> + <os> + <type arch='x86_64' machine='pc-q35-rhel8.6.0'>hvm</type> + <smbios mode='sysinfo'/> + </os> + <features> + <acpi/> + </features> + <cpu mode='custom' match='exact' check='full'> + <model fallback='forbid'>Skylake-Server-IBRS</model> + <vendor>Intel</vendor> + <topology sockets='128' dies='1' cores='1' threads='1'/> + <feature policy='require' name='ss'/> + <feature policy='require' name='vmx'/> + <feature policy='require' name='pdcm'/> + <feature policy='require' name='hypervisor'/> + <feature policy='require' name='tsc_adjust'/> + <feature policy='require' name='clflushopt'/> + <feature policy='require' name='umip'/> + <feature policy='require' name='pku'/> + <feature policy='require' name='md-clear'/> + <feature policy='require' name='stibp'/> + <feature policy='require' name='arch-capabilities'/> + <feature policy='require' name='ssbd'/> + <feature policy='require' name='xsaves'/> + <feature policy='require' name='ibpb'/> + <feature policy='require' name='ibrs'/> + <feature policy='require' name='amd-stibp'/> + <feature policy='require' name='amd-ssbd'/> + <feature policy='require' name='skip-l1dfl-vmentry'/> + <feature policy='require' name='pschange-mc-no'/> + <feature policy='disable' name='mpx'/> + <numa> + <cell id='0' cpus='0-127' memory='1048576' unit='KiB'/> + </numa> + </cpu> + <clock offset='utc'/> + <on_poweroff>destroy</on_poweroff> + <on_reboot>restart</on_reboot> + <on_crash>destroy</on_crash> + <devices> + <emulator>/usr/libexec/qemu-kvm</emulator> + <disk type='network' device='disk' model='virtio-non-transitional'> + <driver name='qemu' type='raw' error_policy='stop' discard='unmap'/> + <auth username='rbd-provisioner'> + <secret type='ceph' uuid='8fedf300-282c-4531-a66d-ca2691aaa88b'/> + </auth> + <source protocol='rbd' name='demo-pool/vol-5e83bed9-a2a3-11ed-bee4-3cfdfee07278' index='2'> + <host name='xx.xx.xx.xx' port='6789'/> + <host name='xx.xx.xx.xx' port='6789'/> + <host name='xx.xx.xx.xx' port='6789'/> + </source> + <target dev='vda' bus='virtio'/> + <boot order='1'/> + <alias name='ua-bootdisk'/> + <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> + </disk> + <disk type='file' device='disk' model='virtio-non-transitional'> + <driver name='qemu' type='raw' cache='writethrough' error_policy='stop' discard='unmap'/> + <source file='/var/run/kubevirt-ephemeral-disks/cloud-init-data/demo-vm/configdrive.iso' index='1'/> + <backingStore/> + <target dev='vdb' bus='virtio'/> + <alias name='ua-cloudinitdisk'/> + <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> + </disk> + <controller type='usb' index='0' model='none'> + <alias name='usb'/> + </controller> + <controller type='scsi' index='0' model='virtio-non-transitional'> + <alias name='scsi0'/> + <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> + </controller> + <controller type='virtio-serial' index='0' model='virtio-non-transitional'> + <alias name='virtio-serial0'/> + <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> + </controller> + <controller type='pci' index='0' model='pcie-root'> + <alias name='pcie.0'/> + </controller> + <controller type='pci' index='1' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='1' port='0x10'/> + <alias name='pci.1'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> + </controller> + <controller type='pci' index='2' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='2' port='0x11'/> + <alias name='pci.2'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> + </controller> + <controller type='pci' index='3' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='3' port='0x12'/> + <alias name='pci.3'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> + </controller> + <controller type='pci' index='4' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='4' port='0x13'/> + <alias name='pci.4'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> + </controller> + <controller type='pci' index='5' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='5' port='0x14'/> + <alias name='pci.5'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> + </controller> + <controller type='pci' index='6' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='6' port='0x15'/> + <alias name='pci.6'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x5'/> + </controller> + <controller type='pci' index='7' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='7' port='0x16'/> + <alias name='pci.7'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x6'/> + </controller> + <controller type='pci' index='8' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='8' port='0x18'/> + <alias name='pci.8'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0' multifunction='on'/> + </controller> + <controller type='pci' index='9' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='9' port='0x19'/> + <alias name='pci.9'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x1'/> + </controller> + <controller type='pci' index='10' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='10' port='0x1a'/> + <alias name='pci.10'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x2'/> + </controller> + <controller type='pci' index='11' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='11' port='0x1b'/> + <alias name='pci.11'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x3'/> + </controller> + <controller type='pci' index='12' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='12' port='0x1c'/> + <alias name='pci.12'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x4'/> + </controller> + <controller type='sata' index='0'> + <alias name='ide'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> + </controller> + <interface type='ethernet'> + <mac address='00:00:00:6a:d3:bc'/> + <target dev='e6250550b78a43a' managed='yes'/> + <model type='virtio'/> + <mtu size='1500'/> + <alias name='ua-attachnet1'/> + <rom enabled='no'/> + <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> + </interface> + <interface type='bridge'> + <mac address='00:e0:4c:6a:3b:51'/> + <source bridge='br-test1'/> + <target dev='vnet5'/> + <model type='virtio'/> + <alias name='ua-test'/> + <address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> + </interface> + <serial type='pty'> + <source path='/dev/pts/31'/> + <log file='/var/log/vm/79db3d82-ce8f-44e8-96a5-940cc37c0064/console.log' append='off'/> + <target type='isa-serial' port='0'> + <model name='isa-serial'/> + </target> + <alias name='serial0'/> + </serial> + <console type='pty' tty='/dev/pts/31'> + <source path='/dev/pts/31'/> + <log file='/var/log/vm/79db3d82-ce8f-44e8-96a5-940cc37c0064/console.log' append='off'/> + <target type='serial' port='0'/> + <alias name='serial0'/> + </console> + <channel type='unix'> + <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-226-demo-vm/org.qemu.guest_agent.0'/> + <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/> + <alias name='channel0'/> + <address type='virtio-serial' controller='0' bus='0' port='1'/> + </channel> + <input type='mouse' bus='ps2'> + <alias name='input0'/> + </input> + <input type='keyboard' bus='ps2'> + <alias name='input1'/> + </input> + <graphics type='vnc' port='5920' autoport='yes' listen='0.0.0.0'> + <listen type='address' address='0.0.0.0'/> + </graphics> + <audio id='1' type='none'/> + <video> + <model type='vga' vram='16384' heads='1' primary='yes'/> + <alias name='video0'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> + </video> + <memballoon model='virtio-non-transitional'> + <alias name='balloon0'/> + <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> + </memballoon> + </devices> + <seclabel type='dynamic' model='dac' relabel='yes'> + <label>+107:+107</label> + <imagelabel>+107:+107</imagelabel> + </seclabel> +</domain> +``` +7. Console to vm and check pci +``` +$ virsh console demo-vm +# no additional nic found in `ip a` list +[root@demo-vm ~]# ip a +# Compare pci +[root@demo-vm ~]# lshw > after +# instead of a virtio network pci i saw a virtio SCSI is created +[root@demo-vm ~]# diff before after +# output + *-scsi + description: SCSI storage controller + product: Virtio SCSI + vendor: Red Hat, Inc. + physical id: 0 + bus info: pci@0000:02:00.0 + version: 01 + width: 64 bits + clock: 33MHz + capabilities: scsi msix pm pciexpress bus_master cap_list + configuration: driver=virtio-pci latency=0 + resources: irq:22 memory:fe600000-fe600fff memory:fc400000-fc403fff +``` +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1479 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1479 new file mode 100644 index 000000000..f12e11fac --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1479 @@ -0,0 +1 @@ +system/arm/cpu-features.html : text describing options is misrendered diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/148 b/gitlab/issues_text/target_missing/host_missing/accel_missing/148 new file mode 100644 index 000000000..3f19dfbd6 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/148 @@ -0,0 +1 @@ +Please solve graceful (ACPI) poweroff issue, using signals, most importantly SIGTERM diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1480 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1480 new file mode 100644 index 000000000..9bdcf4b58 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1480 @@ -0,0 +1 @@ +-cpu <whatever>,help should print the options available for that CPU type diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1481 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1481 new file mode 100644 index 000000000..1a2e4cd35 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1481 @@ -0,0 +1 @@ +How to create Rootfs for sifive_u machine diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1482 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1482 new file mode 100644 index 000000000..31b71581e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1482 @@ -0,0 +1,15 @@ +Network failed in qemu-7.2.0 +Description of problem: +After I created and installed Ubuntu 20.04 img in qemu virtual machine from Ubuntu 20.04 iso, I found that the network could not work normally, the network settings wasn't right yet. +Steps to reproduce: +1. Download the source code of qemu-7.2.0 using command "wget https://download.qemu.org/qemu-7.2.0.tar.xz"; +2. Untar using command "tar Jxvf qemu-7.2.0.tar.xz"; +3. Configure with command "./configure --target-list=x86_64-softmmu" under root of qemu source code; +4. Build with command "make"; +5. Install with command "make install" or "sudo make install"; +5. Create image with command "qemu-img create -f qcow2 Ubuntu2004.img 40G"; +5. Launch and install guest with ubuntu 20.04 iso using command "qemu-system-x86_64 -enable-kvm -m 8G -smp 4 -boot once=d -cdrom ../iso_images/Ubuntu-20.04.5-desktop-amd.iso -drive file=./Ubuntu2004.img -device ac97"; +6. After system installed, launch guest with command "qemu-system-x86_64 -enable-kvm -m 8G -smp 4 -drive file=./Ubuntu2004.img -device ac97" +Additional information: +1. When I used qemu version 7.1.0, that is qemu-7.1.0, and go through the same steps above, then the network worked normally, and the network setting was right. +2. Windows images from Windows iso(s) had the same phenomenon. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1483 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1483 new file mode 100644 index 000000000..03b47749e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1483 @@ -0,0 +1 @@ +Failed to mount pmem device in qemu diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1485 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1485 new file mode 100644 index 000000000..0da0412af --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1485 @@ -0,0 +1,12 @@ +hw/at24c : not support 1 byte-address with eeprom size less than 256 byte +Description of problem: +I created the new platform base on aspeed/fuji, +that uses the virtual eeprom (at24c), some eeprom used 24c02, which size 256 bytes. +but when using /hw/at24c.c, the result will not same the real device. +Steps to reproduce: +1. create a machine with EEPROM size less then or equal 256 bytes +2. start the qemu +3. use i2cget/i2cset/i2cdump to write and display eeprom data +Additional information: +I fixed and validated, refer +https://gitlab.com/ssinprem/qemu/-/tree/at24c-1-byte-address-mode diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1486 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1486 new file mode 100644 index 000000000..7d85ff5fa --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1486 @@ -0,0 +1,89 @@ +LXD fails to create VM with QEMU 7.2.0: "../../net/net.c:1106: net_client_init1: Assertion `nc' failed." +Description of problem: +Beginning with QEMU 7.2.0, LXD is unable to launch virtual machines using the default network profile, which breaks the out-of-box experience if a user wishes to create a virtual machine. This worked correctly with QEMU 7.1.0. + +Multiple users across different Linux distributions are reporting this issue: +- https://discuss.linuxcontainers.org/t/failed-adding-nic-netdev-monitor-is-disconnected/15946 +- https://forums.gentoo.org/viewtopic-p-8774212.html +- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030365 + +``` +gibmat@tharkun:~$ lxc launch images:debian/sid debian-sid-vm --vm +Creating debian-sid-vm +Starting debian-sid-vm +Error: Failed setting up device via monitor: Failed setting up device "eth0": Failed adding NIC netdev: Monitor is disconnected +Try `lxc info --show-log local:debian-sid-vm` for more info +gibmat@tharkun:~$ lxc info --show-log local:debian-sid-vm +Name: debian-sid-vm +Status: STOPPED +Type: virtual-machine +Architecture: x86_64 +Created: 2023/02/10 23:47 UTC + +Log: + +warning: tap: open vhost char device failed: Permission denied +warning: tap: open vhost char device failed: Permission denied +qemu-system-x86_64: ../../net/net.c:1106: net_client_init1: Assertion `nc' failed. + +``` + +``` +gibmat@tharkun:~$ qemu-system-x86_64 --version +QEMU emulator version 7.2.0 (Debian 1:7.2+dfsg-2) +Copyright (c) 2003-2022 Fabrice Bellard and the QEMU Project developers +gibmat@tharkun:~$ lxc version +Client version: 5.0.2 +Server version: 5.0.2 +``` +Steps to reproduce: +1. Install LXD and QEMU 7.2.0 +2. `lxc launch images:debian/sid debian-sid-vm --vm` + - This will fail as reported above +3. Downgrade to QEMU 7.1.0 (such as from https://snapshot.debian.org/package/qemu/1%3A7.1%2Bdfsg-2/) +4. `lxc launch images:debian/sid debian-sid-vm --vm` + - Now VM creation is successful + ``` + gibmat@tharkun:~$ lxc launch images:debian/sid debian-sid-vm --vm + Creating debian-sid-vm + Starting debian-sid-vm + gibmat@tharkun:~$ lxc list + +---------------+---------+------+-----------------------------------------------+-----------------+-----------+ + | NAME | STATE | IPV4 | IPV6 | TYPE | SNAPSHOTS | + +---------------+---------+------+-----------------------------------------------+-----------------+-----------+ + | debian-sid-vm | RUNNING | | fd42:ea61:feb4:55ef:216:3eff:feb8:2e8c (eth0) | VIRTUAL-MACHINE | 0 | + +---------------+---------+------+-----------------------------------------------+-----------------+-----------+ + gibmat@tharkun:~$ lxc info --show-log local:debian-sid-vm + Name: debian-sid-vm + Status: RUNNING + Type: virtual-machine + Architecture: x86_64 + PID: 2502 + Created: 2023/02/11 15:08 UTC + Last Used: 2023/02/11 15:08 UTC + + Resources: + Processes: -1 + Network usage: + eth0: + Type: broadcast + State: UP + Host interface: tap5efa7582 + MAC address: 00:16:3e:b8:2e:8c + MTU: 1500 + Bytes received: 3.13kB + Bytes sent: 164B + Packets received: 12 + Packets sent: 2 + IP addresses: + inet6: fd42:ea61:feb4:55ef:216:3eff:feb8:2e8c/64 (global) + + Log: + + warning: tap: open vhost char device failed: Permission denied + warning: tap: open vhost char device failed: Permission denied + + gibmat@tharkun:~$ qemu-system-x86_64 --version + QEMU emulator version 7.1.0 (Debian 1:7.1+dfsg-2+b3) + Copyright (c) 2003-2022 Fabrice Bellard and the QEMU Project developers + ``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1487 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1487 new file mode 100644 index 000000000..c83f01c13 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1487 @@ -0,0 +1,5 @@ +Mac OS X 10.4-10.6 i386/x86_64 not working on Apple Silicon +Description of problem: +Mac OS X panics early in the boot process. There are no issues using later versions of macOS or the PPC architecture +Steps to reproduce: +1. trying to boot 10.4/10.5/10.6 using i368/x86_64 emulation on apple silicon diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1489 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1489 new file mode 100644 index 000000000..96f7d5c53 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1489 @@ -0,0 +1,94 @@ +Breakpoints set at wrong addresses in `test-gdbstub.py` for some Linux kernels guest images +Description of problem: +The script `tests/guest-debug/test-gdbstub.py` for testing QEMU's GDB +stub on Linux kernel guests sets breakpoints on `kernel_init()` and +`wait_for_completion()`. As the script is coded, breakpoints are set +(implicitly) not at the functions' start addresses, but at the end of +the functions' prologues. + +For some Linux kernel builds in which `kernel_init()` and +`wait_for_completion()` get compiled with a function prologue, the +script fails to detect breakpoint hits in `check_hbreak()` and +`check_break()` because it compares the stopped address (i.e. the end of +the function's prologue) with the function's start address, and they +differ. To observe the difference in GDB: + +```sh +$ gdb -q --nx vmlinux +Reading symbols from vmlinux... +(gdb) b kernel_init +Breakpoint 1 at 0xffff800008fbeb28: file init/main.c, line 1497. # <- prologue start +(gdb) b *kernel_init +Breakpoint 2 at 0xffff800008fbeb18: file init/main.c, line 1491. # <- function start +``` + +In my tests, the issue doesn't occur with standard Linux kernels builds +(e.g. compiled on Linux hosts with GCC) because typically both +`kernel_init()` and `wait_for_completion()` seem to be without +prologues. +Steps to reproduce: +The issue has so far been encountered only with arm64 Linux kernel +guests compiled on macOS arm64 with +[mac-linux-kdk](https://github.com/GayPizzaSpecifications/mac-linux-kdk). + +1. Compile a recent arm64 Linux kernel on macOS arm64 with debugging + information (first `make defconfig`, then `make menuconfig` and set + `Kernel hacking / Compile-time checks and compiler options / Debug + information / Rely on toolchain's implicit default DWARF version`) + + ```sh + $ file /tmp/linux-5.19/arch/arm64/boot/Image + /tmp/linux-5.19/arch/arm64/boot/Image: Linux kernel ARM64 boot executable Image, little-endian, 4K pages + $ file /tmp/linux-5.19/vmlinux + /tmp/linux-5.19/vmlinux: ELF 64-bit LSB pie executable, ARM aarch64, version 1 (SYSV), statically linked, BuildID[sha1]=bf9e422d48e0aded5859fe34d6de2c174ef3a20b, with debug_info, not stripped + ``` + +2. Start QEMU waiting for GDB to connect: + + ```sh + $ ./qemu-system-aarch64 -smp 1 -M virt -cpu cortex-a57 -kernel /tmp/linux-5.19/arch/arm64/boot/Image -append nokaslr -s -S + ``` + +3. Execute the `test-gdbstub.py` script (as described in the script file + itself): + + ```sh + $ gdb /tmp/linux-5.19/vmlinux -x tests/guest-debug/test-gdbstub.py + ``` + + The script then hangs. + +Tested both on a macOS host and a Linux host. +Additional information: +The proposed fix is to explicitly disable GDB's prologue decoder and set +the two breakpoints at the functions' start addresses [by adding an +asterisk before the function +name](https://stackoverflow.com/a/31451340): + +```diff +diff --git a/tests/guest-debug/test-gdbstub.py b/tests/guest-debug/test-gdbstub.py +index 98a5df4d4..6202d17c3 100644 +--- a/tests/guest-debug/test-gdbstub.py ++++ b/tests/guest-debug/test-gdbstub.py +@@ -31,7 +31,7 @@ def check_step(): + def check_break(sym_name): + "Setup breakpoint, continue and check we stopped." + sym, ok = gdb.lookup_symbol(sym_name) +- bp = gdb.Breakpoint(sym_name) ++ bp = gdb.Breakpoint("*%s" % (sym_name)) + + gdb.execute("c") + +@@ -48,7 +48,7 @@ def check_break(sym_name): + def check_hbreak(sym_name): + "Setup hardware breakpoint, continue and check we stopped." + sym, ok = gdb.lookup_symbol(sym_name) +- gdb.execute("hbreak %s" % (sym_name)) ++ gdb.execute("hbreak *%s" % (sym_name)) + gdb.execute("c") + + # hopefully we came back +``` + +This change shouldn't impact the Linux kernel guests for which the +script is already working as intended. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/149 b/gitlab/issues_text/target_missing/host_missing/accel_missing/149 new file mode 100644 index 000000000..c0a441cb3 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/149 @@ -0,0 +1 @@ +vmxnet3 unable to send IPv6 ESP packets diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1490 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1490 new file mode 100644 index 000000000..052dfe94b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1490 @@ -0,0 +1,61 @@ +Keystrokes for F13-24 are not forwarded by an evdev input device +Description of problem: +Currently, keystrokes for F13-F24 are not forwarded by an evdev input device. +Steps to reproduce: +``` +/usr/bin/qemu-system-x86_64 \ +-name guest=win10,debug-threads=on \ +-S \ +-object '{"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-11-win10/master-key.aes"}' \ +-machine pc-q35-7.2,usb=off,vmport=off,dump-guest-core=off,memory-backend=pc.ram \ +-accel kvm \ +-cpu host,migratable=on,hv-time=on,hv-relaxed=on,hv-vapic=on,hv-spinlocks=0x1fff \ +-m 4096 \ +-object '{"qom-type":"memory-backend-ram","id":"pc.ram","size":4294967296}' \ +-overcommit mem-lock=off \ +-smp 4,sockets=1,dies=1,cores=4,threads=1 \ +-uuid ca2e9d01-6e02-4aa7-9feb-7846499f7d8a \ +-no-user-config \ +-nodefaults \ +-chardev socket,id=charmonitor,fd=33,server=on,wait=off \ +-mon chardev=charmonitor,id=monitor,mode=control \ +-rtc base=localtime,driftfix=slew \ +-global kvm-pit.lost_tick_policy=delay \ +-no-hpet \ +-no-shutdown \ +-global ICH9-LPC.disable_s3=1 \ +-global ICH9-LPC.disable_s4=1 \ +-boot strict=on \ +-device '{"driver":"pcie-root-port","port":16,"chassis":1,"id":"pci.1","bus":"pcie.0","multifunction":true,"addr":"0x2"}' \ +-device '{"driver":"pcie-root-port","port":17,"chassis":2,"id":"pci.2","bus":"pcie.0","addr":"0x2.0x1"}' \ +-device '{"driver":"pcie-root-port","port":18,"chassis":3,"id":"pci.3","bus":"pcie.0","addr":"0x2.0x2"}' \ +-device '{"driver":"pcie-root-port","port":19,"chassis":4,"id":"pci.4","bus":"pcie.0","addr":"0x2.0x3"}' \ +-device '{"driver":"pcie-root-port","port":20,"chassis":5,"id":"pci.5","bus":"pcie.0","addr":"0x2.0x4"}' \ +-device '{"driver":"pcie-root-port","port":21,"chassis":6,"id":"pci.6","bus":"pcie.0","addr":"0x2.0x5"}' \ +-device '{"driver":"pcie-root-port","port":22,"chassis":7,"id":"pci.7","bus":"pcie.0","addr":"0x2.0x6"}' \ +-device '{"driver":"pcie-root-port","port":23,"chassis":8,"id":"pci.8","bus":"pcie.0","addr":"0x2.0x7"}' \ +-device '{"driver":"pcie-root-port","port":24,"chassis":9,"id":"pci.9","bus":"pcie.0","multifunction":true,"addr":"0x3"}' \ +-device '{"driver":"pcie-root-port","port":25,"chassis":10,"id":"pci.10","bus":"pcie.0","addr":"0x3.0x1"}' \ +-device '{"driver":"pcie-root-port","port":26,"chassis":11,"id":"pci.11","bus":"pcie.0","addr":"0x3.0x2"}' \ +-device '{"driver":"pcie-root-port","port":27,"chassis":12,"id":"pci.12","bus":"pcie.0","addr":"0x3.0x3"}' \ +-device '{"driver":"pcie-root-port","port":28,"chassis":13,"id":"pci.13","bus":"pcie.0","addr":"0x3.0x4"}' \ +-device '{"driver":"pcie-root-port","port":29,"chassis":14,"id":"pci.14","bus":"pcie.0","addr":"0x3.0x5"}' \ +-device '{"driver":"qemu-xhci","id":"usb","bus":"pci.1","addr":"0x0"}' \ +-blockdev '{"driver":"file","filename":"/tmp/win10.qcow2","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' \ +-blockdev '{"node-name":"libvirt-1-format","read-only":false,"driver":"qcow2","file":"libvirt-1-storage","backing":null}' \ +-device '{"driver":"ide-hd","bus":"ide.0","drive":"libvirt-1-format","id":"sata0-0-0","bootindex":2}' \ +-object '{"qom-type":"input-linux","id":"input2","evdev":"/dev/input/by-id/usb-04d9_f50e-event-mouse"}' \ +-object '{"qom-type":"input-linux","id":"input3","evdev":"/dev/input/by-id/usb-0c45_6515-event-kbd","repeat":true,"grab_all":true,"grab-toggle":"scrolllock"}' \ +-audiodev '{"id":"audio1","driver":"spice"}' \ +-spice port=5900,addr=127.0.0.1,disable-ticketing=on,image-compression=off,seamless-migration=on \ +-device '{"driver":"qxl-vga","id":"video0","max_outputs":1,"ram_size":67108864,"vram_size":67108864,"vram64_size_mb":0,"vgamem_mb":16,"bus":"pcie.0","addr":"0x1"}' \ +-device '{"driver":"virtio-balloon-pci","id":"balloon0","bus":"pci.2","addr":"0x0"}' \ +-sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ +-msg timestamp=on +``` + +This is probably not a minimal example, but I didn't know how to generate one. I think the only relevant lines are these: +``` +-object '{"qom-type":"input-linux","id":"input2","evdev":"/dev/input/by-id/usb-04d9_f50e-event-mouse"}' \ +-object '{"qom-type":"input-linux","id":"input3","evdev":"/dev/input/by-id/usb-0c45_6515-event-kbd","repeat":true,"grab_all":true,"grab-toggle":"scrolllock"}' +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1495 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1495 new file mode 100644 index 000000000..1b81ad752 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1495 @@ -0,0 +1,6 @@ +MacOS fails check-unit for test-io-channel-command for some reason +Description of problem: +While adding the socat dependency to the CI system it triggers a failure on the ARM MacOS build, eg: https://gitlab.com/stsquad/qemu/-/jobs/3769189709 +Steps to reproduce: +1. install socat +2. make check-unit diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1496 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1496 new file mode 100644 index 000000000..231ebb14a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1496 @@ -0,0 +1,27 @@ +Multiple issues detected by the thread sanitizer build +Description of problem: +Switching the tsan build in the CI from benchmark to check-unit revealed a bunch of issues even in our most basic tests. +Steps to reproduce: +1. configure --enable-tsan --cc=clang --cxx=clang++ --enable-trace-backends=ust --enable-fdt=system --disable-slirp +2. make check-unit +3. recoil in horror at the failures +Additional information: +From: https://gitlab.com/stsquad/qemu/-/jobs/3779216892 + +``` +Summary of Failures: +27/95 qemu:unit / rcutorture ERROR 3.83s exit status 66 +28/95 qemu:unit / test-rcu-list ERROR 5.28s exit status 66 +29/95 qemu:unit / test-rcu-simpleq ERROR 5.07s exit status 66 +30/95 qemu:unit / test-rcu-tailq ERROR 5.12s exit status 66 +32/95 qemu:unit / test-rcu-slist ERROR 5.07s exit status 66 +40/95 qemu:unit / test-logging ERROR 2.50s exit status 66 +52/95 qemu:unit / test-aio-multithread ERROR 9.53s exit status 66 +54/95 qemu:unit / test-thread-pool ERROR 7.22s exit status 66 +55/95 qemu:unit / test-bdrv-drain ERROR 2.37s exit status 66 +58/95 qemu:unit / test-blockjob ERROR 2.04s exit status 66 +60/95 qemu:unit / test-block-iothread ERROR 2.08s exit status 66 +74/95 qemu:unit / test-io-channel-command ERROR 0.10s killed by signal 13 SIGPIPE +90/95 qemu:unit / test-replication ERROR 25.03s exit status 66 +93/95 qemu:unit / test-util-filemonitor ERROR 2.61s exit status 66 +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1497 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1497 new file mode 100644 index 000000000..f7acbb541 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1497 @@ -0,0 +1,3 @@ +no documentation on plugins with mem_cb in their name +Additional information: +I'm especially interested in how vector ops under mask report their memory traffic diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1504 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1504 new file mode 100644 index 000000000..b30110f85 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1504 @@ -0,0 +1 @@ +Implement Synopsys DesignWare PCI-I2C adapter model diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1505 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1505 new file mode 100644 index 000000000..774b16862 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1505 @@ -0,0 +1 @@ +guest agent: add --allow-rpcs / whitelist mode diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1507 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1507 new file mode 100644 index 000000000..f2ff75793 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1507 @@ -0,0 +1,37 @@ +export/fuse/fuse.c:fuse_fallocate does not do anything but returns success +Description of problem: +block/export/fuse.c:fuse_fallocate with `FALLOC_FL_PUNCH_HOLE` does not do anything even though it returns 0 (success). A later read incorrectly returns old data instead of zeros. +Should probably return EOPNOTSUPP. + +FALLOC_FL_PUNCH_HOLE: +>Within the specified range, partial filesystem blocks are zeroed, +and whole filesystem blocks are removed from the file. After a +successful call, subsequent reads from this range will return +zeros. +https://man7.org/linux/man-pages/man2/fallocate.2.html +Steps to reproduce: +```sh +touch /tmp/data /tmp/fuse_exp +dd if=/dev/random of=/tmp/data count=1000 bs=1M +qemu-storage-daemon --blockdev node-name=node0,driver=raw,file.driver=file,file.filename=/tmp/data --export type=fuse,id=node0-export,node-name=node0,mountpoint=/tmp/fuse_exp,writable=on + +hexdump /tmp/fuse_exp -n 16 +# 0000000 4d5f db2d 57ab 02f6 f9c2 d2f1 0c1b 4b86 +fallocate -l 1G --punch-hole /tmp/fuse_exp +echo $? +# 0 +hexdump /tmp/fuse_exp -n 16 +# 0000000 4d5f db2d 57ab 02f6 f9c2 d2f1 0c1b 4b86 + + +hexdump /tmp/data -n 16 +# 0000000 4d5f db2d 57ab 02f6 f9c2 d2f1 0c1b 4b86 +fallocate -l 1G --punch-hole /tmp/data +hexdump /tmp/data -n 16 +# 0000000 0000 0000 0000 0000 0000 0000 0000 0000 + +# sudo bpftrace -e 'uretprobe:/usr/bin/qemu-storage-daemon:blk_co_pdiscard { printf("ret=%d\n",retval); }' +# ret=0 +# sudo bpftrace -e 'kretfunc:fuse_file_fallocate { printf("len=%d \t mode=%d ret=%d\n", args->length , args->mode,retval); }' +# len=1073741824 mode=3 ret=0 +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1508 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1508 new file mode 100644 index 000000000..688369c7c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1508 @@ -0,0 +1,91 @@ +vfio-pci 0000:00:02.1: VF token required to access device +Description of problem: +I'm trying to use SR-IOV on an i5-12400 trying to create VFs for my UHD Graphics 730. + +I had to build this DKMS module for it to work: +https://github.com/strongtz/i915-sriov-dkms + +So far I have managed to have 7 VFs created per the dmsg: +``` +[root@fedora ~]# dmesg | grep -i vf +[ 0.000000] Command line: BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.1.13-200.fc37.x86_64 root=UUID=a1ec5891-71c6-44ea-9beb-c4f1cde55c0e ro rootflags=subvol=root rhgb quiet intel_iommu=on iommu=pt split_lock_detect=off i915.enable_guc=7 video=vesafb:off video=efifb:off initcall_blacklist=sysfb_init vfio-pci.disable_vga=1 vfio-pci.enable_sriov=1 vfio-pci.ids=8086:4692,8086:7ad0 +[ 0.074362] Kernel command line: BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.1.13-200.fc37.x86_64 root=UUID=a1ec5891-71c6-44ea-9beb-c4f1cde55c0e ro rootflags=subvol=root rhgb quiet intel_iommu=on iommu=pt split_lock_detect=off i915.enable_guc=7 video=vesafb:off video=efifb:off initcall_blacklist=sysfb_init v +io-pci.disable_vga=1 vfio-pci.enable_sriov=1 vfio-pci.ids=8086:4692,8086:7ad0 +[ 0.288336] pci 0000:00:02.0: VF(n) BAR0 space: [mem 0x60e0000000-0x60e6ffffff 64bit] (contains BAR0 for 7 VFs) +[ 0.288339] pci 0000:00:02.0: VF(n) BAR2 space: [mem 0x6000000000-0x60dfffffff 64bit pref] (contains BAR2 for 7 VFs) +[ 0.293518] pci 0000:01:00.0: VF(n) BAR0 space: [mem 0xa1330000-0xa134ffff 64bit] (contains BAR0 for 8 VFs) +[ 0.336464] VFS: Disk quotas dquot_6.6.0 +[ 0.336470] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes) +[ 1.028560] VFIO - User Level meta-driver version: 0.3 +[ 1.039931] vfio-pci 0000:00:02.0: vgaarb: deactivate vga console +[ 1.039933] vfio-pci 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem +[ 1.040007] vfio_pci: add [8086:4692[ffffffff:ffffffff]] class 0x000000/00000000 +[ 1.040140] vfio_pci: add [8086:7ad0[ffffffff:ffffffff]] class 0x000000/00000000 +[ 3.373977] RAPL PMU: API unit is 2^-32 Joules, 3 fixed counters, 655360 ms ovfl timer +[ 45.696323] vfio-pci 0000:00:02.0: Captured SR-IOV VF 0000:00:02.1 driver_override +[ 45.696356] vfio-pci 0000:00:02.1: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none +[ 45.696598] vfio-pci 0000:00:02.0: Captured SR-IOV VF 0000:00:02.2 driver_override +[ 45.696609] vfio-pci 0000:00:02.2: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none +[ 45.696724] vfio-pci 0000:00:02.0: Captured SR-IOV VF 0000:00:02.3 driver_override +[ 45.696734] vfio-pci 0000:00:02.3: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none +[ 45.696811] vfio-pci 0000:00:02.0: Captured SR-IOV VF 0000:00:02.4 driver_override +[ 45.696825] vfio-pci 0000:00:02.4: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none +[ 45.696947] vfio-pci 0000:00:02.0: Captured SR-IOV VF 0000:00:02.5 driver_override +[ 45.696958] vfio-pci 0000:00:02.5: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none +[ 45.697050] vfio-pci 0000:00:02.0: Captured SR-IOV VF 0000:00:02.6 driver_override +[ 45.697060] vfio-pci 0000:00:02.6: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none +[ 45.697127] vfio-pci 0000:00:02.0: Captured SR-IOV VF 0000:00:02.7 driver_override +[ 45.697137] vfio-pci 0000:00:02.7: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none +``` +I've blacklisted these modules: +``` +blacklist igb +blacklist i915 +blacklist snd_hda_intel +blacklist snd_sof_pci_intel_tgl +``` +And loaded these modules: +``` +vfio +vfio-pci +vfio_virqfd +vfio_iommu_type1 +``` +Kernel args: +``` +GRUB_CMDLINE_LINUX="rhgb quiet intel_iommu=on iommu=pt split_lock_detect=off i915.enable_guc=7 video=vesafb:off video=efifb:off initcall_blacklist=sysfb_init vfio-pci.disable_vga=1 vfio-pci.enable_sriov=1 vfio-pci.ids=8086:4692,8086:7ad0" +``` + +**Error shown:** +``` +[root@fedora ~]# ./test.sh +QEMU 7.0.0 monitor - type 'help' for more information +(qemu) qemu-system-x86_64: -device vfio-pci,host=0000:02.2,multifunction=on,bus=pcie.1,addr=0x00,x-vga=on: vfio 0000:00:02.2: error getting device from group 14: Permission denied +Verify all devices in group 14 are bound to vfio-<bus> or pci-stub and not already in use +``` +**DMESG shows:** +``` +[ 2160.408395] vfio-pci 0000:00:02.2: VF token required to access device +``` + +This lead me to this conversation / thread: + +https://inbox.dpdk.org/dev/CALBAE1MrEoCc8Ch6MNUNTsOcZyJnhr+z+iD0VWjHagQsEdBWCw@mail.gmail.com/#t + +Quote: "Something needs to be sorted with the QEMU community." + +In fact, something needs to be sorted. **It seems there's no way to specify this VF token anywhere from the CLI args**, so I'm reporting this as a bug (or feature not developed yet?? any ETA?) + +**Additional information:** It seems that QEMU might require a patch or a change to allow this VF token to be passed through. It seems that DPDK and other similar projects have already implemented this (it seems Linux has it since Kernel 5.7 - Maybe I'm missing something to pass this token with QEMU considering how old that kernel is? I'd expect this flag to be here in QEMU already) + +**Useful code / info:** +* https://patches.dpdk.org/project/dpdk/patch/20200529013710.72302-3-haiyue.wang@intel.com/ +* https://github.com/intel/pf-bb-config/blob/master/README.md#usage-example +* https://support.hpe.com/hpesc/public/docDisplay?docId=sd00001790en_us&docLocale=en_US&page=GUID-1D5D76F8-522A-47F5-922B-142BD5177033.html + +Thanks, + +-Alemar +Steps to reproduce: +1. See description +2. Run QEMU as described diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/151 b/gitlab/issues_text/target_missing/host_missing/accel_missing/151 new file mode 100644 index 000000000..55700434d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/151 @@ -0,0 +1 @@ +virtio-net ignores the absence of the VIRTIO_NET_F_CTRL_VQ feature bit diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1510 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1510 new file mode 100644 index 000000000..f8ec39381 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1510 @@ -0,0 +1,92 @@ +LibFuzzer: Deadly Signals +Description of problem: +``` +INFO: libFuzzer ignores flags that start with '--' +INFO: Running with entropic power schedule (0xFF, 100). +INFO: Seed: 1075449567 +INFO: Loaded 1 modules (323687 inline 8-bit counters): 323687 [0x558e9ece6000, 0x558e9ed35067), +INFO: Loaded 1 PC tables (323687 PCs): 323687 [0x558e9e7f5680,0x558e9ece5cf0), +./qemu-fuzz-i386: Running 1 inputs 1 time(s) each. +Running: crash-11075f8b34e355e114f92367a5e8b9bbb36a352d +Matching objects by name *usb* +Matching objects by name *ohci* +This process will try to fuzz the following MemoryRegions: + * bus master container[0] (size 0xffffffffffffffff) + * ohci[0] (size 0x100) + * bus master[0] (size 0xffffffffffffffff) +qemu-fuzz-i386: ../hw/usb/core.c:744: struct USBEndpoint *usb_ep_get(USBDevice *, int, int): Assertion `pid == USB_TOKEN_IN || pid == USB_TOKEN_OUT' failed. +==1763255== ERROR: libFuzzer: deadly signal + #0 0x558e9ad46cb1 in __sanitizer_print_stack_trace (/home/hyper/qemu/build/qemu-fuzz-i386+0x1f71cb1) (BuildId: 49539853a6c034db6a511d608192f681fdffa439) + #1 0x558e9acb9548 in fuzzer::PrintStackTrace() (/home/hyper/qemu/build/qemu-fuzz-i386+0x1ee4548) (BuildId: 49539853a6c034db6a511d608192f681fdffa439) + #2 0x558e9ac9efc3 in fuzzer::Fuzzer::CrashCallback() (/home/hyper/qemu/build/qemu-fuzz-i386+0x1ec9fc3) (BuildId: 49539853a6c034db6a511d608192f681fdffa439) + #3 0x7faa5444251f (/lib/x86_64-linux-gnu/libc.so.6+0x4251f) (BuildId: 69389d485a9793dbe873f0ea2c93e02efaa9aa3d) + #4 0x7faa54496a7b in __pthread_kill_implementation nptl/./nptl/pthread_kill.c:43:17 + #5 0x7faa54496a7b in __pthread_kill_internal nptl/./nptl/pthread_kill.c:78:10 + #6 0x7faa54496a7b in pthread_kill nptl/./nptl/pthread_kill.c:89:10 + #7 0x7faa54442475 in gsignal signal/../sysdeps/posix/raise.c:26:13 + #8 0x7faa544287f2 in abort stdlib/./stdlib/abort.c:79:7 + #9 0x7faa5442871a in __assert_fail_base assert/./assert/assert.c:92:3 + #10 0x7faa54439e95 in __assert_fail assert/./assert/assert.c:101:3 + #11 0x558e9b6c89d9 in usb_ep_get /home/hyper/qemu/build/../hw/usb/core.c:744:5 + #12 0x558e9b701fa4 in ohci_service_td /home/hyper/qemu/build/../hw/usb/hcd-ohci.c:957:14 + #13 0x558e9b701fa4 in ohci_service_ed_list /home/hyper/qemu/build/../hw/usb/hcd-ohci.c:1122:21 + #14 0x558e9b6fa47b in ohci_frame_boundary /home/hyper/qemu/build/../hw/usb/hcd-ohci.c:1192:9 + #15 0x558e9cbe8b9c in timerlist_run_timers /home/hyper/qemu/build/../util/qemu-timer.c:576:9 + #16 0x558e9c2a9c7d in qtest_clock_warp /home/hyper/qemu/build/../softmmu/qtest.c:358:9 + #17 0x558e9c2a6411 in qtest_process_command /home/hyper/qemu/build/../softmmu/qtest.c:751:9 + #18 0x558e9c2a1f98 in qtest_process_inbuf /home/hyper/qemu/build/../softmmu/qtest.c:802:9 + #19 0x558e9c2a1db3 in qtest_server_inproc_recv /home/hyper/qemu/build/../softmmu/qtest.c:933:9 + #20 0x558e9c932980 in qtest_sendf /home/hyper/qemu/build/../tests/qtest/libqtest.c:600:5 + #21 0x558e9c932a84 in qtest_clock_step_next /home/hyper/qemu/build/../tests/qtest/libqtest.c:955:5 + #22 0x558e9ad86fed in generic_fuzz /home/hyper/qemu/build/../tests/qtest/fuzz/generic_fuzz.c:715:17 + #23 0x558e9ad7aae3 in LLVMFuzzerTestOneInput /home/hyper/qemu/build/../tests/qtest/fuzz/fuzz.c:152:5 + #24 0x558e9aca0553 in fuzzer::Fuzzer::ExecuteCallback(unsigned char const*, unsigned long) (/home/hyper/qemu/build/qemu-fuzz-i386+0x1ecb553) (BuildId: 49539853a6c034db6a511d608192f681fdffa439) + #25 0x558e9ac8a2cf in fuzzer::RunOneTest(fuzzer::Fuzzer*, char const*, unsigned long) (/home/hyper/qemu/build/qemu-fuzz-i386+0x1eb52cf) (BuildId: 49539853a6c034db6a511d608192f681fdffa439) + #26 0x558e9ac90026 in fuzzer::FuzzerDriver(int*, char***, int (*)(unsigned char const*, unsigned long)) (/home/hyper/qemu/build/qemu-fuzz-i386+0x1ebb026) (BuildId: 49539853a6c034db6a511d608192f681fdffa439) + #27 0x558e9acb9e42 in main (/home/hyper/qemu/build/qemu-fuzz-i386+0x1ee4e42) (BuildId: 49539853a6c034db6a511d608192f681fdffa439) + #28 0x7faa54429d8f in __libc_start_call_main csu/../sysdeps/nptl/libc_start_call_main.h:58:16 + #29 0x7faa54429e3f in __libc_start_main csu/../csu/libc-start.c:392:3 + #30 0x558e9ac84b94 in _start (/home/hyper/qemu/build/qemu-fuzz-i386+0x1eafb94) (BuildId: 49539853a6c034db6a511d608192f681fdffa439) + +NOTE: libFuzzer has rudimentary signal handlers. + Combine libFuzzer with AddressSanitizer or similar for better crash reports. +SUMMARY: libFuzzer: deadly signal +qemu-fuzz-i386: ../hw/usb/core.c:744: struct USBEndpoint *usb_ep_get(USBDevice *, int, int): Assertion `pid == USB_TOKEN_IN || pid == USB_TOKEN_OUT' failed. +==1763258== ERROR: libFuzzer: deadly signal + #0 0x558e9ad46cb1 in __sanitizer_print_stack_trace (/home/hyper/qemu/build/qemu-fuzz-i386+0x1f71cb1) (BuildId: 49539853a6c034db6a511d608192f681fdffa439) + #1 0x558e9acb9548 in fuzzer::PrintStackTrace() (/home/hyper/qemu/build/qemu-fuzz-i386+0x1ee4548) (BuildId: 49539853a6c034db6a511d608192f681fdffa439) + #2 0x558e9ac9efc3 in fuzzer::Fuzzer::CrashCallback() (/home/hyper/qemu/build/qemu-fuzz-i386+0x1ec9fc3) (BuildId: 49539853a6c034db6a511d608192f681fdffa439) + #3 0x7faa5444251f (/lib/x86_64-linux-gnu/libc.so.6+0x4251f) (BuildId: 69389d485a9793dbe873f0ea2c93e02efaa9aa3d) + #4 0x7faa54496a7b in __pthread_kill_implementation nptl/./nptl/pthread_kill.c:43:17 + #5 0x7faa54496a7b in __pthread_kill_internal nptl/./nptl/pthread_kill.c:78:10 + #6 0x7faa54496a7b in pthread_kill nptl/./nptl/pthread_kill.c:89:10 + #7 0x7faa54442475 in gsignal signal/../sysdeps/posix/raise.c:26:13 + #8 0x7faa544287f2 in abort stdlib/./stdlib/abort.c:79:7 + #9 0x7faa5442871a in __assert_fail_base assert/./assert/assert.c:92:3 + #10 0x7faa54439e95 in __assert_fail assert/./assert/assert.c:101:3 + #11 0x558e9b6c89d9 in usb_ep_get /home/hyper/qemu/build/../hw/usb/core.c:744:5 + #12 0x558e9b701fa4 in ohci_service_td /home/hyper/qemu/build/../hw/usb/hcd-ohci.c:957:14 + #13 0x558e9b701fa4 in ohci_service_ed_list /home/hyper/qemu/build/../hw/usb/hcd-ohci.c:1122:21 + #14 0x558e9b6fa47b in ohci_frame_boundary /home/hyper/qemu/build/../hw/usb/hcd-ohci.c:1192:9 + #15 0x558e9cbe8b9c in timerlist_run_timers /home/hyper/qemu/build/../util/qemu-timer.c:576:9 + #16 0x558e9c2a9c7d in qtest_clock_warp /home/hyper/qemu/build/../softmmu/qtest.c:358:9 + #17 0x558e9c2a6411 in qtest_process_command /home/hyper/qemu/build/../softmmu/qtest.c:751:9 + #18 0x558e9c2a1f98 in qtest_process_inbuf /home/hyper/qemu/build/../softmmu/qtest.c:802:9 + #19 0x558e9c2a1db3 in qtest_server_inproc_recv /home/hyper/qemu/build/../softmmu/qtest.c:933:9 + #20 0x558e9c932980 in qtest_sendf /home/hyper/qemu/build/../tests/qtest/libqtest.c:600:5 + #21 0x558e9c932a84 in qtest_clock_step_next /home/hyper/qemu/build/../tests/qtest/libqtest.c:955:5 + #22 0x558e9ad86fed in generic_fuzz /home/hyper/qemu/build/../tests/qtest/fuzz/generic_fuzz.c:715:17 + #23 0x558e9ad7aae3 in LLVMFuzzerTestOneInput /home/hyper/qemu/build/../tests/qtest/fuzz/fuzz.c:152:5 + #24 0x558e9aca0553 in fuzzer::Fuzzer::ExecuteCallback(unsigned char const*, unsigned long) (/home/hyper/qemu/build/qemu-fuzz-i386+0x1ecb553) (BuildId: 49539853a6c034db6a511d608192f681fdffa439) + #25 0x558e9aca1175 in fuzzer::Fuzzer::TryDetectingAMemoryLeak(unsigned char const*, unsigned long, bool) (/home/hyper/qemu/build/qemu-fuzz-i386+0x1ecc175) (BuildId: 49539853a6c034db6a511d608192f681fdffa439) + #26 0x558e9ac8a317 in fuzzer::RunOneTest(fuzzer::Fuzzer*, char const*, unsigned long) (/home/hyper/qemu/build/qemu-fuzz-i386+0x1eb5317) (BuildId: 49539853a6c034db6a511d608192f681fdffa439) + #27 0x558e9ac90026 in fuzzer::FuzzerDriver(int*, char***, int (*)(unsigned char const*, unsigned long)) (/home/hyper/qemu/build/qemu-fuzz-i386+0x1ebb026) (BuildId: 49539853a6c034db6a511d608192f681fdffa439) + #28 0x558e9acb9e42 in main (/home/hyper/qemu/build/qemu-fuzz-i386+0x1ee4e42) (BuildId: 49539853a6c034db6a511d608192f681fdffa439) + #29 0x7faa54429d8f in __libc_start_call_main csu/../sysdeps/nptl/libc_start_call_main.h:58:16 + #30 0x7faa54429e3f in __libc_start_main csu/../csu/libc-start.c:392:3 + #31 0x558e9ac84b94 in _start (/home/hyper/qemu/build/qemu-fuzz-i386+0x1eafb94) (BuildId: 49539853a6c034db6a511d608192f681fdffa439) +``` +Steps to reproduce: +1. ./qemu-fuzz-i386 --fuzz-target=generic-fuzz-ohci +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1511 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1511 new file mode 100644 index 000000000..9b97d6b6f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1511 @@ -0,0 +1 @@ +Please a CPU model for ABI version for x86_64 i386 according to x86-64 psABI diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1512 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1512 new file mode 100644 index 000000000..4778bb046 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1512 @@ -0,0 +1 @@ +AVX/AVX2 not correcly detected in user mode diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1513 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1513 new file mode 100644 index 000000000..961fa124c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1513 @@ -0,0 +1 @@ +CPU flags should be better documented diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1515 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1515 new file mode 100644 index 000000000..e973926eb --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1515 @@ -0,0 +1,18 @@ +qemu have the way to change the windows sid? +Description of problem: +I want to change the guest of windows sid after clone guest, have the way to change it before new guest start? "virt-sysprep" Seems impossible to do it. Although it can be done manually as follow: + +[change sid in windows system](https://www.heelpbook.net/2019/microsoft-changing-sid-of-cloned-vms/) + +query windows sid: +cmd: whoami /user + + +step: +1.clone a new windows guest vm_new + +2.change the sid of vm_new (step2 I don't know how to do that) + +3.start vm_new + +4.query the vm_new's sid is change diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1516 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1516 new file mode 100644 index 000000000..4e5213df8 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1516 @@ -0,0 +1,39 @@ +QEMU does not reload kernel image on guest reboot (direct kernel boot) +Description of problem: +I am using virtiofs as root filesystem with QEMU direct kernel boot. The kernel is loaded from the guests directory structure that is exported from the host. + +The problem is that QEMU does not reload the kernel image file from disk during a guest reboot. This means it is not possible to update the kernel from inside the guest and do a simple reboot to load it. A full power cycle of the guest is required to load the updated kernel image. +Steps to reproduce: +1. Migrate a Linux guest to virtiofs as root fs. +2. Enable QEMU direct kernel boot and point to guest's kernel in the exported root filesystem. +3. Boot. +4. Update the kernel inside the guest. Overwrite the existing kernel image +5. Issue `reboot` inside the guest. +6. When the guest reboots, the old kernel is still booted, even though the image file was overwritten. +7. Issue `poweroff` inside the guest. +8. Issue `virsh start <guest-vm>` +9. Now the new kernel image is booted. +Additional information: +XML: +``` +<type arch='x86_64' machine='pc-q35-7.0'>hvm</type> + <kernel>/media/vm/libvirt/images/alpine-q/root/boot/vmlinuz-virt</kernel> + <initrd>/media/vm/libvirt/images/alpine-q/root/boot/initramfs-virt</initrd> + <cmdline>rootfstype=virtiofs root=root rw</cmdline> + <boot dev='hd'/> + <bootmenu enable='no'/> + </os> + +... + + <filesystem type='mount' accessmode='passthrough'> + <driver type='virtiofs'/> + <binary path='/usr/libexec/virtiofsd' xattr='on'> + <cache mode='always'/> + <lock posix='on' flock='on'/> + </binary> + <source dir='/media/vm/libvirt/images/alpine-q/root'/> + <target dir='root'/> + <address type='pci' domain='0x0000' bus='0x09' slot='0x00' function='0x0'/> + </filesystem> +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1518 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1518 new file mode 100644 index 000000000..bf9df59b0 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1518 @@ -0,0 +1,90 @@ +qemu tests/unit/test-vmstate crashes in g_tree_foreach +Description of problem: +qemu test suite crashes with the latest Fedora Rawhide. +Downstream issue: https://bugzilla.redhat.com/show_bug.cgi?id=2173639 +Steps to reproduce: +1. Compile and test qemu from source as normal. + +``` +214/658 qemu:unit / test-vmstate ERROR 0.22s killed by signal 11 SIGSEGV +317/658 qemu:qtest+qtest-i386 / qtest-i386/rtl8139-test ERROR 0.28s 2 subtests passed +588/658 qemu:qtest+qtest-x86_64 / qtest-x86_64/rtl8139-test ERROR 0.45s 2 subtests passed +``` + +The stack trace from the test is: + +``` +#0 g_tree_foreach (user_data=0x7fffa23ccbc0, func=0x55a834fe3770 <diff_tree>, + tree=<optimized out>) at ../glib/gtree.c:1132 +#1 g_tree_foreach (tree=<optimized out>, func=0x55a834fe3770 <diff_tree>, + user_data=0x7fffa23ccbc0) at ../glib/gtree.c:1117 +#2 0x000055a834fe382c in compare_trees (tree1=0x55a836723bf0, + tree2=0x55a836723f50, + function=function@entry=0x55a834fe3570 <match_interval_mapping_node>) + at ../tests/unit/test-vmstate.c:1085 +#3 0x000055a834fee265 in diff_domain (d2=0x55a836709310, d1=0x55a836708fd0) + at ../tests/unit/test-vmstate.c:1093 +#4 test_gtree_load_domain () at ../tests/unit/test-vmstate.c:1138 +#5 0x00007f0eef39d32e in test_case_run (tc=0x55a836724150) + at ../glib/gtestutils.c:3108 +#6 g_test_run_suite_internal (suite=suite@entry=0x55a8367056e0, + path=path@entry=0x0) at ../glib/gtestutils.c:3203 +#7 0x00007f0eef39cf03 in g_test_run_suite_internal ( + suite=suite@entry=0x55a836705090, path=path@entry=0x0) + at ../glib/gtestutils.c:3222 +#8 0x00007f0eef39cf03 in g_test_run_suite_internal ( + suite=suite@entry=0x55a8366ff670, path=path@entry=0x0) + at ../glib/gtestutils.c:3222 +#9 0x00007f0eef39cf03 in g_test_run_suite_internal ( + suite=suite@entry=0x55a836700140, path=path@entry=0x0) +#10 0x00007f0eef39d8c2 in g_test_run_suite (suite=0x55a836700140) + at ../glib/gtestutils.c:3302 +#11 0x00007f0eef397c40 in g_test_run () at ../glib/gtestutils.c:2409 +#12 g_test_run () at ../glib/gtestutils.c:2396 +#13 0x000055a834fe2645 in main (argc=<optimized out>, argv=<optimized out>) + at ../tests/unit/test-vmstate.c:1523 +``` + +This can also be reproduced in gdb using a command similar to: + +``` +$ MALLOC_PERTURB_=175 G_TEST_SRCDIR=/home/rjones/d/qemu/tests/unit G_TEST_BUILDDIR=/home/rjones/d/qemu/build/tests/unit gdb --args /home/rjones/d/qemu/build/tests/unit/test-vmstate --tap -k +... +(gdb) run +Thread 1 "test-vmstate" received signal SIGSEGV, Segmentation fault. +g_tree_foreach (user_data=0x7fffffffd3e0, func=0x555555568770 <diff_tree>, tree=<optimized out>) at ../glib/gtree.c:1132 +1132 if ((*func) (node->key, node->value, user_data)) +(gdb) bt +#0 g_tree_foreach (user_data=0x7fffffffd3e0, func=0x555555568770 <diff_tree>, + tree=<optimized out>) at ../glib/gtree.c:1132 +#1 g_tree_foreach (tree=<optimized out>, func=0x555555568770 <diff_tree>, + user_data=0x7fffffffd3e0) at ../glib/gtree.c:1117 +#2 0x000055555556882c in compare_trees (tree1=0x5555555ccdb0, + tree2=0x5555555cd110, + function=function@entry=0x555555568570 <match_interval_mapping_node>) + at ../tests/unit/test-vmstate.c:1085 +#3 0x0000555555573265 in diff_domain (d2=0x5555555b3310, d1=0x5555555b2fd0) + at ../tests/unit/test-vmstate.c:1093 +#4 test_gtree_load_domain () at ../tests/unit/test-vmstate.c:1138 +#5 0x00007ffff7eb132e in test_case_run (tc=0x5555555cd310) + at ../glib/gtestutils.c:3108 +#6 g_test_run_suite_internal (suite=suite@entry=0x5555555af6e0, + path=path@entry=0x0) at ../glib/gtestutils.c:3203 +#7 0x00007ffff7eb0f03 in g_test_run_suite_internal ( + suite=suite@entry=0x5555555af090, path=path@entry=0x0) + at ../glib/gtestutils.c:3222 +#8 0x00007ffff7eb0f03 in g_test_run_suite_internal ( + suite=suite@entry=0x5555555a9670, path=path@entry=0x0) + at ../glib/gtestutils.c:3222 +#9 0x00007ffff7eb0f03 in g_test_run_suite_internal ( + suite=suite@entry=0x5555555aa140, path=path@entry=0x0) + at ../glib/gtestutils.c:3222 +#10 0x00007ffff7eb18c2 in g_test_run_suite (suite=0x5555555aa140) + at ../glib/gtestutils.c:3302 +#11 0x00007ffff7eabc40 in g_test_run () at ../glib/gtestutils.c:2409 +#12 g_test_run () at ../glib/gtestutils.c:2396 +#13 0x0000555555567645 in main (argc=<optimized out>, argv=<optimized out>) + at ../tests/unit/test-vmstate.c:1523 +``` + +Unfortunately so much is "optimized out" that it's hard to tell what's going wrong. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1519 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1519 new file mode 100644 index 000000000..a39907533 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1519 @@ -0,0 +1,12 @@ +audio recording not working on qemu +Description of problem: +QEMU fails to record audio from the guest even when the device options hda-duplex and hda-micro options are used. Tried using the other available audio backends (alsa and sdl) but recording on the guest still fails +Steps to reproduce: +1. run the qemu command line above with any of the available audio backends +2. record audio on the guest +3. arecord -vv -d 5 recordng.wav +4. there's an attempt to record but it hangs +5. play recorded audio, there's no output +6. aplay recordng.wav +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/152 b/gitlab/issues_text/target_missing/host_missing/accel_missing/152 new file mode 100644 index 000000000..1ef0bcb01 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/152 @@ -0,0 +1 @@ +qemu-img compare -m option is missing diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1520 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1520 new file mode 100644 index 000000000..78abbaa68 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1520 @@ -0,0 +1,49 @@ +x86 TCG acceleration running on s390x with -smp > host cpus slowed down by x10 +Description of problem: +This boots up a trivial guest using OVMF, when the conditions below are given it runs ~10x slower. + +I have found this breaking our tests of qemu 7.2 [(which due to Debian adding the offending change as backport is affected)](https://salsa.debian.org/qemu-team/qemu/-/blob/master/debian/patches/master/acpi-cpuhp-fix-guest-visible-maximum-access-size-to-.patch) by runnig an order of magnitude slower. + + +I was tracing it down (insert a long strange trip here) and found that it occurs: +- only with patch dab30fb "acpi: cpuhp: fix guest-visible maximum access size to the legacy reg block" applied + - latest master is still affetced +- only with s390x running emulation of x86 + - emulating x86 on ppc64 didn't show the same behavior +- only with -smp > host cpus + - smp 2 with 1 host cpu => slow + - smp 4 with 2 host cpu => slow + - any case where host cpu >= smp => fast + +On average good cases are on a 2964 s390x machine taking ~5-6 seconds for the good case. +The bad case is close to 60s which is the timeout of the automated tests. + +We all know -smp shouldn't be >host-cpus, and I totally admit that this is the definition of an edge case. +But I do not know what else might be affected and this just happened to be what the test does by default - and a slowdown by x10 seems too much even for edge cases to be just ignored. +And while we could just bump up the timeout (and probably will as an interim workaround) I wanted to file it here for your awareness. +Steps to reproduce: +You can recreate the same by using the commandline above and timing things on your own. + +Or you can use the [autopkgtest of edk2 in Ubuntu](https://git.launchpad.net/ubuntu/+source/edk2/tree/debian/tests/shell.py#n214) which have [shown this](https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/s390x/e/edk2/20230224_094012_c95f4@/log.gz) first. +Additional information: +Only signed OVMF cases are affected, while aavmf and other OVMF are more or less on the same speed. + +``` +1 CPU / 1GB Memory +7.0 7.2 +6.54s 58.32s test_ovmf_ms +6.72s 56.96s test_ovmf_4m_ms +7.54s 55.47s test_ovmf_4m_secboot +7.56s 49.88s test_ovmf_secboot +7.01s 39.79s test_ovmf32_4m_secboot +7.38s 7.43s test_aavmf32 +7.27s 7.30s test_aavmf +7.26s 7.26s test_aavmf_snakeoil +5.83s 5.95s test_ovmf_4m +5.61s 5.81s test_ovmf_q35 +5.51s 5.64s test_ovmf_pc +5.26s 5.42s test_ovmf_snakeoil +``` + +Highlighting @cborntra since it is somewhat s390x related and @mjt0k as the patch is applied as backport in Debian. +I didn't find the handle of Laszlo (Author) to highlight him as well. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1521 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1521 new file mode 100644 index 000000000..cd5e6ccb2 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1521 @@ -0,0 +1 @@ +USB HID not using the keycodemapdb and thus lacking new entries diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1522 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1522 new file mode 100644 index 000000000..1f5bfa899 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1522 @@ -0,0 +1,40 @@ +Floppy controller returns the wrong thing for multitrack reads which span tracks +Description of problem: +I've just discovered that the Minix 1 and 2 operating systems no longer boot on qemu. + +Investigation reveals the following: + +- when Minix reads a 1024-byte block from disk, it issues a two-sector multitrack read to the FDC. +- if the FDC runs out of sectors when it's on head 0, it automatically switches to head 1 (this is correct). +- if the FDC runs out of sectors when it's on head 1, it stops the transfer (which is what is supposed to happen). + +What qemu does for the latter case is that it will automatically seek to the next track and switch to head 0. It then sets the SEEK COMPLETE bit in the status register. Minix sees this but isn't expecting it, because this shouldn't be emitted for reads and writes, and fails thinking it's an error. + +For example, here's the logging for such a transfer: + +``` +FLOPPY: Start transfer at 0 1 4f 11 (2878) +FLOPPY: direction=1 (1024 - 10240) +FLOPPY: copy 512 bytes (1024 0 10240) 0 pos 1 4f (17-0x00000b3e 0x00167c00) +FLOPPY: seek to next sector (1 4f 11 => 2878) <--- reads the last sector of head 1 track 0x4f +FLOPPY: copy 512 bytes (1024 512 10240) 0 pos 1 4f (18-0x00000b3f 0x00167e00) +FLOPPY: seek to next sector (1 4f 12 => 2879) <--- attempt to move to the next sector, which fails +FLOPPY: seek to next track (0 50 01 => 2879) <--- moved to next track, which shouldn't happen +FLOPPY: end transfer 1024 1024 10240 +FLOPPY: transfer status: 00 00 00 (20) <--- status report +``` + +Transfer status 20 is the SEEK COMPLETE bit. For a normal head switch, that should be 04 (with the NOW ON HEAD 1 bit set). + +For reference, see page 5-13 of the uPD765 datasheet here: https://www.cpcwiki.eu/imgs/f/f3/UPD765_Datasheet_OCRed.pdf It says: + +> IF MT is high, a multitrack operation is performed. +> If MT = 1 after finishing read/write operation on side 0, +> FDC will automatically start command searching for sector +> 1 on side 1 +Steps to reproduce: +1. `qemu-system-i386 --fda images/minix-2.0-root-720kB.img` +2. Press = to boot. +3. Observe the 'Unrecoverable Read` errors as the ramdisk is loaded. (The system will still boot, but will then crash if you try to do anything due to a corrupt ramdisk.) + +[minix-2.0-root-720kB.img.bz2](/uploads/77d34db96f353d92cdb2d01928b8fc01/minix-2.0-root-720kB.img.bz2) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1526 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1526 new file mode 100644 index 000000000..d89fa5a74 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1526 @@ -0,0 +1 @@ +hw/vfio/trace-events incorrect format diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1527 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1527 new file mode 100644 index 000000000..81d85c82f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1527 @@ -0,0 +1,3 @@ +-blockdev option missing host_device documenation and command line help support +Additional information: +We recommend -blockdev in the documentation as the preferred way to configure storage backends but the online help isn't useful. We also seem to be missing information for some of the blockdev drivers, for example host_device. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1529 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1529 new file mode 100644 index 000000000..a65829969 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1529 @@ -0,0 +1 @@ +Documentation refers to Windows Hypervisor Platform as wphx instead of whpx diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/153 b/gitlab/issues_text/target_missing/host_missing/accel_missing/153 new file mode 100644 index 000000000..7c0085378 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/153 @@ -0,0 +1 @@ +SLIRP SMB silently fails with MacOS smbd diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1530 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1530 new file mode 100644 index 000000000..8a03a3efe --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1530 @@ -0,0 +1,11 @@ +Problem with sdl,gl=on windows 10 +Description of problem: +sdl window opens with black screen, freezes, then crashes +Steps to reproduce: +1. run the command +Additional information: +- Works fine with just `sdl`, running `gtk,gl=on` outputs `opengl is not supported by the display` +- tried with both `-vga virtio` and `vga std`, same result +- tried with SVM turned on and off (AMD cpu, ryzen 2600x), same result +- built the project `./configure --enable-gtk --enable-sdl --enable-opengl, saw the `OK` for all 3 +- have opengl ver 4.6 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1532 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1532 new file mode 100644 index 000000000..f31f98f60 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1532 @@ -0,0 +1,503 @@ +libivrtd fork qemu to create vm ,which start with ceph rbd device, after vm status:runing , the qemu stuck at booting from hard disk.... +Description of problem: +[root@ceph-client ceph]# virsh list --all + Id Name State +---------------------------------------------------- + 19 c7_ceph running + +the vm qemu stuck at booting from hard disk..... +Steps to reproduce: +1. use ceph-deploy deploy a ceph distribute storage, which use to store vm's qcow2 files,this ceph has 3 osd node +2. refer the link https://docs.ceph.com/en/quincy/rbd/libvirt/ create a ceph user :client.libvirt +3. import a exists qcow2 file into ceph libvit-pool, then start vm + +[root@ceph-1 ~]# ceph -s + cluster: + id: 3fbbf51f-88fd-4883-9f24-595bf853c5f2 + health: HEALTH_OK + + services: + mon: 1 daemons, quorum ceph-1 + mgr: ceph-1(active) + osd: 3 osds: 3 up, 3 in + + data: + pools: 1 pools, 128 pgs + objects: 940 objects, 3.6 GiB + usage: 31 GiB used, 209 GiB / 240 GiB avail + pgs: 128 active+clean + +[root@ceph-1 ~]#ceph auth ls +client.libvirt + key: AQD/XwFkq7kHMhAA1OmPtKPVno6gjmZleOevOA== + caps: [mon] allow r + caps: [osd] allow class-read object_prefix rbd_children, allow rwx pool=libvirt-pool + +[root@ceph-client ceph]# cat ceph.conf +[global] +fsid = 3fbbf51f-88fd-4883-9f24-595bf853c5f2 +mon_initial_members = ceph-1 +mon_host = 172.24.193.62 +auth_cluster_required = cephx +auth_service_required = cephx +auth_client_required = cephx + +osd_pool_default_size = 2 +[root@ceph-client ceph]# + +[root@ceph-client ceph]# virsh start c7_ceph +Domain c7_ceph started + +[root@ceph-client ceph]# +[root@ceph-client ceph]# virsh list --all + Id Name State +---------------------------------------------------- + 19 c7_ceph running + + + <emulator>/usr/local/qemu-3.0/bin/qemu-system-x86_64</emulator> + <disk type='network' device='disk'> + <driver name='qemu' type='raw' cache='writeback'/> + <auth username='libvirt'> + <secret type='ceph' uuid='fb57a2a3-8cdf-44cb-afc1-2d8bdc0fc5d0'/> + </auth> + <source protocol='rbd' name='libvirt-pool/root-vsys_c5.qcow2'> + <host name='172.24.193.62' port='6789'/> + <host name='172.24.193.63' port='6789'/> + <host name='172.24.193.64' port='6789'/> + </source> + <target dev='vda' bus='virtio'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> + </disk> + +======================== +[root@ceph-client ceph]# cat /run/libvirt/qemu/c7_ceph.xml + + +<domstatus state='running' reason='booted' pid='57437'> + <monitor path='/var/lib/libvirt/qemu/domain-19-c7_ceph/monitor.sock' json='1' type='unix'/> + <namespaces> + <mount/> + </namespaces> + <vcpus> + <vcpu id='0' pid='57487'/> + <vcpu id='1' pid='57488'/> + </vcpus> + <qemuCaps> + <flag name='kvm'/> + <flag name='no-hpet'/> + <flag name='spice'/> + <flag name='boot-index'/> + <flag name='hda-duplex'/> + <flag name='ccid-emulated'/> + <flag name='ccid-passthru'/> + <flag name='virtio-tx-alg'/> + <flag name='virtio-blk-pci.ioeventfd'/> + <flag name='sga'/> + <flag name='virtio-blk-pci.event_idx'/> + <flag name='virtio-net-pci.event_idx'/> + <flag name='piix3-usb-uhci'/> + <flag name='piix4-usb-uhci'/> + <flag name='usb-ehci'/> + <flag name='ich9-usb-ehci1'/> + <flag name='vt82c686b-usb-uhci'/> + <flag name='pci-ohci'/> + <flag name='usb-redir'/> + <flag name='usb-hub'/> + <flag name='ich9-ahci'/> + <flag name='no-acpi'/> + <flag name='virtio-blk-pci.scsi'/> + <flag name='scsi-disk.channel'/> + <flag name='scsi-block'/> + <flag name='transaction'/> + <flag name='block-job-async'/> + <flag name='scsi-cd'/> + <flag name='ide-cd'/> + <flag name='hda-micro'/> + <flag name='dump-guest-memory'/> + <flag name='nec-usb-xhci'/> + <flag name='balloon-event'/> + <flag name='lsi'/> + <flag name='virtio-scsi-pci'/> + <flag name='blockio'/> + <flag name='disable-s3'/> + <flag name='disable-s4'/> + <flag name='usb-redir.filter'/> + <flag name='ide-drive.wwn'/> + <flag name='scsi-disk.wwn'/> + <flag name='seccomp-sandbox'/> + <flag name='reboot-timeout'/> + <flag name='seamless-migration'/> + <flag name='block-commit'/> + <flag name='vnc'/> + <flag name='drive-mirror'/> + <flag name='usb-redir.bootindex'/> + <flag name='usb-host.bootindex'/> + <flag name='blockdev-snapshot-sync'/> + <flag name='qxl'/> + <flag name='VGA'/> + <flag name='cirrus-vga'/> + <flag name='vmware-svga'/> + <flag name='device-video-primary'/> + <flag name='usb-serial'/> + <flag name='usb-net'/> + <flag name='add-fd'/> + <flag name='nbd-server'/> + <flag name='virtio-rng'/> + <flag name='rng-random'/> + <flag name='rng-egd'/> + <flag name='megasas'/> + <flag name='tpm-passthrough'/> + <flag name='tpm-tis'/> + <flag name='pci-bridge'/> + <flag name='vfio-pci'/> + <flag name='vfio-pci.bootindex'/> + <flag name='scsi-generic'/> + <flag name='scsi-generic.bootindex'/> + <flag name='mem-merge'/> + <flag name='vnc-websocket'/> + <flag name='drive-discard'/> + <flag name='mlock'/> + <flag name='device-del-event'/> + <flag name='dmi-to-pci-bridge'/> + <flag name='i440fx-pci-hole64-size'/> + <flag name='q35-pci-hole64-size'/> + <flag name='usb-storage'/> + <flag name='usb-storage.removable'/> + <flag name='ich9-intel-hda'/> + <flag name='kvm-pit-lost-tick-policy'/> + <flag name='boot-strict'/> + <flag name='pvpanic'/> + <flag name='spice-file-xfer-disable'/> + <flag name='spiceport'/> + <flag name='usb-kbd'/> + <flag name='msg-timestamp'/> + <flag name='active-commit'/> + <flag name='change-backing-file'/> + <flag name='memory-backend-ram'/> + <flag name='numa'/> + <flag name='memory-backend-file'/> + <flag name='usb-audio'/> + <flag name='rtc-reset-reinjection'/> + <flag name='splash-timeout'/> + <flag name='iothread'/> + <flag name='migrate-rdma'/> + <flag name='ivshmem'/> + <flag name='drive-iotune-max'/> + <flag name='VGA.vgamem_mb'/> + <flag name='vmware-svga.vgamem_mb'/> + <flag name='qxl.vgamem_mb'/> + <flag name='pc-dimm'/> + <flag name='machine-vmport-opt'/> + <flag name='aes-key-wrap'/> + <flag name='dea-key-wrap'/> + <flag name='pci-serial'/> + <flag name='vhost-user-multiqueue'/> + <flag name='migration-event'/> + <flag name='ioh3420'/> + <flag name='x3130-upstream'/> + <flag name='xio3130-downstream'/> + <flag name='rtl8139'/> + <flag name='e1000'/> + <flag name='virtio-net'/> + <flag name='gic-version'/> + <flag name='incoming-defer'/> + <flag name='virtio-gpu'/> + <flag name='virtio-keyboard'/> + <flag name='virtio-mouse'/> + <flag name='virtio-tablet'/> + <flag name='virtio-input-host'/> + <flag name='chardev-file-append'/> + <flag name='ich9-disable-s3'/> + <flag name='ich9-disable-s4'/> + <flag name='vserport-change-event'/> + <flag name='virtio-balloon-pci.deflate-on-oom'/> + <flag name='mptsas1068'/> + <flag name='qxl.vram64_size_mb'/> + <flag name='chardev-logfile'/> + <flag name='debug-threads'/> + <flag name='secret'/> + <flag name='pxb'/> + <flag name='pxb-pcie'/> + <flag name='device-tray-moved-event'/> + <flag name='nec-usb-xhci-ports'/> + <flag name='virtio-scsi-pci.iothread'/> + <flag name='name-guest'/> + <flag name='qxl.max_outputs'/> + <flag name='spice-unix'/> + <flag name='drive-detect-zeroes'/> + <flag name='tls-creds-x509'/> + <flag name='intel-iommu'/> + <flag name='smm'/> + <flag name='virtio-pci-disable-legacy'/> + <flag name='query-hotpluggable-cpus'/> + <flag name='virtio-net.rx_queue_size'/> + <flag name='virtio-vga'/> + <flag name='drive-iotune-max-length'/> + <flag name='ivshmem-plain'/> + <flag name='ivshmem-doorbell'/> + <flag name='query-qmp-schema'/> + <flag name='gluster.debug_level'/> + <flag name='drive-iotune-group'/> + <flag name='query-cpu-model-expansion'/> + <flag name='virtio-net.host_mtu'/> + <flag name='nvdimm'/> + <flag name='pcie-root-port'/> + <flag name='query-cpu-definitions'/> + <flag name='block-write-threshold'/> + <flag name='query-named-block-nodes'/> + <flag name='cpu-cache'/> + <flag name='qemu-xhci'/> + <flag name='kernel-irqchip'/> + <flag name='kernel-irqchip.split'/> + <flag name='intel-iommu.intremap'/> + <flag name='intel-iommu.caching-mode'/> + <flag name='intel-iommu.eim'/> + <flag name='intel-iommu.device-iotlb'/> + <flag name='virtio.iommu_platform'/> + <flag name='virtio.ats'/> + <flag name='loadparm'/> + <flag name='vnc-multi-servers'/> + <flag name='virtio-net.tx_queue_size'/> + <flag name='chardev-reconnect'/> + <flag name='virtio-gpu.max_outputs'/> + <flag name='vxhs'/> + <flag name='virtio-blk.num-queues'/> + <flag name='vmcoreinfo'/> + <flag name='numa.dist'/> + <flag name='disk-share-rw'/> + <flag name='iscsi.password-secret'/> + <flag name='isa-serial'/> + <flag name='dump-completed'/> + <flag name='qcow2-luks'/> + <flag name='pcie-pci-bridge'/> + <flag name='seccomp-blacklist'/> + <flag name='query-cpus-fast'/> + <flag name='disk-write-cache'/> + <flag name='nbd-tls'/> + <flag name='tpm-crb'/> + <flag name='pr-manager-helper'/> + <flag name='qom-list-properties'/> + <flag name='memory-backend-file.discard-data'/> + <flag name='sdl-gl'/> + <flag name='screendump_device'/> + <flag name='hda-output'/> + <flag name='blockdev-del'/> + <flag name='vmgenid'/> + <flag name='vhost-vsock'/> + <flag name='chardev-fd-pass'/> + <flag name='tpm-emulator'/> + <flag name='mch'/> + <flag name='mch.extended-tseg-mbytes'/> + <flag name='usb-storage.werror'/> + <flag name='egl-headless'/> + <flag name='vfio-pci.display'/> + </qemuCaps> + <devices> + <device alias='rng0'/> + <device alias='virtio-disk0'/> + <device alias='virtio-serial0'/> + <device alias='video0'/> + <device alias='serial0'/> + <device alias='balloon0'/> + <device alias='channel0'/> + <device alias='net0'/> + <device alias='input0'/> + <device alias='scsi0'/> + <device alias='usb'/> + </devices> + <libDir path='/var/lib/libvirt/qemu/domain-19-c7_ceph'/> + <channelTargetDir path='/var/lib/libvirt/qemu/channel/target/domain-19-c7_ceph'/> + <cpu mode='custom' match='exact' check='partial'> + <model fallback='forbid'>Broadwell</model> + </cpu> + <chardevStdioLogd/> + <allowReboot value='yes'/> + <blockjobs active='no'/> + <domain type='kvm' id='19'> + <name>c7_ceph</name> + <uuid>ff08671e-824c-4939-80ec-602235c0662e</uuid> + <memory unit='KiB'>4194304</memory> + <currentMemory unit='KiB'>4194304</currentMemory> + <vcpu placement='static'>2</vcpu> + <resource> + <partition>/machine</partition> + </resource> + <os> + <type arch='x86_64' machine='pc-i440fx-3.0'>hvm</type> + <boot dev='hd'/> + </os> + <features> + <acpi/> + <apic/> + </features> + <cpu mode='custom' match='exact' check='full'> + <model fallback='forbid'>Broadwell</model> + <feature policy='require' name='vme'/> + <feature policy='require' name='f16c'/> + <feature policy='require' name='rdrand'/> + <feature policy='require' name='hypervisor'/> + <feature policy='require' name='arat'/> + <feature policy='disable' name='erms'/> + <feature policy='require' name='xsaveopt'/> + <feature policy='require' name='abm'/> + </cpu> + <clock offset='utc'> + <timer name='rtc' tickpolicy='catchup'/> + <timer name='pit' tickpolicy='delay'/> + <timer name='hpet' present='no'/> + </clock> + <on_poweroff>destroy</on_poweroff> + <on_reboot>restart</on_reboot> + <on_crash>destroy</on_crash> + <pm> + <suspend-to-mem enabled='no'/> + <suspend-to-disk enabled='no'/> + </pm> + <devices> + <emulator>/usr/local/qemu-3.0/bin/qemu-system-x86_64</emulator> + <disk type='network' device='disk'> + <driver name='qemu' type='raw' cache='writeback'/> + <auth username='libvirt'> + <secret type='ceph' uuid='fb57a2a3-8cdf-44cb-afc1-2d8bdc0fc5d0'/> + </auth> + <source protocol='rbd' name='libvirt-pool/root-vsys_c5.qcow2' tlsFromConfig='0'> + <host name='172.24.193.62' port='6789'/> + <host name='172.24.193.63' port='6789'/> + <host name='172.24.193.64' port='6789'/> + <privateData> + <objects> + <secret type='auth' alias='virtio-disk0-secret0'/> + </objects> + </privateData> + </source> + <target dev='vda' bus='virtio'/> + <alias name='virtio-disk0'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> + </disk> + <controller type='usb' index='0' model='ich9-ehci1'> + <alias name='usb'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x7'/> + </controller> + <controller type='usb' index='0' model='ich9-uhci1'> + <alias name='usb'/> + <master startport='0'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0' multifunction='on'/> + </controller> + <controller type='usb' index='0' model='ich9-uhci2'> + <alias name='usb'/> + <master startport='2'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x1'/> + </controller> + <controller type='usb' index='0' model='ich9-uhci3'> + <alias name='usb'/> + <master startport='4'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x2'/> + </controller> + <controller type='pci' index='0' model='pci-root'> + <alias name='pci.0'/> + </controller> + <controller type='virtio-serial' index='0'> + <alias name='virtio-serial0'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> + </controller> + <controller type='scsi' index='0' model='lsilogic'> + <alias name='scsi0'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> + </controller> + <controller type='ide' index='0'> + <alias name='ide'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> + </controller> + <interface type='bridge'> + <mac address='52:54:00:2e:e1:1f'/> + <source bridge='virbr0'/> + <target dev='vnet0'/> + <model type='virtio'/> + <alias name='net0'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> + </interface> + <serial type='pty'> + <source path='/dev/pts/2'/> + <target type='isa-serial' port='0'> + <model name='isa-serial'/> + </target> + <alias name='serial0'/> + </serial> + <console type='pty' tty='/dev/pts/2'> + <source path='/dev/pts/2'/> + <target type='serial' port='0'/> + <alias name='serial0'/> + </console> + <channel type='unix'> + <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-19-c7_ceph/org.qemu.guest_agent.0'/> + <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> + <alias name='channel0'/> + <address type='virtio-serial' controller='0' bus='0' port='1'/> + </channel> + <input type='tablet' bus='usb'> + <alias name='input0'/> + <address type='usb' bus='0' port='1'/> + </input> + <input type='mouse' bus='ps2'> + <alias name='input1'/> + </input> + <input type='keyboard' bus='ps2'> + <alias name='input2'/> + </input> + <graphics type='vnc' port='5900' autoport='yes' listen='0.0.0.0'> + <listen type='address' address='0.0.0.0' fromConfig='0' autoGenerated='no'/> + </graphics> + <video> + <model type='cirrus' vram='16384' heads='1' primary='yes'/> + <alias name='video0'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> + </video> + <memballoon model='virtio'> + <alias name='balloon0'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> + </memballoon> + <rng model='virtio'> + <backend model='random'>/dev/urandom</backend> + <alias name='rng0'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> + </rng> + </devices> + <seclabel type='dynamic' model='selinux' relabel='yes'> + <label>system_u:system_r:svirt_t:s0:c99,c659</label> + <imagelabel>system_u:object_r:svirt_image_t:s0:c99,c659</imagelabel> + </seclabel> + <seclabel type='dynamic' model='dac' relabel='yes'> + <label>+107:+107</label> + <imagelabel>+107:+107</imagelabel> + </seclabel> + </domain> +</domstatus> +[root@ceph-client ceph]# + +/usr/local/qemu-3.0/bin/qemu-system-x86_64 which is build by qemu-3.0 source code , first i build qemu-3.0 source with --enable-rbd , +later i rebuild qemu-3.0 source with more config paramter from centos7-2009 qemu, those config paramter from qemu-kvm-1.5.3-175.el7.src.rpm ,which has those paramters: +# QEMU configure log Fri Mar 3 18:22:31 CST 2023 +# Configured with: './configure' '--prefix=/usr' '--libdir=/usr/lib64' '--sysconfdir=/etc' '--interp-prefix=/usr/qemu-%M' '--audio-drv-list=pa,alsa' '--with-confsuffix=/qemu-kvm' '--localstatedir=/var' '--libexecdir=/usr/libexec' '--wit +h-pkgversion=qemu-kvm-1.5.3-175.el7' '--disable-strip' '--disable-qom-cast-debug' '--extra-ldflags=-Wl,--build-id -pie -Wl,-z,relro -Wl,-z,now' '--extra-cflags=-O2 -g -pipe -Wall -fexceptions -fstack-protector-strong --param=ssp-buffer +-size=4 -grecord-gcc-switches -m64 -mtune=generic -fPIE -DPIE' '--enable-trace-backend=dtrace' '--enable-werror' '--disable-xen' '--disable-virtfs' '--enable-kvm' '--enable-libusb' '--enable-spice' '--enable-seccomp' '--disable-fdt' '-- +enable-docs' '--disable-sdl' '--disable-debug-tcg' '--disable-sparse' '--disable-brlapi' '--disable-bluez' '--disable-vde' '--disable-curses' '--enable-curl' '--enable-libssh2' '--enable-vnc-tls' '--enable-vnc-sasl' '--enable-linux-aio' + '--enable-smartcard-nss' '--enable-lzo' '--enable-snappy' '--enable-usb-redir' '--enable-vnc-png' '--disable-vnc-jpeg' '--enable-vnc-ws' '--enable-uuid' '--disable-vhost-scsi' '--disable-guest-agent' '--disable-live-block-ops' '--disab +le-live-block-migration' '--enable-rbd' '--enable-glusterfs' '--enable-tcmalloc' '--block-drv-rw-whitelist=qcow2,raw,file,host_device,blkdebug,nbd,iscsi,gluster,rbd' '--block-drv-ro-whitelist=vmdk,vhdx,vpc,ssh,https' '--iasl=/bin/false' + '--target-list=x86_64-softmmu' + + +, after rebuild the qemu-system-x86_64 : + +virsh start c7_ceph +[root@ceph-client ceph]# virsh list --all + Id Name State +---------------------------------------------------- + 19 c7_ceph running + +qemu still stuck at booting from hard disk... + + + +to my surprised if the libvirtd xml file if i replace /usr/local/qemu-3.0/bin/qemu-system-x86_64 with /usr/libexec/bin/qemu-kvm , then the vm +can start successfully . diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1537 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1537 new file mode 100644 index 000000000..9f58396df --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1537 @@ -0,0 +1,11 @@ +One-floppy windows 3.11 file manager does not work in tcg mode +Description of problem: +When I try to boot mini win 3.11 from https://archive.org/details/mwin-3 it boots into desktop ok, but double-clicking on file manager icon result in black window/GPF (briefly flashing text I can't fully read). + +Starting it with boot choice 2 - with emm386 - same action result in machine reboot. + +Using same disk with kvm works for choice #2 (boot with emm386) +Steps to reproduce: +1. Download IMG file from Arhivce org +2. Run it like I shown above +3. Any (out of two) boot choices lead to same outcome - desktop and say ms-dos console works, but launching file manager gives you black screen/error diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1538 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1538 new file mode 100644 index 000000000..f162f6465 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1538 @@ -0,0 +1 @@ +igd.c gives up IGD legacy mode if no option ROM found diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/154 b/gitlab/issues_text/target_missing/host_missing/accel_missing/154 new file mode 100644 index 000000000..44cb36c39 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/154 @@ -0,0 +1 @@ +readlink(2) returns incorrect size for /proc/self/exe diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1541 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1541 new file mode 100644 index 000000000..7b712df8e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1541 @@ -0,0 +1,32 @@ +Invalid position of G_NORETURN in clang v15 +Description of problem: +Order of `G_NORETURN` used in https://gitlab.com/qemu-project/qemu/-/blob/0f3de970febd2c9b29dccecb63ca928c6802a101/include/qemu/osdep.h#L240-242 is not valid in clang++ 15.0.7. + +Switching `extern` with `G_NORETURN` seems to fix the issue. +Steps to reproduce: +1. Build qemu system for MIPSEL or use minimal reproducer: + +`example.cpp`: +``` +#include "/path/to/qemu/include/glib-compat.h" + +extern G_NORETURN +void // QEMU_ERROR("code path is reachable") + qemu_build_not_reached_always(void); +``` + +``` +$ clang++ --version +clang version 15.0.7 +Target: x86_64-pc-linux-gnu +Thread model: posix +InstalledDir: /usr/bin +$ clang++ -m64 -mcx16 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -fcolor-diagnostics -Wall -Winvalid-pch -std=gnu++11 -O0 -g example.cpp +example.cpp:3:8: error: an attribute list cannot appear here +extern G_NORETURN + ^~~~~~~~~~ +/usr/include/glib-2.0/glib/gmacros.h:1075:21: note: expanded from macro 'G_NORETURN' +# define G_NORETURN [[noreturn]] + ^~~~~~~~~~~~ +1 error generated. +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1543 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1543 new file mode 100644 index 000000000..9a25b6042 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1543 @@ -0,0 +1 @@ +Heap-use-after-free in e1000e_receive_internal diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1544 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1544 new file mode 100644 index 000000000..080553a16 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1544 @@ -0,0 +1 @@ +Abort in net_tx_pkt_do_sw_fragmentation diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1545 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1545 new file mode 100644 index 000000000..6d506bf55 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1545 @@ -0,0 +1,9 @@ +SSL is out of date on website +Description of problem: +The Linux KVM website is running an out of date SSL certificate. +Steps to reproduce: +1. visit the website. https://www.linux-kvm.org/page/Main_Page +2. +3. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1546 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1546 new file mode 100644 index 000000000..bd13b2d4a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1546 @@ -0,0 +1 @@ +Git build fail in fp tests diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1548 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1548 new file mode 100644 index 000000000..276ef31d0 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1548 @@ -0,0 +1,38 @@ +8.0.0rc0 Regression: vnc fails with Segmentation fault +Description of problem: +On connecting with `gvncviewer localhost:05` the qemu process fails with +``` +Segmentation fault +``` +`gvncviewer localhost:05` prints +``` +Connected to server +Error: Server closed the connection +Disconnected from server +``` +Steps to reproduce: +1. Enter `qemu-system-x86_64 -m 1536 -display vnc=:05 -k de -cdrom openSUSE-Leap-15.3-GNOME-Live-x86_64-Media.iso` in first terminal +2. Enter `gvncviewer localhost:05` in second terminal +Additional information: +Final output of `git bisect`: +``` +385ac97f8fad0e6980c5dfea71132d5ecfb16608 is the first bad commit +commit 385ac97f8fad0e6980c5dfea71132d5ecfb16608 +Author: Marc-André Lureau <marcandre.lureau@redhat.com> +Date: Tue Jan 17 15:24:40 2023 +0400 + + ui: keep current cursor with QemuConsole + + Keeping the current cursor around is useful, not only for VNC, but for + other displays. Let's move it down, see the following patches for other + usages. + + Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com> + Reviewed-by: Daniel P. Berrangé <berrange@redhat.com> + + include/ui/console.h | 1 + + ui/console.c | 8 ++++++++ + ui/vnc.c | 7 ++----- + ui/vnc.h | 1 - + 4 files changed, 11 insertions(+), 6 deletions(-) +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1549 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1549 new file mode 100644 index 000000000..53dc0ad72 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1549 @@ -0,0 +1,95 @@ +8.0.0rc0 Regression: spicy windows doesn't open +Description of problem: +Soon after start the qemu process outputs +``` +qemu-system-x86_64.exe: fd=900 is not a socket, AIO implementation is missing +qemu-system-x86_64.exe: fd=800 is not a socket, AIO implementation is missing +``` +On connecting with `spicy -h localhost -p 5905 --spice-debug` spicy stops progress after writing this line +``` +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.406: ../spice-gtk-0.42/src/spice-channel.c:1415 main-1:0: channel type 1 id 0 num common caps 1 num caps 1 +``` +Steps to reproduce: +1. Start qemu with `qemu-system-x86_64 -m 1536 -vga qxl -spice port=5905,addr=127.0.0.1,disable-ticketing=on -cdrom openSUSE-Leap-15.3-GNOME-Live-x86_64-Media.iso` in first MSYS2 MinGW64 terminal +2. Start spice with `spicy -h localhost -p 5905 --spice-debug` in second MSYS2 MinGW64 terminal +Additional information: +Final output of `git bisect` +``` +abe34282b088499f4e86fff9bb6d6dafd57ae1d0 is the first bad commit +commit abe34282b088499f4e86fff9bb6d6dafd57ae1d0 +Author: Marc-André Lureau <marcandre.lureau@redhat.com> +Date: Tue Feb 21 16:47:59 2023 +0400 + + win32: avoid mixing SOCKET and file descriptor space + + Until now, a win32 SOCKET handle is often cast to an int file + descriptor, as this is what other OS use for sockets. When necessary, + QEMU eventually queries whether it's a socket with the help of + fd_is_socket(). However, there is no guarantee of conflict between the + fd and SOCKET space. Such conflict would have surprising consequences, + we shouldn't mix them. + + Also, it is often forgotten that SOCKET must be closed with + closesocket(), and not close(). + + Instead, let's make the win32 socket wrapper functions return and take a + file descriptor, and let util/ wrappers do the fd/SOCKET conversion as + necessary. A bit of adaptation is necessary in io/ as well. + + Unfortunately, we can't drop closesocket() usage, despite + _open_osfhandle() documentation claiming transfer of ownership, testing + shows bad behaviour if you forget to call closesocket(). + + Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com> + Reviewed-by: Stefan Berger <stefanb@linux.ibm.com> + Message-Id: <20230221124802.4103554-15-marcandre.lureau@redhat.com> + + include/sysemu/os-win32.h | 4 +- + io/channel-watch.c | 6 +- + util/aio-win32.c | 9 +- + util/oslib-win32.c | 219 +++++++++++++++++++++++++++++++++++++++------- + 4 files changed, 197 insertions(+), 41 deletions(-) +``` +Complete spicy output +``` +$ spicy -h localhost -p 5905 --spice-debug +(spicy.exe:5584): GSpice-DEBUG: 18:43:52.890: ../spice-gtk-0.42/src/spice-session.c:288 New session (compiled from package spice-gtk 0.42) +(spicy.exe:5584): GSpice-DEBUG: 18:43:53.872: ../spice-gtk-0.42/src/spice-session.c:292 Supported channels: main, display, inputs, cursor, playback, record, smartcard, usbredir, webdav +(spicy.exe:5584): GSpice-WARNING **: 18:43:53.877: SpiceSession:gl-scanout is only available on Unix +(spicy.exe:5584): GSpice-WARNING **: 18:43:53.881: UsbDk driver is not installed +(spicy.exe:5584): GSpice-DEBUG: 18:43:53.908: ../spice-gtk-0.42/src/usb-device-manager.c:393 auto-connect filter set to 0x03,-1,-1,-1,0|-1,-1,-1,-1,1 +(spicy.exe:5584): GSpice-DEBUG: 18:43:53.913: ../spice-gtk-0.42/src/usb-backend.c:440 spice_usb_backend_new >> +(spicy.exe:5584): GSpice-DEBUG: 18:43:53.918: ../spice-gtk-0.42/src/usb-backend.c:462 spice_usb_backend_new << +(spicy.exe:5584): GSpice-DEBUG: 18:43:53.995: ../spice-gtk-0.42/src/usb-backend.c:207 adding 04F2:B43C at 1:1 +(spicy.exe:5584): GSpice-DEBUG: 18:43:53.998: ../spice-gtk-0.42/src/usb-backend.c:207 adding 8086:8C26 at 3:0 +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.000: ../spice-gtk-0.42/src/usb-backend.c:207 adding 8086:8C2D at 1:0 +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.003: ../spice-gtk-0.42/src/usb-backend.c:207 adding 0BDA:B728 at 1:4 +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.006: ../spice-gtk-0.42/src/usb-backend.c:158 created dev 00000148d2a9e280, usblib dev 00000148d27a2590 +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.010: ../spice-gtk-0.42/src/usb-backend.c:207 adding 8086:8C31 at 2:0 +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.014: ../spice-gtk-0.42/src/usb-backend.c:207 adding 05E3:0608 at 3:5 +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.017: ../spice-gtk-0.42/src/usb-backend.c:207 adding 8087:8008 at 1:5 +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.020: ../spice-gtk-0.42/src/usb-backend.c:207 adding 0BDA:0129 at 1:3 +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.023: ../spice-gtk-0.42/src/usb-backend.c:158 created dev 00000148d2a9e140, usblib dev 00000148d27a2b30 +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.027: ../spice-gtk-0.42/src/usb-backend.c:207 adding 8087:8000 at 3:4 +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.030: ../spice-gtk-0.42/src/usb-backend.c:207 adding 045E:00DB at 3:1 +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.033: ../spice-gtk-0.42/src/usb-backend.c:207 adding 17EF:6019 at 3:2 +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.035: ../spice-gtk-0.42/src/usb-backend.c:158 created dev 00000148d2a9e190, usblib dev 00000148d27a5460 +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.074: ../spice-gtk-0.42/tools/spicy.c:1881 connection_new (1) +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.074: ../spice-gtk-0.42/src/usb-backend.c:469 handle_libusb_events >> +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.081: ../spice-gtk-0.42/src/spice-session.c:1835 no migration in progress +Spice-INFO: 18:43:54.086: ../spice-gtk-0.42/src/channel-main.c:342:spice_main_set_property: SpiceMainChannel::color-depth has been deprecated. Property is ignored +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.090: ../spice-gtk-0.42/src/spice-channel.c:142 main-1:0: spice_channel_constructed +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.093: ../spice-gtk-0.42/src/spice-session.c:2330 main-1:0: new main channel, switching +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.097: ../spice-gtk-0.42/tools/spicy.c:1758 new channel (#0) +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.099: ../spice-gtk-0.42/tools/spicy.c:1761 new main channel +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.102: ../spice-gtk-0.42/src/usb-device-manager.c:800 device added 0bda:b728 (00000148d2a9e280) +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.105: ../spice-gtk-0.42/src/usb-device-manager.c:800 device added 0bda:0129 (00000148d2a9e140) +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.108: ../spice-gtk-0.42/src/usb-device-manager.c:800 device added 17ef:6019 (00000148d2a9e190) +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.113: ../spice-gtk-0.42/src/spice-channel.c:2763 main-1:0: Open coroutine starting 00000148d2a403f0 +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.116: ../spice-gtk-0.42/src/spice-channel.c:2587 main-1:0: Started background coroutine 00000148d2a402b0 +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.120: ../spice-gtk-0.42/src/spice-session.c:2267 main-1:0: Using plain text, port 5905 +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.124: ../spice-gtk-0.42/src/spice-session.c:2198 open host localhost:5905 +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.136: ../spice-gtk-0.42/src/spice-session.c:2120 main-1:0: connecting 000000010f1ffc90... +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.402: ../spice-gtk-0.42/src/spice-session.c:2104 main-1:0: connect ready +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.406: ../spice-gtk-0.42/src/spice-channel.c:1415 main-1:0: channel type 1 id 0 num common caps 1 num caps 1 +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1550 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1550 new file mode 100644 index 000000000..86acfddaa --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1550 @@ -0,0 +1,16 @@ +Crazy mouse movement when passing `-M pc,vmport=off -accel kvm -vga virtio` at the same time +Description of problem: +The mouse cursor is unusable in an x86 guest (disappears, jumps around like crazy) in a graphical environment when `-M pc,vmport=off -accel kvm -vga virtio` is given at the same time. +Steps to reproduce: +1. Download https://download.manjaro.org/xfce/22.0.5/manjaro-xfce-22.0.5-230316-linux61.iso +2. Start above command +3. Wait until the graphical desktop appears +4. Click inside the window and move the mouse + +-> Mouse cursor disappears or jumps around like crazy +Additional information: +If vmport=off is **not** passed, at some point during startup (before graphical login manager appears) the guest switches to use vmmouse from PS/2 mouse. There it also requests usage of absolute input coordinates (VMMOUSE_REQUEST_ABSOLUTE). This code path works normal. Therefore the culprit might be in the guest. + +Another way to reproduce the issue is to use -accel whpx under Windows host (no need to pass vmport=off there). It can be observed that the same guest doesn't attempt to switch to vmmouse there, just like passing vmport=off under Linux. + +The problem does not exist on Linux host when -accel tcg is used in which case the guest doesn't attempt to switch to vmmouse. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1553 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1553 new file mode 100644 index 000000000..282da2ba7 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1553 @@ -0,0 +1,12 @@ +Build error: implicit declaration of function 'qemu_close_to_socket' +Description of problem: +When build the latest master code with MSYS2 on Windows 10, GCC reports: +../ui/spice-core.c: In function 'watch_remove': +../ui/spice-core.c:152:5: error: implicit declaration of function 'qemu_close_to_socket' [-Werror=implicit-function-declaration] + 152 | qemu_close_to_socket(watch->fd); + | ^~~~~~~~~~~~~~~~~~~~ +../ui/spice-core.c:152:5: error: nested extern declaration of 'qemu_close_to_socket' [-Werror=nested-externs] +Steps to reproduce: +1. ./configure --enable-sdl --enable-gtk --target-list=arm-softmmu,aarch64-softmmu +2. cd build +3. make diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1554 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1554 new file mode 100644 index 000000000..20b20ee71 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1554 @@ -0,0 +1,6 @@ +I want get a qemu-img tool,which can run in Any linux operating system, what can i do? +Description of problem: +As we known,qemu-img depends on many dynamic libraries,it can't run in other os if libraries is not support.whether qemu can use static compilation to solve this problem？ + + +i refer to this [issue 1190](https://gitlab.com/qemu-project/qemu/-/issues/1190),but when compile over,it not generate a static qemu-img. Or it has other functions to get a qemu-img which can run in Any linux operating system? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1557 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1557 new file mode 100644 index 000000000..94bfc80ee --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1557 @@ -0,0 +1,11 @@ +qemu-binfmt-conf.sh handles errors inconsistently +Description of problem: +We are installing qemu via multiarch/qemu-user-static docker image. https://github.com/multiarch/qemu-user-static + +What we have noticed is that because qemu-binfmt-conf.sh does not use `set -e`, its behavior with regards to failures is inconsistent. In short, registering the same thing into binfmt twice is an error (you get EEXIST). However, the exit code of qemu-binfmt-conf.sh itself seems to depend only on whether the last interpreter succeeded, leading to confusing and inconsistent results. +Steps to reproduce: +1. Register only qemu-arm-static interpreter with binfmt. +2. Run qemu-binfmt-conf.sh. Observe that the exit code is zero, and logs show the duplicate interpreter was rejected. +3. Remove all qemu interpreters. +3. Register only qemu-loongarch64-static interpreter (currently last in qemu_target_list) with binfmt. +3. Run qemu-binfmt-conf.sh. Observe that the exit code is non-zero, and logs show the duplicate interpreter was rejected. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1558 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1558 new file mode 100644 index 000000000..7529f6b4c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1558 @@ -0,0 +1,21 @@ +Bug checklist for AEHD +Description of problem: +There was a discussion on qemu-devel about addition of a new hypervisor, which is essentially a rewrite of linux/kvm, but for windows +- 202303002 Haito Shan [PATCH 0/6] Adding the Android Emulator hypervisor driver accelerator + https://lore.kernel.org/qemu-devel/CAGD3tSzW1QoAsn+uGjoAkBegLt1iZ=9YWDFcvqbcHMr0S_5kVw@mail.gmail.com/ + +If the new hypervisor AEHD does not support these, then each of the below may automatically qualify as a feature catchup bug +1) Nested Virtualization +2) virtio-GPU/virgl/OpenGL/venus +3) Vulkan passthrough +4) Xen emulation on KVM ( a feature also currently under development) + 20230302 [phase1-qemu-8.0](https://lore.kernel.org/qemu-devel/20230302123029.153265-1-pbonzini@redhat.com/) [PULL 00/62] i386, misc changes for QEMU 8.0 soft freeze + 20230307 [phase2-qemu-8.0](https://lore.kernel.org/qemu-devel/20230307171750.2293175-1-dwmw2@infradead.org/) [PATCH v2 00/27] Enable PV backends with Xen/KVM emulation +5) Migration +6) others?? + +perhaps also document if known for certain that there is no intention to catchup to a particular feature. +Steps to reproduce: +NA +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/156 b/gitlab/issues_text/target_missing/host_missing/accel_missing/156 new file mode 100644 index 000000000..73002a357 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/156 @@ -0,0 +1 @@ +-nodefaults has unclear documentation diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1560 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1560 new file mode 100644 index 000000000..442ed8709 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1560 @@ -0,0 +1 @@ +SLIRP hostfwd_add ignores bind address and uses `INADDR_ANY` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1561 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1561 new file mode 100644 index 000000000..560f77b7f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1561 @@ -0,0 +1,27 @@ +Compile QEMU 6.2.0 fail for file not found +Description of problem: +Compile QEMU failed with error message: +``` +In file included from ../subprojects/libvhost-user/libvhost-user.c:45: +../subprojects/libvhost-user/libvhost-user.h:23:10: Fatal error：standard-headers/linux/virtio_ring.h：no such file or directory + 23 | #include "standard-headers/linux/virtio_ring.h" + | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +``` +Steps to reproduce: +1. Download qemu-6.2.0 tarball at https://download.qemu.org/qemu-6.2.0.tar.xz +2. unzip the tarball to dir ```qemu-6.2.0``` +2. cd ```qemu-6.2.0```, and then ```./configure && make -j2``` +Additional information: +In ```qemu-6.2.0/subprojects/libvhost-user/libvhost-user.c:45```, the included files are: + +``` +#include <stdint.h> +#include <stdbool.h> +#include <stddef.h> +#include <poll.h> +#include <linux/vhost.h> +#include <pthread.h> +#include "standard-headers/linux/virtio_ring.h" +``` + +```standard-headers``` are in ```qemu-6.2.0/include/standard-headers/```, but above #include assume it's in the same dir of ```libvhost-user.c```. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1562 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1562 new file mode 100644 index 000000000..050ae55b5 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1562 @@ -0,0 +1,129 @@ +qemu live migration with compression ( zstd or zlib ) in same server always(100% reproduce) failed (recevied ram page flag 0x0) +Description of problem: + +Steps to reproduce: +1. live migration with compress mode in same server +2. src: qemu-system-x86_64 -cpu Cascadelake-Server-v4 -smp 10 -enable-kvm -m 50G -nographic -serial telnet:localhost:4321,server,nowait -nic tap,ifname=tap0,script=no,downscript=no CentOS-Stream-GenericCloud-9-20230123.0.x86_64_test_0.qcow2 + +``` + QEMU 7.2.91 monitor - type 'help' for more information +(qemu) migrate_set_capability compress on +(qemu) migrate_set_parameter multifd-compression zstd +(qemu) info migrate_capabilities +xbzrle: off +rdma-pin-all: off +auto-converge: off +zero-blocks: off +compress: on +events: off +postcopy-ram: off +x-colo: off +release-ram: off +block: off +return-path: off +pause-before-switchover: off +multifd: off +dirty-bitmaps: off +postcopy-blocktime: off +late-block-activate: off +x-ignore-shared: off +validate-uuid: off +background-snapshot: off +zero-copy-send: off +postcopy-preempt: off +(qemu) info migrate_parameters +announce-initial: 50 ms +announce-max: 550 ms +announce-rounds: 5 +announce-step: 100 ms +compress-level: 1 +compress-threads: 8 +compress-wait-thread: on +decompress-threads: 2 +throttle-trigger-threshold: 50 +cpu-throttle-initial: 20 +cpu-throttle-increment: 10 +cpu-throttle-tailslow: off +max-cpu-throttle: 99 +tls-creds: '' +tls-hostname: '' +max-bandwidth: 134217728 bytes/second +downtime-limit: 300 ms +x-checkpoint-delay: 20000 ms +block-incremental: off +multifd-channels: 2 +multifd-compression: zstd +xbzrle-cache-size: 67108864 bytes +max-postcopy-bandwidth: 0 +tls-authz: '' +(qemu) migrate -d tcp:localhost:4444 +(qemu) qemu-system-x86_64: failed to save SaveStateEntry with id(name): 2(ram): -5 +qemu-system-x86_64: Unable to write to socket: Connection reset by peer +``` + +3.dest(in same server): qemu-system-x86_64 -cpu Cascadelake-Server-v4 -smp 10 -enable-kvm -m 50G -nographic -serial telnet:localhost:4322,server,nowait -nic tap,ifname=tap1,script=no,downscript=no --incoming tcp:0:4444 CentOS-Stream-GenericCloud-9-20230123.0.x86_64_test_0.qcow2 + +``` + QEMU 7.2.91 monitor - type 'help' for more information +(qemu) migrate_set_capability compress on +(qemu) migrate_set_parameter multifd-compression zstd +(qemu) info mi +mice migrate migrate_capabilities +migrate_parameters +(qemu) info migrate_capabilities +xbzrle: off +rdma-pin-all: off +auto-converge: off +zero-blocks: off +compress: on +events: off +postcopy-ram: off +x-colo: off +release-ram: off +block: off +return-path: off +pause-before-switchover: off +multifd: off +dirty-bitmaps: off +postcopy-blocktime: off +late-block-activate: off +x-ignore-shared: off +validate-uuid: off +background-snapshot: off +zero-copy-send: off +postcopy-preempt: off +(qemu) info migr +migrate migrate_capabilities migrate_parameters +(qemu) info migrate_parameters +announce-initial: 50 ms +announce-max: 550 ms +announce-rounds: 5 +announce-step: 100 ms +compress-level: 1 +compress-threads: 8 +compress-wait-thread: on +decompress-threads: 2 +throttle-trigger-threshold: 50 +cpu-throttle-initial: 20 +cpu-throttle-increment: 10 +cpu-throttle-tailslow: off +max-cpu-throttle: 99 +tls-creds: '' +tls-hostname: '' +max-bandwidth: 134217728 bytes/second +downtime-limit: 300 ms +x-checkpoint-delay: 20000 ms +block-incremental: off +multifd-channels: 2 +multifd-compression: zstd +xbzrle-cache-size: 67108864 bytes +max-postcopy-bandwidth: 0 +tls-authz: '' +(qemu) info migrate_capabilitiesqemu-system-x86_64: Unknown combination of migration flags: 0x0 +qemu-system-x86_64: decompress data failed +qemu-system-x86_64: error while loading state section id 2(ram) +qemu-system-x86_64: load of migration failed: Operation not permitted +``` +Additional information: +$ zstd -V +*** zstd command line interface 64-bits v1.5.1, by Yann Collet *** diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1563 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1563 new file mode 100644 index 000000000..5b4eeb21d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1563 @@ -0,0 +1,3 @@ +lsi53c895a: DMA reentrancy issue leads to stack overflow (CVE-2023-0330) +Description of problem: +See https://bugzilla.redhat.com/show_bug.cgi?id=2160151. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1566 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1566 new file mode 100644 index 000000000..0cc9e2073 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1566 @@ -0,0 +1,9 @@ +qemo-8-0-0-rc2 error: redeclaration of 'enum fsconfig_command' +Description of problem: + +Steps to reproduce: +1. +2. +3. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1567 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1567 new file mode 100644 index 000000000..4d6ca6fc8 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1567 @@ -0,0 +1,34 @@ +On windows, storage daemon does not support daemonize +Description of problem: +Presently, in order to run qemu-storage-daemon on windows, one has to login and run it in a terminal window that is kept open. + +# +Steps to reproduce: +just run the command +Additional information: +https://gitlab.com/qemu-project/qemu/-/blob/master/storage-daemon/qemu-storage-daemon.c#L299 +``` + case OPTION_DAEMONIZE: + if (os_set_daemonize(true) < 0) { + /* + * --daemonize is parsed before monitor_init_globals(), so + * error_report() does not work yet + */ + fprintf(stderr, "--daemonize not supported in this build\n"); + exit(EXIT_FAILURE); + } +``` +https://gitlab.com/qemu-project/qemu/-/blob/master/include/sysemu/os-win32.h#L114 +``` +static inline int os_set_daemonize(bool d) +{ + if (d) { + return -ENOTSUP; + } + return 0; +} +``` + +- Recently Marc has added windows socket support + 20230313 marcandre.lureau [PULL 00/25] Win socket patches + https://lore.kernel.org/qemu-devel/20230313114335.424093-1-marcandre.lureau@redhat.com/ diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1569 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1569 new file mode 100644 index 000000000..75e42de22 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1569 @@ -0,0 +1,27 @@ +NVMe FS operations hang after suspending and resuming both guest and host +Description of problem: +Hello and thank you for your work on QEMU! + +Using the NVMe driver with my Seagate FireCuda 530 2TB M.2 works fine until I encounter this problem, which is reliably reproducible for me. + +When I suspend the guest and then suspend (s2idle) my host all is well until I resume the guest (manually with `virsh dompmwakeup $VMNAME`, after the host has resumed). Although the guest resumes and is interactive, it seems that anything involving filesystem operations hang forever and do not return. + +Suspending and resuming the Linux guest seems to work perfectly if I don't suspend/resume the host. + +Ultimately what I'm wanting to do is share the drive between VMs with qemu-storage-daemon. I can reproduce the problem in that scenario in much the same way. Using PCI passthrough with the same VM and device works fine and doesn't exhibit this problem. + +Hopefully that's clear enough - let me know if there's anything else I can provide. +Steps to reproduce: +1. Create a VM with a dedicated NVMe disk. +2. Boot an ISO and install to the disk. +3. Verify that suspend and resume works when not suspending the host. +4. Suspend the guest. +5. Suspend the host. +6. Wake the host. +7. Wake the guest. +8. Try just about anything that isn't likely already cached somewhere: `du -s /etc`. +Additional information: +I've attached the libvirt domain XML[1] and libvirtd debug logs for QEMU[2] ("1:qemu") that covers suspending the guest & host, resuming host & guest and doing something to cause a hang. I tried to leave enough time afterwards for any timeout to occur. + +1. [nvme-voidlinux.xml](/uploads/1dea47af096ce58175f7aa526eca455e/nvme-voidlinux.xml) +2. [nvme-qemu-debug.log](/uploads/42d3bed456a795069023a61d38fa5ccd/nvme-qemu-debug.log) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/157 b/gitlab/issues_text/target_missing/host_missing/accel_missing/157 new file mode 100644 index 000000000..a5f47bd3a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/157 @@ -0,0 +1 @@ +Xbox One controller USB passthrough disconnections and stops diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1572 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1572 new file mode 100644 index 000000000..30e8840f6 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1572 @@ -0,0 +1 @@ +Assertion !rss_info->enabled failed in e1000e_write_lgcy_rx_descr diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1573 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1573 new file mode 100644 index 000000000..f8eb439db --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1573 @@ -0,0 +1 @@ +TCP Previous segment not captured diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1574 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1574 new file mode 100644 index 000000000..b143fae08 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1574 @@ -0,0 +1,89 @@ +The guest paused after living migration on destination host, vm-entry error code 0x80000021 +Description of problem: +The guest start on source host, then living migration to destination host, the guest status is pausing. +source host CPU: Intel(R) Xeon(R) Silver 4114 CPU @ 2.20GHz +destination host CPU: Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz +If the guest migration from E5-2650 to Silver 4114, the guest runs normally without pausing. +Steps to reproduce: +1. start guest, on source host, host CPU: Intel(R) Xeon(R) Silver 4114 CPU @ 2.20GHz. +2. living migration guest to destination host, host CPU: Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz. +3. migration finished, the guest pausing. +Additional information: +/label ~"kind::Bug" +qemu log: +``` +KVM: entry failed, hardware error 0x80000021 + +If you're running a guest on an Intel machine without unrestricted mode +support, the failure can be most likely due to the guest entering an invalid +state for Intel VT. For example, the guest maybe running in big real mode +which is not supported on less recent Intel processors. + +EAX=94d14da0 EBX=95341e20 ECX=00000000 EDX=00000000 +ESI=00000000 EDI=00000046 EBP=95203eb0 ESP=95203eb0 +EIP=94d14f76 EFL=00000286 [--S--P-] CPL=0 II=0 A20=1 SMM=0 HLT=0 +ES =0000 00000000 0000ffff 00009300 +CS =f000 ffff0000 0000ffff 00009b00 +SS =0000 00000000 0000ffff 00009300 +DS =0000 00000000 0000ffff 00009300 +FS =0000 00000000 0000ffff 00009300 +GS =0000 00000000 0000ffff 00009300 +LDT=0000 00000000 0000ffff 00008200 +TR =0000 00000000 0000ffff 00008b00 +GDT= 00000000 0000ffff +IDT= 00000000 0000ffff +CR0=60000010 CR2=00000000 CR3=00000000 CR4=00000000 +DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 +DR6=00000000ffff0ff0 DR7=0000000000000400 +EFER=0000000000000000 +Code=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <00> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +``` +host log: +``` +kernel: [228693.951391] *** Guest State *** +kernel: [228693.951411] CR0: actual=0x0000000000000030, shadow=0x0000000060000010, gh_mask=fffffffffffffff7 +kernel: [228693.951422] CR4: actual=0x0000000000002040, shadow=0x0000000000000000, gh_mask=fffffffffffff871 +kernel: [228693.951430] CR3 = 0x0000000000000000 +kernel: [228693.951437] PDPTR0 = 0x0000000000000000 PDPTR1 = 0x0000000000000000 +kernel: [228693.951445] PDPTR2 = 0x0000000000000000 PDPTR3 = 0x0000000000000000 +kernel: [228693.951452] RSP = 0xffffffff95203eb0 RIP = 0xffffffff94d14f76 +kernel: [228693.951459] RFLAGS=0x00000286 DR7 = 0x0000000000000400 +kernel: [228693.951467] Sysenter RSP=0000000000000000 CS:RIP=0000:0000000000000000 +kernel: [228693.951476] CS: sel=0xf000, attr=0x0009b, limit=0x0000ffff, base=0x00000000ffff0000 +kernel: [228693.951485] DS: sel=0x0000, attr=0x00093, limit=0x0000ffff, base=0x0000000000000000 +kernel: [228693.951494] SS: sel=0x0000, attr=0x00093, limit=0x0000ffff, base=0x0000000000000000 +kernel: [228693.951502] ES: sel=0x0000, attr=0x00093, limit=0x0000ffff, base=0x0000000000000000 +kernel: [228693.951510] FS: sel=0x0000, attr=0x00093, limit=0x0000ffff, base=0x0000000000000000 +kernel: [228693.951519] GS: sel=0x0000, attr=0x00093, limit=0x0000ffff, base=0x0000000000000000 +kernel: [228693.951527] GDTR: limit=0x0000ffff, base=0x0000000000000000 +kernel: [228693.951537] LDTR: sel=0x0000, attr=0x00082, limit=0x0000ffff, base=0x0000000000000000 +kernel: [228693.951545] IDTR: limit=0x0000ffff, base=0x0000000000000000 +kernel: [228693.951553] TR: sel=0x0000, attr=0x0008b, limit=0x0000ffff, base=0x0000000000000000 +kernel: [228693.951562] EFER = 0x0000000000000000 PAT = 0x0007040600070406 +kernel: [228693.951569] DebugCtl = 0x0000000000000000 DebugExceptions = 0x0000000000000000 +kernel: [228693.951578] Interruptibility = 00000000 ActivityState = 00000000 +kernel: [228693.951586] InterruptStatus = 00b1 +kernel: [228693.951591] *** Host State *** +kernel: [228693.951597] RIP = 0xffffffffc4b064ff RSP = 0xffffaf14ccf87d10 +kernel: [228693.951606] CS=0010 SS=0018 DS=0000 ES=0000 FS=0000 GS=0000 TR=0040 +kernel: [228693.951614] FSBase=00007f0b2657a640 GSBase=ffff9c083f580000 TRBase=fffffe00001a0000 +kernel: [228693.951623] GDTBase=fffffe000019e000 IDTBase=fffffe0000000000 +kernel: [228693.951631] CR0=0000000080050033 CR3=000000029800c004 CR4=00000000003726e0 +kernel: [228693.951639] Sysenter RSP=fffffe00001a0000 CS:RIP=0010:ffffffff95801590 +kernel: [228693.951648] EFER = 0x0000000000000d01 PAT = 0x0407050600070106 +kernel: [228693.951655] *** Control State *** +kernel: [228693.951662] CPUBased=0xb5a06dfa SecondaryExec=0x00032ff2 TertiaryExec=0x0000000000000000 +kernel: [228693.951671] PinBased=0x000000ff EntryControls=0000d1ff ExitControls=002befff +kernel: [228693.951679] ExceptionBitmap=00060042 PFECmask=00000000 PFECmatch=00000000 +kernel: [228693.951686] VMEntry: intr_info=00000000 errcode=00000000 ilen=00000000 +kernel: [228693.951695] VMExit: intr_info=00000000 errcode=00000000 ilen=00000000 +kernel: [228693.951702] reason=80000021 qualification=0000000000000000 +kernel: [228693.951709] IDTVectoring: info=00000000 errcode=00000000 +kernel: [228693.951717] TSC Offset = 0xfffe2c437c9ab552 +kernel: [228693.951724] SVI|RVI = 00|b1 TPR Threshold = 0x00 +kernel: [228693.951734] virt-APIC addr = 0x00000002a3014000 +kernel: [228693.951736] PostedIntrVec = 0xf2 +kernel: [228693.951743] EPT pointer = 0x000000012dfe705e +kernel: [228693.951749] PLE Gap=00000080 Window=00001000 +kernel: [228693.951755] Virtual processor ID = 0x0009 +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1576 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1576 new file mode 100644 index 000000000..b3f954743 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1576 @@ -0,0 +1,28 @@ +Migration from v8.0.0-rc2 to v7.2.0 with pcie-root-port device fails +Description of problem: +Loading the VM state fails with: +``` +qemu-system-x86_64: get_pci_config_device: Bad config data: i=0x10a read: 40 device: 0 cmask: ff wmask: 0 w1cmask:0 +qemu-system-x86_64: Failed to load PCIDevice:config +qemu-system-x86_64: Failed to load pcie-root-port:parent_obj.parent_obj.parent_obj +qemu-system-x86_64: error while loading state for instance 0x0 of device '0000:00:1c.0/pcie-root-port' +qemu-system-x86_64: Error -22 while loading VM state +``` +Steps to reproduce: +Used the following script with the first argument being a build directory of v8.0.0-rc2 and the second a build directory of v7.2.0 +``` +#!/bin/bash +rm /tmp/disk.qcow2 +args=" + -device pcie-root-port,multifunction=on,bus=pcie.0,addr=1c.0,port=1,chassis=1 + -machine type=pc-q35-7.2" +$1/qemu-img create -f qcow2 /tmp/disk.qcow2 1G +$1/qemu-system-x86_64 --qmp stdio --blockdev qcow2,node-name=node0,file.driver=file,file.filename=/tmp/disk.qcow2 $args <<EOF +{"execute": "qmp_capabilities"} +{"execute": "snapshot-save", "arguments": { "job-id": "save0", "tag": "snap", "vmstate": "node0", "devices": ["node0"] } } +{"execute": "quit"} +EOF +$2/qemu-system-x86_64 --qmp stdio --blockdev qcow2,node-name=node0,file.driver=file,file.filename=/tmp/disk.qcow2 $args -loadvm snap +``` +Additional information: +Bisecting shows that 010746ae1d ("hw/pci/aer: Implement PCI_ERR_UNCOR_MASK register") is the first bad commit. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1577 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1577 new file mode 100644 index 000000000..f24609089 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1577 @@ -0,0 +1,84 @@ +device_del return is already in the process of unplug frequently +Description of problem: +recently we update qemu 6.1.1 to qemu 7.1.0, and run into an issue with the following error: + +command '{ "execute": "device_del", "arguments": { "id": "virtio-diskX" } }' for VM "id" failed ({ "return": {"class": "GenericError", "desc": "Device virtio-diskX is already in the process of unplug"} }). + +The issue is reproducible. With a few seconds delay before hot-unplug, hot-unplug just works fine. + +After a few digging, we found that the commit 9323f892b39 may incur the issue. +------------------ + failover: fix unplug pending detection + + Failover needs to detect the end of the PCI unplug to start migration + after the VFIO card has been unplugged. + + To do that, a flag is set in pcie_cap_slot_unplug_request_cb() and reset in + pcie_unplug_device(). + + But since + 17858a169508 ("hw/acpi/ich9: Set ACPI PCI hot-plug as default on Q35") + we have switched to ACPI unplug and these functions are not called anymore + and the flag not set. So failover migration is not able to detect if card + is really unplugged and acts as it's done as soon as it's started. So it + doesn't wait the end of the unplug to start the migration. We don't see any + problem when we test that because ACPI unplug is faster than PCIe native + hotplug and when the migration really starts the unplug operation is + already done. + + See c000a9bd06ea ("pci: mark device having guest unplug request pending") + a99c4da9fc2a ("pci: mark devices partially unplugged") + + Signed-off-by: Laurent Vivier <lvivier@redhat.com> + Reviewed-by: Ani Sinha <ani@anisinha.ca> + Message-Id: <20211118133225.324937-4-lvivier@redhat.com> + Reviewed-by: Michael S. Tsirkin <mst@redhat.com> + Signed-off-by: Michael S. Tsirkin <mst@redhat.com> +------------------ +The purpose is for detecting the end of the PCI device hot-unplug. However, we feel the error confusing. How is it possible that a disk "is already in the process of unplug" during the first hot-unplug attempt? So far as I know, the issue was also encountered by libvirt, but they simply ignored it: + + https://bugzilla.redhat.com/show_bug.cgi?id=1878659 + +Hence, a question is: should we have the line below in acpi_pcihp_device_unplug_request_cb()? + + pdev->qdev.pending_deleted_event = true; + +It would be great if you as the author could give us a few hints. + +Thank you very much for your reply! + +Sincerely, + +Yu Zhang @ Compute Platform IONOS + + +The issue is reproducible in our own stack, which is not quite easy to describe in a few command lines. We simplified it a bit by a script instead. Although it's not able to reproduce, it could be somewhat helpful to understand the issue. + +``` +#!/bin/bash + +HOME=~ +QEMU=$HOME/qemu/bin/qemu-system-x86_64 +DISK1=$HOME/img/disk1.qcow2 +DISK4=$HOME/img/disk4.qcow2 +DISK5=$HOME/img/disk5.qcow2 + +$QEMU \ + -cpu host -enable-kvm -m 2048 -smp 2 \ + -object iothread,id=iothread1 \ + -drive file=$DISK1,if=none,id=drive-virtio-disk1,format=qcow2,snapshot=off,discard=on,cache=none \ + -device virtio-blk-pci,bus=pci.0,addr=0x4,drive=drive-virtio-disk1,iothread=iothread1,num-queues=1,discard=on,id=virtio-disk1 \ + -object iothread,id=iothread4 \ + -drive file=$DISK4,if=none,id=drive-virtio-disk4,format=qcow2,snapshot=off,discard=on,cache=none \ + -device virtio-blk-pci,bus=pci.0,addr=0x5,drive=drive-virtio-disk4,iothread=iothread4,num-queues=1,discard=on,id=virtio-disk4 \ + -object iothread,id=iothread5 \ + -drive file=$DISK5,if=none,id=drive-virtio-disk5,format=qcow2,snapshot=off,discard=on,cache=none \ + -device virtio-blk-pci,bus=pci.0,addr=0x6,drive=drive-virtio-disk5,iothread=iothread5,num-queues=1,discard=on,id=virtio-disk5 \ + -qmp unix:./qmp-sock,server,nowait & + +sleep 5 + +echo '{"execute":"qmp_capabilities"}{"execute": "device_del","arguments": { "id": "virtio-disk5"}}{"execute": "query-block"}' | nc -U -w 1 ./qmp-sock +echo '{"execute":"qmp_capabilities"}{"execute": "device_del","arguments": { "id": "virtio-disk5"}}{"execute": "query-block"}' | nc -U -w 1 ./qmp-sock``` +Additional information: +Possible workaround: https://lore.kernel.org/qemu-devel/20230403131833-mutt-send-email-mst@kernel.org/T/#t diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1578 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1578 new file mode 100644 index 000000000..cd5a96404 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1578 @@ -0,0 +1,3 @@ +Send all the SVQ control commands in parallel instead of serialized +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1579 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1579 new file mode 100644 index 000000000..56adc47ba --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1579 @@ -0,0 +1,4 @@ +Cache vdpa initialization & startup slow ioctls +Additional information: +* vring groups are cached in this patch, still not upstream [this example patch](https://lists.nongnu.org/archive/html/qemu-devel/2023-03/msg05961.html). +* hw/virtio/vhost-vdpa.c and net/vhost-vdpa.c are both files that worth exploring. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/158 b/gitlab/issues_text/target_missing/host_missing/accel_missing/158 new file mode 100644 index 000000000..a245b6bcb --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/158 @@ -0,0 +1 @@ +qemu system emulator crashed when using xhci usb controller diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1580 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1580 new file mode 100644 index 000000000..19a7741f9 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1580 @@ -0,0 +1,44 @@ +QEMU crashes when running inside Hyper-V VM on AMD EPYC +Description of problem: +Starting the VM very rarely succeeds and often it crashes with: +``` +# qemu-system-x86_64 -cpu EPYC -machine accel=kvm -smp 1 -m 512 -drive if=pflash,format=raw,readonly=on,file=/usr/share/OVMF/OVMF_CODE.fd -drive if=pflash,format=raw,file=OVMF_VARS.fd -drive file=debian-11-nocloud-amd64-20230124-1270.qcow2,format=qcow2 -snapshot -monitor none +qemu: module ui-ui-gtk not found, do you want to install qemu-system-gui package? +qemu: module ui-ui-sdl not found, do you want to install qemu-system-gui package? +VNC server running on ::1:5900 +KVM internal error. Suberror: 1 +extra data[0]: 0x0000000000000001 +extra data[1]: 0x96d0cff2bed0cf0f +extra data[2]: 0x0bfd29af72b35c7c +extra data[3]: 0x0000000000000400 +extra data[4]: 0x0000000100000004 +extra data[5]: 0x00000000581c356c +extra data[6]: 0x0000000000000000 +extra data[7]: 0x0000000000000000 +emulation failure +EAX=fffd26a4 EBX=00000000 ECX=00000000 EDX=b731cdad +ESI=00000101 EDI=00005042 EBP=fffcc000 ESP=581c3564 +EIP=fffff8a8 EFL=00000002 [-------] CPL=0 II=0 A20=1 SMM=0 HLT=0 +ES =0008 00000000 ffffffff 00c09300 DPL=0 DS [-WA] +CS =0010 00000000 ffffffff 00c09b00 DPL=0 CS32 [-RA] +SS =0008 00000000 ffffffff 00c09300 DPL=0 DS [-WA] +DS =0008 00000000 ffffffff 00c09300 DPL=0 DS [-WA] +FS =0008 00000000 ffffffff 00c09300 DPL=0 DS [-WA] +GS =0008 00000000 ffffffff 00c09300 DPL=0 DS [-WA] +LDT=0000 00000000 0000ffff 00008200 DPL=0 LDT +TR =0000 00000000 0000ffff 00008b00 DPL=0 TSS32-busy +GDT= fffffee0 00000027 +IDT= 00000000 00000000 +CR0=40000033 CR2=00000000 CR3=00800000 CR4=00000660 +DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 +DR6=00000000ffff0ff0 DR7=0000000000000400 +EFER=0000000000000100 +Code=00 0f 20 e0 0f ba e8 05 0f 22 e0 31 db e9 13 02 00 00 85 c0 <75> 38 b9 80 00 00 c0 0f 32 0f ba e8 08 0f 30 31 db b9 01 00 00 00 0f a3 0d 04 b0 80 00 74 +``` +Steps to reproduce: +1. Create a [Standard_D8ads_v5 VM](https://learn.microsoft.com/en-us/azure/virtual-machines/dasv5-dadsv5-series) (AMD EPYC 7763 64-Core Processor) in Azure with Debian 11 +2. Install `qemu-system-x86` (1:7.2+dfsg-5~bpo11+1) from `bullseye-backports` +3. Install `ovmf` (2022.11-6) from `bookworm` (testing) +4. Run the commands under "QEMU command line" +Additional information: +VNC displays "Guest has not initialized the display (yet)". The setup works perfectly on a [Standard_D8ds_v5 VM](https://learn.microsoft.com/en-us/azure/virtual-machines/ddv5-ddsv5-series) (Intel(R) Xeon(R) Platinum 8370C CPU @ 2.80GHz). diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1582 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1582 new file mode 100644 index 000000000..7bc657c1e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1582 @@ -0,0 +1 @@ +Floating-point-exception in rtl8139_cplus_transmit_one diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1583 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1583 new file mode 100644 index 000000000..ab661fa24 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1583 @@ -0,0 +1,19 @@ +SGX Device mapping is not listed into QEMU KVM +Description of problem: +I want to run SGX into QEMU VM, the vm is up and running but SGX device mappings are not listed there. I also looked in dmesg | grep sgx and it returned "There are zero epc section" + +I have upgraded the libvirt to 8.6.0 because of below issue +https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1982896 + +I tried with libvirt-8.0.0 but it did not help + +I have attached the xml, please let me know why sgx mappings are not showing inside VM +Steps to reproduce: +1. Create a Ubuntu 20.04 VM with SGX mapping +Additional information: +Please let me know if any other logs are required + + + + +[ubuntu20.04.xml](/uploads/2609abc31db08e04cc3e3dbf923cd8d7/ubuntu20.04.xml) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1584 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1584 new file mode 100644 index 000000000..f8eb439db --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1584 @@ -0,0 +1 @@ +TCP Previous segment not captured diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1585 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1585 new file mode 100644 index 000000000..933a20874 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1585 @@ -0,0 +1,27 @@ +Incorrect VGA text mode rendering +Description of problem: +All of my physical machines use black as `DarkGray` and have the text starting from `White+DarkGray` blink (watch the video below). The ISO I'm using is a minimal kernel I've written to check VGA text mode (provided by the BIOS at `0xb8000` with a 80x25 resolution) handling on multiple emulators and machines. +Changing the emulated CPU and display driver doesn't change this behaviour. + +Hyper-V: color test shows correct colors, all text starting from `White+DarkGray` is blinking + + + +AMD Athlon 64 X2 6000+ + NVIDIA Quadro 400 on actual hardware: same as Hyper-V +I've tested this with multiple physical GPUs and they all have the same behaviour and color palette. + + + +QEMU: dark gray is the wrong color and the text doesn't blink +Changing the emulated device doesn't change this behaviour. + + + +I think QEMU should emulate the hardware as close as possible and therefore atleast have the blinking text. +Consider this a low priority issue. +Steps to reproduce: +1. Download ISO from the link above +2. Run the QEMU command above +3. See the text not blink +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1586 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1586 new file mode 100644 index 000000000..b82fb2390 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1586 @@ -0,0 +1,107 @@ +qemu-8.0.0-rc3 mock build test stage failures +Description of problem: +https://bugzilla.redhat.com/show_bug.cgi?id=2185288 +Following files have been attached to that report +Attached : +- The rpmuild SPEC file so far (qemu.spec.20230408.v3.txt) +- testlog.20230408.v3.txt +- build.log.20230408.v3.txt +- hw_info.log.20230408.v3.txt +- installed_pkgs.log.20230408.v3.txt +- root.log.20230408.v3.txt +- state.log.20230408.v3.txt + +A number of test failure involving allwinner-i2c and pci_expander_bridge + +``` +Summary of Failures: + + 39/817 qemu:qtest+qtest-aarch64 / qtest-aarch64/test-hmp ERROR 32.55s killed by signal 6 SIGABRT + 41/817 qemu:qtest+qtest-arm / qtest-arm/test-hmp ERROR 34.48s killed by signal 6 SIGABRT + 1/817 qemu:qtest+qtest-aarch64 / qtest-aarch64/qom-test ERROR 210.93s killed by signal 6 SIGABRT + 3/817 qemu:qtest+qtest-arm / qtest-arm/qom-test ERROR 212.50s killed by signal 6 SIGABRT + 45/817 qemu:qtest+qtest-i386 / qtest-i386/bios-tables-test ERROR 272.50s killed by signal 6 SIGABRT + 68/817 qemu:qtest+qtest-x86_64 / qtest-x86_64/bios-tables-test ERROR 286.06s killed by signal 6 SIGABRT +230/817 qemu:qtest+qtest-aarch64 / qtest-aarch64/device-introspect-test ERROR 8.92s killed by signal 6 SIGABRT +270/817 qemu:qtest+qtest-arm / qtest-arm/device-introspect-test ERROR 5.95s killed by signal 6 SIGABRT +337/817 qemu:qtest+qtest-i386 / qtest-i386/cxl-test ERROR 0.90s killed by signal 6 SIGABRT +630/817 qemu:qtest+qtest-x86_64 / qtest-x86_64/cxl-test ERROR 0.84s killed by signal 6 SIGABRT + +Ok: 737 +Expected Fail: 0 +Fail: 10 +Unexpected Pass: 0 +Skipped: 70 +Timeout: 0 + +``` + +The below includes a last line of log snippet for each failure +``` + + 39/817 qemu:qtest+qtest-aarch64 / qtest-aarch64/test-hmp ERROR 32.55s killed by signal 6 SIGABRT + /builddir/build/BUILD/qemu-8.0.0/include/hw/i2c/allwinner-i2c.h:35:AW_I2C: Object 0x7fec734903a0 is not an instance of type allwinner.i2c +Broken pipe +../tests/qtest/libqtest.c:193: kill_qemu() detected QEMU death from signal 6 (Aborted) (core dumped) + + + 41/817 qemu:qtest+qtest-arm / qtest-arm/test-hmp ERROR 34.48s killed by signal 6 SIGABRT +/builddir/build/BUILD/qemu-8.0.0/include/hw/i2c/allwinner-i2c.h:35:AW_I2C: Object 0x55e683992440 is not an instance of type allwinner.i2c +Broken pipe +../tests/qtest/libqtest.c:193: kill_qemu() detected QEMU death from signal 6 (Aborted) (core dumped) + + + 1/817 qemu:qtest+qtest-aarch64 / qtest-aarch64/qom-test ERROR 210.93s killed by signal 6 SIGABRT +/builddir/build/BUILD/qemu-8.0.0/include/hw/i2c/allwinner-i2c.h:35:AW_I2C: Object 0x7fbddaf123a0 is not an instance of type allwinner.i2c +Broken pipe +../tests/qtest/libqtest.c:193: kill_qemu() detected QEMU death from signal 6 (Aborted) (core dumped) + + + 3/817 qemu:qtest+qtest-arm / qtest-arm/qom-test ERROR 212.50s killed by signal 6 SIGABRT +/builddir/build/BUILD/qemu-8.0.0/include/hw/i2c/allwinner-i2c.h:35:AW_I2C: Object 0x55c346ae4440 is not an instance of type allwinner.i2c +Broken pipe +../tests/qtest/libqtest.c:193: kill_qemu() detected QEMU death from signal 6 (Aborted) (core dumped) + +45/817 qemu:qtest+qtest-i386 / qtest-i386/bios-tables-test ERROR 272.50s killed by signal 6 SIGABRT +../hw/pci-bridge/pci_expander_bridge.c:54:PXB_DEV: Object 0x5636d9f16fa0 is not an instance of type pxb +Broken pipe +../tests/qtest/libqtest.c:193: kill_qemu() detected QEMU death from signal 6 (Aborted) (core dumped) + + +68/817 qemu:qtest+qtest-x86_64 / qtest-x86_64/bios-tables-test ERROR 286.06s killed by signal 6 SIGABRT +../hw/pci-bridge/pci_expander_bridge.c:54:PXB_DEV: Object 0x55e0736d8e20 is not an instance of type pxb +Broken pipe +../tests/qtest/libqtest.c:193: kill_qemu() detected QEMU death from signal 6 (Aborted) (core dumped) + +230/817 qemu:qtest+qtest-aarch64 / qtest-aarch64/device-introspect-test ERROR 8.92s killed by signal 6 SIGABRT +/builddir/build/BUILD/qemu-8.0.0/include/hw/i2c/allwinner-i2c.h:35:AW_I2C: Object 0x55ab62324420 is not an instance of type allwinner.i2c +Broken pipe +../tests/qtest/libqtest.c:193: kill_qemu() detected QEMU death from signal 6 (Aborted) (core dumped) + + +270/817 qemu:qtest+qtest-arm / qtest-arm/device-introspect-test ERROR 5.95s killed by signal 6 SIGABRT +----------------------------------- stderr ----------------------------------- +/builddir/build/BUILD/qemu-8.0.0/include/hw/i2c/allwinner-i2c.h:35:AW_I2C: Object 0x564fbf62ee90 is not an instance of type allwinner.i2c +Broken pipe +../tests/qtest/libqtest.c:193: kill_qemu() detected QEMU death from signal 6 (Aborted) (core dumped) + + + +337/817 qemu:qtest+qtest-i386 / qtest-i386/cxl-test ERROR 0.90s killed by signal 6 SIGABRT +../hw/pci-bridge/pci_expander_bridge.c:54:PXB_DEV: Object 0x55c66482d5f0 is not an instance of type pxb +Broken pipe +../tests/qtest/libqtest.c:193: kill_qemu() detected QEMU death from signal 6 (Aborted) (core dumped) + +630/817 qemu:qtest+qtest-x86_64 / qtest-x86_64/cxl-test ERROR 0.84s killed by signal 6 SIGABRT +../hw/pci-bridge/pci_expander_bridge.c:54:PXB_DEV: Object 0x5634e6278170 is not an instance of type pxb +Broken pipe +../tests/qtest/libqtest.c:193: kill_qemu() detected QEMU death from signal 6 (Aborted) (core dumped) +``` +Steps to reproduce: +1. Populate rpmbuild folders with ```rpm -i qemu-7.2.0-7.fc39.srpm``` from https://koji.fedoraproject.org/koji/packageinfo?packageID=3685 +2. Download to ```~/rpmbuild/SOURCES/qemu-8.0.0.tar.xz``` from ```https://download.qemu.org/qemu-8.0.0-rc3.tar.xz``` +3. craft ```~/SPECS/qemu.spec``` for qemu-8.0.0-rc3 (or download attachment of bugzilla bug) +4. recreate new qemu-8.0.0 srpm ```rpmbuild -bs SPECS/qemu.spec``` +5. run ```mock -r /etc/mock/fedora-38-x86_64.cfg --rebuild ~/rpmbuild/SRPMS/qemu-8.0.0-0.fc38.src.rpm``` +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1588 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1588 new file mode 100644 index 000000000..7a93f4139 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1588 @@ -0,0 +1,169 @@ +virsh backup-begin crashes guest - qcow2_get_specific_info: Assertion `false' failed. +Description of problem: +I run a daily backup job of around 350 guests, scattered on different host machines. + +Each day around 1-2 guests crashes on virsh backup-begin with the following error in /var/log/libvirt/qemu/$GUEST.log: + +```qemu-system-x86_64: ../../block/qcow2.c:5175: qcow2_get_specific_info: Assertion `false' failed.``` (https://github.com/qemu/qemu/blob/0c8022876f2183f93e23a7314862140c94ee62e7/block/qcow2.c) + +Different guests every day, no patterns what I can see. + +I'm using a top and a base image with incremental backups, qcow2 compat 1.1, output of qemu-img info of the base and top image; + +``` +qemu-img info base.qcow2 +image: base.qcow2 +file format: qcow2 +virtual size: 5 GiB (5368709120 bytes) +disk size: 1.9 GiB +cluster_size: 65536 +Format specific information: + compat: 1.1 + compression type: zlib + lazy refcounts: false + refcount bits: 16 + corrupt: false + extended l2: false + +qemu-img info -U top.qcow2 +image: top.qcow2 +file format: qcow2 +virtual size: 60 GiB (64424509440 bytes) +disk size: 1.36 GiB +cluster_size: 65536 +backing file: base.qcow2 +backing file format: qcow2 +Format specific information: + compat: 1.1 + compression type: zlib + lazy refcounts: false + bitmaps: + [0]: + flags: + [0]: in-use + [1]: auto + name: 1680670811 + granularity: 65536 + refcount bits: 16 + corrupt: false + extended l2: false +``` + +I know I'm not be using the latest qemu and that this is difficult to reproduce. This bug happens in production and upgrading qemu would be a huge task, given that I would have to upgrade the entire production. Nevertheless I of course would be willing to do it if deemed necessary but at this point I'm just looking for directions on how to pin point this bug. + +A "guest-1" grepped version of libvirt debug logs during the seconds this happened: + +``` +2023-04-08 20:37:20.453+0000: 431153: debug : virDomainLookupByName:413 : conn=0x7fbff000ca30, name=guest-1 +2023-04-08 20:37:20.453+0000: 431153: debug : virDomainDispose:348 : release domain 0x7fc068021c60 guest-1 29ac5dd8-6eb9-4140-a9d1-cdcbae01ac0f +2023-04-08 20:37:20.454+0000: 431155: debug : virDomainGetState:2493 : dom=0x7fc068024330, (VM: name=guest-1, uuid=29ac5dd8-6eb9-4140-a9d1-cdcbae01ac0f), state=0x7fc08c052cf0, reason=0x7fc08c052cf4, flags=0x0 +2023-04-08 20:37:20.454+0000: 431155: debug : virDomainDispose:348 : release domain 0x7fc068024330 guest-1 29ac5dd8-6eb9-4140-a9d1-cdcbae01ac0f +2023-04-08 20:37:20.483+0000: 431152: debug : virDomainLookupByName:413 : conn=0x7fc070014e90, name=guest-1 +2023-04-08 20:37:20.483+0000: 431152: debug : virDomainDispose:348 : release domain 0x7fc0500075f0 guest-1 29ac5dd8-6eb9-4140-a9d1-cdcbae01ac0f +2023-04-08 20:37:20.483+0000: 431148: debug : virDomainListAllCheckpoints:292 : dom=0x7fc0ac002380, (VM: name=guest-1, uuid=29ac5dd8-6eb9-4140-a9d1-cdcbae01ac0f), checkpoints=0x7fc0b79018a8, flags=0x0 +2023-04-08 20:37:20.483+0000: 431148: debug : virDomainDispose:348 : release domain 0x7fc0ac002380 guest-1 29ac5dd8-6eb9-4140-a9d1-cdcbae01ac0f +2023-04-08 20:37:20.484+0000: 431151: debug : virDomainDispose:348 : release domain 0x7fc0b0006950 guest-1 29ac5dd8-6eb9-4140-a9d1-cdcbae01ac0f +2023-04-08 20:37:20.516+0000: 431150: debug : virDomainLookupByName:413 : conn=0x7fc0a80027a0, name=guest-1 +2023-04-08 20:37:20.516+0000: 431150: debug : virDomainDispose:348 : release domain 0x7fc08c007c60 guest-1 29ac5dd8-6eb9-4140-a9d1-cdcbae01ac0f +2023-04-08 20:37:20.516+0000: 431152: debug : virDomainGetState:2493 : dom=0x7fc068021e90, (VM: name=guest-1, uuid=29ac5dd8-6eb9-4140-a9d1-cdcbae01ac0f), state=0x7fc0a47c64d0, reason=0x7fc0a47c64d4, flags=0x0 +2023-04-08 20:37:20.516+0000: 431152: debug : virDomainDispose:348 : release domain 0x7fc068021e90 guest-1 29ac5dd8-6eb9-4140-a9d1-cdcbae01ac0f +2023-04-08 20:37:20.544+0000: 431156: debug : virDomainLookupByName:413 : conn=0x7fc0a80025a0, name=guest-1 +2023-04-08 20:37:20.544+0000: 431156: debug : virDomainDispose:348 : release domain 0x7fc068029d00 guest-1 29ac5dd8-6eb9-4140-a9d1-cdcbae01ac0f +2023-04-08 20:37:20.544+0000: 431149: debug : virDomainSuspend:623 : dom=0x7fc050007500, (VM: name=guest-1, uuid=29ac5dd8-6eb9-4140-a9d1-cdcbae01ac0f) +2023-04-08 20:37:20.544+0000: 431149: debug : qemuDomainObjBeginJobInternal:831 : Starting job: job=suspend agentJob=none asyncJob=none (vm=0x7fc0a4033a10 name=guest-1, current job=none agentJob=none async=none) +2023-04-08 20:37:20.544+0000: 431149: debug : qemuDomainObjBeginJobInternal:883 : Started job: suspend (async=none vm=0x7fc0a4033a10 name=guest-1) +2023-04-08 20:37:20.544+0000: 431149: debug : qemuDomainObjEnterMonitorInternal:5872 : Entering monitor (mon=0x7fc0480048b0 vm=0x7fc0a4033a10 name=guest-1) +2023-04-08 20:37:20.580+0000: 1882669: debug : qemuProcessHandleStop:660 : Transitioned guest guest-1 to paused state, reason user, event detail 0 +2023-04-08 20:37:20.580+0000: 1882669: debug : virLockManagerLogParams:90 : key=name type=string value=guest-1 +2023-04-08 20:37:20.580+0000: 1882669: debug : virDomainLockManagerAddImage:90 : Add disk /home/vm/domains/guest-1/disk.qcow2 +2023-04-08 20:37:20.580+0000: 1882669: debug : virLockManagerAddResource:325 : lock=0x7fbf8801fdc0 type=0 name=/home/vm/domains/guest-1/disk.qcow2 nparams=0 params=(nil) flags=0x0 +2023-04-08 20:37:20.581+0000: 431149: debug : qemuDomainObjExitMonitor:5902 : Exited monitor (mon=0x7fc0480048b0 vm=0x7fc0a4033a10 name=guest-1) +2023-04-08 20:37:20.581+0000: 431149: debug : virLockManagerLogParams:90 : key=name type=string value=guest-1 +2023-04-08 20:37:20.581+0000: 431149: debug : virDomainLockManagerAddImage:90 : Add disk /home/vm/domains/guest-1/disk.qcow2 +2023-04-08 20:37:20.581+0000: 431149: debug : virLockManagerAddResource:325 : lock=0x7fc0a8968e60 type=0 name=/home/vm/domains/guest-1/disk.qcow2 nparams=0 params=(nil) flags=0x0 +2023-04-08 20:37:20.582+0000: 431149: debug : qemuDomainObjEndJob:1135 : Stopping job: suspend (async=none vm=0x7fc0a4033a10 name=guest-1) +2023-04-08 20:37:20.582+0000: 431149: debug : virDomainDispose:348 : release domain 0x7fc050007500 guest-1 29ac5dd8-6eb9-4140-a9d1-cdcbae01ac0f +2023-04-08 20:37:20.608+0000: 431148: debug : virDomainLookupByName:413 : conn=0x7fbff000cc30, name=guest-1 +2023-04-08 20:37:20.608+0000: 431148: debug : virDomainDispose:348 : release domain 0x7fc07001e330 guest-1 29ac5dd8-6eb9-4140-a9d1-cdcbae01ac0f +2023-04-08 20:37:20.608+0000: 431151: debug : virDomainGetState:2493 : dom=0x7fc050007550, (VM: name=guest-1, uuid=29ac5dd8-6eb9-4140-a9d1-cdcbae01ac0f), state=0x7fc0a003d640, reason=0x7fc0a003d644, flags=0x0 +2023-04-08 20:37:20.608+0000: 431151: debug : virDomainDispose:348 : release domain 0x7fc050007550 guest-1 29ac5dd8-6eb9-4140-a9d1-cdcbae01ac0f +2023-04-08 20:37:20.634+0000: 431150: debug : virDomainLookupByName:413 : conn=0x7fc0a8002ea0, name=guest-1 +2023-04-08 20:37:20.634+0000: 431150: debug : virDomainDispose:348 : release domain 0x7fbfc00072e0 guest-1 29ac5dd8-6eb9-4140-a9d1-cdcbae01ac0f +2023-04-08 20:37:20.634+0000: 431152: debug : virDomainBackupBegin:13040 : dom=0x7fc0500075f0, (VM: name=guest-1, uuid=29ac5dd8-6eb9-4140-a9d1-cdcbae01ac0f), backupXML=<domainbackup><incremental>1680930625</incremental></domainbackup>, checkpointXML=<domaincheckpoint><name>1680986240</name></domaincheckpoint>, flags=0x0 +2023-04-08 20:37:20.667+0000: 431152: debug : qemuDomainObjBeginJobInternal:831 : Starting job: job=none agentJob=none asyncJob=backup (vm=0x7fc0a4033a10 name=guest-1, current job=none agentJob=none async=none) +2023-04-08 20:37:20.667+0000: 431152: debug : qemuDomainObjBeginJobInternal:892 : Started async job: backup (vm=0x7fc0a4033a10 name=guest-1) +2023-04-08 20:37:20.668+0000: 431152: debug : virStringMatch:662 : match '/home/vm/domains/guest-1/qemu.agent' for '^/var/lib/libvirt/qemu/channel/target/([^/]+\.)|(domain-[^/]+/)org\.qemu\.guest_agent\.0$' +2023-04-08 20:37:20.669+0000: 431152: debug : virStringMatch:662 : match '/home/vm/domains/guest-1/qemu.agent' for '^/var/lib/libvirt/qemu/channel/target/([^/]+\.)|(domain-[^/]+/)org\.qemu\.guest_agent\.0$' +2023-04-08 20:37:20.670+0000: 431152: debug : virStringMatch:662 : match '/home/vm/domains/guest-1/qemu.agent' for '^/var/lib/libvirt/qemu/channel/target/([^/]+\.)|(domain-[^/]+/)org\.qemu\.guest_agent\.0$' +2023-04-08 20:37:20.670+0000: 431152: debug : qemuDomainObjBeginJobInternal:831 : Starting job: job=async nested agentJob=none asyncJob=none (vm=0x7fc0a4033a10 name=guest-1, current job=none agentJob=none async=backup) +2023-04-08 20:37:20.670+0000: 431152: debug : qemuDomainObjBeginJobInternal:883 : Started job: async nested (async=backup vm=0x7fc0a4033a10 name=guest-1) +2023-04-08 20:37:20.670+0000: 431152: debug : qemuDomainObjEnterMonitorInternal:5872 : Entering monitor (mon=0x7fc0480048b0 vm=0x7fc0a4033a10 name=guest-1) +2023-04-08 20:37:20.671+0000: 1882669: debug : qemuMonitorJSONIOProcessLine:222 : Line [{"return": [{"iops_rd": 0, "detect_zeroes": "off", "image": {"virtual-size": 32212254720, "filename": "/home/vm/domains/guest-1/disk.qcow2", "cluster-size": 65536, "format": "qcow2", "actual-size": 7361290240, "format-specific": {"type": "qcow2", "data": {"compat": "1.1", "compression-type": "zlib", "lazy-refcounts": false, "refcount-bits": 16, "corrupt": false, "extended-l2": false}}, "dirty-flag": false}, "iops_wr": 0, "ro": false, "node-name": "libvirt-1-format", "backing_file_depth": 0, "drv": "qcow2", "iops": 0, "bps_wr": 0, "write_threshold": 0, "dirty-bitmaps": [{"name": "1680930625", "recording": true, "persistent": true, "busy": false, "granularity": 65536, "count": 458293248}], "encrypted": false, "bps": 0, "bps_rd": 0, "cache": {"no-flush": false, "direct": false, "writeback": true}, "file": "/home/vm/domains/guest-1/disk.qcow2"}, {"iops_rd": 0, "detect_zeroes": "off", "image": {"virtual-size": 7882014720, "filename": "/home/vm/domains/guest-1/disk.qcow2", "format": "file", "actual-size": 7361290240, "dirty-flag": false}, "iops_wr": 0, "ro": false, "node-name": "libvirt-1-storage", "backing_file_depth": 0, "drv": "file", "iops": 0, "bps_wr": 0, "write_threshold": 0, "encrypted": false, "bps": 0, "bps_rd": 0, "cache": {"no-flush": false, "direct": false, "writeback": true}, "file": "/home/vm/domains/guest-1/disk.qcow2"}], "id": "libvirt-39597736"}] +2023-04-08 20:37:20.671+0000: 1882669: debug : virJSONValueFromString:1691 : string={"return": [{"iops_rd": 0, "detect_zeroes": "off", "image": {"virtual-size": 32212254720, "filename": "/home/vm/domains/guest-1/disk.qcow2", "cluster-size": 65536, "format": "qcow2", "actual-size": 7361290240, "format-specific": {"type": "qcow2", "data": {"compat": "1.1", "compression-type": "zlib", "lazy-refcounts": false, "refcount-bits": 16, "corrupt": false, "extended-l2": false}}, "dirty-flag": false}, "iops_wr": 0, "ro": false, "node-name": "libvirt-1-format", "backing_file_depth": 0, "drv": "qcow2", "iops": 0, "bps_wr": 0, "write_threshold": 0, "dirty-bitmaps": [{"name": "1680930625", "recording": true, "persistent": true, "busy": false, "granularity": 65536, "count": 458293248}], "encrypted": false, "bps": 0, "bps_rd": 0, "cache": {"no-flush": false, "direct": false, "writeback": true}, "file": "/home/vm/domains/guest-1/disk.qcow2"}, {"iops_rd": 0, "detect_zeroes": "off", "image": {"virtual-size": 7882014720, "filename": "/home/vm/domains/guest-1/disk.qcow2", "format": "file", "actual-size": 7361290240, "dirty-flag": false}, "iops_wr": 0, "ro": false, "node-name": "libvirt-1-storage", "backing_file_depth": 0, "drv": "file", "iops": 0, "bps_wr": 0, "write_threshold": 0, "encrypted": false, "bps": 0, "bps_rd": 0, "cache": {"no-flush": false, "direct": false, "writeback": true}, "file": "/home/vm/domains/guest-1/disk.qcow2"}], "id": "libvirt-39597736"} +2023-04-08 20:37:20.672+0000: 1882669: info : qemuMonitorJSONIOProcessLine:241 : QEMU_MONITOR_RECV_REPLY: mon=0x7fc0480048b0 reply={"return": [{"iops_rd": 0, "detect_zeroes": "off", "image": {"virtual-size": 32212254720, "filename": "/home/vm/domains/guest-1/disk.qcow2", "cluster-size": 65536, "format": "qcow2", "actual-size": 7361290240, "format-specific": {"type": "qcow2", "data": {"compat": "1.1", "compression-type": "zlib", "lazy-refcounts": false, "refcount-bits": 16, "corrupt": false, "extended-l2": false}}, "dirty-flag": false}, "iops_wr": 0, "ro": false, "node-name": "libvirt-1-format", "backing_file_depth": 0, "drv": "qcow2", "iops": 0, "bps_wr": 0, "write_threshold": 0, "dirty-bitmaps": [{"name": "1680930625", "recording": true, "persistent": true, "busy": false, "granularity": 65536, "count": 458293248}], "encrypted": false, "bps": 0, "bps_rd": 0, "cache": {"no-flush": false, "direct": false, "writeback": true}, "file": "/home/vm/domains/guest-1/disk.qcow2"}, {"iops_rd": 0, "detect_zeroes": "off", "image": {"virtual-size": 7882014720, "filename": "/home/vm/domains/guest-1/disk.qcow2", "format": "file", "actual-size": 7361290240, "dirty-flag": false}, "iops_wr": 0, "ro": false, "node-name": "libvirt-1-storage", "backing_file_depth": 0, "drv": "file", "iops": 0, "bps_wr": 0, "write_threshold": 0, "encrypted": false, "bps": 0, "bps_rd": 0, "cache": {"no-flush": false, "direct": false, "writeback": true}, "file": "/home/vm/domains/guest-1/disk.qcow2"}], "id": "libvirt-39597736"} +2023-04-08 20:37:20.672+0000: 431152: debug : qemuDomainObjExitMonitor:5902 : Exited monitor (mon=0x7fc0480048b0 vm=0x7fc0a4033a10 name=guest-1) +2023-04-08 20:37:20.672+0000: 431152: debug : qemuDomainObjEndJob:1135 : Stopping job: async nested (async=backup vm=0x7fc0a4033a10 name=guest-1) +2023-04-08 20:37:20.672+0000: 431152: debug : virStorageFileBackendFileInit:57 : initializing FS storage file 0x7fc0704b3740 (file:/home/vm/domains/guest-1/disk.qcow2.1680986240)[64055:108] +2023-04-08 20:37:20.672+0000: 431152: debug : qemuDomainStorageSourceAccessModify:7767 : src='/home/vm/domains/guest-1/disk.qcow2.1680986240' readonly=0 force_ro=0 force_rw=1 revoke=0 chain=0 +2023-04-08 20:37:20.672+0000: 431152: debug : virLockManagerLogParams:90 : key=name type=string value=guest-1 +2023-04-08 20:37:20.672+0000: 431152: debug : virDomainLockManagerAddImage:90 : Add disk /home/vm/domains/guest-1/disk.qcow2.1680986240 +2023-04-08 20:37:20.672+0000: 431152: debug : virLockManagerAddResource:325 : lock=0x7fc0a460ca40 type=0 name=/home/vm/domains/guest-1/disk.qcow2.1680986240 nparams=0 params=(nil) flags=0x0 +2023-04-08 20:37:20.683+0000: 431152: debug : virCommandRunAsync:2630 : About to run LIBVIRT_LOG_OUTPUTS=3:stderr /usr/lib/libvirt/virt-aa-helper -r -u libvirt-29ac5dd8-6eb9-4140-a9d1-cdcbae01ac0f -F /home/vm/domains/guest-1/disk.qcow2.1680986240 +2023-04-08 20:37:20.796+0000: 431151: debug : virDomainLookupByName:413 : conn=0x7fc0a80020a0, name=guest-1 +2023-04-08 20:37:20.893+0000: 431152: debug : qemuSetupImagePathCgroup:74 : Allow path /home/vm/domains/guest-1/disk.qcow2.1680986240, perms: rw +2023-04-08 20:37:20.894+0000: 431152: debug : qemuDomainObjBeginJobInternal:831 : Starting job: job=async nested agentJob=none asyncJob=none (vm=0x7fc0a4033a10 name=guest-1, current job=none agentJob=none async=backup) +2023-04-08 20:37:20.894+0000: 431152: debug : qemuDomainObjBeginJobInternal:883 : Started job: async nested (async=backup vm=0x7fc0a4033a10 name=guest-1) +2023-04-08 20:37:20.894+0000: 431152: debug : qemuDomainObjEnterMonitorInternal:5872 : Entering monitor (mon=0x7fc0480048b0 vm=0x7fc0a4033a10 name=guest-1) +2023-04-08 20:37:20.894+0000: 431152: debug : qemuDomainObjExitMonitor:5902 : Exited monitor (mon=0x7fc0480048b0 vm=0x7fc0a4033a10 name=guest-1) +2023-04-08 20:37:20.894+0000: 431152: debug : qemuDomainObjEndJob:1135 : Stopping job: async nested (async=backup vm=0x7fc0a4033a10 name=guest-1) +2023-04-08 20:37:20.894+0000: 431152: debug : qemuDomainObjBeginJobInternal:831 : Starting job: job=async nested agentJob=none asyncJob=none (vm=0x7fc0a4033a10 name=guest-1, current job=none agentJob=none async=backup) +2023-04-08 20:37:20.894+0000: 431152: debug : qemuDomainObjBeginJobInternal:883 : Started job: async nested (async=backup vm=0x7fc0a4033a10 name=guest-1) +2023-04-08 20:37:20.894+0000: 431152: debug : qemuDomainObjEnterMonitorInternal:5872 : Entering monitor (mon=0x7fc0480048b0 vm=0x7fc0a4033a10 name=guest-1) +2023-04-08 20:37:20.894+0000: 431151: debug : virDomainDispose:348 : release domain 0x7fc014007240 guest-1 29ac5dd8-6eb9-4140-a9d1-cdcbae01ac0f +2023-04-08 20:37:20.894+0000: 431152: info : qemuMonitorSend:914 : QEMU_MONITOR_SEND_MSG: mon=0x7fc0480048b0 msg={"execute":"blockdev-add","arguments":{"driver":"file","filename":"/home/vm/domains/guest-1/disk.qcow2.1680986240","node-name":"libvirt-78-storage","auto-read-only":true,"discard":"unmap"},"id":"libvirt-39597737"} +2023-04-08 20:37:20.894+0000: 1882669: info : qemuMonitorIOWrite:402 : QEMU_MONITOR_IO_WRITE: mon=0x7fc0480048b0 buf={"execute":"blockdev-add","arguments":{"driver":"file","filename":"/home/vm/domains/guest-1/disk.qcow2.1680986240","node-name":"libvirt-78-storage","auto-read-only":true,"discard":"unmap"},"id":"libvirt-39597737"} +2023-04-08 20:37:20.895+0000: 1385058: debug : virDomainGetInfo:2444 : dom=0x7fc0ac001b80, (VM: name=guest-1, uuid=29ac5dd8-6eb9-4140-a9d1-cdcbae01ac0f), info=0x7fc009ffa880 +2023-04-08 20:37:20.895+0000: 1385058: debug : virDomainDispose:348 : release domain 0x7fc0ac001b80 guest-1 29ac5dd8-6eb9-4140-a9d1-cdcbae01ac0f +2023-04-08 20:37:20.895+0000: 431149: debug : virDomainGetBlockInfo:6284 : dom=0x7fc068024100, (VM: name=guest-1, uuid=29ac5dd8-6eb9-4140-a9d1-cdcbae01ac0f), info=0x7fc0b7100890, flags=0x0 +2023-04-08 20:37:20.895+0000: 431149: debug : qemuDomainObjBeginJobInternal:831 : Starting job: job=query agentJob=none asyncJob=none (vm=0x7fc0a4033a10 name=guest-1, current job=async nested agentJob=none async=backup) +2023-04-08 20:37:20.895+0000: 431149: debug : qemuDomainObjBeginJobInternal:867 : Waiting for job (vm=0x7fc0a4033a10 name=guest-1) +2023-04-08 20:37:20.895+0000: 431152: debug : qemuDomainObjExitMonitor:5902 : Exited monitor (mon=0x7fc0480048b0 vm=0x7fc0a4033a10 name=guest-1) +2023-04-08 20:37:20.895+0000: 431152: debug : qemuDomainObjEndJob:1135 : Stopping job: async nested (async=backup vm=0x7fc0a4033a10 name=guest-1) +2023-04-08 20:37:20.896+0000: 431152: debug : qemuDomainObjBeginJobInternal:831 : Starting job: job=async nested agentJob=none asyncJob=none (vm=0x7fc0a4033a10 name=guest-1, current job=none agentJob=none async=backup) +2023-04-08 20:37:20.896+0000: 431152: debug : qemuDomainObjBeginJobInternal:883 : Started job: async nested (async=backup vm=0x7fc0a4033a10 name=guest-1) +2023-04-08 20:37:20.896+0000: 431152: debug : qemuDomainObjEnterMonitorInternal:5872 : Entering monitor (mon=0x7fc0480048b0 vm=0x7fc0a4033a10 name=guest-1) +2023-04-08 20:37:20.896+0000: 431149: debug : qemuDomainObjBeginJobInternal:867 : Waiting for job (vm=0x7fc0a4033a10 name=guest-1) +2023-04-08 20:37:20.896+0000: 431152: info : qemuMonitorSend:914 : QEMU_MONITOR_SEND_MSG: mon=0x7fc0480048b0 msg={"execute":"blockdev-create","arguments":{"job-id":"create-libvirt-78-format","options":{"driver":"qcow2","file":"libvirt-78-storage","size":32212254720,"cluster-size":65536,"backing-file":"/home/vm/domains/guest-1/disk.qcow2","backing-fmt":"qcow2"}},"id":"libvirt-39597738"} +2023-04-08 20:37:20.896+0000: 1882669: info : qemuMonitorIOWrite:402 : QEMU_MONITOR_IO_WRITE: mon=0x7fc0480048b0 buf={"execute":"blockdev-create","arguments":{"job-id":"create-libvirt-78-format","options":{"driver":"qcow2","file":"libvirt-78-storage","size":32212254720,"cluster-size":65536,"backing-file":"/home/vm/domains/guest-1/disk.qcow2","backing-fmt":"qcow2"}},"id":"libvirt-39597738"} +2023-04-08 20:37:20.898+0000: 1882669: debug : qemuProcessHandleJobStatusChange:956 : job 'create-libvirt-78-format'(domain: 0x7fc0a4033a10,guest-1) state changed to 'created'(1) +2023-04-08 20:37:20.898+0000: 1882669: debug : qemuProcessHandleJobStatusChange:956 : job 'create-libvirt-78-format'(domain: 0x7fc0a4033a10,guest-1) state changed to 'running'(2) +2023-04-08 20:37:20.898+0000: 431152: debug : qemuDomainObjExitMonitor:5902 : Exited monitor (mon=0x7fc0480048b0 vm=0x7fc0a4033a10 name=guest-1) +2023-04-08 20:37:20.898+0000: 431152: debug : qemuDomainObjEndJob:1135 : Stopping job: async nested (async=backup vm=0x7fc0a4033a10 name=guest-1) +2023-04-08 20:37:20.899+0000: 431149: debug : qemuDomainObjBeginJobInternal:883 : Started job: query (async=backup vm=0x7fc0a4033a10 name=guest-1) +2023-04-08 20:37:20.899+0000: 431149: debug : qemuDomainObjEnterMonitorInternal:5872 : Entering monitor (mon=0x7fc0480048b0 vm=0x7fc0a4033a10 name=guest-1) +2023-04-08 20:37:21.432+0000: 1882669: debug : qemuProcessHandleAgentEOF:147 : Received EOF from agent on 0x7fc0a4033a10 'guest-1' +2023-04-08 20:37:21.432+0000: 1882669: debug : qemuMonitorIO:576 : Error on monitor Unable to read from monitor: Connection reset by peer mon=0x7fc0480048b0 vm=0x7fc0a4033a10 name=guest-1 +2023-04-08 20:37:21.432+0000: 1882669: debug : qemuMonitorIO:609 : Triggering error callback mon=0x7fc0480048b0 vm=0x7fc0a4033a10 name=guest-1 +2023-04-08 20:37:21.432+0000: 1882669: debug : qemuProcessHandleMonitorError:355 : Received error on 0x7fc0a4033a10 'guest-1' +2023-04-08 20:37:21.432+0000: 431149: debug : qemuMonitorSend:927 : Send command resulted in error Unable to read from monitor: Connection reset by peer mon=0x7fc0480048b0 vm=0x7fc0a4033a10 name=guest-1 +2023-04-08 20:37:21.433+0000: 431149: debug : qemuDomainObjExitMonitor:5902 : Exited monitor (mon=0x7fc0480048b0 vm=0x7fc0a4033a10 name=guest-1) +2023-04-08 20:37:21.433+0000: 1882669: debug : qemuMonitorIO:576 : Error on monitor Unable to read from monitor: Connection reset by peer mon=0x7fc0480048b0 vm=0x7fc0a4033a10 name=guest-1 +2023-04-08 20:37:21.433+0000: 431149: debug : qemuDomainObjEndJob:1135 : Stopping job: query (async=backup vm=0x7fc0a4033a10 name=guest-1) +2023-04-08 20:37:21.433+0000: 1882669: debug : qemuMonitorIO:598 : Triggering EOF callback mon=0x7fc0480048b0 vm=0x7fc0a4033a10 name=guest-1 +2023-04-08 20:37:21.433+0000: 1882669: debug : qemuProcessHandleMonitorEOF:310 : Received EOF on 0x7fc0a4033a10 'guest-1' +2023-04-08 20:37:21.433+0000: 431149: debug : virDomainDispose:348 : release domain 0x7fc068024100 guest-1 29ac5dd8-6eb9-4140-a9d1-cdcbae01ac0f +2023-04-08 20:37:21.433+0000: 620333: debug : qemuProcessKill:7931 : vm=0x7fc0a4033a10 name=guest-1 pid=1882665 flags=0x1 +2023-04-08 20:37:21.633+0000: 620333: debug : qemuDomainObjBeginJobInternal:831 : Starting job: job=destroy agentJob=none asyncJob=none (vm=0x7fc0a4033a10 name=guest-1, current job=none agentJob=none async=backup) +2023-04-08 20:37:21.633+0000: 620333: debug : qemuDomainObjBeginJobInternal:883 : Started job: destroy (async=backup vm=0x7fc0a4033a10 name=guest-1) +2023-04-08 20:37:21.634+0000: 620333: debug : processMonitorEOFEvent:4025 : Monitor connection to 'guest-1' closed without SHUTDOWN event; assuming the domain crashed +2023-04-08 20:37:21.634+0000: 620333: debug : qemuProcessStop:8014 : Shutting down vm=0x7fc0a4033a10 name=guest-1 id=814 pid=1882665, reason=crashed, asyncJob=none, flags=0x0 +2023-04-08 20:37:21.634+0000: 620333: debug : qemuDomainLogAppendMessage:6740 : Append log message (vm='guest-1' message='2023-04-08 20:37:21.634+0000: shutting down, reason=crashed +2023-04-08 20:37:22.617+0000: 620333: debug : qemuProcessKill:7931 : vm=0x7fc0a4033a10 name=guest-1 pid=1882665 flags=0x5 +2023-04-08 20:37:22.617+0000: 620333: debug : qemuDomainCleanupRun:7321 : driver=0x7fc07015c730, vm=guest-1 +2023-04-08 20:37:22.617+0000: 620333: debug : qemuProcessAutoDestroyRemove:8416 : vm=guest-1 +2023-04-08 20:37:22.617+0000: 620333: debug : virCloseCallbacksUnset:145 : vm=guest-1, uuid=29ac5dd8-6eb9-4140-a9d1-cdcbae01ac0f, cb=0x7fc09e3f9ba0 +``` + +If you need any further information just let me know. As per request, ping @pipo.sk +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1589 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1589 new file mode 100644 index 000000000..d39ad2bb3 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1589 @@ -0,0 +1,10 @@ +Crash when using qemu 8.0.0 version tcg mode +Description of problem: +Can I no longer use qemu in tcg mode? +When operating in tcg mode in all versions of 8.0.0, a crash occurs on the booting screen and the window closes (the window stops responding before closing). +Steps to reproduce: +1. Run qemu with -accel tcg option +2. enter the boot screen +3. The screen freezes and the window closes after a few seconds (at which point it becomes unresponsive) +Additional information: +I have not checked whether the same symptom occurs in Linux, and it occurs in all versions of 8.0.0 for Windows. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/159 b/gitlab/issues_text/target_missing/host_missing/accel_missing/159 new file mode 100644 index 000000000..da9bd8a68 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/159 @@ -0,0 +1 @@ +qemu-nbd -l and -s options don't work together diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1590 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1590 new file mode 100644 index 000000000..7f2d881b3 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1590 @@ -0,0 +1,121 @@ +Regression: ARMv8M secure mode debugging non-functional since ~v7.2.0 +Description of problem: +Prior to qemu commit 4a35855682cebb89f9630b07aa9fd37c4e8c733b, both semihosting printf calls and debugging via gdb work as expected. + +Builds of qemu containing commit 4a35855682cebb89f9630b07aa9fd37c4e8c733b do not produce any semihosting output and are not debuggable via gdb. +Steps to reproduce: +1. Run ``qemu-system-arm -machine mps2-an505 -nographic -semihosting -kernel build/mps2_an505_cm33_blink_demo.elf`` with qemu v7.1.0, note the "blinking" print to the console once a second. +2. Run ``qemu-system-arm -machine mps2-an505 -nographic -semihosting -kernel build/mps2_an505_cm33_blink_demo.elf`` with qemu v7.2.0, note that no messages are printed to the console. +3. Run ``qemu-system-arm -machine mps2-an505 -nographic -semihosting -kernel build/mps2_an505_cm33_blink_demo.elf -S -s`` and attach gdb with the following gdbinit file. +Additional information: +Log of successful gdb session with the attached patch on top of qemu master branch: +``` +% arm-none-eabi-gdb build/mps2_an505_cm33_blink_demo.elf +GNU gdb (Arm GNU Toolchain 12.2.MPACBTI-Rel1 (Build arm-12-mpacbti.34)) 13.1.90.20230307-git +Copyright (C) 2023 Free Software Foundation, Inc. +License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> +This is free software: you are free to change and redistribute it. +There is NO WARRANTY, to the extent permitted by law. +Type "show copying" and "show warranty" for details. +This GDB was configured as "--host=x86_64-apple-darwin19.6.0 --target=arm-none-eabi". +Type "show configuration" for configuration details. +For bug reporting instructions, please see: +<https://bugs.linaro.org/>. +Find the GDB manual and other documentation resources online at: + <http://www.gnu.org/software/gdb/documentation/>. + +For help, type "help". +Type "apropos word" to search for commands related to "word"... +Reading symbols from build/mps2_an505_cm33_blink_demo.elf... +The target architecture is set to "armv8-m.main". +Reset_Handler () at /FreeRTOS/FreeRTOS/Demo/ARM_MPS/startup.c:172 +172 { +Section .privileged_functions, range 0x10000000 -- 0x10008000: matched. +Section .text, range 0x10008000 -- 0x10019c18: matched. +Section .rodata, range 0x10019c18 -- 0x1001b270: matched. +Section .ARM.exidx, range 0x1001b270 -- 0x1001b278: matched. +Section .copy.table, range 0x1001b278 -- 0x1001b284: matched. +Section .data, range 0x1001b28c -- 0x1001bb90: matched. +Section .ram_vectors, range 0x1001bb90 -- 0x1001bdd0: matched. +Section .zero.table, range 0x1001b284 -- 0x1001b28c: matched. +Breakpoint 1 at 0x10009900: file /FreeRTOS/Demo/ARM_MPS/fault_handlers.c, line 494. +(gdb) s +174 asm volatile +(gdb) s +189 init_data_sections(); +(gdb) s +init_data_sections () at /FreeRTOS/FreeRTOS/Demo/ARM_MPS/startup.c:99 +99 for( pCopyTable = &__copy_table_start__; pCopyTable <= &__copy_table_end__; pCopyTable++ ) +(gdb) s +101 for( dataIndex = 0; dataIndex < pCopyTable->uxLen; dataIndex++ ) +(gdb) info locals +pCopyTable = 0x1001b278 +dataIndex = 0 +(gdb) print /x *0xE000ED08 +$1 = 0x10000000 +``` + +Log of an unsuccessful gdb session with qemu v7.2.0 +``` +pbartell@147dda7342a9 ARM_MPS % arm-none-eabi-gdb build/mps2_an505_cm33_blink_demo.elf +GNU gdb (Arm GNU Toolchain 12.2.MPACBTI-Rel1 (Build arm-12-mpacbti.34)) 13.1.90.20230307-git +Copyright (C) 2023 Free Software Foundation, Inc. +License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> +This is free software: you are free to change and redistribute it. +There is NO WARRANTY, to the extent permitted by law. +Type "show copying" and "show warranty" for details. +This GDB was configured as "--host=x86_64-apple-darwin19.6.0 --target=arm-none-eabi". +Type "show configuration" for configuration details. +For bug reporting instructions, please see: +<https://bugs.linaro.org/>. +Find the GDB manual and other documentation resources online at: + <http://www.gnu.org/software/gdb/documentation/>. + +For help, type "help". +Type "apropos word" to search for commands related to "word"... +Reading symbols from build/mps2_an505_cm33_blink_demo.elf... +The target architecture is set to "armv8-m.main". +Reset_Handler () at /FreeRTOS/FreeRTOS/Demo/ARM_MPS/startup.c:172 +172 { +Section .privileged_functions, range 0x10000000 -- 0x10008000: MIS-MATCHED! +Section .text, range 0x10008000 -- 0x10019c18: MIS-MATCHED! +Section .rodata, range 0x10019c18 -- 0x1001b270: MIS-MATCHED! +Section .ARM.exidx, range 0x1001b270 -- 0x1001b278: MIS-MATCHED! +Section .copy.table, range 0x1001b278 -- 0x1001b284: MIS-MATCHED! +Section .data, range 0x1001b28c -- 0x1001bb90: MIS-MATCHED! +Section .ram_vectors, range 0x1001bb90 -- 0x1001bdd0: MIS-MATCHED! +Section .zero.table, range 0x1001b284 -- 0x1001b28c: MIS-MATCHED! +warning: One or more sections of the target image does not match +the loaded file + +Breakpoint 1 at 0x10009900: file /FreeRTOS/FreeRTOS/Demo/ARM_MPS/fault_handlers.c, line 494. +(gdb) s +Reset_Handler () at /FreeRTOS/FreeRTOS/Demo/ARM_MPS/startup.c:174 +174 asm volatile +(gdb) s +Reset_Handler () at /FreeRTOS/FreeRTOS/Demo/ARM_MPS/startup.c:189 +189 init_data_sections(); +(gdb) s +init_data_sections () at /FreeRTOS/FreeRTOS/Demo/ARM_MPS/startup.c:95 +95 { +(gdb) s +init_data_sections () at /FreeRTOS/FreeRTOS/Demo/ARM_MPS/startup.c:99 +99 for( pCopyTable = &__copy_table_start__; pCopyTable <= &__copy_table_end__; pCopyTable++ ) +(gdb) info locals +pCopyTable = <error reading variable pCopyTable (Cannot access memory at address 0x381fffdc)> +dataIndex = <error reading variable dataIndex (Cannot access memory at address 0x381fffd8)> +(gdb) print /x *0xE000ED08 +$1 = 0x0 +(gdb) quit +``` + +.gdbinit file: +``` +set architecture armv8-m.main +target extended-remote :1234 +compare-sections +break HardFault_Handler +``` + +[mps2_an505_cm33_blink_demo.elf](/uploads/c86e086b00651a8d5392857b9e4a2c4d/mps2_an505_cm33_blink_demo.elf) +[target-arm-Fix-debugging-of-ARMv8M-Secure-code.patch](/uploads/5735d5f7d7b15dbbeb0c2d214a46c1a8/target-arm-Fix-debugging-of-ARMv8M-Secure-code.patch) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1593 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1593 new file mode 100644 index 000000000..dd64fce44 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1593 @@ -0,0 +1,7 @@ +SLIRP hostfwd ignores bind address and uses `INADDR_ANY` +Description of problem: +When using `-netdev hostfwd=`..., qemu SLIRP uses `INADDR_ANY` instead of any bind address provided by the user. As a result, even if the user specifies to listen only on localhost (e.g. `-netdev user,hostfwd=tcp:127.0.0.1:22-:22`), qemu will listen on `*.*`. This is a potential security issue (as it may unexpectedly expose the guest to internet or local network traffic). +Additional information: +The bug is here: https://gitlab.com/qemu-project/qemu/-/blob/master/net/slirp.c#L777 + +Rather than hardcoding `INADDR_ANY`, qemu should respect the user-defined bind address. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1594 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1594 new file mode 100644 index 000000000..24018dc2b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1594 @@ -0,0 +1,21 @@ +Wrong cpu information is still received when using whpx acceleration. +Description of problem: +I received wrong information the other day and registered an issue, but now the latest version has not been fixed and is delivering the same wrong information. +If not fixed, Windows Home version (Windows 11 Home version) cannot run more than 5 cores with whpx acceleration. +(If you boot after setting more than 5 cores, an incorrect CPU parameter BSOD occurs during booting, and Windows 11 home version seems to allow up to 4 physical CPUs..) +* Even if you explicitly give -smp cores=n,threads=1,sockets=1 and boot, it is ignored and recognized as a PC with n 1-core CPUs. +Steps to reproduce: +1. Run qemu with -accel whpx option +2. Check CPU information after booting is complete +3. Check the same CPU information after booting from a physical PC and other virtualization software (VMware, Virtual Box, etc.) +4. It has been confirmed that the number of physical CPUs and the number of cores per CPU are different from other virtualization software or physical PCs. (For example, when setting 4 cores, it is recognized as 1CPU 4Core in other virtualization software, but as 4CPU 1Core in qemu operated with whpx acceleration) +Additional information: +* The CPU was set to 4 cores, and the image was taken as a screenshot of the information recognized as the 4th processor by Linux. +> Linux CPU information booted from qemu (with whpx acceleration) +execution statement : qemu-system-x86_64 -M q35 -smp cores=4,threads=1,sockets=1 -m 4g -display sdl -drive file=test.vdi,id=disk,if=none -device ahci,id=ahci -device ide-hd,drive=disk,bus=ahci.0 -accel whpx (or 'qemu-system-x86_64 -M q35 -smp 4 -m 4g -display sdl -drive file=test.vdi,id=disk,if=none -device ahci,id=ahci -device ide-hd,drive=disk,bus=ahci.0 -accel whpx') + + + +> Linux CPU information booted from other virtualization software (Virtual Box) + + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1595 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1595 new file mode 100644 index 000000000..24b2547bb --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1595 @@ -0,0 +1,29 @@ +CPU boot sometimes fails on big.LITTLE CPUs with varying cache sizes +Description of problem: +The RK3588 SoC has three core clusters; one with A55 cores, and the other two have A76 cores. The big cores have more L2 cache than the little cores, so the value of `CCSIDR` depends on the core that it is read from. + +In `write_list_to_kvmstate`, QEMU attempts to use `KVM_SET_ONE_REG` with an ID for `KVM_REG_ARM_DEMUX_ID_CCSIDR`, trying to set `CCSIDR` to a previously read value. + +Normally, that works fine, but if the host kernel has moved QEMU from one core cluster to the other, then the value will be different and `demux_c15_set` will return `EINVAL`, causing the entire `arm_set_cpu_on` to fail, and the guest kernel to print an error. + +https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm64/kvm/sys_regs.c?h=v6.2#n2827 + +I tried changing the condition for the `ok = false` line in `write_list_to_kvmstate` to `ret && r.id >> 8 != 0x60200000001100`. This causes all CPUs to initialize correctly in the guest, but obviously that's a hack. + +I assume that `CCSIDR` not being uniform across all CPUs means that the guest's copy of `CCSIDR` may be wrong, and so cache maintenance operations may not act on the entire cache. I do not know whether that could actually cause problems. Will QEMU need to find the maximum cache size across all CPUs and present that to guests? +Steps to reproduce: +On a SoC where big and little cores have different cache sizes (e.g. RK3588): + +```text +$ qemu-system-aarch64 -M virt -accel kvm -cpu host -smp 4 -nographic -kernel arch/arm64/boot/Image -append quiet +[ 0.001399][ T1] psci: failed to boot CPU1 (-22) +[ 0.001407][ T1] CPU1: failed to boot: -22 +[ 0.001685][ T1] psci: failed to boot CPU2 (-22) +[ 0.001691][ T1] CPU2: failed to boot: -22 +[ 0.001809][ T1] psci: failed to boot CPU3 (-22) +[ 0.001814][ T1] CPU3: failed to boot: -22 +``` + +The error is not always printed, because it depends on which core cluster the processes are scheduled on. + +Using `taskset -c 0-3` or `taskset -c 4-7` to force QEMU to stick to the little or big cores respectively makes the bug not reproduce. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1596 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1596 new file mode 100644 index 000000000..31c2c3665 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1596 @@ -0,0 +1,20 @@ +VNC console with 4K resolutions is cut off on the right side and mouse coordinates are offset (or horizontal res greater than 2600-3000 pixels) +Description of problem: +For some reason when connecting to the VNC console of a QEMU VM, when you use a resolution that has its horizontal size of about 3000 pixels or more, it gets cut off by about 1/4 of the screen from the right, and the mouse position is offset by that value towards the left. See image for explanation: + + +Steps to reproduce: +1. Create a Fedora 37 VM +2. Use `virtio-vga-gl` and `egl-headless` +3. Set the resolution to 4K (3840x2160) or anything with the horizontal resolution greater than 3000 pixels +4. Use Windows to connect to the VNC console. Issue happens with TightVNC Viewer and RealVNC Viewer +Additional information: +I also tried `-device virtio-vga-gl,edid=off,xres=3840,yres=2160`. Same result, but `edid=off` helps to make 2560x1600 appear, making it bearable. + +This also happens with Wayland and Xorg. + +Please note that while it's possible to use Gnome's Screen Sharing (RDP/VNC) options, as well as NoMachine or other options, this is an undesirable behavior in QEMU's VNC server/console that should be fixed (and can, the VNC protocol perfectly supports 4K without issues) + +Not to mention that, at least in my use case, the VNC console is faster than the alternatives, even SPICE (connecting from Windows is barely unusable at 4K res - it's a bliss from Linux. Both cases from a remote machine in the same LAN, but that is unrelated to this bug). + +I would happily try different use cases to try to help nail down this bug :smile: diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1597 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1597 new file mode 100644 index 000000000..9259c3b4a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1597 @@ -0,0 +1,56 @@ +Intel Arc A-Series GPUs VFIO passthrough no video out +Description of problem: +Once the VM is booted, the screen goes blank. +Steps to reproduce: +1. Passthough any Intel Arc A (Alchemist) series video card. +2. Boot VM. +3. Screen goes blank. +Additional information: +I have startup and shutdown scripts that detach and reattach the card and these scripts work fine if I test them alone. It's only when I start the VM that issue presents itself. + + + +kernel command line: + +``` +amd_iommu=on iommu=pt rd.driver.pre=vfio-pci pci=realloc iommu=1 i915.force_probe=* + +``` + +startup script: + +``` +#!/bin/bash +# Helpful to read output when debugging +set -x + +# Load the config file with our environmental variables +source "/etc/libvirt/hooks/kvm.conf" +source "/etc/libvirt/hooks/vmPreBootSetup" + +cpuPerf + +# Stop your display manager. If you're on kde it'll be sddm.service. Gnome users should use 'killall gdm-x-session' instead +systemctl stop gdm.service + +# Unbind VTconsoles +echo 0 > /sys/class/vtconsole/vtcon0/bind +echo 0 > /sys/class/vtconsole/vtcon1/bind + +# Avoid a race condition by waiting a couple of seconds. This can be calibrated to be shorter or longer if required for your system +sleep 2 + +modprobe -r drm_buddy intel_gtt video drm_display_helper cec ttm i915 + +# Unbind the GPU from display driver +virsh nodedev-detach $VIRSH_GPU_VIDEO +virsh nodedev-detach $VIRSH_GPU_AUDIO + +# Load VFIO kernel module +modprobe vfio +modprobe vfio_pci +modprobe vfio_iommu_type1 + +sleep 5s ; systemctl restart connman.service + +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1598 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1598 new file mode 100644 index 000000000..f1f5e46f8 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1598 @@ -0,0 +1,58 @@ +vfio-pci - Intel Arc DG2 - host errors +Description of problem: +The host continues to respond (slowly) after the VM is shutdown. Speeds back up to normal after about an hour. However, a reboot is required to get the host to operate normally. + +When shutting down the VM, the host starts to display the following messages in dmesg: + +[Thu Apr 13 01:30:47 2023] vfio-pci 0000:18:00.0: not ready 1023ms after FLR; waiting +[Thu Apr 13 01:30:49 2023] vfio-pci 0000:18:00.0: not ready 2047ms after FLR; waiting +[Thu Apr 13 01:30:52 2023] vfio-pci 0000:18:00.0: not ready 4095ms after FLR; waiting +[Thu Apr 13 01:30:57 2023] vfio-pci 0000:18:00.0: not ready 8191ms after FLR; waiting +[Thu Apr 13 01:31:06 2023] vfio-pci 0000:18:00.0: not ready 16383ms after FLR; waiting +[Thu Apr 13 01:31:25 2023] vfio-pci 0000:18:00.0: not ready 32767ms after FLR; waiting +[Thu Apr 13 01:31:59 2023] vfio-pci 0000:18:00.0: not ready 65535ms after FLR; giving up +[Thu Apr 13 01:32:11 2023] vfio-pci 0000:18:00.0: not ready 1023ms after bus reset; waiting +[Thu Apr 13 01:32:13 2023] vfio-pci 0000:18:00.0: not ready 2047ms after bus reset; waiting +[Thu Apr 13 01:32:16 2023] vfio-pci 0000:18:00.0: not ready 4095ms after bus reset; waiting +[Thu Apr 13 01:32:21 2023] vfio-pci 0000:18:00.0: not ready 8191ms after bus reset; waiting +[Thu Apr 13 01:32:31 2023] vfio-pci 0000:18:00.0: not ready 16383ms after bus reset; waiting +[Thu Apr 13 01:32:48 2023] vfio-pci 0000:18:00.0: not ready 32767ms after bus reset; waiting +[Thu Apr 13 01:33:22 2023] vfio-pci 0000:18:00.0: not ready 65535ms after bus reset; giving up +Steps to reproduce: +1. Shutdown VM. +Additional information: +I have startup and shutdown scripts that detach and reattach the card and these scripts work fine if I test them alone. It's only when I shutdown the VM that issue presents itself. + +revert.sh + +``` +#!/bin/bash +set -x + +systemctl reboot # to workaround host lockup on shutdown + +# Load the config file with our environmental variables +source "/etc/libvirt/hooks/kvm.conf" +source "/etc/libvirt/hooks/vmPreBootSetup" + +cpuSchedutil + +# Unload VFIO-PCI Kernel Driver +modprobe -r vfio_pci +modprobe -r vfio_iommu_type1 +modprobe -r vfio + +# Re-Bind GPU to our display drivers +virsh nodedev-reattach $VIRSH_GPU_VIDEO +virsh nodedev-reattach $VIRSH_GPU_AUDIO + +#modprobe drm_buddy intel_gtt video drm_display_helper cec ttm i915 + +# Restart Display Manager +systemctl restart sddm.service +``` + + + +Full dmesg log: +[vfio_13_april_2023.txt](/uploads/5d5b642595c53cabb3c3608c07d59eb3/vfio_13_april_2023.txt) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1599 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1599 new file mode 100644 index 000000000..27e39587f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1599 @@ -0,0 +1,9 @@ +7.2.1 - Windows installer +Description of problem: +Please release windows installer for new stable version 7.2.1 in + +https://www.qemu.org/download/ +Steps to reproduce: + +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/160 b/gitlab/issues_text/target_missing/host_missing/accel_missing/160 new file mode 100644 index 000000000..aff60e319 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/160 @@ -0,0 +1 @@ +Record/replay example does not work diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1601 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1601 new file mode 100644 index 000000000..b5bea7c4b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1601 @@ -0,0 +1,80 @@ +QEMU Guest Agent (qga) high CPU usage (1 core at 100%). May happen with guest-network-get-interfaces. Strace says: EAGAIN (Resource temporarily unavailable) +Description of problem: +I have a VM that has the QEMU guest agent installed. I use the QGA to get information periodically about the network interfaces. Meaning, I execute the `guest-network-get-interfaces` in a period around 1-2 seconds each. + +After a while (maybe a day or so) the QGA seems to lock up with the CPU at 100% in 1 core. It does not reply to more commands, and restarting the service sometimes doesn't work, so a hard reboot it is. + +`dmesg` doesn't show anything useful/relevant. When attempting to edit the `qemu-guest-agent.service` and append `/usr/bin/strace` to it, I can get this in a loop: + +``` +strace[114154]: write(4, "{\"return\": [{\"name\": \"lo\", \"ip-a"..., 2047) = -1 EAGAIN (Resource temporarily unavailable) +strace[114154]: write(4, "{\"return\": [{\"name\": \"lo\", \"ip-a"..., 2047) = -1 EAGAIN (Resource temporarily unavailable) +strace[114154]: write(4, "{\"return\": [{\"name\": \"lo\", \"ip-a"..., 2047) = -1 EAGAIN (Resource temporarily unavailable) +strace[114154]: write(4, "{\"return\": [{\"name\": \"lo\", \"ip-a"..., 2047) = -1 EAGAIN (Resource temporarily unavailable) +strace[114154]: write(4, "{\"return\": [{\"name\": \"lo\", \"ip-a"..., 2047) = -1 EAGAIN (Resource temporarily unavailable) +strace[114154]: write(4, "{\"return\": [{\"name\": \"lo\", \"ip-a"..., 2047) = -1 EAGAIN (Resource temporarily unavailable) +strace[114154]: write(4, "{\"return\": [{\"name\": \"lo\", \"ip-a"..., 2047) = -1 EAGAIN (Resource temporarily unavailable) +strace[114154]: write(4, "{\"return\": [{\"name\": \"lo\", \"ip-a"..., 2047) = -1 EAGAIN (Resource temporarily unavailable) +``` + +I don't have more knowledge to debug this further. I can help to provide more info if some guidance is provided. + +**Don't know if it helps/affects**, but the guest VM is running Docker with around 10 containers or so, so when QGA works, I get around 18 network interfaces, counting loopback, docker `veth`s and `br` interfaces. +Steps to reproduce: +1. Create a VM with Fedora 37 +2. Install the QEMU Guest Agent +3. Call `guest-network-get-interfaces` in a loop every 1-2 seconds (after it finishes) through QGA using the unix socket using the provided python script, called as: `python qga.py --socket /run/test-vm-108.qga '{ "execute": "guest-network-get-interfaces" }'` +4. Eventually, the guest agent will lock up at 100% CPU usage on 1 core +Additional information: +Python script used to call QGA: +``` +import argparse +import socket +import sys + +def main(): + buf_size = 1024 + timeout_secs = .5 + + parser = argparse.ArgumentParser() + parser.add_argument('--socket', required=True, help='Path to Unix socket') + parser.add_argument('request', help='Request to send') + args = parser.parse_args() + + unix_socket_path = args.socket + request = args.request + + try: + with socket.socket(socket.AF_UNIX, socket.SOCK_STREAM) as sock: + sock.settimeout(timeout_secs) + sock.connect(unix_socket_path) + + request_bytes = request.encode('utf-8') + sock.sendall(request_bytes) + + response_bytes = b'' + received_bytes = sock.recv(buf_size) + response_bytes += received_bytes + + sock.setblocking(False) + while True: + try: + received_bytes = sock.recv(buf_size) + if not received_bytes: + break + response_bytes += received_bytes + except (BlockingIOError, TimeoutError): + break + except (FileNotFoundError, ConnectionRefusedError): + sock.close() + sys.exit() + + response = response_bytes.decode('utf-8').strip() + print(response) + + except (TimeoutError, FileNotFoundError, BlockingIOError, ConnectionRefusedError): + sys.exit() + +if __name__ == "__main__": + main() +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1602 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1602 new file mode 100644 index 000000000..fe21b63d5 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1602 @@ -0,0 +1,7 @@ +github.com/qemu/qemu has been out of sync with GitLab since Mar 23, 2023 +Description of problem: +https://github.com/qemu/qemu has been out of sync with https://gitlab.com/qemu-project/qemu since Mar 23, 2023. +Steps to reproduce: +See https://github.com/qemu/qemu +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1604 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1604 new file mode 100644 index 000000000..6bb1146ff --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1604 @@ -0,0 +1,63 @@ +Get wrong rom when loading 2 different firmware to 2 cpu. +Description of problem: +HI, I'm trying to model a machine with 2 cortex-m7 cpu. The 2 CPUs have their own address spaces. +and when loading rom to init sp and pc, the CPU1 would load the rom of CPU0, because it seems not check +address space here. +```c +void *rom_ptr_for_as(AddressSpace *as, hwaddr addr, size_t size) +{ + /* + * Find any ROM data for the given guest address range. If there + * is a ROM blob then return a pointer to the host memory + * corresponding to 'addr'; otherwise return NULL. + * + * We look not only for ROM blobs that were loaded directly to + * addr, but also for ROM blobs that were loaded to aliases of + * that memory at other addresses within the AddressSpace. + * + * Note that we do not check @as against the 'as' member in the + * 'struct Rom' returned by rom_ptr(). The Rom::as is the + * AddressSpace which the rom blob should be written to, whereas + * our @as argument is the AddressSpace which we are (effectively) + * reading from, and the same underlying RAM will often be visible + * in multiple AddressSpaces. (A common example is a ROM blob + * written to the 'system' address space but then read back via a + * CPU's cpu->as pointer.) This does mean we might potentially + * return a false-positive match if a ROM blob was loaded into an + * AS which is entirely separate and distinct from the one we're + * querying, but this issue exists also for rom_ptr() and hasn't + * caused any problems in practice. + */ + FlatView *fv; + void *rom; + hwaddr len_unused; + FindRomCBData cbdata = {}; + + /* Easy case: there's data at the actual address */ + rom = rom_ptr(addr, size); + if (rom) { + return rom; + } +``` +Steps to reproduce: +1. create a machine with 2 cortex-m7 cores and their own rom/ram. +2. Set different ram size for them. for example, cpu0 ram size:0x40000, cpu1 ram size:0x20000 +3. build firmware of 2 cpu. make sure the init SP(local at 0x0) is set to the top the ram. +4. use command: +``` +./qemu-system-arm -M mymachine -smp 2 \ +-device loader,file=./cpu0.elf,addr=0x0,cpu-num=0 \ +-device loader,file=./cpu1.elf,addr=0x0,cpu-num=1 \ +-serial stdio -serial tcp::5678,server=on,wait=off +``` +to start this machine. + +5. the cpu1 will panic when it try to use stack: +`qemu-system-arm: ../target/arm/cpu.h:2396: arm_is_secure_below_el3: Assertion failed.` + + +Sorry that I'm not sure whether this is an issue or I did something wrong. So post it here. +For local fix this problem, I add a func `rom_ptr_wit_as(addr,size,as)` to find a rom with addresspace check. +Is it proper? +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1605 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1605 new file mode 100644 index 000000000..3fd77be02 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1605 @@ -0,0 +1,38 @@ +On windows, 2nd kind vhdx-dyn bug, crash on Unexpected error in bdrv_check_qiov_request() in io.c +Description of problem: +On windows, 2nd kind vhdx-dyn bug, crash on Unexpected error in bdrv_check_qiov_request() in io.c +- qemu windows crashes during data copy + ```D:\tmpq\qemu\8.0.0-rc4\qemu\qemu-system-x86_64 -cpu qemu64 -m 4096 -machine "type=q35,kernel-irqchip=off" -accel whpx -smp "sockets=1,cores=8,threads=1" -bios D:\vstorage\win_m01_edk2-x8_64.fd -boot c -drive "index=0,if=virtio,media=disk,format=raw,file=D:\vstorage\m01_bootnoefi.raw.img" -drive "index=1,if=virtio,media=disk,format=raw,file=F:\m01_lnx.raw.img.vtoy" -drive "index=2,if=virtio,media=disk,format=vhdx,file=F:\gkpics01.vhdx" -drive "index=3,if=virtio,media=disk,format=vhdx,file=D:\test\sgdata.vhdx" -display sdl -vga virtio -rtc base=utc -netdev user,id=vmnic1,net=192.168.20.0/24,dns=192.168.20.3,dhcpstart=192.168.20.15,hostfwd=tcp::9551-:22 -device virtio-net,netdev=vmnic1 -chardev qemu-vdagent,id=ch1,name=vdagent,clipboard=on -device virtio-serial -device virtserialport,chardev=ch1,id=ch1,name=com.redhat.spice.0 -qmp "tcp:127.0.0.1:5955,server,nowait"``` + ``` ``` + ```Windows Hypervisor Platform accelerator is operational``` + ```Unexpected error in bdrv_check_qiov_request() at ../../../block/io.c:815:``` + ```D:\tmpq\qemu\8.0.0-rc4\qemu\qemu-system-x86_64.exe: offset is negative: -28983296``` + +. +- The **LINE NUMBER** : https://gitlab.com/qemu-project/qemu/-/blob/master/block/io.c#L815 +- qemu setup is ```qemu-w64-setup-20230414.exe ``` +Steps to reproduce: +1. have fresh vhdx ready create a vhdx in ```diskmgmt``` (also attached to [comment](https://gitlab.com/qemu-project/qemu/-/issues/727#note_1346341805)) +2. have vhdx with synthetic generated data ready (see process to generate sgdata in [comment](https://gitlab.com/qemu-project/qemu/-/issues/727#note_739930694) ) +3. start qemu, login, open terminal +4. Inside VM, start a terminal window, sudo root, +5. open```gdisk /dev/vdc``` create a ntfs partition +6. format as ntfs: ```mkfs.ntfs -Q -L fs_gkpics01 /dev/vdc1``` +7. mount the partition ```mount -t ntfs3 /dev/vdc1 /mnt/a -o uid=1000,gid=1000,defaults,umask=0002``` +8. mount the partition ```mount -t ntfs3 /dev/vdd2 /mnt/b -o uid=1000,gid=1000,defaults,umask=0002``` +9. In a user login, do rsync data-copy step + ```( fl="photos001" ; src="/mnt/b/sgdata" ; dst="/mnt/a" ; sdate=`date` ; echo "$sdate" ; cd "$src" ; rsync -avH "$fl" "$dst" ; echo "$sdate" ; date ; sudo -u gana DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus DISPLAY=:0.0 -- notify-send "$src/$fl" "rsync $src/$fl" )``` + + +The bug is easily reproducible. +The moment of the crash may seems spurious, but is almost certainly bound to happen. +When it happens, it can be seen to be the same error message. +Sometimes the crash happens in ```gdisk``` step, sometimes during ```mkfs.ntfs``` sometimes partway through the ```rsync```-copy, not very long into it. +Additional information: +- This has been happening for some time. I haven't used/tested vhdx much in windows much since 7.0.0 on account of other corruption bugs/lack of dependability. +- This does not happen in Linux, as tested in #727 +- The fix of #727 is unrelated to this. It doesn't have the same feel/reproduction intuitive-signature. + - Happens before (on doing the same test) + - on 8.0.0-rc1 (line number of io.c there is L811) + - on 7.2.0 (line no of io.c there is [L971](https://gitlab.com/qemu-project/qemu/-/blob/ace5a161ea1c09d8eaa8b2a717528457dc924e83/block/io.c#L971)) +- It may be caused by other changes going into block code since 7.0 . diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1607 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1607 new file mode 100644 index 000000000..619148659 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1607 @@ -0,0 +1 @@ +QEMU calls glXMakeCurrent which is current in another thread when running VM with SDL diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/161 b/gitlab/issues_text/target_missing/host_missing/accel_missing/161 new file mode 100644 index 000000000..995c98586 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/161 @@ -0,0 +1 @@ +virtio-scsi gives improper discard sysfs entries diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1610 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1610 new file mode 100644 index 000000000..4a49de47a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1610 @@ -0,0 +1 @@ +support of directX in windows guest diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1611 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1611 new file mode 100644 index 000000000..eb4707816 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1611 @@ -0,0 +1 @@ +How to test rutabaga_gfx/gfxstream patches diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1613 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1613 new file mode 100644 index 000000000..7607c7365 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1613 @@ -0,0 +1,37 @@ +Enhanced SuperSpeed Isochronous Endpoints with high-bandwidth pipes not working (Webcams and Microphones) +Description of problem: +I have encountered an issue with QEMU when forwarding HD webcams and microphones in SuperSpeed mode. + +When passing the USB webcam "Logitech BRIO Ultra HD Webcam" to the guest using USB HighSpeed mode, all pixel formats and video modes work as expected. However, when using SuperSpeed mode, only the MJPEG format operates at low resolutions. I have attached a [USB_Webcam_Testing_Truth_Table.pdf](/uploads/309d493989da1164198af0b315012fb1/USB_Webcam_Testing_Truth_Table.pdf) that displays the functioning modes. + +This issue arises with both qemu-xhci and nec-usb-xhci xHCI implementations, as well as with usb-host and usb-redir. + +Upon tracing and comparing the USB packets from the host and guest systems, I discovered an issue with the isochronous endpoint configurations supporting "high bandwidth" pipes (e.g., SS Companion Descriptor with bMaxBurst > 0). I created three pcap files to illustrate the problem: +1. [host-libusb.pcapng](/uploads/18a66948dc6dc10ff68b7f55d70fa209/host-libusb.pcapng) +2. [qemu-guest.pcapng](/uploads/b616507f2f7c1c042a9d085dc3af579f/qemu-guest.pcapng) +3. [host-native.pcapng](/uploads/279aa7f264a75a77203fa7bf6c5afc83/host-native.pcapng) + +To generate each capture, I executed the following command: +```console +timeout --preserve-status 3s ffplay -f v4l2 -i "/dev/video0" -input_format mjpeg -framerate 30 -video_size 1920x1060 +``` + +The "SET INTERFACE" packet reveals that the USB video driver selects bAlternateSetting=7, which has the following parameters: +``` +wMaxPacketSize: 1024 +bMaxBurst: 2 +bmAttributes: 0x01 + .... ..01 = Mult: 1 +``` +According to Section 4.14.2.1.3 of the xHCI specification, the size of an isoch transfer should be `Packet Size * (Max Burst Size + 1) * (Mult + 1) = 6144`. + +However, the host-libusb.pcapng capture shows that each transfer is only 1024 bytes in size. + +For higher bitrate formats, it is observed that the system generates erroneous transfers in which the data offset in the isodescriptor exceeds the packet size. + +Currently, I am unsure of the cause of this issue. If you need any additional information, logs, or specific USB packet captures, I would be more than happy to provide them. + +Thanks +Additional information: +[lsusb-cam-SuperSpeed.txt](/uploads/712ac9e67d0b53ce46573bee3df883d0/lsusb-cam-SuperSpeed.txt) +[lsusb-cam-HighSpeed.txt](/uploads/70f855e471714fb1b48a7ed7912c0be4/lsusb-cam-HighSpeed.txt) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1614 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1614 new file mode 100644 index 000000000..cfa652cd2 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1614 @@ -0,0 +1 @@ +Add option to chardev pty for setting a named link to the allocated pty diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1615 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1615 new file mode 100644 index 000000000..c5aa8a42b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1615 @@ -0,0 +1,11 @@ +8.0.0: Crash when attempting to commit snapshot +Description of problem: +When trying to commit a snapshot to the backing store, qemu exits with the error: + +`qemu: qemu_mutex_unlock_impl: Operation not permitted` +Steps to reproduce: +1. Run qemu command above +2. Open the monitor virtual console (Ctrl-Alt-2) +3. Execute command: `commit os` +Additional information: +Attached are the [backtrace](/uploads/ba8f519e6b00eb054ba416054c782122/8.0.0-1-bt) and the [configure output](/uploads/17124b45e12b252bd01cf41e7a3d2ea4/8.0.0-1-conf.gz). This is a regression from 7.2.1 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1618 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1618 new file mode 100644 index 000000000..0ebb50b25 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1618 @@ -0,0 +1,13 @@ +intel-hda: SD_STS different behavior for byte write vs. word write +Description of problem: +The Intel HDA SD_STS register is accessible two different ways in QEMU: either it's the top 8 bits of a 32-bit access +or it's directly accessible as a byte. +On reads, the register behavior for SD_STS is identical whether accessed as a 32-bit read or an 8-bit read. +On writes, the behavior is different; when written to as an 8-bit write, the BCIS, FIFOE, and DESE bits implement the documented HDA behavior of RW1C (writing a 1 to a bit clears it). When written to as the top 8 bits of a 32-bit write, writing a 1 to a bit sets the bit -- so an attempt to clear a status bit instead unconditionally sets the status bit. +Steps to reproduce: +1. Write 32 bits at SD_CTL address with bit 27 set (FIFOE). This should clear FIFOE, but does not. +2. Read back SD_STS (SD_CTL address + 3) as a byte. The FIFOE bit will be set. +3. Write 8 bits at SD_STS address with bit 3 set (FIFOE). This should clear FIFOE, and it does. +4. Read back SD_STS as a byte. The FIFOE bit will be cleared. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1619 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1619 new file mode 100644 index 000000000..cfa318730 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1619 @@ -0,0 +1 @@ +Emulate x86_64 on ARM machine diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/162 b/gitlab/issues_text/target_missing/host_missing/accel_missing/162 new file mode 100644 index 000000000..807c83b18 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/162 @@ -0,0 +1 @@ +util/path.c/follow_path() does not handle "/" well diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1621 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1621 new file mode 100644 index 000000000..dbf4c7467 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1621 @@ -0,0 +1,106 @@ +QCOW2 image grows over 110% of its virtual size +Description of problem: +Follow-up of https://github.com/oVirt/vdsm/issues/371 + +As oVirt divides a iSCSI LUN into a LVM device and each VM disk is a Logical Volume, the qcow2 images are inside a LV. +This works fine, and oVirt allows the LV to grow to 110% of its virtual size. + +Now we have like 1 time each month the issue that a VM tries to grow over its 110% limit, which should never happen. +Steps to reproduce: +1. When it happend in production, I copied the LV via dd to some file. +2. I copied the file to a new LV on a test machine, and created a VM for it +3. Start the VM +4. Issue reoccurs directly +Additional information: +So I started some gdb'ing on the pid, and this it what seems to happen: +``` +#16 0x0000563c60921f25 in qcow2_add_task (bs=bs@entry=0x563c62bb8090, pool=pool@entry=0x0, func=func@entry=0x563c60924860 <qcow2_co_pwritev_task_entry>, subcluster_type=subcluster_type@entry=QCOW2_SUBCLUSTER_UNALLOCATED_PLAIN, host_offset=17718824960, offset=offset@entry=15192346624, bytes=1310720, qiov=0x7f84c4003a70, qiov_offset=0, l2meta=0x7f84c401c600) + at ../block/qcow2.c:2249 + local_task = {task = {pool = 0x0, func = 0x563c60924860 <qcow2_co_pwritev_task_entry>, ret = 0}, bs = 0x563c62bb8090, subcluster_type = QCOW2_SUBCLUSTER_UNALLOCATED_PLAIN, host_offset = 17718824960, offset = 15192346624, bytes = 1310720, qiov = 0x7f84c4003a70, qiov_offset = 0, l2meta = 0x7f84c401c600} + task = 0x7f82bafffb00 +#17 0x0000563c609225b7 in qcow2_co_pwritev_part (bs=0x563c62bb8090, offset=15192346624, bytes=1310720, qiov=0x7f84c4003a70, qiov_offset=0, flags=<optimized out>) at ../block/qcow2.c:2645 + s = 0x563c62bbf990 + offset_in_cluster = <optimized out> + ret = <optimized out> + cur_bytes = 1310720 + host_offset = 17718824960 + l2meta = 0x7f84c401c600 + aio = 0x0 +#18 0x0000563c6090395b in bdrv_driver_pwritev (bs=bs@entry=0x563c62bb8090, offset=offset@entry=15192346624, bytes=bytes@entry=1310720, qiov=qiov@entry=0x7f84c4003a70, qiov_offset=qiov_offset@entry=0, flags=flags@entry=0) at ../block/io.c:1248 + drv = 0x563c6125fb20 <bdrv_qcow2> + sector_num = <optimized out> + nb_sectors = <optimized out> + local_qiov = {iov = 0x563c6125fb20 <bdrv_qcow2>, niov = 8192, {{nalloc = 4096, local_iov = {iov_base = 0x563c62bb8090, iov_len = 0}}, {__pad = "\000\020\000\000\000\000\000\000\220\200\273b", size = 0}}} + ret = <optimized out> + __PRETTY_FUNCTION__ = "bdrv_driver_pwritev" +#19 0x0000563c60905872 in bdrv_aligned_pwritev (child=0x563c647f3c10, req=0x7f82bafffe30, offset=15192346624, bytes=1310720, align=<optimized out>, qiov=0x7f84c4003a70, qiov_offset=0, flags=0) at ../block/io.c:2122 + bs = 0x563c62bb8090 + drv = 0x563c6125fb20 <bdrv_qcow2> + ret = <optimized out> + bytes_remaining = 1310720 + max_transfer = <optimized out> + __PRETTY_FUNCTION__ = "bdrv_aligned_pwritev" +#20 0x0000563c6090622b in bdrv_co_pwritev_part (child=0x563c647f3c10, offset=<optimized out>, offset@entry=15192346624, bytes=<optimized out>, bytes@entry=1310720, qiov=<optimized out>, qiov@entry=0x7f84c4003a70, qiov_offset=<optimized out>, qiov_offset@entry=0, flags=flags@entry=0) at ../block/io.c:2310 + bs = <optimized out> + req = {bs = 0x563c62bb8090, offset = 15192346624, bytes = 1310720, type = BDRV_TRACKED_WRITE, serialising = false, overlap_offset = 15192346624, overlap_bytes = 1310720, list = {le_next = 0x7f829c6c8e30, le_prev = 0x7f82a3fffe60}, co = 0x7f84c4004210, wait_queue = {entries = {sqh_first = 0x0, sqh_last = 0x7f82bafffe78}}, waiting_for = 0x0} + align = <optimized out> + pad = {buf = 0x0, buf_len = 0, tail_buf = 0x0, head = 0, tail = 0, merge_reads = false, local_qiov = {iov = 0x0, niov = 0, {{nalloc = 0, local_iov = {iov_base = 0x0, iov_len = 0}}, {__pad = '\000' <repeats 11 times>, size = 0}}}} + ret = <optimized out> + padded = false + __PRETTY_FUNCTION__ = "bdrv_co_pwritev_part" +#21 0x0000563c608f71e0 in blk_co_do_pwritev_part (blk=0x563c648183c0, offset=15192346624, bytes=1310720, qiov=0x7f84c4003a70, qiov_offset=qiov_offset@entry=0, flags=0) at ../block/block-backend.c:1289 + ret = <optimized out> + bs = 0x563c62bb8090 +``` + +There is a write from the VM with size 1310720 on offset 15192346624. +A host offset is calculated for this, but this offset is 17718824960 !! +The image/LV is only 17716740096, and 17716740096 < 17718824960 -> ENOSPC error is triggered. + +The code for calculating the host offset seems to be untouched for the last years. +But it seems like for some reason it takes some offset way beyond the virtual size boundaries. + +The qemu-img output: +``` +# qemu-img info /dev/mapper/test-xxxxx +image: /dev/mapper/test-xxxxx +file format: qcow2 +virtual size: 15 GiB (16106127360 bytes) +disk size: 0 B +cluster_size: 65536 +Format specific information: + compat: 1.1 + compression type: zlib + lazy refcounts: false + bitmaps: + [0]: + flags: + [0]: in-use + [1]: auto + name: 428fae80-3892-4083-9107-51fb76a7f06b + granularity: 65536 + [1]: + flags: + [0]: in-use + [1]: auto + name: 51ccd1fc-08a4-485d-8c04-0eb750665e05 + granularity: 65536 + [2]: + flags: + [0]: in-use + [1]: auto + name: 19796bed-56a5-44c1-a7f2-dae633e65c87 + granularity: 65536 + [3]: + flags: + [0]: in-use + [1]: auto + name: 13056186-e65e-448e-a3c3-019ab25d3a27 + granularity: 65536 + refcount bits: 16 + corrupt: false + extended l2: false +``` + +Also attaching the map where you can see there are plenty of zero blocks, but still it tries to allocate a new block for some reason. +[map.txt](/uploads/0890cf718f77c0ad2e562165eb350d13/map.txt) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1622 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1622 new file mode 100644 index 000000000..53684218c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1622 @@ -0,0 +1 @@ +PNG screendump has R/B channels swapped diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1625 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1625 new file mode 100644 index 000000000..d2168f595 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1625 @@ -0,0 +1,13 @@ +[7.2.0] Qemu process hang with `defunct` when using `-blockdev` json property which file doesn't exists +Description of problem: +When using `throttle` and `throttle-group` to apply block device QOS, +there is something wrong with check file exists validation. +In upper commands, if the file which located `/mnt/b3b8dfb5-0a7c-4285-81d8-2bf8d33a3297/32c55f5a-96d1-4af4-a149-c95fd6652e3e/b016af76-f6b1-4614-b29a-78917924e55e` doesn't exist, it just hang with `defunct` process. + +Steps to reproduce: +1. Start Guest with upper command. +2. Hanged with defunct process +3. +Additional information: + +- With GDB stack, i can find `no such file` error, but process don't exit diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1626 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1626 new file mode 100644 index 000000000..9e9e0f563 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1626 @@ -0,0 +1,5 @@ +QEMU insists on using /var/tmp instead of /tmp +Description of problem: +On a host, our sysadmins have decided for whatever reason that `/var/tmp` is not a thing that normal users can write to (and perhaps that's dumb, but it is what it is and would be a challenging non-technical problem to solve). Whenever QEMU detects the temporary directory is /tmp, it changes it to `/var/tmp` without a mechanism to change it (see https://gitlab.com/qemu-project/qemu/-/commit/69fbfff95e849156985cf95e2010ffc8762e34e6). + +I'm sure in the general case this is fine, but can you add an environment variable or a ./configure option to make this location configurable? I really would like to write to `/tmp`. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1629 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1629 new file mode 100644 index 000000000..e8ce977c8 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1629 @@ -0,0 +1 @@ +qem-img Heap Buffer Overflow diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/163 b/gitlab/issues_text/target_missing/host_missing/accel_missing/163 new file mode 100644 index 000000000..330d041ca --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/163 @@ -0,0 +1 @@ +SPICE session's connection_id's are not unique diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1630 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1630 new file mode 100644 index 000000000..cfec1b95c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1630 @@ -0,0 +1,200 @@ +[8.0.0] qemu breaks mac os vm (passed through sata controller) +Description of problem: +I have a mac os montery vm which is not able to boot after upgrading from qemu 7.2.1 to qemu 8.0.0.\ +Mac os bootloader (opencore) logs do not show anything useful, nothing useful also in libvirt logs.\ +Apple screen hangs at "still waiting for root device" with the prohibition symbol.\ +This should point that mac os is not able to find the disk to boot from.\ +The bootloader sees the disk with its partitions.\ +I'm passing through a sata controller with the boot disk attached, together with a usb controller, builtin audio and a gpu.\ +Changing machine type (q35) to older versions change nothing.\ +Downgrading to 7.2.1 and no issue. + +Maybe related to some acpi changes? +Additional information: +This is the libvirt xml I'm using: +``` +<domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> + <name>Montereytest</name> + <memory unit='KiB'>33554432</memory> + <currentMemory unit='KiB'>33554432</currentMemory> + <memoryBacking> + <nosharepages/> + </memoryBacking> + <vcpu placement='static'>8</vcpu> + <iothreads>2</iothreads> + <iothreadids> + <iothread id='1'/> + <iothread id='2'/> + </iothreadids> + <cputune> + <vcpupin vcpu='0' cpuset='1'/> + <vcpupin vcpu='1' cpuset='2'/> + <vcpupin vcpu='2' cpuset='3'/> + <vcpupin vcpu='3' cpuset='4'/> + <vcpupin vcpu='4' cpuset='5'/> + <vcpupin vcpu='5' cpuset='6'/> + <vcpupin vcpu='6' cpuset='7'/> + <vcpupin vcpu='7' cpuset='9'/> + </cputune> + <os> + <type arch='x86_64' machine='pc-q35-7.2'>hvm</type> + <loader readonly='yes' type='pflash'>/opt/macos/OVMF_CODE_TEST.fd</loader> + <nvram>/opt/macos/OVMF_VARS_TEST.fd</nvram> + <boot dev='hd'/> + </os> + <features> + <acpi/> + <apic/> + </features> + <cpu mode='host-passthrough' check='none' migratable='on'> + <topology sockets='1' dies='1' cores='4' threads='2'/> + </cpu> + <clock offset='utc'> + <timer name='rtc' tickpolicy='catchup'/> + <timer name='pit' tickpolicy='delay'/> + <timer name='hpet' present='no'/> + </clock> + <on_poweroff>destroy</on_poweroff> + <on_reboot>restart</on_reboot> + <on_crash>restart</on_crash> + <devices> + <emulator>/usr/bin/qemu-system-x86_64</emulator> + <controller type='pci' index='0' model='pcie-root'/> + <controller type='pci' index='1' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='1' port='0x8'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> + </controller> + <controller type='pci' index='2' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='2' port='0x9'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> + </controller> + <controller type='pci' index='3' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='3' port='0xc'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> + </controller> + <controller type='pci' index='4' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='4' port='0x13'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> + </controller> + <controller type='virtio-serial' index='0'> + <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> + </controller> + <controller type='usb' index='0' model='ich9-ehci1'> + <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x1'/> + </controller> + <controller type='usb' index='0' model='ich9-uhci1'> + <master startport='0'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0' multifunction='on'/> + </controller> + <controller type='sata' index='0'> + <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> + </controller> + <interface type='bridge'> + <mac address='c8:2a:14:55:1a:b2'/> + <source bridge='br0'/> + <model type='virtio'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> + </interface> + <interface type='bridge'> + <mac address='c8:2a:14:32:2c:ff'/> + <source bridge='br1'/> + <model type='virtio'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> + </interface> + <serial type='pty'> + <target type='isa-serial' port='0'> + <model name='isa-serial'/> + </target> + </serial> + <console type='pty'> + <target type='serial' port='0'/> + </console> + <channel type='unix'> + <target type='virtio' name='org.qemu.guest_agent.0'/> + <address type='virtio-serial' controller='0' bus='0' port='1'/> + </channel> + <input type='keyboard' bus='ps2'/> + <input type='mouse' bus='ps2'/> + <audio id='1' type='none'/> + <hostdev mode='subsystem' type='pci' managed='yes'> + <driver name='vfio'/> + <source> + <address domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> + </source> + <rom file='/opt/gpu-bios/6900xt.rom'/> + <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0' multifunction='on'/> + </hostdev> + <hostdev mode='subsystem' type='pci' managed='yes'> + <driver name='vfio'/> + <source> + <address domain='0x0000' bus='0x06' slot='0x00' function='0x1'/> + </source> + <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x1'/> + </hostdev> + <hostdev mode='subsystem' type='pci' managed='yes'> + <driver name='vfio'/> + <source> + <address domain='0x0000' bus='0x00' slot='0x1b' function='0x0'/> + </source> + <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> + </hostdev> + <hostdev mode='subsystem' type='pci' managed='yes'> + <driver name='vfio'/> + <source> + <address domain='0x0000' bus='0x0c' slot='0x00' function='0x0'/> + </source> + <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> + </hostdev> + <hostdev mode='subsystem' type='pci' managed='yes'> + <driver name='vfio'/> + <source> + <address domain='0x0000' bus='0x84' slot='0x00' function='0x0'/> + </source> + <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> + </hostdev> + <hostdev mode='subsystem' type='usb' managed='no'> + <source> + <vendor id='0x046d'/> + <product id='0x0892'/> + </source> + <address type='usb' bus='0' port='2'/> + </hostdev> + <hostdev mode='subsystem' type='usb' managed='no'> + <source> + <vendor id='0x148f'/> + <product id='0x3070'/> + </source> + <address type='usb' bus='0' port='1'/> + </hostdev> + <watchdog model='itco' action='reset'/> + <memballoon model='none'/> + </devices> + <qemu:commandline> + <qemu:arg value='-smbios'/> + <qemu:arg value='type=2'/> + <qemu:arg value='-global'/> + <qemu:arg value='ICH9-LPC.acpi-pci-hotplug-with-bridge-support=off'/> + <qemu:arg value='-global'/> + <qemu:arg value='pcie-root-port.x-speed=8'/> + <qemu:arg value='-global'/> + <qemu:arg value='pcie-root-port.x-width=16'/> + <qemu:arg value='-cpu'/> + <qemu:arg value='host,+hypervisor,migratable=no,-erms,kvm=on,+invtsc,+topoext,+avx,+aes,+xsave,+xsaveopt,+ssse3,+sse4_2,+popcnt,+arat,+pclmuldq,+pdpe1gb,+rdtscp,+vme,+umip,check'/> + </qemu:commandline> +</domain> +``` + +06:00.0/1 --> gpu\ +00:1b.0 --> audio\ +0c:00.0 --> sata controller\ +84:00.0 --> usb controller\ +0x046d 0x0892 --> usb webcam\ +0x148f 0x3070 --> usb wifi + + + +[] diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1632 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1632 new file mode 100644 index 000000000..dd6114e76 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1632 @@ -0,0 +1,490 @@ +Porting support for GVM/AEHD to qemu 8.0 +Description of problem: +I'm trying to find reason why changes work fine with qemu 7.1 but it doesn't work with qemu 7.2 and 8.0. Could you recommend me point where I should investigate this bug/error when using GVM acceleration. I know it is not part of official QEMU and somebody is also working on that [topic ](https://gitlab.com/qemu-project/qemu/-/issues/1558). + + +``` +GVM is operational +** +ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized) +** +ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized) +Bail out! ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized) +** +ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized)Bail out! ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized) + +** +ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized) +Bail out! ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized) +** +ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized) +Bail out! ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized) +** +ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized)Bail out! ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized) + +** +ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized)Bail out! ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized) + +** +ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized) +Bail out! ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized) +** +ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized)Bail out! ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized) + +** +ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized)Bail out! ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized) + +** +ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized)Bail out! ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized) + +** +ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized)Bail out! ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized) + +Bail out! ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized) +``` +Steps to reproduce: +1. Checkout my fork with this branch [qemu-8.0-gvm](https://gitlab.com/MateuszKrawczuk/qemu/-/tree/qemu-8.0-gvm) +2. Build on windows using mingw64 +3. Try launch with using GVM acceleration +Additional information: +``` +./configure --enable-sdl --enable-gtk --enable-whpx --target-list=x86_64-softmmu +Using './build' as the directory for build output +ln: nie udało się utworzyć dowiązania symbolicznego 'x86_64-softmmu/qemu-system-x86_64.exe': No such file or directory +The Meson build system +Version: 0.61.5 +Source dir: C:/Users/AMD-RYZEN-PC/qemu +Build dir: C:/Users/AMD-RYZEN-PC/qemu/build +Build type: native build +Project name: qemu +Project version: 8.0.0 +C compiler for the host machine: cc -m64 -mcx16 (gcc 12.2.0 "cc (Rev10, Built by MSYS2 project) 12.2.0") +C linker for the host machine: cc -m64 -mcx16 ld.bfd 2.40 +Host machine cpu family: x86_64 +Host machine cpu: x86_64 +Program scripts/symlink-install-tree.py found: YES (C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/mingw64/bin/python3.exe C:/Users/AMD-RYZEN-PC/qemu/scripts/symlink-install-tree.py) +Program sh found: YES (C:\Users\AMD-RYZEN-PC\scoop\apps\msys2\2023-03-18\usr\bin/sh.EXE) +C++ compiler for the host machine: c++ -m64 -mcx16 (gcc 12.2.0 "c++ (Rev10, Built by MSYS2 project) 12.2.0") +C++ linker for the host machine: c++ -m64 -mcx16 ld.bfd 2.40 +Program python3 found: YES (C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/mingw64/bin/python3.exe) +Program bzip2 found: YES (C:\Users\AMD-RYZEN-PC\scoop\apps\msys2\2023-03-18\mingw64\bin/bzip2.EXE) +Program iasl found: NO +Compiler for C supports link arguments -Wl,-z,relro: NO +Compiler for C supports link arguments -Wl,-z,now: NO +Compiler for C supports link arguments -Wl,--no-seh: YES +Compiler for C supports link arguments -Wl,--nxcompat: YES +Compiler for C supports link arguments -Wl,--dynamicbase: YES +Compiler for C supports link arguments -Wl,--high-entropy-va: YES +Compiler for C++ supports link arguments -Wl,--warn-common: YES +Program cgcc found: NO +Library m found: YES +Run-time dependency threads found: YES +Library util found: NO +Program midl found: NO +Program widl found: YES +Library pathcch found: YES +Library ws2_32 found: YES +Library winmm found: YES +Windows resource compiler: GNU windres (GNU Binutils) 2.40 +Has header "WinHvPlatform.h" : YES +Has header "WinHvEmulation.h" : YES +Run-time dependency appleframeworks found: NO (tried framework) +Found pkg-config: C:\Users\AMD-RYZEN-PC\scoop\apps\msys2\2023-03-18\mingw64\bin/pkg-config.EXE (1.8.0) +Run-time dependency gio-2.0 found: YES 2.76.1 +Program C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/mingw64/bin/gdbus-codegen found: YES (C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/mingw64/bin/gdbus-codegen.exe) +Run-time dependency gio-unix-2.0 found: NO (tried pkgconfig) +Run-time dependency pixman-1 found: YES 0.42.2 +Run-time dependency zlib found: YES 1.2.13 +Has header "libaio.h" : NO +Run-time dependency liburing found: NO (tried pkgconfig) +Run-time dependency libnfs found: NO (tried pkgconfig) +Has header "attr/xattr.h" : NO +Run-time dependency appleframeworks found: NO (tried framework) +Run-time dependency appleframeworks found: NO (tried framework) +Run-time dependency libseccomp found: NO (tried pkgconfig) +Has header "cap-ng.h" : NO +Run-time dependency xkbcommon found: NO (tried pkgconfig) +Run-time dependency slirp found: YES 4.7.0 +Has header "libvdeplug.h" : NO +Run-time dependency jack found: NO (tried pkgconfig) +Run-time dependency sndio found: NO (tried pkgconfig) +Run-time dependency spice-protocol found: NO (tried pkgconfig) +Run-time dependency spice-server found: NO (tried pkgconfig) +Library rt found: NO +Run-time dependency libiscsi found: NO (tried pkgconfig) +Run-time dependency libzstd found: YES 1.5.5 +Run-time dependency virglrenderer found: YES 0.9.1 +Run-time dependency blkio found: NO (tried pkgconfig) +Run-time dependency libcurl found: NO (tried pkgconfig) +Run-time dependency ncurses found: NO (tried pkgconfig) +Run-time dependency ncursesw found: YES 6.4.20230211 +Has header "brlapi.h" : NO +Run-time dependency sdl2 found: YES 2.26.5 +Run-time dependency sdl2_image found: YES 2.6.3 +Library rados found: NO +Has header "rbd/librbd.h" : NO +Run-time dependency glusterfs-api found: NO (tried pkgconfig) +Run-time dependency libssh found: NO (tried pkgconfig) +Has header "bzlib.h" : YES +Library bz2 found: YES +Has header "lzfse.h" : NO +Has header "sys/soundcard.h" : NO +Has header "dsound.h" : YES +Run-time dependency epoxy found: YES 1.5.10 +Has header "epoxy/egl.h" with dependency epoxy: YES +Run-time dependency gbm found: NO (tried pkgconfig) +Run-time dependency gnutls found: NO (tried pkgconfig) +Run-time dependency gnutls found: NO (tried pkgconfig) +libgcrypt-config found: NO need ['>=1.8'] +Run-time dependency libgcrypt found: NO (tried config-tool) +Run-time dependency nettle found: NO (tried pkgconfig) +Run-time dependency gmp found: YES 6.2.1 +Run-time dependency gtk+-3.0 found: YES 3.24.38 +Run-time dependency gtk+-x11-3.0 found: NO (tried pkgconfig) +Run-time dependency vte-2.91 found: NO (tried pkgconfig) +Run-time dependency libpng found: YES 1.6.39 +Run-time dependency libjpeg found: YES 2.1.5.1 +Has header "sasl/sasl.h" : NO +Has header "security/pam_appl.h" : NO +Has header "snappy-c.h" : NO +Has header "lzo/lzo1x.h" : YES +Library lzo2 found: YES +Has header "numa.h" : NO +Library ibumad found: NO +Has header "rdma/rdma_cma.h" : NO +Library ibverbs found: NO +Run-time dependency xencontrol found: NO (tried pkgconfig) +Library xenstore found: NO +Library xenctrl found: NO +Library xendevicemodel found: NO +Library xenforeignmemory found: NO +Library xengnttab found: NO +Library xenevtchn found: NO +Library xentoolcore found: NO +Run-time dependency libcacard found: NO (tried pkgconfig) +Run-time dependency u2f-emu found: NO (tried pkgconfig) +Run-time dependency canokey-qemu found: NO (tried pkgconfig) +Run-time dependency libusbredirparser-0.5 found: NO (tried pkgconfig) +Run-time dependency libusb-1.0 found: YES 1.0.26 +Run-time dependency libpmem found: NO (tried pkgconfig) +Run-time dependency libdaxctl found: NO (tried pkgconfig) +Run-time dependency libkeyutils found: NO (tried pkgconfig) +Checking for function "gettid" : NO +Run-time dependency libselinux found: NO (tried pkgconfig) +Run-time dependency fuse3 found: NO (tried pkgconfig) +Run-time dependency libbpf found: NO (tried pkgconfig) +Run-time dependency libdw found: NO (tried pkgconfig) +Checking for function "pthread_fchdir_np" : NO +Has header "sys/epoll.h" : NO +Has header "linux/magic.h" : NO +Has header "valgrind/valgrind.h" : NO +Has header "linux/btrfs.h" : NO +Has header "libdrm/drm.h" : NO +Has header "pty.h" : NO +Has header "sys/disk.h" : NO +Has header "sys/ioccom.h" : NO +Has header "sys/kcov.h" : NO +Has header "afunix.h" : YES +Checking for function "close_range" : NO +Checking for function "accept4" : NO +Checking for function "clock_adjtime" : NO +Checking for function "dup3" : NO +Checking for function "fallocate" : NO +Checking for function "posix_fallocate" : NO +Checking for function "posix_memalign" : NO +Checking for function "_aligned_malloc" : YES +Checking for function "valloc" : NO +Checking for function "memalign" : NO +Checking for function "ppoll" : NO +Checking for function "preadv" : NO +Checking for function "pthread_fchdir_np" : NO (cached) +Checking for function "sendfile" : NO +Checking for function "setns" : NO +Checking for function "syncfs" : NO +Checking for function "sync_file_range" : NO +Checking for function "timerfd_create" : NO +Checking for function "copy_file_range" : NO +Checking for function "getifaddrs" : NO +Checking for function "openpty" with dependency -lutil: NO +Checking for function "strchrnul" : NO +Checking for function "system" : YES +Header <sys/epoll.h> has symbol "epoll_create1" : NO +Header <linux/falloc.h> has symbol "FALLOC_FL_PUNCH_HOLE" : NO +Header <linux/falloc.h> has symbol "FALLOC_FL_ZERO_RANGE" : NO +Has header "linux/fiemap.h" : NO +Checking for function "getrandom" : NO +Header <sys/inotify.h> has symbol "inotify_init" : NO +Header <sys/inotify.h> has symbol "inotify_init1" : NO +Header <sys/prctl.h> has symbol "PR_SET_TIMERSLACK" : NO +Header <linux/rtnetlink.h> has symbol "IFLA_PROTO_DOWN" : NO +Header <sys/sysmacros.h> has symbol "makedev" : NO +Header <getopt.h> has symbol "optreset" : NO +Header <netinet/in.h> has symbol "IPPROTO_MPTCP" : NO +Checking whether type "struct sigevent" has member "sigev_notify_thread_id" : NO +Checking whether type "struct stat" has member "st_atim" : NO +Checking for type "struct iovec" : NO +Checking for type "struct utmpx" : NO +Checking for type "struct mmsghdr" : NO +Header <linux/vm_sockets.h> has symbol "AF_VSOCK" : NO +Has header "vscoordint.h" : NO +Checking if "_lock_file and _unlock_file" : links: YES +Checking if "mingw setjmp and longjmp" : links: NO +Program scripts/minikconf.py found: YES (C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/mingw64/bin/python3.exe C:/Users/AMD-RYZEN-PC/qemu/scripts/minikconf.py) +Configuring x86_64-softmmu-config-target.h using configuration +Configuring x86_64-softmmu-config-devices.mak with command +Reading depfile: C:/Users/AMD-RYZEN-PC/qemu/build/meson-private/x86_64-softmmu-config-devices.mak.d +Configuring x86_64-softmmu-config-devices.h using configuration +Program scripts/make-config-poison.sh found: YES (sh C:/Users/AMD-RYZEN-PC/qemu/scripts/make-config-poison.sh) +Run-time dependency capstone found: NO (tried pkgconfig) +Library fdt found: NO +Configuring config-host.h using configuration +Program scripts/hxtool found: YES (sh C:/Users/AMD-RYZEN-PC/qemu/scripts/hxtool) +Program scripts/shaderinclude.py found: YES (C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/mingw64/bin/python3.exe C:/Users/AMD-RYZEN-PC/qemu/scripts/shaderinclude.py) +Program scripts/qapi-gen.py found: YES (C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/mingw64/bin/python3.exe C:/Users/AMD-RYZEN-PC/qemu/scripts/qapi-gen.py) +Program scripts/qemu-version.sh found: YES (sh C:/Users/AMD-RYZEN-PC/qemu/scripts/qemu-version.sh) +Program scripts/decodetree.py found: YES (C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/mingw64/bin/python3.exe C:/Users/AMD-RYZEN-PC/qemu/scripts/decodetree.py) +Program ../scripts/modules/module_block.py found: YES (C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/mingw64/bin/python3.exe C:/Users/AMD-RYZEN-PC/qemu/block/../scripts/modules/module_block.py) +Program ../scripts/block-coroutine-wrapper.py found: YES (C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/mingw64/bin/python3.exe C:/Users/AMD-RYZEN-PC/qemu/block/../scripts/block-coroutine-wrapper.py) +Program scripts/modinfo-collect.py found: YES (C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/mingw64/bin/python3.exe C:/Users/AMD-RYZEN-PC/qemu/scripts/modinfo-collect.py) +Program scripts/modinfo-generate.py found: YES (C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/mingw64/bin/python3.exe C:/Users/AMD-RYZEN-PC/qemu/scripts/modinfo-generate.py) +Program nm found: YES +Program scripts/undefsym.py found: YES (C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/mingw64/bin/python3.exe C:/Users/AMD-RYZEN-PC/qemu/scripts/undefsym.py) +Program scripts/feature_to_c.sh found: YES (sh C:/Users/AMD-RYZEN-PC/qemu/scripts/feature_to_c.sh) +Compiler for C supports link arguments -fstack-protector-all: YES +Compiler for C supports link arguments -fstack-protector-strong: YES +Compiler for C supports link arguments -Wl,--add-stdcall-alias: YES +Compiler for C supports link arguments -Wl,--enable-stdcall-fixup: YES +Library ole32 found: YES +Library oleaut32 found: YES +Library shlwapi found: YES +Library uuid found: YES +Library intl found: YES +Program windmc found: YES +Program windres found: YES +Program wixl found: NO +Configuring 50-edk2-i386-secure.json using configuration +Configuring 50-edk2-x86_64-secure.json using configuration +Configuring 60-edk2-aarch64.json using configuration +Configuring 60-edk2-arm.json using configuration +Configuring 60-edk2-i386.json using configuration +Configuring 60-edk2-x86_64.json using configuration +Program qemu-keymap found: NO +Program sphinx-build found: NO +Program diff found: YES (C:\Users\AMD-RYZEN-PC\scoop\apps\msys2\2023-03-18\usr\bin/diff.EXE) +Program dbus-daemon found: NO +Found CMake: C:\Users\AMD-RYZEN-PC\scoop\shims/cmake.EXE (3.26.3) +WARNING: CMake Toolchain: Failed to determine CMake compilers state +Run-time dependency gvnc-1.0 found: NO (tried pkgconfig and cmake) +Run-time dependency sysprof-capture-4 found: NO (tried pkgconfig and cmake) +Program initrd-stress.sh found: YES (sh C:/Users/AMD-RYZEN-PC/qemu/tests/migration/initrd-stress.sh) +Program xgettext found: YES (C:\Users\AMD-RYZEN-PC\scoop\apps\msys2\2023-03-18\mingw64\bin/xgettext.EXE) +Program scripts/nsis.py found: YES (C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/mingw64/bin/python3.exe C:/Users/AMD-RYZEN-PC/qemu/scripts/nsis.py) +Build targets in project: 516 + +qemu 8.0.0 + + Directories + Install prefix : C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/qemu + BIOS directory : share/ + firmware path : share/qemu-firmware + binary directory : C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/qemu/. + library directory : C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/qemu/lib + module directory : lib/ + libexec directory : C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/qemu/libexec + include directory : C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/qemu/include + config directory : C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/qemu/etc + local state directory : queried at runtime + Doc directory : C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/qemu/share/doc + Build directory : C:/Users/AMD-RYZEN-PC/qemu/build + Source path : C:/Users/AMD-RYZEN-PC/qemu + GIT submodules : ui/keycodemapdb meson tests/fp/berkeley-testfloat-3 tests/fp/berkeley-softfloat-3 dtc + + Host binaries + git : git + make : make + python : C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/mingw64/bin/python3.exe (version: 3.10) + sphinx-build : NO + gdb : /mingw64/bin/gdb-multiarch + iasl : NO + genisoimage : + wixl : NO + smbd : NO + + Configurable features + Documentation : NO + system-mode emulation : YES + user-mode emulation : NO + block layer : YES + Install blobs : YES + module support : NO + fuzzing support : NO + Audio drivers : dsound sdl + Trace backends : log + D-Bus display : NO + QOM debugging : NO + vhost-kernel support : NO + vhost-net support : NO + vhost-user support : NO + vhost-user-crypto support : NO + vhost-user-blk server support: NO + vhost-vdpa support : NO + build guest agent : YES + + Compilation + host CPU : x86_64 + host endianness : little + C compiler : cc -m64 -mcx16 + Host C compiler : cc -m64 -mcx16 + C++ compiler : c++ -m64 -mcx16 + CFLAGS : -g -O2 + CXXFLAGS : -g -O2 + QEMU_CFLAGS : -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fno-pie -no-pie -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -fno-strict-aliasing -fno-common -fwrapv -Wundef -Wwrite-strings -Wmissing-prototypes -Wstrict-prototypes -Wredundant-decls -Wold-style-declaration -Wold-style-definition -Wtype-limits -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body -Wnested-externs -Wendif-labels -Wexpansion-to-defined -Wimplicit-fallthrough=2 -Wmissing-format-attribute -Wno-missing-include-dirs -Wno-shift-negative-value -Wno-psabi -fstack-protector-strong + QEMU_CXXFLAGS : -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fno-pie -no-pie -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -fno-strict-aliasing -fno-common -fwrapv -Wundef -Wwrite-strings -Wtype-limits -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body -Wendif-labels -Wexpansion-to-defined -Wimplicit-fallthrough=2 -Wmissing-format-attribute -Wno-missing-include-dirs -Wno-shift-negative-value -Wno-psabi -fstack-protector-strong + QEMU_LDFLAGS : -fstack-protector-strong -Wl,--no-seh -Wl,--nxcompat -Wl,--dynamicbase -Wl,--high-entropy-va -Wl,--warn-common + profiler : NO + link-time optimization (LTO) : NO + PIE : NO + static build : NO + malloc trim support : NO + membarrier : NO + debug stack usage : NO + mutex debugging : NO + memory allocator : system + avx2 optimization : YES + avx512bw optimization : YES + avx512f optimization : NO + gprof : NO + gcov : NO + thread sanitizer : NO + CFI support : NO + strip binaries : NO + sparse : NO + mingw32 support : YES + + Cross compilers + x86_64 : cc + + Targets and accelerators + KVM support : NO + GVM support : YES + HAX support : YES + HVF support : NO + WHPX support : YES + NVMM support : NO + Xen support : NO + Xen emulation : NO + TCG support : YES + TCG backend : native (x86_64) + TCG plugins : NO + TCG debug enabled : NO + target list : x86_64-softmmu + default devices : YES + out of process emulation : NO + vfio-user server : NO + + Block layer support + coroutine backend : win32 + coroutine pool : YES + Block whitelist (rw) : + Block whitelist (ro) : + Use block whitelist in tools : NO + VirtFS support : NO + Live block migration : YES + replication support : YES + bochs support : YES + cloop support : YES + dmg support : YES + qcow v1 support : YES + vdi support : YES + vvfat support : YES + qed support : YES + parallels support : YES + FUSE exports : NO + VDUSE block exports : NO + + Crypto + TLS priority : NORMAL + GNUTLS support : NO + libgcrypt : NO + nettle : NO + AF_ALG support : NO + rng-none : NO + Linux keyring : NO + + Dependencies + SDL support : YES + SDL image support : YES 2.6.3 + GTK support : YES + pixman : YES 0.42.2 + VTE support : NO + slirp support : YES 4.7.0 + libtasn1 : NO + PAM : NO + iconv support : YES + curses support : YES + virgl support : YES 0.9.1 + blkio support : NO + curl support : NO + Multipath support : NO + PNG support : YES 1.6.39 + VNC support : YES + VNC SASL support : NO + VNC JPEG support : YES 2.1.5.1 + DirectSound support : YES + JACK support : NO + brlapi support : NO + vde support : NO + netmap support : NO + l2tpv3 support : NO + Linux AIO support : NO + Linux io_uring support : NO + ATTR/XATTR support : NO + RDMA support : NO + PVRDMA support : NO + fdt support : internal + libcap-ng support : NO + bpf support : NO + spice protocol support : NO + rbd support : NO + smartcard support : NO + U2F support : NO + libusb : YES 1.0.26 + usb net redir : NO + OpenGL support (epoxy) : YES 1.5.10 + GBM : NO + libiscsi support : NO + libnfs support : NO + QGA VSS support : YES + seccomp support : NO + GlusterFS support : NO + TPM support : NO + libssh support : NO + lzo support : YES + snappy support : NO + bzip2 support : YES + lzfse support : NO + zstd support : YES 1.5.5 + NUMA host support : NO + capstone : NO + libpmem support : NO + libdaxctl support : NO + libudev : NO + FUSE lseek : NO + selinux : NO + libdw : NO + + User defined options + Native files : config-meson.cross + bindir : + prefix : C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/qemu + werror : true + b_pie : false + gtk : enabled + qemu_suffix : + sdl : enabled + vfio_user_server : disabled + whpx : enabled + +Found ninja-1.11.1 at C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/usr/bin/ninja.exe +Running postconf script 'C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/mingw64/bin/python3.exe C:/Users/AMD-RYZEN-PC/qemu/scripts/symlink-install-tree.py' +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1638 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1638 new file mode 100644 index 000000000..50c0fdb1f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1638 @@ -0,0 +1,19 @@ +BUG: Segmentation fault when -object memory-backend-file use readonly=on, prealloc=on together +Description of problem: +Segmentation Fault while booting VM. +Steps to reproduce: +1. set qemu boot params to `-object memory-backend-file,id=mem1,readonly=on,prealloc=on,mem-path=<any-img-file>,size=4G` +2. +3. +Additional information: +It might not be a bug, probably a feature. +The reason of this segfault is: +readonly would mmap the backend file using PROT_READ, make it readonly, +but the prealloc=on would touch_pages the memory mmaped by the file. +SO the segfault happens. + +But there is no docs about this segfault condition (the readonly and prealloc cannot be used together.) + +And maybe there is a way to solve this problem, I think. +Use mmap the memory backend file to PROT_READ|PROT_WRITE at the beginnning, after touch_pages, then mprotect the memory. +change the prot to readonly if required. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1641 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1641 new file mode 100644 index 000000000..44f0af776 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1641 @@ -0,0 +1,24 @@ +[abrt] qemu-system-x86-core: do_patch_instruction(): qemu-system-x86_64 killed by SIGABRT +Description of problem: +Copied from downstream bug: https://bugzilla.redhat.com/show_bug.cgi?id=2195952 + +Description of problem: +Virtualizing a Windows XP system which tried to reboot. + +Version-Release number of selected component: +qemu-system-x86-core-2:7.2.1-1.fc38 + +Additional info: +reason: qemu-system-x86_64 killed by SIGABRT +backtrace_rating: 4 +crash_function: do_patch_instruction +comment: Virtualizing a Windows XP system which tried to reboot. + +Truncated backtrace: +Thread no. 1 (6 frames) + #4 do_patch_instruction at ../hw/i386/kvmvapic.c:439 + #5 process_queued_cpu_work at ../cpus-common.c:347 + #6 qemu_wait_io_event at ../softmmu/cpus.c:435 + #7 kvm_vcpu_thread_fn at ../accel/kvm/kvm-accel-ops.c:56 + #8 qemu_thread_start at ../util/qemu-thread-posix.c:505 + #10 clone3 at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1643 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1643 new file mode 100644 index 000000000..0ab593a1d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1643 @@ -0,0 +1 @@ +Connect to MACVTAP by name diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1644 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1644 new file mode 100644 index 000000000..d1c3c69da --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1644 @@ -0,0 +1,14 @@ +qemu 8.0.0 console-gl.c:105: surface_gl_update_texture: Assertion `gls' failed. +Description of problem: +run ubuntu20.04 in virtualBox, and run qemu in this ubuntu. +1. qemu report error at qemu start. +2. qemu-system-x86_64 can't run myOS with 'virtio-gpu-pci -display sdl,gl=on', +3. qemu report error: qemu-system-x86_64: ../ui/console-gl.c:105: surface_gl_update_texture: Assertion `gls' failed. Aborted +Steps to reproduce: +1. run ubuntu20.04 in virtualBox +2. qemu config enabled sdl, virglrenderer, opengl, gtk +3. ./qemu-system-x86_64 -machine q35 -cpu Nehalem -m 1024 -smp 8 -kernel myOS -device virtio-gpu-pci -display sdl,gl=on +4. qemu report error: qemu-system-x86_64: ../ui/console-gl.c:105: surface_gl_update_texture: Assertion `gls' failed. Aborted +Additional information: +qemu-system-x86_64: ../ui/console-gl.c:105: surface_gl_update_texture: Assertion `gls' failed. +Aborted diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1645 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1645 new file mode 100644 index 000000000..7b5892a70 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1645 @@ -0,0 +1,8 @@ +qemu error `hotplug memory" error="QMP command failed: a used vhost backend has no free memory slots left"` +Description of problem: +When I create a Qemu VM with 8 Gpus and hot-plugging memory, this will return the error QMP command failed: a used vhost backend has no free memory slots left. I read some source file https://gitlab.com/qemu-project/qemu/-/blob/master/hw/virtio/vhost-user.c#L2077, and debug show u->user->memory_slots is 32, but this https://gitlab.com/qemu-project/qemu/-/blob/master/hw/virtio/vhost.c#L62 used_memslots is bigger than u->user->memory_slots. `u->user->memory_slots` is defined 32 by https://gitlab.com/qemu-project/qemu/-/blob/master/subprojects/libvhost-user/libvhost-user.h#L37, but I also see VHOST_USER_MAX_RAM_SLOTS defined 512 under x86 architecture. Can I improve `u->user->memory_slots` by any way? +Steps to reproduce: +1.crate kata containers with 8 Gpus +2.kata containers return error +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1646 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1646 new file mode 100644 index 000000000..1e7ed29bd --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1646 @@ -0,0 +1,61 @@ +fstrim dont work after live migrate +Description of problem: +We have use lvm thin pool and after live migration non-shared storage fstrim cannot free data usage Data% without reboot, after reboot fstim work fine + +``` + LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert + p639937 vm Vwi-aotz-- 30.00g pool 99.35 + +virsh qemu-agent-command p639937 '{"execute":"guest-fstrim"}' +{"return":{"paths":[{"minimum":0,"path":"/","trimmed":0}]}} + +virsh shutdown p639937 +Domain 'p639937' is being shutdown + +virsh start p639937 +Domain 'p639937' started + +virsh qemu-agent-command p639937 '{"execute":"guest-fstrim"}' +{"return":{"paths":[{"minimum":0,"path":"/","trimmed":29178654720}]}} + +lvs|grep p639937 + p639937 vm Vwi-aotz-- 30.00g pool 9.58 +``` + +On source host before migration: +``` + LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert + p639937 vm Vwi-a-tz-- 30.00g pool 9.48 +``` + +migration script +``` +SSH_OPTS='-o StrictHostKeyChecking=no -o PasswordAuthentication=no ' +MIGR_OPTS="--live --copy-storage-all --verbose --persistent --undefinesource" +ssh $SSH_OPTS $HOST -t "[ -b /dev/vm/$ACCT ] || /usr/sbin/lvcreate -V${SIZE}G -T vm/pool -n$ACCT" || f_print_err "Error: creation lvm" +virsh migrate $MIGR_OPTS $ACCT qemu+ssh://$SERV/system tcp://local.$SERV/ || f_print_err "Error on step: virsh migrate" +echo "Waiting for trim start..." +sleep 10 +ssh $SSH_OPTS $HOST -t "/usr/bin/virsh qemu-agent-command $ACCT --timeout 60 '{\"execute\":\"guest-fstrim\"}' >/dev/null 2>&1" +``` + +Disc config: +``` + <disk type='block' device='disk'> + <driver name='qemu' type='raw' cache='none' io='threads' discard='unmap'/> + <source dev='/dev/vm/p639937'/> + <backingStore/> + <target dev='sda' bus='scsi'/> + <iotune> + <write_bytes_sec>104857600</write_bytes_sec> + <write_bytes_sec_max>524288000</write_bytes_sec_max> + <write_bytes_sec_max_length>120</write_bytes_sec_max_length> + </iotune> + <address type='drive' controller='0' bus='0' target='0' unit='0'/> + </disk> +``` + +Sometimes trimming working after migration, bit this is very rare. +We have try rescanning disc, drop caches on vm after migration, but didnt help. + +Inside vm's ext4 fs and almalinux 8/ubuntu 20+/debian 10-11 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1650 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1650 new file mode 100644 index 000000000..63984c3bf --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1650 @@ -0,0 +1,14 @@ +Consider doing runtime detection of MAP_FIXED_NOREPLACE +Description of problem: +``` +qemu-i386-static: Unable to reserve 0xfffff000 bytes of virtual address space at 0x1000 (Operation not supported) for use as guest address space (check your virtual memory ulimit setting, min_mmap_addr or reserve less using -R option) +``` +strace says +``` + mmap(0x1000, 4294963200, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_NORESERVE|MAP_FIXED_NOREPLACE, -1, 0) = -1 EOPNOTSUPP (Operation not supported) +``` +Steps to reproduce: +1. `apt install qemu-i386-static 32subsystem` +2. `strace qemu-i386-static /opt/32/bin/as` +Additional information: +Repeating the strace call in a minimal C program gives the same errno as expected -- the kernel is only 4.4. The problem here is that qemu only does `MAP_FIXED_NOREPLACE` feature detection at build-time via a `#ifndef` and even that behavior is poorly documented. Maybe do something at runtime? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1652 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1652 new file mode 100644 index 000000000..0c410f756 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1652 @@ -0,0 +1,32 @@ +make check failed about qemu@master on debian10_aarch64 +Description of problem: +make check failed about qemu@master on debian10_aarch64 +Steps to reproduce: +1../configure +2.make -j16 +3.make -j16 check +Additional information: +error: +>>> QTEST_QEMU_STORAGE_DAEMON_BINARY=./storage-daemon/qemu-storage-daemon QTEST_QEMU_IMG=./qemu-img G_TEST_DBUS_DAEMON=/home/stage/root/spack-stage-qemu-master-d6wsqaf6ydt7c6frhxqd3nyqhh72vz7v/spack-src/tests/dbus-vmstate-daemon.sh MALLOC_PERTURB_=105 QTEST_QEMU_BINARY=./qemu-system-aarch64 /home/stage/root/spack-stage-qemu-master-d6wsqaf6ydt7c6frhxqd3nyqhh72vz7v/spack-src/build/tests/qtest/migration-test --tap -k +――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――― ✀ ――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――― +stderr: +Broken pipe +../tests/qtest/libqtest.c:184: kill_qemu() tried to terminate QEMU process but encountered exit status 1 (expected 0) + + +TAP parsing error: Too few tests run (expected 18, got 0) +(test program exited with status code -6) +―――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――― + +190/627 qemu:qtest+qtest-aarch64 / qtest-aarch64/arm-cpu-features ERROR 0.34s killed by signal 6 SIGABRT +>>> QTEST_QEMU_STORAGE_DAEMON_BINARY=./storage-daemon/qemu-storage-daemon QTEST_QEMU_IMG=./qemu-img G_TEST_DBUS_DAEMON=/home/stage/root/spack-stage-qemu-master-d6wsqaf6ydt7c6frhxqd3nyqhh72vz7v/spack-src/tests/dbus-vmstate-daemon.sh MALLOC_PERTURB_=115 QTEST_QEMU_BINARY=./qemu-system-aarch64 /home/stage/root/spack-stage-qemu-master-d6wsqaf6ydt7c6frhxqd3nyqhh72vz7v/spack-src/build/tests/qtest/arm-cpu-features --tap -k +――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――― ✀ ――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――― +stderr: +qemu-system-aarch64: Failed to retrieve host CPU features +Broken pipe +../tests/qtest/libqtest.c:184: kill_qemu() tried to terminate QEMU process but encountered exit status 1 (expected 0) + + +TAP parsing error: Too few tests run (expected 5, got 1) +(test program exited with status code -6) +―――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――― diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1653 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1653 new file mode 100644 index 000000000..cd8369204 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1653 @@ -0,0 +1,20 @@ +qemu uses uefi to install the redhad6.0 VM, use the vnc connect it which is stuck +Description of problem: +I want to use uefi(udk2-->ovmf.fd) to install redhad6.0, but after I enter uefi and start up, I cannot use vnc to connect to it,The screen is black or often stuck, nor can I use the console of other pages, or it is a special slow to be able to use it. It's sure that the virtual machine is not crash. Anad the same operation is normal for redhad6.1 systems. +Steps to reproduce: +1.compile udk2 generate ovmf.fd +compile config: + +make -C BaseTools/Source/C + +./OvmfPkg/build.sh -D DEBUG_ON_SERIAL_PORT=true + + +2.run qemu with "-bios /bin/OVMF.fd" + + +3.use vnc to connet it + + + +The screen is stuck can't handle it. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1654 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1654 new file mode 100644 index 000000000..642abe676 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1654 @@ -0,0 +1,81 @@ +Memory out of bounds access vulnerability when guest accesses Block Limits information of SCSI devices +Description of problem: +When a guest uses a Linux kernel version 5.19 or higher and uses an scsi device, there will be a memory access violation, which can be clearly seen when ASAN is turned on. + +**reason：** +Linux kernel 5.19 merge commit： + +https://github.com/torvalds/linux/commit/c92a6b5d63359dd6d2ce6ea88ecd8e31dd769f6b + +The Linux kernel will first issue a header request to obtain the VPD length before obtaining the VPD information. The BUF for obtaining the VPD length is less than 8 bytes. However, QEMU regards the header for obtaining the VPD length as obtaining all VPD information, and a memory access violation occurs when writing information to BUF. + +The specific memory out of bounds information is as follows: +==12430==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases! + +==12430==WARNING: ASan is ignoring requested __asan_handle_no_return: stack top: +0x7fffebc1d000; bottom 0x7f61115ee000; size: 0x009eda62f000 (682268749824) + +False positive error reports may follow + +==12430==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x60200024d858 at pc 0x55767513791c bp 0x7f6111fcddc0 sp 0x7f6111fcddb0 + +WRITE of size 4 at 0x60200024d858 thread T0 + + #0 0x55767513791b in stl_he_p /root/hci/qemu/qemu-5.0.0/include/qemu/bswap.h:357 + + #1 0x55767513791b in stl_be_p /root/hci/qemu/qemu-5.0.0/include/qemu/bswap.h:464 + + #2 0x55767513791b in scsi_handle_inquiry_reply hw/scsi/scsi-generic.c:173 + + #3 0x55767513791b in scsi_read_complete hw/scsi/scsi-generic.c:318 + + #4 0x55767545d7c6 in blk_aio_complete block/block-backend.c:1425 + + #5 0x557675544d79 in coroutine_trampoline util/coroutine-ucontext.c:115 + + #6 0x7f611b9f14df (/lib/x86_64-linux-gnu/libc.so.6+0x5b4df) + +0x60200024d858 is located 4 bytes to the right of 4-byte region [0x60200024d850,0x60200024d854) + +allocated by thread T0 here: + + #0 0x557674a987f2 in malloc (/sf/bin/qemu-system-x86_64+0x7827f2) + + #1 0x7f6120141d41 in g_malloc (/usr/lib/libglib256-2.0.so.0+0x61d41) + + #2 0x557675137bb4 in scsi_send_command hw/scsi/scsi-generic.c:459 + + #3 0x55767513e902 in scsi_req_enqueue hw/scsi/scsi-bus.c:836 + + #4 0x557674c5f26e in virtio_scsi_handle_cmd_req_submit /root/hci/qemu/qemu-5.0.0/hw/scsi/virtio-scsi.c:589 + + #5 0x557674c5f26e in virtio_scsi_handle_cmd_vq /root/hci/qemu/qemu-5.0.0/hw/scsi/virtio-scsi.c:634 + + #6 0x557674c61089 in virtio_scsi_data_plane_handle_cmd /root/hci/qemu/qemu-5.0.0/hw/scsi/virtio-scsi-dataplane.c:60 + + #7 0x557674c9a520 in virtio_queue_notify_aio_vq /root/hci/qemu/qemu-5.0.0/hw/virtio/virtio.c:2338 + + #8 0x55767552c7c4 in aio_dispatch_handler util/aio-posix.c:328 + +SUMMARY: AddressSanitizer: heap-buffer-overflow /root/hci/qemu/qemu-5.0.0/include/qemu/bswap.h:357 stl_he_p +Steps to reproduce: +1. QEMU Enable ASAN +2. Use a guest with a Linux kernel version greater than 5.19 and mount an scsi physical device +3. Upon startup, memory out of bounds access can be detected +Additional information: +At present, I have made some simple modifications, but I am not sure if this is the best solution and can serve as a reference. + +Make a judgment on buflen, ignore the header information issued by the Linux kernel, and write the VPD information when issuing the actual instruction to obtain VPD information. + +hw/scsi/scsi-generic.c:scsi_handle_inquiry_reply + +``` +if (r->buflen >= 12) { + stl_be_p(&r->buf[8], max_transfer); +} +if (r->buflen >= 16){ + /* Also take care of the opt xfer len. */ + stl_be_p(&r->buf[12], + MIN_NON_ZERO(max_transfer, ldl_be_p(&r->buf[12]))); +} +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1655 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1655 new file mode 100644 index 000000000..afd30367f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1655 @@ -0,0 +1 @@ +qemu-7.2.2 build failed diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1656 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1656 new file mode 100644 index 000000000..fcb0d2498 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1656 @@ -0,0 +1,7 @@ +https://wiki.qemu.org/: TLS certificate has expired (`May 14 21:15:57 2023 GMT`) +Description of problem: +The ceritficate for https://wiki.qemu.org/ has expired on May 14 21:15:57 2023 GMT. +Steps to reproduce: +1. Browse https://wiki.qemu.org/ +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/166 b/gitlab/issues_text/target_missing/host_missing/accel_missing/166 new file mode 100644 index 000000000..7827b94dd --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/166 @@ -0,0 +1 @@ +qemu-bridge-helper failure but qemu not exit diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1662 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1662 new file mode 100644 index 000000000..d2430b3f6 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1662 @@ -0,0 +1,35 @@ +qemu-system-loongarch64 start Loongnix system coredump +Description of problem: + +Steps to reproduce: +1. build qemu: + ./configure --prefix=/usr --disable-werror --disable-gtk --target-list="loongarch64-softmmu"\ + --enable-debug + make -j32 +2. get bios and qcow2: + wget https://mirrors.wsyu.edu.cn/loongarch/archlinux/images/QEMU_EFI_7.2.fd + wget http://pkg.loongnix.cn/loongnix/isos/Loongnix-20.4/Loongnix-20.4.cartoon.gui.loongarch64.en.qcow2 +3. start Loongnix + ./build/qemu-system-loongarch64 \ + -m 8G \ + -cpu la464 \ + -machine virt \ + -smp 16 \ + -bios ./QEMU_EFI_7.2.fd \ + -serial stdio \ + -device virtio-gpu-pci \ + -net nic -net user \ + -device nec-usb-xhci,id=xhci,addr=0x1b \ + -device usb-tablet,id=tablet,bus=xhci.0,port=1 \ + -device usb-kbd,id=keyboard,bus=xhci.0,port=2 \ + -device virtio-blk-pci,drive=test -drive if=none,id=test,file=./Loongnix-20.4.cartoon.gui.loongarch64.en.qcow2 + +4. VNC connect +5. use the system + login loongson/Loongson20 +6. qemu coredump + + qemu-system-loongarch64: /root/work/qemu/include/tcg/tcg.h:675: temp_idx: Assertion `n >= 0 && n < tcg_ctx->nb_temps' failed. +./start-loongnix.sh: line 13: 40242 Aborted (core dumped) ./build/qemu-system-loongarch64 -m 8G -cpu la464 -machine virt -smp 16 -bios ./QEMU_EFI_7.2.fd -serial stdio -device virtio-gpu-pci -net nic -net user -device nec-usb-xhci,id=xhci,addr=0x1b -device usb-tablet,id=tablet,bus=xhci.0,port=1 -device usb-kbd,id=keyboard,bus=xhci.0,port=2 -device virtio-blk-pci,drive=test -drive if=none,id=test,file=./Loongnix-20.4.cartoon.gui.loongarch64.en.qcow2 +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1663 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1663 new file mode 100644 index 000000000..9ef0f6506 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1663 @@ -0,0 +1,34 @@ +make check-venv fails with errors about incompatible avocado +Description of problem: +``` +$ rm -rf build/ +$ ./configure --target-list=x86_64-softmmu,i386-softmmu +$ make -j 16 +$ ./scripts/device-crash-test -q --tcg-only ./qemu-system-i386 +Module 'qemu' not found. + Try 'make check-venv' from your build directory, + and then one way to run this script is like so: + > $builddir/pyvenv/bin/python3 "/home/berrange/src/virt/qemu/scripts/device-crash-test" +$ make check-venv +make[1]: Entering directory '/home/berrange/src/virt/qemu/build' + GIT ui/keycodemapdb tests/fp/berkeley-testfloat-3 tests/fp/berkeley-softfloat-3 dtc + VENVPIP install -e /home/berrange/src/virt/qemu/python/ + VENVPIP install -r /home/berrange/src/virt/qemu/tests/requirements.txt +ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts. +avocado-framework-plugin-varianter-yaml-to-mux 98.0 requires avocado-framework==98.0, but you have avocado-framework 101.0 which is incompatible. +avocado-framework-plugin-result-html 98.0 requires avocado-framework==98.0, but you have avocado-framework 101.0 which is incompatible. +make[1]: Leaving directory '/home/berrange/src/virt/qemu/build' +``` + +Despite this, it seems to have at least partially populated the venv, since I can now run device-crash-test. + +My host does have some avocado related python bits present: + +``` +python-avocado-common-98.0-1.module_f38+15908+ffe8d4e2.noarch +python3-avocado-98.0-1.module_f38+15908+ffe8d4e2.noarch +python3-avocado-plugins-output-html-98.0-1.module_f38+15908+ffe8d4e2.noarch +python3-avocado-plugins-varianter-yaml-to-mux-98.0-1.module_f38+15908+ffe8d4e2.noarch +``` + +I would expect the venv to not use these host packages however, since they're outdated compare to what QEMU askes for in tests/requirements.txt diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1664 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1664 new file mode 100644 index 000000000..59c12a3a8 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1664 @@ -0,0 +1 @@ +mingw64 cross compile: libslirp from subproject fails to link, undefined reference to WinMain diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1665 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1665 new file mode 100644 index 000000000..1ad56086a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1665 @@ -0,0 +1 @@ +When using the"yum install qemu-kvm" command in in rhel 9 , it is not possible to proceed past the "Windows Installer Select Disk" page by iso install diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1666 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1666 new file mode 100644 index 000000000..00ddeafc4 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1666 @@ -0,0 +1 @@ +About the develop environment diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1669 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1669 new file mode 100644 index 000000000..e018bf311 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1669 @@ -0,0 +1,11 @@ +In the ARM environment, using pci-ohci with specific OS (CentOS-8-aarch64-1905-dvd1.iso) to start a virtual machine, will cause the memory leak +Description of problem: + +Steps to reproduce: +1.Using the pci-ohci as the USB controller to start the VM; + +2.install the OS using the CentOS-8-aarch64-1905-dvd1.iso ; + +3.The QEMU process is taking up more and more memory, which looks like Memory leak +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/167 b/gitlab/issues_text/target_missing/host_missing/accel_missing/167 new file mode 100644 index 000000000..85045ca71 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/167 @@ -0,0 +1 @@ +qemu 4.0 doesnt support glsl 3.0 but yes older versions, that have no sense IMO diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1670 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1670 new file mode 100644 index 000000000..fea5bf206 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1670 @@ -0,0 +1,9 @@ +Cannot statically build x86_64-softmmu with Darwin(Intel) +Description of problem: +I am using `Podman` and currently,`Podman` uses qemu on macOS. The `Podman` team has adopted a scheme to dynamically compile `qemu` (https://github.com/containers/podman-machine-qemu). However, I am currently trying to use static compilation for both amd64 and arm64 targets. + +I have searched many articles online, most of which are about static compilation on Linux. Very few articles mention static compilation on macOS, and some mention that `softmmu` does not support static compilation. However, I have not found any concrete evidence to support this claim. + +I also want to ask another question: Does `qemu` support static compilation on macOS? +Additional information: +[meson-log.txt](/uploads/6e32691488533a06c64dc34ee4514135/meson-log.txt) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1672 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1672 new file mode 100644 index 000000000..f5d9b1d24 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1672 @@ -0,0 +1,8 @@ +failed to migrate using multifd with multifd-channels larger than 2 +Description of problem: +try to using multifd live migration on QEMU v8.0.0 using multifd channels larger than 2, but failed. +Steps to reproduce: +1. start source / dest qemu vm +2. migrate_set_capability multifd on && migrate_set_parameter multifd-channels 8 + +then live migration will failed diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1673 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1673 new file mode 100644 index 000000000..96fe071b3 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1673 @@ -0,0 +1,49 @@ +compilation of 8.0.0 FAILED: target/hexagon/idef-generated-emitter.indented.c on ubuntu 18.04 +Description of problem: +Cannot compile on ubuntu 18.04. +Steps to reproduce: +1. get 8.0.0 tarball or git clone/submodule... on a ubuntu 18.04 system (with a few more recent tools in ~/opt, such as python 3.9) +2. ./configure --prefix=$HOME/opt && make +3. It finishes with this strange error: FAILED: target/hexagon/idef-generated-emitter.indented.c +``` +... +[850/10154] Compiling C object target/hexagon/idef-parser.p/meson-generated_idef-parser.yy.c.o +[851/10154] Compiling C object target/hexagon/idef-parser.p/meson-generated_idef-parser.tab.c.o +[852/10154] Compiling C object target/hexagon/idef-parser.p/_home_pbourguignon_opt_src_qemu-8.0.0_target_hexagon_idef-parser_parser-helpers.c.o +[853/10154] Linking target target/hexagon/idef-parser +[854/10154] Generating target/hexagon/idef-generated-tcg with a custom command +[855/10154] Generating target/hexagon/indent with a custom command +FAILED: target/hexagon/idef-generated-emitter.indented.c +/home/pbourguignon/bin/indent -linux target/hexagon/idef-generated-emitter.c -o target/hexagon/idef-generated-emitter.indented.c +Indenting region... +Indenting region... done +Directory `/home/pbourguignon/opt/src/qemu-8.0.0/build/-linux target/hexagon/idef-generated-emitter.c -o target/hexagon/' does not exist; create? (y or n) Error reading from stdin +ninja: build stopped: subcommand failed. +Makefile:165: recipe for target 'run-ninja' failed +make[1]: *** [run-ninja] Error 1 +make[1]: Leaving directory '/home/pbourguignon/opt/src/qemu-8.0.0/build' +GNUmakefile:10: recipe for target 'all' failed +make: *** [all] Error 2 +``` +Additional information: +https://dpaste.org/Hr9Zq +``` +~/opt/src/qemu-git +16:15[pbourguignon@frprld7818008 :0.0 qemu-git ]$ ls ~/opt/bin +./ ecl-config* pydoc3@ run-avr* run-microblaze* +../ emacs@ pydoc3.9* run-bfin* run-mips* +2to3@ emacs-27.2* python@ run-bpf* run-mn10300* +2to3-3.9* emacsclient* python3@ run-cr16* run-moxie* +bundle* erb* python3-config@ run-cris* run-msp430* +bundler* etags* python3.9* run-d10v* run-or1k* +ccl* gcore* python3.9-config* run-erc32* run-ppc* +ccmake* gdb* racc* run-frv* run-pru* +cmake* gdb-add-index* rake* run-ft32* run-riscv* +cpack* gdbserver* rbs* run-h8300* run-rl78* +ctags* gem* rdbg* run-iq2000* run-rx* +ctest* idle3@ rdoc* run-lm32* run-sh* +curl* idle3.9* ri* run-m32c* run-v850* +curl-config* irb* ruby* run-m32r* sbcl* +ebrowse* pip3* run-aarch64* run-m68hc11* sis* +ecl* pip3.9* run-arm* run-mcore* typeprof* +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1674 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1674 new file mode 100644 index 000000000..31b27860e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1674 @@ -0,0 +1,23 @@ +Arrow key not functional in QEMU monitor when using nographic on Windows 11 host +Description of problem: +The arrow keys do not work on the Windows QEMU when using -nographic option. On the Linux QEMU they work. +Steps to reproduce: +1. Download the qemu source code from https://download.qemu.org/qemu-8.0.0.tar.xz. THe sha256sum of the file is bb60f0341531181d6cc3969dd19a013d0427a87f918193970d9adb91131e56d0. +2. Prepare the build system on MSYS2 according to the instructions on https://wiki.qemu.org/Hosts/W32#Native_builds_with_MSYS2. +3. Uncompress the source code using `tar -xf qemu-8.0.0.tar.xz`. +4. Change the working directory to qemu-8.0.0/. The build configuration command is `./configure --target-list=arm-softmmu --extra-cflags="-g -ggdb"` +5. Run the command `./qemu-system-arm -s -S -M virt -nographic`. +6. Press Ctrl-C A to switch to QEMU monitor. +7. Input "help" command to the monitor. +8. Press Arrow-Up key. +9. The previous "help" command does not appear in the monitor prompt. +Additional information: +1. The pre-built binary downloaded from https://qemu.weilnetz.de/w64/qemu-w64-setup-20230424.exe has the same behaviour. +2. The QEMU from MSYS2, `pacman -S mingw-w64-x86_64-qemu`, has the same behaviour. +3. If the "-nographic" option is removed, the arrow-up key works in the GTK console. +4. Neither of arrow-up, arrow-down, arrow-right, arrow-left key work. +5. If the valid kernel and rootfs are added in the command line by "-kernel" and "-initrd" options, neither key work after booting to the Linux successfully. +6. If the code `dwMode |= ENABLE_LINE_INPUT;` in the function `qemu_chr_open_stdio()` is changed to `dwMode |= ENABLE_LINE_INPUT|ENABLE_VIRTUAL_TERMINAL_INPUT;`, build again. All arrow keys work. +7. The VT sequence support was added in `EmulatorPkg/Win/Host/WinThunk.c` by this commit https://gitlab.com/qemu-project/edk2/-/commit/5601e90d5cdbc4cea748e00e34ae07ce39bd700f. +8. The above commit is to add VT sequence support at compile-time. Microsoft provides some code to enable it at run-time on https://learn.microsoft.com/en-us/windows/console/console-virtual-terminal-sequences#example-of-enabling-virtual-terminal-processing. +9. The function readline_handle_byte() is not called when the VT sequence is not enabled. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1675 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1675 new file mode 100644 index 000000000..947ba0379 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1675 @@ -0,0 +1 @@ +virtual machines still randomly crashing on kernel 6.1.30 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1676 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1676 new file mode 100644 index 000000000..6ce8bf948 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1676 @@ -0,0 +1,7 @@ +Signed release tarball for 8.0.2 is missing +Description of problem: +Hi! I package QEMU for Arch Linux. I usually rely on the signed tarballs (which are also linked to from the website). +For [8.0.2](https://gitlab.com/qemu-project/qemu/-/tags/v8.0.2) there does not seem to be a signed tarball though. +Steps to reproduce: +1. Try to update to 8.0.2 using a signed tarball +2. Find no signed tarball in https://download.qemu.org/ diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1677 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1677 new file mode 100644 index 000000000..5cca58e53 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1677 @@ -0,0 +1,13 @@ +qemu-system-x86_64 cannot run on Windows when -smp is specified with a value higher than `1`. An important argument for any expectation of VM performance +Description of problem: +qemu-system-x86_64 seems to crash on Windows the moment you try to use -smp to define more vcpus, even the basic usage of `-smp 4` will cause qemu to segfault after the guest's boot option is selected. +Steps to reproduce: +1. `qemu-system-x86_64 -smp 4 -cdrom rhel-9.2-x86_64-dvd.iso -drive if=pflash,format=raw,unit=0,readonly=on,file=edk2-x64/OVMF_CODE.fd -m 6G -nodefaults -serial mon:stdio` +2. Select the boot option to begin your installation +3. qemu hangs for 10 or so seconds then throws a Segmentation Fault. +Additional information: +1. This does not happen if -smp arguments are omitted, but running VMs with a single vcpu thread is slow and painful. +2. This still happens even without OVMF (Traditional bios booting) +3. This still happens even without -defaults and without a serial device + +Only output from qemu at death is `Segmentation fault` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1679 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1679 new file mode 100644 index 000000000..3638ffb44 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1679 @@ -0,0 +1,15 @@ +Running Qemu on windows arm64 host, and use qemu-system-x86_64 to emulate an ubuntu OS, but it didn't work.Enter the issue title +Description of problem: +Running QemuV8.0 on windows arm64 host, and use qemu-system-x86_64 to emulate an ubuntu OS, but it didn't work. +Steps to reproduce: +1.qemu-img.exe create hdd.img 10G + +2.qemu-system-x86_64.exe -m 8096 hdd.img -cdrom ubuntu22.04-desktop-amd64.iso -machine pc +Additional information: +both Use qemu v8.0 and qemu v8.1 to test, but failed also + + + +Thanks, + +Jianbin diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1680 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1680 new file mode 100644 index 000000000..5f4c39e92 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1680 @@ -0,0 +1,102 @@ +qemu-system-x86_64: ../softmmu/memory.c:1111: memory_region_transaction_commit: Assertion `qemu_mutex_iothread_locked()' failed. +Description of problem: +While testing master build, I have the following crash on shutdown of the VM: +qemu-system-x86_64: ../softmmu/memory.c:1111: memory_region_transaction_commit: Assertion `qemu_mutex_iothread_locked()' failed. +Steps to reproduce: +1. Run VM +2. Once booted, do poweroff inside the Linux VM +3. When poweroff completes, qemu crashes. +Additional information: +```(gdb) bt full +#0 0x00007ffff29edacf in raise () at /lib64/libc.so.6 +#1 0x00007ffff29c0ea5 in abort () at /lib64/libc.so.6 +#2 0x00007ffff29c0d79 in _nl_load_domain.cold.0 () at /lib64/libc.so.6 +#3 0x00007ffff29e6426 in () at /lib64/libc.so.6 +#4 0x0000555555bed6d3 in memory_region_transaction_commit () at ../softmmu/memory.c:1111 + as = <optimized out> + __PRETTY_FUNCTION__ = "memory_region_transaction_commit" +#5 0x0000555555bef2bf in memory_region_add_eventfd (mr=mr@entry=0x555557c318a0, addr=<optimized out>, size=size@entry=0, match_data=<optimized out>, data=<optimized out>, e=<optimized out>) at ../softmmu/memory.c:2583 + mrfd = {addr = {start = 0, size = 0}, match_data = false, data = 0, e = 0x555557c41aa4} + i = <optimized out> +#6 0x0000555555a2c85c in virtio_pci_ioeventfd_assign (d=0x555557c30a00, notifier=0x555557c41aa4, n=0, assign=<optimized out>) at ../hw/virtio/virtio-pci.c:347 + proxy = 0x555557c30a00 + vdev = <optimized out> + vq = <optimized out> + legacy = true + modern = <optimized out> + fast_mmio = true + modern_pio = false + modern_mr = <optimized out> + modern_notify_mr = 0x555557c319c0 + legacy_mr = 0x555557c31430 + modern_addr = <optimized out> +#7 0x0000555555a2be78 in virtio_bus_set_host_notifier (bus=0x555557c38d50, n=n@entry=0, assign=assign@entry=true) at ../hw/virtio/virtio-bus.c:296 + vdev = <optimized out> + k = 0x555556a7b620 + proxy = 0x555557c30a00 + vq = 0x555557c41a30 + notifier = 0x555557c41aa4 + r = <optimized out> + __func__ = "virtio_bus_set_host_notifier" +#8 0x0000555555ba1595 in virtio_scsi_set_host_notifier (s=s@entry=0x555557c38dd0, n=n@entry=0, vq=<optimized out>) at /root/qemu/include/hw/virtio/virtio-bus.h:35 + qbus = <optimized out> + rc = <optimized out> +#9 0x0000555555ba1860 in virtio_scsi_dataplane_start (vdev=<optimized out>) at ../hw/scsi/virtio-scsi-dataplane.c:130 + i = <optimized out> + rc = <optimized out> + vq_init_count = 0 + qbus = 0x555557c38d50 + k = 0x555556a7b620 + vs = 0x555557c38dd0 + s = 0x555557c38dd0 +#10 0x0000555555a2bbd2 in virtio_bus_start_ioeventfd (bus=0x555557c38d50) at ../hw/virtio/virtio-bus.c:236 + k = <optimized out> + proxy = 0x555557c30a00 + vdev = 0x555557c38dd0 + vdc = 0x555556a19cc0 + r = <optimized out> + __func__ = "virtio_bus_start_ioeventfd" +#11 0x0000555555bc0739 in virtio_device_start_ioeventfd (vdev=vdev@entry=0x555557c38dd0) at ../hw/virtio/virtio.c:3741 + qbus = <optimized out> + vbus = <optimized out> +#12 0x0000555555b9fc80 in virtio_scsi_defer_to_dataplane (s=0x555557c38dd0) at ../hw/scsi/virtio-scsi.c:614 + s = 0x555557c38dd0 +#13 0x0000555555b9fc80 in virtio_scsi_defer_to_dataplane (s=0x555557c38dd0) at ../hw/scsi/virtio-scsi.c:608 + s = 0x555557c38dd0 +#14 0x0000555555b9fc80 in virtio_scsi_handle_event (vdev=<optimized out>, vq=<optimized out>) at ../hw/scsi/virtio-scsi.c:1011 + s = 0x555557c38dd0 +#15 0x0000555555bba2af in virtio_queue_notify_vq (vq=0x555557c41ac8) at ../hw/virtio/virtio.c:2248 + vdev = 0x555557c38dd0 +#16 0x0000555555de7b08 in aio_dispatch_handler (ctx=ctx@entry=0x555556c2c130, node=0x555557ffbff0) at ../util/aio-posix.c:356 + progress = false + poll_ready = true + revents = <optimized out> +#17 0x0000555555de861c in aio_dispatch_ready_handlers (ready_list=0x7fffde952fe8, ctx=0x555556c2c130) at ../util/aio-posix.c:401 + progress = false + node = <optimized out> + ready_list = {lh_first = 0x0} + progress = true + use_notify_me = <optimized out> + timeout = <optimized out> + start = <optimized out> + __PRETTY_FUNCTION__ = "aio_poll" +#18 0x0000555555de861c in aio_poll (ctx=0x555556c2c130, blocking=blocking@entry=true) at ../util/aio-posix.c:723 + ready_list = {lh_first = 0x0} + progress = true + use_notify_me = <optimized out> + timeout = <optimized out> + start = <optimized out> + __PRETTY_FUNCTION__ = "aio_poll" +#19 0x0000555555ca9ae6 in iothread_run (opaque=opaque@entry=0x555556943200) at ../iothread.c:63 + iothread = 0x555556943200 +#20 0x0000555555deaf6a in qemu_thread_start (args=<optimized out>) at ../util/qemu-thread-posix.c:541 + __cancel_buf = {__cancel_jmp_buf = {{__cancel_jmp_buf = {93825016192880, 1094026140696841148, 140737488341294, 140737488341295, 140737488341440, 140736927707584, 6520036150746942396, 1094028099712322492}, __mask_was_saved = 0}}, __pad = {0x7fffde953110, 0x0, 0x0, 0x0}} + __cancel_routine = 0x555555deafc0 <qemu_thread_atexit_notify> + __not_first_call = <optimized out> + qemu_thread_args = <optimized out> + start_routine = 0x555555ca9aa0 <iothread_run> + arg = 0x555556943200 + r = <optimized out> +#21 0x00007ffff2d6c1ca in start_thread () at /lib64/libpthread.so.0 +#22 0x00007ffff29d8e73 in clone () at /lib64/libc.so.6 +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1681 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1681 new file mode 100644 index 000000000..84d2f77d1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1681 @@ -0,0 +1,49 @@ +watchdog: BUG: soft lockup - CPU#N stuck for XXs! +Description of problem: +Repeatedly seeing Qemu VMs locking up with guest Linux kernel reporting: +"watchdog: BUG: soft lockup - CPU#<N> stuck for <XX>s!" +e.g.: "watchdog: BUG: soft lockup - CPU#5 stuck for 26s! [swapper/5:0]" + +When the guest VM is in this condition, the host Linux OS reports that the Qemu process is typically running steadily at ~250% CPU. +Steps to reproduce: +1. Windows 10 on an x64 PC (right on the metal). +2. VMWare Workstation running Fedora Workstation 38 x64 guest, in turn acting as host with nested virtualization. +3. Qemu 7.2.1 running on Fedora host with Fedora Server 38 x64 guest. +4. Invoke Qemu using F38 QCow2 image: `$ qemu-system-x86_64 -machine pc -cpu max -smp 8 -accel kvm -accel hvf -accel tcg -m 3G -nographic -hda Client.qcow2 -nic socket,model=virtio-net-pci,mcast=239.1.2.3:4567,mac=4a:e0:72:85:c0:fb -nic user,model=virtio-net-pci,mac=4a:e0:d8:cd:a5:e6,hostfwd=tcp:127.0.0.1:2288-:22` +5. Not necessarily right away, but pretty consistently if left running overnight, guest Linux kernel repeatedly reports CPU(s) stuck, guest VM is unresponsive +6. Host Linux `top` reports Qemu process using ~250% CPU. +Additional information: +Console log attached, small sample here: + +``` +[ 181.101152] watchdog: BUG: soft lockup - CPU#5 stuck for 26s! [swapper/5:0] +[ 181.145578] Modules linked in: nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nfg +[ 181.145578] CPU: 5 PID: 0 Comm: swapper/5 Not tainted 6.2.9-300.fc38.x86_64 #1 +[ 181.145578] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-1.fc38 04/01/2014 +[ 181.145578] RIP: 0010:netif_receive_skb_list_internal+0x58/0x300 +[ 181.145578] Code: 4c 89 74 24 08 49 89 ec 4c 89 74 24 10 4c 8b 6d 00 48 39 ef 75 14 eb 7c 49 8b 8 +[ 181.145578] RSP: 0018:ff5a086d401b8da8 EFLAGS: 00000202 +[ 181.145578] RAX: 0000000000000000 RBX: ff2d02b1b404c910 RCX: 0000000000000100 +[ 181.145578] RDX: 0000000000000000 RSI: 0000000000000001 RDI: ff2d02b1b404c910 +[ 181.145578] RBP: ff2d02b18998a600 R08: 0000000000000001 R09: ff2d02b188bd5d00 +[ 181.145578] R10: 000000000000000c R11: ffa7ad3980175000 R12: ff2d02b18998a600 +[ 181.145578] R13: ff2d02b1b404c910 R14: ff5a086d401b8db0 R15: ff2d02b1882d19c0 +[ 181.145578] FS: 0000000000000000(0000) GS:ff2d02b23cb40000(0000) knlGS:0000000000000000 +[ 181.145578] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 +[ 181.145578] CR2: 00007f232000f0d8 CR3: 0000000027010000 CR4: 0000000000751ee0 +[ 181.145578] PKRU: 55555554 +[ 181.145578] Call Trace: +[ 181.145578] <IRQ> +[ 181.145578] napi_complete_done+0x6e/0x1a0 +[ 181.145578] virtnet_poll+0x420/0x550 [virtio_net] +[ 181.145578] __napi_poll+0x2b/0x1b0 +[ 181.145578] net_rx_action+0x2a5/0x360 +[ 181.145578] ? vp_vring_interrupt+0x73/0x90 +[ 181.145578] __do_softirq+0xfd/0x31a +[ 181.145578] __irq_exit_rcu+0xd7/0x140 +[ 181.145578] common_interrupt+0xb9/0xd0 +[ 181.145578] </IRQ> +[ 181.145578] <TASK> +[ 181.145578] asm_common_interrupt+0x22/0x40 +[ 181.145578] RIP: 0010:native_safe_halt+0xb/0x10 +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1682 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1682 new file mode 100644 index 000000000..9139826db --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1682 @@ -0,0 +1,3 @@ +QEMU-USER macOS support +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1683 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1683 new file mode 100644 index 000000000..566b1418f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1683 @@ -0,0 +1 @@ +How to run qemu inside ubuntu:latest docker container? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1685 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1685 new file mode 100644 index 000000000..8c58a67e0 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1685 @@ -0,0 +1,59 @@ +QEMU segfaults when I restart Windows 11 VM with virtio-vga-gl +Description of problem: +When I restart the Windows 11 VM with the virtio GPU DoD driver installed, QEMU crashes with a SIGSEGV. This also happens if I try to uninstall this driver in the Device Manager. I attached the backtrace. +Steps to reproduce: +1. Install Windows 11 into the VM; +2. Install virtio GPU DoD driver; +3. Click Start -> Power -> Restart. +Additional information: +virtio-win version: 0.1.229 + +Backtrace: +``` +Thread 1 "qemu-system-x86" received signal SIGSEGV, Segmentation fault. +[Switching to Thread 0x7ffff64a3e80 (LWP 118206)] +_mesa_TexParameteri () at ../mesa-23.1.1/src/mesa/main/texparam.c:1248 +1248 texObj = _mesa_get_texobj_by_target_and_texunit(ctx, target, +(gdb) bt +#0 _mesa_TexParameteri() () at ../mesa-23.1.1/src/mesa/main/texparam.c:1248 +#1 0x00007ffece03cba2 in _mesa_unmarshal_TexParameteri () at src/mapi/glapi/gen/marshal_generated0.c:5332 +#2 0x00007ffecdf1bb30 in glthread_unmarshal_batch() () at ../mesa-23.1.1/src/mesa/main/glthread.c:122 +#3 0x00007ffecdf269c2 in _mesa_glthread_finish () at ../mesa-23.1.1/src/mesa/main/glthread.c:382 +#4 _mesa_glthread_finish() () at ../mesa-23.1.1/src/mesa/main/glthread.c:347 +#5 0x00007ffecdebd20f in dri_make_current () at ../mesa-23.1.1/src/gallium/frontends/dri/dri_context.c:303 +#6 dri_make_current () at ../mesa-23.1.1/src/gallium/frontends/dri/dri_context.c:287 +#7 driBindContext() () at ../mesa-23.1.1/src/gallium/frontends/dri/dri_util.c:701 +#8 0x00007ffee6e8693f in dri3_bind_context () at ../mesa-23.1.1/src/glx/dri3_glx.c:181 +#9 0x00007ffee6e78075 in MakeContextCurrent () at ../mesa-23.1.1/src/glx/glxcurrent.c:149 +#10 0x00007ffee7c84e73 in InternalMakeCurrentVendor + (dpy=dpy@entry=0x5555570fe3b0, draw=draw@entry=90177544, read=read@entry=90177544, ctxInfo=ctxInfo@entry=0x5555579418b0, callerOpcode=callerOpcode@entry=5 '\005', threadState=threadState@entry=0x55555702fbe0, vendor=0x55555707f520) at ../libglvnd-v1.6.0/src/GLX/libglx.c:871 +#11 0x00007ffee7c8bce1 in CommonMakeCurrent (dpy=0x5555570fe3b0, draw=90177544, read=90177544, context=0x55555780f760, callerOpcode=<optimized out>) + at ../libglvnd-v1.6.0/src/GLX/libglx.c:1053 +#12 0x00007ffff51f90b1 in X11_GL_MakeCurrent (_this=0x5555570c1aa0, window=<optimized out>, context=0x55555780f760) + at /usr/src/debug/sdl2/SDL2-2.26.5/src/video/x11/SDL_x11opengl.c:865 +#13 0x00007ffff51d0a3f in SDL_GL_MakeCurrent_REAL (window=0x5555570048b0, ctx=0x55555780f760) at /usr/src/debug/sdl2/SDL2-2.26.5/src/video/SDL_video.c:4120 +#14 0x00007ffff6492b86 in sdl2_gl_switch () at ../qemu-8.0.2/ui/sdl2-gl.c:83 +#15 0x000055555598efe2 in displaychangelistener_gfx_switch () at ../qemu-8.0.2/ui/console.c:1158 +#16 0x00005555559997aa in dpy_gfx_replace_surface () at ../qemu-8.0.2/ui/console.c:1815 +#17 0x0000555555d03398 in vga_draw_graphic () at ../qemu-8.0.2/hw/display/vga.c:1589 +#18 vga_update_display () at ../qemu-8.0.2/hw/display/vga.c:1789 +#19 vga_update_display () at ../qemu-8.0.2/hw/display/vga.c:1762 +#20 0x0000555555998acb in graphic_hw_update () at ../qemu-8.0.2/ui/console.c:234 +#21 0x00007ffff6493952 in sdl2_gl_refresh () at ../qemu-8.0.2/ui/sdl2-gl.c:113 +#22 0x000055555599d79a in dpy_refresh () at ../qemu-8.0.2/ui/console.c:1852 +#23 gui_update () at ../qemu-8.0.2/ui/console.c:169 +#24 0x0000555555fd9690 in timerlist_run_timers () at ../qemu-8.0.2/util/qemu-timer.c:576 +#25 0x0000555555fd97b4 in timerlist_run_timers () at ../qemu-8.0.2/util/qemu-timer.c:509 +#26 qemu_clock_run_timers () at ../qemu-8.0.2/util/qemu-timer.c:590 +#27 qemu_clock_run_all_timers () at ../qemu-8.0.2/util/qemu-timer.c:672 +#28 0x0000555555fd9a53 in main_loop_wait () at ../qemu-8.0.2/util/main-loop.c:603 +#29 0x0000555555e1ab17 in qemu_main_loop () at ../qemu-8.0.2/softmmu/runstate.c:731 +--Type <RET> for more, q to quit, c to continue without paging--c +#30 qemu_default_main () at ../qemu-8.0.2/softmmu/main.c:37 +#31 0x00007ffff6c15850 in __libc_start_call_main (main=main@entry=0x55555598baa0 <main>, argc=argc@entry=33, argv=argv@entry=0x7fffffffd338) + at ../sysdeps/nptl/libc_start_call_main.h:58 +#32 0x00007ffff6c1590a in __libc_start_main_impl + (main=0x55555598baa0 <main>, argc=33, argv=0x7fffffffd338, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffd328) + at ../csu/libc-start.c:360 +#33 0x000055555598e6f5 in _start () +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1686 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1686 new file mode 100644 index 000000000..d747734a7 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1686 @@ -0,0 +1,43 @@ +VPS does not boots with CPU Model QEMU64 or KVM64 +Description of problem: + +Steps to reproduce: +1. Boot the VPS using AlmaLinux 9 ISO / image and it boots to kernel panic +Additional information: +VNC shows this message : + +[ 1.749935] do_exit.cold+0x14/0x9f + +[1.7502581 do_group_exit+0x33/0xa0 + +1.7506001 _x64_sys_exit_group+0x14/0x20 + +1.7510081 do_syscall 64+0x5c/0x90 + +[1.751361] ? syscall_exit_to_user_mode+0x12/0x30 + +[1.7517911 ? do_syscall_64+0x69/0x90 + +[1.752131] ? do_user_addr_fault+0x1d8/0x698 + +[1.7525091 ? exc_page_fault+0x62/0x150 1.752896] entry_SYSCALL_64_after_hwframe+ +0x63/0xcd + +[1.753612] RIP: 0033:0x7fb0e95b62d1 + +[ 1.7539561 Code: c3 of 1f 84 00 00 00 00 00 f3 Of le fa be e7 00 00 00 ba 3c 00 00 00 eb Od 89 de Of 05 48 3d 00 fe ff ff 77 1c f4 89 fe of 05 <48> 3d 00 fe ff ff 76 e7 f7 d8 89 05 ff fe 00 00 eb dd of 1f 44 00 + +[ 1.755047] RSP: 002b:00007ffe484df 288 EFLAGS: 00000246 ORIG_RAX: 00000000000 + +000e7 + +[ 1.755590] RAX: fffff ffffda RBX: 00007fb0e95b0f30 RCX: 00007fb0e95b62d1 1.756100] RDX: 000000000000003c RSI: 00000000000000e7 RDI: 000000000000007f + +[1.756565] RBP: 00007ffe484df410 R08: 00007ffe484dedf9 R09: 0000000000000000 + +[ 1.757034] R10: 00000000ffffffff R11: 0000000000000246 R12: 00007fb0e958f000 + +[ 1.7574981 R13: 0000002300000007 R14: 0000000000000007 R15: 00007ffe484df420 + +[ 1.7579921 Kernel Offset: 0x3aa00000 from Oxffffffff81000000 (relocation ran ge: 0xffffffff80000000-0xffffffffbfffffff) + +[ 1.7589051---[ end Kernel panic code=0x00007f00 --- not syncing: Attempted to kill init! exit diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1687 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1687 new file mode 100644 index 000000000..1c685f4fa --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1687 @@ -0,0 +1,53 @@ +Memory leak for x86 guest on macOS ARM host +Description of problem: +QEMU is used by docker to run `x86` binaries on Apple silicon. Then using `mmap` followed by `munmap` results in a memory leak manifested by continuously growing RSS memory usage when running `mmap` and `munmap` in a loop, e.g., when running the following binary: + +``` +#include <stdio.h> +#include <unistd.h> +#include <sys/mman.h> + +const int page = 4096; + +int work(int N) { + int *ptr = mmap(NULL, N * sizeof(int), PROT_WRITE, MAP_PRIVATE | MAP_ANONYMOUS, 0, 0); + + if (ptr == MAP_FAILED) { + printf("Mapping Failed\n"); + return 1; + } + + for(int i = 0; i < N; i++) { + ptr[i] = i * 10; + } + + int err = munmap(ptr, N * sizeof(int)); + if (err != 0) { + printf("UnMapping Failed\n"); + return 1; + } + + return 0; +} + +int main() { + int N = page * 1024; + + while (1) { + int res = work(N); + if (res) { + return res; + } + printf(".\n"); + } + + return 0; +} +``` +Steps to reproduce: +``` +$ LEAK=$(docker run --platform linux/amd64 -d -it martin2718/mmap-leak ./a.out) +$ docker exec -it $LEAK top # you should observe that RES for a.out keeps growing +$ docker exec -it $LEAK pmap -x 1 # you should see a single memory mapping whose RSS memory usage keeps growing +$ docker kill $LEAK # abort the experiment +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1689 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1689 new file mode 100644 index 000000000..ec6c997a2 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1689 @@ -0,0 +1,11 @@ +memory backend file unnecessarily requires write permission while it is only mapped privately +Description of problem: +One day I wanted to boot the machine with physical memory initialized with a file, in a copy-on-write style. That is why I tried out `-mem-path` and `-object memory-backend-file`. Actually `-mem-path` already works if not considering that qemu dislikes the backing file being readonly and requires it to be writeable even when only private mappings are used here. + +I sadly found out that when using memory-backend-file, and when `share=off`, if `readonly=on`, then file is `open`ed with `O_RDONLY` and mmap prot is `PROT_READ`; if `readonly=off`, then the file is `open`ed with `O_RDWR` and mmap prot is `PROT_READ|PROT_WRITE`. I want `O_RDONLY` and `PROT_READ|PROT_WRITE` but I cannot find it anywhere. + +In my opinion, expected behavior should be that if `share=off`, the file can already be opened with `O_RDONLY` no matter what prot the mmap is. That is how linux `MAP_PRIVATE` works - basically copy on write. When I only need copy on write for the content of file, why do I require write permission for it? + +Now I cannot find a setup that opens the file with `fd=open(*, O_RDONLY)` and mmap it with `mmap(*, *, PROT_READ|PROT_WRITE, MAP_PRIVATE|*, fd, *)`. + +Tell me if I misunderstood linux (for example certain file behave differently if one open with O_RDONLY and this behavior is necessary) or qemu or other posix systems where copy-on-write does not work like this. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/169 b/gitlab/issues_text/target_missing/host_missing/accel_missing/169 new file mode 100644 index 000000000..1274cfd34 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/169 @@ -0,0 +1 @@ +[RFC] dma buf: support sprite plane diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1690 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1690 new file mode 100644 index 000000000..366893e11 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1690 @@ -0,0 +1,3 @@ +arguments to specify mapping offsets or map like a elf loader for memory backend file +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1691 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1691 new file mode 100644 index 000000000..e7662acb1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1691 @@ -0,0 +1,10 @@ +QEMU's NVMe emulator behaving not standard compliant +Description of problem: +QEMU's NVMe emulator behaves slightly non-conformant to the standard. +For one, in the CAP.CSS register, bits 0, 6 and 7 are set. Bit 7 indicates that the NVMe Controller does not support any I/O Command Set, while bit 6 is set when the NVMe Controller supports one or more I/O Command Sets (see Figure 36 of the NVM Express® Base Specification, Revision 2.0c). This is obviously contradictory and only bit 6 (and 0) should be set. These bits are configured in hw/nvme/ctrl.c:8250. +The NVMe emulator also checks whether the values of CC.IOSQES and CC.IOCQES are within the allowed range when the controller is enabled by setting CC.EN to 1. However this check should not be performed yet, as the allowed range can only be discovered after the controller is enabled, by submitting the Identify Command. This command reports the valid range in the Identify Controller Data Structure, however it requires the controller to be enabled which in turn would, at least in the current version, require valid values in CC.IOSQES and CC.IOCQES. The NVMe emulator also uses the values configured in CC.IOSQES and IO.IOCQES for the Admin Queues which, from what I understand, should not be the case. Only the I/O Queues should use these values. These checks are done in hw/nvme/ctrl.c:7199f. In the same function the values are already used to initialize the controllers cqe_size and sqe_size which should also happen at a later time. +Steps to reproduce: +1. Start any virtual machine with a NVMe Controller attached. +2. Read the value of CAP.CSS (located in BAR0 of the PCIe NVMe Controller). This value will be contradictory. +3. Follow the initialization procedure as described in section 3.5.1 of the NVM Express® Base Specification, Revision 2.0c. Do not set the values of CC.IOSQES and CC.IOCQES. +4. The NVMe Controller will fail to enable when setting CC.EN to 1 by setting CC.CFS to 1 and reporting the respective trace event (pci_nvme_err_startfail_cqent_too_small and variations). diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1692 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1692 new file mode 100644 index 000000000..6482baceb --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1692 @@ -0,0 +1,102 @@ +Got "Assertion `bus->irq_count[i] == 0` failed" when running fuzzing +Description of problem: +When running the fuzzer on ac97, it always stops with "Assertion `bus->irq_count[i] == 0` failed". +Steps to reproduce: +Run `./qemu-fuzz-x86_64 --fuzz-target=generic-fuzz-ac97` +Additional information: +The logs triggered by the crash report are: +``` +==2330108==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases! +[I 0.000000] OPENED +INFO: libFuzzer ignores flags that start with '--' +INFO: Running with entropic power schedule (0xFF, 100). +INFO: Seed: 1879893091 +INFO: Loaded 1 modules (358762 inline 8-bit counters): 358762 [0x55bec313a1a0, 0x55bec3191b0a), +INFO: Loaded 1 PC tables (358762 PCs): 358762 [0x55bec3191b10,0x55bec370b1b0), +./qemu-fuzz-x86_64: Running 1 inputs 1 time(s) each. +Running: ./crash-55e7a160b7c66d5b41718e22c7620a29e9f568f1 +Starting x86_64 with Arguments: -display none -machine accel=qtest, -m 512M -machine q35 -nodefaults -device ac97,audiodev=snd0 -audiodev none,id=snd0 -nodefaults -qtest /dev/null +Matching objects by name ac97* +This process will try to fuzz the following MemoryRegions: + * bus master[0] (size 0xffffffffffffffff) + * ac97-nabm[0] (size 0x100) + * bus master container[0] (size 0xffffffffffffffff) + * ac97-nam[0] (size 0x400) +[R +0.033680] outl 0xcf8 0x80000800 +[S +0.033714] [R +0.033729] inw 0xcfc +[S +0.033750] [R +0.033766] outl 0xcf8 0x80000810 +[S +0.033781] [R +0.033792] outl 0xcfc 0xffffffff +[S +0.033816] [R +0.033827] outl 0xcf8 0x80000810 +[S +0.033841] [R +0.033852] inl 0xcfc +[S +0.033866] [R +0.033879] outl 0xcf8 0x80000810 +[S +0.033894] [R +0.033904] outl 0xcfc 0xc001 +[S +0.033920] [R +0.033935] outl 0xcf8 0x80000814 +[S +0.033952] [R +0.033967] outl 0xcfc 0xffffffff +[S +0.033984] [R +0.033994] outl 0xcf8 0x80000814 +[S +0.034008] [R +0.034017] inl 0xcfc +[S +0.034031] [R +0.034043] outl 0xcf8 0x80000814 +[S +0.034057] [R +0.034067] outl 0xcfc 0xc401 +[S +0.034085] [R +0.034096] outl 0xcf8 0x80000804 +[S +0.034110] [R +0.034120] inw 0xcfc +[S +0.034133] [R +0.034145] outl 0xcf8 0x80000804 +[S +0.034159] [R +0.034170] outw 0xcfc 0x7 +[S +0.035259] [R +0.035272] outl 0xcf8 0x80000804 +[S +0.035285] [R +0.035291] inw 0xcfc +[S +0.035300] [I +0.035389] CLOSED +x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] outl 0xcf8 0x80000805 +x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] outl 0xcfc 0x5050505 +x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] outw 0xc40b 0x6f0d +[DMA] x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] write 0x0 0x8 0x2a256c5a2c008425 +x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] clock_step +x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] outl 0xcf8 0x80000805 +x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] outl 0xcfc 0x8468920 +x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] clock_step +qemu-fuzz-x86_64: ../../../../hw/pci/pci.c:435: void pcibus_reset(BusState *): Assertion `bus->irq_count[i] == 0' failed. +==2330108== ERROR: libFuzzer: deadly signal + #0 0x55bebf2624de in __sanitizer_print_stack_trace ../../llvm-project-15.0.0.src/compiler-rt/lib/asan/asan_stack.cpp:87:3 + #1 0x55bebf1a4b31 in fuzzer::PrintStackTrace() ../../llvm-project-15.0.0.src/compiler-rt/lib/fuzzer/FuzzerUtil.cpp:210:38 + #2 0x55bebf17f406 in fuzzer::Fuzzer::CrashCallback() (.part.0) ../../llvm-project-15.0.0.src/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:233:18 + #3 0x55bebf17f4cd in fuzzer::Fuzzer::CrashCallback() ../../llvm-project-15.0.0.src/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:205:1 + #4 0x55bebf17f4cd in fuzzer::Fuzzer::StaticCrashSignalCallback() ../../llvm-project-15.0.0.src/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:204:19 + #5 0x7fae9f8a441f (/lib/x86_64-linux-gnu/libpthread.so.0+0x1441f) (BuildId: 7b4536f41cdaa5888408e82d0836e33dcf436466) + #6 0x7fae9f69800a in __libc_signal_restore_set /build/glibc-SzIz7B/glibc-2.31/signal/../sysdeps/unix/sysv/linux/internal-signals.h:86:3 + #7 0x7fae9f69800a in raise /build/glibc-SzIz7B/glibc-2.31/signal/../sysdeps/unix/sysv/linux/raise.c:48:3 + #8 0x7fae9f677858 in abort /build/glibc-SzIz7B/glibc-2.31/stdlib/abort.c:79:7 + #9 0x7fae9f677728 in __assert_fail_base /build/glibc-SzIz7B/glibc-2.31/assert/assert.c:92:3 + #10 0x7fae9f688fd5 in __assert_fail /build/glibc-SzIz7B/glibc-2.31/assert/assert.c:101:3 + #11 0x55bebfab33a7 in pcibus_reset ../hw/pci/pci.c:435:9 + #12 0x55bec0c75ae3 in resettable_phase_hold ../hw/core/resettable.c + #13 0x55bec0c6e543 in device_reset_child_foreach ../hw/core/qdev.c:276:9 + #14 0x55bec0c757c5 in resettable_phase_hold ../hw/core/resettable.c:173:5 + #15 0x55bec0c5c421 in bus_reset_child_foreach ../hw/core/bus.c:97:13 + #16 0x55bec0c757c5 in resettable_phase_hold ../hw/core/resettable.c:173:5 + #17 0x55bec0c73729 in resettable_assert_reset ../hw/core/resettable.c:60:5 + #18 0x55bec0c7336a in resettable_reset ../hw/core/resettable.c:45:5 + #19 0x55bec0c7309a in qemu_devices_reset ../hw/core/reset.c:84:9 + #20 0x55bec02d95bb in pc_machine_reset ../hw/i386/pc.c:1901:5 + #21 0x55bebff4ede6 in qemu_system_reset ../softmmu/runstate.c:451:9 + #22 0x55bec0c49684 in fuzz_reset ../tests/qtest/fuzz/fuzz.c:56:5 + #23 0x55bec0c55641 in generic_fuzz ../tests/qtest/fuzz/generic_fuzz.c:676:5 + #24 0x55bec0c4a0f7 in LLVMFuzzerTestOneInput ../tests/qtest/fuzz/fuzz.c:158:5 + #25 0x55bebf17fc88 in fuzzer::Fuzzer::ExecuteCallback(unsigned char const*, unsigned long) .. /../llvm-project-15.0.0.src/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:612:15 + #26 0x55bebf1630a4 in fuzzer::RunOneTest(fuzzer::Fuzzer*, char const*, unsigned long) ../../llvm-project-15.0.0.src/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:324:21 + #27 0x55bebf16fa8a in fuzzer::FuzzerDriver(int*, char***, int (*)(unsigned char const*, unsigned long)) ../../llvm-project-15.0.0.src/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:860:19 + #28 0x55bebf15a856 in main ../../llvm-project-15.0.0.src/compiler-rt/lib/fuzzer/FuzzerMain.cpp:20:30 + #29 0x7fae9f679082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16 + #30 0x55bebf15a8dd in _start (../qemu-fuzz-x86_64+0x1e938dd) + +NOTE: libFuzzer has rudimentary signal handlers. + Combine libFuzzer with AddressSanitizer or similar for better crash reports. +SUMMARY: libFuzzer: deadly signal + +``` + +After some manual checks, I find out that the instruction `outl 0xcf8 0x80000805` and `outl 0xcfc 0x8468920` will set irq_count[5] to -1 while the pcibus_reset() doesn't set it back to 0 so it will fail the assertion. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1694 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1694 new file mode 100644 index 000000000..4df798f9e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1694 @@ -0,0 +1 @@ +cpu-x86-uarch-abi.py is missing "xsave" cpuid for x86-64-v3 && x86-64-v4 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1695 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1695 new file mode 100644 index 000000000..7d6709294 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1695 @@ -0,0 +1,11 @@ +Latest Windows MSI does not include libssp-0.dll +Description of problem: +The latest Qemu MSI installer for Windows (https://qemu.weilnetz.de/w64/2023/qemu-w64-setup-20230530.exe) does not include libssp-0.dll, which is why the executables fail to run. + +This Mingw library should be included when building the MSI if stack protection is enabled. +Steps to reproduce: +1. Install the latest qemu MSI +2. Try to invoke any qemu command +3. Use Dependency Walker to easily find missing dependencies (https://www.dependencywalker.com/) +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1696 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1696 new file mode 100644 index 000000000..e380fb973 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1696 @@ -0,0 +1,39 @@ +Linux kernel hangs rarely when booting on the latest qemu +Description of problem: +(Downstream bug: https://bugzilla.redhat.com/show_bug.cgi?id=2213346) + +In Fedora we have noticed that the latest Linux kernel (rarely) hangs when booting +on the latest qemu. It hangs after printing: + +``` +[ 0.070120] x86/cpu: User Mode Instruction Prevention (UMIP) activated +[ 0.070120] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127 +[ 0.070120] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0 +[ 0.070120] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization +[ 0.070120] Spectre V2 : Mitigation: Retpolines +[ 0.070120] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch +[ 0.070120] Spectre V2 : Spectre v2 / SpectreRSB : Filling RSB on VMEXIT +[ 0.070120] Spectre V2 : Enabling Speculation Barrier for firmware calls +[ 0.070120] RETBleed: Mitigation: untrained return thunk +[ 0.070120] Spectre V2 : mitigation: Enabling conditional Indirect Branch Prediction Barrier +[ 0.070120] Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl +[ 0.070120] Freeing SMP alternatives memory: 48K +``` + +The next line which would be printed (if it didn't hang) is: + +``` +[ 0.070794] smpboot: CPU0: AMD Ryzen 9 3900X 12-Core Processor (family: 0x17, model: 0x71, stepping: 0x0) +``` + +We've seen this hang on both AMD and Intel. It probably happens one in every 300 boots. +Steps to reproduce: +By far the easiest way to reproduce this is to just run guestfish in a loop: + +``` +$ while guestfish -a /dev/null -v run >& /tmp/log; do echo -n . ; done +``` +Additional information: +The full qemu command is rather long but you can find it in this log file: + +https://bugzilla-attachments.redhat.com/attachment.cgi?id=1969620 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/170 b/gitlab/issues_text/target_missing/host_missing/accel_missing/170 new file mode 100644 index 000000000..a572bcf77 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/170 @@ -0,0 +1 @@ +Request to add something like "Auth failed from IP" log report for built-in VNC server diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1701 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1701 new file mode 100644 index 000000000..5c2f52ce3 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1701 @@ -0,0 +1,5 @@ +-boot menu=on that vm is hangs +Description of problem: +virtual machine hangs, stop at press ESC for boot menu. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1702 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1702 new file mode 100644 index 000000000..ae00f7365 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1702 @@ -0,0 +1,8 @@ +Enable whpx acceleration, unable to start Linux system +Description of problem: +The accel=whpx parameter stops responding in the boot menu. + +The accel=whpx,kernel-irqchip=off parameter stops responding during startup +Additional information: + + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1703 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1703 new file mode 100644 index 000000000..41ac48abf --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1703 @@ -0,0 +1,45 @@ +Undefined behaviour when running guest with -enable-kvm and attached debugger +Description of problem: +When attaching a debugger to a Qemu instance with `-enable-kvm` my linux kernel panics on (f.e.) module load. +I am not sure if this is a Qemu bug, however the issue is not occurring if I a) do not attach the debugger (even though Qemu is listening for one) or b) I do not pass `-enable-kvm` (and attach a debugger). +The issue seems to relate to the `lx-symbols` command provided by the Linux kernel gdb script suite. +Every time a module is loaded this script will reload the symbols for said module which may take some time, so maybe there is some race involved? +The issue does not reproduce if you do not run `lx-symbols` prior to continuing (it will however run automatically after first module load as it adds a breakpoint to kernel/module/main.c:do_init_module, so the kernel will crash after the second module load) +Steps to reproduce: +1. Start kernel with some img +2. Attach gdb debugger +3. Run the `lx-symbols` command provided by the Linux kernel gdb scripts in gdb, run `continue` in gdb +3. Load a kernel module +Additional information: +This is the kernel stack trace: +``` +[ 22.930691] invalid opcode: 0000 [#1] PREEMPT SMP NOPTI +[ 22.931174] CPU: 2 PID: 241 Comm: modprobe Tainted: G E 6.1.31+ #2 +[ 22.931675] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-1.fc37 04/01/2014 +[ 22.931675] RIP: 0010:do_init_module+0x1/0x210 +[ 22.931675] Code: 74 0c 48 8b 78 08 48 89 de e8 8b df ff ff 65 ff 0d 84 94 ef 7e 0f 85 e5 fe ff ff 0f 1f 44 00 008 +[ 22.931675] RSP: 0018:ffffc90000593e40 EFLAGS: 00010246 +[ 22.931675] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 000000000006e202 +[ 22.931675] RDX: 000000000006e002 RSI: 5b4504de76578f76 RDI: ffffffffc024e180 +[ 22.931675] RBP: ffffc90000593e50 R08: ffffea0000174a88 R09: ffffea0000174ac0 +[ 22.931675] R10: ffff888006a9c270 R11: 0000000000000100 R12: 0000562f9087b4a0 +[ 22.931675] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 +[ 22.931675] FS: 00007f0dbc5a4040(0000) GS:ffff88801f500000(0000) knlGS:0000000000000000 +[ 22.931675] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 +[ 22.931675] CR2: 00007ffdc94bc3f8 CR3: 0000000006f8e000 CR4: 00000000003506e0 +[ 22.931675] Call Trace: +[ 22.931675] <TASK> +[ 22.931675] ? die+0x32/0x80 +[ 22.931675] ? do_trap+0xd6/0x100 +[ 22.931675] ? do_init_module+0x1/0x210 +[ 22.931675] ? do_error_trap+0x6a/0x90 +[ 22.931675] ? do_init_module+0x1/0x210 +[ 22.931675] ? exc_invalid_op+0x4c/0x60 +[ 22.931675] ? do_init_module+0x1/0x210 +[ 22.931675] ? asm_exc_invalid_op+0x16/0x20 +[ 22.931675] ? do_init_module+0x1/0x210 +[ 22.931675] __do_sys_finit_module+0x9e/0xf0 +[ 22.931675] do_syscall_64+0x63/0x90 +[ 22.931675] ? exit_to_user_mode_prepare+0x1a/0x120 +[ 22.931675] entry_SYSCALL_64_after_hwframe+0x63/0xcd +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1705 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1705 new file mode 100644 index 000000000..74c4dd289 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1705 @@ -0,0 +1,66 @@ +Illegal instruction when I want to numactl --cpubind=0 --membind=1 to CXL Memory +Description of problem: +I ran QEMU for simulating CXL DRAM and when I tried to run `numactl --cpubind=0 --membind=1 ls` , I got `Illegal instruction` +The numa node 1 was the CXL DRAM simulated by QEMU. + +> root@8003:~# numactl -H +> available: 2 nodes (0-1) +> node 0 cpus: 0 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 +> node 0 size: 32090 MB +> node 0 free: 31325 MB +> node 1 cpus: +> node 1 size: 32768 MB +> node 1 free: 32768 MB +> node distances: +> node 0 1 +> 0: 10 20 +> 1: 20 10 + +When I ran on numa node 1, no failed + +> root@8003:~# numactl --membind=0 ls +> ndctl + +When I ran on numa node 1(CXL DRAM),it failed. + +> root@8003:~# numactl --membind=1 ls +> [ 913.975032] traps: ls[667] trap invalid opcode ip:7fdec255d180 sp:7ffd3c507288 error:0 in ld-linux-x86-64.so.2[7fdec2546000+2a000] +> **Illegal instruction** +Steps to reproduce: +1. start the guest +2. cxl list (we could see the simulated CXL DRAM) +> root@8003:~# cxl list +> [ +> { +> "memdev":"mem0", +> "ram_size":34359738368, +> "serial":0, +> "host":"0000:0d:00.0" +> } +> ] +3. cxl create-region -t ram -d decoder0.0 -m mem0 +4. daxctl reconfigure-device dax0.0 --mode=system-ram +5. numactl -H +> root@8003:~# numactl -H +> available: 2 nodes (0-1) +> node 0 cpus: 0 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 +> node 0 size: 32090 MB +> node 0 fr +> ee: 31254 MB +> node 1 cpus: +> node 1 size: 32768 MB +> node 1 free: 32768 MB +> node distances: +> node 0 1 +> 0: 10 20 +> 1: 20 10 +6. numactl --membind=1 ls +> root@8003:~# numactl --membind=1 ls +> [38441.892140] **traps: ls[861] trap invalid opcode ip:7f15db6ac180 sp:7ffc648755c8 **error:0 in ld-linux-x86-64.so.2[7f15db695000+2a000] +> **Illegal instruction** +Additional information: +When I run dmesg, I found an error. +> root@8003:~# dmesg|grep error +> [ 2.321130] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 + +Since my CPU is a Xeon III, not a Xeon IV with CXL support, **I'm wondering if it's because the CPU doesn't support CXL instructions, or if the Xeon III can emulate it, just because my settings don't make sense**. If this is my settings problem, could you help me to deal this? Or it just caused by my Xeon III,I will update it to Xeon IV. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1706 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1706 new file mode 100644 index 000000000..9e31bc223 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1706 @@ -0,0 +1,9 @@ +Allow TCG plugins to read registers +Additional information: +- `include/qemu/plugin.h` +- `include/qemu/qemu-plugin.h` + +PANDA implemented this already but it is not a very clean solution: +- https://github.com/panda-re/qemu/commit/b97c5a56edd0ba3b5f6ab16bf531ac1f7abaac04 (mentioned in QPP patch series: https://lore.kernel.org/qemu-devel/20221213213757.4123265-1-fasano@mit.edu/) + +I personally think the flag for the TB translation and execution callbacks makes more sense diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1707 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1707 new file mode 100644 index 000000000..ee317fd7f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1707 @@ -0,0 +1,23 @@ +linux-user qemu-x86_64 can't exec a binary on aarch64 or Loongarch. +Description of problem: +on master branch, we build an simply hello.c with x86_cross gcc. +then. run './build/qemu-x86_64 hello', no output. +Steps to reproduce: +1. build an hello.c with x86_64 cross. use --static. +2. build qemu-x86_64 on aarch64 or LoongArch host. +3. run './build/qemu-x86_64 hello' +Additional information: +[strace.txt](/uploads/5362e0e9b04ad9a582470faf4a9fcedb/strace.txt) + + + + [hello](/uploads/12d9277fa4e853286414f575010a37ac/hello) + + +The following commit causes this problem． + +commit 86f04735ac2088d5c069c3d1712212ec7428c562 +Author: Helge Deller <deller@gmx.de> +Date: Sun Dec 25 09:23:19 2022 +0100 + + linux-user: Fix brk() to release pages diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1709 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1709 new file mode 100644 index 000000000..ca59fba3f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1709 @@ -0,0 +1,36 @@ +Qemu commit 7efd65423a cannot be built: Couldn't find file "symbols/ar" in include paths +Description of problem: +Hello. + +I try to build qemu based on commit 7efd65423a but it breaks in step 9035/10108, complaining about a missing "symbols/ar". + +The last time I get a full build was with commit fdd0df5340. + +Configure options: `--prefix=/usr --sysconfdir=/etc --localstatedir=/var --libexecdir=/usr/lib/qemu --smbd=/usr/bin/smbd --enable-modules --enable-sdl --disable-werror` + +Here is the error log I got: + +``` +Running postconf script '/home/fred/qemu-git/src/qemu/build-full/pyvenv/bin/python3 /home/fred/qemu-git/src/qemu/scripts/symlink-install-tree.py' +[9035/10108] Generating pc-bios/keymaps/ar with a custom command +FAILED: pc-bios/keymaps/ar +/home/fred/qemu-git/src/qemu/build-full/qemu-keymap -f pc-bios/keymaps/ar -l ar +xkbcommon: ERROR: Couldn't find file "symbols/ar" in include paths +xkbcommon: ERROR: 1 include paths searched: +xkbcommon: ERROR: /usr/share/X11/xkb +xkbcommon: ERROR: 3 include paths could not be added: +xkbcommon: ERROR: /home/fred/.config/xkb +xkbcommon: ERROR: /home/fred/.xkb +xkbcommon: ERROR: /etc/xkb +xkbcommon: ERROR: Abandoning symbols file "(unnamed)" +xkbcommon: ERROR: Failed to compile xkb_symbols +xkbcommon: ERROR: Failed to compile keymap +[9040/10108] Generating pc-bios/edk2-x...d (wrapped by meson to capture output) +ninja: build stopped: subcommand failed. +``` + +I'll try to do a bisect as soon as possible to see which commit break all. +Steps to reproduce: +1. Just grab commit 7efd65423a +2. Apply these configure options: `--prefix=/usr --sysconfdir=/etc --localstatedir=/var --libexecdir=/usr/lib/qemu --smbd=/usr/bin/smbd --enable-modules --enable-sdl --disable-werror` +3. launch make and wait diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/171 b/gitlab/issues_text/target_missing/host_missing/accel_missing/171 new file mode 100644 index 000000000..fc5a41b6b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/171 @@ -0,0 +1 @@ +[RFE] option to suppress gemu_log() output diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1710 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1710 new file mode 100644 index 000000000..ee2e7e254 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1710 @@ -0,0 +1,51 @@ +contrib/plugins/Makefile is not crossplatform +Description of problem: +Currently `contrib/plugins/Makefile` makes multiple assumptions about paths used, compiler flags available, and library extension +Steps to reproduce: +1. Compile QEMU from sources on macOS or Windows +2. Enter `contrib/plugins` +3. Type `make` and become sad. +Additional information: +As the rest of QEMU switched to Meson, maybe it's a good idea to do the same for plugins as well? + +This is what I come with myself: + +`meson.build`: +```meson +project('qemu-plugins', 'c', meson_version: '>=0.50.0') + +qemu_src = get_option('qemu_path') +if qemu_src == '' + qemu_src = '../..' +endif + +qemu_include = qemu_src + '/include/qemu' +incdir = include_directories(qemu_include) + +plugins = [ + 'execlog', + 'hotblocks', + 'hotpages', + 'howvec', + 'lockstep', + 'hwprofile', + 'cache', + 'drcov', +] + +th = dependency('threads', required: true) +glib = dependency('glib-2.0', required: true) + +foreach p: plugins + library(p, p + '.c', + include_directories: incdir, + dependencies: [th, glib], + override_options: ['b_lundef=false'] + ) +endforeach +``` + +`meson_options.txt`: +``` +option('qemu_path', type : 'string', value : '', description : 'Full path to the QEMU sources to build the plugin for') +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1711 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1711 new file mode 100644 index 000000000..351ca81ec --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1711 @@ -0,0 +1 @@ +unable to set PWD with guest-exec without starting a shell diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1712 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1712 new file mode 100644 index 000000000..afbb5c88e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1712 @@ -0,0 +1,9 @@ +Arabic keyboard layout wrong. +Description of problem: +After a while the compilation process starts, xkb gives an error about symbols/ar not found. According to my research, linux distros using "ara" for arabic layout. But qemu pc-bios/keymaps/ folder contains "ar" for arabic layout. +Steps to reproduce: +1.Configure +2.Build +3.Wait until error appears. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1713 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1713 new file mode 100644 index 000000000..22591e4fb --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1713 @@ -0,0 +1,40 @@ +hw/input/hid.c - Add Support for More Than Five Mouse Buttons in QEMU for evdev? +Additional information: +Sure enough, there appear to only be five buttons defined. + +https://gitlab.com/qemu-project/qemu/-/blob/master/hw/input/hid.c#L113 + +```c +[INPUT_BUTTON_LEFT] = 0x01, +[INPUT_BUTTON_RIGHT] = 0x02, +[INPUT_BUTTON_MIDDLE] = 0x04, +[INPUT_BUTTON_SIDE] = 0x08, +[INPUT_BUTTON_EXTRA] = 0x10, +``` + + +At this point, the existing naming schema cannot be continued... might I suggest: + +```c +[INPUT_BUTTON_SIX] = 0x??, +[INPUT_BUTTON_SEVEN] = 0x??, +[INPUT_BUTTON_EIGHT] = 0x??, +[INPUT_BUTTON_NINE] = 0x??, +[INPUT_BUTTON_TEN] = 0x??, +[INPUT_BUTTON_ELEVEN] = 0x??, +[INPUT_BUTTON_TWELVE] = 0x??, +``` +Although, I'm not sure if 12 buttons is future-proofed enough. + +I should also note that I found this post which states that there's no more space left in PS2 emulation, so I don't know if that would cause a conflict. +"ps/2 emulation looks like there are no unused bits for more buttons. Possibly we have to extend the usb mouse emulation for that." +https://listman.redhat.com/archives/vfio-users/2016-January/001596.html + +Unfortunately, I have never written a patch. I'm not even sure how I would apply a patch in Unraid, other than overwriting the bin file. So if this is ever fixed, I would simply hope that one day a new version of QEMU would get up-streamed into a new version of Unraid. + +So, here I am humbly asking for support. I don't know if it's as simple as just adding new definitions... and I have no idea what hex value to assign them. + +*edit* I also failed to get a temporary workaround to work by remapping the mouse buttons in the host VM using xmodmap using this command: + +`xmodmap -e "pointer = 1 12 3 4 5 6 7 8 9 10 11 2" &` +I tried saving `pointer = 1 12 3 4 5 6 7 8 9 10 11 2` in the host VM's root folder in .Xmodmap, but it did not propogate to guest VMs. The buttons were still their original mapping and running the xmod command had no effect. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1715 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1715 new file mode 100644 index 000000000..80aa09eeb --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1715 @@ -0,0 +1 @@ +qemu-img convert about target_is_new diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1716 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1716 new file mode 100644 index 000000000..d67de9818 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1716 @@ -0,0 +1,9 @@ +Cannot raise low memory using max-ram-below-4g on current i440fx +Description of problem: +We have a use case where we have a virtual machine with at least 8 Gb of RAM and at least 3.5Gb of it in the low memory. However, I could not achieve it this far with QEMU, only on the deprecated i440fx 1.7 architecture. The size of lowmem is never greater than 3 Gb, except if I assign memory to the vm between 3 Gb and 3.5 Gb. If I go even a slightly above 3.5 Gb then it falls back to 3 Gb. + +I did some research and I found the source file hw/i386/pc_piix.c. There is a piece of code which is responsible for setting the low memory at the beginning of function pc_init1(). It seems that the problem lies in the property `gigabyt_align` of all i440fx architectures newer than 1.7. The comment which explains this piece of code does not mention at all that raising lowmem does not work on newer pc architectures. According to the comments setting the size of lowmem based of the `max-ram-below-4g` option should happen before the gigabyte alignment, not after it. Anyway, it does not make sense because with default being 3 Gb gigabyte alignment always means 3 Gb so raising is not possible at all. The last example of the comment clearly states that raising should be possible using the newest `pc` architecture: `qemu -M pc,max-ram-below-4g=4G -m 3968M -> 3968M low (=4G-128M)`. However, according to the code below the comment this is not the way it works because gigabyte alignment happens after. + +To solve the problem there are two possibilities: if this is a bug then the solution is obvious, the gigabyte aligment should happen before applying the `max-ram-below-4g` option. If this is not a bug but the expected way of working then there could be an option to override the `gigabyte_align` attribute from command line. + +What do you think? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1717 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1717 new file mode 100644 index 000000000..13ab8c046 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1717 @@ -0,0 +1,29 @@ +GPU passthrough (NV h100)case vfio Error +Description of problem: +GPU passthrough (NV h100) will case a error + + +qemu-system-x86_64: vfio_err_notifier_handler(0000:17:00.0) Unrecoverable error detected. Please collect any data possible and then kill the guest + + +this error happen in centos, redhat linux,ubuntu with some kernel i have try( 5.19.0,6.0,6.2) +The same server insert L4,L40 GPU, will not happen. Only happen on H100 GPU +The same server install esxios. everything is normal. GPU work fine + +With vfio error. there is some idrac log error on my dell server + +``` +A bus fatal error was detected on a component at slot 2. Tue Jun 20 2023 05:51:51 +A fatal error was detected on a component at bus 23 device 0 function 0. Tue Jun 20 2023 05:51:51 +A fatal error was detected on a component at bus 22 device 2 function 0. Tue Jun 20 2023 05:51:51 +``` + +Otherwise, I have try to passthrough gpu on dell amd and intel server both. +With AMD CPU , gpu not working in vm. but will not case vfio error +With INTEL CPU, will case vfio error. +Steps to reproduce: +1. Set GPU passthrought +2. Start VM +3. Do something in vm +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1718 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1718 new file mode 100644 index 000000000..c5f7688c1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1718 @@ -0,0 +1,47 @@ +Strange throttle-group test results +Description of problem: +I have a question about throttle-group test results. + +I did a test to limit IO by applying THROTTLE-GROUP and the expected result is not what I expected + +The setup environment looks like this throttle-group to x-iops-total=500, x-bps-total=524288000 and throttling vdb, benchmarked with fio command + +``` +# mount -t xfs /dev/vdb1 /mnt/disk + +# fio --direct=1 --bs=1M --iodepth=128 --rw=read --size=1G --numjobs=1 --runtime=600 --time_based --name=/mnt/disk/fio-file --ioengine=libaio --output=/mnt/disk/read-1M +``` + +When I test with a --bs value of 1M, I get 500Mib throughput. + + + +When I test with a --bs value of 2m, I don't get 500Mibs but 332Mibs throughput. +``` +fio --direct=1 --bs=2M --iodepth=128 --rw=read --size=1G --numjobs=1 --runtime=600 --time_based --name=/mnt/disk/fio-file --ioengine=libaio --output=/mnt/disk/read-2M +``` + + + +If I set the qemu x-iops-total value to 1500 and the fio --bs value to 2M test again, I get 500Mib throughput. + + + + +To summarize, here is the Test result. + +| fio bs | qemu x-iops-total | qemu x-bps-total | Result iops |Result throughput +| ------ | ------ |------ |------ |------ | +| 2M | 1500 | 524288000 | 250 | 500 | +| **2M** |**500** | **524288000** | **166** | **332** | +| 1M | 1500 | 524288000 | 500 | 500 | +| 1M | 500. | 524288000 | 500 | 500 | + + +When the --bs value is 2M and the x-iops-total value is 500, the throughput should be 500, but it is not, so I don't know what the problem is. + +If there is anything I missed, please let me know. +Steps to reproduce: +1. Apply throttle-group to vdb and start the VM +2. mount vdb1 +3. test fio diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1719 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1719 new file mode 100644 index 000000000..c51e32c93 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1719 @@ -0,0 +1,7 @@ +Allow TCG plugins to read memory +Additional information: +* `include/qemu/plugin.h` +* `include/qemu/qemu-plugin.h` +* `plugin/api.c` + +PANDA implemented this already (not sure if this solution is acceptable for the mainline QEMU): https://github.com/qemu/qemu/commit/72c661a7f141ab41fbce5e95eb3593b69f40e246 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1720 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1720 new file mode 100644 index 000000000..66a50c3c8 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1720 @@ -0,0 +1,40 @@ +Problems in mapping memory regions in multiple machines using GPEX pci-host +Description of problem: +Multiple machines use the GPEX pci-host model. This model forsees 3 MMIO regions: +1. ECAM space +2. MMIO space +3. IO space + +In the different machines, aliases to the 3 memory regions are created which are then mapped onto the sysbus. + +For the ARM virt machine for example following calls are happening: + + ecam_alias = g_new0(MemoryRegion, 1); + ecam_reg = sysbus_mmio_get_region(SYS_BUS_DEVICE(dev), 0); + memory_region_init_alias(ecam_alias, OBJECT(dev), "pcie-ecam", ecam_reg, 0, size_ecam); + memory_region_add_subregion(get_system_memory(), base_ecam, ecam_alias); + + mmio_alias = g_new0(MemoryRegion, 1); + mmio_reg = sysbus_mmio_get_region(SYS_BUS_DEVICE(dev), 1); + memory_region_init_alias(mmio_alias, OBJECT(dev), "pcie-mmio", mmio_reg, base_mmio, size_mmio); + memory_region_add_subregion(get_system_memory(), base_mmio, mmio_alias); + +We now add a generic PCIe root port (gen_pcie_root_port.c) on the PCIBus exposed by the GPEX device: + + pci_create_simple(PCI_HOST_BRIDGE(dev)->bus, -1, "pcie-root-port"); + +This device contains an MSI-x table which is accessible via BAR 0. + +However, if we try to access this space we always get 0xFFFFFFFF as a return value on reads because the memory regions are not correctly mapped IMO. + +If we again look at the mapping of the MMIO space: + + memory_region_init_alias(mmio_alias, OBJECT(dev), "pcie-mmio", mmio_reg, base_mmio, size_mmio); + memory_region_add_subregion(get_system_memory(), base_mmio, mmio_alias); + +The alias is created to the MMIO region in the GPEX device, at offset base_mmio. Afterwards the memory region alias is mapped onto the sysbus at offset base_mmio. To me it seems that the offset is incorrect in creating the alias and should be 0 instead: + + memory_region_init_alias(mmio_alias, OBJECT(dev), "pcie-mmio", mmio_reg, 0, size_mmio); + memory_region_add_subregion(get_system_memory(), base_mmio, mmio_alias); + +With this change the above scenario (accessing the MSI-x table of the generic PCIe root port) is working. I'm not sure if this is the correct fix for this problem and how to cope with e.g. high MMIO regions (as are also present in the virt machine). diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1721 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1721 new file mode 100644 index 000000000..db3237ed6 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1721 @@ -0,0 +1,62 @@ +Problem in combination with RabbitMQ and erlang +Description of problem: +I have a problem with rabbitMQ /erlang / Qemu on my local system. + +I use docker with: + +version: "3.6" +``` +services: + rabbitmq: + image: rabbitmq:3-management +``` + +Docker Desktop 4.20.1 (110738) +Docker version 24.0.2, build cb74dfc + +Apple Macbook Pro with M1 Chip Ventura 13.4. + +I deleted all containers and images related to rabbitMQ. Then when I do a: docker compose up -d + +I always get this error and rabbitMQ stopps: + +``` +rabbitmq-server-rabbitmq-1 | 2023-06-22 08:12:18.984151+00:00 [notice] <0.44.0> Application mnesia exited with reason: stopped +rabbitmq-server-rabbitmq-1 | 2023-06-22 08:12:20.658039+00:00 [info] <0.230.0> Waiting for Mnesia tables for 30000 ms, 9 retries left +rabbitmq-server-rabbitmq-1 | 2023-06-22 08:12:20.659274+00:00 [info] <0.230.0> Successfully synced tables from a peer +rabbitmq-server-rabbitmq-1 | 2023-06-22 08:12:20.662647+00:00 [notice] <0.283.0> Feature flags: attempt to enable `stream_sac_coordinator_unblock_group`... +rabbitmq-server-rabbitmq-1 | 2023-06-22 08:12:20.793670+00:00 [notice] <0.283.0> Feature flags: `stream_sac_coordinator_unblock_group` enabled +rabbitmq-server-rabbitmq-1 | qemu: uncaught target signal 11 (Segmentation fault) - core dumped +rabbitmq-server-rabbitmq-1 | Segmentation fault +``` + +In the past it worked, like 5 months ago. + +Reproduction steps docker compose up -d + +Expected behavior that the container runs and does not exit + +Additional context docker compose logs + +``` +rabbitmq-server-rabbitmq-1 | 2023-06-22 08:12:06.946635+00:00 [notice] <0.44.0> Application syslog exited with reason: stopped +rabbitmq-server-rabbitmq-1 | 2023-06-22 08:12:06.966134+00:00 [notice] <0.230.0> Logging: switching to configured handler(s); following messages may not be visible in this log output +rabbitmq-server-rabbitmq-1 | 2023-06-22 08:12:06.973002+00:00 [notice] <0.230.0> Logging: configured log handlers are now ACTIVE +rabbitmq-server-rabbitmq-1 | 2023-06-22 08:12:07.539052+00:00 [info] <0.230.0> ra: starting system quorum_queues +rabbitmq-server-rabbitmq-1 | 2023-06-22 08:12:07.539748+00:00 [info] <0.230.0> starting Ra system: quorum_queues in directory: /var/lib/rabbitmq/mnesia/rabbit@4fb71bcd203a/quorum/rabbit@4fb71bcd203a +rabbitmq-server-rabbitmq-1 | 2023-06-22 08:12:07.715984+00:00 [info] <0.261.0> ra system 'quorum_queues' running pre init for 0 registered servers +rabbitmq-server-rabbitmq-1 | 2023-06-22 08:12:07.749375+00:00 [info] <0.262.0> ra: meta data store initialised for system quorum_queues. 0 record(s) recovered +rabbitmq-server-rabbitmq-1 | 2023-06-22 08:12:07.786151+00:00 [notice] <0.267.0> WAL: ra_log_wal init, open tbls: ra_log_open_mem_tables, closed tbls: ra_log_closed_mem_tables +rabbitmq-server-rabbitmq-1 | 2023-06-22 08:12:07.857344+00:00 [info] <0.230.0> ra: starting system coordination +rabbitmq-server-rabbitmq-1 | 2023-06-22 08:12:07.857635+00:00 [info] <0.230.0> starting Ra system: coordination in directory: /var/lib/rabbitmq/mnesia/rabbit@4fb71bcd203a/coordination/rabbit@4fb71bcd203a +rabbitmq-server-rabbitmq-1 | 2023-06-22 08:12:07.868808+00:00 [info] <0.274.0> ra system 'coordination' running pre init for 0 registered servers +rabbitmq-server-rabbitmq-1 | 2023-06-22 08:12:07.874965+00:00 [info] <0.275.0> ra: meta data store initialised for system coordination. 0 record(s) recovered +rabbitmq-server-rabbitmq-1 | 2023-06-22 08:12:07.875747+00:00 [notice] <0.280.0> WAL: ra_coordination_log_wal init, open tbls: ra_coordination_log_open_mem_tables, closed tbls: ra_coordination_log_closed_mem_tables +rabbitmq-server-rabbitmq-1 | 2023-06-22 08:12:07.899618+00:00 [info] <0.230.0> +rabbitmq-server-rabbitmq-1 | 2023-06-22 08:12:07.899618+00:00 [info] <0.230.0> Starting RabbitMQ 3.12.0 on Erlang 25.3.2.2 [jit] +rabbitmq-server-rabbitmq-1 | 2023-06-22 08:12:07.899618+00:00 [info] <0.230.0> Copyright (c) 2007-2023 VMware, Inc. or its affiliates. +rabbitmq-server-rabbitmq-1 | 2023-06-22 08:12:07.899618+00:00 [info] <0.230.0> Licensed under the MPL 2.0. Website: https://rabbitmq.com +rabbitmq-server-rabbitmq-1 | +rabbitmq-server-rabbitmq-1 | +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1725 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1725 new file mode 100644 index 000000000..77dd71e0c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1725 @@ -0,0 +1,21 @@ +qemu-system-x86_64 reports wrong thread to GDB on SIGINT +Description of problem: +Upon interruption of a thread by GDB, QEMU in some circumstances will send a stop reply with the ID of a thread that had not been resumed. + +This happens for the following reasons: +1. GDB uses `vCont` exclusively to resume and step through threads. +2. When a thread is interrupted by GDB, QEMU runs `vm_stop(RUN_STATE_PAUSED)`, which triggers `gdb_vm_state_change`, which, in turn, uses whatever CPU is pointed to by `gdbserver_state.c_cpu` at that time to construct the stop reply. +3. The `vCont` handler in QEMU doesn't set `gdbserver_state.c_cpu` before resuming any CPUs. + +Important to note is that stepping is not affected by this issue because the `EXCP_DEBUG` handler sets `gdbserver_state.c_cpu` to the CPU the exception happened in before `gdb_vm_state_change` runs. Which also means single stepping before continuing is an effective way to work around this bug. +Steps to reproduce: +1. Run QEMU with at least two threads and the GDB stub enabled. +2. Run `gdb --nx --ex 'target remote :1234' --ex 'set scheduler-locking on'` +3. Switch to Thread 1.2 in GDB with `thr 2` +4. Resume Thread 1.2 in GDB with `c` +5. Press Ctrl+C to interrupt the VM +6. Notice that the event is reported as having happened in Thread 1.1, which has not been resumed. +Additional information: +Note that, while this bug happens no matter the state of `scheduler-locking`, it only becomes a problem when it is enabled. This is because, when it is disabled, GDB will always resume all threads on `continue`, so it doesn't matter what thread ID QEMU says the interrupt happened in, as it is guaranteed to have been resumed anyway. That, however, is not the case when `scheduler-locking` is enabled. + +Regardless, I don't think it makes sense for QEMU to be reporting events happening in threads that weren't resumed through either `s/S/c/C` or `vCont`, which is what it's doing here. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1727 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1727 new file mode 100644 index 000000000..5163b7265 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1727 @@ -0,0 +1,81 @@ +virtio-gpu-gl-pci console tries to make GL context before widget is realized leading to crash +Description of problem: +When `-vga none` is added to the command line, there is no crash. + +When it is not, two `GtkGLArea` widgets are created: one for VGA and one for `virtio-gpu-gl-pci`. Only the first one is realized, but the virgl code tries to create a GL context for the second. In `gd_gl_area_create_context`, `gtk_widget_get_window(vc->gfx.drawing_area)` evaluates to NULL a crash follows: + +``` +qemu: Gdk: gdk_window_create_gl_context: assertion 'GDK_IS_WINDOW (window)' failed +qemu: Gdk: gdk_gl_context_set_required_version: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_realize: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_make_current: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_get_version: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gtk: gtk_gl_area_make_current: assertion 'gtk_widget_get_realized (widget)' failed +qemu: Gdk: gdk_window_create_gl_context: assertion 'GDK_IS_WINDOW (window)' failed +qemu: Gdk: gdk_gl_context_set_required_version: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_realize: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_make_current: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_get_version: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gtk: gtk_gl_area_make_current: assertion 'gtk_widget_get_realized (widget)' failed +qemu: Gdk: gdk_window_create_gl_context: assertion 'GDK_IS_WINDOW (window)' failed +qemu: Gdk: gdk_gl_context_set_required_version: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_realize: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_make_current: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_get_version: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gtk: gtk_gl_area_make_current: assertion 'gtk_widget_get_realized (widget)' failed +qemu: Gdk: gdk_window_create_gl_context: assertion 'GDK_IS_WINDOW (window)' failed +qemu: Gdk: gdk_gl_context_set_required_version: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_realize: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_make_current: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_get_version: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gtk: gtk_gl_area_make_current: assertion 'gtk_widget_get_realized (widget)' failed +qemu: Gdk: gdk_window_create_gl_context: assertion 'GDK_IS_WINDOW (window)' failed +qemu: Gdk: gdk_gl_context_set_required_version: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_realize: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_make_current: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_get_version: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gtk: gtk_gl_area_make_current: assertion 'gtk_widget_get_realized (widget)' failed +qemu: Gdk: gdk_window_create_gl_context: assertion 'GDK_IS_WINDOW (window)' failed +qemu: Gdk: gdk_gl_context_set_required_version: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_realize: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_make_current: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_get_version: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gtk: gtk_gl_area_make_current: assertion 'gtk_widget_get_realized (widget)' failed +qemu: Gdk: gdk_window_create_gl_context: assertion 'GDK_IS_WINDOW (window)' failed +qemu: Gdk: gdk_gl_context_set_required_version: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_realize: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_make_current: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_get_version: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gtk: gtk_gl_area_make_current: assertion 'gtk_widget_get_realized (widget)' failed +qemu: Gdk: gdk_window_create_gl_context: assertion 'GDK_IS_WINDOW (window)' failed +qemu: Gdk: gdk_gl_context_set_required_version: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_realize: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_make_current: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_get_version: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gtk: gtk_gl_area_make_current: assertion 'gtk_widget_get_realized (widget)' failed +qemu: Gdk: gdk_window_create_gl_context: assertion 'GDK_IS_WINDOW (window)' failed +qemu: Gdk: gdk_gl_context_set_required_version: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_realize: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_make_current: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_get_version: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gtk: gtk_gl_area_make_current: assertion 'gtk_widget_get_realized (widget)' failed +qemu: Gdk: gdk_window_create_gl_context: assertion 'GDK_IS_WINDOW (window)' failed +qemu: Gdk: gdk_gl_context_set_required_version: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_realize: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_make_current: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_get_version: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gtk: gtk_gl_area_make_current: assertion 'gtk_widget_get_realized (widget)' failed +qemu: Gdk: gdk_window_create_gl_context: assertion 'GDK_IS_WINDOW (window)' failed +qemu: Gdk: gdk_gl_context_set_required_version: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_realize: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_make_current: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_get_version: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gtk: gtk_gl_area_make_current: assertion 'gtk_widget_get_realized (widget)' failed +qemu: Gdk: gdk_gl_context_make_current: assertion 'GDK_IS_GL_CONTEXT (context)' failed +gl_version 0 - compat profile +WARNING: running without ARB/KHR robustness in place may crash +qemu-system-x86_64: ../libepoxy/src/dispatch_common.c:872: epoxy_get_proc_address: Assertion `0 && "Couldn't find current GLX or EGL context.\n"' failed. +``` +Steps to reproduce: +1. Get OVMF. On Arch Linux, you can install the `edk2-ovmf` package. On other distros, find a similar package and modify the path in the command accordingly. +2. Run the command above. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1728 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1728 new file mode 100644 index 000000000..b79688f10 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1728 @@ -0,0 +1,18 @@ +blockdev parameter does not accept dots in pool name in json config +Description of problem: +I'm trying to provision a VM using qemu 6.2.0 and pass the remote disk parameters like libvirt. When I start the VM, I get an error saying + + +``` +qemu-system-x86_64: -blockdev {driver:rbd,pool:cloud.disk.hiops,image:csi-vol-8577fffd-0f48-3344-b333-02000038163a,server:[{host:1.2.3.4,port:6789},{host:1.2.3.5,port:6789},{host:1.2.3.6,port:6789}],user:compute-staging,auth-client-required:[cephx,none],key-secret:ceph-secret,node-name:pv-MD7PBV3SRD21L08115JUJ94HMG,cache:{direct:false,no-flush:false},auto-read-only:true,discard:unmap}: JSON parse error, stray '.' +``` + + +I changed the ip address and some fields. + + +My question is should we avoid dots in pool name? I tried to look at the source code of json parser but in its doc, it did not mention a sequence of characters for escaping dots. +Steps to reproduce: +1. Provision a VM with the provided config +Additional information: +bl diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1729 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1729 new file mode 100644 index 000000000..996ecd14d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1729 @@ -0,0 +1,47 @@ +mremap fails with EFAULT if address range overlaps with stack guard +Description of problem: +When running 32-bit user-static on 64-bit host, `mremap` behave differently from the kernel. This difference let programs that call `pthread_getattr_np` on musl-libc to run into a loop on repeated calling `mremap`. + +https://git.musl-libc.org/cgit/musl/plain/src/thread/pthread_getattr_np.c + +``` c + while (mremap(p-l-PAGE_SIZE, PAGE_SIZE, 2*PAGE_SIZE, 0)==MAP_FAILED && errno==ENOMEM) + l += PAGE_SIZE; +``` +Steps to reproduce: +Compile the following program against musl-libc arm 32-bit, and run it in qemu-user-static on x86_64 host. + +``` c +#define _GNU_SOURCE +#include <pthread.h> + +int main(int argc, char *argv[]) { + pthread_attr_t attr; + return pthread_getattr_np(pthread_self(), &attr); +} +``` + +For example, on x86_64 fedora 38 with podman and qemu-user-static installed, we can reproduce this with alpine container: + +``` +$ podman run --rm -it --arch arm/v7 docker.io/library/alpine:latest + +/ # apk add alpine-sdk + +...... + +/ # cat test.c +#define _GNU_SOURCE +#include <pthread.h> + +int main(int argc, char *argv[]) { + pthread_attr_t attr; + return pthread_getattr_np(pthread_self(), &attr); +} + +/ # gcc test.c + +/ # ./a.out +``` +Additional information: +Original thread on musl mail list where this was initially reported: https://www.openwall.com/lists/musl/2017/06/15/9 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/173 b/gitlab/issues_text/target_missing/host_missing/accel_missing/173 new file mode 100644 index 000000000..cfc517638 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/173 @@ -0,0 +1 @@ +unable to read symlinks when mounting 9p filesystem with security_model=mapped diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1730 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1730 new file mode 100644 index 000000000..48091360c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1730 @@ -0,0 +1,16 @@ +Virtual console in GTK input uses wrong color for dark gray +Description of problem: +The virtual console in the GTK window uses black to draw dark gray text. This becomes unintelligible if drawing on black background. +Steps to reproduce: +1. Boot any distro to shell prompt with `-serial vc`. +2. Switch to serial console in QEMU GTK window (Ctrl+Alt+3). +4. Run `echo -e "\e[1;30mDark Greay\e[m"`. +5. Output is black on black. + +or + +1. `qemu-system-x86_64 -bios /usr/share/edk2/x64/OVMF.fd` +2. Enter EFI internal shell +3. `cls 0 8` +4. Run `help cls` and observe correct colors in VGA window. +5. Switch to serial console and observe black on black colors. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1731 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1731 new file mode 100644 index 000000000..aaceefea7 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1731 @@ -0,0 +1,12 @@ +i440fx ide cdrom pathological slow on early win10 install screen +Description of problem: +if you choose i440fx virtual hardware (default in proxmox) for windows 10 instead of q35 , from power on to the windows boot logo is 10 times slower. you need to wait more then 1m45s on my hardware until the blinking cursor in the upper left goes away and the blue windows bootlogo appears. that leads to false assumption, that your setup hangs. + +what's causing this slownewss? + +is implementation really that bad? + +i did compare read performance of ide, sata and scsi cdrom in linux vm and cannot observe such a big difference. + +see +https://forum.proxmox.com/threads/win10-installation-pathological-slowness-with-i440fx-ide-cdrom.129351/ diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1732 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1732 new file mode 100644 index 000000000..210fa72c9 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1732 @@ -0,0 +1,3 @@ +Is there a way to disconnect the network of guest? +Description of problem: +When guest is running,I wan to disconnect the network(not detach the net),which should keep disconnect after migrate or restart if we not reconnect it againt. Whether qemu has some ways to do it? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1734 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1734 new file mode 100644 index 000000000..445455925 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1734 @@ -0,0 +1,16 @@ +mmap-ing more than 1GB of files fails on v8.0 of QEMU, but works on older version +Description of problem: +Trying to run an application using QEMU user mode for an ARM binary. My host system is Ubuntu 22.04 based. The v6.2 from Ubuntu repos is able to mmap files that contain more than 1GB of address space, but version 8.0 that I compiled will not. + +I created a repo with a readme, and a simple application that you can use to demonstrate the problem: +https://github.com/mwales/qemu_mmap_test + +Example application simply takes a list of files, mmaps the entire file into memory, and then computes a checksum of the file data. Once the file(s) sizes exceed around 1GB, the mmap calls will fail because the memory from 0x00000000 - 0x40000000 has been exhausted. +Steps to reproduce: +1. Compile test application that mmaps entire files +2. Create 5 256MB test files +3. Run the program tell it to mmap all the files. The first 3 files succeed, but the 4th when run gets a -1 returned from mmap. +Additional information: +Lots of details on my github writeup and a demo of the bug in question. + +It seems that this 1GB limit is an artifact of where QEMU loaded the original ELF binary at (0x40000000). I've also been playing around with moving that address using the -B 0x80000000 option, but I've encountered other problems doing that. As I diagnose that, I figured I would write up this report on what I've seen so far incase I'm doing something dumb / creating a bad build or something. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1738 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1738 new file mode 100644 index 000000000..3be4a4f4a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1738 @@ -0,0 +1,149 @@ +qemu-system-x86_64 crash during kernel PCI init with large number of busses +Description of problem: +When booting a Linux kernel under qemu-system-x86_64 (tcg) using a large number of PCI busses (25+), qemu crashes with an invalid memory access during kernel PCI init phase. Failure rate is not 100%; some kernel boots do succeed, but the failure rate increases as the number of pci busses increases. Note that no initrd is needed; crash happens before kernel even gets to the point of trying to mount root. +Steps to reproduce: +Launch qemu using command line above along with 4.19.x kernel image (have not tested 5.x). It may take a few tries but within about 20 boot attempts, qemu will crash at least once. +Additional information: +Final kernel logs before crash: +``` +... +[ 1.413615] ACPI: Added _OSI(Module Device) +[ 1.413947] ACPI: Added _OSI(Processor Device) +[ 1.414262] ACPI: Added _OSI(3.0 _SCP Extensions) +[ 1.414421] ACPI: Added _OSI(Processor Aggregator Device) +[ 1.414922] ACPI: Added _OSI(Linux-Dell-Video) +[ 1.415445] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio) +[ 1.444489] ACPI: 1 ACPI AML tables successfully acquired and loaded +[ 1.468218] ACPI: Interpreter enabled +[ 1.469897] ACPI: (supports S0 S3 S4 S5) +[ 1.470200] ACPI: Using IOAPIC for interrupt routing +[ 1.471811] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and repog +[ 1.474421] ACPI: Enabled 2 GPEs in block 00 to 3F +[ 1.536854] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff]) +[ 1.537996] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] +[ 1.540988] acpi PNP0A08:00: _OSC: platform does not support [LTR] +[ 1.542232] acpi PNP0A08:00: _OSC: OS now controls [PME AER PCIeCapability] +[ 1.546310] PCI host bridge to bus 0000:00 +[ 1.546650] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7 window] +[ 1.547471] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff window] +[ 1.548039] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window] +[ 1.548421] pci_bus 0000:00: root bus resource [mem 0x80000000-0xafffffff window] +[ 1.549086] pci_bus 0000:00: root bus resource [mem 0xc0000000-0xfebfffff window] +[ 1.549945] pci_bus 0000:00: root bus resource [mem 0x280000000-0xa7fffffff window] +[ 1.550994] pci_bus 0000:00: root bus resource [bus 00-ff] +<...crash...> +``` + +QEMU backtrace: +``` +$ gdb build/qemu-system-x86_64 core.3475232 +<...> +Reading symbols from build/qemu-system-x86_64... +[New LWP 3475243] +[New LWP 3475244] +[New LWP 3475241] +[New LWP 3475238] +[New LWP 3475245] +[New LWP 3475239] +[New LWP 3475246] +[New LWP 3475240] +[New LWP 3475232] +[New LWP 3475242] +[New LWP 3475236] +[New LWP 3475247] +[Thread debugging using libthread_db enabled] +Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". +Core was generated by `build/qemu-system-x86_64 -m 8192 -smp cpus=10,threads=2 -nographic -machine q35'. +Program terminated with signal SIGSEGV, Segmentation fault. +#0 0x0000556065897e0e in memory_region_dispatch_write (mr=mr@entry=0x0, addr=addr@entry=768, data=data@entry=253, + op=op@entry=MO_32, attrs=...) at ../softmmu/memory.c:1497 +1497 if (mr->alias) { +[Current thread is 1 (Thread 0x7fe2e951d640 (LWP 3475243))] +(gdb) bt full +#0 0x0000556065897e0e in memory_region_dispatch_write + (mr=mr@entry=0x0, addr=addr@entry=768, data=data@entry=253, op=op@entry=MO_32, attrs=...) at ../softmmu/memory.c:1497 + size = <optimized out> +#1 0x00005560659112c2 in io_writex + (env=env@entry=0x556066bbd5d0, full=0x7fe08401ec70, mmu_idx=mmu_idx@entry=2, val=val@entry=253, addr=addr@entry=18446744073699050240, retaddr=retaddr@entry=140611404753775, op=MO_32) at ../accel/tcg/cputlb.c:1430 + _iothread_lock_auto = 0x1 + cpu = 0x556066bbb1e0 + mr_offset = 768 + section = 0x7fe078d7d570 + mr = 0x0 + r = <optimized out> +#2 0x0000556065915f14 in store_helper + (op=MO_32, retaddr=140611404753775, oi=<optimized out>, val=<optimized out>, addr=18446744073699050240, env=0x556066bbd5d0) + at ../accel/tcg/cputlb.c:2454 + full = <optimized out> + need_swap = false + a_bits = <optimized out> + mmu_idx = 2 + tlb_addr = <optimized out> + haddr = <optimized out> + size = 4 + index = <optimized out> + entry = 0x7fe08401bc40 +#3 full_le_stl_mmu (env=0x556066bbd5d0, addr=18446744073699050240, val=253, oi=<optimized out>, retaddr=140611404753775) + at ../accel/tcg/cputlb.c:2542 +#4 0x00007fe2a4d4eb6f in code_gen_buffer () +#5 0x00005560659065bb in cpu_tb_exec + (cpu=cpu@entry=0x556066bbb1e0, itb=itb@entry=0x7fe2a4d4e9c0 <code_gen_buffer+13953427>, tb_exit=tb_exit@entry=0x7fe2e951c758) + at ../accel/tcg/cpu-exec.c:460 + env = 0x556066bbd5d0 + ret = <optimized out> + last_tb = <optimized out> + tb_ptr = 0x7fe2a4d4ea80 <code_gen_buffer+13953619> + __PRETTY_FUNCTION__ = "cpu_tb_exec" +#6 0x0000556065906ab6 in cpu_loop_exec_tb + (tb_exit=0x7fe2e951c758, last_tb=<synthetic pointer>, pc=<optimized out>, tb=0x7fe2a4d4e9c0 <code_gen_buffer+13953427>, cpu=0x556066bbb1e0) at ../accel/tcg/cpu-exec.c:893 + insns_left = <optimized out> + __PRETTY_FUNCTION__ = "cpu_loop_exec_tb" + tb = 0x7fe2a4d4e9c0 <code_gen_buffer+13953427> + flags = <optimized out> + cflags = 4280811520 + cs_base = <optimized out> + pc = <optimized out> + last_tb = <optimized out> + tb_exit = 0 +--Type <RET> for more, q to quit, c to continue without paging-- + ret = <optimized out> +#7 cpu_exec_loop (cpu=cpu@entry=0x556066bbb1e0, sc=sc@entry=0x7fe2e951c7f0) at ../accel/tcg/cpu-exec.c:1013 + tb = 0x7fe2a4d4e9c0 <code_gen_buffer+13953427> + flags = <optimized out> + cflags = 4280811520 + cs_base = <optimized out> + pc = <optimized out> + last_tb = <optimized out> + tb_exit = 0 + ret = <optimized out> +#8 0x0000556065907311 in cpu_exec_setjmp (cpu=cpu@entry=0x556066bbb1e0, sc=sc@entry=0x7fe2e951c7f0) at ../accel/tcg/cpu-exec.c:1043 + __func__ = "cpu_exec_setjmp" +#9 0x00005560659079f0 in cpu_exec (cpu=cpu@entry=0x556066bbb1e0) at ../accel/tcg/cpu-exec.c:1069 + ret = <optimized out> + sc = {diff_clk = 0, last_cpu_icount = 0, realtime_clock = 0} +#10 0x000055606592a854 in tcg_cpus_exec (cpu=cpu@entry=0x556066bbb1e0) at ../accel/tcg/tcg-accel-ops.c:81 + ret = <optimized out> + __PRETTY_FUNCTION__ = "tcg_cpus_exec" +#11 0x000055606592a9a7 in mttcg_cpu_thread_fn (arg=arg@entry=0x556066bbb1e0) at ../accel/tcg/tcg-accel-ops-mttcg.c:95 + r = <optimized out> + + force_rcu = {notifier = {notify = 0x55606592aac0 <mttcg_force_rcu>, node = {le_next = 0x0, le_prev = 0x7fe2e951d4a0}}, cpu = 0x556066bbb1e0} + cpu = 0x556066bbb1e0 + __PRETTY_FUNCTION__ = "mttcg_cpu_thread_fn" + __func__ = "mttcg_cpu_thread_fn" +#12 0x0000556065aa2e91 in qemu_thread_start (args=<optimized out>) at ../util/qemu-thread-posix.c:541 + + __cancel_buf = {__cancel_jmp_buf = {{__cancel_jmp_buf = {140612553791040, -3809744250012005023, 93872529245600, 25, 140612607756368, 140729970282144, -7051494707616903839, -3809738403745854111}, __mask_was_saved = 0}}, __pad = {0x7fe2e951c970, 0x0, 0x0, 0x0}} + __cancel_routine = 0x556065aa2ee0 <qemu_thread_atexit_notify> + __not_first_call = <optimized out> + start_routine = 0x55606592a8a0 <mttcg_cpu_thread_fn> + arg = 0x556066bbb1e0 + r = <optimized out> +#13 0x00007fe2ec894b43 in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:442 + ret = <optimized out> + pd = <optimized out> + + unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140729970281792, 7053160723592154465, 140612553791040, 25, 140612607756368, 140729970282144, -7051494707570766495, -7051505217351676575}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}} + not_first_call = <optimized out> +#14 0x00007fe2ec926a00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1739 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1739 new file mode 100644 index 000000000..ed3b24c20 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1739 @@ -0,0 +1,36 @@ +Build process is broken in /audio/dbusaudio.c:36: pixman.h cannot be found +Description of problem: +Hello. + +I try to build qemu using commit aa1048e33c. But build process stop in /audio/dbusaudio.c with this error log: + +``` +[979/9916] Generating audio-dbus.modin...d (wrapped by meson to capture output) +FAILED: audio-dbus.modinfo +/home/fred/qemu-git/src/qemu/build-full/pyvenv/bin/meson --internal exe --capture audio-dbus.modinfo -- /home/fred/qemu-git/src/qemu/build-full/pyvenv/bin/python3 /home/fred/qemu-git/src/qemu/scripts/modinfo-collect.py ../audio/dbusaudio.c +--- stderr --- +In file included from /home/fred/qemu-git/src/qemu/include/ui/console.h:4, + from /home/fred/qemu-git/src/qemu/ui/dbus.h:31, + from ../audio/dbusaudio.c:36: +/home/fred/qemu-git/src/qemu/include/ui/qemu-pixman.h:12:10: fatal error: pixman.h: No such file or directory + 12 | #include <pixman.h> + | ^~~~~~~~~~ +compilation terminated. +``` + +Of course I have pixman.h which could be find in pixman package: + +``` +pacman -Ql pixman | grep pixman.h +pixman /usr/include/pixman-1/pixman.h +``` + +Used configuration: ```--prefix=/usr --sysconfdir=/etc --localstatedir=/var --libexecdir=/usr/lib/qemu --smbd=/usr/bin/smbd --enable-modules --enable-sdl --disable-werror``` + +The last time I got a buildable qemu was with commit 79dbd910c9, 3 days ago. +Steps to reproduce: +1. Grab latest commit +2. Use this configure line: ```--prefix=/usr --sysconfdir=/etc --localstatedir=/var --libexecdir=/usr/lib/qemu --smbd=/usr/bin/smbd --enable-modules --enable-sdl --disable-werror``` +3. make and wait +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/174 b/gitlab/issues_text/target_missing/host_missing/accel_missing/174 new file mode 100644 index 000000000..90bf8ab27 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/174 @@ -0,0 +1 @@ +European keyboard PC-105 deadkey diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1741 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1741 new file mode 100644 index 000000000..dcd557991 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1741 @@ -0,0 +1 @@ +95059f9c313a7fbd7f22e4cdc1977c0393addc7b breaks some 32bit architectures in linux-user on amd64 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1743 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1743 new file mode 100644 index 000000000..ccb400ae4 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1743 @@ -0,0 +1,16 @@ +QEm+Android emulator crashes on x86 host (but not mac M1) +Description of problem: +Using QEmu+Android emulator crashes when using tflite on x86 hosts (but not M1 macs). +Steps to reproduce: +1. Install android toolchain, including emulator (sdkmanager, adb, avdmanager etc) +2. Start android emulator on an x86 host +3. Follow instructions to download and run tflite benchmarking tool [here](https://www.tensorflow.org/lite/performance/measurement) +4. Crashes with the following error + +``` +06-27 17:38:28.093 8355 8355 F ndk_translation: vendor/unbundled_google/libs/ndk_translation/intrinsics/intrinsics_impl_x86_64.cc:86: CHECK failed: 524288 == 0 +``` + +We have tried with many different models and the result is always the same. The same models run fine when the emulator runs on a mac M1 host. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1744 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1744 new file mode 100644 index 000000000..7d8556ae4 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1744 @@ -0,0 +1 @@ +Divide-by-zero in virtio_gpu_simple_process_cmd diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1746 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1746 new file mode 100644 index 000000000..131ab500d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1746 @@ -0,0 +1,3 @@ +PIC32 support in QEMU +Additional information: +There is a fork of an older version of QEMU that includes running a PIC32 microcontoller in QEMU hosted [here](https://github.com/sergev/qemu), however, it is very outdated. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1747 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1747 new file mode 100644 index 000000000..ece0bda4b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1747 @@ -0,0 +1,16 @@ +eMMC support is missing as a storage type +Additional information: +There seems several attempts at this, but the most recent appears much more complete: +* https://lists.gnu.org/archive/html/qemu-devel/2023-07/msg00347.html + + + +Historical; +"[PATCH v3 06/21] sd: emmc: Update CMD8 to send EXT_CSD register" +https://mail.gnu.org/archive/html/qemu-devel/2021-03/msg00118.html + +"[RFC PATCH 00/17] hw/sd: Rework models for eMMC support" +https://lore.kernel.org/qemu-devel/8aa56da0-a54a-102a-fc85-2fa9f02c18d1@kaod.org/ + +2011 eMMC original support +https://lists.nongnu.org/archive/html/qemu-devel/2011-07/msg02835.html diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1748 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1748 new file mode 100644 index 000000000..dd63e95a0 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1748 @@ -0,0 +1,56 @@ +qcow2: disk size exceeds virtual size +Description of problem: +Disk size of qcow2 image file exceeds its virtual size after repeatedly writing, and deleting data in qemu vm. +Steps to reproduce: +1. qemu-img create -f qcow2 tmp.qcow2 32M +2. attach tmp.qcow2 as a device to qemu vm +3. mount the device in qemu vm, and repeatedly writing, and deleting data +Additional information: +xml for attaching tmp.qcow2 +```xml + <disk device="disk" type="file"> + <target bus="virtio" dev="vdb"/> + <source file="/path/to/tmp.qcow2"/> + <driver type="qcow2" name="qemu" cache="none" discard="unmap"/> + </disk> +``` +in fact, set discard="unmap" or not seems has `little impact` on the final result. +reproducible shell script. +```sh +#! /bin/sh + +for i in {1..1000}; do + for j in {1..27}; do + dd if=/dev/zero of=/mnt/test-$j bs=1M count=1 & + done + sync + sleep 10 + rm -f /mnt/test-* + fstrim /mnt +done +``` +MOUNT the device and run this script, problem happens about 30 minutes. + +final result looks like: +```sh +# qemu-img info tmp.qcow2 --force +image: tmp.qcow2 +file format: qcow2 +virtual size: 32 MiB (33554432 bytes) +disk size: 33 MiB +cluster_size: 65536 +Format specific information: + compat: 1.1 + compression type: zlib + lazy refcounts: false + refcount bits: 16 + corrupt: false + extended l2: false +Child node '/file': + filename: tmp.qcow2 + protocol type: file + file length: 32.3 MiB (33882112 bytes) + disk size: 33 MiB + Format specific information: + extent size hint: 1048576 +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/175 b/gitlab/issues_text/target_missing/host_missing/accel_missing/175 new file mode 100644 index 000000000..42b46dfd9 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/175 @@ -0,0 +1 @@ +qmp monitor deadlock (with spice events for ex) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1753 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1753 new file mode 100644 index 000000000..ea3f48ef4 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1753 @@ -0,0 +1,3 @@ +Does the qemu have luks2 support? +Description of problem: +Does the qemu have luks2 support? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1754 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1754 new file mode 100644 index 000000000..80ffefb8f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1754 @@ -0,0 +1,16 @@ +QEMU wrongly requires SD card sizes to be a power of two +Description of problem: +QEMU arbitrarily requires SD card sizes to be a power of 2. However, this behavior does not match the real world, and I am unable to pass a *physical* SD card into the guest operating system. +``` +$ sudo qemu-system-aarch64 -M raspi2b -drive file=/dev/mmcblk0,if=sd,format=raw +qemu-system-aarch64: Invalid SD card size: 29.7 GiB +SD card size has to be a power of 2, e.g. 32 GiB. +You can resize disk images with 'qemu-img resize <imagefile> <new-size>' +(note that this will lose data if you make the image smaller than it currently is). +``` +Steps to reproduce: +1. Insert a physical SD card into your host system and make a note of its device name. It will be something like `/dev/mmcblk0` +2. Attempt to start a guest OS with the SD card attached. See the command above. +3. You will get an error saying that the card size is not a power of two. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1755 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1755 new file mode 100644 index 000000000..c23d64c07 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1755 @@ -0,0 +1,20 @@ +qemu-arm fails to execute a cortex-M binary (page_set_flags: Assertion 'last <= GUEST_ADDR_MAX' failed.) +Description of problem: +I've noticed that qemu-arm (so linux-user mode) fails to execute a binary targeting cortex-M. This used to work until commit +"Make the commpage executable". +Steps to reproduce: +1. Compile a simple hello.c for arm-eabi. If you don't have such a toolchain, you can download one from https://developer.arm.com/downloads/-/arm-gnu-toolchain-downloads For instance https://developer.arm.com/-/media/Files/downloads/gnu/12.2.rel1/binrel/arm-gnu-toolchain-12.2.rel1-x86_64-arm-none-eabi.tar.xz (for an x86_64 linux host) + +2.# compile for cortex-m3: + +3. arm-none-eabi-gcc hello.c -o hello.exe.m3 -mcpu=cortex-m3 -specs=rdimon.specs + +4.qemu-arm -cpu cortex-m3 hello.exe.m3 +.....user-exec.c:492: page_set_flags: Assertion 'last <= GUEST_ADDR_MAX' failed. + +5. # compile for cortex-a9: + +6. arm-none-eabi-gcc hello.c -o hello.exe.a9 -mcpu=cortex-a9 -specs=rdimon.specs + +7. qemu-arm -cpu cortex-a9 hello.exe.a9 +Hello diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1756 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1756 new file mode 100644 index 000000000..1c30a239b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1756 @@ -0,0 +1,43 @@ +qemu8-user on Linux: SIGSEGV because brk(NULL) does not exist +Description of problem: +On Linux, the return value of the system call brk(NULL) need not point to a page that exists. +If so, then qemu8-user will generate SIGSEGV at the next call to brk() with a higher value, +because qemu8 believes that it should maintain contiguous .bss with bytes of value 0. +Thus qemu8-user so calls `memset(g2h_untagged(target_brk), 0, brk_page - target_brk); +in do_brk() at ../linux-user/syscall.c:867, and this generates SIGSEGV at +the non-existent page that covers brk(NULL). + +Instead, the safest thing to do is nothing at all. +Linux deliberately returns a random value for brk(NULL), subject to the conditions +that the value be at least as large as the maximum over all PT_LOAD of (.p_vaddr + .p_memsz), +and "somewhat near" that maximum. The purpose of randomness is to use variability +to interfere with effectiveness of malware, and to expose application coding errors +regarding brk() and sbrk(). If qemu-user wants to preserve contiguous .bss, +then qemu-user should call memset() only if the first page of the range exists. +(As explained in the next paragraph, "contiguous .bss" is a murky concept.) + +Linux itself is partly to blame, because it computes the maximum (.p_vaddr + .p_memsz) +over all the PT_LOAD of the most recent execve(). The most recent execve() seen by +Linux might have no relationship to the state of the address space at the time of +_either_ call to brk(). The app can do arbitrary mmap, munmap, mprotect at any time. +In particular, the run-time de-compressor of UPX does exactly that for a compressed +main program. The maximum computed by Linux is for the compressed program, +which has a different layout than the de-compressed program. + +There is a Linux system call prctl(PR_SET_MM_BRK, new_value) which sets a value +for "the brk", but that syscall tries to validate the new_value based on +the most recent execve(). Once again, that has no relationship to the current +layout of the address space produced by the UPX de-compressor. +Steps to reproduce: +1. build qemu8-x86_64 from +``` +commit fcb237e64f9d026c03d635579c7b288d0008a6e5 (HEAD -> master, origin/master, origin/HEAD) +Merge: 2ff49e96ac c00aac6f14 +Date: Mon Jul 10 09:17:06 2023 +0100 +``` +2. run `build/qemu-x86_64 -strace upx-4.0.2-amd64_linux/upx --version` where the upx +is from https://github.com/upx/upx/releases/download/v4.0.2/upx-4.0.2-amd64_linux.tar.xz +3. output ends with +``` +372621 close(3) = 0 +372621 munmap(0x0000004000803000,3055) = 0 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1757 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1757 new file mode 100644 index 000000000..138abda46 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1757 @@ -0,0 +1 @@ +guest-agent: improve help for --allow-rpcs and --block-rpcs diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1758 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1758 new file mode 100644 index 000000000..13c8ad5f6 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1758 @@ -0,0 +1,12 @@ +libssh missing on macOS/m1 +Description of problem: +I did a "git pull" in my source for qemu. Now when I do "make" I get: +../block/ssh.c:27:10: fatal error: 'libssh/libssh.h' file not found + +Am I supposed to install libssh separately? I were able to compile qemu about a month ago or so. +Steps to reproduce: +1. +2. +3. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1759 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1759 new file mode 100644 index 000000000..098bafaf3 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1759 @@ -0,0 +1,10 @@ +qemu-system-i386 error during install windows 95/98 +Description of problem: +Installation of the Windows starts but when Windows 95 is supposed to copy files it failes like:  +Installation of Windows 98 failes like:  +Steps to reproduce: +1. get boot floppy & install cd for windows 95 +2. create hard drive C image +3. try to install Windows 95 +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/176 b/gitlab/issues_text/target_missing/host_missing/accel_missing/176 new file mode 100644 index 000000000..0449b9016 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/176 @@ -0,0 +1 @@ +virtual machine cpu soft lockup when qemu attach disk diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1760 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1760 new file mode 100644 index 000000000..b6afa4408 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1760 @@ -0,0 +1,53 @@ +qemu8-i386 gets wrong arguments for 32-bit old mmap syscall (_NR_mmap = 90) +Description of problem: +qemu8-i386 does not decode syscall arguments correctly for system call _NR_mmap = 90 on i386. +``` +$ strace ./oldmmap +execve("./oldmmap", ["./oldmmap"], 0x7fff46ba6d40 /* 61 vars */) = 0 +[ Process PID=405233 runs in 32 bit mode. ] +mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xf7fa7000 +exit(5) = ? ++++ exited with 5 +++ + +$ build/qemu-i386 -strace ./oldmmap +405254 mmap(0x40800058,0,PROT_NONE,0,0,0) = 0x3fffb000 +405254 exit(5) +``` +Steps to reproduce: +1. gcc -m32 -o oldmmap -nostartfiles -nostdlib oldmmap.S # build 32-bit executable +2. strace ./oldmmap # run under strace +3. build/qemu-i386 -strace ./oldmmap # run under "qemu-i386 -strace" +4. Notice that qemu-i386 did not report the same arguments to the _NR_map syscall as /usr/bin/strace did. +Additional information: +``` +$ cat oldmmap.S +MAP_FIXED= 0x10 +MAP_PRIVATE= 0x02 +MAP_ANONYMOUS= 0x20 + +PROT_READ= 1 +PROT_WRITE= 2 +PROT_EXEC= 4 + +_NR_exit = 1 +_NR_mmap = 90 // oldmmap: %ebx -> array of 6 arguments + + .globl _start +_start: + push $0 // offset + push $-1 // fd + push $MAP_PRIVATE|MAP_ANONYMOUS // flags + push $PROT_READ|PROT_WRITE // protection + push $2<<12 // length + push $0 // addr (kernel chooses) + mov %esp,%ebx + mov $_NR_mmap,%eax + int $0x80 + nop + + mov $5,%ebx + mov $_NR_exit,%eax + int $0x80 + hlt +$ +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1764 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1764 new file mode 100644 index 000000000..d1c317eb7 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1764 @@ -0,0 +1 @@ +lsusb fails with qemu-system-x86_64 command (qemu-system-x86 package) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1766 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1766 new file mode 100644 index 000000000..0dec71af0 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1766 @@ -0,0 +1,3 @@ +-strace should print target program counter when SIGSEGV +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1767 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1767 new file mode 100644 index 000000000..3792bf336 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1767 @@ -0,0 +1,3 @@ +Add iphone emulated device +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1768 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1768 new file mode 100644 index 000000000..0bd34a03d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1768 @@ -0,0 +1,32 @@ +Could not allocate more than ~2GB with qemu-user +Description of problem: +On qemu-user, failed to allocate more than about 2GB on 32bit platform supporting up to 4GB (arm, ppc, etc.) +Steps to reproduce: +1. Try to allocate more than 2GB [e.g. for(i=0;i<64;i++) if(malloc(64*1024*1024)==NULL) perror("Failed to allocate 64MB");] +2. Only 1 64MB chunck is allocated in the upper 2GB memory space +3. Failed to allocate after about 2GB. +Additional information: +The problem is in **pageflags_find** and **pageflags_next** functions (found in _accel/tcg/user-exec.c_) 3rd parameters, that should be **target_ulong** instead of incorrect _target_long_ (the parameter will be converted signed extended to uint64_t). +The testing program is the following: +``` +#include <stdio.h> +#include <stdlib.h> + +int main(int argc,char *argv[]) { + unsigned int a; + unsigned int i; + char *al; + unsigned int sss=1U*1024*1024*64; + for(a=0;a<128;a++) { + al=malloc(sss); + if(al!=NULL) { + printf("ALLOC OK %u (%08lX)!\n",sss*(a+1),al); + } + else { + printf("Cannot alloc %d\n",(a+1)*sss); + perror("Cannot alloc"); + exit(1); + } + } +} +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/177 b/gitlab/issues_text/target_missing/host_missing/accel_missing/177 new file mode 100644 index 000000000..4745d7304 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/177 @@ -0,0 +1 @@ +qemu-bridge-helper undocumented and broken diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1770 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1770 new file mode 100644 index 000000000..002e39109 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1770 @@ -0,0 +1,22 @@ +Wrong unpacked structure for epoll_event on qemu-or1k (openrisc) +Description of problem: +When using cmake automoc, the process will infinite loop waiting for epoll_events. +Steps to reproduce: +1. Try to compile cmake with qt5 support +2. The build process will freeze when "Automatic MOC" is invoked +Additional information: +The problem is that or1k has a "packed" epoll_event structure, so it should be also packed in target_epoll_event structure. +Following the (very trivial) patch: +``` +--- qemu-20230327/linux-user/syscall_defs.h.orig 2023-03-27 15:41:42.000000000 +0200 ++++ qemu-20230327/linux-user/syscall_defs.h 2023-06-30 17:29:39.034322213 +0200 +@@ -2714,7 +2709,7 @@ + #define FUTEX_CMD_MASK ~(FUTEX_PRIVATE_FLAG | FUTEX_CLOCK_REALTIME) + + #ifdef CONFIG_EPOLL +-#if defined(TARGET_X86_64) ++#if defined(TARGET_X86_64) || defined(TARGET_OPENRISC) + #define TARGET_EPOLL_PACKED QEMU_PACKED + #else + #define TARGET_EPOLL_PACKED +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1773 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1773 new file mode 100644 index 000000000..abdceee96 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1773 @@ -0,0 +1,9 @@ +qemu does not use the mic of the webcam dedicated to the VM +Description of problem: + +Steps to reproduce: +1. plug two webcams to the desktop, one for the host and one for the VM +2. launch QEMU VM +3. QEMU VM take the desktop webcam mic instead of the webcam mic dedicated to the VM. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1775 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1775 new file mode 100644 index 000000000..926932e07 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1775 @@ -0,0 +1,61 @@ +QEMU abort on Cortex-M breakpoint exception +Description of problem: +When a breakpoint exception is raised in a ARM Cortex-M board QEMU aborts. + +``` +$ qemu-system-arm --version +QEMU emulator version 8.0.90 (v8.1.0-rc0-21-gd1181d2937) + +$ ./qemu-system-arm -M stm32vldiscovery -nographic -device loader,file=raw-bkpt.hex -d in_asm,exec,int +[...] +Trace 0: 0x7fac6c000100 [00800400/0000000000000100/00000110/ff200000] +---------------- +IN: +0x00000110: be01 bkpt #1 + +Linking TBs 0x7fac6c000100 index 0 -> 0x7fac6c0002c0 +Trace 0: 0x7fac6c0002c0 [00800400/0000000000000110/00000110/ff200000] +qemu-system-arm: ../target/arm/helper.c:12224: arm_security_space_below_el3: Assertion `!arm_feature(env, ARM_FEATURE_M)' failed. +``` + +Expected behavior: +``` +$ qemu-system-arm --version +QEMU emulator version 7.1.0 + +$ ./qemu-system-arm -M stm32vldiscovery -nographic -device loader,file=raw-bkpt.hex -d in_asm,exec,int +[...] +Trace 0: 0x7f5408000100 [00800400/00000100/00000110/ff000000] +---------------- +IN: +0x00000110: be01 bkpt #1 + +Linking TBs 0x7f5408000100 [00000100] index 0 -> 0x7f54080002c0 [00000110] +Trace 0: 0x7f54080002c0 [00800400/00000110/00000110/ff000000] +Taking exception 7 [Breakpoint] on CPU 0 +...BusFault with BFSR.STKERR +...taking pending nonsecure exception 3 +...loading from element 3 of non-secure vector table at 0xc +...loaded new PC 0x0 +---------------- +``` +Steps to reproduce: +1. Run any Cortex-M firmware that raises a breakpoint exception. (minimal example attached) +Additional information: +- Minimal Reproducer: +[raw-bkpt.hex](/uploads/b9289c6f3a4feef015c8a3dffb4fc467/raw-bkpt.hex) +- This is **not** a duplicate of #1658 / #1740 +- Stacktrace: +``` +#2 0x00007ffff5a68538 in abort () at /usr/lib/libc.so.6 +#3 0x00007ffff5a6845c in () at /usr/lib/libc.so.6 +#4 0x00007ffff5a783d6 in () at /usr/lib/libc.so.6 +#5 0x0000555555c55921 in arm_security_space_below_el3 (env=0x555556dc1b40) at ../target/arm/helper.c:12224 +#6 arm_security_space_below_el3 (env=env@entry=0x555556dc1b40) at ../target/arm/helper.c:12222 +#7 0x0000555555c48b08 in arm_is_secure_below_el3 (env=0x555556dc1b40) at ../target/arm/cpu.h:2465 +#8 arm_is_el2_enabled (env=0x555556dc1b40) at ../target/arm/cpu.h:2517 +#9 arm_debug_target_el (env=env@entry=0x555556dc1b40) at ../target/arm/debug_helper.c:24 +#10 0x0000555555c49cb5 in helper_exception_bkpt_insn (env=0x555556dc1b40, syndrome=0xe2000001) at ../target/arm/debug_helper.c:510 +#11 0x00007fffac0002d9 in code_gen_buffer () +[...] +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1777 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1777 new file mode 100644 index 000000000..59e9986a5 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1777 @@ -0,0 +1 @@ +Allow logging of IP addresses of connections made to QEMU socket backends for e.g. VNC or SPICE console diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1778 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1778 new file mode 100644 index 000000000..b007a3680 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1778 @@ -0,0 +1 @@ +Spice audio play at wrong speed and frequency after qemu-7.2.0 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/178 b/gitlab/issues_text/target_missing/host_missing/accel_missing/178 new file mode 100644 index 000000000..143483b3c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/178 @@ -0,0 +1 @@ +Meson setup fails with meson 0.58.0 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1781 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1781 new file mode 100644 index 000000000..b50fa1b4a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1781 @@ -0,0 +1,54 @@ +8.1.0rc0: configure from tar file fetches subprojects via git +Description of problem: +Executing configure from tar file fetches subprojects via git. Fetched subprojects are https://gitlab.com/qemu-project/dtc and https://gitlab.com/qemu-project/keycodemapdb +``` +$ ./configure --disable-download +Using './build' as the directory for build output +... +Initialized empty Git repository in /home/helge/qemu-8.1.0-rc0/subprojects/dtc/.git/ +remote: Enumerating objects: 319, done. +remote: Counting objects: 100% (319/319), done. +remote: Compressing objects: 100% (251/251), done. +remote: Total 319 (delta 54), reused 163 (delta 38), pack-reused 0 +Receiving objects: 100% (319/319), 250.56 KiB | 1.94 MiB/s, done. +Resolving deltas: 100% (54/54), done. +From https://gitlab.com/qemu-project/dtc + * branch b6910bec11614980a21e46fbccc35934b671bd81 -> FETCH_HEAD +HEAD is now at b6910be Bump version to v1.6.1 +... +Initialized empty Git repository in /home/helge/qemu-8.1.0-rc0/subprojects/keycodemapdb/.git/ +remote: Enumerating objects: 26, done. +remote: Counting objects: 100% (26/26), done. +remote: Compressing objects: 100% (21/21), done. +remote: Total 26 (delta 0), reused 23 (delta 0), pack-reused 0 +Unpacking objects: 100% (26/26), 30.65 KiB | 216.00 KiB/s, done. +From https://gitlab.com/qemu-project/keycodemapdb + * branch f5772a62ec52591ff6870b7e8ef32482371f22c6 -> FETCH_HEAD +HEAD is now at f5772a6 Add Qemu qcode support for F13 to F24 +... +``` + +Using `--disable-download` is no option: +``` +$ ./configure --disable-download +Using './build' as the directory for build output + +ERROR: missing subprojects + +This is not a GIT checkout but subproject content appears to +be missing. Do not use 'git archive' or GitHub download links +to acquire QEMU source archives. Non-GIT builds are only +supported with source archives linked from: + + https://www.qemu.org/download/#source +``` + +If I understand the error message correctly, the subprojects should be part of the tar. +Steps to reproduce: +1. Open Clang64 console +2. `pacman -Syu` +3. `pacman -S binutils mingw-w64-clang-x86_64-toolchain mingw-w64-clang-x86_64-glib2 mingw-w64-clang-x86_64-ninja mingw-w64-clang-x86_64-pixman mingw-w64-clang-x86_64-python mingw-w64-clang-x86_64-python-sphinx mingw-w64-clang-x86_64-python-sphinx_rtd_theme` +4. `wget https://download.qemu.org/qemu-8.1.0-rc0.tar.xz` +5. `tar -xf qemu-8.1.0-rc0.tar.xz` +6. `cd qemu-8.1.0-rc0` +7. `./configure` or `./configure --disable-download` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1782 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1782 new file mode 100644 index 000000000..62b3b34db --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1782 @@ -0,0 +1,58 @@ +8.1.0rc0: Build failure compiling with clang on windows +Description of problem: +Building in Clang64 environment finally fails with: +``` +... +[1416/2001] Compiling C object libcommon.fa.p/ui_dbus-listener.c.obj +FAILED: libcommon.fa.p/ui_dbus-listener.c.obj +"cc" "-m64" "-mcx16" "-Ilibcommon.fa.p" "-Isubprojects/dtc/libfdt" "-I../subprojects/dtc/libfdt" "-Iui" "-I../ui" "-IC:/msys64/clang64/include/pixman-1" "-IC:/msys64/clang64/include/glib-2.0" "-IC:/msys64/clang64/lib/glib-2.0/include" "-IC:/msys64/clang64/include/ncursesw" "-fcolor-diagnostics" "-Wall" "-Winvalid-pch" "-std=gnu11" "-O2" "-g" "-fstack-protector-strong" "-Wundef" "-Wwrite-strings" "-Wmissing-prototypes" "-Wstrict-prototypes" "-Wredundant-decls" "-Wold-style-definition" "-Wtype-limits" "-Wformat-security" "-Wformat-y2k" "-Winit-self" "-Wignored-qualifiers" "-Wempty-body" "-Wnested-externs" "-Wendif-labels" "-Wexpansion-to-defined" "-Wmissing-format-attribute" "-Wno-initializer-overrides" "-Wno-missing-include-dirs" "-Wno-shift-negative-value" "-Wno-string-plus-int" "-Wno-typedef-redefinition" "-Wno-tautological-type-limit-compare" "-Wno-psabi" "-Wno-gnu-variable-sized-type-not-at-end" "-Wthread-safety" "-iquote" "." "-iquote" "C:/msys64/home/helge/qemu-8.1.0-rc0" "-iquote" "C:/msys64/home/helge/qemu-8.1.0-rc0/include" "-iquote" "C:/msys64/home/helge/qemu-8.1.0-rc0/host/include/x86_64" "-iquote" "C:/msys64/home/helge/qemu-8.1.0-rc0/host/include/generic" "-iquote" "C:/msys64/home/helge/qemu-8.1.0-rc0/tcg/i386" "-D_GNU_SOURCE" "-D_FILE_OFFSET_BITS=64" "-D_LARGEFILE_SOURCE" "-fno-strict-aliasing" "-fno-common" "-fwrapv" "-fno-pie" "-DNCURSES_WIDECHAR" "-DNCURSES_WIDECHAR=1" -MD -MQ libcommon.fa.p/ui_dbus-listener.c.obj -MF "libcommon.fa.p/ui_dbus-listener.c.obj.d" -o libcommon.fa.p/ui_dbus-listener.c.obj "-c" ../ui/dbus-listener.c +../ui/dbus-listener.c:355:10: error: call to undeclared function 'd3d_texture2d_release0'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration] + if (!d3d_texture2d_release0(tex, &err)) { + ^ +../ui/dbus-listener.c:360:10: error: call to undeclared function 'd3d_texture2d_share'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration] + if (!d3d_texture2d_share(tex, &share_handle, &err)) { + ^ +../ui/dbus-listener.c:392:10: error: call to undeclared function 'd3d_texture2d_acquire0'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration] + if (!d3d_texture2d_acquire0(tex, &err)) { + ^ +3 errors generated. +ninja: build stopped: subcommand failed. +make[1]: *** [Makefile:162: run-ninja] Error 1 +make[1]: Leaving directory '/home/helge/qemu-8.1.0-rc0/build' +make: *** [GNUmakefile:11: all] Error 2 + +... +``` +Steps to reproduce: +1. Open Clang64 console +2. `pacman -Syu` +3. `pacman -S binutils mingw-w64-clang-x86_64-toolchain mingw-w64-clang-x86_64-glib2 mingw-w64-clang-x86_64-ninja mingw-w64-clang-x86_64-pixman mingw-w64-clang-x86_64-python mingw-w64-clang-x86_64-python-sphinx mingw-w64-clang-x86_64-python-sphinx_rtd_theme` +4. `wget https://download.qemu.org/qemu-8.1.0-rc0.tar.xz` +5. `tar -xf qemu-8.1.0-rc0.tar.xz` +6. `cd qemu-8.1.0-rc0` +7. `./configure --target-list=x86_64-softmmu` +8. `make` +Additional information: +The used cc is clang in Msys2/Clang64 environment: +``` +$ md5sum /clang64/bin/cc.exe /clang64/bin/clang.exe +bb70e04a10456b05b07f14d190ad9015 */clang64/bin/cc.exe +bb70e04a10456b05b07f14d190ad9015 */clang64/bin/clang.exe +``` + +On manually repeating the command in build directory a different error is shown: +``` +$ cd build +$ "cc" "-m64" "-mcx16" "-Ilibcommon.fa.p" "-Isubprojects/dtc/libfdt" "-I../subprojects/dtc/libfdt" "-Iui" "-I../ui" "-IC:/msys64/clang64/include/pixman-1" "-IC:/msys64/clang64/include/glib-2.0" "-IC:/msys64/clang64/lib/glib-2.0/include" "-IC:/msys64/clang64/include/ncursesw" "-fcolor-diagnostics" "-Wall" "-Winvalid-pch" "-std=gnu11" "-O2" "-g" "-fstack-protector-strong" "-Wundef" "-Wwrite-strings" "-Wmissing-prototypes" "-Wstrict-prototypes" "-Wredundant-decls" "-Wold-style-definition" "-Wtype-limits" "-Wformat-security" "-Wformat-y2k" "-Winit-self" "-Wignored-qualifiers" "-Wempty-body" "-Wnested-externs" "-Wendif-labels" "-Wexpansion-to-defined" "-Wmissing-format-attribute" "-Wno-initializer-overrides" "-Wno-missing-include-dirs" "-Wno-shift-negative-value" "-Wno-string-plus-int" "-Wno-typedef-redefinition" "-Wno-tautological-type-limit-compare" "-Wno-psabi" "-Wno-gnu-variable-sized-type-not-at-end" "-Wthread-safety" "-iquote" "." "-iquote" "C:/msys64/home/helge/qemu-8.1.0-rc0" "-iquote" "C:/msys64/home/helge/qemu-8.1.0-rc0/include" "-iquote" "C:/msys64/home/helge/qemu-8.1.0-rc0/host/include/x86_64" "-iquote" "C:/msys64/home/helge/qemu-8.1.0-rc0/host/include/generic" "-iquote" "C:/msys64/home/helge/qemu-8.1.0-rc0/tcg/i386" "-D_GNU_SOURCE" "-D_FILE_OFFSET_BITS=64" "-D_LARGEFILE_SOURCE" "-fno-strict-aliasing" "-fno-common" "-fwrapv" "-fno-pie" "-DNCURSES_WIDECHAR" "-DNCURSES_WIDECHAR=1" -MD -MQ libcommon.fa.p/ui_dbus-listener.c.obj -MF "libcommon.fa.p/ui_dbus-listener.c.obj.d" -o libcommon.fa.p/ui_dbus-listener.c.obj "-c" ../ui/dbus-listener.c +../ui/dbus-listener.c:236:9: error: expected expression + Error *err = NULL; + ^ +../ui/dbus-listener.c:240:56: error: use of undeclared identifier 'err' + if (!d3d_texture2d_release0(ddl->d3d_texture, &err)) { + ^ +../ui/dbus-listener.c:241:30: error: use of undeclared identifier 'err' + error_report_err(err); + ^ +3 errors generated. + +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1783 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1783 new file mode 100644 index 000000000..685d9595e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1783 @@ -0,0 +1,3 @@ +Emulate Breakout Network Connections +Additional information: +This functionality is required to model/QA real-world implementations for datacenter fabrics in virtual environments. Break-out cabling is how port density is achieved in practice on modern optical fabrics. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1784 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1784 new file mode 100644 index 000000000..ffcbc6dae --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1784 @@ -0,0 +1,13 @@ +Mac M1 Max / Debian guest / Luks password / Switching to graphical login manager (lightdm/Gdm) hangs in 75% +Description of problem: +In approximately 70% of cases I start QEMU with a Debian guest where the Debian guest was installed with full disk encryption, QEMU 'hangs' (does not respond') after I unlock the encrypted guest and the guest tries to start the graphical login manager (gdm or lightdm). + +I need to force quit QEMU, restart it multiple times until the start of the graphical login manager works. +Steps to reproduce: +1. Install Debian with (guided) full disk encryption and either the Gnome or the XFCE desktop environment +2. To be able to unlock the hard disk after the installation finished, the Linux boot parameter 'console=tty1' needs to be added within grub to the Linux command line +3. Try to restart/reboot QEMU several times and QEMU will become unresponsive multiple times in this process. +Additional information: +I encounter this problem for several months now, with different versions of QEMU, macOS and Debian. + +There is one observation, which might help: I installed [DropBear](https://packages.debian.org/buster/dropbear-initramfs) to experiment with remote unlocking of Luks encrypted Linux boxes. It seems, that QEMU does not go into the unresponsive state, when I unlock the hard disk via SSH and not focus the QEMU window until after the graphical login manager started. (Only tried remote unlocking a few times so it is too early to confirm if this works 100% of the time. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1785 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1785 new file mode 100644 index 000000000..684ed07ac --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1785 @@ -0,0 +1,25 @@ +8.1.0rc0: Build failure when building static binaries, auto config incorrectly mark bzip2 as supported on my machine +Description of problem: +8.1.0rc0 fails to build when I build static binaries. + +``` +Jul 24 20:28:22 clang-13: warning: argument unused during compilation: '-pie' [-Wunused-command-line-argument] +Jul 24 20:28:22 ld.lld: error: attempted static link of dynamic object /usr/bin/../lib/libbz2.so +Jul 24 20:28:22 clang-13: error: linker command failed with exit code 1 (use -v to see invocation) +``` + +It seems that `./configure` mistaken my dynamic library of bzip2 as able to compile under static compilation. +Steps to reproduce: +1. `./configure --target-list=x86_64-softmmu --static` with bzip2 only dynamicly installed and static library not installed +2. see output + +You can see +``` + snappy support : NO + bzip2 support : YES + lzfse support : NO +``` + +which is wrong. Additionally, the compilation fails because the system only have bzip2 dynamicly but not staticly. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1786 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1786 new file mode 100644 index 000000000..a58ec5747 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1786 @@ -0,0 +1,24 @@ +Impossible to create an uncompressed QCOW2 disk +Description of problem: +An QCOW2 image is created compressed unconditionally. There is no way to disable compression, albeit the QCOW format specification allows this. + +``` +$ qemu-img --version +qemu-img version 6.2.0 (Debian 1:6.2+dfsg-2ubuntu6.12) +Copyright (c) 2003-2021 Fabrice Bellard and the QEMU Project developers +$ qemu-img create -f qcow2 test.qcow2 1G +Formatting 'test.qcow2', fmt=qcow2 cluster_size=65536 extended_l2=off compression_type=zlib size=1073741824 lazy_refcounts=off refcount_bits=16 +$ +``` + +Same is applicable for 8-x qemu-img version (I built it for testing purposes) +``` +$ ./build/qemu-img create -f qcow2 disk.qcow2 1G +Formatting 'disk.qcow2', fmt=qcow2 cluster_size=65536 extended_l2=off compression_type=zlib size=1073741824 lazy_refcounts=off refcount_bits=16 +$ ./build/qemu-img --version +qemu-img version 8.0.90 (v8.1.0-rc0-21-gd1181d2937) +Copyright (c) 2003-2023 Fabrice Bellard and the QEMU Project developers +$ +``` +Steps to reproduce: +Create a QCOW2 disk with `qemu-img` of never versions. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1787 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1787 new file mode 100644 index 000000000..d7a87a524 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1787 @@ -0,0 +1,13 @@ +Qemu asan test make vm crash when using qxl and spice +Description of problem: +When I tested QEMU with asan, the vm crash. The error message is as follows： + +Steps to reproduce: +1.Start the vm with qxl and spice. +2.Attach the vm with vnc and spice. +3.Placed for more than three days. +4.Operation on spice client and possible reproduce this bug. +Additional information: +https://github.com/qemu/qemu/blob/44f28df24767cf9dca1ddc9b23157737c4cbb645/ui/cursor.c#L112 +I think the reason for the problem is that the cursor pointer was not set to NULL when qemu call cursor_put. But I don't know what situation will trigger this error. +This error is difficult to reproduce by natural. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1788 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1788 new file mode 100644 index 000000000..c04f1f04d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1788 @@ -0,0 +1,29 @@ +Floating point rounding fails on mps3-an547 amd cortex-m55 while using LLVM-embedded-toolchain-for-Arm and Picolibic. +Description of problem: +Rounding of long double gives unexpected result. Simple code as example: +``` +#include <math.h> +int main(void) +{ + long double value = -8.5L; + long rounded_value = lrintl(value); + if( -8 == rounded_value ) + { + return 0; + } + return 1; +} +``` +Steps to reproduce: +1. Checkout project: [LLVM-embedded-toolchain-for-ARM](https://github.com/ARM-software/LLVM-embedded-toolchain-for-Arm) +2. Configure it with option -DLLVM_TOOLCHAIN_LIBRARY_VARIANTS=armv8.1m.main_hard_nofp_mve +3. Build project +4. Run Picolbic tests with ninja picolibc_armv8.1m.main_hard_nofp_mve-test + +As a result long_double test fails with incorrect rounding. +Last qemu version which successfully execute mentioned test is: qemu 7.0.0 downloaded via [qemu-7.0.0](https://download.qemu.org/qemu-7.0.0.tar.bz2). +Issue is present since qemu version 7.1. +Additional information: +As a result long_double test fails with incorrect rounding. +Last qemu version which successfully execute mentioned test is: qemu 7.0.0 downloaded via [qemu-7.0.0](https://download.qemu.org/qemu-7.0.0.tar.bz2). +Issue is present since qemu version 7.1. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1789 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1789 new file mode 100644 index 000000000..841bbd3cf --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1789 @@ -0,0 +1,17 @@ +First connection to spice hangs after 1 min +Description of problem: +After starting a VM the first connection to spice logs this errors: + +``` +2023-07-25T16:00:47.497042Z qemu-system-x86_64: warning: Spice: main:0 (0x7f1a3fca5b90): invalid net test stage, ping id 0 test id 0 stage 4 +2023-07-25T16:00:47.497170Z qemu-system-x86_64: warning: Spice: main:0 (0x7f1a3fca5b90): invalid net test stage, ping id 0 test id 0 stage 0 +``` + +And after 60 seconds the spice viewer is closed with this error: +``` +2023-07-25T16:01:47.384207Z qemu-system-x86_64: warning: Spice: main:0 (0x7f1a3fca5b90): rcc 0x7f1a1968cb60 has been unresponsive for more than 30000 ms, disconnecting +``` +Steps to reproduce: +1. Start vm with spice +2. Connect to spice +3. Wait for at least 60 seconds and the viewer will close diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/179 b/gitlab/issues_text/target_missing/host_missing/accel_missing/179 new file mode 100644 index 000000000..e3c40e1a1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/179 @@ -0,0 +1 @@ +qemu guest crashes on spice client USB redirected device removal diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1791 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1791 new file mode 100644 index 000000000..b01c936b3 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1791 @@ -0,0 +1,40 @@ +qemu 8.1.0 rc tarballs are broken, missing subproject content +Description of problem: +The released tarballs for 8.1.0 rc releases (both rc0 adn rc1) are missing the +subproject content. Only the submodule content appears present +Steps to reproduce: +1. `wget http://download.qemu.org/qemu-8.1.0-rc1.tar.xz` +2. `tar Jxvf qemu-8.1.0-rc1.tar.xz` +3. `cd qemu-8.1.0-rc1` +4. `./configure --target-list=x86_64-softmmu --disable-download` + +``` +Using './build' as the directory for build output + +ERROR: missing subprojects + +This is not a GIT checkout but subproject content appears to +be missing. Do not use 'git archive' or GitHub download links +to acquire QEMU source archives. Non-GIT builds are only +supported with source archives linked from: + + https://www.qemu.org/download/#source + +Developers working with GIT can use scripts/archive-source.sh +if they need to create valid source archives. + +``` + +The missing subprojects are + +``` + berkeley-softfloat-3 + berkeley-testfloat-3 + dtc + keycodemapdb + libvfio-user +``` + +If I use 'make-release . 8.1.0-rc1' to create a tarball from git, it has all the expected content. + +IOW, either the release tarballs are not being created using 'make-release', or there's something broken with 'make-release' in some scenarios diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1792 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1792 new file mode 100644 index 000000000..e0f78ec63 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1792 @@ -0,0 +1,81 @@ +qemu-8.1-rc1 and rc0 fail build. 8.0 is fine +Description of problem: +Build error with 8.1.0-rc0 and 8.1.0-rc1. +Build of 8.0.3 works correctly, using the same build configuration. +Steps to reproduce: +1. Run configure as below in logs +2.`/var/media/DATA/home-rudi/LibreELEC.tv/build.LibreELEC-Generic.x86_64-12.0-devel/build/qemu-8.1.0-rc1/.x86_64-linux-gnu/pyvenv/bin/python3 -m ensurepip --upgrade --default-pip` +3. +Additional information: +``` +$ s/build qemu:host +CLEAN qemu + * Removing /var/media/DATA/home-rudi/LibreELEC.tv/build.LibreELEC-Generic.x86_64-12.0-devel/build/qemu-8.1.0-rc0 ... + * Removing /var/media/DATA/home-rudi/LibreELEC.tv/build.LibreELEC-Generic.x86_64-12.0-devel/qa_checks/qemu-* ... +UNPACK qemu +BUILD qemu (host) + TOOLCHAIN configure +Executing (host): /var/media/DATA/home-rudi/LibreELEC.tv/build.LibreELEC-Generic.x86_64-12.0-devel/build/qemu-8.1.0-rc1/configure --bindir=/var/media/DATA/home-rudi/LibreELEC.tv/build.LibreELEC-Generic.x86_64-12.0-devel/toolchain/bin --extra-cflags=-I/var/media/DATA/home-rudi/LibreELEC.tv/build.LibreELEC-Generic.x86_64-12.0-devel/toolchain/include --extra-ldflags=-L/var/media/DATA/home-rudi/LibreELEC.tv/build.LibreELEC-Generic.x86_64-12.0-devel/toolchain/lib --libexecdir=/var/media/DATA/home-rudi/LibreELEC.tv/build.LibreELEC-Generic.x86_64-12.0-devel/toolchain/lib --localstatedir=/var/media/DATA/home-rudi/LibreELEC.tv/build.LibreELEC-Generic.x86_64-12.0-devel/toolchain/var --prefix=/var/media/DATA/home-rudi/LibreELEC.tv/build.LibreELEC-Generic.x86_64-12.0-devel/toolchain --sbindir=/var/media/DATA/home-rudi/LibreELEC.tv/build.LibreELEC-Generic.x86_64-12.0-devel/toolchain/sbin --sysconfdir=/var/media/DATA/home-rudi/LibreELEC.tv/build.LibreELEC-Generic.x86_64-12.0-devel/toolchain/etc --enable-tools --enable-malloc=system --disable-attr --disable-auth-pam --disable-install-blobs --disable-capstone --disable-curl --disable-debug-info --disable-debug-mutex --disable-debug-tcg --disable-docs --disable-gcrypt --disable-gnutls --disable-system --disable-user --disable-vnc --disable-werror --disable-xkbcommon --disable-zstd +python determined to be '/var/media/DATA/home-rudi/LibreELEC.tv/build.LibreELEC-Generic.x86_64-12.0-devel/toolchain/bin/python3' +python version: Python 3.11.4 +mkvenv: Creating non-isolated virtual environment at 'pyvenv' +mkvenv subprocess failed: +cmd: ['/var/media/DATA/home-rudi/LibreELEC.tv/build.LibreELEC-Generic.x86_64-12.0-devel/build/qemu-8.1.0-rc1/.x86_64-linux-gnu/pyvenv/bin/python3', '-m', 'ensurepip', '--upgrade', '--default-pip'] +returncode: 1 +========== stdout ========== +Looking in links: /tmp/tmpio395oka +Processing /tmp/tmpio395oka/setuptools-65.5.0-py3-none-any.whl +Processing /tmp/tmpio395oka/pip-23.1.2-py3-none-any.whl +Installing collected packages: setuptools, pip +ERROR: Exception: +Traceback (most recent call last): + File "/tmp/tmpio395oka/pip-23.1.2-py3-none-any.whl/pip/_internal/cli/base_command.py", line 169, in exc_logging_wrapper + status = run_func(*args) + ^^^^^^^^^^^^^^^ + File "/tmp/tmpio395oka/pip-23.1.2-py3-none-any.whl/pip/_internal/cli/req_command.py", line 248, in wrapper + return func(self, options, args) + ^^^^^^^^^^^^^^^^^^^^^^^^^ + File "/tmp/tmpio395oka/pip-23.1.2-py3-none-any.whl/pip/_internal/commands/install.py", line 449, in run + installed = install_given_reqs( + ^^^^^^^^^^^^^^^^^^^ + File "/tmp/tmpio395oka/pip-23.1.2-py3-none-any.whl/pip/_internal/req/__init__.py", line 72, in install_given_reqs + requirement.install( + File "/tmp/tmpio395oka/pip-23.1.2-py3-none-any.whl/pip/_internal/req/req_install.py", line 800, in install + install_wheel( + File "/tmp/tmpio395oka/pip-23.1.2-py3-none-any.whl/pip/_internal/operations/install/wheel.py", line 731, in install_wheel + _install_wheel( + File "/tmp/tmpio395oka/pip-23.1.2-py3-none-any.whl/pip/_internal/operations/install/wheel.py", line 620, in _install_wheel + assert os.path.exists(pyc_path) +AssertionError +Traceback (most recent call last): + File "<frozen runpy>", line 198, in _run_module_as_main + File "<frozen runpy>", line 88, in _run_code + File "/var/media/DATA/home-rudi/LibreELEC.tv/build.LibreELEC-Generic.x86_64-12.0-devel/toolchain/lib/python3.11/ensurepip/__main__.py", line 5, in <module> + sys.exit(ensurepip._main()) + ^^^^^^^^^^^^^^^^^ + File "/var/media/DATA/home-rudi/LibreELEC.tv/build.LibreELEC-Generic.x86_64-12.0-devel/toolchain/lib/python3.11/ensurepip/__init__.py", line 286, in _main + return _bootstrap( + ^^^^^^^^^^^ + File "/var/media/DATA/home-rudi/LibreELEC.tv/build.LibreELEC-Generic.x86_64-12.0-devel/toolchain/lib/python3.11/ensurepip/__init__.py", line 202, in _bootstrap + return _run_pip([*args, *_PACKAGE_NAMES], additional_paths) + ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + File "/var/media/DATA/home-rudi/LibreELEC.tv/build.LibreELEC-Generic.x86_64-12.0-devel/toolchain/lib/python3.11/ensurepip/__init__.py", line 103, in _run_pip + return subprocess.run(cmd, check=True).returncode + ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + File "/var/media/DATA/home-rudi/LibreELEC.tv/build.LibreELEC-Generic.x86_64-12.0-devel/toolchain/lib/python3.11/subprocess.py", line 571, in run + raise CalledProcessError(retcode, process.args, +subprocess.CalledProcessError: Command '['/var/media/DATA/home-rudi/LibreELEC.tv/build.LibreELEC-Generic.x86_64-12.0-devel/build/qemu-8.1.0-rc1/.x86_64-linux-gnu/pyvenv/bin/python3', '-W', 'ignore::DeprecationWarning', '-c', '\nimport runpy\nimport sys\nsys.path = [\'/tmp/tmpio395oka/setuptools-65.5.0-py3-none-any.whl\', \'/tmp/tmpio395oka/pip-23.1.2-py3-none-any.whl\'] + sys.path\nsys.argv[1:] = [\'install\', \'--no-cache-dir\', \'--no-index\', \'--find-links\', \'/tmp/tmpio395oka\', \'--upgrade\', \'setuptools\', \'pip\']\nrunpy.run_module("pip", run_name="__main__", alter_sys=True)\n']' returned non-zero exit status 2. + +============================ + +*** Ouch! *** + +VENV creation subprocess failed. + + + +ERROR: python venv creation failed + +FAILURE: s/build qemu:host during configure_host (default) + +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1794 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1794 new file mode 100644 index 000000000..d1bcbf530 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1794 @@ -0,0 +1,27 @@ +Virtio-GPU doesn't fill Response data for cursor queue +Description of problem: +Implementation of virtio-gpu in Qemu is likely not fill Response header in cursor commands. + +Inside the virtio 1.2 specification, document said: +``` +VIRTIO_GPU_CMD_UPDATE_CURSOR + Update cursor. Request data is struct virtio_gpu_update_cursor. Response type is VIRTIO_GPU_RESP_OK_NODATA. + Full cursor update. Cursor will be loaded from the specified resource_id and will be moved to pos. The driver must + transfer the cursor into the resource beforehand (using control queue commands) and make sure the commands to fill + the resource are actually processed (using fencing). + +VIRTIO_GPU_CMD_MOVE_CURSOR + Move cursor. Request data is struct virtio_gpu_update_cursor. Response type is VIRTIO_GPU_RESP_OK_NODATA. + Move cursor to the place specified in pos. The other fields are not used and will be ignored by the device. +``` +The cursor commands do have a response like control commands. + +But in [hw/display/virtio-gpu.c#L1136](https://gitlab.com/qemu-project/qemu/-/blob/master/hw/display/virtio-gpu.c#L1136), QEMU doesn't care anything about response, just fetching command and execute. + +It this a Implementation compromise or I missing something in the specification? +Steps to reproduce: +1. Write any kernel that using virtio-gpu. +2. Run on qemu. +3. No response on cursor command. +Additional information: +Specification: [virtio-v1.2-cs01.html](https://docs.oasis-open.org/virtio/virtio/v1.2/cs01/virtio-v1.2-cs01.html#x1-3650007) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1796 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1796 new file mode 100644 index 000000000..2b515afb9 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1796 @@ -0,0 +1,16 @@ +qemu-img does not accept backing image file path, only file name +Description of problem: +In `qemu-img create ... -b <backing_image> ... <snapshot_image>`, <backing_image> cannot be a file path, but must be a file name. <backing_image> and <snapshot_image> are forced to be in the same directory for the command to work. +Steps to reproduce: +``` +$ mkdir test +$ qemu-img create -f qcow2 test/a.img 1G +... +$ qemu-img create -f qcow2 -b test/a.img -F qcow2 test/a.img.snap +qemu-img: test/a.img.snap: Could not open 'test/test/a.img': No such file or directory +Could not open backing image. +$ qemu-img create -f qcow2 -b a.img -F qcow2 test/a.img.snap +... +$ ls test +a.img a.img.snap +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1797 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1797 new file mode 100644 index 000000000..ddb1a72cf --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1797 @@ -0,0 +1,3 @@ +RAM-backed snapshotting +Additional information: +And thank you for QEMU! 🙂 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1798 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1798 new file mode 100644 index 000000000..595e846e8 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1798 @@ -0,0 +1 @@ +conversions of malloc/calloc/free to g_malloc/g_new/g_free etc diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1801 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1801 new file mode 100644 index 000000000..baeab1ac8 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1801 @@ -0,0 +1,51 @@ +qemu-system-arm: Linux doesn't boot with UEFI (hangs after printing `EFI stub: Exiting boot services... `.) +Description of problem: +Ubuntu 23.04 (armhf) doesn't boot with UEFI. +It hangs after printing `EFI stub: Exiting boot services... `. +Steps to reproduce: +```console +$ qemu-system-arm -machine virt -m 2048 -nographic -bios /usr/local/share/qemu/edk2-arm-code.fd -hda ubuntu-23.04-server-cloudimg-armhf.img -snapshot +UEFI firmware (version edk2-stable202302-for-qemu built at 17:13:00 on Mar 15 2023) +Error: Image at 000BFD84000 start failed: Not Found +Error: Image at 000BFCEE000 start failed: Unsupported +Error: Image at 000BFC85000 start failed: Not Found +Tpm2SubmitCommand - Tcg2 - Not Found +Tpm2GetCapabilityPcrs fail! +Tpm2SubmitCommand - Tcg2 - Not Found +BdsDxe: loading Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0x2,0x0) +BdsDxe: starting Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0x2,0x0) +EFI stub: Booting Linux Kernel... +EFI stub: Entering in SVC mode with MMU enabled +EFI stub: Using DTB from configuration table +EFI stub: Exiting boot services... +``` +Additional information: +It still boots when vmlinuz and initrd are directly specified: +```console +$ qemu-system-arm -machine virt -m 2048 -nographic -bios /usr/local/share/qemu/edk2-arm-code.fd -hda ubuntu-23.04-server-cloudimg-armhf.img -snapshot -kernel ubuntu-23.04-server-cloudimg-armhf-vmlinuz-lpae -initrd ubuntu-23.04-server-cloudimg-armhf-initrd-generic-lpae -append "root=LABEL=cloudimg-rootfs ro" +UEFI firmware (version edk2-stable202302-for-qemu built at 17:13:00 on Mar 15 2023) +Error: Image at 000BFD84000 start failed: Not Found +Error: Image at 000BFCEE000 start failed: Unsupported +Tpm2SubmitCommand - Tcg2 - Not Found +Tpm2GetCapabilityPcrs fail! +Tpm2SubmitCommand - Tcg2 - Not Found +EFI stub: Booting Linux Kernel... +EFI stub: Entering in SVC mode with MMU enabled +EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path +EFI stub: Using DTB from configuration table +EFI stub: Exiting boot services... +[ 0.000000] Booting Linux on physical CPU 0x0 +[ 0.000000] Linux version 6.2.0-26-generic-lpae (buildd@bos02-arm64-018) (arm-linux-gnueabihf-gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0, GNU ld (GNU + Binutils for Ubuntu) 2.40) #26-Ubuntu SMP Tue Jul 11 10:32:58 UTC 2023 (Ubuntu 6.2.0-26.26-generic-lpae 6.2.13) +[ 0.000000] CPU: ARMv7 Processor [414fc0f0] revision 0 (ARMv7), cr=30c5387d +... +Ubuntu 23.04 ubuntu ttyAMA0 + +ubuntu login: +``` + + +Files: +- https://cloud-images.ubuntu.com/releases/23.04/release-20230729/ubuntu-23.04-server-cloudimg-armhf.img +- https://cloud-images.ubuntu.com/releases/23.04/release-20230729/unpacked/ubuntu-23.04-server-cloudimg-armhf-vmlinuz-lpae +- https://cloud-images.ubuntu.com/releases/23.04/release-20230729/unpacked/ubuntu-23.04-server-cloudimg-armhf-initrd-generic-lpae diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1804 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1804 new file mode 100644 index 000000000..2f222d351 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1804 @@ -0,0 +1,11 @@ +Virtual Machines Do Not Recognize Mouse 5 and 6 +Description of problem: +Trying to click the mouse buttons 5 and 6 to go forwards and backwards in Firefox does not work. It seems that those buttons are not recognized by the virtual machine. Tested with both `libvirt` and `aqemu`. Though `libvirt` testing was done on a Fedora host a few months prior. + +Running Fedora 38 VM in virtualbox does not have this problem, the guest recognizes button 5 and 6, going forwards and backwards in Firefox. +Steps to reproduce: +1. Install aqemu or libvirt on Debian 12 +2. Create a Fedora 38 Guest machine +3. Open Firefox and navigate to a few pages, then try to go backwards and forwards in history using the mouse buttons. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1805 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1805 new file mode 100644 index 000000000..f5849982f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1805 @@ -0,0 +1,66 @@ +build-user-hexagon CI job is not actually testing hexagon +Description of problem: +Look at the output from the `build-user-hexagon` CI job and see what compiler meson reports it is using: + + https://gitlab.com/qemu-project/qemu/-/jobs/4790457871 + +``` +Project name: qemu +Project version: 8.0.91 +C compiler for the host machine: cc -m64 -mcx16 (gcc 10.2.1 "cc (Debian 10.2.1-6) 10.2.1 20210110") +C linker for the host machine: cc -m64 -mcx16 ld.bfd 2.35.2 +Host machine cpu family: x86_64 +Host machine cpu: x86_64 +``` + +What is 'cc' resolving to ? + +``` +$ podman run -it registry.gitlab.com/qemu-project/qemu/qemu/debian-hexagon-cross cc -v | grep Target +Target: x86_64-linux-gnu +``` + +That is a x86_64 target native compiler, not a hexagon target cross compiler. + +The ``tests/docker/dockerfiles/debian-hexagon-cross.docker`` file installs the hexagon toolchain under ``/opt`` and adds the dir to ``$PATH`` with: + +``` +ENV PATH $PATH:${TOOLCHAIN_INSTALL}/${TOOLCHAIN_BASENAME}/x86_64-linux-gnu/bin +``` + +This toolchain just installs a `clang` binary, not ``cc`` + +So when ``configure`` runs it looks for ``cc`` first and finds the naitve x86_64 GCC install from the container, not the clang cross compiler + +It is also not possible to merely set ``CC=clang`` because meson will assume it is a native compiler and crash and burn when unable to run binaries + +``` +# CC=clang ./configure --target-list=x86_64-softmmu +Using './build' as the directory for build output +...snip... +Sphinx not found/usable, disabling docs. +Disabling PIE due to missing toolchain support +The Meson build system +Version: 1.2.0 +Source dir: /qemu +Build dir: /qemu/build +Build type: native build +Project name: qemu +Project version: 8.0.92 + +../meson.build:1:0: ERROR: Executables created by c compiler clang -m64 -mcx16 are not runnable. +``` + +AFAICT, the root problem here is that the hexagon container is not setup in the same way as the other cross compiler containers. + +We need the toolchain binaries to be named after the target triplet - ie not ``clang`` but ``hexagon-unknown-linux-musl-clang`` + +This used to be done but was thrown away when switching to a pre-built toolchain in b9052d36342c947b36447558ed0a0dd3fb3fb8f4 + +Then the container also needs to set the configure args for the cross target + +``` +ENV QEMU_CONFIGURE_OPTS --cross-prefix=hexagon-unknown-linux-musl- +``` + +AFAICT, this was never done, so even before switching to the pre-built toolchain, I think the `build-user-hexagon` CI job was running a native built not hexagon build. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1809 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1809 new file mode 100644 index 000000000..662e939fa --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1809 @@ -0,0 +1,53 @@ +config machine "virt-6.2" with qemu-system-aarch64,it report "mem is not supported by this machine type" +Description of problem: +When i config the machine with virt-6.2 and config the numa for cpu,it report "mem is not supported by this machine type",but with virt-5.0 it work well,the newer version virt not support it? It is bug or require hardware support?Or compile configure is not correctlly? + +when i create vm,get the error report as follow: + +virsh create test.xml +``` +qemu unexpectedly closed the monitor: qemu-system-aarch64: -chardev socket,id=charmonitor,fd=34,server,nowait: warning: short-form boolean option 'server' deprecated +Please use server=on instead +qemu-system-aarch64: -chardev socket,id=charmonitor,fd=34,server,nowait: warning: short-form boolean option 'nowait' deprecated +Please use wait=off instead +configure accelerator virt-6.2 start +machine init start +2023-08-04T02:17:13.984797Z qemu-system-aarch64: -numa node,nodeid=0,cpus=0-3,mem=8192: Parameter -numa node,mem is not supported by this machine type +Use -numa node,memdev instead + +``` + + +I use qmp command "query-machines" get the result as follow: +``` +{ + "hotpluggable-cpus": true, + "name": "virt-6.2", + ** "numa-mem-supported": false,** + "default-cpu-type": "cortex-a15-arm-cpu", + "cpu-max": 512, + "deprecated": false, + "default-ram-id": "mach-virt.ram", + "alias": "virt" + }, +``` + +I add the code "mc->numa_mem_supported = true;" in the api "virt_machine_6_1_options",it can supoort numa,but i don't know whether it is affected. + +``` +DEFINE_VIRT_MACHINE_AS_LATEST(6, 2) + +static void virt_machine_6_1_options(MachineClass *mc) +{ + VirtMachineClass *vmc = VIRT_MACHINE_CLASS(OBJECT_CLASS(mc)); + + virt_machine_6_2_options(mc); + compat_props_add(mc->compat_props, hw_compat_6_1, hw_compat_6_1_len); + mc->smp_props.prefer_sockets = true; + vmc->no_cpu_topology = true; + **mc->numa_mem_supported = true;** + + /* qemu ITS was introduced with 6.2 */ + vmc->no_tcg_its = true; +} +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/181 b/gitlab/issues_text/target_missing/host_missing/accel_missing/181 new file mode 100644 index 000000000..a5b810e64 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/181 @@ -0,0 +1 @@ +qemu crashes when doing iotest on virtio-9p filesystem diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1810 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1810 new file mode 100644 index 000000000..217fc170c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1810 @@ -0,0 +1,191 @@ +heap-buffer-overflow in esp_do_dma() +Description of problem: +Got a heap-buffer-overflow error when fuzzing the device am53c974. +Steps to reproduce: +Minimized reproducer: + +```plaintext +cat << EOF | ./qemu-system-x86_64 -display none -machine accel=qtest, -m 512M -device \ +am53c974,id=scsi -device scsi-hd,drive=disk0 -drive \ +id=disk0,if=none,file=null-co://,format=raw -nodefaults -qtest /dev/null\ + -qtest stdio +outl 0xcf8 0x80001010 +outl 0xcfc 0xc000 +outl 0xcf8 0x80001004 +outw 0xcfc 0x05 +outl 0xc03d 0x03000000 +outl 0xc047 0x065a9d80 +outl 0xc00a 0xc10000 +write 0x65a9d 0x1 0x04 +write 0x65a9e 0x1 0x10 +outl 0xc03d 0x03000000 +outl 0xc00a 0xc10000 +outl 0xc00b 0x0800 +outl 0xc00b 0x00 +outl 0xc00b 0x0800 +outl 0xc00b 0x0800 +outl 0xc00b 0x0800 +outl 0xc00b 0x0400 +outl 0xc00b 0x0800 +outl 0xc00b 0x0800 +outw 0xc00b 0x1000 +outw 0xc00b 0x9000 +EOF +``` +Additional information: +The crash report triggered by the reproducer is: + +```plaintext +[I 0.000000] OPENED +[R +0.022834] outl 0xcf8 0x80001010 +[S +0.022864] OK +OK +[R +0.022874] outl 0xcfc 0xc000 +[S +0.022887] OK +OK +[R +0.022942] outl 0xcf8 0x80001004 +[S +0.022990] OK +OK +[R +0.023028] outw 0xcfc 0x05 +[S +0.023508] OK +OK +[R +0.023518] outl 0xc03d 0x03000000 +[S +0.023527] OK +OK +[R +0.023532] outl 0xc047 0x065a9d80 +[S +0.023537] OK +OK +[R +0.023544] outl 0xc00a 0xc10000 +[S +0.023573] OK +OK +[R +0.023581] write 0x65a9d 0x1 0x04 +[S +0.023891] OK +OK +[R +0.023900] write 0x65a9e 0x1 0x10 +[S +0.023906] OK +OK [R +0.023910] outl 0xc03d 0x03000000 +[S +0.023917] OK +OK +[R +0.023921] outl 0xc00a 0xc10000 +[S +0.023983] OK +OK +[R +0.023581] write 0x65a9d 0x1 0x04 +[S +0.023891] OK +OK +[R +0.023900] write 0x65a9e 0x1 0x10 +[S +0.023906] OK +OK [R +0.023910] outl 0xc03d 0x03000000 +[S +0.023917] OK +OK +[R +0.023921] outl 0xc00a 0xc10000 +[S +0.023983] OK +OK +[R +0.023991] outl 0xc00b 0x0800 +[S +0.023998] OK +OK +[R +0.024002] outl 0xc00b 0x00 +[S +0.024008] OK +OK +[R +0.024014] outl 0xc00b 0x0800 +[S +0.024028] OK +OK +[R +0.024034] outl 0xc00b 0x0800 +[S +0.024040] OK +OK +[R +0.024051] outl 0xc00b 0x0800 +[S +0.024058] OK +OK +[R +0.024065] outl 0xc00b 0x0400 +[S +0.024073] OK +OK +[R +0.024082] outl 0xc00b 0x0800 +[S +0.024089] OK +OK +[R +0.024104] outl 0xc00b 0x0800 +[S +0.024121] OK +OK +[R +0.024133] outw 0xc00b 0x1000 +[S +0.024150] OK +OK +[R +0.024159] outw 0xc00b 0x9000 +================================================================= +==63330==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x62500020c000 at pc 0x5601fffcf1d4 bp 0x7ffe1920dcf0 sp 0x7ffe1920d4b0 +WRITE of size 32736 at 0x62500020c000 thread T0 + #0 0x5601fffcf1d3 in __asan_memcpy ../../llvm-project-15.0.0.src/compiler-rt/lib/asan/asan_interceptors_memintrinsics.cpp:22:3 + #1 0x5602015f506b in flatview_read_continue ../softmmu/physmem.c:2726:13 + #2 0x5602015f5ee3 in flatview_read ../softmmu/physmem.c:2762:12 + #3 0x5602015f5bf7 in address_space_read_full ../softmmu/physmem.c:2775:18 + #4 0x560200943ef0 in dma_memory_rw_relaxed ../include/sysemu/dma.h:87:12 + #5 0x560200943ef0 in dma_memory_rw ../include/sysemu/dma.h:130:12 + #6 0x560200943ef0 in pci_dma_rw ../hw/pci/pci_device.h:233:12 + #7 0x560200943ef0 in esp_pci_dma_memory_rw ../hw/scsi/esp-pci.c:283:5 + #8 0x56020092db7e in esp_do_dma ../hw/scsi/esp.c + #9 0x560200935774 in handle_ti ../hw/scsi/esp.c:912:9 + #10 0x560200932db6 in esp_reg_write ../hw/scsi/esp.c:1083:13 + #11 0x56020094574d in esp_pci_io_write ../hw/scsi/esp-pci.c:214:9 + #12 0x5602015b5f23 in memory_region_write_accessor ../softmmu/memory.c:493:5 + #13 0x5602015b56aa in access_with_adjusted_size ../softmmu/memory.c:569:18 + #14 0x5602015b4a50 in memory_region_dispatch_write ../softmmu/memory.c + #15 0x5602015fefbf in flatview_write_continue ../softmmu/physmem.c:2653:23 + #16 0x5602015f6463 in flatview_write ../softmmu/physmem.c:2695:12 + #17 0x5602015f6177 in address_space_write ../softmmu/physmem.c:2791:18 + #18 0x5602015a7e99 in cpu_outw ../softmmu/ioport.c:75:5 + #19 0x560200d28daa in qtest_process_command ../softmmu/qtest.c:483:13 + #20 0x560200d2795b in qtest_process_inbuf ../softmmu/qtest.c:788:9 + #21 0x560201b581a6 in fd_chr_read ../chardev/char-fd.c:72:9 + #22 0x7f8fce57e04d in g_main_context_dispatch (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x5204d) (BuildId: 5fdb313daf182a33a858ba2cc945211b11d34561) + #23 0x560201dc540f in glib_pollfds_poll ../util/main-loop.c:290:9 + #24 0x560201dc540f in os_host_main_loop_wait ../util/main-loop.c:313:5 + #25 0x560201dc540f in main_loop_wait ../util/main-loop.c:592:11 + #26 0x560200d34f76 in qemu_main_loop ../softmmu/runstate.c:732:9 + #27 0x56020173e835 in qemu_default_main ../softmmu/main.c:37:14 + #28 0x7f8fcd3a5082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16 + #29 0x5601fff2009d in _start ./qemu-system-x86_64+0x1e9109d) + +0x62500020c000 is located 0 bytes to the right of 4096-byte region [0x62500020b000,0x62500020c000) +allocated by thread T0 here: + #0 0x5601fffd0a0c in posix_memalign ../../llvm-project-15.0.0.src/compiler-rt/lib/asan/asan_malloc_linux.cpp:145:3 + #1 0x560201db83da in qemu_try_memalign ../util/memalign.c:53:11 + #2 0x560201db8762 in qemu_memalign ../util/memalign.c:73:15 + #3 0x5602008c779e in scsi_req_enqueue ../hw/scsi/scsi-bus.c:906:10 + #4 0x56020093bd2f in do_command_phase ../hw/scsi/esp.c:296:15 + #5 0x56020093bd2f in do_cmd ../hw/scsi/esp.c:344:5 + #6 0x560200932911 in esp_reg_write ../hw/scsi/esp.c:1112:13 + #7 0x56020094574d in esp_pci_io_write ../hw/scsi/esp-pci.c:214:9 + #8 0x5602015b5f23 in memory_region_write_accessor ../softmmu/memory.c:493:5 + #9 0x5602015b56aa in access_with_adjusted_size ../softmmu/memory.c:569:18 + +SUMMARY: AddressSanitizer: heap-buffer-overflow ./llvm-project-15.0.0.src/compiler-rt/lib/asan/asan_interceptors_memintrinsics.cpp:22:3 in __asan_memcpy +Shadow bytes around the buggy address: + 0x0c4a800397b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 + 0x0c4a800397c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 + 0x0c4a800397d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 + 0x0c4a800397e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 + 0x0c4a800397f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +=>0x0c4a80039800:[fa]fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa + 0x0c4a80039810: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa + 0x0c4a80039820: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa + 0x0c4a80039830: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa + 0x0c4a80039840: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa + 0x0c4a80039850: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa +Shadow byte legend (one shadow byte represents 8 application bytes): + Addressable: 00 + Partially addressable: 01 02 03 04 05 06 07 + Heap left redzone: fa + Freed heap region: fd + Stack left redzone: f1 + Stack mid redzone: f2 + Stack right redzone: f3 + Stack after return: f5 + Stack use after scope: f8 + Global redzone: f9 + Global init order: f6 + Poisoned by user: f7 + Container overflow: fc + Array cookie: ac + Intra object redzone: bb + ASan internal: fe + Left alloca redzone: ca + Right alloca redzone: cb +==63330==ABORTING +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1811 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1811 new file mode 100644 index 000000000..b382c1f57 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1811 @@ -0,0 +1,36 @@ +ppc serial appears to have a maximum ratio of output to input, hides output and only writes it on subsequent input(?!) +Description of problem: +When pasting in large chunks of text, the echo is partial, but completes with subsequent writes (and is drained when the writes are small). Sorry this is really stupid, see video. + +(also, when booting, the console stops at +``` +Building dt strings... +Building dt structure... +Device tree strings 0x00000000062c0000 -> 0x00000000062c0b90 +Device tree struct 0x00000000062d0000 -> 0x00000000062e0000 +Quiescing Open Firmware ... +Booting Linux via __start() @ 0x0000000002000000 ... +Linux ppc64le +#1 SMP Debian 6. +``` +and then continues with more messages from just after the dot: +``` +Linux ppc64le +#1 SMP Debian 6.[ 15.683156] vio vio: uevent: failed to send synthetic uevent: -19 +vio: Failed to write 'add' to '/sys/devices/vio/uevent', ignoring: No such device +/dev/vda2: clean, 17371/987360 files, 345018/3942144 blocks +``` +) +Steps to reproduce: +1. `cat > /dev/null` +2. paste in a couple solid lines +3. observe that the echo completed mid-line +4. paste in a couple more solid lines +5. observe that the echo includes the end of the first few lines, and the start of the second set +6. ^D +7. observe that with every key input into the shell, you get a few bytes back, and those bytes are the tail-end of the second set of lines +8. when the echo buffer is drained, it's drained +Additional information: +Demo video: https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=1041707;filename=2023-07-21+17-59-25.mp4;msg=5 + +Downstream bug: https://bugs.debian.org/1041707 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1813 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1813 new file mode 100644 index 000000000..a143de340 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1813 @@ -0,0 +1,112 @@ +FPE division by zero in scsi_disk_reset() [CVE-2023-42467] +Description of problem: +Got an FPE division by zero error when fuzzing the device am53c974. +Steps to reproduce: +Minimized reproducer for the error: + +```plaintext +cat << EOF | ./qemu-system-x86_64 -display none -machine accel=qtest, -m 512M -device \ +am53c974,id=scsi -device scsi-hd,drive=disk0 -drive \ +id=disk0,if=none,file=null-co://,format=raw -nodefaults -qtest /dev/null\ + -qtest stdio +outl 0xcf8 0x80001010 +outl 0xcfc 0xc000 +outl 0xcf8 0x80001004 +outw 0xcfc 0x05 +outl 0xc047 0x065a9d01 +write 0x65a9d 0x1 0x15 +write 0x65a9e 0x1 0x10 +write 0x65aa0 0x1 0x08 +write 0x65aa1 0x1 0x0c +write 0x65aa7 0x1 0x01 +outl 0xc03d 0x03000000 +outl 0xc00a 0xc10000 +outl 0xc03d 0x03000000 +outl 0xc00a 0xc10000 +outl 0xc00b 0x9000 +outl 0xc00b 0x0300 +EOF +``` +Additional information: +The crash report triggered by the reproducer is: + +```plaintext +[I 0.000000] OPENED +[R +0.024387] outl 0xcf8 0x80001010 +[S +0.024420] OK +OK +[R +0.024470] outl 0xcfc 0xc000 +[S +0.024490] OK +OK +[R +0.024513] outl 0xcf8 0x80001004 +[S +0.024521] OK +OK +[R +0.024527] outw 0xcfc 0x05 +[S +0.022723] OK +OK +[R +0.022734] outl 0xc047 0x065a9d01 +[S +0.022742] OK +OK +[R +0.022747] write 0x65a9d 0x1 0x15 +[S +0.022932] OK +OK +[R +0.022941] write 0x65a9e 0x1 0x10 +[S +0.022947] OK +OK +[R +0.022952] write 0x65aa0 0x1 0x08 +[S +0.022958] OK +OK +[R +0.022965] write 0x65aa1 0x1 0x0c +[S +0.022973] OK +OK +[R +0.022983] write 0x65aa7 0x1 0x01 +[S +0.022991] OK +OK +[R +0.023004] outl 0xc03d 0x03000000 +[S +0.023014] OK +OK +[R +0.023021] outl 0xc00a 0xc10000 +[S +0.023048] OK +OK +[R +0.023056] outl 0xc03d 0x03000000 +[S +0.023065] OK +OK +[R +0.023072] outl 0xc00a 0xc10000 +[S +0.023128] OK +OK +[R +0.023141] outl 0xc00b 0x9000 +[S +0.023159] OK +OK +[R +0.023166] outl 0xc00b 0x0300 +../hw/scsi/scsi-disk.c:2351:16: runtime error: division by zero +SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior ../hw/scsi/scsi-disk.c:2351:16 in +AddressSanitizer:DEADLYSIGNAL +================================================================= +==1208622==ERROR: AddressSanitizer: FPE on unknown address 0x558e9c0a9386 (pc 0x558e9c0a9386 bp 0x7ffcc04aaf50 sp 0x7ffcc04aaec0 T0) + #0 0x558e9c0a9386 in scsi_disk_reset ../hw/scsi/scsi-disk.c:2351:16 + #1 0x558e9cf23f23 in resettable_phase_hold ../hw/core/resettable.c + #2 0x558e9cf0a861 in bus_reset_child_foreach ../hw/core/bus.c:97:13 + #3 0x558e9cf23c05 in resettable_phase_hold ../hw/core/resettable.c:173:5 + #4 0x558e9cf21b69 in resettable_assert_reset ../hw/core/resettable.c:60:5 + #5 0x558e9cf217aa in resettable_reset ../hw/core/resettable.c:45:5 + #6 0x558e9c0facd7 in esp_reg_write ../hw/scsi/esp.c:1075:13 + #7 0x558e9c10d74d in esp_pci_io_write ../hw/scsi/esp-pci.c:214:9 + #8 0x558e9cd7df23 in memory_region_write_accessor ../softmmu/memory.c:493:5 + #9 0x558e9cd7d6aa in access_with_adjusted_size ../softmmu/memory.c:569:18 + #10 0x558e9cd7ca50 in memory_region_dispatch_write ../softmmu/memory.c + #11 0x558e9cdc6fbf in flatview_write_continue ../softmmu/physmem.c:2653:23 + #12 0x558e9cdbe463 in flatview_write ../softmmu/physmem.c:2695:12 + #13 0x558e9cdbe177 in address_space_write ../softmmu/physmem.c:2791:18 + #14 0x558e9cd70208 in cpu_outl ../softmmu/ioport.c:85:5 + #15 0x558e9c4f0e76 in qtest_process_command ../softmmu/qtest.c:485:13 + #16 0x558e9c4ef95b in qtest_process_inbuf ../softmmu/qtest.c:788:9 + #17 0x558e9d3201a6 in fd_chr_read ../chardev/char-fd.c:72:9 + #18 0x7f974a7c904d in g_main_context_dispatch (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x5204d) (BuildId: 5fdb313daf182a33a858ba2cc945211b11d34561) + #19 0x558e9d58d40f in glib_pollfds_poll ../util/main-loop.c:290:9 + #20 0x558e9d58d40f in os_host_main_loop_wait ../util/main-loop.c:313:5 + #21 0x558e9d58d40f in main_loop_wait ../util/main-loop.c:592:11 + #22 0x558e9c4fcf76 in qemu_main_loop ../softmmu/runstate.c:732:9 + #23 0x558e9cf06835 in qemu_default_main ../softmmu/main.c:37:14 + #24 0x7f97495f0082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16 + #25 0x558e9b6e809d in _start (./qemu-system-x86_64+0x1e9109d) +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1814 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1814 new file mode 100644 index 000000000..a339b69ca --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1814 @@ -0,0 +1,16 @@ +`-M none` breaks on ARM64 platforms with max IPA size < 40 +Description of problem: +QEMU fails to initialize the KVM type properly when `-M none` is used. On ARM64, the KVM type sets the IPA size. Without that setting, the kernel defaults to 40 bits. This fails on machines which cannot support that IPA size, such as Apple M1 machines. + +This presumably happens because `virt_machine_class_init()` in `hw/arm/virt.c` never gets called in that case, which means it doesn't initialize `mc->kvm_type` to the correct callback to do the IPA check. + +Since the max IPA size is a property of the host CPU and must be queried properly for things to work at all, this logic should be invoked unconditionally for all machines, even `none`. + +This is breaking libvirt on Apple M1/M2 systems, since it uses `-M none,accel=kvm` for its KVM test, and when it fails it considers KVM support unavailable. See: https://gitlab.com/libvirt/libvirt/-/issues/365 +Steps to reproduce: +On any ARM64 machine: + +1. strace -e ioctl qemu-system-aarch64 -M none,accel=kvm 2>&1 | grep -C1 CREATE_VM +2. strace -e ioctl qemu-system-aarch64 -M virt,accel=kvm 2>&1 | grep -C1 CREATE_VM + +Observe that the first command line does not issue a `KVM_CAP_ARM_VM_IPA_SIZE` and does not set the machine type argument to `KVM_CREATE_VM`, while the second one does. On machines with <40 bit max IPA, the first invocation would fail to initialize KVM. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1815 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1815 new file mode 100644 index 000000000..f98054c2f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1815 @@ -0,0 +1,82 @@ +Null pointer access in nvme_directive_receive() +Description of problem: +Got an access within null pointer error when fuzzing nvme. +Steps to reproduce: +Minimized reproducer for the error: + +```plaintext +cat << EOF | ./qemu-system-x86_64 -display none -machine accel=qtest, -m 512M -machine q35 \ +-nodefaults -drive file=null-co://,if=none,format=raw,id=disk0 -device \ +nvme,drive=disk0,serial=1 -qtest /dev/null -qtest stdio +outl 0xcf8 0x80000810 +outl 0xcfc 0xe0000000 +outl 0xcf8 0x80000804 +outw 0xcfc 0x06 +write 0xe0000024 0x4 0x040002 +write 0xe0000014 0x4 0x61004600 +write 0xe0001000 0x1 0x04 +write 0x0 0x1 0x1a +write 0x4 0x1 0x01 +write 0x2c 0x1 0x01 +EOF +``` +Additional information: +The crash report triggered by the reproducer is: + +```plaintext +[I 0.000000] OPENED +[R +0.025407] outl 0xcf8 0x80000810 +[S +0.025443] OK +OK +[R +0.025456] outl 0xcfc 0xe0000000 +[S +0.025470] OK +OK +[R +0.025476] outl 0xcf8 0x80000804 +[S +0.025483] OK +OK +[R +0.025489] outw 0xcfc 0x06 +[S +0.025934] OK +OK +[R +0.025946] write 0xe0000024 0x4 0x040002 +[S +0.025958] OK +OK +[R +0.025964] write 0xe0000014 0x4 0x61004600 +[S +0.025988] OK +OK +[R +0.026025] write 0xe0001000 0x1 0x04 +[S +0.026041] OK +OK +[R +0.026048] write 0x0 0x1 0x1a +[S +0.026256] OK +OK +[R +0.026268] write 0x4 0x1 0x01 +[S +0.026279] OK +OK +[R +0.026292] write 0x2c 0x1 0x01 +[S +0.026303] OK +OK +../hw/nvme/ctrl.c:6890:29: runtime error: member access within null pointer of type 'NvmeEnduranceGroup' (aka 'struct NvmeEnduranceGroup') +SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior ../hw/nvme/ctrl.c:6890:29 in +AddressSanitizer:DEADLYSIGNAL +================================================================= +==1085476==ERROR: AddressSanitizer: SEGV on unknown address 0x000000001fc8 (pc 0x56306b765ebf bp 0x7ffff17fd890 sp 0x7ffff17f6a00 T0) +==1085476==The signal is caused by a READ memory access. + #0 0x56306b765ebf in nvme_directive_receive ../hw/nvme/ctrl.c:6890:33 + #1 0x56306b765ebf in nvme_admin_cmd ../hw/nvme/ctrl.c:6958:16 + #2 0x56306b765ebf in nvme_process_sq ../hw/nvme/ctrl.c:7015:13 + #3 0x56306cda2c3b in aio_bh_call ../util/async.c:169:5 + #4 0x56306cda3384 in aio_bh_poll ../util/async.c:216:13 + #5 0x56306cd3f15b in aio_dispatch ../util/aio-posix.c:423:5 + #6 0x56306cda72da in aio_ctx_dispatch ../util/async.c:358:5 + #7 0x7fa321cc417c in g_main_context_dispatch (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x5217c) (BuildId: 5fdb313daf182a33a858ba2cc945211b11d34561) + #8 0x56306cda840f in glib_pollfds_poll ../util/main-loop.c:290:9 + #9 0x56306cda840f in os_host_main_loop_wait ../util/main-loop.c:313:5 + #10 0x56306cda840f in main_loop_wait ../util/main-loop.c:592:11 + #11 0x56306bd17f76 in qemu_main_loop ../softmmu/runstate.c:732:9 + #12 0x56306c721835 in qemu_default_main ../softmmu/main.c:37:14 + #13 0x7fa320aeb082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16 + #14 0x56306af0309d in _start (./qemu-system-x86_64+0x1e9109d) + +AddressSanitizer can not provide additional info. +SUMMARY: AddressSanitizer: SEGV ../hw/nvme/ctrl.c:6890:33 in nvme_directive_receive +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1816 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1816 new file mode 100644 index 000000000..ed8f494f6 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1816 @@ -0,0 +1,74 @@ +Memory size limitation under podman on Apple silicon +Description of problem: +We are using latest MacOS (Ventura) on M2 Ultra with 128Gb RAM (Mac Studio) to run our product Linux aarch64 builds in podman containers. This is cheaper than buying ARM server hardware, and we are not able to use cloud services. + +The issue arises when we try to use the available RAM for the underlying QEMU machine. There seems to be a memory limit which looks like it is in QEMU not podman machine, since that is more of a wrapper in this process. + +The use case is to init a Fedora Linux VM by QEMU which provides a Linux kernel. That kernel is then used to run podman containers. + +When we set the memory limit to 64513Mb the podman machine (VM) start fails with "Error: HV_BAD_ARGUMENT". If we reduce the memory limit to "64512" it works as expected. + +This is an example of how to reproduce: + +` +macstudio:~ build $ podman machine init --cpus="18" --memory="64513" podman-machine-default +Extracting compressed file +Image resized. +Machine init complete +To start your machine run: + +podman machine start + +macstudio:~ build $ podman machine start +Starting machine "podman-machine-default" +Waiting for VM ... +Error: qemu exited unexpectedly with exit code -1, stderr: qemu-system-aarch64: Error: HV_BAD_ARGUMENT + +macstudio:~ build $ podman machine rm --force +macstudio:~ build $ podman machine init --cpus="18" --memory="64512" podman-machine-default +Extracting compressed file +Image resized. +Machine init complete +To start your machine run: + +podman machine start + +macstudio:~ build $ podman machine start +Starting machine "podman-machine-default" +Waiting for VM ... +Mounting volume... /Users:/Users +Mounting volume... /private:/private +Mounting volume... /var/folders:/var/folders + +This machine is currently configured in rootless mode. If your containers +require root permissions (e.g. ports < 1024), or if you run into compatibility +issues with non-podman clients, you can switch using the following command: + +podman machine set --rootful + +API forwarding listening on: /Users/build_ci/.local/share/containers/podman/machine/qemu/podman.sock + +The system helper service is not installed; the default Docker API socket +address can't be used by podman. If you would like to install it run the +following commands: + +sudo /opt/homebrew/Cellar/podman/4.6.0/bin/podman-mac-helper install +podman machine stop; podman machine start + +You can still connect Docker API clients by setting DOCKER_HOST using the +following command in your terminal session: + +export DOCKER_HOST='unix:///Users/build/.local/share/containers/podman/machine/qemu/podman.sock' + +Machine "podman-machine-default" started successfully +macstudio:~ build $ podman machine ls +NAME VM TYPE CREATED LAST UP CPUS MEMORY DISK SIZE +podman-machine-default* qemu About a minute ago Currently running 18 63GiB 100GiB + +` +Steps to reproduce: +1. Initialise the VM with a RAM limit of 64513Mb, then start it. +2. +3. +Additional information: +Feel free to ask for more information. Unfortunately, these machines are our production platform, so further testing will not have a rapid turn around. We are open to taking a machine out of production for testing, it just needs scheduling. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1817 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1817 new file mode 100644 index 000000000..5aae4b244 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1817 @@ -0,0 +1 @@ +meson complains about use of install_subdir in docs/meson.build diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1818 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1818 new file mode 100644 index 000000000..0d16ae07a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1818 @@ -0,0 +1,20 @@ +whpx does not work with hyper-v enabled +Description of problem: +I am experiencing issues with the WHPX (Windows Hypervisor Platform Accelerator) hardware acceleration in QEMU on my Windows 10 22h2 system. When I run QEMU with the `-accel whpx` option, I encounter the following problems: + +2. I receive the error message "WHPX: No accelerator found, hr=00000000" followed by "failed to initialize whpx: No space left on device." +Steps to reproduce: +1. Enable the Hyper-V feature on Windows. +2. Install the latest QEMU version +3. Run the QEMU command with the `-accel whpx` option. +Additional information: +- my cpu : intel i7 6500U +- ram : 8 gigabytes +- gpu : intel hd 520 +- drive : C: -> 200 gigabytes, D: -> 1to (c: 109 used, d: 732 used) +- emulated drive -> 50 gigabytes (500mb used) + + + + +(in french sorry) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/182 b/gitlab/issues_text/target_missing/host_missing/accel_missing/182 new file mode 100644 index 000000000..dbac4e03c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/182 @@ -0,0 +1 @@ +qemu-xhci device should detect if libusb host supports streams diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1821 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1821 new file mode 100644 index 000000000..390c2a9bd --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1821 @@ -0,0 +1,53 @@ +snapshot-save very slow in 8.1-rc2 +Description of problem: +Before commit 813cd61669 ("migration: Use migration_transferred_bytes() to calculate rate_limit") the above script will take about 1.5 seconds to execute, after the commit, 1 minute 30 seconds. More RAM makes it take longer still. +Steps to reproduce: +1. Execute the script given as the command line above. +Additional information: +Creating the issue here, so it doesn't get lost and is documented. + +The following series by @juan.quintela would've avoided the regression, but seems like it never landed: https://lists.nongnu.org/archive/html/qemu-devel/2023-05/msg07971.html + +Logs: + +Before commit 813cd61669 +``` +root@pve8a1 /home/febner/repos/qemu/build # time ~/save-snap.sh +Formatting '/tmp/test.qcow2', fmt=qcow2 cluster_size=65536 extended_l2=off compression_type=zlib size=1073741824 lazy_refcounts=off refcount_bits=16 +{"QMP": {"version": {"qemu": {"micro": 50, "minor": 0, "major": 8}, "package": "v8.0.0-967-g3db9c05a90-dirty"}, "capabilities": ["oob"]}} +VNC server running on ::1:5900 +{"return": {}} +{"timestamp": {"seconds": 1691572701, "microseconds": 708660}, "event": "JOB_STATUS_CHANGE", "data": {"status": "created", "id": "save0"}} +{"timestamp": {"seconds": 1691572701, "microseconds": 708731}, "event": "JOB_STATUS_CHANGE", "data": {"status": "running", "id": "save0"}} +{"return": {}} +{"timestamp": {"seconds": 1691572701, "microseconds": 709239}, "event": "STOP"} +{"timestamp": {"seconds": 1691572702, "microseconds": 939059}, "event": "RESUME"} +{"timestamp": {"seconds": 1691572702, "microseconds": 939565}, "event": "JOB_STATUS_CHANGE", "data": {"status": "waiting", "id": "save0"}} +{"timestamp": {"seconds": 1691572702, "microseconds": 939605}, "event": "JOB_STATUS_CHANGE", "data": {"status": "pending", "id": "save0"}} +{"timestamp": {"seconds": 1691572702, "microseconds": 939638}, "event": "JOB_STATUS_CHANGE", "data": {"status": "concluded", "id": "save0"}} +{"return": {}} +{"timestamp": {"seconds": 1691572702, "microseconds": 939730}, "event": "SHUTDOWN", "data": {"guest": false, "reason": "host-qmp-quit"}} +{"timestamp": {"seconds": 1691572702, "microseconds": 941746}, "event": "JOB_STATUS_CHANGE", "data": {"status": "null", "id": "save0"}} +~/save-snap.sh 1.18s user 0.09s system 85% cpu 1.476 total +``` + +After commit 813cd61669 +``` +root@pve8a1 /home/febner/repos/qemu/build # time ~/save-snap.sh +Formatting '/tmp/test.qcow2', fmt=qcow2 cluster_size=65536 extended_l2=off compression_type=zlib size=1073741824 lazy_refcounts=off refcount_bits=16 +{"QMP": {"version": {"qemu": {"micro": 92, "minor": 0, "major": 8}, "package": "v8.1.0-rc2-102-ga8fc5165aa"}, "capabilities": ["oob"]}} +VNC server running on ::1:5900 +{"return": {}} +{"timestamp": {"seconds": 1691572864, "microseconds": 944026}, "event": "JOB_STATUS_CHANGE", "data": {"status": "created", "id": "save0"}} +{"timestamp": {"seconds": 1691572864, "microseconds": 944115}, "event": "JOB_STATUS_CHANGE", "data": {"status": "running", "id": "save0"}} +{"return": {}} +{"timestamp": {"seconds": 1691572864, "microseconds": 944631}, "event": "STOP"} +{"timestamp": {"seconds": 1691572954, "microseconds": 697523}, "event": "RESUME"} +{"timestamp": {"seconds": 1691572954, "microseconds": 697962}, "event": "JOB_STATUS_CHANGE", "data": {"status": "waiting", "id": "save0"}} +{"timestamp": {"seconds": 1691572954, "microseconds": 697996}, "event": "JOB_STATUS_CHANGE", "data": {"status": "pending", "id": "save0"}} +{"timestamp": {"seconds": 1691572954, "microseconds": 698020}, "event": "JOB_STATUS_CHANGE", "data": {"status": "concluded", "id": "save0"}} +{"return": {}} +{"timestamp": {"seconds": 1691572954, "microseconds": 698089}, "event": "SHUTDOWN", "data": {"guest": false, "reason": "host-qmp-quit"}} +{"timestamp": {"seconds": 1691572954, "microseconds": 701263}, "event": "JOB_STATUS_CHANGE", "data": {"status": "null", "id": "save0"}} +~/save-snap.sh 31.81s user 41.69s system 81% cpu 1:30.03 total +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1822 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1822 new file mode 100644 index 000000000..210039cf9 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1822 @@ -0,0 +1,7 @@ +Signed source tarball for 8.0.4 missing +Description of problem: +Hi! I package this project for Arch Linux. I would like to upgrade to 8.0.4, but unfortunately there is no signed source tarball for that version available yet. +Steps to reproduce: +1. Go to https://download.qemu.org/ and find no source tarball for 8.0.4 +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1824 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1824 new file mode 100644 index 000000000..85e4c34c4 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1824 @@ -0,0 +1 @@ +[8.x] qemu-user does not build under CentOS 7 any longer diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1827 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1827 new file mode 100644 index 000000000..56b9af7e4 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1827 @@ -0,0 +1 @@ +Turn DPRINTF macro use into tracepoints diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1828 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1828 new file mode 100644 index 000000000..9e5995e81 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1828 @@ -0,0 +1,21 @@ +[v8.0.4 regression] `qemu-system-x86_64: -accel hvf: Unknown Error` +Description of problem: +`-accel hvf` crashes with "Unknown Error". +Regression in v8.0.4. + +The master branch doesn't seem affected. +Steps to reproduce: +v8.0.3: +```console +$ qemu-system-x86_64 -accel hvf +(shows iPXE screen, as expected) +``` + +v8.0.4: +```console +$ qemu-system-x86_64 -accel hvf +qemu-system-x86_64: -accel hvf: Unknown Error +Abort trap: 6 +``` +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1829 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1829 new file mode 100644 index 000000000..eacdc2a30 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1829 @@ -0,0 +1,88 @@ +DoS via assert failure by guest user +Description of problem: +As root in guest VM user can execute special script, which crashes the whole VM with error + +```plaintext +hw/display/qxl.c:1594 inside of function void qxl_set_mode(PCIQXLDevice *, unsigned int, int): Assertion `qxl_add_memslot(d, 0, devmem, QXL_SYNC) == 0` failed +``` +Steps to reproduce: +1. This bug can be reproduced with: + + ```bash + cat << EOF | ./build/qemu-system-x86_64 -vga qxl -m 2048 -nodefaults -qtest stdio + outl 0xcf8 0x8000101c + outl 0xcfc 0xc000 + outl 0xcf8 0x80001001 + outl 0xcfc 0x01000000 + outl 0xc006 0x00 + EOF + ``` +2. Also, we can execute this python3 script inside guest VM as root (to invoke VM use command: **_qemu-system-x86_64 -vga qxl -hda debian.img -m 2048 -nodefaults_**): + + ```python + import os + f = os.open("/dev/port", os.O_RDWR|os.O_NDELAY) + l = os.lseek(f, 0xcf8, 0) + os.write(f, b'\x80\x00\x10\x1c') + l = os.lseek(f, 0xcfc, 0) + os.write(f, b'\xc0\x00') + l = os.lseek(f, 0xcf8, 0) + os.write(f, b'\x80\x00\x10\x01') + l = os.lseek(f, 0xcfc, 0) + os.write(f, b'\x01\x00\x00\x00') + l = os.lseek(f, 0xc006, 0) + os.write(f, b'\x00') + ``` + + This script causes VM to crash. + + [PoC_qxl-vga_crash.mkv](/uploads/7ee262c20dca69aa9417812f6a93a532/PoC_qxl-vga_crash.mkv) +Additional information: +This issue was found by fuzzing. Here is an auto-generated C source code for a test case that will reproduce the bug. + +```plaintext +/* + * Autogenerated Fuzzer Test Case + * + * Copyright (c) 2023 Artem Nasonov <anasonov@astralinux.ru> + * + * This work is licensed under the terms of the GNU GPL, version 2 or later. + * See the COPYING file in the top-level directory. + */ + +#include "qemu/osdep.h" + +#include "libqtest.h" + +/* + * cat << EOF | qemu-system-x86_64 -vga qxl -hda \ + * ~/Downloads/virtualdebian.img -m 2048 -nodefaults -qtest stdio + * outl 0xcf8 0x8000101c + * outl 0xcfc 0xc000 + * outl 0xcf8 0x80001001 + * outl 0xcfc 0x01000000 + * outl 0xc006 0x00 + * EOF +*/ +static void test_qxl_set_mode(void) +{ +QTestState *s = qtest_init("-vga qxl -m 2048 -nodefaults"); +qtest_outl(s, 0xcf8, 0x8000101c); +qtest_outl(s, 0xcfc, 0xc000); +qtest_outl(s, 0xcf8, 0x80001001); +qtest_outl(s, 0xcfc, 0x01000000); +qtest_outl(s, 0xc006, 0x00); +qtest_quit(s); +}int main(int argc, char **argv) +{ + const char *arch = qtest_get_arch(); + + g_test_init(&argc, &argv, NULL); + + if (strcmp(arch, "x86_64") == 0) { + qtest_add_func("fuzz/test_qxl_set_mode",test_qxl_set_mode); + } + + return g_test_run(); +} +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/183 b/gitlab/issues_text/target_missing/host_missing/accel_missing/183 new file mode 100644 index 000000000..6ffb0b23e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/183 @@ -0,0 +1 @@ +Cannot use usb-host on Mac OS diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1830 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1830 new file mode 100644 index 000000000..24472b67e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1830 @@ -0,0 +1,26 @@ +command hangs in CentOS 7 arm64 container with Ubuntu 22 amd64 host +Description of problem: +The command hangs in the container, taking over the CPU: + +``` +$ docker run -it centos:7 +[root@42e655bf3d60 /]# LD_DEBUG=all /lib64/ld-2.17.so --list /usr/bin/true & +[1] 74 +[root@42e655bf3d60 /]# 74: file=/usr/bin/true [0]; generating link map + +[root@42e655bf3d60 /]# ps -e -o pid,ppid,etime,time,state,args + PID PPID ELAPSED TIME S COMMAND + 1 0 34:59 00:00:00 S /usr/libexec/qemu-binfmt/aarch64-binfmt-P /bin/bash /bin/bash + 74 1 03:16 00:03:13 R /usr/libexec/qemu-binfmt/aarch64-binfmt-P /lib64/ld-2.17.so /lib64/ld-2.17.so + 80 1 4-19:34:01 00:00:00 R ps -e -o pid,ppid,etime,time,state,args +[root@42e655bf3d60 /]# +``` +Steps to reproduce: +1. Start container +2. Run `/lib64/ld-2.17.so --list /usr/bin/true` +Additional information: +1. The problem is not observed in an Ubuntu 20.04 host system performing the same scenario. +2. My team build environment has amd64 native architecture hardware. I ran a similar scenario on an AWS arm64 native machine (QEMU is not needed) and the command works fine in the container. +3. My team builds several Linux images daily - about a dozen amd64 and eight arm64. This is the only image that's causing us this problem. +4. I built trace-cmd but when I tried to start a trace it told me `No events enabled with kvm`. +5. I built qemu-8.1.0-rc3 and saw the same behavior but I don't think `/usr/libexec/qemu-binfmt/aarch64-binfmt-P` was replaced with a new version so I don't think the old version was used for my container. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1835 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1835 new file mode 100644 index 000000000..abdea2dbf --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1835 @@ -0,0 +1,18 @@ +IPv4 guest/outbound port forwarding not working +Description of problem: +Python http server running on the host can receive the first http request from guest and provides correct response, but the resent request gets stuck. Package couldn't be seen in `tcpdump` running on host. +Steps to reproduce: +1. Build libslirp, I am using HEAD @ master. +1. Build your QEMU with user network enabled to use slirp (`./configure -target-list=x86_64-softmmu --enable-slirp`). +1. Ran a Python server on host listening to port `6655` (`python3 -m http.server --bind :: 6655`). +1. Boot your QEMU with aforementioned QEMU command line, I am forwarding a server address to host's local address `guestfwd=tcp:10.0.2.100:6657-tcp:127.0.0.1:6655`. For image, I am using a ordinary Fedora 38 workstation live cdrom. +1. In your guest OS (emulated enviroment), open a terminal and run `curl http://10.0.2.100:6657`, this sends a http get to the +slirp outbound forwarding server. You should see the Python http server gets the request and provides correct response `::ffff:127.0.0.1 - - [17/Aug/2023 18:24:34] "GET / HTTP/1.1" 200 -`, nothing but just `ls` the directory. +5. Repeat step 4, you will see the `curl` command gets stuck. +Additional information: +I've added a .pacp capturing line in QEMU command line and investigated it via Wireshark, noticed the slirp gets the http get, but after that being stuck in some place, I saw the guest sending keep alive request to slirp, so I think this could be something in the QEMU side. + + + + + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1837 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1837 new file mode 100644 index 000000000..7a6a2ca67 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1837 @@ -0,0 +1,35 @@ +Support IP_MULTICAST_IF socket option in linux-user +Additional information: +I've run into this limitation in qemu-aarch64-static version Debian 1:6.2+dfsg-2ubuntu6.12, but from the link above, it doesn't seem to be implemented on master yet. + +Here's some source code that demonstrates the failure: +``` +#include <sys/socket.h> +#include <arpa/inet.h> +#include <netinet/ip.h> +#include <unistd.h> +#include <assert.h> +#include <stdio.h> + +int main() +{ + int fd, ret; + struct in_addr addr = {htonl(INADDR_LOOPBACK)}; + + fd = socket(AF_INET, SOCK_DGRAM, IPPROTO_UDP); + assert(fd >= 0); + ret = setsockopt(fd, IPPROTO_IP, IP_MULTICAST_IF, &addr, sizeof(addr)); + if (ret < 0) + { + perror("setsockopt failed"); + return 1; + } + close(fd); + printf("Success!\n"); + return 0; +} +``` + +When run under qemu, it gives the error `setsockopt failed: Protocol not available`. + +It doesn't look like it should be too hard to support (certainly no worse than IP_ADD_MEMBERSHIP). Let me know if I can help with a patch. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1838 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1838 new file mode 100644 index 000000000..dbb24a804 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1838 @@ -0,0 +1 @@ +Win9x on qemu 8.0.3 - Impossible to launch a win32 app diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1839 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1839 new file mode 100644 index 000000000..7bdea7c60 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1839 @@ -0,0 +1,41 @@ +command line option (fw_cfg) not being treated as opaque and generates error "short-form boolean option 'x' deprecated" +Description of problem: +I'm trying to run qemu with `fw_cfg` arguments. With a full example I am trying to provide an ignition configuration a flatcar VM using a 'string' parameter which is JSON (rather than a file parameter). + +Running qemu with command line options where the fields have arbitrary data that should be opaque to qemu are being interpreted and cause the command line argument parsing the fail. I have tried putting quotes and double quotes around various parts of the command without success. + + +Sorry, but I haven't tested this with latest (v8.1.0.rc4 / v8.0.4) + +Examples: + +```# qemu-system-x86_64 -fw_cfg name=z,string=a,b +qemu-system-x86_64: -fw_cfg name=z,string=a,b: warning: short-form boolean option 'b' deprecated +Please use b=on instead +qemu-system-x86_64: -fw_cfg name=z,string=a,b: Invalid parameter 'b' +``` + +Single quotes around the `string` value: +``` +# qemu-system-x86_64 -fw_cfg name=z,string='a,b' +qemu-system-x86_64: -fw_cfg name=z,string=a,b: warning: short-form boolean option 'b' deprecated +Please use b=on instead +qemu-system-x86_64: -fw_cfg name=z,string=a,b: Invalid parameter 'b' +``` + +Double quotes around the `string` value +``` +# qemu-system-x86_64 -fw_cfg name=z,string="a,b" +qemu-system-x86_64: -fw_cfg name=z,string=a,b: warning: short-form boolean option 'b' deprecated +Please use b=on instead +qemu-system-x86_64: -fw_cfg name=z,string=a,b: Invalid parameter 'b' + +``` + +Double quotes around the whole `fw_cfg` option value: +``` +# qemu-system-x86_64 -fw_cfg "name=z,string=a,b" +qemu-system-x86_64: -fw_cfg name=z,string=a,b: warning: short-form boolean option 'b' deprecated +Please use b=on instead +qemu-system-x86_64: -fw_cfg name=z,string=a,b: Invalid parameter 'b' +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1840 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1840 new file mode 100644 index 000000000..0c0d4d776 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1840 @@ -0,0 +1 @@ +Amend RISCV machine default value diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1841 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1841 new file mode 100644 index 000000000..c18cb8e00 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1841 @@ -0,0 +1,12 @@ +qemu version with 7.2.5 or earlier than 7.2.5 with nvme disk has I/O QID 22 timeout, Aborting errors +Description of problem: +When I use the 7.2.5 version of qemu or versions earlier than 7.2.5 to compile and start the virtual machine, the machine has an nvme disk which is SAMSUNG MZQL23T8HCLS-00B7C and passed through by VFIO. When i use fio to perform pressure test on the nvme disk in vm, dmesg shows message like this nvme nvme0: I/O QID 22 timeout, Aborting, the picture below shows its details. Howerver, when i use 8.0.0 version of qemu to compile and start vm, and using fio to perform pressure test on the nvme disk in vm, it does not have the problem like that. I have using different kernel version, however, the probelem persists, so i think this is not a kernel issue, but a qemu problem. + + +if the irqbalance is running in vm, the problem happens very often, however if the irqbalance is stopped, the problem disappear. + + +Steps to reproduce: +1. using the 7.2.5 or versions earlier than 7.2.5 and start vm which has an nvme disk +2. the nvme disk is passed through by VFIO +3. using FIO to perform pressure test on the nvme disk in vm diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1842 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1842 new file mode 100644 index 000000000..107b792c4 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1842 @@ -0,0 +1,15 @@ +keyutils meson regression in 8.1.0 +Description of problem: +keyutils is no longer found by meson during the build. + +commit 0db0fbb5cf8955d4f7a4a82bde32cfd93bd042ea appears to be buggy: +``` +$ grep KEYUTILS config-host.h +#undef CONFIG_KEYUTILS +``` +Steps to reproduce: +1. Have keyutils installed +2. Build QEMU 8.1.0 +3. Note that keyutils is no longer linked into the build + +Thanks diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1843 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1843 new file mode 100644 index 000000000..2848861ba --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1843 @@ -0,0 +1,15 @@ +Multitouch - GTK: Tapping 3 points or more at too close in interval causes all points to be lost +Description of problem: +When using the new multitouch input device, if you use three or more fingers within two rapid interval, the all finger inputs get dropped. +Steps to reproduce: +ANDROID +1. Download and install BlissOS +2. Swipe with two fingers +3. try multitouch debug app + +FEDORA +1. Load fedora +2. install wev +3. try touch 3 or more points +Additional information: +Not sure what logs are relevant diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1844 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1844 new file mode 100644 index 000000000..7278dcc76 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1844 @@ -0,0 +1,22 @@ +qemu process memory usage greater than windows guest memory usage +Description of problem: +The Windows Guest internal memory usage is low,but is very high on host of qemu progress. But the linux guest is no such case.Is there any way to trigger the host to reclaim virtual machine memory? +Steps to reproduce: +1.install a windows guest with 128GB of memory and start it. + +2.When the machine is stable, the VM internal memory usage is low,but is very high on host of qemu progress. + +3.on host,use "free -g" to query,the memory used is also very high + +4.when migrate or dormancy,it can recovery,but I want to know is there any way to trigger the host to reclaim virtual machine memory? + + +host: + + + + + +guest: + + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1845 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1845 new file mode 100644 index 000000000..91216cc95 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1845 @@ -0,0 +1,9 @@ +qemu-xhci not working on aarch64 +Description of problem: +Once the VM is loaded I run lsusb from the cli and I get no devices listed. +Steps to reproduce: +1. Build qemu from source with libusb support +2. Launch vm using the above configuration +3. Run lsusb from the command line in the VM instance +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1848 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1848 new file mode 100644 index 000000000..1cd4dfcd7 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1848 @@ -0,0 +1,25 @@ +8.1.0 build failure ../accel/tcg/cputlb.c: In function ‘do_ld_mmio_beN’: error: call to ‘qemu_build_not_reached_always’ declared with attribute error: code path is reachable +Description of problem: +Error when building with -Og. Does not occur with -O2. + +``` +FAILED: libqemu-i386-softmmu.fa.p/accel_tcg_cputlb.c.o +x86_64-pc-linux-gnu-gcc -m64 -mcx16 -Ilibqemu-i386-softmmu.fa.p -I. -I.. -Itarget/i386 -I../target/i386 -Iqapi -Itrace -Iui -Iui/shader -I/usr/include/pixman-1 -I/usr/include/spice-server -I/usr/include/spice-1 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/opus -fdiagnostics-color=auto -Wall -Winvalid-pch -std=gnu11 -O2 -fstack-protector-strong -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -Wundef -Wwrite-strings -Wmissing-prototypes -Wstrict-prototypes -Wredundant-decls -Wold-style-declaration -Wold-style-definition -Wtype-limits -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body -Wnested-externs -Wendif-labels -Wexpansion-to-defined -Wimplicit-fallthrough=2 -Wmissing-format-attribute -Wno-missing-include-dirs -Wno-shift-negative-value -Wno-psabi -isystem /x/portage/app-emulation/qemu-8.1.0/work/qemu-8.1.0/linux-headers -isystem linux-headers -iquote . -iquote /x/portage/app-emulation/qemu-8.1.0/work/qemu-8.1.0 -iquote /x/portage/app-emulation/qemu-8.1.0/work/qemu-8.1.0/include -iquote /x/portage/app-emulation/qemu-8.1.0/work/qemu-8.1.0/host/include/x86_64 -iquote /x/portage/app-emulation/qemu-8.1.0/work/qemu-8.1.0/host/include/generic -iquote /x/portage/app-emulation/qemu-8.1.0/work/qemu-8.1.0/tcg/i386 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -fno-strict-aliasing -fno-common -fwrapv -march=amdfam10 -Og -g -fPIE -isystem../linux-headers -isystemlinux-headers -DNEED_CPU_H '-DCONFIG_TARGET="i386-softmmu-config-target.h"' '-DCONFIG_DEVICES="i386-softmmu-config-devices.h"' -MD -MQ libqemu-i386-softmmu.fa.p/accel_tcg_cputlb.c.o -MF libqemu-i386-softmmu.fa.p/accel_tcg_cputlb.c.o.d -o libqemu-i386-softmmu.fa.p/accel_tcg_cputlb.c.o -c ../accel/tcg/cputlb.c +In file included from ../accel/tcg/cputlb.c:20: +../accel/tcg/cputlb.c: In function ‘do_ld_mmio_beN’: +/x/portage/app-emulation/qemu-8.1.0/work/qemu-8.1.0/include/qemu/osdep.h:244:35: error: call to ‘qemu_build_not_reached_always’ declared with attribute error: code path is reachable + 244 | #define qemu_build_not_reached() qemu_build_not_reached_always() + | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +../accel/tcg/cputlb.c:2121:13: note: in expansion of macro ‘qemu_build_not_reached’ + 2121 | qemu_build_not_reached(); + | ^~~~~~~~~~~~~~~~~~~~~~ +../accel/tcg/cputlb.c: In function ‘do_st_mmio_leN’: +/x/portage/app-emulation/qemu-8.1.0/work/qemu-8.1.0/include/qemu/osdep.h:244:35: error: call to ‘qemu_build_not_reached_always’ declared with attribute error: code path is reachable + 244 | #define qemu_build_not_reached() qemu_build_not_reached_always() + | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +../accel/tcg/cputlb.c:2764:13: note: in expansion of macro ‘qemu_build_not_reached’ + 2764 | qemu_build_not_reached(); + | ^~~~~~~~~~~~~~~~~~~~~~ +``` + +Downstream bug: https://bugs.gentoo.org/913083 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1849 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1849 new file mode 100644 index 000000000..f039b93d1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1849 @@ -0,0 +1,71 @@ +Problems with building riscv Linux using qemu on wsl2 +Description of problem: +execute: + +`qemu-system-riscv64 -M virt -m 256M -nographic -kernel /home/ysc/test/linux-6.1.46/arch/riscv/boot/Image -drive file=rootfs.img,format=raw,id=hd0 -device virtio-blk-device,drive=hd0 -append "root=/dev/vda rw console=ttyS0"` + +**appear:** + +OpenSBI + +/ \_\_ \\ / **_| \_ \_ | | | | | \_\_ \__\_ \_ \_\_ | (_**\_ | |_) || | | | | | '\_ \\ / \_ \\ '\_ \\ \__\_ | \_ \< | | | |\*\*| | |_) | \_\_/ | | |) | |) || | \_\_**/| .**/ \_\*\*|_| |_|**_/|\___\_/_**| | | |\_| + +Platform Name : riscv-virtio,qemu + +Platform Features : medeleg Platform HART Count : 1 + +Platform IPI Device : aclint-mswi + +Platform Timer Device : aclint-mtimer @ 10000000Hz + +Platform Console Device : uart8250 Platform HSM Device : --- + +Platform Reboot Device : sifive_test Platform Shutdown Device : sifive_test + +Firmware Base : 0x80000000 + +Firmware Size : 252 KB + +Runtime SBI Version : 0.3 + +Domain0 Name : root + +Domain0 Boot HART : 0 + +Domain0 HARTs : 0\* + +Domain0 Region00 : 0x0000000002000000-0x000000000200ffff (I) + +Domain0 Region01 : 0x0000000080000000-0x000000008003ffff () + +Domain0 Region02 : 0x0000000000000000-0xffffffffffffffff (R,W,X) + +Domain0 Next Address : 0x0000000080200000 Domain0 Next Arg1 : 0x000000008f000000 + +Domain0 Next Mode : S-mode Domain0 SysReset : yes + +Boot HART ID : 0 + +Boot HART Domain : root + +Boot HART ISA : rv64imafdcsuh + +Boot HART Features : scounteren,mcounteren,time + +Boot HART PMP Count : 16 + +Boot HART PMP Granularity : 4 + +Boot HART PMP Address Bits: 54 + +Boot HART MHPM Count : 0 + +Boot HART MIDELEG : 0x0000000000001666 + +Boot HART MEDELEG : 0x0000000000f0b509 + +When I run qemu, it's stuck here +Steps to reproduce: +1. Build the kernel file using Linux-6.1.46 +2. Use busbox to build rootfs +3. run qemu diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/185 b/gitlab/issues_text/target_missing/host_missing/accel_missing/185 new file mode 100644 index 000000000..f8a8ca37c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/185 @@ -0,0 +1 @@ +Coroutines: Audit use of "coroutine_fn" specifier diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1851 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1851 new file mode 100644 index 000000000..c0e558492 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1851 @@ -0,0 +1,435 @@ +hw/net/rocker: NULL pointer dereference in of_dpa_cmd_add_l2_flood +Description of problem: +rocker_tlv_parse_nested could return early because of no group ids in the group_tlvs. In such case tlvs is NULL; tlvs\[i + 1\] in the next for-loop will deref the NULL pointer. +Steps to reproduce: +Compile and run the following code within the guest: + +``` +#include <stdio.h> +#include <stdlib.h> +#include <string.h> +#include <assert.h> +#include <fcntl.h> +#include <inttypes.h> +#include <sys/mman.h> +#include <sys/types.h> +#include <sys/stat.h> +#include <unistd.h> +#include <sys/io.h> +#include <stdint.h> +#include <stdbool.h> +#include <err.h> +#include <errno.h> +#include <pthread.h> + +/* + * Rocker DMA ring register offsets + */ +#define ROCKER_DMA_DESC_BASE 0x1000 +#define ROCKER_DMA_DESC_SIZE 32 +#define ROCKER_DMA_DESC_MASK 0x1F +#define ROCKER_DMA_DESC_TOTAL_SIZE \ + (ROCKER_DMA_DESC_SIZE * 64) /* 62 ports + event + cmd */ +#define ROCKER_DMA_DESC_ADDR_OFFSET 0x00 /* 8-byte */ +#define ROCKER_DMA_DESC_SIZE_OFFSET 0x08 +#define ROCKER_DMA_DESC_HEAD_OFFSET 0x0c +#define ROCKER_DMA_DESC_TAIL_OFFSET 0x10 +#define ROCKER_DMA_DESC_CTRL_OFFSET 0x14 +#define ROCKER_DMA_DESC_CREDITS_OFFSET 0x18 +#define ROCKER_DMA_DESC_RSVD_OFFSET 0x1c + +/* + * Rocker dma ctrl register bits + */ +#define ROCKER_DMA_DESC_CTRL_RESET (1 << 0) + +/* + * Rocker test registers + */ +#define ROCKER_TEST_REG 0x0010 +#define ROCKER_TEST_REG64 0x0018 /* 8-byte */ +#define ROCKER_TEST_IRQ 0x0020 +#define ROCKER_TEST_DMA_ADDR 0x0028 /* 8-byte */ +#define ROCKER_TEST_DMA_SIZE 0x0030 +#define ROCKER_TEST_DMA_CTRL 0x0034 + +/* + * Rocker general purpose registers + */ +#define ROCKER_CONTROL 0x0300 +#define ROCKER_PORT_PHYS_COUNT 0x0304 +#define ROCKER_PORT_PHYS_LINK_STATUS 0x0310 /* 8-byte */ +#define ROCKER_PORT_PHYS_ENABLE 0x0318 /* 8-byte */ +#define ROCKER_SWITCH_ID 0x0320 /* 8-byte */ + +/* + * Rocker test register ctrl + */ +#define ROCKER_TEST_DMA_CTRL_CLEAR (1 << 0) +#define ROCKER_TEST_DMA_CTRL_FILL (1 << 1) +#define ROCKER_TEST_DMA_CTRL_INVERT (1 << 2) + +#define __le16 uint16_t +#define __le32 uint32_t +#define __le64 uint64_t + +typedef struct rocker_desc { + __le64 buf_addr; + uint64_t cookie; + __le16 buf_size; + __le16 tlv_size; + __le16 rsvd[5]; /* pad to 32 bytes */ + __le16 comp_err; +} __attribute__((packed, aligned(8))) RockerDesc; + + +/* + * Rocker TLV type fields + */ + +typedef struct rocker_tlv { + __le32 type; + __le16 len; + __le16 rsvd; +} __attribute__((packed, aligned(8))) RockerTlv; + + +typedef struct cmd_group_msg { + RockerTlv tlv1; + __le64 t1_value; + RockerTlv tlv2; + __le64 t2_value; + RockerTlv tlv3; + __le64 t3_value; +} __attribute__((packed, aligned(8))) CmdGroupMsg; + + +typedef struct cmd_msg { + RockerTlv tlv1; + __le64 t1_value; + RockerTlv tlv2; + CmdGroupMsg group_msg; +} __attribute__((packed, aligned(8))) CmdMsg; + + +typedef struct rx_msg { + RockerTlv tlv1; + __le64 t1_value; + RockerTlv tlv2; + __le64 t2_value; + RockerTlv tlv3; + __le64 t3_value; + RockerTlv tlv4; + __le64 t4_value; + RockerTlv tlv5; + __le64 t5_value; +} __attribute__((packed, aligned(8))) RxMsg; + + +/* Rx msg */ +enum { + ROCKER_TLV_RX_UNSPEC, + ROCKER_TLV_RX_FLAGS, /* u16, see RX_FLAGS_ */ + ROCKER_TLV_RX_CSUM, /* u16 */ + ROCKER_TLV_RX_FRAG_ADDR, /* u64 */ + ROCKER_TLV_RX_FRAG_MAX_LEN, /* u16 */ + ROCKER_TLV_RX_FRAG_LEN, /* u16 */ + + __ROCKER_TLV_RX_MAX, + ROCKER_TLV_RX_MAX = __ROCKER_TLV_RX_MAX - 1, +}; + +/* Tx msg */ +enum { + ROCKER_TLV_TX_UNSPEC, + ROCKER_TLV_TX_OFFLOAD, /* u8, see TX_OFFLOAD_ */ + ROCKER_TLV_TX_L3_CSUM_OFF, /* u16 */ + ROCKER_TLV_TX_TSO_MSS, /* u16 */ + ROCKER_TLV_TX_TSO_HDR_LEN, /* u16 */ + ROCKER_TLV_TX_FRAGS, /* array */ + + __ROCKER_TLV_TX_MAX, + ROCKER_TLV_TX_MAX = __ROCKER_TLV_TX_MAX - 1, +}; + +/* cmd msg */ +enum { + ROCKER_TLV_CMD_UNSPEC, + ROCKER_TLV_CMD_TYPE, /* u16 */ + ROCKER_TLV_CMD_INFO, /* nest */ + + __ROCKER_TLV_CMD_MAX, + ROCKER_TLV_CMD_MAX = __ROCKER_TLV_CMD_MAX - 1, +}; + +enum { + ROCKER_TLV_CMD_TYPE_UNSPEC, + ROCKER_TLV_CMD_TYPE_GET_PORT_SETTINGS, + ROCKER_TLV_CMD_TYPE_SET_PORT_SETTINGS, + ROCKER_TLV_CMD_TYPE_OF_DPA_FLOW_ADD, + ROCKER_TLV_CMD_TYPE_OF_DPA_FLOW_MOD, + ROCKER_TLV_CMD_TYPE_OF_DPA_FLOW_DEL, + ROCKER_TLV_CMD_TYPE_OF_DPA_FLOW_GET_STATS, + ROCKER_TLV_CMD_TYPE_OF_DPA_GROUP_ADD, + ROCKER_TLV_CMD_TYPE_OF_DPA_GROUP_MOD, + ROCKER_TLV_CMD_TYPE_OF_DPA_GROUP_DEL, + ROCKER_TLV_CMD_TYPE_OF_DPA_GROUP_GET_STATS, + + __ROCKER_TLV_CMD_TYPE_MAX, + ROCKER_TLV_CMD_TYPE_MAX = __ROCKER_TLV_CMD_TYPE_MAX - 1, +}; + +/* + * cmd info nested for OF-DPA msgs + */ + +enum { + ROCKER_TLV_OF_DPA_UNSPEC, + ROCKER_TLV_OF_DPA_TABLE_ID, /* u16 */ + ROCKER_TLV_OF_DPA_PRIORITY, /* u32 */ + ROCKER_TLV_OF_DPA_HARDTIME, /* u32 */ + ROCKER_TLV_OF_DPA_IDLETIME, /* u32 */ + ROCKER_TLV_OF_DPA_COOKIE, /* u64 */ + ROCKER_TLV_OF_DPA_IN_PPORT, /* u32 */ + ROCKER_TLV_OF_DPA_IN_PPORT_MASK, /* u32 */ + ROCKER_TLV_OF_DPA_OUT_PPORT, /* u32 */ + ROCKER_TLV_OF_DPA_GOTO_TABLE_ID, /* u16 */ + ROCKER_TLV_OF_DPA_GROUP_ID, /* u32 */ + ROCKER_TLV_OF_DPA_GROUP_ID_LOWER, /* u32 */ + ROCKER_TLV_OF_DPA_GROUP_COUNT, /* u16 */ + ROCKER_TLV_OF_DPA_GROUP_IDS, /* u32 array */ + ROCKER_TLV_OF_DPA_VLAN_ID, /* __be16 */ + ROCKER_TLV_OF_DPA_VLAN_ID_MASK, /* __be16 */ + ROCKER_TLV_OF_DPA_VLAN_PCP, /* __be16 */ + ROCKER_TLV_OF_DPA_VLAN_PCP_MASK, /* __be16 */ + ROCKER_TLV_OF_DPA_VLAN_PCP_ACTION, /* u8 */ + ROCKER_TLV_OF_DPA_NEW_VLAN_ID, /* __be16 */ + ROCKER_TLV_OF_DPA_NEW_VLAN_PCP, /* u8 */ + ROCKER_TLV_OF_DPA_TUNNEL_ID, /* u32 */ + ROCKER_TLV_OF_DPA_TUNNEL_LPORT, /* u32 */ + ROCKER_TLV_OF_DPA_ETHERTYPE, /* __be16 */ + ROCKER_TLV_OF_DPA_DST_MAC, /* binary */ + ROCKER_TLV_OF_DPA_DST_MAC_MASK, /* binary */ + ROCKER_TLV_OF_DPA_SRC_MAC, /* binary */ + ROCKER_TLV_OF_DPA_SRC_MAC_MASK, /* binary */ + ROCKER_TLV_OF_DPA_IP_PROTO, /* u8 */ + ROCKER_TLV_OF_DPA_IP_PROTO_MASK, /* u8 */ + ROCKER_TLV_OF_DPA_IP_DSCP, /* u8 */ + ROCKER_TLV_OF_DPA_IP_DSCP_MASK, /* u8 */ + ROCKER_TLV_OF_DPA_IP_DSCP_ACTION, /* u8 */ + ROCKER_TLV_OF_DPA_NEW_IP_DSCP, /* u8 */ + ROCKER_TLV_OF_DPA_IP_ECN, /* u8 */ + ROCKER_TLV_OF_DPA_IP_ECN_MASK, /* u8 */ + ROCKER_TLV_OF_DPA_DST_IP, /* __be32 */ + ROCKER_TLV_OF_DPA_DST_IP_MASK, /* __be32 */ + ROCKER_TLV_OF_DPA_SRC_IP, /* __be32 */ + ROCKER_TLV_OF_DPA_SRC_IP_MASK, /* __be32 */ + ROCKER_TLV_OF_DPA_DST_IPV6, /* binary */ + ROCKER_TLV_OF_DPA_DST_IPV6_MASK, /* binary */ + ROCKER_TLV_OF_DPA_SRC_IPV6, /* binary */ + ROCKER_TLV_OF_DPA_SRC_IPV6_MASK, /* binary */ + ROCKER_TLV_OF_DPA_SRC_ARP_IP, /* __be32 */ + ROCKER_TLV_OF_DPA_SRC_ARP_IP_MASK, /* __be32 */ + ROCKER_TLV_OF_DPA_L4_DST_PORT, /* __be16 */ + ROCKER_TLV_OF_DPA_L4_DST_PORT_MASK, /* __be16 */ + ROCKER_TLV_OF_DPA_L4_SRC_PORT, /* __be16 */ + ROCKER_TLV_OF_DPA_L4_SRC_PORT_MASK, /* __be16 */ + ROCKER_TLV_OF_DPA_ICMP_TYPE, /* u8 */ + ROCKER_TLV_OF_DPA_ICMP_TYPE_MASK, /* u8 */ + ROCKER_TLV_OF_DPA_ICMP_CODE, /* u8 */ + ROCKER_TLV_OF_DPA_ICMP_CODE_MASK, /* u8 */ + ROCKER_TLV_OF_DPA_IPV6_LABEL, /* __be32 */ + ROCKER_TLV_OF_DPA_IPV6_LABEL_MASK, /* __be32 */ + ROCKER_TLV_OF_DPA_QUEUE_ID_ACTION, /* u8 */ + ROCKER_TLV_OF_DPA_NEW_QUEUE_ID, /* u8 */ + ROCKER_TLV_OF_DPA_CLEAR_ACTIONS, /* u32 */ + ROCKER_TLV_OF_DPA_POP_VLAN, /* u8 */ + ROCKER_TLV_OF_DPA_TTL_CHECK, /* u8 */ + ROCKER_TLV_OF_DPA_COPY_CPU_ACTION, /* u8 */ + + __ROCKER_TLV_OF_DPA_MAX, + ROCKER_TLV_OF_DPA_MAX = __ROCKER_TLV_OF_DPA_MAX - 1, +}; + +#define PAGE_SHIFT 12 +#define PAGE_SIZE (1 << PAGE_SHIFT) +#define PFN_PRESENT (1ull << 63) +#define PFN_PFN ((1ull << 55) - 1) + +uint64_t get_physical_pfn(void* ptr) +{ + uint64_t pfn = -1; + FILE* fp = fopen("/proc/self/pagemap", "rb"); + if (!fp) + { + return pfn; + } + + if (!fseek(fp, (unsigned long)ptr / PAGE_SIZE * 8, SEEK_SET)) + { + fread(&pfn, sizeof(pfn), 1, fp); + if (pfn & PFN_PRESENT) + { + pfn &= PFN_PFN; + } + } + fclose(fp); + return pfn; +} + +uint64_t get_physical_addr(void* ptr) +{ + uint64_t pfn = get_physical_pfn(ptr); + return pfn * PAGE_SIZE + (uint64_t)ptr % PAGE_SIZE; +} + +void* mmio_mem; + +void mmio_write(uint32_t addr, uint32_t value) +{ + *((uint32_t*)(mmio_mem + addr))= value; +} + +void mmio_write64(uint32_t addr, uint64_t value) +{ + *((uint64_t*)(mmio_mem + addr))= value; +} + +uint64_t mmio_read(uint32_t addr) +{ + return *((uint64_t*)(mmio_mem +addr)); +} + +uint64_t mmio_read64(uint64_t addr) +{ + return *((uint64_t*)(mmio_mem +addr)); +} + +uint64_t ring_desk_base_addr(int index) +{ + return ROCKER_DMA_DESC_BASE + index * 32; +} + +int main() +{ + int mmio_fd= open("/sys/devices/pci0000:00/0000:00:04.0/resource0", O_RDWR | O_SYNC); + if (mmio_fd== -1) { + printf("mmio_fd open failed"); + return 1; + } + + mmio_mem = mmap(0, 0x2000, PROT_READ | PROT_WRITE, MAP_SHARED, mmio_fd, 0); + if (mmio_mem == MAP_FAILED) { + printf("mmap mmio_mem failed"); + return 1; + } + + iopl(3); + + RockerTlv cmd_group_tlv = {ROCKER_TLV_OF_DPA_GROUP_ID, sizeof(RockerTlv) + sizeof(__le64), 12345 }; + RockerTlv cmd_count_tlv = {ROCKER_TLV_OF_DPA_GROUP_COUNT, sizeof(RockerTlv) + sizeof(__le64), 12345}; + RockerTlv cmd_ids_tlv = {ROCKER_TLV_OF_DPA_GROUP_IDS, sizeof(RockerTlv) + sizeof(__le64), 12345 }; + + CmdGroupMsg group_msg = { cmd_group_tlv, 0x40000000, cmd_count_tlv, 65535, cmd_ids_tlv, 12345}; + + RockerTlv cmd_type_tlv = {ROCKER_TLV_CMD_TYPE, sizeof(RockerTlv) + sizeof(__le64), 12345 }; + RockerTlv cmd_info_tlv = {ROCKER_TLV_CMD_INFO, sizeof(RockerTlv) + sizeof(CmdGroupMsg), 12345 }; + CmdMsg cmd_msg = {cmd_type_tlv, ROCKER_TLV_CMD_TYPE_OF_DPA_GROUP_ADD, cmd_info_tlv, group_msg }; + RockerDesc cmd_desc = {get_physical_addr(&cmd_msg), 0xdeadbeef, sizeof(CmdMsg), sizeof(CmdMsg), 0x1, 0x4242 }; + + mmio_write64(ROCKER_PORT_PHYS_ENABLE, 0xE); + + // cmd ring + mmio_write(ring_desk_base_addr(0) + ROCKER_DMA_DESC_CTRL_OFFSET, ROCKER_DMA_DESC_CTRL_RESET); + // base_addr + mmio_write64(ring_desk_base_addr(0), get_physical_addr(&cmd_desc)); + mmio_write(ring_desk_base_addr(0) + ROCKER_DMA_DESC_SIZE_OFFSET, 8); + mmio_write(ring_desk_base_addr(0) + ROCKER_DMA_DESC_HEAD_OFFSET, 4); + + printf("End\n"); + return 0; +} +``` + +Stack trace: + +```plaintext +=================================================================================================== +ldl_he_p(const void * ptr) (/home/arayz/arayz/qemu-git-e1000e/include/qemu/bswap.h:359) +ldl_le_p(const void * ptr) (/home/arayz/arayz/qemu-git-e1000e/include/qemu/bswap.h:394) +rocker_tlv_get_le32(const RockerTlv * tlv) (/home/arayz/arayz/qemu-git-e1000e/hw/net/rocker/rocker_tlv.h:114) +of_dpa_cmd_add_l2_flood(OfDpa * of_dpa, OfDpaGroup * group, RockerTlv ** group_tlvs) (/home/arayz/arayz/qemu-git-e1000e/hw/net/rocker/rocker_of_dpa.c:2043) +of_dpa_cmd_group_do(OfDpa * of_dpa, uint32_t group_id, OfDpaGroup * group, RockerTlv ** group_tlvs) (/home/arayz/arayz/qemu-git-e1000e/hw/net/rocker/rocker_of_dpa.c:2125) +of_dpa_cmd_group_add(OfDpa * of_dpa, uint32_t group_id, RockerTlv ** group_tlvs) (/home/arayz/arayz/qemu-git-e1000e/hw/net/rocker/rocker_of_dpa.c:2145) +of_dpa_group_cmd(OfDpa * of_dpa, struct desc_info * info, char * buf, uint16_t cmd, RockerTlv ** group_tlvs) (/home/arayz/arayz/qemu-git-e1000e/hw/net/rocker/rocker_of_dpa.c:2204) +of_dpa_cmd(World * world, struct desc_info * info, char * buf, uint16_t cmd, RockerTlv * cmd_info_tlv) (/home/arayz/arayz/qemu-git-e1000e/hw/net/rocker/rocker_of_dpa.c:2234) +world_do_cmd(World * world, DescInfo * info, char * buf, uint16_t cmd, RockerTlv * cmd_info_tlv) (/home/arayz/arayz/qemu-git-e1000e/hw/net/rocker/rocker_world.c:43) +cmd_consume(Rocker * r, DescInfo * info) (/home/arayz/arayz/qemu-git-e1000e/hw/net/rocker/rocker.c:450) +ring_pump(DescRing * ring) (/home/arayz/arayz/qemu-git-e1000e/hw/net/rocker/rocker_desc.c:242) +desc_ring_set_head(DescRing * ring, uint32_t new) (/home/arayz/arayz/qemu-git-e1000e/hw/net/rocker/rocker_desc.c:281) +rocker_io_writel(void * opaque, hwaddr addr, uint32_t val) (/home/arayz/arayz/qemu-git-e1000e/hw/net/rocker/rocker.c:805) +rocker_mmio_write(void * opaque, hwaddr addr, uint64_t val, unsigned int size) (/home/arayz/arayz/qemu-git-e1000e/hw/net/rocker/rocker.c:996) +memory_region_write_accessor(MemoryRegion * mr, hwaddr addr, uint64_t * value, unsigned int size, int shift, uint64_t mask, MemTxAttrs attrs) (/home/arayz/arayz/qemu-git-e1000e/softmmu/memory.c:492) +access_with_adjusted_size(hwaddr addr, uint64_t * value, unsigned int size, unsigned int access_size_min, unsigned int access_size_max, MemTxResult (*)(MemoryRegion *, hwaddr, uint64_t *, unsigned int, int, uint64_t, MemTxAttrs) access_fn, MemoryRegion * mr, MemTxAttrs attrs) (/home/arayz/arayz/qemu-git-e1000e/softmmu/memory.c:554) +memory_region_dispatch_write(MemoryRegion * mr, hwaddr addr, uint64_t data, MemOp op, MemTxAttrs attrs) (/home/arayz/arayz/qemu-git-e1000e/softmmu/memory.c:1514) +flatview_write_continue(FlatView * fv, hwaddr addr, MemTxAttrs attrs, const void * ptr, hwaddr len, hwaddr addr1, hwaddr l, MemoryRegion * mr) (/home/arayz/arayz/qemu-git-e1000e/softmmu/physmem.c:2783) +flatview_write(FlatView * fv, hwaddr addr, MemTxAttrs attrs, const void * buf, hwaddr len) (/home/arayz/arayz/qemu-git-e1000e/softmmu/physmem.c:2823) +address_space_write(AddressSpace * as, hwaddr addr, MemTxAttrs attrs, const void * buf, hwaddr len) (/home/arayz/arayz/qemu-git-e1000e/softmmu/physmem.c:2915) +address_space_rw(AddressSpace * as, hwaddr addr, MemTxAttrs attrs, void * buf, hwaddr len, _Bool is_write) (/home/arayz/arayz/qemu-git-e1000e/softmmu/physmem.c:2925) +kvm_cpu_exec(CPUState * cpu) (/home/arayz/arayz/qemu-git-e1000e/accel/kvm/kvm-all.c:2929) +kvm_vcpu_thread_fn(void * arg) (/home/arayz/arayz/qemu-git-e1000e/accel/kvm/kvm-accel-ops.c:49) +qemu_thread_start(void * args) (/home/arayz/arayz/qemu-git-e1000e/util/qemu-thread-posix.c:556) +libpthread.so.0!start_thread(void * arg) (/build/glibc-sMfBJT/glibc-2.31/nptl/pthread_create.c:477) +libc.so.6!clone() (/build/glibc-sMfBJT/glibc-2.31/sysdeps/unix/sysv/linux/x86_64/clone.S:95) +=================================================================================================== + + disassemble and register context: +=================================================================================================== +Dump of assembler code for function ldl_he_p: + 0x000055d8a1a473e6 <+0>: push %rbp + 0x000055d8a1a473e7 <+1>: mov %rsp,%rbp + 0x000055d8a1a473ea <+4>: sub $0x20,%rsp + 0x000055d8a1a473ee <+8>: mov %rdi,-0x18(%rbp) + 0x000055d8a1a473f2 <+12>: mov %fs:0x28,%rax + 0x000055d8a1a473fb <+21>: mov %rax,-0x8(%rbp) + 0x000055d8a1a473ff <+25>: xor %eax,%eax + 0x000055d8a1a47401 <+27>: mov -0x18(%rbp),%rax +=> 0x000055d8a1a47405 <+31>: mov (%rax),%eax + 0x000055d8a1a47407 <+33>: mov %eax,-0xc(%rbp) + 0x000055d8a1a4740a <+36>: mov -0xc(%rbp),%eax + 0x000055d8a1a4740d <+39>: mov -0x8(%rbp),%rdx + 0x000055d8a1a47411 <+43>: xor %fs:0x28,%rdx + 0x000055d8a1a4741a <+52>: je 0x55d8a1a47421 <ldl_he_p+59> + 0x000055d8a1a4741c <+54>: callq 0x55d8a186d6d0 <__stack_chk_fail@plt> + 0x000055d8a1a47421 <+59>: leaveq + 0x000055d8a1a47422 <+60>: retq +End of assembler dump. + +rax 0x8 8 +rbx 0x7f7828088ac0 140154044451520 +rcx 0x0 0 +rdx 0x7f7828088ac0 140154044451520 +rsi 0x8 8 +rdi 0x8 8 +rbp 0x7f7832cfd100 0x7f7832cfd100 +rsp 0x7f7832cfd0e0 0x7f7832cfd0e0 +r8 0x7f7828088ac0 140154044451520 +r9 0x7f7828000790 140154043893648 +r10 0x7f78280008d0 140154043893968 +r11 0x7f7828000080 140154043891840 +r12 0x7ffec007cb1e 140732120156958 +r13 0x7ffec007cb1f 140732120156959 +r14 0x7ffec007cbe0 140732120157152 +r15 0x7f7832cfdb00 140154225285888 +rip 0x55d8a1a47405 0x55d8a1a47405 <ldl_he_p+31> +eflags 0x10246 [ PF ZF IF RF ] +cs 0x33 51 +ss 0x2b 43 +ds 0x0 0 +es 0x0 0 +fs 0x0 0 +gs 0x0 0 +=================================================================================================== +``` +Additional information: +This was wrongly assigned a high-severity CVE and is being discussed on qemu-devel ML: https://lists.nongnu.org/archive/html/qemu-devel/2023-08/msg04621.html diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1853 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1853 new file mode 100644 index 000000000..9cfcb73a0 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1853 @@ -0,0 +1 @@ +Errors when install QEMU from source code diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1855 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1855 new file mode 100644 index 000000000..f1435edb9 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1855 @@ -0,0 +1,59 @@ +io-qcow2-iothreads-commit-active test fails in a "minimal" build of QEMU +Description of problem: +The build fails because of the `io-qcow2-iothreads-commit-active` test failure: + +``` +343/412 qemu:block / io-qcow2-iothreads-commit-active ERROR 1.66s exit status 1 +――――――――――――――――――――――――――――――――――――― ✀ ――――――――――――――――――――――――――――――――――――― +stderr: +--- /tmp/guix-build-qemu-minimal-8.1.0.drv-0/qemu-8.1.0/tests/qemu-iotests/tests/iothreads-commit-active.out ++++ /tmp/guix-build-qemu-minimal-8.1.0.drv-0/qemu-8.1.0/b/qemu/scratch/qcow2-file-iothreads-commit-active/iothreads-commit-active.out.bad +@@ -11,13 +11,27 @@ + 10 MiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec) + + Launching VM... +-Creating some background I/O... +-{"return": {}} +-Starting active commit... +-{"return": {}} +-{"execute": "job-complete", "arguments": {"id": "job1"}} +-{"return": {}} +-{"data": {"device": "job1", "len": 131072, "offset": 131072, "speed": 0, "type": "commit"}, "event": "BLOCK_JOB_READY", "timestamp": {"microseconds": "USECS", "seconds": "SECS"}} +-{"data": {"device": "job1", "len": 131072, "offset": 131072, "speed": 0, "type": "commit"}, "event": "BLOCK_JOB_COMPLETED", "timestamp": {"microseconds": "USECS", "seconds": "SECS"}} +-{"execute": "job-dismiss", "arguments": {"id": "job1"}} +-{"return": {}} ++Traceback (most recent call last): ++ File "/tmp/guix-build-qemu-minimal-8.1.0.drv-0/qemu-8.1.0/python/qemu/machine/machine.py", line 436, in launch ++ self._launch() ++ File "/tmp/guix-build-qemu-minimal-8.1.0.drv-0/qemu-8.1.0/python/qemu/machine/machine.py", line 463, in _launch ++ self._pre_launch() ++ File "/tmp/guix-build-qemu-minimal-8.1.0.drv-0/qemu-8.1.0/tests/qemu-iotests/iotests.py", line 841, in _pre_launch ++ super()._pre_launch() ++ File "/tmp/guix-build-qemu-minimal-8.1.0.drv-0/qemu-8.1.0/python/qemu/machine/qtest.py", line 143, in _pre_launch ++ self._qtest = QEMUQtestProtocol(self._qtest_path, server=True) ++ File "/tmp/guix-build-qemu-minimal-8.1.0.drv-0/qemu-8.1.0/python/qemu/machine/qtest.py", line 54, in __init__ ++ self._sock.bind(self._address) ++OSError: AF_UNIX path too long ++ ++The above exception was the direct cause of the following exception: ++ ++Traceback (most recent call last): ++ File "/tmp/guix-build-qemu-minimal-8.1.0.drv-0/qemu-8.1.0/tests/qemu-iotests/tests/iothreads-commit-active", line 65, in <module> ++ vm.launch() ++ File "/tmp/guix-build-qemu-minimal-8.1.0.drv-0/qemu-8.1.0/python/qemu/machine/machine.py", line 449, in launch ++ raise VMLaunchFailure( ++qemu.machine.machine.VMLaunchFailure: OSError: AF_UNIX path too long ++ Command: /tmp/guix-build-qemu-minimal-8.1.0.drv-0/qemu-8.1.0/b/qemu/tests/qemu-iotests/../../qemu-system-x86_64 -display none -vga none -chardev socket,id=mon,fd=3 -mon chardev=mon,mode=control -qtest unix:path=/tmp/guix-build-qemu-minimal-8.1.0.drv-0/tmptfjmlerc/qcow2-file-iothreads-commit-active/qemu-58979-qtest.sock -accel qtest -nodefaults -display none -accel qtest -object iothread,id=iothread0 -object throttle-group,x-bps-write=1048576,id=tg0 -blockdev file,node-name=disk0-file,filename=/tmp/guix-build-qemu-minimal-8.1.0.drv-0/qemu-8.1.0/b/qemu/scratch/qcow2-file-iothreads-commit-active/58979-disk0.img -blockdev qcow2,node-name=disk0-fmt,file=disk0-file -drive if=none,id=drive0,file=/tmp/guix-build-qemu-minimal-8.1.0.drv-0/qemu-8.1.0/b/qemu/scratch/qcow2-file-iothreads-commit-active/58979-disk0-snap.img,format=qcow2,cache=writeback,aio=threads,backing=disk0-fmt,node-name=disk0 -device virtio-scsi,iothread=iothread0 -device scsi-hd,drive=drive0 -blockdev file,filename=/tmp/guix-build-qemu-minimal-8.1.0.drv-0/qemu-8.1.0/b/qemu/scratch/qcow2-file-iothreads-commit-active/58979-mirror-src.img,node-name=mirror-src-file -blockdev qcow2,file=mirror-src-file,node-name=mirror-src -blockdev file,filename=/tmp/guix-build-qemu-minimal-8.1.0.drv-0/qemu-8.1.0/b/qemu/scratch/qcow2-file-iothreads-commit-active/58979-mirror-dst.img,node-name=mirror-dst-file -blockdev qcow2,file=mirror-dst-file,node-name=mirror-dst-fmt -blockdev throttle,throttle-group=tg0,file=mirror-dst-fmt,node-name=mirror-dst -device scsi-hd,drive=mirror-src ++ Output: ++ + +(test program exited with status code 1) +―――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――― +``` +Steps to reproduce: +1. Install GNU Guix on your GNU/Linux machine. +2. `guix time-machine --url=https://gitlab.com/Apteryks/guix --branch=qemu-minimal-io-qcow2-iothreads-commit-active-test-failure -- build qemu-minimal --keep-failed` +3. Observe the test failure. The build artifacts are left under /tmp/guix-build-qemu-minimal-8.1.0.drv-0 to inspect. +Additional information: +Attached is the complete build log +[8xr1k7v10jp2wgbimib6f0s51ilqgj3z-qemu-minimal-8.1.0.drv.gz](/uploads/59a0f88a05715c18a6bdb44845b83a18/8xr1k7v10jp2wgbimib6f0s51ilqgj3z-qemu-minimal-8.1.0.drv.gz) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1859 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1859 new file mode 100644 index 000000000..1461e6423 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1859 @@ -0,0 +1,8 @@ +Trying to boot Windows Server 2008 Windows Host +Description of problem: +On Windows 10 trying to boot Windows Server 2008 R2 I am just stuck on starting Windows if I do get past Starting Windows it just goes to 0x0000007F BSOD +Steps to reproduce: +1. Run Windows Server with my command line input +2. Stuck on Starting Windows +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/186 b/gitlab/issues_text/target_missing/host_missing/accel_missing/186 new file mode 100644 index 000000000..29a596e34 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/186 @@ -0,0 +1 @@ +Audit consistent option usage in documentation diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1860 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1860 new file mode 100644 index 000000000..33aae4320 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1860 @@ -0,0 +1,10 @@ +virtio-gpu: Only black screen observed after resuming when guest vm do S3 +Description of problem: +On Xen hypervisor, host(dom0) is PVH, guest(domU) is hvm, config virtio-gpu for guest. + +## +Steps to reproduce: +1. In guest vm run "sudo su root" & "echo mem \> /sys/power/state" +2. In host run "sudo xl trigger \<guest id\> s3resume" +Additional information: +## diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1862 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1862 new file mode 100644 index 000000000..5e9f3ed91 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1862 @@ -0,0 +1,18 @@ +SVGA/VESA strange colors (NetWare 6.x) +Description of problem: +The text mode part of the installation is correct but whenever the X server is starting, the display seems to be in 16 colors although GUI settings shows "SVGA/256 colors" (NetWare setup reports a "SVGA Plug & Play" display, VESA 2.0 compliance expected). Color depth issue with VESA? Telling NetWare to use explicitly the Cirrus Logic driver for a CL GD 5446 bring the display back to normal and colors are displayed as they should. +Steps to reproduce: +1. Grab a NetWare 6.0 installation ISO on some abandonware site (no need of a license key, unlicensed = 2 users max.) +2. Execute the command line above +3. Complete the text-mode part (defaults choices are fine) +Additional information: +NetWare 6.0 + Qemu => Same issue. SVGA PnP with wrong colors. +NetWare 6.5 + Qemu => Same issue. SVGA PnP with wrong colors. +NetWare 6.0 + PCem/86Box => does not exhibit the issue. Colors are normal. + +Using SeaBIOS 1.16. + +Screenshots: + + + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1863 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1863 new file mode 100644 index 000000000..f02a41a8d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1863 @@ -0,0 +1,72 @@ +Assertion `core->delayed_causes == 0` failed in hw/net/e1000e_core.c:353 during fuzzing +Description of problem: +Got an assertion failure `core->delayed_causes == 0` when fuzzing e1000e. +Steps to reproduce: +Minimized reproducer for the error: + +```plaintext +cat << EOF | ./qemu-system-x86_64 -display none -machine accel=qtest, -m 512M -M q35 \ +-nodefaults -device e1000e,netdev=net0 -netdev user,id=net0 -qtest \ +/dev/null -qtest stdio +outl 0xcf8 0x80000810 +outl 0xcfc 0xe0000000 +outl 0xcf8 0x80000804 +outw 0xcfc 0x06 +write 0xe000042a 0x2 0x0241 +write 0xe0000402 0x2 0x0200 +write 0x400b 0x1 0x88 +write 0xe0000438 0x4 0x01040000 +outl 0xcf8 0x800008a3 +outb 0xcfc 0x80 +EOF +``` +Additional information: +The crash report triggered by the reproducer is: + +```plaintext +qemu-fuzz-x86_64: /../hw/net/e1000e_core.c:353: uint32_t e1000e_intmgr_collect_delayed_causes(E1000ECore *): Assertion `core->delayed_causes == 0' failed. +==2036033== ERROR: libFuzzer: deadly signal + #0 0x5606ff6c555e in __sanitizer_print_stack_trace ../../../llvm-project-15.0.0.src/compiler-rt/lib/asan/asan_stack.cpp:87:3 + #1 0x5606ff607bb1 in fuzzer::PrintStackTrace() ../../../llvm-project-15.0.0.src/compiler-rt/lib/fuzzer/FuzzerUtil.cpp:210:38 + #2 0x5606ff5e2486 in fuzzer::Fuzzer::CrashCallback() (.part.0) ../../../llvm-project-15.0.0.src/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:233:18 + #3 0x5606ff5e254d in fuzzer::Fuzzer::CrashCallback() ../../../llvm-project-15.0.0.src/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:205:1 + #4 0x5606ff5e254d in fuzzer::Fuzzer::StaticCrashSignalCallback() ../../../llvm-project-15.0.0.src/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:204:19 + #5 0x7f7490e4e41f (/lib/x86_64-linux-gnu/libpthread.so.0+0x1441f) (BuildId: 7b4536f41cdaa5888408e82d0836e33dcf436466) + #6 0x7f7490c4200a in __libc_signal_restore_set /build/glibc-SzIz7B/glibc-2.31/signal/../sysdeps/unix/sysv/linux/internal-signals.h:86:3 + #7 0x7f7490c4200a in raise /build/glibc-SzIz7B/glibc-2.31/signal/../sysdeps/unix/sysv/linux/raise.c:48:3 + #8 0x7f7490c21858 in abort /build/glibc-SzIz7B/glibc-2.31/stdlib/abort.c:79:7 + #9 0x7f7490c21728 in __assert_fail_base /build/glibc-SzIz7B/glibc-2.31/assert/assert.c:92:3 + #10 0x7f7490c32fd5 in __assert_fail /build/glibc-SzIz7B/glibc-2.31/assert/assert.c:101:3 + #11 0x5606ffd20c33 in e1000e_intmgr_collect_delayed_causes ../hw/net/e1000e_core.c:353:9 + #12 0x5606ffd20c33 in e1000e_set_interrupt_cause ../hw/net/e1000e_core.c:2203:12 + #13 0x5606ffd1bd1b in e1000e_receive_internal ../hw/net/e1000e_core.c:1751:9 + #14 0x56070055a58a in qemu_deliver_packet_iov ../net/net.c:820:15 + #15 0x56070055e215 in qemu_net_queue_deliver ../net/queue.c:164:11 + #16 0x56070055f9ca in qemu_net_queue_flush ../net/queue.c:286:15 + #17 0x56070054f5c8 in qemu_flush_or_purge_queued_packets ../net/net.c:681:9 + #18 0x5606ffd14ff5 in e1000e_start_recv ../hw/net/e1000e_core.c:983:9 + #19 0x5606ffd3c33b in e1000e_set_rx_control ../hw/net/e1000e_core.c:1959:9 + #20 0x5606ffd20fe8 in e1000e_core_write ../hw/net/e1000e_core.c:3306:9 + #21 0x560700caeb43 in memory_region_write_accessor ../softmmu/memory.c:493:5 + #22 0x560700cae2ca in access_with_adjusted_size ../softmmu/memory.c:569:18 + #23 0x560700cad670 in memory_region_dispatch_write ../softmmu/memory.c + #24 0x560700cf7d6f in flatview_write_continue ../softmmu/physmem.c:2677:23 + #25 0x560700cef213 in flatview_write ../softmmu/physmem.c:2719:12 + #26 0x560700ceef27 in address_space_write ../softmmu/physmem.c:2815:18 + #27 0x560700420b2f in qtest_process_command ../softmmu/qtest.c:558:13 + #28 0x56070041ecfb in qtest_process_inbuf ../softmmu/qtest.c:810:9 + #29 0x56070041eb19 in qtest_server_inproc_recv ../softmmu/qtest.c:941:9 + #30 0x56070126a792 in qtest_sendf ../tests/qtest/libqtest.c:607:5 + #31 0x56070126ae9e in qtest_write ../tests/qtest/libqtest.c:1072:5 + #32 0x56070126ae9e in qtest_writel ../tests/qtest/libqtest.c:1088:5 + #33 0x5606ff7058cb in __wrap_qtest_writel ../tests/qtest/fuzz/qtest_wrappers.c:180:9 + #34 0x5606ff70d5f2 in op_write ../tests/qtest/fuzz/generic_fuzz.c:485:13 + #35 0x5606ff70bd2f in generic_fuzz ../tests/qtest/fuzz/generic_fuzz.c:666:13 + #36 0x5606ff7008e7 in LLVMFuzzerTestOneInput ../tests/qtest/fuzz/fuzz.c:158:5 + #37 0x5606ff5e2d08 in fuzzer::Fuzzer::ExecuteCallback(unsigned char const*, unsigned long) ../../../llvm-project-15.0.0.src/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:612:15 + #38 0x5606ff5c6124 in fuzzer::RunOneTest(fuzzer::Fuzzer*, char const*, unsigned long) ../../../llvm-project-15.0.0.src/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:324:21 + #39 0x5606ff5d2b0a in fuzzer::FuzzerDriver(int*, char***, int (*)(unsigned char const*, unsigned long)) ../../../llvm-project-15.0.0.src/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:860:19 + #40 0x5606ff5bd8d6 in main ../../../llvm-project-15.0.0.src/compiler-rt/lib/fuzzer/FuzzerMain.cpp:20:30 + #41 0x7f7490c23082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16 + #42 0x5606ff5bd95d in _start (./qemu-fuzz-x86_64+0x1ef595d) +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1871 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1871 new file mode 100644 index 000000000..cd0890878 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1871 @@ -0,0 +1 @@ +Browse qcow2 image contents and add/remove files diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1872 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1872 new file mode 100644 index 000000000..5411a055a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1872 @@ -0,0 +1 @@ +When I compile package , I will report 'Could not open'/lib64/ld musl arch64. so. 1 ': No such file or directory diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1873 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1873 new file mode 100644 index 000000000..888aed0ea --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1873 @@ -0,0 +1,84 @@ +igb driver failed to change MTU +Description of problem: +I am using the new IGB model to test sriov inside a virtual machine. + +and when the operator tries to configure MTU of 9000 on the VF I get a kernel crash and the node goes into reboot + +``` +virsh console virt-cluster-worker-0 +Connected to domain 'virt-cluster-worker-0' +Escape character is ^] (Ctrl + ]) +[ 486.776188] kernel BUG at include/linux/skbuff.h:2420! +[ 486.779661] invalid opcode: 0000 [#1] PREEMPT SMP NOPTI +[ 486.781938] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.14.0-284.16.1.el9_2.x86_64 #1 +[ 486.783847] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.2-0-gea1b7a073390-prebuilt.qemu.org 04/01/2014 +[ 486.785681] RIP: 0010:eth_type_trans+0xd3/0x140 +[ 486.787051] Code: 80 00 00 00 eb c1 8b 47 70 2b 47 74 48 8b 97 c8 00 00 00 83 f8 01 7e 1b 48 85 d2 74 06 66 83 3a ff 74 09 b8 00 04 00 00 eb a5 <0f> 0b b8 00 01 00 00 eb 9c 48 85 ff 74 eb 31 f6 b9 02 00 00 00 48 +[ 486.790542] RSP: 0018:ffffaef200114e30 EFLAGS: 00010283 +[ 486.791726] RAX: 000000000000002e RBX: ffffaef206a38000 RCX: 0000000000000028 +[ 486.793086] RDX: ffff90bb7767a840 RSI: ffff90bc7d6a0000 RDI: ffff90bb413bc600 +[ 486.794430] RBP: ffff90bb413bc600 R08: 0000000000000000 R09: ffff90bc7d6a0980 +[ 486.795779] R10: 000000000000003c R11: 00000001a8be8000 R12: 0000000000000001 +[ 486.797132] R13: 0000000000000003 R14: ffff90bd3b94e400 R15: ffff90bdcbc8c000 +[ 486.798499] FS: 0000000000000000(0000) GS:ffff90beafc40000(0000) knlGS:0000000000000000 +[ 486.800325] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 +[ 486.801520] CR2: 00007faf740ec058 CR3: 000000010a40c004 CR4: 0000000000770ee0 +[ 486.802856] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 +[ 486.804171] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 +[ 486.805459] PKRU: 55555554 +[ 486.806291] Call Trace: +[ 486.807083] <IRQ> +[ 486.807822] igbvf_clean_rx_irq.constprop.0.isra.0+0x1b4/0x600 [igbvf] +[ 486.809027] igbvf_poll+0x3d/0x210 [igbvf] +[ 486.809981] __napi_poll+0x27/0x170 +[ 486.810886] net_rx_action+0x233/0x2f0 +[ 486.811777] __do_softirq+0xc7/0x2ac +[ 486.812644] __irq_exit_rcu+0xb5/0xe0 +[ 486.813515] common_interrupt+0x80/0xa0 +[ 486.814404] </IRQ> +[ 486.815113] <TASK> +[ 486.815800] asm_common_interrupt+0x22/0x40 +[ 486.816710] RIP: 0010:default_idle+0x10/0x20 +[ 486.817631] Code: cc 0f ae f0 0f ae 38 0f ae f0 eb b5 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 0f 1f 44 00 00 66 90 0f 00 2d 7e 3e 4d 00 fb f4 <c3> cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc 0f 1f 44 00 00 65 +[ 486.820523] RSP: 0018:ffffaef2000afed0 EFLAGS: 00000246 +[ 486.821705] RAX: ffffffff99f36ea0 RBX: ffff90bb4032a300 RCX: ffff90bd581f2430 +[ 486.822936] RDX: 000000000013bd13 RSI: 0000000000000001 RDI: 000000000013bd14 +[ 486.824165] RBP: 0000000000000000 R08: 0000007155e9e493 R09: ffff90bb437f4800 +[ 486.825374] R10: 0000000000000232 R11: 0000000000000000 R12: 0000000000000000 +[ 486.826581] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 +[ 486.827777] ? mwait_idle+0x80/0x80 +[ 486.828593] default_idle_call+0x33/0xe0 +[ 486.829479] cpuidle_idle_call+0x15d/0x1c0 +[ 486.830381] ? kvm_sched_clock_read+0x14/0x40 +[ 486.831289] do_idle+0x7b/0xe0 +[ 486.832035] cpu_startup_entry+0x19/0x20 +[ 486.833076] start_secondary+0x116/0x140 +[ 486.834527] secondary_startup_64_no_verify+0xe5/0xeb +[ 486.835953] </TASK> +[ 486.836991] Modules linked in: igbvf veth ipt_REJECT nf_reject_ipv4 xt_nat xt_CT vhost_net vhost vhost_iotlb tap tun nf_conntrack_netlink tls xt_MASQUERADE nft_chain_nat xt_mark xt_conntrack xt_comment nft_compat nft_counter nf_tables rfkill geneve ip6_udp_tunnel udp_tunnel nfnetlink_cttimeout nfnetlink openvswitch nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 overlay ext4 mbcache jbd2 intel_rapl_msr intel_rapl_common isst_if_common nfit libnvdimm kvm_intel kvm irqbypass rapl iTCO_wdt iTCO_vendor_support cirrus drm_shmem_helper drm_kms_helper pcspkr i2c_i801 syscopyarea sysfillrect i2c_smbus sysimgblt virtio_balloon lpc_ich fb_sys_fops joydev ip_tables drm xfs libcrc32c dm_multipath sr_mod cdrom sg igb nvme_tcp ahci nvme_fabrics nvme libahci nvme_core virtio_net crct10dif_pclmul libata i2c_algo_bit crc32_pclmul dca virtio_console net_failover nvme_common virtio_blk t10_pi crc32c_intel failover ghash_clmulni_intel serio_raw dm_mirror dm_region_hash dm_log dm_mod fuse +[ 486.852907] ---[ end trace d1f9cdb1a6c92411 ]--- +[ 486.854263] RIP: 0010:eth_type_trans+0xd3/0x140 +[ 486.855234] Code: 80 00 00 00 eb c1 8b 47 70 2b 47 74 48 8b 97 c8 00 00 00 83 f8 01 7e 1b 48 85 d2 74 06 66 83 3a ff 74 09 b8 00 04 00 00 eb a5 <0f> 0b b8 00 01 00 00 eb 9c 48 85 ff 74 eb 31 f6 b9 02 00 00 00 48 +[ 486.858732] RSP: 0018:ffffaef200114e30 EFLAGS: 00010283 +[ 486.859777] RAX: 000000000000002e RBX: ffffaef206a38000 RCX: 0000000000000028 +[ 486.861020] RDX: ffff90bb7767a840 RSI: ffff90bc7d6a0000 RDI: ffff90bb413bc600 +[ 486.862238] RBP: ffff90bb413bc600 R08: 0000000000000000 R09: ffff90bc7d6a0980 +[ 486.863478] R10: 000000000000003c R11: 00000001a8be8000 R12: 0000000000000001 +[ 486.864718] R13: 0000000000000003 R14: ffff90bd3b94e400 R15: ffff90bdcbc8c000 +[ 486.865969] FS: 0000000000000000(0000) GS:ffff90beafc40000(0000) knlGS:0000000000000000 +[ 486.867317] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 +[ 486.868458] CR2: 00007faf740ec058 CR3: 000000010a40c004 CR4: 0000000000770ee0 +[ 486.869705] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 +[ 486.870959] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 +[ 486.872212] PKRU: 55555554 +[ 486.873040] Kernel panic - not syncing: Fatal exception in interrupt +[ 486.875441] Kernel Offset: 0x18400000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff) +[ 486.877044] Rebooting in 10 seconds.. +``` +Steps to reproduce: +1. create a vm using igb driver for the network interface +2. change the MTU of the PF to 9000 +3. allocate virtual functions +4. change the MTU on the virtual function (vm crash) +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1875 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1875 new file mode 100644 index 000000000..a24f5921a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1875 @@ -0,0 +1,9 @@ +qemu-system-x86_64: warning: no scancode found for keysym 65483 +Description of problem: +qemu-system-x86_64: warning: no scancode found for keysym 65483 + +I'm hoping this is something that could easily be added to qemu, rather than a limitation of windows: + +I want to bind F14 to an arbitrary key, in this case `keycode 148 = XF86Calculator`, but it's not happening, and qemu is giving the error: `qemu-system-x86_64: warning: no scancode found for keysym 65483` + +`xmodmap -e "keycode 148 = F14 F14 F14 F14 F14"` Executes with no error, and xev correctly shows as F14 pressed/released, but a windows 10 VM started afterwards cannot recognise this bind. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1876 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1876 new file mode 100644 index 000000000..bd6f8b3fd --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1876 @@ -0,0 +1 @@ +Host wayland gtk problem diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1877 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1877 new file mode 100644 index 000000000..c7b63f178 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1877 @@ -0,0 +1,243 @@ +virtiofs Illegal Seek Error because of ivshmem device of looking-glass +Description of problem: +tl;dr: The dev "gnif" from looking-glass does not want to analyse this problem which his config from the documentation is causing. He insists someone opens a issue here at qemu's, so thats what i did now :) He also insists this problem is not caused by his config (even though the config is needed for looking-glass) and does not want to help or analyse this whole mess. Sorry if i'm a bit salty. + +Please see the following issues on his and the virtio-win github : \ +https://github.com/gnif/LookingGlass/issues/1089 + +https://github.com/gnif/LookingGlass/issues/1083 + +[https://github.com/virtio-win/kvm-guest-drivers-windows/issues/911](https://github.com/virtio-win/kvm-guest-drivers-windows/issues/911%5C) + +# +Steps to reproduce: +1. Create a VM +2. enable looking-glass (i used the latest Beta6 release from github) with the mentioned kernel module (i use manjaro and can use looking-glass-module-dkms from AUR) +3. add virtiofs from virt-manager +Additional information: +libvirt XML + +```plaintext +<domain xmlns:qemu="http://libvirt.org/schemas/domain/qemu/1.0" type="kvm"> + <name>win10</name> + <uuid>a026f749-3adc-4ab8-a5cf-521a4e8ec9d6</uuid> + <metadata> + <libosinfo:libosinfo xmlns:libosinfo="http://libosinfo.org/xmlns/libvirt/domain/1.0"> + <libosinfo:os id="http://microsoft.com/win/10"/> + </libosinfo:libosinfo> + </metadata> + <memory unit="KiB">12582912</memory> + <currentMemory unit="KiB">12582912</currentMemory> + <memoryBacking> + <source type="memfd"/> + <access mode="shared"/> + </memoryBacking> + <vcpu placement="static">10</vcpu> + <os> + <type arch="x86_64" machine="pc-q35-5.1">hvm</type> + <loader readonly="yes" type="pflash">/usr/share/edk2-ovmf/x64/OVMF_CODE.fd</loader> + <nvram>/var/lib/libvirt/qemu/nvram/win10_VARS.fd</nvram> + </os> + <features> + <acpi/> + <apic/> + <hyperv mode="custom"> + <relaxed state="on"/> + <vapic state="on"/> + <spinlocks state="on" retries="8191"/> + <vendor_id state="on" value="ASRock"/> + </hyperv> + <vmport state="off"/> + </features> + <cpu mode="host-passthrough" check="none" migratable="on"> + <topology sockets="1" dies="1" cores="5" threads="2"/> + </cpu> + <clock offset="localtime"> + <timer name="hpet" present="yes"/> + <timer name="hypervclock" present="yes"/> + </clock> + <on_poweroff>destroy</on_poweroff> + <on_reboot>restart</on_reboot> + <on_crash>restart</on_crash> + <pm> + <suspend-to-mem enabled="no"/> + <suspend-to-disk enabled="yes"/> + </pm> + <devices> + <emulator>/usr/bin/qemu-system-x86_64</emulator> + <disk type="file" device="cdrom"> + <driver name="qemu" type="raw"/> + <target dev="sdc" bus="sata"/> + <readonly/> + <boot order="1"/> + <address type="drive" controller="0" bus="0" target="0" unit="2"/> + </disk> + <disk type="file" device="disk"> + <driver name="qemu" type="qcow2" cache="none" discard="unmap"/> + <source file="/opt/windowsos.qcow2"/> + <target dev="sdd" bus="scsi"/> + <boot order="2"/> + <address type="drive" controller="0" bus="0" target="0" unit="3"/> + </disk> + <disk type="block" device="disk"> + <driver name="qemu" type="raw" cache="none" io="native" discard="unmap"/> + <source dev="/dev/zvol/satassd2tb/vms/windowsdata2"/> + <target dev="sde" bus="scsi"/> + <address type="drive" controller="0" bus="0" target="0" unit="4"/> + </disk> + <controller type="usb" index="0" model="qemu-xhci" ports="15"> + <address type="pci" domain="0x0000" bus="0x02" slot="0x00" function="0x0"/> + </controller> + <controller type="pci" index="0" model="pcie-root"/> + <controller type="pci" index="1" model="pcie-root-port"> + <model name="pcie-root-port"/> + <target chassis="1" port="0x10"/> + <address type="pci" domain="0x0000" bus="0x00" slot="0x02" function="0x0" multifunction="on"/> + </controller> + <controller type="pci" index="2" model="pcie-root-port"> + <model name="pcie-root-port"/> + <target chassis="2" port="0x11"/> + <address type="pci" domain="0x0000" bus="0x00" slot="0x02" function="0x1"/> + </controller> + <controller type="pci" index="3" model="pcie-root-port"> + <model name="pcie-root-port"/> + <target chassis="3" port="0x12"/> + <address type="pci" domain="0x0000" bus="0x00" slot="0x02" function="0x2"/> + </controller> + <controller type="pci" index="4" model="pcie-root-port"> + <model name="pcie-root-port"/> + <target chassis="4" port="0x13"/> + <address type="pci" domain="0x0000" bus="0x00" slot="0x02" function="0x3"/> + </controller> + <controller type="pci" index="5" model="pcie-root-port"> + <model name="pcie-root-port"/> + <target chassis="5" port="0x14"/> + <address type="pci" domain="0x0000" bus="0x00" slot="0x02" function="0x4"/> + </controller> + <controller type="pci" index="6" model="pcie-root-port"> + <model name="pcie-root-port"/> + <target chassis="6" port="0x15"/> + <address type="pci" domain="0x0000" bus="0x00" slot="0x02" function="0x5"/> + </controller> + <controller type="pci" index="7" model="pcie-root-port"> + <model name="pcie-root-port"/> + <target chassis="7" port="0x16"/> + <address type="pci" domain="0x0000" bus="0x00" slot="0x02" function="0x6"/> + </controller> + <controller type="pci" index="8" model="pcie-root-port"> + <model name="pcie-root-port"/> + <target chassis="8" port="0x17"/> + <address type="pci" domain="0x0000" bus="0x00" slot="0x02" function="0x7"/> + </controller> + <controller type="pci" index="9" model="pcie-to-pci-bridge"> + <model name="pcie-pci-bridge"/> + <address type="pci" domain="0x0000" bus="0x05" slot="0x00" function="0x0"/> + </controller> + <controller type="pci" index="10" model="pcie-root-port"> + <model name="pcie-root-port"/> + <target chassis="10" port="0x18"/> + <address type="pci" domain="0x0000" bus="0x00" slot="0x03" function="0x0" multifunction="on"/> + </controller> + <controller type="pci" index="11" model="pcie-root-port"> + <model name="pcie-root-port"/> + <target chassis="11" port="0x19"/> + <address type="pci" domain="0x0000" bus="0x00" slot="0x03" function="0x1"/> + </controller> + <controller type="pci" index="12" model="pcie-root-port"> + <model name="pcie-root-port"/> + <target chassis="12" port="0x1a"/> + <address type="pci" domain="0x0000" bus="0x00" slot="0x03" function="0x2"/> + </controller> + <controller type="scsi" index="0" model="virtio-scsi"> + <address type="pci" domain="0x0000" bus="0x08" slot="0x00" function="0x0"/> + </controller> + <controller type="sata" index="0"> + <address type="pci" domain="0x0000" bus="0x00" slot="0x1f" function="0x2"/> + </controller> + <controller type="virtio-serial" index="0"> + <address type="pci" domain="0x0000" bus="0x0c" slot="0x00" function="0x0"/> + </controller> + <filesystem type="mount" accessmode="passthrough"> + <driver type="virtiofs"/> + <source dir="/home/nemu/Downloads"/> + <target dir="nemu_downloads"/> + <address type="pci" domain="0x0000" bus="0x04" slot="0x00" function="0x0"/> + </filesystem> + <interface type="bridge"> + <mac address="52:54:00:cc:75:be"/> + <source bridge="vmbr0"/> + <model type="virtio"/> + <link state="up"/> + <address type="pci" domain="0x0000" bus="0x01" slot="0x00" function="0x0"/> + </interface> + <interface type="bridge"> + <mac address="52:54:00:b8:8d:30"/> + <source bridge="vmbr1"/> + <model type="virtio"/> + <address type="pci" domain="0x0000" bus="0x07" slot="0x00" function="0x0"/> + </interface> + <channel type="spicevmc"> + <target type="virtio" name="com.redhat.spice.0"/> + <address type="virtio-serial" controller="0" bus="0" port="1"/> + </channel> + <input type="mouse" bus="virtio"> + <address type="pci" domain="0x0000" bus="0x0a" slot="0x00" function="0x0"/> + </input> + <input type="keyboard" bus="virtio"> + <address type="pci" domain="0x0000" bus="0x0b" slot="0x00" function="0x0"/> + </input> + <input type="mouse" bus="ps2"/> + <input type="keyboard" bus="ps2"/> + <graphics type="spice" port="-1" autoport="no" listen="127.0.0.1"> + <listen type="address" address="127.0.0.1"/> + <image compression="off"/> + <gl enable="no"/> + </graphics> + <sound model="ich9"> + <audio id="1"/> + <address type="pci" domain="0x0000" bus="0x00" slot="0x1b" function="0x0"/> + </sound> + <audio id="1" type="spice"/> + <video> + <model type="vga" vram="16384" heads="1" primary="yes"> + <acceleration accel3d="no"/> + </model> + <address type="pci" domain="0x0000" bus="0x00" slot="0x01" function="0x0"/> + </video> + <hostdev mode="subsystem" type="pci" managed="yes"> + <source> + <address domain="0x0000" bus="0x04" slot="0x00" function="0x0"/> + </source> + <address type="pci" domain="0x0000" bus="0x03" slot="0x00" function="0x0"/> + </hostdev> + <hostdev mode="subsystem" type="pci" managed="yes"> + <source> + <address domain="0x0000" bus="0x04" slot="0x00" function="0x1"/> + </source> + <address type="pci" domain="0x0000" bus="0x06" slot="0x00" function="0x0"/> + </hostdev> + <redirdev bus="usb" type="spicevmc"> + <address type="usb" bus="0" port="2"/> + </redirdev> + <redirdev bus="usb" type="spicevmc"> + <address type="usb" bus="0" port="3"/> + </redirdev> + <redirdev bus="usb" type="spicevmc"> + <address type="usb" bus="0" port="4"/> + </redirdev> + <redirdev bus="usb" type="spicevmc"> + <address type="usb" bus="0" port="5"/> + </redirdev> + <watchdog model="itco" action="reset"/> + <memballoon model="none"/> + </devices> + <qemu:commandline> + <qemu:arg value="-device"/> + <qemu:arg value="{"driver":"ivshmem-plain","id":"shmem1","memdev":"looking-glass"}"/> + <qemu:arg value="-object"/> + <qemu:arg value="{"qom-type":"memory-backend-file","id":"looking-glass","mem-path":"/dev/kvmfr0","size":134217728,"share":true}"/> + </qemu:commandline> +</domain> +``` + +If more logs are needed please just ask. I will gladly provide them. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1879 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1879 new file mode 100644 index 000000000..9abd277aa --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1879 @@ -0,0 +1,9 @@ +ARM Cortex-A15 Emulation Not Working +Description of problem: +I want to make a VM with Windows RT 8.1 but it fails because it can't find a file for the to-emulate ARM CPU. +Steps to reproduce: +1. Use virt-manager to make a VM with the ARM architecture. +2. Make sure the emulated CPU is an ARM Cortex-A15. +3. Try installing and making the VM, it will fail with the error. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1880 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1880 new file mode 100644 index 000000000..9fb2160fd --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1880 @@ -0,0 +1,13 @@ +CXL Mem enable error +Description of problem: +During the process of booting, the following info indicate that the CXL Mem is not enabled. +``` +Media not active (-16) +probe of mem0 failed with error -16 +``` +Steps to reproduce: +1. Compile Linux kernel v5.18 as shown in the QEMU doc +2. Run the above-mentioned script +3. Check the booting script +Additional information: +Could you give me some hints of how to operate on the CXL device properly? Thanks a lot. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1881 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1881 new file mode 100644 index 000000000..feee04229 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1881 @@ -0,0 +1,15 @@ +netdev-socket test_stream_unix() is unreliable +Description of problem: +test_stream_unix is unreliable and causes random CI job failures such as this one: +https://gitlab.com/qemu-project/qemu/-/jobs/5020899550 + +``` +576/839 ERROR:../tests/qtest/netdev-socket.c:293:test_stream_unix: assertion failed (resp == expect): ("st0: index=0,type=stream,connection error\r\n" == "st0: index=0,type=stream,unix:/tmp/netdev-socket.UW5IA2/stream_unix\r\n") ERROR +576/839 qemu:qtest+qtest-sh4 / qtest-sh4/netdev-socket ERROR 62.85s killed by signal 6 SIGABRT +>>> MALLOC_PERTURB_=249 QTEST_QEMU_BINARY=./qemu-system-sh4 QTEST_QEMU_STORAGE_DAEMON_BINARY=./storage-daemon/qemu-storage-daemon G_TEST_DBUS_DAEMON=/home/gitlab-runner/builds/-LCfcJ2T/0/qemu-project/qemu/tests/dbus-vmstate-daemon.sh QTEST_QEMU_IMG=./qemu-img /home/gitlab-runner/builds/-LCfcJ2T/0/qemu-project/qemu/build/tests/qtest/netdev-socket --tap -k +――――――――――――――――――――――――――――――――――――― ✀ ――――――――――――――――――――――――――――――――――――― +stderr: +** +ERROR:../tests/qtest/netdev-socket.c:293:test_stream_unix: assertion failed (resp == expect): ("st0: index=0,type=stream,connection error\r\n" == "st0: index=0,type=stream,unix:/tmp/netdev-socket.UW5IA2/stream_unix\r\n") +(test program exited with status code -6) +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1882 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1882 new file mode 100644 index 000000000..babf3dc22 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1882 @@ -0,0 +1,9 @@ +Test suite hangs on FreeBSD 13.2 +Description of problem: +The 80 minute timeout for the x64-freebsd-13-build CI job is insufficient: +https://gitlab.com/qemu-project/qemu/-/jobs/5058610599 + +``` +672/832 qemu:block / io-qcow2-041 OK 39.77s 1 subtests passed +Timed out! +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1883 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1883 new file mode 100644 index 000000000..80864432a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1883 @@ -0,0 +1,6 @@ +riscv64-debian-cross-container CI job fails +Description of problem: +The riscv64-debian-cross-container job is allowed to fail and has been failing for some time. If it fails all the time then running it is a waste of electricity and the test should be disabled. Or maybe someone familiar with the test can rectify things and get it passing again. Either way, it's time for someone familiar with the test to review it. + +Here it a recent CI failure: +https://gitlab.com/qemu-project/qemu/-/jobs/5058610458 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1884 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1884 new file mode 100644 index 000000000..4a2d2eec6 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1884 @@ -0,0 +1,10 @@ +avocado-system-* CI jobs are unreliable +Description of problem: +The avocado-system-* CI jobs fail randomly: +https://gitlab.com/qemu-project/qemu/-/jobs/5058610614 +https://gitlab.com/qemu-project/qemu/-/jobs/5058610654 +https://gitlab.com/qemu-project/qemu/-/jobs/5030428571 + +I don't know how to interpret the test output. Until these CI jobs pass reliably it won't be possible for me to identify when a subtest that is actually healthy/reliable breaks. + +Please take a look at the logs and fix or remove unreliable test cases. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1885 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1885 new file mode 100644 index 000000000..02086fc2b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1885 @@ -0,0 +1,24 @@ +mipsel malta machine is broken in avocado console tests +Description of problem: +As noted in #1884 we see failures of the boot_linux_console.py test. Unlikely other avocado failures, these ones are consistent and reproduce locally with 100% success + +``` +./configure --target-list=mipsel-softmmu +make -j 20 +cd build +./pyvenv/bin/python3 -B -m avocado --show=app run --job-results-dir=./tests/results -t arch:mipsel --failfast tests/avocado/boot_linux_console.py:BootLinuxConsole.test_mips_malta32el_nanomips_4k +``` + +This test will reliably fail with a timeout waiting for console output. + +Attempting to run the QEMU command manually + +``` +$ ./qemu-system-mipsel -display none -vga none -machine malta -chardev stdio,id=console -serial chardev:console -cpu I7200 -no-reboot -kernel /home/berrange/src/virt/qemu/build/tests/results/job-2023-09-13T17.14-77de093/test-results/tmp_dir520smana/1-tests_avocado_boot_linux_console.py_BootLinuxConsole.test_mips_malta32el_nanomips_4kkernel -append 'printk.time=0 mem=256m@@0x0 console=ttyS0' +``` + +results in no serial console output at all. + +IMHO either the MIPS malta machine has had a regression, or the kernel we're downloading for testing has had a regression. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1886 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1886 new file mode 100644 index 000000000..ccfe07b49 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1886 @@ -0,0 +1,17 @@ +migration-test is unreliable +Description of problem: +The following intermittent failure occurred in the CI: + +``` +>>> QTEST_QEMU_IMG=./qemu-img MALLOC_PERTURB_=116 QTEST_QEMU_STORAGE_DAEMON_BINARY=./storage-daemon/qemu-storage-daemon G_TEST_DBUS_DAEMON=/builds/qemu-project/qemu/tests/dbus-vmstate-daemon.sh QTEST_QEMU_BINARY=./qemu-system-x86_64 /builds/qemu-project/qemu/build/tests/qtest/migration-test --tap -k +――――――――――――――――――――――――――――――――――――― ✀ ――――――――――――――――――――――――――――――――――――― +stderr: +qemu-system-x86_64: Unable to read from socket: Connection reset by peer +Memory content inconsistency at 5b43000 first_byte = bd last_byte = bc current = 4f hit_edge = 1 +** +ERROR:../tests/qtest/migration-test.c:300:check_guests_ram: assertion failed: (bad == 0) +(test program exited with status code -6) +``` + +You can find the full output here: +https://gitlab.com/qemu-project/qemu/-/jobs/5080200417 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1887 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1887 new file mode 100644 index 000000000..7f198bb67 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1887 @@ -0,0 +1,9 @@ +Window VM failed to resume when using GPU passthrough(GVT-d) on Intel platform if add 'hv-stimer' option, seems like it happened after V6.2.0 +Description of problem: +Windows VM failed to be resumed if adding 'hv-stimer' after Qemu v6.2.0. +Steps to reproduce: +1.Set up GVTd env and launch Windows 10 VM as guest; +2. Sleep the Windows VM with Sleep button; +3. Resume Windows VM via telnet to qemu ,e.g.,'telnet 127.0.0.1 2222', then input 'system_wakeup' to resume Windows VM. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1888 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1888 new file mode 100644 index 000000000..d91223c4a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1888 @@ -0,0 +1,12 @@ +megasas: Buffer I/O error on dev sda / critical target error, dev sda, sector 0 op 0x0:(READ) +Description of problem: +Since QEMU 7.2.0 when using `megasas` device the guest kernel is unable to I/O with the device (Input/output error) also producing errors messages in `dmesg` like these: +``` +[ 18.739344] critical target error, dev sda, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 +[ 18.739925] Buffer I/O error on dev sda, logical block 0, async page read +[ 18.740374] Dev sda: unable to read RDB block 0 +``` + +Relevant options are: `-device megasas -blockdev driver=null-co,read-zeroes=on,node-name=null -device scsi-hd,drive=null` then in guest `modprobe megaraid-sas`. With qcow2 images - errors are the same. + +I also tested that the same commands produce no errors on QEMU 6.0.0 - 7.1.0. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1889 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1889 new file mode 100644 index 000000000..ecf5eb937 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1889 @@ -0,0 +1,47 @@ +IO delays on live migration lv initialization +Description of problem: +Hi, + +When I live migrate a VM via Proxmox and the destination is an LVM thin pool I see that at the start of copying the disk it's first initialized. + +This leads the thin volume to be directly 100% allocated which needs to be discarded afterwards. Not ideal but .... + +The more annoying thing is that this initialization step used 100% of disk IO. In iotop I see it writing over 1000MB/sec. The nasty side effect is that other VM's on that host are negatively affected. It's not completely locked up, I can ssh in and look around, but storage intensive things see more delay. With e.g. http requests timing out. And even a simple ls command could take 10+ seconds which is normally instant. + + +I've previously reported it on the [proxmox forum](https://forum.proxmox.com/threads/io-delays-on-live-migration-lv-initialization.132296/#post-582050) but the call was made that this is behavior from Qemu. + +> The zeroing happens, because of what QEMU does when the discard option is enabled: + + +When I disable discard for the VM disk I can see that it's not pre-initialized during migration, but not having that defeats the purpose of having an lvm thin pool. + +For the (disk) migration itself I can set a bandwidth limit ... could we do something similar for initialization? + + +Even better would be to not initialize at all when using LVM thin. As far as I understand it the new blocks allocated by lvm thin should always be empty. +Steps to reproduce: +1. Migrate a vm with a large disk +2. look in iotop on the new host, would be see more write IO then the network could handle.. just before the disk content is transferred. +3. look in another VM on the destination host, reading from disk would be significantly slower then normal. +Additional information: +An example VM config +``` +agent: 1,fstrim_cloned_disks=1 +balloon: 512 +bootdisk: scsi0 +cores: 6 +ide2: none,media=cdrom +memory: 8196 +name: ... +net0: virtio=...,bridge=... +numa: 0 +onboot: 1 +ostype: l26 +scsi0: thin_pool_hwraid:vm-301-disk-0,discard=on,format=raw,size=16192M +scsi1: thin_pool_hwraid:vm-301-disk-1,discard=on,format=raw,size=26G +scsihw: virtio-scsi-pci +serial0: socket +smbios1: uuid=... +sockets: 1 +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1892 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1892 new file mode 100644 index 000000000..dd8fabd8e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1892 @@ -0,0 +1,33 @@ +docs/system/devices/cxl.rst suggests qemu-system-aarch64 command lines which fail with "Property 'virt-8.2-machine.cxl' not found" +Description of problem: +When trying to run qemu-system-aarch64 with "-M virt,gic-version=3,cxl=on -m 4g,maxmem=8G,slots=8 -cpu max", get the following problem: +"qemu-system-aarch64: Property 'virt-8.2-machine.cxl' not found". Do I need to compile the QEMU with specific option? +Steps to reproduce: +1. Compile QEMU with "./config" "make -j6" +2. Compile Linux +``` +#!/bin/bash + +KERNEL_PATH=/users/LiuQun/linux/arch/arm64/boot/Image +DISK_IMG=/users/LiuQun/ARM_img/disk-image-22.04-server-arm64.img + +./build/qemu-system-aarch64 \ +-M virt,gic-version=3,cxl=on -m 4g,maxmem=8G,slots=8 -cpu max \ +-bios /users/LiuQun/ARM_img/QEMU_EFI.fd \ +-kernel $KERNEL_PATH \ +-drive file=$DISK_IMG,format=raw,if=none,id=drive-sata0-0-0 \ +-device virtio-blk-device,drive=drive-sata0-0-0 \ +-append "console=ttyAMA0 root=/dev/vda1 rdinit=/init acpi=off" \ +-object memory-backend-file,id=cxl-mem1,share=on,mem-path=cxl-window1,size=512M \ +-object memory-backend-file,id=cxl-label1,share=on,mem-path=cxl-label1,size=1K \ +-object memory-backend-file,id=cxl-label2,share=on,mem-path=cxl-label2,size=1K \ +-device pxb-cxl,id=cxl.0,bus=pcie.0,bus_nr=52,uid=0,len-window-base=1,window-base[0]=0x4c00000000,memdev[0]=cxl-mem1 \ +-device cxl-rp,id=rp0,bus=cxl.0,addr=0.0,chassis=0,slot=0,port=0 \ +-device cxl-rp,id=rp1,bus=cxl.0,addr=1.0,chassis=0,slot=1,port=1 \ +-device cxl-type3,bus=rp0,memdev=cxl-mem1,id=cxl-pmem0,size=256M,lsa=cxl-label1 \ +-device cxl-type3,bus=rp1,memdev=cxl-mem1,id=cxl-pmem1,size=256M,lsa=cxl-label2 \ +-nographic + +``` +Additional information: +The same problem happens with QEMU 8.1 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1893 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1893 new file mode 100644 index 000000000..2e92849c0 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1893 @@ -0,0 +1,13 @@ +assert on savevm +Description of problem: + +Steps to reproduce: +1. launch as above (n.b. qemu-img command: qemu-img create -f qcow2 rootfs.qcow2 60G +2. from qemu monitor: savevm test +3. On stderr + +``` +Assertion failed: (qemu_get_current_aio_context() == qemu_get_aio_context()), function bdrv_poll_co, file block-gen.h, line 43. +``` +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1894 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1894 new file mode 100644 index 000000000..3aa706d5a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1894 @@ -0,0 +1,11 @@ +Can't emulate audio with OpenCore Mac OS X 10.7 +Description of problem: +OpenCore wants me to use `AppleALC`, but to use _that_, I need the layout ID of the motherboard or something and I'm not sure how I'd do that since it's a QEMU VM. All I want to do is have some audio :( + +So, how can I emulate audio with AppleALC + OpenCore/how can I get a layout ID that'll give me audio on a QEMU VM? Do note that I am using UTM (https://getutm.app/) (UTM uses QEMU and is basically a QEMU frontend). +Steps to reproduce: +1. Set up OpenCore and install Mac OS X 10.7 +2. Copy across a .mp3 file +3. iTunes fails to play it due to no audio drivers/audio outputs +Additional information: +N/A diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1896 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1896 new file mode 100644 index 000000000..1bd81bc19 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1896 @@ -0,0 +1,54 @@ +Use `qemu_exit()` function instead of `exit()` +Additional information: +I just saw the similar refactoring for the GDB part of QEMU and thought it might be useful in more general case too: https://lore.kernel.org/qemu-devel/20230907112640.292104-1-chigot@adacore.com/T/#m540552946cfa960b34c4d76d2302324f5de8627f + +``` +$ rg "exit\(0" -t c -l +gdbstub/gdbstub.c +qemu-edid.c +subprojects/libvhost-user/libvhost-user.c +semihosting/arm-compat-semi.c +softmmu/async-teardown.c +softmmu/device_tree.c +softmmu/vl.c +softmmu/runstate.c +os-posix.c +dtc/util.c +dtc/dtc.c +dtc/tests/dumptrees.c +qemu-keymap.c +qemu-io.c +contrib/ivshmem-server/main.c +contrib/rdmacm-mux/main.c +tests/qtest/vhost-user-blk-test.c +tests/qtest/fuzz/fuzz.c +tests/qtest/fuzz/generic_fuzz.c +tests/unit/test-seccomp.c +tests/unit/test-rcu-list.c +tests/unit/rcutorture.c +tests/bench/qht-bench.c +tests/bench/atomic64-bench.c +tests/bench/atomic_add-bench.c +tests/unit/test-iov.c +tests/tcg/multiarch/linux/linux-test.c +tests/tcg/aarch64/mte-3.c +tests/tcg/aarch64/pauth-2.c +tests/tcg/aarch64/mte-5.c +tests/tcg/aarch64/mte-6.c +tests/tcg/aarch64/mte-2.c +tests/tcg/cris/libc/check_glibc_kernelversion.c +tests/tcg/cris/libc/check_lz.c +tests/tcg/s390x/signals-s390x.c +tests/tcg/i386/hello-i386.c +tests/tcg/cris/bare/sys.c +tests/tcg/ppc64/mtfsf.c +qemu-nbd.c +net/net.c +hw/nvram/eeprom93xx.c +hw/arm/allwinner-r40.c +hw/rdma/rdma_backend.c +hw/watchdog/watchdog.c +trace/control.c +hw/pci/pci.c +hw/misc/sifive_test.c +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1897 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1897 new file mode 100644 index 000000000..8f53876ca --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1897 @@ -0,0 +1,21 @@ +npcm7xx_timer-test.c is unreliable +Description of problem: +Sometimes npcm7xx_timer-test fails intermittently: +https://gitlab.com/qemu-project/qemu/-/jobs/5121787250 + +``` +38/96 qemu:qtest+qtest-arm / qtest-arm/npcm7xx_timer-test ERROR 0.95s exit status 1 +>>> QTEST_QEMU_BINARY=./qemu-system-arm QTEST_QEMU_STORAGE_DAEMON_BINARY=./storage-daemon/qemu-storage-daemon G_TEST_DBUS_DAEMON=/builds/qemu-project/qemu/tests/dbus-vmstate-daemon.sh QTEST_QEMU_IMG=./qemu-img MALLOC_PERTURB_=103 /builds/qemu-project/qemu/build/tests/qtest/npcm7xx_timer-test --tap -k +――――――――――――――――――――――――――――――――――――― ✀ ――――――――――――――――――――――――――――――――――――― +stderr: +** +ERROR:../tests/qtest/npcm7xx_timer-test.c:475:test_periodic_interrupt: assertion failed (tim_read(td, TISR) == tim_timer_bit(td)): (0x00000000 == 0x00000004) +** +ERROR:../tests/qtest/npcm7xx_timer-test.c:476:test_periodic_interrupt: 'qtest_get_irq(global_qtest, tim_timer_irq(td))' should be TRUE +(test program exited with status code 1) +―――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――― +``` + +When I reran the CI job, it passed. + +Please investigate why this test is unreliable and fix it. Thanks! diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1898 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1898 new file mode 100644 index 000000000..f83309bb8 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1898 @@ -0,0 +1,32 @@ +Ninja makeserver support +Description of problem: +Building `qemu` using a patched version of `ninja`[0] to utilize `make`'s jobserver feature doesn't work when building `qemu`. Usually, when using a jobserver to control the number of jobs being built in parallel across multiple different builds (i.e. when building with `open-embedded` or `buildroot`), the `-j$(nproc)` argument is left out. In this case, the `Qemu` `Makefile` interprets the absent `-j` argument as a wish for a single process only, and adds a `-j1` argument to the `ninja` call. +Steps to reproduce: +1. Built/install the patched `ninja` from [0]: `export PATH=<path/to/ninja>:$PATH` +2. Start the attached [jobserver.py](/uploads/8215e8a470c97cd456d2d14e2c71c6a5/jobserver.py) script: `python jobserver.py /tmp/jobserver 4` +3. Configure `qemu`: `mkdir build; ../configure` +4. Build `qemu`: `MAKEFLAGS="--jobserver-auth=fifo:/tmp/jobserver" make` +5. Observe that only a single CPU/core is being used. + +Now, to avoid passing `-j1` to `ninja`, remove filtering of `-j` arguments from the `Makefile`: + +```patch +diff --git a/Makefile b/Makefile +index bfc4b2c8e9..d66141787e 100644 +--- a/Makefile ++++ b/Makefile +@@ -142,7 +142,6 @@ MAKE.k = $(findstring k,$(firstword $(filter-out --%,$(MAKEFLAGS)))) + MAKE.q = $(findstring q,$(firstword $(filter-out --%,$(MAKEFLAGS)))) + MAKE.nq = $(if $(word 2, $(MAKE.n) $(MAKE.q)),nq) + NINJAFLAGS = $(if $V,-v) $(if $(MAKE.n), -n) $(if $(MAKE.k), -k0) \ +- $(filter-out -j, $(lastword -j1 $(filter -l% -j%, $(MAKEFLAGS)))) \ + -d keepdepfile + ninja-cmd-goals = $(or $(MAKECMDGOALS), all) + ninja-cmd-goals += $(foreach g, $(MAKECMDGOALS), $(.ninja-goals.$g)) +``` + +Run the build again, and see four jobs being run in parallel: + +`make clean; MAKEFLAGS="--jobserver-auth=fifo:/tmp/jobserver" make` +Additional information: +[0] https://github.com/stefanb2/ninja/tree/topic-issue-1139-part-3-jobserver-fifo diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/190 b/gitlab/issues_text/target_missing/host_missing/accel_missing/190 new file mode 100644 index 000000000..484fb04d7 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/190 @@ -0,0 +1 @@ +'set_link net0 off' not working with e1000e driver diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1900 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1900 new file mode 100644 index 000000000..a68e77648 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1900 @@ -0,0 +1 @@ +8.1.0-r1: segfault at get_zones_wp() at ../block/file-posix.c:1337 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1902 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1902 new file mode 100644 index 000000000..ee1a5eb56 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1902 @@ -0,0 +1,65 @@ +Crash on macOS when screen resolution changes when using SDL UI frontend +Description of problem: +In the above configuration, booting NetBSD works fine up to the point where the kernel sets the framebuffer resolution for the console, which results in a window size change. At this point, the OS terminates the qemu process with this error message: + +``` +*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'NSWindow geometry should only be modified on the main thread!' +*** First throw call stack: +( + 0 CoreFoundation 0x00000001849208c0 __exceptionPreprocess + 176 + 1 libobjc.A.dylib 0x0000000184419eb4 objc_exception_throw + 60 + 2 CoreFoundation 0x0000000184945bac _CFBundleGetValueForInfoKey + 0 + 3 AppKit 0x00000001880a6ab8 -[NSWindow(NSWindow_Theme) _postWindowNeedsToResetDragMarginsUnlessPostingDisabled] + 240 + 4 AppKit 0x00000001880b2a38 -[NSThemeFrame _tileTitlebarAndRedisplay:] + 88 + 5 AppKit 0x00000001880c18a0 -[NSTitledFrame _titleDidChange] + 116 + 6 AppKit 0x0000000188a92f04 -[NSTitledFrame setTitle:subtitle:] + 420 + 7 AppKit 0x00000001880c1570 -[NSThemeFrame setTitle:] + 52 + 8 AppKit 0x000000018866e0fc -[NSFrameView _updateTitleProperties:animated:] + 44 + 9 AppKit 0x0000000188a85e98 -[NSThemeFrame _updateTitleProperties:animated:] + 156 + 10 CoreFoundation 0x00000001848a0780 __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 148 + 11 CoreFoundation 0x00000001849349a8 ___CFXRegistrationPost_block_invoke + 88 + 12 CoreFoundation 0x00000001849348f0 _CFXRegistrationPost + 440 + 13 CoreFoundation 0x000000018486f434 _CFXNotificationPost + 764 + 14 Foundation 0x0000000185960c74 -[NSNotificationCenter postNotificationName:object:userInfo:] + 88 + 15 AppKit 0x000000018881da88 -[NSWindowTitleController _propertiesChanged:] + 128 + 16 AppKit 0x00000001880c1388 -[NSWindow _dosetTitle:andDefeatWrap:] + 156 + 17 libSDL2-2.0.0.dylib 0x0000000106aa9abc Cocoa_SetWindowTitle + 104 + 18 qemu-system-aarch64 0x0000000105006628 sdl_update_caption + 256 + 19 qemu-system-aarch64 0x0000000105007838 sdl_mouse_mode_change + 168 + 20 qemu-system-aarch64 0x00000001054ab100 notifier_list_notify + 36 + 21 qemu-system-aarch64 0x0000000104d28124 qemu_input_check_mode_change + 96 + 22 qemu-system-aarch64 0x0000000104e13a74 hid_pointer_activate + 32 + 23 qemu-system-aarch64 0x0000000104f44c2c usb_process_one + 464 + 24 qemu-system-aarch64 0x0000000104f4491c usb_handle_packet + 120 + 25 qemu-system-aarch64 0x0000000104f58a94 xhci_kick_epctx + 1888 + 26 qemu-system-aarch64 0x00000001052d8f78 memory_region_write_accessor + 264 + 27 qemu-system-aarch64 0x00000001052d8db8 access_with_adjusted_size + 348 + 28 qemu-system-aarch64 0x00000001052d8c04 memory_region_dispatch_write + 428 + 29 qemu-system-aarch64 0x00000001052e6cfc flatview_write_continue + 344 + 30 qemu-system-aarch64 0x00000001052e4068 flatview_write + 156 + 31 qemu-system-aarch64 0x00000001052e9424 subpage_write + 124 + 32 qemu-system-aarch64 0x00000001052d8db8 access_with_adjusted_size + 348 + 33 qemu-system-aarch64 0x00000001052d8c04 memory_region_dispatch_write + 428 + 34 qemu-system-aarch64 0x000000010532ebf4 io_writex + 184 + 35 qemu-system-aarch64 0x000000010532ed44 do_st_mmio_leN + 104 + 36 qemu-system-aarch64 0x0000000105323e78 do_st4_mmu + 536 + 37 ??? 0x0000000108a91750 0x0 + 4440266576 + 38 qemu-system-aarch64 0x00000001053108f0 cpu_tb_exec + 164 + 39 qemu-system-aarch64 0x0000000105311754 cpu_exec_loop + 1084 + 40 qemu-system-aarch64 0x0000000105310edc cpu_exec_setjmp + 48 + 41 qemu-system-aarch64 0x0000000105310dcc cpu_exec + 560 + 42 qemu-system-aarch64 0x0000000105332650 tcg_cpus_exec + 44 + 43 qemu-system-aarch64 0x0000000105332c1c mttcg_cpu_thread_fn + 240 + 44 qemu-system-aarch64 0x00000001054a7494 qemu_thread_start + 128 + 45 libsystem_pthread.dylib 0x00000001847cf034 _pthread_start + 136 + 46 libsystem_pthread.dylib 0x00000001847c9e3c thread_start + 8 +) +libc++abi: terminating due to uncaught exception of type NSException +``` + +I think there have been other bugs of a similar nature in the past with the Cocoa UI. The regression may be because of stricter checks in the new macOS version. +Steps to reproduce: +1. Start qemu (the QEMU_EFI.fd is from Tianocore EDK2). +2. Wait for the NetBSD kernel to set framebuffer resolution and observe the crash. + +With `-nographic`, the problem does not occur. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1903 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1903 new file mode 100644 index 000000000..65effad94 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1903 @@ -0,0 +1,41 @@ +qemu/kvm are instantly SIGKILLed by systemd on shutdown, without wait. +Description of problem: +systemd assumes it cannot terminate qemu, and SIGKILLs it. Instantly. +Steps to reproduce: +1. Start qemu on a systemd managed host +2. Shutdown/Reboot +Additional information: +Nothing on qemu's own log, besides that it is starting a vnc server. + +```plaintext +# journalctl -b -1 +... +Sep 22 18:38:04 local kernel: kvm_amd: TSC scaling supported +Sep 22 18:38:04 local kernel: kvm_amd: Nested Virtualization enabled +Sep 22 18:38:04 local kernel: kvm_amd: Nested Paging enabled +Sep 22 18:38:04 local kernel: kvm_amd: Virtual VMLOAD VMSAVE supported +Sep 22 18:38:04 local kernel: kvm_amd: Virtual GIF supported +Sep 22 18:38:04 local kernel: kvm_amd: LBR virtualization supported +... +Sep 22 18:38:50 local systemd-logind[721]: The system will reboot now! +Sep 22 18:38:50 local systemd-logind[721]: System is rebooting. +Sep 22 18:38:50 local sddm-helper[850]: Signal received: SIGTERM +... +Sep 22 18:38:50 local systemd[1]: Stopping User Manager for UID 1000... +Sep 22 18:38:50 local systemd-logind[721]: Removed session 1. +Sep 22 18:38:50 local systemd[854]: Activating special unit Exit the Session... +Sep 22 18:38:50 local systemd[854]: app-org.kde.konsole-1ab3dac6a1db4b29b55899b477b32975.scope: Failed to kill control group /user.slice/user-1000.slice/user@1000.service/app.slice/> +Sep 22 18:38:50 local systemd[854]: app-org.kde.konsole-1ab3dac6a1db4b29b55899b477b32975.scope: Killing process 1708 (qemu-system-x86) with signal SIGKILL. +Sep 22 18:38:50 local systemd[854]: app-org.kde.konsole-1ab3dac6a1db4b29b55899b477b32975.scope: Killing process 1712 (kvm-nx-lpage-recovery-1708) with signal SIGKILL. +Sep 22 18:38:50 local systemd[854]: app-org.kde.konsole-1ab3dac6a1db4b29b55899b477b32975.scope: Failed to kill control group /user.slice/user-1000.slice/user@1000.service/app.slice/> +Sep 22 18:38:50 local systemd[854]: Stopped Konsole - Terminal. +... (some other applications terminanting normally ) +Sep 22 18:38:50 local systemd[854]: app-org.kde.konsole-1ab3dac6a1db4b29b55899b477b32975.scope: Consumed 10.068s CPU time. +Sep 22 18:38:50 local systemd[854]: Removed slice User Background Tasks Slice. +Sep 22 18:38:50 local systemd[854]: background.slice: Consumed 2.960s CPU time. +... +``` + +I cannot explain why it sends SIGKILL to qemu/kvm... it is the same second as the shutdown started, their docs says there's a delay for that. + +Also, other processes owned by the user received a single SIGTERM after qemu was SIGKILLed. Some even take a couple seconds to exit and are not SIGKILLed. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1904 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1904 new file mode 100644 index 000000000..4b9c20e24 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1904 @@ -0,0 +1,16 @@ +Windows LTO build fails +Description of problem: +LTO likes to delete `win32_close_exception_handler` which causes an error when linking +``` +[2736/5786] Linking target qemu-system-avr.exe +FAILED: qemu-system-avr.exe +"cc" "-m64" "-mcx16" @qemu-system-avr.exe.rsp +`win32_close_exception_handler' referenced in section `.xdata' of C:\msys64\tmp\cceRwR4N.ltrans59.ltrans.o: defined in discarded section `.text' of libqemuutil.a.p/util_oslib-win32.c.obj (symbol from plugin) +collect2.exe: error: ld returned 1 exit status +``` +Steps to reproduce: +1. `./configure --enable-lto` +2. `make` +Additional information: +Looks like the offending commit is d89f30b4df13dfe389a4d6cf8a30b2f87c4c166e "win32: wrap socket close() with an exception handler". +Undoing the commit or marking the exception handler as `__attribute__ ((noinline, used))` both appear to fix the issue. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1905 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1905 new file mode 100644 index 000000000..61c0907bb --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1905 @@ -0,0 +1,3 @@ +Allow for copying text from serial output +Additional information: +In addition to the serial output, it would be beneficial if this copy feature could also be extended to the QEMU monitor and parallel output. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1906 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1906 new file mode 100644 index 000000000..5198e5bbc --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1906 @@ -0,0 +1,34 @@ +Failed to compile QEMU 7.0.0 source code. recipe for target 'run-ninja' failed. +Description of problem: +Failed to compiling the download QEMU 7.0.0 source code. It seems to be due to something wrong with ninja. +The followings are error logs after executing command "make -j$(nproc)": + +changing dir to build for make ""... +make[1]: Entering directory '/home/liangke/os-env/qemu-7.0.0/build' +/usr/bin/ninja build.ninja && touch build.ninja.stamp +**ninja: no work to do.** +... +... +... +[1350/2396] Compiling C object libqemu-riscv64-softmmu.fa.p/target_riscv_translate.c.o +**FAILED: libqemu-riscv64-softmmu.fa.p/target_riscv_translate.c.o** +cc -m64 -mcx16 -Ilibqemu-riscv64-softmmu.fa.p -I. -I.. -Itarget/riscv -I../target/riscv -I../dtc/libfdt -I../capstone/include/capstone -Iqapi -Itrace -Iui -Iui/shader -I/usr/include/pixman-1 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -fdiagnostics-color=auto -Wall -Winvalid-pch -std=gnu11 -O2 -g -isystem /home/liangke/os-env/qemu-7.0.0/linux-headers -isystem linux-headers -iquote . -iquote /home/liangke/os-env/qemu-7.0.0 -iquote /home/liangke/os-env/qemu-7.0.0/include -iquote /home/liangke/os-env/qemu-7.0.0/disas/libvixl -iquote /home/liangke/os-env/qemu-7.0.0/tcg/i386 -pthread -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fno-common -fwrapv -Wold-style-declaration -Wold-style-definition -Wtype-limits -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body -Wnested-externs -Wendif-labels -Wexpansion-to-defined -Wimplicit-fallthrough=2 -Wno-missing-include-dirs -Wno-shift-negative-value -Wno-psabi -fstack-protector-strong -fPIE -isystem../linux-headers -isystemlinux-headers -DNEED_CPU_H '-DCONFIG_TARGET="riscv64-softmmu-config-target.h"' '-DCONFIG_DEVICES="riscv64-softmmu-config-devices.h"' -MD -MQ libqemu-riscv64-softmmu.fa.p/target_riscv_translate.c.o -MF libqemu-riscv64-softmmu.fa.p/target_riscv_translate.c.o.d -o libqemu-riscv64-softmmu.fa.p/target_riscv_translate.c.o -c ../target/riscv/translate.c +**cc: fatal error: Killed signal terminated program cc1** +**compilation terminated.** +**ninja: build stopped: subcommand failed.** +**Makefile:163: recipe for target 'run-ninja' failed** +**make[1]: *** [run-ninja] Error 1** +make[1]: Leaving directory '/home/liangke/os-env/qemu-7.0.0/build' +**GNUmakefile:10: recipe for target 'all' failed** +**make: *** [all] Error 2** +Steps to reproduce: +1. cd qemu-7.0.0 source code folder; +2. ./configure --target-list=riscv64-softmmu,riscv64-linux-user; +3. make -j$(nproc) +Additional information: +1. I downloaded the source code from https://download.qemu.org/qemu-7.0.0.tar.xz. +2. my compiling prerequisites: +sudo apt install autoconf automake autotools-dev curl libmpc-dev libmpfr-dev libgmp-dev \ + gawk build-essential bison flex texinfo gperf libtool patchutils bc ninja-build \ + zlib1g-dev libexpat-dev pkg-config libglib2.0-dev libpixman-1-dev git tmux python3 +3. Found ninja-1.8.2 at /usr/bin/ninja diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1907 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1907 new file mode 100644 index 000000000..4691d56fe --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1907 @@ -0,0 +1,57 @@ +QEMU LoongArch regression after merging LASX changes +Description of problem: +After enabling LASX in qemu (@gaosong), booting Gentoo Linux with latest glibc master (w/ LSX & LASX optimized libc routines) will fail in systemd: + +``` +[ 10.350207] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000085 +[ 10.350557] CPU: 5 PID: 1 Comm: systemd Not tainted 6.5.2-gentoo #2 +[ 10.350655] Hardware name: QEMU QEMU Virtual Machine, BIOS 0.0.0 02/06/2015 +[ 10.350961] Stack : 0072617764726148 0000000000000000 9000000000223440 90000001000e4000 +[ 10.351181] 90000001000e7990 90000001000e7998 0000000000000000 90000001000e7ad8 +[ 10.351294] 90000001000e7ad0 90000001000e7ad0 90000001000e7900 0000000000000001 +[ 10.351406] 0000000000000001 90000001000e7998 ec94a2e1446052e6 9000000100438140 +[ 10.351519] 0000000000000001 0000000000000003 0000000000000000 0000000000000030 +[ 10.351630] 0000000000000000 00000000000559bf 00000000056e0000 0000000000000004 +[ 10.351745] 0000000000000000 0000000000000000 900000000162b438 900000000177e000 +[ 10.351856] 00000000400004d8 0000000000000001 0000000000000018 90000001000e7c84 +[ 10.351968] 0000000000020000 0000000000000000 9000000000223458 00007ffff0341af0 +[ 10.352081] 00000000000000b0 0000000000000004 0000000000000000 0000000000071c1c +[ 10.352196] ... +[ 10.352277] Call Trace: +[ 10.352482] [<9000000000223458>] show_stack+0x5c/0x180 +[ 10.353518] [<9000000001178d4c>] dump_stack_lvl+0x60/0x88 +[ 10.353592] [<900000000115cd7c>] panic+0x13c/0x308 +[ 10.353670] [<900000000024244c>] do_exit+0x860/0x868 +[ 10.353735] [<900000000024261c>] do_group_exit+0x34/0x94 +[ 10.353803] [<9000000000250514>] get_signal+0x75c/0x804 +[ 10.353869] [<90000000002254c4>] arch_do_signal_or_restart+0x74/0xae0 +[ 10.353944] [<90000000002c738c>] exit_to_user_mode_loop.isra.0+0x90/0x10c +[ 10.354041] [<9000000001179ff0>] irqentry_exit_to_user_mode+0x1c/0x28 +[ 10.354119] [<90000000011792f8>] do_bp+0xcc/0x2ac +[ 10.354222] [<90000001005a1924>] 0x90000001005a1924 +[ 10.354522] [<00007ffff0341af0>] 0x7ffff0341af0 +``` + +Full log: + +[stderr](/uploads/61b9870ae2441c9a25f44791c67889b8/stderr) + +Instruction trace `-d in_asm,out_asm,op` (very large): + +[log.tar.zstd](https://cloud.tsinghua.edu.cn/f/a83eac6d44694ede8cb1/?dl=1) + +I also tried to boot LoongArchLinux whose glibc does not have LSX/LASX optimized C routines, and it can boot without problems. If I chroot from LoongArchLinux into Gentoo Linux, running `emerge` command will SIGSEGV. + +If I disable LASX in CPUCFG2, the problem is gone: + +```cpp +// data = FIELD_DP32(data, CPUCFG2, LASX, 1), +``` + +I guess the bug is related to LASX assemblies in [glibc](https://github.com/bminor/glibc/tree/master/sysdeps/loongarch/lp64/multiarch). +Steps to reproduce: +1. Launch qemu +2. Wait for systemd to be killed +3. Collect logs +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1914 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1914 new file mode 100644 index 000000000..9e10aa314 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1914 @@ -0,0 +1,7 @@ +x86 q35 machine type documentation is missing +Description of problem: +The x86 machine type of q35 was added in 2012 by commit +df2d8b3ed4d2 ("q35: Introduce q35 pc based chipset emulator") +but no documentation was added to docs/master/system/target-i386.html +Additional information: +There was development documentation at https://wiki.qemu.org/Features/Q35 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1915 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1915 new file mode 100644 index 000000000..e0f91d670 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1915 @@ -0,0 +1,11 @@ +whpx causes a blue screen on guest windows +Description of problem: +i wanted to install windows 7 with qemu, but qunad i tried i got a blue screen . Then I downgraded to version 5.0.2 and it worked perfectly, I also tried with windows 10 and it didn't boot. + + +Steps to reproduce: +1. install windows 7 iso +2. run the setup +3. and the bsod.. +Additional information: +I tried it with qemu 5.0.2 and it worked perfectly. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1918 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1918 new file mode 100644 index 000000000..2166b756b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1918 @@ -0,0 +1,49 @@ +Build failure on FreeBSD 13.2-RELEASE-p3 amd64 with --vhost-user +Description of problem: +- Assumption that the python interpreter is in PATH as `python3` +- Attempt to include Linux headers on a FreeBSD system +Steps to reproduce: +1. `$ ./configure --prefix=/opt/qemu --enable-vhost-user` (log attached below) +2. `$ ninja -C build` +3. See it running a python script without an explicit python interpreter +4. Work around by invoking the python script through the interpreter that meson found: + +```diff +diff --git a/ui/meson.build b/ui/meson.build +index 0a1e8272a3..c6456f54c4 100644 +--- a/ui/meson.build ++++ b/ui/meson.build +@@ -81,7 +81,7 @@ if dbus_display + input: 'dbus-display1.xml', + output: 'dbus-display1.xml', + env: env, +- command: [xml_pp, '@INPUT@', '@OUTPUT@']) ++ command: [python, xml_pp, '@INPUT@', '@OUTPUT@']) + dbus_display1 = custom_target('dbus-display gdbus-codegen', + output: ['dbus-display1.h', 'dbus-display1.c'], + input: xml, + +``` + +5. Then fails trying to include a Linux header: + +```console +/usr/bin/cc -m64 -mcx16 -Ilibcommon.fa.p -I../common-user/host/x86_64 -I../bsd-user/include -Isubprojects/dtc/libfdt -I../subprojects/dtc/libfdt -Iui -I../ui -I/usr/local/include/capstone -I/usr/local/include/pixman-1 -I/usr/local/include/l +ibpng16 -I/usr/local/include -I/usr/local/include/p11-kit-1 -I/usr/local/include/SDL2 -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/gio-unix-2.0 -I/usr/local/include/slirp -I/usr/local/include/gtk-3.0 +-I/usr/local/include/pango-1.0 -I/usr/local/include/harfbuzz -I/usr/local/include/freetype2 -I/usr/local/include/fribidi -I/usr/local/include/cairo -I/usr/local/include/gdk-pixbuf-2.0 -I/usr/local/include/libepoll-shim -I/usr/local/include/ +atk-1.0 -I/usr/local/include/at-spi2-atk/2.0 -I/usr/local/include/at-spi-2.0 -I/usr/local/include/dbus-1.0 -I/usr/local/lib/dbus-1.0/include -I/usr/local/include/vte-2.91 -I/usr/local/include/webp -fcolor-diagnostics -Wall -Winvalid-pch -st +d=gnu11 -O2 -g -fstack-protector-strong -Wundef -Wwrite-strings -Wmissing-prototypes -Wstrict-prototypes -Wredundant-decls -Wold-style-definition -Wtype-limits -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body -Wn +ested-externs -Wendif-labels -Wexpansion-to-defined -Wmissing-format-attribute -Wno-initializer-overrides -Wno-missing-include-dirs -Wno-shift-negative-value -Wno-string-plus-int -Wno-typedef-redefinition -Wno-tautological-type-limit-compar +e -Wno-psabi -Wno-gnu-variable-sized-type-not-at-end -Wthread-safety -iquote . -iquote /usr/home/nico/build/qemu -iquote /usr/home/nico/build/qemu/include -iquote /usr/home/nico/build/qemu/host/include/x86_64 -iquote /usr/home/nico/build/qe +mu/host/include/generic -iquote /usr/home/nico/build/qemu/tcg/i386 -pthread -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -fno-strict-aliasing -fno-common -fwrapv -fPIE -DAVIF_DLL -DHWY_SHARED_DEFINE -D_REENTRANT -D_THREAD_SAFE - +MD -MQ libcommon.fa.p/hw_net_vhost_net.c.o -MF libcommon.fa.p/hw_net_vhost_net.c.o.d -o libcommon.fa.p/hw_net_vhost_net.c.o -c ../hw/net/vhost_net.c +In file included from ../hw/net/vhost_net.c:37: +/usr/home/nico/build/qemu/linux-headers/linux/vhost.h:14:10: fatal error: 'linux/vhost_types.h' file not found +#include <linux/vhost_types.h> + ^~~~~~~~~~~~~~~~~~~~~ +``` + +I don't know what that is about. Full build log is attached below. +Additional information: +[config_log](/uploads/49d1c33d4b3951f79f826a701ceff1c2/config_log) +[build_log_fail](/uploads/2cb3b49e7503a430457c4d99b1c60dbe/build_log_fail) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1923 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1923 new file mode 100644 index 000000000..c444722a9 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1923 @@ -0,0 +1,18 @@ +qemu breaks vmdk larger than 600GB. +Description of problem: +The vmdk larger than 600G is corrupted after an edit by qemu-nbd. If I open the corrupted vmdk file, I find an extra **^@** byte. +``` +RW 4194304 SPARSE "disk-s289.vmdk" +RW 4^@94304 SPARSE "disk-s290.vmdk" +RW 4194304 SPARSE "disk-s291.vmdk" +``` +Steps to reproduce: +``` + qemu-img create -f vmdk -o subformat=twoGbMaxExtentSparse disk.vmdk 1T + sudo qemu-nbd -c /dev/nbd0 disk.vmdk + sudo mkfs.btrfs /dev/nbd0 + sudo qemu-nbd -d /dev/nbd0 + qemu-img info disk.vmdk | head + ``` +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1924 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1924 new file mode 100644 index 000000000..2ea997d44 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1924 @@ -0,0 +1,66 @@ +memory leak for pthread_create by valgrind +Description of problem: +qemu_thread_create calls pthread_create have memory leak +valgrind stack +``` +==4075190== 1,776 bytes in 3 blocks are possibly lost in loss record 6,778 of 6,978 +==4075190== at 0x4C3721A: calloc (vg_replace_malloc.c:760) +==4075190== by 0x40129EB: _dl_allocate_tls (in /usr/lib64/ld-2.28.so) +==4075190== by 0xADA3DA2: pthread_create@@GLIBC_2.2.5 (in /usr/lib64/libpthread-2.28.so) +==4075190== by 0x9B0DA5: qemu_thread_create (qemu-thread-posix.c:581) +==4075190== by 0x9C470C: do_spawn_thread (thread-pool.c:145) +==4075190== by 0x9C47C0: worker_thread (thread-pool.c:82) +==4075190== by 0x9AFD89: qemu_thread_start (qemu-thread-posix.c:541) +==4075190== by 0xADA3149: start_thread (in /usr/lib64/libpthread-2.28.so) +==4075190== by 0xB0B7DC2: clone (in /usr/lib64/libc-2.28.so) +==4075190== +==4075190== 2,368 bytes in 4 blocks are possibly lost in loss record 6,834 of 6,978 +==4075190== at 0x4C3721A: calloc (vg_replace_malloc.c:760) +==4075190== by 0x40129EB: _dl_allocate_tls (in /usr/lib64/ld-2.28.so) +==4075190== by 0xADA3DA2: pthread_create@@GLIBC_2.2.5 (in /usr/lib64/libpthread-2.28.so) +==4075190== by 0x9B0DA5: qemu_thread_create (qemu-thread-posix.c:581) +==4075190== by 0x827FA8: kvm_start_vcpu_thread (kvm-accel-ops.c:75) +==4075190== by 0x633672: qemu_init_vcpu (cpus.c:642) +==4075190== by 0x722EA7: x86_cpu_realizefn (cpu.c:7430) +==4075190== by 0x833E2E: device_set_realized (qdev.c:510) +==4075190== by 0x8371D5: property_set_bool (object.c:2299) +==4075190== by 0x839512: object_property_set (object.c:1434) +==4075190== by 0x83C58E: object_property_set_qobject (qom-qobject.c:28) +==4075190== by 0x839783: object_property_set_bool (object.c:1503) +``` + +If we do vcpu hotplug and hot unplug for virtual machine continuously, the virtual memory and RES memory of qemu is increasing. +Steps to reproduce: +1. start qemu： +valgrind --tool=memcheck --leak-check=full /home/qemu-system-x86_64 -accel kvm -cpu host -m 4G -smp 4,maxcpus=64,sockets=8,dies=1,cores=8,threads=1 -drive file=/home/centosx861.qcow2,if=none,id=drive0,cache=none -device virtio-blk,drive=drive0,bootindex=1 -monitor stdio -vnc :0 +2. after boot successful +ctl+c kill qemu + +``` +==4075190== 1,776 bytes in 3 blocks are possibly lost in loss record 6,778 of 6,978 +==4075190== at 0x4C3721A: calloc (vg_replace_malloc.c:760) +==4075190== by 0x40129EB: _dl_allocate_tls (in /usr/lib64/ld-2.28.so) +==4075190== by 0xADA3DA2: pthread_create@@GLIBC_2.2.5 (in /usr/lib64/libpthread-2.28.so) +==4075190== by 0x9B0DA5: qemu_thread_create (qemu-thread-posix.c:581) +==4075190== by 0x9C470C: do_spawn_thread (thread-pool.c:145) +==4075190== by 0x9C47C0: worker_thread (thread-pool.c:82) +==4075190== by 0x9AFD89: qemu_thread_start (qemu-thread-posix.c:541) +==4075190== by 0xADA3149: start_thread (in /usr/lib64/libpthread-2.28.so) +==4075190== by 0xB0B7DC2: clone (in /usr/lib64/libc-2.28.so) +==4075190== +==4075190== 2,368 bytes in 4 blocks are possibly lost in loss record 6,834 of 6,978 +==4075190== at 0x4C3721A: calloc (vg_replace_malloc.c:760) +==4075190== by 0x40129EB: _dl_allocate_tls (in /usr/lib64/ld-2.28.so) +==4075190== by 0xADA3DA2: pthread_create@@GLIBC_2.2.5 (in /usr/lib64/libpthread-2.28.so) +==4075190== by 0x9B0DA5: qemu_thread_create (qemu-thread-posix.c:581) +==4075190== by 0x827FA8: kvm_start_vcpu_thread (kvm-accel-ops.c:75) +==4075190== by 0x633672: qemu_init_vcpu (cpus.c:642) +==4075190== by 0x722EA7: x86_cpu_realizefn (cpu.c:7430) +==4075190== by 0x833E2E: device_set_realized (qdev.c:510) +==4075190== by 0x8371D5: property_set_bool (object.c:2299) +==4075190== by 0x839512: object_property_set (object.c:1434) +==4075190== by 0x83C58E: object_property_set_qobject (qom-qobject.c:28) +==4075190== by 0x839783: object_property_set_bool (object.c:1503) +``` +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1929 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1929 new file mode 100644 index 000000000..4b98489b3 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1929 @@ -0,0 +1,21 @@ +regression: 7.0.0 breaks registering process subreaper on Apple silicon +Description of problem: +When running any container on the QEMU virtual guest that is using a utility like `tini` which is trying to register itself as a process subreaper I get an error message like this: + +``` +[FATAL tini (1)] PR_SET_CHILD_SUBREAPER is unavailable on this platform. Are you using Linux >= 3.4? +``` + +The issue has been observed by multiple people on Apple silicon Macs, e.g. in these issues: +https://github.com/docker/for-mac/issues/6620#issuecomment-1694380189 +https://github.com/GoogleCloudPlatform/spark-on-k8s-operator/issues/1735 +Steps to reproduce: +1. Install QEMU 7.0.0+ on an Apple silicon MAC +2. Run a virtual guest +3. Try to register a process subreaper, e.g. like `tini -s` does +Additional information: +the issue was introduced in QEMU 7.0.0 with this commit: +https://gitlab.com/qemu-project/qemu/-/commit/220717a6f46a99031a5b1af964bbf4dec1310440 + +tini readme talking about process subreaping: +https://github.com/krallin/tini#subreaping diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1930 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1930 new file mode 100644 index 000000000..c0d76b306 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1930 @@ -0,0 +1,46 @@ +qemu-aarch64 results in segmentation fault while running a test binary compiled for QNX +Description of problem: +We have cross compiled a simple hello world program for QNX SDP 7.1.0 on Ubuntu Focal x86_64. Running the binary using qemu-aarch64 results in segmentation fault error. + +``` + $ qemu-aarch64 -L /home/vsts/qnx710/target/qnx7/aarch64le ./hello-world + qemu: uncaught target signal 11 (Segmentation fault) - core dumped + Segmentation fault (core dumped) +``` + +We also tried Ubuntu Jammy which has qemu-aarch64 v6.2.0 but got the same error. +Can you tell us how we can emulate the binary using QEMU emulator that is built for QNX on x86_64 platform? Any help would be much appreciated. +Steps to reproduce: +1. Download QNX SDP from QNX software center https://www.qnx.com/download/group.html?programid=29178. +2. Write a simple hello world program. + +``` + #include <stdio.h> + + int main(void) { + return printf("Hello World!"); + } +``` + +3. Source QNX SDP to set some environment variables. + + `$ source ./qnx710/qnxsdp-env.sh` + +4. Compile using the QNX compiler. + + `$ qcc -Vgcc_ntoaarch64le -o hello-world hello-world.c` + +5. Running the binary as it is results to: + +``` + $ ./hello-world + aarch64-binfmt-P: Could not open '/usr/lib/ldqnx-64.so.2': No such file or directory +``` + +5. Running using QEMU emulator results to segmentation fault. + +``` + $ qemu-aarch64 -L /home/vsts/qnx710/target/qnx7/aarch64le ./hello-world + qemu: uncaught target signal 11 (Segmentation fault) - core dumped + Segmentation fault (core dumped) +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1931 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1931 new file mode 100644 index 000000000..efe28140e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1931 @@ -0,0 +1,3 @@ +dbus: Support multiple QEMU instances +Additional information: +cc @marcandre.lureau diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1933 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1933 new file mode 100644 index 000000000..56c737931 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1933 @@ -0,0 +1,41 @@ +qemu 8.1.1 and 7.2.6 live migration with qcow2 attached to vm using postcopy crashes +Description of problem: +Live migrating a vm with a qcow2 disk attached using postcopy will cause vm to crash during migration. +Steps to reproduce: +1. Create a generic vm and attach a qcow2 file to the vm. +<disk type='file' device='disk'> + <driver name='qemu' type='qcow2' cache='none'/> + <source file='/var/lib/libvirt/images/jlow2.qcow2'/> + <target dev='vda' bus='virtio'/> + <boot order='1'/> +</disk> + +2. virsh migrate jlow2 --change-protection --persistent --live --verbose --undefinesource --abort-on-error --postcopy --postcopy-after-precopy --timeout 1 --timeout-postcopy qemu+tcp://10.18.64.118/system + +vm will start migrating and then pause on the source and be shut down on the target once migration switches to postcopy + +Migration: [33.08 %]error: internal error: QEMU unexpectedly closed the monitor (vm='jlow2'): 2023-10-12T06:23:44.354387Z qemu-system-x86_64: warning: TSC frequency mismatch between VM (2892749 kHz) and host (2799999 kHz), and TSC scaling unavailable +2023-10-12T06:23:44.354538Z qemu-system-x86_64: warning: TSC frequency mismatch between VM (2892749 kHz) and host (2799999 kHz), and TSC scaling unavailable +qemu-system-x86_64: ../block/qcow2.c:5257: qcow2_get_specific_info: Assertion `false' failed. + + +Logs from source + +2023-10-12 06:23:43.412+0000: initiating migration + +2023-10-12T06:23:44.362392Z qemu-system-x86_64: failed to save SaveStateEntry with id(name): 3(ram): -5 + +2023-10-12T06:23:44.362485Z qemu-system-x86_64: Detected IO failure for postcopy. Migration paused. + +Logs from target + +2023-10-12T06:23:44.354387Z qemu-system-x86_64: warning: TSC frequency mismatch between VM (2892749 kHz) and host (2799999 kHz), and TSC scaling unavailable + +2023-10-12T06:23:44.354538Z qemu-system-x86_64: warning: TSC frequency mismatch between VM (2892749 kHz) and host (2799999 kHz), and TSC scaling unavailable + +qemu-system-x86_64: ../block/qcow2.c:5257: qcow2_get_specific_info: Assertion `false' failed. +2023-10-12 06:23:44.408+0000: shutting down, reason=failed + +If postcopy is disabled with command below, migration will succeed: + +virsh migrate jlow2 --change-protection --persistent --live --verbose --undefinesource --abort-on-error qemu+tcp://10.18.64.118/system diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1935 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1935 new file mode 100644 index 000000000..8eba8784f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1935 @@ -0,0 +1,5 @@ +migrate problem when add SCSI reservations with iSCSI backed disks +Description of problem: +When performing migrations with QEMU using iSCSI as the backend, it's common for the migration to start successfully. However, in scenarios where Persistent Reservations are added in the guest, the target host, under the precopy mode, preempts the Persistent Reservations right from the beginning, causing migration issues. Is there a way to control the Persistent Reservations lock within QEMU at an appropriate time, ensuring that it's only preempted during the switchover phase？ + +Isn't libiscsi thread-safe? Can multiple threads operate on Persistent Reservations lock simultaneously? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1937 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1937 new file mode 100644 index 000000000..e4983ab7e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1937 @@ -0,0 +1,11 @@ +Live migration with TLS fail (GNUTLS AUTO_REKEY) +Description of problem: +Live migration with TLS fail in postcopy stage when: + +# +Steps to reproduce: +1. run VM with heavy RAM load: `nohup stress-ng --vm 6 --vm-bytes 12G &` +2. run precopy for more that 80sec +3. switch into post-copy stage +Additional information: +This only occurs with TLS transport, if clear qemu+tcp is used then everything works. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1939 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1939 new file mode 100644 index 000000000..9368672ab --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1939 @@ -0,0 +1,64 @@ +qemu master git can no longer be compiled under MacOs Sonoma 14.0 +Description of problem: + +Steps to reproduce: +Qemu master git fails to compile under MacOs M1/2, I already tested it with "git-bisect" "git bisect good" and "git bisect bad".All dependencies for qemu are fulfilled and were installed using Homebrew under MacOs.It fails with these commits: + + +`>>>>> commit 7c3fb52bcdaef85b15a91b3ca4d1516f9d9b5402 +>>>>> Author: Paolo Bonzini <pbonzini@redhat.com> +>>>>> Date: Tue Aug 8 20:28:25 2023 +0200 +>>>>> +>>>>> configure: never use PyPI for Meson +>>>>> +>>>>> Since there is a vendored copy, there is no point in choosing +>> online +>>>> +>>>>> operation. +>>>>> +>>>>> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> +>> +>>>>> +>>>>> configure | 6 ------ +>>>>> 1 file changed, 6 deletions(-) +>>>>>` +Additional information: +Older sources Qemu 8.1 can be compiled without problems. The only thing that has changed is that I did a major system update and Xcode was also updated. Since then compiling on qemu master version 8.1.50 breaks. + +``` +`On branch master +Your branch is up to date with 'origin/master'. + +nothing to commit, working tree clean +Mac-Studio qemu % ./configure --target-list=ppc-softmmu +Using './build' as the directory for build output +python determined to be '/Library/Frameworks/Python.framework/Versions/3.10/bin/python3' +python version: Python 3.10.8 +mkvenv: Creating non-isolated virtual environment at 'pyvenv' +mkvenv: checking for tomli>=1.2.0 +mkvenv: installing tomli>=1.2.0 +mkvenv: checking for meson>=0.63.0 +mkvenv: installing meson==0.63.3 +mkvenv: checking for sphinx>=1.6 +mkvenv: checking for sphinx_rtd_theme>=0.5 + +'sphinx==5.3.0' not found: +• Python package 'sphinx' was not found nor installed. +• mkvenv was configured to operate offline and did not check PyPI. + + +Sphinx not found/usable, disabling docs. +Disabling PIE due to missing toolchain support +The Meson build system +Version: 0.63.3 +Source dir: /Users/qemu +Build dir: /Users/qemu/build +Build type: native build +Project name: qemu +Project version: 8.1.50 + +../meson.build:1:0: ERROR: Unable to detect linker for compiler `cc -Wl,--version` +stdout: +stderr: ld: unknown options: --version +clang: error: linker command failed with exit code 1 (use -v to see invocation)` +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/194 b/gitlab/issues_text/target_missing/host_missing/accel_missing/194 new file mode 100644 index 000000000..6fce8d2da --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/194 @@ -0,0 +1 @@ +Qemu fails to start with error " There is no option group 'spice'" diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1940 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1940 new file mode 100644 index 000000000..df077593b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1940 @@ -0,0 +1,20 @@ +Saving vm with shared folder results in Error: State blocked by non-migratable device '000.../vhost-user-fs' +Description of problem: +Saving a vm with savevm in the QEMU Monitor with a shared folder causes the following error message: +`Error: State blocked by non-migratable device '0000:00:05.0/vhost-user-fs'` +Steps to reproduce: +1. Get an qcow2 image that can boot (not sure if working qcow2 image is actually needed) +2. Start virtiofsd with this /usr/libexec/virtiofsd --socket-path=/tmp/virtiofs_socket -o source=/path/to/share +3. Run qemu-system-x86_64 -m 4G -object memory-backend-file,id=mem,size=4G,mem-path=/dev/shm,share=on -numa node,memdev=mem -smp 2 -hda image.qcow2 -vga qxl -virtfs local,path=/path/to/share,mount_tag=share,security_model=passthrough,id=virtiofs -chardev socket,id=char0,path=/tmp/virtiofs_socket -device vhost-user-fs-pci,queue-size=1024,chardev=char0,tag=share +4. Let the image boot and/or go into the QEMU monitor. +5. type savevm testvm +6. See error. +Additional information: +This happens with both the legacy virtio-fs and the rust version. + +According to the first reply to https://gitlab.com/virtio-fs/virtiofsd/-/issues/81 there needs to be "a lot of changes not only in virtiofsd but also in the rust-vmm crates and qemu (and maybe in the vhost-user protocol)" so I'm reporting this here in the hopes it will speed something up. + +I followed the following to get virtiofsd working with command line QEMU: +https://github.com/virtio-win/kvm-guest-drivers-windows/wiki/Virtiofs:-Shared-file-system + +This is blocking our migration from VirtualBox because it doesn't have problems like this. The least I need is a work around or alternative shared filesystem. We are trying to avoid networked shares. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1943 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1943 new file mode 100644 index 000000000..c44870bcf --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1943 @@ -0,0 +1,24 @@ +Weird error trying to autodetect CHS disk geometry +Description of problem: +Error: "SSD Read Error" + +Something about the contents of the disk causes qemu to wildly misdetect the disk geometry. +This disk started as a blank disk, and had a FAT filesystem written to it from inside it; thus +writing the detected geometry to the disk. And this caused the detected geometry to change to +something nonsensical. +Steps to reproduce: +1. Unpack the attached [hd.bz2](/uploads/53f5bb00cdd563223bea1f7a0f86fe1c/hd.bz2) to hd.img +2. Run qemu -hda hd.img +3. Observe error +Additional information: +The following command appears to fix the problem; however it is wrong: + +qemu -drive if=none,id=dr,file=hd.img -device ide-hd,drive=dr,cyls=1023,heads=16,secs=63 + +The problem with this command is this command yields only 504MB instead of the 512MB the +disk is actually formatted to be. CHS translation should be enabled on this disk but won't +be with this command. + +This command was copied essentially blindly from "Removed features" because that's what comes +up for a google search for "qemu specify geometry" and I don't understand the command well +enough to correct it. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1944 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1944 new file mode 100644 index 000000000..0f678ba7d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1944 @@ -0,0 +1,71 @@ +Deadlock on snapshot removal (bdrv_graph_wrlock) +Description of problem: +VM was hanging during snapshot removal. +There was an attempt to shutdown the VM, but that did hang. + +gdb shows me: +``` +(gdb) bt full +#0 0x00007f20493427fe in __ppoll (fds=0x557e630718b0, nfds=2, timeout=<optimized out>, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:43 + sc_ret = -514 + sc_cancel_oldtype = 0 + sc_ret = <optimized out> + tval = {tv_sec = 139776632323420, tv_nsec = 139776632323432} +#1 0x0000557e619cab52 in fdmon_poll_wait.llvm () +No symbol table info available. +#2 0x0000557e619ca0b6 in aio_poll () +No symbol table info available. +#3 0x0000557e61801651 in bdrv_graph_wrlock () +No symbol table info available. +#4 0x0000557e617c873b in bdrv_replace_child_noperm.llvm () +No symbol table info available. +#5 0x0000557e617c8601 in bdrv_root_unref_child () +No symbol table info available. +#6 0x0000557e617f6333 in blk_unref () +No symbol table info available. +#7 0x0000557e6181b0d1 in mirror_exit_common () +No symbol table info available. +#8 0x0000557e617dbdb4 in job_do_finalize_locked.llvm () +No symbol table info available. +#9 0x0000557e617dd72b in job_exit () +No symbol table info available. +#10 0x0000557e619e5101 in aio_bh_poll () +No symbol table info available. +#11 0x0000557e619c95a4 in aio_dispatch () +No symbol table info available. +#12 0x0000557e619e655f in aio_ctx_dispatch () +No symbol table info available. +#13 0x00007f2049546e2f in g_main_dispatch (context=0x557e62ecebd0) at ../glib/gmain.c:3337 + dispatch = 0x557e619e6550 <aio_ctx_dispatch> + prev_source = 0x0 + begin_time_nsec = 232172181173336 + was_in_call = <optimized out> + user_data = 0x0 + callback = 0x0 + cb_funcs = 0x0 + cb_data = 0x0 + need_destroy = <optimized out> + source = 0x557e62ec73e0 + current = 0x557e63e4b600 + i = 0 + __func__ = {<optimized out> <repeats 16 times>} +#14 g_main_context_dispatch (context=0x557e62ecebd0) at ../glib/gmain.c:4055 +No locals. +#15 0x0000557e619e74be in main_loop_wait () +No symbol table info available. +#16 0x0000557e615201e7 in qemu_main_loop () +No symbol table info available. +#17 0x0000557e61374c6a in qemu_default_main () +No symbol table info available. +#18 0x00007f204923feb0 in __libc_start_call_main (main=main@entry=0x557e61374c80 <main>, argc=argc@entry=153, argv=argv@entry=0x7ffe07495238) at ../sysdeps/nptl/libc_start_call_main.h:58 + self = <optimized out> + result = <optimized out> + unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0, -6145724763479124305, 140729020666424, 94001285254272, 94001294953808, 139776661151744, 6145708635144279727, 6121919821307926191}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x7f204954cb41 <g_malloc0+33>, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 1230293825}}} + not_first_call = <optimized out> +#19 0x00007f204923ff60 in __libc_start_main_impl (main=0x557e61374c80 <main>, argc=153, argv=0x7ffe07495238, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffe07495228) at ../csu/libc-start.c:389 +No locals. +#20 0x0000557e613743d5 in _start () +No symbol table info available. +``` +Steps to reproduce: +Still trying to reproduce in lab. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1949 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1949 new file mode 100644 index 000000000..d7a5e7db3 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1949 @@ -0,0 +1,12 @@ +chardev zombie TCP session +Description of problem: +When user terminates TCP session ungracefully (eg: power-cycle or network cable disconnect), the TCP session keeps in established status forever. In this state, new sessions can't access the chardev, since the zombie TCP session keeps exclusive access to chardev. +Steps to reproduce: +1.Establish client session to chardev TCP socket. +2.Power-off the client machine. +3.Establish a new client session +4.Observe that old TCP session is never killed and new session can connect but not interact with chardev. +Additional information: +Suggestions to resolve this and improve the chardev feature: +- enable TCP keep-alive for chardev server. +- allow multiple client sessions concurrently, where chardev output is broadcasted to all client sessions, and chardev input is shared by all clients. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/195 b/gitlab/issues_text/target_missing/host_missing/accel_missing/195 new file mode 100644 index 000000000..e0f9d8a5a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/195 @@ -0,0 +1 @@ +wavcapture does not record silence diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1951 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1951 new file mode 100644 index 000000000..dfbc54fa9 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1951 @@ -0,0 +1,138 @@ +MacOS requires root to pass through USB devices properly +Description of problem: +If I run qemu as a normal user, the PlutoSDR USB device will not work in the VM. For example, the umass device will remain attached to the host system, and will not appear in the guest system. The device will appear in the guest system, but it will fail to be configured: +``` +usb_alloc_device: Failure selecting configuration index 0:USB_ERR_STALLED, port 2, addr 2 (ignored) +``` + +I believe that similar issues are happening w/ guest OS's Ubuntu 20.04 and 22.04, but I have not tested them to confirm. + +There is no error message (that I noticed) that reports that this might be an issue and that you need to run qemu as root. +Steps to reproduce: +1. Run qemu like above +2. Plug in a PlutoSDR +3. See that the device appears in the guest, but does not attach completely +Additional information: +The confusing part is that a simple device, an RTL-SDR device will appear to work fine when passed through w/o running as root making things more confusing to debug. + +When run qemu as a normal user, the console (includes FreeBSD kernel messages: +``` +login: qemu-system-aarch64: libusb_detach_kernel_driver: -3 [ACCESS] +qemu-system-aarch64: libusb_detach_kernel_driver: -3 [ACCESS] +qemu-system-aarch64: libusb_detach_kernel_driver: -3 [ACCESS] +qemu-system-aarch64: libusb_detach_kernel_driver: -3 [ACCESS] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_detach_kernel_driver: -3 [ACCESS] +qemu-system-aarch64: libusb_detach_kernel_driver: -3 [ACCESS] +qemu-system-aarch64: libusb_detach_kernel_driver: -3 [ACCESS] +qemu-system-aarch64: libusb_detach_kernel_driver: -3 [ACCESS] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_detach_kernel_driver: -3 [ACCESS] +qemu-system-aarch64: libusb_detach_kernel_driver: -3 [ACCESS] +qemu-system-aarch64: libusb_detach_kernel_driver: -3 [ACCESS] +qemu-system-aarch64: libusb_detach_kernel_driver: -3 [ACCESS] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +usb_alloc_device: Failure selecting configuration index 0:USB_ERR_STALLED, port 2, addr 2 (ignored) +ugen1.2: <Analog Devices Inc. PlutoSDR (ADALM-PLUTO)> at usbus1 +qemu-system-aarch64: libusb_detach_kernel_driver: -3 [ACCESS] +qemu-system-aarch64: libusb_detach_kernel_driver: -3 [ACCESS] +qemu-system-aarch64: libusb_detach_kernel_driver: -3 [ACCESS] +qemu-system-aarch64: libusb_detach_kernel_driver: -3 [ACCESS] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_detach_kernel_driver: -3 [ACCESS] +qemu-system-aarch64: libusb_detach_kernel_driver: -3 [ACCESS] +qemu-system-aarch64: libusb_detach_kernel_driver: -3 [ACCESS] +qemu-system-aarch64: libusb_detach_kernel_driver: -3 [ACCESS] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +``` + +It's not clear what action, if any needs to be taken w/ these error messages. At a minimum, qemu should complain loudly about needing to be run as root, but would be best if it didn't need to run as root, like other VM systems. + +If I run qemu as root (via sudo), it attachs as expected: +``` +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +qemu-system-aarch64: libusb_kernel_driver_active: -5 [NOT_FOUND] +ugen1.2: <Analog Devices Inc. PlutoSDR (ADALM-PLUTO)> at usbus1 +umass0 on uhub0 +umass0: <Mass Storage> on usbus1 +umass0: SCSI over Bulk-Only; quirks = 0x0000 +umass0:0:0: Attached to scbus0 +da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 +da0: <Linux File-Stor Gadget 0414> Removable Direct Access SCSI-2 device +da0: 40.000MB/s transfers +da0: 30MB (61441 512 byte sectors) +da0: quirks=0x2<NO_6_BYTE> +urndis0 on uhub0 +urndis0: <RNDIS Communications Control> on usbus1 +umodem0 on uhub0 +umodem0: <CDC Abstract Control Model (ACM)> on usbus1 +umodem0: data interface 4, has no CM over data, has no break +``` + +Trying root was inspired by: +https://github.com/libusb/libusb/issues/1014 + +From that issue, it appears that this is a qemu build issue and does not have the proper entitlements. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1954 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1954 new file mode 100644 index 000000000..35076404a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1954 @@ -0,0 +1,28 @@ +guest-fsfreeze can't work well on windows +Description of problem: +I used qemu 5.0 to cross-compile windows gqa on the fedroa30 system.And install it on guest with windows10,but i can't work well. +Steps to reproduce: +1. ./configure --cross-prefix=x86_64-w64-mingw32- --enable-guest-agent-msi --with-vss-sdk=/root/vssdk/VSSSDK72 + + my vssdk download from:[vssdk](https://www.microsoft.com/en-us/download/details.aspx?id=23490),i install it on my pc and copy to /root/vssdk/VSSSDK72 + +2. make qemu-ga -j4 + +3. and then install qemu-ga-x86_64.msi on windows10,it report the error: +  + +4.then I ./configure not with "--with-vss-sdk",the qemu-ga-x86_64.msi can install successfully. + +5.So, I install gga first. Then ./configure with "--with-vss-sdk" to make get the qemu-ga.exe + +6.replace qemu-ga.exe and reboot gga service,then execute the command "virsh domfsfreeze" on host,but it report error: + + error: Unable to freeze filesystems + error: internal error: unable to execute QEMU agent command 'guest-fsfreeze-freeze': failed to add \\?\Volume{d1ee1072-0000-0000-0000-100000000000}\ to snapshot set: + + +**I looked at the windows Event Viewer,it get the error:** + + Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005, Access is denied. + +I have referred to this [document](https://www.ryadel.com/en/volume-shadow-copy-service-error-unexpected-error-querying-for-the-ivsswritercallback-interface-how-to-fix-that/),but it not work. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1957 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1957 new file mode 100644 index 000000000..ea997db39 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1957 @@ -0,0 +1,20 @@ +Reading files failed from QEMU TFTP server +Description of problem: +QEMU TFTP server on Linux is sensitive to the filename delimiters: + +After building QEMU UEFI firmware with the entire NetworkPkg stack and booting to UEFI shell, one can use `tftp` command to read files from the QEMU TFTP server specified during QEMU launching. i.e. `tftp 10.0.2.2 Boot\BCD`. However, when setting up the TFTP folder to be exactly the same (Linux and Windows), the result for running this command is different. On Windows host, this tftp command from emulated UEFI shell will proceed properly. But on Linux host, this will fail with "File Not Found". + +The issue seems to be around the slirp engine used by QEMU: the received packet will hand off to slirp as is, which leads to a host specific libc implementation of "open" function call: https://git.launchpad.net/ubuntu/+source/libslirp/tree/src/tftp.c#n113. Thus the server result would be different when the host is different. + +This will cause the PXE boot to fail when setting up the PXE folder on through QEMU on Linux because Windows will attempt to read BCD file at the same directory of the initial boot file, with a `\` in between. + +As TFTP protocol seems to be folder agnostic (just file names), in this case, should the TFTP server (QEMU here) handle the path normalization to make sure the file lookup to go through? Otherwise, Windows PXE boot on QEMU Linux host will always fail. + +Any suggestion here? Thanks in advance! +Steps to reproduce: +1. Build OVMF UEFI with full network stack +2. Launch QEMU with the built UEFI with nic enabled, boot to UEFI shell. +3. Invoke `tftp 10.0.2.2 Boot\BCD` from UEFI shell. +4. When performing step 1-3 on Windows, this will succeed. But on Linux, this will fail with "File Not Found" +Additional information: +Attached is a wireshark dump from QEMU on Linux host. The same command sequence will all be successful on Windows host. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1959 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1959 new file mode 100644 index 000000000..f8cfeb416 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1959 @@ -0,0 +1 @@ +qemu-img: support ZSTD compression level customization diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/196 b/gitlab/issues_text/target_missing/host_missing/accel_missing/196 new file mode 100644 index 000000000..026a90a3f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/196 @@ -0,0 +1 @@ +Improve UX for macOS when launching from a fullscreen app diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1962 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1962 new file mode 100644 index 000000000..e5623d19f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1962 @@ -0,0 +1,29 @@ +systemd-tmpfiles-setup-dev-early.service fails in emulated systemd-nspawn container +Description of problem: +When booting a fresh `debootstrap`ed Debian Trixie/testing rootfs with foreign architecture via `systemd-nspawn` and `qemu-user-static`, invoked via `systemd-binfmt`, the `systemd-tmpfiles-setup-dev-early.service` service within the guest fails, which leads to `/dev` not existing (respectively no default content), so that several other guest system components fail as well, like any console/shell access: +``` +Starting systemd-tmpfiles-setup-dev-early.service - Create Static Device Nodes in /dev gracefully... +systemd-tmpfiles-setup-dev-early.service: Failed to set up credentials: Invalid argument +systemd-tmpfiles-setup-dev-early.service: Main process exited, code=exited, status=243/CREDENTIALS +systemd-tmpfiles-setup-dev-early.service: Failed with result 'exit-code'. +[FAILED] Failed to start systemd-tmpfiles-setup-dev-early.service - Create Static Device Nodes in /dev gracefully. +See 'systemctl status systemd-tmpfiles-setup-dev-early.service' for details. +Starting systemd-tmpfiles-setup-dev.service - Create Static Device Nodes in /dev... +systemd-tmpfiles-setup-dev.service: Failed to set up credentials: Invalid argument +systemd-tmpfiles-setup-dev.service: Main process exited, code=exited, status=243/CREDENTIALS +systemd-tmpfiles-setup-dev.service: Failed with result 'exit-code'. +[FAILED] Failed to start systemd-tmpfiles-setup-dev.service - Create Static Device Nodes in /dev. +See 'systemctl status systemd-tmpfiles-setup-dev.service' for details. +``` +Steps to reproduce: +1. `apt install debootstrap systemd-container qemu-user-static` +2. `systemctl restart systemd-binfmt` +3. `mkdir rootfs` +4. `debootstrap --variant=minbase --include=systemd-sysv --arch=arm64 trixie ./rootfs 'https://deb.debian.org/debian'` +5. `systemd-nspawn -bD rootfs` +Additional information: +On Bookworm guest systems and/or without QEMU emulation, this works without issues, so I guess systemd recently started to use a certain syscall for the `ImportCredential=tmpfiles.*` method in systemd units, which is not supported by QEMU, probably similar to https://github.com/systemd/systemd/pull/28954? + +I hope it is fine to report it here. Always difficult to decide whether to report to the distribution (Debian) or one, and in case which, of the related projects, which do not work together. + +Debian Trixie currently ships `systemd 254.4-1` btw. I am not sure whether the issue was introduced with 253 or 254, since the linked issue prevented booting such containers on an earlier stage with 253, which was fixed in 254, which has the here reported issue. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1963 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1963 new file mode 100644 index 000000000..08d34929e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1963 @@ -0,0 +1,28 @@ +EOF is not detected, when semihosting is reading from stdin +Description of problem: +QEMU hangs. +Steps to reproduce: +1. Run the program with stdin from a pipe. +Additional information: +The code is compiled from this source: +``` +#include <stdio.h> + +int main(int argc, char** argv) { + int i = -1; + int result = scanf("%d", &i); + printf("result = %d, i = %d\n", result, i); + return 0; +} +``` +compiled with GCC and picolibc: +``` +arm-none-eabi-gcc --specs=picolibc.specs -march=armv7-m ~/sources/picolibc/git/test-stdin.c -o test-stdin -lc -lsemihost --crt0=hosted -O0 -g +``` +[test-stdin](/uploads/dbd2650c8e0aaca353fd7630ac9c8440/test-stdin) +The execution hangs at semihosting SYS_READC(0x7) call: +``` + movs r0, #7 +(...) + bkpt #0xab +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1967 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1967 new file mode 100644 index 000000000..ecee5be41 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1967 @@ -0,0 +1 @@ +Guest SIGRTMIN remapped incorrectly diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1968 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1968 new file mode 100644 index 000000000..ae09d2aae --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1968 @@ -0,0 +1 @@ +scripts (checkpatch): make braces {} necessary for 'for' loops diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1969 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1969 new file mode 100644 index 000000000..1bbd1a2bf --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1969 @@ -0,0 +1 @@ +Test fails with SIGSEGV because of use-after-free diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1971 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1971 new file mode 100644 index 000000000..8f0c1a9c2 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1971 @@ -0,0 +1,148 @@ +Cannot build QEMU on MSYS2 on Windows 10 22H2 +Description of problem: +I have followed build instructions on Wiki, section Native builds with MSYS2. MSYS2 and other tools are installed without any errors. But when run `./configure --enable-sdl --enable-gtk`, I have this error that I have never seen before: + +``` +# ./configure --enable-sdl --enable-gtk +Using './build' as the directory for build output +ln: failed to create symbolic link 'aarch64-softmmu/qemu-system-aarch64.exe': No such file or directory +ln: failed to create symbolic link 'alpha-softmmu/qemu-system-alpha.exe': No such file or directory +ln: failed to create symbolic link 'arm-softmmu/qemu-system-arm.exe': No such file or directory +ln: failed to create symbolic link 'avr-softmmu/qemu-system-avr.exe': No such file or directory +ln: failed to create symbolic link 'cris-softmmu/qemu-system-cris.exe': No such file or directory +ln: failed to create symbolic link 'hppa-softmmu/qemu-system-hppa.exe': No such file or directory +ln: failed to create symbolic link 'i386-softmmu/qemu-system-i386.exe': No such file or directory +ln: failed to create symbolic link 'loongarch64-softmmu/qemu-system-loongarch64.exe': No such file or directory +ln: failed to create symbolic link 'm68k-softmmu/qemu-system-m68k.exe': No such file or directory +ln: failed to create symbolic link 'microblaze-softmmu/qemu-system-microblaze.exe': No such file or directory +ln: failed to create symbolic link 'microblazeel-softmmu/qemu-system-microblazeel.exe': No such file or directory +ln: failed to create symbolic link 'mips-softmmu/qemu-system-mips.exe': No such file or directory +ln: failed to create symbolic link 'mips64-softmmu/qemu-system-mips64.exe': No such file or directory +ln: failed to create symbolic link 'mips64el-softmmu/qemu-system-mips64el.exe': No such file or directory +ln: failed to create symbolic link 'mipsel-softmmu/qemu-system-mipsel.exe': No such file or directory +ln: failed to create symbolic link 'nios2-softmmu/qemu-system-nios2.exe': No such file or directory +ln: failed to create symbolic link 'or1k-softmmu/qemu-system-or1k.exe': No such file or directory +ln: failed to create symbolic link 'ppc-softmmu/qemu-system-ppc.exe': No such file or directory +ln: failed to create symbolic link 'ppc64-softmmu/qemu-system-ppc64.exe': No such file or directory +ln: failed to create symbolic link 'riscv32-softmmu/qemu-system-riscv32.exe': No such file or directory +ln: failed to create symbolic link 'riscv64-softmmu/qemu-system-riscv64.exe': No such file or directory +ln: failed to create symbolic link 'rx-softmmu/qemu-system-rx.exe': No such file or directory +ln: failed to create symbolic link 's390x-softmmu/qemu-system-s390x.exe': No such file or directory +ln: failed to create symbolic link 'sh4-softmmu/qemu-system-sh4.exe': No such file or directory +ln: failed to create symbolic link 'sh4eb-softmmu/qemu-system-sh4eb.exe': No such file or directory +ln: failed to create symbolic link 'sparc-softmmu/qemu-system-sparc.exe': No such file or directory +ln: failed to create symbolic link 'sparc64-softmmu/qemu-system-sparc64.exe': No such file or directory +ln: failed to create symbolic link 'tricore-softmmu/qemu-system-tricore.exe': No such file or directory +ln: failed to create symbolic link 'x86_64-softmmu/qemu-system-x86_64.exe': No such file or directory +ln: failed to create symbolic link 'xtensa-softmmu/qemu-system-xtensa.exe': No such file or directory +ln: failed to create symbolic link 'xtensaeb-softmmu/qemu-system-xtensaeb.exe': No such file or directory +The Meson build system +Version: 1.2.3 +Source dir: C:/msys64/home/DuyThanh/qemu-ios +Build dir: C:/msys64/home/DuyThanh/qemu-ios/build +Build type: native build +Project name: qemu +Project version: 7.2.50 +C compiler for the host machine: cc -m64 -mcx16 (gcc 13.2.0 "cc (Rev2, Built by MSYS2 project) 13.2.0") +C linker for the host machine: cc -m64 -mcx16 ld.bfd 2.41 +Host machine cpu family: x86_64 +Host machine cpu: x86_64 +Program scripts/symlink-install-tree.py found: YES (C:/msys64/mingw64/bin/python.exe C:/msys64/home/DuyThanh/qemu-ios/scripts/symlink-install-tree.py) +Program sh found: YES (C:\msys64\usr\bin/sh.EXE) +Program python3 found: YES (C:/msys64/mingw64/bin/python.exe) +Program bzip2 found: YES (C:\msys64\mingw64\bin/bzip2.EXE) +Program iasl found: NO +Compiler for C supports link arguments -Wl,-z,relro: NO +Compiler for C supports link arguments -Wl,-z,now: NO +Compiler for C supports link arguments -Wl,--no-seh: YES +Compiler for C supports link arguments -Wl,--nxcompat: YES +C++ compiler for the host machine: c++ -m64 -mcx16 (gcc 13.2.0 "c++ (Rev2, Built by MSYS2 project) 13.2.0") +C++ linker for the host machine: c++ -m64 -mcx16 ld.bfd 2.41 +Compiler for C++ supports link arguments -Wl,--warn-common: YES +Program cgcc found: NO +Library m found: YES +Run-time dependency threads found: YES +Traceback (most recent call last): + File "C:/msys64/mingw64/lib/python3.11/site-packages/mesonbuild/mesonmain.py", line 194, in run + return options.run_func(options) + ^^^^^^^^^^^^^^^^^^^^^^^^^ + File "C:/msys64/mingw64/lib/python3.11/site-packages/mesonbuild/msetup.py", line 358, in run + app.generate() + File "C:/msys64/mingw64/lib/python3.11/site-packages/mesonbuild/msetup.py", line 183, in generate + return self._generate(env, capture, vslite_ctx) + ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + File "C:/msys64/mingw64/lib/python3.11/site-packages/mesonbuild/msetup.py", line 228, in _generate + intr.run() + File "C:/msys64/mingw64/lib/python3.11/site-packages/mesonbuild/interpreter/interpreter.py", line 3002, in run + super().run() + File "C:/msys64/mingw64/lib/python3.11/site-packages/mesonbuild/interpreterbase/interpreterbase.py", line 164, in run + self.evaluate_codeblock(self.ast, start=1) + File "C:/msys64/mingw64/lib/python3.11/site-packages/mesonbuild/interpreterbase/interpreterbase.py", line 190, in evaluate_codeblock + raise e + File "C:/msys64/mingw64/lib/python3.11/site-packages/mesonbuild/interpreterbase/interpreterbase.py", line 182, in evaluate_codeblock + self.evaluate_statement(cur) + File "C:/msys64/mingw64/lib/python3.11/site-packages/mesonbuild/interpreterbase/interpreterbase.py", line 198, in evaluate_statement + self.assignment(cur) + File "C:/msys64/mingw64/lib/python3.11/site-packages/mesonbuild/interpreterbase/interpreterbase.py", line 635, in assignment + value = self.evaluate_statement(node.value) + ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + File "C:/msys64/mingw64/lib/python3.11/site-packages/mesonbuild/interpreterbase/interpreterbase.py", line 200, in evaluate_statement + return self.method_call(cur) + ^^^^^^^^^^^^^^^^^^^^^ + File "C:/msys64/mingw64/lib/python3.11/site-packages/mesonbuild/interpreterbase/interpreterbase.py", line 550, in method_call + res = obj.method_call(method_name, args, kwargs) + ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + File "C:/msys64/mingw64/lib/python3.11/site-packages/mesonbuild/interpreterbase/baseobjects.py", line 94, in method_call + return method(args, kwargs) + ^^^^^^^^^^^^^^^^^^^^ + File "C:/msys64/mingw64/lib/python3.11/site-packages/mesonbuild/interpreterbase/decorators.py", line 109, in wrapped + ret = f(*wrapped_args, **wrapped_kwargs) + ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + File "C:/msys64/mingw64/lib/python3.11/site-packages/mesonbuild/interpreterbase/decorators.py", line 277, in wrapper + return f(*nargs, **wrapped_kwargs) + ^^^^^^^^^^^^^^^^^^^^^^^^^^^ + File "C:/msys64/mingw64/lib/python3.11/site-packages/mesonbuild/interpreterbase/decorators.py", line 596, in wrapper + return f(*wrapped_args, **wrapped_kwargs) + ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + File "C:/msys64/mingw64/lib/python3.11/site-packages/mesonbuild/interpreter/compiler.py", line 635, in find_library_method + linkargs = self.compiler.find_library(libname, self.environment, search_dirs, libtype) + ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + File "C:/msys64/mingw64/lib/python3.11/site-packages/mesonbuild/compilers/mixins/clike.py", line 1191, in find_library + return self._find_library_impl(libname, env, extra_dirs, code, libtype, lib_prefix_warning) + ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + File "C:/msys64/mingw64/lib/python3.11/site-packages/mesonbuild/compilers/mixins/clike.py", line 1180, in _find_library_impl + value = self._find_library_real(libname, env, extra_dirs, code, libtype, lib_prefix_warning) + ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + File "C:/msys64/mingw64/lib/python3.11/site-packages/mesonbuild/compilers/mixins/clike.py", line 1158, in _find_library_real + for d in itertools.chain(extra_dirs, self.get_library_dirs(env, elf_class)): + ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + File "C:/msys64/mingw64/lib/python3.11/site-packages/mesonbuild/compilers/mixins/clike.py", line 261, in get_library_dirs + return self._get_library_dirs(env, elf_class).copy() + ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + File "C:/msys64/mingw64/lib/python3.11/site-packages/mesonbuild/compilers/mixins/clike.py", line 220, in _get_library_dirs + dirs = self.get_compiler_dirs(env, 'libraries') + ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + File "C:/msys64/mingw64/lib/python3.11/site-packages/mesonbuild/compilers/mixins/gnu.py", line 515, in get_compiler_dirs + return self._split_fetch_real_dirs(line.split('=', 1)[1]) + ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + File "C:/msys64/mingw64/lib/python3.11/site-packages/mesonbuild/compilers/mixins/gnu.py", line 497, in _split_fetch_real_dirs + if pobj.exists(): + ^^^^^^^^^^^^^ + File "C:/msys64/mingw64/lib/python3.11/pathlib.py", line 1237, in exists + self.stat() + File "C:/msys64/mingw64/lib/python3.11/pathlib.py", line 1015, in stat + return os.stat(self, follow_symlinks=follow_symlinks) + ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +OSError: [WinError 1005] The volume does not contain a recognized file system. +Please make sure that all required file system drivers are loaded and that the volume is not corrupted: 'D:/a/msys64/mingw64/lib/x86_64-w64-mingw32/13.2.0' + +ERROR: Unhandled python OSError. This is probably not a Meson bug, but an issue with your build environment. + +ERROR: meson setup failed +``` +Steps to reproduce: +1. Install MSYS2 and follow the wiki page +2. Git clone +3. Run configure then error +Additional information: +No diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1972 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1972 new file mode 100644 index 000000000..11e722f47 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1972 @@ -0,0 +1,39 @@ +Windows TCG plugin build fails with mingw cross-compile images +Description of problem: +It looks like the mingw variants of the compiler are sensitive to the order of linking: + +``` +bash-5.2$ x86_64-w64-mingw32-gcc -m64 -mcx16 plugins/qemu_plugin_api.lib -o tests/plugin/libinsn.dll tests/plugin/libinsn.dll.p/insn.c.obj tests/plugin/libinsn.dll.p/.._.._contrib_plugins_win32_linker.c.obj plugins/qemu_plugin_api.lib -Wl,--allow-shlib-undefined -shared -Wl,--start-group -Wl,--out-implib=tests/plugin/libinsn.dll.a -fstack-protector-strong -Wl,--no-seh -Wl,--nxcompat -Wl,--dynamicbase -Wl,--high-entropy-va -Wl,--warn-common /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libglib-2.0.dll.a /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libintl.dll.a /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libgmodule-2.0.dll.a -lkernel32 -luser32 -lgdi32 -lwinspool -lshell32 -lole32 -loleaut32 -luuid -lcomdlg32 -ladvapi32 -Wl,--end-group +bash-5.2$ x86_64-w64-mingw32-gcc -m64 -mcx16 plugins/qemu_plugin_api.lib -o tests/plugin/libinsn.dll tests/plugin/libinsn.dll.p/insn.c.obj tests/plugin/libinsn.dll.p/.._.._contrib_plugins_win32_linker.c.obj -Wl,--allow-shlib-undefined -shared -Wl,--start-group -Wl,--out-implib=tests/plugin/libinsn.dll.a -fstack-protector-strong -Wl,--no-seh -Wl,--nxcompat -Wl,--dynamicbase -Wl,--high-entropy-va -Wl,--warn-common /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libglib-2.0.dll.a /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libintl.dll.a /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libgmodule-2.0.dll.a -lkernel32 -luser32 -lgdi32 -lwinspool -lshell32 -lole32 -loleaut32 -luuid -lcomdlg32 -ladvapi32 -Wl,--end-group +/usr/lib/gcc/x86_64-w64-mingw32/12.2.1/../../../../x86_64-w64-mingw32/bin/ld: tests/plugin/libinsn.dll.p/insn.c.obj: in function `vcpu_tb_trans': +/tmp/qemu-test/build/../src/tests/plugin/insn.c:90: undefined reference to `__imp_qemu_plugin_tb_n_insns' +/usr/lib/gcc/x86_64-w64-mingw32/12.2.1/../../../../x86_64-w64-mingw32/bin/ld: /tmp/qemu-test/build/../src/tests/plugin/insn.c:100: undefined reference to `__imp_qemu_plugin_insn_vaddr' +/usr/lib/gcc/x86_64-w64-mingw32/12.2.1/../../../../x86_64-w64-mingw32/bin/ld: /tmp/qemu-test/build/../src/tests/plugin/insn.c:97: undefined reference to `__imp_qemu_plugin_register_vcpu_insn_exec_inline' +/usr/lib/gcc/x86_64-w64-mingw32/12.2.1/../../../../x86_64-w64-mingw32/bin/ld: /tmp/qemu-test/build/../src/tests/plugin/insn.c:94: undefined reference to `__imp_qemu_plugin_tb_get_insn' +/usr/lib/gcc/x86_64-w64-mingw32/12.2.1/../../../../x86_64-w64-mingw32/bin/ld: /tmp/qemu-test/build/../src/tests/plugin/insn.c:101: undefined reference to `__imp_qemu_plugin_register_vcpu_insn_exec_cb' +/usr/lib/gcc/x86_64-w64-mingw32/12.2.1/../../../../x86_64-w64-mingw32/bin/ld: /tmp/qemu-test/build/../src/tests/plugin/insn.c:107: undefined reference to `__imp_qemu_plugin_insn_size' +/usr/lib/gcc/x86_64-w64-mingw32/12.2.1/../../../../x86_64-w64-mingw32/bin/ld: /tmp/qemu-test/build/../src/tests/plugin/insn.c:121: undefined reference to `__imp_qemu_plugin_insn_disas' +/usr/lib/gcc/x86_64-w64-mingw32/12.2.1/../../../../x86_64-w64-mingw32/bin/ld: /tmp/qemu-test/build/../src/tests/plugin/insn.c:130: undefined reference to `__imp_qemu_plugin_register_vcpu_insn_exec_cb' +/usr/lib/gcc/x86_64-w64-mingw32/12.2.1/../../../../x86_64-w64-mingw32/bin/ld: tests/plugin/libinsn.dll.p/insn.c.obj: in function `plugin_exit': +/tmp/qemu-test/build/../src/tests/plugin/insn.c:168: undefined reference to `__imp_qemu_plugin_outs' +/usr/lib/gcc/x86_64-w64-mingw32/12.2.1/../../../../x86_64-w64-mingw32/bin/ld: /tmp/qemu-test/build/../src/tests/plugin/insn.c:168: undefined reference to `__imp_qemu_plugin_outs' +/usr/lib/gcc/x86_64-w64-mingw32/12.2.1/../../../../x86_64-w64-mingw32/bin/ld: /tmp/qemu-test/build/../src/tests/plugin/insn.c:168: undefined reference to `__imp_qemu_plugin_outs' +/usr/lib/gcc/x86_64-w64-mingw32/12.2.1/../../../../x86_64-w64-mingw32/bin/ld: tests/plugin/libinsn.dll.p/insn.c.obj: in function `vcpu_insn_matched_exec_before': +/tmp/qemu-test/build/../src/tests/plugin/insn.c:83: undefined reference to `__imp_qemu_plugin_outs' +/usr/lib/gcc/x86_64-w64-mingw32/12.2.1/../../../../x86_64-w64-mingw32/bin/ld: tests/plugin/libinsn.dll.p/insn.c.obj: in function `qemu_plugin_install': +/tmp/qemu-test/build/../src/tests/plugin/insn.c:199: undefined reference to `__imp_qemu_plugin_bool_parse' +/usr/lib/gcc/x86_64-w64-mingw32/12.2.1/../../../../x86_64-w64-mingw32/bin/ld: /tmp/qemu-test/build/../src/tests/plugin/insn.c:215: undefined reference to `__imp_qemu_plugin_register_vcpu_tb_trans_cb' +/usr/lib/gcc/x86_64-w64-mingw32/12.2.1/../../../../x86_64-w64-mingw32/bin/ld: /tmp/qemu-test/build/../src/tests/plugin/insn.c:216: undefined reference to `__imp_qemu_plugin_register_atexit_cb' +collect2: error: ld returned 1 exit status + + +If you move the qemu_plugin_api.lib to after the other .obj files, it works: + +bash-5.2$ x86_64-w64-mingw32-gcc -m64 -mcx16 plugins/qemu_plugin_api.lib -o tests/plugin/libinsn.dll tests/plugin/libinsn.dll.p/insn.c.obj tests/plugin/libinsn.dll.p/.._.._contrib_plugins_win32_linker.c.obj plugins/qemu_plugin_api.lib -Wl,--allow-shlib-undefined -shared -Wl,--start-group -Wl,--out-implib=tests/plugin/libinsn.dll.a -fstack-protector-strong -Wl,--no-seh -Wl,--nxcompat -Wl,--dynamicbase -Wl,--high-entropy-va -Wl,--warn-common /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libglib-2.0.dll.a /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libintl.dll.a /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libgmodule-2.0.dll.a -lkernel32 -luser32 -lgdi32 -lwinspool -lshell32 -lole32 -loleaut32 -luuid -lcomdlg32 -ladvapi32 -Wl,--end-group +bash-5.2$ echo $? +0 +``` +Steps to reproduce: +``` +make docker-test-build@fedora-win64-cross J=30 V=1 EXTRA_CONFIGURE_OPTS="--enable-fdt=internal --enable-plugins" NETWORK=1 +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1973 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1973 new file mode 100644 index 000000000..22a6c3500 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1973 @@ -0,0 +1 @@ +Issues with dmabuf use in dbus interface diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1974 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1974 new file mode 100644 index 000000000..8bb0ccb16 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1974 @@ -0,0 +1 @@ +Default console changes break Xen command-line diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1975 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1975 new file mode 100644 index 000000000..b98bd36a1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1975 @@ -0,0 +1,37 @@ +SEGV on exit: net_cleanup() frees devices it doesn't own. +Description of problem: +On exiting QEMU, the `net_cleanup()` function iterates over all existing `net_clients`, both netdevs and nics, and deletes them all. Freeing the netdevs is fine, and they are correctly detached from their peer nic as appropriate. But the nics belong to an actual device and this can cause a use-after-free or double-free. + +Mostly this doesn't happen because emulated devices *don't* bother to clean up after themselves on exit; none of their state is going to outlast the QEMU process so there's no point. But XenBus devices interact with the external XenStore and do need to perform a cleanup. The `xen_netdev_unrealize()` function calls `qemu_del_nic()` on the nic which `net_cleanup()` already stole from it, and crashes... + +``` +QEMU: Terminated + +Thread 1 "qemu-system-x86" received signal SIGSEGV, Segmentation fault. +qemu_del_nic (nic=0x55555846ab00) at ../net/net.c:451 +451 int i, queues = MAX(nic->conf->peers.queues, 1); +(gdb) bt +#0 qemu_del_nic (nic=0x55555846ab00) at ../net/net.c:451 +#1 0x0000555555a89ce3 in xen_device_unrealize (dev=<optimized out>) at ../hw/xen/xen-bus.c:973 +#2 0x0000555555e5c847 in notifier_list_notify (list=<optimized out>, data=0x0) at ../util/notify.c:39 +#3 0x00007ffff5fe51e6 in __run_exit_handlers (status=0, listp=<optimized out>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:111 +#4 0x00007ffff5fe532e in __GI_exit (status=<optimized out>) at exit.c:141 +#5 0x00007ffff5fccb91 in __libc_start_call_main (main=main@entry=0x5555558837a0 <main>, argc=argc@entry=23, argv=argv@entry=0x7fffffffd7a8) at ../sysdeps/nptl/libc_start_call_main.h:74 +#6 0x00007ffff5fccc4b in __libc_start_main_impl + (main=0x5555558837a0 <main>, argc=23, argv=0x7fffffffd7a8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffd798) at ../csu/libc-start.c:360 +#7 0x0000555555885345 in _start () +``` +Steps to reproduce: +1. Launch a Xen guest as described at https://qemu-project.gitlab.io/qemu/system/i386/xen.html (which will get a Xen NIC by default). +2. Terminate QEMU. + +It doesn't need to boot, doesn't need to do anything. Just launch a completely non-functional guest and then hit `Ctrl-a x` on the default monitor: +``` +$ ./qemu-system-x86_64 -accel kvm,xen-version=0x40010,kernel-irqchip=split -display none +QEMU: Terminated +Segmentation fault + +``` + +For `net_cleanup()` to clean up the *netdevs* makes sense, because those might have state which persists in the system after QEMU exits, and need to be cleaned up. But deleting the nics doesn't seem to be necessary. +Fix at https://lore.kernel.org/qemu-devel/61ea91785772a8138ad12b305cbd5aac4aa1e86a.camel@infradead.org diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1977 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1977 new file mode 100644 index 000000000..1d46f73d4 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1977 @@ -0,0 +1,30 @@ +MSYS2 build fails with link errors on Window 10 22H2 +Description of problem: +Linking target tests/plugin/libbb.dll fails with undefined references in below attached output +Steps to reproduce: +1. Open MSYS2 build environment on Windows 10 +2. mkdir build && cd build && ../configure --prefix=/home/Admin --enable-sdl --enable-gtk --target-list=arm-softmmu +3. make -j4 +Additional information: +[2300/2631] Linking target tests/plugin/libbb.dll +FAILED: tests/plugin/libbb.dll +"cc" "-m64" "-mcx16" -o tests/plugin/libbb.dll plugins/qemu_plugin_api.lib tests/plugin/libbb.dll.p/bb.c.obj tests/plugin/libbb.dll.p/.._.._contrib_plugins_win32_linker.c.obj "-Wl,--allow-shlib-undefined" "-shared" "-Wl,--start-group" "-Wl,--out-implib=tests/plugin/libbb.dll.a" "-fstack-protector-strong" "-Wl,--no-seh" "-Wl,--nxcompat" "-Wl,--dynamicbase" "-Wl,--high-entropy-va" "-Wl,--warn-common" "C:/msys64/ucrt64/lib/libglib-2.0.dll.a" "C:/msys64/ucrt64/lib/libintl.dll.a" "C:/msys64/ucrt64/lib/libgmodule-2.0.dll.a" "-lkernel32" "-luser32" "-lgdi32" "-lwinspool" "-lshell32" "-lole32" "-loleaut32" "-luuid" "-lcomdlg32" "-ladvapi32" "-Wl,--end-group" +C:/msys64/ucrt64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: tests/plugin/libbb.dll.p/bb.c.obj: in function `vcpu_tb_trans': +C:\msys64\home\Admin\qemu\build/../tests/plugin/bb.c:84:(.text+0x4f): undefined reference to `__imp_qemu_plugin_tb_n_insns' +C:/msys64/ucrt64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: C:\msys64\home\Admin\qemu\build/../tests/plugin/bb.c:87:(.text+0x62): undefined reference to `__imp_qemu_plugin_register_vcpu_tb_exec_inline' +C:/msys64/ucrt64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: C:\msys64\home\Admin\qemu\build/../tests/plugin/bb.c:93:(.text+0xba): undefined reference to `__imp_qemu_plugin_register_vcpu_tb_exec_cb' +C:/msys64/ucrt64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: tests/plugin/libbb.dll.p/bb.c.obj: in function `plugin_exit': +C:\msys64\home\Admin\qemu\build/../tests/plugin/bb.c:55:(.text+0x1cb): undefined reference to `__imp_qemu_plugin_outs' +C:/msys64/ucrt64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: C:\msys64\home\Admin\qemu\build/../tests/plugin/bb.c:55:(.text+0x204): undefined reference to `__imp_qemu_plugin_outs' +C:/msys64/ucrt64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: tests/plugin/libbb.dll.p/bb.c.obj: in function `vcpu_idle': +C:\msys64\home\Admin\qemu\build/../tests/plugin/bb.c:66:(.text+0x299): undefined reference to `__imp_qemu_plugin_outs' +C:/msys64/ucrt64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: tests/plugin/libbb.dll.p/bb.c.obj: in function `qemu_plugin_install': +C:\msys64\home\Admin\qemu\build/../tests/plugin/bb.c:114:(.text+0x2e8): undefined reference to `__imp_qemu_plugin_bool_parse' +C:/msys64/ucrt64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: C:\msys64\home\Admin\qemu\build/../tests/plugin/bb.c:141:(.text+0x3d5): undefined reference to `__imp_qemu_plugin_register_vcpu_tb_trans_cb' +C:/msys64/ucrt64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: C:\msys64\home\Admin\qemu\build/../tests/plugin/bb.c:142:(.text+0x3ea): undefined reference to `__imp_qemu_plugin_register_atexit_cb' +C:/msys64/ucrt64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: C:\msys64\home\Admin\qemu\build/../tests/plugin/bb.c:138:(.text+0x420): undefined reference to `__imp_qemu_plugin_register_vcpu_idle_cb' +collect2.exe: error: ld returned 1 exit status +[2301/2631] Compiling C object tests/plugin/libempty.dll.p/.._.._contrib_plugins_win32_linker.c.obj +[2302/2631] Compiling C object tests/libtestqapi.a.p/meson-generated_.._test-qapi-visit.c.obj +[2303/2631] Compiling C object tests/plugin/libinsn.dll.p/.._.._contrib_plugins_win32_linker.c.obj +ninja: build stopped: subcommand failed. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1979 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1979 new file mode 100644 index 000000000..da73ab7ad --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1979 @@ -0,0 +1,31 @@ +pc-q35-7.2 breaks the pcie hot plugin +Description of problem: +the new pc-q35 version >6.0 break the pcie hot plug feature +if I use 5.2, 6.0, it works fine. `dmesg | grep pcieport` shows that: +there is pciehp which provide functionality of hot plug for PCIE device +``` +[test@localhost ~]$ dmesg | grep pcieport +[ 1.161129] pcieport 0000:00:02.0: PME: Signaling with IRQ 24 +[ 1.162254] pcieport 0000:00:02.0: AER: enabled with IRQ 24 +[ 1.163218] pcieport 0000:00:02.0: pciehp: Slot #0 AttnBtn+ PwrCtrl+ MRL- AttnInd+ PwrInd+ HotPlug+ Surprise+ Interlock+ NoCompl- IbPresDis- LLActRep+ +``` + +if I switch to 6.1, 6.2, 7.0, 7.1 ,7.2, the pciehp does not show any control slot. +``` +[test@localhost ~]$ dmesg | grep pcieport +[ 1.164311] pcieport 0000:00:02.0: PME: Signaling with IRQ 24 +[ 1.165446] pcieport 0000:00:02.0: AER: enabled with IRQ 24 +``` +Steps to reproduce: +1. run the qemu command as I produced +2. connect to console +3. run `dmesg | grep pcieport` +4. you can try to plug in a GPU or something else, the device initialization will fail because there is no pciehp slow to power it on, normall you will see something like following, with >6.0 you cannot see them: + ``` + pciehp: Slot(0-8): Attention button pressed + pciehp: Slot(0-8) Powering on due to button press + pciehp: Slot(0-8): Card present + pciehp: Slot(0-8): Link Up + ``` +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1980 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1980 new file mode 100644 index 000000000..265ddb470 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1980 @@ -0,0 +1,13 @@ +pipewire backend, bad mic sound +Description of problem: +Qemu VM and openSUSE share the webcam mic. +Pipewire is used by openSUSE. + +If using qemu with pa backend, there is no sound problem when mic is used by Skype in openSUSE. +If using qemu with pipewire backend and Skype used the mic then my contact says he does not recognize my voice and there are cracks. +Steps to reproduce: +1. +2. +3. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1982 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1982 new file mode 100644 index 000000000..c089f7824 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1982 @@ -0,0 +1,9 @@ +PS/2 mouse and keyboard not disabled when adding USB devices +Description of problem: +Documentation (such as https://www.qemu.org/docs/master/system/qemu-manpage.html or https://www.qemu.org/docs/master/system/devices/usb.html) says that enabling a USB keyboard or mouse (or tablet) will disable the PS/2 equivalent, but it seems both are present instead. +Steps to reproduce: +1. Pass a `-usbdevice` or `-device` option to QEMU. +2. Boot Haiku. +3. Find two identical devices in Preferences > Input, both `Extended PS/2 Mouse 1` and `USB Tablet 1`, as well as `AT Keyboard 1` and `USB Keyboard 1`. +Additional information: +The content of /var/log/syslog, which shows discovery of PS/2 devices: [syslog.zst](/uploads/7ed067538c94edfdbaf35ec92a422c68/syslog.zst) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1983 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1983 new file mode 100644 index 000000000..6f645021f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1983 @@ -0,0 +1,30 @@ +Guest boot displays "virtio: device uses modern interface but does not have VIRTIO_F_VERSION_1" and then happens Call Trace +Description of problem: +Guest boot displays "FATAL: Module scsi_wait_scan not found", and then happens Call Trace. + +``` +Call Trace: + dump_stack+0x4f/0x66 + panic+0xa2/0x258 + do_exit+0x858/0xab0 + do_group_exit+0x2f/0x90 + ? do_page_fault+0x18c/0x4c0 + sys_exit_group+0x11/0x20 + do_fast_syscall_32+0x8b/0x1c2 + entry_SYSENTER_32+0xa5/0xf8 +EIP: 0xb7fcec71 +Code: 89 01 31 c0 89 51 04 89 71 08 89 79 0c eb 03 83 c8 ff 83 c4 28 5b 5e 5f 5d c3 8b 1c 24 c3 90 90 90 51 52 55 89 e5 0f 34 cd 80 <5d> 5a 59 c3 90 90 90 90 8d 76 00 58 b8 77 00 00 00 cd 80 90 8d 76 +EAX: ffffffda EBX: 00000001 ECX: 034c4745 EDX: 00000000 +ESI: 00000000 EDI: 00000000 EBP: bff7db18 ESP: bff7da3c +DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 007b EFLAGS: 00000246 +Kernel Offset: 0x16c00000 from 0xc0400000 (relocation range: 0xc0000000-0xf75fdfff) +``` +Steps to reproduce: +1.Create guest by using the command + ``` + ./qemu-system-x86_64 -accel kvm -m 4096 -smp 4 -cpu host -drive file=test-img.qcow2,format=qcow2,if=none,id=virtio-disk0 -device virtio-blk-pci,drive=virtio-disk0,bootindex=0 -monitor pty -daemonize -vnc :32137 -device virtio-net-pci,netdev=nic0,mac=00:c2:58:38:8e:f0 -netdev tap,id=nic0,br=virbr0,helper=/usr/local/libexec/qemu-bridge-helper,vhost=on + ``` +Additional information: +Suspected to be a QEMU regression issue, the first bad commit id: 14f5a7bae4cb5ca45a03e16b5bb0c5d766fd51b7. + +Latest successful version commit id: cea3ea670fe265421131aad90c36fbb87bc4d206 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1984 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1984 new file mode 100644 index 000000000..8ca10d585 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1984 @@ -0,0 +1 @@ +Fails to start dataplane while using vdpa-dev with vduse backend diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1988 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1988 new file mode 100644 index 000000000..5fdac05f5 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1988 @@ -0,0 +1,26 @@ +8.2.0rc0 Regression: '-display vnc' opens gtk display as well +Description of problem: +A VNC display is requested, but a GTK frontend is opened as well. A VNC client is able to connect. +Steps to reproduce: +1. /configure --enable-fdt=internal --target-list=x86_64-softmmu +2. make +3. build/qemu-system-x86_64 -display vnc=:05 -k de +Additional information: +git bisect finally shows +``` +484629fc8141eaa257f961b5e5e310a1bbd0f1a2 is the first bad commit +commit 484629fc8141eaa257f961b5e5e310a1bbd0f1a2 +Author: Marc-André Lureau <marcandre.lureau@redhat.com> +Date: Wed Oct 25 17:21:17 2023 +0400 + + vl: simplify display_remote logic + + Bump the display_remote variable when the -vnc option is parsed, just + like -spice. + + Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com> + Reviewed-by: Thomas Huth <thuth@redhat.com> + + system/vl.c | 6 +----- + 1 file changed, 1 insertion(+), 5 deletions(-) +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1989 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1989 new file mode 100644 index 000000000..1e0de3e12 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1989 @@ -0,0 +1,32 @@ +Regression: by default qemu opens both vnc and stdout console +Description of problem: +Running qemu with a vnc display (by default I'm not using the -display option) and -monitor stdio, +it fails because the display also wants the std output (it fails even if a pass the -vnc option). +If I remove the monitor I have both the vnc and the std output console at the same time. +I was able to use `-monitor stdio`, passing `-serial telent:...` +Steps to reproduce: +1. ./configure --enable-slirp --target-list=x86_64-softmmu --disable-user --disable-docs +2. make -j 4 +3. qemu-system-x86_64 ... (without `-display` as shown above) +Additional information: +After bisecting I found the following commit changed the behavior: + +``` +commit 1bec1cc0da497e55c16e2a7b50f94cdb2a02197f +Author: Marc-André Lureau <marcandre.lureau@redhat.com> +Date: Tue Sep 5 23:18:08 2023 +0400 + + ui/console: allow to override the default VC + + If a display is backed by a specialized VC, allow to override the + default "vc:80Cx24C". + + As suggested by Paolo, if the display doesn't implement a VC (get_vc() + returns NULL), use a fallback that will use a muxed console on stdio. + + This changes the behaviour of "qemu -display none", to create a muxed + serial/monitor by default (on TTY & not daemonized). + + Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com> + Reviewed-by: Thomas Huth <thuth@redhat.com> +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/199 b/gitlab/issues_text/target_missing/host_missing/accel_missing/199 new file mode 100644 index 000000000..f19f46d32 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/199 @@ -0,0 +1 @@ +Convert QAPI to static types diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1994 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1994 new file mode 100644 index 000000000..3ba76b2d8 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1994 @@ -0,0 +1 @@ +MacOS window sizing bug diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1995 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1995 new file mode 100644 index 000000000..349d24d7a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1995 @@ -0,0 +1 @@ +No equivalent of `-boot once` for `bootindex` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1996 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1996 new file mode 100644 index 000000000..7f8899666 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1996 @@ -0,0 +1,67 @@ +[Regression in v8.2.0-rc0] [macOS] configure: `ld: unknown options: --version ` +Description of problem: +On macOS, `./configure` fails since v8.2.0-rc0 due to `ld: unknown options: --version` +Steps to reproduce: +```console +$ ./configure +Using './build' as the directory for build output +python determined to be '/usr/local/bin/python3' +python version: Python 3.11.6 +mkvenv: Creating non-isolated virtual environment at 'pyvenv' +mkvenv: checking for meson>=0.63.0 +mkvenv: installing meson==0.63.3 +mkvenv: checking for sphinx>=1.6 +mkvenv: checking for sphinx_rtd_theme>=0.5 + +'sphinx==5.3.0' not found: + • Python package 'sphinx' was not found nor installed. + • mkvenv was configured to operate offline and did not check PyPI. + + +Sphinx not found/usable, disabling docs. +Disabling PIE due to missing toolchain support +The Meson build system +Version: 0.63.3 +Source dir: /Users/suda/gopath/src/gitlab.com/qemu-project/qemu +Build dir: /Users/suda/gopath/src/gitlab.com/qemu-project/qemu/build +Build type: native build +Project name: qemu +Project version: 8.1.90 + +../meson.build:1:0: ERROR: Unable to detect linker for compiler `cc -m64 -mcx16 -Wl,--version` +stdout: +stderr: ld: unknown options: --version +clang: error: linker command failed with exit code 1 (use -v to see invocation) + + +A full log can be found at /Users/suda/gopath/src/gitlab.com/qemu-project/qemu/build/meson-logs/meson-log.txt + +ERROR: meson setup failed + + +``` +Additional information: +```console +$ cc -m64 -mcx16 -Wl,--version +ld: unknown options: --version +clang: error: linker command failed with exit code 1 (use -v to see invocation) + +$ cc --version +Apple clang version 15.0.0 (clang-1500.0.40.1) +Target: x86_64-apple-darwin23.1.0 +Thread model: posix +InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bi + +$ ld --version +ld: unknown option: --version + +$ ld -v +@(#)PROGRAM:ld PROJECT:dyld-1015.7 +BUILD 16:59:22 Oct 1 2023 +configured to support archs: armv6 armv7 armv7s arm64 arm64e arm64_32 i386 x86_64 x86_64h armv6m armv7k armv7m armv7em +will use ld-classic for: armv6 armv7 armv7s arm64_32 i386 armv6m armv7k armv7m armv7em +LTO support using: LLVM version 15.0.0 (static support for 29, runtime is 29) +TAPI support using: Apple TAPI version 15.0.0 (tapi-1500.0.12.3) +Library search paths: +Framework search paths: +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1997 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1997 new file mode 100644 index 000000000..6befbccef --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1997 @@ -0,0 +1,20 @@ +Disk corruption on ARM64 (Apple Silicon) Linux VMs +Description of problem: +aarch64 Linux VMs will encounter disk corruption if they're set up with a filesystem that will notice it when it happens, e.g. BTRFS. This seems to be across the board with products, including Apple Hypervisor Framework, or just QEMU, so it very well might be an aarch64 Linux bug. +Steps to reproduce: +1. Install an aarch64 Linux VM using BTRFS as the root filesystem. ZFS might recognize silent corruption readily as well. +2. Run `stress-ng --iomix 4` +3. Check your `dmesg` and/or `btrfs check --force <device>` to check for filesystem corruption. +Additional information: +This is discussed in two other tickets, but I'm hoping to get more attention to the problem here. +[https://github.com/lima-vm/lima/issues/1957](https://github.com/lima-vm/lima/issues/1957) +[](https://github.com/utmapp/UTM/issues/4840) + + + + + +I can't seem to figure out how to upload images, but you can probably get to the image that I'm trying to share somehow... + + +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/200 b/gitlab/issues_text/target_missing/host_missing/accel_missing/200 new file mode 100644 index 000000000..e03760789 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/200 @@ -0,0 +1 @@ +Add Python linters (mypy, pylint, isort, flake8) to Gitlab CI diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2001 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2001 new file mode 100644 index 000000000..22c0923bb --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2001 @@ -0,0 +1,43 @@ +qemu_img convert and drive mirror migrate the same raw disk to rbd volume, will get the different USED size in ceph cluster. +Description of problem: +qemu_img convert and drive mirror migrate the same raw disk to rbd volume, will get the different USED size in ceph cluster. +Steps to reproduce: +create raw and qcow2 disk + +1. qemu-img create -f raw lvm_volume_1.raw 12G +2. qemu-img create -f qcow2 lvm_volume_1.qcow2 12G + + install a centos OS + +3. qemu-system-x86_64 -m 4096 -drive file=lvm_volume_1.qcow2,format=qcow2,index=0 -nographic -cdrom CentOS-8.3.2011-x86_64-dvd1.iso -vnc :25 + + convert the qcow2 OS disk to q raw OS disk + +4. qemu-img convert -f qcow2 -O raw ./lvm_volume_1.qcow2 ./lvm_volume_1.raw + + create a qemu-rbd process + +5. qemu-nbd --fork -x node1 -p 1238 rbd:cephpool- test/volume_1:id=xxx:key=xxx:mon_host=xxx:auth_supported=cephx + + boot the raw OS disk + +6. qemu-system-x86_64 -hda ./lvm_volume_1.raw -m 4096 -smp 4 -vnc :25 -monitor stdio + + migrate the raw OS disk to a ceph volume + +7. drive_mirror -n -f #block125 nbd:localhost:1238:exportname=node1 raw + + check the rbd volume USED size in ceph cluster + "rbd du cephpool-test/volume_1" + the ceph rbd volume PROVISION and USED are the same size + + convert the raw OS disk to a ceph volume + +8. qemu-img convert -n -f raw -O raw ./lvm_volume_1.raw rbd:cephpool- +test/volume_2:id=xxx:key=xxx:mon_host=xxx:auth_supported=cephx + + check the rbd volume USED size in ceph cluster + "rbd du cephpool-test/volume_2" + the ceph rbd volume PROVISION and USED are different PROVISION > USED +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2002 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2002 new file mode 100644 index 000000000..20631211c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2002 @@ -0,0 +1,3 @@ +Need to be able to set WM_CLASS under X11 +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2004 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2004 new file mode 100644 index 000000000..1b4b0cf69 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2004 @@ -0,0 +1,33 @@ +do_guest_openat /proc interposition doesn't work for openat +Description of problem: +For instance, trying with hppa emulated on top of x86: + +``` +$ hppa-linux-gnu-gcc test.c -o test +$ qemu-hppa-static ./test +``` + +One gets the host cpu information: + +``` +processor : 0 +vendor_id : GenuineIntel +cpu family : 6 +model : 142 +model name : Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz +[...] +``` + +while we would want to see the guest cpu information, like the test program does when `#if 0` is turned into `#if 1`: + +``` +processor : 0 +cpu family : PA-RISC 1.1e +cpu : PA7300LC (PCX-L2) +capabilities : os32 +model : 9000/778/B160L - Merlin L2 160 QEMU (9000/778/B160L) +``` + +This is because `do_guest_openat` only checks for the path, and does not look at `dirfd`, so it doesn't recognize that `openat(dirfd, "cpuinfo", O_RDONLY)` is actually opening a file in `/proc`. + +We could probably, when `dirfd` is not `AT_FDCWD`, try to `fstat()` it, open `/proc` with `O_DIRECTORY` and `fstat()` that too, and compare their `st_dev` and `st_ino`? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2006 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2006 new file mode 100644 index 000000000..b22555fd3 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2006 @@ -0,0 +1,42 @@ +migrating failed with rcu_preempt message on proxmox 8 +Description of problem: +when i migrate the VM from one host to another, it fails and give messages: + + ``` +[ 584.109502] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks: +[ 584.109534] rcu: 1-...!: (0 ticks this GP) idle=1408/0/0x0 softirq=8428/8428 fqs=0 (false positive?) +[ 584.109556] (detected by 0, t=5252 jiffies, g=2953, q=74 ncpus=2) +[ 584.109561] Sending NMI from CPU 0 to CPUs 1: +[ 584.109587] NMI backtrace for cpu 1 skipped: idling at native_safe_halt+0xb/0x10 +[ 584.110564] rcu: rcu_preempt kthread timer wakeup didn't happen for 5251 jiffies! g2953 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 +[ 584.110585] rcu: Possible timer handling issue on cpu=1 timer-softirq=8006 +[ 584.110597] rcu: rcu_preempt kthread starved for 5252 jiffies! g2953 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=1 +[ 584.110614] rcu: Unless rcu_preempt kthread gets sufficient CPU time, OOM is now expected behavior. +[ 584.110645] rcu: RCU grace-period kthread stack dump: +[ 584.110658] task:rcu_preempt state:I stack:0 pid:15 ppid:2 flags:0x00004000 +[ 584.110667] Call Trace: +[ 584.110672] <TASK> +[ 584.110688] __schedule+0x351/0xa20 +[ 584.110699] ? rcu_gp_cleanup+0x480/0x480 +[ 584.110704] schedule+0x5d/0xe0 +[ 584.110705] schedule_timeout+0x94/0x150 +[ 584.110709] ? __bpf_trace_tick_stop+0x10/0x10 +[ 584.110714] rcu_gp_fqs_loop+0x141/0x4c0 +[ 584.110717] rcu_gp_kthread+0xd0/0x190 +[ 584.110720] kthread+0xe9/0x110 +[ 584.110725] ? kthread_complete_and_exit+0x20/0x20 +[ 584.110728] ret_from_fork+0x22/0x30 +[ 584.110735] </TASK> +[ 584.110736] rcu: Stack dump where RCU GP kthread last ran: +[ 584.110747] Sending NMI from CPU 0 to CPUs 1: +[ 584.110757] NMI backtrace for cpu 1 skipped: idling at native_safe_halt+0xb/0x10 + + ``` + +we can reproduce on our R630 cluster easily, but it is OK on R730 cluster and R740 cluster. +Steps to reproduce: +1. create and run an VM +2. migrate the vm to other host +3. it failed with message +Additional information: +i downgrade the pve-qemu-kvm from 8.1.2-4 to 8.0.2-3, same problem. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2009 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2009 new file mode 100644 index 000000000..87bda221a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2009 @@ -0,0 +1 @@ +ld: warning: -undefined error is deprecated diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/201 b/gitlab/issues_text/target_missing/host_missing/accel_missing/201 new file mode 100644 index 000000000..eb7bc8891 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/201 @@ -0,0 +1 @@ +Create an asynchronous Python QMP library diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2011 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2011 new file mode 100644 index 000000000..04a4a23fa --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2011 @@ -0,0 +1 @@ +ARM emulation layer for Windows x86_64 OS request diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2012 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2012 new file mode 100644 index 000000000..193ce0c16 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2012 @@ -0,0 +1,12 @@ +Possible regression: Windows 95 setup fails on show of license +Description of problem: +Install of Windows 95 fails when showing the license. Qemu v8.1.0 is fine, Qemu 8.1.3 and later failes. Git bisect suggest the problem may have been introduced at 9fb45b05582438dcd52d2d48d48feb05de680c37 +Steps to reproduce: +1. Find install CD for Windows 95 and a DOS boot floppy +2. Create a harddrive (size 300MB) +3. Boot from floppy, create and format partition C: using all available space +4. change to the CD at D: and run command SETUP.EXE +5. follow instructions until display of license +6. See error: SUWIN caused a General Protection Fault in module <unknown> +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2014 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2014 new file mode 100644 index 000000000..b3cc9db95 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2014 @@ -0,0 +1,53 @@ +virtio: bounce.in_use==true in virtqueue_map_desc() +Description of problem: + +Steps to reproduce: +1. Build EDK II (edk2-stable202311) for riscv64 +2. Build UEFI SCT (commit 81dfa8d53d4290) for riscv64 +3. Run the UEFI SCT +4. Observe the message "qemu: virtio: bogus descriptor or out of resources" after which the execution stalls. + +The full procedure is described in https://github.com/xypron/sct_release_test + +To save time you can call `sct -u` and select only test 'MediaAccessTest\\BlockIOProtocolTest'. Run it with `F9`. +Additional information: +virtqueue_map_desc() may be called for a large buffers size `sz`. It will then call dma_memory_map() multiple times in a loop. In address_space_map() `bounce.in_use` is set to `true` on the first call. Each subsequent call is bound to fail. + +To verify this is the cause I applied the following diff: + +```plaintext +diff --git a/system/physmem.c b/system/physmem.c +index a63853a7bc..12b3c2f828 100644 +--- a/system/physmem.c ++++ b/system/physmem.c +@@ -3151,12 +3151,16 @@ void *address_space_map(AddressSpace *as, + + if (!memory_access_is_direct(mr, is_write)) { + if (qatomic_xchg(&bounce.in_use, true)) { ++ fprintf(stderr, "bounce.in_use in address_space_map\n"); ++ + *plen = 0; + return NULL; + } + /* Avoid unbounded allocations */ + l = MIN(l, TARGET_PAGE_SIZE); + bounce.buffer = qemu_memalign(TARGET_PAGE_SIZE, l); ++ if (!bounce.buffer) ++ fprintf(stderr, "Out of memory in address_space_map\n"); + bounce.addr = addr; + bounce.len = l; +``` + +and saw this output: + +```plaintext +Logfile: "\sct\Log\MediaAccessTest\BlockIOProtocolTest0\ReadBlocks_Conf_0_0_8261 +59D3-04A5-4CCE-8431-344707A8B57A.log" +Test Started: 12/02/23 08:43a +------------------------------------------------------------ +Current Device: Acpi(PNP0A03,0)/Pci(3|0) +Bounce.in_use in address_space_map +qemu: virtio: bogus descriptor or out of resources +``` + +See related bug #850. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2016 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2016 new file mode 100644 index 000000000..73b8a5b8c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2016 @@ -0,0 +1,9 @@ +-virtfs not working on windows +Description of problem: +performing the above returns +qemu-system-aarch64.exe: -virtfs abc: There is no option group 'virtfs' +qemu-system-aarch64.exe: -virtfs abc: virtfs support is disabled +Steps to reproduce: +1.qemu-system-aarch64.exe -virtfs abc +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2018 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2018 new file mode 100644 index 000000000..b60d0dfc3 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2018 @@ -0,0 +1,18 @@ +QEMU would not start when trying to create two UFS host controllers +Description of problem: +This issue is reported by Akinobu Mita. +https://lore.kernel.org/qemu-devel/20231204150543.48252-1-akinobu.mita@gmail.com/ + +> QEMU would not start when trying to create two UFS host controllers and a UFS logical unit for each with the following options: +> +> -device ufs,id=bus0 \ +> -device ufs-lu,drive=drive1,bus=bus0,lun=0 \ +> -device ufs,id=bus1 \ +> -device ufs-lu,drive=drive2,bus=bus1,lun=0 \ +> +> This is because the same ID string ("0:0:0/scsi-disk") is generated +> for both UFS logical units. +> +> To fix this issue, prepend the parent pci device's path to make +> the ID string unique. +> ("0000:00:03.0/0:0:0/scsi-disk" and "0000:00:04.0/0:0:0/scsi-disk") diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2019 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2019 new file mode 100644 index 000000000..986dcf9de --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2019 @@ -0,0 +1,26 @@ +Additional network device is not recognized on windows guest vm +Description of problem: +I have a problem for using Windows 2019/2022 guest vm as QEMU. +When I add a network device more online, it isn't work and recognized. +There is an error occurs at the Device Manager. + + + +I added network device with this qmp command +``` +'{ "execute": "chardev-add", "arguments":{"id":"charnet_35", "backend": { "type" : "socket", "data" : { "addr" : { "type" : "unix", "data" : {"path" : "/tmp/17115.1''"}}, "server" : true, "wait" : false }}}}' | nc -U $socket -N +'{ "execute": "netdev_add", "arguments":{"type":"vhost-user", "id":"'hostnet_35", "chardev":"charnet_35", "queues":2 }}' | nc -U $socket -N +'{ "execute" : "device_add", "arguments" : {"driver" : "virtio-net-pci", "mq":"on" ,"vectors":6, "netdev":"hostnet_35", "id":"dpdk_35", "mac":"F2:20:AF:40:12:65", "bus" : "bridge", "addr" : "0x8", "page-per-vq": "on", "rx_queue_size" : 1024, "tx_queue_size": 1024, "mrg_rxbuf" : "on", "disable-legacy": "on", "disable-modern" : "off" , "host_mtu" : 1500, "csum" : "on", "guest_csum" : "on", "host_tso4" : "on", "host_tso6" : "on"}}' | nc -U $socket -N +``` + +But, I can check recognized additional Network device after Windows guest vm rebooted. +Steps to reproduce: +1. Boot Windows 2019/2022 guest vm +2. Add chardev, netdev, device more with qmp command as hotplug +3. Check Network device recognition on the guest os +Additional information: +- I'm using hardware vDPA offloading with mellanox NIC card. +And When I use tap device instead vhost-user at the netdev, I don't have any problem. That error does not occured + +- And second, when I disable the first NIC, The additional NIC is recognized. + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/202 b/gitlab/issues_text/target_missing/host_missing/accel_missing/202 new file mode 100644 index 000000000..a2b5a7041 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/202 @@ -0,0 +1 @@ +Move scripts/qmp/qom-* tooling into qemu.qmp.* diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2021 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2021 new file mode 100644 index 000000000..b1fe0a475 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2021 @@ -0,0 +1 @@ +crashing when trying to read data from sensor though usb diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2023 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2023 new file mode 100644 index 000000000..12d573d2d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2023 @@ -0,0 +1 @@ +[block jobs]qemu hang when creating snapshot target node(iothread enable) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2024 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2024 new file mode 100644 index 000000000..46870ebb7 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2024 @@ -0,0 +1,30 @@ +IPv6 DHCPv6 DUID-UUID Generation Issue with iPXE on QEMU 8.1.2 and SMBIOS 3.0 +Description of problem: +I'm creating this ticket in both projects affected as I'm unsure which side needs to resolve it. I discovered this bug after upgrading Proxmox to version 8.1. I use iPXE to boot in IPv6 and retrieve the configuration from a web server. I have a DHCPv6 and SLAAC server configured. + +In this configuration, iPXE is unable to generate the necessary DUID-UUID for IPv6. If I revert to the previous QEMU version (using the machine: pc-i440fx-8.0 option in Proxmox), I have no issues. The only difference I notice and understand is the switch to SMBIOS 3.0, which is 64 bits, compared to SMBIOS 2.8, which is 32 bits. It appears to be the same issue with Libvirt. By default, it uses pc-q35-8.1, and I encounter the bug. However, if I switch to pc-q35-8.0, the problem is resolved. + +I've included two sets of information in the first part. The first one is from my local computer using libvirt, making it easier to reproduce the bug. The second set is from my production environment. + +Here's the iPXE trace: + +```plaintext +iPXE> ifconf --configurator ipv6 +Configuring [ipv6] (net0 66:b5:3e:97:7d:4e)... +DHCPv6 net0 could not create DUID-UUID: No such file or directory (https://ipxe.org/2d0c203b) +No such file or directory (https://ipxe.org/2d0c203b) +``` +Steps to reproduce: +1. Create a PXE ISO with IPv6 debug options: + 1. Clone the iPXE repository with the following command: + * `git clone https://github.com/ipxe/ipxe` + 2. Navigate to the src directory: + * `cd ipxe/src` + 3. Build the iPXE ISO with IPv6 debug options using the following command: + * `DEBUG='dhcpv6,neighbour' make bin/ipxe.iso` +2. Set up a Libvirt network with DHCPv6 enabled (example configuration provided in the next section). +3. Create a virtual machine with the generated iPXE ISO and the network configured for IPv6. +4. Press `Ctrl+B` to access the iPXE shell. +5. Execute the command `ifconf --configurator ipv6` in the iPXE shell. +Additional information: +# diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2025 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2025 new file mode 100644 index 000000000..066120082 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2025 @@ -0,0 +1,26 @@ +Can't make the touchscreen work in Windows VM, device virtio-multitouch-pci not starting +Description of problem: +I tried the multitouch on qemu 8, by adding "-device virtio-multitouch-pci" to the qemu cmd line +I could make the multitouch work for an Ubuntu VM, but not for a Windows VM +Last version of Virtio drivers are installed in Windows. + +Here are the issues i can see in windows : + + +Windows Events of virtio input driver device : + +``` +Device PCI\VEN_1AF4&DEV_1052&SUBSYS_11001AF4&REV_01\3&2411e6fe&0&18 had a problem starting. +Driver Name: oem7.inf +Class Guid: {745a17a0-74d3-11d0-b6fe-00a0c90f57da} +Service: VirtioInput +Lower Filters: +Upper Filters: +Problem: 0xA +Problem Status: 0xC000009A +``` +Qemu didnt produce any logs regarding this PCI + +Do I miss something ? + +Thanks for your help diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2026 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2026 new file mode 100644 index 000000000..d38bc90e8 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2026 @@ -0,0 +1,8 @@ +Virtio-vga-gl: If xres/yres is set, Qemu should not inherit the resolution of the window +Description of problem: +Despite setting xres=1920,yres-1080 when the VM the resolution the VM gets set to is inherited from the window. +Steps to reproduce: +1. Launch VM with xres/yres set +2. check display size +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2028 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2028 new file mode 100644 index 000000000..76b53ddb0 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2028 @@ -0,0 +1 @@ +CAN sja1000 standard frame filter bug diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2029 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2029 new file mode 100644 index 000000000..b06a3e0d3 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2029 @@ -0,0 +1 @@ +[block jobs]Guest hang when dd file on snapshot overlay(iothread enable) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/203 b/gitlab/issues_text/target_missing/host_missing/accel_missing/203 new file mode 100644 index 000000000..826ccd1f3 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/203 @@ -0,0 +1 @@ +move ./scripts/qapi/ to ./python/qemu/qapi/ diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2031 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2031 new file mode 100644 index 000000000..85db5b661 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2031 @@ -0,0 +1,13 @@ +Redundant comparison +Description of problem: +The result of the function `qdev_get_hotplug_handler` is always __NULL__. That is why the comparison in the line №502 is redundant: + +https://gitlab.com/qemu-project/qemu/-/blob/master/hw/core/qdev.c#L501 + +This code will never be executed: + +https://gitlab.com/qemu-project/qemu/-/blob/master/hw/core/qdev.c#L502-L507 + +Found by Linux Verification Center (portal.linuxtesting.ru) with SVACE. + +Author A. Voronin. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2032 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2032 new file mode 100644 index 000000000..32cd6035f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2032 @@ -0,0 +1,31 @@ +qemu-guest-agent not starting +Description of problem: +Trace found in syslog : +``` +syslog:Dec 11 13:45:08 mail systemd[1]: dev-virtio\x2dports-org.qemu.guest_agent.0.device: Job dev-virtio\x2dports-org.qemu.guest_agent.0.device/start timed out. +syslog:Dec 11 13:45:08 mail systemd[1]: Timed out waiting for device /dev/virtio-ports/org.qemu.guest_agent.0. +syslog:Dec 11 13:45:08 mail systemd[1]: qemu-guest-agent.service: Job qemu-guest-agent.service/start failed with result 'dependency'. +syslog:Dec 11 13:45:08 mail systemd[1]: dev-virtio\x2dports-org.qemu.guest_agent.0.device: Job dev-virtio\x2dports-org.qemu.guest_agent.0.device/start failed with result 'timeout'. +``` +Steps to reproduce: +systemctl start qemu-guest-agent +Additional information: +Messages when installing the systemd unit : +``` +systemctl enable qemu-guest-agent +Synchronizing state of qemu-guest-agent.service with SysV service script with /lib/systemd/systemd-sysv-install. +Executing: /lib/systemd/systemd-sysv-install enable qemu-guest-agent +The unit files have no installation config (WantedBy=, RequiredBy=, Also=, +Alias= settings in the [Install] section, and DefaultInstance= for template +units). This means they are not meant to be enabled using systemctl. + +Possible reasons for having this kind of units are: +• A unit may be statically enabled by being symlinked from another unit's + .wants/ or .requires/ directory. +• A unit's purpose may be to act as a helper for some other unit which has + a requirement dependency on it. +• A unit may be started when needed via activation (socket, path, timer, + D-Bus, udev, scripted systemctl call, ...). +• In case of template units, the unit is meant to be enabled with some + instance name specified. + ``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2033 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2033 new file mode 100644 index 000000000..304bc46ae --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2033 @@ -0,0 +1 @@ +goldfish_rtc device incorrectly migrates tick offset as an offset from QEMU_CLOCK_VIRTUAL diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2035 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2035 new file mode 100644 index 000000000..b6cb5ef36 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2035 @@ -0,0 +1,54 @@ +TCG Plugin exit callback not executing +Description of problem: +I cannot get the plugin exit callback to register/execute. I should see "Goodbye from plugin" but dont. I have also tried using `qemu_plugin_outs` without success. + +**Update: If I make my test binary an infinite loop and kill it with CTRL-C, then the callback is called as expected. Am I just using it wrong?** +Steps to reproduce: +1. Configured QEMU with `--target-list=riscv32-linux-user,riscv64-linux-user --enable-plugins --disable-system` +2. Compiled plugin with +``` +gcc -I./qemu/include/qemu `pkg-config --libs glib-2.0` -O0 -fvisibility=hidden -Wall -shared -fPIC `pkg-config --cflags glib-2.0` +``` +3. Compiled test binary (just a hello world) with `riscv64-unknown-elf-gcc test_qemu.c -o test_qemu` +4. Ran ./qemu/build/qemu-riscv64 -plugin ./test_plugin.so -d plugin ./test_qemu +Additional information: +test_plugin.c +``` +#include <inttypes.h> +#include <assert.h> +#include <stdlib.h> +#include <string.h> +#include <unistd.h> +#include <stdio.h> +#include <qemu-plugin.h> + +QEMU_PLUGIN_EXPORT int qemu_plugin_version = QEMU_PLUGIN_VERSION; + +static void vcpu_tb_trans(qemu_plugin_id_t id, struct qemu_plugin_tb *tb) +{ + int n_insns = qemu_plugin_tb_n_insns(tb); + printf("> New TB of size %d\n", n_insns); + + for (int i = 0; i < n_insns; i++) { + struct qemu_plugin_insn * insn = qemu_plugin_tb_get_insn(tb, i); + char * disassembly = qemu_plugin_insn_disas(insn); + printf(" > Instruciton: %s\n", disassembly); + } +} + +static void plugin_exit(qemu_plugin_id_t id, void *p) +{ + printf("> Goodbye from plugin. %d\n", id); +} + +QEMU_PLUGIN_EXPORT int qemu_plugin_install(qemu_plugin_id_t id, + const qemu_info_t *info, + int argc, char **argv) +{ + printf("> Hello From Plugin!\n"); + qemu_plugin_register_vcpu_tb_trans_cb(id, vcpu_tb_trans); + qemu_plugin_register_atexit_cb(id, plugin_exit, NULL); + printf("> Everything was registered\n"); + return 0; +} +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2036 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2036 new file mode 100644 index 000000000..cad6b7c02 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2036 @@ -0,0 +1,11 @@ +`edk2-riscv-code.fd.bz2` is included in the repo but not installed to `$PREFIX/share/qemu` +Description of problem: +`edk2-riscv-code.fd.bz2` is included in the repo (https://gitlab.com/qemu-project/qemu/-/blob/v8.2.0-rc4/pc-bios/edk2-riscv-code.fd.bz2), but this file is not installed to `$PREFIX/share/qemu`. + +The binaries for other architectures (aarch64, arm, i386, x86\_64) are installed as expected. +https://gitlab.com/qemu-project/qemu/-/blob/v8.2.0-rc4/pc-bios/meson.build?ref_type=tags#L3-L12 +Steps to reproduce: +`ls $PREFIX/share/qemu/edk2-*` +Additional information: +- Not sure if this is intentional or a bug. +- The descriptor JSON file is missing for riscv: https://gitlab.com/qemu-project/qemu/-/tree/v8.2.0-rc4/pc-bios/descriptors diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2038 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2038 new file mode 100644 index 000000000..55381d49f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2038 @@ -0,0 +1,16 @@ +simpletrace.py does nothing, and syntax error when called from bash script +Description of problem: +The simpletrace python script appears to do nothing when I run it as above. + +It appears to run (but do nothing) when called from my terminal but there is also a syntax error when I run it from the bash script above. + +``` +SyntaxError: invalid syntax + File "<fstring>", line 1 + (pid=) + ^ +``` + +I think this syntax error is caused by the line `print(f'{event.name} {delta_ns / 1000:0.3f} {pid=} ' + ' '.join(fields))` +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2039 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2039 new file mode 100644 index 000000000..bd38d9705 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2039 @@ -0,0 +1,11 @@ +there is no 'write' lock checked when exec `qemu-img check lvqcow2` +Description of problem: +There is a difference between a qcow2 file image and a lvqcow2 img. + +'write' lock will be checked when using a normal qcow2-format image (/path/to/img/test.qcow2) to avoid some risky operations. However, when I create a qcow2 img on a lv, there is not any write lock checked when I perform `qemu-img check` on this lvqcow2 even though it was attached to a vm. +Steps to reproduce: +1. create a lvqcow2: `qemu-img create -f qcow2 /path/to/lv xxG` +2. create a vm using this lvqcow2 +3. exec `qemu-img check` on this lvqcow2, there is no any perm (such as 'write' lock) check and notifaction even though this lvqcow2 is using in qemu vm. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/204 b/gitlab/issues_text/target_missing/host_missing/accel_missing/204 new file mode 100644 index 000000000..9be001c64 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/204 @@ -0,0 +1 @@ +Dos Keypad is not working for numbers - numlock is not working diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2042 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2042 new file mode 100644 index 000000000..9a02801b4 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2042 @@ -0,0 +1,18 @@ +Not able to reboot Linux guest on Windows host +Description of problem: +I am running Linux Mint on Windows, but when I try to reboot the machine, I get the following error: + +qemu: WHPX: Unexpected VP exit code 4 + +I did some experiments changing the flags I use when I launch Qemu and I realized that if I set -smp 1 it does not fail. Furthermore, if I set the irqchip to off (kernel-irqchip=off) it does not fail either, but both options do not have good performance at all. I realized too that if I set 4 cores (-smp 4), the error might appear up to 4 times. + +What seems to be failing then is the APIC emulation that Hyper-V provides. Does anyone know if: + +1. Am I missing a flag when launching Qemu? +2. Is it there a patch to solve this? + +Any leads for solving this problem would be highly appreciated. +Steps to reproduce: +1. Install MSYS +2. Open MSYS and run pacman -S mingw-w64-x86_64-qemu +3. Launch Qemu and reboot machine diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2043 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2043 new file mode 100644 index 000000000..4fa216ec0 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2043 @@ -0,0 +1,74 @@ +QEMU hangs sometimes during TRIM command +Description of problem: +I encountered a virtual machine freeze when map cache invalidation request was received while executing a TRIM command. + +I did some research and i think i found the problem. + +1. `xen_invalidate_map_cache` calls `bdrv_drain_all` before invalidation +2. All BlockBackend devices run into quiesce mode (increment of `blk->quiesce_counter` in `blk_root_drained_begin`) +3. When processing another block in TRIM command coroutine `blk_co_do_pdiscard` calls `blk_wait_while_drained` +4. In `blk_wait_while_drained` we go under tre condition, decrement `in_flight` counter and yield the coroutine +5. After return from `blk_aio_complete_bh` `in_flight` counter of `BlockBackend` device remains with value 1, which prevents `AIO_WAIT_WHILE_UNLOCKED(NULL, bdrv_drain_all_poll());` loop from exiting +6. So QEMU stays in `bdrv_drain_all_begin` method + +Now why `in_flight` counter does not go to zero in point 5? + +Below is a call diagram for TRIM command. For example, consider processing of 2 blocks. + + + +s can be seen from the diagram `in_flight` counter of BlockBackend at first increments at start of command in `ide_issue_trim`, and next in `blk_aio_prwv` before start of coroutine. But for second and next blocks we get into BH method `blk_aio_complete_bh` and before decrementing `in_flight` we call `acb->common.cb` callback, that is in fact `ide_issue_trim_cb`, so we incrementing `in_flight` again to value of 3. And decrementing to value of 2 before return from `blk_aio_complete`. + +So, the value of `blk->in_flight` varies in range [2..3] during block processing. + +Now consider the situation when map cache invalidation request is received during a block processing in TRIM command. Below is a call diagram for this situation. + + + +In this example we get invalidation request before second block processing. Our BlockBackend device run into quiesce mode, and we yielding the coroutine in `blk_wait_while_drained`, decrementing `in_flight` counter from 3 to 2. Second decrement is made in `blk_aio_complete` (2 to 1). + +And now we get in situation, when we not scheduling any block processing methods, as they must be called later from `bdrv_drain_all_end`, and on the other hand, `bdrv_drain_all_poll` always returns true, as we have non-zero `in_flight` counter on one of BlockBackend devices. + +As one of possible solutions i try to call `blk_set_disable_request_queuing(s->blk, true);` in `ide_issue_trim` and corresponding `blk_set_disable_request_queuing(blk, false);` in `ide_trim_bh_cb`. Looks like it solves the problem, so TRIM command always process completely, as is ignore quiesce mode and not do coroutine yielding. But i think is not optimal. + +I try also remove incrementing and decrementing of `in_flight` counter in `ide_issue_trim` and `ide_trim_bh_cb`, so value of counter varies in range [1..2] during block processing. This also works, but i started to get warings like `Locked DMA mapping while invalidating mapcache!`, as TRIM command probably uses map cache and is not completed before actual map cache invalidation. +Steps to reproduce: +1. Run virtual machine +2. Run progrms, work with files, etc. +Additional information: +QEMU trace logs. Enabled trace events: handle_ioreq, ide_dma_cb, dma_blk_io, dma_blk_cb, dma_complete, qemu_coroutime_yield. + +Log of TRIM command without freeze excerpt: + +``` +… +handle_ioreq I/O=0x7ffc51d5e160 type=0 dir=0 df=0 ptr=0 port=0x1f4 data=0x0 count=1 size=1 +handle_ioreq I/O=0x7ffc51d5e160 type=0 dir=0 df=0 ptr=0 port=0x1f5 data=0x0 count=1 size=1 +handle_ioreq I/O=0x7ffc51d5e160 type=0 dir=0 df=0 ptr=0 port=0x1f7 data=0x6 count=1 size=1 +handle_ioreq I/O=0x7ffc51d5e160 type=0 dir=0 df=0 ptr=0 port=0xc160 data=0x1 count=1 size=1 +ide_dma_cb IDEState 0x5559d513ff98; sector_num=0 n=1 cmd=DMA TRIM +dma_blk_io dbs=0x5559d5c6f350 bs=0x5559d513ff98 offset=0 to_dev=1 +dma_blk_cb dbs=0x5559d5c6f350 ret=0 +dma_blk_cb dbs=0x5559d5c6f350 ret=0 +dma_complete dbs=0x5559d5c6f350 ret=0 cb=0x5559d1585620 +handle_ioreq I/O=0x7ffc51d5e160 type=0 dir=1 df=0 ptr=0 port=0xc162 data=0x0 count=1 size=1 +handle_ioreq I/O=0x7ffc51d5e160 type=0 dir=1 df=0 ptr=0 port=0xc162 data=0x0 count=1 size=1 +handle_ioreq I/O=0x7ffc51d5e160 type=0 dir=0 df=0 ptr=0 port=0xc160 data=0x0 count=1 size=1 +… +``` + +Log of TRIM command with freeze: + +``` +… +handle_ioreq I/O=0x7ffc52722ae0 type=8 dir=0 df=0 ptr=0 port=0x0 data=0xffffffffffffffff count=0 size=4 +handle_ioreq I/O=0x7ffc52722ae0 type=8 dir=0 df=0 ptr=0 port=0x0 data=0xffffffffffffffff count=0 size=4 +handle_ioreq I/O=0x7ffc52722ae0 type=8 dir=0 df=0 ptr=0 port=0x0 data=0xffffffffffffffff count=0 size=4 +handle_ioreq I/O=0x7ffc52722ae0 type=0 dir=0 df=0 ptr=0 port=0xc160 data=0x1 count=1 size=1 +ide_dma_cb IDEState 0x55c76faccf98; sector_num=0 n=1 cmd=DMA TRIM +dma_blk_io dbs=0x55c770425b50 bs=0x55c76faccf98 offset=0 to_dev=1 +dma_blk_cb dbs=0x55c770425b50 ret=0 +handle_ioreq I/O=0x7ffc52722ae0 type=8 dir=0 df=0 ptr=0 port=0x0 data=0xffffffffffffffff count=0 size=4 +qemu_coroutine_yield from 0x55c76f4207f0 to 0x7f7fb099e0c0 +[end of log, no more events] +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2045 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2045 new file mode 100644 index 000000000..7c57179b9 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2045 @@ -0,0 +1 @@ +virtio-gpu-*-pci Support reset of virtual GPU from /sys/bus/pci/devices/$NUMBER/reset diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2046 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2046 new file mode 100644 index 000000000..607101a71 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2046 @@ -0,0 +1 @@ +live migration error : qemu-kvm: Missing section footer for 0000:00:01.3/piix4_pm diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2047 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2047 new file mode 100644 index 000000000..5ffa31a68 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2047 @@ -0,0 +1,3 @@ +Support of LibVF.IO - vendor neutral GPU multiplexing tool driven by YAML & VFIO. +Additional information: +Git: https://github.com/Arc-Compute/LibVF.IO/tree/master/ diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2048 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2048 new file mode 100644 index 000000000..76520a9f8 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2048 @@ -0,0 +1 @@ +Host: Wayland sdl display problem diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2049 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2049 new file mode 100644 index 000000000..603872a93 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2049 @@ -0,0 +1,11 @@ +drive-mirror RBD thin +Description of problem: +I found that this problem was first discovered in 2014. There was a post +[2014 bug description](https://lists.gnu.org/archive/html/qemu-devel/2014-10/msg01231.html )、 +[2014 patch](https://patchwork.ozlabs.org/project/qemu-devel/patch/1433747185-16797-2-git-send-email-famz@redhat.com/) +mentioning this bug. +The patch in the post said that this problem had been solved, but after trying and asking, I found that the problem had not been solved. +Later, I saw this problem in the [2017 bug description](https://forum.proxmox.com/threads/drive-mirror-rbd-thin.33250/#post-613502) forum and it was said that there was a patch to fix it, but it was not. +I tried the latest qemu version and found that this problem has not been solved. +Additional information: +nbd is normal, but rbd is wrong！ diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/205 b/gitlab/issues_text/target_missing/host_missing/accel_missing/205 new file mode 100644 index 000000000..e258c4066 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/205 @@ -0,0 +1 @@ +Arrow keys press is double in some programs in Dos diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2050 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2050 new file mode 100644 index 000000000..703249b39 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2050 @@ -0,0 +1,7 @@ +Graphical glitch on boot screen of ubuntu aarch64 +Description of problem: +Glitches on boot screen. +Additional information: + + +(The "TIANO Core" screen before this has similar issues) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2051 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2051 new file mode 100644 index 000000000..fae44e28e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2051 @@ -0,0 +1 @@ +virtio-gpu redraw issue diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2052 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2052 new file mode 100644 index 000000000..e75c20e14 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2052 @@ -0,0 +1 @@ +sdl window partially catches mouse cursor diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2055 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2055 new file mode 100644 index 000000000..9aee4a8b9 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2055 @@ -0,0 +1,7 @@ +Unable to set the PBMTE bit in the menvcfg register for RISCV 64 bit +Description of problem: +We are unable to program the PBMTE bit in the menvcfg register of a RV64 machine. The following is the command that was used to do this. + +write_csr(menvcfg,PTE_PBMT); +Steps to reproduce: +1. A simple test program with the above command should be able to reproduce this issue. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2056 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2056 new file mode 100644 index 000000000..35d968cd0 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2056 @@ -0,0 +1,14 @@ +macOS Cocoa title bar covers top of VM screen +Description of problem: +When using the Cocoa interface the title bar covers the top part of the VM screen. In Windows XP, using show-cursor=on and USB tablet (-usb -device usb-tablet,bus=usb-bus.0), the mouse cursor seems to be off by the height of the title bar; to click on a target the mouse cursor has to be below the target by about the height of the top bar. +Steps to reproduce: +1. Run Qemu using the Cocoa-interface (-display cocoa) +Additional information: +The problem exists in both Qemu 8.2.0 (compiled from source) as well as in the MacPorts version (version 8.0.5). Further testing shows the same problem in versions 6.2.0, 7.0.0, and 7.1.0. This problem did not exist in previous versions of macOS. + +A screenshot is enclosed: + + +For similar reports, see: https://www.emaculation.com/forum/viewtopic.php?p=77350#p77350 and https://github.com/phil-opp/blog_os/issues/1249#issuecomment-1825933581 and https://68kmla.org/bb/index.php?threads/a-self-contained-qemu-based-a-ux-system-for-macos.45106/post-504970 + +The problem exists on both Apple Silicon and Intel hardware. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2057 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2057 new file mode 100644 index 000000000..4e5fcfc2c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2057 @@ -0,0 +1,5 @@ +QEMU 8.2 configure error +Description of problem: +please see output upper +Steps to reproduce: +1. Just run ./configure diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2058 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2058 new file mode 100644 index 000000000..9713d0194 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2058 @@ -0,0 +1,52 @@ +QEMU should pad Ethernet frames from vmnet.framework on macOS hosts +Description of problem: +When using a `vmnet` network device on a macOS host, the host’s [ARP](https://en.wikipedia.org/wiki/Address_Resolution_Protocol) replies are smaller than the 64-octet minimum frame size defined for Ethernet in IEEE Std 802.3-2022 (subclause 4.2.3.3 and Table 4–2). + +When QEMU presents such frames to a guest, the guest’s Ethernet device driver may drop them with “frame too short” or “runt” errors, since they are smaller than actual Ethernet frames should ever be. This prevents the guest from resolving the host’s MAC address, so the guest and host can’t communicate as expected. + +I observed this problem with a Mac OS X 10.4.11 guest using a `sungem` or `rtl8139` virtual network device, but it might also affect other guests and virtual network devices. +Additional information: +To prevent this problem, QEMU should pad Ethernet frames received from `vmnet` to the minimum size, 60 bytes before the frame check sequence, before handing them off to a guest. (QEMU’s virtual network devices used to add such padding, but that was changed earlier this year in commits such as 63b901bf and aee87b43.) + +Here is a patch for `net/vmnet-common.m` that calls `eth_pad_short_frame()` for this, as `net/tap.c` and `net/slirp.c` already do: + +``` +--- net/vmnet-common.m.orig 2023-12-19 13:24:34.000000000 -0800 ++++ net/vmnet-common.m 2023-12-27 13:30:15.000000000 -0800 +@@ -18,6 +18,7 @@ + #include "qemu/error-report.h" + #include "qapi/error.h" + #include "sysemu/runstate.h" ++#include "net/eth.h" + + #include <vmnet/vmnet.h> + #include <dispatch/dispatch.h> +@@ -150,10 +151,23 @@ + */ + static void vmnet_write_packets_to_qemu(VmnetState *s) + { ++ uint8_t *pkt; ++ size_t pktsz; ++ uint8_t min_pkt[ETH_ZLEN]; ++ size_t min_pktsz = sizeof(min_pkt); ++ + while (s->packets_send_current_pos < s->packets_send_end_pos) { +- ssize_t size = qemu_send_packet_async(&s->nc, +- s->iov_buf[s->packets_send_current_pos].iov_base, +- s->packets_buf[s->packets_send_current_pos].vm_pkt_size, ++ pkt = s->iov_buf[s->packets_send_current_pos].iov_base; ++ pktsz = s->packets_buf[s->packets_send_current_pos].vm_pkt_size; ++ ++ if (net_peer_needs_padding(&s->nc)) { ++ if (eth_pad_short_frame(min_pkt, &min_pktsz, pkt, pktsz)) { ++ pkt = min_pkt; ++ pktsz = min_pktsz; ++ } ++ } ++ ++ ssize_t size = qemu_send_packet_async(&s->nc, pkt, pktsz, + vmnet_send_completed); + + if (size == 0) { + +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/206 b/gitlab/issues_text/target_missing/host_missing/accel_missing/206 new file mode 100644 index 000000000..ba05720c5 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/206 @@ -0,0 +1 @@ +Dos on the fly CD image replacement is not Working with DOS diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2060 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2060 new file mode 100644 index 000000000..f7f7ff883 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2060 @@ -0,0 +1,3 @@ +memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set +Additional information: +i'm using pve-qemu-kvm 8.1.2-6 on 6.5.11-7-pve kernel diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2061 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2061 new file mode 100644 index 000000000..675e416f7 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2061 @@ -0,0 +1,13 @@ +Regression: QEMU 8.2.0 VFIO GPU guests cannot reboot due to improper reset +Description of problem: +Prior to QEMU 8.2.0 (i.e. 8.1.4), rebooting the guest with VFIO GPU passed through would result in a proper reboot. +After updating to QEMU 8.2.0, rebooting the guest results in a black screen due to improper reset behaviour. +I was able to narrow this down to commit #3d779ab. Compiling and running with commit #0bddd88 results in the correct behaviour. +That is, the GPU properly resets on guest reboot and boots successfully to Windows. +Steps to reproduce: +1. Update to QEMU 8.2.0 +2. Boot Windows 11 23H2 +3. Reboot +4. Notice a black screen +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2062 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2062 new file mode 100644 index 000000000..9d2fe5602 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2062 @@ -0,0 +1 @@ +qemu-img snapshot -l output formatting is broken (field to small / whitespace missing) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2065 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2065 new file mode 100644 index 000000000..9b6b4fe9c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2065 @@ -0,0 +1 @@ +rfe: Cygwin support diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2067 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2067 new file mode 100644 index 000000000..754903466 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2067 @@ -0,0 +1 @@ +screen unblanking issue with debian 12 gui diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2068 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2068 new file mode 100644 index 000000000..48272728f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2068 @@ -0,0 +1,15 @@ +Regression: 8.1.3 -> 8.2.0 breaks virtio vga driver +Description of problem: +I have a number of emulated arch linuxes using the same x11/kde configuration. After updating from 8.1.3 to 8.2.0, they all broke in the following way: +- screen tearing/artifacts seen from bios up until sddm +- sddm is possibly affected +- kde/x11 has so many artifacts that its unusable. if i attempt to write in a console window, i can only see parts of what ive written if i attempt to gently resize the bottom of the window. clicking the menu item will only render the menu 1/6 times and only partly. however if I click where I remember the shutdown button to be, the system shuts down immediately, so thi seems to be purely a graphics issue. +- starting with -vga qxl fixes all issues. +Steps to reproduce: +1. make new qemu, install arch/kde +2. boot said qemu with -vga virtio option +3. observe issue from the moment it boots +Additional information: +Using nVidia card and drivers on host. + +Removing x86-video-vesa on the guest system seemed to significant improve performance. There are still many artifacts but its almost usable with this driver removed. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2069 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2069 new file mode 100644 index 000000000..84ac55e7f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2069 @@ -0,0 +1,352 @@ +[virtio_blk:iothread-vq-mapping]Qemu core dump when checking the deleted device via "info qtree" +Description of problem: +[virtio_blk:iothread-vq-mapping]Qemu core dump when checking the deleted device via "info qtree" +Steps to reproduce: +1.Start guest with qemu cmds: \ + qemu-system-x86_64 \ + -S \ + -name 'avocado-vt-vm1' \ + -machine pc,memory-backend=mem-machine_mem \ + -nodefaults \ + -device '{"driver": "VGA", "bus": "pci.0", "addr": "0x2"}' \ + -m 30720 \ + -object '{"size": 32212254720, "id": "mem-machine_mem", "qom-type": "memory-backend-ram"}' \ + -smp 10,maxcpus=10,cores=5,threads=1,dies=1,sockets=2 \ + -cpu 'Cascadelake-Server-noTSX',+kvm_pv_unhalt \ + -chardev socket,path=/tmp/monitor-qmpmonitor1-20240104-043347-5Miq4hMP,wait=off,server=on,id=qmp_id_qmpmonitor1 \ + -mon chardev=qmp_id_qmpmonitor1,mode=control \ + -chardev socket,path=tmp/monitor-catch_monitor-20240104-043347-5Miq4hMP,wait=off,server=on,id=qmp_id_catch_monitor \ + -mon chardev=qmp_id_catch_monitor,mode=control \ + -device '{"ioport": 1285, "driver": "pvpanic", "id": "id3KTLMV"}' \ + -chardev socket,path=/tmp/serial-serial0-20240104-043347-5Miq4hMP,wait=off,server=on,id=chardev_serial0 \ + -device '{"id": "serial0", "driver": "isa-serial", "chardev": "chardev_serial0"}' \ + -chardev socket,id=seabioslog_id_20240104-043347-5Miq4hMP,path=/tmp/seabios-20240104-043347-5Miq4hMP,server=on,wait=off \ + -device isa-debugcon,chardev=seabioslog_id_20240104-043347-5Miq4hMP,iobase=0x402 \ + -device '{"driver": "ich9-usb-ehci1", "id": "usb1", "addr": "0x1d.0x7", "multifunction": true, "bus": "pci.0"}' \ + -device '{"driver": "ich9-usb-uhci1", "id": "usb1.0", "multifunction": true, "masterbus": "usb1.0", "addr": "0x1d.0x0", "firstport": 0, "bus": "pci.0"}' \ + -device '{"driver": "ich9-usb-uhci2", "id": "usb1.1", "multifunction": true, "masterbus": "usb1.0", "addr": "0x1d.0x2", "firstport": 2, "bus": "pci.0"}' \ + -device '{"driver": "ich9-usb-uhci3", "id": "usb1.2", "multifunction": true, "masterbus": "usb1.0", "addr": "0x1d.0x4", "firstport": 4, "bus": "pci.0"}' \ + -device '{"driver": "usb-tablet", "id": "usb-tablet1", "bus": "usb1.0", "port": "1"}' \ + -object '{"qom-type": "iothread", "id": "t1"}' \ + -object '{"qom-type": "iothread", "id": "t2"}' \ + -object '{"qom-type": "iothread", "id": "t3"}' \ + -object '{"qom-type": "iothread", "id": "t4"}' \ + -blockdev '{"node-name": "file_image1", "driver": "file", "auto-read-only": true, "discard": "unmap", "aio": "threads", "filename": "/home/kvm_autotest_root/images/rhel9-virtio.qcow2", "cache": {"direct": true, "no-flush": false}}' \ + -blockdev '{"node-name": "drive_image1", "driver": "qcow2", "read-only": false, "cache": {"direct": true, "no-flush": false}, "file": "file_image1"}' \ + -device '{"driver": "virtio-blk-pci", "id": "image1", "drive": "drive_image1", "bootindex": 0, "write-cache": "on", "bus": "pci.0", "addr": "0x3"}' \ + -blockdev '{"node-name": "file_stg1", "driver": "file", "auto-read-only": true, "discard": "unmap", "aio": "threads", "filename": "/home/kvm_autotest_root/images/stg1.qcow2", "cache": {"direct": true, "no-flush": false}}' \ + -blockdev '{"node-name": "drive_stg1", "driver": "qcow2", "read-only": false, "cache": {"direct": true, "no-flush": false}, "file": "file_stg1"}' \ + -device '{"driver": "virtio-blk-pci", "id": "stg1", "drive": "drive_stg1", "bootindex": 1, "write-cache": "on", "serial": "stg1", "bus": "pci.0", "addr": "0x4", "iothread-vq-mapping": [{"iothread": "t2"}, {"iothread": "t3"}]}' \ + -blockdev '{"node-name": "file_stg2", "driver": "file", "auto-read-only": true, "discard": "unmap", "aio": "threads", "filename": "/home/kvm_autotest_root/images/stg2.qcow2", "cache": {"direct": true, "no-flush": false}}' \ + -blockdev '{"node-name": "drive_stg2", "driver": "qcow2", "read-only": false, "cache": {"direct": true, "no-flush": false}, "file": "file_stg2"}' \ + -device '{"driver": "virtio-blk-pci", "id": "stg2", "drive": "drive_stg2", "bootindex": 2, "write-cache": "on", "serial": "stg2", "num-queues": 6, "iothread-vq-mapping": [{"iothread": "t1", "vqs": [0, 1, 2]}, {"iothread": "t2", "vqs": [3]}, {"iothread": "t4", "vqs": [4, 5]}], "bus": "pci.0", "addr": "0x5"}' \ + -device '{"driver": "virtio-net-pci", "mac": "9a:5b:6c:5f:5b:5b", "id": "iddNmpYv", "netdev": "idG9Emyl", "bus": "pci.0", "addr": "0x6"}' \ + -netdev '{"id": "idG9Emyl", "type": "tap", "vhost": true}' \ + -vnc :0 \ + -rtc base=utc,clock=host,driftfix=slew \ + -boot menu=off,order=cdn,once=c,strict=off \ + -enable-kvm \ + +2. Continue VM: \ + {"execute": "cont"} \ + +3. Check disk info before hot unplug: \ + (guest)#ls /dev/[vhs]d* | grep -v [0-9]$ \ + +4. Unplug device from vm: \ + {"execute": "device_del", "arguments": {"id": "stg1"}} \ + {"timestamp": {"seconds": 1704360854, "microseconds": 751289}, "event": "DEVICE_DELETED", "data": {"path": "/machine/peripheral/stg1/virtio-backend"}} \ + {"timestamp": {"seconds": 1704360854, "microseconds": 752078}, "event": "DEVICE_DELETED", "data": {"device": "stg1", "path": "/machine/peripheral/stg1"}} \ + +5. Check device info via "info qtree": \ + {"execute": "human-monitor-command", "arguments": {"command-line": "info qtree"}} \ + +Actual Result: \ + After step5, qemu core dump with info: \ + qemu-system-x86_64: ../qapi/string-output-visitor.c:316: start_list: Assertion `sov->list_mode == LM_NONE' failed. \ + /tmp/aexpect_fNRmaiS3/aexpect-okx056xs.sh: line 1: 480254 Aborted (core dumped) MALLOC_PERTURB_=1 qemu-system-x86_64 -S -name 'avocado-vt-vm1' -machine pc,memory-backend=mem-machine_mem ... \ + +Coredump info as bellow: \ + #coredumpctl debug 480254 \ + Stack trace of thread 480254: + #0 0x00007f9397ea365c __pthread_kill_implementation (libc.so.6 + 0xa365c) \ + #1 0x00007f9397e54d06 __GI_raise (libc.so.6 + 0x54d06) \ + #2 0x00007f9397e287f3 __GI_abort (libc.so.6 + 0x287f3) \ + #3 0x00007f9397e2871b __assert_fail_base (libc.so.6 + 0x2871b) \ + #4 0x00007f9397e4dca6 __assert_fail (libc.so.6 + 0x4dca6) \ + #5 0x000056472e810e0d start_list (qemu-system-x86_64 + 0xa92e0d) \ + #6 0x000056472e80acb9 visit_start_list (qemu-system-x86_64 + 0xa8ccb9) \ + #7 0x000056472e75e9c0 visit_type_uint16List (qemu-system-x86_64 + 0x9e09c0) \ + #8 0x000056472e7e9955 visit_type_IOThreadVirtQueueMapping_members (qemu-system-x86_64 + 0xa6b955) \ + #9 0x000056472e7e9a1b visit_type_IOThreadVirtQueueMapping (qemu-system-x86_64 + 0xa6ba1b) \ + #10 0x000056472e7e9b0d visit_type_IOThreadVirtQueueMappingList (qemu-system-x86_64 + 0xa6bb0d) \ + #11 0x000056472e1519b2 get_iothread_vq_mapping_list (qemu-system-x86_64 + 0x3d39b2) \ + #12 0x000056472e629d0f field_prop_get (qemu-system-x86_64 + 0x8abd0f) \ + #13 0x000056472e635b24 object_property_get (qemu-system-x86_64 + 0x8b7b24) \ + #14 0x000056472e6368b3 object_property_print (qemu-system-x86_64 + 0x8b88b3) \ + #15 0x000056472e38f97a qdev_print_props (qemu-system-x86_64 + 0x61197a) \ + #16 0x000056472e38fc9f qdev_print (qemu-system-x86_64 + 0x611c9f) \ + #17 0x000056472e38fdd9 qbus_print (qemu-system-x86_64 + 0x611dd9) \ + #18 0x000056472e38fd03 qdev_print (qemu-system-x86_64 + 0x611d03) \ + #19 0x000056472e38fdd9 qbus_print (qemu-system-x86_64 + 0x611dd9) \ + #20 0x000056472e38fd03 qdev_print (qemu-system-x86_64 + 0x611d03) \ + #21 0x000056472e38fdd9 qbus_print (qemu-system-x86_64 + 0x611dd9) \ + #22 0x000056472e38fe26 hmp_info_qtree (qemu-system-x86_64 + 0x611e26) \ + #23 0x000056472e3ed6ed handle_hmp_command_exec (qemu-system-x86_64 + 0x66f6ed) \ + #24 0x000056472e3ed91a handle_hmp_command (qemu-system-x86_64 + 0x66f91a) \ + #25 0x000056472e3eef02 qmp_human_monitor_command (qemu-system-x86_64 + 0x670f02) \ + #26 0x000056472e7cc89b qmp_marshal_human_monitor_command (qemu-system-x86_64 + 0xa4e89b) \ + #27 0x000056472e8117d0 do_qmp_dispatch_bh (qemu-system-x86_64 + 0xa937d0) \ + #28 0x000056472e83be78 aio_bh_call (qemu-system-x86_64 + 0xabde78) \ + #29 0x000056472e83bf93 aio_bh_poll (qemu-system-x86_64 + 0xabdf93) \ + #30 0x000056472e81eb3e aio_dispatch (qemu-system-x86_64 + 0xaa0b3e) \ + #31 0x000056472e83c3d2 aio_ctx_dispatch (qemu-system-x86_64 + 0xabe3d2) \ + #32 0x00007f939829ff4f g_main_dispatch (libglib-2.0.so.0 + 0x54f4f) \ + #33 0x000056472e83d8a8 glib_pollfds_poll (qemu-system-x86_64 + 0xabf8a8) \ + #34 0x000056472e83d925 os_host_main_loop_wait (qemu-system-x86_64 + 0xabf925) \ + #35 0x000056472e83da33 main_loop_wait (qemu-system-x86_64 + 0xabfa33) \ + #36 0x000056472e396150 qemu_main_loop (qemu-system-x86_64 + 0x618150) \ + #37 0x000056472e628b7f qemu_default_main (qemu-system-x86_64 + 0x8aab7f) \ + #38 0x000056472e628bba main (qemu-system-x86_64 + 0x8aabba) \ + #39 0x00007f9397e3feb0 __libc_start_call_main (libc.so.6 + 0x3feb0) \ + #40 0x00007f9397e3ff60 __libc_start_main_impl (libc.so.6 + 0x3ff60) \ + #41 0x000056472e08e435 _start (qemu-system-x86_64 + 0x310435) \ + \ + Stack trace of thread 480255: \ + #0 0x00007f9397e3ee5d syscall (libc.so.6 + 0x3ee5d) \ + #1 0x000056472e82343c qemu_futex_wait (qemu-system-x86_64 + 0xaa543c) \ + #2 0x000056472e823623 qemu_event_wait (qemu-system-x86_64 + 0xaa5623) \ + #3 0x000056472e830d03 call_rcu_thread (qemu-system-x86_64 + 0xab2d03) \ + #4 0x000056472e8237d6 qemu_thread_start (qemu-system-x86_64 + 0xaa57d6) \ + #5 0x00007f9397ea1912 start_thread (libc.so.6 + 0xa1912) \ + #6 0x00007f9397e3f450 __clone3 (libc.so.6 + 0x3f450) \ + \ + Stack trace of thread 480258: \ + #0 0x00007f9397f429be __ppoll (libc.so.6 + 0x1429be) \ + #1 0x000056472e841cf0 qemu_poll_ns (qemu-system-x86_64 + 0xac3cf0) \ + #2 0x000056472e81f95f fdmon_poll_wait (qemu-system-x86_64 + 0xaa195f) \ + #3 0x000056472e81f29b aio_poll (qemu-system-x86_64 + 0xaa129b) \ + #4 0x000056472e67440c iothread_run (qemu-system-x86_64 + 0x8f640c) \ + #5 0x000056472e8237d6 qemu_thread_start (qemu-system-x86_64 + 0xaa57d6) \ + #6 0x00007f9397ea1912 start_thread (libc.so.6 + 0xa1912) \ + #7 0x00007f9397e3f450 __clone3 (libc.so.6 + 0x3f450) \ + \ + Stack trace of thread 480266: \ + #0 0x00007f9397e3ec6b ioctl (libc.so.6 + 0x3ec6b) \ + #1 0x000056472e619a24 kvm_vcpu_ioctl (qemu-system-x86_64 + 0x89ba24) \ + #2 0x000056472e619236 kvm_cpu_exec (qemu-system-x86_64 + 0x89b236) \ + #3 0x000056472e61c0fc kvm_vcpu_thread_fn (qemu-system-x86_64 + 0x89e0fc) \ + #4 0x000056472e8237d6 qemu_thread_start (qemu-system-x86_64 + 0xaa57d6) \ + #5 0x00007f9397ea1912 start_thread (libc.so.6 + 0xa1912) \ + #6 0x00007f9397e3f450 __clone3 (libc.so.6 + 0x3f450) \ + \ + Stack trace of thread 480267: \ + #0 0x00007f9397e3ec6b ioctl (libc.so.6 + 0x3ec6b) \ + #1 0x000056472e619a24 kvm_vcpu_ioctl (qemu-system-x86_64 + 0x89ba24) \ + #2 0x000056472e619236 kvm_cpu_exec (qemu-system-x86_64 + 0x89b236) \ + #3 0x000056472e61c0fc kvm_vcpu_thread_fn (qemu-system-x86_64 + 0x89e0fc) \ + #4 0x000056472e8237d6 qemu_thread_start (qemu-system-x86_64 + 0xaa57d6) \ + #5 0x00007f9397ea1912 start_thread (libc.so.6 + 0xa1912) \ + #6 0x00007f9397e3f450 __clone3 (libc.so.6 + 0x3f450) \ + \ + Stack trace of thread 480257: \ + #0 0x00007f9397f429be __ppoll (libc.so.6 + 0x1429be) \ + #1 0x000056472e841cf0 qemu_poll_ns (qemu-system-x86_64 + 0xac3cf0) \ + #2 0x000056472e81f95f fdmon_poll_wait (qemu-system-x86_64 + 0xaa195f) \ + #3 0x000056472e81f29b aio_poll (qemu-system-x86_64 + 0xaa129b) \ + #4 0x000056472e67440c iothread_run (qemu-system-x86_64 + 0x8f640c) \ + #5 0x000056472e8237d6 qemu_thread_start (qemu-system-x86_64 + 0xaa57d6) \ + #6 0x00007f9397ea1912 start_thread (libc.so.6 + 0xa1912) \ + #7 0x00007f9397e3f450 __clone3 (libc.so.6 + 0x3f450) \ + \ + Stack trace of thread 480256: \ + #0 0x00007f9397f429be __ppoll (libc.so.6 + 0x1429be) \ + #1 0x000056472e841d87 qemu_poll_ns (qemu-system-x86_64 + 0xac3d87) \ + #2 0x000056472e81f95f fdmon_poll_wait (qemu-system-x86_64 + 0xaa195f) \ + #3 0x000056472e81f29b aio_poll (qemu-system-x86_64 + 0xaa129b) \ + #4 0x000056472e67440c iothread_run (qemu-system-x86_64 + 0x8f640c) \ + #5 0x000056472e8237d6 qemu_thread_start (qemu-system-x86_64 + 0xaa57d6) \ + #6 0x00007f9397ea1912 start_thread (libc.so.6 + 0xa1912) \ + #7 0x00007f9397e3f450 __clone3 (libc.so.6 + 0x3f450) \ + \ + Stack trace of thread 480260: \ + #0 0x00007f9397e9e4aa __futex_abstimed_wait_common64 (libc.so.6 + 0x9e4aa) \ + #1 0x00007f9397ea0fb4 __pthread_cond_wait_common (libc.so.6 + 0xa0fb4) \ + #2 0x000056472e823041 qemu_cond_timedwait_ts (qemu-system-x86_64 + 0xaa5041) \ + #3 0x000056472e8230dc qemu_cond_timedwait_impl (qemu-system-x86_64 + 0xaa50dc) \ + #4 0x000056472e840595 worker_thread (qemu-system-x86_64 + 0xac2595) \ + #5 0x000056472e8237d6 qemu_thread_start (qemu-system-x86_64 + 0xaa57d6) \ + #6 0x00007f9397ea1912 start_thread (libc.so.6 + 0xa1912) \ + #7 0x00007f9397e3f450 __clone3 (libc.so.6 + 0x3f450) \ + \ + Stack trace of thread 480264: \ + #0 0x00007f9397f428bf __GI___poll (libc.so.6 + 0x1428bf) \ + #1 0x00007f93982f51fc g_main_context_poll (libglib-2.0.so.0 + 0xaa1fc) \ + #2 0x00007f939829f5a3 g_main_loop_run (libglib-2.0.so.0 + 0x545a3) \ + #3 0x000056472e67443f iothread_run (qemu-system-x86_64 + 0x8f643f) \ + #4 0x000056472e8237d6 qemu_thread_start (qemu-system-x86_64 + 0xaa57d6) \ + #5 0x00007f9397ea1912 start_thread (libc.so.6 + 0xa1912) \ + #6 0x00007f9397e3f450 __clone3 (libc.so.6 + 0x3f450) \ + \ + Stack trace of thread 480274: \ + #0 0x00007f9397e3ec6b ioctl (libc.so.6 + 0x3ec6b) \ + #1 0x000056472e619a24 kvm_vcpu_ioctl (qemu-system-x86_64 + 0x89ba24) \ + #2 0x000056472e619236 kvm_cpu_exec (qemu-system-x86_64 + 0x89b236) \ + #3 0x000056472e61c0fc kvm_vcpu_thread_fn (qemu-system-x86_64 + 0x89e0fc) \ + #4 0x000056472e8237d6 qemu_thread_start (qemu-system-x86_64 + 0xaa57d6) \ + #5 0x00007f9397ea1912 start_thread (libc.so.6 + 0xa1912) \ + #6 0x00007f9397e3f450 __clone3 (libc.so.6 + 0x3f450) \ + \ + Stack trace of thread 480337: \ + #0 0x00007f9397e9e4aa __futex_abstimed_wait_common64 (libc.so.6 + 0x9e4aa) \ + #1 0x00007f9397ea0fb4 __pthread_cond_wait_common (libc.so.6 + 0xa0fb4) \ + #2 0x000056472e823041 qemu_cond_timedwait_ts (qemu-system-x86_64 + 0xaa5041) \ + #3 0x000056472e8230dc qemu_cond_timedwait_impl (qemu-system-x86_64 + 0xaa50dc) \ + #4 0x000056472e840595 worker_thread (qemu-system-x86_64 + 0xac2595) \ + #5 0x000056472e8237d6 qemu_thread_start (qemu-system-x86_64 + 0xaa57d6) \ + #6 0x00007f9397ea1912 start_thread (libc.so.6 + 0xa1912) \ + #7 0x00007f9397e3f450 __clone3 (libc.so.6 + 0x3f450) \ + \ + Stack trace of thread 480273: \ + #0 0x00007f9397e3ec6b ioctl (libc.so.6 + 0x3ec6b) \ + #1 0x000056472e619a24 kvm_vcpu_ioctl (qemu-system-x86_64 + 0x89ba24) \ + #2 0x000056472e619236 kvm_cpu_exec (qemu-system-x86_64 + 0x89b236) \ + #3 0x000056472e61c0fc kvm_vcpu_thread_fn (qemu-system-x86_64 + 0x89e0fc) \ + #4 0x000056472e8237d6 qemu_thread_start (qemu-system-x86_64 + 0xaa57d6) \ + #5 0x00007f9397ea1912 start_thread (libc.so.6 + 0xa1912) \ + #6 0x00007f9397e3f450 __clone3 (libc.so.6 + 0x3f450) \ + \ + Stack trace of thread 480358: \ + #0 0x00007f9397e9e4aa __futex_abstimed_wait_common64 (libc.so.6 + 0x9e4aa) \ + #1 0x00007f9397ea0fb4 __pthread_cond_wait_common (libc.so.6 + 0xa0fb4) \ + #2 0x000056472e823041 qemu_cond_timedwait_ts (qemu-system-x86_64 + 0xaa5041) \ + #3 0x000056472e8230dc qemu_cond_timedwait_impl (qemu-system-x86_64 + 0xaa50dc) \ + #4 0x000056472e840595 worker_thread (qemu-system-x86_64 + 0xac2595) \ + #5 0x000056472e8237d6 qemu_thread_start (qemu-system-x86_64 + 0xaa57d6) \ + #6 0x00007f9397ea1912 start_thread (libc.so.6 + 0xa1912) \ + #7 0x00007f9397e3f450 __clone3 (libc.so.6 + 0x3f450) \ + \ + Stack trace of thread 480276: \ + #0 0x00007f9397e9e4aa __futex_abstimed_wait_common64 (libc.so.6 + 0x9e4aa) \ + #1 0x00007f9397ea0cb0 __pthread_cond_wait_common (libc.so.6 + 0xa0cb0) \ + #2 0x000056472e822f8e qemu_cond_wait_impl (qemu-system-x86_64 + 0xaa4f8e) \ + #3 0x000056472e0c6f39 vnc_worker_thread_loop (qemu-system-x86_64 + 0x348f39) \ + #4 0x000056472e0c7544 vnc_worker_thread (qemu-system-x86_64 + 0x349544) \ + #5 0x000056472e8237d6 qemu_thread_start (qemu-system-x86_64 + 0xaa57d6) \ + #6 0x00007f9397ea1912 start_thread (libc.so.6 + 0xa1912) \ + #7 0x00007f9397e3f450 __clone3 (libc.so.6 + 0x3f450) \ + \ + Stack trace of thread 480259: \ + #0 0x00007f9397f429be __ppoll (libc.so.6 + 0x1429be) \ + #1 0x000056472e841cf0 qemu_poll_ns (qemu-system-x86_64 + 0xac3cf0) \ + #2 0x000056472e81f95f fdmon_poll_wait (qemu-system-x86_64 + 0xaa195f) \ + #3 0x000056472e81f29b aio_poll (qemu-system-x86_64 + 0xaa129b) \ + #4 0x000056472e67440c iothread_run (qemu-system-x86_64 + 0x8f640c) \ + #5 0x000056472e8237d6 qemu_thread_start (qemu-system-x86_64 + 0xaa57d6) \ + #6 0x00007f9397ea1912 start_thread (libc.so.6 + 0xa1912) \ + #7 0x00007f9397e3f450 __clone3 (libc.so.6 + 0x3f450) \ + \ + Stack trace of thread 480357: \ + #0 0x00007f9397e9e4aa __futex_abstimed_wait_common64 (libc.so.6 + 0x9e4aa) \ + #1 0x00007f9397ea0fb4 __pthread_cond_wait_common (libc.so.6 + 0xa0fb4) \ + #2 0x000056472e823041 qemu_cond_timedwait_ts (qemu-system-x86_64 + 0xaa5041) \ + #3 0x000056472e8230dc qemu_cond_timedwait_impl (qemu-system-x86_64 + 0xaa50dc) \ + #4 0x000056472e840595 worker_thread (qemu-system-x86_64 + 0xac2595) \ + #5 0x000056472e8237d6 qemu_thread_start (qemu-system-x86_64 + 0xaa57d6) \ + #6 0x00007f9397ea1912 start_thread (libc.so.6 + 0xa1912)\ + #7 0x00007f9397e3f450 __clone3 (libc.so.6 + 0x3f450) \ + \ + Stack trace of thread 480268: \ + #0 0x00007f9397e3ec6b ioctl (libc.so.6 + 0x3ec6b) \ + #1 0x000056472e619a24 kvm_vcpu_ioctl (qemu-system-x86_64 + 0x89ba24) \ + #2 0x000056472e619236 kvm_cpu_exec (qemu-system-x86_64 + 0x89b236) \ + #3 0x000056472e61c0fc kvm_vcpu_thread_fn (qemu-system-x86_64 + 0x89e0fc) \ + #4 0x000056472e8237d6 qemu_thread_start (qemu-system-x86_64 + 0xaa57d6) \ + #5 0x00007f9397ea1912 start_thread (libc.so.6 + 0xa1912) \ + #6 0x00007f9397e3f450 __clone3 (libc.so.6 + 0x3f450) \ + \ + Stack trace of thread 480269: \ + #0 0x00007f9397e3ec6b ioctl (libc.so.6 + 0x3ec6b) \ + #1 0x000056472e619a24 kvm_vcpu_ioctl (qemu-system-x86_64 + 0x89ba24) \ + #2 0x000056472e619236 kvm_cpu_exec (qemu-system-x86_64 + 0x89b236) \ + #3 0x000056472e61c0fc kvm_vcpu_thread_fn (qemu-system-x86_64 + 0x89e0fc) \ + #4 0x000056472e8237d6 qemu_thread_start (qemu-system-x86_64 + 0xaa57d6) \ + #5 0x00007f9397ea1912 start_thread (libc.so.6 + 0xa1912) \ + #6 0x00007f9397e3f450 __clone3 (libc.so.6 + 0x3f450) \ + \ + Stack trace of thread 480353: \ + #0 0x00007f9397e9e4aa __futex_abstimed_wait_common64 (libc.so.6 + 0x9e4aa) \ + #1 0x00007f9397ea0fb4 __pthread_cond_wait_common (libc.so.6 + 0xa0fb4) \ + #2 0x000056472e823041 qemu_cond_timedwait_ts (qemu-system-x86_64 + 0xaa5041) \ + #3 0x000056472e8230dc qemu_cond_timedwait_impl (qemu-system-x86_64 + 0xaa50dc) \ + #4 0x000056472e840595 worker_thread (qemu-system-x86_64 + 0xac2595) \ + #5 0x000056472e8237d6 qemu_thread_start (qemu-system-x86_64 + 0xaa57d6) \ + #6 0x00007f9397ea1912 start_thread (libc.so.6 + 0xa1912) \ + #7 0x00007f9397e3f450 __clone3 (libc.so.6 + 0x3f450) \ + \ + Stack trace of thread 480271: \ + #0 0x00007f9397e3ec6b ioctl (libc.so.6 + 0x3ec6b) \ + #1 0x000056472e619a24 kvm_vcpu_ioctl (qemu-system-x86_64 + 0x89ba24) \ + #2 0x000056472e619236 kvm_cpu_exec (qemu-system-x86_64 + 0x89b236) \ + #3 0x000056472e61c0fc kvm_vcpu_thread_fn (qemu-system-x86_64 + 0x89e0fc) \ + #4 0x000056472e8237d6 qemu_thread_start (qemu-system-x86_64 + 0xaa57d6) \ + #5 0x00007f9397ea1912 start_thread (libc.so.6 + 0xa1912) \ + #6 0x00007f9397e3f450 __clone3 (libc.so.6 + 0x3f450) \ + \ + Stack trace of thread 480354: \ + #0 0x00007f9397e9e4aa __futex_abstimed_wait_common64 (libc.so.6 + 0x9e4aa) \ + #1 0x00007f9397ea0fb4 __pthread_cond_wait_common (libc.so.6 + 0xa0fb4) \ + #2 0x000056472e823041 qemu_cond_timedwait_ts (qemu-system-x86_64 + 0xaa5041) \ + #3 0x000056472e8230dc qemu_cond_timedwait_impl (qemu-system-x86_64 + 0xaa50dc) \ + #4 0x000056472e840595 worker_thread (qemu-system-x86_64 + 0xac2595) \ + #5 0x000056472e8237d6 qemu_thread_start (qemu-system-x86_64 + 0xaa57d6) \ + #6 0x00007f9397ea1912 start_thread (libc.so.6 + 0xa1912) \ + #7 0x00007f9397e3f450 __clone3 (libc.so.6 + 0x3f450) \ + \ + Stack trace of thread 480356: \ + #0 0x00007f9397e9e4aa __futex_abstimed_wait_common64 (libc.so.6 + 0x9e4aa) \ + #1 0x00007f9397ea0fb4 __pthread_cond_wait_common (libc.so.6 + 0xa0fb4) \ + #2 0x000056472e823041 qemu_cond_timedwait_ts (qemu-system-x86_64 + 0xaa5041) \ + #3 0x000056472e8230dc qemu_cond_timedwait_impl (qemu-system-x86_64 + 0xaa50dc) \ + #4 0x000056472e840595 worker_thread (qemu-system-x86_64 + 0xac2595) \ + #5 0x000056472e8237d6 qemu_thread_start (qemu-system-x86_64 + 0xaa57d6) \ + #6 0x00007f9397ea1912 start_thread (libc.so.6 + 0xa1912) \ + #7 0x00007f9397e3f450 __clone3 (libc.so.6 + 0x3f450) \ + \ + Stack trace of thread 480355: \ + #0 0x00007f9397e9e4aa __futex_abstimed_wait_common64 (libc.so.6 + 0x9e4aa) \ + #1 0x00007f9397ea0fb4 __pthread_cond_wait_common (libc.so.6 + 0xa0fb4) \ + #2 0x000056472e823041 qemu_cond_timedwait_ts (qemu-system-x86_64 + 0xaa5041) \ + #3 0x000056472e8230dc qemu_cond_timedwait_impl (qemu-system-x86_64 + 0xaa50dc) \ + #4 0x000056472e840595 worker_thread (qemu-system-x86_64 + 0xac2595) \ + #5 0x000056472e8237d6 qemu_thread_start (qemu-system-x86_64 + 0xaa57d6) \ + #6 0x00007f9397ea1912 start_thread (libc.so.6 + 0xa1912) \ + #7 0x00007f9397e3f450 __clone3 (libc.so.6 + 0x3f450) \ + \ + Stack trace of thread 480270: \ + #0 0x00007f9397e3ec6b ioctl (libc.so.6 + 0x3ec6b) \ + #1 0x000056472e619a24 kvm_vcpu_ioctl (qemu-system-x86_64 + 0x89ba24) \ + #2 0x000056472e619236 kvm_cpu_exec (qemu-system-x86_64 + 0x89b236) \ + #3 0x000056472e61c0fc kvm_vcpu_thread_fn (qemu-system-x86_64 + 0x89e0fc) \ + #4 0x000056472e8237d6 qemu_thread_start (qemu-system-x86_64 + 0xaa57d6) \ + #5 0x00007f9397ea1912 start_thread (libc.so.6 + 0xa1912) \ + #6 0x00007f9397e3f450 __clone3 (libc.so.6 + 0x3f450) \ + \ + Stack trace of thread 480272: \ + #0 0x00007f9397e3ec6b ioctl (libc.so.6 + 0x3ec6b) \ + #1 0x000056472e619a24 kvm_vcpu_ioctl (qemu-system-x86_64 + 0x89ba24) \ + #2 0x000056472e619236 kvm_cpu_exec (qemu-system-x86_64 + 0x89b236) \ + #3 0x000056472e61c0fc kvm_vcpu_thread_fn (qemu-system-x86_64 + 0x89e0fc) \ + #4 0x000056472e8237d6 qemu_thread_start (qemu-system-x86_64 + 0xaa57d6) \ + #5 0x00007f9397ea1912 start_thread (libc.so.6 + 0xa1912) \ + #6 0x00007f9397e3f450 __clone3 (libc.so.6 + 0x3f450) \ + \ + Stack trace of thread 480265: \ + #0 0x00007f9397e3ec6b ioctl (libc.so.6 + 0x3ec6b) \ + #1 0x000056472e619a24 kvm_vcpu_ioctl (qemu-system-x86_64 + 0x89ba24) \ + #2 0x000056472e619236 kvm_cpu_exec (qemu-system-x86_64 + 0x89b236) \ + #3 0x000056472e61c0fc kvm_vcpu_thread_fn (qemu-system-x86_64 + 0x89e0fc) \ + #4 0x000056472e8237d6 qemu_thread_start (qemu-system-x86_64 + 0xaa57d6) \ + #5 0x00007f9397ea1912 start_thread (libc.so.6 + 0xa1912) \ + #6 0x00007f9397e3f450 __clone3 (libc.so.6 + 0x3f450) \ + ELF object binary architecture: AMD x86-64 \ diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/207 b/gitlab/issues_text/target_missing/host_missing/accel_missing/207 new file mode 100644 index 000000000..0f29d617a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/207 @@ -0,0 +1 @@ +move ./scripts/qmp to ./python/qemu/qmp diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2071 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2071 new file mode 100644 index 000000000..481d11bad --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2071 @@ -0,0 +1,112 @@ +Segfault when starting a guest with spice configured to listen on a unix socket +Description of problem: +Guest crash immediately when spice is configured to listen on a unix socket. +Steps to reproduce: +1. Configure spice to listen on a unix socket +2. Start the guest +Additional information: +Here's the log when I start the guest: + +``` +[root@localhost ~]# virsh start fedora-waydroid +error: Failed to start domain 'fedora-waydroid' +error: internal error: qemu unexpectedly closed the monitor +``` +Here's the relevant output in journald: + +`SECCOMP auid=4294967295 uid=107 gid=107 ses=4294967295 pid=17930 comm="qemu-system-x86" exe="/usr/bin/qemu-system-x86_64" sig=31 arch=c000003e syscall=56 compat=0 ip=0x7f7b95459397 code=0x80000000` + +<details><summary>Full journald</summary> + +``` +Jan 04 11:59:03 localhost polkitd[1436]: Registered Authentication Agent for unix-process:17895:5747660 (system bus name :1.160 [/usr/bin/pkttyagent --process 17895 --notify-fd 4 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) +Jan 04 11:59:03 localhost audit[1595]: VIRT_MACHINE_ID pid=1595 uid=0 auid=4294967295 ses=4294967295 msg='virt=kvm vm="fedora-waydroid" uuid=abcdefgh-ijkl-mnop-qrst-uvwx12345678 vm-ctx=+107:+107 img-ctx=+107:+107 model=dac exe="/usr/sbin/virtqemud" hostname=? addr=? terminal=? res=success' +Jan 04 11:59:03 localhost virtlogd[1659]: Client hit max requests limit 1. This may result in keep-alive timeouts. Consider tuning the max_client_requests server parameter +Jan 04 11:59:03 localhost virtlogd[1659]: Client hit max requests limit 1. This may result in keep-alive timeouts. Consider tuning the max_client_requests server parameter +Jan 04 11:59:03 localhost polkitd[1436]: Unregistered Authentication Agent for unix-process:17895:5747660 (system bus name :1.160, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus) +Jan 04 11:59:03 localhost audit: ANOM_PROMISCUOUS dev=vnet12 prom=256 old_prom=0 auid=4294967295 uid=0 gid=0 ses=4294967295 +Jan 04 11:59:03 localhost audit[1595]: VIRT_RESOURCE pid=1595 uid=0 auid=4294967295 ses=4294967295 msg='virt=kvm resrc=net reason=open vm="fedora-waydroid" uuid=abcdefgh-ijkl-mnop-qrst-uvwx12345678 net=52:54:00:72:c3:92 path="/dev/net/tun" rdev=0A:C8 exe="/usr/sbin/virtqemud" hostname=? addr=? terminal=? res=success' +Jan 04 11:59:03 localhost audit[1595]: VIRT_RESOURCE pid=1595 uid=0 auid=4294967295 ses=4294967295 msg='virt=kvm resrc=net reason=open vm="fedora-waydroid" uuid=abcdefgh-ijkl-mnop-qrst-uvwx12345678 net=52:54:00:72:c3:92 path="/dev/vhost-net" rdev=0A:EE exe="/usr/sbin/virtqemud" hostname=? addr=? terminal=? res=success' +Jan 04 11:59:03 localhost NetworkManager[1338]: <info> [1704394743.2422] manager: (vnet12): new Tun device (/org/freedesktop/NetworkManager/Devices/19) +Jan 04 11:59:03 localhost kernel: br-dmz: port 4(vnet12) entered blocking state +Jan 04 11:59:03 localhost kernel: br-dmz: port 4(vnet12) entered disabled state +Jan 04 11:59:03 localhost kernel: vnet12: entered allmulticast mode +Jan 04 11:59:03 localhost kernel: vnet12: entered promiscuous mode +Jan 04 11:59:03 localhost kernel: br-dmz: port 4(vnet12) entered blocking state +Jan 04 11:59:03 localhost kernel: br-dmz: port 4(vnet12) entered forwarding state +Jan 04 11:59:03 localhost NetworkManager[1338]: <info> [1704394743.2468] device (vnet12): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external') +Jan 04 11:59:03 localhost NetworkManager[1338]: <info> [1704394743.2470] device (vnet12): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external') +Jan 04 11:59:03 localhost NetworkManager[1338]: <info> [1704394743.2473] device (vnet12): Activation: starting connection 'vnet12' (abcdefgh-ijkl-mnop-qrst-uvwx12345679) +Jan 04 11:59:03 localhost NetworkManager[1338]: <info> [1704394743.2478] device (vnet12): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external') +Jan 04 11:59:03 localhost NetworkManager[1338]: <info> [1704394743.2479] device (vnet12): state change: prepare -> config (reason 'none', sys-iface-state: 'external') +Jan 04 11:59:03 localhost NetworkManager[1338]: <info> [1704394743.2480] device (vnet12): state change: config -> ip-config (reason 'none', sys-iface-state: 'external') +Jan 04 11:59:03 localhost NetworkManager[1338]: <info> [1704394743.2480] device (br-dmz): bridge port vnet12 was attached +Jan 04 11:59:03 localhost NetworkManager[1338]: <info> [1704394743.2480] device (vnet12): Activation: connection 'vnet12' enslaved, continuing activation +Jan 04 11:59:03 localhost NetworkManager[1338]: <info> [1704394743.2481] device (vnet12): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external') +Jan 04 11:59:03 localhost systemd-machined[1368]: New machine qemu-10-fedora-waydroid. +Jan 04 11:59:03 localhost systemd[1]: Started machine-qemu\x2d10\x2dfedora\x2dwaydroid.scope - Virtual Machine qemu-10-fedora-waydroid. +Jan 04 11:59:03 localhost systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service... +Jan 04 11:59:03 localhost audit: BPF prog-id=112 op=LOAD +Jan 04 11:59:03 localhost audit[1595]: VIRT_RESOURCE pid=1595 uid=0 auid=4294967295 ses=4294967295 msg='virt=kvm resrc=cgroup reason=deny vm="fedora-waydroid" uuid=abcdefgh-ijkl-mnop-qrst-uvwx12345678 cgroup="/sys/fs/cgroup/machine.slice/machine-qemu\x2d10\x2dfedora\x2dwaydroid.scope/" class=all exe="/usr/sbin/virtqemud" hostname=? addr=? terminal=? res=success' +Jan 04 11:59:03 localhost audit[1595]: VIRT_RESOURCE pid=1595 uid=0 auid=4294967295 ses=4294967295 msg='virt=kvm resrc=cgroup reason=allow vm="fedora-waydroid" uuid=abcdefgh-ijkl-mnop-qrst-uvwx12345678 cgroup="/sys/fs/cgroup/machine.slice/machine-qemu\x2d10\x2dfedora\x2dwaydroid.scope/" class=path path="/dev/null" rdev=01:03 acl=rw exe="/usr/sbin/virtqemud" hostname=? addr=? terminal=? res=success' +Jan 04 11:59:03 localhost audit[1595]: VIRT_RESOURCE pid=1595 uid=0 auid=4294967295 ses=4294967295 msg='virt=kvm resrc=cgroup reason=allow vm="fedora-waydroid" uuid=abcdefgh-ijkl-mnop-qrst-uvwx12345678 cgroup="/sys/fs/cgroup/machine.slice/machine-qemu\x2d10\x2dfedora\x2dwaydroid.scope/" class=path path="/dev/full" rdev=01:07 acl=rw exe="/usr/sbin/virtqemud" hostname=? addr=? terminal=? res=success' +Jan 04 11:59:03 localhost audit[1595]: VIRT_RESOURCE pid=1595 uid=0 auid=4294967295 ses=4294967295 msg='virt=kvm resrc=cgroup reason=allow vm="fedora-waydroid" uuid=abcdefgh-ijkl-mnop-qrst-uvwx12345678 cgroup="/sys/fs/cgroup/machine.slice/machine-qemu\x2d10\x2dfedora\x2dwaydroid.scope/" class=path path="/dev/zero" rdev=01:05 acl=rw exe="/usr/sbin/virtqemud" hostname=? addr=? terminal=? res=success' +Jan 04 11:59:03 localhost audit[1595]: VIRT_RESOURCE pid=1595 uid=0 auid=4294967295 ses=4294967295 msg='virt=kvm resrc=cgroup reason=allow vm="fedora-waydroid" uuid=abcdefgh-ijkl-mnop-qrst-uvwx12345678 cgroup="/sys/fs/cgroup/machine.slice/machine-qemu\x2d10\x2dfedora\x2dwaydroid.scope/" class=path path="/dev/random" rdev=01:08 acl=rw exe="/usr/sbin/virtqemud" hostname=? addr=? terminal=? res=success' +Jan 04 11:59:03 localhost audit[1595]: VIRT_RESOURCE pid=1595 uid=0 auid=4294967295 ses=4294967295 msg='virt=kvm resrc=cgroup reason=allow vm="fedora-waydroid" uuid=abcdefgh-ijkl-mnop-qrst-uvwx12345678 cgroup="/sys/fs/cgroup/machine.slice/machine-qemu\x2d10\x2dfedora\x2dwaydroid.scope/" class=path path="/dev/urandom" rdev=01:09 acl=rw exe="/usr/sbin/virtqemud" hostname=? addr=? terminal=? res=success' +Jan 04 11:59:03 localhost audit[1595]: VIRT_RESOURCE pid=1595 uid=0 auid=4294967295 ses=4294967295 msg='virt=kvm resrc=cgroup reason=allow vm="fedora-waydroid" uuid=abcdefgh-ijkl-mnop-qrst-uvwx12345678 cgroup="/sys/fs/cgroup/machine.slice/machine-qemu\x2d10\x2dfedora\x2dwaydroid.scope/" class=path path="/dev/ptmx" rdev=05:02 acl=rw exe="/usr/sbin/virtqemud" hostname=? addr=? terminal=? res=success' +Jan 04 11:59:03 localhost audit[1595]: VIRT_RESOURCE pid=1595 uid=0 auid=4294967295 ses=4294967295 msg='virt=kvm resrc=cgroup reason=allow vm="fedora-waydroid" uuid=abcdefgh-ijkl-mnop-qrst-uvwx12345678 cgroup="/sys/fs/cgroup/machine.slice/machine-qemu\x2d10\x2dfedora\x2dwaydroid.scope/" class=path path="/dev/kvm" rdev=0A:E8 acl=rw exe="/usr/sbin/virtqemud" hostname=? addr=? terminal=? res=success' +Jan 04 11:59:03 localhost audit[1595]: VIRT_RESOURCE pid=1595 uid=0 auid=4294967295 ses=4294967295 msg='virt=kvm resrc=cgroup reason=allow vm="fedora-waydroid" uuid=abcdefgh-ijkl-mnop-qrst-uvwx12345678 cgroup="/sys/fs/cgroup/machine.slice/machine-qemu\x2d10\x2dfedora\x2dwaydroid.scope/" class=major category=pty maj=88 acl=rw exe="/usr/sbin/virtqemud" hostname=? addr=? terminal=? res=success' +Jan 04 11:59:03 localhost audit[1595]: VIRT_RESOURCE pid=1595 uid=0 auid=4294967295 ses=4294967295 msg='virt=kvm resrc=cgroup reason=allow vm="fedora-waydroid" uuid=abcdefgh-ijkl-mnop-qrst-uvwx12345678 cgroup="/sys/fs/cgroup/machine.slice/machine-qemu\x2d10\x2dfedora\x2dwaydroid.scope/" class=path path="/dev/dri/by-path/pci-0000:00:02.0-render" rdev=E2:80 acl=rw exe="/usr/sbin/virtqemud" hostname=? addr=? terminal=? res=success' +Jan 04 11:59:03 localhost audit[1595]: VIRT_RESOURCE pid=1595 uid=0 auid=4294967295 ses=4294967295 msg='virt=kvm resrc=cgroup reason=allow vm="fedora-waydroid" uuid=abcdefgh-ijkl-mnop-qrst-uvwx12345678 cgroup="/sys/fs/cgroup/machine.slice/machine-qemu\x2d10\x2dfedora\x2dwaydroid.scope/" class=path path="/dev/urandom" rdev=01:09 acl=rw exe="/usr/sbin/virtqemud" hostname=? addr=? terminal=? res=success' +Jan 04 11:59:03 localhost systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service. +Jan 04 11:59:03 localhost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' +Jan 04 11:59:03 localhost NetworkManager[1338]: <info> [1704394743.2796] device (vnet12): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external') +Jan 04 11:59:03 localhost NetworkManager[1338]: <info> [1704394743.2797] device (vnet12): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external') +Jan 04 11:59:03 localhost NetworkManager[1338]: <info> [1704394743.2799] device (vnet12): Activation: successful, device activated. +Jan 04 11:59:03 localhost systemd[1]: iscsi.service: Unit cannot be reloaded because it is inactive. +Jan 04 11:59:03 localhost audit[17930]: SECCOMP auid=4294967295 uid=107 gid=107 ses=4294967295 pid=17930 comm="qemu-system-x86" exe="/usr/bin/qemu-system-x86_64" sig=31 arch=c000003e syscall=56 compat=0 ip=0x7f7b95459397 code=0x80000000 +Jan 04 11:59:03 localhost audit[17930]: ANOM_ABEND auid=4294967295 uid=107 gid=107 ses=4294967295 pid=17930 comm="qemu-system-x86" exe="/usr/bin/qemu-system-x86_64" sig=31 res=1 +Jan 04 11:59:03 localhost audit: BPF prog-id=113 op=LOAD +Jan 04 11:59:03 localhost audit: BPF prog-id=114 op=LOAD +Jan 04 11:59:03 localhost audit: BPF prog-id=115 op=LOAD +Jan 04 11:59:03 localhost systemd[1]: Started systemd-coredump@3-17978-0.service - Process Core Dump (PID 17978/UID 0). +Jan 04 11:59:03 localhost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@3-17978-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' +Jan 04 11:59:03 localhost systemd-coredump[17980]: Resource limits disable core dumping for process 17930 (qemu-system-x86). +Jan 04 11:59:03 localhost systemd-coredump[17980]: [🡕] Process 17930 (qemu-system-x86) of user 107 terminated abnormally without generating a coredump. +Jan 04 11:59:03 localhost systemd[1]: systemd-coredump@3-17978-0.service: Deactivated successfully. +Jan 04 11:59:03 localhost audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@3-17978-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' +Jan 04 11:59:03 localhost audit: ANOM_PROMISCUOUS dev=vnet12 prom=0 old_prom=256 auid=4294967295 uid=107 gid=107 ses=4294967295 +Jan 04 11:59:03 localhost kernel: br-dmz: port 4(vnet12) entered disabled state +Jan 04 11:59:03 localhost kernel: vnet12 (unregistering): left allmulticast mode +Jan 04 11:59:03 localhost kernel: vnet12 (unregistering): left promiscuous mode +Jan 04 11:59:03 localhost kernel: br-dmz: port 4(vnet12) entered disabled state +Jan 04 11:59:03 localhost NetworkManager[1338]: <info> [1704394743.3895] device (vnet12): state change: activated -> unmanaged (reason 'unmanaged', sys-iface-state: 'removed') +Jan 04 11:59:03 localhost NetworkManager[1338]: <info> [1704394743.3897] device (vnet12): released from master device br-dmz +Jan 04 11:59:03 localhost virtqemud[1595]: Unable to read from monitor: Connection reset by peer +Jan 04 11:59:03 localhost virtqemud[1595]: internal error: qemu unexpectedly closed the monitor +Jan 04 11:59:03 localhost virtqemud[1595]: internal error: process exited while connecting to monitor +Jan 04 11:59:03 localhost virtlogd[1659]: Client hit max requests limit 1. This may result in keep-alive timeouts. Consider tuning the max_client_requests server parameter +Jan 04 11:59:03 localhost virtqemud[1595]: Failed to acquire pid file '/run/libvirt/qemu/swtpm/10-fedora-waydroid-swtpm.pid': Resource temporarily unavailable +Jan 04 11:59:03 localhost systemd[1]: machine-qemu\x2d10\x2dfedora\x2dwaydroid.scope: Deactivated successfully. +Jan 04 11:59:03 localhost systemd-machined[1368]: Machine qemu-10-fedora-waydroid terminated. +Jan 04 11:59:03 localhost audit: BPF prog-id=115 op=UNLOAD +Jan 04 11:59:03 localhost audit: BPF prog-id=114 op=UNLOAD +Jan 04 11:59:03 localhost audit: BPF prog-id=113 op=UNLOAD +Jan 04 11:59:03 localhost audit: BPF prog-id=112 op=UNLOAD +Jan 04 11:59:03 localhost audit[1595]: VIRT_RESOURCE pid=1595 uid=0 auid=4294967295 ses=4294967295 msg='virt=kvm resrc=disk reason=start vm="fedora-waydroid" uuid=abcdefgh-ijkl-mnop-qrst-uvwx12345678 old-disk="?" new-disk="/var/lib/libvirt/images/fedora-waydroid.img" exe="/usr/sbin/virtqemud" hostname=? addr=? terminal=? res=success' +Jan 04 11:59:03 localhost audit[1595]: VIRT_RESOURCE pid=1595 uid=0 auid=4294967295 ses=4294967295 msg='virt=kvm resrc=net reason=start vm="fedora-waydroid" uuid=abcdefgh-ijkl-mnop-qrst-uvwx12345678 old-net="?" new-net="52:54:00:72:c3:92" exe="/usr/sbin/virtqemud" hostname=? addr=? terminal=? res=success' +Jan 04 11:59:03 localhost audit[1595]: VIRT_RESOURCE pid=1595 uid=0 auid=4294967295 ses=4294967295 msg='virt=kvm resrc=dev reason=start vm="fedora-waydroid" uuid=abcdefgh-ijkl-mnop-qrst-uvwx12345678 bus=usb device=555342207265646972646576 exe="/usr/sbin/virtqemud" hostname=? addr=? terminal=? res=success' +Jan 04 11:59:03 localhost audit[1595]: VIRT_RESOURCE pid=1595 uid=0 auid=4294967295 ses=4294967295 msg='virt=kvm resrc=dev reason=start vm="fedora-waydroid" uuid=abcdefgh-ijkl-mnop-qrst-uvwx12345678 bus=usb device=555342207265646972646576 exe="/usr/sbin/virtqemud" hostname=? addr=? terminal=? res=success' +Jan 04 11:59:03 localhost audit[1595]: VIRT_RESOURCE pid=1595 uid=0 auid=4294967295 ses=4294967295 msg='virt=kvm resrc=rng reason=start vm="fedora-waydroid" uuid=abcdefgh-ijkl-mnop-qrst-uvwx12345678 old-rng="?" new-rng="/dev/urandom" exe="/usr/sbin/virtqemud" hostname=? addr=? terminal=? res=success' +Jan 04 11:59:03 localhost audit[1595]: VIRT_RESOURCE pid=1595 uid=0 auid=4294967295 ses=4294967295 msg='virt=kvm resrc=tpm-emulator reason=start vm="fedora-waydroid" uuid=abcdefgh-ijkl-mnop-qrst-uvwx12345678 device="?" exe="/usr/sbin/virtqemud" hostname=? addr=? terminal=? res=success' +Jan 04 11:59:03 localhost audit[1595]: VIRT_RESOURCE pid=1595 uid=0 auid=4294967295 ses=4294967295 msg='virt=kvm resrc=mem reason=start vm="fedora-waydroid" uuid=abcdefgh-ijkl-mnop-qrst-uvwx12345678 old-mem=0 new-mem=4194304 exe="/usr/sbin/virtqemud" hostname=? addr=? terminal=? res=success' +Jan 04 11:59:03 localhost audit[1595]: VIRT_RESOURCE pid=1595 uid=0 auid=4294967295 ses=4294967295 msg='virt=kvm resrc=vcpu reason=start vm="fedora-waydroid" uuid=abcdefgh-ijkl-mnop-qrst-uvwx12345678 old-vcpu=0 new-vcpu=4 exe="/usr/sbin/virtqemud" hostname=? addr=? terminal=? res=success' +Jan 04 11:59:03 localhost audit[1595]: VIRT_CONTROL pid=1595 uid=0 auid=4294967295 ses=4294967295 msg='virt=kvm op=start reason=booted vm="fedora-waydroid" uuid=abcdefgh-ijkl-mnop-qrst-uvwx12345678 vm-pid=0 exe="/usr/sbin/virtqemud" hostname=? addr=? terminal=? res=failed' +``` + +<details> + +For the record I filed a bug earlier in libvirt (https://gitlab.com/libvirt/libvirt/-/issues/573) but I now think it's qemu related. + + +/label ~"kind::Bug" diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2073 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2073 new file mode 100644 index 000000000..7461f6110 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2073 @@ -0,0 +1,16 @@ +Audio: missing ability to disable microphone input from host? +Description of problem: +**It appears there is no way to disable the microphone / input to the audio backend device(s).** + + +There are at least two cases where this matters: +1. The host has no microphone input (e.g. only HDMI audio output with video). +2. The host has a microphone input, but the user doesn't want the guest VM to have access to the microphone/input. + +I tried the option in.channels=0, as that seemed the most obvious way, though that doesn't work. + +For -audio dsound, it appears that CLSID_DirectSoundCapture is unconditionally acquired. + +There will also be later periodic warning/text outputs from QEMU "Could not create a backend for voice virtio.in", if you're running on a host system with no audio input device. + +Adding a couple backend checks for channels > 0 may work well. Not sure if it matters that audio front end device in the VM still thinks there is an audio input. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2075 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2075 new file mode 100644 index 000000000..7e6089dfe --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2075 @@ -0,0 +1,10 @@ +QGA guest-get-fsinfo can not return windows dynamic volumes +Description of problem: +Install qemu-ga (newest version) in Windows, create multiple dynamic volumes（containing multiple disks）, + + +get them information via guest-get-fsinfo, but guest-get-fsinfo does not return the the dynamic volume. +Steps to reproduce: +virsh qemu-agent-command {domain} --pretty '{ "execute": "guest-get-fsinfo" }' +Additional information: +Please see if this bug can be fixed by [qga-win: Fix guest-get-fsinfo multi-disks collection](https://patchew.org/QEMU/20231227071540.4035803-1-peng.ji@smartx.com/) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2076 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2076 new file mode 100644 index 000000000..814aa86e2 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2076 @@ -0,0 +1 @@ +stringop-overread warning in tests/tcg/multiarch/sha1.c diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2077 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2077 new file mode 100644 index 000000000..ed943d9e5 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2077 @@ -0,0 +1 @@ +flaky CI test: acpiBitsTest.test_acpi_smbios_bits diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/208 b/gitlab/issues_text/target_missing/host_missing/accel_missing/208 new file mode 100644 index 000000000..bc026d28b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/208 @@ -0,0 +1 @@ +Write a new, asynchronous qmp-shell TUI diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2080 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2080 new file mode 100644 index 000000000..164f817e8 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2080 @@ -0,0 +1 @@ +CI 'pages' job sometimes fails with "htags: Negative exec line limit" diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2081 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2081 new file mode 100644 index 000000000..538976cb7 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2081 @@ -0,0 +1,9 @@ +[OHCI] OHCI_CC_DEVICENOTRESPONDING not set when transferring to a disconnected device +Description of problem: +If a USB device is disconnected and is cleaned up by qemu, subsequent transfers to that device address are ignored. On a real OHCI controller `OHCI_CC_DEVICENOTRESPONDING` bit is set and is reported as an error to the host. + +qemu attempts to set it here https://github.com/qemu/qemu/blob/ffd454c67e38cc6df792733ebc5d967eee28ac0d/hw/usb/hcd-ohci.c#L795 which would work fine on a valid device handle. + +However this check https://github.com/qemu/qemu/blob/ffd454c67e38cc6df792733ebc5d967eee28ac0d/hw/usb/hcd-ohci.c#L975 leaves early if no device handle is found so the error code is never set. + +Fix is to set `OHCI_CC_DEVICENOTRESPONDING` if `ohci_find_device` fails before returning. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2082 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2082 new file mode 100644 index 000000000..db6b3fdc8 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2082 @@ -0,0 +1,44 @@ +"Unable to find a guest_base to satisfy all guest address mapping requirements" running certain x86_64 binaries on aarch64 host +Description of problem: +Copying from: + + https://bugzilla.redhat.com/show_bug.cgi?id=2256916 + +With ``qemu-x86_64-static`` from ``qemu-8.1.3-1.fc39``, I can no longer run on the m1 the ``x86_64`` binary created by https://github.com/containers/PodmanHello + +If I try with ``qemu-x86_64-static`` from ``qemu-7.2.7-1.fc38`` then this works. + +If I build the binary manually on a fc39 x86 system with ``gcc -O2 -static -o podman_hello_world podman_hello_world.c``, then I can also run it successfully with ``qemu-8.1.3-1.fc39``. +It's only the static binary built inside the alpine container which cannot be run on the M1. + + +Misc tests I ran: + +``` +$ ./qemu-x86_64-static-8.1.3 podman_hello_world.alpine +qemu-x86_64-static-8.1.3: /var/roothome/podman_hello_world.alpine: Unable to find a guest_base to satisfy all guest address mapping requirements + 0000000000000000-0000000000000fff + 0000000000400000-00000000004047ef + +$ ./qemu-x86_64-static-7.2.7 podman_hello_world.alpine +!... Hello Podman World ...! +[...] + +$ ./qemu-x86_64-static-8.1.3 podman_hello_world.fc39 +!... Hello Podman World ...! +[...] +``` + +The issue is still present with ``qemu-8.2.0-0.3.rc2.fc40`` + +I also could not reproduce on ``x86_64`` machines. I just tried it on fc39 installed on non-Apple ``aarch64`` hardware, and I'm seeing the same issue: + +``` +# rpm -qf /usr/bin/qemu-x86_64-static +qemu-user-static-x86-8.1.3-1.fc39.aarch64 + +# qemu-x86_64-static ./podman_hello_world.alpine +qemu-x86_64-static: /root/podman_hello_world.alpine: Unable to find a guest_base to satisfy all guest address mapping requirements + 0000000000000000-0000000000000fff + 0000000000400000-00000000004047ef +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2085 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2085 new file mode 100644 index 000000000..a24e5cdda --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2085 @@ -0,0 +1,22 @@ +screen doesn't update fully wth spice + virtio-vga graphics +Description of problem: +When using spice graphics with virtio-vga, display updates and missing and/or delayed making interaction unusable +Steps to reproduce: +Create a VM with spice graphics and virtio-vga with earlier mentioned command line + +Open ``remote-viewer spice://localhost:5900`` + +Boot the Fedora 39 server network installer CDROM ISO + +When Ananconda starts, select 'continue' at the first language choice screen + +Select 'Root Account' config option + +Toggle between "Disable root account" and "Enable root account" options + +Observe when the password entry box is shown/hidden, the screen does not redraw correctly +Additional information: +See also + +https://bugzilla.redhat.com/show_bug.cgi?id=2256884 +https://bbs.archlinux.org/viewtopic.php?id=291606 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2086 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2086 new file mode 100644 index 000000000..ca7f72291 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2086 @@ -0,0 +1,15 @@ +qemu-img created VMDK files lead to "Unsupported or invalid disk type 7" on ESXi +Description of problem: +Trying to start the VM using vmdk converted with qemu-img fails with + +Failed to start the virtual machine. +Module DevicePowerOn power on failed. +Unable to create virtual SCSI device for scsi0:1, '/vmfs/volumes/5cca0155-bdddf31d-2714-00215acbeb1e/AppD-VM01/AppDdisk1-VM01.vmdk' +Failed to open disk scsi0:1: Unsupported or invalid disk type 7. Ensure that the disk has been imported. +Steps to reproduce: +1. Convert booting OS (in both Qemu and VMWare with the help of drivers) to vmdk +2. Push vmdk file to ESXi datastore +3. Try to boot + +Additional information: +ESXi seem to use a specific implementation of vmdk, with a *name*.vmdk file being the descriptor of the virtual disk and a *name*-flat.vmdk. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2087 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2087 new file mode 100644 index 000000000..623a3318d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2087 @@ -0,0 +1,28 @@ +usb-host / libusb: handling of clear_halt leads to slow device attach, possibly unusable VMs (edit:fix within) +Description of problem: +When passing through a common JMicron USB SATA IDE brige storage device to a windows guest, the windows VM and the attached device become unusable. It appears to take several minutes to identify the connected device, and many minutes to pull up the device properties (though they are correct). The trace log seems to indicate a retry/reset retry loop is occuring. + +The device works fine passed through to a fedora guest VM. Device also work fine when used by the Windows host system. + +The primary difference may be the XHCI controller device behavior in the Windows and fedora guest VMs.\ +It appears there may possibly be 2 separate issues: + +1. Incompatible handling of this type of storage device in usb-host / libusb. +2. Windows XHCI not properly handling malformed or possibly mis-behaved devices. + +I also tried the nec-usb-xhci device instead of qemu-xhci, and also tried the ICH9 usb device; no difference in behavior in the Windows VM. (Though windows appears to use the same xhci device driver in all cases). + +A simple USB 3.x storage stick (at speed 5000) works fine passed through to the Windows guest VM, configured in the same way, with both cases using WinUSB to allow passthrough/attach to work. +Additional information: +lsusb output in the working Fedora VM case: + +only the debug descriptor fails to dump, running as root + +[lsusb.txt](/uploads/c1a702bc628ed9bc983dba3e703e8af4/lsusb.txt) + +\-trace enable=usb_host\_\* output (fragment of logfile) from the non-working Windows VM case: + +[usb_noprogress.txt](/uploads/f66b2ff7d4658f9569859ac122413d9f/usb_noprogress.txt) + +```plaintext +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2088 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2088 new file mode 100644 index 000000000..f1aa2d67e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2088 @@ -0,0 +1,21 @@ +Building qemu fails on Solaris 11.4 +Description of problem: +Building qemu-system-hppa on Solaris 11.4 (details above) fails because in qga/commands-posix.c + +(1) Solaris does not have net/ethernet.h +``` + #if defined(__NetBSD__) || defined(__OpenBSD__) + #include <net/if_arp.h> + #include <netinet/if_ether.h> + #else + #include <net/ethernet.h> + #endif +``` +Solaris *does* have net/if_arp.h and netinet/if_ether.h + +(2) Solaris does not define ETHER_ADDR_LEN, instead it defines ETHERADDRL +Steps to reproduce: +1. '../configure' '--disable-docs' '--disable-rdma' '--target-list=hppa-softmmu' +2. gmake +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/209 b/gitlab/issues_text/target_missing/host_missing/accel_missing/209 new file mode 100644 index 000000000..b86663a31 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/209 @@ -0,0 +1 @@ +the version number of qemu 6.0.0 is still 5.2.0 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2090 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2090 new file mode 100644 index 000000000..c2aafda1d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2090 @@ -0,0 +1,7 @@ +Long initialisation of VM before boot. +Description of problem: +When i start VM in "Virtual machine manager" I got black screen, which hang there approximately one minute. After this delay VM begin booted and all work properly. Some time ago VMs booted immediately without mentioned delay after starting of VM. I checked all relevant log files, changed 3 times kernel, rebuilded Qemu, but problem persist. I don't know when problem began. + + + +## diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2095 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2095 new file mode 100644 index 000000000..d2acc2cb7 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2095 @@ -0,0 +1 @@ +RFE: support AF_UNIX userspace backend for virtio-vsock matching firecracker diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2099 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2099 new file mode 100644 index 000000000..0ce01ce44 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2099 @@ -0,0 +1,11 @@ +Setting for initial GTK window size? +Description of problem: + +Steps to reproduce: +1. When starting QEMU on Windows, the GTK window size appears to be sized to approx 640x480, which is very hard to see on a 4k+ monitor. So interacting with the boot, reading BIOS messages, etc, isn't great. +2. It would be great to be able to specify the dimensions of the GTK window, say 2560x1600, and then just set "Zoom to Fit". +3. This way, the visible window area remains constant, and all stages of graphical interaction get scaled to a workable size. +4. The OS can be configured to say 2560x1600 once setup. +5. Perhaps I've overlook settings to accomplish this? + +Thank you. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/210 b/gitlab/issues_text/target_missing/host_missing/accel_missing/210 new file mode 100644 index 000000000..530b3251c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/210 @@ -0,0 +1 @@ +Function not implemented when using libaio diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2100 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2100 new file mode 100644 index 000000000..87698c7f6 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2100 @@ -0,0 +1,6 @@ +Add option to skip quit confirmation with Cocoa display +Additional information: +This change was originally requested in back in 2016, but got lost in the issue tracker migration: https://bugs.launchpad.net/qemu/+bug/1556372 + +Patch in question: +https://lists.gnu.org/archive/html/qemu-devel/2015-09/msg05031.html diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2102 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2102 new file mode 100644 index 000000000..f05765fef --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2102 @@ -0,0 +1,40 @@ +"qemu-img resize -f qcow2" produces broken disk images +Description of problem: +The documentation of `qemu-img` at +<https://www.qemu.org/docs/master/tools/qemu-img.html> +makes it sound like `qemu-img resize` supports various image formats +(raw, qcow2, etc.) in the same way. + +But it doesn't. While `qemu-img resize -f raw` works as expected, +`qemu-img resize -f qcow2` produces broken disk images. +Steps to reproduce: +``` +$ wget http://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-9/latest/evbarm-aarch64/binary/gzimg/arm64.img.gz +$ gunzip arm64.img +``` + +First resize, then convert: +``` +$ cp arm64.img arm64-rc.img +$ qemu-img resize -f raw arm64-rc.img 10G +$ qemu-img convert -f raw -O qcow2 arm64-rc.img arm64-rc.qcow2 +$ rm -f arm64-rc.img +``` + +First convert, then resize: +``` +$ qemu-img convert -f raw -O qcow2 arm64.img arm64-cr.qcow2 +$ qemu-img resize -f qcow2 arm64-cr.qcow2 10G +``` + +Attach to a VM in VirtualBox (as an additional SATA disk) and start that VM. + +arm64-rc.qcow2 => +`# fdisk /dev/sdb` => it has two partitions. + +arm64-cr.qcow2 => +`# fdisk /dev/sdb` => it has no partitions! +And the VM cannot be cleanly shut down. I had to manually kill the VirtualBoxVM +process. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2103 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2103 new file mode 100644 index 000000000..502fcea74 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2103 @@ -0,0 +1 @@ +docs/system/keys.rst.inc still refers to removed options -alt-grab and -ctrl-grab diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2104 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2104 new file mode 100644 index 000000000..8eca4fa87 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2104 @@ -0,0 +1 @@ +source code of function trace_memory_region_ops_write() diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2109 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2109 new file mode 100644 index 000000000..fa7f624c8 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2109 @@ -0,0 +1 @@ +NetBSD VM fails to install due to missing py311-expat package diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2110 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2110 new file mode 100644 index 000000000..8287251b1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2110 @@ -0,0 +1,11 @@ +live migrations fail qemu-kvm +Description of problem: +live migrations fail between two identical hosts +``` +2024-01-18T00:16:31.582070Z qemu-kvm: Missing section footer for 0000:00:01.3/piix4_pm +2024-01-18T00:16:31.582169Z qemu-kvm: load of migration failed: Invalid argument +2024-01-18 00:16:31.611+0000: shutting down, reason=failed +``` +Additional information: +source log for vm [source.log](/uploads/5816f929a5e543f423bb909a0df23fb7/source.log) +dest log for vm [dest.log](/uploads/a1b6ae02e4c8235536e740b86d16ddd6/dest.log) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2111 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2111 new file mode 100644 index 000000000..aecf44676 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2111 @@ -0,0 +1,59 @@ +Assertion failure with active vhost NIC when snapshot_save_job_bh() is executed as part of a vCPU thread's aio_poll() +Description of problem: +During a `snapshot-save` QMP command the `snapshot_save_job_bh()` bottom half can end up being executed as part of a vCPU thread's `aio_poll()`. This is problematic and can lead to an assertion failure (see below for backtrace) when there is an active vhost network device: + +``` +qemu-system-x86_64: ../hw/net/virtio-net.c:3835: virtio_net_pre_save: Assertion `!n->vhost_started' failed. +``` +Steps to reproduce: +It is very racy and very difficult to reproduce when actually taking snapshots. So the way I can get it pretty reliably is: + +1. Issue `snapshot-save` QMP commands with an invalid device ID in a loop. At the same time, have the guest write to the pflash. +2. In GDB, wait for `snapshot_save_job_bh()` to be hit by a vCPU thread. +3. Manually change the device ID to a valid one (`scsi1` in the example) so that taking a snapshot will actually be attempted. +4. Continue in GDB and the assertion failure will happen. +Additional information: +Full backtrace: + +``` + #0 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44 + #1 0x00007f1de5ae3d9f in __pthread_kill_internal (signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:78 + #2 0x00007f1de5a94f32 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 + #3 0x00007f1de5a7f472 in __GI_abort () at ./stdlib/abort.c:79 + #4 0x00007f1de5a7f395 in __assert_fail_base (fmt=0x7f1de5bf3a90 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x563cb92d56e7 "!n->vhost_started", + file=file@entry=0x563cb92d56d0 "../hw/net/virtio-net.c", line=line@entry=3835, function=function@entry=0x563cb92d65a0 <__PRETTY_FUNCTION__.2> "virtio_net_pre_save") at ./assert/assert.c:92 + #5 0x00007f1de5a8de32 in __GI___assert_fail (assertion=assertion@entry=0x563cb92d56e7 "!n->vhost_started", file=file@entry=0x563cb92d56d0 "../hw/net/virtio-net.c", line=line@entry=3835, + function=function@entry=0x563cb92d65a0 <__PRETTY_FUNCTION__.2> "virtio_net_pre_save") at ./assert/assert.c:101 + #6 0x0000563cb8ebf23c in virtio_net_pre_save (opaque=<optimized out>) at ../hw/net/virtio-net.c:3835 + #7 virtio_net_pre_save (opaque=<optimized out>) at ../hw/net/virtio-net.c:3829 + #8 0x0000563cb917515b in vmstate_save_state_v (f=0x7f1dc43aec30, vmsd=0x563cb9e5a580 <vmstate_virtio_net>, opaque=0x563cbbb6eb40, vmdesc=0x7f1dc4080040, version_id=11, errp=0x7f1dcbdf9908) + at ../migration/vmstate.c:359 + #9 0x0000563cb9175d0c in vmstate_save_state_with_err (f=<optimized out>, vmsd=<optimized out>, opaque=<optimized out>, vmdesc_id=<optimized out>, errp=<optimized out>) at ../migration/vmstate.c:347 + #10 0x0000563cb8d9a1b2 in vmstate_save (f=f@entry=0x7f1dc43aec30, se=se@entry=0x563cbbcbdc70, vmdesc=vmdesc@entry=0x7f1dc4080040) at ../migration/savevm.c:1037 + #11 0x0000563cb8d9d6e6 in qemu_savevm_state_complete_precopy_non_iterable (f=f@entry=0x7f1dc43aec30, in_postcopy=in_postcopy@entry=false, inactivate_disks=inactivate_disks@entry=false) + at ../migration/savevm.c:1553 + #12 0x0000563cb8d9daa2 in qemu_savevm_state_complete_precopy (f=f@entry=0x7f1dc43aec30, iterable_only=iterable_only@entry=false, inactivate_disks=inactivate_disks@entry=false) at ../migration/savevm.c:1628 + #13 0x0000563cb8da076e in qemu_savevm_state (errp=0x7f1dc42c59f0, f=0x7f1dc43aec30) at ../migration/savevm.c:1734 + #14 save_snapshot (name=<optimized out>, overwrite=overwrite@entry=false, vmstate=<optimized out>, has_devices=has_devices@entry=true, devices=0x7f1dc4096600, errp=0x7f1dc42c59f0) at ../migration/savevm.c:3131 + #15 0x0000563cb8da0926 in snapshot_save_job_bh (opaque=0x7f1dc42c5930) at ../migration/savevm.c:3430 + #16 0x0000563cb9110036 in aio_bh_poll (ctx=ctx@entry=0x563cba818b40) at ../util/async.c:216 + #17 0x0000563cb90fa09a in aio_poll (ctx=ctx@entry=0x563cba818b40, blocking=blocking@entry=true) at ../util/aio-posix.c:722 + #18 0x0000563cb8fb1015 in bdrv_poll_co (s=0x7f1dcbdf9db0) at /home/febner/repos/qemu/block/block-gen.h:43 + #19 blk_pwrite (blk=<optimized out>, offset=offset@entry=91136, bytes=bytes@entry=512, buf=0x7f1dc9a16400, flags=flags@entry=0) at block/block-gen.c:2012 + #20 0x0000563cb8bb8985 in pflash_update (pfl=pfl@entry=0x563cbaa84bf0, offset=91136, offset@entry=91526, size=size@entry=1) at ../hw/block/pflash_cfi01.c:394 + #21 0x0000563cb8bbacd8 in pflash_write (be=0, width=1, value=63, offset=91526, pfl=0x563cbaa84bf0) at ../hw/block/pflash_cfi01.c:522 + #22 pflash_mem_write_with_attrs (opaque=0x563cbaa84bf0, addr=91526, value=<optimized out>, len=1, attrs=...) at ../hw/block/pflash_cfi01.c:681 + #23 0x0000563cb8f06e2e in access_with_adjusted_size (addr=addr@entry=91526, value=value@entry=0x7f1dcbdf9f58, size=size@entry=1, access_size_min=<optimized out>, access_size_max=<optimized out>, + access_fn=0x563cb8f06710 <memory_region_write_with_attrs_accessor>, mr=<optimized out>, attrs=...) at ../system/memory.c:573 + #24 0x0000563cb8f07e59 in memory_region_dispatch_write (mr=mr@entry=0x563cbaa84fb0, addr=addr@entry=91526, data=<optimized out>, op=<optimized out>, attrs=attrs@entry=...) at ../system/memory.c:1528 + #25 0x0000563cb8f0f43c in flatview_write_continue (fv=fv@entry=0x7f1dc42e4720, addr=addr@entry=4290864518, attrs=..., attrs@entry=..., ptr=ptr@entry=0x7f1de7946028, len=len@entry=1, addr1=<optimized out>, + l=<optimized out>, mr=0x563cbaa84fb0) at ../system/physmem.c:2714 + #26 0x0000563cb8f0f6b3 in flatview_write (fv=0x7f1dc42e4720, addr=addr@entry=4290864518, attrs=attrs@entry=..., buf=buf@entry=0x7f1de7946028, len=len@entry=1) at ../system/physmem.c:2756 + #27 0x0000563cb8f12959 in address_space_write (len=1, buf=0x7f1de7946028, attrs=..., addr=4290864518, as=0x563cb9fd8ec0 <address_space_memory>) at ../system/physmem.c:2863 + #28 address_space_rw (as=0x563cb9fd8ec0 <address_space_memory>, addr=4290864518, attrs=attrs@entry=..., buf=buf@entry=0x7f1de7946028, len=1, is_write=<optimized out>) at ../system/physmem.c:2873 + #29 0x0000563cb8f64ab8 in kvm_cpu_exec (cpu=cpu@entry=0x563cbac066d0) at ../accel/kvm/kvm-all.c:2915 + #30 0x0000563cb8f65ce5 in kvm_vcpu_thread_fn (arg=arg@entry=0x563cbac066d0) at ../accel/kvm/kvm-accel-ops.c:51 + #31 0x0000563cb90fd1c8 in qemu_thread_start (args=0x563cbaac33c0) at ../util/qemu-thread-posix.c:541 + #32 0x00007f1de5ae2044 in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:442 + #33 0x00007f1de5b6261c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2112 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2112 new file mode 100644 index 000000000..a3bfe5698 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2112 @@ -0,0 +1,26 @@ +Limited Support for MIPS clone syscall in QEMU User Mode +Description of problem: +Hello, + +I have been working with QEMU user mode to run programs based on the MIPS architecture and have encountered a limitation regarding the support for the MIPS clone syscall in the current implementation of QEMU user mode. Specifically, when invoking the clone syscall with certain flags, it results in the error "errno=22 (Invalid argument)" due to the absence of corresponding handling code in QEMU. + +Upon further investigation, I pinpointed the probable cause. QEMU user mode appears to check if the flags for the clone syscall include all the flags defined in CLONE_THREAD_FLAGS. If there is a mismatch, it returns "-TARGET_EINVAL". + +[source code](https://gitlab.com/qemu-project/qemu/-/blob/master/linux-user/syscall.c?ref_type=heads#L6564) + +The current CLONE_THREAD_FLAGS in QEMU are set to include: (CLONE_VM | CLONE_FS | CLONE_FILES | CLONE_SIGHAND | CLONE_THREAD | CLONE_SYSVSEM). + +However, in my MIPS program, the flags are only: (CLONE_VM | CLONE_FS | CLONE_FILES | CLONE_SIGHAND). + +Aligning my MIPS program to include all the flags as per CLONE_THREAD_FLAGS alters the clone syscall's behavior, deviating from the original semantics required by my MIPS program. + +I am seeking guidance on whether there is a way in QEMU user mode's MIPS syscall handling to exclusively use the flags (CLONE_VM | CLONE_FS | CLONE_FILES | CLONE_SIGHAND). Alternatively, I am interested in any possible approach to enable support for the MIPS architecture's clone syscall in QEMU user mode. + +Thank you for your time and assistance. +Steps to reproduce: +1. Write a C program that utilizes the clone function, specifying the flags as: CLONE_VM | CLONE_FS | CLONE_FILES | CLONE_SIGHAND. + +strace output: +``` +clone(CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND,child_stack=0x009359a8,parent_tidptr=0x00000f00,tls=0x00000003,child_tidptr=0x2b36d510) = -1 errno=22 (Invalid argument) +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2113 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2113 new file mode 100644 index 000000000..1850391e8 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2113 @@ -0,0 +1 @@ +x64-freebsd-13-build CI job fails with "/usr/local/lib/libtasn1.so: undefined reference to strverscmp@FBSD_1.7" diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2116 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2116 new file mode 100644 index 000000000..a47655df2 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2116 @@ -0,0 +1,28 @@ +[CRASH] OpenGL acceleration except gtk: bad interaction between NVIDIA usermode opengl libraries and QEMU seccomp -sandbox on,spawn=deny, crashes immediately on startup with Bad system call +Description of problem: +When running any of the above command lines, QEMU crashes with Bad system call (core dumped). Not exclusive to spice; it seems this is caused by QEMU forking during OpenGL initialization after seccomp takes effect. +Steps to reproduce: +1. Run the above commandline +2. Notice a Bad system call (core dumped) +Additional information: +This crash only happens if spawn=deny is set, resourcecontrol/obsolete/elevateprivileges don't cause crashes. + +The crash happens around the same time as an audit event is generated in dmesg: `audit: type=1326 audit(1705775880.776:14): auid=MYUSERID uid=MYUID gid=MYGID ses=REDACTED pid=REDACTED comm="qemu-system-x86" exe="/usr/bin/qemu-system-x86_64" sig=31 arch=c000003e syscall=56 compat=0 ip=REDACTED code=REDACTED` + +`ausyscall c000003e 56` tells me it's `clone` which (iirc) is the syscall used by glibc to implement fork() (I might be wrong about glibc part) + +Suggested solution: move seccomp activation until just before guest code starts executing? make frontends (ie -display gtk/sdl/whatever, including -spice) initialize before seccomp? + +Workaround: `chmod -x /bin/nvidia-modprobe` if not using the NVIDIA gpu or use this wrapper script (untested, not enterprise-ready, I am not responsible if unexpected things happen): +- rename /bin/qemu-system-x86_64 to qemu-system-x86_64.real +- put this in /bin/qemu-system-x86_64 and chmod +x it +```sh +#!/usr/bin/env sh +chmod -x /bin/nvidia-modprobe +qemu-system-x86_64.real $@ & disown +sleep 10 # excessive but maybe safer? +chmod +x /bin/nvidia-modprobe +``` +Also, you can use -display gtk,gl=on instead, or (unknown security implications) remove spawn=deny from -sandbox args + +original bug report was https://gitlab.com/libvirt/libvirt/-/issues/585 but I realized this was more of a qemu issue than a libvirt one diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2117 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2117 new file mode 100644 index 000000000..17e7980cf --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2117 @@ -0,0 +1,27 @@ +Unraid, Ubuntu, 9P/virtio and memory issues +Description of problem: +I am running an Ubuntu VM on Unraid - which is using Qemu. I am exposing my shares through "9p Mode" to the VM. + +The logs shows: +-fsdev local,security_model=passthrough,id=fsdev-fs0,path=/mnt/user/backup \ +-device '{"driver":"virtio-9p-pci","id":"fs0","fsdev":"fsdev-fs0","mount_tag":"backup","bus":"pci.1","addr":"0x0"}' \ + +Inside Ubuntu, I mount the exposed shares like this: + +sudo mount -t 9p -o trans=virtio "backup" /media/share/backup + +I have a script that uses rsync to sync the files from these mounted shares onto an internal disk drive. + +The issues that I am facing, is that rsync sometimes reports "cannot allocate memory": + +rsync: [sender] readdir("/media/share/backup/myfolder"): Cannot allocate memory (12) + +There are "ten thousands" of files in that folder hierarchy, but there are plenty of memory available on the VM (many GBs), so that is no issue. The next time I run the job, it might go through as normal. But I would like to get rid of these issues. + +The question is: Is there some kind of memory allocation/limit to the virtio/9p as well? If yes - is there some way to increase it to avoid these errors? +Steps to reproduce: +1. Mount as shown +2. Run rsync on folder with lots of files +3. See error +Additional information: +N/A diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2118 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2118 new file mode 100644 index 000000000..883b5a74c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2118 @@ -0,0 +1 @@ +make vm-build-openbsd reinstalls OpenBSD every time diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2119 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2119 new file mode 100644 index 000000000..77f4a54a9 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2119 @@ -0,0 +1 @@ +target/riscv/gdbstub.c：The V registers in gdb debugging mode can only be accessed when the single-letter V is enabled diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2121 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2121 new file mode 100644 index 000000000..80e7bd30a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2121 @@ -0,0 +1 @@ +tests/qtest/ahci-test.c:89:verify_state: assertion failed (ahci_fingerprint == ahci->fingerprint): (0xe0000000 == 0x29228086) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2122 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2122 new file mode 100644 index 000000000..defbe24ea --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2122 @@ -0,0 +1,7 @@ +qemu-user-static segfault running ldconfig on host x86_64 with client arm64 +Description of problem: +qemu segfault +Steps to reproduce: +1. download ubuntu jammy arm64 rootfs (I assume any will do) +2. mount it (with /proc from host so apt is happy) +3. execute an apt uninstall that triggers libc-bin processing diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2123 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2123 new file mode 100644 index 000000000..cfe839330 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2123 @@ -0,0 +1,31 @@ +Invalid subprocess commands spawns successfully when running under QEMU +Description of problem: +When executing a subprocess from with a non-existing command EQMU still spawns a process. + +Consider this small rust program for instance: +```rust +use std::process::Command; + +fn main() { + match Command::new("thisdoesnotexist").spawn() { + Ok(child) => { + println!("Child process id is {}", child.id()); + } + Err(_) => { + println!("This should happen"); + } + } +} +``` + +**Executing with `qemu-aarch64`:** +```shell +qemu-aarch64 ./rust-app +Child process id is 20182 +``` + +**Executing regularly:** +```shell +./rust-app +This should happen +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2124 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2124 new file mode 100644 index 000000000..5bf125363 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2124 @@ -0,0 +1 @@ +Use watchdog_perform_action() for watchdogs currently using qemu_system_reset_request() diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2125 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2125 new file mode 100644 index 000000000..c71352c03 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2125 @@ -0,0 +1,14 @@ +The value of 'tx_queue_size' is set to only 256 in the network device option on qemu 8.2. +Description of problem: +I have been using the 'tx_queue_size' value set to 1024 in the network device option on qemu 7.2 without any issues.\ +but when I upgrade to qemu 8.2 I got this error message (and also qemu 8.1) and I cannot use any value other than 256 +``` +qemu-system-x86_64: -device virtio-net-pci,mq=on,vectors=6,netdev=hostnet_34,id=dpdk_34,mac=F2:20:AF:40:12:65,bus=bridge,addr=0x7,page-per-vq=on,rx_queue_size=1024,tx_queue_size=1024,mrg_rxbuf=on,disable-legacy=on,disable-modern=off,host_mtu=1500,csum=on,guest_csum=on,host_tso4=on,host_tso6=on: Invalid tx_queue_size (= 1024), must be a power of 2 between 256 and 256 +``` + +and I think virtqueue max size value has never changed from 1024.\ +https://gitlab.com/qemu-project/qemu/-/blob/staging-8.2/include/hw/virtio/virtio.h?ref_type=heads#L62 +Steps to reproduce: +1. boot qemu-system-x86_64 on qemu 8.2 and network device option set tx_queue_size value over 256 +Additional information: +- I'm using hardware vDPA offloading with mellanox NIC card. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2126 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2126 new file mode 100644 index 000000000..1a3f37819 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2126 @@ -0,0 +1 @@ +iotest-144 sometimes fails due to minor reordering of output diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2127 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2127 new file mode 100644 index 000000000..e09c1e5dc --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2127 @@ -0,0 +1 @@ +test-aio-multithread.c:371:test_multi_fair_mutex: assertion failed (counter == atomic_counter): (316636 == 316637) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2128 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2128 new file mode 100644 index 000000000..1fa647a6d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2128 @@ -0,0 +1 @@ +avocado tests using landley.net URLs sometimes time out fetching assets diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2129 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2129 new file mode 100644 index 000000000..973286d7f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2129 @@ -0,0 +1 @@ +migration-test sometimes fails diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/213 b/gitlab/issues_text/target_missing/host_missing/accel_missing/213 new file mode 100644 index 000000000..03561239a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/213 @@ -0,0 +1 @@ +memory writes via gdb don't work for memory mapped hardware diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2130 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2130 new file mode 100644 index 000000000..30264d3ee --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2130 @@ -0,0 +1 @@ +latest code missing "singlestep" diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2131 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2131 new file mode 100644 index 000000000..d9f26a844 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2131 @@ -0,0 +1 @@ +tcg mem plugin, udata always zero diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2132 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2132 new file mode 100644 index 000000000..1ef3f9723 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2132 @@ -0,0 +1,11 @@ +USB Hub as USB Host Device: Child devices not recognized in Win11 +Description of problem: +I wanted to give the Windows environment direct access to some of the physical USB ports on my pc. So I mapped a selection of ports to Windows via the associated hub. Windows correctly recognizes the hub. Also, when devices are plugged into or removed from the associated ports, Windows recognizes the connection of a new device or its removal. However, regardless of the device, Windows reports: +"USB device not recognized. +The last USB device you connected to this computer has malfunctioned, and Windows does not recognize it." +Steps to reproduce: +1. Add one of the hosts USB hubs to a Windows VM as a USB Host Device. +2. Verify that Windows recognizes the host hub in device manager. +3. Try plugging in a USB device into one of the corresponding physical ports. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2134 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2134 new file mode 100644 index 000000000..176158896 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2134 @@ -0,0 +1 @@ +[Tricore Board]How to map LOCAL. DSPR/LOCAL.PSPR to other CPU globle_DSPR/globle_PSPR diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2135 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2135 new file mode 100644 index 000000000..29a66bb7e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2135 @@ -0,0 +1,24 @@ +Looking for ways to bypass MPS3-AN547 bootram size limit +Description of problem: +Could not boot MPS3-AN547 machine with images larger than 512KiB. + +I've tried to move part of the symbols to other memory area, but the memories were discontinuous and this resulted in a large image which covers the reserved area in-between and wouldn't boot. I'm looking for advice on how to put more code in bootram. + +I've also noticed the 8MB QSPI rom area, but AN547 does not have the remapping capability as AN524 and cannot use that as bootram. What is the best way to solve this? +Steps to reproduce: +1.Generate an image which goes beyond 0x00000000~(0+512K) + +2.```qemu-system-arm -M mps3-an547 -nographic -kernel big-image.bin``` + +3."```qemu-system-arm: Could not load kernel 'nuttx/nuttx.bin'```" +Additional information: +Current working linker script: +``` +MEMORY +{ + flash (rx) : ORIGIN = 0x00000000, LENGTH = 512K + sram1 (rwx) : ORIGIN = 0x01000000, LENGTH = 2M + sram2 (rwx) : ORIGIN = 0x21000000, LENGTH = 4M +} +``` +Problem X is that the flash will overflow. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2138 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2138 new file mode 100644 index 000000000..58480f34d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2138 @@ -0,0 +1,22 @@ +Build failure on macOS when using --disable-cocoa +Description of problem: +Build fails: + +``` +../qemu-8.2.1/meson.build:3741:13: ERROR: No host machine compiler for 'audio/coreaudio.m' +``` +Steps to reproduce: +1. On macOS run `./configure --disable-cocoa` + +Result: + +``` +Compiler for language objc skipped: feature cocoa disabled +``` +``` +../meson.build:3741:13: ERROR: No host machine compiler for 'audio/coreaudio.m' +``` +Additional information: +It seems your build script contains the assumption that an Objective-C compiler is not needed when the Cocoa UI is disabled, but it still appears to be needed to compile the CoreAudio code regardless of UI. + +This was originally reported to MacPorts here: https://trac.macports.org/ticket/67984 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2139 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2139 new file mode 100644 index 000000000..5390181c4 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2139 @@ -0,0 +1,9 @@ +Super/Win key seems to release immediately on sdl+windows +Description of problem: +Currently on windows when trying SerenityOS the super key releases immediately so you can't use the shortcuts, with the GTK gui (gl off) it works though. but GTK has other problems with mouse which sometimes doesn't work at all, SDL seems to work well besides from this one issue. +Steps to reproduce: +1. Boot with default settings on wsl2 which launches qemu on windows if it's installed +2. Try to use any of the superkey shortcuts like superkey+space for a search popup https://github.com/SerenityOS/serenity/blob/dc47d01fdc62a1ee319310e2b11c26b8ebe8899d/Base/usr/share/man/man7/KeyboardShortcuts.md#L4 +3. Fail because it immediately opens the menu blocking the shortcuts. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/214 b/gitlab/issues_text/target_missing/host_missing/accel_missing/214 new file mode 100644 index 000000000..ada6d81e3 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/214 @@ -0,0 +1 @@ +QEMU manpages provoke man(1) "can't break line" warnings diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2140 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2140 new file mode 100644 index 000000000..1b6421b27 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2140 @@ -0,0 +1 @@ +Compiling object tests/fp - Can't create tests/fp Is directory Centos 7 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2142 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2142 new file mode 100644 index 000000000..a301e9432 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2142 @@ -0,0 +1 @@ +`-machine microvm -cpu host` crashes when guest attempts to check CPUID SGX bits diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2144 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2144 new file mode 100644 index 000000000..d72c3a7fb --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2144 @@ -0,0 +1,22 @@ +macOS build fails when using --enable-debug +Description of problem: +the build fails because a symbol can't be found: + +``` +ld: Undefined symbols: + _lasi_82596_init, referenced from: + _machine_HP_common_init_tail in hw_hppa_machine.c.o +``` +Steps to reproduce: +1. on macOS 14.3 in build folder +2. ../configure --enable-debug +3. make -j12 +Additional information: +the default build with + +``` +../configure +make -j12 +``` + +succeeds normally. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2147 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2147 new file mode 100644 index 000000000..36c3edd00 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2147 @@ -0,0 +1,9 @@ +The Windows version of QEMU runs the semihost project without printing +Description of problem: +In Linux, running this command to execute the Semihost project will print `Hello World` in the console, but running in Windows will not print anything. + +I'd like to know if it's the windows version of qemu that doesn't have perfect support for semihost, or if I need to adjust the input parameters. +Steps to reproduce: + +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2148 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2148 new file mode 100644 index 000000000..0c4568070 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2148 @@ -0,0 +1,9 @@ +vdso.so is required to build vdso.so since 8.2.0 +Description of problem: +Removing binaries from the "source" distribution makes it unable to compile. It used to work in 8.1.4. +Steps to reproduce: +1. remove **/vdso.so +2. configure, build +3. `../linux-user/i386/meson.build:7:20: ERROR: File vdso.so does not exist.` +Additional information: +Build log in my Gentoo harness: [build.log](/uploads/da1933173b39dd6e5f9f90de09adc3a1/build.log) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2149 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2149 new file mode 100644 index 000000000..7a1dc95a9 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2149 @@ -0,0 +1,11 @@ +Segfault in libvhost-user and libvduse because of invalid pointer arithmetic with indirect read +Description of problem: +Hello, this is my first experience communicating with open-source community. I have already reported the problem and have submitted patches through qemu-devel mailing list https://mail.gnu.org/archive/html/qemu-devel/2024-01/msg02533.html, as instructed in https://www.qemu.org/docs/master/devel/submitting-a-patch.html, albeit getting no response from any maintainer. I know, that everyone are very busy and are spammed everyday from millions of threads, but I am getting very upset, that such a trivial bug lives in code base for many years and even have been copied to "sister"-library without proper review. So, excuse me, if I am taking this issue too personally. + +The problem - when one tries to use libvhost-user\libvduse and triggers for some reason non-zero-copy mode (like pushing a lot of data) of indirect descriptor reading routine `virtqueue_read_indirect_desc`, any time one got to read more than one descriptor - one would overwrite stack and depending on one's luck getting some weird behaviour, or simple crash moments later, when other code tries to access broken data. + +Steps to reproduce are non-trivial, because depends on one's host and VM (one simply gets random crashes here and there, with core dumps pointing somewhere around given libraries), but anyone who can read C code, can clearly see that pointer arithmetic of `struct vring_desc *desc` is wrong. + +Maybe, I got instructions wrong and posted fixes to wrong mailing list, maybe, nobody cares, so thank you for attention. I'll be glad to hear any advice on how can I help with fixing this simple error, besides what has been done already. + +Thank you. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2151 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2151 new file mode 100644 index 000000000..feee5a9d0 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2151 @@ -0,0 +1,195 @@ +Nested vIOMMU PCI Passthrough kernel panics +Description of problem: +In an effort to test vIOMMU according to <https://wiki.qemu.org/Features/VT-d> I've run into a kernel panic on an L2 guest receiving the L1 hypervisor's PCI passed virtual macvtap hostdev. Upon an `ifup` inside the L2 guest, on the network device passed through from the L1 host, the following kernel panic occurs and the L2 guest reboots: + +``` +[ OK ] Started ifup@enp0s2.service - ifup for enp0s2. +[ OK ] Started ifup@enp0s3.service - ifup for enp0s3.[ 24.019839] audit: type=1400 audit(1707113302.472:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=457 comm="apparmor_parser" + + Starting networking.service - Raise network interfaces... +[ 24.255671] audit: type=1400 audit(1707113302.472:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=457 comm="apparmor_parser" +[ OK ] Finished systemd-tmpfiles-…te Volatile Files and Directories. +[ 24.361355] audit: type=1400 audit(1707113302.472:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=457 comm="apparmor_parser" + Starting systemd-timesyncd… - Network Time Synchronization... + Starting systemd-update-ut…rd System Boot/Shutdown in UTMP... +[ OK ] Finished systemd-update-ut…cord System Boot/Shutdown in UTMP. +[ OK ] Finished networking.service - Raise network interfaces. +[ OK ] Reached target network.target - Network. +[ OK ] Started systemd-timesyncd.…0m - Network Time Synchronization. +[ OK ] Reached target sysinit.target - System Initialization. +[ OK ] Started etckeeper.timermit of changes in /etc directory. +[ OK ] Started systemd-tmpfiles-c… Cleanup of Temporary Directories. +[ OK ] Reached target time-set.target - System Time Set. +[ OK ] Started apt-daily.timer - Daily apt download activities.[ 46.187450] rcu: INFO: rcu_preempt self-detected stall on CPU +[ 46.187522] rcu: 0-...!: (5250 ticks this GP) idle=3774/1/0x4000000000000000 softirq=12350/12350 fqs=0 +[ 46.187522] (t=5250 jiffies g=8669 q=7 ncpus=1) +[ 46.187522] rcu: rcu_preempt kthread timer wakeup didn't happen for 5249 jiffies! g8669 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 +[ 46.187522] rcu: Possible timer handling issue on cpu=0 timer-softirq=2282 +[ 46.187522] rcu: rcu_preempt kthread starved for 5250 jiffies! g8669 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=0 +[ 46.187522] rcu: Unless rcu_preempt kthread gets sufficient CPU time, OOM is now expected behavior. +[ 46.187522] rcu: RCU grace-period kthread stack dump: +[ 46.187522] task:rcu_preempt state:I stack:0 pid:15 ppid:2 flags:0x00004000 +[ 46.187522] Call Trace: +[ 46.187522] <TASK> +[ 46.187522] __schedule+0x34d/0x9e0 +[ 46.187522] ? rcu_gp_cleanup+0x460/0x460 +[ 46.187522] schedule+0x5a/0xd0 +[ 46.187522] schedule_timeout+0x94/0x150 +[ 46.187522] ? __bpf_trace_tick_stop+0x10/0x10 +[ 46.187522] rcu_gp_fqs_loop+0x141/0x550 +[ 46.187522] rcu_gp_kthread+0xd0/0x190 +[ 46.187522] kthread+0xda/0x100 +[ 46.187522] ? kthread_complete_and_exit+0x20/0x20 +[ 46.187522] ret_from_fork+0x22/0x30 +[ 46.187522] </TASK> +[ 46.187522] rcu: Stack dump where RCU GP kthread last ran: +[ 46.187522] CPU: 0 PID: 487 Comm: ip Not tainted 6.1.0-17-amd64 #1 Debian 6.1.69-1 +[ 46.187522] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS Arch Linux 1.16.3-1-1 04/01/2014 +[ 46.187522] RIP: 0010:virtqueue_get_buf_ctx_split+0x94/0xd0 [virtio_ring] +[ 46.187522] Code: 42 fe ff ff 0f b7 43 58 83 c0 01 66 89 43 58 f6 83 80 00 00 00 01 75 12 80 7b 4a 00 48 8b 4b 70 8b 53 60 74 0f 66 87 44 51 04 <48> 89 e8 5b 5d c3 cc cc cc cc 66 89 44 51 04 0f ae f0 48 89 e8 5b +[ 46.187522] RSP: 0018:ffff960c408135c8 EFLAGS: 00000246 +[ 46.187522] RAX: 0000000000000000 RBX: ffff88e04e976100 RCX: 0000000000000001 +[ 46.187522] RDX: 0000000000000000 RSI: ffff960c408135e4 RDI: ffff88e04e976100 +[ 46.187522] RBP: 0000000000000000 R08: 0000000000000004 R09: ffff88e0034fa980 +[ 46.187522] R10: 0000000000000003 R11: ffff960c40813628 R12: 0000000000000002 +[ 46.187522] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000001 +[ 46.187522] FS: 00007f11d16da2c0(0000) GS:ffff88e07dc00000(0000) knlGS:0000000000000000 +[ 46.187522] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 +[ 46.187522] CR2: 00007f11d17ff8d0 CR3: 0000000004ac6000 CR4: 00000000000006f0 +[ 46.187522] Call Trace: +[ 46.187522] <IRQ> +[ 46.187522] ? rcu_check_gp_kthread_starvation+0xec/0xfd +[ 46.187522] ? rcu_sched_clock_irq.cold+0xe3/0x459 +[ 46.187522] ? update_load_avg+0x7e/0x780 +[ 46.187522] ? sched_slice+0x87/0x140 +[ 46.187522] ? timekeeping_update+0xdd/0x130 +[ 46.187522] ? timekeeping_advance+0x377/0x570 +[ 46.187522] ? update_process_times+0x70/0xb0 +[ 46.187522] ? tick_sched_handle+0x22/0x60 +[ 46.187522] ? tick_sched_timer+0x63/0x80 +[ 46.187522] ? tick_sched_do_timer+0xa0/0xa0 +[ 46.187522] ? __hrtimer_run_queues+0x112/0x2b0 +[ 46.187522] ? hrtimer_interrupt+0xf4/0x210 +[ 46.187522] ? __sysvec_apic_timer_interrupt+0x5d/0x110 +[ 46.187522] ? sysvec_apic_timer_interrupt+0x69/0x90 +[ 46.187522] </IRQ> +[ 46.187522] <TASK> +[ 46.187522] ? asm_sysvec_apic_timer_interrupt+0x16/0x20 +[ 46.187522] ? virtqueue_get_buf_ctx_split+0x94/0xd0 [virtio_ring] +[ 46.187522] virtnet_send_command+0x18e/0x1e0 [virtio_net] +[ 46.187522] virtnet_set_rx_mode+0xd4/0x2d0 [virtio_net] +[ 46.187522] __dev_open+0x12b/0x1a0 +[ 46.187522] __dev_change_flags+0x1d2/0x240 +[ 46.187522] dev_change_flags+0x22/0x60 +[ 46.187522] do_setlink+0x37c/0x12b0 +[ 46.187522] ? __nla_validate_parse+0x61/0xc00 +[ 46.187522] __rtnl_newlink+0x623/0x9e0 +[ 46.187522] ? __kmem_cache_alloc_node+0x191/0x2a0 +[ 46.187522] rtnl_newlink+0x43/0x70 +[ 46.187522] rtnetlink_rcv_msg+0x14e/0x3b0 +[ 46.187522] ? __kmem_cache_alloc_node+0x191/0x2a0 +[ 46.187522] ? __alloc_skb+0x88/0x1a0 +[ 46.187522] ? rtnl_calcit.isra.0+0x140/0x140 +[ 46.187522] netlink_rcv_skb+0x51/0x100 +[ 46.187522] netlink_unicast+0x24a/0x390 +[ 46.187522] netlink_sendmsg+0x250/0x4c0 +[ 46.187522] __sock_sendmsg+0x5f/0x70 +[ 46.187522] ____sys_sendmsg+0x277/0x2f0 +[ 46.187522] ? copy_msghdr_from_user+0x7d/0xc0 +[ 46.187522] ___sys_sendmsg+0x9a/0xe0 +[ 46.187522] __sys_sendmsg+0x76/0xc0 +[ 46.187522] do_syscall_64+0x5b/0xc0 +[ 46.187522] ? exit_to_user_mode_prepare+0x40/0x1e0 +[ 46.187522] ? syscall_exit_to_user_mode+0x27/0x40 +[ 46.187522] ? do_syscall_64+0x67/0xc0 +[ 46.187522] ? do_user_addr_fault+0x1b0/0x580 +[ 46.187522] ? exit_to_user_mode_prepare+0x40/0x1e0 +[ 46.187522] entry_SYSCALL_64_after_hwframe+0x64/0xce +[ 46.187522] RIP: 0033:0x7f11d1811af0 +[ 46.187522] Code: 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb b7 66 2e 0f 1f 84 00 00 00 00 00 90 80 3d f1 fa 0c 00 00 74 17 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 58 c3 0f 1f 80 00 00 00 00 48 83 ec 28 89 54 +[ 46.187522] RSP: 002b:00007ffe21b533a8 EFLAGS: 00000202 ORIG_RAX: 000000000000002e +[ 46.187522] RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007f11d1811af0 +[ 46.187522] RDX: 0000000000000000 RSI: 00007ffe21b53410 RDI: 0000000000000003 +[ 46.187522] RBP: 0000000000000003 R08: 0000000065c07b57 R09: 00005580e154e2a0 +[ 46.187522] R10: 00007ffe21b52e34 R11: 0000000000000202 R12: 0000000065c07b58 +[ 46.187522] R13: 00005580e016e020 R14: 0000000000000001 R15: 0000000000000000 +[ 46.187522] </TASK> +[ 46.187522] CPU: 0 PID: 487 Comm: ip Not tainted 6.1.0-17-amd64 #1 Debian 6.1.69-1 +[ 46.187522] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS Arch Linux 1.16.3-1-1 04/01/2014 +[ 46.187522] RIP: 0010:virtqueue_get_buf_ctx_split+0x94/0xd0 [virtio_ring] +[ 46.187522] Code: 42 fe ff ff 0f b7 43 58 83 c0 01 66 89 43 58 f6 83 80 00 00 00 01 75 12 80 7b 4a 00 48 8b 4b 70 8b 53 60 74 0f 66 87 44 51 04 <48> 89 e8 5b 5d c3 cc cc cc cc 66 89 44 51 04 0f ae f0 48 89 e8 5b +[ 46.187522] RSP: 0018:ffff960c408135c8 EFLAGS: 00000246 +[ 46.187522] RAX: 0000000000000000 RBX: ffff88e04e976100 RCX: 0000000000000001 +[ 46.187522] RDX: 0000000000000000 RSI: ffff960c408135e4 RDI: ffff88e04e976100 +[ 46.187522] RBP: 0000000000000000 R08: 0000000000000004 R09: ffff88e0034fa980 +[ 46.187522] R10: 0000000000000003 R11: ffff960c40813628 R12: 0000000000000002 +[ 46.187522] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000001 +[ 46.187522] FS: 00007f11d16da2c0(0000) GS:ffff88e07dc00000(0000) knlGS:0000000000000000 +[ 46.187522] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 +[ 46.187522] CR2: 00007f11d17ff8d0 CR3: 0000000004ac6000 CR4: 00000000000006f0 +[ 46.187522] Call Trace: +[ 46.187522] <IRQ> +[ 46.187522] ? rcu_dump_cpu_stacks+0xa4/0xe0 +[ 46.187522] ? rcu_sched_clock_irq.cold+0xe8/0x459 +[ 46.187522] ? update_load_avg+0x7e/0x780 +[ 46.187522] ? sched_slice+0x87/0x140 +[ 46.187522] ? timekeeping_update+0xdd/0x130 +[ 46.187522] ? timekeeping_advance+0x377/0x570 +[ 46.187522] ? update_process_times+0x70/0xb0 +[ 46.187522] ? tick_sched_handle+0x22/0x60 +[ 46.187522] ? tick_sched_timer+0x63/0x80 +[ 46.187522] ? tick_sched_do_timer+0xa0/0xa0 +[ 46.187522] ? __hrtimer_run_queues+0x112/0x2b0 +[ 46.187522] ? hrtimer_interrupt+0xf4/0x210 +[ 46.187522] ? __sysvec_apic_timer_interrupt+0x5d/0x110 +[ 46.187522] ? sysvec_apic_timer_interrupt+0x69/0x90 +[ 46.187522] </IRQ> +[ 46.187522] <TASK> +[ 46.187522] ? asm_sysvec_apic_timer_interrupt+0x16/0x20 +[ 46.187522] ? virtqueue_get_buf_ctx_split+0x94/0xd0 [virtio_ring] +[ 46.187522] virtnet_send_command+0x18e/0x1e0 [virtio_net] +[ 46.187522] virtnet_set_rx_mode+0xd4/0x2d0 [virtio_net] +[ 46.187522] __dev_open+0x12b/0x1a0 +[ 46.187522] __dev_change_flags+0x1d2/0x240 +[ 46.187522] dev_change_flags+0x22/0x60 +[ 46.187522] do_setlink+0x37c/0x12b0 +[ 46.187522] ? __nla_validate_parse+0x61/0xc00 +[ 46.187522] __rtnl_newlink+0x623/0x9e0 +[ 46.187522] ? __kmem_cache_alloc_node+0x191/0x2a0 +[ 46.187522] rtnl_newlink+0x43/0x70 +[ 46.187522] rtnetlink_rcv_msg+0x14e/0x3b0 +[ 46.187522] ? __kmem_cache_alloc_node+0x191/0x2a0 +[ 46.187522] ? __alloc_skb+0x88/0x1a0 +[ 46.187522] ? rtnl_calcit.isra.0+0x140/0x140 +[ 46.187522] netlink_rcv_skb+0x51/0x100 +[ 46.187522] netlink_unicast+0x24a/0x390 +[ 46.187522] netlink_sendmsg+0x250/0x4c0 +[ 46.187522] __sock_sendmsg+0x5f/0x70 +[ 46.187522] ____sys_sendmsg+0x277/0x2f0 +[ 46.187522] ? copy_msghdr_from_user+0x7d/0xc0 +[ 46.187522] ___sys_sendmsg+0x9a/0xe0 +[ 46.187522] __sys_sendmsg+0x76/0xc0 +[ 46.187522] do_syscall_64+0x5b/0xc0 +[ 46.187522] ? exit_to_user_mode_prepare+0x40/0x1e0 +[ 46.187522] ? syscall_exit_to_user_mode+0x27/0x40 +[ 46.187522] ? do_syscall_64+0x67/0xc0 +[ 46.187522] ? do_user_addr_fault+0x1b0/0x580 +[ 46.187522] ? exit_to_user_mode_prepare+0x40/0x1e0 +[ 46.187522] entry_SYSCALL_64_after_hwframe+0x64/0xce +[ 46.187522] RIP: 0033:0x7f11d1811af0 +[ 46.187522] Code: 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb b7 66 2e 0f 1f 84 00 00 00 00 00 90 80 3d f1 fa 0c 00 00 74 17 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 58 c3 0f 1f 80 00 00 00 00 48 83 ec 28 89 54 +[ 46.187522] RSP: 002b:00007ffe21b533a8 EFLAGS: 00000202 ORIG_RAX: 000000000000002e +[ 46.187522] RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007f11d1811af0 +[ 46.187522] RDX: 0000000000000000 RSI: 00007ffe21b53410 RDI: 0000000000000003 +[ 46.187522] RBP: 0000000000000003 R08: 0000000065c07b57 R09: 00005580e154e2a0 +[ 46.187522] R10: 00007ffe21b52e34 R11: 0000000000000202 R12: 0000000065c07b58 +[ 46.187522] R13: 00005580e016e020 R14: 0000000000000001 R15: 0000000000000000 +[ 46.187522] </TASK> +``` +Steps to reproduce: +1. Create the following nested passthrough configuration +2. Attempt to configure the L1 network hostdev interface inside the L2 guest + +Any attempt will cause the kernel panics documented. +Additional information: +# diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2153 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2153 new file mode 100644 index 000000000..c1837b132 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2153 @@ -0,0 +1 @@ +ubuntu-20.04-s390x-all CI job is very flaky diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2154 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2154 new file mode 100644 index 000000000..5f5952955 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2154 @@ -0,0 +1,7 @@ +ID_AA64MMFR2_EL1 is all zeros +Description of problem: +When the `ID_AA64MMFR2_EL1` register is read via `mrs x[n], ID_AA64MMFR2_EL1`, it is read as all zeros. This is at the very least not correct for `ID_AA64MMFR2_EL1.ST`, which describes support for small translation tables (FEAT_TTST). +Steps to reproduce: +1. Run `mrs x[n], ID_AA64MMFR2_EL1` within qemu-system-aarch64 +Additional information: +FEAT_TTST is a relatively new aarch64 feature that appears to have caused many problems basically everywhere. However, [qemu has reportedly implemented it](https://www.qemu.org/2021/04/30/qemu-6-0-0/). diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2156 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2156 new file mode 100644 index 000000000..50fb9a348 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2156 @@ -0,0 +1,15 @@ +Userland QEMU segfaults when emulating itself thrice +Description of problem: +See title. +``` +$ qemu-x86_64-static qemu-x86_64-static qemu-x86_64-static /bin/true +qemu-x86_64-static: QEMU internal SIGSEGV {code=ACCERR, addr=0x7f9ae80001a0} +[1] 15705 segmentation fault (core dumped) qemu-x86_64-static qemu-x86_64-static qemu-x86_64-static /bin/true +``` +Steps to reproduce: +1. Execute command above +Additional information: +Coredump (~322MB uncompressed) +[qemu_qemu-x86_64-static_20240208-123447_15705.core.xz](/uploads/a6723aaf956dfd1efc434303e62c25e2/qemu_qemu-x86_64-static_20240208-123447_15705.core.xz) + +SHA1: 31c2b06a61f63dca5199b64b767aa2fdeefbeec6 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2157 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2157 new file mode 100644 index 000000000..3ec2175d2 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2157 @@ -0,0 +1,43 @@ +qemu-user fails to run 32-bit x86 binaries on hosts with a page size > 4KB +Description of problem: +`qemu-i386` refuses to run 32-bit x86 binaries on hosts with a page size > 4KB +(such as LoongArch, ppc64le, arm64 with 3 level page tables). +Steps to reproduce: +1. Compile x86 binary which makes a single exit(0) syscall: + ``` + cat > exit0.S << EOF + #include <sys/syscall.h> + .text + .global _start + _start: + movl $__NR_exit, %eax + movl $0, %ebx + int $0x80 + EOF + i586-linux-gnu-gcc -nostdlib -static -no-pie -o exit0 exit0.S + ``` + Alternatively one might compile it on a x86 host: + ``` + gcc -m32 -nostdlib -static -no-pie -o exit0 exit0.S + ``` + and transfer the `exit0` binary to ppc64/LoongArch/arm64 system + + 2. Run the `exit0` binary with `qemu-i386` + ``` + qemu-i386-static ./exit0 + ``` + + # +Additional information: +`.text` segment of (32-bit) x86 binaries is typically aligned at 4KB: +``` +Program Headers: + Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align + LOAD 0x000000 0x08048000 0x08048000 0x00100 0x00100 R 0x1000 + LOAD 0x001000 0x08049000 0x08049000 0x0000c 0x0000c R E 0x1000 + NOTE 0x0000b4 0x080480b4 0x080480b4 0x0004c 0x0004c R 0x4 + GNU_PROPERTY 0x0000d8 0x080480d8 0x080480d8 0x00028 0x00028 R 0x4 +``` + +Thus on a host with a page size being 64 KB (ppc64, arm64 with 3 level page tables) or 16 KB (LoongArch) +alignment requirements in [pbg_dynamic](https://gitlab.com/qemu-project/qemu/-/blob/master/linux-user/elfload.c?ref_type=heads#L3020) can not be satisfied. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2158 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2158 new file mode 100644 index 000000000..a2d5d2590 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2158 @@ -0,0 +1,9 @@ +Qemu will not release mouse even after using the release mouse keybind +Description of problem: +There wasn't a crash but this is an annoying problem. The mouse does not release when the VM sizes the window larger because, as far as I know, qemu moves the window and relies on the user to click to release the mouse. +Steps to reproduce: +1. Open qemu +2. Try to release the mouse using the keybind shown. +3. It move the window and won't release. +Additional information: +In case it's really needed, I am using a custom QEMU VM Manager called "QEMU Manager". diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2160 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2160 new file mode 100644 index 000000000..79003d03b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2160 @@ -0,0 +1 @@ +msys2-32bit CI job fails with "error: target not found: mingw-w64-i686-libusb" diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2161 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2161 new file mode 100644 index 000000000..7b0ecb23f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2161 @@ -0,0 +1 @@ +warnings when building lockstep plugin on s390 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2162 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2162 new file mode 100644 index 000000000..43f624831 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2162 @@ -0,0 +1 @@ +Some subtests have over-optimistic timeouts and time out on the s390 runner diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2167 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2167 new file mode 100644 index 000000000..61e5b9393 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2167 @@ -0,0 +1,40 @@ +The GPIO controllers connected to the emulated PCIe bus via vhost-user can't generate interrupts. +Description of problem: +The problem is related to emulation of GPIO controllers using the vhost-user protocol for GPIO. The problem was detected when using the [vhost-device-gpio](https://github.com/rust-vmm/vhost-device) software. I have described the whole issue in https://github.com/rust-vmm/vhost-device/issues/613 , but it is QEMU related, and therefore I describe it here as well. +The broader context is described in https://stackoverflow.com/questions/75906208/how-to-connect-via-virtio-gui-running-on-host-with-gpio-in-a-qemu-emulated-virtu . +Steps to reproduce: +1. For Debian/testing you need to compile a libgpiod-2.1.1 (I assume that the following is done in the home directory directory of the `dev` user: `/home/dev`): + + ``` + wget https://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git/snapshot/libgpiod-2.1.tar.gz ; \ + tar -xzf libgpiod-2.1.tar.gz ; \ + cd libgpiod-2.1 ; \ + autoupdate ; \ + ./autogen.sh ; \ + make + ``` + 2. Download the vhost-device-gpio (`git clone https://github.com/rust-vmm/vhost-device.git`) + 3. Build the vhost-device-gpio (in the `vhost-device-gpio` subdirectory) + + ``` + export PATH_TO_LIBGPIOD=/home/dev/libgpiod-2.1 + export SYSTEM_DEPS_LIBGPIOD_NO_PKG_CONFIG=1 + export SYSTEM_DEPS_LIBGPIOD_SEARCH_NATIVE="${PATH_TO_LIBGPIOD}/lib/.libs/" + export SYSTEM_DEPS_LIBGPIOD_LIB=gpiod + export SYSTEM_DEPS_LIBGPIOD_INCLUDE="${PATH_TO_LIBGPIOD}/include/" + cargo build --features "mock_gpio" + ``` + 4. Start vhost-device-gpio: (`LD_LIBRARY_PATH=/home/emb/libgpiod-2.1/lib/.libs/ ./vhost-device-gpio -s /tmp/gpio.sock -l s4`) + 5. Download the Buildroot 2023.11.1 (`wget https://buildroot.org/downloads/buildroot-2023.11.1.tar.xz` in another directory) and unpack it. Buildroot and the main directory of Buildroot tree are denoted by BR if the following description. + 6. Configure BR (run `make qemu_aarch64_virt_defconfig` in the main BR directory, run `make menuconfig` and select external toolchain, `BR2_PACKAGE_LIBGPIOD=y`, `BR2_PACKAGE_LIBGPIOD_TOOLS=y`, run `make linux-menuconfig` and select `CONFIG_GPIO_VIRTIO=m` in the kernel configuration) + 7. Build the Linux and QEMU (run `make` in the BR directory). + 8. Run the emulation in BR/output/images, using the command line given above. + 9. After the virtual machine starts, log in as root and load the driver: `modprobe gpio-virtio` +10. Try to monitor changes of one of the emulated pins: `gpiomon 0 0` +11. You'll get the error message: + + ``` + gpiomon: error waiting for events: No such device + ``` +Additional information: +[0009-enable-F-IRQ-in-virtio-pci.patch](/uploads/39bc04b2d94063ccd539c5cfbc9cd105/0009-enable-F-IRQ-in-virtio-pci.patch) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2171 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2171 new file mode 100644 index 000000000..6c6fd66bc --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2171 @@ -0,0 +1,25 @@ +VPS Disk space over use +Description of problem: +\# qemu-img info -U v1001-dluw9EHRDbmMd8fQ-CACjC7FWnMhISeDM.qcow2 + +file format: qcow2 + +virtual size: 800G (858993459200 bytes) + +disk size: **812G** + +cluster_size: 65536 + +Format specific information: + +compat: 1.1 + +lazy refcounts: false + +refcount bits: 16 + +corrupt: false + +Disk size is using beyond the Virtual size. + +How is that even possible ? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2172 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2172 new file mode 100644 index 000000000..b483a7ea1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2172 @@ -0,0 +1 @@ +Error "cannot enable SPICE if pixman is not available" diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2176 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2176 new file mode 100644 index 000000000..00e1cc781 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2176 @@ -0,0 +1 @@ +Events delivered during Capabilities Negotiation mode diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2177 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2177 new file mode 100644 index 000000000..659e2316c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2177 @@ -0,0 +1 @@ +msys2-32bit CI job fails with "error: target not found: mingw-w64-i686-dtc" diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2178 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2178 new file mode 100644 index 000000000..835a38d31 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2178 @@ -0,0 +1,17 @@ +USB passthrough on Apple Silicon is unusable +Description of problem: +I can't get USB passthrough to work sufficiently well with wifi modems such as the RTL8187L or Atheros AR 9271. + +I only use the VM as a router since the host OS doesn't have drivers for any external wifi modems. This is a setup I've used flawlessly many times in the past with other VMs on x86 platforms for many years, but with ARM it's been one fail after another. Parallels does work with the exact same host and guest, but fails in the networking area (plus it's expensive and overkill for something this simple). I mention this because I know the guest drivers work 100% with a different VM. +Steps to reproduce: +1. Run any Linux on QEMU on any Apple Silicon mac +2. Attempt to use a Atheros AR 9271 USB device +3. Various fails including + a) USB device not showing up (lsusb) + b) device shows up and Linux attempts to attach driver, but fails (lsmod shows driver loaded but no interface listed on iwconfig) + c) interface shows up (never got the Atheros this far, but RealTek does) but the interface is slow, corrupts data, etc. + d) after re-attaching several times it will eventually stop attaching at all requiring a MacOS system reboot, which is really annoying for my workflow. + +It's basically non-functional for me. Atheros is 100% non-functional and RealTek 10% works (well enough to *sometimes* connect to the AP, but usually craps the bed if you try to do anything as simple as run a dhcp client to fetch the IP). + +If anyone knows of any other Linux ARM on Mac ARM vm solutions that allow USB passthrough please let me know. Unfortunately, VirtualBox os currently not one of them. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2179 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2179 new file mode 100644 index 000000000..a04432f38 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2179 @@ -0,0 +1,51 @@ +qemu-storage-daemon: fuse export deadlock +Steps to reproduce: +1. Start QSD +2. Issue a `block-stream` and a read from the fuse export at the same time + +``` +Term 1: +(QEMU) block-stream device=root job-id=job1 +{"return": {}} +(QEMU) +{'timestamp': {'seconds': 1708386076, 'microseconds': 965781}, 'event': 'JOB_STATUS_CHANGE', 'data': {'status': 'created', 'id': 'job1'}} +{'timestamp': {'seconds': 1708386076, 'microseconds': 965838}, 'event': 'JOB_STATUS_CHANGE', 'data': {'status': 'running', 'id': 'job1'}} +(QEMU) +(QEMU) +(QEMU) +(QEMU) query-block-jobs + +<HANGS> + + +Term 2: +dd if=/tmp/fuse_exp of=/dev/null bs=1M skip=2000 +<HANGS> +``` + +``` +$ pidof qemu-storage-daemon + 92313 +$ sudo cat /proc/92313/task/92313/stack +[<0>] do_sys_poll+0x4e1/0x5d0 +[<0>] __x64_sys_ppoll+0xe2/0x170 +[<0>] do_syscall_64+0x64/0xe0 +[<0>] entry_SYSCALL_64_after_hwframe+0x6e/0x76 + +$ sudo cat /proc/92313/task/92314/stack +[<0>] futex_wait_queue+0x63/0x90 +[<0>] __futex_wait+0x14f/0x1c0 +[<0>] futex_wait+0x77/0x110 +[<0>] do_futex+0xcb/0x190 +[<0>] __x64_sys_futex+0x129/0x1e0 +[<0>] do_syscall_64+0x64/0xe0 +[<0>] entry_SYSCALL_64_after_hwframe+0x6e/0x76 +``` +Additional information: +This might also be a general between `block-stream` and `copy-on-read` but I could only trigger the problem with FUSE and not NBD. E.g this command does not deadlock: +``` +--export type=nbd,id=nbd-root,node-name=root_crw,name=root_crw,writable=off + +nbdfuse /tmp/tmp.69dRvNXj1O/disk nbd://localhost:10809/root_crw +dd if=/tmp/tmp.69dRvNXj1O/disk of=/dev/null bs=1M skip=2000 +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/218 b/gitlab/issues_text/target_missing/host_missing/accel_missing/218 new file mode 100644 index 000000000..1336b7545 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/218 @@ -0,0 +1 @@ +qemu-storage-daemon --nbd-server fails with "too many connections" error diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2182 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2182 new file mode 100644 index 000000000..f9b4bce51 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2182 @@ -0,0 +1 @@ +Replication and Network diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2184 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2184 new file mode 100644 index 000000000..479dd27f0 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2184 @@ -0,0 +1,53 @@ +NVMe differences between QEMU v4.1.0 and v8.2.1 +Description of problem: +We are currently upgrading QEMU from v4.1.0 to v8.2.1. In order to keep compatibility between the two QEMUs, we are adding ``-machine pc-q35-4.1``. One of our test is to ensure a guest that has hibernated on the previous QEMU is able to resume on the new one. + +When resuming, we get the following error: + +``` +[ 7.394709] nvme nvme0: Device not ready; aborting reset, CSTS=0x1 +[ 7.926188] nvme nvme0: Device not ready; aborting reset, CSTS=0x1 +[ 7.938235] Read-error on swap-device (259:0:4874880) +[ 7.938237] Read-error on swap-device (259:0:4620184) +[ 7.938240] Read-error on swap-device (259:0:5536464) +[ 7.938311] Read-error on swap-device (259:0:5006840) +[ 7.938316] Read-error on swap-device (259:0:5791888) +[ 7.938386] Read-error on swap-device (259:0:6579728) +[ 7.938391] Read-error on swap-device (259:0:5536680) +[ 7.938431] Read-error on swap-device (259:0:4877384) +[ 7.938434] Read-error on swap-device (259:0:5005376) +[ 7.938457] Read-error on swap-device (259:0:5269328) +[ 7.939200] EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1611: inode #1561: comm kworker/u8:1: reading directory lblock 0 +[ 7.939267] EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1611: inode #1561: comm kworker/u8:1: reading directory lblock 0 +[ 7.946359] EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1611: inode #1561: comm kworker/u8:1: reading directory lblock 0 +[ 8.063186] EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1611: inode #1561: comm kworker/u8:1: reading directory lblock 0 +[ 8.069556] Aborting journal on device nvme0n1p1-8. +[ 8.069561] Buffer I/O error on dev nvme0n1p1, logical block 262144, lost sync page write +[ 8.069564] JBD2: Error -5 detected when updating journal superblock for nvme0n1p1-8. +[ 8.081218] EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1611: inode #1561: comm kworker/u8:1: reading directory lblock 0 +[ 8.081242] Buffer I/O error on dev nvme0n1p1, logical block 0, lost sync page write +[ 8.081247] EXT4-fs (nvme0n1p1): I/O error while writing superblock +[ 8.147693] EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1611: inode #1561: comm kworker/u8:1: reading directory lblock 0 +[ 8.147753] Buffer I/O error on dev nvme0n1p1, logical block 0, lost sync page write +[ 8.163478] EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1611: inode #1561: comm kworker/u8:1: reading directory lblock 0 +[ 8.174179] EXT4-fs (nvme0n1p1): I/O error while writing superblock +[ 8.198741] EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1611: inode #1561: comm kworker/u8:2: reading directory lblock 0 +[ 8.214483] EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1611: inode #1561: comm kworker/u8:1: reading directory lblock 0 +[ 8.230322] EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1611: inode #1561: comm kworker/u8:2: reading directory lblock 0 +[ 8.246249] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b +[ 8.246269] Core dump to |/usr/share/apport/apport pipe failed +[ 8.246291] Core dump to |/usr/share/apport/apport pipe failed +[ 8.246336] Core dump to |/usr/share/apport/apport pipe failed +[ 8.246826] Core dump to |/usr/share/apport/apport pipe failed +[ 8.249232] Core dump to |/usr/share/apport/apport pipe failed +[ 8.249320] Core dump to |/usr/share/apport/apport pipe failed +[ 8.249880] Core dump to |/usr/share/apport/apport pipe failed +``` + +Digging throw the NVMe code, I have found one [patch](https://lists.gnu.org/archive/html/qemu-devel/2021-01/msg04202.html) changing the BAR layout. It doesn't look like there is a way to select the previous BAR layout. + +When selecting the ``-machine``, I was expecting that the underlying HW (including devices) would not change. Can you clarify if hibernating from QEMU A and resuming to QEMU B is meant to be supported? +Steps to reproduce: +1. Start the guest with qemu v4.1.0 and an NVME disk +2. Hibernate the OS +3. Resume the guest with qemu v8.2.1 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2186 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2186 new file mode 100644 index 000000000..c153ebf31 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2186 @@ -0,0 +1,34 @@ +riscv virt pflash0 writes not supported +Description of problem: +I am using GDB to debug some Firmware related stuff. At some point in the execution my BIOS/Firmware writes into some global variable (at 0x2000525C) inside the .bss section which is linked to be inside the memory mapped pflash0. But when I step forward with GDB to the exact location where the store instruction (sw) is executed, QEMU prints the following: +``` +pflash_write: Unimplemented flash cmd sequence (offset 000000000000525c, wcycle 0x0 cmd 0x0 value 0x1) +``` +According to the top of `hw/block/pflash_cfi01.c` Flash writes are supported. I was also under the impression that the flash is memory mapped, but maybe that is not true? I am probably missing something here so it would be nice if someone could point me in the right direction. I would also gladly contribute if there is something missing in the riscv virt target. + +I made a simple program to more easily reproduce this: +``` +.section .text +.global _start +_start: + lui a5, 0x20000 + li a4, 5 + sw a4, 24(a5) + +``` +results in QEMU error msg: +``` +pflash_write: Unimplemented flash cmd sequence (offset 0000000000000018, wcycle 0x0 cmd 0x0 value 0x5) +``` +Steps to reproduce: +1. compile above assembly program like this: +``` +riscv64-unknown-elf-gcc -nostdlib -O0 bios.S +riscv64-unknown-elf-objcopy -O binary a.out +truncate -s 33554432 a.out +``` +2. start QEMU like this: +``` +qemu-system-riscv64 -M virt -bios none -drive if=pflash,format=raw,unit=0,file=a.out -nographic -d unimp +``` +3. notice the error message printed by QEMU diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2187 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2187 new file mode 100644 index 000000000..83a67c450 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2187 @@ -0,0 +1 @@ +system/cpu: deadlock in pause_all_vcpus() diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2188 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2188 new file mode 100644 index 000000000..9ac358238 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2188 @@ -0,0 +1,10 @@ +virtio_gpu_gl_update_cursor_data() ignores the cursor resource's pixel format +Description of problem: +The function virtio_gpu_gl_update_cursor_data() ignores the pixel format of the resource it's reading from. It literally uses memcpy() to copy the pointer data. This works just fins if both the guest OS and the display backend use the same pixel format. + +The SDL backend seems to use a different pixel format to the GTK display backend. So, you'll get the correct colours in one, but not the other. +Steps to reproduce: +1. Run a VM using Virtio GPU using the GTK backend. Set the guest OS' mouse pointer to one that's red instead of white, and note the mouse pointer's actual colour +2. Now run the same VM using the SDL display backend. Check the colour of the mouse pointer (that should be red) + +NOTE: The choice of guest OS shouldn't matter. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2189 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2189 new file mode 100644 index 000000000..2bd6fdd8a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2189 @@ -0,0 +1,14 @@ +vhost_user:When configure queues of vhost-user NIC exceeds max_queues, the virtual machine is always paused +Description of problem: +When the virtual machine uses the vhost-user network card and sets the queue number of the network card to exceed the maximum number of supported queues, the virtual machine fails to start and stays in the paused state. +And the virtual machine log file kept print "qemu - system - x86_64: -netdev host-user,chardev=charnet0,queues=5,id=hostnet0:you are asking more queues than supported:4” +Steps to reproduce: +1.Configure vhost-user network cards for VMS and use multiple queues. +2.The number of NIC queues configured in the VM xml file is greater than the maximum number of queues supported by the VM, that is, the number of Vcpus on the VM. +3.Execute "virsh create VM_xml_file" cmd to start VM. +Additional information: +According to normal logic, if the number of configured vhost-user NIC queues exceeds max-queues, the qemu process should be stopped, rather than paused the virtual machine. +I am confused about this patch:https://github.com/qemu/qemu/commit/c89804d674e4e3804bd3ac1fe79650896044b4e8 +The process will remain in the do...while loop, when vhost_user_start is called in net_vhost_user_event, if queues > max_queues in vhost_user_start. +/label ~"kind::Bug" +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/219 b/gitlab/issues_text/target_missing/host_missing/accel_missing/219 new file mode 100644 index 000000000..d71ae53ec --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/219 @@ -0,0 +1 @@ +Request A Port of QEMU to UWP for xbox dev mode diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2190 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2190 new file mode 100644 index 000000000..0065e5818 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2190 @@ -0,0 +1,7 @@ +qemu-block-drivers.rst.inc is embedded twice +Description of problem: +`qemu-block-drivers.rst.inc` is included both in `docs/system/qemu-block-drivers.rst` and in `docs/system/images.rst`, so it is repeated both at https://www.qemu.org/docs/master/system/qemu-block-drivers.html and at https://www.qemu.org/docs/master/system/images.html . + +This also makes the generation of the sphinx `objects.inv` search index nondeterministic: it will point to one page or the other depending on random chance at build time. + +Perhaps instead of embedding the drivers, `images.rst` should point to https://www.qemu.org/docs/master/system/qemu-block-drivers.html for the list? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2191 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2191 new file mode 100644 index 000000000..308f54704 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2191 @@ -0,0 +1 @@ +Support exposing exports based on authentication diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2192 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2192 new file mode 100644 index 000000000..fbd692203 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2192 @@ -0,0 +1 @@ +make vm-build-openbsd tries to download nonexistent 7.2 install ISO: need to update to 7.4 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2194 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2194 new file mode 100644 index 000000000..7dcf208e2 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2194 @@ -0,0 +1,94 @@ +qemu-system-mips64el loongson3-virt fails to complete boot +Description of problem: +I try to install Debian 12 using the netboot kernel (6.1.0) and initrd: +``` +NETBOOT=http://ftp.debian.org/debian/dists/stable/main/installer-mips64el/current/images/loongson-3/netboot +wget $NETBOOT/initrd.gz +wget $NETBOOT/vmlinuz-6.1.0-18-loongson-3 -O vmlinuz +qemu-img create -f qcow2 disk.qcow2 30G +``` + +Then I boot the installer: +``` +qemu-system-mips64el \ + -machine loongson3-virt -cpu Loongson-3A1000 -smp 4 -m 6G -nographic \ + -kernel vmlinuz -initrd initrd.gz \ + -drive file=disk.qcow2,if=none,id=drive-virtio-disk0 \ + -device virtio-blk-pci,drive=drive-virtio-disk0 \ + -append "root=/dev/sda1" +``` + +The boot stops after this: +``` +[ 0.000000] Linux version 6.1.0-18-loongson-3 (debian-kernel@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT Debian 6.1.76-1 (2024-02-01) +[ 0.000000] Firmware: Coherent DMA: on +[ 0.000000] CpuClock = 800000000 +[ 0.000000] The bridge chip is VIRTUAL +[ 0.000000] CP0_Config3: CP0 16.3 (0x80) +[ 0.000000] CP0_PageGrain: CP0 5.1 (0x20000000) +[ 0.000000] NUMA: Discovered 4 cpus on 1 nodes +[ 0.000000] Node 0, mem_type:1 [0x0000000000000000], 0x000000000f000000 bytes usable +[ 0.000000] Node 0, mem_type:2 [0x0000000090000000], 0x0000000170000000 bytes usable +[ 0.000000] Node0's addrspace_offset is 0x0 +[ 0.000000] Node0: start_pfn=0x0, end_pfn=0x80000 +[ 0.000000] NUMA: set cpumask cpu 0 on node 0 +[ 0.000000] NUMA: set cpumask cpu 1 on node 0 +[ 0.000000] NUMA: set cpumask cpu 2 on node 0 +[ 0.000000] NUMA: set cpumask cpu 3 on node 0 +[ 0.000000] printk: bootconsole [early0] enabled +[ 0.000000] CPU0 revision is: 00006305 (ICT Loongson-3) +[ 0.000000] FPU revision is: 00770501 +[ 0.000000] MIPS: machine is loongson,loongson64v-4core-virtio +[ 0.000000] Initial ramdisk at: 0x9800000004000000 (28553950 bytes) +[ 0.000000] software IO TLB: area num 1. +[ 0.000000] software IO TLB: mapped [mem 0x0000000005b3c000-0x0000000009b3c000] (64MB) +[ 0.000000] DMI not present or invalid. +[ 0.000000] Detected 4 available CPU(s) +[ 0.000000] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes. +[ 0.000000] Primary data cache 64kB, 4-way, VIPT, no aliases, linesize 32 bytes +[ 0.000000] Unified victim cache 0kB direct mapped, linesize 0 bytes. +[ 0.000000] Unified secondary cache 4096kB 4-way, linesize 32 bytes. +[ 0.000000] Zone ranges: +[ 0.000000] DMA32 [mem 0x0000000000000000-0x00000000ffffffff] +[ 0.000000] Normal [mem 0x0000000100000000-0x00000001ffffffff] +[ 0.000000] Movable zone start for each node +[ 0.000000] Early memory node ranges +[ 0.000000] node 0: [mem 0x0000000000000000-0x000000000effffff] +[ 0.000000] node 0: [mem 0x0000000090000000-0x00000001ffffffff] +[ 0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x00000001ffffffff] +[ 0.000000] On node 0, zone DMA32: 1024 pages in unavailable ranges +[ 0.000000] percpu: Embedded 13 pages/cpu s170800 r8192 d34000 u212992 +[ 0.000000] Fallback order for Node 0: 0 +[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 390660 +[ 0.000000] Policy zone: Normal +[ 0.000000] Kernel command line: rd_start=0xffffffff84000000 rd_size=28553950 root=/dev/sda1 nokaslr +[ 0.000000] Unknown kernel command line parameters "nokaslr", will be passed to user space. +[ 0.000000] Dentry cache hash table entries: 1048576 (order: 9, 8388608 bytes, linear) +[ 0.000000] Inode-cache hash table entries: 524288 (order: 8, 4194304 bytes, linear) +[ 0.000000] mem auto-init: stack:all(zero), heap alloc:on, heap free:off +[ 0.000000] Memory: 2183328K/6275072K available (11247K kernel code, 1773K rwdata, 3152K rodata, 2688K init, 547K bss, 184208K reserved, 0K cma-reserved) +[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 +[ 0.000000] ftrace: allocating 32150 entries in 32 pages +[ 0.000000] ftrace: allocated 32 pages with 1 groups +[ 0.000000] trace event string verifier disabled +[ 0.000000] rcu: Preemptible hierarchical RCU implementation. +[ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=16 to nr_cpu_ids=4. +[ 0.000000] Trampoline variant of Tasks RCU enabled. +[ 0.000000] Rude variant of Tasks RCU enabled. +[ 0.000000] Tracing variant of Tasks RCU enabled. +[ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies. +[ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4 +[ 0.000000] NR_IRQS: 320 +[ 0.000000] ISA Bridge: /bus@10000000/isa@18000000 +[ 0.000000] IO 0x0000000018000000..0x0000000018003fff -> 0x0000000000000000 +[ 0.000000] rcu: srcu_init: Setting srcu_struct sizes based on contention. +[ 0.000000] clocksource: MIPS: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 4778151116 ns +[ 0.000072] sched_clock: 32 bits at 400MHz, resolution 2ns, wraps every 5368709118ns +[ 0.002813] Console: colour dummy device 80x25 +[ 0.003195] printk: console [tty0] enabled +[ 0.005876] printk: bootconsole [early0] disabled +``` + +Then, nothing happens. The qemu process uses 100% CPU on the host. + +I tried with `-smp 1` and got the same result. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2196 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2196 new file mode 100644 index 000000000..b16d477e6 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2196 @@ -0,0 +1 @@ +Missing support for video hardware accelerate support in virgl (virtio-gpu) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2197 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2197 new file mode 100644 index 000000000..789c6a254 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2197 @@ -0,0 +1,58 @@ +qemu user space emulator handles syscall `setsockopt()` with `optlen=0` incorrectly +Description of problem: +Note that despite I have only tested with the parameters/environments above, this problem probably **affects ALL architectures on Linux**. + +When user program calls `setsockopt(fd, SOL_ALG, ALG_SET_KEY, NULL, 0)`, qemu intercepts the syscall and returns `-1` with `errno = ENOMEM`, which should have completed successfully returning zero. +Steps to reproduce: +1. compile this code to binary executable: +```c +#include <unistd.h> +#include <sys/types.h> +#include <sys/socket.h> +#include <stdio.h> +#include <stdlib.h> +#include <string.h> +#include <linux/if_alg.h> + +int create_alg(const char *alg) +{ + struct sockaddr_alg salg; + int sk; + + sk = socket(PF_ALG, SOCK_SEQPACKET | SOCK_CLOEXEC, 0); + if (sk < 0) + return -1; + + memset(&salg, 0, sizeof(salg)); + salg.salg_family = AF_ALG; + strcpy((char *) salg.salg_type, "hash"); + strcpy((char *) salg.salg_name, alg); + + if (bind(sk, (struct sockaddr *) &salg, sizeof(salg)) < 0) { + close(sk); + return -1; + } + + return sk; +} + +int main() { + int fd = create_alg("hmac(sha1)"); + char buf[10]; + int ret = setsockopt(fd, SOL_ALG, ALG_SET_KEY, NULL, 0); + if(ret < 0){ + perror("err"); + } + else{ + puts("SUCCESS!"); + } + return 0; +} +``` +2. run it in any qemu user space emulator + +On real Linux kernel, this program outputs a `SUCCESS!` while in qemu it prints `err: Cannot allocate memory`. + +The error is neither informative nor intuitive and could be misleading for user programs. +Additional information: +I already have a patch which fixes the issue and I'm willing to send it to mailing list as soon as I have done the testing. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2199 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2199 new file mode 100644 index 000000000..84b5b488e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2199 @@ -0,0 +1,12 @@ +QEMU8 not working properly for Win9x guest +Description of problem: +Cannot boot to Win9x desktop. Enter safe mode of Win9x, then open C:\Windows\system\iosubsys, then rename drvwq117.vxd to drvwq117.vxd.bak, this problem solved.<br /> +Sound card and network card not found in Win9x Device Manager.<br /> +Cannot change resolution in Win9x Control Panel, this will cause "RUNDLL32 program error". + +We found that Plug-and-Play (\$PNP) and PCI IRQ Routing (\$PIR) functions of SeaBIOS are buggy for Win9x guest. +Steps to reproduce: +1.Install Win98 RTM on QEMU8, it cannot boot to Win98 desktop.<br /> +2.Install WinME on QEMU8, it will stuck on "copying files". +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/220 b/gitlab/issues_text/target_missing/host_missing/accel_missing/220 new file mode 100644 index 000000000..1782727ea --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/220 @@ -0,0 +1 @@ +Broken mouse movement inside MS-DOS for at least one program diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2201 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2201 new file mode 100644 index 000000000..b830cca40 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2201 @@ -0,0 +1,11 @@ +Windows 11 Guests ExtendedDesktopSize Not Working +Description of problem: +Windows 11 VM with the latest virtio-win drivers installed (v0.1.240) does not respond to remote resize requests. +Steps to reproduce: +1. Create a Windows 11 VM with virtio-win drivers installed and virtio video enabled. +2. Create a VNC session with resizeSession enabled. +3. Try resizing the window. +Additional information: +The resolution can be resized within the VM itself (i.e., from display settings), just doesn't automatically resize when the viewing window changes. Other VMs (including Windows 10) created and viewed within the same setup do change with the window resize. + +The Chrome console log has a number of `Server did not accept resize request: Unknown reason` errors in it. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2202 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2202 new file mode 100644 index 000000000..840aa6c9a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2202 @@ -0,0 +1,33 @@ +Crash in contrib/elf2dmp +Description of problem: +The elf2dmp program crash. +``` +$ ./contrib/elf2dmp/elf2dmp ./crash_1 /dev/null +Using Linux mmap +[1] 994585 segmentation fault ./contrib/elf2dmp/elf2dmp ./crash_1 /dev/null +``` +Steps to reproduce: +1. build the qemu project following standard steps +2. navigate to the `build` directory and run `./contrib/elf2dmp/elf2dmp ./crash_1 /dev/null` + +The [crash_1](/uploads/d0890c0f8873b8264c417b0f98ee83a4/crash_1) file. +Additional information: +Run in GDB. +``` +$ gdb ./contrib/elf2dmp/elf2dmp +... +(gdb) set args ./crash_1 /dev/null +(gdb) r +Starting program: /data/share/qemu_latest/build/contrib/elf2dmp/elf2dmp ./crash_1 /dev/null +[Thread debugging using libthread_db enabled] +Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". +Using Linux mmap + +Program received signal SIGSEGV, Segmentation fault. +init_states (qe=0x7fffffff83f0) at ../contrib/elf2dmp/qemu_elf.c:66 +66 Elf64_Nhdr *start = (void *)((uint8_t *)qe->map + phdr[0].p_offset); +(gdb) bt +#0 init_states (qe=0x7fffffff83f0) at ../contrib/elf2dmp/qemu_elf.c:66 +#1 QEMU_Elf_init (qe=qe@entry=0x7fffffff83f0, filename=<optimized out>) at ../contrib/elf2dmp/qemu_elf.c:235 +#2 0x0000555555555508 in main (argc=<optimized out>, argv=0x7fffffffdb58) at ../contrib/elf2dmp/main.c:538 +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2204 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2204 new file mode 100644 index 000000000..f66253dd8 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2204 @@ -0,0 +1,73 @@ +Hyper-V on Windows Server 2022 cannot load images converted from OVA to VHDX by qemu-img: Boot failure. Reboot and Select proper Boot device or Insert Boot Media in selected Boot device +Description of problem: +We have reference OVA image: https://storage.googleapis.com/fastnetmon_advanced_vm_images/fastnetmon-ubuntu-22.04-amd64-2.0.360.0.ova and we want to convert it to VMDX format. +Steps to reproduce: +I downloaded reference OVA and converted it to VMDX with three possible options. + +With subformat dynamic: +``` +qemu-img convert fastnetmon-ubuntu-22.04-amd64-2.0.360.0.ova -O vhdx -o subformat=dynamic fastnetmon-ubuntu-22.04-amd64-2.0.360.0.vhdx +``` + +And without it: +``` +qemu-img convert fastnetmon-ubuntu-22.04-amd64-2.0.360.0.ova -O vhdx fastnetmon-ubuntu-22.04-amd64-2.0.360.0.vhdx +``` + +And with explicitly setting fixed: +``` +qemu-img convert fastnetmon-ubuntu-22.04-amd64-2.0.360.0.ova -O vhdx -o subformat=fixed fastnetmon-ubuntu-22.04-amd64-2.0.360.0.vhdx +``` + +In all cases I tried loading images using VM of Generation 1 and Generation 2: +``` +The application encountered an error while attempting to change the state of +'New Virtual Machine'. + +'New Virtual Machine' failed to start. + +Microsoft Emulated IDE Controller (Instance ID 83F8638B-8DCA-4152-9EDA-2CA8B33039B4): Failed to Power on with Error 'The requested operation could not be completed due to a virtual disk system limitation. Virtual hard disk files must be uncompressed and unencrypted and must not be sparse.. + +Failed to open attachment 'C:\Program Files\qemu\fastnetmon_non_dynamic.hdx''. Error: 'The requested operation could not be completed due to a virtual disk system limitation. Virtual hard disk files must be uncompressed and unencrypted and must not be sparse.. + +Failed to open attachment 'C:\Program Files\qemu\fastnetmon_non_dynamic.vhdx'. Error: 'The requested operation could not be completed due to a virtual disk system limitation. Virtual hard disk files must be uncompressed and unencrypted and must not be sparse.'. +``` + +I noticed some similarities with https://gitlab.com/qemu-project/qemu/-/issues/136 and applied workaround to fix it: +``` +fsutil sparse setflag fastnetmon-ubuntu-22.04-amd64-2.0.360.0.vhdx 0 +``` + +It started complaining that file is being used by another app. I waited long enough and then rebooted server. + +After that error changed to: +``` +Boot failure. Reboot and Select proper Boot device or Insert Boot Media in selected Boot device_ +``` + +As image: + + + +For Generation 2 error is slightly different: +``` +Virtual Machine Boot Summary +1. SCSI Disk +(0,0) +The boot loader did not load an operating system. +2. Network Adapter (00155D01770C) +A boot image was not found. +``` + +As image:  + +I tried doing conversion from VirtualBox with same OVA and it worked just fine: +``` +VBoxManage clonehd fastnetmon-ubuntu-22.04-amd64-disk1.vmdk fastnetmon.vhd --format vhd +``` + +I believe something is wrong with boot records for VMDX images. + +Example of converted VHDX with dynamic flag can be found here: https://storage.googleapis.com/fastnetmon_advanced_vm_images/fastnetmon-ubuntu-22.04-amd64-2.0.356.0.vhdx + +By Pavel Odintsov at FastNetMon.com diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2205 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2205 new file mode 100644 index 000000000..e7661af17 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2205 @@ -0,0 +1,50 @@ +9p rootfs issues +Description of problem: +I've created qemu guest per https://wiki.qemu.org/Documentation/9p_root_fs guidelines. debootstrap fails on this guest. +Steps to reproduce: +``` +root@ubuntu-dev:~# debootstrap --arch amd64 --variant=minbase noble /var/tmp/new_root/ +I: Retrieving InRelease +I: Checking Release signature +E: Error executing gpgv to check Release signature +root@ubuntu-dev:~# +``` +Additional information: +I noticed, that gpg key extracted by debootstrap from the InRelease is corrupted: +``` +root@ubuntu-dev:~# head /var/tmp/new_root/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_noble_Release.gpg +-----BEGIN PGP SIGNATURE----- +-----BEGIN PGP SIGNATURE----- + +-----BEGIN PGP SIGNATURE----- +-----BEGIN PGP SIGNATURE----- + +iQIzBAEBCgAdFiEE9uyzdiR07anSG3Aihxkg0ZkbyTwFAmXkbkUACgkQhxkg0Zkb +-----BEGIN PGP SIGNATURE----- +-----BEGIN PGP SIGNATURE----- + +root@ubuntu-dev:~# +``` +I also noticed that on the 9p filesystem appending to files corrupts them: +``` +root@ubuntu-dev:~# echo 1 >/var/tmp/test +root@ubuntu-dev:~# cat /var/tmp/test +1 +root@ubuntu-dev:~# echo 2 >>/var/tmp/test +root@ubuntu-dev:~# cat /var/tmp/test +1 +1 +2 +root@ubuntu-dev:~# +``` +This is not happening on the tmpfs: +``` +root@ubuntu-dev:~# echo 1 >/tmp/test +root@ubuntu-dev:~# cat /tmp/test +1 +root@ubuntu-dev:~# echo 2 >>/tmp/test +root@ubuntu-dev:~# cat /tmp/test +1 +2 +root@ubuntu-dev:~# +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2209 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2209 new file mode 100644 index 000000000..ad4ab0a10 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2209 @@ -0,0 +1,47 @@ +no 'system' llibfdt (or too old), subprojects/dtc/ populated, ./configure --disable-download fails +Description of problem: +./configure ... --disable-download, with subprojects/ pre-populated, fails. +Steps to reproduce: +1. ensure libfdt/dtc files/libs/binaries are *not* found in system +2. have subprojects/dtc pre-populated +3. ./configure --target-list=riscv32-softmmu --prefix=/opt/riscv --enable-debug --without-default-features --without-default-devices --disable-download + +configure fails with: +``` +../meson.build:3171:13: ERROR: C shared or static library 'fdt' not found + +A full log can be found at /home/too/vc/ext/qemu/build/meson-logs/meson-log.txt + +ERROR: meson setup failed +``` + +If I outcomment the following lines in meson.build: +``` + #if get_option('wrap_mode') == 'nodownload' + # fdt_opt = 'system' + #endif +``` +Then the above command line works (with --disable-download) +Additional information: +The case is where one wants to ensure that configure does not try to access +network while doing its job. And in a system where dtc/libfdt is not available, +(or is too old, line in Centos/RHEL 7) one has dowloaded the files already in +subprojects/dtc/. + +The meson.build clearly sets (as of 2024-03-05) expectation that dtc/libfdt/ +has to come from 'system' if 'wrap_mode' is set to 'nodownload'. + +Without this check it it works nicely -- and if subprojects/dtc/ was not populated, +the error message is + +``` +Library fdt found: NO + +../meson.build:3187:18: ERROR: Automatic wrap-based subproject downloading is disabled + +A full log can be found at /home/too/vc/ext/qemu/build/meson-logs/meson-log.txt + +ERROR: meson setup failed +``` + +So -- to me -- that looks like it could be a suitable solution to this problem. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2210 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2210 new file mode 100644 index 000000000..b259cacc5 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2210 @@ -0,0 +1,55 @@ +contrib/plugins/execlog.c: warning: passing argument 2 of ‘g_ptr_array_add’ discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers] +Description of problem: +Hit some warning messages when compiling upstream qemu +Steps to reproduce: +1. Clone repo and compile it + + 1.1 git clone https://gitlab.com/qemu-project/qemu.git + + 1.2 mkdir build + + 1.3 cd build/ + + 1.4 ../configure --target-list=x86_64-softmmu --enable-debug-info + + 1.5 make + +2. It will print the following warning messages: +``` +[2767/2767] Linking target tests/qtest/netdev-socket +/root/qemu/contrib/plugins/execlog.c: In function ‘registers_init’: +/root/qemu/contrib/plugins/execlog.c:339:63: warning: passing argument 2 of ‘g_ptr_array_add’ discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers] + 339 | g_ptr_array_add(all_reg_names, reg->name); + | ~~~^~~~~~ +In file included from /usr/include/glib-2.0/glib.h:31, + from /root/qemu/contrib/plugins/execlog.c:9: +/usr/include/glib-2.0/glib/garray.h:192:62: note: expected ‘gpointer’ {aka ‘void *’} but argument is of type ‘const char *’ + 192 | gpointer data); + | ~~~~~~~~~~~~~~~~~~^~~~ +``` +Additional information: +1. After Eugenio Perez Martin (eperezma@redhat.com) debug, we found this problem introduced by this commit: +``` +commit af6e4e0a22c18a7cc97650caec56ed99c9899dd7 +Author: Alex Bennée <alex.bennee@linaro.org> +Date: Tue Feb 27 14:43:32 2024 +0000 + + contrib/plugins: extend execlog to track register changes +``` +2. The latest commit in my env: +``` +commit db596ae19040574e41d086e78469014191d7d7fc (origin/staging, origin/master, origin/HEAD) +Merge: 7d4e29ef80 7558300c53 +Author: Peter Maydell <peter.maydell@linaro.org> +Date: Tue Mar 5 13:54:54 2024 +0000 + + Merge tag 'pull-target-arm-20240305' of https://git.linaro.org/people/pmaydell/qemu-arm into staging + + target-arm queue: + * raspi: Implement Broadcom Serial Controller (BSC) for BCM2835 boards + * hw/char/pl011: Add support for loopback + * STM32L4x5: Implement RCC clock control device + * target/arm: Do memory type alignment checks + * atomic.h: Reword confusing comment for qatomic_cmpxchg + * qemu-options.hx: Don't claim "-serial" has limit of 4 serial ports +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2211 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2211 new file mode 100644 index 000000000..961caa6a3 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2211 @@ -0,0 +1,27 @@ +Live Migration Issue - get_pci_config_device: Bad config data +Description of problem: +Hello everybody, +recently i have updated my environment from QEMU 7.1 (Build based from Upstream Code) to QEMU 7.2 (Build based from Upstream Code). +Since the patching went very well, i noticed that Live Migrations are not possible anymore. +It looks like that the Migration Process itself is running fine, but at the moment where QEMU wants to get the VM back live on the destination node, it crashes with the following error: + +``` +internal error: qemu unexpectedly closed the monitor: 2024-03-06T16:05:46.118520Z qemu-system-x86_64: get_pci_config_device: Bad config data: i=0x34 read: c8 device: dc cmask: ff wmask: 0 w1cmask:0 +2024-03-06T16:05:46.118804Z qemu-system-x86_64: Failed to load PCIDevice:config +2024-03-06T16:05:46.118813Z qemu-system-x86_64: Failed to load virtio-rng:virtio +2024-03-06T16:05:46.118821Z qemu-system-x86_64: error while loading state for instance 0x0 of device '0000:00:02.5:00.0/virtio-rng' +2024-03-06T16:05:46.120947Z qemu-system-x86_64: load of migration failed: Invalid argument +``` + +If i would stop/start the instance in question, live migration is back working. +This let me think that this might be an issue caused by the VM emulation process isn't running with the latest source of QEMU 7.2? + +Could someone please help me to figure out how i could resolve this issue to unblock the live migration capability without restarting all of my instances? +Steps to reproduce: +1. Prepare to Test Systems + - SOURCE = Install with QEMU 7.1 + - DESTINATION = Install with QEMU 7.2 +2. Start an example VM instance on the SOURCE +3. Update QEMU to 7.2 on the SOURCE +4. Start Live Migration from SOURCE to DESTINATION. +5. Error should be raised like mentioned above diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2212 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2212 new file mode 100644 index 000000000..77b8f4469 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2212 @@ -0,0 +1,17 @@ +"pci_hp_register failed with error -16" was found in Guest when launching VM with pci-bridge and "-machine q35" +Description of problem: +Host and guest config file configuration: + CONFIG_HOTPLUG_PCI_CPCI=y + CONFIG_HOTPLUG_PCI_CPCI_ZT5550=m + CONFIG_HOTPLUG_PCI_CPCI_GENERIC=m + CONFIG_HOTPLUG_PCI_SHPC=y +Use this configuration kernel to boot QEMU, with the QEMU parameter "-machine q35 -device pci-bridge,id=bridge0,chassis_nr=1". After the guest boot, dmesg will display "shpchp 0000:00:04.0: pci_hp_register failed with error -16". +Steps to reproduce: +1.Boot QEMU + +2.Check dmesg in VM +Additional information: +Error log: +[root@localhost ~]# dmesg | grep pci_hp_register +[ 0.723893] shpchp 0000:00:04.0: pci_hp_register failed with error -16 +[dmesg.log](/uploads/8ce302f996255544b4327d27ea4ac555/dmesg.log) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2214 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2214 new file mode 100644 index 000000000..48af3e9ad --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2214 @@ -0,0 +1 @@ +QEMU gdbstub does not report SIGALRM diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2215 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2215 new file mode 100644 index 000000000..913d4da2f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2215 @@ -0,0 +1 @@ +qemu-8.2.2 compile failure against musl diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2216 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2216 new file mode 100644 index 000000000..b30f438ea --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2216 @@ -0,0 +1,3 @@ +Incresaed artifacts generation speed with paralleled process +Additional information: +`parallel-jobs` was referenced `main` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2217 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2217 new file mode 100644 index 000000000..b053f1086 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2217 @@ -0,0 +1 @@ +Changing screen grab diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2219 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2219 new file mode 100644 index 000000000..9fdbb1fb9 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2219 @@ -0,0 +1 @@ +Core dump instead of error when starting on nohz_full system with enable-membarrier diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/222 b/gitlab/issues_text/target_missing/host_missing/accel_missing/222 new file mode 100644 index 000000000..05a608213 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/222 @@ -0,0 +1 @@ +Reading /proc/self/task/<pid>/maps is not remapped to the target diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2221 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2221 new file mode 100644 index 000000000..5c1b94f56 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2221 @@ -0,0 +1 @@ +CI timeouts on 'gcov' job: test-bufferiszero, test-crypto-tlscredsx509 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2222 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2222 new file mode 100644 index 000000000..4203146a5 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2222 @@ -0,0 +1 @@ +elf2dmp has endianness bugs diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2225 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2225 new file mode 100644 index 000000000..395e7efa5 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2225 @@ -0,0 +1,11 @@ +Mouse capture doesn't actually capture (GTK) +Description of problem: +The mouse is never actually captured by the window, you can always move it off screen, and because the guest OS has no awareness of the absolute mouse position there are many situations where you can't actually click something in the guest OS because the host mouse cursor is out of the window so clicking clicks on another program's window. It's unusable. + +It's clear that the problem is that the cursor isn't actually captured, if it ever was then the problem wouldn't occur. When the mouse is "uncaptured" we see the host cursor at all times and the guest cursor simply doesn't move, but when it's """captured""" the guest cursor still moves freely, it's just hidden while hovering the entire window (and not just the guest rectangle but really the whole thing) and the host cursor moves too at its own pace. + +It happens with `-display gtk` but not `-display sdl`. +Steps to reproduce: +1. Launch windowed guest +2. Click on window +3. Try to move mouse out of the window diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2231 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2231 new file mode 100644 index 000000000..8cf78950d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2231 @@ -0,0 +1,14 @@ +GNOME/Mutter - Wayland Fractional Scaling Breaks VM Resolution +Description of problem: +VMs are rendered at a higher resolution than the pixel count of their window, seemingly because mutter is upscaling for fractional scaling. +Steps to reproduce: +1. Enable GNOME Mutter experimental fractional scaling +2. Launch VM +Additional information: +This only occurs when wayland fractional scaling is enabled, not when text is scaled. Since GNOME/mutter accomplishes fractional scaling by upscaling, I think the VM is being told its window has a higher resolution than it actually has, so it is rendering the VM at a higher resolution, which is then displayed at the display's real resolution. + +In the screenshot below, my resolution is 2256 x 1504 and I have set fractional scaling to 125%. It is worth noting (2256 / 1.25) / 3606 is approximately 0.5. + + + +I apologize if the report is unsatisfactory. I will provide more detail if instructed. I tried reporting to GNOME Boxes and Virt-manager, which both use QEMU, but it seems the problem is upstream. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2232 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2232 new file mode 100644 index 000000000..65be2e2a8 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2232 @@ -0,0 +1 @@ +ui/qemu.desktop is nonconformant with the desktop entry specification diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2233 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2233 new file mode 100644 index 000000000..d8e703eac --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2233 @@ -0,0 +1,49 @@ +EDK2 BIOS images have wrong version string +Description of problem: +cosmetic, low priority, but maybe easy to fix +I think the displayed version inside the edk2 bios interface is not updating from version to version. +The updated version number is useful for the qemu-user to be assured that the updated bios file is in use. + +There is also some unreliability in whether the bios screen is entered on pressing F2. I need to try do it a few times, that is restart qemu, for it to succeed and reach the bios interface. No issue with registering the F2 keystroke, starting screen does react to it. Sometimes it stops on a intermediate bios screen that does probing. I documented this as a different bug #2234 . + +The reason I am trying out these bios files is because I am having trouble booting an iso image, which I filed as a different bug #2235. + +This is how I create a bios file on update of a qemu version. +I have extracted and overwritten the 8.2.0 files in the scoop installed qemu folder with 9.0.0-rc0 files from gitlab artifact. +I have used ```qemu-setup-v9.0.0-rc0-42-g54294b23e1.exe``` which should include kraxel's 20240320 pull request ```[PULL 0/5] Edk2 20240320 patches Gerd Hoffmann```. +In a command prompt window +```C:\vol\scoop_01\scoopg\apps\qemu\8.2.0\share> C:\vol\scoop_01\scoopg\apps\git\current\usr\bin\cat.exe .\edk2-i386-vars.fd .\edk2-x86_64-code.fd > D:\vstorage\win_m01_qemu_2403_edk2-x86_64.fd``` + +so far following files have been created +``` +D:\vstorage>dir D:\vstorage\win_m01_qemu_2* + Volume in drive D is VD_15KJ + Volume Serial Number is 1EA6-2771 + + Directory of D:\vstorage + +04/17/2023 09:23 PM 4,194,304 win_m01_qemu_2302_edk2-x86_64.fd # 8.0.0 +03/20/2024 10:31 AM 4,194,304 win_m01_qemu_2308_edk2-x86_64.fd # 8.1.0 +03/20/2024 01:18 PM 4,194,304 win_m01_qemu_2402_edk2-x86_64.fd # 8.2.0 +03/21/2024 11:24 AM 4,194,304 win_m01_qemu_2403_edk2-x86_64.fd # 9.0.0-rc0 + 4 File(s) 16,777,216 bytes + 0 Dir(s) 140,732,907,520 bytes free + +D:\vstorage>C:\vol\scoop_01\scoopg\apps\git\current\usr\bin\cmp.exe win_m01_qemu_2302_edk2-x86_64.fd win_m01_qemu_2403_edk2-x86_64.fd +win_m01_qemu_2302_edk2-x86_64.fd win_m01_qemu_2403_edk2-x86_64.fd differ: char 540809, line 1 + +D:\vstorage>C:\vol\scoop_01\scoopg\apps\git\current\usr\bin\cmp.exe win_m01_qemu_2402_edk2-x86_64.fd win_m01_qemu_2403_edk2-x86_64.fd +D:\vstorage> +``` + +The above indicate to me that nothing has changed in edk2 binaries between 8.2.0 and 9.0.0. Is that correct? +Steps to reproduce: +1. start qemu +2. press F2 when qemu guest display window pops up. When it works, it brings up the edk2 bios interface. +3. observe guest display screen . Notice that the displayed version still says `edk2-stable202302-for-qemu`. The displayed version has remained the same regardless of the bios file being used to boot qemu be they from 8.0.0 upto 9.0.0 + I expect it to show `edk2-stable202302-for-qemu`, `edk2-stable202308-for-qemu`, `edk2-stable202402-for-qemu`, `edk2-stable202403-for-qemu` etc + +guest display screen + +Additional information: +herein notifying @kraxel diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2234 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2234 new file mode 100644 index 000000000..55298a8dc --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2234 @@ -0,0 +1,23 @@ +upon pressing F2 failures in loading the edk2 bios interface app +Description of problem: +Cosmetic, low priority, but maybe easy to fix +Occasional failures to load the edk2 bios interface app +Workaround, retry until success +Steps to reproduce: +1. start qemu +2. press F2 when qemu guest display window pops up. When it works, it brings up the edk2 bios interface. + This bug concerns the case when it does not work + +For reasons not clear, sometimes, after pressing F2, and after qemu registered the key-stroke (F2) and responded by changing the window size, the bios interface loading process seems to abruptly stop at the following guest-display-screen with the following message. +```BdsDxe: Loading Boot0000 "UiApp" From Fv(7CB8BDC9-F8EB-F434-AAEA-3EE4AF6516A1)/FvFile(462CAA21-7614-4503-836E-8AB6F4662311)``` + + +When the bios interface loading process does succeed, it goes to the expected screen: + +Additional information: +Unsure if this sort of bug should go upstream to https://github.com/tianocore/edk2/issues +Herein notifying @kraxel + +Not a measured statistic, but on basis of feeling, I'd qualitatively say 4 out of 5 times it fails to bring up the bios interface. Its a bit frustrating because it feels like one has no control over it and a successful event is left to chance. + +This isn't a recent introduction/regression. I've noticed this since 8.0.0, so its been this way maybe longer. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2235 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2235 new file mode 100644 index 000000000..167ff307f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2235 @@ -0,0 +1,57 @@ +Hiren's Bootcd PE LiveCD not booting in windows qemu +Description of problem: +Hiren's Bootcd PE LiveCD not booting up in windows qemu. +PE stands for pre-execution environment which is like a minimal boot environment like windows-recovery. +The ram drive it makes is about 3.5 GiB. +Being able to boot something like Hiren BootCD PE is like a simple test of qemu. + +I've tried many things, but I can't figure out if it's because I can't get the arguments right or if it is because of something else. + +So far, using windows-qemu, I have not tried to boot a win10-guest-OS on win10 host-OS. +Steps to reproduce: +1. Try to start qemu as per command. Try figure out what the right arguments/options are. + +The live cd boot process is as follows +1. First the livecd bootloader loads files from the cdrom and unpacks them into a ramdrive + During this phase, in the taskmgr it can be seen that the memory of the qemu process grows to about 1.5 GiB +2. Then the boot process should transfer to the unpacked OS in the ramdrive. + In the center of the screen, if one is doing efi-boot, then one can see the tianocore logo, else if one is doing legacy boot, then one can see the windows logo. + The windows loading animation, dots in circle, does not start. In some boot attempts, it seems to have put only 1 dot, in other boot attempts nothing at all. + Even after the expansion phase, the qemu process in the taskmgr shows a 11% use (which 1 cpu in a hyperthreading i7 quadcore cpu). + This means emulator is doing something. But, despite waiting for a long time, nothing seems to happen in the guest-display-window. + +``` +PS F:\> dir D:\bootable\hb*.iso + + Directory: D:\bootable + +Mode LastWriteTime Length Name +---- ------------- ------ ---- +-a--- 9/17/2021 7:29 PM 3099203584 HBCD_PE_x64_v1.0.2_20210701.iso +-a--- 3/13/2024 4:45 PM 3291686912 HBCD_PE_x64_v1.0.8_20240305.iso + +PS F:\> Get-FileHash -Algorithm SHA256 D:\bootable\HBCD_PE_x64_v1.0.2_20210701.iso + +Algorithm Hash Path +--------- ---- ---- +SHA256 8281107683E81BE362AFD213026D05B2219BC6A7CA9AF4D2856663F3FFC17BFD D:\bootable\HBCD_PE_x64_v1.0.2_… + +PS F:\> Get-FileHash -Algorithm SHA256 D:\bootable\HBCD_PE_x64_v1.0.8_20240305.iso + +Algorithm Hash Path +--------- ---- ---- +SHA256 8C4C670C9C84D6C4B5A9C32E0AA5A55D8C23DE851D259207D54679EA774C2498 D:\bootable\HBCD_PE_x64_v1.0.8_… + +PS F:\> Get-Content D:\bootable\HBCD_PE_x64_v1.0.2_20210701.iso.sha256 +8281107683E81BE362AFD213026D05B2219BC6A7CA9AF4D2856663F3FFC17BFD HBCD_PE_x64_v1.0.2_20210701.iso +PS F:\> Get-Content D:\bootable\HBCD_PE_x64_v1.0.8_20240305.iso.sha256 +8c4c670c9c84d6c4b5a9c32e0aa5a55d8c23de851d259207d54679ea774c2498 HBCD_PE_x64_v1.0.8_20240305.iso +``` +Additional information: +- https://www.hirensbootcd.org/download/ +- method to create the bios file is explained in #2233 +- I have booted into v1.0.2 in native, so I know v1.0.2 works. +- I have tried qemu with and without EFI bios. +- The more recent v1.0.8 released on 20240305 is Win11 PE based (>22621) +- Virtualbox-7.0.14 is able to boot HBCDPE as normal, but with EFI disabled, and not when enabled. +- As of this issue creation, not yet checked whether under Linux if qemu-kvm can boot HBCDPE. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2237 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2237 new file mode 100644 index 000000000..84381a322 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2237 @@ -0,0 +1,39 @@ +mirror block job memory leak +Description of problem: +After creating a background mirror job, and then the connection to the mirror target storage be interrupted and writing cannot be performed, the qemu process memory will increase significantly every time the mirror job performs a write. When the target stroage is restored, the data writing will be completed normally, but the memory will not be reduced. +Steps to reproduce: +1. start a virtual machine with libvirt(virsh start file) +2. add a target mirror block dev, configure io timeout to 2 sec(virsh qemu-monitor-command file --pretty '{"execute": "blockdev-add", "arguments": {"driver": "raw", "cache": {"direct": true}, "node-name": "node-target","file": {"driver": "rbd", "conf":"/etc/ceph/ceph.node53.conf", "pool": "test", "image": "rbd1", "auth-client-required": ["none"], "server": [{"host": "10.0.12.53", "port": "6789"}]}}}') +3. create a background mirror block job(virsh qemu-monitor-command file --pretty '{ "execute": "blockdev-mirror", "arguments": {"device": "libvirt-1-format", "target": "node-target", "sync": "full", "copy-mode": "background", "on-target-error": "ignore", "job-id": "job0"}}') +4. wait for the initial full synchronization to complete +5. write a large number of random ios in the virtual machine with the fio program(fio -filename=/dev/vdb -direct=1 -iodepth 1 -thread -rw=randwrite -ioengine=psync -bs=4k -size=4G -numjobs=1 -runtime=300 -group_reporting -name=sep) +6. break the connection with the remote storage or shutdown the remote storage while fio program is running(if the connection is interrupted first and then written io, the probability of reproduce is very low) +7. qemu will report an error indicating that io writing failed and try to write again(qemu-kvm: rbd request failed: cmd 1 offset 1421803520 bytes 1048576 flags 0 task.ret -110 (Connection timed out)) +8. use the numastat command to continuously observe the memory usage of the process and find that the heap memory has increased significantly. + +``` +Per-node process memory usage (in MBs) for PID 946492 (qemu-kvm) + Node 0 Total + --------------- --------------- +Huge 2048.00 2048.00 +Heap 2698.13 2698.13 +Stack 0.71 0.71 +Private 781.48 781.48 +---------------- --------------- --------------- +Total 5528.32 5528.32 + +after a while + +Per-node process memory usage (in MBs) for PID 1059068 (qemu-kvm) + Node 0 Total + --------------- --------------- +Huge 2048.00 2048.00 +Heap 21769.94 21769.94 +Stack 0.71 0.71 +Private 827.22 827.22 +---------------- --------------- --------------- +Total 24645.87 24645.87 +``` +Additional information: +libvirt xml: +[file.xml](/uploads/82ff2e410183f94fde7cbaf19e7911dc/file.xml) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2238 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2238 new file mode 100644 index 000000000..8f73f13a5 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2238 @@ -0,0 +1,47 @@ +The `rw` parameter of `qemu_plugin_register_vcpu_mem_cb()` is not properly honored +Description of problem: +The `rw` parameter of `qemu_plugin_register_vcpu_mem_cb()` is not properly honored. +Steps to reproduce: +1. Register a callback with `qemu_plugin_register_vcpu_mem_cb()` +2. In the callback, print the return of `qemu_plugin_mem_is_store()` (either `true` or `false`) +3. Change the value of `rw` parameter of `qemu_plugin_register_vcpu_mem_cb()` and look whether the callback prints `true` and/or `false` to determine if this is inline with `rw`. + +In the callback, we don't we get what we asked for. + +| Requested with rw | Observed in the callback | +|---------------------|----------------------------| +| QEMU_PLUGIN_MEM_R | Only writes | +| QEMU_PLUGIN_MEM_W | Both reads and writes | +| QEMU_PLUGIN_MEM_RW | Both reads and writes | +Additional information: +In `plugin-gen.c`, line 497, there is the following function: + +```cpp +static bool op_rw(const TCGOp *op, const struct qemu_plugin_dyn_cb *cb) +{ + int w; + + w = op->args[2]; + return !!(cb->rw & (w + 1)); +} +``` + +The issue described above seems to be caused by the `+ 1`. I removed it and got the expected results. + +This function is used in the same file, line 526, like this: + +```cpp + if (!ok(begin_op, cb)) { + continue; + } +``` + +This isn't consistent with `core.c`, line 509, where the same flag is checked like this: + +```cpp + if (!(rw & cb->rw)) { + break; + } +``` + +Inconsistent because of the `+1` and also because of `break`/`continue`. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2239 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2239 new file mode 100644 index 000000000..3b25b973a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2239 @@ -0,0 +1 @@ +Legacy system requirments: iptables diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2240 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2240 new file mode 100644 index 000000000..cbdf02980 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2240 @@ -0,0 +1,4 @@ +Please provide useful defaults for machine and cpu +Additional information: +See https://bugs.debian.org/1040212 and https://salsa.debian.org/helmutg/debvm/-/issues/15 for the preceding discussion and +https://salsa.debian.org/helmutg/debvm/-/blob/main/bin/debvm-run and https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/80 for the used machine and cpu values. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2241 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2241 new file mode 100644 index 000000000..2aec892b1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2241 @@ -0,0 +1 @@ +QMP Commands dont't work properly diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2242 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2242 new file mode 100644 index 000000000..4d881d4bf --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2242 @@ -0,0 +1,14 @@ +Hugepages are not released after windows guest shutdown +Description of problem: +* Hugepages are not released after windows guest shutdown (tested with server 2019 and 2022), everything is ok with linux guests +* Issue is present in both cases: shutdown is initiated by guest, and with the qemu monitor command ``system_shutdown`` +* If the guest is configured with 4G as memory size, hugepages not released may vary but in most cases, only 1G are not released +* Host is a x86_64 linux system, with 1G hugepages only : kernel cmline contains ``default_hugepagesz=1G hugepagesz=1G hugepages=88`` +* I've done many tests with qemu components disabled (network, monitor, vnc), issue is still present with basic command line (launched as root) ``qemu-system-x86_64 -cpu host -enable-kvm -smp 4 -machine type=q35,accel=kvm -m 4G -mem-path /mnt/hugepages -drive id=drv0,file=win.qcow2 -nodefaults`` +* Same issue with args in command line, with or without prealloc: + + -m 4G -mem-path /mnt/hugepages [-mem-prealloc] + -m 4G -machine memory-backend=mem0 -object memory-backend-memfd,id=mem0,size=4G,hugetlb=on,hugetlbsize=1G[,prealloc=on] +Additional information: +* Hugepages release process is audited with command ``cat /proc/meminfo`` +* I can't find any online documentation to help to troubleshoot used hugepages : articles suggest to audit /proc/[pid]/smaps, but here, issue is raised after qemu process terminates diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2243 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2243 new file mode 100644 index 000000000..faf8f6668 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2243 @@ -0,0 +1,9 @@ +ES1370 sound card can crash the Windows 2000 and Windows XP guest. +Description of problem: +If using ES1370 sound card with Windows 2000 and Windows XP guest, it will crash the Windows 2000 and Windows XP guest. Windows 2000 and Windows XP have built in ES1370 driver. +Steps to reproduce: +1. +2. +3. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2247 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2247 new file mode 100644 index 000000000..89a101125 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2247 @@ -0,0 +1,6 @@ +virsh qemu-monitor-command --hmp help information missing inject-nmi for watchdog_action +Description of problem: +watchdog_action missing inject-nmi which already supported in Commit [795dc6e4](https://gitlab.com/qemu-project/qemu/-/commit/795dc6e46d953d70b4b7ddd3f4956f8f4b9d8565) +Steps to reproduce: +1. virsh qemu-monitor-command <id> --hmp help |grep watchdog +2. change watchdog action to inject-nmi diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/225 b/gitlab/issues_text/target_missing/host_missing/accel_missing/225 new file mode 100644 index 000000000..975126373 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/225 @@ -0,0 +1 @@ +Menu is not clickable on OSX Catalina diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2251 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2251 new file mode 100644 index 000000000..637b501a5 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2251 @@ -0,0 +1,14 @@ +Windows 11 VM with VBS enabled crashes +Description of problem: + +Steps to reproduce: +1. Run a Windows 11 VM on a node (both VM domain XML and node capabilities XML is provided below). +2. Enable VBS on the guest. For doing so you can use https://github.com/MicrosoftDocs/windows-itpro-docs/files/4020040/DG_Readinessv3.7.zip. Then, in Windows terminal, run DG_Readiness_Tool_{version}.ps1 -Enable. +3. Reboot the guest. +4. Windows cannot start (see picture below). +Additional information: +- Domain Capabilities: https://pastebin.com/GdQGQ639 +- VMX capabilities: https://pastebin.com/5nbUH0ev +- contents of /proc/cpuinfo: https://pastebin.com/xZM4x89z +- Domain XML: https://pastebin.com/s4VehTXK +- Windows crash at boot: https://ibb.co/Ny1xRbz diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2252 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2252 new file mode 100644 index 000000000..b74b57a40 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2252 @@ -0,0 +1,11 @@ +Poor VGA graphics when passing through a graphics card to a BIOS guest using the x-vga flag +Description of problem: +When passing through a GPU (in my case an Nvidia RTX 2070 Super) to a guest with BIOS firmware (using the x-vga flag to get a display out in BIOS mode), the VGA graphics used before an operating system loads proper graphics drivers seems to perform very poorly. Some symptoms of this are: GRUB and Windows Boot Manager are invisible, only showing a black screen (not sure if it affects all bootloaders) Windows 7 falls back to the more basic Vista boot animation during startup instead of the proper Starting Windows + orbs animation Windows 7 while using VGA graphics looks very low quality, with a pixelated look and a low color depth (attached below in additional information) Windows 10's setup just shows a black screen and fails to even boot. It seems to just restart after a bit (with any potential errors being invisible) Once graphics drivers are loaded inside Windows 7 or Linux in the guest, everything works fine. Seems like it's a firmware bug maybe? + +I've tested, and QEMU version 8.1 seems to be the last version without this bug, as 8.2 and up all have this issue. I'm not sure if this affects all graphics cards, as I've only tested this on an RTX 2070 super. +Steps to reproduce: +1. Create a guest with SeaBIOS firmware +2. Pass through a graphics card using -vfio-pci +3. Enable the x-vga flag +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2253 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2253 new file mode 100644 index 000000000..c805f792a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2253 @@ -0,0 +1 @@ +NO_CAST.INTEGER_OVERFLOW in /hw/net/eepro100.c diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2254 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2254 new file mode 100644 index 000000000..549b9b12e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2254 @@ -0,0 +1 @@ +UNCHECKED_FUNC_RES.LIB.STRICT in /io/channel-socket.c diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2255 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2255 new file mode 100644 index 000000000..ed74da6e0 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2255 @@ -0,0 +1 @@ +INVARIANT_RESULT in /qapi/opts-visitor.c diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2256 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2256 new file mode 100644 index 000000000..515061c9a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2256 @@ -0,0 +1 @@ +cirrus CI jobs failing diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2257 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2257 new file mode 100644 index 000000000..9fb7e6f7e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2257 @@ -0,0 +1 @@ +STRING_OVERFLOW in /qapi/opts-visitor.c diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/226 b/gitlab/issues_text/target_missing/host_missing/accel_missing/226 new file mode 100644 index 000000000..d48aa42c3 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/226 @@ -0,0 +1 @@ +host window size does not change when guest video screen size changes while moving host window diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2260 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2260 new file mode 100644 index 000000000..a4a8ccee0 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2260 @@ -0,0 +1,25 @@ +Storage device missing/Not recognized by driver (regression) +Description of problem: +Installation CD boots but can not find any storage/harddrive to install to. +This works in qemu 8.2.2, so it seems like a regression. +Steps to reproduce: +1. +2. +3. +Get virtio iso from https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/latest-virtio/ + +Install swtpm like: brew install swtpm + +Use CrystalFetch from https://docs.getutm.app/guides/windows/ to download Windows ISO. + +Create storage: qemu-img create -f qcow2 Win11.qcow2 80G + +dd if=/dev/zero of=vars-pflash.raw bs=1M count=64 + +start tpm like: /opt/homebrew/bin/swtpm socket --tpm2 --tpmstate dir=/Users/jonas/qw11arm/mytpm --ctrl type=unixio,path=/Users/jonas/qw11arm/mytpm/swtpm-sock + +start qemu like: \~/qemu/qemu/build/qemu-system-aarch64 --machine virt,virtualization=on --cpu neoverse-n1 --monitor stdio -smp cpus=4,sockets=1,cores=4,threads=1 -m 5G -device nec-usb-xhci -device qemu-xhci -device usb-kbd -device usb-tablet -device usb-storage,drive=windows,serial=windows -drive if=none,id=windows,format=raw,media=cdrom,file=/Users/jonas/ISOs/22631.2861.231204-0538.23H2_NI_RELEASE_SVC_REFRESH_CLIENTCONSUMER_RET_A64FRE_en-us.iso,readonly=on -device virtio-scsi -device scsi-hd,drive=boot,serial=boot -drive if=none,id=boot,format=qcow2,file=./Win11.qcow2 -drive if=pflash,format=raw,unit=0,file=/Users/jonas/qemu/qemu/build/pc-bios/edk2-aarch64-code.fd,readonly=on -drive file=vars-pflash.raw,format=raw,if=pflash,unit=1 -chardev socket,id=chrtpm,path=/Users/jonas/qw11arm/mytpm/swtpm-sock -tpmdev emulator,id=tpm0,chardev=chrtpm -device tpm-tis-device,tpmdev=tpm0 --display cocoa -rtc base=localtime -device ramfb -boot menu=on -device usb-storage,drive=virtio,serial=virtio -drive if=none,id=virtio,format=raw,media=cdrom,file=/Users/jonas/Downloads/virtio-win-0.1.240.iso,readonly=on -nic user,model=virtio-net-pci,mac=52:54:98:76:54:32 + +Adjust paths and be ready to bypass windows checks as described on https://docs.getutm.app/guides/windows/#this-pc-cant-run-windows-11 +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2261 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2261 new file mode 100644 index 000000000..51ca737b8 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2261 @@ -0,0 +1,87 @@ +qemu-system-x86_64 crashs in cursor_put functions +Description of problem: +This problem cannot be stably reproduced，but we try enable --enable-sanitizers and catch the following information，why qemu_spice_cursor_refresh_bh be called twice at the same time？ + +==57296==ERROR: AddressSanitizer: heap-use-after-free on address 0x623000738110 at pc 0x55cec2ed06aa bp 0x7ffc54d1fea0 sp 0x7ffc54d1fe90 +READ of size 4 at 0x623000738110 thread T0 + #0 0x55cec2ed06a9 in cursor_put ../qemu-6.0.1/ui/cursor.c:112 + #1 0x55cec2f05d40 in vnc_dpy_cursor_define ../qemu-6.0.1/ui/vnc.c:1041 + #2 0x55cec2ec6352 in dpy_cursor_define ../qemu-6.0.1/ui/console.c:1841 + #3 0x55cec3ab176c in qemu_spice_cursor_refresh_bh ../qemu-6.0.1/ui/spice-display.c:469 + #4 0x55cec4abc6eb in aio_bh_call ../qemu-6.0.1/util/async.c:136 + #5 0x55cec4abce43 in aio_bh_poll ../qemu-6.0.1/util/async.c:164 + #6 0x55cec4a5f457 in aio_dispatch ../qemu-6.0.1/util/aio-posix.c:381 + #7 0x55cec4abe386 in aio_ctx_dispatch ../qemu-6.0.1/util/async.c:306 + #8 0x7fa4fadcdd3a in g_main_context_dispatch (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x55d3a) + #9 0x55cec4b0b5d6 in glib_pollfds_poll ../qemu-6.0.1/util/main-loop.c:231 + #10 0x55cec4b0b7c0 in os_host_main_loop_wait ../qemu-6.0.1/util/main-loop.c:254 + #11 0x55cec4b0bac5 in main_loop_wait ../qemu-6.0.1/util/main-loop.c:530 + #12 0x55cec3f49e70 in qemu_main_loop ../qemu-6.0.1/softmmu/runstate.c:786 + #13 0x55cec2e7f679 in main ../qemu-6.0.1/softmmu/main.c:50 + #14 0x7fa4f96f4d8f in __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:58 + #15 0x7fa4f96f4e3f in __libc_start_main_impl ../csu/libc-start.c:392 + #16 0x55cec2e7f584 in _start (/usr/bin/qemu-system-x86_64+0x298a584) + +0x623000738110 is located 16 bytes inside of 6416-byte region [0x623000738100,0x623000739a10) +freed by thread T0 here: + #0 0x7fa4fb7d9537 in __interceptor_free ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:127 + #1 0x55cec2ed0769 in cursor_put ../qemu-6.0.1/ui/cursor.c:115 + #2 0x55cec3ab1818 in qemu_spice_cursor_refresh_bh ../qemu-6.0.1/ui/spice-display.c:471 + #3 0x55cec4abc6eb in aio_bh_call ../qemu-6.0.1/util/async.c:136 + #4 0x55cec4abce43 in aio_bh_poll ../qemu-6.0.1/util/async.c:164 + #5 0x55cec4a5f457 in aio_dispatch ../qemu-6.0.1/util/aio-posix.c:381 + #6 0x55cec4abe386 in aio_ctx_dispatch ../qemu-6.0.1/util/async.c:306 + #7 0x7fa4fadcdd3a in g_main_context_dispatch (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x55d3a) + +previously allocated by thread T14 here: + #0 0x7fa4fb7d9a57 in __interceptor_calloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:154 + #1 0x7fa4fadd6c50 in g_malloc0 (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x5ec50) + #2 0x55cec3b16918 in qxl_cursor ../qemu-6.0.1/hw/display/qxl-render.c:361 + #3 0x55cec3b18698 in qxl_render_cursor ../qemu-6.0.1/hw/display/qxl-render.c:448 + #4 0x55cec3af53a5 in interface_get_cursor_command ../qemu-6.0.1/hw/display/qxl.c:856 + #5 0x7fa4fb39ca1f in red_process_cursor ../../server/red-worker.c:152 + #6 0x7fa4fb39ca1f in red_process_cursor ../../server/red-worker.c:140 + +Thread T14 created by T0 here: + #0 0x7fa4fb77d685 in __interceptor_pthread_create ../../../../src/libsanitizer/asan/asan_interceptors.cpp:216 + #1 0x7fa4fb39ece5 in red_worker_run ../../server/red-worker.c:1588 + #2 0x62100002d94f (<unknown module>) + +SUMMARY: AddressSanitizer: heap-use-after-free ../qemu-6.0.1/ui/cursor.c:112 in cursor_put +Shadow bytes around the buggy address: + 0x0c46800defd0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa + 0x0c46800defe0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa + 0x0c46800deff0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa + 0x0c46800df000: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa + 0x0c46800df010: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa +=>0x0c46800df020: fd fd[fd]fd fd fd fd fd fd fd fd fd fd fd fd fd + 0x0c46800df030: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd + 0x0c46800df040: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd + 0x0c46800df050: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd + 0x0c46800df060: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd + 0x0c46800df070: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd +Shadow byte legend (one shadow byte represents 8 application bytes): + Addressable: 00 + Partially addressable: 01 02 03 04 05 06 07 + Heap left redzone: fa + Freed heap region: fd + Stack left redzone: f1 + Stack mid redzone: f2 + Stack right redzone: f3 + Stack after return: f5 + Stack use after scope: f8 + Global redzone: f9 + Global init order: f6 + Poisoned by user: f7 + Container overflow: fc + Array cookie: ac + Intra object redzone: bb + ASan internal: fe + Left alloca redzone: ca + Right alloca redzone: cb + Shadow gap: cc +==57296==ABORTING +Steps to reproduce: +This problem cannot be stably reproduced +Additional information: +/label ~"kind::Bug" diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2264 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2264 new file mode 100644 index 000000000..18a274628 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2264 @@ -0,0 +1,57 @@ +tests fail in staging-7.2 after "fix direction of "32-bit MMU" patch +Description of problem: +Running the tests with current staging-7.2 sources after compiling, it results in failing some tests after introduction of the following patches: + +- [target/i386: introduce function to query MMU indices](https://gitlab.com/qemu-project/qemu/-/commit/6332f3c12f7fc6c01fae1eaa59d661fef280f499) + +- [target/i386: use separate MMU indexes for 32-bit accesses](https://gitlab.com/qemu-project/qemu/-/commit/6b9875b03c81351c5f0268f571e011cf5f2fd9d2) + +- [target/i386: fix direction of "32-bit MMU" test](https://gitlab.com/qemu-project/qemu/-/commit/64e5fffe523daee23b06f3fd0f31721b137901b5) + +- [target/i386: Revert monitor_puts() in do_inject_x86_mce()](https://gitlab.com/qemu-project/qemu/-/commit/1d024cdc49a9ebc4d51142d2c33668bba1d31c89) + +in particular is the fix: + +- [target/i386: fix direction of "32-bit MMU" test](https://gitlab.com/qemu-project/qemu/-/commit/64e5fffe523daee23b06f3fd0f31721b137901b5) + +that causes the tests failing (removing such fix, tests passes). The failing tests are: + +``` +Summary of Failures: + + 92/689 qemu:qtest+qtest-i386 / qtest-i386/boot-serial-test ERROR 0.10s killed by signal 6 SIGABRT +127/689 qemu:qtest+qtest-x86_64 / qtest-x86_64/boot-serial-test ERROR 0.12s killed by signal 6 SIGABRT + 48/689 qemu:qtest+qtest-i386 / qtest-i386/bios-tables-test ERROR 40.95s killed by signal 6 SIGABRT + 71/689 qemu:qtest+qtest-x86_64 / qtest-x86_64/bios-tables-test ERROR 40.45s killed by signal 6 SIGABRT +``` + +In particular we have: + +``` + 92/689 qemu:qtest+qtest-i386 / qtest-i386/boot-serial-test ERROR 0.10s killed by signal 6 SIGABRT +――――――――――――――――――――――――――――――――――――― ✀ ――――――――――――――――――――――――――――――――――――― +stderr: +Broken pipe +../tests/qtest/libqtest.c:188: kill_qemu() detected QEMU death from signal 11 (Segmentation fault) (core dumped) + +(test program exited with status code -6) +―――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――― +``` + +and + + +``` +127/689 qemu:qtest+qtest-x86_64 / qtest-x86_64/boot-serial-test ERROR 0.12s killed by signal 6 SIGABRT +――――――――――――――――――――――――――――――――――――― ✀ ――――――――――――――――――――――――――――――――――――― +stderr: +Broken pipe +../tests/qtest/libqtest.c:188: kill_qemu() detected QEMU death from signal 11 (Segmentation fault) (core dumped) + +(test program exited with status code -6) + +TAP parsing error: Too few tests run (expected 2, got 0) +―――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――― +``` + +and so on. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2265 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2265 new file mode 100644 index 000000000..c70544c1b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2265 @@ -0,0 +1,48 @@ +qemu-system-x86_64 crash creating snapshot +Description of problem: +I'm facing a crash in qemu-system-x86_64.\ +I crash because bs->children.lh_first is null and QLIST_NEXT try dereference the pointer. It triggers a SIGSEGV\ +The manner to reproduce is too complex to give on gitlab and the version is not recent. (I reproduce also with 7.1)\ + +here is the stack: + +(gdb) p bs->children\ +$1 = {lh_first = 0x0}\ +(gdb)\ +(gdb) p child\ +$2 = (BdrvChild *) 0x0\ +(gdb)\ + if (bs->implicit) {\ + /* For implicit nodes, just copy everything from the single child */\ + child = QLIST_FIRST(&bs->children);\ +----->> assert(QLIST_NEXT(child, next) == NULL);\ + pstrcpy(bs->exact_filename, sizeof(bs->exact_filename),\ + + +#0 bdrv_refresh_filename (bs=0x562927927000) at ../qemu-6.2.0/block.c:7525\ +#1 0x000056292527dd97 in bdrv_block_device_info (blk=blk@entry=0x0, bs=bs@entry=0x562927927000, flat=flat@entry=true, errp=errp@entry=0x7ffcef7e8318) at ../qemu-6.2.0/block/qapi.c:58\ +#2 0x00005629252470c0 in bdrv_named_nodes_list (flat=true, errp=errp@entry=0x7ffcef7e8318) at ../qemu-6.2.0/block.c:5863\ +#3 0x000056292523da7e in qmp_query_named_block_nodes (has_flat=<optimized out>, flat=<optimized out>, errp=errp@entry=0x7ffcef7e8318) at ../qemu-6.2.0/blockdev.c:2935\ +#4 0x0000562925301ebd in qmp_marshal_query_named_block_nodes (args=<optimized out>, ret=0x7fc833c83e88, errp=0x7fc833c83e80) at qapi/qapi-commands-block-core.c:423\ +#5 0x0000562925344129 in do_qmp_dispatch_bh (opaque=0x7fc833c83e90) at ../qemu-6.2.0/qapi/qmp-dispatch.c:129 +#6 0x000056292535ecf5 in aio_bh_call (bh=0x5629295ab560) at ../qemu-6.2.0/util/async.c:141\ +#7 aio_bh_poll (ctx=ctx@entry=0x5629276c93e0) at ../qemu-6.2.0/util/async.c:169\ +#8 0x000056292534cf9e in aio_dispatch (ctx=0x5629276c93e0) at ../qemu-6.2.0/util/aio-posix.c:381\ +#9 0x000056292535eb9e in aio_ctx_dispatch (source=<optimized out>, callback=<optimized out>, user_data=<optimized out>) at ../qemu-6.2.0/util/async.c:311\ +#10 0x00007fc8351cafee in g_match_info_fetch_pos () from /lib/x86_64-linux-gnu/libglib-2.0.so.0\ +#11 0x00007fc800000000 in ?? ()\ +#12 0x000003a05cb8b408 in ?? ()\ +#13 0x0000000000000000 in ?? ()\ + +The case lh_first = 0x0 seems to be common, but never when bs->implicit is true. bs->implicit seems to be switch to true by another thread.\ +Because the qemu version and the system are too old, I'm not expecting a patch, I'm just requesting an opinion.\ + +I fixed the problem by just doing:\ +child = QLIST_FIRST(&bs->children);\ +if (bs->implicit && (child != NULL)) {\ + assert(QLIST_NEXT(child, next) == NULL);\ + ....\ +}\ +I don't have the qemu knowledge to evaluate it and consequences.\ +Is there anyone who have any idea ?\ +Thank you very much.\ diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2267 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2267 new file mode 100644 index 000000000..cb5522739 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2267 @@ -0,0 +1,552 @@ +Out of bounds access in tx_fifo_push() +Description of problem: +I detected an out-of-bounds access in tx_fifo_push with my fuzzer. + +Stack trace (part):\ +`hw/net/lan9118.c:798:17: runtime error: index 2048 out of bounds for`\ +`type 'uint8_t[2048]' (aka 'unsigned char[2048]')`\ + `#0 0x563ec9a057b1 in tx_fifo_push hw/net/lan9118.c:798:43`\ + `#1 0x563ec99fbb28 in lan9118_writel hw/net/lan9118.c:1042:9`\ + `#2 0x563ec99f2de2 in lan9118_16bit_mode_write hw/net/lan9118.c:1205:9`\ + `#3 0x563ecbf78013 in memory_region_write_accessor system/memory.c:497:5`\ + `#4 0x563ecbf776f5 in access_with_adjusted_size system/memory.c:573:18`\ + `#5 0x563ecbf75643 in memory_region_dispatch_write system/memory.c:1521:16`\ + `#6 0x563ecc01bade in flatview_write_continue_step system/physmem.c:2713:18`\ + `#7 0x563ecc01b374 in flatview_write_continue system/physmem.c:2743:19`\ + `#8 0x563ecbff1c9b in flatview_write system/physmem.c:2774:12`\ + `#9 0x563ecbff1768 in address_space_write system/physmem.c:2894:18`\ +`...` +Steps to reproduce: +Reproducer:\ +export QEMU_ARGS="-display none -machine accel=qtest, -m 512M -machine smdkc210"\ +cat \<\< EOF | ./qemu-system-arm $QEMU_ARGS -qtest /dev/null -qtest stdio\ +outl 0xcf8 0x80000010\ +outl 0xcfc 0x5000000\ +outl 0xcf8 0x80000004\ +outl 0xcfc 0x07\ +writew 0x5000030 0x4918237b\ +writew 0x5000030 0x4918237b\ +writel 0x500003c 0x223bd37f\ +writel 0x500003c 0x223bd37f\ +writel 0x500003c 0x223bd37f\ +writew 0x500003c 0x223bd37f\ +writel 0x500003c 0x223bd37f\ +writew 0x500003c 0x223bd37f\ +writel 0x500003c 0x223bd37f\ +writel 0x500003c 0x223bd37f\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0xcb06897\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x17954990\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x17954990\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0xcb06897\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x17954990\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0xcb06897\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000024 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x17954990\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0xcb06897\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000024 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x17954990\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000024 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0xcb06897\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0xcb06897\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x17954990\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0xcb06897\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x17954990\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x17954990\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0xcb06897\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x17954990\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0xcb06897\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0xcb06897\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x17954990\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0xcb06897\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x17954990\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0xcb06897\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x17954990\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0xcb06897\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x17954990\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0xcb06897\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x17954990\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x17954990\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0xcb06897\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +writel 0x5000020 0x6a035c1b\ +EOF +Additional information: +Ack: Chuhong Yuan (hslester96@gmail.com) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2268 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2268 new file mode 100644 index 000000000..55e66a0d6 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2268 @@ -0,0 +1,43 @@ +Out of bounds access in smc91c111_readb() +Description of problem: +I detected an out-of-bounds access in smc91c111_readb with my fuzzer. + +Stack trace (part):\ +`hw/net/smc91c111.c:607:24: runtime error: index 175 out of bounds for`\ +`type 'uint8_t[4][2048]' (aka 'unsigned char[4][2048]')`\ +`SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior`\ +`hw/net/smc91c111.c:607:24 in`\ +`AddressSanitizer:DEADLYSIGNAL`\ +`==============================`<wbr>`==============================`<wbr>`=====`\ +`==397944==ERROR: AddressSanitizer: SEGV on unknown address`\ +`0x629000077db4 (pc 0x56272aed3b8d bp 0x7ffd1471f290 sp 0x7ffd1471ea20`\ +`T0)`\ +`==397944==The signal is caused by a READ memory access.`\ + `#0 0x56272aed3b8d in smc91c111_readb hw/net/smc91c111.c:607:24`\ + `#1 0x56272aecfd61 in smc91c111_readfn hw/net/smc91c111.c:650:16`\ + `#2 0x56272d4b228b in memory_region_read_accessor system/memory.c:445:11`\ + `#3 0x56272d46fb85 in access_with_adjusted_size system/memory.c:573:18`\ + `#4 0x56272d46c58e in memory_region_dispatch_read1 system/memory.c:1426:16`\ + `#5 0x56272d46bcd7 in memory_region_dispatch_read system/memory.c:1459:9`\ + `#6 0x56272d4e8e03 in flatview_read_continue_step system/physmem.c:2794:18`\ + `#7 0x56272d4e871e in flatview_read_continue system/physmem.c:2835:19`\ + `#8 0x56272d4e98b8 in flatview_read system/physmem.c:2865:12`\ + `#9 0x56272d4e9388 in address_space_read_full system/physmem.c:2878:18`\ + `#10 0x56272d6e7840 in address_space_read include/exec/memory.h:3026:18`\ +`...`\ +Bug analysis: I found s-\>packet_num = 175 at line 599. +Steps to reproduce: +Reproducer:\ +export QEMU_ARGS="-display none -machine accel=qtest, -m 512M -machine\ +mainstone"\ +cat \<\< EOF | ./qemu-system-arm $QEMU_ARGS -qtest /dev/null -qtest stdio\ +outl 0xcf8 0x80000010\ +outl 0xcfc 0x10000300\ +outl 0xcf8 0x80000004\ +outl 0xcfc 0x07\ +writel 0x1000030c 0x66027cd6\ +writel 0x10000300 0x64af8eda\ +readw 0x10000308\ +EOF +Additional information: +Ack: Chuhong Yuan (hslester96@gmail.com) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/227 b/gitlab/issues_text/target_missing/host_missing/accel_missing/227 new file mode 100644 index 000000000..aa5975a9f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/227 @@ -0,0 +1 @@ +meson: incomplete 'make help' diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2272 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2272 new file mode 100644 index 000000000..1a36f787c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2272 @@ -0,0 +1,21 @@ +Memory leak in the virtual device applesmc +Description of problem: +In the function _qdev_applesmc_isa_reset_, the device mallocs the _AppleSMCData_ but does not free them, causing a memory leak. + +The following log reveals it: + +``` +==1029295==ERROR: LeakSanitizer: detected memory leaksDirect leak of 80 byte(s) in 2 object(s) allocated from: +#0 0x5574dc600a82 in __interceptor_calloc compiler-rt/lib/asan/asan_malloc_linux.cpp:138:3 +#1 0x7f4919b22c50 in g_malloc0 (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x5ec50) +#2 0x5574dcdb0dfe in qdev_applesmc_isa_reset qemu/hw/misc/applesmc.c:285:5 +#3 0x5574de30e099 in resettable_phase_hold qemu/hw/core/resettable.c +#4 0x5574de2ef753 in bus_reset_child_foreach qemu/hw/core/bus.c:97:13 +#5 0x5574de30dcfe in resettable_child_foreach qemu/hw/core/resettable.c:96:9 +#6 0x5574de30dcfe in resettable_phase_hold qemu/hw/core/resettable.c:173:5 +#7 0x5574de3059b3 in device_reset_child_foreach qemu/hw/core/qdev.c:276:9 +``` +Steps to reproduce: +1. Build qemu with the sanitizer +2. Boot the Linux kernel with the above command line. +3. Stop the qemu process diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2273 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2273 new file mode 100644 index 000000000..f20eb0937 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2273 @@ -0,0 +1,45 @@ +Abort in net_tx_pkt_update_sctp_checksum() +Description of problem: +In the function _net_tx_pkt_update_sctp_checksum(),_ an abort happened: + +``` +qemu-fuzz-x86_64: ../../../third_party/qemu/util/iov.c:39: size_t iov_from_buf_full(const struct iovec *, unsigned int, size_t, const void *, size_t): Assertion `offset == 0' failed. +==1052929== ERROR: libFuzzer: deadly signal + #0 0x5575e5cccbe1 in __sanitizer_print_stack_trace llvm/compiler-rt/lib/asan/asan_stack.cpp:87:3 + #1 0x5575e5c479b8 in fuzzer::PrintStackTrace() llvm/compiler-rt/lib/fuzzer/FuzzerUtil.cpp:210:5 + #2 0x5575e5c2bbb3 in fuzzer::Fuzzer::CrashCallback() llvm/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:233:3 + #3 0x7f691f24251f (/lib/x86_64-linux-gnu/libc.so.6+0x4251f) + #4 0x7f691f2969fb in __pthread_kill_implementation nptl/./nptl/pthread_kill.c:43:17 + #5 0x7f691f2969fb in __pthread_kill_internal nptl/./nptl/pthread_kill.c:78:10 + #6 0x7f691f2969fb in pthread_kill nptl/./nptl/pthread_kill.c:89:10 + #7 0x7f691f242475 in gsignal signal/../sysdeps/posix/raise.c:26:13 + #8 0x7f691f2287f2 in abort stdlib/./stdlib/abort.c:79:7 + #9 0x7f691f22871a in __assert_fail_base assert/./assert/assert.c:92:3 + #10 0x7f691f239e95 in __assert_fail assert/./assert/assert.c:101:3 + #11 0x5575e81e952a in iov_from_buf_full qemu/util/iov.c:39:5 + #12 0x5575e6500768 in net_tx_pkt_update_sctp_checksum qemu/hw/net/net_tx_pkt.c:144:9 + #13 0x5575e659f3e1 in igb_setup_tx_offloads qemu/hw/net/igb_core.c:478:11 + #14 0x5575e659f3e1 in igb_tx_pkt_send qemu/hw/net/igb_core.c:552:10 + #15 0x5575e659f3e1 in igb_process_tx_desc qemu/hw/net/igb_core.c:671:17 + #16 0x5575e659f3e1 in igb_start_xmit qemu/hw/net/igb_core.c:903:9 + #17 0x5575e659f3e1 in igb_set_tdt qemu/hw/net/igb_core.c:2812:5 + #18 0x5575e657d6a4 in igb_core_write qemu/hw/net/igb_core.c:4248:9 +``` +Steps to reproduce: +Here's a simple PoC: + +``` +cat << EOF | \ +qemu-system-x86_64 \ +-display none -machine accel=qtest -m 512M -M q35 -nodefaults -device \ +igb,netdev=net0 -netdev user,id=net0 -qtest stdio +outl 0xcf8 0x80000810 +outl 0xcfc 0xe0000000 +outl 0xcf8 0x80000804 +outw 0xcfc 0x06 +write 0xe0000403 0x1 0x02 +writel 0xe0003808 0xffffffff +write 0xe000381a 0x1 0x5b +write 0xe000381b 0x1 0x00 +EOF +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2274 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2274 new file mode 100644 index 000000000..a80c587dd --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2274 @@ -0,0 +1,43 @@ +Assertion failuer in cryptodev_builtin_close_session() +Description of problem: +In the function _cryptodev_builtin_close_session(),_ an assertation happened: + +``` +qemu-fuzz-x86_64: qemu/backends/cryptodev-builtin.c:430: int cryptodev_builtin_close_session(CryptoDevBackend *, uint64_t, uint32_t, CryptoDevCompletionFunc, void *): Assertion `session_id < MAX_NUM_SESSIONS && builtin->sessions[session_id]' failed. +==1256139== ERROR: libFuzzer: deadly signal + #9 0x71acb8c2871a in __assert_fail_base assert/./assert/assert.c:92:3 + #10 0x71acb8c39e95 in __assert_fail assert/./assert/assert.c:101:3 + #11 0x5af7f624b12b in cryptodev_builtin_close_session qemu/backends/cryptodev-builtin.c:430:5 + #12 0x5af7f60b2860 in virtio_crypto_handle_close_session qemu/hw/virtio/virtio-crypto.c:262:12 + #13 0x5af7f60b2860 in virtio_crypto_handle_ctrl qemu/hw/virtio/virtio-crypto.c:423:19 +``` + +The user could send an invalid session_id to trigger this assertion. +Steps to reproduce: +Here's a simple PoC: + +``` +cat << EOF | qemu-system-x86_64 -display none\ + -machine accel=qtest -m 512M -machine q35 -nodefaults -object \ +cryptodev-backend-builtin,id=cryptodev0 -device \ +virtio-crypto-pci,id=crypto0,cryptodev=cryptodev0 -qtest stdio +outl 0xcf8 0x80000804 +outw 0xcfc 0x06 +outl 0xcf8 0x80000820 +outl 0xcfc 0xe0008000 +write 0x10800e 0x1 0x01 +write 0xe0008016 0x1 0x01 +write 0xe0008020 0x4 0x00801000 +write 0xe0008028 0x4 0x00c01000 +write 0xe000801c 0x1 0x01 +write 0x110000 0x1 0x05 +write 0x110001 0x1 0x04 +write 0x108002 0x1 0x11 +write 0x108008 0x1 0x48 +write 0x10800c 0x1 0x01 +write 0x108018 0x1 0x10 +write 0x10801c 0x1 0x02 +write 0x10c002 0x1 0x01 +write 0xe000b005 0x1 0x00 +EOF +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2275 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2275 new file mode 100644 index 000000000..183fcbf26 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2275 @@ -0,0 +1,9 @@ +qemu crash +Description of problem: + +Steps to reproduce: +1. +2. +3. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2276 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2276 new file mode 100644 index 000000000..ee5e9373f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2276 @@ -0,0 +1,42 @@ +qemu crash for suspend and resume vm while backup disk of vm +Description of problem: + +Steps to reproduce: +1. virsh create vm2.xml +2. virsh backup-begin domid +3. virsh suspend domid +4. sleep 1 && virsh resume domid + +qemu crash +Additional information: +static int blk_do_set_aio_context(BlockBackend *blk, AioContext *new_context, + bool update_root_node, Error **errp) +{ + BlockDriverState *bs = blk_bs(blk); + ThrottleGroupMember *tgm = &blk->public.throttle_group_member; + int ret; + + if (bs) { + bdrv_ref(bs); + + if (update_root_node) { + ret = bdrv_child_try_set_aio_context(bs, new_context, blk->root, + errp); + if (ret < 0) { + bdrv_unref(bs); + return ret; + } + } + if (tgm->throttle_state) { + _ ****bdrv_drained_begin(bs);----- bs->aio_context->lock lock count is 0,so unlock failed**_ + throttle_group_detach_aio_context(tgm); + throttle_group_attach_aio_context(tgm, new_context); + bdrv_drained_end(bs); + } + + bdrv_unref(bs); + } + + blk->ctx = new_context; + return 0; +} diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2277 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2277 new file mode 100644 index 000000000..faa78f8ad --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2277 @@ -0,0 +1 @@ +COarse-grained LOck-stepping Virtual Machines for Non-stop Service Encountered Assertion Error diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2278 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2278 new file mode 100644 index 000000000..92b2132dc --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2278 @@ -0,0 +1 @@ +Build issue on OpenBSD with Clang 16 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/228 b/gitlab/issues_text/target_missing/host_missing/accel_missing/228 new file mode 100644 index 000000000..a3f4cfb54 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/228 @@ -0,0 +1 @@ +TCG test targets missing from 'make check-help' diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2280 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2280 new file mode 100644 index 000000000..f221798db --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2280 @@ -0,0 +1 @@ +Not Installing Properly diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2282 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2282 new file mode 100644 index 000000000..dc8cebad7 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2282 @@ -0,0 +1 @@ +Corrupted output when using Intel Arc GPU with qemu+spice+virgl in headed mode diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2283 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2283 new file mode 100644 index 000000000..553a227df --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2283 @@ -0,0 +1,33 @@ +memory leak in virtio-crypto +Description of problem: +The following log reveals it: + +``` +==1878896==ERROR: LeakSanitizer: detected memory leaks + +Direct leak of 48 byte(s) in 1 object(s) allocated from: + #0 0x5646565ec262 in __interceptor_calloc llvm/compiler-rt/lib/asan/asan_malloc_linux.cpp:138:3 + #1 0x7f591ec3bc50 in g_malloc0 (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x5ec50) + #2 0x564659227db7 in error_setg_internal qemu/util/error.c:105:5 + #3 0x56465794ad35 in cryptodev_builtin_operation qemu/backends/cryptodev-builtin.c:557:9 + #4 0x5646579550b5 in cryptodev_backend_operation qemu/backends/cryptodev.c:180:16 + #5 0x564657953640 in cryptodev_backend_crypto_operation qemu/backends/cryptodev.c:289:12 + #6 0x56465773a647 in virtio_crypto_handle_request qemu/hw/virtio/virtio-crypto.c:911:19 + #7 0x5646577386a0 in virtio_crypto_handle_dataq qemu/hw/virtio/virtio-crypto.c:938:13 + #8 0x564657734f87 in virtio_crypto_dataq_bh qemu/hw/virtio/virtio-crypto.c:963:9 + #9 0x56465928a6b1 in aio_bh_call qemu/util/async.c:171:5 + #10 0x56465928b58c in aio_bh_poll qemu/util/async.c:218:13 + #11 0x5646591eb398 in aio_dispatch qemu/util/aio-posix.c:423:5 + #12 0x5646592919ce in aio_ctx_dispatch qemu/util/async.c:360:5 + #13 0x7f591ec32d3a in g_main_context_dispatch (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x55d3a) + +Indirect leak of 36 byte(s) in 1 object(s) allocated from: + #0 0x5646565ec0cd in malloc llvm/compiler-rt/lib/asan/asan_malloc_linux.cpp:129:3 + #1 0x7f591e488157 in __vasprintf_internal libio/./libio/vasprintf.c:71:30 +``` +Steps to reproduce: +``` +qemu-system-x86_64 -display none -machine accel=qtest -m 512M -machine q35 -nodefaults -object cryptodev-backend-builtin,id=cryptodev0 -device virtio-crypto-pci,id=crypto0,cryptodev=cryptodev0 -qtest stdio < /tmp/reproducer +``` + +[reproducer](/uploads/e0161b0d482bc5dac08929d51e70e7fc/reproducer) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2284 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2284 new file mode 100644 index 000000000..7a95df317 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2284 @@ -0,0 +1 @@ +sunxi avocado tests: kernel no longer available on armbian diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2288 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2288 new file mode 100644 index 000000000..961e0177f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2288 @@ -0,0 +1,29 @@ +ERROR: Unrecognized host OS (uname -s reports 'Linux') +Description of problem: +Hit "Unrecognized host OS (uname -s reports 'Linux')" ERROR when run configure file on upstream qemu. +Steps to reproduce: +1.Clone repo and compile it + + 1.1 git clone https://gitlab.com/qemu-project/qemu.git + + 1.2 cd qemu + + 1.3 mkdir build + + 1.4 cd build + + 1.5 ../configure --target-list=x86_64-softmmu --enable-debug + +2.The following ERROR message: + +ERROR: Unrecognized host OS (uname -s reports 'Linux') +Additional information: +Cpu information: + +Vendor ID: AuthenticAMD + + BIOS Vendor ID: Advanced Micro Devices, Inc. + + Model name: AMD EPYC 9754 128-Core Processor + + BIOS Model name: AMD EPYC 9754 128-Core Processor diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2289 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2289 new file mode 100644 index 000000000..1a2f62003 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2289 @@ -0,0 +1 @@ +virtio-blk not work in freebsd guest with qemu>=7.0.0 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/229 b/gitlab/issues_text/target_missing/host_missing/accel_missing/229 new file mode 100644 index 000000000..7e9bee660 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/229 @@ -0,0 +1 @@ +build-tools-and-docs-debian job waste cycles building pointless things diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2291 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2291 new file mode 100644 index 000000000..cc6b0d724 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2291 @@ -0,0 +1,182 @@ +building qemu with msys2 mingw64 in github actions, sed error unterminated address regex +Description of problem: +in Github Actions (Windows) +``` +$ make --trace -j $(nproc) +ninja: no work to do. +/d/a/qemu_app/qemu_app/qemu/BUILD/pyvenv/bin/meson introspect --targets --tests --benchmarks | D:/a/qemu_app/qemu_app/qemu/BUILD/pyvenv/bin/python3.exe -B scripts/mtest2make.py > Makefile.mtest +D:\a\_temp\msys64\mingw64\bin\sed.exe: -e expression #1, char 41: unterminated address regex +D:\a\_temp\msys64\mingw64\bin\sed.exe: -e expression #1, char 41: unterminated address regex +``` +Steps to reproduce: +```sh +# enable symlinks in msys2 MINGW64 shell + +export MSYS=winsymlinks:native + +# download and extract qemu + +curl -L https://download.qemu.org/qemu-9.0.0-rc4.tar.xz -O +tar xvJf qemu-9.0.0-rc4.tar.xz +mv qemu-9.0.0-rc4 qemu + +# remove symlinks known to cause `git add` to fail, we will recreate these later in the yaml file + +/usr/bin/rm -f qemu/roms/edk2/EmulatorPkg/Unix/Host/X11IncludeHack +/usr/bin/rm -f qemu/roms/skiboot/opal-ci/build-debian-unstable.sh +/usr/bin/rm -f qemu/roms/skiboot/opal-ci/build-fedora-rawhide.sh +/usr/bin/rm -f qemu/roms/u-boot/board/xilinx/zynq/zynq-cse-nand +/usr/bin/rm -f qemu/roms/u-boot/board/xilinx/zynqmp/avnet-ultra96-rev1 +/usr/bin/rm -f qemu/roms/u-boot/board/xilinx/zynqmp/zynqmp-g-a2197-00-revA +/usr/bin/rm -f qemu/roms/u-boot/board/xilinx/zynqmp/zynqmp-m-a2197-01-revA +/usr/bin/rm -f qemu/roms/u-boot/board/xilinx/zynqmp/zynqmp-m-a2197-03-revA +/usr/bin/rm -f qemu/roms/u-boot/board/xilinx/zynqmp/zynqmp-mini +/usr/bin/rm -f qemu/roms/u-boot/board/xilinx/zynqmp/zynqmp-mini-emmc0 +/usr/bin/rm -f qemu/roms/u-boot/board/xilinx/zynqmp/zynqmp-mini-emmc1 +/usr/bin/rm -f qemu/roms/u-boot/board/xilinx/zynqmp/zynqmp-mini-qspi +/usr/bin/rm -f qemu/roms/u-boot/board/xilinx/zynqmp/zynqmp-p-a2197-00-revA +/usr/bin/rm -f qemu/roms/u-boot/board/xilinx/zynqmp/zynqmp-zcu104-revC +/usr/bin/rm -f qemu/roms/u-boot/include/ctype.h +/usr/bin/rm -f qemu/roms/u-boot/tools/binman/binman +/usr/bin/rm -f qemu/roms/u-boot/tools/dtoc/dtoc +/usr/bin/rm -f qemu/roms/u-boot/tools/microcode-tool +/usr/bin/rm -f qemu/roms/u-boot/tools/patman/patman +/usr/bin/rm -f qemu/tests/lcitool/libvirt-ci/ci/gitlab/all_mappings_prep_env/almalinux-8-prep.sh +/usr/bin/rm -f qemu/tests/lcitool/libvirt-ci/ci/gitlab/all_mappings_prep_env/alpine-317-prep.sh +/usr/bin/rm -f qemu/tests/lcitool/libvirt-ci/ci/gitlab/all_mappings_prep_env/alpine-edge-prep.sh +/usr/bin/rm -f qemu/tests/lcitool/libvirt-ci/ci/gitlab/all_mappings_prep_env/fedora-37-prep.sh +/usr/bin/rm -f qemu/tests/lcitool/libvirt-ci/ci/gitlab/all_mappings_prep_env/fedora-38-prep.sh +/usr/bin/rm -f qemu/tests/lcitool/libvirt-ci/ci/gitlab/all_mappings_prep_env/fedora-rawhide-prep.sh + +# push qemu to github to test + +git init +git add -Av +git commit -m "qemu fail" +git branch -M main + +git remote add origin < a url to a newly created git repo to test the qemu build which currently fails with sed error > + +git push origin +``` +```yaml + +# save this in the following file: .github/workflows/windows.yaml + +# Job execution time - Each job in a workflow can run for up to 6 hours of execution time. +# Workflow run time - Each workflow run is limited to 35 days + +name: windows + +on: + push: + branches: [ "main" ] + workflow_dispatch: + +defaults: + run: + shell: msys2 {0} + +# each job runs under a NEW image +jobs: + build_qemu: + strategy: + matrix: + include: + - os: windows-latest + name: windows + sys: MINGW64 + + runs-on: ${{ matrix.os }} + + name: build qemu - ${{ matrix.name }} + + steps: + # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it + - uses: actions/checkout@v4 + with: + ref: ${{needs.should_run.outputs.output1}} + submodules: recursive + + - name: '${{ matrix.icon }} Setup MSYS2' + uses: msys2/setup-msys2@v2 + with: + msystem: ${{matrix.sys}} + update: true + path-type: strict + + - name: update packages + run: | + pacman -Sy + + - name: install qemu deps + run: | + # https://github.com/qemu/qemu/blob/master/.gitlab-ci.d/windows.yml#L84 + pacman -S --noconfirm --needed pactoys + pacman -S --noconfirm --needed bison flex git + pacboy -S --noconfirm --needed make:p cmake:p gcc:p meson:p autotools:p ninja:p python:p python-sphinx:p python-sphinx_rtd_theme:p tools-git:p angleproject:p capstone:p curl:p cyrus-sasl:p dtc:p expat:p fontconfig:p freetype:p fribidi:p gcc-libs:p gdk-pixbuf2:p gettext:p glib2:p gmp:p gnutls:p graphite2:p gst-plugins-base:p gstreamer:p gtk3:p harfbuzz:p jbigkit:p lerc:p libc++:p libdatrie:p libdeflate:p libepoxy:p libffi:p libiconv:p libidn2:p libjpeg-turbo:p libnfs:p libpng:p libpsl:p libslirp:p libssh:p libssh2:p libtasn1:p libthai:p libtiff:p libunistring:p libunwind:p libusb:p libwebp:p libwinpthread-git:p lz4:p lzo2:p nettle:p openssl:p opus:p orc:p p11-kit:p pango:p pixman:p SDL2:p SDL2_image:p snappy:p spice:p usbredir:p xz:p zlib:p zstd:p brotli:p bzip2:p nghttp2 diffutils grep make sed:p binutils:p capstone:p curl:p cyrus-sasl:p dtc:p gcc:p glib2:p gnutls:p gtk3:p libgcrypt:p libjpeg-turbo:p libnfs:p libpng:p libssh:p libtasn1:p libusb:p lzo2:p nettle:p ninja:p pixman:p pkgconf:p python:p SDL2:p SDL2_image:p snappy:p spice:p usbredir:p zstd:p + + - name: restore symlinks + run: | + export MSYS=winsymlinks:native + ln -s /opt/X11/include qemu/roms/edk2/EmulatorPkg/Unix/Host/X11IncludeHack + ln -s build-ubuntu-latest.sh qemu/roms/skiboot/opal-ci/build-debian-unstable.sh + ln -s build-fedora33.sh qemu/roms/skiboot/opal-ci/build-fedora-rawhide.sh + ln -s zynq-zc770-xm011 qemu/roms/u-boot/board/xilinx/zynq/zynq-cse-nand + ln -s zynqmp-zcu100-revC qemu/roms/u-boot/board/xilinx/zynqmp/avnet-ultra96-rev1 + ln -s zynqmp-a2197-revA qemu/roms/u-boot/board/xilinx/zynqmp/zynqmp-g-a2197-00-revA + ln -s zynqmp-a2197-revA qemu/roms/u-boot/board/xilinx/zynqmp/zynqmp-m-a2197-01-revA + ln -s zynqmp-a2197-revA qemu/roms/u-boot/board/xilinx/zynqmp/zynqmp-m-a2197-03-revA + ln -s zynqmp-zcu102-rev1.0 qemu/roms/u-boot/board/xilinx/zynqmp/zynqmp-mini + ln -s zynqmp-zcu100-revC qemu/roms/u-boot/board/xilinx/zynqmp/zynqmp-mini-emmc0 + ln -s zynqmp-zcu102-rev1.0 qemu/roms/u-boot/board/xilinx/zynqmp/zynqmp-mini-emmc1 + ln -s zynqmp-zcu102-rev1.0 qemu/roms/u-boot/board/xilinx/zynqmp/zynqmp-mini-qspi + ln -s zynqmp-a2197-revA qemu/roms/u-boot/board/xilinx/zynqmp/zynqmp-p-a2197-00-revA + ln -s zynqmp-zcu104-revA qemu/roms/u-boot/board/xilinx/zynqmp/zynqmp-zcu104-revC + ln -s linux/ctype.h qemu/roms/u-boot/include/ctype.h + ln -s main.py qemu/roms/u-boot/tools/binman/binman + ln -s main.py qemu/roms/u-boot/tools/dtoc/dtoc + ln -s microcode-tool.py qemu/roms/u-boot/tools/microcode-tool + ln -s main.py qemu/roms/u-boot/tools/patman/patman + ln -s centos-stream-8-prep.sh qemu/tests/lcitool/libvirt-ci/ci/gitlab/all_mappings_prep_env/almalinux-8-prep.sh + ln -s alpine-prep.sh qemu/tests/lcitool/libvirt-ci/ci/gitlab/all_mappings_prep_env/alpine-317-prep.sh + ln -s alpine-prep.sh qemu/tests/lcitool/libvirt-ci/ci/gitlab/all_mappings_prep_env/alpine-edge-prep.sh + ln -s fedora-prep.sh qemu/tests/lcitool/libvirt-ci/ci/gitlab/all_mappings_prep_env/fedora-37-prep.sh + ln -s fedora-prep.sh qemu/tests/lcitool/libvirt-ci/ci/gitlab/all_mappings_prep_env/fedora-38-prep.sh + ln -s fedora-prep.sh qemu/tests/lcitool/libvirt-ci/ci/gitlab/all_mappings_prep_env/fedora-rawhide-prep.sh + + # we dont use split.exe since we need only fails the build and need not upload the results + + # there is no use in caching the build directory since ../configure will cause a full rebuild + # and we are lazy to detect an existing Makefile + + - name: cmake configure qemu - Release + run: | + export MSYS=winsymlinks:native + cd qemu + mkdir BUILD || true + mkdir BUILD/BUILD_ROOT || true + cd BUILD + ls -l + + # this should succeed + ../configure --prefix=$(pwd)/BUILD_ROOT --enable-sdl --enable-gtk --disable-user --target-list=x86_64-softmmu --enable-whpx + + - name: cmake build qemu - Release + run: | + export MSYS=winsymlinks:native + cd qemu/BUILD + ls -l + cat -n Makefile + + # this should fail with sed.exe: -e expression #1, char 41: unterminated address regex + make --trace -j $(nproc) +``` +Additional information: +https://github.com/mgood7123/qemu_app/actions/runs/8732163169/job/23958798258 + +note `make` `succeeds` (returns 0) but does not build anything due to sed error + +qemu folder is https://download.qemu.org/qemu-9.0.0-rc4.tar.xz + +symlinks incompatible with `git add` have been removed and then recreated in GHA diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2292 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2292 new file mode 100644 index 000000000..20c03a5b5 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2292 @@ -0,0 +1,19 @@ +UNIX socket path is too long +Description of problem: +At [Unikraft](https://unikraft.org) we facilitate the construction and also runtime lifecycle management of ultra-lightweight virtual machine unikernels. We have developed [`kraft`](https://github.com/unikraft/kraftkit), an open-source tool which facilitates this across a number of different virtual machine monitors, [including QEMU](https://github.com/unikraft/kraftkit/tree/staging/machine/qemu). + +We are receiving increased reports of the following error from our users: + +``` +could not start and wait for QEMU process: qemu-system-x86_64: -qmp unix:/Users/__USERNAME__/.local/share/kraftkit/runtime/37a7691a-d402-4760-b493-692bb8d0460a/qemu_control.sock,server,nowait: UNIX socket path '/Users/__USERNAME__/.local/share/kraftkit/runtime/37a7691a-d402-4760-b493-692bb8d0460a/qemu_control.sock' is too long +``` + +We systematically build the relevant QEMU process command line and arguments with flags [via our Go SDK](https://github.com/unikraft/kraftkit/blob/staging/machine/qemu/v1alpha1.go#L180-L229) and include what has become an erroneously long UNIX path for the QAPI control socket which we use to manage instantiated VM instances. + +This issue tracks the increasing of maximum path length for the `-qmp` (and maybe other) flags which accept paths. +Steps to reproduce: +1. Install [`kraft`](https://github.com/unikraft/kraftkit), [Unikraft](https://unikraft.org)'s companion command-line client; +2. Update KraftKit's config file to include an arbitrarily long path for `runtime_dir` by editing `~/.config/kraftkit/config.yaml`; +3. Start a QEMU unikernel instance with `kraft run --arch x86_64 --plat qemu unikraft.org/helloworld:latest` +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2293 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2293 new file mode 100644 index 000000000..fef8dbe01 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2293 @@ -0,0 +1,35 @@ +[u2f-passthru]: pamu2fcfg command will stuck forever in Guest OS of Qemu +Description of problem: +To use FIDO2 user verification we need to run `pamu2fcfg` command which will stuck forever in Guest OS of Qemu + +Passing `-usb -device u2f-passthru,hidraw=/dev/hidraw2` for U2F-Passthrough +Steps to reproduce: +1. Make you have have plugged Yubikey. +2. In Guest shell install package using following command `sudo apt-get install pamu2fcfg` +3. Run $`pamu2fcfg` command will stuck forever. + +**Note:** If I run `pamu2fcfg` in my Ubuntu Host environment it works fine. +Additional information: +**lsusb output:** + +**$lusb** + +Bus 001 Device 002: ID 46f4:0005 **QEMU U2F USB key** + +Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + +**Debug Details:** + +When pamu2fcfg was launched following will be the call flow. + +[u2f_key_recv_from_guest](https://github.com/qemu/qemu/blob/master/hw/usb/u2f.c#L251 "https://github.com/qemu/qemu/blob/master/hw/usb/u2f.c#L251") → [recv_from_guest](https://github.com/qemu/qemu/blob/master/hw/usb/u2f.c#L204 "https://github.com/qemu/qemu/blob/master/hw/usb/u2f.c#L204") → [u2f_passthru_recv_from_guest](https://github.com/qemu/qemu/blob/master/hw/usb/u2f-passthru.c#L332 "https://github.com/qemu/qemu/blob/master/hw/usb/u2f-passthru.c#L332") → [u2f_passthru_read](https://github.com/qemu/qemu/blob/master/hw/usb/u2f-passthru.c#L305 "https://github.com/qemu/qemu/blob/master/hw/usb/u2f-passthru.c#L305") → [u2f_passthru_recv_from_host](https://github.com/qemu/qemu/blob/master/hw/usb/u2f-passthru.c#L329 "https://github.com/qemu/qemu/blob/master/hw/usb/u2f-passthru.c#L329") →[ u2f_transaction_get_from_nonce](https://github.com/qemu/qemu/blob/master/hw/usb/u2f-passthru.c#L272 "https://github.com/qemu/qemu/blob/master/hw/usb/u2f-passthru.c#L272") → [u2f_send_to_guest](https://github.com/qemu/qemu/blob/master/hw/usb/u2f-passthru.c#L302 "https://github.com/qemu/qemu/blob/master/hw/usb/u2f-passthru.c#L302") →[ u2f_pending_in_add](https://github.com/qemu/qemu/blob/master/hw/usb/u2f.c#L207 "https://github.com/qemu/qemu/blob/master/hw/usb/u2f.c#L207") → [main_loop_wait](https://github.com/qemu/qemu/blob/master/system/runstate.c#L783 "https://github.com/qemu/qemu/blob/master/system/runstate.c#L783") (stuck here) + +From above call flow looks like guest is waiting for key. + +Even I have tried enabling U2F support flag in Qemu while building but that one was not helping either. + +**References:** + +https://github.com/Yubico/pam-u2f/tree/main + +https://www.qemu.org/docs/master/system/devices/usb-u2f.html diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2296 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2296 new file mode 100644 index 000000000..752d1a637 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2296 @@ -0,0 +1,97 @@ +heap-buffer-overflow in virtio-sound +Description of problem: +The following log reveals it: + +``` +==3191578==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x602000068620 at pc 0x55dadcde4ec5 bp 0x7ffe7f18aef0 sp 0x7ffe7f18aee0 +READ of size 8 at 0x602000068620 thread T0 + #0 0x55dadcde4ec4 in virtio_snd_handle_rx_xfer ../hw/audio/virtio-snd.c:988 + #1 0x55daddffbf5e in virtio_queue_notify ../hw/virtio/virtio.c:2296 + #2 0x55dadd6cff4a in virtio_pci_notify_write ../hw/virtio/virtio-pci.c:1721 + #3 0x55dade0ab336 in memory_region_write_accessor ../system/memory.c:497 + #4 0x55dade0af3d0 in access_with_adjusted_size ../system/memory.c:573 + #5 0x55dade0b5032 in memory_region_dispatch_write ../system/memory.c:1528 + #6 0x55dade0ebb62 in flatview_write_continue_step ../system/physmem.c:2713 + #7 0x55dade0ebfb2 in flatview_write_continue ../system/physmem.c:2743 + #8 0x55dade0ebfb2 in flatview_write ../system/physmem.c:2774 + #9 0x55dade0edd58 in address_space_write ../system/physmem.c:2894 + #10 0x55dadd809972 in qtest_process_command ../system/qtest.c:679 + #11 0x55dadd80c3e2 in qtest_process_inbuf ../system/qtest.c:811 + #12 0x55dade6e79a4 in fd_chr_read ../chardev/char-fd.c:72 + #13 0x7f79b0d29c43 in g_main_context_dispatch (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x55c43) + #14 0x55dade998bcf in glib_pollfds_poll ../util/main-loop.c:287 + #15 0x55dade998bcf in os_host_main_loop_wait ../util/main-loop.c:310 + #16 0x55dade998bcf in main_loop_wait ../util/main-loop.c:589 + #17 0x55dadd810e00 in qemu_main_loop ../system/runstate.c:783 + #18 0x55dade2b703a in qemu_default_main ../system/main.c:37 + #19 0x7f79afe29d8f in __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:58 + #20 0x7f79afe29e3f in __libc_start_main_impl ../csu/libc-start.c:392 + #21 0x55dadcb5a284 in _start (/home/joey/repo/qemu/build/qemu-system-x86_64+0x2ef6284) + +0x602000068620 is located 0 bytes to the right of 16-byte region [0x602000068610,0x602000068620) +allocated by thread T0 here: + #0 0x7f79b18b4a57 in __interceptor_calloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:154 + #1 0x7f79b0d32c50 in g_malloc0 (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x5ec50) + #2 0x55dadebf5847 (/home/joey/repo/qemu/build/qemu-system-x86_64+0x4f91847) + +SUMMARY: AddressSanitizer: heap-buffer-overflow ../hw/audio/virtio-snd.c:988 in virtio_snd_handle_rx_xfer +Shadow bytes around the buggy address: + 0x0c0480005070: fa fa 05 fa fa fa 07 fa fa fa 00 01 fa fa 07 fa + 0x0c0480005080: fa fa 05 fa fa fa 07 fa fa fa 00 03 fa fa fd fd + 0x0c0480005090: fa fa fd fd fa fa fd fd fa fa fd fd fa fa 00 06 + 0x0c04800050a0: fa fa 00 00 fa fa 00 00 fa fa 00 01 fa fa 05 fa + 0x0c04800050b0: fa fa 00 03 fa fa 00 03 fa fa 00 01 fa fa 00 05 +=>0x0c04800050c0: fa fa 00 00[fa]fa 00 00 fa fa 00 04 fa fa 00 00 + 0x0c04800050d0: fa fa fd fd fa fa fd fd fa fa fd fa fa fa fd fa + 0x0c04800050e0: fa fa fd fa fa fa fd fa fa fa fd fa fa fa fd fa + 0x0c04800050f0: fa fa fd fa fa fa fd fa fa fa fd fa fa fa fd fa + 0x0c0480005100: fa fa fd fd fa fa fd fa fa fa fd fa fa fa fd fa + 0x0c0480005110: fa fa fd fa fa fa fd fa fa fa fd fa fa fa fd fa +Shadow byte legend (one shadow byte represents 8 application bytes): + Addressable: 00 + Partially addressable: 01 02 03 04 05 06 07 + Heap left redzone: fa + Freed heap region: fd + Stack left redzone: f1 + Stack mid redzone: f2 + Stack right redzone: f3 + Stack after return: f5 + Stack use after scope: f8 + Global redzone: f9 + Global init order: f6 + Poisoned by user: f7 + Container overflow: fc + Array cookie: ac + Intra object redzone: bb + ASan internal: fe + Left alloca redzone: ca + Right alloca redzone: cb + Shadow gap: cc +``` +Steps to reproduce: +``` +cat << EOF | qemu-system-x86_64 -display none \ +-machine accel=qtest -m 512M -machine q35 -device \ +virtio-sound,audiodev=my_audiodev,streams=2 -audiodev \ +alsa,id=my_audiodev -qtest stdio +outl 0xcf8 0x80001804 +outw 0xcfc 0x06 +outl 0xcf8 0x80001820 +outl 0xcfc 0xe0008000 +write 0xe0008016 0x1 0x03 +write 0xe0008020 0x4 0x00901000 +write 0xe0008028 0x4 0x00a01000 +write 0xe000801c 0x1 0x01 +write 0xe000a004 0x1 0x40 +write 0x10c000 0x1 0x02 +write 0x109001 0x1 0xc0 +write 0x109002 0x1 0x10 +write 0x109008 0x1 0x04 +write 0x10a002 0x1 0x01 +write 0xe000b00d 0x1 0x00 +EOF +``` + +# Possible Fix + +check the user-assigned value in virtio_snd_set_config() diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2298 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2298 new file mode 100644 index 000000000..4d49f718a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2298 @@ -0,0 +1,12 @@ +Invariant result in opts-visitor.c +Description of problem: +Expressions: +1) val2 <= INT64_MAX +2) INT64_MIN <= val2 +in line [431](https://github.com/qemu/qemu/blob/62dbe54c24dbf77051bafe1039c31ddc8f37602d/qapi/opts-visitor.c#L431) are always true. + +Seems like this checks are redundant. + +Found by Linux Verification Center (portal.linuxtesting.ru) with SVACE. + +Author A. Burke. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2299 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2299 new file mode 100644 index 000000000..ae432c688 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2299 @@ -0,0 +1,203 @@ +UFS Device sanitizers error +Description of problem: +Sanitizers error reported by Zheyu Ma zheyuma97@gmail.com + +The following log can reveal it: + +==3619819==ERROR: AddressSanitizer: heap-buffer-overflow on address + +0x62a000011200 at pc 0x7f9f9903a2c3 bp 0x7ffd44e1ee60 sp 0x7ffd44e1e608 + +WRITE of size 20512 at 0x62a000011200 thread T0 + +``` +#0 0x7f9f9903a2c2 in __interceptor_memcpy +``` + +../../../../src/libsanitizer/sanitizer_common/sanitizer_common_interceptors.inc:827 + +``` +#1 0x5f23331ea4fc in memcpy +``` + +/usr/include/x86_64-linux-gnu/bits/string_fortified.h:29 + +``` +#2 0x5f23331ea4fc in flatview_read_continue_step +``` + +../system/physmem.c:2818 + +``` +#3 0x5f23331eab72 in flatview_read_continue ../system/physmem.c:2835 + +#4 0x5f23331eadc4 in flatview_read ../system/physmem.c:2865 + +#5 0x5f23331ec2a5 in address_space_read_full ../system/physmem.c:2878 + +#6 0x5f23331ec2a5 in address_space_rw ../system/physmem.c:2906 + +#7 0x5f23326b7ad0 in ufs_dma_read_req_upiu ../hw/ufs/ufs.c:129 + +#8 0x5f23326b7ad0 in ufs_dma_read_upiu ../hw/ufs/ufs.c:185 + +#9 0x5f23326b7ad0 in ufs_exec_req ../hw/ufs/ufs.c:1021 + +#10 0x5f23326b7ad0 in ufs_process_req ../hw/ufs/ufs.c:1066 + +#11 0x5f2333a9160d in aio_bh_call ../util/async.c:171 + +#12 0x5f2333a91f45 in aio_bh_poll ../util/async.c:218 + +#13 0x5f2333a217a9 in aio_dispatch ../util/aio-posix.c:423 + +#14 0x5f2333a90d01 in aio_ctx_dispatch ../util/async.c:360 + +#15 0x7f9f985c4d3a in g_main_context_dispatch +``` + +(/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x55d3a) + +``` +#16 0x5f2333a9690f in glib_pollfds_poll ../util/main-loop.c:287 + +#17 0x5f2333a9690f in os_host_main_loop_wait ../util/main-loop.c:310 + +#18 0x5f2333a9690f in main_loop_wait ../util/main-loop.c:589 + +#19 0x5f23329370e0 in qemu_main_loop ../system/runstate.c:783 + +#20 0x5f23333b4d7a in qemu_default_main ../system/main.c:37 + +#21 0x7f9f97629d8f in __libc_start_call_main +``` + +../sysdeps/nptl/libc_start_call_main.h:58 + +``` +#22 0x7f9f97629e3f in __libc_start_main_impl ../csu/libc-start.c:392 + +#23 0x5f2331c8df64 in _start +``` + +(/home/joey/repo/qemu/build/qemu-system-x86_64+0x2ea8f64) + +0x62a000011200 is located 0 bytes to the right of 20480-byte region + +\[0x62a00000c200,0x62a000011200) + +allocated by thread T0 here: + +``` +#0 0x7f9f990b4a57 in __interceptor_calloc +``` + +../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:154 + +``` +#1 0x7f9f985cdc50 in g_malloc0 +``` + +(/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x5ec50) + +``` +#2 0xf0e808deae299ff (<unknown module>) +``` + +SUMMARY: AddressSanitizer: heap-buffer-overflow + +../../../../src/libsanitizer/sanitizer_common/sanitizer_common_interceptors.inc:827 + +in \__interceptor_memcpy + +Shadow bytes around the buggy address: + +0x0c547fffa1f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 + +0x0c547fffa200: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 + +0x0c547fffa210: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 + +0x0c547fffa220: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 + +0x0c547fffa230: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 + +=\>0x0c547fffa240:\[fa\]fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa + +0x0c547fffa250: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa + +0x0c547fffa260: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa + +0x0c547fffa270: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa + +0x0c547fffa280: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa + +0x0c547fffa290: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa + +Shadow byte legend (one shadow byte represents 8 application bytes): + +Addressable: 00 + +Partially addressable: 01 02 03 04 05 06 07 + +Heap left redzone: fa + +Freed heap region: fd + +Stack left redzone: f1 + +Stack mid redzone: f2 + +Stack right redzone: f3 + +Stack after return: f5 + +Stack use after scope: f8 + +Global redzone: f9 + +Global init order: f6 + +Poisoned by user: f7 + +Container overflow: fc + +Array cookie: ac + +Intra object redzone: bb + +ASan internal: fe + +Left alloca redzone: ca + +Right alloca redzone: cb + +Shadow gap: cc + +==3619819==ABORTING + +And Here is a simple PoC: + +cat \<\< EOF \\ + +qemu-system-x86_64 \\ + +\-display none -machine accel=qtest -m 512M -M q35 -nodefaults -drive \\ + +file=[null-co://,if=none,id=disk0](null-co://,if=none,id=disk0) -device ufs,id=ufs_bus -device \\ + +ufs-lu,drive=disk0,bus=ufs_bus -qtest stdio + +outl 0xcf8 0x80000810 + +outl 0xcfc 0xe0000000 + +outl 0xcf8 0x80000804 + +outw 0xcfc 0x06 + +write 0xe0000058 0x1 0xa7 + +write 0xa 0x1 0x50 + +EOF diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/230 b/gitlab/issues_text/target_missing/host_missing/accel_missing/230 new file mode 100644 index 000000000..baca53a8a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/230 @@ -0,0 +1 @@ +Confuse error message in virtio_init_region_cache() diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2301 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2301 new file mode 100644 index 000000000..01a7020af --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2301 @@ -0,0 +1 @@ +GitLab Windows Server 2019 runner is deprecated diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2303 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2303 new file mode 100644 index 000000000..91beda752 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2303 @@ -0,0 +1,71 @@ +Multiple displays configuration supports +Additional information: +The following patch is a quick "hack" to make it work + +```patch + +From 18ad5058a18fa9f6db2c0c3058e25989908d95bb Mon Sep 17 00:00:00 2001 +From: Sergio Lopez <slp@redhat.com> +Date: Fri, 23 Jun 2023 13:15:15 +0200 +Subject: [PATCH 6/8] HACK: Set static resolutions for the VM + +--- + hw/display/virtio-gpu-base.c | 10 +++++++++- + ui/gtk.c | 6 ++++-- + 2 files changed, 13 insertions(+), 3 deletions(-) + +diff --git a/hw/display/virtio-gpu-base.c b/hw/display/virtio-gpu-base.c +index a29f191aa8..b1ccfa17b7 100644 +--- a/hw/display/virtio-gpu-base.c ++++ b/hw/display/virtio-gpu-base.c +@@ -47,6 +47,7 @@ virtio_gpu_base_fill_display_info(VirtIOGPUBase *g, + dpy_info->pmodes[i].enabled = 1; + dpy_info->pmodes[i].r.width = cpu_to_le32(g->req_state[i].width); + dpy_info->pmodes[i].r.height = cpu_to_le32(g->req_state[i].height); ++ fprintf(stderr, "display %d: %dx%d\n", i, dpy_info->pmodes[i].r.width, dpy_info->pmodes[i].r.height); + } + } + } +@@ -63,14 +64,17 @@ static void virtio_gpu_text_update(void *opaque, console_ch_t *chardata) + { + } + ++#if 0 + static void virtio_gpu_notify_event(VirtIOGPUBase *g, uint32_t event_type) + { + g->virtio_config.events_read |= event_type; + virtio_notify_config(&g->parent_obj); + } ++#endif + + static void virtio_gpu_ui_info(void *opaque, uint32_t idx, QemuUIInfo *info) + { ++#if 0 + VirtIOGPUBase *g = opaque; + + if (idx >= g->conf.max_outputs) { +@@ -94,6 +98,7 @@ static void virtio_gpu_ui_info(void *opaque, uint32_t idx, QemuUIInfo *info) + /* send event to guest */ + virtio_gpu_notify_event(g, VIRTIO_GPU_EVENT_DISPLAY); + return; ++#endif + } + + static void +@@ -186,11 +191,14 @@ virtio_gpu_base_device_realize(DeviceState *qdev, + virtio_add_queue(vdev, 16, cursor_cb); + } + +- g->enabled_output_bitmask = 1; ++ g->enabled_output_bitmask = 3; + + g->req_state[0].width = g->conf.xres; + g->req_state[0].height = g->conf.yres; + ++ g->req_state[1].width = 800; ++ g->req_state[1].height = 600; ++ + g->hw_ops = &virtio_gpu_ops; + for (i = 0; i < g->conf.max_outputs; i++) { + g->scanout[i].con = +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2306 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2306 new file mode 100644 index 000000000..962d22a47 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2306 @@ -0,0 +1 @@ +A bug of ptimer that the freq can't set more than 1000M diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2307 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2307 new file mode 100644 index 000000000..6c52d7fed --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2307 @@ -0,0 +1,39 @@ +QEMU Windows COM port filenames not recognized i.e. \\.\COM19 or \\.\CNCA0 +Steps to reproduce: +1. Run qemu-system-arm with the comand line above. +2. QEMU fails with `qemu-system-arm.exe: -gdb \\.\CNCA8: '\\.\CNCA8' is not a valid char driver` +3. ```qemu-system-arm.exe -machine mps2-an500 -gdb \\.\COM19 +qemu-system-arm.exe: -gdb \\.\COM19: '\\.\COM19' is not a valid char driver +``` +Additional information: +Windows allows COM ports numbered 10 and higher to be prefixed with a `\\.\` escape as in `\\.\COM17`. Such COM port assignments are not uncommon when a plurality of USB serial adapters. +Equally problematic are virtual COM port designations such as `\\.\CNCA8` created by the Windows 10x64 driver package known as `com0com`: https://pete.akeo.ie/2011/07/com0com-signed-drivers.html + +Upon checking the source pulled from the Github mirror an initial fix was to simply modify /chardev/char.c, but this appears insufficient. Sadly. + +Please ask if more information is required. I am actively working on extending an existing QEMU machine emulation. A patch to fix this problem is below. Please comment if applicable. + +Jerry. + +``` +diff --git a/chardev/char.c b/chardev/char.c +index 3c43fb1278..7a3f342c72 100644 +--- a/chardev/char.c ++++ b/chardev/char.c +@@ -418,6 +418,13 @@ QemuOpts *qemu_chr_parse_compat(const char *label, const char *filename, + qemu_opt_set(opts, "path", filename, &error_abort); + return opts; + } ++ // JME ++ if (strstart(filename, "\\\\.\\", NULL)) { ++ qemu_opt_set(opts, "backend", "serial", &error_abort); ++ qemu_opt_set(opts, "path", filename, &error_abort); ++ return opts; ++ } ++ + if (strstart(filename, "file:", &p)) { + qemu_opt_set(opts, "backend", "file", &error_abort); + qemu_opt_set(opts, "path", p, &error_abort); + +``` +/label ~"kind::Bug" diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2308 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2308 new file mode 100644 index 000000000..7a276f84a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2308 @@ -0,0 +1,79 @@ +QEMU Windows COM port setup dialog always invoked and fails if none is available (USB or virtual serial port hardware) +Description of problem: +The Windows backend serial port in `chardev/char-win.c` always calls `CommConfigDialog()`. This should display a COM port configuration dialog which does (and can) not persist the COM port settings. If the COM port does not support this action (see https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-commconfigdialoga) then the function fails. +Steps to reproduce: +1. Currently not possible with QEMU releases as QEMU does not recognize extended COM port specifications like `\\.\COM19` or `\\.\CNCA0` +Additional information: +See https://support.microsoft.com/en-gb/topic/howto-specify-serial-ports-larger-than-com9-db9078a5-b7b6-bf00-240f-f749ebfd913e for details on COM port filenames. + +I have a patch which 'fixes' this problem by setting the nominated COM port to defaults of `115200,8,N,0` which seems perfectly sensible in 2024. Please contact me for more details. A git diff shown below (with extensive error reporting) + +N.B. Markodown will destroy formatting! + +``` +diff --git a/chardev/char-win.c b/chardev/char-win.c +index d4fb44c4dc..a05896ffe9 100644 +--- a/chardev/char-win.c ++++ b/chardev/char-win.c +@@ -96,12 +96,24 @@ int win_chr_serial_init(Chardev *chr, const char *filename, Error **errp) + s->file = CreateFile(filename, GENERIC_READ | GENERIC_WRITE, 0, NULL, + OPEN_EXISTING, FILE_FLAG_OVERLAPPED, 0); + if (s->file == INVALID_HANDLE_VALUE) { ++ { ++ char buffer[1024] = { 0 }; ++ DWORD dw = GetLastError(); ++ sprintf_s(buffer, 1024, "%s(%d) Error: %d 0x%x %s\r\n", __FILE__, __LINE__, dw, dw, filename); ++ OutputDebugString(buffer); ++ } + error_setg_win32(errp, GetLastError(), "Failed CreateFile"); + s->file = NULL; + goto fail; + } + + if (!SetupComm(s->file, NRECVBUF, NSENDBUF)) { ++ { ++ char buffer[1024] = { 0 }; ++ DWORD dw = GetLastError(); ++ sprintf_s(buffer, 1024, "%s(%d) Error: %d 0x%x %s\r\n", __FILE__, __LINE__, dw, dw, filename); ++ OutputDebugString(buffer); ++ } + error_setg(errp, "Failed SetupComm"); + goto fail; + } +@@ -110,9 +122,31 @@ int win_chr_serial_init(Chardev *chr, const char *filename, Error **errp) + size = sizeof(COMMCONFIG); + GetDefaultCommConfig(filename, &comcfg, &size); + comcfg.dcb.DCBlength = sizeof(DCB); +- CommConfigDialog(filename, NULL, &comcfg); +- ++#if 1 ++ // JME hardwire. There seems to be no mechanism to simply specify serial port options ++ comcfg.dcb.BaudRate = 115200; ++ comcfg.dcb.Parity = NOPARITY; ++ comcfg.dcb.StopBits = ONESTOPBIT; ++ comcfg.dcb.ByteSize = 8; ++#else ++ { ++ BOOL ret = CommConfigDialog(filename, NULL, &comcfg); ++ if (!ret) ++ { ++ char buffer[1024] = { 0 }; ++ DWORD dw = GetLastError(); ++ sprintf_s(buffer, 1024, "%s(%d) Error: %d 0x%x %s\r\n", __FILE__, __LINE__, dw, dw, filename); ++ OutputDebugString(buffer); ++ } ++ } ++#endif + if (!SetCommState(s->file, &comcfg.dcb)) { ++ { ++ char buffer[1024]={0}; ++ DWORD dw = GetLastError(); ++ sprintf_s(buffer,1024,"%s(%d) Error: %d 0x%x %s\r\n",__FILE__,__LINE__,dw,dw, filename); ++ OutputDebugString(buffer); ++ } + error_setg(errp, "Failed SetCommState"); + goto fail; + } +``` + +/label ~"kind::Bug" diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/231 b/gitlab/issues_text/target_missing/host_missing/accel_missing/231 new file mode 100644 index 000000000..5e8771248 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/231 @@ -0,0 +1 @@ +Many leaks from qemu_spice_create_update diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2310 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2310 new file mode 100644 index 000000000..c939fa5bd --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2310 @@ -0,0 +1 @@ +Virtio devices not working diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2311 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2311 new file mode 100644 index 000000000..5f7512b7d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2311 @@ -0,0 +1,15 @@ +Possible dereference of NULL +Description of problem: +There is possible dereference of NULL using macro QEMU_LOCK_GUARD(&q->lock) in: +1) /block/nvme.c line [326](https://github.com/qemu/qemu/blob/5da72194df36535d773c8bdc951529ecd5e31707/block/nvme.c#L326) +2) /include/qemu/ratelimit.h line [45](https://github.com/qemu/qemu/blob/5da72194df36535d773c8bdc951529ecd5e31707/include/qemu/ratelimit.h#L45) +3) /include/qemu/ratelimit.h line [88](https://github.com/qemu/qemu/blob/5da72194df36535d773c8bdc951529ecd5e31707/include/qemu/ratelimit.h#L88) + + +The QEMU_MAKE_LOCKABLE(x) macro provides a special case (line [71](https://github.com/qemu/qemu/blob/5da72194df36535d773c8bdc951529ecd5e31707/include/qemu/lockable.h#L71) of the lockable.h) if NULL gets into it. Then the macro will return NULL, which will get to the input of the qemu_lockable_auto_lock() function, then to the qemu_lockable_lock() function, where NULL dereference will occur (line [95](https://github.com/qemu/qemu/blob/5da72194df36535d773c8bdc951529ecd5e31707/include/qemu/lockable.h#L95)). + +It turns out that the NULL case is provided, but not handled properly. I think a NULL check should be added. + +Found by Linux Verification Center (portal.linuxtesting.ru) with SVACE. + +Author A. Burke. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2313 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2313 new file mode 100644 index 000000000..6e327d835 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2313 @@ -0,0 +1,17 @@ +RISC-V KVM strerrorname_np regression breaks build on Alpine Linux +Description of problem: +Build from source fails on Alpine Linux due to the use of the non-portable `strerrorname_np`: +``` +/usr/lib/gcc/riscv64-alpine-linux-musl/13.2.1/../../../../riscv64-alpine-linux-musl/bin/ld: libqemu-riscv64-softmmu.fa.p/target_riscv_kvm_kvm-cpu.c.o: in function `kvm_cpu_realize': +kvm-cpu.c:(.text+0x538): undefined reference to `strerrorname_np' +/usr/lib/gcc/riscv64-alpine-linux-musl/13.2.1/../../../../riscv64-alpine-linux-musl/bin/ld: libqemu-riscv64-softmmu.fa.p/target_riscv_kvm_kvm-cpu.c.o: in function `kvm_cpu_instance_init': +kvm-cpu.c:(.text+0x1244): undefined reference to `strerrorname_np' +``` +Steps to reproduce: +1. install alpine linux on a riscv64 machine +2. build qemu-9.0.0 from source. +3. +Additional information: +Same problem as https://gitlab.com/qemu-project/qemu/-/issues/2041 + +Re-introduced with d4ff3da8f45c52670941c6e1b94e771d69d887e9 and 0d71f0a34938a6ac11953ae3dbec40113d2838a1 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2314 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2314 new file mode 100644 index 000000000..b7b02debb --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2314 @@ -0,0 +1,16 @@ +Building QEMU 9.0.0 fails on MacOS 10.15.7 (error: initializing 'NSEdgeInsets' (aka 'struct NSEdgeInsets') with an expression of incompatible type 'id') +Description of problem: +QEMU fails to compile using Homebrew on OS X 10.15.7: +``` +../ui/cocoa.m:542:18: error: initializing 'NSEdgeInsets' (aka 'struct NSEdgeInsets') with an expression of incompatible type 'id' + NSEdgeInsets insets = [[[self window] screen] safeAreaInsets]; + ^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +1 error generated. +``` +Steps to reproduce: +1. Compile QEMU on OS X 10.15.7 using Homebrew +2. +3. +Additional information: +Build log +[02.make.zip](/uploads/dfb618b86984ed6cf699d94bf9d6c9e1/02.make.zip) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2315 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2315 new file mode 100644 index 000000000..8592170cb --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2315 @@ -0,0 +1,12 @@ +Mouse cursor is flipped / inverted / upside-down with virtio-gpu in some Wayland compositors +Description of problem: +The mouse cursor is flipped: +Steps to reproduce: +1. Install a Linux system with a 6.8.x kernel inside the virtual machine +2. Install sway / wayfire / hyprland, or kwin 6.0.4.1 +3. See the mouse cursor +Additional information: +The [kwin fix](https://invent.kde.org/plasma/kwin/-/commit/a31561c392adf5abcda0284e8049fafcb3701585) just makes use of dumb buffers instead of dmabuf. + +The mouse cursor should be pointing to the maximizing button at the top-right corner: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2316 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2316 new file mode 100644 index 000000000..0fcbee479 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2316 @@ -0,0 +1,36 @@ +aarch64 virt cortex-a53 libc printf (with argument) hello world strange behavior +Description of problem: +My hello world get lost after + +`0x0000000040000370 <+48>: str q0, [sp, #80]` + +in + +``` + 0x1f8: udf #0 + 0x1fc: udf #0 +=> 0x200: udf #0 + 0x204: udf #0 + 0x208: udf #0 + 0x20c: udf #0 + 0x210: udf #0 + 0x214: udf #0 +``` + +By bisecting, I got the last commit OK : v8.2.0-2033-g49fa457ca5 + +``` +$ qemu-system-aarch64 -M virt,secure=on,gic-version=3 -cpu cortex-a53 -kernel aarch64-none-elf-a.elf -serial stdio -display none +printf with an integer : 42 +``` + +But after v8.2.0-2034-g59754f85ed https://gitlab.com/qemu-project/qemu/-/commit/59754f85ed35cbd5f4bf2663ca2136c78d5b2413 (for example with latest v9.0.0-265-gfd87be1dad), it doesn't work anymore. +Steps to reproduce: +1. Build qemu-system-aarch64 with ``./configure --prefix=$PREFIX --target-list=aarch64-softmmu --disable-user --disable-linux-user --disable-bsd-user --enable-kvm --enable-tcg --disable-gnutls --disable-nettle --disable-gtk --disable-iconv --disable-curses --disable-curl --disable-vnc --disable-vnc-jpeg --disable-attr --disable-libusb --disable-opengl --disable-tpm --disable-bzip2 && make -j$(nproc) && make install`` + +2. Run my hello world : ``qemu-system-aarch64 -M virt,secure=on,gic-version=3 -cpu cortex-a53 -kernel aarch64-none-elf-a.elf -serial stdio -display none`` +Additional information: +I provide here the hello world (elf + map). Of course the problem might be that it (qemu and/or hello world) was not built correctly and that everything was working by chance before v8.2.0-2033-g49fa457ca5 +[aarch64-none-elf-a.elf](/uploads/daf7f37aec260c56d4be5fd90554dce3/aarch64-none-elf-a.elf) +[aarch64-none-elf-a.map](/uploads/5564cee13a214e7eb8d6d4bf79f09682/aarch64-none-elf-a.map) +Depending on the investigation, I can provide what's needed to rebuild it. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/232 b/gitlab/issues_text/target_missing/host_missing/accel_missing/232 new file mode 100644 index 000000000..48506d623 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/232 @@ -0,0 +1 @@ +I/O write make QXL abort in qxl_set_mode() diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2322 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2322 new file mode 100644 index 000000000..9f7594eaa --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2322 @@ -0,0 +1 @@ +Qemu 9 make install failed on Ubuntu 23.10 ARM64 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2323 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2323 new file mode 100644 index 000000000..2000bca2d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2323 @@ -0,0 +1,26 @@ +Win/Super key not working correctly under Windows hosts +Description of problem: +I accidentally noticed `Win` key (VK_LWIN) not working correctly on Windows hosts, more specifically: + +1. It is impossible to "hold" `Win`. If one presses and holds `Win`, the guest is spammed with `Win` keypresses, instead of receiving a single `Win` keypress at the point of releasing the button (VK_LWIN button up). +2. It is impossible to make key combinations (shortcuts, hotkeys etc.) that involve the `Win/Super` key. Maybe implicitly solved by fixing #1. + +This behavior is present starting from bc8e883065f36581e4f2352c31a1dfa5f65a82f2 (ui/sdl2: disable SDL_HINT_GRAB_KEYBOARD on Windows). Before it, on the SDL2 keyboard hook `Win/Super` key worked correctly. I demonstrate the problem on Fedora/WinXP, but it affects all guests. +Steps to reproduce: +1. (see additional information) +2. +3. +Additional information: +Short video demonstration on a WinXP guest and a Fedora 39 guest. The qemus used are (qemu-8.0.2 e0968d21e27ef9c406f709180a39a076e786efbe; working correctly) and (qemu-9.0.0 from the release tarball qemu-9.0.0.tar.xz; buggy) + +1. In the WinXP video, I'm pressing and holding the `Win` key for about 3 seconds. In the correct version, the start menu is opened only at the point of release. In the buggy version, the start menu is opened repeatedly tens of times (flickering). You can see the point of release in Nirsoft's KeyboardStateView, when VK_LWIN loses the "pressed" asterisk. + + At the end of the video I'm trying to use the `Win+e` shortcut for WinExplorer. In the buggy version, Outlook is opened instead. This is because the keypresses are processed individually, first `Win` opens the start menu and then `e` opens email application (in this case outlook). In the correct version WinExplorer is opened. + +  +  + +2. In the Fedora video, I'm trying to set up a simple shortcut, I'm pressing on my keyboard `LCTRL+LALT+Super+E`. In the buggy version, the `Super` key is not picked up. All the shortcut combinations involving `Super` are therefore not working. + +  +  diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2327 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2327 new file mode 100644 index 000000000..ea172bdb9 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2327 @@ -0,0 +1,61 @@ +negative shift exponent in cirrus_colorexpand_pattern_transp_0_24() +Description of problem: +My fuzzer detected a runtime error in cirrus_colorexpand_pattern_transp_0_24() + +The stack trace is: + +``` +../hw/display/cirrus_vga_rop2.h:216:23: runtime error: shift exponent -2 is negative + #0 0x5589a028c89a in cirrus_colorexpand_pattern_transp_0_24 hw/display/cirrus_vga_rop2.h:216:23 + #1 0x5589a031e239 in cirrus_bitblt_common_patterncopy hw/display/cirrus_vga.c:689:5 + #2 0x5589a032735d in cirrus_bitblt_cputovideo_next hw/display/cirrus_vga.c:820:13 + #3 0x5589a032cde9 in cirrus_linear_write hw/display/cirrus_vga.c:2365:13 + #4 0x5589a2982823 in memory_region_write_accessor system/memory.c:497:5 + #5 0x5589a2981f05 in access_with_adjusted_size system/memory.c:573:18 + #6 0x5589a297fe69 in memory_region_dispatch_write system/memory.c:1521:16 + #7 0x5589a2a2193e in flatview_write_continue_step system/physmem.c:2749:18 + #8 0x5589a2a211d4 in flatview_write_continue system/physmem.c:2779:19 + #9 0x5589a29f9cfb in flatview_write system/physmem.c:2810:12 + #10 0x5589a29f97c8 in address_space_write system/physmem.c:2930:18 +... +``` +Steps to reproduce: +Arguments:\ +export QEMU_ARGS="-display none -machine accel=qtest, -m 512M -machine\ +q35 -nodefaults -device cirrus-vga -display vnc=localhost:99 -L ../pc-bios/"\ +The base addresses of memory regions: + +* cirrus-io, 0x3b0 +* cirrus-low-memory, 0xa0000 +* cirrus-linear-io, 0xe0000000 +* cirrus-bitblt-mmio, 0xe1000000 +* cirrus-mmio, 0xe2000000 + +Reproducer: + +``` +writeb 0xe2000108 0x642a8d58 +writeb 0xe2000117 0x335af91c +writeb 0xe2000118 0x765861ed +writeb 0xe200010d 0x7c3af934 +writeb 0xe2000140 0x33f13baf +clock_step +writeb 0xe01f0e68 0x6ea3696c +writeb 0xe13bc720 0x11bb09ba +readb 0xe2000133 +writeb 0xe033629b 0x80f19dd +writeb 0xe134bba7 0x1eb198f9 +readb 0xe2000680 +writeb 0xe2000b84 0x3f0591fc +clock_step +writeb 0xe003469e 0xdbd627e +writeb 0xe114f2bc 0x41adfe48 +readb 0xe2000cde +readb 0xb269d +writeb 0xe1368066 0x3c9ab77 +readb 0xe12a7fe1 +writeb 0xe0191988 0x7e18b0d1 +EOF +``` +Additional information: +Ack: Chuhong Yuan (hslester96@gmail.com) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2329 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2329 new file mode 100644 index 000000000..355a1017f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2329 @@ -0,0 +1 @@ +Windows 64-bit, qemu-monitor, change diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2331 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2331 new file mode 100644 index 000000000..c368b5872 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2331 @@ -0,0 +1 @@ +(Question) There's a CLI option for the GUI option "Grab On Hover" ? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2335 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2335 new file mode 100644 index 000000000..7873ce8b5 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2335 @@ -0,0 +1,208 @@ +SPICE Worker segfault +Description of problem: +Hello. Sometimes we have an error. kvm randomly crashes. +May 07 16:55:50 vdi1 kernel: SPICE Worker[249326]: segfault at 7f1c8c03af40 ip 00007f1fbbbb2579 sp 00007f1dabbf9d20 error 4 in libc.so.6[7f1fbbb41000+155000] likely on CPU 89 (core 20, socket 1) +Steps to reproduce: +1. +2. +3. +Additional information: +`# coredumpctl info + PID: 249293 (kvm) + UID: 0 (root) + GID: 0 (root) + Signal: 11 (SEGV) + Timestamp: Tue 2024-05-07 16:55:50 MSK (18h ago) + Command Line: /usr/bin/kvm -id 141 -name VDI,debug-threads=on -no-shutdown -chardev socket,id=qmp,path=/var/run/qemu-server/141.qmp,server=on,wait=off -mon chardev=qmp,mode=control -chard> + Executable: /usr/bin/qemu-system-x86_64 + Control Group: /qemu.slice/141.scope + Unit: 141.scope + Slice: qemu.slice + Boot ID: 5cfcd2d515a6425fa3880a61d8cd6bfc + Machine ID: 6e4c2fe391324304a856baa8e6c88002 + Hostname: vdi1 + Storage: /var/lib/systemd/coredump/core.kvm.0.5cfcd2d515a6425fa3880a61d8cd6bfc.249293.1715090150000000.zst (present) + Size on Disk: 2.3G + Message: Process 249293 (kvm) of user 0 dumped core. + + Module libsystemd.so.0 from deb systemd-252.22-1~deb12u1.amd64 + Module libudev.so.1 from deb systemd-252.22-1~deb12u1.amd64 + Stack trace of thread 249326: + #0 0x00007f1fbbbb2579 _int_malloc (libc.so.6 + 0x97579) + #1 0x00007f1fbbbb46e2 __libc_calloc (libc.so.6 + 0x996e2) + #2 0x00007f1fbd3f76d1 g_malloc0 (libglib-2.0.so.0 + 0x5a6d1) + #3 0x00007f1fbdadd7a3 red_get_data_chunks_ptr (libspice-server.so.1 + 0x3e7a3) + #4 0x00007f1fbdaddf6b red_get_data_chunks (libspice-server.so.1 + 0x3ef6b) + #5 0x00007f1fbdadedd9 red_get_copy_ptr (libspice-server.so.1 + 0x3fdd9) + #6 0x00007f1fbdadf1e5 red_get_native_drawable (libspice-server.so.1 + 0x401e5) + #7 0x00007f1fbdaf1a2c red_process_display (libspice-server.so.1 + 0x52a2c) + #8 0x00007f1fbdaf1cb7 worker_source_dispatch (libspice-server.so.1 + 0x52cb7) + #9 0x00007f1fbd3f17a9 g_main_context_dispatch (libglib-2.0.so.0 + 0x547a9) + #10 0x00007f1fbd3f1a38 n/a (libglib-2.0.so.0 + 0x54a38) + #11 0x00007f1fbd3f1cef g_main_loop_run (libglib-2.0.so.0 + 0x54cef) + #12 0x00007f1fbdaf0fa9 red_worker_main (libspice-server.so.1 + 0x51fa9) + #13 0x00007f1fbbba4134 start_thread (libc.so.6 + 0x89134) + #14 0x00007f1fbbc247dc __clone3 (libc.so.6 + 0x1097dc) + + Stack trace of thread 249321: + #0 0x00007f1fbbc18c5b __GI___ioctl (libc.so.6 + 0xfdc5b) + #1 0x000055b3bae626cf kvm_vcpu_ioctl (qemu-system-x86_64 + 0x72b6cf) + #2 0x000055b3bae62ba5 kvm_cpu_exec (qemu-system-x86_64 + 0x72bba5) + #3 0x000055b3bae6408d kvm_vcpu_thread_fn (qemu-system-x86_64 + 0x72d08d) + #4 0x000055b3baffbb78 qemu_thread_start (qemu-system-x86_64 + 0x8c4b78) + #5 0x00007f1fbbba4134 start_thread (libc.so.6 + 0x89134) + #6 0x00007f1fbbc247dc __clone3 (libc.so.6 + 0x1097dc) + + Stack trace of thread 249327: + #0 0x00007f1fbdac9b48 glz_rgb_alpha_compress_seg (libspice-server.so.1 + 0x2ab48) + #1 0x00007f1fbdacc1cb glz_rgb_alpha_compress (libspice-server.so.1 + 0x2d1cb) + #2 0x00007f1fbdad08ed image_encoders_compress_glz (libspice-server.so.1 + 0x318ed) + #3 0x00007f1fbdaba608 _Z18dcc_compress_imageP20DisplayChannelClientP10SpiceImageP11SpiceBitmapP8DrawableiP20compress_send_data_t (libspice-server.so.1 + 0x1b608) + #4 0x00007f1fbdabb7f5 fill_bits (libspice-server.so.1 + 0x1c7f5) + #5 0x00007f1fbdabca2f red_marshall_qxl_draw_copy (libspice-server.so.1 + 0x1da2f) + #6 0x00007f1fbdabe82b marshall_lossless_qxl_drawable (libspice-server.so.1 + 0x1f82b) + #7 0x00007f1fbdadb5d3 _ZN16RedChannelClient4pushEv (libspice-server.so.1 + 0x3c5d3) + #8 0x00007f1fbdadb700 red_channel_client_event (libspice-server.so.1 + 0x3c700) + #9 0x00007f1fbdac579d spice_watch_dispatch (libspice-server.so.1 + 0x2679d) + #10 0x00007f1fbd3f167f g_main_context_dispatch (libglib-2.0.so.0 + 0x5467f) + #11 0x00007f1fbd3f1a38 n/a (libglib-2.0.so.0 + 0x54a38) + #12 0x00007f1fbd3f1cef g_main_loop_run (libglib-2.0.so.0 + 0x54cef) + #13 0x00007f1fbdaf0fa9 red_worker_main (libspice-server.so.1 + 0x51fa9) + #14 0x00007f1fbbba4134 start_thread (libc.so.6 + 0x89134) + #15 0x00007f1fbbc247dc __clone3 (libc.so.6 + 0x1097dc) + + Stack trace of thread 249324: + #0 0x00007f1fbbc18c5b __GI___ioctl (libc.so.6 + 0xfdc5b) + #1 0x000055b3bae626cf kvm_vcpu_ioctl (qemu-system-x86_64 + 0x72b6cf) + #2 0x000055b3bae62ba5 kvm_cpu_exec (qemu-system-x86_64 + 0x72bba5) + #3 0x000055b3bae6408d kvm_vcpu_thread_fn (qemu-system-x86_64 + 0x72d08d) + #4 0x000055b3baffbb78 qemu_thread_start (qemu-system-x86_64 + 0x8c4b78) + #5 0x00007f1fbbba4134 start_thread (libc.so.6 + 0x89134) + #6 0x00007f1fbbc247dc __clone3 (libc.so.6 + 0x1097dc) + + Stack trace of thread 249293: + #0 0x00007f1fbbc17256 __ppoll (libc.so.6 + 0xfc256) + #1 0x000055b3bb011dfe ppoll (qemu-system-x86_64 + 0x8dadfe) + #2 0x000055b3bb00f6ee os_host_main_loop_wait (qemu-system-x86_64 + 0x8d86ee) + #3 0x000055b3bac6caa7 qemu_main_loop (qemu-system-x86_64 + 0x535aa7) + #4 0x000055b3bae6cf46 qemu_default_main (qemu-system-x86_64 + 0x735f46) + #5 0x00007f1fbbb4224a __libc_start_call_main (libc.so.6 + 0x2724a) + #6 0x00007f1fbbb42305 __libc_start_main_impl (libc.so.6 + 0x27305) + #7 0x000055b3baa5f0a1 _start (qemu-system-x86_64 + 0x3280a1) + + Stack trace of thread 249322: + #0 0x00007f1fbbc18c5b __GI___ioctl (libc.so.6 + 0xfdc5b) + #1 0x000055b3bae626cf kvm_vcpu_ioctl (qemu-system-x86_64 + 0x72b6cf) + #2 0x000055b3bae62ba5 kvm_cpu_exec (qemu-system-x86_64 + 0x72bba5) + #3 0x000055b3bae6408d kvm_vcpu_thread_fn (qemu-system-x86_64 + 0x72d08d) + #4 0x000055b3baffbb78 qemu_thread_start (qemu-system-x86_64 + 0x8c4b78) + #5 0x00007f1fbbba4134 start_thread (libc.so.6 + 0x89134) + #6 0x00007f1fbbc247dc __clone3 (libc.so.6 + 0x1097dc) + + Stack trace of thread 249323: + #0 0x00007f1fbbc18c5b __GI___ioctl (libc.so.6 + 0xfdc5b) + #1 0x000055b3bae626cf kvm_vcpu_ioctl (qemu-system-x86_64 + 0x72b6cf) + #2 0x000055b3bae62ba5 kvm_cpu_exec (qemu-system-x86_64 + 0x72bba5) + #3 0x000055b3bae6408d kvm_vcpu_thread_fn (qemu-system-x86_64 + 0x72d08d) + #4 0x000055b3baffbb78 qemu_thread_start (qemu-system-x86_64 + 0x8c4b78) + #5 0x00007f1fbbba4134 start_thread (libc.so.6 + 0x89134) + #6 0x00007f1fbbc247dc __clone3 (libc.so.6 + 0x1097dc) + + Stack trace of thread 249294: + #0 0x00007f1fbbc1c719 syscall (libc.so.6 + 0x101719) + #1 0x000055b3baffccfa qemu_futex_wait (qemu-system-x86_64 + 0x8c5cfa) + #2 0x000055b3bb006602 call_rcu_thread (qemu-system-x86_64 + 0x8cf602) + #3 0x000055b3baffbb78 qemu_thread_start (qemu-system-x86_64 + 0x8c4b78) + #4 0x00007f1fbbba4134 start_thread (libc.so.6 + 0x89134) + #5 0x00007f1fbbc247dc __clone3 (libc.so.6 + 0x1097dc) + + Stack trace of thread 249329: + #0 0x00007f1fbbba0e96 __futex_abstimed_wait_common64 (libc.so.6 + 0x85e96) + #1 0x00007f1fbbba3558 __pthread_cond_wait_common (libc.so.6 + 0x88558) + #2 0x000055b3baffc68b qemu_cond_wait_impl (qemu-system-x86_64 + 0x8c568b) + #3 0x000055b3baa88f2b vnc_worker_thread_loop (qemu-system-x86_64 + 0x351f2b) + #4 0x000055b3baa89bc8 vnc_worker_thread (qemu-system-x86_64 + 0x352bc8) + #5 0x000055b3baffbb78 qemu_thread_start (qemu-system-x86_64 + 0x8c4b78) + #6 0x00007f1fbbba4134 start_thread (libc.so.6 + 0x89134) + #7 0x00007f1fbbc247dc __clone3 (libc.so.6 + 0x1097dc) + + Stack trace of thread 3982758: + #0 0x00007f1fbbba0e96 __futex_abstimed_wait_common64 (libc.so.6 + 0x85e96) + #1 0x00007f1fbbba383c __pthread_cond_wait_common (libc.so.6 + 0x8883c) + #2 0x000055b3baffbd01 qemu_cond_timedwait_ts (qemu-system-x86_64 + 0x8c4d01) + #3 0x000055b3baffc8a0 qemu_cond_timedwait_impl (qemu-system-x86_64 + 0x8c58a0) + #4 0x000055b3bb0110d4 worker_thread (qemu-system-x86_64 + 0x8da0d4) + #5 0x000055b3baffbb78 qemu_thread_start (qemu-system-x86_64 + 0x8c4b78) + #6 0x00007f1fbbba4134 start_thread (libc.so.6 + 0x89134) + #7 0x00007f1fbbc247dc __clone3 (libc.so.6 + 0x1097dc) + + Stack trace of thread 969111: + #0 0x00007f1fbbba0e96 __futex_abstimed_wait_common64 (libc.so.6 + 0x85e96) + #1 0x00007f1fbbba383c __pthread_cond_wait_common (libc.so.6 + 0x8883c) + #2 0x000055b3baffbd01 qemu_cond_timedwait_ts (qemu-system-x86_64 + 0x8c4d01) + #3 0x000055b3baffc8a0 qemu_cond_timedwait_impl (qemu-system-x86_64 + 0x8c58a0) + #4 0x000055b3bb0110d4 worker_thread (qemu-system-x86_64 + 0x8da0d4) + #5 0x000055b3baffbb78 qemu_thread_start (qemu-system-x86_64 + 0x8c4b78) + #6 0x00007f1fbbba4134 start_thread (libc.so.6 + 0x89134) + #7 0x00007f1fbbc247dc __clone3 (libc.so.6 + 0x1097dc) + + Stack trace of thread 969113: + #0 0x00007f1fbbba0e96 __futex_abstimed_wait_common64 (libc.so.6 + 0x85e96) + #1 0x00007f1fbbba383c __pthread_cond_wait_common (libc.so.6 + 0x8883c) + #2 0x000055b3baffbd01 qemu_cond_timedwait_ts (qemu-system-x86_64 + 0x8c4d01) + #3 0x000055b3baffc8a0 qemu_cond_timedwait_impl (qemu-system-x86_64 + 0x8c58a0) + #4 0x000055b3bb0110d4 worker_thread (qemu-system-x86_64 + 0x8da0d4) + #5 0x000055b3baffbb78 qemu_thread_start (qemu-system-x86_64 + 0x8c4b78) + #6 0x00007f1fbbba4134 start_thread (libc.so.6 + 0x89134) + #7 0x00007f1fbbc247dc __clone3 (libc.so.6 + 0x1097dc) + + Stack trace of thread 969114: + #0 0x00007f1fbbba0e96 __futex_abstimed_wait_common64 (libc.so.6 + 0x85e96) + #1 0x00007f1fbbba383c __pthread_cond_wait_common (libc.so.6 + 0x8883c) + #2 0x000055b3baffbd01 qemu_cond_timedwait_ts (qemu-system-x86_64 + 0x8c4d01) + #3 0x000055b3baffc8a0 qemu_cond_timedwait_impl (qemu-system-x86_64 + 0x8c58a0) + #4 0x000055b3bb0110d4 worker_thread (qemu-system-x86_64 + 0x8da0d4) + #5 0x000055b3baffbb78 qemu_thread_start (qemu-system-x86_64 + 0x8c4b78) + #6 0x00007f1fbbba4134 start_thread (libc.so.6 + 0x89134) + #7 0x00007f1fbbc247dc __clone3 (libc.so.6 + 0x1097dc) + + Stack trace of thread 969112: + #0 0x00007f1fbbba0e96 __futex_abstimed_wait_common64 (libc.so.6 + 0x85e96) + #1 0x00007f1fbbba383c __pthread_cond_wait_common (libc.so.6 + 0x8883c) + #2 0x000055b3baffbd01 qemu_cond_timedwait_ts (qemu-system-x86_64 + 0x8c4d01) + #3 0x000055b3baffc8a0 qemu_cond_timedwait_impl (qemu-system-x86_64 + 0x8c58a0) + #4 0x000055b3bb0110d4 worker_thread (qemu-system-x86_64 + 0x8da0d4) + #5 0x000055b3baffbb78 qemu_thread_start (qemu-system-x86_64 + 0x8c4b78) + #6 0x00007f1fbbba4134 start_thread (libc.so.6 + 0x89134) + #7 0x00007f1fbbc247dc __clone3 (libc.so.6 + 0x1097dc) + + Stack trace of thread 4165267: + #0 0x00007f1fbbba0e96 __futex_abstimed_wait_common64 (libc.so.6 + 0x85e96) + #1 0x00007f1fbbba383c __pthread_cond_wait_common (libc.so.6 + 0x8883c) + #2 0x000055b3baffbd01 qemu_cond_timedwait_ts (qemu-system-x86_64 + 0x8c4d01) + #3 0x000055b3baffc8a0 qemu_cond_timedwait_impl (qemu-system-x86_64 + 0x8c58a0) + #4 0x000055b3bb0110d4 worker_thread (qemu-system-x86_64 + 0x8da0d4) + #5 0x000055b3baffbb78 qemu_thread_start (qemu-system-x86_64 + 0x8c4b78) + #6 0x00007f1fbbba4134 start_thread (libc.so.6 + 0x89134) + #7 0x00007f1fbbc247dc __clone3 (libc.so.6 + 0x1097dc) + + Stack trace of thread 969116: + #0 0x00007f1fbbba0e96 __futex_abstimed_wait_common64 (libc.so.6 + 0x85e96) + #1 0x00007f1fbbba383c __pthread_cond_wait_common (libc.so.6 + 0x8883c) + #2 0x000055b3baffbd01 qemu_cond_timedwait_ts (qemu-system-x86_64 + 0x8c4d01) + #3 0x000055b3baffc8a0 qemu_cond_timedwait_impl (qemu-system-x86_64 + 0x8c58a0) + #4 0x000055b3bb0110d4 worker_thread (qemu-system-x86_64 + 0x8da0d4) + #5 0x000055b3baffbb78 qemu_thread_start (qemu-system-x86_64 + 0x8c4b78) + #6 0x00007f1fbbba4134 start_thread (libc.so.6 + 0x89134) + #7 0x00007f1fbbc247dc __clone3 (libc.so.6 + 0x1097dc) + + Stack trace of thread 969115: + #0 0x00007f1fbbba0e96 __futex_abstimed_wait_common64 (libc.so.6 + 0x85e96) + #1 0x00007f1fbbba383c __pthread_cond_wait_common (libc.so.6 + 0x8883c) + #2 0x000055b3baffbd01 qemu_cond_timedwait_ts (qemu-system-x86_64 + 0x8c4d01) + #3 0x000055b3baffc8a0 qemu_cond_timedwait_impl (qemu-system-x86_64 + 0x8c58a0) + #4 0x000055b3bb0110d4 worker_thread (qemu-system-x86_64 + 0x8da0d4) + #5 0x000055b3baffbb78 qemu_thread_start (qemu-system-x86_64 + 0x8c4b78) + #6 0x00007f1fbbba4134 start_thread (libc.so.6 + 0x89134) + #7 0x00007f1fbbc247dc __clone3 (libc.so.6 + 0x1097dc) + ELF object binary architecture: AMD x86-64` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2337 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2337 new file mode 100644 index 000000000..f43e5ab7f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2337 @@ -0,0 +1,62 @@ +Os boot issues on 9p filesystem due to unix domain sockets open failure +Description of problem: +Unix filesystem API is broken, unix domain socket special files return an error at open() +Steps to reproduce: +Simple script. Tries to use netcat to get data through a local unix domain socket file +``` +#!/bin/bash + +# Cleanup target dir +[ -d ./target ] && rm -rf target +mkdir target + +# Add configuration updates +mkdir -p ./target/etc/initramfs-tools/ +echo 9p >> ./target/etc/initramfs-tools/modules +echo 9pnet_virtio >> ./target/etc/initramfs-tools/modules + +# Add the test script +cat > ./target/test_init << EOF +#!/bin/bash + +echo "Test for unix domain sockets" + +nc -Ul /socket & +sleep 1 +echo "Sockets work" | nc -UN /socket || echo "Sockets fail" + +echo o > /proc/sysrq-trigger +sleep 999 +EOF +chmod 700 ./target/test_init + +# Create an Ubuntu 23.10 around it +echo "Creating Ubuntu target OS" +debootstrap --variant=minbase\ + --include=udev,kmod,initramfs-tools,systemd,netcat-openbsd,linux-image-generic \ + --exclude=man,bash-completion \ + mantic ./target > /dev/null || exit 1 + +# Run the test in 9p forwarded filesystem +echo "Running OS in qemu" +qemu-system-s390x \ + -m 8192 \ + -smp 4 \ + -nodefaults -nographic -no-reboot -no-user-config \ + -kernel ./target/boot/vmlinuz \ + -initrd ./target/boot/initrd.img \ + -append 'root=fsRoot rw rootfstype=9p rootflags=trans=virtio,version=9p2000.L,msize=512000,cache=mmap,posixacl console=ttysclp0 init=/test_init quiet' \ + -fsdev local,security_model=passthrough,multidevs=remap,id=fsdev-fsRoot,path=./target \ + -device virtio-9p-pci,id=fsRoot,fsdev=fsdev-fsRoot,mount_tag=fsRoot \ + -device virtio-serial-ccw -device sclpconsole,chardev=console \ + -chardev stdio,id=console,signal=off +``` +Additional information: +Test output: +``` +Test for unix domain sockets +qemu-system-s390x: 9p: broken or compromised client detected; attempt to open special file (i.e. neither regular file, nor directory) +nc: No such device or address +nc: /socket: No such file or directory +Sockets fail +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2338 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2338 new file mode 100644 index 000000000..3185f3197 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2338 @@ -0,0 +1 @@ +(Feature request) Implement the "grab-on-hover=on" CLI option on the SDL frontend diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2339 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2339 new file mode 100644 index 000000000..3a7eec320 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2339 @@ -0,0 +1 @@ +VM Crash is observed while deploying an ubuntu VM with OS version 18.04 on host with ubuntu version 24.04 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/234 b/gitlab/issues_text/target_missing/host_missing/accel_missing/234 new file mode 100644 index 000000000..f726cfd27 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/234 @@ -0,0 +1 @@ +Failure building with clang-10 and libssh diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2341 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2341 new file mode 100644 index 000000000..f1678c065 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2341 @@ -0,0 +1,32 @@ +IVSHMEM device doesn't work for sharing memory with virtiofsd +Description of problem: +Trying to share a folder on the host to the guest with `virtiofsd` using the `ivshmem-plain` device doesn't work (for memory sharing), while using a NUMA node (with `-numa node,memdev=mem`) works just fine. +Steps to reproduce: +1. Install `virtiofsd` +2. Run `/usr/libexec/virtiofsd --socket-path=/tmp/vhostqemu --shared-dir=$HOME --cache always` as a regular user (or with another shared directory, it doesn't matter) +3. Run QEMU with the aforementioned command line as a regular user +4. Wait a bit for the OS to load and `virtiofsd` should error out +Additional information: +`virtiofsd` logs: +``` +[2024-05-09T19:49:15Z WARN virtiofsd::sandbox] Couldn't set the process uid as root: -1 +[2024-05-09T19:49:15Z WARN virtiofsd::sandbox] Couldn't set the process gid as root: -1 +[2024-05-09T19:49:15Z INFO virtiofsd] Waiting for vhost-user socket connection... +[2024-05-09T19:49:16Z INFO virtiofsd] Client connected, servicing requests +[2024-05-09T19:49:22Z ERROR virtiofsd] Waiting for daemon failed: HandleRequest(ReqHandlerError(Custom { kind: Other, error: MissingMemoryMapping })) +``` + +QEMU logs (after virtiofsd errors out and exits): +``` +qemu: Failed to read msg header. Read -1 instead of 12. Original request 0. +qemu: Failed to write msg. Wrote -1 instead of 20. +qemu: vhost VQ 1 ring restore failed: -22: Invalid argument (22) +qemu: Failed to set msg fds. +qemu: vhost VQ 0 ring restore failed: -22: Invalid argument (22) +qemu: Error starting vhost: 5 +qemu: Failed to set msg fds. +qemu: vhost_set_vring_call failed 22 +qemu: Failed to set msg fds. +qemu: vhost_set_vring_call failed 22 +qemu: Unexpected end-of-file before all data were read +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2342 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2342 new file mode 100644 index 000000000..d0a857539 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2342 @@ -0,0 +1 @@ +DEREF_OF_NULL.RET in qdev-clock.c diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2343 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2343 new file mode 100644 index 000000000..f3e2b97de --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2343 @@ -0,0 +1,31 @@ +pflash write timeout u-boot@qemu-system-aarch64 +Description of problem: +Emulating the write into flash of environment variables within U-boot is not possible anymore. This works natively in Fedora 39 which has the 8.1.3 qemu version. Stopped working after transitioning to Fedora 40 which currently comes with 8.2.2, also doesn't work with Debian 12 which has 7.2.9. + +The write fails with the following message: + +``` +=> saveenv +Saving Environment to Flash... Un-Protected 2 sectors +Erasing Flash... +.. done +Erased 2 sectors +Writing to Flash... pflash_write: Write to buffer emulation is flawed +pflash_write: Write to buffer emulation is flawed +pflash_write: Write to buffer emulation is flawed +Flash buffer write timeout at address 4000000 data ffffffffb64f6361 +Timeout writing to Flash +Protected 2 sectors +Failed (1) +``` +Steps to reproduce: +1. Download or build u-boot for aarch64 qemu. You can extract from u-boot-qemu debian package https://packages.debian.org/unstable/u-boot-qemu . +2. `truncate -s 64m varstore.img` +3. `qemu-system-aarch64 -machine virt -cpu cortex-a35 -nographic -smp 2 -m 1G -bios u-boot.bin -drive if=pflash,format=raw,file=varstore.img,readonly=off,index=1 -d guest_errors,unimp` +Additional information: +After building versions 8.1.3 and 8.1.4 I found both were working fine regartheless the host OS, the issue was introduced in 8.1.5. +After inspecting commits history I drop the following commit [hw/pflash: implement update buffer for block writes (hash:fcc79f2e09550b0461792491965fe202ed2219ae)](https://gitlab.com/qemu-project/qemu/-/commit/fcc79f2e09550b0461792491965fe202ed2219ae) rebuilt and the issue was gone. +I then recheck all non working versions and both versions 8.2.2 and 7.2.9 also have this commit, this explains why it also doesn't work. +I attached a trace running with v8.1.5 and v8.1.5 with drop commit. +[v8.1.5.log](/uploads/04aa0e24e1e16f6bdf29a6e6be587ba1/v8.1.5.log) +[v8.1.5-drop-fcc79f2e.log](/uploads/206fe958ab78c12542fda3764df978da/v8.1.5-drop-fcc79f2e.log) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2344 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2344 new file mode 100644 index 000000000..b1b07abf8 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2344 @@ -0,0 +1,45 @@ +Plugin scoreboard deadlock (plugin.lock vs start_exclusive) +Description of problem: +Deadlock + +In frame 9 the thread grabs the plugin.lock, and starts to wait for other cpus to enter exclusive idle. +``` +#7 0x00005555555a1295 in start_exclusive () at ../hw/core/cpu-common.c:199 +#8 plugin_grow_scoreboards__locked (cpu=0x7fff0c2b4720) at ../plugins/core.c:238 +#9 qemu_plugin_vcpu_init_hook (cpu=0x7fff0c2b4720) at ../plugins/core.c:258 +``` + +The other thread just finished a TB and do the callback to the plugin, so it will not become exclusive idle until it finishes. +That callback tries to create a new 'scoreboard', but plugin.lock is already taken. +``` +#7 qemu_plugin_scoreboard_new (element_size=element_size@entry=8) at ../plugins/api.c:464 +#8 0x00007ffff7fb973d in vcpu_tb_trans (id=<optimized out>, tb=0x555555858d60) at /home/rehn/source/qemu/contrib/plugins/hotblocks.c:125 +#9 0x00005555557394f1 in qemu_plugin_tb_trans_cb (cpu=<optimized out>, tb=0x555555858d60) at ../plugins/core.c:418 +``` + +Locally I'm using this fix, reverse order so we enter exclusive idle before grabbing the plugin.lock: +``` +diff --git a/plugins/core.c b/plugins/core.c +index 1e58a57bf1..0e41c4ef22 100644 +--- a/plugins/core.c ++++ b/plugins/core.c +@@ -236,4 +236,2 @@ static void plugin_grow_scoreboards__locked(CPUState *cpu) + +- /* cpus must be stopped, as tb might still use an existing scoreboard. */ +- start_exclusive(); + struct qemu_plugin_scoreboard *score; +@@ -244,3 +242,2 @@ static void plugin_grow_scoreboards__locked(CPUState *cpu) + tb_flush(cpu); +- end_exclusive(); + } +@@ -250,2 +247,4 @@ void qemu_plugin_vcpu_init_hook(CPUState *cpu) + bool success; ++ /* cpus must be stopped, as tb might still use an existing scoreboard. */ ++ start_exclusive(); + +@@ -259,2 +258,3 @@ void qemu_plugin_vcpu_init_hook(CPUState *cpu) + qemu_rec_mutex_unlock(&plugin.lock); ++ end_exclusive(); +``` +Steps to reproduce: +Run command a few times and get 'unlucky' diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2345 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2345 new file mode 100644 index 000000000..fea5802e2 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2345 @@ -0,0 +1,48 @@ +Undefined behavior error: call to function qemu_mutex_lock through pointer to incorrect function type +Description of problem: +When compiling QEMU with: + +``` +./configure --cc=clang --extra-cflags=-fsanitize=undefined --extra-cflags=-fno-sanitize-recover=undefined --target-list=x86_64-softmmu +``` + +on a system that has Clang v17 or newer (e.g. on Fedora 39 or Fedora 40), the QEMU binary abort with an undefined behavior error: + +``` +$ ./qemu-system-x86_64 +include/qemu/lockable.h:95:5: runtime error: call to function qemu_mutex_lock through pointer to incorrect function type 'void (*)(void *)' +include/qemu/thread.h:122:5: note: qemu_mutex_lock defined here +SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior include/qemu/lockable.h:95:5 +``` + +Or for example when running ``make check-unit`` : + +``` + 97/103 qemu:unit / test-yank ERROR 0.13s killed by signal 6 SIGABRT +>>> G_TEST_BUILDDIR=/tmp/qemu-ubsan/tests/unit ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 MALLOC_PERTURB_=201 G_TEST_SRCDIR=~/qemu/tests/unit /tmp/qemu-ubsan/tests/unit/test-yank --tap -k +――――――――――――――――――――――――― ✀ ――――――――――――――――――――――――――――――――――――――――― +stderr: +include/qemu/lockable.h:95:5: runtime error: call to function qemu_mutex_lock through pointer to incorrect function type 'void (*)(void *)' +include/qemu/thread.h:122:5: note: qemu_mutex_lock defined here + #0 0x55753123f8b9 in qemu_lockable_lock include/qemu/lockable.h:95:5 + #1 0x55753123f8b9 in qemu_lockable_auto_lock include/qemu/lockable.h:105:5 + #2 0x55753123f8b9 in qmp_query_yank util/yank.c:184:5 + #3 0x5575311a35fe in is_yank_instance_registered tests/unit/test-yank.c:43:12 + #4 0x5575311a35fe in char_change_test tests/unit/test-yank.c:128:5 + #5 0x7f7f0a8cfbbf (/lib64/libglib-2.0.so.0+0x8bbbf) (BuildId: 795136df3faa85587229ddc59d709f81d6f697df) + #6 0x7f7f0a8cfb2f (/lib64/libglib-2.0.so.0+0x8bb2f) (BuildId: 795136df3faa85587229ddc59d709f81d6f697df) + #7 0x7f7f0a8cfb2f (/lib64/libglib-2.0.so.0+0x8bb2f) (BuildId: 795136df3faa85587229ddc59d709f81d6f697df) + #8 0x7f7f0a8cfb2f (/lib64/libglib-2.0.so.0+0x8bb2f) (BuildId: 795136df3faa85587229ddc59d709f81d6f697df) + #9 0x7f7f0a8d00c9 in g_test_run_suite (/lib64/libglib-2.0.so.0+0x8c0c9) (BuildId: 795136df3faa85587229ddc59d709f81d6f697df) + #10 0x7f7f0a8d015f in g_test_run (/lib64/libglib-2.0.so.0+0x8c15f) (BuildId: 795136df3faa85587229ddc59d709f81d6f697df) + #11 0x5575311a336f in main tests/unit/test-yank.c:248:12 + #12 0x7f7f0a32d087 in __libc_start_call_main (/lib64/libc.so.6+0x2a087) (BuildId: b098f1c75a76548bb230d8f551eae07a2aeccf06) + #13 0x7f7f0a32d14a in __libc_start_main@GLIBC_2.2.5 (/lib64/libc.so.6+0x2a14a) (BuildId: b098f1c75a76548bb230d8f551eae07a2aeccf06) + #14 0x557531178d64 in _start (/tmp/qemu-ubsan/tests/unit/test-yank+0x77d64) (BuildId: 0bb470b7accec26b684d1c7e941239d31396604e) + +SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior include/qemu/lockable.h:95:5 + +(test program exited with status code -6) +``` + +The way we abuse the (void *) parameter of QemuLockUnlockFunc seems to be undefined behavior, which could likely also trigger issues with CFI or certain compilers/architectures like emscripten, so we should try to avoid this. See also https://github.com/systemd/systemd/issues/29972 or https://github.com/python/cpython/issues/111178 for discussions in other projects. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2346 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2346 new file mode 100644 index 000000000..ab236b57a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2346 @@ -0,0 +1,72 @@ +Undefined behavior error: call to function visit_type_InetSocketAddress_members through pointer to incorrect function type +Description of problem: +When compiling QEMU with --extra-cflags=-fsanitize=undefined and --extra-cflags=-fno-sanitize-recover=undefined on a system that has Clang v17 or newer (e.g. on Fedora 39 or Fedora 40), the unit tests abort with an undefined behavior error. +Steps to reproduce: +1. ``./configure --cc=clang --extra-cflags=-fsanitize=undefined --extra-cflags=-fno-sanitize-recover=undefined --target-list=x86_64-softmmu`` +2. ``make -j$(nproc)`` +3. ``make check-unit`` +Additional information: +test-io-channel-socket aborts with: + +``` + 74/103 qemu:unit / test-io-channel-socket ERROR 0.15s killed by signal 6 SIGABRT +>>> G_TEST_BUILDDIR=/tmp/qemu-ubsan/tests/unit ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 MALLOC_PERTURB_=163 G_TEST_SRCDIR=tests/unit /tmp/qemu-ubsan/tests/unit/test-io-channel-socket --tap -k +―――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――― ✀ ―――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――― +stderr: +qapi/qapi-clone-visitor.c:188:5: runtime error: call to function visit_type_SocketAddress through pointer to incorrect function type 'bool (*)(struct Visitor *, const char *, void **, struct Error **)' +/tmp/qemu-ubsan/qapi/qapi-visit-sockets.c:487: note: visit_type_SocketAddress defined here + #0 0x5642aa2f7f3b in qapi_clone qapi/qapi-clone-visitor.c:188:5 + #1 0x5642aa2c8ce5 in qio_channel_socket_listen_async io/channel-socket.c:285:18 + #2 0x5642aa2b8903 in test_io_channel_setup_async tests/unit/test-io-channel-socket.c:116:5 + #3 0x5642aa2b8204 in test_io_channel tests/unit/test-io-channel-socket.c:179:9 + #4 0x5642aa2b8129 in test_io_channel_ipv4 tests/unit/test-io-channel-socket.c:323:5 + #5 0x7f01212c0bbf (/lib64/libglib-2.0.so.0+0x8bbbf) (BuildId: 795136df3faa85587229ddc59d709f81d6f697df) + #6 0x7f01212c0b2f (/lib64/libglib-2.0.so.0+0x8bb2f) (BuildId: 795136df3faa85587229ddc59d709f81d6f697df) + #7 0x7f01212c0b2f (/lib64/libglib-2.0.so.0+0x8bb2f) (BuildId: 795136df3faa85587229ddc59d709f81d6f697df) + #8 0x7f01212c0b2f (/lib64/libglib-2.0.so.0+0x8bb2f) (BuildId: 795136df3faa85587229ddc59d709f81d6f697df) + #9 0x7f01212c10c9 in g_test_run_suite (/lib64/libglib-2.0.so.0+0x8c0c9) (BuildId: 795136df3faa85587229ddc59d709f81d6f697df) + #10 0x7f01212c115f in g_test_run (/lib64/libglib-2.0.so.0+0x8c15f) (BuildId: 795136df3faa85587229ddc59d709f81d6f697df) + #11 0x5642aa2b72ec in main tests/unit/test-io-channel-socket.c:613:12 + #12 0x7f0120d2d087 in __libc_start_call_main (/lib64/libc.so.6+0x2a087) (BuildId: b098f1c75a76548bb230d8f551eae07a2aeccf06) + #13 0x7f0120d2d14a in __libc_start_main@GLIBC_2.2.5 (/lib64/libc.so.6+0x2a14a) (BuildId: b098f1c75a76548bb230d8f551eae07a2aeccf06) + #14 0x5642aa28cd04 in _start (tests/unit/test-io-channel-socket+0x69d04) (BuildId: eeaee2b8d62ce3aa77ab8b447916a40defd78dc6) + +SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior qapi/qapi-clone-visitor.c:188:5 + +(test program exited with status code -6) +``` + +And ``test-char`` aborts with: + +``` + 99/103 qemu:unit / test-char ERROR 0.12s killed by signal 6 SIGABRT +>>> G_TEST_BUILDDIR=/tmp/qemu-ubsan/tests/unit ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 MALLOC_PERTURB_=197 G_TEST_SRCDIR=tests/unit /tmp/qemu-ubsan/tests/unit/test-char --tap -k +―――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――― ✀ ―――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――― +stderr: +qapi/qapi-clone-visitor.c:202:5: runtime error: call to function visit_type_InetSocketAddress_members through pointer to incorrect function type 'bool (*)(struct Visitor *, void *, struct Error **)' +/tmp/qemu-ubsan/qapi/qapi-visit-sockets.c:65: note: visit_type_InetSocketAddress_members defined here + #0 0x55ee1d20ad60 in qapi_clone_members qapi/qapi-clone-visitor.c:202:5 + #1 0x55ee1d24a993 in socket_address_flattenutil/qemu-sockets.c + #2 0x55ee1d1f26f6 in qmp_chardev_open_udp chardev/char-udp.c:199:34 + #3 0x55ee1d1f5254 in qemu_char_open chardev/char.c:271:9 + #4 0x55ee1d1f5254 in chardev_new chardev/char.c:968:5 + #5 0x55ee1d1f45fd in qemu_chardev_new chardev/char.c:998:11 + #6 0x55ee1d1f45fd in qemu_chr_new_from_opts chardev/char.c:657:11 + #7 0x55ee1d1f49ac in qemu_chr_new_noreplay chardev/char.c:703:11 + #8 0x55ee1d1f4aed in qemu_chr_new_permit_mux_mon chardev/char.c:731:11 + #9 0x55ee1d1b45b8 in char_udp_test_internal tests/unit/test-char.c:590:15 + #10 0x7f3dd421abbf (/lib64/libglib-2.0.so.0+0x8bbbf) (BuildId: 795136df3faa85587229ddc59d709f81d6f697df) + #11 0x7f3dd421ab2f (/lib64/libglib-2.0.so.0+0x8bb2f) (BuildId: 795136df3faa85587229ddc59d709f81d6f697df) + #12 0x7f3dd421b0c9 in g_test_run_suite (/lib64/libglib-2.0.so.0+0x8c0c9) (BuildId: 795136df3faa85587229ddc59d709f81d6f697df) + #13 0x7f3dd421b15f in g_test_run (/lib64/libglib-2.0.so.0+0x8c15f) (BuildId: 795136df3faa85587229ddc59d709f81d6f697df) + #14 0x55ee1d1af6bd in main tests/unit/test-char.c:1579:12 + #15 0x7f3dd3c3d087 in __libc_start_call_main (/lib64/libc.so.6+0x2a087) (BuildId: b098f1c75a76548bb230d8f551eae07a2aeccf06) + #16 0x7f3dd3c3d14a in __libc_start_main@GLIBC_2.2.5 (/lib64/libc.so.6+0x2a14a) (BuildId: b098f1c75a76548bb230d8f551eae07a2aeccf06) + #17 0x55ee1d184e34 in _start (/tmp/qemu-ubsan/tests/unit/test-char+0x78e34) (BuildId: afdf2ec9875e3011d3ff99174ec137dc79fff74e) + +SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior .qapi/qapi-clone-visitor.c:202:5 + +(test program exited with status code -6) +``` + +This undefined behavior could likely also trigger issues with CFI or certain compilers/architectures like emscripten, so we should try to avoid this. See also https://github.com/systemd/systemd/issues/29972 or https://github.com/python/cpython/issues/111178 for discussions in other projects, and https://gitlab.com/qemu-project/qemu/-/issues/2345 for a similar problem in the QEMU lockable code. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2347 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2347 new file mode 100644 index 000000000..3692cae97 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2347 @@ -0,0 +1,9 @@ +Grab Input not working only for Windows key +Description of problem: +When Input Grabbing is enabled (as seen in the menu and the Qemu window title itself), a press on the Windows key will also send that press to the host system (Arch / KDE). + +I expected all inputs to be grabbed and stay within the VM. +Steps to reproduce: +1. Open a QEMU instance in a Arch / KDE host (not fullscreen) +2. Focus the instance and enable Input Grabbing (Ctrl + Alt + G) +3. Press the Windows key diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2348 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2348 new file mode 100644 index 000000000..d17103246 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2348 @@ -0,0 +1,7 @@ +Grabbing is not possible with menu-mode disabled +Description of problem: +When starting a Qemu and bringing it into Focus, I expected Ctrl + Alt + g to enable Input Grab mode. This does not occur when the menu-bar is hidden. It does occur when the menu-bar is visible. +Steps to reproduce: +1. Open a QEMU instance in a Arch / KDE host (not fullscreen) +2. Focus the instance and attempt to enable Input Grabbing (Ctrl + Alt + G) +3. Observe that Input Grab Mode is not toggled diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2349 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2349 new file mode 100644 index 000000000..844e3346d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2349 @@ -0,0 +1,12 @@ +keyboard (and mouse) not working in macOS guest +Description of problem: +keyboard not working after exiting EFI environment. it works in the OpenCore boot picker, but not in the recovery system. The mouse can work by forcing the PS2 controller and pause/resume the VM. See here for more details: +https://github.com/utmapp/UTM/issues/5240#issuecomment-2112477131 +Tried adding ps2 kexts, but qemu USB keyboard, mouse and tablet do not attach to the AppleUSBEHCI bus. It works fine in Snow Leopard only as evident in the picture on the Github issue. +Steps to reproduce: +1.Install macOS guest Mavericks through Sierra using https://github.com/royalgraphx/LegacyOSXKVM/blob/main/info/CONVERSIONS.md +2.https://github.com/kholia/OSX-KVM/blob/master/OpenCore-Boot-macOS.sh +3. +Additional information: +[command.txt](/uploads/3af8e5476833a1f869debc4fbfe97e84/command.txt) +[EFI.zip](/uploads/3f49054b496b19244ebb111cf07ed05a/EFI.zip) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/235 b/gitlab/issues_text/target_missing/host_missing/accel_missing/235 new file mode 100644 index 000000000..07a2b0447 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/235 @@ -0,0 +1 @@ +atomic failure linking with --enable-sanitizers on 32-bit Linux hosts diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2350 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2350 new file mode 100644 index 000000000..538515f57 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2350 @@ -0,0 +1,14 @@ +Incorrect RNG_CTRL and RNG_DATA_OUTPUT register offets for Aspeed AST2600 A3 +Description of problem: +hw/misc/aspeed_scu.c has the following lines: + +#define AST2600_RNG_CTRL TO_REG(0x524) +#define AST2600_RNG_DATA TO_REG(0x540) + +The Datasheet for the AST2600 A3 lists the offsets as 0x520 for RNG_CTRL and 0x524 for RNG_DATA. I can confirm that these addresses are correct on the hardware. I don't know if the offsets changed from a previous revision, but since qemu fills the SILICON_REV register with the AST2600_A3_SILICON_REV value for the AST2600, it makes sense to me that it would use the A3 register offsets. +Steps to reproduce: +1. +2. +3. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2353 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2353 new file mode 100644 index 000000000..bc271aa47 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2353 @@ -0,0 +1,56 @@ +linux-user: may map interpreter at address 0 with nonzero guest_base +Description of problem: +QEMU's user-mode emulation will, under certain conditions, map the ELF interpreter at guest address 0. This is not only a violation of Linux's policy never to map anything at the first page of any virtual address space, but also a cause of confusion (and segfaults) within certain libcs; though I only tested with musl. Musl [interprets a NULL base address](https://elixir.bootlin.com/musl/v1.2.4/source/ldso/dlstart.c#L105) as the dynamic linker being invoked directly, causing it to compute its base address incorrectly. + +The problem arises in `load_elf_image()`, which chooses a `load_addr` of 0 for the ELF interpreter (i.e. the musl dynamic loader). This is passed to `target_mmap()`. I do not know whether `target_mmap()` is meant to follow the POSIX rule that (in absence of `MAP_FIXED`) "All implementations interpret an *addr* value of 0 as granting the implementation complete freedom in selecting *pa*" or if 0 is requesting 0. + +QEMU's usermode mmap() implementation translates the guest address to a host address (this is effectively a no-op with `guest_base == 0`) and passes it along to the host Linux. This means that, when `guest_base == 0`, a NULL input address means "put it anywhere," but when `guest_base != 0`, NULL means "put it at (guest address) 0." +Steps to reproduce: +1. Download a rootfs of Alpine Linux AArch64. +2. Install `gcc` (with `apk add gcc`) in the rootfs. `gcc` is not compiled as PIC, making QEMU use a nonzero `guest_base`. +3. Attempt to run `gcc` within the rootfs via QEMU. +Additional information: +I am interested in submitting a MR that fixes this issue, but I do not know which of 4 possible solutions is preferred: + +1. Modify `load_elf_image()` to ensure that `load_addr` is never NULL. +2. Modify `target_mmap()` so that NULLs are passed to the kernel as NULLs. +3. Modify the guest<->host translation facilities (`g2h_untagged` et al) to translate NULL as NULL. Overwhelmingly, a NULL pointer semantically means "there is no pointer here" and not "a pointer to the zeroth address," so treating these as valid addresses in the translation functions is arguably going against the grain. +4. When a nonzero `guest_base` is selected, reserve the first page of the guest VA space, so that the host kernel cannot accidentally put anything there. + +Here is my local patch that implements item 2 above, which indeed stops the segfaults for me: +<details><summary>Patch</summary> + +```diff +diff --git a/linux-user/mmap.c b/linux-user/mmap.c +index be3b9a6..dad29ef 100644 +--- a/linux-user/mmap.c ++++ b/linux-user/mmap.c +@@ -559,7 +559,7 @@ static abi_long mmap_h_eq_g(abi_ulong start, abi_ulong len, + int host_prot, int flags, int page_flags, + int fd, off_t offset) + { +- void *p, *want_p = g2h_untagged(start); ++ void *p, *want_p = start ? g2h_untagged(start) : 0; + abi_ulong last; + + p = mmap(want_p, len, host_prot, flags, fd, offset); +@@ -609,7 +609,7 @@ static abi_long mmap_h_lt_g(abi_ulong start, abi_ulong len, int host_prot, + int mmap_flags, int page_flags, int fd, + off_t offset, int host_page_size) + { +- void *p, *want_p = g2h_untagged(start); ++ void *p, *want_p = start ? g2h_untagged(start) : 0; + off_t fileend_adj = 0; + int flags = mmap_flags; + abi_ulong last, pass_last; +@@ -739,7 +739,7 @@ static abi_long mmap_h_gt_g(abi_ulong start, abi_ulong len, + int flags, int page_flags, int fd, + off_t offset, int host_page_size) + { +- void *p, *want_p = g2h_untagged(start); ++ void *p, *want_p = start ? g2h_untagged(start) : 0; + off_t host_offset = offset & -host_page_size; + abi_ulong last, real_start, real_last; + bool misaligned_offset = false; +``` +</details> diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2354 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2354 new file mode 100644 index 000000000..e932389c8 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2354 @@ -0,0 +1,7 @@ +Compile error with In function ‘vhost_scsi_set_workers’: +Steps to reproduce: +1. ./configure +2. ./make +Additional information: +I suspect something is misconfigured on my system, but I followed the straighforward directions +for building and I am running stock Debian 12. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2357 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2357 new file mode 100644 index 000000000..2ba37462b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2357 @@ -0,0 +1,18 @@ +assert in dwc2 +Description of problem: +The following log reveals it: + +``` +ERROR:../hw/usb/hcd-dwc2.c:1131:dwc2_hsotg_read: code should not be reached +Bail out! ERROR:../hw/usb/hcd-dwc2.c:1131:dwc2_hsotg_read: code should not be reached +Aborted +``` +Steps to reproduce: +``` +cat << EOF | qemu-system-aarch64 -display \ +none -machine accel=qtest, -m 512M -machine raspi2b -m 1G -nodefaults \ +-usb -drive file=null-co://,if=none,format=raw,id=disk0 -device \ +usb-storage,port=1,drive=disk0 -qtest stdio +readl 0x3f980dfb +EOF +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2359 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2359 new file mode 100644 index 000000000..631d65f56 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2359 @@ -0,0 +1,32 @@ +assert in virtio-iommu +Description of problem: +The following log reveals it: + +``` +qemu-system-x86_64: qemu/hw/virtio/virtio-iommu.c:821: void virtio_iommu_handle_command(VirtIODevice *, VirtQueue *): Assertion `sz == output_size' failed. +Aborted +``` +Steps to reproduce: +``` +cat << EOF | \qemu-system-x86_64 \ +-display none -machine accel=qtest -m 512M -machine q35 -nodefaults \ +-device virtio-iommu -qtest stdio +outl 0xcf8 0x80000804 +outw 0xcfc 0x06 +outl 0xcf8 0x80000820 +outl 0xcfc 0xe0004000 +write 0x10000e 0x1 0x01 +write 0xe0004020 0x4 0x00001000 +write 0xe0004028 0x4 0x00101000 +write 0xe000401c 0x1 0x01 +write 0x106000 0x1 0x05 +write 0x100001 0x1 0x60 +write 0x100002 0x1 0x10 +write 0x100009 0x1 0x04 +write 0x10000c 0x1 0x01 +write 0x100018 0x1 0x04 +write 0x10001c 0x1 0x02 +write 0x101003 0x1 0x01 +write 0xe0007001 0x1 0x00 +EOF +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2362 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2362 new file mode 100644 index 000000000..5c2d9f3d8 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2362 @@ -0,0 +1,63 @@ +short packets dropped by some network cards when using certain network backends +Description of problem: +Effectively a duplicate of https://gitlab.com/qemu-project/qemu/-/issues/2058 -- short ethernet packets (such as ARP packets) are discarded by various networking devices now. + +QEMU previously padded ethernet frames to 64 bytes when some network cards received them, but this was removed in various commits (140eae9c8f760e9260356fe9b56b802a02f0a9d2, c445f200ad241b443aa7a61a5381b26f56a18f0e, c58da33f2f8410b6f22cd1d33377dadf3a4d8867, 05db4476c5d25e437d807175de9f862bf5bf732c, 6d0d261dbfa6122e9b3bdcab7d934ca49f069c21, 63b901bfd30a0975bc326ba8527880fabac2e66, aee87b43fe2206acb8f5e334b42790df33a1cbad). + +969e50b61a285b0cc8dea6d4d2ade3f758d5ecc7 fixed SLIRP and TAP support, however the other various network backends (socket, dgram, vde, others) all have the same issue that some network cards will reject short packets. + +This does not fail on older versions of QEMU. +Steps to reproduce: +I have a python script that shows connecting two VMs of your choice using a socketpair connected to one of the affected NIC types (pcnet). If you start your OS (I used alpine linux as my test), and give each VM a unique IP address (eg, `ip addr add 192.168.0.1/24 dev eth0`), ping will fail to work. When you run tcpdump, you can see that the OS is sending out short ARP packets, but the other VM cannot see them. + +Using an older version of QEMU allows the ping to succeed. + +```python +#!/usr/bin/env python3 + +import argparse +import shlex +import socket +import subprocess + + +QEMU_PATH = "bin/qemu-system-x86_64" +NIC = "pcnet" +vnc = True + +if __name__ == "__main__": + parser = argparse.ArgumentParser() + parser.add_argument("qcow") + args = parser.parse_args() + + p1, p2 = socket.socketpair() + + qargs1 = [ + QEMU_PATH, "-snapshot", + "-m", "2G", + "-drive", f"file={args.qcow}", + "-device", f"{NIC},netdev=n,mac=52:54:00:00:00:01", + "-netdev", f"socket,id=n,fd={p1.fileno()}" + ] + if vnc: + qargs1 += ["-display", "vnc=:2"] + + print("+", shlex.join(qargs1)) + proc1 = subprocess.Popen(qargs1, pass_fds=[p1.fileno()]) + + qargs2 = [ + QEMU_PATH, "-snapshot", + "-m", "2G", + "-drive", f"file={args.qcow}", + "-device", f"{NIC},netdev=n,mac=52:54:00:00:00:02", + "-netdev", f"socket,id=n,fd={p2.fileno()}" + ] + if vnc: + qargs2 += ["-display", "vnc=:3"] + + print("+", shlex.join(qargs2)) + proc2 = subprocess.Popen(qargs2, pass_fds=[p2.fileno()]) + + proc1.wait() + proc2.wait() +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2363 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2363 new file mode 100644 index 000000000..2c9110dfe --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2363 @@ -0,0 +1 @@ +How can I enable MBI support in QEMU when running in KVM mode? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2364 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2364 new file mode 100644 index 000000000..896437744 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2364 @@ -0,0 +1 @@ +how to create two qemu instances on Windows11 so that they can access to each other in the same network? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2365 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2365 new file mode 100644 index 000000000..5ffcc6405 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2365 @@ -0,0 +1,8 @@ +[Regression v8.2/v9.0+] stuck at SeaBIOS for >30s with 100% CPU (1T) +Description of problem: +starting our Linux direct-kernel-boot VMs with same args on different hosts/hardware will get stuck at SeaBIOS for 30-60s with 100% 1T CPU load starting with v8.2 and also in v9.0. v9.0.0 and v8.2.3 - v8.1.5 is OK. To be clear, everything seems to be fine after that, though I did not do any benchmarks to compare performance. It just delays (re)booting by almost 1 minute, which is a shame, because before that update/regression it was instant and our VMs only take 4s to boot, which is now more like 60s. +Downgrading to v8.1 instantly fixes it, upgrading to v8.2/v9.0 instantly breaks it. +Steps to reproduce: +1. start VM with same args on different versions + +somehow if I save this bug with `/label ~"kind::Bug"` it disappears, so I'm unable to add/keep the label diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2366 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2366 new file mode 100644 index 000000000..7b6928035 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2366 @@ -0,0 +1 @@ +qemu8.2 check test failed diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2367 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2367 new file mode 100644 index 000000000..823bb9c48 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2367 @@ -0,0 +1 @@ +qemu8.2 check test failed diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2368 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2368 new file mode 100644 index 000000000..3b32fadd7 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2368 @@ -0,0 +1 @@ +Get get_maintainer.pl working with cover letter files diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2369 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2369 new file mode 100644 index 000000000..36571175d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2369 @@ -0,0 +1 @@ +qemu-img measure is incorrect when using discard-no-unref diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2370 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2370 new file mode 100644 index 000000000..970dafd28 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2370 @@ -0,0 +1,11 @@ +[RFE] vde support on Windows +Additional information: +A vdeswitch approach can be yet another solution for #2364 . +On Windows, other methods to simultaneously bridge local qemu-VMs and allow bridge members to connect to the internet are troublesome. +Compared to MAC/Linux wherein who use kernel provided bridging. Windows users don't have it easy. + +**Ref**: +1. qemu manual for ```netdev vde``` + https://qemu.readthedocs.io/_/downloads/en/v8.2.1/pdf/#page=75 +2. virtualsquare/VDE-2 github bug Can't understand how to get it running on Windows10 64 bit ```#28``` + https://github.com/virtualsquare/vde-2/issues/28 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2378 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2378 new file mode 100644 index 000000000..47cb66baf --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2378 @@ -0,0 +1,28 @@ +make install (meson?) removes needed RPATH for libslirp, making build on CentOS 9 difficult +Description of problem: +make install appears to remove need RPATH attributes from the binary, making it difficult if not impossible to install Qemu 9.0.0 on a CentOS 9 machine. + +I'm trying to build Qemu 9.0.0 on a CentOS 9 Stream machine where I do not have root. +The system ships with libslirp-4.4.0-7.el9.src.rpm which is libslirp 4.4.0, which is too old for Qemu. + +I checked out https://gitlab.freedesktop.org/slirp/libslirp.git which is 2 commits more recent than +libslirp 4.8.0. I installed this version in a separate directory. + +When I configure Qemu using PKG_CONFIG_PATH, it builds the correct executable with the correct RPATH. +readelf -d shows: + + 0x000000000000000f (RPATH) Library rpath: [/web/courses/cs4284/pintostools/lib64] + +which is the correct directory where the proper version of libslirp is located. + +However, when I run "make install" the RPATH attribute is removed. Thus, Qemu resorts to the system version, which is version 4.4 (with which Qemu won't run.) + +Meson's propensity to strip necessary RPATHs appears to be well-known, see, for instance, + +https://github.com/mesonbuild/meson/issues/4027 + +(There is a fix for at least some of the problems in 0.55.0 of Meson +https://mesonbuild.com/Release-notes-for-0-55-0.html +Qemu 9.0.0 appears to use Meson 1.2.3., but yet it still fails.) + +Work-around: don't use make install, copy it directly from the build directory to the destination directory. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2379 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2379 new file mode 100644 index 000000000..29707310e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2379 @@ -0,0 +1,126 @@ +virHashRemoveAll remove all jobs in priv->blockjobs but not set disk->priv->blockjob is null for qemuDomainObjPrivateDataClear and qemuProcessStop +Description of problem: +it call virHashRemoveAll to remove all jobs in priv->blockjobs but the disk privateData blockjob is not null for qemuDomainObjPrivateDataClear and qemuProcessStop. when virHashRemoveAll is caled, accessing priv->blockjob cause segfault in others. +Steps to reproduce: +1. virsh blockcopy testvm vda /root/disk/centos7-copy.qcow2 --wait --verbose --pivot + migrate disk of vm +2. poweoff in guest vm +3. libvirt core dump +Additional information: +--Type <RET> for more, q to quit, c to continue without paging-- + Program terminated with signal SIGSEGV, Segmentation fault. + #0 qemuBlockJobUnregister (vm=0x7f823c045050, job=0x7f827c03ca90) at ../src/qemu/qemu_blockjob.c:211 + 211 if (job == diskPriv->blockjob) { + [Current thread is 1 (Thread 0x7f8283640640 (LWP 152))] + (gdb) bt + #0 qemuBlockJobUnregister (vm=0x7f823c045050, job=0x7f827c03ca90) at ../src/qemu/qemu_blockjob.c:211 + #1 qemuBlockJobEventProcessConcluded (asyncJob=VIR_ASYNC_JOB_MIGRATION_OUT, vm=<optimized out>, driver=<optimized out>, + job=0x7f827c03ca90) at ../src/qemu/qemu_blockjob.c:1678 + #2 qemuBlockJobEventProcess (asyncJob=VIR_ASYNC_JOB_MIGRATION_OUT, job=0x7f827c03ca90, vm=<optimized out>, + driver=<optimized out>) at ../src/qemu/qemu_blockjob.c:1703 + #3 qemuBlockJobUpdate (vm=<optimized out>, job=0x7f827c03ca90, asyncJob=1) at ../src/qemu/qemu_blockjob.c:1756 + #4 0x00007f828050c95f in qemuMigrationSrcNBDStorageCopyReady (vm=0x7f823c045050, asyncJob=VIR_ASYNC_JOB_MIGRATION_OUT) + at ../src/qemu/qemu_migration.c:605 + #5 0x00007f8280518ca5 in qemuMigrationSrcNBDStorageCopy (flags=587, nbdURI=<optimized out>, tlsHostname=0x7f823c2b51d0 "", + tlsAlias=<optimized out>, dconn=0x7f823c014790, migrate_disks=0x7f827c006660, nmigrate_disks=2, speed=<optimized out>, + host=0x7f827c0156a0 "10.253.160.196", mig=0x7f827c027a30, vm=0x7f823c045050, driver=0x7f823c01ac40) + at ../src/qemu/qemu_migration.c:1202 + #6 qemuMigrationSrcRun (driver=0x7f823c01ac40, vm=0x7f823c045050, persist_xml=<optimized out>, cookiein=<optimized out>, + cookieinlen=<optimized out>, cookieout=0x7f828363f500, cookieoutlen=0x7f828363f4d4, flags=587, resource=1024, + spec=0x7f828363f330, dconn=0x7f823c014790, graphicsuri=0x0, nmigrate_disks=2, migrate_disks=0x7f827c006660, + migParams=0x7f827c00d890, nbdURI=0x0) at ../src/qemu/qemu_migration.c:4167 + #7 0x00007f828051a5dd in qemuMigrationSrcPerformNative (driver=0x7f823c01ac40, vm=0x7f823c045050, + persist_xml=0x7f827c020660 "<domain type=\"kvm\">\n <name>default_vm-8altm</name>\n <uuid>4a40fa64-fd9b-5078-8574-3ce5d0041d31</uuid>\n <metadata>\n <nodeagent xmlns=\"http://kubevirt.io/node-agent.io\">\n <vmid>13fb0e90-2930-"..., + uri=<optimized out>, + cookiein=0x7f827c0519e0 "<qemu-migration>\n <name>default_vm-8altm</name>\n <uuid>4a40fa64-fd9b-5078-8574-3ce5d0041d31</uuid>\n <hostname>ceasphere-node-1</hostname>\n <hostuuid>5b0a0842-6535-27c1-b2e7-89c4ac4fd785</hostuuid>"..., + cookieinlen=876, cookieout=0x7f828363f500, cookieoutlen=0x7f828363f4d4, flags=587, resource=1024, dconn=0x7f823c014790, + graphicsuri=0x0, nmigrate_disks=2, migrate_disks=0x7f827c006660, migParams=0x7f827c00d890, nbdURI=0x0) + at ../src/qemu/qemu_migration.c:4506 + #8 0x00007f828051c3e3 in qemuMigrationSrcPerformPeer2Peer3 (flags=<optimized out>, useParams=true, bandwidth=<optimized out>, + migParams=0x7f827c00d890, nbdURI=0x0, nbdPort=0, migrate_disks=0x7f827c006660, nmigrate_disks=<optimized out>, + listenAddress=<optimized out>, graphicsuri=0x0, uri=<optimized out>, dname=0x0, + persist_xml=0x7f827c020660 "<domain type=\"kvm\">\n <name>default_vm-8altm</name>\n <uuid>4a40fa64-fd9b-5078-8574-3ce5d0041d31</uuid>\n <metadata>\n <nodeagent xmlns=\"http://kubevirt.io/node-agent.io\">\n <vmid>13fb0e90-2930-"..., + xmlin=<optimized out>, vm=0x7f823c045050, + dconnuri=0x7f827c00c2b0 "qemu+unix:///system?socket=/var/run/kubevirt/migrationproxy/13fb0e90-2930-4f0b-959a-cc40346e7d64-source.sock", dconn=0x7f823c014790, sconn=0x7f826c00e890, driver=0x7f823c01ac40) at ../src/qemu/qemu_migration.c:4925 + #9 qemuMigrationSrcPerformPeer2Peer (v3proto=<synthetic pointer>, resource=<optimized out>, dname=0x0, flags=587, + migParams=0x7f827c00d890, nbdURI=0x0, nbdPort=0, migrate_disks=0x7f827c006660, nmigrate_disks=<optimized out>, + listenAddress=<optimized out>, graphicsuri=0x0, uri=<optimized out>, + dconnuri=0x7f827c00c2b0 "qemu+unix:///system?socket=/var/run/kubevirt/migrationproxy/13fb0e90-2930-4f0b-959a-cc40346e7d64-source.sock", + --Type <RET> for more, q to quit, c to continue without paging-- + persist_xml=0x7f827c020660 "<domain type=\"kvm\">\n <name>default_vm-8altm</name>\n <uuid>4a40fa64-fd9b-5078-8574-3ce5d0041d31</uuid>\n <metadata>\n <nodeagent xmlns=\"http://kubevirt.io/node-agent.io\">\n <vmid>13fb0e90-2930-"..., + xmlin=<optimized out>, vm=0x7f823c045050, sconn=0x7f826c00e890, driver=0x7f823c01ac40) at ../src/qemu/qemu_migration.c:5230 + #10 qemuMigrationSrcPerformJob (driver=0x7f823c01ac40, conn=0x7f826c00e890, vm=0x7f823c045050, xmlin=<optimized out>, + persist_xml=0x7f827c020660 "<domain type=\"kvm\">\n <name>default_vm-8altm</name>\n <uuid>4a40fa64-fd9b-5078-8574-3ce5d0041d31</uuid>\n <metadata>\n <nodeagent xmlns=\"http://kubevirt.io/node-agent.io\">\n <vmid>13fb0e90-2930-"..., + dconnuri=0x7f827c00c2b0 "qemu+unix:///system?socket=/var/run/kubevirt/migrationproxy/13fb0e90-2930-4f0b-959a-cc40346e7d64-source.sock", uri=<optimized out>, graphicsuri=<optimized out>, listenAddress=<optimized out>, nmigrate_disks=<optimized out>, + migrate_disks=<optimized out>, nbdPort=0, nbdURI=<optimized out>, migParams=<optimized out>, cookiein=<optimized out>, + cookieinlen=0, cookieout=<optimized out>, cookieoutlen=<optimized out>, flags=<optimized out>, dname=<optimized out>, + resource=<optimized out>, v3proto=<optimized out>) at ../src/qemu/qemu_migration.c:5307 + #11 0x00007f828051cce7 in qemuMigrationSrcPerform (driver=0x7f823c01ac40, conn=0x7f826c00e890, vm=0x7f823c045050, + xmlin=0x7f827c01e630 "<domain type=\"kvm\">\n <name>default_vm-8altm</name>\n <uuid>4a40fa64-fd9b-5078-8574-3ce5d0041d31</uuid>\n <metadata>\n <nodeagent xmlns=\"http://kubevirt.io/node-agent.io\">\n <vmid>13fb0e90-2930-"..., + persist_xml=0x7f827c020660 "<domain type=\"kvm\">\n <name>default_vm-8altm</name>\n <uuid>4a40fa64-fd9b-5078-8574-3ce5d0041d31</uuid>\n <metadata>\n <nodeagent xmlns=\"http://kubevirt.io/node-agent.io\">\n <vmid>13fb0e90-2930-"..., + dconnuri=0x7f827c00c2b0 "qemu+unix:///system?socket=/var/run/kubevirt/migrationproxy/13fb0e90-2930-4f0b-959a-cc40346e7d64-source.sock", uri=0x556a1f856b20 "tcp://10.253.160.196:27939", graphicsuri=0x0, listenAddress=0x0, nmigrate_disks=2, + migrate_disks=0x7f827c006660, nbdPort=0, nbdURI=0x0, migParams=0x7f827c00d890, cookiein=0x0, cookieinlen=0, + cookieout=0x7f828363f8a8, cookieoutlen=0x7f828363f89c, flags=587, dname=0x0, resource=1024, v3proto=true) + at ../src/qemu/qemu_migration.c:5513 + #12 0x00007f82804e34d0 in qemuDomainMigratePerform3Params (dom=0x7f8268002ee0, + dconnuri=0x7f827c00c2b0 "qemu+unix:///system?socket=/var/run/kubevirt/migrationproxy/13fb0e90-2930-4f0b-959a-cc40346e7d64-source.sock", params=0x7f827c01e380, nparams=7, cookiein=0x0, cookieinlen=0, cookieout=0x7f828363f8a8, + cookieoutlen=0x7f828363f89c, flags=587) at ../src/qemu/qemu_driver.c:11796 + #13 0x00007f82853256d6 in virDomainMigratePerform3Params (domain=domain@entry=0x7f8268002ee0, + dconnuri=0x7f827c00c2b0 "qemu+unix:///system?socket=/var/run/kubevirt/migrationproxy/13fb0e90-2930-4f0b-959a-cc40346e7d64-source.sock", params=<optimized out>, nparams=7, cookiein=0x0, cookieinlen=0, cookieout=0x7f828363f8a8, + cookieoutlen=0x7f828363f89c, flags=587) at ../src/libvirt-domain.c:5165 + #14 0x0000556a1f200f17 in remoteDispatchDomainMigratePerform3Params (server=<optimized out>, msg=0x556a1f86ba40, + ret=0x7f827c0197f0, args=0x7f827c019520, rerr=0x7f828363f9a0, client=<optimized out>) + at ../src/remote/remote_daemon_dispatch.c:5710 + #15 remoteDispatchDomainMigratePerform3ParamsHelper (server=<optimized out>, client=<optimized out>, msg=0x556a1f86ba40, + rerr=0x7f828363f9a0, args=0x7f827c019520, ret=0x7f827c0197f0) at src/remote/remote_daemon_dispatch_stubs.h:8761 + #16 0x00007f828522c676 in virNetServerProgramDispatchCall (msg=0x556a1f86ba40, client=0x556a1f85b510, server=0x556a1f84c080, + prog=0x556a1f850410) at ../src/rpc/virnetserverprogram.c:428 + #17 virNetServerProgramDispatch (prog=0x556a1f850410, server=0x556a1f84c080, client=0x556a1f85b510, msg=0x556a1f86ba40) + at ../src/rpc/virnetserverprogram.c:302 + --Type <RET> for more, q to quit, c to continue without paging-- + #18 0x00007f82852331d8 in virNetServerProcessMsg (msg=<optimized out>, prog=<optimized out>, client=<optimized out>, + srv=0x556a1f84c080) at ../src/rpc/virnetserver.c:140 + #19 virNetServerHandleJob (jobOpaque=0x556a1f861f90, opaque=0x556a1f84c080) at ../src/rpc/virnetserver.c:160 + #20 0x00007f8285170653 in virThreadPoolWorker (opaque=<optimized out>) at ../src/util/virthreadpool.c:164 + #21 0x00007f828516fc09 in virThreadHelper (data=<optimized out>) at ../src/util/virthread.c:256 + #22 0x00007f8284b10802 in start_thread () from /lib64/libc.so.6 + #23 0x00007f8284ab0450 in clone3 () from /lib64/libc.so.6 + + + (gdb) p job + $1 = (qemuBlockJobData *) 0x7f827c03ca90 + (gdb) p *job + $2 = {parent = {parent_instance = {g_type_instance = {g_class = 0x7f827c00dc90}, ref_count = 1, qdata = 0x0}}, + name = 0x7f827c038cd0 "drive-ua-vol-vm-8altm", disk = 0x7f823c0475c0, chain = 0x556a1f8548f0, mirrorChain = 0x0, + jobflags = 0, jobflagsmissing = false, data = {pull = {base = 0x0}, commit = {topparent = 0x0, top = 0x0, base = 0x0, + deleteCommittedImages = false}, create = {storage = false, src = 0x0}, copy = {shallownew = false}, backup = { + store = 0x0, bitmap = 0x0}}, type = 2, state = 5, errmsg = 0x0, synchronous = true, newstate = 6, brokentype = 0, + invalidData = false, reconnected = false} + (gdb) p *job->disk + $3 = {src = 0x7f823c047, privateData = 0xffe8eec3390edb93, device = VIR_DOMAIN_DISK_DEVICE_DISK, + bus = VIR_DOMAIN_DISK_BUS_VIRTIO, dst = 0x7f823c047300 "\327_'ą\177", tray_status = VIR_DOMAIN_DISK_TRAY_CLOSED, + removable = VIR_TRISTATE_SWITCH_ABSENT, rotation_rate = 0, mirror = 0x0, mirrorState = 0, mirrorJob = 0, geometry = { + cylinders = 0, heads = 0, sectors = 0, trans = VIR_DOMAIN_DISK_TRANS_DEFAULT}, blockio = {logical_block_size = 0, + physical_block_size = 0}, blkdeviotune = {total_bytes_sec = 0, read_bytes_sec = 0, write_bytes_sec = 0, + total_iops_sec = 0, read_iops_sec = 0, write_iops_sec = 0, total_bytes_sec_max = 0, read_bytes_sec_max = 0, + write_bytes_sec_max = 0, total_iops_sec_max = 0, read_iops_sec_max = 0, write_iops_sec_max = 0, size_iops_sec = 0, + group_name = 0x0, total_bytes_sec_max_length = 0, read_bytes_sec_max_length = 0, write_bytes_sec_max_length = 0, + total_iops_sec_max_length = 0, read_iops_sec_max_length = 0, write_iops_sec_max_length = 0}, + driverName = 0x7f823c047270 "\267\262'ą\177", serial = 0x0, wwn = 0x0, vendor = 0x0, product = 0x0, + cachemode = VIR_DOMAIN_DISK_CACHE_DISABLE, error_policy = VIR_DOMAIN_DISK_ERROR_POLICY_RETRY, + rerror_policy = VIR_DOMAIN_DISK_ERROR_POLICY_DEFAULT, retry_interval = 1000, retry_timeout = 0, + iomode = VIR_DOMAIN_DISK_IO_NATIVE, ioeventfd = VIR_TRISTATE_SWITCH_ABSENT, event_idx = VIR_TRISTATE_SWITCH_ABSENT, + copy_on_read = VIR_TRISTATE_SWITCH_ABSENT, snapshot = VIR_DOMAIN_SNAPSHOT_LOCATION_DEFAULT, + startupPolicy = VIR_DOMAIN_STARTUP_POLICY_DEFAULT, transient = false, transientShareBacking = VIR_TRISTATE_BOOL_ABSENT, + info = {alias = 0x0, type = 0, addr = {pci = {domain = 0, bus = 0, slot = 0, function = 0, + multi = VIR_TRISTATE_SWITCH_ABSENT, extFlags = 0, zpci = {uid = {value = 0, isSet = false}, fid = {value = 0, + isSet = false}}}, drive = {controller = 0, bus = 0, target = 0, unit = 0, diskbus = 0}, vioserial = { + controller = 0, bus = 0, port = 0}, ccid = {controller = 0, slot = 0}, usb = {bus = 0, port = {0, 0, 0, 0}}, + spaprvio = {reg = 0, has_reg = false}, ccw = {cssid = 0, ssid = 0, devno = 0, assigned = false}, isa = {iobase = 0, + irq = 0}, dimm = {slot = 0, base = 0}}, mastertype = 0, master = {usb = {startport = 0}}, + romenabled = VIR_TRISTATE_BOOL_ABSENT, rombar = VIR_TRISTATE_SWITCH_ABSENT, romfile = 0x0, bootIndex = 1, + effectiveBootIndex = 1, acpiIndex = 0, pciConnectFlags = 9, pciAddrExtFlags = 0, loadparm = 0x0, isolationGroup = 0, + isolationGroupLocked = false}, rawio = VIR_TRISTATE_BOOL_ABSENT, sgio = VIR_DOMAIN_DEVICE_SGIO_DEFAULT, + discard = VIR_DOMAIN_DISK_DISCARD_DEFAULT, iothread = 1, detect_zeroes = VIR_DOMAIN_DISK_DETECT_ZEROES_DEFAULT, + domain_name = 0x0, queues = 0, queue_size = 0, model = VIR_DOMAIN_DISK_MODEL_DEFAULT, virtio = 0x7f823c047170, + diskElementAuth = false, diskElementEnc = false} diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/238 b/gitlab/issues_text/target_missing/host_missing/accel_missing/238 new file mode 100644 index 000000000..f7877552f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/238 @@ -0,0 +1 @@ +capstone link failure building linux-user static diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2384 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2384 new file mode 100644 index 000000000..b013dd45b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2384 @@ -0,0 +1,26 @@ +Crash on QEMU 7.2.11 with imx6ul arm cpu cortex-a7 when trying to mount rootfs +Description of problem: +trying to run qemu 7.2.11 for NXP mcimx6ul-evk machine, We get a kernel panic trying to mount the rootfs. +... +[ 7.401206] No soundcards found. +[ 7.500010] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. +[ 7.504607] VFS: Mounted root (vfat filesystem) on device 179:1. +[ 7.511987] devtmpfs: error mounting -2 +[ 7.612562] Freeing unused kernel image (initmem) memory: 1024K +[ 7.638370] Run /sbin/init as init process +[ 7.638829] with arguments: +[ 7.639016] /sbin/init +[ 7.639247] earlyprintk +[ 7.639429] noresume +... +[ 7.657347] Kernel panic - not syncing: No working init found. + +The full log is attached.[qemu_imx6ul_kernel_panic_info.txt](/uploads/c4075a3de7894c18050bf53c32bb18a7/qemu_imx6ul_kernel_panic_info.txt) +Steps to reproduce: +1. download and build qemu 7.2.11 +2. download LF_v6.1.55-2.2.1_images_IMX6UL7D.zip from NXP containing kernel, dtb, rootfs, ...etc binaries +3. To use diskimage as ‘sd’ card , we need to shrink .wic image we got from NXP to fit in 4GB : +./qemu-img resize --shrink imx-image-full.wic 4G +4. invoke the command to run qemu described above. +Additional information: +Any help would be appreciated, if it's not the right forum please advise, thank you. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2386 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2386 new file mode 100644 index 000000000..562ade4af --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2386 @@ -0,0 +1,43 @@ +RISCV - Incorrect behaviour of the SLL instruction +Description of problem: +`SLL` (and probably other similar instructions) produce incorrect results. To quote the [RISCV ISA manual](https://drive.google.com/file/d/1uviu1nH-tScFfgrovvFCrj7Omv8tFtkp/view): + +> SLL, SRL, and SRA perform logical left, logical right, and arithmetic right shifts on the value in register +rs1 by the shift amount held in the lower 5 bits of register rs2. + +This instruction should perform a logical shift left by the shift amount from the lower 5 bits held in the third operand, however, it doesn't seem to be the case. As can be seen from the result of the snippet below: `55c3585000000000`, it seems that it calculates the correct value, but then shifts it by another 32 bits to the left: + +```python +correct_shift_res = (0xDB4D6868655C3585 << (0x69C99AB9B9401024 & 0b11111)) & (2 ** 64 - 1) +incorrect_qemu_produced = (correct_shift_res << 32) & (2 ** 64 - 1) +``` +Steps to reproduce: +1. Compile the attached source file: `riscv64-linux-gnu-gcc -static repro.c -o ./repro.elf` + +```c +#include <stdint.h> +#include <stdio.h> + +int main() { + uint64_t a = 0x69C99AB9B9401024; + uint64_t b = 0xDB4D6868655C3585; + uint64_t c; + + asm volatile("sll %0, %1, %2" : "=r"(c) : "r"(b), "r"(a)); + + printf("s8 : %lx\n", c); + printf("expected: %lx\n", 0xb4d6868655c35850); + + return 0; +} +``` + +2. Run qemu: `./qemu-riscv64 ./repro.elf` +3. You will see the output and what the result of the computation should really be: + +``` +s8 : 55c3585000000000 +expected: b4d6868655c35850 +``` +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2387 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2387 new file mode 100644 index 000000000..76e6c0b0c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2387 @@ -0,0 +1,11 @@ +Segmentation fault on booting from ISO when using GTK display with OpenGL enabled +Description of problem: +When trying to boot from the ISO mounted in the `-cdrom` argument, using a GTK display with OpenGL enabled gives a segmentation fault error. If using SDL instead, the whole application kinda freezes most of the times. I managed to get it working once, but I don't know how or why, seemed completely random. After installing it, I can boot from the disk normally with no errors. +Steps to reproduce: +1. Install QEMU for MSYS2 / UCRT64 as described [here](https://www.qemu.org/download/#windows) +2. Download ISO from EndeavourOS website +3. Run `qemu-img create -f qcow2 EndeavourOS.qcow2 64G` to create a disk file +4. Run the script as described above in a `.sh` file +5. See error +Additional information: +I have multiple VMs, included but not limited to Manjaro, Pop!\_OS and Debian, none of them gives this specific error. I also usually avoid SDL because I had multiple issues with the application window completely freezing in the past with "Not responding", and that does not happen with GTK. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2388 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2388 new file mode 100644 index 000000000..acc7675c9 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2388 @@ -0,0 +1,17 @@ +NVMe SQ processing gets stuck when IO queue size is small (for example 4) +Steps to reproduce: +1. Get OSv repo with the NVMe driver and build OSv with the 'Hello World' example: +``` +git clone https://github.com/wkozaczuk/osv.git +cd osv +git checkout nvme_refined +git submodule update --init --recursive +./scripts/setup.py +./scripts/build image=native-example fs=zfs -j$(nproc) +``` +2. Run OSv with NVme on and point to your version of QEMU built with tracing enabled: +``` +./scripts/run.py --qemu-path /home/wkozaczuk/projects/qemu/build/qemu-system-x86_64 --nics=0 --nvme -c 1 --pass-arg "--trace pci_nvme_*" +``` +Additional information: +I am adding both full QEMU logs with NVMe tracing enabled and diff of my changes to QEMU code to add extra logging. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2389 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2389 new file mode 100644 index 000000000..d7427f6a2 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2389 @@ -0,0 +1,34 @@ +Mutex initialization assertion failure due to incompatibility with macOS setrlimit() syscall +Description of problem: +Running the command with with any set of arguments instantly crashes with the following error message: + +``` +Assertion failed: (mutex->initialized), function qemu_mutex_lock_impl, file ../util/qemu-thread-posix.c, line 92. +zsh: abort ./qemu-system-x86_64 +``` +Steps to reproduce: +As per instructions for building from scratch: + +1. `mkdir build && cd build` +2. `../configure --prefix=$PWD/.. --audio-drv-list=sdl --disable-cocoa --enable-sdl --enable-sdl-image` +3. `make && make install` +4. `cd ../bin` +5. `./qemu-system-x86_64` +Additional information: +The issue is coming from the `os_setup_limits()` function in `os-posix.c`. As it turns out, the `setrlimit()` syscall behaves subtly different on macOS than on Linux systems, and the macOS man pages explicitly forbade the code on line 273. + +Line 273 from `os-posix.c`: + +``` +nofile.rlim_cur = nofile.rlim_max; +``` + +macOS `setrlimit()` man page: + +``` +COMPATIBILITY + setrlimit() now returns with errno set to EINVAL in places that historically succeeded. It no longer accepts "rlim_cur = RLIM_INFINITY" for + RLIM_NOFILE. Use "rlim_cur = min(OPEN_MAX, rlim_max)". +``` + +The man page thankfully gives us the [patch](/uploads/e7c8c6e3b5620c3b1ee34e89661097f3/qemu.patch) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2390 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2390 new file mode 100644 index 000000000..ebd1c6ea1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2390 @@ -0,0 +1,63 @@ +linux-user: Qemu handles `getsockopt` with NULL `optval` incorrectly +Description of problem: +In short call to `getsockopt(_, SOL_TCP, TCP_KEEPIDLE, NULL, _)` behaves differently on RISC-V Qemu than on x64 Linux. +On Linux syscall returns 0, but on Qemu it fails with `"Bad address"`. +Apparently Qemu `getsockopt` implementation is more conservative about NULL `optval` argument than kernel implementation. However man permits passing NULL [link](https://man7.org/linux/man-pages/man2/setsockopt.2.html): + +> For getsockopt(), optlen is a value-result argument, initially + containing the size of the buffer pointed to by optval, and + modified on return to indicate the actual size of the value + returned. **If no option value is to be supplied** or returned, + **optval may be NULL.**" + +For me it sounds like accepting NULL without error (and x64 confirms that interpretation). +Steps to reproduce: +1. Use below toy program `getsockopt.c` and compile it without optimizations like: +``` + gcc -Wall -W -std=gnu11 -pedantic getsockopt.c -o getsockopt +``` + +``` +#include <stdlib.h> +#include <unistd.h> +#include <errno.h> +#include <stdio.h> +#include <netinet/in.h> +#include <sys/socket.h> +#include <netinet/tcp.h> + +static void fail_on_error(int error, const char *msg) { + if (error < 0) { + perror(msg); + exit(errno); + } +} + +int main(int argc, char **argv) { + int socketfd = socket(AF_INET, SOCK_STREAM | SOCK_CLOEXEC, IPPROTO_TCP); + fail_on_error(socketfd, "socket error"); + uint8_t *option_value = NULL; + int32_t len = 0; + int32_t *option_len = &len; + socklen_t opt_len = (socklen_t)*option_len; + int status = getsockopt(socketfd, SOL_TCP, TCP_KEEPIDLE, option_value, &opt_len); + fail_on_error(status, "getsockopt error"); + return 0; +} +``` + + +2. Run program on Qemu and compare output with output from x64 build. In my case it looks like: +``` +root@57646f544f3a:/runtime/programs# ./getsockopt-x64 +root@57646f544f3a:/runtime/programs# ./getsockopt-riscv +getsockopt error: Bad address +``` +Additional information: +I don't think issue is platform specific assuming Qemu `getsockopt` implementation that is actually running is here: +[link](https://github.com/qemu/qemu/blob/master/linux-user/syscall.c#L2522) + +Looking at sources, I'm not sure why Qemu can't simply forward everything to kernel space +instead doing extra sanity checks together with `optval` dereference attempt that eventually fails in one of `put_user*_` function: [link](https://github.com/qemu/qemu/blob/master/linux-user/syscall.c#L2753) + +Anyway, I think that interpretation of man quote is rather straightforward and Qemu `getsockopt` implementation should follow it. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2391 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2391 new file mode 100644 index 000000000..8881126f5 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2391 @@ -0,0 +1,16 @@ +virglrenderer related -device help failure +Description of problem: +When QEMU is compiled against a recent `virglrenderer` version, running the above command fails like this: +``` +$ qemu-system-x86_64 -device virtio-vga-gl,help +qemu-system-x86_64: -device virtio-vga-gl,help: failed to open module: /usr/bin/../lib/qemu/hw-display-virtio-gpu-gl.so: undefined symbol: qemu_egl_display +``` +Steps to reproduce: +1. build QEMU against latest `virglrenderer` (1.0.1) +2. run the above command +Additional information: +The cause appears to be related to e8a2db94 cc @marcandre.lureau-rh + +Arch only recently updated to latest `virglrenderer` which has exposed the issue. + +Note that the device seems to function correctly in normal usage when combined with -display e.g. `-device virtio-vga-gl -display gtk,gl=on` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2392 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2392 new file mode 100644 index 000000000..32d31fb97 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2392 @@ -0,0 +1 @@ +Ability to use KVM on Windows diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2395 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2395 new file mode 100644 index 000000000..14a73a3de --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2395 @@ -0,0 +1,60 @@ +qemu-system-x86_64: Assertion `!(bs->open_flags & BDRV_O_INACTIVE)' failed when paused vm migrating (with shared storage) from dest to src host +Description of problem: +We are doing migration tests with share storage (nfs) as follows: +First, we pause the virtual machine using the 'virsh suspend'command, then migrate the virtual machine to the destination host by 'virsh migrate' command, and there is no problem. After the migration is complete, the virtual machine remains paused on the destination host. However, when we migrate the virtual machine back to the original host, an assertion error is triggered on the current host（dest host）: + +``` +705 qemu-system-x86_64: ../block.c:6748: bdrv_inactivate_recurse: Assertion `!(bs->open_flags & BDRV_O_INACTIVE)' failed. +706 2024-06-17 11:15:59.972+0000: shutting down, reason=crashed +``` + +and virsh migrate commant return error: +``` +**virsh migrate test qemu+tcp://host_ip/system tcp://host_ip --live --verbose --unsafe +Migration: [ 98 %]error: operation failed: domain is not running** +``` +Steps to reproduce: +1. We create an vm with shareable storage and then paused vm in source host: + ``` + virsh create test.xml running + virsh suspend test paused + ``` +2. Migrate vm to the destination host: + ``virsh migrate test qemu+tcp://dest_ip/system tcp://dest_ip --live --verbose --unsafe`` +3. In destination host，vm is paused. +4. Migrate vm back to the source host，and then migration failed and assert error in qemu log in destination host: + ``` + virsh migrate test qemu+tcp://host_ip/system tcp://host_ip --live --verbose --unsafe + Migration: [ 98 %]error: operation failed: domain is not running + ``` + ``` + 705 qemu-system-x86_64: ../block.c:6748: bdrv_inactivate_recurse: Assertion `!(bs->open_flags & + BDRV_O_INACTIVE)' failed. + 706 2024-06-17 11:15:59.972+0000: shutting down, reason=crashed + ``` +Additional information: +1) src -----> dest + ``` +migration_thread() + migration_completion + global_state_store() + vm_stop_force_state(RUN_STATE_FINISH_MIGRATE) + qemu_savevm_state_complete_precopy_nop_iterable() + bdrv_inactivate_all () + bdrv_inactivate_recurse() + bs->open_flags |= BDRV_O_INACTIVE; (BDRV_O_INACTIVE=0x0800) +``` + +2) dest -----> src +``` +migration_thread() + qemu_savevm_state_complete_precopy_non_iterable() + bdrv_inactivate_all () + bdrv_inactivate_recurse() + assert(!(bs->open_flags & BDRV_O_INACTIVE)); Assert and Crash +``` + + +I'm not sure how to address this issue. If QEMU does not support such a migration, a gentler way would be to directly report an error and exit, just like what did in migrate_prepare function， instead of crash qemu. + +If you have any ideas, please let me know, thanks. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2396 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2396 new file mode 100644 index 000000000..869b68625 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2396 @@ -0,0 +1 @@ +Exception in interrupt handling after upgrading from 8.0 to 9.0 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2397 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2397 new file mode 100644 index 000000000..e9e2364f1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2397 @@ -0,0 +1 @@ +Restrict qemu_file_set_error_obj() to migration/ diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2398 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2398 new file mode 100644 index 000000000..845e8c5c1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2398 @@ -0,0 +1,62 @@ +qemu stalls when taking LUKS encrypted snapshot +Description of problem: +We have been dealing with an issue recently, where qemu occasionally stalls when taking LUKS encrypted snapshots. We were able to take several core dumps (one example below) when the issue was happening and, upon analyzing those, we found out that the issue is that the function [qcrypto_pbkdf2_count_iters](https://github.com/qemu/qemu/blob/master/crypto/pbkdf.c#L88) reaches an iteration number high enough that the algorithm takes a long time to finish. + +Upon investigation, we were able to see that this is happening because [start_ms and end_ms](https://github.com/qemu/qemu/blob/master/crypto/pbkdf.c#L115) have the same value, giving a delta of zero, causing the number of iterations to always increase. + +Here are the important parts of the coredump: + +``` +(gdb) bt +#0 0x00007fb00aba5489 in _gcry_sha256_transform_amd64_avx2 () at ../../cipher/sha256-avx2-bmi2-amd64.S:346 +#1 0x00007fb00aba3000 in sha256_final (context=0x55ab875d5028) at ../../cipher/sha256.c:591 +#2 0x00007fb00ab19dea in md_final (a=0x55ab82e1bf50) at ../../cipher/md.c:800 +#3 0x00007fb00ab19f89 in md_final (a=a@entry=0x55ab82e1bf50) at ../../cipher/md.c:1003 +#4 _gcry_md_ctl (hd=hd@entry=0x55ab82e1bf50, buflen=0, buffer=0x0, cmd=5) at ../../cipher/md.c:1012 +#5 0x00007fb00ab1a4d0 in _gcry_md_ctl (buflen=0, buffer=0x0, cmd=5, hd=0x55ab82e1bf50) at ../../cipher/md.c:1106 +#6 _gcry_md_read (hd=0x55ab82e1bf50, algo=algo@entry=0) at ../../cipher/md.c:1110 +#7 0x00007fb00ab1d9ef in _gcry_kdf_pkdf2 (passphrase=passphrase@entry=0x55ab8177f040, passphraselen=passphraselen@entry=64, hashalgo=hashalgo@entry=8, salt=salt@entry=0x55ab8397a1d4, saltlen=saltlen@entry=32, + iterations=iterations@entry=32768000000, keysize=20, keybuffer=0x55ab817693c0) at ../../cipher/kdf.c:213 +#8 0x00007fb00ab1de3c in _gcry_kdf_pkdf2 (keybuffer=0x55ab817693c0, keysize=20, iterations=32768000000, saltlen=32, salt=0x55ab8397a1d4, hashalgo=8, passphraselen=64, passphrase=0x55ab8177f040) at ../../cipher/kdf.c:144 +#9 _gcry_kdf_derive (passphrase=0x55ab8177f040, passphraselen=64, algo=34, subalgo=8, salt=0x55ab8397a1d4, saltlen=32, iterations=32768000000, keysize=20, keybuffer=0x55ab817693c0) at ../../cipher/kdf.c:286 +#10 0x00007fb00ab02299 in gcry_kdf_derive (passphrase=passphrase@entry=0x55ab8177f040, passphraselen=passphraselen@entry=64, algo=algo@entry=34, hashalgo=hashalgo@entry=8, salt=salt@entry=0x55ab8397a1d4, saltlen=saltlen@entry=32, + iterations=32768000000, keysize=20, keybuffer=0x55ab817693c0) at ../../src/visibility.c:1337 +#11 0x000055ab7f80ff83 in qcrypto_pbkdf2 (hash=hash@entry=QCRYPTO_HASH_ALG_SHA256, key=key@entry=0x55ab8177f040 "\b@\327\061\177F\f\345\200Bw#", nkey=nkey@entry=64, + salt=salt@entry=0x55ab8397a1d4 "\"ͧ\322+\201!\375\177\020\037\252Hg$\271\021\340\343T\021OKָ\234m\304\066g\024\276", nsalt=nsalt@entry=32, iterations=iterations@entry=32768000000, + out=0x55ab817693c0 "C[\210\003\332\017b\350\f\257\377UP\257\262\275\033\v\034(", nout=20, errp=0x7fa7565e5df8) at ./crypto/pbkdf-gcrypt.c:75 +#12 0x000055ab7f80fe66 in qcrypto_pbkdf2_count_iters (hash=hash@entry=QCRYPTO_HASH_ALG_SHA256, key=key@entry=0x55ab8177f040 "\b@\327\061\177F\f\345\200Bw#", nkey=64, + salt=salt@entry=0x55ab8397a1d4 "\"ͧ\322+\201!\375\177\020\037\252Hg$\271\021\340\343T\021OKָ\234m\304\066g\024\276", nsalt=nsalt@entry=32, nout=nout@entry=20, errp=0x7fa7565e5df8) at ./crypto/pbkdf.c:80 +#13 0x000055ab7f812930 in qcrypto_block_luks_create (block=0x55ab82944540, options=<optimized out>, optprefix=<optimized out>, initfunc=0x55ab7f7abad0 <qcow2_crypto_hdr_init_func>, writefunc=0x55ab7f7ac040 <qcow2_crypto_hdr_write_func>, + opaque=0x55ab83a32290, errp=0x55ab823873d0) at ./crypto/block-luks.c:1362 +#14 0x000055ab7f810d80 in qcrypto_block_create (options=options@entry=0x55ab818e1f40, optprefix=optprefix@entry=0x55ab7f99912b "encrypt.", initfunc=initfunc@entry=0x55ab7f7abad0 <qcow2_crypto_hdr_init_func>, + writefunc=writefunc@entry=0x55ab7f7ac040 <qcow2_crypto_hdr_write_func>, opaque=opaque@entry=0x55ab83a32290, errp=errp@entry=0x55ab823873d0) at ./crypto/block.c:106 +#15 0x000055ab7f7b0f79 in qcow2_set_up_encryption (errp=0x55ab823873d0, cryptoopts=0x55ab818e1f40, bs=0x55ab83a32290) at ./block/qcow2.c:2996 +#16 qcow2_co_create (create_options=<optimized out>, errp=0x55ab823873d0) at ./block/qcow2.c:3529 +#17 0x000055ab7f7e2fca in blockdev_create_run (job=0x55ab82387350, errp=0x55ab823873d0) at ./block/create.c:46 +#18 0x000055ab7f79cf6f in job_co_entry (opaque=0x55ab82387350) at ./job.c:878 +#19 0x000055ab7f87e09c in coroutine_trampoline (i0=<optimized out>, i1=<optimized out>) at ./util/coroutine-ucontext.c:115 +#20 0x00007fb009a14680 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 +#21 0x00007ffd40716530 in ?? () +#22 0x0000000000000000 in ?? () +(gdb) frame 12 +#12 0x000055ab7f80fe66 in qcrypto_pbkdf2_count_iters (hash=hash@entry=QCRYPTO_HASH_ALG_SHA256, key=key@entry=0x55ab8177f040 "\b@\327\061\177F\f\345\200Bw#", nkey=64, + salt=salt@entry=0x55ab8397a1d4 "\"ͧ\322+\201!\375\177\020\037\252Hg$\271\021\340\343T\021OKָ\234m\304\066g\024\276", nsalt=nsalt@entry=32, nout=nout@entry=20, errp=0x7fa7565e5df8) at ./crypto/pbkdf.c:80 +80 if (qcrypto_pbkdf2(hash, +(gdb) info locals +ret = 18446744073709551615 +out = 0x55ab817693c0 "C[\210\003\332\017b\350\f\257\377UP\257\262\275\033\v\034(" +iterations = 32768000000 +delta_ms = <optimized out> +start_ms = 35357141 +end_ms = 35357141 +``` + +We did some investigation on the getrusage system call, which is [used to calculate start_ms and end_ms](https://github.com/qemu/qemu/blob/master/crypto/pbkdf.c#L72) and found some patches which indicate that it might not be that accurate: + +https://github.com/torvalds/linux/commit/3dc167ba5729ddd2d8e3fa1841653792c295d3f1 + +https://lore.kernel.org/lkml/20221226031010.4079885-1-maxing.lan@bytedance.com/t/#m1c7f2fdc0ea742776a70fd1aa2a2e414c437f534 + +So far we have only seen this with Windows guests, but it might be a red herring. It happens maybe once a month and we were unable to get a reproducer. + +I'm open to proposing a fix for this, but how could we measure this without relying on getrusage which is causing us trouble? Any other suggestions or tips on this? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2399 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2399 new file mode 100644 index 000000000..24014b807 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2399 @@ -0,0 +1,27 @@ +division by zero in ide +Description of problem: +The following log reveals it: + +``` +../hw/ide/core.c:659:26: runtime error: division by zero +SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior ../hw/ide/core.c:659:26 in AddressSanitizer:DEADLYSIGNAL ================================================================= +==4104568==ERROR：AddressSanitizer：FPE on unknown address 0x559d996a7ec3 (pc 0x559d996a7ec3 bp 0x7ffdcf109da0 sp 0x7ffdcf109a40 T0) +#0 0x559d996a7ec3 in ide_set_sector qemu/hw/ide/core.c:659:26 +#1 0x559d996c8dee in ide_sector_read_cb qemu/hw/ide/core.c:786:5 +#2 0x559d996aa50a in ide_buffered_readv_cb qemu/hw/ide/core.c:684:9 +#3 0x559d9b499289 in blk_aio_complete qemu/block/block-backend.c:1555:9 +#4 0x559d9b4891af in blk_aio_complete_bh qemu/block/block-backend.c:1565:5 +#5 0x559d9bbef6b1 in aio_bh_call qemu/util/async.c:171:5 +#6 0x559d9bbf058c in aio_bh_poll qemu/util/async.c:218:13 +#7 0x559d9bb58a28 in aio_dispatch qemu/util/aio-posix.c:423:5 +#8 0x559d9bbf69ce in aio_ctx_dispatch qemu/util/async.c:360:5 +#9 0x7f51fbc77d3a in g_main_context_dispatch (/lib/x86_64-linux-gnu/libglib-2.0.so.0) +0x55d3a.+0x55d3a) +#10 0x559d9bbfa229 in glib_pollfds_poll qemu/util/main-loop.c:287:9 +#11 0x559d9bbf8b63 in os_host_main_loop_wait qemu/util/main-loop.c:310:5 +#12 0x559d9bbf872c in main_loop_wait qemu/util/main-loop.c:589:11 +#13 0x559d9a2640e7 in qemu_main_loop qemu/system/runstate.c:796:9 +#14 0x559d9b1dcaec in qemu_default_main qemu/system/main.c:37:14 +#15 0x559d9b1dcb37 in main qemu/system/main.c:48:12 +#16 0x7f51fb229d8f in __libc_start_call_main csu/.../sysdeps/nptl/libc_start_call_main.h:58:16 +#17 0x7f51fb229e3f in __libc_start_main csu/../csu/libc-start.c:392:3 #18 0x559d98f20ed4 in _start (/home/joey/repo/qemu/build/qemu-system-x86_64+0x1f93ed4) +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2400 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2400 new file mode 100644 index 000000000..f81072f73 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2400 @@ -0,0 +1,43 @@ +Qemu fails to boot snapshot image if its header is qcow2 but its payload and backing image extension are luks +Description of problem: +Qemu fails to recognize snapshot image E:\\test_snapshot.qcow2 saying Volume is not in LUKS format + +You need three commands to reproduce: + +`qemu-img create -f luks --object secret,id=sec0,data=123 -o key-secret=sec0 E:\test.luks 1G` + +`qemu-img create --object secret,id=sec0,data=123 -f qcow2 -o encrypt.format=luks,encrypt.key-secret=sec0 -b E:\test.luks -F luks E:\test_snapshot.qcow2` + +`qemu-system-x86_64 -drive file=E:\test_snapshot.qcow2,format=luks,key-secret=sec0 -object secret,id=sec0,data=123` + +This error is printed: + +`qemu-system-x86_64: -drive file=E:\test_snapshot.qcow2,format=luks,key-secret=sec0: Volume is not in LUKS format` + +But fourth command shows that payload of `E:\test_snapshot.qcow2` has LUKS format: + +`qemu-img info E:\test_snapshot.qcow2` + +\[output\] + +```bash +virtual size: 1 GiB (1073741824 bytes) +disk size: 2.25 MiB +encrypted: yes +cluster_size: 65536 +backing file: E:\test.luks +backing file format: luks +Format specific information: + compat: 1.1 + compression type: zlib + lazy refcounts: false + refcount bits: 16 + encrypt: + ivgen alg: plain64 + detached header: false + hash alg: sha256 + cipher alg: aes-256 + uuid: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx + format: luks + cipher mode: xts ... +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2401 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2401 new file mode 100644 index 000000000..f57631c77 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2401 @@ -0,0 +1 @@ +"-nic none" option has no equivalent in config file diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2406 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2406 new file mode 100644 index 000000000..35e4c818d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2406 @@ -0,0 +1,7 @@ +SDL UI on KMSDRM Frontend flips qemu-consoles +Description of problem: +If I launch qemu on the kms/drm console (without X11 or Wayland), the screen flips automatically between all qemu-consoles. The first (500?) milliseconds, there is the maschine output (boot messages), than the next (200?) milliseconds there is the monitor0 console, the next milliseconds, the serial0 console, and than the parallel0 console. And again from beginning (maschine, monitor0, serial0, parallel0, ... maschine, monitor0, serial0, parallel0, ...) - I dont press any key. + +If I disable monitor0, serial0, parallel0, all is fine, except one thing: I cannot issue a command on monitor0, because its disabled ;). +Steps to reproduce: +1. Start qemu without X11 and without wayland on the KMSDRM console. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2407 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2407 new file mode 100644 index 000000000..b918926d7 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2407 @@ -0,0 +1,53 @@ +"code should not be reached" in ati_2d_blt() +Description of problem: +My fuzzer detected a "code should not be reached" bug in ati_2d_blt() + +The stack trace is: + +``` +ERROR:include/qemu/bswap.h:418:stn_he_p: code should not be reached +Bail out! ERROR:include/qemu/bswap.h:418:stn_he_p: code should not be reached +==69534== ERROR: libFuzzer: deadly signal + #0 0x559e65667f5e in __sanitizer_print_stack_trace llvm-project-15.0.0.src/compiler-rt/lib/asan/asan_stack.cpp:87:3 + #1 0x559e655a73bc in fuzzer::PrintStackTrace() llvm-project-15.0.0.src/compiler-rt/lib/fuzzer/FuzzerUtil.cpp:210:38 + #2 0x559e65585a66 in fuzzer::Fuzzer::CrashCallback() (.part.0) llvm-project-15.0.0.src/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:236:18 + #3 0x559e65585b2b in fuzzer::Fuzzer::CrashCallback() llvm-project-15.0.0.src/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:208:1 + #4 0x559e65585b2b in fuzzer::Fuzzer::StaticCrashSignalCallback() llvm-project-15.0.0.src/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:207:19 + #5 0x7fa8835e351f (/lib/x86_64-linux-gnu/libc.so.6+0x4251f) (BuildId: c289da5071a3399de893d2af81d6a30c62646e1e) + #6 0x7fa8836379fb in __pthread_kill_implementation nptl/pthread_kill.c:43:17 + #7 0x7fa8836379fb in __pthread_kill_internal nptl/pthread_kill.c:78:10 + #8 0x7fa8836379fb in pthread_kill nptl/pthread_kill.c:89:10 + #9 0x7fa8835e3475 in gsignal signal/../sysdeps/posix/raise.c:26:13 + #10 0x7fa8835c97f2 in abort stdlib/abort.c:79:7 + #11 0x7fa8848e5b56 (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x1eb56) (BuildId: c74e800dfd5f72649d673b44292f4a817e45150b) + #12 0x7fa88493f70e in g_assertion_message_expr (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x7870e) (BuildId: c74e800dfd5f72649d673b44292f4a817e45150b) + #13 0x559e65fc7d70 in stn_he_p include/qemu/bswap.h:418:1 + #14 0x559e65fc55dc in ati_2d_blt hw/display/ati_2d.c:224:21 + #15 0x559e65faccff in ati_mm_write hw/display/ati.c:857:9 + #16 0x559e685b8363 in memory_region_write_accessor system/memory.c:497:5 + #17 0x559e685b7a45 in access_with_adjusted_size system/memory.c:573:18 + #18 0x559e685b59a9 in memory_region_dispatch_write system/memory.c:1521:16 + #19 0x559e6865938e in flatview_write_continue_step system/physmem.c:2757:18 + #20 0x559e68658c24 in flatview_write_continue system/physmem.c:2787:19 + #21 0x559e6863024b in flatview_write system/physmem.c:2818:12 + #22 0x559e6862fd18 in address_space_write system/physmem.c:2938:18 +... +``` +Steps to reproduce: +Arguments: `export QEMU_ARGS="-machine q35 -nodefaults -device ati-vga,romfile=\"\" -display vnc=localhost:99 -L ../pc-bios/"` + +The base addresses of memory regions: + +ati.mmregs: 0xe1000000 + +Reproducer: + +``` +writew 0xe100146c 0x44e4c5c1 +writeb 0xe10016c0 0x773b93cf +writeb 0xe10016e4 0x2beb6e13 +writel 0xe100143c 0x118b71f6 +EOF +``` +Additional information: +Ack: Chuhong Yuan (hslester96@gmail.com) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2408 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2408 new file mode 100644 index 000000000..9c63adb83 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2408 @@ -0,0 +1,237 @@ +QEMU crashes during guest OS boot if virtserialport is present +Description of problem: +QEMU will load the firmware (`OVMF_CODE.fd`) and run the boot manager (`BootDisk.qcow2`) just fine, then shortly after control is passed to the OS installer (`InstallDisk.raw`) it will crash. + +This only happens if a `virtioserialport` is present: dropping that single device from the configuration will allow the installer to run, even if the `virtio-serial-pci` device is still present. The exact value of the `name` attribute doesn't seem to make a difference either, I'm just using the standard one for qemu-ga here. + +Note that `InstallDisk.raw` is attached using `virtio-blk-pci`, so it's this specific virtio device triggering the crash, not the use of virtio devices in general. +Additional information: +The crash happens 100% of the time. + +Running a bisect between 8.2 (known to work) and 9.0 (known to crash) has identified the commit 2ce6cff94df2650c460f809e5ad263f1d22507c0 as the culpit: + +``` +commit 2ce6cff94df2650c460f809e5ad263f1d22507c0 +Author: Cindy Lu <lulu@redhat.com> +Date: Fri Apr 12 14:26:55 2024 +0800 + + virtio-pci: fix use of a released vector + + During the booting process of the non-standard image, the behavior of the + called function in qemu is as follows: + + 1. vhost_net_stop() was triggered by guest image. This will call the function + virtio_pci_set_guest_notifiers() with assgin= false, + virtio_pci_set_guest_notifiers(） will release the irqfd for vector 0 + + 2. virtio_reset() was triggered, this will set configure vector to VIRTIO_NO_VECTOR + + 3.vhost_net_start() was called (at this time, the configure vector is + still VIRTIO_NO_VECTOR) and then call virtio_pci_set_guest_notifiers() with + assgin=true, so the irqfd for vector 0 is still not "init" during this process + + 4. The system continues to boot and sets the vector back to 0. After that + msix_fire_vector_notifier() was triggered to unmask the vector 0 and meet the crash + + To fix the issue, we need to support changing the vector after VIRTIO_CONFIG_S_DRIVER_OK is set. + + (gdb) bt + 0 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) + at pthread_kill.c:44 + 1 0x00007fc87148ec53 in __pthread_kill_internal (signo=6, threadid=<optimized out>) at pthread_kill.c:78 + 2 0x00007fc87143e956 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 + 3 0x00007fc8714287f4 in __GI_abort () at abort.c:79 + 4 0x00007fc87142871b in __assert_fail_base + (fmt=0x7fc8715bbde0 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x5606413efd53 "ret == 0", file=0x5606413ef87d "../accel/kvm/kvm-all.c", line=1837, function=<optimized out>) at assert.c:92 + 5 0x00007fc871437536 in __GI___assert_fail + (assertion=0x5606413efd53 "ret == 0", file=0x5606413ef87d "../accel/kvm/kvm-all.c", line=1837, function=0x5606413f06f0 <__PRETTY_FUNCTION__.19> "kvm_irqchip_commit_routes") at assert.c:101 + 6 0x0000560640f884b5 in kvm_irqchip_commit_routes (s=0x560642cae1f0) at ../accel/kvm/kvm-all.c:1837 + 7 0x0000560640c98f8e in virtio_pci_one_vector_unmask + (proxy=0x560643c65f00, queue_no=4294967295, vector=0, msg=..., n=0x560643c6e4c8) + at ../hw/virtio/virtio-pci.c:1005 + 8 0x0000560640c99201 in virtio_pci_vector_unmask (dev=0x560643c65f00, vector=0, msg=...) + at ../hw/virtio/virtio-pci.c:1070 + 9 0x0000560640bc402e in msix_fire_vector_notifier (dev=0x560643c65f00, vector=0, is_masked=false) + at ../hw/pci/msix.c:120 + 10 0x0000560640bc40f1 in msix_handle_mask_update (dev=0x560643c65f00, vector=0, was_masked=true) + at ../hw/pci/msix.c:140 + 11 0x0000560640bc4503 in msix_table_mmio_write (opaque=0x560643c65f00, addr=12, val=0, size=4) + at ../hw/pci/msix.c:231 + 12 0x0000560640f26d83 in memory_region_write_accessor + (mr=0x560643c66540, addr=12, value=0x7fc86b7bc628, size=4, shift=0, mask=4294967295, attrs=...) + at ../system/memory.c:497 + 13 0x0000560640f270a6 in access_with_adjusted_size + + (addr=12, value=0x7fc86b7bc628, size=4, access_size_min=1, access_size_max=4, access_fn=0x560640f26c8d <memory_region_write_accessor>, mr=0x560643c66540, attrs=...) at ../system/memory.c:573 + 14 0x0000560640f2a2b5 in memory_region_dispatch_write (mr=0x560643c66540, addr=12, data=0, op=MO_32, attrs=...) + at ../system/memory.c:1521 + 15 0x0000560640f37bac in flatview_write_continue + (fv=0x7fc65805e0b0, addr=4273803276, attrs=..., ptr=0x7fc871e9c028, len=4, addr1=12, l=4, mr=0x560643c66540) + at ../system/physmem.c:2714 + 16 0x0000560640f37d0f in flatview_write + (fv=0x7fc65805e0b0, addr=4273803276, attrs=..., buf=0x7fc871e9c028, len=4) at ../system/physmem.c:2756 + 17 0x0000560640f380bf in address_space_write + (as=0x560642161ae0 <address_space_memory>, addr=4273803276, attrs=..., buf=0x7fc871e9c028, len=4) + at ../system/physmem.c:2863 + 18 0x0000560640f3812c in address_space_rw + (as=0x560642161ae0 <address_space_memory>, addr=4273803276, attrs=..., buf=0x7fc871e9c028, len=4, is_write=true) at ../system/physmem.c:2873 + --Type <RET> for more, q to quit, c to continue without paging-- + 19 0x0000560640f8aa55 in kvm_cpu_exec (cpu=0x560642f205e0) at ../accel/kvm/kvm-all.c:2915 + 20 0x0000560640f8d731 in kvm_vcpu_thread_fn (arg=0x560642f205e0) at ../accel/kvm/kvm-accel-ops.c:51 + 21 0x00005606411949f4 in qemu_thread_start (args=0x560642f292b0) at ../util/qemu-thread-posix.c:541 + 22 0x00007fc87148cdcd in start_thread (arg=<optimized out>) at pthread_create.c:442 + 23 0x00007fc871512630 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 + (gdb) + + MST: coding style and typo fixups + + Fixes: f9a09ca3ea ("vhost: add support for configure interrupt") + Cc: qemu-stable@nongnu.org + Signed-off-by: Cindy Lu <lulu@redhat.com> + Message-ID: <2321ade5f601367efe7380c04e3f61379c59b48f.1713173550.git.mst@redhat.com> + Cc: Lei Yang <leiyang@redhat.com> + Cc: Jason Wang <jasowang@redhat.com> + Signed-off-by: Michael S. Tsirkin <mst@redhat.com> + Tested-by: Cindy Lu <lulu@redhat.com> +``` + +Considering that it touches virtio-pci, the results seem plausible. + +This commit was also backported to stable as part of the 8.2.3 release, and indeed I have verified that that version suffers from the crash while 8.2.2 didn't. + +Reverting the commit makes the crash go away, but obviously the change was made for a reason so we probably need a follow-up fix rather than a plain revert. + +Crash and stack trace: + +``` +Thread 10 "qemu-system-x86" received signal SIGSEGV, Segmentation fault. +[Switching to Thread 0x7fffe56006c0 (LWP 323938)] +kvm_virtio_pci_vq_vector_use (vector=0, proxy=0x555558e04690) at ../hw/virtio/virtio-pci.c:817 +817 if (irqfd->users == 0) { +(gdb) t a a bt + +Thread 33 (Thread 0x7fffe6a006c0 (LWP 323987) "qemu-system-x86"): +#0 0x00007ffff4ae1169 in __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x7fffe69fb010, op=393, expected=0, futex_word=0x555557ad4370) at futex-internal.c:57 +#1 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x555557ad4370, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x7fffe69fb010, private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87 +#2 0x00007ffff4ae11ef in __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x555557ad4370, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x7fffe69fb010, private=private@entry=0) at futex-internal.c:139 +#3 0x00007ffff4ae3e72 in __pthread_cond_wait_common (abstime=0x7fffe69fb010, clockid=0, mutex=0x7fffe69faf90, cond=0x555557ad4348) at pthread_cond_wait.c:503 +#4 ___pthread_cond_timedwait64 (cond=cond@entry=0x555557ad4348, mutex=mutex@entry=0x555557ad42e0, abstime=abstime@entry=0x7fffe69fb010) at pthread_cond_wait.c:643 +#5 0x0000555555efc651 in qemu_cond_timedwait_ts (cond=cond@entry=0x555557ad4348, mutex=mutex@entry=0x555557ad42e0, ts=ts@entry=0x7fffe69fb010, file=file@entry=0x55555616c035 "../util/thread-pool.c", line=line@entry=91) at ../util/qemu-thread-posix.c:239 +#6 0x0000555555efd2f8 in qemu_cond_timedwait_impl (cond=0x555557ad4348, mutex=0x555557ad42e0, ms=<optimized out>, file=0x55555616c035 "../util/thread-pool.c", line=91) at ../util/qemu-thread-posix.c:253 +#7 0x0000555555f129bc in worker_thread (opaque=opaque@entry=0x555557ad42d0) at ../util/thread-pool.c:91 +#8 0x0000555555efc4c8 in qemu_thread_start (args=0x555557aef190) at ../util/qemu-thread-posix.c:541 +#9 0x00007ffff4ae4897 in start_thread (arg=<optimized out>) at pthread_create.c:444 +#10 0x00007ffff4b6ba5c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 + +Thread 32 (Thread 0x7fffece006c0 (LWP 323986) "qemu-system-x86"): +#0 0x00007ffff4ae1169 in __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x7fffecdfb010, op=393, expected=0, futex_word=0x555557ad4374) at futex-internal.c:57 +#1 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x555557ad4374, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x7fffecdfb010, private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87 +#2 0x00007ffff4ae11ef in __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x555557ad4374, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x7fffecdfb010, private=private@entry=0) at futex-internal.c:139 +#3 0x00007ffff4ae3e72 in __pthread_cond_wait_common (abstime=0x7fffecdfb010, clockid=0, mutex=0x7fffecdfaf90, cond=0x555557ad4348) at pthread_cond_wait.c:503 +#4 ___pthread_cond_timedwait64 (cond=cond@entry=0x555557ad4348, mutex=mutex@entry=0x555557ad42e0, abstime=abstime@entry=0x7fffecdfb010) at pthread_cond_wait.c:643 +#5 0x0000555555efc651 in qemu_cond_timedwait_ts (cond=cond@entry=0x555557ad4348, mutex=mutex@entry=0x555557ad42e0, ts=ts@entry=0x7fffecdfb010, file=file@entry=0x55555616c035 "../util/thread-pool.c", line=line@entry=91) at ../util/qemu-thread-posix.c:239 +#6 0x0000555555efd2f8 in qemu_cond_timedwait_impl (cond=0x555557ad4348, mutex=0x555557ad42e0, ms=<optimized out>, file=0x55555616c035 "../util/thread-pool.c", line=91) at ../util/qemu-thread-posix.c:253 +#7 0x0000555555f129bc in worker_thread (opaque=opaque@entry=0x555557ad42d0) at ../util/thread-pool.c:91 +#8 0x0000555555efc4c8 in qemu_thread_start (args=0x555557aee7b0) at ../util/qemu-thread-posix.c:541 +#9 0x00007ffff4ae4897 in start_thread (arg=<optimized out>) at pthread_create.c:444 +#10 0x00007ffff4b6ba5c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 + +Thread 10 (Thread 0x7fffe56006c0 (LWP 323938) "qemu-system-x86"): +#0 kvm_virtio_pci_vq_vector_use (vector=0, proxy=0x555558e04690) at ../hw/virtio/virtio-pci.c:817 +#1 kvm_virtio_pci_vector_use_one (proxy=0x555558e04690, queue_no=5) at ../hw/virtio/virtio-pci.c:893 +#2 0x0000555555cde680 in memory_region_write_accessor (mr=0x555558e05230, addr=26, value=<optimized out>, size=2, shift=<optimized out>, mask=<optimized out>, attrs=...) at ../system/memory.c:497 +#3 0x0000555555cddf26 in access_with_adjusted_size (addr=addr@entry=26, value=value@entry=0x7fffe55fae78, size=size@entry=2, access_size_min=<optimized out>, access_size_max=<optimized out>, access_fn=0x555555cde600 <memory_region_write_accessor>, mr=<optimized out>, attrs=...) at ../system/memory.c:573 +#4 0x0000555555cde271 in memory_region_dispatch_write (mr=mr@entry=0x555558e05230, addr=addr@entry=26, data=<optimized out>, op=<optimized out>, attrs=attrs@entry=...) at ../system/memory.c:1528 +#5 0x0000555555ce623f in flatview_write_continue_step (attrs=attrs@entry=..., buf=buf@entry=0x7fffeef80028 "", mr_addr=26, l=l@entry=0x7fffe55faf90, mr=0x555558e05230, len=2) at ../system/physmem.c:2757 +#6 0x0000555555ce6918 in flatview_write_continue (mr=<optimized out>, l=<optimized out>, mr_addr=<optimized out>, len=2, ptr=0x8100401a, attrs=..., addr=2164277274, fv=0x7fff343ec810) at ../system/physmem.c:2787 +#7 flatview_write (fv=0x7fff343ec810, addr=addr@entry=2164277274, attrs=attrs@entry=..., buf=buf@entry=0x7fffeef80028, len=len@entry=2) at ../system/physmem.c:2818 +#8 0x0000555555ce9e61 in address_space_write (len=2, buf=0x7fffeef80028, attrs=..., addr=2164277274, as=0x555556e03d40 <address_space_memory>) at ../system/physmem.c:2938 +#9 address_space_rw (as=0x555556e03d40 <address_space_memory>, addr=2164277274, attrs=attrs@entry=..., buf=buf@entry=0x7fffeef80028, len=2, is_write=<optimized out>) at ../system/physmem.c:2948 +#10 0x0000555555d45118 in kvm_cpu_exec (cpu=cpu@entry=0x555557cde8b0) at ../accel/kvm/kvm-all.c:3031 +#11 0x0000555555d46845 in kvm_vcpu_thread_fn (arg=arg@entry=0x555557cde8b0) at ../accel/kvm/kvm-accel-ops.c:50 +#12 0x0000555555efc4c8 in qemu_thread_start (args=0x555557c5a370) at ../util/qemu-thread-posix.c:541 +#13 0x00007ffff4ae4897 in start_thread (arg=<optimized out>) at pthread_create.c:444 +#14 0x00007ffff4b6ba5c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 + +Thread 9 (Thread 0x7fffe60006c0 (LWP 323937) "qemu-system-x86"): +#0 futex_wait (private=0, expected=2, futex_word=0x555556deffe0 <bql>) at ../sysdeps/nptl/futex-internal.h:146 +#1 __GI___lll_lock_wait (futex=futex@entry=0x555556deffe0 <bql>, private=0) at lowlevellock.c:49 +#2 0x00007ffff4ae7e41 in lll_mutex_lock_optimized (mutex=0x555556deffe0 <bql>) at pthread_mutex_lock.c:48 +#3 ___pthread_mutex_lock (mutex=mutex@entry=0x555556deffe0 <bql>) at pthread_mutex_lock.c:93 +#4 0x0000555555efc8c3 in qemu_mutex_lock_impl (mutex=0x555556deffe0 <bql>, file=0x5555560e97ca "../system/physmem.c", line=2689) at ../util/qemu-thread-posix.c:94 +#5 0x0000555555ad6082 in bql_lock_impl (file=file@entry=0x5555560e97ca "../system/physmem.c", line=line@entry=2689) at ../system/cpus.c:536 +#6 0x0000555555ce632f in prepare_mmio_access (mr=0x55555874c4b0) at ../system/physmem.c:2689 +#7 flatview_write_continue_step (attrs=..., attrs@entry=..., buf=buf@entry=0x7fffeef83028 "", mr_addr=536, l=l@entry=0x7fffe5ffaf90, mr=0x55555874c4b0, len=4) at ../system/physmem.c:2738 +#8 0x0000555555ce6918 in flatview_write_continue (mr=<optimized out>, l=<optimized out>, mr_addr=<optimized out>, len=4, ptr=0x81084218, attrs=..., addr=2164802072, fv=0x7fff343ec810) at ../system/physmem.c:2787 +#9 flatview_write (fv=0x7fff343ec810, addr=addr@entry=2164802072, attrs=attrs@entry=..., buf=buf@entry=0x7fffeef83028, len=len@entry=4) at ../system/physmem.c:2818 +#10 0x0000555555ce9e61 in address_space_write (len=4, buf=0x7fffeef83028, attrs=..., addr=2164802072, as=0x555556e03d40 <address_space_memory>) at ../system/physmem.c:2938 +#11 address_space_rw (as=0x555556e03d40 <address_space_memory>, addr=2164802072, attrs=attrs@entry=..., buf=buf@entry=0x7fffeef83028, len=4, is_write=<optimized out>) at ../system/physmem.c:2948 +#12 0x0000555555d45118 in kvm_cpu_exec (cpu=cpu@entry=0x555557dbdcd0) at ../accel/kvm/kvm-all.c:3031 +#13 0x0000555555d46845 in kvm_vcpu_thread_fn (arg=arg@entry=0x555557dbdcd0) at ../accel/kvm/kvm-accel-ops.c:50 +#14 0x0000555555efc4c8 in qemu_thread_start (args=0x555557c0b4a0) at ../util/qemu-thread-posix.c:541 +#15 0x00007ffff4ae4897 in start_thread (arg=<optimized out>) at pthread_create.c:444 +#16 0x00007ffff4b6ba5c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 + +Thread 7 (Thread 0x7fffe74006c0 (LWP 323934) "dconf worker"): +#0 0x00007ffff4b5de3d in __GI___poll (fds=0x7fffc8000b90, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 +#1 0x00007ffff6e38f04 in g_main_context_poll_unlocked (priority=2147483647, n_fds=1, fds=0x7fffc8000b90, timeout=<optimized out>, context=0x555557adfef0) at ../glib/gmain.c:4653 +#2 g_main_context_iterate_unlocked.isra.0 (context=context@entry=0x555557adfef0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/gmain.c:4344 +#3 0x00007ffff6ddbad3 in g_main_context_iteration (context=context@entry=0x555557adfef0, may_block=may_block@entry=1) at ../glib/gmain.c:4414 +#4 0x00007ffff7fb16b5 in dconf_gdbus_worker_thread (user_data=0x555557adfef0) at ../gdbus/dconf-gdbus-thread.c:82 +#5 0x00007ffff6e0e573 in g_thread_proxy (data=0x555557ae00d0) at ../glib/gthread.c:831 +#6 0x00007ffff4ae4897 in start_thread (arg=<optimized out>) at pthread_create.c:444 +#7 0x00007ffff4b6ba5c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 + +Thread 6 (Thread 0x7fffe7e006c0 (LWP 323933) "gdbus"): +#0 0x00007ffff4b5de3d in __GI___poll (fds=0x7fffd0000b90, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 +#1 0x00007ffff6e38f04 in g_main_context_poll_unlocked (priority=2147483647, n_fds=3, fds=0x7fffd0000b90, timeout=<optimized out>, context=0x7fffd4005a90) at ../glib/gmain.c:4653 +#2 g_main_context_iterate_unlocked.isra.0 (context=0x7fffd4005a90, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/gmain.c:4344 +#3 0x00007ffff6ddf447 in g_main_loop_run (loop=0x7fffd4005b80) at ../glib/gmain.c:4551 +#4 0x00007ffff7048bc2 in gdbus_shared_thread_func (user_data=0x7fffd4005a60) at ../gio/gdbusprivate.c:284 +#5 0x00007ffff6e0e573 in g_thread_proxy (data=0x7fffd4005bc0) at ../glib/gthread.c:831 +#6 0x00007ffff4ae4897 in start_thread (arg=<optimized out>) at pthread_create.c:444 +#7 0x00007ffff4b6ba5c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 + +Thread 4 (Thread 0x7fffed8006c0 (LWP 323931) "gmain"): +#0 0x00007ffff4b5de3d in __GI___poll (fds=0x555557acd200, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 +#1 0x00007ffff6e38f04 in g_main_context_poll_unlocked (priority=2147483647, n_fds=1, fds=0x555557acd200, timeout=<optimized out>, context=0x555557accfd0) at ../glib/gmain.c:4653 +#2 g_main_context_iterate_unlocked.isra.0 (context=context@entry=0x555557accfd0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/gmain.c:4344 +#3 0x00007ffff6ddbad3 in g_main_context_iteration (context=0x555557accfd0, may_block=may_block@entry=1) at ../glib/gmain.c:4414 +#4 0x00007ffff6ddbb29 in glib_worker_main (data=<optimized out>) at ../glib/gmain.c:6574 +#5 0x00007ffff6e0e573 in g_thread_proxy (data=0x555557ac1140) at ../glib/gthread.c:831 +#6 0x00007ffff4ae4897 in start_thread (arg=<optimized out>) at pthread_create.c:444 +#7 0x00007ffff4b6ba5c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 + +Thread 3 (Thread 0x7fffee2006c0 (LWP 323930) "pool-spawner"): +#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 +#1 0x00007ffff6e35b7d in g_cond_wait (cond=0x555557ac5f28, mutex=0x555557ac5f20) at ../glib/gthread-posix.c:1552 +#2 0x00007ffff6da922b in g_async_queue_pop_intern_unlocked (queue=0x555557ac5f20, wait=1, end_time=-1) at ../glib/gasyncqueue.c:425 +#3 0x00007ffff6e123e3 in g_thread_pool_spawn_thread (data=<optimized out>) at ../glib/gthreadpool.c:311 +#4 0x00007ffff6e0e573 in g_thread_proxy (data=0x555557ac7800) at ../glib/gthread.c:831 +#5 0x00007ffff4ae4897 in start_thread (arg=<optimized out>) at pthread_create.c:444 +#6 0x00007ffff4b6ba5c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 + +Thread 2 (Thread 0x7fffeec006c0 (LWP 323929) "qemu-system-x86"): +#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 +#1 0x0000555555efd7ca in qemu_futex_wait (val=<optimized out>, f=<optimized out>) at /home/abologna/src/upstream/qemu/include/qemu/futex.h:29 +#2 qemu_event_wait (ev=ev@entry=0x555556e182e8 <rcu_call_ready_event>) at ../util/qemu-thread-posix.c:464 +#3 0x0000555555f07216 in call_rcu_thread (opaque=opaque@entry=0x0) at ../util/rcu.c:278 +#4 0x0000555555efc4c8 in qemu_thread_start (args=0x555556ea0ed0) at ../util/qemu-thread-posix.c:541 +#5 0x00007ffff4ae4897 in start_thread (arg=<optimized out>) at pthread_create.c:444 +#6 0x00007ffff4b6ba5c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 + +Thread 1 (Thread 0x7fffef0864c0 (LWP 323692) "qemu-system-x86"): +#0 futex_wait (private=0, expected=2, futex_word=0x555556deffe0 <bql>) at ../sysdeps/nptl/futex-internal.h:146 +#1 __GI___lll_lock_wait (futex=futex@entry=0x555556deffe0 <bql>, private=0) at lowlevellock.c:49 +#2 0x00007ffff4ae7e41 in lll_mutex_lock_optimized (mutex=0x555556deffe0 <bql>) at pthread_mutex_lock.c:48 +#3 ___pthread_mutex_lock (mutex=mutex@entry=0x555556deffe0 <bql>) at pthread_mutex_lock.c:93 +#4 0x0000555555efc8c3 in qemu_mutex_lock_impl (mutex=0x555556deffe0 <bql>, file=0x55555616b7ef "../util/main-loop.c", line=308) at ../util/qemu-thread-posix.c:94 +#5 0x0000555555ad6082 in bql_lock_impl (file=file@entry=0x55555616b7ef "../util/main-loop.c", line=line@entry=308) at ../system/cpus.c:536 +#6 0x0000555555f109a6 in os_host_main_loop_wait (timeout=6299288) at ../util/main-loop.c:308 +#7 main_loop_wait (nonblocking=nonblocking@entry=0) at ../util/main-loop.c:589 +#8 0x0000555555ae0ce9 in qemu_main_loop () at ../system/runstate.c:795 +#9 0x0000555555d50f66 in qemu_default_main () at ../system/main.c:37 +#10 0x00007ffff4a7e14a in __libc_start_call_main (main=main@entry=0x555555897b80 <main>, argc=argc@entry=29, argv=argv@entry=0x7fffffffe0e8) at ../sysdeps/nptl/libc_start_call_main.h:58 +#11 0x00007ffff4a7e20b in __libc_start_main_impl (main=0x555555897b80 <main>, argc=29, argv=0x7fffffffe0e8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffe0d8) at ../csu/libc-start.c:360 +#12 0x00005555558998a5 in _start () +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2409 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2409 new file mode 100644 index 000000000..dccdee111 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2409 @@ -0,0 +1 @@ +High CPU usage on network traffic on Apple laptops diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2410 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2410 new file mode 100644 index 000000000..66405d9af --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2410 @@ -0,0 +1,92 @@ +linux-user: `Setsockopt` with IP_OPTIONS returns "Protocol not available" error +Description of problem: +It seems that call to `setsockopt(sd, SOL_IP, IP_OPTIONS,_)` behaves differently on RISC-V Qemu than on x64 Linux. +On Linux syscall returns 0, but on Qemu it fails with `Protocol not available`. +According [man](https://man7.org/linux/man-pages/man7/ip.7.html) `IP_OPTIONS` on `SOCK_STREAM` socket "should work". +Steps to reproduce: +1. Use below toy program `setsockopt.c` and compile it without optimizations like: +``` + gcc -Wall -W -Wextra -std=gnu17 -pedantic setsockopt.c -o setsockopt +``` + +``` +#include <sys/types.h> +#include <sys/socket.h> +#include <arpa/inet.h> +#include <netinet/in.h> +#include <unistd.h> +#include <stdio.h> +#include <stdlib.h> +#include <string.h> + +int main() { + { + int sd = socket(AF_INET, SOCK_STREAM, IPPROTO_TCP); + if(sd < 0) { + perror("Opening stream socket error"); + exit(1); + } + else + printf("Opening stream socket....OK.\n"); + + struct sockaddr_in local_address = {AF_INET, htons(1234), {inet_addr("255.255.255.255")}, {0}}; + int err = connect(sd, (struct sockaddr*)&local_address, (socklen_t)16); + + if (err < 0) { + perror("Connect error"); + close(sd); + } + else + printf("Connect...OK.\n"); + } + { + int sd = socket(AF_INET, SOCK_STREAM, IPPROTO_TCP); + if(sd < 0) { + perror("Opening stream socket error"); + exit(1); + } + else + printf("Opening stream socket....OK.\n"); + + char option[4] = {0}; + if(setsockopt(sd, SOL_IP, IP_OPTIONS, (char *)option, sizeof(option)) < 0) { + perror("setsockopt error"); + close(sd); + exit(1); + } + else + printf("setsockopt...OK.\n"); + + struct sockaddr_in local_address = {AF_INET, htons(1234), {inet_addr("255.255.255.255")}, {0}}; + int err = connect(sd, (struct sockaddr*)&local_address, (socklen_t)16); + + if (err < 0) { + perror("Connect error"); + close(sd); + } + else + printf("Connect...OK.\n"); + } + return 0; +} +``` + + +2. Run program on Qemu and compare output with output from x64 build. In my case it looks like: +``` +root@AMDC4705:~/runtime/connect$ ./setsockopt-x64 +Opening stream socket....OK. +Connect error: Network is unreachable +Opening stream socket....OK. +setsockopt...OK. +Connect error: Network is unreachable + +root@AMDC4705:/runtime/connect# ./setsockopt-riscv +Opening stream socket....OK. +Connect error: Network is unreachable +Opening stream socket....OK. +setsockopt error: Protocol not available +``` +Additional information: +In above demo option `value` is quite artificial. However I tried passing many different `option` arguments (with same `SOL_IP` + `IP_OPTIONS` combination) but always ended up with `setsockopt` failure. +From the other hand on x64 it worked fine. Then I realized that appropriate path in Qemu was unimplemented: https://github.com/qemu/qemu/blob/master/linux-user/syscall.c#L2141 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2411 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2411 new file mode 100644 index 000000000..29d7e08d5 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2411 @@ -0,0 +1,11 @@ +[SPICE] How to make SPICE work with GVT-g + DMA-BUF + egl-headless ? +Description of problem: +I try to use GVT-g + DMA-BUF in PVE , vGPU display output can be displayed normally on noVNC, + +but when I try use SPICE, VM would not boot, come up with error: kvm: **The console requires display DMABUF support**. +Steps to reproduce: +1. Create a windows virtual machine +2. Manually add args to the conf file, add the mdev device of GVT-g. +3. Starting the Virtual Machine + +# diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2412 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2412 new file mode 100644 index 000000000..95e909d2d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2412 @@ -0,0 +1,100 @@ +Race condition in megasas device +Description of problem: +Race condition DoS in megasas device was found during **fuzzing**. I'm not sure about **worst case impact**, but for now I can make a suggestion: worst case might be leading to **DoS**, but probably it's a rabbit hole. So if we dig deeper we might find something like CWE-200 or CWE-202 (Exposure of Sensitive Information to an Unauthorized Actor and so on). Also, I think that we should analyse thread usage in this case and make all operations thread-safe, but it's not my business of course. As a consequence, I do not suggest any patch (at least for now). +Steps to reproduce: +This command: + +`cat << EOF | ./build/qemu-system-x86_64 \`\ +`-display none -machine accel=qtest, -m 512M -machine q35 -nodefaults \`\ +`-device megasas -device scsi-cd,drive=null0 -blockdev \`\ +`driver=null-co,read-zeroes=on,node-name=null0 -qtest stdio`\ +`outl 0xcf8 0x80000818`\ +`outl 0xcfc 0xc000`\ +`outl 0xcf8 0x80000804`\ +`outw 0xcfc 0x05`\ +`write 0x20 0x1 0x03`\ +`write 0x26 0x1 0x08`\ +`write 0x27 0x1 0x01`\ +`write 0x30 0x1 0x02`\ +`write 0x40 0x1 0x08`\ +`write 0x57 0x1 0x01`\ +`write 0x5a 0x1 0x08`\ +`outl 0xc03d 0x20000000`\ +`outl 0xc03d 0x00`\ +`EOF`\ +\ +Results in:\ +\ +`[R +0.081916] outl 0xcf8 0x80000818`\ +`[S +0.081986] OK`\ +`OK`\ +`[R +0.082033] outl 0xcfc 0xc000`\ +`[S +0.082083] OK`\ +`OK`\ +`[R +0.082102] outl 0xcf8 0x80000804`\ +`[S +0.082117] OK`\ +`OK`\ +`[R +0.082133] outw 0xcfc 0x05`\ +`[S +0.082926] OK`\ +`OK`\ +`[R +0.082961] write 0x20 0x1 0x03`\ +`[S +0.083688] OK`\ +`OK`\ +`[R +0.083731] write 0x26 0x1 0x08`\ +`[S +0.083754] OK`\ +`OK`\ +`[R +0.083780] write 0x27 0x1 0x01`\ +`[S +0.083799] OK`\ +`OK`\ +`[R +0.083817] write 0x30 0x1 0x02`\ +`[S +0.083850] OK`\ +`OK`\ +`[R +0.083872] write 0x40 0x1 0x08`\ +`[S +0.083903] OK`\ +`OK`\ +`[R +0.083925] write 0x57 0x1 0x01`\ +`[S +0.083947] OK`\ +`OK`\ +`[R +0.083962] write 0x5a 0x1 0x08`\ +`[S +0.083985] OK`\ +`OK`\ +`[R +0.084000] outl 0xc03d 0x20000000`\ +`[S +0.085531] OK`\ +`OK`\ +`[R +0.085570] outl 0xc03d 0x00`\ +`[S +0.085673] OK`\ +`OK`\ +`qemu/include/exec/memory.h:1152:12: runtime error: member access within null pointer of type 'AddressSpace' (aka 'struct AddressSpace')`\ +`SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior qemu/include/exec/memory.h:1152:12 in` \ +`AddressSanitizer:DEADLYSIGNAL`\ +`=================================================================`\ +`==168244==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000020 (pc 0x56259b9829ac bp 0x000000000001 sp 0x7ffe62140220 T0)`\ +`==168244==The signal is caused by a READ memory access.`\ +`==168244==Hint: address points to the zero page.`\ + `#0 0x56259b9829ac in address_space_to_flatview qemu/include/exec/memory.h:1152:12`\ + `#1 0x56259b9829ac in address_space_write qemu/build/../system/physmem.c:2929:14`\ + `#2 0x56259b98665e in address_space_unmap qemu/build/../system/physmem.c:3272:9`\ + `#3 0x56259af31dce in dma_memory_unmap qemu/include/sysemu/dma.h:236:5`\ + `#4 0x56259af31dce in dma_blk_unmap qemu/build/../system/dma-helpers.c:93:9`\ + `#5 0x56259af2f220 in dma_complete qemu/build/../system/dma-helpers.c:105:5`\ + `#6 0x56259af2f220 in dma_blk_cb qemu/build/../system/dma-helpers.c:129:9`\ + `#7 0x56259bce7041 in blk_aio_complete qemu/build/../block/block-backend.c:1555:9`\ + `#8 0x56259c224495 in aio_bh_call qemu/build/../util/async.c:171:5`\ + `#9 0x56259c224ca6 in aio_bh_poll qemu/build/../util/async.c:218:13`\ + `#10 0x56259c1b9b89 in aio_dispatch qemu/build/../util/aio-posix.c:423:5`\ + `#11 0x56259c228f40 in aio_ctx_dispatch qemu/build/../util/async.c:360:5`\ + `#12 0x7f2b8c0a07a8 in g_main_context_dispatch (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x547a8) (BuildId: 9f90bd7bbfcf84a1f1c5a6102f70e6264837b9d4)`\ + `#13 0x56259c22a1ed in glib_pollfds_poll qemu/build/../util/main-loop.c:287:9`\ + `#14 0x56259c22a1ed in os_host_main_loop_wait qemu/build/../util/main-loop.c:310:5`\ + `#15 0x56259c22a1ed in main_loop_wait qemu/build/../util/main-loop.c:589:11`\ + `#16 0x56259af5159e in qemu_main_loop qemu/build/../system/runstate.c:796:9`\ + `#17 0x56259baefdb4 in qemu_default_main qemu/build/../system/main.c:37:14`\ + `#18 0x7f2b8aff7249 (/lib/x86_64-linux-gnu/libc.so.6+0x27249) (BuildId: 82ce4e6e4ef08fa58a3535f7437bd3e592db5ac0)`\ + `#19 0x7f2b8aff7304 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x27304) (BuildId: 82ce4e6e4ef08fa58a3535f7437bd3e592db5ac0)`\ + `#20 0x562599f60b70 in _start (qemu/build/qemu-system-x86_64+0x20feb70) (BuildId: 48f1333e9a9d60383d8c9e0db5f690e7c26e1bb2)`\ +`AddressSanitizer can not provide additional info.`\ +`SUMMARY: AddressSanitizer: SEGV qemu/include/exec/memory.h:1152:12 in address_space_to_flatview`\ +`==168244==ABORTING` + +\ +But, if we manually put all of those qtest commands and wait for each command to complete, QEMU doesn't fail. It's because of possible race condition - while QEMU still mapping memory, we already starting to unmap it. It results in this crash. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2415 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2415 new file mode 100644 index 000000000..d586a7342 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2415 @@ -0,0 +1,53 @@ +Assertion `r->req.aiocb == NULL' in am53c974 device +Description of problem: +The following log reveals it: + +``` +qemu-truman-x86_64-4467afcc: qemu/hw/scsi/scsi-disk.c:558: void scsi_write_data(SCSIRequest *): Assertion `r->req.aiocb == NULL' failed. +==2957464== ERROR: libFuzzer: deadly signal + #0 0x55e76f00e911 in __sanitizer_print_stack_trace llvm/compiler-rt/lib/asan/asan_stack.cpp:87:3 + #1 0x55e76ef88fb8 in fuzzer::PrintStackTrace() llvm/compiler-rt/lib/fuzzer/FuzzerUtil.cpp:210:5 + #2 0x55e76ef6d1b3 in fuzzer::Fuzzer::CrashCallback() llvm/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:233:3 + #3 0x7f83d604251f (/lib/x86_64-linux-gnu/libc.so.6+0x4251f) + #4 0x7f83d60969fb in __pthread_kill_implementation nptl/./nptl/pthread_kill.c:43:17 + #5 0x7f83d60969fb in __pthread_kill_internal nptl/./nptl/pthread_kill.c:78:10 + #6 0x7f83d60969fb in pthread_kill nptl/./nptl/pthread_kill.c:89:10 + #7 0x7f83d6042475 in gsignal signal/../sysdeps/posix/raise.c:26:13 + #8 0x7f83d60287f2 in abort stdlib/./stdlib/abort.c:79:7 + #9 0x7f83d602871a in __assert_fail_base assert/./assert/assert.c:92:3 + #10 0x7f83d6039e95 in __assert_fail assert/./assert/assert.c:101:3 + #11 0x55e76fbb55a5 in scsi_write_data qemu/hw/scsi/scsi-disk.c:558:5 + #12 0x55e76fb95a1f in scsi_req_continue qemu/hw/scsi/scsi-bus.c + #13 0x55e76fbfe0cc in esp_do_dma qemu/hw/scsi/esp.c + #14 0x55e76fc0be39 in handle_ti qemu/hw/scsi/esp.c:1104:9 + #15 0x55e76fc042f6 in esp_run_cmd qemu/hw/scsi/esp.c:1186:9 + #16 0x55e76fc042f6 in esp_reg_write qemu/hw/scsi/esp.c:1304:9 + #17 0x55e76fc1329b in esp_pci_io_write qemu/hw/scsi/esp-pci.c:248:9 +``` +Steps to reproduce: +``` +cat << EOF | qemu-system-x86_64 -display none\ +-machine accel=qtest, -m 512M -device am53c974,id=scsi -device \ +scsi-hd,drive=disk0 -drive id=disk0,if=none,file=null-co://,format=raw \ +-nodefaults -qtest stdio +outl 0xcf8 0x80001010 +outl 0xcfc 0xc000 +outl 0xcf8 0x80001004 +outw 0xcfc 0x05 +outl 0xc03e 0x030000 +outl 0xc009 0xc1000000 +outl 0xc008 0x8a +outl 0xc00d 0x0 +outl 0xc009 0x00 +outl 0xc00c 0x11 +outl 0xc00d 0x0 +outl 0xc00d 0x00 +outl 0xc00d 0x0 +outw 0xc00f 0x00 +outb 0xc00d 0x0 +outl 0xc00d 0x0 +outl 0xc009 0x41000000 +outb 0xc00c 0x90 +outl 0xc00d 0x0 +EOF +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2416 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2416 new file mode 100644 index 000000000..c2df3b7ce --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2416 @@ -0,0 +1,39 @@ +Assertion failure in virtio_snd_get_qemu_format() +Description of problem: +The following log reveals it: + +``` +ERROR:hw/audio/virtio-snd.c:356:virtio_snd_get_qemu_format: code should not be reached +Bail out! ERROR:hw/audio/virtio-snd.c:356:virtio_snd_get_qemu_format: code should not be reached +Aborted +``` +Steps to reproduce: +``` +cat << EOF | qemu-system-x86_64 -display none \ +-machine accel=qtest, -m 512M -machine q35 -device \ +virtio-sound,audiodev=my_audiodev,streams=2 -audiodev \ +alsa,id=my_audiodev -qtest stdio +outl 0xcf8 0x80001804 +outw 0xcfc 0x06 +outl 0xcf8 0x80001820 +outl 0xcfc 0xe0008000 +write 0xe0008020 0x4 0x00001000 +write 0xe0008028 0x4 0x00101000 +write 0xe000801c 0x1 0x01 +write 0x10c000 0x1 0x01 +write 0x10c001 0x1 0x01 +write 0x10c014 0x1 0x01 +write 0x10c015 0x1 0x51 +write 0x100001 0x1 0xc0 +write 0x100002 0x1 0x10 +write 0x100008 0x1 0x18 +write 0x10f000 0x1 0x02 +write 0x10f001 0x1 0x01 +write 0x100021 0x1 0xf0 +write 0x100022 0x1 0x10 +write 0x100028 0x1 0x08 +write 0x101006 0x1 0x02 +write 0x101002 0x1 0x02 +write 0xe000b001 0x1 0x00 +EOF +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2417 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2417 new file mode 100644 index 000000000..a9a95f114 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2417 @@ -0,0 +1,5 @@ +qemu-img allocates full size on exFAT when metadata preallocation is requested +Description of problem: +`qemu-img` seems to preallocate the full size of a qcow2 image on exFAT rather than just the metadata when that is requested. This was initially seen via libvirt/libvirt#649. exFAT does not support sparse files. +Steps to reproduce: +1. Run command diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2418 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2418 new file mode 100644 index 000000000..f390918cf --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2418 @@ -0,0 +1,12 @@ +[Gfxstream BUG] +Description of problem: +I tried to test gfxstream with qemu,I build qemu-9.0.1 with --enable-rutabaga-gfx flag,but after I have compiled and try to boot my Virtual Devices,it crashed and told me with "invalid rutabaga build parameters: gfxstream feature not enabled" + +{width=1276 height=99} +Steps to reproduce: +1.Compile the qemu with kvm,vhost,rutabaga_gfxstream,virgl support +2.run the virtual machine with my command + +But I found an interesting thing:If I build and install AEMU&Gfxstream at /usr in place of /usr/local,I could boot Virtual Machine normally😂 + +Could developers solve the problems?Thanks! diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/242 b/gitlab/issues_text/target_missing/host_missing/accel_missing/242 new file mode 100644 index 000000000..71a019b4b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/242 @@ -0,0 +1 @@ +Implementation of Virtual Battery for Battery Status diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2421 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2421 new file mode 100644 index 000000000..441fe6ed4 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2421 @@ -0,0 +1,18 @@ +Cannot boot ArcaOS 5.1.0 (a distro of OS/2 Warp 4.52) in UEFI mode +Description of problem: +ArcaOS has added the UEFI support since 5.1.0, it has been tested on my physical machine(Ryzen 3300X + RTX2060 Super), and VirtualBox with an `Other x64` machine(the new OS/2 bootloader used in UEFI mode is x64 only). + +Fixes applied to #2198 are perfectly worked in legacy BIOS mode, but if I tried to boot it in UEFI mode, it will stuck on logo screen, and if I enable verbose mode in boot menu, nothing will be shown on the screen and serial ports. + +It happens in both `i440fx` machine type and `q35` machine type. +Steps to reproduce: +1. Install latest qemu HEAD version via `brew install qemu --HEAD` +2. Create new virtual disk via `qemu-img create -f qcow2 hdd.img 20G` +3. Copy EFI bios file and var file + ``` + cp /opt/homebrew/Cellar/qemu/HEAD-1a2d52c/share/qemu/edk2-x86_64-code.fd bios.fd + cp /opt/homebrew/Cellar/qemu/HEAD-1a2d52c/share/qemu/edk2-i386-vars.fd vars.fd + ``` +4. Launch it +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2423 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2423 new file mode 100644 index 000000000..b84022dfa --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2423 @@ -0,0 +1,34 @@ +`qemu -serial stdio` leaves stdout in non-blocking mode +Description of problem: +When `-serial stdio` is used, qemu exits leaving stdout in non-blocking mode. Although it [attempts](https://gitlab.com/qemu-project/qemu/-/blob/1a2d52c7fcaeaaf4f2fe8d4d5183dccaeab67768/chardev/char-stdio.c#L52) to restore stdin to blocking mode, it misses that stdout also gets O_NONBLOCK by [qemu_chr_open_fd](https://gitlab.com/qemu-project/qemu/-/blob/1a2d52c7fcaeaaf4f2fe8d4d5183dccaeab67768/chardev/char-stdio.c#L116) ([here](https://gitlab.com/qemu-project/qemu/-/blob/1a2d52c7fcaeaaf4f2fe8d4d5183dccaeab67768/chardev/char-fd.c#L215)). It causes the next applications in the script misbehave because they get unexpected EAGAIN on write to stdout. +Steps to reproduce: +Run the following script: + +``` +#!/usr/bin/env bash + +qemu-system-x86_64 -nodefaults -display none -no-reboot -serial stdio & +PID="$!" +sleep 5 +kill "$PID" +wait "$PID" +echo "EXITING $?" + +sleep 5 +seq 1 400000 +``` + +The seq command will be interrupted prematurely: + +``` +... +5143 +5144 +5145⏎ wResource temporarily unavailable +write: Resource temporarily unavailable +write: Resource temporarily unavailable +``` + +When run from fish shell, it will also start misbehaving when running next commands (fish bug report: https://github.com/fish-shell/fish-shell/issues/10600). +Additional information: +Expect a patch from me soon. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2424 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2424 new file mode 100644 index 000000000..de417ad72 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2424 @@ -0,0 +1,318 @@ +Fatal error: futex robust_list not initialized by pthreads (Unknown syscall 386) +Description of problem: +Seems like steamcmd modified their binary with a function unimplemented by QEMU just recently. This was working perfectly until then. I did some strace debugging and came up with this error: `set_robust_list(0x40b7be2c,12) = -1 errno=38 (Function not implemented)`. I even tried doing `qemu-arm` over `box86` just to see if it'll work but still got that same error. However, using `box86` alone worked. + +I have my reasons of wanting to use `qemu-i386` over `box86` mainly due to it being compilable into an ARM64 binary unlike `box86` which is only an ARM binary. Performance doesn't really matter as it's only being used to download server files. Running QEMU was the only option working for people on M-series Macs to run steamcmd in a container reliably over Docker Desktop as those CPUs don't have 32-bit support. Even if I force them to use only `box86`, Mac's Docker Desktop runs QEMU over the image to emulate 32-bit support which causes the same error. +Steps to reproduce: +1. Install Docker +2. Run `docker run -it --pull=always sonroyaalmerol/steamcmd-arm64:root` +3. Inside the container shell, run `LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/steam/steamcmd/linux32 qemu-i386-static /home/steam/steamcmd/linux32/steamcmd +@sSteamCmdForcePlatformType linux +@sSteamCmdForcePlatformBitness 64 +force_install_dir "/palworld" +login anonymous +app_update 2394010 validate +quit` +Additional information: +I'm running all these inside a Docker container. I maintain a Docker image that is meant to be a base image for steamcmd-based dedicated servers (https://github.com/sonroyaalmerol/steamcmd-arm64). + +I tried both the `qemu-user-static` package from Debian repos (which I believe is v7.2) and building straight from the source (stable-9.0 tag) with no luck. + +strace from the command: +``` +25 brk(NULL) = 0x00a89000 +25 mmap2(NULL,8192,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANONYMOUS,-1,0) = 0x40839000 +25 access("/etc/ld.so.preload",R_OK) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"tls/i686/sse2/libdl.so.2",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"tls/i686/libdl.so.2",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"tls/sse2/libdl.so.2",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"tls/libdl.so.2",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"i686/sse2/libdl.so.2",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"i686/libdl.so.2",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"sse2/libdl.so.2",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"libdl.so.2",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"/home/steam/steamcmd/linux32/tls/i686/sse2/libdl.so.2",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 statx(AT_FDCWD,"/home/steam/steamcmd/linux32/tls/i686/sse2",AT_NO_AUTOMOUNT|AT_STATX_SYNC_AS_STAT,STATX_BASIC_STATS,0x407ffdb8) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"/home/steam/steamcmd/linux32/tls/i686/libdl.so.2",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 statx(AT_FDCWD,"/home/steam/steamcmd/linux32/tls/i686",AT_NO_AUTOMOUNT|AT_STATX_SYNC_AS_STAT,STATX_BASIC_STATS,0x407ffdb8) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"/home/steam/steamcmd/linux32/tls/sse2/libdl.so.2",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 statx(AT_FDCWD,"/home/steam/steamcmd/linux32/tls/sse2",AT_NO_AUTOMOUNT|AT_STATX_SYNC_AS_STAT,STATX_BASIC_STATS,0x407ffdb8) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"/home/steam/steamcmd/linux32/tls/libdl.so.2",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 statx(AT_FDCWD,"/home/steam/steamcmd/linux32/tls",AT_NO_AUTOMOUNT|AT_STATX_SYNC_AS_STAT,STATX_BASIC_STATS,0x407ffdb8) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"/home/steam/steamcmd/linux32/i686/sse2/libdl.so.2",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 statx(AT_FDCWD,"/home/steam/steamcmd/linux32/i686/sse2",AT_NO_AUTOMOUNT|AT_STATX_SYNC_AS_STAT,STATX_BASIC_STATS,0x407ffdb8) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"/home/steam/steamcmd/linux32/i686/libdl.so.2",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 statx(AT_FDCWD,"/home/steam/steamcmd/linux32/i686",AT_NO_AUTOMOUNT|AT_STATX_SYNC_AS_STAT,STATX_BASIC_STATS,0x407ffdb8) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"/home/steam/steamcmd/linux32/sse2/libdl.so.2",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 statx(AT_FDCWD,"/home/steam/steamcmd/linux32/sse2",AT_NO_AUTOMOUNT|AT_STATX_SYNC_AS_STAT,STATX_BASIC_STATS,0x407ffdb8) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"/home/steam/steamcmd/linux32/libdl.so.2",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 statx(AT_FDCWD,"/home/steam/steamcmd/linux32",AT_NO_AUTOMOUNT|AT_STATX_SYNC_AS_STAT,STATX_BASIC_STATS,0x407ffdb8) = 0 +25 openat(AT_FDCWD,"/etc/ld.so.cache",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 3 +25 statx(3,"",AT_EMPTY_PATH|AT_NO_AUTOMOUNT|AT_STATX_SYNC_AS_STAT,STATX_BASIC_STATS,0x407ffe38) = 0 +25 mmap2(NULL,11734,PROT_READ,MAP_PRIVATE,3,0) = 0x4083b000 +25 close(3) = 0 +25 openat(AT_FDCWD,"/lib/i386-linux-gnu/libdl.so.2",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 3 +25 read(3,0x408000a0,512) = 512 +25 statx(3,"",AT_EMPTY_PATH|AT_NO_AUTOMOUNT|AT_STATX_SYNC_AS_STAT,STATX_BASIC_STATS,0x407ffdd8) = 0 +25 mmap2(NULL,16392,PROT_READ,MAP_PRIVATE|MAP_DENYWRITE,3,0) = 0x4083e000 +25 mmap2(0x4083f000,4096,PROT_EXEC|PROT_READ,MAP_PRIVATE|MAP_DENYWRITE|MAP_FIXED,3,0x1) = 0x4083f000 +25 mmap2(0x40840000,4096,PROT_READ,MAP_PRIVATE|MAP_DENYWRITE|MAP_FIXED,3,0x2) = 0x40840000 +25 mmap2(0x40841000,8192,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_DENYWRITE|MAP_FIXED,3,0x2) = 0x40841000 +25 close(3) = 0 +25 openat(AT_FDCWD,"tls/i686/sse2/librt.so.1",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"tls/i686/librt.so.1",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"tls/sse2/librt.so.1",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"tls/librt.so.1",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"i686/sse2/librt.so.1",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"i686/librt.so.1",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"sse2/librt.so.1",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"librt.so.1",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"/home/steam/steamcmd/linux32/librt.so.1",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"/lib/i386-linux-gnu/librt.so.1",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 3 +25 read(3,0x40800080,512) = 512 +25 statx(3,"",AT_EMPTY_PATH|AT_NO_AUTOMOUNT|AT_STATX_SYNC_AS_STAT,STATX_BASIC_STATS,0x407ffdb8) = 0 +25 mmap2(NULL,16400,PROT_READ,MAP_PRIVATE|MAP_DENYWRITE,3,0) = 0x40843000 +25 mmap2(0x40844000,4096,PROT_EXEC|PROT_READ,MAP_PRIVATE|MAP_DENYWRITE|MAP_FIXED,3,0x1) = 0x40844000 +25 mmap2(0x40845000,4096,PROT_READ,MAP_PRIVATE|MAP_DENYWRITE|MAP_FIXED,3,0x2) = 0x40845000 +25 mmap2(0x40846000,8192,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_DENYWRITE|MAP_FIXED,3,0x2) = 0x40846000 +25 close(3) = 0 +25 openat(AT_FDCWD,"tls/i686/sse2/libm.so.6",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"tls/i686/libm.so.6",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"tls/sse2/libm.so.6",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"tls/libm.so.6",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"i686/sse2/libm.so.6",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"i686/libm.so.6",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"sse2/libm.so.6",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"libm.so.6",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"/home/steam/steamcmd/linux32/libm.so.6",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"/lib/i386-linux-gnu/libm.so.6",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 3 +25 read(3,0x40800060,512) = 512 +25 statx(3,"",AT_EMPTY_PATH|AT_NO_AUTOMOUNT|AT_STATX_SYNC_AS_STAT,STATX_BASIC_STATS,0x407ffd98) = 0 +25 mmap2(NULL,1065052,PROT_READ,MAP_PRIVATE|MAP_DENYWRITE,3,0) = 0x40848000 +25 mmap2(0x40855000,786432,PROT_EXEC|PROT_READ,MAP_PRIVATE|MAP_DENYWRITE|MAP_FIXED,3,0xd) = 0x40855000 +25 mmap2(0x40915000,221184,PROT_READ,MAP_PRIVATE|MAP_DENYWRITE|MAP_FIXED,3,0xcd) = 0x40915000 +25 mmap2(0x4094b000,8192,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_DENYWRITE|MAP_FIXED,3,0x103) = 0x4094b000 +25 close(3) = 0 +25 openat(AT_FDCWD,"tls/i686/sse2/libpthread.so.0",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"tls/i686/libpthread.so.0",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"tls/sse2/libpthread.so.0",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"tls/libpthread.so.0",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"i686/sse2/libpthread.so.0",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"i686/libpthread.so.0",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"sse2/libpthread.so.0",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"libpthread.so.0",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"/home/steam/steamcmd/linux32/libpthread.so.0",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"/lib/i386-linux-gnu/libpthread.so.0",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 3 +25 read(3,0x40800040,512) = 512 +25 statx(3,"",AT_EMPTY_PATH|AT_NO_AUTOMOUNT|AT_STATX_SYNC_AS_STAT,STATX_BASIC_STATS,0x407ffd78) = 0 +25 mmap2(NULL,16392,PROT_READ,MAP_PRIVATE|MAP_DENYWRITE,3,0) = 0x4094d000 +25 mmap2(0x4094e000,4096,PROT_EXEC|PROT_READ,MAP_PRIVATE|MAP_DENYWRITE|MAP_FIXED,3,0x1) = 0x4094e000 +25 mmap2(0x4094f000,4096,PROT_READ,MAP_PRIVATE|MAP_DENYWRITE|MAP_FIXED,3,0x2) = 0x4094f000 +25 mmap2(0x40950000,8192,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_DENYWRITE|MAP_FIXED,3,0x2) = 0x40950000 +25 close(3) = 0 +25 openat(AT_FDCWD,"tls/i686/sse2/libc.so.6",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"tls/i686/libc.so.6",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"tls/sse2/libc.so.6",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"tls/libc.so.6",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"i686/sse2/libc.so.6",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"i686/libc.so.6",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"sse2/libc.so.6",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"libc.so.6",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"/home/steam/steamcmd/linux32/libc.so.6",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"/lib/i386-linux-gnu/libc.so.6",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 3 +25 read(3,0x40800020,512) = 512 +25 statx(3,"",AT_EMPTY_PATH|AT_NO_AUTOMOUNT|AT_STATX_SYNC_AS_STAT,STATX_BASIC_STATS,0x407ffd58) = 0 +25 mmap2(NULL,2259228,PROT_READ,MAP_PRIVATE|MAP_DENYWRITE,3,0) = 0x40952000 +25 mmap2(0x40974000,1544192,PROT_EXEC|PROT_READ,MAP_PRIVATE|MAP_DENYWRITE|MAP_FIXED,3,0x22) = 0x40974000 +25 mmap2(0x40aed000,524288,PROT_READ,MAP_PRIVATE|MAP_DENYWRITE|MAP_FIXED,3,0x19b) = 0x40aed000 +25 mmap2(0x40b6d000,12288,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_DENYWRITE|MAP_FIXED,3,0x21b) = 0x40b6d000 +25 mmap2(0x40b70000,39196,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANONYMOUS|MAP_FIXED,-1,0) = 0x40b70000 +25 close(3) = 0 +25 mmap2(NULL,8192,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANONYMOUS,-1,0) = 0x40b7a000 +25 mmap2(NULL,16384,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANONYMOUS,-1,0) = 0x40b7c000 +25 set_thread_area(0x408008b0) = 0 +25 set_tid_address(0x40b7be28) = 25 +25 set_robust_list(0x40b7be2c,12) = -1 errno=38 (Function not implemented) +25 Unknown syscall 386 +25 mprotect(0x40b6d000,8192,PROT_READ) = 0 +25 mprotect(0x40950000,4096,PROT_READ) = 0 +25 mprotect(0x4094b000,4096,PROT_READ) = 0 +25 mprotect(0x40846000,4096,PROT_READ) = 0 +25 mprotect(0x40841000,4096,PROT_READ) = 0 +25 mprotect(0x00a18000,143360,PROT_READ) = 0 +25 mprotect(0x40833000,8192,PROT_READ) = 0 +25 ugetrlimit(3,1082132628,1085730804,1,2097152,1082133208) = 0 +25 munmap(0x4083b000,11734) = 0 +25 getrandom(0x40b72b50,4,1) = 4 +25 brk(NULL) = 0x00a89000 +25 brk(0x00aaa000) = 0x00aaa000 +25 brk(0x00aab000) = 0x00aab000 +25 brk(0x00acc000) = 0x00acc000 +25 futex(0x00a867f0,FUTEX_PRIVATE_FLAG|FUTEX_WAKE,2147483647,NULL,0x40b6eff4,1085730804) = 0 +25 futex(0x00a867f8,FUTEX_PRIVATE_FLAG|FUTEX_WAKE,2147483647,NULL,0x40b6eff4,1085730804) = 0 +25 clock_gettime64(CLOCK_BOOTTIME,0x40800b6c) = 0 ({tv_sec=4668200,tv_nsec=47711961}) +25 gettid() = 25 +25 clock_gettime64(CLOCK_BOOTTIME,0x40800b5c) = 0 ({tv_sec=4668200,tv_nsec=48585844}) +25 getpid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 rt_sigprocmask(SIG_BLOCK,0x407fe9f0,NULL,8) = 0 +25 rt_sigaction(SIGPIPE,0x407fe804,0x407fe890) = 0 +25 ugetrlimit(7,1082125036,1085730804,10725408,13,1082133352) = 0 +25 prlimit64(0,RLIMIT_NOFILE,{rlim_cur=1048576,rlim_max=1048576},NULL) = 0 +25 openat(AT_FDCWD,"/usr/lib/locale/locale-archive",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 3 +25 statx(3,"",AT_EMPTY_PATH|AT_NO_AUTOMOUNT|AT_STATX_SYNC_AS_STAT,STATX_BASIC_STATS,0x407fe5bc) = 0 +25 mmap2(NULL,2097152,PROT_READ,MAP_PRIVATE,3,0) = 0x40b80000 +25 mmap2(NULL,2596864,PROT_READ,MAP_PRIVATE,3,0x6f) = 0x40d80000 +25 close(3) = 0 +25 readlink("/proc/self/exe",0x00a8c450,4095) = 37 +25 readlink("/proc/self/exe",0x00a45060,4095) = 37 +25 chdir("/home/steam/steamcmd") = 0 +25 gettid() = 25 +25 clock_gettime64(CLOCK_BOOTTIME,0x407fe92c) = 0 ({tv_sec=4668200,tv_nsec=87889751}) +25 clock_gettime64(CLOCK_BOOTTIME,0x407fe92c) = 0 ({tv_sec=4668200,tv_nsec=89062235}) +25 clock_gettime64(CLOCK_REALTIME_COARSE,0x407fea1c) = 0 ({tv_sec=1720063413,tv_nsec=948892664}) +25 openat(AT_FDCWD,"/home/steam/steamcmd/steam.cfg",O_RDONLY|O_LARGEFILE) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"/home/steam/steamcmd/Steam.cfg",O_RDONLY|O_LARGEFILE) = -1 errno=2 (No such file or directory) +25 readlink("/root",0x407fb530,1023) = -1 errno=22 (Invalid argument) +25 readlink("/root/.steam",0x407fb530,1023) = -1 errno=2 (No such file or directory) +25 stat64("/root/.steam/steam",0x407fb8f0) = -1 errno=2 (No such file or directory) +25 mkdir("/root/Steam/logs",0777) = -1 errno=17 (File exists) +25 stat64("/root/Steam/logs/bootstrap_log.txt",0x407fd8f0) = 0 +25 lstat64("/root/Steam/logs",0x407fd850) = 0 +25 openat(AT_FDCWD,"/root/Steam/logs/bootstrap_log.txt",O_RDWR|O_LARGEFILE) = 3 +25 flock(3,5,10725408,2,10725408,1082120376) = 0 +25 fcntl64(3,F_SETFD,1) = 0 +25 _llseek(3,0,0,0x407fd8a0,SEEK_END) = 0 +25 write(3,0x9022f3,4) = 4 +25 clock_gettime64(CLOCK_REALTIME_COARSE,0x407fd90c) = 0 ({tv_sec=1720063413,tv_nsec=960892708}) +25 openat(AT_FDCWD,"/etc/localtime",O_RDONLY|O_CLOEXEC) = 4 +25 statx(4,"",AT_EMPTY_PATH|AT_NO_AUTOMOUNT|AT_STATX_SYNC_AS_STAT,STATX_BASIC_STATS,0x407fd65c) = 0 +25 statx(4,"",AT_EMPTY_PATH|AT_NO_AUTOMOUNT|AT_STATX_SYNC_AS_STAT,STATX_BASIC_STATS,0x407fd52c) = 0 +25 read(4,0xaa28b0,4096) = 114 +25 _llseek(4,4294967295,4294967236,0x407fd630,SEEK_CUR) = 0 +25 read(4,0xaa28b0,4096) = 60 +25 close(4) = 0 +25 write(3,0xa90d60,68) = 68 +25 clock_gettime64(CLOCK_REALTIME_COARSE,0x407fd90c) = 0 ({tv_sec=1720063413,tv_nsec=976892768}) +25 write(3,0xa922e0,276) = 276 +25 getcwd(0xaa28b0,4096) = 21 +25 stat64("/home/steam/steamcmd/package/beta",0x407fb8e0) = -1 errno=2 (No such file or directory) +25 openat(AT_FDCWD,"/home/steam/steamcmd/package/steam_cmd_linux.manifest",O_RDONLY|O_LARGEFILE) = 4 +25 flock(4,5,10725408,0,10725408,1082116024) = 0 +25 fcntl64(4,F_SETFD,1) = 0 +25 fstat64(4,0x407fc890) = 0 +25 read(4,0xab1e20,1838) = 1838 +25 close(4) = 0 +25 mmap2(NULL,266240,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANONYMOUS,-1,0) = 0x40ffa000 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 gettid() = 25 +25 munmap(0x40ffa000,266240) = 0 +25 openat(AT_FDCWD,"/home/steam/steamcmd/linux32/crashhandler.so",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 4 +25 read(4,0x407fc180,512) = 512 +25 statx(4,"",AT_EMPTY_PATH|AT_NO_AUTOMOUNT|AT_STATX_SYNC_AS_STAT,STATX_BASIC_STATS,0x407fbeb8) = 0 +25 mmap2(NULL,661476,PROT_READ,MAP_PRIVATE|MAP_DENYWRITE,4,0) = 0x40ffa000 +25 mmap2(0x41002000,442368,PROT_EXEC|PROT_READ,MAP_PRIVATE|MAP_DENYWRITE|MAP_FIXED,4,0x8) = 0x41002000 +25 mmap2(0x4106e000,147456,PROT_READ,MAP_PRIVATE|MAP_DENYWRITE|MAP_FIXED,4,0x74) = 0x4106e000 +25 mmap2(0x41092000,16384,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_DENYWRITE|MAP_FIXED,4,0x97) = 0x41092000 +25 mmap2(0x41096000,22500,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANONYMOUS|MAP_FIXED,-1,0) = 0x41096000 +25 close(4) = 0 +25 mprotect(0x41092000,12288,PROT_READ) = 0 +25 clock_gettime64(CLOCK_REALTIME,0x407fc2ec) = 0 ({tv_sec=1720063414,tv_nsec=1788981}) +25 clock_gettime64(CLOCK_BOOTTIME,0x407fc31c) = 0 ({tv_sec=4668200,tv_nsec=139217662}) +25 gettid() = 25 +25 futex(0x41099f4c,FUTEX_PRIVATE_FLAG|FUTEX_WAKE,2147483647,NULL,0x40b6eff4,1085730804) = 0 +25 futex(0x41099f54,FUTEX_PRIVATE_FLAG|FUTEX_WAKE,2147483647,NULL,0x40b6eff4,1085730804) = 0 +25 clock_gettime64(CLOCK_BOOTTIME,0x407fc2ec) = 0 ({tv_sec=4668200,tv_nsec=147181452}) +25 getpid() = 25 +25 openat(AT_FDCWD,"/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq",O_RDONLY) = -1 errno=2 (No such file or directory) +25 clock_gettime64(CLOCK_REALTIME,0x407fc05c) = 0 ({tv_sec=1720063414,tv_nsec=15478752}) +25 clock_nanosleep(CLOCK_REALTIME,0,{tv_sec = 0,tv_nsec = 5000000},{tv_sec = 7,tv_nsec = 1593058279}) = 0 +25 clock_gettime64(CLOCK_REALTIME,0x407fc05c) = 0 ({tv_sec=1720063414,tv_nsec=21040173}) +25 clock_gettime64(CLOCK_REALTIME,0x407fc05c) = 0 ({tv_sec=1720063414,tv_nsec=21460575}) +25 clock_nanosleep(CLOCK_REALTIME,0,{tv_sec = 0,tv_nsec = 5000000},{tv_sec = 7,tv_nsec = 1593058279}) = 0 +25 clock_gettime64(CLOCK_REALTIME,0x407fc05c) = 0 ({tv_sec=1720063414,tv_nsec=26631394}) +25 openat(AT_FDCWD,"/proc/cpuinfo",O_RDONLY) = 4 +25 statx(4,"",AT_EMPTY_PATH|AT_NO_AUTOMOUNT|AT_STATX_SYNC_AS_STAT,STATX_BASIC_STATS,0x407fb8fc) = 0 +25 read(4,0xaa2ff0,1024) = 968 +25 read(4,0xaa2ff0,1024) = 0 +25 close(4) = 0 +25 gettid() = 25 +25 write(2,0x407fb120,57)Unable to determine CPU Frequency. Try defining CPU_MHZ. + = 57 +25 write(2,0x40b6fd47,1) + = 1 +25 statx(1,"",AT_EMPTY_PATH|AT_NO_AUTOMOUNT|AT_STATX_SYNC_AS_STAT,STATX_BASIC_STATS,0x407fa8fc) = 0 +25 write(1,0xaa2ff0,57)Unable to determine CPU Frequency. Try defining CPU_MHZ. + = 57 +25 openat(AT_FDCWD,"/proc/cpuinfo",O_RDONLY) = 4 +25 statx(4,"",AT_EMPTY_PATH|AT_NO_AUTOMOUNT|AT_STATX_SYNC_AS_STAT,STATX_BASIC_STATS,0x407fc1cc) = 0 +25 read(4,0xaa3400,1024) = 968 +25 read(4,0xaa3400,1024) = 0 +25 close(4) = 0 +25 write(1,0xaa2ff0,52)Redirecting stderr to '/root/Steam/logs/stderr.txt' + = 52 +25 openat(AT_FDCWD,"/root/Steam/logs/stderr.txt",O_WRONLY|O_CREAT|O_LARGEFILE|O_TRUNC,0666) = 4 +25 dup3(4,2,0)Logging directory: '/root/Steam/logs' +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2425 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2425 new file mode 100644 index 000000000..71580940d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2425 @@ -0,0 +1,7 @@ +Add support for the 1366x768 resolution to the -vga std output +Additional information: +There is a Debian [issue](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700055) about it back from 2013. The is also a 2024 thread [thread](https://lists.nongnu.org/archive/html/qemu-discuss/2024-07/msg00003.html) about it on the `qemu-user` mailing list. + +I failed to make it a feature reqeust by keeping the template text +`/label ~"kind::Feature Request"` +at the end of the message: *Gitlab* removes it automatically. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2427 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2427 new file mode 100644 index 000000000..4e467c621 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2427 @@ -0,0 +1,141 @@ +Heap-buffer-overflow in virtio-sound +Description of problem: +The following log reveals it: + +``` +==852995==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x50400002f2f9 at pc 0x5b291f531ba9 bp 0x7ffd8e80c0a0 sp 0x7ffd8e80c098 +WRITE of size 2 at 0x50400002f2f9 thread T0 + #0 0x5b291f531ba8 in clip_natural_int16_t_from_stereo audio/mixeng_template.h:133:16 + #1 0x5b291f4ea707 in audio_pcm_sw_read audio/audio.c:604:5 + #2 0x5b291f4e9502 in AUD_read audio/audio.c:900:16 + #3 0x5b291e6db7c7 in virtio_snd_pcm_in_cb hw/audio/virtio-snd.c:1279:24 + #4 0x5b291f4f3017 in audio_run_in audio/audio.c:1331:21 + #5 0x5b291f4eda89 in audio_run audio/audio.c:1389:5 + #6 0x5b291fa34311 in alsa_poll_handler audio/alsaaudio.c:205:9 + #7 0x5b2921054bb3 in aio_dispatch_handler util/aio-posix.c:372:9 + #8 0x5b292104b9d5 in aio_dispatch_handlers util/aio-posix.c:414:20 + #9 0x5b292104b4b9 in aio_dispatch util/aio-posix.c:424:5 + #10 0x5b29210ede0e in aio_ctx_dispatch util/async.c:360:5 + #11 0x79b4f927fd3a in g_main_context_dispatch (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x55d3a) (BuildId: 224ac2a88b72bc8e2fe8566ee28fae789fc69241) + #12 0x5b29210f1851 in glib_pollfds_poll util/main-loop.c:287:9 + #13 0x5b29210f007a in os_host_main_loop_wait util/main-loop.c:310:5 + #14 0x5b29210efc24 in main_loop_wait util/main-loop.c:589:11 + #15 0x5b291f5e5475 in qemu_main_loop system/runstate.c:795:9 + #16 0x5b292067eefb in qemu_default_main system/main.c:37:14 + #17 0x5b292067ef7d in main system/main.c:48:12 + #18 0x79b4f8829d8f in __libc_start_call_main csu/../sysdeps/nptl/libc_start_call_main.h:58:16 + #19 0x79b4f8829e3f in __libc_start_main csu/../csu/libc-start.c:392:3 + #20 0x5b291e29bef4 in _start (/usr/local/bin/qemu-system-x86_64+0x1c8fef4) + +0x50400002f2f9 is located 1 bytes after 40-byte region [0x50400002f2d0,0x50400002f2f8) +allocated by thread T0 here: + #0 0x5b291e339758 in calloc /home/runner/work/llvm-project/llvm-project/final/llvm-project/compiler-rt/lib/asan/asan_malloc_linux.cpp:77:3 + #1 0x79b4f9288c50 in g_malloc0 (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x5ec50) (BuildId: 224ac2a88b72bc8e2fe8566ee28fae789fc69241) + #2 0x5b29202d0efd in virtio_queue_notify hw/virtio/virtio.c:2297:9 + #3 0x5b291f3d242e in virtio_pci_notify_write hw/virtio/virtio-pci.c:1721:9 + #4 0x5b29203c82a4 in memory_region_write_accessor system/memory.c:497:5 + #5 0x5b29203c7951 in access_with_adjusted_size system/memory.c:573:18 + #6 0x5b29203c57eb in memory_region_dispatch_write system/memory.c:1521:16 + #7 0x5b292046cb42 in flatview_write_continue_step system/physmem.c:2757:18 + #8 0x5b292046c3c1 in flatview_write_continue system/physmem.c:2787:19 + #9 0x5b29204424c9 in flatview_write system/physmem.c:2818:12 + #10 0x5b2920441f1e in address_space_write system/physmem.c:2938:18 + #11 0x5b291f5d8eac in qtest_process_command system/qtest.c:643:9 + #12 0x5b291f5cfec5 in qtest_process_inbuf system/qtest.c:776:9 + #13 0x5b291f5de05e in qtest_read system/qtest.c:788:5 + #14 0x5b2920d2aef0 in qemu_chr_be_write_impl chardev/char.c:214:9 + #15 0x5b2920d2afb1 in qemu_chr_be_write chardev/char.c:226:9 + #16 0x5b2920d37388 in fd_chr_read chardev/char-fd.c:72:9 + #17 0x5b2920719767 in qio_channel_fd_source_dispatch io/channel-watch.c:84:12 + #18 0x79b4f927fc43 in g_main_context_dispatch (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x55c43) (BuildId: 224ac2a88b72bc8e2fe8566ee28fae789fc69241) + +SUMMARY: AddressSanitizer: heap-buffer-overflow audio/mixeng_template.h:133:16 in clip_natural_int16_t_from_stereo +Shadow bytes around the buggy address: + 0x50400002f000: fa fa fd fd fd fd fd fd fa fa fd fd fd fd fd fd + 0x50400002f080: fa fa fd fd fd fd fd fd fa fa fd fd fd fd fd fd + 0x50400002f100: fa fa fd fd fd fd fd fd fa fa fd fd fd fd fd fd + 0x50400002f180: fa fa 00 00 00 00 00 fa fa fa fd fd fd fd fd fd + 0x50400002f200: fa fa fd fd fd fd fd fd fa fa fd fd fd fd fd fd +=>0x50400002f280: fa fa fd fd fd fd fd fd fa fa 00 00 00 00 00[fa] + 0x50400002f300: fa fa fd fd fd fd fd fd fa fa fd fd fd fd fd fd + 0x50400002f380: fa fa fd fd fd fd fd fd fa fa fd fd fd fd fd fd + 0x50400002f400: fa fa fd fd fd fd fd fd fa fa fd fd fd fd fd fd + 0x50400002f480: fa fa fd fd fd fd fd fd fa fa fd fd fd fd fd fd + 0x50400002f500: fa fa fd fd fd fd fd fd fa fa fd fd fd fd fd fd +Shadow byte legend (one shadow byte represents 8 application bytes): + Addressable: 00 + Partially addressable: 01 02 03 04 05 06 07 + Heap left redzone: fa + Freed heap region: fd + Stack left redzone: f1 + Stack mid redzone: f2 + Stack right redzone: f3 + Stack after return: f5 + Stack use after scope: f8 + Global redzone: f9 + Global init order: f6 + Poisoned by user: f7 + Container overflow: fc + Array cookie: ac + Intra object redzone: bb + ASan internal: fe + Left alloca redzone: ca + Right alloca redzone: cb +``` +Steps to reproduce: +``` +cat << EOF | qemu-system-x86_64 -display none \ +-machine accel=qtest, -m 512M -machine q35 -device \ +virtio-sound,audiodev=my_audiodev,streams=2 -audiodev \ +alsa,id=my_audiodev -qtest stdio +outl 0xcf8 0x80001804 +outw 0xcfc 0x7 +outl 0xcf8 0x80001820 +outl 0xcfc 0xe0008000 +write 0xe0008020 0x4 0x00001000 +write 0xe0008028 0x4 0x00101000 +write 0xe0008016 0x1 0x03 +write 0xe0008020 0x4 0x00901000 +write 0xe0008028 0x4 0x00a01000 +write 0xe0008016 0x1 0x00 +write 0xe000801c 0x1 0x01 +write 0xe0008016 0x1 0x03 +write 0xe000801c 0x1 0x01 +write 0x100008 0x1 0x08 +write 0x109008 0x1 0x04 +write 0x11e000 0x1 0x04 +write 0x11e001 0x1 0x01 +write 0x11e004 0x1 0x01 +write 0x100081 0x1 0xe0 +write 0x100082 0x1 0x11 +write 0x100088 0x1 0x08 +write 0x10100a 0x1 0x08 +write 0x151000 0x1 0x01 +write 0x1090c1 0x1 0x10 +write 0x1090c2 0x1 0x15 +write 0x1090c8 0x1 0x04 +write 0x10a00c 0x1 0x0c +write 0x10a002 0x1 0x05 +write 0xe000b00c 0x1 0x03 +write 0x101002 0x1 0x1d +write 0xe000b001 0x1 0x00 +outl 0xcfc 0xe0008000 +outl 0xcf8 0x80001885 +outl 0xcf8 0x80001870 +outl 0xcf8 0x80001878 +inl 0xcfc +outl 0xcf8 0x80001870 +outl 0xcf8 0x80001863 +outl 0xcf8 0x80001853 +inb 0xcfc +outl 0xcf8 0x80001854 +inb 0xcfc +inb 0xcfc +outl 0xcf8 0x80001898 +inb 0xcfc +outl 0xcf8 0x80001899 +outl 0xcf8 0x80001870 +inb 0xcfc +inb 0xcfc +EOF +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2428 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2428 new file mode 100644 index 000000000..badee2b9b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2428 @@ -0,0 +1,29 @@ +Null-pointer-dereference in ufs +Description of problem: +The following log reveals it: + +``` +../hw/ufs/ufs.c:740:13: runtime error: member access within null pointer of type 'UfsSq' (aka 'struct UfsSq') +SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior ../hw/ufs/ufs.c:740:13 in +AddressSanitizer:DEADLYSIGNAL +================================================================= +==848760==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000020 (pc 0x6220e29edfce bp 0x7fffea0c6cf0 sp 0x7fffea0c6c40 T0) +==848760==The signal is caused by a READ memory access. +==848760==Hint: address points to the zero page. + #0 0x6220e29edfce in ufs_mcq_process_db hw/ufs/ufs.c:740:9 + #1 0x6220e29dc10f in ufs_write_mcq_op_reg hw/ufs/ufs.c:758:13 + #2 0x6220e29d85c6 in ufs_mmio_write hw/ufs/ufs.c:813:9 +``` +Steps to reproduce: +``` +cat << EOF | qemu-system-x86_64 \ +-display none -machine accel=qtest, -m 512M -M q35 -nodefaults -drive \ +file=null-co://,if=none,id=disk0 -device ufs,id=ufs_bus -device \ +ufs-lu,drive=disk0,bus=ufs_bus -qtest stdio +outl 0xcf8 0x80000810 +outl 0xcfc 0xe0000000 +outl 0xcf8 0x80000804 +outw 0xcfc 0x02 +write 0xe0001004 0x1 0x01 +EOF +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2430 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2430 new file mode 100644 index 000000000..14d4c1c9a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2430 @@ -0,0 +1,7 @@ +allocate / free need use glibs's function. +Description of problem: +https://gitlab.com/qemu-project/qemu/-/blob/master/hw/core/machine.c?ref_type=heads#L982 + +use g_free to free config,because it is allocated by g_malloc0 + +on windows,if use crt's free && glib's(DLL) g_malloc0 ,will crash. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2431 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2431 new file mode 100644 index 000000000..a886e7926 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2431 @@ -0,0 +1 @@ +we ship a single qemu.1 manpage supposedly applicable for all system emulators but it is full of qemu-system-x86_64 specific info/command lines diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2433 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2433 new file mode 100644 index 000000000..d41dc2ef0 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2433 @@ -0,0 +1,224 @@ +[TestCase] -object filter-redirector completely ignores linked bidirectional chardev, so encryption for netdev is broken +Description of problem: +If I form a wittingly broken network topology using -object filter-redirector and an encrypting bi-directional chardev linked to redirected traffic, the topology continues to function when it must not. See Fig.2. + +By "continues to function", I mean the two guest Windows XP from Fig.2 topology are able to see each other, join the same "MSHOME" workgroup, make shared folders which are mutually seen from each other and even send files to each other's shared folder! + +\ +Why do I consider Fig.2 a broken topology? It includes only one encrypting chardev, whereas a normal encrypted network topology must contain one encrypting and one decrypting chardev.\ +To form Fig.2 topology, follow "Steps to reproduce" section.\ +\ +At the same time, -object filter-redirector works perfectly if only uni-directional chardevs are used, see Fig.1 with corresponding commands to launch guest#1 qemu and guest#2 qemu. All network activities from previous paragraphs seem to function correctly both in Fig.1 and in Fig.2 + +If I put tls-creds=tls0, inside any "-chardev socket" switch in Fig.1 to make traffic encrypted without further decryption, local network between guests becomes broken (0 packets received), which is normal and expected behaviour.\ +\ +The end goal is to have netdev traffic encrypted. If anyone knows a workaround to encrypt netdev traffic on Windows hosts without installing crypto libs/drivers besides GnuTLS, please describe it in comments. + +*** Please note that some old broswers show Fig.1 and Fig.2 a little bit screwed. If so, please copy their source to Mousepad or Notepad - they must show topology correctly. And disable "Word Wrap" mode in your text editor, of course. *** + +``` + *********************** Fig. 1. Perfectly working network topology with uni-directional chardevs ************************* + + NOTE: rx:receive packets sent to the netdev + tx:receive packets sent by the netdev + First qemu Second qemu ++--------------------------------------------------------------------------------------------------+ +----------------------------------------+ +| | | | +| +----------------------------------------------------------------------------------------+ | | +------------------------------+ | +| | Guest Windows XP #1: | | | | Guest Windows XP #2: | | +| | | | | | | | +| | 169.254.144.98 IP, | | | | 169.254.144.99 IP, | | +| | 255.255.0.0 Net mask, | | | | 255.255.0.0 Net mask, | | +| | Gateway empty, | | | | Gateway empty, | | +| | DNS server empty, | | | | DNS server empty, | | +| | WINS server empty, | | | | WINS server empty, | | +| | DHCP off | | | | DHCP off | | +| +----------------------------------------------------------------------------------------+ | | +------------------------------+ | +| ^ | | | ^ | | +| | all | | | | | | +| | V | | | | | +| +--------------+ | | | | | +| | | | | | | | +| indev | filter | outdev | | | | | +| +-----> redirector >-------+ | | | | | +| | | | | | | | | | +| | | queue=all | | | | | | | +| | +--------------+ | | | | | | +| | | | | | | | +| +------------+ +------------+ | | | | | +| | | | | | | | +| +------------------+ +------------------+ | | +-------------------+ +------------------+ | | | | | +| | :9001 | | :9001 | | | | :9002 | | :9002 | | | | | | +| | uni-directional | | uni-directional | | | | uni-directional | | uni-directional | | | | all | | +| +-> chardev |->| chardev >-+ +-> chardev |->| chardev >-+ | | | | | +| | | | | | | | | | | | | | | | +| | | id=tx_in | |id=tx_out_to_guest| |id=rx_in_from_guest| | id=rx_out | | | | | | | +| | | server=on | | | | | | server=on | | | | | | | +| | +------------------+ +------------------+ +-------------------+ +------------------+ | | | | | | +| | | | | | | | +| | | | | | | | +| | +----------------+ +----------------+ | | | | | | +| | | | | | | | | | | | +| | | filter | | filter | | | | | | | +| +-----------------------< redirector | | redirector <------------------------+ | | | | | +| outdev | | | | indev | | | | | +| | queue=tx | | queue=rx | | | | | | +| +--------+-------+ +--------+-------+ | | | | | +| | | | | | | | +| | | | | | V | +| +--------------------------------^---------------------------V-----------------------------+ | | +--------------------------------+ | +| |==========================================================================================|------------->|================================| | +| | | | | | | | | | +| | netdev | mac=52:54:00:12:34:56 |7001:: ::7001| netdev | mac=52:54:00:12:34:57 | | +| | | | | | | | | | +| | | |<-------------| | | | +| +------------------------------------------------------------------------------------------+ | | +--------------------------------+ | +| | | | ++--------------------------------------------------------------------------------------------------+ +----------------------------------------+ + +Command to run Guest Windows XP #1 from Fig.1: + qemu-system-i386.exe \ + -accel tcg \ + -m 256M \ + -cpu Westmere \ + -hda d:\xp1.qcow2 \ + -usb -device usb-tablet \ + -netdev socket,id=net0,listen=localhost:7001 \ + -device rtl8139,netdev=net0,mac=52:54:00:12:34:56 \ + -chardev socket,id=tx_in,host=127.0.0.1,port=9001,server=on,wait=off \ + -chardev socket,id=tx_out_to_guest,host=127.0.0.1,port=9001 \ + -chardev socket,id=rx_out,host=127.0.0.1,port=9002,server=on,wait=off \ + -chardev socket,id=rx_in_from_guest,host=127.0.0.1,port=9002 \ + -object filter-redirector,netdev=net0,queue=tx,outdev=tx_in,id=tx1 \ + -object filter-redirector,netdev=net0,queue=rx,indev=rx_out,id=rx1 \ + -object filter-redirector,netdev=net0,queue=all,outdev=rx_in_from_guest,indev=tx_out_to_guest,id=inner_redirector + +Command to run Guest Windows XP #2 from Fig.1: + qemu-system-i386.exe + -accel tcg \ + -m 256M \ + -cpu Westmere \ + -hda d:\xp2.qcow2 \ + -usb -device usb-tablet \ + -netdev socket,id=net1,connect=localhost:7001 \ + -device rtl8139,netdev=net1,mac=52:54:00:12:34:57 + + + *********************** Fig. 2. Erroneously working network topology, despite encrypting bi-directional chardev ************************* + + NOTE: queue=rx:receive packets sent to the netdev + queue=tx:receive packets sent by the netdev + queue=all:receive packets sent by and to the netdev (both directions) + + First qemu Second qemu ++--------------------------------------------------------------------------------------------------+ +----------------------------------------+ +| | | | +| +----------------------------------------------------------------------------------------+ | | +------------------------------+ | +| | Guest Windows XP #1: | | | | Guest Windows XP #2: | | +| | | | | | | | +| | 169.254.144.98 IP, | | | | 169.254.144.99 IP, | | +| | 255.255.0.0 Net mask, | | | | 255.255.0.0 Net mask, | | +| | Gateway empty, | | | | Gateway empty, | | +| | DNS server empty, | | | | DNS server empty, | | +| | WINS server empty, | | | | WINS server empty, | | +| | DHCP off | | | | DHCP off | | +| +----------------------------------------------------------------------------------------+ | | +------------------------------+ | +| ^ | | | ^ | | +| | all | | | | | | +| | V | | | | | +| +-------------------+ | | | | | +| | | | | | | | +| +------>| filter | | | | | | +| | | redirector | | | | | | +| | +--<| | | | | | | +| | | | queue=all | | | | | | +| | | |id=inner_redirector| | | | | | +| | | +-----------V-------+ | | | | | +| | | | indev | | | | | +| | | | | | | | | +| | | | | | | | | +| | | +----------V-------+ +-----------------------+ | | | | | +| | | | :9001 | | | | | | | | +| | | | bi-directional | | -object tls-creds-psk | | | | | | +| | | |encrypting chardev| | | | | | | | +| | | | |---->| | | | | | | +| | | | tls-creds=tls0 | | id=tls0 | | | | | | +| | | | id=inner_chardev | | endpoint=server | | | | | | +| | | | server=on | | | | | | | | +| | | +------------------+ +-----------------------+ | | | | | +| | | | | | | | +| | | | | | | | +| ^ V | | | V | +| +------------------------------------------------------------------------------------------+ | | +--------------------------------+ | +| |==========================================================================================|------------->|================================| | +| | | | | | | | | | +| | netdev | mac=52:54:00:12:34:56 |7001:: ::7001| netdev | mac=52:54:00:12:34:57 | | +| | | | | | | | | | +| | | |<-------------| | | | +| +------------------------------------------------------------------------------------------+ | | +--------------------------------+ | +| | | | ++--------------------------------------------------------------------------------------------------+ +----------------------------------------+ +``` +Steps to reproduce: +1. Download official GnuTLS .zip for windows from https://www.gnutls.org/download.html and extract it. +2. Download and install official QEMU 9.0 from https://qemu.weilnetz.de/w64/qemu-w64-setup-20240423.exe +3. Open command prompt, navigate to the folder with psktool.exe from Step 1. +4. Run this command: "psktool -u qemu_user -p keys.psk" +5. Run first guest Windows XP with the command described in "QEMU command line" section above, replacing "dir=C:\\Downloads" with path to keys.psk, like this: "dir=C:\\path_to_keys_dot_psk" (without filename itself) +6. Run second guest Windows XP with the following command: `qemu-system-i386.exe -accel tcg -m 256M -cpu Westmere -hda d:\\xp2.qcow2 -usb -device usb-tablet -netdev socket,id=net1,connect=localhost:7001 -device rtl8139,netdev=net1,mac=52:54:00:12:34:57` +Additional information: +Yes, I know Qemu on Linux hosts is able to encrypt netdev traffic with the aid of `-netdev vhost-user,id=net0,chardev=chr0`\ +But `-netdev vhost-user,id=net0,chardev=chr0` is not officially supported by Qemu on Windows hosts.\ +\ +If I run this command in one command prompt instance:\ +`qemu-system-i386.exe -accel tcg -m 256M -object tls-creds-psk,id=tls0,endpoint=server,dir=C:\Downloads -chardev socket,id=chr0,port=7001,host=127.0.0.1,tls-creds=tls0,server=on -netdev vhost-user,id=net0,chardev=chr0 -device virtio-net-pci,netdev=net0,mac=52:54:00:12:34:56`\ +\ +And this one in another instance\ +`gnutls-cli.exe --priority=NORMAL -p 7001 --pskusername=pskusername_from_keys_psk_file --pskkey=pskkeyhash_from_keys_psk_file 127.0.0.1`\ +\ +I see this:\ +`qemu-system-i386.exe: -netdev vhost-user,id=net0,chardev=chr0: network backend 'vhost-user' is not compiled into this binary`\ +\ +Testcase: + +<details> + +static void test_redirector_incomplete_bidirectional_topology_connectionError(void)\ +{\ +//prepare keys.psk\ +FILE \*fileAddress;\ +fileAddress = fopen("/home/keys.psk", "w");\ +char content\[50\] = "deadbeefname:deadbeefkey";\ +int i;\ +int len = strlen(content);\ +\ +if (fileAddress != NULL) {\ +for (i = 0; i \< len; i++) {\ +fputc (content\[i\], fileAddress);\ +}\ +fclose(fileAddress); \ +}\ +else {\ +return -1;\ +}\ +\ +\ +QTestState \*qts0;\ +char \*expect;\ +\ +qts0 = qtest_initf("-netdev socket,id=net0,listen=localhost:7001 "\ +"-device rtl8139,netdev=net0,mac=52:54:00:12:34:56 "\ +"-object filter-redirector,netdev=net0,queue=all,indev=inner_chardev,id=inner_redirector"\ +"-chardev socket,id=inner_chardev,host=127.0.0.1,port=9001,tls-creds=tls0,server=on,wait=off"\ +"-object tls-creds-psk,id=tls0,endpoint=server,dir=/home/");\ +\ +expect = g_strdup_printf("st0: index=0,type=socket,connection error\\r\\n");\ +\ +EXPECT_STATE(qts0, expect, 0);\ +\ +g_free(expect);\ +\ +qtest_quit(qts0);\ +} + +</details> diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2434 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2434 new file mode 100644 index 000000000..4d28dfb76 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2434 @@ -0,0 +1,29 @@ +qemu fails to build tests/unit/test-nested-aio-poll with errors about writing <N> bytes into a region of size <M> overflows the destination +Description of problem: +Fails to compile from source with: +``` +[2/2] Linking target tests/unit/test-nested-aio-poll +FAILED: tests/unit/test-nested-aio-poll +cc -m64 -o tests/unit/test-nested-aio-poll libevent-loop-base.a.p/event-loop-base.c.o libqom.a.p/qom_container.c.o libqom.a.p/qom_object.c.o libqom.a.p/qom_object_interfaces.c.o libqom.a.p/qom_qom-qobject.c.o libblock.a.p/block.c.o libblock.a.p/blockjob.c.o libblock.a.p/job.c.o libblock.a.p/qemu-io-cmds.c.o libblock.a.p/replication.c.o libblock.a.p/nbd_client.c.o libblock.a.p/nbd_client-connection.c.o libblock.a.p/nbd_common.c.o libblock.a.p/scsi_utils.c.o libblock.a.p/scsi_pr-manager.c.o libblock.a.p/scsi_pr-manager-helper.c.o libblock.a.p/block_accounting.c.o libblock.a.p/block_aio_task.c.o libblock.a.p/block_amend.c.o libblock.a.p/block_backup.c.o libblock.a.p/block_blkdebug.c.o libblock.a.p/block_blklogwrites.c.o libblock.a.p/block_blkverify.c.o libblock.a.p/block_block-backend.c.o libblock.a.p/block_block-copy.c.o libblock.a.p/block_commit.c.o libblock.a.p/block_copy-before-write.c.o libblock.a.p/block_copy-on-read.c.o libblock.a.p/block_create.c.o libblock.a.p/block_crypto.c.o libblock.a.p/block_dirty-bitmap.c.o libblock.a.p/block_filter-compress.c.o libblock.a.p/block_graph-lock.c.o libblock.a.p/block_io.c.o libblock.a.p/block_mirror.c.o libblock.a.p/block_nbd.c.o libblock.a.p/block_null.c.o libblock.a.p/block_preallocate.c.o libblock.a.p/block_progress_meter.c.o libblock.a.p/block_qapi.c.o libblock.a.p/block_qcow2.c.o libblock.a.p/block_qcow2-bitmap.c.o libblock.a.p/block_qcow2-cache.c.o libblock.a.p/block_qcow2-cluster.c.o libblock.a.p/block_qcow2-refcount.c.o libblock.a.p/block_qcow2-snapshot.c.o libblock.a.p/block_qcow2-threads.c.o libblock.a.p/block_quorum.c.o libblock.a.p/block_raw-format.c.o libblock.a.p/block_reqlist.c.o libblock.a.p/block_snapshot.c.o libblock.a.p/block_snapshot-access.c.o libblock.a.p/block_throttle.c.o libblock.a.p/block_throttle-groups.c.o libblock.a.p/block_write-threshold.c.o libblock.a.p/block_qcow.c.o libblock.a.p/block_vdi.c.o libblock.a.p/block_vhdx-endian.c.o libblock.a.p/block_vhdx-log.c.o libblock.a.p/block_vhdx.c.o libblock.a.p/block_vmdk.c.o libblock.a.p/block_vpc.c.o libblock.a.p/block_cloop.c.o libblock.a.p/block_bochs.c.o libblock.a.p/block_vvfat.c.o libblock.a.p/block_dmg.c.o libblock.a.p/block_qed-check.c.o libblock.a.p/block_qed-cluster.c.o libblock.a.p/block_qed-l2-cache.c.o libblock.a.p/block_qed-table.c.o libblock.a.p/block_qed.c.o libblock.a.p/block_parallels.c.o libblock.a.p/block_parallels-ext.c.o libblock.a.p/block_file-posix.c.o libblock.a.p/block_iscsi-opts.c.o libblock.a.p/block_nvme.c.o libblock.a.p/block_replication.c.o libblock.a.p/block_linux-aio.c.o libblock.a.p/block_io_uring.c.o libblock.a.p/block_stream.c.o libblock.a.p/block_monitor_bitmap-qmp-cmds.c.o libblock.a.p/block_blkio.c.o libblock.a.p/block_curl.c.o libblock.a.p/block_gluster.c.o libblock.a.p/block_iscsi.c.o libblock.a.p/block_nfs.c.o libblock.a.p/block_ssh.c.o libblock.a.p/block_dmg-bz2.c.o libblock.a.p/meson-generated_.._block_block-gen.c.o libcrypto.a.p/crypto_afsplit.c.o libcrypto.a.p/crypto_akcipher.c.o libcrypto.a.p/crypto_block-luks.c.o libcrypto.a.p/crypto_block-qcow.c.o libcrypto.a.p/crypto_block.c.o libcrypto.a.p/crypto_cipher.c.o libcrypto.a.p/crypto_der.c.o libcrypto.a.p/crypto_hash.c.o libcrypto.a.p/crypto_hmac.c.o libcrypto.a.p/crypto_ivgen-essiv.c.o libcrypto.a.p/crypto_ivgen-plain.c.o libcrypto.a.p/crypto_ivgen-plain64.c.o libcrypto.a.p/crypto_ivgen.c.o libcrypto.a.p/crypto_pbkdf.c.o libcrypto.a.p/crypto_secret_common.c.o libcrypto.a.p/crypto_secret.c.o libcrypto.a.p/crypto_tlscreds.c.o libcrypto.a.p/crypto_tlscredsanon.c.o libcrypto.a.p/crypto_tlscredspsk.c.o libcrypto.a.p/crypto_tlscredsx509.c.o libcrypto.a.p/crypto_tlssession.c.o libcrypto.a.p/crypto_rsakey.c.o libcrypto.a.p/crypto_hash-gnutls.c.o libcrypto.a.p/crypto_hmac-gnutls.c.o libcrypto.a.p/crypto_pbkdf-gnutls.c.o libcrypto.a.p/crypto_secret_keyring.c.o libauthz.a.p/authz_base.c.o libauthz.a.p/authz_list.c.o libauthz.a.p/authz_listfile.c.o libauthz.a.p/authz_simple.c.o libauthz.a.p/authz_pamacct.c.o libio.a.p/io_channel-buffer.c.o libio.a.p/io_channel-command.c.o libio.a.p/io_channel-file.c.o libio.a.p/io_channel-null.c.o libio.a.p/io_channel-socket.c.o libio.a.p/io_channel-tls.c.o libio.a.p/io_channel-util.c.o libio.a.p/io_channel-watch.c.o libio.a.p/io_channel-websock.c.o libio.a.p/io_channel.c.o libio.a.p/io_dns-resolver.c.o libio.a.p/io_net-listener.c.o libio.a.p/io_task.c.o tests/unit/test-nested-aio-poll.p/test-nested-aio-poll.c.o tests/unit/test-nested-aio-poll.p/iothread.c.o -Werror -flto -Wl,--as-needed -Wl,--no-undefined -Wl,-O1 -pie -Wl,-z,relro -Wl,-z,now -march=native -fno-omit-frame-pointer -Wl,-rpath,/usr/lib64/iscsi -Wl,-rpath-link,/usr/lib64/iscsi -Wl,--start-group libqemuutil.a subprojects/libvhost-user/libvhost-user-glib.a subprojects/libvhost-user/libvhost-user.a /usr/lib64/libzstd.so /usr/lib64/libz.so /usr/lib64/iscsi/libiscsi.so -laio /usr/lib64/liburing.so -lblkio /usr/lib64/libcurl.so /usr/lib64/libacl.so /usr/lib64/libgfapi.so /usr/lib64/libglusterfs.so /usr/lib64/libgfrpc.so /usr/lib64/libgfxdr.so /usr/lib64/libuuid.so /usr/lib64/libnfs.so /usr/lib64/libssh.so /usr/lib64/libglib-2.0.so /usr/lib64/libgmodule-2.0.so -pthread -lbz2 /usr/lib64/libgnutls.so -lpam -lnuma /usr/lib64/libgio-2.0.so /usr/lib64/libgobject-2.0.so -lm -Wl,--end-group +In function ‘aio_notify’, + inlined from ‘aio_bh_enqueue’ at ../util/async.c:96:5, + inlined from ‘aio_bh_schedule_oneshot_full’ at ../util/async.c:139:5, + inlined from ‘aio_wait_kick.part.0’ at ../util/aio-wait.c:54:9: +../util/async.c:494:5: error: ‘__atomic_store_1’ writing 1 byte into a region of size 0 overflows the destination [-Werror=stringop-overflow=] + 494 | qatomic_set(&ctx->notified, true); + | ^ +In function ‘aio_wait_kick.part.0’: +lto1: note: destination object is likely at address zero +In function ‘aio_notify’, + inlined from ‘aio_bh_enqueue’ at ../util/async.c:96:5, + inlined from ‘aio_bh_schedule_oneshot_full’ at ../util/async.c:139:5, + inlined from ‘aio_wait_kick.part.0’ at ../util/aio-wait.c:54:9: +../util/async.c:501:9: error: ‘__atomic_load_4’ writing 4 bytes into a region of size 0 overflows the destination [-Werror=stringop-overflow=] + 501 | if (qatomic_read(&ctx->notify_me)) { + | ^ +In function ‘aio_wait_kick.part.0’: +lto1: note: destination object is likely at address zero +lto1: all warnings being treated as errors +``` +Steps to reproduce: +1. Build qemu from source, probably with LTO enabled and recent GCC. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2435 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2435 new file mode 100644 index 000000000..21fbd0d6d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2435 @@ -0,0 +1,20 @@ +CPU halted during fuzzing OHCI +Description of problem: +Is there a limit on the number of CPU cores that QEMU can use? I am running multiple sets of parallel fuzzing tests on a host machine. To prevent CPU contention, I have divided the running environments by using docker. The docker startup command is as follows: +`docker run --cpuset-cpus=8-15 --privileged --name qemu-container-ohci -it qemu-container bash` + +I found that the CPU is in a halted state and encountered the following error: +``` +#0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=126899170563648) at ./nptl/pthread_kill.c:44 +#1 __pthread_kill_internal (signo=6, threadid=126899170563648) at ./nptl/pthread_kill.c:78 +#2 __GI___pthread_kill (threadid=126899170563648, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 +#3 0x0000736a904a3476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 +#4 0x0000736a904897f3 in __GI_abort () at ./stdlib/abort.c:79 +#5 0x0000736a90dcbb57 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 +#6 0x0000736a90e2570f in g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 +#7 0x00005eca4aff5bad in mttcg_cpu_thread_fn (arg=0x62b000000200) at ../accel/tcg/tcg-accel-ops-mttcg.c:110 +#8 0x00005eca4b89d658 in qemu_thread_start (args=0x60300008b030) at ../util/qemu-thread-posix.c:541 +#9 0x0000736a904f5ac3 in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:442 +#10 0x0000736a90587850 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 +``` +Can someone help analyze the reason? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2437 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2437 new file mode 100644 index 000000000..8809e7138 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2437 @@ -0,0 +1,37 @@ +qm terminal VMID return "Inappropriate ioctl for device" when spawned by an another process +Description of problem: +as i dont want to mess with vnc i want to use qm terminal to interact with my vms and it doesnt work im currently using nodejs as a test heres the code if anybody wanna try it +```js +import { spawn } from "child_process"; +var child = spawn('qm', ["terminal", "100"]); + +child.stdout.setEncoding('utf8'); +child.stdin.setDefaultEncoding("utf8"); +child.stdout.on('data', function (data) { + console.log('stdout: ' + data.trim()); +}); + +child.stderr.setEncoding('utf8'); +child.stderr.on('data', function (data) { + console.log('stderr: ' + data.trim()); +}); + +child.on('close', function (code) { + console.log('closing code: ' + code); +}); + +setInterval(() => { + child.stdin.write("\n"); +}, 5000); +``` +its just spawning qm terminal and sending return every 5 seconds + +it seems to start but crash + +"Inappropriate ioctl for device" + +{width=478 height=48} + +maybe its not the place to put that but i have no clue so here am i + +At least i tryed spawning something else my code is working diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2438 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2438 new file mode 100644 index 000000000..5888d2693 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2438 @@ -0,0 +1 @@ +QEMU needs compat tweak to build against upstream capstone 6 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2439 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2439 new file mode 100644 index 000000000..58545ef88 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2439 @@ -0,0 +1,9 @@ +qemu.org ssl certificate is expired +Description of problem: + +Steps to reproduce: +1. go to qemu.org +2. look at it +3. maybe screenshot +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2440 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2440 new file mode 100644 index 000000000..312af6b1a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2440 @@ -0,0 +1,112 @@ +virtio-net: Use-After-Free during unrealization of virtio-net +Description of problem: +When hotplugging `virtio-net` device, mishandling of `failover` option may leads to use-after-free. +More specifically, if we try to hotplug virtio-net device with `failover=on` and other invalid option (e.g. `rx_queue_size=0`), the device listner callback is registered but not unregistered before being freed, leading to UAF. +Steps to reproduce: +```sh +cat <<EOF | qemu-system-i386 -M q35 -nodefaults -chardev stdio,id=char0 -mon char0 -device pcie-pci-bridge,id=br1,bus=pcie.0 +device_add virtio-net,failover=on,rx_queue_size=0,bus=br1,id=dev0 +device_add virtio-net,failover=on,bus=br1,id=dev0 +quit +EOF +``` + +If above command is not working, let me know so that I provide more information. +Additional information: +The following log leveals bug location: + +```sh +$ cat <<EOF | qemu-system-i386 -M q35 -nodefaults -chardev stdio,id=char0 -mon char0 -device pcie-pci-bridge,id=br1,bus=pcie.0 +device_add virtio-net,failover=on,rx_queue_size=0,bus=br1,id=dev0 +device_add virtio-net,failover=on,bus=br1,id=dev0 +quit +EOF +==836681==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases! +QEMU 8.1.93 monitor - type 'help' for more information +VNC server running on 127.0.0.1:5900 +(qemu) device_add virtio-net,failover=on,rx_queue_size=0,bus=br1,id=dev0 +Error: Invalid rx_queue_size (= 0), must be a power of 2 between 256 and 1024. +(qemu) device_add virtio-net,failover=on,bus=br1,id=dev0 +================================================================= +==836681==ERROR: AddressSanitizer: heap-use-after-free on address 0x62e00000ab58 at pc 0x5577bbb8fe22 bp 0x7ffeb03fca50 sp 0x7ffeb03fca48 +READ of size 8 at 0x62e00000ab58 thread T0 + #0 0x5577bbb8fe21 in qdev_should_hide_device /home/XXX/qemu/build/../hw/core/qdev.c:233:23 + #1 0x5577bb14aac4 in qdev_device_add_from_qdict /home/XXX/qemu/build/../system/qdev-monitor.c:662:9 + #2 0x5577bb14c364 in qdev_device_add /home/XXX/qemu/build/../system/qdev-monitor.c:738:11 + #3 0x5577bb14d6eb in qmp_device_add /home/XXX/qemu/build/../system/qdev-monitor.c:860:11 + #4 0x5577bb14e11d in hmp_device_add /home/XXX/qemu/build/../system/qdev-monitor.c:968:5 + #5 0x5577bb29aef4 in handle_hmp_command_exec /home/XXX/qemu/build/../monitor/hmp.c:1106:9 + #6 0x5577bb298fa3 in handle_hmp_command /home/XXX/qemu/build/../monitor/hmp.c:1158:9 + #7 0x5577bb2949ee in monitor_command_cb /home/XXX/qemu/build/../monitor/hmp.c:47:5 + #8 0x5577bc2b0c3a in readline_handle_byte /home/XXX/qemu/build/../util/readline.c:419:13 + #9 0x5577bb29d261 in monitor_read /home/XXX/qemu/build/../monitor/hmp.c:1390:13 + #10 0x5577bbfda644 in fd_chr_read /home/XXX/qemu/build/../chardev/char-fd.c:72:9 + #11 0x7f53d36e5c43 in g_main_context_dispatch (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x55c43) (BuildId: 224ac2a88b72bc8e2fe8566ee28fae789fc69241) + #12 0x5577bc2536db in glib_pollfds_poll /home/XXX/qemu/build/../util/main-loop.c:290:9 + #13 0x5577bc2536db in os_host_main_loop_wait /home/XXX/qemu/build/../util/main-loop.c:313:5 + #14 0x5577bc2536db in main_loop_wait /home/XXX/qemu/build/../util/main-loop.c:592:11 + #15 0x5577bb15dd06 in qemu_main_loop /home/XXX/qemu/build/../system/runstate.c:782:9 + #16 0x5577bbb81115 in qemu_default_main /home/XXX/qemu/build/../system/main.c:37:14 + #17 0x7f53d2c3fd8f in __libc_start_call_main csu/../sysdeps/nptl/libc_start_call_main.h:58:16 + #18 0x7f53d2c3fe3f in __libc_start_main csu/../csu/libc-start.c:392:3 + #19 0x5577ba4c3584 in _start (/usr/local/bin/qemu-system-i386+0x1ada584) (BuildId: c7ca543ea41d3478bc13cdf604d47805b990620e) + +0x62e00000ab58 is located 42840 bytes inside of 43008-byte region [0x62e000000400,0x62e00000ac00) +freed by thread T1 here: + #0 0x5577ba546122 in __interceptor_free (/usr/local/bin/qemu-system-i386+0x1b5d122) (BuildId: c7ca543ea41d3478bc13cdf604d47805b990620e) + #1 0x5577bbba5135 in object_finalize /home/XXX/qemu/build/../qom/object.c:714:9 + #2 0x5577bbba5135 in object_unref /home/XXX/qemu/build/../qom/object.c:1217:9 + #3 0x5577bbb91ac3 in bus_free_bus_child /home/XXX/qemu/build/../hw/core/qdev.c:55:5 + +previously allocated by thread T0 here: + #0 0x5577ba5463ce in malloc (/usr/local/bin/qemu-system-i386+0x1b5d3ce) (BuildId: c7ca543ea41d3478bc13cdf604d47805b990620e) + #1 0x7f53d36ee738 in g_malloc (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x5e738) (BuildId: 224ac2a88b72bc8e2fe8566ee28fae789fc69241) + #2 0x5577bb14c364 in qdev_device_add /home/XXX/qemu/build/../system/qdev-monitor.c:738:11 + #3 0x5577bb29aef4 in handle_hmp_command_exec /home/XXX/qemu/build/../monitor/hmp.c:1106:9 + #4 0x5577bb298fa3 in handle_hmp_command /home/XXX/qemu/build/../monitor/hmp.c:1158:9 + #5 0x5577bb2949ee in monitor_command_cb /home/XXX/qemu/build/../monitor/hmp.c:47:5 + +Thread T1 created by T0 here: + #0 0x5577ba52f84c in pthread_create (/usr/local/bin/qemu-system-i386+0x1b4684c) (BuildId: c7ca543ea41d3478bc13cdf604d47805b990620e) + #1 0x5577bc1fcc24 in qemu_thread_create /home/XXX/qemu/build/../util/qemu-thread-posix.c:581:11 + #2 0x5577bc229970 in rcu_init_complete /home/XXX/qemu/build/../util/rcu.c:415:5 + #3 0x5577bc229970 in rcu_init /home/XXX/qemu/build/../util/rcu.c:471:5 + #4 0x7f53d2c3feba in call_init csu/../csu/libc-start.c:145:3 + #5 0x7f53d2c3feba in __libc_start_main csu/../csu/libc-start.c:379:5 + +SUMMARY: AddressSanitizer: heap-use-after-free /home/XXX/qemu/build/../hw/core/qdev.c:233:23 in qdev_should_hide_device +Shadow bytes around the buggy address: + 0x0c5c7fff9510: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd + 0x0c5c7fff9520: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd + 0x0c5c7fff9530: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd + 0x0c5c7fff9540: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd + 0x0c5c7fff9550: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd +=>0x0c5c7fff9560: fd fd fd fd fd fd fd fd fd fd fd[fd]fd fd fd fd + 0x0c5c7fff9570: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd + 0x0c5c7fff9580: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa + 0x0c5c7fff9590: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa + 0x0c5c7fff95a0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa + 0x0c5c7fff95b0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa +Shadow byte legend (one shadow byte represents 8 application bytes): + Addressable: 00 + Partially addressable: 01 02 03 04 05 06 07 + Heap left redzone: fa + Freed heap region: fd + Stack left redzone: f1 + Stack mid redzone: f2 + Stack right redzone: f3 + Stack after return: f5 + Stack use after scope: f8 + Global redzone: f9 + Global init order: f6 + Poisoned by user: f7 + Container overflow: fc + Array cookie: ac + Intra object redzone: bb + ASan internal: fe + Left alloca redzone: ca + Right alloca redzone: cb +==836681==ABORTING +``` + +# diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2441 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2441 new file mode 100644 index 000000000..a9b2af504 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2441 @@ -0,0 +1,100 @@ +virtio-net: memory leak when hotplugging virtio-net +Description of problem: +When invalid option for virtio-net device is provided during hotplug, allocated string is not freed, leading to memory leak. +Steps to reproduce: +```sh +cat <<EOF | qemu-system-i386 -M q35 -nodefaults \ +-chardev stdio,id=char0 -mon char0 -device pcie-pci-bridge,id=br1,bus=pcie.0 +device_add virtio-net,rx_queue_size=0,bus=br1,id=dev0 +quit +EOF +``` + +If above command is not working, let me know so that I provide more information. +Additional information: +There is LeakSanitizer log: + +```sh +$ cat <<EOF | LSAN_OPTIONS=fast_unwind_on_malloc=0 qemu-system-i386 -M q35 -nodefaults \ +-chardev stdio,id=char0 -mon char0 -device pcie-pci-bridge,id=br1,bus=pcie.0 +device_add virtio-net,rx_queue_size=0,bus=br1,id=dev0 +quit +EOF +==831633==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases! +QEMU 8.1.93 monitor - type 'help' for more information +VNC server running on 127.0.0.1:5900 +(qemu) device_add virtio-net,rx_queue_size=0,bus=br1,id=dev0 +Error: Invalid rx_queue_size (= 0), must be a power of 2 between 256 and 1024. +(qemu) quit + +================================================================= +==831633==ERROR: LeakSanitizer: detected memory leaks + +Direct leak of 15 byte(s) in 1 object(s) allocated from: + #0 0x55c1ac66b3ce in malloc (/usr/local/bin/qemu-system-i386+0x1b5d3ce) (BuildId: c7ca543ea41d3478bc13cdf604d47805b990620e) + #1 0x7f45c1695738 in g_malloc (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x5e738) (BuildId: 224ac2a88b72bc8e2fe8566ee28fae789fc69241) + #2 0x7f45c16aa583 in g_strdup (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x73583) (BuildId: 224ac2a88b72bc8e2fe8566ee28fae789fc69241) + #3 0x55c1ad943dd4 in virtio_net_set_netclient_name /home/XXX/qemu/build/../hw/net/virtio-net.c:3445:25 + #4 0x55c1adace541 in virtio_net_pci_realize /home/XXX/qemu/build/../hw/virtio/virtio-net-pci.c:62:5 + #5 0x55c1ad13ec00 in virtio_pci_realize /home/XXX/qemu/build/../hw/virtio/virtio-pci.c:2228:9 + #6 0x55c1acdec557 in pci_qdev_realize /home/XXX/qemu/build/../hw/pci/pci.c:2117:9 + #7 0x55c1adcb9484 in device_set_realized /home/XXX/qemu/build/../hw/core/qdev.c:510:13 + #8 0x55c1adcd6278 in property_set_bool /home/XXX/qemu/build/../qom/object.c:2305:5 + #9 0x55c1adcd1443 in object_property_set /home/XXX/qemu/build/../qom/object.c:1435:5 + #10 0x55c1adcdd15c in object_property_set_qobject /home/XXX/qemu/build/../qom/qom-qobject.c:28:10 + #11 0x55c1adcd1d11 in object_property_set_bool /home/XXX/qemu/build/../qom/object.c:1504:15 + #12 0x55c1ad27021a in qdev_device_add_from_qdict /home/XXX/qemu/build/../system/qdev-monitor.c:719:10 + #13 0x55c1ad271364 in qdev_device_add /home/XXX/qemu/build/../system/qdev-monitor.c:738:11 + #14 0x55c1ad2726eb in qmp_device_add /home/XXX/qemu/build/../system/qdev-monitor.c:860:11 + #15 0x55c1ad27311d in hmp_device_add /home/XXX/qemu/build/../system/qdev-monitor.c:968:5 + #16 0x55c1ad3bfef4 in handle_hmp_command_exec /home/XXX/qemu/build/../monitor/hmp.c:1106:9 + #17 0x55c1ad3bdfa3 in handle_hmp_command /home/XXX/qemu/build/../monitor/hmp.c:1158:9 + #18 0x55c1ad3b99ee in monitor_command_cb /home/XXX/qemu/build/../monitor/hmp.c:47:5 + #19 0x55c1ae3d5c3a in readline_handle_byte /home/XXX/qemu/build/../util/readline.c:419:13 + #20 0x55c1ad3c2261 in monitor_read /home/XXX/qemu/build/../monitor/hmp.c:1390:13 + #21 0x55c1ae0ff644 in fd_chr_read /home/XXX/qemu/build/../chardev/char-fd.c:72:9 + #22 0x7f45c168cc43 in g_main_context_dispatch (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x55c43) (BuildId: 224ac2a88b72bc8e2fe8566ee28fae789fc69241) + #23 0x55c1ae3786db in glib_pollfds_poll /home/XXX/qemu/build/../util/main-loop.c:290:9 + #24 0x55c1ae3786db in os_host_main_loop_wait /home/XXX/qemu/build/../util/main-loop.c:313:5 + #25 0x55c1ae3786db in main_loop_wait /home/XXX/qemu/build/../util/main-loop.c:592:11 + #26 0x55c1ad282d06 in qemu_main_loop /home/XXX/qemu/build/../system/runstate.c:782:9 + #27 0x55c1adca6115 in qemu_default_main /home/XXX/qemu/build/../system/main.c:37:14 + #28 0x7f45c0bd0d8f in __libc_start_call_main csu/../sysdeps/nptl/libc_start_call_main.h:58:16 + #29 0x7f45c0bd0e3f in __libc_start_main csu/../csu/libc-start.c:392:3 + +Direct leak of 5 byte(s) in 1 object(s) allocated from: + #0 0x55c1ac66b3ce in malloc (/usr/local/bin/qemu-system-i386+0x1b5d3ce) (BuildId: c7ca543ea41d3478bc13cdf604d47805b990620e) + #1 0x7f45c1695738 in g_malloc (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x5e738) (BuildId: 224ac2a88b72bc8e2fe8566ee28fae789fc69241) + #2 0x7f45c16aa583 in g_strdup (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x73583) (BuildId: 224ac2a88b72bc8e2fe8566ee28fae789fc69241) + #3 0x55c1ad943da2 in virtio_net_set_netclient_name /home/XXX/qemu/build/../hw/net/virtio-net.c:3444:25 + #4 0x55c1adace541 in virtio_net_pci_realize /home/XXX/qemu/build/../hw/virtio/virtio-net-pci.c:62:5 + #5 0x55c1ad13ec00 in virtio_pci_realize /home/XXX/qemu/build/../hw/virtio/virtio-pci.c:2228:9 + #6 0x55c1acdec557 in pci_qdev_realize /home/XXX/qemu/build/../hw/pci/pci.c:2117:9 + #7 0x55c1adcb9484 in device_set_realized /home/XXX/qemu/build/../hw/core/qdev.c:510:13 + #8 0x55c1adcd6278 in property_set_bool /home/XXX/qemu/build/../qom/object.c:2305:5 + #9 0x55c1adcd1443 in object_property_set /home/XXX/qemu/build/../qom/object.c:1435:5 + #10 0x55c1adcdd15c in object_property_set_qobject /home/XXX/qemu/build/../qom/qom-qobject.c:28:10 + #11 0x55c1adcd1d11 in object_property_set_bool /home/XXX/qemu/build/../qom/object.c:1504:15 + #12 0x55c1ad27021a in qdev_device_add_from_qdict /home/XXX/qemu/build/../system/qdev-monitor.c:719:10 + #13 0x55c1ad271364 in qdev_device_add /home/XXX/qemu/build/../system/qdev-monitor.c:738:11 + #14 0x55c1ad2726eb in qmp_device_add /home/XXX/qemu/build/../system/qdev-monitor.c:860:11 + #15 0x55c1ad27311d in hmp_device_add /home/XXX/qemu/build/../system/qdev-monitor.c:968:5 + #16 0x55c1ad3bfef4 in handle_hmp_command_exec /home/XXX/qemu/build/../monitor/hmp.c:1106:9 + #17 0x55c1ad3bdfa3 in handle_hmp_command /home/XXX/qemu/build/../monitor/hmp.c:1158:9 + #18 0x55c1ad3b99ee in monitor_command_cb /home/XXX/qemu/build/../monitor/hmp.c:47:5 + #19 0x55c1ae3d5c3a in readline_handle_byte /home/XXX/qemu/build/../util/readline.c:419:13 + #20 0x55c1ad3c2261 in monitor_read /home/XXX/qemu/build/../monitor/hmp.c:1390:13 + #21 0x55c1ae0ff644 in fd_chr_read /home/XXX/qemu/build/../chardev/char-fd.c:72:9 + #22 0x7f45c168cc43 in g_main_context_dispatch (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x55c43) (BuildId: 224ac2a88b72bc8e2fe8566ee28fae789fc69241) + #23 0x55c1ae3786db in glib_pollfds_poll /home/XXX/qemu/build/../util/main-loop.c:290:9 + #24 0x55c1ae3786db in os_host_main_loop_wait /home/XXX/qemu/build/../util/main-loop.c:313:5 + #25 0x55c1ae3786db in main_loop_wait /home/XXX/qemu/build/../util/main-loop.c:592:11 + #26 0x55c1ad282d06 in qemu_main_loop /home/XXX/qemu/build/../system/runstate.c:782:9 + #27 0x55c1adca6115 in qemu_default_main /home/XXX/qemu/build/../system/main.c:37:14 + #28 0x7f45c0bd0d8f in __libc_start_call_main csu/../sysdeps/nptl/libc_start_call_main.h:58:16 + #29 0x7f45c0bd0e3f in __libc_start_main csu/../csu/libc-start.c:392:3 + +SUMMARY: AddressSanitizer: 20 byte(s) leaked in 2 allocation(s). +``` + +# diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2442 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2442 new file mode 100644 index 000000000..05c75831b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2442 @@ -0,0 +1,147 @@ +kvm-unit-tests ept failed +Description of problem: +On the Sierra Forest and Emerald Rapids platform, the ept test in kvm-unit-tests failed on the latest QEMU. + +QEMU first bad commit is 0b2757412cb1d1947d7e2c1fe14985f1e72bba32. + +This bad commit also caused other errors, such as: + +1.kvm-unit-tests vmx_pf_invvpid_test + +Test suite: vmx_pf_invvpid_test + +Host skipping test: INVVPID ADDR unsupported + +filter = vmx_pf_invvpid_test, test = vmx_pf_vpid_test + +filter = vmx_pf_invvpid_test, test = vmx_exception_test + +SUMMARY: 0 tests + +SKIP vmx_pf_invvpid_test (0 tests) + +2.kvm-unit-tests vmx_pf_no_vpid_test + +Test suite: vmx_pf_no_vpid_test + +run + +x86/vmx_tests.c:10568: assert failed: false: Unexpected exit to L1, exit_reason: VMX_CR (0x1c) + STACK: 40717c 4072a3 402039 403f11 4001bd + +FAIL vmx_pf_no_vpid_test + +3.kvm-unit-tests vmx: + +Test suite: vmx_controls_test + +FAIL: Clear primary processor-based controls bit 15: vmlaunch fails + +FAIL: Clear primary processor-based controls bit 16: vmlaunch fails + +Test suite: vmx_mtf_test + +FAIL: x86/vmx_tests.c:2164: Assertion failed: (expected) == (actual) + LHS: 0x0000000000000025 - 0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0010'0101 - 37 + RHS: 0x000000000000001c - 0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0001'1100 - 28 +Expected VMX_MTF, got VMX_CR. + STACK: 406faa 407478 407911 402039 403f11 4001bd + +4.Failed to boot L2 guest on L1 windows guest, host does not support "Intel EPT" hardware assisted MMU virtualization. +Steps to reproduce: +1.git clone https://gitlab.com/kvm-unit-tests/kvm-unit-tests.git + +2.cd kvm-unit-tests; ./configure + +3.make standalone + +4.rmmod kvm_intel + +5.modprobe kvm_intel nested=Y allow_smaller_maxphyaddr=Y + +6.cd tests; ./ept +Additional information: +... +Test suite: ept_access_test_paddr_not_present_ad_disabled +FAIL: x86/vmx_tests.c:2164: Assertion failed: (expected) == (actual) + LHS: 0x0000000000000012 - 0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0001'0010 - 18 + RHS: 0x000000000000001c - 0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0001'1100 - 28 +Expected VMX_VMCALL, got VMX_CR. + STACK: 406faa 40730c 416905 416cf2 416f68 402039 403f11 4001bd +filter = ept_access*, test = ept_access_test_paddr_not_present_ad_enabled + +Test suite: ept_access_test_paddr_not_present_ad_enabled +FAIL: x86/vmx_tests.c:2164: Assertion failed: (expected) == (actual) + LHS: 0x0000000000000012 - 0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0001'0010 - 18 + RHS: 0x000000000000001c - 0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0001'1100 - 28 +Expected VMX_VMCALL, got VMX_CR. + STACK: 406faa 40730c 416905 416cf2 416f09 402039 403f11 4001bd +filter = ept_access*, test = ept_access_test_paddr_read_only_ad_disabled + +Test suite: ept_access_test_paddr_read_only_ad_disabled +FAIL: x86/vmx_tests.c:2164: Assertion failed: (expected) == (actual) + LHS: 0x0000000000000012 - 0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0001'0010 - 18 + RHS: 0x000000000000001c - 0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0001'1100 - 28 +Expected VMX_VMCALL, got VMX_CR. + STACK: 406faa 40730c 416905 416cf2 417150 402039 403f11 4001bd +filter = ept_access*, test = ept_access_test_paddr_read_only_ad_enabled + +Test suite: ept_access_test_paddr_read_only_ad_enabled +FAIL: x86/vmx_tests.c:2164: Assertion failed: (expected) == (actual) + LHS: 0x0000000000000012 - 0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0001'0010 - 18 + RHS: 0x000000000000001c - 0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0001'1100 - 28 +Expected VMX_VMCALL, got VMX_CR. + STACK: 406faa 40730c 416905 416cf2 416e14 402039 403f11 4001bd +filter = ept_access*, test = ept_access_test_paddr_read_write + +Test suite: ept_access_test_paddr_read_write +FAIL: x86/vmx_tests.c:2164: Assertion failed: (expected) == (actual) + LHS: 0x0000000000000012 - 0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0001'0010 - 18 + RHS: 0x000000000000001c - 0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0001'1100 - 28 +Expected VMX_VMCALL, got VMX_CR. + STACK: 406faa 40730c 416905 416fb1 4170fb 402039 403f11 4001bd +filter = ept_access*, test = ept_access_test_paddr_read_write_execute + +Test suite: ept_access_test_paddr_read_write_execute +FAIL: x86/vmx_tests.c:2164: Assertion failed: (expected) == (actual) + LHS: 0x0000000000000012 - 0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0001'0010 - 18 + RHS: 0x000000000000001c - 0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0001'1100 - 28 +Expected VMX_VMCALL, got VMX_CR. + STACK: 406faa 40730c 416905 416fb1 4170b0 402039 403f11 4001bd +filter = ept_access*, test = ept_access_test_paddr_read_execute_ad_disabled + +Test suite: ept_access_test_paddr_read_execute_ad_disabled +FAIL: x86/vmx_tests.c:2164: Assertion failed: (expected) == (actual) + LHS: 0x0000000000000012 - 0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0001'0010 - 18 + RHS: 0x000000000000001c - 0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0001'1100 - 28 +Expected VMX_VMCALL, got VMX_CR. + STACK: 406faa 40730c 416905 416cf2 416fde 402039 403f11 4001bd +filter = ept_access*, test = ept_access_test_paddr_read_execute_ad_enabled + +Test suite: ept_access_test_paddr_read_execute_ad_enabled +FAIL: x86/vmx_tests.c:2164: Assertion failed: (expected) == (actual) + LHS: 0x0000000000000012 - 0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0001'0010 - 18 + RHS: 0x000000000000001c - 0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0000'0001'1100 - 28 +Expected VMX_VMCALL, got VMX_CR. + STACK: 406faa 40730c 416905 416cf2 416d1f 402039 403f11 4001bd +filter = ept_access*, test = ept_access_test_paddr_not_present_page_fault + +Test suite: ept_access_test_paddr_not_present_page_fault +filter = ept_access*, test = ept_access_test_force_2m_page + +Test suite: ept_access_test_force_2m_page +filter = ept_access*, test = atomic_switch_max_msrs_test +filter = ept_access*, test = atomic_switch_overflow_msrs_test +filter = ept_access*, test = rdtsc_vmexit_diff_test +filter = ept_access*, test = vmx_mtf_test +filter = ept_access*, test = vmx_mtf_pdpte_test +filter = ept_access*, test = vmx_pf_exception_test +filter = ept_access*, test = vmx_pf_exception_forced_emulation_test +filter = ept_access*, test = vmx_pf_no_vpid_test +filter = ept_access*, test = vmx_pf_invvpid_test +filter = ept_access*, test = vmx_pf_vpid_test +filter = ept_access*, test = vmx_exception_test +SUMMARY: 5824 tests, 8 unexpected failures +FAIL ept (5824 tests, 8 unexpected failures) + +[error.log](/uploads/407a04df83bae220bca6fad3c9bba9ff/error.log) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2443 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2443 new file mode 100644 index 000000000..55df97324 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2443 @@ -0,0 +1,18 @@ +virtio-gpu-gl: "opengl is not available" message is too vague and doesn't suggest how to fix the problem +Description of problem: +I finally compiled qemu for Apple Silicon M2 Pro with opengl enabled and virtglrenderer enabled thanks to instruction from homebrew formula, +but I did it without homebrew nor macports just manually compiling necessary libraries. +Qemu was compiled succesfully with flags: +```` +./configure --target-list=aarch64-softmmu,x86_64-softmmu --enable-cocoa --enable-sdl --enable-virglrenderer --enable-vhost-net --enable-spice-protocol --enable-tools --enable-opengl --enable-pixman --enable-vmnet +```` + +the device is clearly listed: +```` +name "virtio-gpu-device", bus virtio-bus +name "virtio-gpu-gl-device", bus virtio-bus +name "virtio-gpu-gl-pci", bus PCI, alias "virtio-gpu-gl" +name "virtio-gpu-pci", bus PCI, alias "virtio-gpu" +```` + +So why it not working and gives that info while opengl is clearly there and is enabled. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2444 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2444 new file mode 100644 index 000000000..e124800f6 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2444 @@ -0,0 +1 @@ +Use of vulnerable function 'strcpy' at can_socketcan.c:213. This function is unsafe. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2446 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2446 new file mode 100644 index 000000000..c3bc64096 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2446 @@ -0,0 +1,60 @@ +linux-user: Qemu doesn't support `set_robust_list` used by glibc robust mutex implementation +Description of problem: +It seems that syscall set_robust_list is not implemented on Qemu for any Linux platform: [link]( https://github.com/qemu/qemu/blob/master/linux-user/syscall.c#L12811) +Steps to reproduce: +1. Use below toy program `set_robust_list.c` and compile it without optimizations like: +``` + gcc -Wall -W -Wextra -std=gnu17 -pedantic set_robust_list.c -o set_robust_list +``` + +``` +#include <stdio.h> +#include <stdlib.h> +#include <errno.h> +#include <sys/syscall.h> +#include <sys/types.h> +#include <unistd.h> +#include <linux/futex.h> +#include <syscall.h> + +int main(void) +{ +#ifdef __NR_set_robust_list + struct robust_list_head head; + size_t len = sizeof(struct robust_list_head); + + // This call to set_robust_list function should fail + int err = syscall(__NR_set_robust_list, &head, -1); + if (err < 0) + perror("1st set_robust_list error"); + else + puts("1st set_robust_list OK"); + + // This call to set_robust_list function should be sucessful + err = syscall(__NR_set_robust_list, &head, len); + if (err < 0) + perror("2nd set_robust_list error"); + else + puts("2nd set_robust_list OK"); +#else + puts("No set_robust_list support"); +#endif + exit(0); +} +``` + +2. Run program on Qemu and compare output with output from x64 build. In my case it looks like: +``` +root@AMDC4705:/runtime/set_robust_list# ./set_robust_list +1st set_robust_list error: Invalid argument +2nd set_robust_list OK +root@AMDC4705:/runtime/set_robust_list# ./set_robust_list-riscv +1st set_robust_list error: Function not implemented +2nd set_robust_list error: Function not implemented +``` +Additional information: +Working `set_robust_list` on Linux is quite important in context of named robust mutexes. In NPTL `set_robust_list` is used internally at ld.so initialization time to perform following check: [link](https://github.com/bminor/glibc/blob/master/sysdeps/nptl/dl-tls_init_tp.c#L96) + +When syscall fails, later `pthread_mutex_init` (with `PTHREAD_MUTEX_ROBUST` + `PTHREAD_PROCESS_SHARED` attributes) end up with `ENOTSUP` error [link](https://github.com/bminor/glibc/blob/master/nptl/pthread_mutex_init.c#L99). + +In dotnet we use robust mutexes for process synchronization purpose. Although there are other available techniques like named semaphores or file locks, robust mutexes are better locking option in case of unexpected process death. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2447 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2447 new file mode 100644 index 000000000..e92400668 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2447 @@ -0,0 +1,23 @@ +With -display sdl,gl=on and 3D acceleration, the position of mouse does not show correctly +Description of problem: +Real mouse position is nearly 100 px on the left of drawn cursor. The closer the cursor to the lower right corner of the VM window, the worse (divergence becomes way bigger than 100 px). + +Split off from https://gitlab.com/qemu-project/qemu/-/issues/761 + +VM window is not necessary to be resized to reproduce this bug. If your VM desktop comes 1920x1080 originally, the bug can be reproduced from the very start. + +Smaller resolutions show this bug too, but it not so noticeable. +Steps to reproduce: +1. Download and install official QEMU 9.0 from https://qemu.weilnetz.de/w64/qemu-w64-setup-20240423.exe +2. Go to https://www.kali.org/get-kali/#kali-virtual-machines and click big QEMU 64 icon, and wait till kali-linux-2024.2-qemu-amd64.7z has been downloaded +3. Extract kali-linux-2024.2-qemu-amd64.qcow2 from kali-linux-2024.2-qemu-amd64.7z +4. Run it: `qemu-system-x86_64.exe -accel tcg -device virtio-vga-gl -display sdl,gl=on -hda C:\kali-linux-2024.2-qemu-amd64.qcow2 -usb -device usb-tablet -m 4096 -machine q35 -smp 2 -cpu Westmere` +5. Enter `kali` as user and `kali` as password when prompted +6. When the desktop is shown up, click the leftmost, upmost blue "Applications" button. Then click Settings -\> Display +7. Pick 1920x1080 as resolution and click Apply, then Keep this configuration. +8. Click Firefox Browser icon on the top panel. +9. When the browser starts working, experience how hard to use its interface, though it's fast. Real mouse position is nearly 100 px on the left of drawn cursor. The closer the cursor to the lower right corner of the VM window, the worse (divergence becomes way bigger than 100 px). +Additional information: +Run `qemu-system-x86_64.exe -accel tcg -device virtio-vga -display sdl -hda C:\kali-linux-2024.2-qemu-amd64.qcow2 -usb -device usb-tablet -m 4096 -machine q35 -smp 2 -cpu Westmere` and experience correct behavior. + +Mouse in Gtk mode works ok. OpenGL not available for Windows in GTK mode. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2448 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2448 new file mode 100644 index 000000000..3f791d0d2 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2448 @@ -0,0 +1,46 @@ +linux-user as binfmt_misc fails to recognize AT_EXECFD if it's 0 and leaves it open as stdin +Description of problem: +When a `*-linux-user` is used as binfmt_misc, and... + +- The `O` (i.e. open-binary) flag is set +- File descriptor 0 is closed when running the executable + +FD 0 is opened to point at the executable and passed as `AT_EXECFD`, which QEMU fails to recognize and leaves open before handing control over to the executable, leading to the program to think stdin is opened for reading its own executable. + +Some use cases rely on closed stdin to behave correctly. For example, this problem causes the `tests/tail/follow-stdin.sh` and `tests/tac/tac-2-nonseekable.sh` tests in GNU coreutils to fail. In any case, having the executable itself be stdin is definitely incorrect and quite surprising behavior. +Steps to reproduce: +1. Set up qemu-riscv64 as binfmt_misc with `qemu-binfmt-conf.sh`, with the `--credential` flag (which enables open-binary) +2. Get a coreutils built for riscv64 (Let's say it can be found in `riscv64-coreutils/bin`) +3. Run it with something like `riscv64-coreutils/bin/cat <&- | xxd | head` (`xxd | head` to catch the binary output) + +The correct behavior is (You can see by running the native `cat <&-`): + +``` +cat: -: Bad file descriptor +cat: closing standard input: Bad file descriptor +``` + +Instead, the executable `cat` itself is dumped to stdout. + +Perhaps slightly more clear is `riscv64-coreutils/bin/ls -l /proc/self/fd <&-` which shows fd 0 unexpectedly pointing to the coreutils executable. +Additional information: +I'm interested in writing a patch to fix this issue but I'm uncertain how to proceed. This is what I've found so far: + +In `linux-user/main.c` if (effectively) `getauxval(AT_EXECFD)` is 0 it's treated as nonexistent. (https://gitlab.com/qemu-project/qemu/-/blob/0d9f1016d43302108d33d1268304a06cc3fb2021/linux-user/main.c#L758-765) + +```c + execfd = qemu_getauxval(AT_EXECFD); + if (execfd == 0) { + execfd = open(exec_path, O_RDONLY); + if (execfd < 0) { + printf("Error while loading %s: %s\n", exec_path, strerror(errno)); + _exit(EXIT_FAILURE); + } + } +``` + +However as we've seen `getauxval(AT_EXECFD)` can have 0 as a valid value. + +`qemu_getauxval` in `util/getauxval.c` implements several strategies to get the auxv, but doesn't currently give a way to distinguish not found and 0. FreeBSD `elf_aux_info` has `EINVAL` and `ENOENT` error codes but it's ignored here. On Linux, glibc sets `errno` to `ENOENT` to distinguish the two cases but only on glibc >= 2.19. Musl's `getauxval` has always had setting `errno` to `ENOENT`. + +Once we add a proper "`AT_EXECFD` doesn't exist" check this will no longer be a problem since (IIUC) `execfd` will eventually be closed after loading. How should we add "not found" support to `qemu_getauxval`? Is just simply relying on libc's `getauxval` setting `errno` okay? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2449 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2449 new file mode 100644 index 000000000..d2d0f46e1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2449 @@ -0,0 +1 @@ +How to extract FIS (personal question) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2451 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2451 new file mode 100644 index 000000000..46eada499 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2451 @@ -0,0 +1 @@ +Italian language (po) not updated diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2454 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2454 new file mode 100644 index 000000000..13af8c3b5 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2454 @@ -0,0 +1,8 @@ +sd: assertion in sd_read_byte() +Description of problem: +The following log reveals it: + +``` +ERROR: qemu/hw/sd/sd.c:2541:sd_read_byte: code should not be reached +Bail out! ERROR: qemu/hw/sd/sd.c:2541:sd_read_byte: code should not be reached Aborted (core dumped) +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2455 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2455 new file mode 100644 index 000000000..f2c88aa55 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2455 @@ -0,0 +1,8 @@ +sdhci: assertion in sdhci_read_dataport() +Description of problem: +The following log reveals it: + +``` +qemu-system-x86_64: qemu/hw/sd/sdhci.c:476: uint32_t sdhci_read_dataport(SDHCIState *, unsigned int): Assertion `s->data_count < s->buf_maxsz' failed. +Aborted (core dumped) +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2457 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2457 new file mode 100644 index 000000000..50fb869ba --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2457 @@ -0,0 +1 @@ +Building plugin sources doesn't produce any output to 'make' diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2458 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2458 new file mode 100644 index 000000000..93e31b9ea --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2458 @@ -0,0 +1 @@ +Documentation build fails with Sphinx 8 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2459 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2459 new file mode 100644 index 000000000..f1ebebf9c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2459 @@ -0,0 +1 @@ +Qemu in termux network bug diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/246 b/gitlab/issues_text/target_missing/host_missing/accel_missing/246 new file mode 100644 index 000000000..7f89ebcc1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/246 @@ -0,0 +1 @@ +Build fails with 64 bits time_t diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2465 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2465 new file mode 100644 index 000000000..8260b1012 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2465 @@ -0,0 +1 @@ +QEMU does not stop other threads when hitting a breakpoint diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2466 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2466 new file mode 100644 index 000000000..75884d1d2 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2466 @@ -0,0 +1,24 @@ +I'm not sure. But I Think I could cause the err(include/qemu/queue.h). +Description of problem: +At file "include/qemu/queue.h", Maybe I Think QTAILQ_REMOVE could cause a Error. + +``` +#define QTAILQ_REMOVE(head, elm, field) do { \ + if (((elm)->field.tqe_next) != NULL) \ + (elm)->field.tqe_next->field.tqe_circ.tql_prev = \ + (elm)->field.tqe_circ.tql_prev; \ + else \ + (head)->tqh_circ.tql_prev = (elm)->field.tqe_circ.tql_prev; \ + (elm)->field.tqe_circ.tql_prev->tql_next = (elm)->field.tqe_next; \ + (elm)->field.tqe_circ.tql_prev = NULL; \ + (elm)->field.tqe_circ.tql_next = NULL; \ + (elm)->field.tqe_next = NULL; \ +} while (/*CONSTCOND*/0) +``` +If the length of the que is one, line 7 cause a segmentation fault. +Steps to reproduce: +1. Create a Que with QTAILQ_INIT +2. Add one element to que. +3. Remove the element with QTAILQ_REMOVE +Additional information: +queue.h file is located at "inclue/qemu/queue.h" diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2471 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2471 new file mode 100644 index 000000000..f2a9849b1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2471 @@ -0,0 +1 @@ +error handling in of_dpa_cmd_add_acl() diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2472 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2472 new file mode 100644 index 000000000..a56f72a9e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2472 @@ -0,0 +1 @@ +optimize nvme_directive_receive() function diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2475 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2475 new file mode 100644 index 000000000..3dab86fd4 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2475 @@ -0,0 +1 @@ +Inconsistency between cpu_tb_exec() and qemu_plugin_register_vcpu_tb_exec_cb()? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2476 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2476 new file mode 100644 index 000000000..536d16748 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2476 @@ -0,0 +1,52 @@ +Regression 9.1.0-rc0: Msys2/Clang64 build fails +Description of problem: +Building QEMU in Msys2/Clang64 environment now fails. It is possible with 8.2.0 and 9.0.0 if option "--disable-plugins" is used. + +I suppose this option is broken now: + +``` +[2207/2362] Linking target qemu-system-aarch64.exe +FAILED: qemu-system-aarch64.exe +"cc" "-m64" @qemu-system-aarch64.exe.rsp +lld: error: unknown argument: --dynamic-list=D:/msys64plain/home/Normalo/qemu-9.1.0-rc0/plugins/qemu-plugins.symbols + + +cc: error: linker command failed with exit code 1 (use -v to see invocation) + + +ninja: build stopped: subcommand failed. +make[1]: *** [Makefile:167: run-ninja] Error 1 +make[1]: Leaving directory '/home/Normalo/qemu-9.1.0-rc0/build' +make: *** [GNUmakefile:6: build] Error 2 +``` +Steps to reproduce: +1. tar -xf qemu-9.1.0-rc0.tar.xz +2. cd qemu-9.1.0-rc0 +3. ./configure --target-list=aarch64-softmmu --disable-plugins +4. make +Additional information: +See attached log files [configure.log](/uploads/c56dd6c9064d98d3498923adcd61a4f9/configure.log) and [build.log](/uploads/c3f16160cffcd4a817f0304226db604e/build.log) + +After reverting the last commit on plugins/meson.build the build succeeds, because here the parameter causing the failure (`--dynamic-list`) is only applied, if plugins are enabled. +``` +commit 0082475e26430297ef65e598db5b67c8ac182620 +Author: Paolo Bonzini <pbonzini@redhat.com> +Date: Thu Jun 6 15:07:23 2024 +0200 + + meson: merge plugin_ldflags into emulator_link_args + + These serve the same purpose, except plugin_ldflags ends up in the linker + command line in a more roundabout way (through specific_ss). Simplify. + + Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> +``` + +Configuring with plugins enabled fails with: +``` +../plugins/meson.build:28:32: ERROR: Command `D:\msys64plain\clang64\bin/dlltool.EXE --input-def D:/msys64plain/home/Normalo/qemu-9.1.0-rc0/build/plugins/qemu_plugin_api.def --output-delaylib D:/msys64plain/home/Normalo/qemu-9.1.0-rc0/build/plugins/libqemu_plugin_api.a --dllname qemu.exe` failed with status 1. + +A full log can be found at D:/msys64plain/home/Normalo/qemu-9.1.0-rc0/build/meson-logs/meson-log.txt + +ERROR: meson setup failed +``` +See attached log files [configure-plugins-enabled.log](/uploads/5ce608791fe9a47165c3fecaddce1aa8/configure-plugins-enabled.log) and [meson-log-plugins-enabled.txt](/uploads/8dc1e95726847270052def5d7b0bd63a/meson-log-plugins-enabled.txt) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2477 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2477 new file mode 100644 index 000000000..ace7a0a38 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2477 @@ -0,0 +1 @@ +GDB_HAS_MTE detection is incomplete diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2478 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2478 new file mode 100644 index 000000000..1b5690c2a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2478 @@ -0,0 +1,18 @@ +STM32F1 STM32VLDicovery board: incorrect clock register setting +Description of problem: +The execution of the program hangs when testing, from libopencm3 clock initialization, the status of the clock in ``rcc_wait_for_osc_ready()``. This function https://github.com/libopencm3/libopencm3/blob/master/lib/stm32/f1/rcc.c#L366 loops until the bit stating that the oscillator is stabilized is set. I am unable to find in qemu this bit being set upon clock initialization, which I believe is an hardware emulation shortcoming. Commenting this line in libopencm3 allows for the emulation to complete correctly, but I believe the error lies in the hardware emulation and not in the libopencm3 test. Reading the status of ``RCC_CR`` from ``gdb-multiarch`` probing the QEMU internal state returns 0, leading to the failure of the test at https://github.com/libopencm3/libopencm3/blob/master/lib/stm32/f1/rcc.c#L353 + +See https://www.st.com/resource/en/reference_manual/rm0008-stm32f101xx-stm32f102xx-stm32f103xx-stm32f105xx-and-stm32f107xx-advanced-armbased-32bit-mcus-stmicroelectronics.pdf for the expected behavior of this register content on page 99/1136 +``` +7.3.1 Clock control register (RCC_CR) + +Bit 17 HSERDY: External high-speed clock ready flag +Set by hardware to indicate that the HSE oscillator is stable. This bit needs 6 cycles of the +HSE oscillator clock to fall down after HSEON reset. +0: HSE oscillator not ready +1: HSE oscillator ready +``` +Steps to reproduce: +1. git clone --recursive https://github.com/libopencm3/libopencm3-examples +2. make +3. qemu-system-arm -M stm32vldiscovery -nographic -serial mon:stdio -kernel examples/stm32/f1/stm32vl-discovery/usart/usart.elf diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/248 b/gitlab/issues_text/target_missing/host_missing/accel_missing/248 new file mode 100644 index 000000000..f9e90fc12 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/248 @@ -0,0 +1 @@ +Reconnect failed with loopback virtio1.1 server mode test diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2480 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2480 new file mode 100644 index 000000000..c562db4e1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2480 @@ -0,0 +1,29 @@ +Two questions about VFIO device live migration +Description of problem: +For my own pcie device, i implement system memory && device memory dirty bitmap track and works well + +use pre-copy mode live migration by the way. + +first question: +- for system memory dirty bitmap sync, notice that last sync will come early than i expected + read qemu code and found qemu will call every savevm_state.handlers->save_live_complete_precopy callback + in "qemu_savevm_state_complete_precopy_iterable", and "vfio" handler will always behind "ram". + so here is question, my own vfio device will only be halted after "vfio" handler enter + save_live_complete_precopy, and last system memory dirty bitmap sync will come with "ram"'s + save_live_complete_precopy, there will be some system dirty between this period, should we add one more + system dirty bitmap sync after "vfio"'s save_live_complete_precopy + +second question: +- notice that qemu will clean up migration and call every savevm_state.handlers->save_cleanup call back, and + in this function, qemu will only call vfio listener's log_global_stop call back when vm_is_running + but for my vfio device, state will be paused(postmigrate) when enter here, so there is no chance for qemu + to relese some resource create by my device kernel mode driver, where should i put the logic about "stop + migration resource" anyway + +Thanks ^_^ +Steps to reproduce: +1. +2. +3. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2481 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2481 new file mode 100644 index 000000000..34b61a729 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2481 @@ -0,0 +1 @@ +Possible dereference of NULL diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2482 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2482 new file mode 100644 index 000000000..ac1bb2cc6 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2482 @@ -0,0 +1,136 @@ +qemu-system-x86_64: Live Migration fails with BLOCK_JOB_ERROR +Description of problem: +After disk migration is completed and RAM migration is being performed, migration status switches to 'pre-switchover'. +In the 'pre-switchover' migration state, block jobs status is still set to 'ready' instead of 'running' +on queried for block job status when 'offset' and 'length' diverged. Thus, It results in BLOCK_JOB_ERROR. +Steps to reproduce: +On source host +1. Add disk(s) that needed to be migrated by issuing 'blockdev-add' QMP command. +2. start blockdev-mirror operations to perform disk(s) transfer by issuing QMP command +3. start RAM migration. (send HMP commands - listed below +4. Migration status changed to 'pre-switchover'. While in 'pre-switchover', check for disk activity + +While RAM migration is happening, Migration status is changed to 'pre-switchover' +and observe that block jobs 'offset' and 'length' diverged. But, block job status is still set to 'ready' instead of 'running'. + +On destination host +1. Launch the VM in listening mode (-incoming) for migrations +2. start NBD server +3. add disks to NBD server. +4. set migration parameters by sending HMP commands +Additional information: +# On SOURCE Host, start all blockdev-add operations +# Issue QMP commands (blockdev-add) for all block devices ("drive-scsi-disk-0" and "drive-scsi-disk-1") of VM + +``` + { + "execute" => "blockdev-add", + "arguments" => { + "driver" => "raw", + "node-name" => "node_drive-scsi-disk-0", + "auto-read-only" => false, + "read-only" => false, + "file" => { + "driver" => "nbd", + "export" => "drive-scsi-disk-0", + "server" => { + "type" => "inet", + "host" => "2600:3c0f:17:14::21", + "port" => "37552", + }, + "tls-creds" => "tlscreds0" + } + } + } +``` + + { + "execute" => "blockdev-add", + "arguments" => { + "driver" => "raw", + "node-name" => "node_drive-scsi-disk-1", + "auto-read-only" => false, + "read-only" => false, + "file" => { + "driver" => "nbd", + "export" => "drive-scsi-disk-1", + "server" => { + "type" => "inet", + "host" => "2600:3c0f:17:14::21", + "port" => "37552", + }, + "tls-creds" => "tlscreds0" + } + } + } + +# On SOURCE Host, start all blockdev-mirror operations to start disk transfer +# i.e Issue QMP commands (blockdev-mirror) for each of those block devices ("drive-scsi-disk-0" and "drive-scsi-disk-1") + +``` + { + "execute" => "blockdev-mirror", + "arguments" => { + "device" => "drive-scsi-disk0", + "target" => "node_drive-scsi-disk-0", + "speed" => 100000000, + "sync" => "full", + } + } +``` + +``` + { + "execute" => "blockdev-mirror", + "arguments" => { + "device" => "drive-scsi-disk1", + "target" => "node_drive-scsi-disk-1", + "speed" => 100000000, + "sync" => "full", + } + } +``` + +# NBD server configuration on destination host by issuing QMP command +# Start NBD server +``` + { + "execute" => "nbd-server-start", + "arguments" => { + "addr" => { + "type" => "inet", + "data" => { + "host" => "2600:3c0f:17:14::21", + "port" => "37552" + } + }, + "tls-creds" => "tlscreds0" + } + } +``` + +# On DESTINATION Host +# Register incoming disks(2) with NBD server by issuing QMP commands to VM on the destination host +# Disk# 1 +``` + { + "execute" => "nbd-server-add", + "arguments" => { + "device" => "drive-scsi-disk0", + "writable" => true + } + } +``` +# Disk# 2 +``` + { + "execute" => "nbd-server-add", + "arguments" => { + "device" => "drive-scsi-disk1", + "writable" => true + } + } +``` + +# Wait for disks to finish the bulk of the data migration. +# diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2485 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2485 new file mode 100644 index 000000000..3b80f94f3 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2485 @@ -0,0 +1,47 @@ +getifaddrs linked with musl libc hangs on big-endian targets +Description of problem: +When the following C program (borrowed from curl's `configure`) is compiled for { m68k, ppc, ppc64, s390x } (possibly others, like or1k and sparc) and linked against musl libc, it hangs inside musl when run. Copying the same binaries to real hardware results in success. + +```c +#include <stdlib.h> +#include <ifaddrs.h> + +int +main (void) +{ + + struct ifaddrs *ifa = 0; + int error; + + error = getifaddrs(&ifa); + if (error || !ifa) + exit(1); + else + exit(0); + + return 0; +} +``` +Steps to reproduce: +1. Compile the above program and link it with musl libc (pre-built toolchains are available [here](https://musl.cc/)) +2. Run the appropriate `qemu-*` (e.g. `qemu-m68k ./test` or `qemu-ppc ./test`) +3. Observe that the process hangs. +Additional information: +This has come up elsewhere: + +* https://bugs.gentoo.org/914256 +* https://www.openwall.com/lists/musl/2018/05/30/4 +* Likely affects or1k but I can't test that at the moment (need to debug an unrelated issue with that toolchain) +* Likely affects sparc but that port/toolchain is also a WIP + +Here are some static sample binaries for the above program: + +* https://temp.zv.io/qemu-bug.tar.xz (no guarantees of continued existence months or years later) + +GitLab labels seem to be missing: + +* ~"kind::Bug" +* ~"linux-user" +* ~"target: ppc" +* ~"target: m68k" +* ~"target: s390x" diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2490 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2490 new file mode 100644 index 000000000..fe28dc94b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2490 @@ -0,0 +1,51 @@ +Windows: virtio-vga-gl no longer works with current virglrenderer version +Description of problem: +Error occurs, when executing QEMU with virtio-vga-gl device using current virglrenderer: +First the boot screen is shown as expected. +After a short while the screen shows and keeps showing "virtio-vga-gl: Display output is not active." +Console logs: +``` +qemu: GtkGLArea console lacks DMABUF support. +qemu: GtkGLArea console lacks DMABUF support. +qemu: GtkGLArea console lacks DMABUF support. +qemu: GtkGLArea console lacks DMABUF support. +Realize gdk gl context failed: GL-Kontext kann nicht erstellt werden +Realize gdk gl context failed: GL-Kontext kann nicht erstellt werden +virtio_gpu_virgl_process_cmd: ctrl 0x103, error 0x1203 +virtio_gpu_virgl_process_cmd: ctrl 0x103, error 0x1203 +virtio_gpu_virgl_process_cmd: ctrl 0x103, error 0x1203 +``` +Steps to reproduce: +1. Prepare current Msys2/Ucrt64 environment including virglrenderer 1.0.1 by installing QEMU as described in https://www.qemu.org/download/#windows +2. `wget https://download.opensuse.org/distribution/leap/15.3/live/openSUSE-Leap-15.3-GNOME-Live-x86_64-Media.iso` +3. `qemu-system-x86_64.exe -m 1024 -display gtk,gl=on -device virtio-vga-gl -cdrom openSUSE-Leap-15.3-GNOME-Live-x86_64-Media.iso` +Additional information: +virglrenderer may use certain D3D features starting with virglrenderer 1.0.0, see https://gitlab.freedesktop.org/virgl/virglrenderer/-/merge_requests/1103 for details + +Given virglrenderer >= 1.0.0, QEMU activates these D3D features since https://gitlab.com/qemu-project/qemu/-/commit/c1600f84ce011a056c9c432c8ad8d77f7f8b9e6f. + +But the current QEMU implementation is broken when using these D3D features. + +git bisect finishes with: +``` +574b64aa6754ba491f51024c5a823a674d48a658 is the first bad commit +commit 574b64aa6754ba491f51024c5a823a674d48a658 +Author: Dmitry Osipenko <dmitry.osipenko@collabora.com> +Date: Mon Jan 29 10:39:21 2024 +0300 + + virtio-gpu: Correct virgl_renderer_resource_get_info() error check + + virgl_renderer_resource_get_info() returns errno and not -1 on error. + Correct the return-value check. + + Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com> + Signed-off-by: Dmitry Osipenko <dmitry.osipenko@collabora.com> + Message-Id: <20240129073921.446869-1-dmitry.osipenko@collabora.com> + Cc: qemu-stable@nongnu.org + Reviewed-by: Michael S. Tsirkin <mst@redhat.com> + Signed-off-by: Michael S. Tsirkin <mst@redhat.com> + + contrib/vhost-user-gpu/virgl.c | 6 +++--- + hw/display/virtio-gpu-virgl.c | 2 +- + 2 files changed, 4 insertions(+), 4 deletions(-) +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2492 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2492 new file mode 100644 index 000000000..eb8c3945f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2492 @@ -0,0 +1,20 @@ +Unable to disable gvnc dependency during build +Description of problem: +The qtest tests will pick up a copy of gvnc if it happens to be installed and there does not appear +to be any way of disabling the dependency to ensure a reproducible build. We tripped over this in +bulk builds on OpenBSD. +Steps to reproduce: +1. Install gvnc +2. Build QEMU +Additional information: +From tests/qtest/meson.build + +``` +if vnc.found() + gvnc = dependency('gvnc-1.0', method: 'pkg-config', required: false) + if gvnc.found() + qtests += {'vnc-display-test': [gvnc]} + qtests_generic += [ 'vnc-display-test' ] + endif +endif +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2493 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2493 new file mode 100644 index 000000000..11521877a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2493 @@ -0,0 +1 @@ +qemu-img delete snapshot by id diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2494 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2494 new file mode 100644 index 000000000..7a40b89f6 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2494 @@ -0,0 +1 @@ +Isolated network between VMs not visible to the host diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2496 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2496 new file mode 100644 index 000000000..72f7c471b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2496 @@ -0,0 +1,33 @@ +Regression 9.1.0-rc1: Adventcalendar 2016, Day 14 crashes +Description of problem: +Crashes with + ``` + **** PANIC: **** + terminating with uncaught exception of type hw::Device_not_found: Device of type NIC not found at position #0 + ``` +see [acorn.log](/uploads/daa06857763716183cec625ead619387/acorn.log) for details +Steps to reproduce: +1. Download https://www.qemu-advent-calendar.org/2016/download/day14.tar.xz +2. Execute +Additional information: +git bisect determines: + ``` +64f75f57f9d2c8c12ac6d9355fa5d3a2af5879ca is the first bad commit +commit 64f75f57f9d2c8c12ac6d9355fa5d3a2af5879ca +Author: David Woodhouse <dwmw@amazon.co.uk> +Date: Tue Jul 9 13:34:44 2024 +0100 + + net: Reinstate '-net nic, model=help' output as documented in man page + + While refactoring the NIC initialization code, I broke '-net nic,model=help' + which no longer outputs a list of available NIC models. + + Fixes: 2cdeca04adab ("net: report list of available models according to platform") + Cc: qemu-stable@nongnu.org + Signed-off-by: David Woodhouse <dwmw@amazon.co.uk> + Reviewed-by: Michael Tokarev <mjt@tls.msk.ru> + Signed-off-by: Jason Wang <jasowang@redhat.com> + + net/net.c | 25 ++++++++++++++++++++++--- + 1 file changed, 22 insertions(+), 3 deletions(-) + ``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/250 b/gitlab/issues_text/target_missing/host_missing/accel_missing/250 new file mode 100644 index 000000000..a3ab92c5c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/250 @@ -0,0 +1 @@ +windows qemu-img fails to convert vhdx, assertion failure diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2501 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2501 new file mode 100644 index 000000000..a4451aa3e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2501 @@ -0,0 +1 @@ +compile qemu as a shared library diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2503 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2503 new file mode 100644 index 000000000..42a28bd06 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2503 @@ -0,0 +1,9 @@ +how to install cmake scipt in QEMU with riscv +Description of problem: + +Steps to reproduce: +1. +2. +3. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2505 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2505 new file mode 100644 index 000000000..15f79cbfc --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2505 @@ -0,0 +1 @@ +Interpreter ELF flags ignored when selecting CPU diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2506 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2506 new file mode 100644 index 000000000..d2c0733e6 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2506 @@ -0,0 +1,58 @@ +LC_RPATH stripped despite setting INSTALL_REMOVE_ENVIRONMENT_RPATH=FALSE +Description of problem: +When I try to run qemu, I get the following output: +> dyld[93165]: Library not loaded: @rpath/libjpeg.62.dylib +> Referenced from: <85BC1FBA-CA2E-3CAC-9ABF-E5330AC86CAF> /Users/mj/local/bin/qemu-system-aarch64 +> Reason: no LC_RPATH's found +Steps to reproduce: +If the qemu-9.0.2 folder is present, remove it: +``` +$ rm -rf qemu-9.0.2 +``` +Create the source folder: +``` +$ tar xzf qemu-9.0.2.tar.xz +$ cd qemu-9.0.2 +``` + +Make sure the following environment variables are set: +``` +$ export CC=clang +$ export LDFLAGS="-rpath $HOME/local/lib" +$ export INSTALL_REMOVE_ENVIRONMENT_RPATH=FALSE +``` + +Configure as follows: +``` +$ ./configure --prefix=$HOME/local --disable-sdl --enable-slirp --enable-fdt=internal --enable-spice +``` + +Build +``` +$ make -j 10 +``` + +Note there are a large number of linker warnings like this: +> ld: warning: duplicate -rpath '/Users/mj/local/lib' ignored + +Execute this: +``` +$ otool -l build/qemu-system-aarch64 | grep LC_RPATH -A2 +``` + +See this output +> cmd LC_RPATH +> cmdsize 32 +> path /Users/mj/local/lib (offset 12) + +Change directory to $HOME/local/bin & execute: +``` +$ otool -l qemu-system-aarch64 | grep LC_RPATH -A2 +``` + +The output is now empty - the LC_RPATH has been stripped by the install. This results in the failure to execute the resulting binary. Note, I tried using install_name_tool to add the RPATH, but it warned me this changed the signature of the file, and it would not run. + +Executing qemu-system-aarch64 produces the following: +> dyld[93165]: Library not loaded: @rpath/libjpeg.62.dylib +> Referenced from: <85BC1FBA-CA2E-3CAC-9ABF-E5330AC86CAF> /Users/mj/local/bin/qemu-system-aarch64 +> Reason: no LC_RPATH's found diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2508 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2508 new file mode 100644 index 000000000..fcf59e5d5 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2508 @@ -0,0 +1 @@ +test-aio unreliable on MSYS2 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/251 b/gitlab/issues_text/target_missing/host_missing/accel_missing/251 new file mode 100644 index 000000000..04253a5f8 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/251 @@ -0,0 +1 @@ +Qemu DOS Quake - 640x480 and above resolutions - Unable to load VESA palette in dos prompt and game crashing are not working diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2510 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2510 new file mode 100644 index 000000000..b70c807ff --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2510 @@ -0,0 +1,45 @@ +Cross compiling tools / qemu-img results in "ninja: no work to do" +Description of problem: +I have the following Dockerfile setting up a cross-compile environment for QEMU. +I am trying to build qemu-img.exe only at the moment + + +``` +FROM fedora as builder +RUN --mount=type=cache,target=/var/cache \ + dnf -v install --assumeyes strace gcc make mingw64-gcc mingw64-binutils python-setuptools meson mingw64-glib2-static mingw64-glib2 diffutils + +FROM builder as qemu-builder +WORKDIR /src/qemu #assuming qemu source tree is already available at /src/qemu +RUN +RUN ./configure --cross-prefix=x86_64-w64-mingw32- --target-list='' --static +RUN make V=1 tools +``` +With either `make tools` or `make qemu-img.exe` I get + +``` +#10 0.265 changing dir to build for make "tools"... +#10 0.267 make[1]: Entering directory '/src/qemu/build' +#10 0.330 ninja: no work to do. +#10 0.331 { \ +#10 0.331 echo 'ninja-targets = \'; \ +#10 0.331 /usr/bin/ninja -t targets all | sed 's/:.*//; $!s/$/ \\/'; \ +#10 0.331 echo 'build-files = \'; \ +#10 0.331 /usr/bin/ninja -t query build.ninja | sed -n '1,/^ input:/d; /^ outputs:/q; s/$/ \\/p'; \ +#10 0.331 } > Makefile.ninja.tmp && mv Makefile.ninja.tmp Makefile.ninja +#10 0.363 /src/qemu/build/pyvenv/bin/meson introspect --targets --tests --benchmarks | /src/qemu/build/pyvenv/bin/python3 -B scripts/mtest2make.py > Makefile.mtest +#10 0.634 make[1]: Nothing to be done for 'tools'. +#10 0.634 make[1]: Leaving directory '/src/qemu/build' +#10 DONE 0.6s +``` + +Following the info in `make help`, I tried `make qemu-img.o` which resulted in + +``` +cc -c -o qemu-img.o qemu-img.c +qemu-img.c:25:10: fatal error: qemu/osdep.h: No such file or directory + 25 | #include "qemu/osdep.h" + | ^~~~~~~~~~~~~~ +``` +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2512 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2512 new file mode 100644 index 000000000..c87e63666 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2512 @@ -0,0 +1,45 @@ +macOS builds of target arm-softmmu broken +Description of problem: +Attempting to build for target `arm-softmmu` on macOS fails with errors: + +``` +[919/2786] Compiling C object libblock.a.p/block_file-posix.c.o +FAILED: libblock.a.p/block_file-posix.c.o +clang -Ilibblock.a.p -I. -I.. -Iqapi -Itrace -Iui -Iui/shader -Iblock -I/nix/store/vb7baj6dq2mvynfh6zmwxz57w83h7w0q-zlib-1.3.1-dev/include -I/nix/store/k1yzx1ykpwmhqvyr0j5fxvs9px7k92m7-glib-2.80.4-dev/include/glib-2.0 -I/nix/store/fm2kb8jvvc9s9nhi2gpr3jp6xxjxcvkq-glib-2.80.4/lib/glib-2.0/include -I/nix/store/k1yzx1ykpwmhqvyr0j5fxvs9px7k92m7-glib-2.80.4-dev/include -fcolor-diagnostics -Wall -Winvalid-pch -std=gnu11 -O2 -g -fstack-protector-strong -Wempty-body -Wendif-labels -Wexpansion-to-defined -Wformat-security -Wformat-y2k -Wignored-qualifiers -Winit-self -Wmissing-format-attribute -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wredundant-decls -Wstrict-prototypes -Wtype-limits -Wundef -Wvla -Wwrite-strings -Wno-gnu-variable-sized-type-not-at-end -Wno-initializer-overrides -Wno-missing-include-dirs -Wno-psabi -Wno-shift-negative-value -Wno-string-plus-int -Wno-tautological-type-limit-compare -Wno-typedef-redefinition -iquote . -iquote /Users/josh/workspace/qemu -iquote /Users/josh/workspace/qemu/include -iquote /Users/josh/workspace/qemu/host/include/aarch64 -iquote /Users/josh/workspace/qemu/host/include/generic -iquote /Users/josh/workspace/qemu/tcg/aarch64 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -fno-strict-aliasing -fno-common -fwrapv -fno-pie -ftrivial-auto-var-init=zero -fzero-call-used-regs=used-gpr -MD -MQ libblock.a.p/block_file-posix.c.o -MF libblock.a.p/block_file-posix.c.o.d -o libblock.a.p/block_file-posix.c.o -c ../block/file-posix.c +../block/file-posix.c:1501:19: error: variable has incomplete type 'struct statfs' + struct statfs buf; + ^ +../block/file-posix.c:1501:12: note: forward declaration of 'struct statfs' + struct statfs buf; + ^ +../block/file-posix.c:1503:10: error: call to undeclared function 'fstatfs'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration] + if (!fstatfs(s->fd, &buf)) { + ^ +2 errors generated. +``` +Steps to reproduce: +1. nix-shell -p python3 ninja pkg-config glib +2. ./configure --target-list=arm-softmmu +3. make +Additional information: +The following patch fixes the issue (although I'm not sure whether this is the most appropriate fix): + +``` +diff --git a/block/file-posix.c b/block/file-posix.c +index ff928b5e85..6c78db3b0b 100644 +--- a/block/file-posix.c ++++ b/block/file-posix.c +@@ -44,10 +44,10 @@ + + #if defined(__APPLE__) && (__MACH__) + #include <sys/ioctl.h> +-#if defined(HAVE_HOST_BLOCK_DEVICE) +-#include <paths.h> + #include <sys/param.h> + #include <sys/mount.h> ++#if defined(HAVE_HOST_BLOCK_DEVICE) ++#include <paths.h> + #include <IOKit/IOKitLib.h> + #include <IOKit/IOBSD.h> + #include <IOKit/storage/IOMediaBSDClient.h> +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2513 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2513 new file mode 100644 index 000000000..c0d2d7687 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2513 @@ -0,0 +1,13 @@ +CXL Device Missing PCI_CAP_ID_PM (01h) in CAP List Implementation According to PCIe SPEC +Description of problem: +- The lack of **PCI_CAP_ID_PM (01h)** will not cause any crash or error when running QEMU, but it is violated to the PCIe SPEC. +- When some vendors test the power management capability (e.g., Linux Runtime PM), they must manually implement this CAP list to support the D1/D2/D3_Hot d-states changes. +- We don't see any PCI_CAP_ID_PM (01h) in the CXL rootport or endpoint + + {width=349 height=474} + + +# +Steps to reproduce: +1. Run the qemu-system-x86 (See QEMU command line) +2. sudo lspci -xxx diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2514 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2514 new file mode 100644 index 000000000..b820bd4f0 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2514 @@ -0,0 +1 @@ +network unreachable to esxi 8 guest diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2515 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2515 new file mode 100644 index 000000000..cbb87fbda --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2515 @@ -0,0 +1,46 @@ +qemu -daemonize crashes on macOS with "NSPlaceholderDate initialize may have been in progress in another thread" +Description of problem: +Context: I build [an open source project](https://tsduck.io/) on several operating systems and architectures. For riscv64, s390x, ppc64, I build in emulated virtual machines. The three emulated OS work correctly when running qemu manually and the project is correctly built. + +Now, I want to automate the process in a script: for each target architecture, boot the VM (start qemu as a background process), connect to the VM using ssh, build the software, collect the binaries, shut down the VM. + +Starting the same qemu command as used interactively as a background process with `&` does not work and fails immediately, apparently because of the lack of stdin. So, I added option `-daemonize` (and removed `-nographic` because an error message says the two options are incompatible). + +Using `-daemonize` instead of `-nographic`, all qemu command immediately fail with the following error: + +``` +objc[1141]: +[__NSPlaceholderDate initialize] may have been in progress in another thread when fork() was called. +objc[1141]: +[__NSPlaceholderDate initialize] may have been in progress in another thread when fork() was called. We cannot safely call it or ignore it in the fork() child process. Crashing instead. Set a breakpoint on objc_initializeAfterForkError to debug. +``` +Steps to reproduce: +``` +$ qemu-system-riscv64 -machine virt -smp 8 -m 8192 -daemonize \ + -bios fw_jump.bin -kernel u-boot.bin \ + -device virtio-net-device,netdev=net \ + -netdev user,id=net,hostfwd=tcp::2233-:22 \ + -drive file=disk.qcow2,format=qcow2,if=virtio -device virtio-rng-pci +objc[1141]: +[__NSPlaceholderDate initialize] may have been in progress in another thread when fork() was called. +objc[1141]: +[__NSPlaceholderDate initialize] may have been in progress in another thread when fork() was called. We cannot safely call it or ignore it in the fork() child process. Crashing instead. Set a breakpoint on objc_initializeAfterForkError to debug. + + +$ qemu-system-s390x -machine s390-ccw-virtio -cpu max,zpci=on -smp 8 -m 8192 -daemonize \ + -drive file=disk.qcow2,format=qcow2,if=none,id=drive-virtio-disk0,cache=none \ + -device virtio-blk-ccw,devno=fe.0.0002,drive=drive-virtio-disk0,bootindex=1 \ + -nic user,hostfwd=tcp::2288-:22 +objc[1209]: +[__NSPlaceholderDate initialize] may have been in progress in another thread when fork() was called. +objc[1209]: +[__NSPlaceholderDate initialize] may have been in progress in another thread when fork() was called. We cannot safely call it or ignore it in the fork() child process. Crashing instead. Set a breakpoint on objc_initializeAfterForkError to debug. + + +$ qemu-system-ppc64 -smp 8 -m 8192 -daemonize \ + -drive file=disk.qcow2,format=qcow2 -nic user,hostfwd=tcp::2299-:22 +qemu-system-ppc64: warning: TCG doesn't support requested feature, cap-cfpc=workaround +qemu-system-ppc64: warning: TCG doesn't support requested feature, cap-sbbc=workaround +qemu-system-ppc64: warning: TCG doesn't support requested feature, cap-ibs=workaround +qemu-system-ppc64: warning: TCG doesn't support requested feature, cap-ccf-assist=on +objc[1166]: +[__NSPlaceholderDate initialize] may have been in progress in another thread when fork() was called. +objc[1166]: +[__NSPlaceholderDate initialize] may have been in progress in another thread when fork() was called. We cannot safely call it or ignore it in the fork() child process. Crashing instead. Set a breakpoint on objc_initializeAfterForkError to debug. +``` + +All the above commands work correctly when using `-nographic` instead of `-daemonize`. The virtual disks are the same as in the interactive runs, with a fully configured Linux OS (Ubuntu or Debian). +Additional information: +From a [report from here](https://stackoverflow.com/questions/63041445/python-os-high-sierra-nsplaceholderdate-error), I tried to define the environment variable `OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES` before running qemu. The `[__NSPlaceholderDate initialize]` errors disappear but qemu still crashes immediately. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2516 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2516 new file mode 100644 index 000000000..c9b85e7dd --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2516 @@ -0,0 +1 @@ +Qemu 9.1 dropped support for Ubuntu 20.04 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2517 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2517 new file mode 100644 index 000000000..c800e7ef1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2517 @@ -0,0 +1 @@ +destroying a vCPU will leak its AddressSpaces diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2519 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2519 new file mode 100644 index 000000000..91038368a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2519 @@ -0,0 +1 @@ +make check TIMEOUT_MULTIPLIER variable is undocumented diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/252 b/gitlab/issues_text/target_missing/host_missing/accel_missing/252 new file mode 100644 index 000000000..db998ac58 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/252 @@ -0,0 +1 @@ +KVM Old ATI(pre) AMD card passthrough is not working diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2521 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2521 new file mode 100644 index 000000000..f47ac5c0f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2521 @@ -0,0 +1,16 @@ +USB Passthrough Improper Remote Wakeup +Description of problem: +I am doing research with Linux Power Management interactions with USB devices. Which is why I would like to be able to wake a qemu vm from suspend with a passed through USB device. The first issue is that remote wakeup from usb devices do not wake the vm at all when running in -nographic mode (issuing system_wakeup from a qemu monitor shell will wake it though). When running with a GUI it is possible to wake the vm from a usb device as well as the qemu monitor shell but both will result in the GUI screen being black afterwards. It is still possible to use the vm though. Finally, waking the vm with a usb device is only possible when a valid usb device is passed through in the qemu launch command line. But interestingly the usb device specified to be passed through will only wakeup the vm if it is unplugged and plugged back in during the suspend. All other usb devices can wakeup the vm normally even though they are not passed through. It is not clear to me what is going on here and why other devices not being passed through to qemu can wake the vm. Note I have also enabled the /sys/bus/usb/devices/usb#/power/wakeup file and have manually unsuppressed the remote_wakeup flag in the source code to enable the /sys/bus/usb/devices/#-#/power/wakeup files to be generated but it has not affected anything. +Steps to reproduce: +I have tested this issue with multiple kernel versions (6.10, 6.10-rc4, 6.6.43) as well as custom and generic kernel configs and different debian images so these do not seem to be the problem. But here is a detailed description of the exact setup I am currently using: + +1. Download linux-6.10-rc4 source and configure with syzkaller fuzzing config https://github.com/google/syzkaller/blob/master/dashboard/config/linux/upstream-usb.config +2. Set CONFIG_KCOV_INSTRUMENT_ALL to off (breaks suspend/resume in vm) and create bzImage +2. Create a debian bookworm image with syzkaller script https://github.com/google/syzkaller/blob/master/tools/create-image.sh +3. Download and build Qemu from source (see attached for detailed configuration and dependencies) +4. Attach a usb keyboard and mouse +5. Choose one device to pass through via command line +6. Try waking the vm with nographic and graphic mode using the usb devices +Additional information: +[configuration_output.txt](/uploads/f7d3487dab65deef40bd0e110b64a573/configuration_output.txt) +[gui_wakeup_log.txt](/uploads/72b192a88d587eced4bb4032307307e5/gui_wakeup_log.txt) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2524 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2524 new file mode 100644 index 000000000..caf9a4d60 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2524 @@ -0,0 +1,3 @@ +Reverse debugging is broken on release and stable branches +Description of problem: +Master branch has commit 94962ff00d09674047aed896e87ba09736cd6941, which reverts incorrect commit and fix reverse debugging. But this commit is missing in 9.0.x 9.1.x releases branches and in stable branches too. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2525 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2525 new file mode 100644 index 000000000..feeb64730 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2525 @@ -0,0 +1 @@ +bFLT triggers accel/tcg/user-exec.c:505: page_set_flags: Assertion `have_mmap_lock()' failed. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2526 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2526 new file mode 100644 index 000000000..88afd4a59 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2526 @@ -0,0 +1,39 @@ +qemu-system-aarch64: Build of system emulators with --static failed on aarch64 Ubuntu 22.04 for tests/unit/test-bitcnt +Description of problem: +Build Qemu got error: +``` +[1107/2870] Compiling C object tcg/libtcg_system.fa.p/perf.c.o +[1108/2870] Linking target tests/unit/test-bitcnt +FAILED: tests/unit/test-bitcnt +cc -o tests/unit/test-bitcnt tests/unit/test-bitcnt.p/test-bitcnt.c.o -Wl,--as-needed -Wl,--no-undefined -pie -Wl,--whole-archive libevent-loop-base.fa libqom.fa -Wl,--no-whole-archive -static-pie -fstack-protector-strong -Wl,-z,relro -Wl,-z,now -Wl,--start-group libqemuutil.a subprojects/libvhost-user/libvhost-user-glib.a subprojects/libvhost-user/libvhost-user.a libevent-loop-base.fa libqom.fa /usr/lib/aarch64-linux-gnu/libgio-2.0.a /usr/lib/aarch64-linux-gnu/libgmodule-2.0.a -pthread /usr/lib/aarch64-linux-gnu/libz.a -ldl /usr/lib/aarch64-linux-gnu/libblkid.a /usr/lib/aarch64-linux-gnu/libselinux.a /usr/lib/aarch64-linux-gnu/libsepol.a /usr/lib/aarch64-linux-gnu/libpcre2-8.a /usr/lib/aarch64-linux-gnu/libgobject-2.0.a /usr/lib/aarch64-linux-gnu/libffi.a /usr/lib/aarch64-linux-gnu/libglib-2.0.a -lm /usr/lib/aarch64-linux-gnu/libpcre.a -lmount -lmount -Wl,--end-group +/usr/bin/ld: cannot find -lmount: No such file or directory +/usr/bin/ld: cannot find -lmount: No such file or directory +collect2: error: ld returned 1 exit status +[1109/2870] Linking target tests/unit/test-qapi-util +FAILED: tests/unit/test-qapi-util +cc -o tests/unit/test-qapi-util tests/unit/test-qapi-util.p/test-qapi-util.c.o -Wl,--as-needed -Wl,--no-undefined -pie -Wl,--whole-archive libevent-loop-base.fa libqom.fa -Wl,--no-whole-archive -static-pie -fstack-protector-strong -Wl,-z,relro -Wl,-z,now -Wl,--start-group libqemuutil.a subprojects/libvhost-user/libvhost-user-glib.a subprojects/libvhost-user/libvhost-user.a libevent-loop-base.fa libqom.fa /usr/lib/aarch64-linux-gnu/libgio-2.0.a /usr/lib/aarch64-linux-gnu/libgmodule-2.0.a -pthread /usr/lib/aarch64-linux-gnu/libz.a -ldl /usr/lib/aarch64-linux-gnu/libblkid.a /usr/lib/aarch64-linux-gnu/libselinux.a /usr/lib/aarch64-linux-gnu/libsepol.a /usr/lib/aarch64-linux-gnu/libpcre2-8.a /usr/lib/aarch64-linux-gnu/libgobject-2.0.a /usr/lib/aarch64-linux-gnu/libffi.a /usr/lib/aarch64-linux-gnu/libglib-2.0.a -lm /usr/lib/aarch64-linux-gnu/libpcre.a -lmount -lmount -Wl,--end-group +/usr/bin/ld: cannot find -lmount: No such file or directory +/usr/bin/ld: cannot find -lmount: No such file or directory +collect2: error: ld returned 1 exit status +[1110/2870] Linking target tests/unit/check-qom-interface +FAILED: tests/unit/check-qom-interface +cc -o tests/unit/check-qom-interface tests/unit/check-qom-interface.p/check-qom-interface.c.o -Wl,--as-needed -Wl,--no-undefined -pie -Wl,--whole-archive libevent-loop-base.fa libqom.fa -Wl,--no-whole-archive -static-pie -fstack-protector-strong -Wl,-z,relro -Wl,-z,now -Wl,--start-group libqemuutil.a subprojects/libvhost-user/libvhost-user-glib.a subprojects/libvhost-user/libvhost-user.a libevent-loop-base.fa libqom.fa /usr/lib/aarch64-linux-gnu/libgio-2.0.a /usr/lib/aarch64-linux-gnu/libgmodule-2.0.a -pthread /usr/lib/aarch64-linux-gnu/libz.a -ldl /usr/lib/aarch64-linux-gnu/libblkid.a /usr/lib/aarch64-linux-gnu/libselinux.a /usr/lib/aarch64-linux-gnu/libsepol.a /usr/lib/aarch64-linux-gnu/libpcre2-8.a /usr/lib/aarch64-linux-gnu/libgobject-2.0.a /usr/lib/aarch64-linux-gnu/libffi.a /usr/lib/aarch64-linux-gnu/libglib-2.0.a -lm /usr/lib/aarch64-linux-gnu/libpcre.a -lmount -lmount -Wl,--end-group +/usr/bin/ld: cannot find -lmount: No such file or directory +/usr/bin/ld: cannot find -lmount: No such file or directory +collect2: error: ld returned 1 exit status +``` +After install libmount-dev, this error is still there. +If we just run: +``` +./configure --target-list=aarch64-softmmu --enable-kvm +make -16 +``` +This works well. +Steps to reproduce: +``` +1. ./configure --target-list=aarch64-softmmu --enable-kvm --disable-brlapi --disable-docs --disable-curses --disable-gtk --disable-opengl --disable-sdl --disable-spice --disable-vte --disable-vnc --disable-vnc-jpeg --disable-png --disable-vnc-sasl --disable-auth-pam --disable-glusterfs --disable-libiscsi --disable-libnfs --disable-libssh --disable-bzip2 --disable-lzo --disable-snappy --disable-slirp --disable-libusb --disable-usb-redir --static --disable-qom-cast-debug --disable-libudev --disable-curl --disable-rdma --disable-tools --enable-virtfs --disable-bsd-user --disable-linux-user --disable-sparse --disable-vde --disable-nettle --disable-xen --disable-linux-aio --disable-capstone --disable-virglrenderer --disable-replication --disable-smartcard --disable-guest-agent --disable-guest-agent-msi --disable-vvfat --disable-vdi --disable-qed --disable-qcow1 --disable-bochs --disable-cloop --disable-dmg --disable-parallels --disable-colo-proxy --disable-debug-graph-lock --disable-hexagon-idef-parser --disable-libdw --disable-pipewire --disable-pixman --disable-relocatable --disable-rutabaga-gfx --disable-vmdk --disable-avx512bw --disable-vpc --disable-vhdx --disable-hv-balloon + +2.make -j16 +``` +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2527 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2527 new file mode 100644 index 000000000..0b49919c0 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2527 @@ -0,0 +1 @@ +bFLT parser doesn't select MMU-less CPU diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2528 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2528 new file mode 100644 index 000000000..a3295ce56 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2528 @@ -0,0 +1,9 @@ +nbd: CVE-2024-7409 fix is incomplete +Description of problem: +Patch will hit list soon, but opening issue here since if this misses 9.1, we would need to allocate a second CVE for having an incomplete fix (a remaining use-after-free) in the code originally proposed for CVE-2024-7409. +Steps to reproduce: +1. stress test of attempting repeated 'qemu-nbd --list' in parallel with repeated 'nbd-server-start/nbd-server-stop' loops in a qemu process revealed a use-after-free SEGV of nbd_server->listener +2. +3. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2529 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2529 new file mode 100644 index 000000000..971c62595 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2529 @@ -0,0 +1,32 @@ +`stack smashing detected` running arm64 image from amd64 machine +Description of problem: +When running a linux/arm64 `ubuntu:20.04` docker image on a linux/amd64 machine, an single command `apt-get update` will through below error +```sh +root@189bd36b9ae7:/# apt-get update +0% [Working]*** stack smashing detected ***: terminated +Reading package lists... Done +E: Method http has died unexpectedly! +E: Sub-process http received signal 6. + +``` + +Tested this is happening for ubuntu:18.04, ubuntu:20.04, ubuntu:22.04 so far + +If running same image directly from an ARM64 host, issue is gone +Steps to reproduce: +1. install QEMU on an AMD64 host machine (Ubuntu20) + ```sh + docker run --rm --privileged multiarch/qemu-user-static --reset -p yes + ``` +2. run linux/arm64 docker image of ubuntu:20.04 + ```sh + docker run --platform linux/arm64 -it --entrypoint /bin/bash ubuntu:20.04 + ``` +3. from within the container, run `apt-get update`, it will through below error + ```sh + root@189bd36b9ae7:/# apt-get update + 0% [Working]*** stack smashing detected ***: terminated + Reading package lists... Done + E: Method http has died unexpectedly! + E: Sub-process http received signal 6. + ``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/253 b/gitlab/issues_text/target_missing/host_missing/accel_missing/253 new file mode 100644 index 000000000..50482b708 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/253 @@ -0,0 +1 @@ +Qemu Win98 VM with KVM videocard passthrough DOS mode video is not working for most of games.. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2532 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2532 new file mode 100644 index 000000000..b8d4e440d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2532 @@ -0,0 +1,40 @@ +empty vmdk disk created by qemu-img cann't import to vmware ESXi or Workstation +Description of problem: +qemu-img create empty vmdk file, and can't import to vmware workstation or ESXi. the ovftool + fail. the log: + +> ``` +> 2024-08-23T11:19:32.335+08:00 verbose OVFTool[4088548] [Originator@6876 sub=Default] Opening disk target empty-disk2.vmdk +> 2024-08-23T11:19:32.335+08:00 error OVFTool[4088548] [Originator@6876 sub=Default] Error on read, error: -1 +> 2024-08-23T11:19:32.336+08:00 verbose OVFTool[4088187] [Originator@6876 sub=Default] Exception thrown: N5boost16exception_detail10clone_implINS_17unknown_exceptionEEE(std::exception) +> 2024-08-23T11:19:32.337+08:00 verbose OVFTool[4088187] [Originator@6876 sub=Default] Backtrace: +> --> [backtrace begin] product: VMware Workstation, version: e.x.p, build: build-15722219, tag: OVFTool, cpu: x86_64, os: linux, buildType: release +> --> backtrace[00] libvmacore.so[0x003DD716] +> --> backtrace[01] libvmacore.so[0x001CF8DF]: Vmacore::System::Stacktrace::CaptureWork(unsigned int) +> --> backtrace[02] libvmacore.so[0x001B6EA9]: Vmacore::System::SystemFactory::CreateQuickBacktrace(Vmacore::Ref<Vmacore::System::Backtrace>&) +> --> backtrace[03] libvmacore.so[0x0016CF2E]: Vmacore::Throwable::Throwable(std::string&&) +> --> backtrace[04] ovftool.bin[0x001C1F38] +> --> backtrace[05] ovftool.bin[0x002008D5] +> --> backtrace[06] ovftool.bin[0x00129EF0] +> --> backtrace[07] libc.so.6[0x00044E50] +> --> backtrace[08] libc.so.6[0x00044EFC] +> --> backtrace[09] ovftool.bin[0x00132D21] +> --> [backtrace end] +> ``` + +the log file: +[test.log](/uploads/174db2ace468bd9f0ec3ab14de524217/test.log) +Steps to reproduce: +1. create empty vmdk file + +./qemu-img create -f vmdk -o adapter_type=lsilogic,subformat=streamOptimized empty.vmdk 1G + +2. add empty file info to ovf file +<File ovf:href="empty.vmdk" ovf:id="file2"/> + +3. import it to vmware workstation +Additional information: +If i write some data to empty vmdk file, it can import successfully. The reson: qemu only write metadata for empty vmdk file, but the ovftool need read more data and it cann't read more. +we can write one sector zero data after the metadata, ovftool work well. +I submitted the patch: +https://patchew.org/QEMU/20240822105237.777-1-luzhipeng@cestc.cn/ diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2535 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2535 new file mode 100644 index 000000000..07da8a04b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2535 @@ -0,0 +1 @@ +Security patch of CVE-2024-4693 backport request diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2537 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2537 new file mode 100644 index 000000000..d8be7c068 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2537 @@ -0,0 +1 @@ +Hang in Cocoa_SetWindowSize() diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2539 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2539 new file mode 100644 index 000000000..823ca5581 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2539 @@ -0,0 +1 @@ +Crash in early_gtk_display_init() on macOS 14.6.1 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/254 b/gitlab/issues_text/target_missing/host_missing/accel_missing/254 new file mode 100644 index 000000000..f5f8661fd --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/254 @@ -0,0 +1 @@ +Windows 98 videocard passthrough - unable to load higher resolution -Desktop, after some games crashes, without whole physical machine reset.. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2541 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2541 new file mode 100644 index 000000000..dc2336b05 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2541 @@ -0,0 +1 @@ +virtio-9p qos-test failure: v9fs_req_recv: assertion failed (hdr.id == id): (7 == 73) FAIL diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2544 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2544 new file mode 100644 index 000000000..c5e397a8e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2544 @@ -0,0 +1 @@ +Bug: qemu not properly flushing error messages related to bad arguments diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2545 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2545 new file mode 100644 index 000000000..22fc087d2 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2545 @@ -0,0 +1,9 @@ +QEMU Version 9.0.0 - HAXM 7.8.0.0 - Error : qemu-system-x86_64.exe: -accel hax: invalid accelerator hax +Description of problem: + +Steps to reproduce: +1. +2. +3. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2548 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2548 new file mode 100644 index 000000000..e8f735442 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2548 @@ -0,0 +1,406 @@ +Assert failure in `usb_ep_get` : Assertion `pid == USB_TOKEN_IN || pid == USB_TOKEN_OUT` failed. +Description of problem: +Assert failure in `usb_ep_get` : Assertion `pid == USB_TOKEN_IN || pid == USB_TOKEN_OUT` failed. + +The TD PID needs to be either `USB_TOKEN_IN` or `USB_TOKEN_OUT` in `usb_ep_get`, but in the caller `uhci_handle_td` it may be `USB_TOKEN_SETUP`. + +An unprivileged guest user may be able to reach the assertion, I think this bug is quite akin to CVE-2024-3567 (https://gitlab.com/qemu-project/qemu/-/issues/2273) : + +Users are not directly able to craft URBs, however as a user, one might be able to find a kernel path that would send a TD with PID `USB_TOKEN_SETUP` to QEMU (which is called `USB_PID_SETUP` in Linux). +For instance in the Linux Kernel, `uhci_submit_control` in `drivers/usb/host/uhci-q.c:789` does link a `USB_PID_SETUP` TD to the URB. +Steps to reproduce: +Minimized reproducer: + +``` +cat << EOF | ./qemu/build2/qemu-system-x86_64 -machine q35 -nodefaults \ +-device \ +ich9-usb-ehci1,bus=pcie.0,addr=1d.7,multifunction=on,id=ich9-ehci-1 \ +-device ich9-usb-uhci1,bus=pcie.0,addr=1d.0,multifunction=on,masterbus=i\ +ch9-ehci-1.0,firstport=0 -device ich9-usb-uhci2,bus=pcie.0,addr=1d.1,mul\ +tifunction=on,masterbus=ich9-ehci-1.0,firstport=2 -device ich9-usb-uhci3\ +,bus=pcie.0,addr=1d.2,multifunction=on,masterbus=ich9-ehci-1.0,firstport\ +=4 -drive if=none,id=usbcdrom,media=cdrom -device \ +usb-tablet,bus=ich9-ehci-1.0,port=1,usb_version=1 -device \ +usb-storage,bus=ich9-ehci-1.0,port=2,drive=usbcdrom -qtest stdio +outl 0xcf8 0x8000e900 +inw 0xcfc +outl 0xcf8 0x8000e920 +outl 0xcfc 0xffffffff +outl 0xcf8 0x8000e920 +inl 0xcfc +outl 0xcf8 0x8000e920 +outl 0xcfc 0xc001 +outl 0xcf8 0x8000e904 +inw 0xcfc +outl 0xcf8 0x8000e904 +outw 0xcfc 0x7 +outl 0xcf8 0x8000e904 +inw 0xcfc +outl 0xcf8 0x8000ef00 +inw 0xcfc +outl 0xcf8 0x8000ef10 +outl 0xcfc 0xffffffff +outl 0xcf8 0x8000ef10 +inl 0xcfc +outl 0xcf8 0x8000ef10 +outl 0xcfc 0xe0000000 +outl 0xcf8 0x8000ef04 +inw 0xcfc +outl 0xcf8 0x8000ef04 +outw 0xcfc 0x7 +outl 0xcf8 0x8000ef04 +inw 0xcfc +outl 0xcf8 0x8000ea00 +inw 0xcfc +outl 0xcf8 0x8000ea20 +outl 0xcfc 0xffffffff +outl 0xcf8 0x8000ea20 +inl 0xcfc +outl 0xcf8 0x8000ea20 +outl 0xcfc 0xc021 +outl 0xcf8 0x8000ea04 +inw 0xcfc +outl 0xcf8 0x8000ea04 +outw 0xcfc 0x7 +outl 0xcf8 0x8000ea04 +inw 0xcfc +outl 0xcf8 0x8000e800 +inw 0xcfc +outl 0xcf8 0x8000e820 +outl 0xcfc 0xffffffff +outl 0xcf8 0x8000e820 +inl 0xcfc +outl 0xcf8 0x8000e820 +outl 0xcfc 0xc041 +outl 0xcf8 0x8000e804 +inw 0xcfc +outl 0xcf8 0x8000e804 +outw 0xcfc 0x7 +outl 0xcf8 0x8000e804 +inw 0xcfc +outl 0xcf8 0x8000fa00 +inw 0xcfc +outl 0xcf8 0x8000fa20 +outl 0xcfc 0xffffffff +outl 0xcf8 0x8000fa20 +inl 0xcfc +outl 0xcf8 0x8000fa20 +outl 0xcfc 0xc061 +outl 0xcf8 0x8000fa24 +outl 0xcfc 0xffffffff +outl 0xcf8 0x8000fa24 +inl 0xcfc +outl 0xcf8 0x8000fa24 +outl 0xcfc 0xe0001000 +outl 0xcf8 0x8000fa04 +inw 0xcfc +outl 0xcf8 0x8000fa04 +outw 0xcfc 0x7 +outl 0xcf8 0x8000fa04 +inw 0xcfc +outl 0xcf8 0x8000ea20 +outl 0xcfc 0x625f69a0 +outb 0xc040 0x46 +outb 0xc040 0x69 +inb 0xc000 +outb 0xc040 0x46 +clock_step +outb 0xc040 0x69 +clock_step +write 0x0 0x4 0x64657669 +write 0x69766560 0x8 0x000000ff6c46f228 +write 0x69766568 0x8 0x2d323334319c6c65 +write 0xff000000 0x8 0x000000ff6c6f6766 +write 0xff000008 0x8 0x8d6c65652d736400 +outb 0xc040 0x69 +outl 0xcf8 0x8000ef76 +outw 0xcfc 0x6563 +outb 0xc040 0x46 +clock_step +outb 0xc040 0x69 +inb 0xc000 +clock_step +write 0x4 0x4 0x64657669 +write 0x69766560 0x8 0x000000ff6c46f228 +write 0x69766568 0x8 0x2d323334319c6c65 +write 0xff000000 0x8 0x000000ff6c6f6766 +write 0xff000008 0x8 0x8d6c65652d736400 +outb 0xc040 0x69 +outw 0xc003 0x6769 +outb 0xc040 0x69 +readq 0xe0000074 +outb 0xc040 0x46 +clock_step +outb 0xc040 0x69 +clock_step +write 0x8 0x4 0x00000100 +write 0x10000 0x10 0x000000ff6c46f2282d00363939333336 +write 0xff000000 0x8 0x6465766963656d69 +write 0xff000008 0x8 0x740d00699b652d63 +write 0x69766560 0x8 0x000000ff6c46f228 +write 0x69766568 0x8 0x2d323334319c6c65 +clock_step +write 0xc 0x4 0x000000ff +write 0xff000000 0x8 0x0000010000000069 +write 0xff000008 0x8 0x636c395f61707269 +write 0x10000 0x10 0x000000ff6c46f2282d00363939333336 +outw 0xc003 0x6f00 +outb 0xc040 0x69 +outl 0xc053 0x6378616d +clock_step +write 0x10 0x4 0x000000ff +write 0xff000000 0x8 0x6465766963656d69 +write 0xff000008 0x8 0x740d00699b652d63 +write 0x69766560 0x8 0x000000ff6c46f228 +write 0x69766568 0x8 0x2d323334319c6c65 +outb 0xc051 0x6d +outb 0xc04f 0x61 +outb 0xc040 0x69 +clock_step +write 0x14 0x4 0x000000ff +write 0xff000000 0x8 0x0000010000000069 +write 0xff000008 0x8 0x636c395f61707269 +write 0x10000 0x10 0x000000ff6c46f2282d00363939333336 +EOF +``` + +# Additional information +The crash report triggered by the reproducer is: + +``` +[R +0.033173] outl 0xcf8 0x8000e900 +[S +0.033189] [R +0.033195] inw 0xcfc +[S +0.033205] [R +0.033212] outl 0xcf8 0x8000e920 +[S +0.033218] [R +0.033222] outl 0xcfc 0xffffffff +[S +0.033231] [R +0.033235] outl 0xcf8 0x8000e920 +[S +0.033241] [R +0.033245] inl 0xcfc +[S +0.033250] [R +0.033255] outl 0xcf8 0x8000e920 +[S +0.033261] [R +0.033265] outl 0xcfc 0xc001 +[S +0.033271] [R +0.033275] outl 0xcf8 0x8000e904 +[S +0.033281] [R +0.033285] inw 0xcfc +[S +0.033290] [R +0.033295] outl 0xcf8 0x8000e904 +[S +0.033300] [R +0.033306] outw 0xcfc 0x7 +[S +0.033755] [R +0.033767] outl 0xcf8 0x8000e904 +[S +0.033774] [R +0.033779] inw 0xcfc +[S +0.033785] [R +0.033792] outl 0xcf8 0x8000ef00 +[S +0.033798] [R +0.033802] inw 0xcfc +[S +0.033808] [R +0.033813] outl 0xcf8 0x8000ef10 +[S +0.033818] [R +0.033840] outl 0xcfc 0xffffffff +[S +0.033848] [R +0.033853] outl 0xcf8 0x8000ef10 +[S +0.033859] [R +0.033864] inl 0xcfc +[S +0.033870] [R +0.033875] outl 0xcf8 0x8000ef10 +[S +0.033880] [R +0.033884] outl 0xcfc 0xe0000000 +[S +0.033891] [R +0.033895] outl 0xcf8 0x8000ef04 +[S +0.033901] [R +0.033904] inw 0xcfc +[S +0.033909] [R +0.033916] outl 0xcf8 0x8000ef04 +[S +0.033922] [R +0.033926] outw 0xcfc 0x7 +[S +0.034381] [R +0.034389] outl 0xcf8 0x8000ef04 +[S +0.034395] [R +0.034399] inw 0xcfc +[S +0.034405] [R +0.034412] outl 0xcf8 0x8000ea00 +[S +0.034417] [R +0.034421] inw 0xcfc +[S +0.034427] [R +0.034431] outl 0xcf8 0x8000ea20 +[S +0.034437] [R +0.034441] outl 0xcfc 0xffffffff +[S +0.034448] [R +0.034452] outl 0xcf8 0x8000ea20 +[S +0.034457] [R +0.034463] inl 0xcfc +[S +0.034469] [R +0.034474] outl 0xcf8 0x8000ea20 +[S +0.034480] [R +0.034484] outl 0xcfc 0xc021 +[S +0.034490] [R +0.034494] outl 0xcf8 0x8000ea04 +[S +0.034500] [R +0.034504] inw 0xcfc +[S +0.034509] [R +0.034515] outl 0xcf8 0x8000ea04 +[S +0.034521] [R +0.034525] outw 0xcfc 0x7 +[S +0.034948] [R +0.034955] outl 0xcf8 0x8000ea04 +[S +0.034961] [R +0.034965] inw 0xcfc +[S +0.034971] [R +0.034989] outl 0xcf8 0x8000e800 +[S +0.034996] [R +0.035000] inw 0xcfc +[S +0.035005] [R +0.035010] outl 0xcf8 0x8000e820 +[S +0.035016] [R +0.035020] outl 0xcfc 0xffffffff +[S +0.035027] [R +0.035033] outl 0xcf8 0x8000e820 +[S +0.035039] [R +0.035043] inl 0xcfc +[S +0.035048] [R +0.035053] outl 0xcf8 0x8000e820 +[S +0.035059] [R +0.035065] outl 0xcfc 0xc041 +[S +0.035071] [R +0.035075] outl 0xcf8 0x8000e804 +[S +0.035081] [R +0.035084] inw 0xcfc +[S +0.035089] [R +0.035094] outl 0xcf8 0x8000e804 +[S +0.035100] [R +0.035103] outw 0xcfc 0x7 +[S +0.035525] [R +0.035532] outl 0xcf8 0x8000e804 +[S +0.035538] [R +0.035542] inw 0xcfc +[S +0.035548] [R +0.035553] outl 0xcf8 0x8000fa00 +[S +0.035558] [R +0.035562] inw 0xcfc +[S +0.035567] [R +0.035572] outl 0xcf8 0x8000fa20 +[S +0.035578] [R +0.035581] outl 0xcfc 0xffffffff +[S +0.035589] [R +0.035594] outl 0xcf8 0x8000fa20 +[S +0.035600] [R +0.035604] inl 0xcfc +[S +0.035609] [R +0.035613] outl 0xcf8 0x8000fa20 +[S +0.035618] [R +0.035623] outl 0xcfc 0xc061 +[S +0.035629] [R +0.035633] outl 0xcf8 0x8000fa24 +[S +0.035638] [R +0.035642] outl 0xcfc 0xffffffff +[S +0.035648] [R +0.035652] outl 0xcf8 0x8000fa24 +[S +0.035658] [R +0.035664] inl 0xcfc +[S +0.035669] [R +0.035673] outl 0xcf8 0x8000fa24 +[S +0.035679] [R +0.035683] outl 0xcfc 0xe0001000 +[S +0.035689] [R +0.035696] outl 0xcf8 0x8000fa04 +[S +0.035702] [R +0.035706] inw 0xcfc +[S +0.035711] [R +0.035716] outl 0xcf8 0x8000fa04 +[S +0.035722] [R +0.035725] outw 0xcfc 0x7 +[S +0.036402] [R +0.036412] outl 0xcf8 0x8000fa04 +[S +0.036418] [R +0.036422] inw 0xcfc +[S +0.036434] [R +0.036442] outl 0xcf8 0x8000ea20 +[S +0.036448] [R +0.036463] outl 0xcfc 0x625f69a0 +[S +0.036906] [I +0.036981] CLOSED +x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] outb 0xc040 0x46 +x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] outb 0xc040 0x69 +x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] inb 0xc000 +x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] outb 0xc040 0x46 +x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] clock_step +x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] outb 0xc040 0x69 +x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] clock_step +[DMA] x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] write 0x0 0x4 0x64657669 +[DMA] x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] write 0x69766560 0x8 0x000000ff6c46f228 +[DMA] x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] write 0x69766568 0x8 0x2d323334319c6c65 +[DMA] x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] write 0xff000000 0x8 0x000000ff6c6f6766 +[DMA] x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] write 0xff000008 0x8 0x8d6c65652d736400 +x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] outb 0xc040 0x69 +x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] outl 0xcf8 0x8000ef76 +x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] outw 0xcfc 0x6563 +x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] outb 0xc040 0x46 +x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] clock_step +x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] outb 0xc040 0x69 +x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] inb 0xc000 +x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] clock_step +[DMA] x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] write 0x4 0x4 0x64657669 +[DMA] x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] write 0x69766560 0x8 0x000000ff6c46f228 +[DMA] x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] write 0x69766568 0x8 0x2d323334319c6c65 +[DMA] x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] write 0xff000000 0x8 0x000000ff6c6f6766 +[DMA] x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] write 0xff000008 0x8 0x8d6c65652d736400 +x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] outb 0xc040 0x69 +x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] outw 0xc003 0x6769 +x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] outb 0xc040 0x69 +x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] readq 0xe0000074 +x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] outb 0xc040 0x46 +x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] clock_step +x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] outb 0xc040 0x69 +x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] clock_step +[DMA] x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] write 0x8 0x4 0x00000100 +[DMA] x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] write 0x10000 0x10 0x000000ff6c46f2282d00363939333336 +[DMA] x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] write 0xff000000 0x8 0x6465766963656d69 +[DMA] x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] write 0xff000008 0x8 0x740d00699b652d63 +[DMA] x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] write 0x69766560 0x8 0x000000ff6c46f228 +[DMA] x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] write 0x69766568 0x8 0x2d323334319c6c65 +x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] clock_step +[DMA] x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] write 0xc 0x4 0x000000ff +[DMA] x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] write 0xff000000 0x8 0x0000010000000069 +[DMA] x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] write 0xff000008 0x8 0x636c395f61707269 +[DMA] x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] write 0x10000 0x10 0x000000ff6c46f2282d00363939333336 +x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] outw 0xc003 0x6f00 +x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] outb 0xc040 0x69 +x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] outl 0xc053 0x6378616d +x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] clock_step +[DMA] x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] write 0x10 0x4 0x000000ff +[DMA] x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] write 0xff000000 0x8 0x6465766963656d69 +[DMA] x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] write 0xff000008 0x8 0x740d00699b652d63 +[DMA] x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] write 0x69766560 0x8 0x000000ff6c46f228 +[DMA] x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] write 0x69766568 0x8 0x2d323334319c6c65 +x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] outb 0xc051 0x6d +x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] outb 0xc04f 0x61 +x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] outb 0xc040 0x69 +x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] clock_step +[DMA] x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] write 0x14 0x4 0x000000ff +[DMA] x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] write 0xff000000 0x8 0x0000010000000069 +[DMA] x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] write 0xff000008 0x8 0x636c395f61707269 +[DMA] x86_64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed +[R +0.000000] write 0x10000 0x10 0x000000ff6c46f2282d00363939333336 +qemu-fuzz-x86_64: ../hw/usb/core.c:744: struct USBEndpoint *usb_ep_get(USBDevice *, int, int): Assertion `pid == USB_TOKEN_IN || pid == USB_TOKEN_OUT' failed. +==892641== ERROR: libFuzzer: deadly signal + #0 0x557dd985fc41 in __sanitizer_print_stack_trace (/home/hypervisor/qemu_fuzz/qemu/build2/qemu-fuzz-x86_64+0x20b2c41) (BuildId: 1208fb4c12f2da2381e7763dabbbdabaf2db65e5) + #1 0x557dd97cfa58 in fuzzer::PrintStackTrace() (/home/hypervisor/qemu_fuzz/qemu/build2/qemu-fuzz-x86_64+0x2022a58) (BuildId: 1208fb4c12f2da2381e7763dabbbdabaf2db65e5) + #2 0x557dd97b5ae3 in fuzzer::Fuzzer::CrashCallback() (/home/hypervisor/qemu_fuzz/qemu/build2/qemu-fuzz-x86_64+0x2008ae3) (BuildId: 1208fb4c12f2da2381e7763dabbbdabaf2db65e5) + #3 0x7fd7e623c45f (/lib/x86_64-linux-gnu/libc.so.6+0x3c45f) (BuildId: d320ce4e63925d698610ed423fc4b1f0e8ed51f1) + #4 0x7fd7e629152a in __pthread_kill_implementation nptl/pthread_kill.c:43:17 + #5 0x7fd7e629152a in __pthread_kill_internal nptl/pthread_kill.c:78:10 + #6 0x7fd7e629152a in pthread_kill nptl/pthread_kill.c:89:10 + #7 0x7fd7e623c3b5 in raise signal/../sysdeps/posix/raise.c:26:13 + #8 0x7fd7e622287b in abort stdlib/abort.c:79:7 + #9 0x7fd7e622279a in __assert_fail_base assert/assert.c:92:3 + #10 0x7fd7e6233b65 in __assert_fail assert/assert.c:101:3 + #11 0x557dda3b67c6 in usb_ep_get /home/hypervisor/qemu_fuzz/qemu/build2/../hw/usb/core.c:744:5 + #12 0x557dda3d8820 in uhci_handle_td /home/hypervisor/qemu_fuzz/qemu/build2/../hw/usb/hcd-uhci.c:819:14 + #13 0x557dda3d41ed in uhci_process_frame /home/hypervisor/qemu_fuzz/qemu/build2/../hw/usb/hcd-uhci.c:1022:15 + #14 0x557dda3cbf7e in uhci_frame_timer /home/hypervisor/qemu_fuzz/qemu/build2/../hw/usb/hcd-uhci.c:1121:9 + #15 0x557ddb90c0ff in timerlist_run_timers /home/hypervisor/qemu_fuzz/qemu/build2/../util/qemu-timer.c:576:9 + #16 0x557ddb90d3e8 in qemu_clock_run_timers /home/hypervisor/qemu_fuzz/qemu/build2/../util/qemu-timer.c:590:12 + #17 0x557ddb90d3e8 in qemu_clock_advance_virtual_time /home/hypervisor/qemu_fuzz/qemu/build2/../util/qemu-timer.c:696:9 + #18 0x557dda67fa2f in qtest_process_command /home/hypervisor/qemu_fuzz/qemu/build2/../system/qtest.c:722:9 + #19 0x557dda67b3bb in qtest_process_inbuf /home/hypervisor/qemu_fuzz/qemu/build2/../system/qtest.c:776:9 + #20 0x557dda67acf6 in qtest_server_inproc_recv /home/hypervisor/qemu_fuzz/qemu/build2/../system/qtest.c:907:9 + #21 0x557ddb5fa3e2 in qtest_sendf /home/hypervisor/qemu_fuzz/qemu/build2/../tests/qtest/libqtest.c:640:5 + #22 0x557ddb5fa4f4 in qtest_clock_step_next /home/hypervisor/qemu_fuzz/qemu/build2/../tests/qtest/libqtest.c:1009:5 + #23 0x557ddb67c2ef in generic_fuzz /home/hypervisor/qemu_fuzz/qemu/build2/../tests/qtest/fuzz/generic_fuzz.c:667:13 + #24 0x557ddb66e807 in LLVMFuzzerTestOneInput /home/hypervisor/qemu_fuzz/qemu/build2/../tests/qtest/fuzz/fuzz.c:158:5 + #25 0x557dd97b6f52 in fuzzer::Fuzzer::ExecuteCallback(unsigned char const*, unsigned long) (/home/hypervisor/qemu_fuzz/qemu/build2/qemu-fuzz-x86_64+0x2009f52) (BuildId: 1208fb4c12f2da2381e7763dabbbdabaf2db65e5) + #26 0x557dd97a1080 in fuzzer::RunOneTest(fuzzer::Fuzzer*, char const*, unsigned long) (/home/hypervisor/qemu_fuzz/qemu/build2/qemu-fuzz-x86_64+0x1ff4080) (BuildId: 1208fb4c12f2da2381e7763dabbbdabaf2db65e5) + #27 0x557dd97a6d07 in fuzzer::FuzzerDriver(int*, char***, int (*)(unsigned char const*, unsigned long)) (/home/hypervisor/qemu_fuzz/qemu/build2/qemu-fuzz-x86_64+0x1ff9d07) (BuildId: 1208fb4c12f2da2381e7763dabbbdabaf2db65e5) + #28 0x557dd97d0292 in main (/home/hypervisor/qemu_fuzz/qemu/build2/qemu-fuzz-x86_64+0x2023292) (BuildId: 1208fb4c12f2da2381e7763dabbbdabaf2db65e5) + #29 0x7fd7e6223a8f in __libc_start_call_main csu/../sysdeps/nptl/libc_start_call_main.h:58:16 + #30 0x7fd7e6223b48 in __libc_start_main csu/../csu/libc-start.c:360:3 + #31 0x557dd979b884 in _start (/home/hypervisor/qemu_fuzz/qemu/build2/qemu-fuzz-x86_64+0x1fee884) (BuildId: 1208fb4c12f2da2381e7763dabbbdabaf2db65e5) +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2550 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2550 new file mode 100644 index 000000000..e0925fdc2 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2550 @@ -0,0 +1,25 @@ +GICv3 vGIC system registers not initialized on ARM Cortex-A15 +Description of problem: +For Cortex-A15, the GICv3 vGIC registers are not initialized like for AArch64 CPUs, for example Cotex-A35, Cortex-A55, etc +Steps to reproduce: +The setup is not trivial. I can provide a boot image on request. But I hope the problem is straight-forward. +Additional information: +Suggested fix: +```diff +index 20c2737f17..136b513bda 100644 +--- a/target/arm/tcg/cpu32.c ++++ b/target/arm/tcg/cpu32.c +@@ -569,6 +569,12 @@ static void cortex_a15_initfn(Object *obj) + cpu->ccsidr[1] = 0x201fe00a; /* 32K L1 icache */ + cpu->ccsidr[2] = 0x711fe07a; /* 4096K L2 unified cache */ + cpu->isar.reset_pmcr_el0 = 0x410F3000; ++ ++ /* From B3.5 VGIC Type register */ ++ cpu->gic_num_lrs = 4; ++ cpu->gic_vpribits = 5; ++ cpu->gic_vprebits = 5; ++ + define_arm_cp_regs(cpu, cortexa15_cp_reginfo); + } + +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2552 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2552 new file mode 100644 index 000000000..41319fbde --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2552 @@ -0,0 +1,72 @@ +system libfdt said to be too old (1.5.1 min required) but 1.7.1 is installed. +Description of problem: +<-- +I am running an update build of the latest qemu version 9.0.2 to update it from 8.1.2 in the IPFire firewall distribution. +The build command being run was + +` +./configure \ + --prefix=/usr \ + --sysconfdir=/etc \ + --localstatedir=/var \ + --enable-kvm \ + --disable-attr \ + --target-list="$(TARGETS)" \ + --extra-cflags="$(CFLAGS)" \ + --enable-spice \ + --enable-usb-redir \ + --enable-seccomp \ + --disable-docs \ + --disable-sdl \ + --enable-slirp +` + +and where $TARGETS is + +` x86_64-linux-user \ + aarch64-linux-user \ + riscv64-linux-user \ + x86_64-softmmu \ + aarch64-softmmu \ + riscv64-softmmu +` + +and $CFLAGS is + +` "-O2" + "-g0" + "-pipe" + "-Wall" + "-fexceptions" + "-fPIC" + "-Wp,-U_FORTIFY_SOURCE" + "-Wp,-D_FORTIFY_SOURCE=3" + "-Wp,-D_GLIBCXX_ASSERTIONS" + "-fstack-protector-strong" + "-fstack-clash-protection" +` + +This built qemu successfully with version 8.1.2 and earlier versions. + +From version 9.0.1 onwards the subproject dtc has been removed from the Source Tarball and the build came back with the error message + +Library fdt found: NO + +../meson.build:3190:18: ERROR: Git command failed: ['/usr/bin/git', 'fetch', '--depth', '1', 'origin', 'b6910bec11614980a21e46fbccc35934b671bd81'] + +The git command failed as the distribution build is done with no network connection. All packages have to be available in the build and so the package cannot be downloaded during the build. + +Therefore I moved the dtc package in the IPFire build to before building qemu and added --disable-download to the ./configure options. + +The error message changed to + +Library fdt found: YES + +../meson.build:3182:7: ERROR: Problem encountered: system libfdt requested, but it is too old (1.5.1 or newer required) + +However the dtc libfdt version is 1.7.1 - definitely newer than 1.5.1 + +Why is the version being seen as too old? +How do I get this to detect the dtc libfdt version correctly (it has detected that libfdt is present in the IPFire build environment). + +--> diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2557 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2557 new file mode 100644 index 000000000..2ab9a20fe --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2557 @@ -0,0 +1 @@ +balloon size startup parameter needed diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2559 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2559 new file mode 100644 index 000000000..fbd96a413 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2559 @@ -0,0 +1,11 @@ +macOS cocoa UI cursor position mismatch when running Windows XP under QEMU 9.1.0 +Description of problem: +QEMU 9.1.0 got hardware cursor support on macOS with the cocoa UI. When running a Windows XP guest, the windows's own cursor got a 13 pixel offset both in X and Y direction. When the "show-cursor" is off, the problem still exists, so the click target is not under the pointer of the cursor. I was using the "Red Hat QXL GPU" driver v6.1.0.10024 which was built in 2015. + +I also checked it with Linux (i have an x86-64 Alma Linux 8 installation too), this working fine when using the "-display cocoa,show-cursoor=off,zoom-to-fit=off -device virtio-vga" parameters. +Steps to reproduce: +1. Load a Windows XP with QXL drivers installed +Additional information: + + + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/256 b/gitlab/issues_text/target_missing/host_missing/accel_missing/256 new file mode 100644 index 000000000..f8d712b99 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/256 @@ -0,0 +1 @@ +`make install` fails on documentation when using Sphinx 4 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2561 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2561 new file mode 100644 index 000000000..a351b5ca3 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2561 @@ -0,0 +1,39 @@ +Sound doesnt work on debian guest + debian host using Pipewire +Description of problem: +There is no sound on Debian Stable VM. Im using SPICE for audio redirection. +Steps to reproduce: +1. Download debian stable ISO (12 atm) +2. Install it on your KVM +3. Make sure your host and your guest are using pipewire (check https://wiki.debian.org/PipeWire#Installation) +4. No sound is transmitted to the host. +Additional information: +- I have tried switching SPICE to something else like ALSA, but it will result in hanging of the video page similar to this video: + +https://github.com/QubesOS/qubes-issues/issues/1698#issuecomment-1031376517 + +- Tried to use direct pipewire, but resulted into error: + +``` +Error starting domain: internal error: process exited while connecting to monitor: 2024-09-04T18:13:40.241754Z qemu-system-x86_64: Unknown audio driver pipewire'. Perhaps you want to install qemu-system-gui package? + +Traceback (most recent call last): + File "/usr/share/virt-manager/virtManager/asyncjob.py", line 72, in cb_wrapper + callback(asyncjob, *args, **kwargs) + File "/usr/share/virt-manager/virtManager/asyncjob.py", line 108, in tmpcb + callback(*args, **kwargs) + File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 57, in newfn + ret = fn(self, *args, **kwargs) + ^^^^^^^^^^^^^^^^^^^^^^^^^ + File "/usr/share/virt-manager/virtManager/object/domain.py", line 1402, in startup + self._backend.create() + File "/usr/lib/python3/dist-packages/libvirt.py", line 1379, in create + raise libvirtError('virDomainCreate() failed') +libvirt.libvirtError: internal error: process exited while connecting to monitor: 2024-09-04T18:13:40.241754Z qemu-system-x86_64: Unknown audio driver pipewire'. Perhaps you want to install qemu-system-gui package? +``` + +Yes i have installed "qemu-system-gui" but still got the same message. + + +Debian XML with SPICE: + +[Debian-XML.txt](/uploads/66e09b37f672b49f8f0a0a01d3c6a6b2/Debian-XML.txt) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2563 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2563 new file mode 100644 index 000000000..dfcacf9e6 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2563 @@ -0,0 +1,210 @@ +W64 build referenced to by https://www.qemu.org/download/#windows fails to run with GTK and 3D but cross-build for W64 works ok with GTK and 3d +Description of problem: +Qemu W64 build referenced to by https://www.qemu.org/download/#windows (https://qemu.weilnetz.de/w64/qemu-w64-setup-20240903.exe) crashes with aforementioned command line, leaving 0xc0000005 exception in Windows event log. But a custom cross-compiled build at least boots into default qemu BIOS. See steps below to cross-compile qemu with GTK + OpenGL +VirGL support. +Steps to reproduce: +1. `wget https://qemu.weilnetz.de/w64/qemu-w64-setup-20240903.exe`, install it, run `qemu-system-x86_64.exe -display gtk,gl=on -device virtio-vga-gl` and watch immediate qemu crash. + 2. Prepare cross-compilation build of qemu 9.1.0 using following steps: + 3. Download official Fedora workstation 40 x86_64 ISO and install it to a virtual disk and boot that disk. + 4. `wget https://download.qemu.org/qemu-9.1.0.tar.xz`\ + `tar xvJf qemu-9.1.0.tar.xz`\ + `cd qemu-9.1.0` + 5. Run `sudo yum install git meson ninja-build python3-sphinx python3-sphinx_rtd_theme gcc mingw64-gcc mingw64-glib2 mingw64-pkg-config mingw64-pixman mingw64-gtk3 mingw64-SDL2 mingw64-libepoxy mingw64-librsvg2` in virtual Fedora. `mingw64-librsvg2` is optional, see step #14 + 6. `git clone https://gitlab.freedesktop.org/slirp/libslirp.git` (e61dbd45 as of 04 August 2024) `git clone https://gitlab.freedesktop.org/virgl/virglrenderer.git` (3d82ed86 as of 03 September 2024) + 7. create file x86_64-w64-mingw32.txt in qemu-9.1.0 directory with the content as follows:\ + `[binaries]`\ + `c = '/usr/bin/x86_64-w64-mingw32-gcc'`\ + `cpp = '/usr/bin/x86_64-w64-mingw32-g++'`\ + `ar = '/usr/bin/x86_64-w64-mingw32-ar'`\ + `strip = '/usr/bin/x86_64-w64-mingw32-strip'`\ + `pkg-config = '/usr/bin/x86_64-w64-mingw32-pkg-config'`\ + `exe_wrapper = 'wine'`\ + \ + `[host_machine]`\ + `system = 'windows'`\ + `cpu_family = 'x86_64'`\ + `cpu = 'i686'`\ + `endian = 'little'` + 8. Make a directory to which QEMU dependencies will be installed after compilation from git: `export CROSS_QEMU_DEPS="/home/cross-qemu-deps"`\ + `sudo mkdir -p $CROSS_QEMU_DEPS` + 9. Install libslirp so that future qemu binaries can have internet access via -netdev user\ + ` cd libslirp`\ + \ + ` meson setup --cross-file ../x86_64-w64-mingw32.txt --prefix "$CROSS_QEMU_DEPS" build-mingw/`\ + ` meson compile -C build-mingw`\ + ` cd build-mingw`\ + ` ninja install` +10. Install virgl to have 3D hardware acceleration\ + ` cd ../../`\ + ` cd virglrenderer`\ + \ + ` meson setup --cross-file ../x86_64-w64-mingw32.txt --prefix "$CROSS_QEMU_DEPS" build-mingw/`\ + ` meson compile -C build-mingw`\ + ` cd build-mingw`\ + ` ninja install` +11. Set three environment variables for cross-compilation: + + `sudo find / -type f -name '*.pc'` and make sure all mingw \*.pc files live in `/usr/x86_64-w64-mingw32/sys-root/mingw/share/pkgconfig/` and `/usr/x86_64-w64-mingw32/sys-root/mingw/lib/pkgconfig/`. Correct these paths in PKG_CONFIG_PATH if you see they were altered by mingw or package contributors.\ + \ + `export PKG_CONFIG_PATH="/usr/x86_64-w64-mingw32/sys-root/mingw/share/pkgconfig/:/usr/x86_64-w64-mingw32/sys-root/mingw/lib/pkgconfig/:$PKG_CONFIG_PATH"` + + \ + `export PKG_CONFIG_LIBDIR="${CROSS_QEMU_DEPS}/lib/pkgconfig/:$PKG_CONFIG_LIBDIR"` + + \ + `export PKG_CONFIG_SYSROOT_DIR=""` +12. <span dir="">Configure Qemu makefile:</span> + + `cd ../../` + + `./configure --cross-prefix=x86_64-w64-mingw32- --enable-gtk --enable-sdl --enable-opengl --enable-virglrenderer --enable-slirp --enable-debug` + + and make sure you see this in the output of configure: + + `Compilation`\ + `host CPU : x86_64`\ + `host endianness : little`\ + `C compiler : x86_64-w64-mingw32-gcc -m64`\ + `Host C compiler : cc` + + and this one: + + `Checking whether type "struct virgl_renderer_resource_info_ext" has member "d3d_tex2d" with dependency virglrenderer: YES` +13. Cross-compile qemu: `` make -j`nproc` `` +14. \[optional step to get rid of "**Gtk-WARNING \*\*: 19:22:02.461: Could not load a pixbuf**"\] + + **Copy gdk-pixbuf-query-loaders.exe** from `/usr/x86_64-w64-mingw32/sys-root/mingw/bin/`\ + to\ + `./qemu-9.1.0/build/qemu-bundle/qemu`**\ + \ + `mkdir -p ./qemu-9.1.0/build/qemu-bundle/qemu/lib`\ + \ + copy recursively /usr/x86_64-w64-mingw32/sys-root/mingw/lib/gdk-pixbuf-2.0** to `./qemu-9.1.0/build/qemu-bundle/qemu/lib` + + **`mkdir -p ./qemu-9.1.0/build/qemu-bundle/qemu/share`**\ + \ + **copy recursively /usr/x86_64-w64-mingw32/sys-root/mingw/share/icons** to `./qemu-9.1.0/build/qemu-bundle/qemu/share` + + **copy recursively /usr/x86_64-w64-mingw32/sys-root/mingw/share/themes** to `./qemu-9.1.0/build/qemu-bundle/qemu/share` + + Run `gdk-pixbuf-query-loaders.exe --update-cache` on host right before step 17. +15. Copy all dll files from + + `/usr/x86_64-w64-mingw32/sys-root/mingw/bin/`\ + to\ + `./qemu-9.1.0/build/qemu-bundle/`**`qemu`** + + Copy libvirglrenderer-1.dll and libslirp-0.dll from `$CROSS_QEMU_DEPS` directory exported above to + + `./qemu-9.1.0/build/qemu-bundle/`**`qemu`** +16. Copy this **`qemu`** folder from the previous step to Windows machine using ssh or whatever else\ + E.g. by doing\ + ` sudo yum install openssh-server`\ + ` sudo systemctl start sshd`\ + ` sudo systemctl status sshd`\ + on guest OS (provided you have launched guest Fedora qemu with `-nic user,hostfwd=tcp::8888-:22` command line parameter for ssh) + + and then + + `scp.exe -P 8888 -r virtual_machine_user@127.0.0.1:/home/virtual_machine_user/qemu-9.1.0/build/qemu-bundle/qemu C:\downloads\qemu`\ + on host OS +17. `cd` to that `qemu` folder and run `qemu-system-x86_64.exe -display gtk,gl=on -device virtio-vga-gl` and watch qemu booting into BIOS. + +<details> +<summary>Previous version</summary> + +1\. \`wget https://qemu.weilnetz.de/w64/qemu-w64-setup-20240903.exe\\\\\\\\\\\\\\\`, install it, run \`qemu-system-x86_64.exe -display gtk,gl=on -device virtio-vga-gl\` and watch immediate qemu crash. 2. Prepare cross-compilation build of qemu 9.1.0 using following steps: 3. Download official Fedora workstation 40 x86_64 ISO and install it to a virtual disk and boot that disk. 4. Run \`sudo yum install meson ninja-build python3-sphinx python3-sphinx_rtd_theme gcc mingw64-gcc mingw64-glib2 mingw64-pkg-config mingw64-pixman mingw64-gtk3 mingw64-SDL2 mingw64-libepoxy\` in virtual Fedora. 5. \`wget https://download.qemu.org/qemu-9.1.0.tar.xz\\\\\\\\\\\\\\\\\\\\\\\` + +``` +`tar xvJf qemu-9.1.0.tar.xz`\ +`cd qemu-9.1.0` +``` + + 6. `git clone https://gitlab.freedesktop.org/virgl/virglrenderer.git` (3d82ed86 as of 03 September 2024)\ + `cd virglrenderer` + 7. create file x86_64-w64-mingw32.txt in virglrenderer directory with the content as follows:\ + `[binaries]`\ + `c = '/usr/bin/x86_64-w64-mingw32-gcc'`\ + `cpp = '/usr/bin/x86_64-w64-mingw32-g++'`\ + `ar = '/usr/bin/x86_64-w64-mingw32-ar'`\ + `strip = '/usr/bin/x86_64-w64-mingw32-strip'`\ + `pkg-config = '/usr/bin/x86_64-w64-mingw32-pkg-config'`\ + `exe_wrapper = 'wine'`\ + \ + `[host_machine]`\ + `system = 'windows'`\ + `cpu_family = 'x86_64'`\ + `cpu = 'i686'`\ + `endian = 'little'` + 8. Run `meson setup --cross-file x86_64-w64-mingw32.txt build-mingw`\ + `meson compile -C build-mingw`\ + `cd build-mingw`\ + `ninja install` + 9. Set pkgconfig for virglrenderer: `export PKG_CONFIG_PATH=$PKG_CONFIG_PATH:/home/your_user/virglrenderer/build-mingw/meson-private`\ + (replace /home/your_user/virglrenderer/build-mingw/meson-private with path containing virglrenderer.pc file from output of `sudo find / -type f -name 'virglrenderer.pc'` command) +10. Run confugure: \ + `cd ../../`\ + `./configure --cross-prefix=x86_64-w64-mingw32- --enable-gtk --enable-sdl --enable-opengl --enable-virglrenderer --enable-debug`\ + \ + and make sure you see this in the output of configure:\ + `Compilation`\ + `host CPU : x86_64`\ + `host endianness : little`\ + `C compiler : x86_64-w64-mingw32-gcc -m64`\ + `Host C compiler : cc`\ + \ + run\ + `export PKG_CONFIG_PATH="/usr/local/lib/pkgconfig"` +11. Run this command to see where x86_64-w64-mingw32-pkg-config will look for virglrenderer.h: + + `/usr/bin/x86_64-w64-mingw32-pkg-config --cflags virglrenderer`\ + \> -I/usr/x86_64-w64-mingw32/sys-root/mingw/usr/local/include/virgl (possible result) +12. Copy folder containing virglrenderer.h to that one to satisfy mingw expectations: + + `sudo mkdir -p /usr/x86_64-w64-mingw32/sys-root/mingw/usr/local/include/`\ + `sudo cp -r /usr/local/include/virgl /usr/x86_64-w64-mingw32/sys-root/mingw/usr/local/include/` +13. Run search `sudo find / -type f -name 'libvirglrenderer.dll.a'` and satisfy mingw's expectation for libvirglrenderer.dll.a:\ + `sudo mkdir -p /usr/x86_64-w64-mingw32/sys-root/usr/local/lib/`\ + `sudo ln -s /usr/local/lib/libvirglrenderer.dll.a /usr/x86_64-w64-mingw32/sys-root/usr/local/lib/libvirglrenderer.dll.a` +14. Cross-compile qemu: \ + `make -j4`\ + \* if you see "/usr/lib/gcc/x86_64-w64-mingw32/14.1.1/../../../../x86_64-w64-mingw32/bin/ld: cannot find -lvirglrenderer: No such file or directory" then most likely Qemu's makefile was confused by libvirglrenderer.dll.a path; check `/usr/x86_64-w64-mingw32/bin/ld -lvirglrenderer --verbose` output to find out path of libvirglrenderer.dll.a file it cannot find +15. copy all dll files from \ + /usr/x86_64-w64-mingw32/sys-root/mingw/bin/\ + to\ + ./qemu-9.1.0-rc4/**build** +16. copy libvirglrenderer-1.dll from /usr/local/bin to\ + ./qemu-9.1.0-rc4/**build** +17. copy this **build** folder to Windows machine using ssh or whatever else +18. `cd` to that **build** folder and run `qemu-system-x86_64.exe -display gtk,gl=on -device virtio-vga-gl` and watch qemu booting into BIOS. + +</details> +Additional information: +P.S. Cross-compilation on Fedora build machine for Windows target usually requires installing pre-compiled binary packages along with libslirp and libvirglrenderer from git. Almost all of them include \*.pc files (pkg-config files) needed by mingw to find .h headers and .dll.a library files. Normally, it's not necessarry to add extra include paths using something like CFLAGS="-I/include_headers_path" or LDFLAGS="-L/path_to_dll_a_lib". The commands from above must produce a fully working windows build. But, just in case someone damages packages in Fedora repository or libslirp or virglrenderer in their git, here are some ideas how to fix broken links between files: + +- First, make sure you have enumerated all .pc folders from Fedora repository packages in PKG_CONFIG_PATH= and all .pc folders built from source in PKG_CONFIG_LIBDIR=, as it was shown at Step 11. If you see a message saying something like "virglrenderer.h not found", run this command to see where x86_64-w64-mingw32-pkg-config will look for virglrenderer.h: `/usr/bin/x86_64-w64-mingw32-pkg-config --cflags virglrenderer` + +> \-I/usr/x86_64-w64-mingw32/sys-root/mingw/usr/local/include/virgl (possible result) + +- Then copy folder containing virglrenderer.h (for example, /usr/local/include/virgl) to that one to satisfy mingw expectations: + + `sudo mkdir -p /usr/x86_64-w64-mingw32/sys-root/mingw/usr/local/include/` `sudo cp -r /usr/local/include/virgl /usr/x86_64-w64-mingw32/sys-root/mingw/usr/local/include/` +- If you see "/usr/lib/gcc/x86_64-w64-mingw32/14.1.1/../../../../x86_64-w64-mingw32/bin/ld: cannot find -lvirglrenderer: No such file or directory" then most likely Qemu's makefile was confused by libvirglrenderer.dll.a path; check `/usr/x86_64-w64-mingw32/bin/ld -lvirglrenderer --verbose` output to find out path of libvirglrenderer.dll.a file it cannot find +- For example, `/usr/x86_64-w64-mingw32/bin/ld -lvirglrenderer --verbose` shows that build script tries to find .dll.a file under /usr/x86_64-w64-mingw32/sys-root/usr/local/lib/libvirglrenderer.dll.a and `find / -type f -name 'libvirglrenderer.dll.a'` shows that file is in /usr/local/lib/libvirglrenderer.dll.a +- Then satisfy mingw's expectation for libvirglrenderer.dll.a: `sudo mkdir -p /usr/x86_64-w64-mingw32/sys-root/usr/local/lib/`\ + `sudo ln -s /usr/local/lib/libvirglrenderer.dll.a /usr/x86_64-w64-mingw32/sys-root/usr/local/lib/libvirglrenderer.dll.a` + +Upd: I was able to refine instructions on how to cross-compile Qemu's dependencies thanks to these references: + +https://gitlab.freedesktop.org/pkg-config/pkg-config/-/issues/52: + +> PKG_CONFIG_SYSROOT_DIR blindly prepend the sysroot to all paths. I made a MR that add PKG_CONFIG_SYSROOT_MAP to get smarter mapping from pcfiledir-\>sysroot. !7. I generally discontinued the use of PKG_CONFIG_SYSROOT_DIR and switched to merely using PKG_CONFIG_LIBDIR. That way I got absolute paths everyehere which at least was consistent and could be postprocessed if needed. + +https://forum.qt.io/topic/88946/qt5-10-1-cross-compile-configure-errors/9: + +> WARNING: Disabling pkg-config since PKG_CONFIG_LIBDIR is not set and the host's .pc files would be used (even if you set PKG_CONFIG_PATH). Set this variable to the directory that contains target .pc files for pkg-config to function correctly when cross-compiling or use -pkg-config to override this test. + +https://cmake.org/pipermail/cmake/2008-November/025050.html: + +> The situation is as follows: PKG_CONFIG_PATH is searched before PKG_CONFIG_LIBDIR for the desired \*.pc file. (The man page doesn't say which is searched first, but my tests reveal that is the order at least for the present version of pkg-config.) Cross-compiling users should avoid using native paths in PKG_CONFIG_PATH and PKG_CONFIG_LIBDIR. Furthermore, cross-compiling users should always specify PKG_CONFIG_LIBDIR (with or without PKG_CONFIG_PATH) since use of PKG_CONFIG_LIBDIR supresses appending default native paths to whatever is specified in PKG_CONFIG_PATH and PKG_CONFIG_LIBDIR. +> +> In sum, for cross-compilation purposes you should always use PKG_CONFIG_LIBDIR (with or without PKG_CONFIG_PATH) and make sure there are no native paths in it (or in PKG_CONFIG_PATH). If you follow those rules you should get a good cross-compilation result, otherwise not. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2564 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2564 new file mode 100644 index 000000000..4ce6bd274 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2564 @@ -0,0 +1 @@ +ubuntu-22.04-s390x-all-system CI job often times out diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2565 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2565 new file mode 100644 index 000000000..ee223209a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2565 @@ -0,0 +1,13 @@ +Bisected: 176e3783f2ab14 results in a heavy performance regression with the SDL interface +Description of problem: +With the patch 176e3783f2ab14 a significant 3D performance regression was introduced when using the SDL gui and VirGL. Before the patch glxgears runs at about 4000 FPS on my machine, with the patch this drops to about 150 FPS, and if one moves the mouse the reported frame rate drops even more. +Steps to reproduce: +1. Run the qemu like given above with a current Debian-SID guest +2. Start glxgears from a terminal +3. Move the mouse continuously to see the extra drop in frame rate +Additional information: +* (Guest) OpenGL Renderer string: virgl (AMD Radeon RX 6700 XT (radeonsi, navi22, LLVM 18.1.8 ...) +* Reverting the commit 176e3783f2ab14 fixes the problem on SDL +* I don't think the host kernel version is an issue here (namely the KVM patches that are required to run Venus on discrete graphics cards) +* I've seen a similar issue when using GTK, but other that with SDL it's already present in version 7.2.11 (the one I used as a "good" base when I was bisecting the regression) - so I was not able to bisect yet. +* I've looked around in the code and I'm aware the that commit *shouldn't* have the impact it seems to have. I can only assume that there is some unexpected side effect when creating the otherwise unused renderer. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2566 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2566 new file mode 100644 index 000000000..d46bdc6af --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2566 @@ -0,0 +1,119 @@ +Plugin deadlock with qemu_plugin_register_vcpu_mem_cb introduced prior to v8.1.0 +Description of problem: +Between v8.0.5 and v8.1.0 a bug was introduced where a TCG plugin calling `qemu_plugin_register_vcpu_mem_cb` can cause a deadlock. This bug is still present in the current head of master (a66f28df650166ae8b50c992eea45e7b247f4143). + +I was able to reproduce this reliably (>95% of the time) testing with the minimal plugin shown below. In more limited testing, I found the logic in the (in-tree) hotpages plugin will also trigger this deadlock. + +I tested with the Ubuntu Bionic qcow from [here](https://panda.re/qcows/linux/ubuntu/1804/x86_64/bionic-server-cloudimg-amd64-noaslr-nokaslr.qcow2), but don't think there's anything particularly special about this qcow. + + +A minimal plugin to trigger the deadlock is as follows. To build the plugin, you'll need to add a `NAMES += customtest` line into `contrib/plugins/Makefile. + +contrib/plugins/customtest.c: +``` +#include <qemu-plugin.h> + +QEMU_PLUGIN_EXPORT int qemu_plugin_version = QEMU_PLUGIN_VERSION; + +static void vcpu_mem(unsigned int cpu_index, qemu_plugin_meminfo_t info, + uint64_t vaddr, void *udata) +{} + + +static void vcpu_tb_trans(qemu_plugin_id_t id, struct qemu_plugin_tb *tb) +{ + struct qemu_plugin_insn *insn; + size_t n = qemu_plugin_tb_n_insns(tb); + + for (size_t i = 0; i < n; i++) { + insn = qemu_plugin_tb_get_insn(tb, i); + + /* Register callback on memory read or write */ + qemu_plugin_register_vcpu_mem_cb(insn, vcpu_mem, + QEMU_PLUGIN_CB_NO_REGS, + QEMU_PLUGIN_MEM_R, NULL); + } +} + +QEMU_PLUGIN_EXPORT int qemu_plugin_install(qemu_plugin_id_t id, + const qemu_info_t *info, int argc, + char **argv) +{ + qemu_plugin_register_vcpu_tb_trans_cb(id, vcpu_tb_trans); + + return 0; +} +``` +Steps to reproduce: +1. From the current head of `master` (a66f28df650166ae8b50c992eea45e7b247f4143) +2. Add the above plugin to the contrib/plugins directory and update the `contrib/plugins/Makefile` with `NAMES += customtest` so it will be built. +3. `../configure --enable-plugins --target-list=x86_64-softmmu` +4. `make && make plugins` +5. `wget https://panda.re/qcows/linux/ubuntu/1804/x86_64/bionic-server-cloudimg-amd64-noaslr-nokaslr.qcow2` +6. Launch the guest with `./qemu-system-x86_64 -m 1G -plugin contrib/plugins/libcustomtest.so bionic-server-cloudimg-amd64-noaslr-nokaslr.qcow2 -nographic -d plugin`, and wait a moment. There will be no output after the initial "Booting from Hard Disk" mesasge. Switch to the monitor with `ctrl+a c` type `quit` and press enter, qemu fails to exit because of the deadlock. +Additional information: +* I tested and saw the bug on the following commits/tags: current head of master (a66f28df650166ae8b50c992eea45e7b247f4143), v9.1.0, v9.0.0, and v8.2.6, v8.1.0. +* I tested and saw no bug on the following tags: v8.0.5, v8.0.4, v8.0.0 +* If `qemu_plugin_register_vcpu_mem_cb` is called with a fourth argument of `0` instead of `QEMU_PLUGIN_MEM_R`, the guest did not hang (at least on the current head of master). +* The monitor can still be reached with `ctrl+a c` after the deadlock, but running the `quit` command does not terminate the emulator (I don't think this is related to #1195 since things start hanging before the shutdown begins) + +Gdb shows the following backtraces (from the head of master) across the running threads. It seems that thread 3 and thread 2 are stuck, though I'm not too familiar with what they're doing. +``` +(gdb) thread apply all bt + +Thread 3 (Thread 0x7f9677fff640 (LWP 754761) "qemu-system-x86"): +#0 __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x55a9c1047748 <exclusive_cond+40>) at ./nptl/futex-internal.c:57 +#1 __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x0, clockid=0, expected=0, futex_word=0x55a9c1047748 <exclusive_cond+40>) at ./nptl/futex-internal.c:87 +#2 __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x55a9c1047748 <exclusive_cond+40>, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at ./nptl/futex-internal.c:139 +#3 0x00007f968280aa41 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55a9c1047660 <qemu_cpu_list_lock>, cond=0x55a9c1047720 <exclusive_cond>) at ./nptl/pthread_cond_wait.c:503 +#4 ___pthread_cond_wait (cond=cond@entry=0x55a9c1047720 <exclusive_cond>, mutex=mutex@entry=0x55a9c1047660 <qemu_cpu_list_lock>) at ./nptl/pthread_cond_wait.c:627 +#5 0x000055a9bff8ce9f in qemu_cond_wait_impl (cond=0x55a9c1047720 <exclusive_cond>, mutex=0x55a9c1047660 <qemu_cpu_list_lock>, file=0x55a9bffc37b6 "../cpu-common.c", line=221) at ../util/qemu-thread-posix.c:225 +#6 0x000055a9bf8fc7b7 in start_exclusive () at ../cpu-common.c:221 +#7 start_exclusive () at ../cpu-common.c:192 +#8 0x000055a9bfc2f981 in ptw_setl_slow (new=23069091, old=23069059, in=0x7f9677ffa540) at ../target/i386/tcg/sysemu/excp_helper.c:112 +#9 ptw_setl (set=<optimized out>, old=23069059, in=0x7f9677ffa540) at ../target/i386/tcg/sysemu/excp_helper.c:130 +#10 ptw_setl (set=<optimized out>, old=23069059, in=0x7f9677ffa540) at ../target/i386/tcg/sysemu/excp_helper.c:121 +#11 mmu_translate (env=env@entry=0x55a9c2ab3bc0, in=in@entry=0x7f9677ffa5f0, out=out@entry=0x7f9677ffa5c0, err=err@entry=0x7f9677ffa5d0, ra=ra@entry=140283034940586) at ../target/i386/tcg/sysemu/excp_helper.c:412 +#12 0x000055a9bfc2fe4f in get_physical_address (ra=<optimized out>, err=<optimized out>, out=<optimized out>, mmu_idx=<optimized out>, access_type=<optimized out>, addr=25041848, env=<optimized out>) at ../target/i386/tcg/sysemu/excp_helper.c:583 +#13 x86_cpu_tlb_fill (cs=0x55a9c2ab1400, addr=25041848, size=<optimized out>, access_type=MMU_DATA_LOAD, mmu_idx=5, probe=<optimized out>, retaddr=140283034940586) at ../target/i386/tcg/sysemu/excp_helper.c:603 +#14 0x000055a9bfd92a59 in tlb_fill (retaddr=140283034940586, mmu_idx=5, access_type=MMU_DATA_LOAD, size=<optimized out>, addr=25041848, cpu=0x55a9c2ab1450) at ../accel/tcg/cputlb.c:1237 +#15 mmu_lookup1 (cpu=cpu@entry=0x55a9c2ab1400, data=data@entry=0x7f9677ffa750, mmu_idx=5, access_type=access_type@entry=MMU_DATA_LOAD, ra=ra@entry=140283034940586) at ../accel/tcg/cputlb.c:1634 +#16 0x000055a9bfd92b71 in mmu_lookup (cpu=cpu@entry=0x55a9c2ab1400, addr=addr@entry=25041848, oi=oi@entry=37, ra=ra@entry=140283034940586, type=type@entry=MMU_DATA_LOAD, l=l@entry=0x7f9677ffa750) at ../accel/tcg/cputlb.c:1724 +#17 0x000055a9bfd937b0 in do_ld4_mmu (cpu=cpu@entry=0x55a9c2ab1400, addr=addr@entry=25041848, oi=oi@entry=37, ra=140283034940586, ra@entry=37, access_type=access_type@entry=MMU_DATA_LOAD) at ../accel/tcg/cputlb.c:2356 +#18 0x000055a9bfd96afa in cpu_ldl_mmu (ra=37, oi=37, addr=25041848, env=0x55a9c2ab3bc0) at ../accel/tcg/ldst_common.c.inc:160 +#19 cpu_ldl_le_mmuidx_ra (env=env@entry=0x55a9c2ab3bc0, addr=25041848, mmu_idx=mmu_idx@entry=5, ra=ra@entry=140283034940586) at ../accel/tcg/ldst_common.c.inc:298 +#20 0x000055a9bfc9a639 in popl (sa=<synthetic pointer>) at ../target/i386/tcg/seg_helper.c:88 +#21 helper_ret_protected (env=0x55a9c2ab3bc0, shift=1, is_iret=0, addend=0, retaddr=140283034940586) at ../target/i386/tcg/seg_helper.c:2031 +#22 0x00007f96307734aa in code_gen_buffer () +#23 0x000055a9bfd855f6 in cpu_tb_exec (cpu=cpu@entry=0x55a9c2ab1400, itb=itb@entry=0x7f96307733c0 <code_gen_buffer+7811987>, tb_exit=tb_exit@entry=0x7f9677ffadd8) at ../accel/tcg/cpu-exec.c:458 +#24 0x000055a9bfd85b4c in cpu_loop_exec_tb (tb_exit=0x7f9677ffadd8, last_tb=<synthetic pointer>, pc=<optimized out>, tb=0x7f96307733c0 <code_gen_buffer+7811987>, cpu=0x55a9c2ab1400) at ../accel/tcg/cpu-exec.c:908 +#25 cpu_exec_loop (cpu=cpu@entry=0x55a9c2ab1400, sc=sc@entry=0x7f9677ffae70) at ../accel/tcg/cpu-exec.c:1022 +#26 0x000055a9bfd86351 in cpu_exec_setjmp (cpu=cpu@entry=0x55a9c2ab1400, sc=sc@entry=0x7f9677ffae70) at ../accel/tcg/cpu-exec.c:1039 +#27 0x000055a9bfd86b0e in cpu_exec (cpu=cpu@entry=0x55a9c2ab1400) at ../accel/tcg/cpu-exec.c:1065 +#28 0x000055a9bfdaafa4 in tcg_cpu_exec (cpu=cpu@entry=0x55a9c2ab1400) at ../accel/tcg/tcg-accel-ops.c:78 +#29 0x000055a9bfdab0ff in mttcg_cpu_thread_fn (arg=arg@entry=0x55a9c2ab1400) at ../accel/tcg/tcg-accel-ops-mttcg.c:95 +#30 0x000055a9bff8c2d1 in qemu_thread_start (args=<optimized out>) at ../util/qemu-thread-posix.c:541 +#31 0x00007f968280bac3 in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:442 +#32 0x00007f968289d850 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 + +Thread 2 (Thread 0x7f967d990640 (LWP 754759) "qemu-system-x86"): +#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 +#1 0x000055a9bff8d5b2 in qemu_futex_wait (val=<optimized out>, f=<optimized out>) at /home/user/git/qemu/include/qemu/futex.h:29 +#2 qemu_event_wait (ev=ev@entry=0x55a9c1079588 <rcu_call_ready_event>) at ../util/qemu-thread-posix.c:464 +#3 0x000055a9bff97d82 in call_rcu_thread (opaque=opaque@entry=0x0) at ../util/rcu.c:278 +#4 0x000055a9bff8c2d1 in qemu_thread_start (args=<optimized out>) at ../util/qemu-thread-posix.c:541 +#5 0x00007f968280bac3 in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:442 +#6 0x00007f968289d850 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 + +Thread 1 (Thread 0x7f967dc035c0 (LWP 754758) "qemu-system-x86"): +#0 0x00007f968288fcce in __ppoll (fds=0x55a9c382dd00, nfds=5, timeout=<optimized out>, timeout@entry=0x7ffeadbd44d0, sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:42 +#1 0x000055a9bffa4e05 in ppoll (__ss=0x0, __timeout=0x7ffeadbd44d0, __nfds=<optimized out>, __fds=<optimized out>) at /usr/include/x86_64-linux-gnu/bits/poll2.h:64 +#2 qemu_poll_ns (fds=<optimized out>, nfds=<optimized out>, timeout=timeout@entry=54822346) at ../util/qemu-timer.c:351 +#3 0x000055a9bffa1ed6 in os_host_main_loop_wait (timeout=54822346) at ../util/main-loop.c:305 +#4 main_loop_wait (nonblocking=nonblocking@entry=0) at ../util/main-loop.c:589 +#5 0x000055a9bfb47217 in qemu_main_loop () at ../system/runstate.c:826 +#6 0x000055a9bfee421b in qemu_default_main () at ../system/main.c:37 +#7 0x00007f96827a0d90 in __libc_start_call_main (main=main@entry=0x55a9bf8f9790 <main>, argc=argc@entry=9, argv=argv@entry=0x7ffeadbd46e8) at ../sysdeps/nptl/libc_start_call_main.h:58 +#8 0x00007f96827a0e40 in __libc_start_main_impl (main=0x55a9bf8f9790 <main>, argc=9, argv=0x7ffeadbd46e8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffeadbd46d8) at ../csu/libc-start.c:392 +#9 0x000055a9bf8fa7b5 in _start () +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/257 b/gitlab/issues_text/target_missing/host_missing/accel_missing/257 new file mode 100644 index 000000000..094b66003 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/257 @@ -0,0 +1 @@ +[Archlinux][git]With git revision e58c7a3b, packaging with meson install is broken. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2570 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2570 new file mode 100644 index 000000000..13fc29790 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2570 @@ -0,0 +1,55 @@ +TCG Plugins: "Code should not be reached" error after resetting plugin from vcpu_tb_trans callback +Description of problem: +In a TCG plugin, using the `qemu_plugin_reset` method from within a `vcpu_tb_trans` callback produces the following error. If this isn't a supported use case, it should probably be described in the documentation. If this is supposed to work, it doesn't seem to. + +``` +** +ERROR:/home/user/git/qemu/tcg/i386/tcg-target.c.inc:3018:tcg_out_op: code should not be reached +Bail out! ERROR:/home/user/git/qemu/tcg/i386/tcg-target.c.inc:3018:tcg_out_op: code should not be reached +Aborted (core dumped) +``` +Steps to reproduce: +1. Build the current head of master (4b7ea33074450bc6148c8e1545d78f179e64adb4) with the below `min` plugin (i.e., add to contrib/plugins and update contrib/plugins/Makefile so it is built) +2. `../configure --enable-plugins --target-list=x86_64-softmmu --disable-docs` +3. `make && make plugins` +4. Get a qcow, e.g., the Ubuntu Bionic qcow from [here](https://panda.re/qcows/linux/ubuntu/1804/x86_64/bionic-server-cloudimg-amd64-noaslr-nokaslr.qcow2). +5. `./qemu-system-x86_64 -plugin contrib/plugins/libmin.so bionic-server-cloudimg-amd64-noaslr-nokaslr.qcow2 -nographic` + +The first three lines are output by the plugin as expected, the error after that and the abort are unexpected: +``` +Translating basic block +Reset request issued +Reset finished +** +ERROR:/home/user/git/qemu/tcg/i386/tcg-target.c.inc:3018:tcg_out_op: code should not be reached +Bail out! ERROR:/home/user/git/qemu/tcg/i386/tcg-target.c.inc:3018:tcg_out_op: code should not be reached +Aborted (core dumped) +``` +Additional information: +contrib/plugins/min.c +```c +#include <stdio.h> +#include <qemu-plugin.h> + +QEMU_PLUGIN_EXPORT int qemu_plugin_version = QEMU_PLUGIN_VERSION; + +qemu_plugin_id_t plugin_id = {0}; + +static void post_reset(qemu_plugin_id_t id) { + printf("Reset finished\n"); +} + +static void vcpu_tb_trans(qemu_plugin_id_t id, struct qemu_plugin_tb *tb) { + printf("Translating basic block\n"); + qemu_plugin_reset(plugin_id, post_reset); + printf("Reset request issued\n"); +} + +QEMU_PLUGIN_EXPORT int qemu_plugin_install(qemu_plugin_id_t id, + const qemu_info_t *info, int argc, char **argv) { + + qemu_plugin_register_vcpu_tb_trans_cb(id, vcpu_tb_trans); + plugin_id = id; + return 0; +} +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2575 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2575 new file mode 100644 index 000000000..82a41fb5d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2575 @@ -0,0 +1 @@ +cocoa: Remove deprecated CVDisplayLinkCreateWithCGDisplay() calls diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2576 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2576 new file mode 100644 index 000000000..8a1148d25 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2576 @@ -0,0 +1 @@ +virtio-balloon: Assertion `mrs.mr' failed. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2579 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2579 new file mode 100644 index 000000000..4bb5329d1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2579 @@ -0,0 +1 @@ +Is there a plan to fix the vulnerabilities CVE-2023-1386 and CVE-2021-3735? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/258 b/gitlab/issues_text/target_missing/host_missing/accel_missing/258 new file mode 100644 index 000000000..0bf8921c8 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/258 @@ -0,0 +1 @@ +Add Illumnos VM image diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2584 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2584 new file mode 100644 index 000000000..afea4ac65 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2584 @@ -0,0 +1,16 @@ +nbd URI wrong export name (regression in qemu 9.1) +Description of problem: +qemu with an nbd URI seems to pass the wrong export name to the server, if the exportname is `.`. This seems +to be a regression in qemu 9.1, because it didn't happen in 9.0. +Steps to reproduce: +``` +$ nbdkit -fv -U - null --run 'qemu-img info "nbd+unix:///.?socket=$unixsocket"' +... +nbdkit: null[1]: debug: null: open readonly=0 exportname="" tls=0 +``` + +In qemu 9.0 this was correct: + +``` +nbdkit: null[1]: debug: null: open readonly=0 exportname="." tls=0 +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2587 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2587 new file mode 100644 index 000000000..0e3f09f7c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2587 @@ -0,0 +1 @@ +Avoid using error_setg(&error_fatal, ...) in the QEMU sources diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2589 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2589 new file mode 100644 index 000000000..06c4dbf93 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2589 @@ -0,0 +1,56 @@ +Support guest shutdown of Alpine Linux in guest agent +Description of problem: +The qemu-guest-agent's shutdown calls `/sbin/shutdown` with the apropriate flags to shut down a posix system. On Alpine Linux, which is based on busybox, there is no `/sbin/shutdown`, instead there are `/sbin/poweroff`, `/sbin/halt` and `/sbin/reboot`. We have used a downstream patch for years that will exec those as a fallback in case execing `/sbin/shutdown` fails. + +With qemu 9.2 this patch no longer applies and it is probably time to solve this properly in upstream qemu. + +The question is how? + +Some options: + +- Set the powerdown, halt and reboot commands via build time configure option +- Add a fallback if the `execlp` fails (similar to what downstream Alpine's patch does now). We could for example give `ga_run_command` a `const char **argv[]`, and try `execvp` all of them before erroring out. +- Test the existence of `/sbin/shutdown` before calling `ga_run_command`. +- Do nothing. Let downstream Alpine Linux handle it. +Steps to reproduce: +1. Build qemu-guest-agent for Alpine Linux +2. boot a Alpine linux VM and install the qemu-guest-agent +3. Try shutdown the VM via qmp command. +Additional information: +The patch that we previously used that no longer applies: +```diff +diff --git a/qga/commands-posix.c b/qga/commands-posix.c +index 954efed01..61427652c 100644 +--- a/qga/commands-posix.c ++++ b/qga/commands-posix.c +@@ -84,6 +84,7 @@ static void ga_wait_child(pid_t pid, int *status, Error **errp) + void qmp_guest_shutdown(bool has_mode, const char *mode, Error **errp) + { + const char *shutdown_flag; ++ const char *fallback_cmd = NULL; + Error *local_err = NULL; + pid_t pid; + int status; +@@ -101,10 +102,13 @@ void qmp_guest_shutdown(bool has_mode, const char *mode, Error **errp) + slog("guest-shutdown called, mode: %s", mode); + if (!has_mode || strcmp(mode, "powerdown") == 0) { + shutdown_flag = powerdown_flag; ++ fallback_cmd = "/sbin/poweroff"; + } else if (strcmp(mode, "halt") == 0) { + shutdown_flag = halt_flag; ++ fallback_cmd = "/sbin/halt"; + } else if (strcmp(mode, "reboot") == 0) { + shutdown_flag = reboot_flag; ++ fallback_cmd = "/sbin/reboot"; + } else { + error_setg(errp, + "mode is invalid (valid values are: halt|powerdown|reboot"); +@@ -125,6 +129,7 @@ void qmp_guest_shutdown(bool has_mode, const char *mode, Error **errp) + #else + execl("/sbin/shutdown", "shutdown", "-h", shutdown_flag, "+0", + "hypervisor initiated shutdown", (char *)NULL); ++ execle(fallback_cmd, fallback_cmd, (char*)NULL, environ); + #endif + _exit(EXIT_FAILURE); + } else if (pid < 0) { +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/259 b/gitlab/issues_text/target_missing/host_missing/accel_missing/259 new file mode 100644 index 000000000..fae787c1c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/259 @@ -0,0 +1 @@ +dma_blk_cb leaks memory map handles on misaligned IO diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2592 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2592 new file mode 100644 index 000000000..3e2f82a01 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2592 @@ -0,0 +1,37 @@ +qemu-aarch64 cannot properly support some python functions from the `time` module +Description of problem: +When a function is run in python (for example, `time.time()`), python returns the following error: +``` +Traceback (most recent call last): + File "<string>", line 1, in <module> +OSError: [Errno 0] Error +``` +I am absolutely sure that this problem is related to `qemu-aarch64`, because the same python build works perfectly in aarch64 machine. In addition, python for arm architecture with `qemu-arm` does not have such a problem. +Steps to reproduce: +Note, this instruction specifies the stage of installation of that very python. But since it is compiled for Termux, you will have to use some scripts. +1. Create a simple codespace environment. +2. Run the following commands through the terminal: +``` +git clone https://github.com/termux-pacman/glibc-packages +cd glibc-packages +./get-build-package.sh +sudo mkdir /data +sudo chown codespace /data +sudo chgrp codespace /data +sudo apt update +sudo apt install patchelf +./scripts/setup-cgct.sh +``` +3. Run the following command. Note that the installation phase will start there. You should stop the script when the installation phase is complete. +``` +./build-package.sh -I -w --library glibc gpkg/gobject-introspection +``` +4. Install standard qemu via apt. +5. Run the following command: +``` +qemu-aarch64 /data/data/com.termux/files/usr/glibc/bin/python3.12 -c "import time; time.time()" +``` +Additional information: +- For some reason this error only occurs in the environment from GitHub. On my computer this error does not occur. + - Here is a log of one of the github actions, which shows an attempt to compile packages with python on different architectures - https://github.com/termux-pacman/glibc-packages/actions/runs/11023254502. +For reference, I use qemu for more flexible compilation of packages. And in github actions, qemu is installed here - https://github.com/termux-pacman/glibc-packages/blob/main/.github/workflows/build.yml#L35. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2596 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2596 new file mode 100644 index 000000000..01406fee7 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2596 @@ -0,0 +1 @@ +linux-user elf parsing endianness issue (Invalid note in PT_GNU_PROPERTY) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2602 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2602 new file mode 100644 index 000000000..7d8ea2561 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2602 @@ -0,0 +1,9 @@ +Windows installer being signed with an expired certificate +Description of problem: +Digital Signature for setup is invalid +Steps to reproduce: +1. Downloaded the latest 64-bit windows installer +2. Right Click and select Digital Signature tab +3. Observe certificate shows valid dates are 12/8/2022 - 12/9/2023 +Additional information: +{width=621 height=393} diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2603 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2603 new file mode 100644 index 000000000..2cb6522c7 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2603 @@ -0,0 +1,102 @@ +Recent libslirp commit broke Qemu network stack: qemu and libslirp teams should settle on SOCKET handler type +Description of problem: +https://gitlab.freedesktop.org/slirp/libslirp/-/commit/72f85005a2307fd0961543e3cea861ad7a4d201e introduced regression causing QEMU compilation for Windows to error out due to missing 64-bit SOCKET handler pointer type. + +``` +x86_64-w64-mingw32-gcc -m64 ... -MD -MQ libcommon.a.p/net_slirp.c.obj -MF libcommon.a.p/net_slirp.c.obj.d -o libcommon.a.p/net_slirp.c.obj -c ../net/slirp.c +../net/slirp.c:289:25: error: initialization of 'void (*)(slirp_os_socket, void *)' {aka 'void (*)(long long unsigned int, void *)'} from incompatible pointer type 'void (*)(int, void *)' [-Wincompatible-pointer-types] + 289 | .register_poll_fd = net_slirp_register_poll_fd, + | ^~~~~~~~~~~~~~~~~~~~~~~~~~ +../net/slirp.c:289:25: note: (near initialization for 'slirp_cb.register_poll_fd') +../net/slirp.c:290:27: error: initialization of 'void (*)(slirp_os_socket, void *)' {aka 'void (*)(long long unsigned int, void *)'} from incompatible pointer type 'void (*)(int, void *)' [-Wincompatible-pointer-types] + 290 | .unregister_poll_fd = net_slirp_unregister_poll_fd, + | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ +../net/slirp.c:290:27: note: (near initialization for 'slirp_cb.unregister_poll_fd') +../net/slirp.c: In function 'net_slirp_poll_notify': +../net/slirp.c:367:28: error: passing argument 3 of 'slirp_pollfds_fill' from incompatible pointer type [-Wincompatible-pointer-types] + 367 | net_slirp_add_poll, poll->pollfds); + | ^~~~~~~~~~~~~~~~~~ + | | + | int (*)(int, int, void *) +In file included from ../net/slirp.c:41: +/home/cross-qemu-deps/include/slirp/libslirp.h:255:40: note: expected 'SlirpAddPollCb' {aka 'int (*)(long long unsigned int, int, void *)'} but argument is of type 'int (*)(int, int, void *)' + 255 | SlirpAddPollCb add_poll, void *opaque); + | ~~~~~~~~~~~~~~~^~~~~~~~ +``` + +Possible solution relying on cross-platform MACRO: https://handsonnetworkprogramming.com/articles/socket-function-return-value-windows-linux-macos/ +Steps to reproduce: +1. Prepare cross-compilation build of qemu 9.1.0 using following steps (It's not necessary to set up a virtual machine if your main OS has good mingw repository, like Fedora, Arch linux, Manjaro. But if you're on Debian or Ubuntu, it's required): +2. Download official Fedora workstation 40 x86_64 ISO and install it to a virtual disk and boot that disk. +3. On Fedora, do:\ + `wget https://download.qemu.org/qemu-9.1.0.tar.xz`\ + ` tar xvJf qemu-9.1.0.tar.xz`\ + ` cd qemu-9.1.0` +4. `sudo yum install git meson ninja-build python3-sphinx python3-sphinx_rtd_theme gcc mingw64-gcc mingw64-pkg-config mingw64-glib2` +5. `git clone https://gitlab.freedesktop.org/slirp/libslirp.git` +6. create file x86_64-w64-mingw32.txt in qemu-9.1.0 directory with the content as follows: + +``` +[binaries] +c = '/usr/bin/x86_64-w64-mingw32-gcc' +cpp = '/usr/bin/x86_64-w64-mingw32-g++' +ar = '/usr/bin/x86_64-w64-mingw32-ar' +strip = '/usr/bin/x86_64-w64-mingw32-strip' +pkg-config = '/usr/bin/x86_64-w64-mingw32-pkg-config' +exe_wrapper = 'wine' + +[host_machine] +system = 'windows' +cpu_family = 'x86_64' +cpu = 'i686' +endian = 'little' +``` + + 7. Run 2 commands: + + `export CROSS_QEMU_DEPS="/home/cross-qemu-deps"`\ + ` sudo mkdir -p $CROSS_QEMU_DEPS` + 8. Install libslirp so that future qemu binaries can have internet access via \`-netdev user\`\ + \ + `cd libslirp`\ + \ + ` meson setup --cross-file ../x86_64-w64-mingw32.txt --prefix "$CROSS_QEMU_DEPS" build-mingw/`\ + ` meson compile -C build-mingw`\ + ` cd build-mingw`\ + ` ninja install` + 9. Set environment variables for cross-compilation\ + \ + ` sudo find / -type f -name '*.pc'` and make sure all mingw \*.pc files live in /usr/x86_64-w64-mingw32/sys-root/mingw/lib/pkgconfig/. Correct this path in PKG_CONFIG_PATH if you see it was altered by mingw or package contributors.\ + \ + ` export PKG_CONFIG_PATH="/usr/x86_64-w64-mingw32/sys-root/mingw/lib/pkgconfig/:$PKG_CONFIG_PATH"`\ + ` export PKG_CONFIG_LIBDIR="${CROSS_QEMU_DEPS}/lib/pkgconfig/:$PKG_CONFIG_LIBDIR"`\ + ` export PKG_CONFIG_SYSROOT_DIR=""` +10. Configure Qemu makefile:\ + \ + `cd ../../`\ + `./configure --cross-prefix=x86_64-w64-mingw32- --enable-slirp`\ + \ + and make sure you see this in the output of configure:\ + `Compilation`\ + `host CPU : x86_64`\ + `host endianness : little`\ + `C compiler : x86_64-w64-mingw32-gcc -m64`\ + `Host C compiler : cc` +11. Cross-compile qemu: `` make -j`nproc` `` +12. Get the error `initialization of 'void (*)(slirp_os_socket, void *)' {aka 'void (*)(long long unsigned int, void *)'} from incompatible pointer type 'void (*)(int, void *)'` as above. +Additional information: +After having seen this bug, do these steps (revert to the commit right before the buggy one). + +` cd libslirp`\ +` git reset --hard 5e97a93b` + +` meson setup --cross-file ../x86_64-w64-mingw32.txt --prefix "$CROSS_QEMU_DEPS" build-mingw/ --reconfigure`\ +` meson compile -C build-mingw`\ +` cd build-mingw`\ +` ninja install` + +`` cd ../../ ``\ +`` ./configure --cross-prefix=x86_64-w64-mingw32- --enable-slirp ``\ +`` make -j`nproc` `` + +=\> Cross-compilation comes to an end just fine, building all compilation targets without any errors. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2606 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2606 new file mode 100644 index 000000000..697309b26 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2606 @@ -0,0 +1,198 @@ +PowerPC host code is broken on Darwin +Description of problem: +Existing code is just wrong for Darwin ppc, it won’t compile. Assembler syntax needs to be fixed and likely adjusted to correct ABI. +Steps to reproduce: +1. Run the build of qemu on Darwin ppc, see it fail. +Additional information: +This is a patch I used earlier to fix the build (together with few minor unrelated to powerpc fixes): +``` +--- common-user/host/ppc/safe-syscall.inc.S.orig 2022-04-20 03:10:27.000000000 +0800 ++++ common-user/host/ppc/safe-syscall.inc.S 2023-08-18 18:08:15.000000000 +0800 +@@ -25,17 +25,11 @@ + # else + # error "Unknown ABI" + # endif +-#endif +- +-#ifndef _CALL_SYSV +-# error "Unsupported ABI" + #endif + +- + .global safe_syscall_base + .global safe_syscall_start + .global safe_syscall_end +- .type safe_syscall_base, @function + + .text + +@@ -47,11 +41,8 @@ + * arguments being syscall arguments (also 'long'). + */ + safe_syscall_base: +- .cfi_startproc +- stwu 1, -8(1) +- .cfi_def_cfa_offset 8 +- stw 30, 4(1) +- .cfi_offset 30, -4 ++ stwu r1, -8(r1) ++ stw r30, 4(r1) + + /* + * We enter with r3 == &signal_pending +@@ -64,14 +55,14 @@ + * and returns the result in r3 + * Shuffle everything around appropriately. + */ +- mr 30, 3 /* signal_pending */ +- mr 0, 4 /* syscall number */ +- mr 3, 5 /* syscall arguments */ +- mr 4, 6 +- mr 5, 7 +- mr 6, 8 +- mr 7, 9 +- mr 8, 10 ++ mr r30, r3 /* signal_pending */ ++ mr r0, r4 /* syscall number */ ++ mr r3, r5 /* syscall arguments */ ++ mr r4, r6 ++ mr r5, r7 ++ mr r6, r8 ++ mr r7, r9 ++ mr r8, r10 + + /* + * This next sequence of code works in conjunction with the +@@ -83,25 +74,22 @@ + */ + safe_syscall_start: + /* if signal_pending is non-zero, don't do the call */ +- lwz 12, 0(30) +- cmpwi 0, 12, 0 ++ lwz r12, 0(r30) ++ cmpwi cr0, r12, 0 + bne- 2f + sc + safe_syscall_end: + /* code path when we did execute the syscall */ +- lwz 30, 4(1) /* restore r30 */ +- addi 1, 1, 8 /* restore stack */ +- .cfi_restore 30 +- .cfi_def_cfa_offset 0 ++ lwz r30, 4(r1) /* restore r30 */ ++ addi r1, r1, 8 /* restore stack */ ++ + bnslr+ /* return on success */ + b safe_syscall_set_errno_tail + + /* code path when we didn't execute the syscall */ +-2: lwz 30, 4(1) +- addi 1, 1, 8 +- addi 3, 0, QEMU_ERESTARTSYS ++2: lwz r30, 4(r1) ++ addi r1, r1, 8 ++ addi r3, 0, QEMU_ERESTARTSYS + b safe_syscall_set_errno_tail + +- .cfi_endproc +- + .size safe_syscall_base, .-safe_syscall_base + + +--- common-user/host/ppc64/safe-syscall.inc.S.orig 2022-04-20 03:10:27.000000000 +0800 ++++ common-user/host/ppc64/safe-syscall.inc.S 2022-05-31 13:23:21.000000000 +0800 +@@ -13,7 +13,6 @@ + .global safe_syscall_base + .global safe_syscall_start + .global safe_syscall_end +- .type safe_syscall_base, @function + + .text + +@@ -23,19 +22,10 @@ + * second one the system call number (as a 'long'), and all further + * arguments being syscall arguments (also 'long'). + */ +-#if _CALL_ELF == 2 +-safe_syscall_base: +- .cfi_startproc +- .localentry safe_syscall_base,0 +-#else +- .section ".opd","aw" ++ + .align 3 + safe_syscall_base: +- .quad .L.safe_syscall_base,.TOC.@tocbase,0 +- .previous +-.L.safe_syscall_base: +- .cfi_startproc +-#endif ++ + /* We enter with r3 == &signal_pending + * r4 == syscall number + * r5 ... r10 == syscall arguments +@@ -46,16 +36,15 @@ + * and returns the result in r3 + * Shuffle everything around appropriately. + */ +- std 14, 16(1) /* Preserve r14 in SP+16 */ +- .cfi_offset 14, 16 +- mr 14, 3 /* signal_pending */ +- mr 0, 4 /* syscall number */ +- mr 3, 5 /* syscall arguments */ +- mr 4, 6 +- mr 5, 7 +- mr 6, 8 +- mr 7, 9 +- mr 8, 10 ++ std r14, 16(r1) /* Preserve r14 in SP+16 */ ++ mr r14, r3 /* signal_pending */ ++ mr r0, r4 /* syscall number */ ++ mr r3, r5 /* syscall arguments */ ++ mr r4, r6 ++ mr r5, r7 ++ mr r6, r8 ++ mr r7, r9 ++ mr r8, r10 + + /* This next sequence of code works in conjunction with the + * rewind_if_safe_syscall_function(). If a signal is taken +@@ -66,29 +55,20 @@ + */ + safe_syscall_start: + /* if signal_pending is non-zero, don't do the call */ +- lwz 12, 0(14) +- cmpwi 0, 12, 0 ++ ld r12, 0(r14) ++ cmpdi cr0, r12, 0 + bne- 2f + sc + safe_syscall_end: + /* code path when we did execute the syscall */ +- ld 14, 16(1) /* restore r14 */ ++ ld r14, 16(r1) /* restore r14 */ + bso- 1f + blr + + /* code path when we didn't execute the syscall */ +-2: ld 14, 16(1) /* restore r14 */ +- addi 3, 0, QEMU_ERESTARTSYS ++2: ld r14, 16(r1) /* restore r14 */ ++ addi r3, 0, QEMU_ERESTARTSYS + + /* code path setting errno */ + 1: b safe_syscall_set_errno_tail + nop /* per abi, for the linker to modify */ +- +- .cfi_endproc +- +-#if _CALL_ELF == 2 +- .size safe_syscall_base, .-safe_syscall_base +-#else +- .size safe_syscall_base, .-.L.safe_syscall_base +- .size .L.safe_syscall_base, .-.L.safe_syscall_base +-#endif +``` +(Obviously, it is not made in a portable way – that was not needed at the time.) + +Unfortunately, while build itself worked, the binary crashed on launch. So something is not quite right, maybe with ABI compliance. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2607 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2607 new file mode 100644 index 000000000..365c734fa --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2607 @@ -0,0 +1,67 @@ +msys2 build failed +Description of problem: + +Steps to reproduce: +1. Install MSYS2 and QEMU build dependencies +2. Update (pacman -Syu) +3. Build: +``` +./configure --enable-sdl --enable-fdt=system --disable-docs --target-list=arm-softmmu,aarch64-softmmu --enable-avx2 +make -j16 +``` +Additional information: +See: https://github.com/msys2/MINGW-packages/issues/22104#issuecomment-2393727818 + +output: +``` +FAILED: libcommon.a.p/net_tap-win32.c.obj +"cc" "-m64" "-Ilibcommon.a.p" "-ID:/a/_temp/msys64/mingw64/include/capstone" "-ID:/a/_temp/msys64/mingw64/include/p11-kit-1" "-ID:/a/_temp/msys64/mingw64/include/pixman-1" "-ID:/a/_temp/msys64/mingw64/include/libpng16" "-ID:/a/_temp/msys64/mingw64/include/spice-server" "-ID:/a/_temp/msys64/mingw64/include/spice-1" "-ID:/a/_temp/msys64/mingw64/include/cacard" "-ID:/a/_temp/msys64/mingw64/include/nss3" "-ID:/a/_temp/msys64/mingw64/include/nspr" "-ID:/a/_temp/msys64/mingw64/include/glib-2.0" "-ID:/a/_temp/msys64/mingw64/lib/glib-2.0/include" "-ID:/a/_temp/msys64/mingw64/include/libusb-1.0" "-ID:/a/_temp/msys64/mingw64/include/SDL2" "-ID:/a/_temp/msys64/mingw64/include/slirp" "-ID:/a/_temp/msys64/mingw64/include/ncursesw" "-ID:/a/_temp/msys64/mingw64/include/gtk-3.0" "-ID:/a/_temp/msys64/mingw64/include/pango-1.0" "-ID:/a/_temp/msys64/mingw64/include/harfbuzz" "-ID:/a/_temp/msys64/mingw64/include/cairo" "-ID:/a/_temp/msys64/mingw64/include/freetype2" "-ID:/a/_temp/msys64/mingw64/include/gdk-pixbuf-2.0" "-ID:/a/_temp/msys64/mingw64/include/webp" "-ID:/a/_temp/msys64/mingw64/include/atk-1.0" "-ID:/a/_temp/msys64/mingw64/include/fribidi" "-ID:/a/_temp/msys64/mingw64/include/rav1e" "-ID:/a/_temp/msys64/mingw64/include/svt-av1" "-fdiagnostics-color=auto" "-Wall" "-Winvalid-pch" "-Werror" "-std=gnu11" "-O2" "-g" "-fstack-protector-strong" "-Wempty-body" "-Wendif-labels" "-Wexpansion-to-defined" "-Wformat-security" "-Wformat-y2k" "-Wignored-qualifiers" "-Wimplicit-fallthrough=2" "-Winit-self" "-Wmissing-format-attribute" "-Wmissing-prototypes" "-Wnested-externs" "-Wold-style-declaration" "-Wold-style-definition" "-Wredundant-decls" "-Wshadow=local" "-Wstrict-prototypes" "-Wtype-limits" "-Wundef" "-Wvla" "-Wwrite-strings" "-Wno-missing-include-dirs" "-Wno-psabi" "-Wno-shift-negative-value" "-iquote" "." "-iquote" "D:/a/qemu/qemu" "-iquote" "D:/a/qemu/qemu/include" "-iquote" "D:/a/qemu/qemu/host/include/x86_64" "-iquote" "D:/a/qemu/qemu/host/include/generic" "-iquote" "D:/a/qemu/qemu/tcg/i386" "-msse2" "-mcx16" "-D_GNU_SOURCE" "-D_FILE_OFFSET_BITS=64" "-D_LARGEFILE_SOURCE" "-fno-strict-aliasing" "-fno-common" "-fwrapv" "-fno-pie" "-no-pie" "-ftrivial-auto-var-init=zero" "-fzero-call-used-regs=used-gpr" "-DHWY_SHARED_DEFINE" "-DAVIF_DLL" "-DEB_DLL" "-DLIBDEFLATE_DLL" "-DNCURSES_WIDECHAR" "-DNCURSES_WIDECHAR=1" "-Dmain=SDL_main" "-DSTRUCT_IOVEC_DEFINED" -MD -MQ libcommon.a.p/net_tap-win32.c.obj -MF "libcommon.a.p/net_tap-win32.c.obj.d" -o libcommon.a.p/net_tap-win32.c.obj "-c" ../net/tap-win32.c +../net/tap-win32.c: In function 'tap_win32_open': +../net/tap-win32.c:343:19: error: '%s' directive output may be truncated writing up to 255 bytes into a region of size 176 [-Werror=format-truncation=] + 343 | "%s\\%s\\Connection", + | ^~ + 344 | NETWORK_CONNECTIONS_KEY, enum_name); + | ~~~~~~~~~ +In function 'get_device_guid', + inlined from 'tap_win32_open' at ../net/tap-win32.c:616:10: +../net/tap-win32.c:341:9: note: 'snprintf' output between 92 and 347 bytes into a destination of size 256 + 341 | snprintf(connection_string, + | ^~~~~~~~~~~~~~~~~~~~~~~~~~~ + 342 | sizeof(connection_string), + | ~~~~~~~~~~~~~~~~~~~~~~~~~~ + 343 | "%s\\%s\\Connection", + | ~~~~~~~~~~~~~~~~~~~~~ + 344 | NETWORK_CONNECTIONS_KEY, enum_name); + | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +../net/tap-win32.c: In function 'tap_win32_open': +../net/tap-win32.c:242:58: error: '%s' directive output may be truncated writing up to 255 bytes into a region of size 178 [-Werror=format-truncation=] + 242 | snprintf (unit_string, sizeof(unit_string), "%s\\%s", + | ^~ + 243 | ADAPTER_KEY, enum_name); + | ~~~~~~~~~ +In function 'is_tap_win32_dev', + inlined from 'get_device_guid' at ../net/tap-win32.c:368:21, + inlined from 'tap_win32_open' at ../net/tap-win32.c:616:10: +../net/tap-win32.c:242:9: note: 'snprintf' output between 79 and 334 bytes into a destination of size 256 + 242 | snprintf (unit_string, sizeof(unit_string), "%s\\%s", + | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + 243 | ADAPTER_KEY, enum_name); + | ~~~~~~~~~~~~~~~~~~~~~~~ +../net/tap-win32.c: In function 'tap_win32_open': +../net/tap-win32.c:620:52: error: '%s' directive output may be truncated writing up to 255 bytes into a region of size 245 [-Werror=format-truncation=] + 620 | snprintf (device_path, sizeof(device_path), "%s%s%s", + | ^~ + 621 | USERMODEDEVICEDIR, + 622 | device_guid, + | ~~~~~~~~~~~ +../net/tap-win32.c:620:5: note: 'snprintf' output between 16 and 271 bytes into a destination of size 256 + 620 | snprintf (device_path, sizeof(device_path), "%s%s%s", + | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + 621 | USERMODEDEVICEDIR, + | ~~~~~~~~~~~~~~~~~~ + 622 | device_guid, + | ~~~~~~~~~~~~ + 623 | TAPSUFFIX); + | ~~~~~~~~~~ +cc1.exe: all warnings being treated as errors +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2611 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2611 new file mode 100644 index 000000000..8432b3f5f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2611 @@ -0,0 +1,3 @@ +[Documentation]What is a Block driver? +Additional information: +Using Windows 11 but can use Linux diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2613 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2613 new file mode 100644 index 000000000..11c80cab6 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2613 @@ -0,0 +1 @@ +I was trying to build QEMU from source(noble) using debian commands in ubuntu24.04 derived docker and I got this error: cc1: error: ‘-fcf-protection’ is not compatible with this target diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2614 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2614 new file mode 100644 index 000000000..ca217c733 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2614 @@ -0,0 +1 @@ +vhost user documentation for VHOST_USER_ADD_MEM_REG incorrect diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2615 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2615 new file mode 100644 index 000000000..73eba6012 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2615 @@ -0,0 +1,10 @@ +tpm_emulator: the qemu process will be blocked while receiving an unexpected ctrl command's response from the swtpm +Description of problem: +When the swtpm sends the unexpected ctrl command's repsonse to the qemu process, the qemu will be blocked. When we use the gdb to attach the qemu process, we will find out that the qemu process is blocked in `recv_msg` function. +Steps to reproduce: +1.The QEMU process sends a `CMD_GET_TPMESTABLISHED` control command to the swtpm. +2.If the swtpm is not currently active (`tpm_running` is false), it responds to the QEMU process with an err_not_running message, which has a fixed size of 4 bytes. +(Reference: https://github.com/stefanberger/swtpm/blob/master/src/swtpm/ctrlchannel.c#L938) +3. However, the QEMU process expects to receive a valid response (ptm_est est) of 8 bytes. Consequently, the QEMU process will be blocked in the recv_msg function if the response does not match the expected format. +Additional information: +After analysing the source codes in `tpm_emulator.c`, we found that qemu does not process the unexpected ctrol command response from the swtpm correctly (e.g. `CMD_GET_TPMESTABLISHED`). The qemu would be blocked in this function if it received unexpected response from the swtpm (https://gitlab.com/qemu-project/qemu/-/blob/3e9f48bcdabe57f8f90cf19f01bbbf3c86937267/backends/tpm/tpm_emulator.c#L140). diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2617 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2617 new file mode 100644 index 000000000..ee26f7b04 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2617 @@ -0,0 +1,9 @@ +Go no +Description of problem: + +Steps to reproduce: +1. +2. +3. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2619 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2619 new file mode 100644 index 000000000..0b8c9c4d7 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2619 @@ -0,0 +1 @@ +INTEGER_OVERFLOW in nios2.c diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/262 b/gitlab/issues_text/target_missing/host_missing/accel_missing/262 new file mode 100644 index 000000000..83a7b0490 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/262 @@ -0,0 +1 @@ +Broken scaling with gtk,gl=on on a hidpi display diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2621 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2621 new file mode 100644 index 000000000..503e69123 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2621 @@ -0,0 +1,15 @@ +virtgpu does not return error for misconfigured virgl command +Description of problem: +When ```virgl_renderer_submit_cmd``` reports error, cmd->error should be set. Otherwise driver cannot know if there is error. +https://gitlab.com/qemu-project/qemu/-/blob/master/hw/display/virtio-gpu-virgl.c?ref_type=heads#L233 + +Probably 0x1200 (unspec) or 0x1205 (invalid param) should return as error. + + +If there is problem in cmd virgl freezes drawing window. +Steps to reproduce: +1. Send misformated command to virgl over vgpu device +2. +3. +Additional information: +Misformated 3d commands stops opengl's drawings. Without returning error we cannot know any error, hence we cannot reset vgpu. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2623 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2623 new file mode 100644 index 000000000..6a8d8e794 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2623 @@ -0,0 +1 @@ +Timeout waiting for ARP/RARP packets diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2624 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2624 new file mode 100644 index 000000000..2ea0c0c1a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2624 @@ -0,0 +1,39 @@ +qemu-system-aarch64: tpm-emulator: TPM result for CMD_INIT: 0x9 operation failed +Description of problem: +I'm using QEMU (compile from the latest source code) to simulate a tpm2 device with the above command, it just returns an error message: +``` +qemu-system-aarch64: tpm-emulator: TPM result for CMD_INIT: 0x9 operation failed +``` +swtpm start command: +``` +TPMSOCK=/tmp/swtpm-sock$$ +swtpm socket --tpm2 -t -d --tpmstate dir=$PWD/tpm --ctrl type=unixio,path=$TPMSOCK --log level=20 +``` +swtpm version: +``` +TPM emulator version 0.7.3, Copyright (c) 2014-2021 IBM Corp. +``` +Also tried the latest swtpm, encountered the same error. + +swtpm log (0.7.3): +``` +swtpm: Data client disconnected +swtpm: SWTPM_NVRAM_Lock_Dir: Could not open lockfile: Permission denied +swtpm: Error: Could not initialize libtpms. +swtpm: Error: Could not initialize the TPM +swtpm: Data client disconnected +``` + +swtpm log (0.10.0): +``` +swtpm: SWTPM_NVRAM_StoreData: Error (fatal) opening tpm/TMP2-00.permall for write failed, Permission denied +swtpm: SWTPM_NVRAM_Lock_Dir: Could not open lockfile: Permission denied +swtpm: Error: Could not initialize the TPM +swtpm: Data client disconnected +``` + +Any clues about this error? Best regrads. +Steps to reproduce: +Refer to [Description of problem](#description-of-problem) +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2628 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2628 new file mode 100644 index 000000000..f30ba793d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2628 @@ -0,0 +1,20 @@ +dpkg-deb in userspace emulation crashes in compression routine (armv7, aarch64, s390) on some machines +Description of problem: +chroot /scratch/debian-stable/ dpkg-deb -f /var/cache/apt/archives/dpkg_1.21.22_s390x.deb Version + +dpkg-deb: error: subprocess was killed by signal (Aborted), core dumped + +chroot /scratch/debian-stable/ dpkg-deb -f /var/cache/apt/archives/dpkg_1.21.22_arm64.deb Version + +dpkg-deb: error: subprocess was killed by signal (Segmentation fault), core dumped + +chroot /scratch/debian-stable/ dpkg-deb -f /var/cache/apt/archives/dpkg_1.21.22_armhf.deb Version + +dpkg-deb: error: subprocess was killed by signal (Segmentation fault), core dumped +Steps to reproduce: +1. debootstrap --arch=arm64 stable /scratch/debian-stable +2. chroot /scratch/debian-stable/ dpkg-deb -f /var/cache/apt/archives/dpkg_1.21.22_arm64.deb Version +Additional information: +Working environment: Debian 12 x86_64 Linux 6.1.0-25-amd64 qemu 7.2.13 AMD E-450 APU + +chroot can be created on this machine, when transferred to the broken machine (including the qemu binary used for emulation) dpkg cannot extract packages and crashes diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2629 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2629 new file mode 100644 index 000000000..ed1b312c2 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2629 @@ -0,0 +1 @@ +dpkg-deb in userspace emulation crashes in compression routine (armv7, aarch64, s390) on some machines diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/263 b/gitlab/issues_text/target_missing/host_missing/accel_missing/263 new file mode 100644 index 000000000..cafb19171 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/263 @@ -0,0 +1 @@ +readdir() returns NULL (errno=EOVERFLOW) for 32-bit user-static qemu on 64-bit host diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2630 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2630 new file mode 100644 index 000000000..ab8f1096d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2630 @@ -0,0 +1 @@ +Issue template broken diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2633 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2633 new file mode 100644 index 000000000..72eff0d8b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2633 @@ -0,0 +1,26 @@ +migration-test occassionally hangs with "Failed to peek at channel" +Description of problem: +Running the 'migration-test' qtest in a loop, eventually resulted in a hang. + +``` +# Running /x86_64/migration/multifd/tcp/plain/cancel +# Using machine type: pc-q35-9.2 +# starting QEMU: exec ./qemu-system-x86_64 -qtest unix:/tmp/qtest-75145.sock -qtest-log /dev/null -chardev socket,path=/tmp/qtest-75145.qmp,id=char0 -mon chardev=char0,mode=control -display none -audio none -accel kvm -accel tcg -machine pc-q35-9.2, -name source,debug-threads=on -m 150M -serial file:/tmp/migration-test-DJLYV2/src_serial -drive if=none,id=d0,file=/tmp/migration-test-DJLYV2/bootsect,format=raw -device ide-hd,drive=d0,secs=1,cyls=1,heads=1 2>/dev/null -accel qtest +# starting QEMU: exec ./qemu-system-x86_64 -qtest unix:/tmp/qtest-75145.sock -qtest-log /dev/null -chardev socket,path=/tmp/qtest-75145.qmp,id=char0 -mon chardev=char0,mode=control -display none -audio none -accel kvm -accel tcg -machine pc-q35-9.2, -name target,debug-threads=on -m 150M -serial file:/tmp/migration-test-DJLYV2/dest_serial -incoming defer -drive if=none,id=d0,file=/tmp/migration-test-DJLYV2/bootsect,format=raw -device ide-hd,drive=d0,secs=1,cyls=1,heads=1 2>/dev/null -accel qtest +# Using machine type: pc-q35-9.2 +# starting QEMU: exec ./qemu-system-x86_64 -qtest unix:/tmp/qtest-75145.sock -qtest-log /dev/null -chardev socket,path=/tmp/qtest-75145.qmp,id=char0 -mon chardev=char0,mode=control -display none -audio none -accel kvm -accel tcg -machine pc-q35-9.2, -name target,debug-threads=on -m 150M -serial file:/tmp/migration-test-DJLYV2/dest_serial -incoming defer -drive if=none,id=d0,file=/tmp/migration-test-DJLYV2/bootsect,format=raw -device ide-hd,drive=d0,secs=1,cyls=1,heads=1 -accel qtest +qemu-system-x86_64: Failed to peek at channel +....hang here.... +``` +Steps to reproduce: +In host run + +``` +make vm-build-openbsd DEBUG=1' +``` +when it is done and gives a shell account then run + +1. `cd /home/qemu/qemu-test.*/build` +2. `export QTEST_QEMU_BINARY=./qemu-system-x86_64` +3. `while true ; do ./tests/qtest/migration-test ; done` +4. ....wait some time until it shows the above hang.... diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2635 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2635 new file mode 100644 index 000000000..ac875080b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2635 @@ -0,0 +1,12 @@ +A use-after-free bug in pflash_cfi01 snapshot implementation +Description of problem: +The flash snapshot restore does not function correctly. Basically when you use “if=pflash,format=raw,unit=0,file=OVMF_VAR.fd", it crashes when trying to restore a snapshot. + +The root cause is: + +1. In system/runstate.c, function vm_state_notify loops through vm_change_state_head list and calls the callback function for each entry. +2. One of the callback function pointer points to function postload_update_cb in hw/block/pflash_cfi01.c. +3. In function postload_update_cb, it calls qemu_del_vm_change_state_handler in which the entry element memory is freed. +4. Note that, it is still running in the loop, the entry will be visited and get executed, the function pointer may point to a wide memory. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2637 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2637 new file mode 100644 index 000000000..92dfa7c73 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2637 @@ -0,0 +1,53 @@ +ubuntu 22.04 virtio-vga-gl notwork +Description of problem: + +Steps to reproduce: +1.qemu-system-x86_64 \ + -m 2048 \ + -smp 2 \ + -hda /home/perilla/virt/redroid.qcow2 \ + -boot d \ + -net nic -net user,hostfwd=tcp::1122-:22,hostfwd=tcp::19000-:9000,hostfwd=tcp::15555-:5555 \ + -vnc :0 \ + -device virtio-vga-gl \ + -display sdl,gl=on \ + -enable-kvm + +the machine can't startup normally + +host console output: +qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2]\n +qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2]\n +gl_version 46 - core profile enabled\n + +after`gl_version` line, startup prograss stopped![image] + +vm console output: +it seems different every startup progress + +first time: + +{width=764 height=467} +second time: + +{width=780 height=415} + +2. +3. +Additional information: +when I use -device virtio-gpu, it works fine +qemu-system-x86_64 \ + -m 2048 \ + -smp 2 \ + -hda /home/username/virt/redroid.qcow2 \ + -boot d \ + -net nic -net user,hostfwd=tcp::1122-:22,hostfwd=tcp::19000-:9000,hostfwd=tcp::15555-:5555 \ + -vnc :0 \ + -device virtio-gpu \ + -display sdl,gl=on \ + -enable-kvm \ + -device qxl + +host console output:\n +qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2]\n +qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2]\n diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2638 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2638 new file mode 100644 index 000000000..b865a5ec0 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2638 @@ -0,0 +1,17 @@ +Incorrect SPDX license expression +Description of problem: +In the source code, the syntax of license expressions after the keyword SPDX-License-Identifier is not always correct. + +"GPL-2.0" should be "GPL-2.0-only" + +"GPL-2.0 WITH Linux-syscall-note" should be "GPL-2.0-only WITH Linux-syscall-note" + +"GPL-2.0+" should be "GPL-2.0-or-later" + +"GPL-2.0+ WITH Linux-syscall-note" should be "GPL-2.0-or-later WITH Linux-syscall-note" + +"GPL-v2-only" should be "GPL-2.0-only" + +"LGPL-2.1+" should be "LGPL-2.1-or-later" + +"MIT CC0-1.0" should be "MIT" diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2639 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2639 new file mode 100644 index 000000000..5c429384a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2639 @@ -0,0 +1,22 @@ +[Regression] v9.1.1: hw/audio/hda audio output stream closes (SPICE) +Description of problem: +Beginning with QEMU 9.1.1, SPICE is unable to route audio from the guest to host. This affects `virt-viewer` as well as `Looking Glass`. Reverting packages to 9.1.0 restores functionality. + +Reported at [Arch Linux forums](https://bbs.archlinux.org/viewtopic.php?id=300475) and [Looking Glass discord](https://discord.com/channels/804108879436316733/1298405109210022038) + +---- + +I've confirmed https://gitlab.com/qemu-project/qemu/-/commit/6d03242a7e47815ed56687ecd13f683d8da3f2fe caused the regression, applying reverse patch to 9.1.1 resolves the issue +Additional information: +Debugging output from the [Looking Glass discord](https://discord.com/channels/804108879436316733/1298405109210022038/1298669405118664767): +``` +00:00:00.633 [I] main.c:1735 | lg_run | Starting session +[New Thread 0x7fffd12006c0 (LWP 10071)] +[New Thread 0x7fffc7e006c0 (LWP 10072)] +00:00:00.633 [I] main.c:553 | main_frameThread | Using DMA buffer support +00:00:01.339 [I] main.c:710 | main_frameThread | Format: FRAME_TYPE_BGRA 2560x1400 (2560x1400) stride:2560 pitch:10240 rotation:0 hdr:0 pq:0 + +Thread 2 "spiceThread" received signal SIGPIPE, Broken pipe. +[Switching to Thread 0x7fffdba006c0 (LWP 10024)] +0x00007ffff712a6ea in send () from /usr/lib/libc.so.6 +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/264 b/gitlab/issues_text/target_missing/host_missing/accel_missing/264 new file mode 100644 index 000000000..1e000425a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/264 @@ -0,0 +1 @@ +qed leaked clusters diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2640 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2640 new file mode 100644 index 000000000..90e1aa3ce --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2640 @@ -0,0 +1 @@ +QEMU twice logging when use SDL. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2641 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2641 new file mode 100644 index 000000000..df0a2429b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2641 @@ -0,0 +1 @@ +Possible DEREF_OF_NULL in linux-user/syscall.c diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2642 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2642 new file mode 100644 index 000000000..d6d26a96a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2642 @@ -0,0 +1,5 @@ +guest-set-time not supported +Description of problem: +guest-set-time is not supported un Ubuntu 24.04 guests. It still works on a Ubuntu 22.04 guest and on W10 and W11 guests + +feedback from the Ubuntu 24.04 guest: error: internal error: unable to execute QEMU agent command 'guest-set-time': this feature or command is not currently supported diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2643 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2643 new file mode 100644 index 000000000..5f92b1b41 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2643 @@ -0,0 +1,52 @@ +gtk initialization failed +Description of problem: +I compiled latest qemu version from sources with gtk enabled like below but still there is an issue of gtk initialization failed + ``` + ./configure --enable-gtk --enable-slirp + ``` +Steps to reproduce: +1. building qemu from sources or installing from packages results with gtk initialization failed message +Additional information: +``` + # virt-host-validate + QEMU: Checking for hardware virtualization : PASS + QEMU: Checking if device /dev/kvm exists : PASS + QEMU: Checking if device /dev/kvm is accessible : PASS + QEMU: Checking if device /dev/vhost-net exists : PASS + QEMU: Checking if device /dev/net/tun exists : PASS + QEMU: Checking for cgroup 'cpu' controller support : PASS + QEMU: Checking for cgroup 'cpuacct' controller support : PASS + QEMU: Checking for cgroup 'cpuset' controller support : PASS + QEMU: Checking for cgroup 'memory' controller support : PASS + QEMU: Checking for cgroup 'devices' controller support : PASS + QEMU: Checking for cgroup 'blkio' controller support : PASS + QEMU: Checking for device assignment IOMMU support : WARN (No ACPI IVRS table found, IOMMU either disabled in BIOS or not supported by this hardware platform) + QEMU: Checking for secure guest support : WARN (Unknown if this platform has Secure Guest support) + LXC: Checking for Linux >= 2.6.26 : PASS + LXC: Checking for namespace ipc : PASS + LXC: Checking for namespace mnt : PASS + LXC: Checking for namespace pid : PASS + LXC: Checking for namespace uts : PASS + LXC: Checking for namespace net : PASS + LXC: Checking for namespace user : PASS + LXC: Checking for cgroup 'cpu' controller support : PASS + LXC: Checking for cgroup 'cpuacct' controller support : PASS + LXC: Checking for cgroup 'cpuset' controller support : PASS + LXC: Checking for cgroup 'memory' controller support : PASS + LXC: Checking for cgroup 'devices' controller support : PASS + LXC: Checking for cgroup 'freezer' controller support : FAIL (Enable 'freezer' in kernel Kconfig file or mount/enable cgroup controller in your system) + LXC: Checking for cgroup 'blkio' controller support : PASS + LXC: Checking if device /sys/fs/fuse/connections exists : PASS + ``` + ``` +# apt list --installed | grep gtk +gir1.2-gtk-3.0/noble-updates,now 3.24.41-4ubuntu1.2 amd64 [installed,automatic] +gtk-update-icon-cache/noble-updates,now 3.24.41-4ubuntu1.2 amd64 [installed,automatic] +libavahi-ui-gtk3-0/noble,now 0.8-13ubuntu6 amd64 [installed,automatic] +libavahi-ui-gtk3-dev/noble,now 0.8-13ubuntu6 amd64 [installed] +libdecor-0-plugin-1-gtk/noble,now 0.2.2-1build2 amd64 [installed,automatic] +libgtk-3-0t64/noble-updates,now 3.24.41-4ubuntu1.2 amd64 [installed,automatic] +libgtk-3-bin/noble-updates,now 3.24.41-4ubuntu1.2 amd64 [installed,automatic] +libgtk-3-common/noble-updates,now 3.24.41-4ubuntu1.2 all [installed,automatic] +libgtk-3-dev/noble-updates,now 3.24.41-4ubuntu1.2 amd64 [installed,automatic] + ``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2644 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2644 new file mode 100644 index 000000000..fd105cf0f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2644 @@ -0,0 +1,66 @@ +openbsd 7.5 crashes with QEMU since "virtio-pci: Add lookup subregion of VirtIOPCIRegion MR" +Description of problem: +Attempt to boot OpenBSD 7.5 in QEMU current git HEAD fdf250e5a37830615e324017cb3a503e84b3712c. + +It immediately aborts with + +``` +Thread 6 (Thread 0x7fe06d2006c0 (LWP 2797401) "CPU 0/KVM"): +#0 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 +#1 0x00007fe0764476d3 in __pthread_kill_internal (threadid=<optimized out>, signo=6) at pthread_kill.c:78 +#2 0x00007fe0763eec4e in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 +#3 0x00007fe0763d6902 in __GI_abort () at abort.c:79 +#4 0x00007fe0763d681e in __assert_fail_base (fmt=0x7fe076562b98 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x55a00b998b4d "mrs.mr", file=file@entry=0x55a00b998b33 "../hw/virtio/virtio-pci.c", line=line@entry=620, function=function@entry=0x55a00bb596b0 <__PRETTY_FUNCTION__.13> "virtio_address_space_lookup") at assert.c:94 +#5 0x00007fe0763e6d87 in __assert_fail (assertion=assertion@entry=0x55a00b998b4d "mrs.mr", file=file@entry=0x55a00b998b33 "../hw/virtio/virtio-pci.c", line=line@entry=620, function=function@entry=0x55a00bb596b0 <__PRETTY_FUNCTION__.13> "virtio_address_space_lookup") at assert.c:103 +#6 0x000055a00b49d368 in virtio_address_space_lookup (proxy=proxy@entry=0x55a0213a59d0, off=off@entry=0x7fe06d1f3370, len=len@entry=1) at ../hw/virtio/virtio-pci.c:620 +#7 0x000055a00b4a127f in virtio_address_space_write (proxy=0x55a0213a59d0, addr=<optimized out>, buf=0x55a0213b32c8 "", len=1) at ../hw/virtio/virtio-pci.c:654 +#8 virtio_write_config (pci_dev=<optimized out>, address=<optimized out>, val=<optimized out>, len=<optimized out>) at ../hw/virtio/virtio-pci.c:790 +#9 0x000055a00b6edc30 in memory_region_write_accessor (mr=0x55a01fa1b470, addr=4194520, value=<optimized out>, size=1, shift=<optimized out>, mask=<optimized out>, attrs=...) at ../system/memory.c:497 +#10 0x000055a00b6ed4be in access_with_adjusted_size (addr=addr@entry=4194520, value=0x7fe06d1f34c8, size=size@entry=1, access_size_min=<optimized out>, access_size_max=<optimized out>, access_fn=0x55a00b6edbb0 <memory_region_write_accessor>, mr=<optimized out>, attrs=...) at ../system/memory.c:573 +#11 0x000055a00b6ed7fa in memory_region_dispatch_write (mr=mr@entry=0x55a01fa1b470, addr=addr@entry=4194520, data=<optimized out>, op=<optimized out>, attrs=attrs@entry=...) at ../system/memory.c:1560 +#12 0x000055a00b6f593f in flatview_write_continue_step (attrs=attrs@entry=..., buf=buf@entry=0x7fe07988e028 "", mr_addr=4194520, l=l@entry=0x7fe06d1f3590, mr=0x55a01fa1b470, len=1) at ../system/physmem.c:2786 +#13 0x000055a00b6f6058 in flatview_write_continue (fv=0x7fdf505079f0, addr=2956984536, attrs=..., ptr=0xb04000d8, len=1, mr_addr=<optimized out>, l=<optimized out>, mr=<optimized out>) at .--Type <RET> for more, q to quit, c to continue without paging-- +./system/physmem.c:2816 +#14 flatview_write (fv=0x7fdf505079f0, addr=addr@entry=2956984536, attrs=attrs@entry=..., buf=buf@entry=0x7fe07988e028, len=len@entry=1) at ../system/physmem.c:2847 +#15 0x000055a00b6f97a1 in address_space_write (as=0x55a00ca34600 <address_space_memory>, addr=2956984536, attrs=..., buf=0x7fe07988e028, len=1) at ../system/physmem.c:2967 +#16 address_space_rw (as=0x55a00ca34600 <address_space_memory>, addr=2956984536, attrs=attrs@entry=..., buf=buf@entry=0x7fe07988e028, len=1, is_write=<optimized out>) at ../system/physmem.c:2977 +#17 0x000055a00b75c256 in kvm_cpu_exec (cpu=cpu@entry=0x55a01f9cb690) at ../accel/kvm/kvm-all.c:3184 +#18 0x000055a00b75da25 in kvm_vcpu_thread_fn (arg=arg@entry=0x55a01f9cb690) at ../accel/kvm/kvm-accel-ops.c:50 +#19 0x000055a00b94daa8 in qemu_thread_start (args=0x55a01f9d2140) at ../util/qemu-thread-posix.c:541 +#20 0x00007fe0764456d7 in start_thread (arg=<optimized out>) at pthread_create.c:447 +#21 0x00007fe0764c9414 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:100 + +``` + +Git bisect points to + +``` +commit ffa8a3e3b2e6ff017113b98d500d6a9e05b1560a (HEAD) +Author: Gao Shiyuan <gaoshiyuan@baidu.com> +Date: Tue Sep 3 20:03:04 2024 +0800 + + virtio-pci: Add lookup subregion of VirtIOPCIRegion MR + + Now virtio_address_space_lookup only lookup common/isr/device/notify + MR and exclude their subregions. + + When VHOST_USER_PROTOCOL_F_HOST_NOTIFIER enable, the notify MR has + host-notifier subregions and we need use host-notifier MR to + notify the hardware accelerator directly instead of eventfd notify. + + Further more, maybe common/isr/device MR also has subregions in + the future, so need memory_region_find for each MR incluing + their subregions. + + Add lookup subregion of VirtIOPCIRegion MR instead of only lookup container MR. + + Fixes: a93c8d8 ("virtio-pci: Replace modern_as with direct access to modern_bar") + Co-developed-by: Zuo Boqun <zuoboqun@baidu.com> + Signed-off-by: Gao Shiyuan <gaoshiyuan@baidu.com> + Signed-off-by: Zuo Boqun <zuoboqun@baidu.com> + Message-Id: <20240903120304.97833-1-gaoshiyuan@baidu.com> + Reviewed-by: Michael S. Tsirkin <mst@redhat.com> + Signed-off-by: Michael S. Tsirkin <mst@redhat.com> +``` + +cc @mstredhat diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2646 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2646 new file mode 100644 index 000000000..46c5bf721 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2646 @@ -0,0 +1,25 @@ +osx 10.6.8 guest on x86-64 macos 10.12 host can't boot on HVF, boots on tcg +Description of problem: +for some reason HVF acceleration does not work with mac-on-mac. Haiku beta5 (x64), win10 x64, Debian netinstall 12.7.0 - all works. +Steps to reproduce: +``` +1. get 10.6.8 image from archive.org +2. bin/qemu-system-x86_64 -device isa-applesmc,osk="well_known_string" -usb -M pc-q35-2.11 -device usb-kbd -device usb-tablet -m 1536 -smp 1 -cpu Penryn,vendor=GenuineIntel,+ssse3,+sse4.1,+sse4.2 -L /opt/local/share/qemu -device ac97 -vnc :3 --no-reboot -accel hvf -boot c -bios usr/share/edk2-ovmf-x64/OVMF_CODE.fd -hda osx-10.6-xcode-compressed-efi.qcow2 -d unimp +audio: Could not create a backend for voice `ac97.pi' +audio: Could not create a backend for voice `ac97.mc' +audio: Could not create a backend for voice `ac97.pi' +audio: Could not create a backend for voice `ac97.mc' +ahci: IRQ#0 level:1 +ahci: IRQ#0 level:1 + +{many more of those} +``` +and at this point qemu quits. + +without --no-reboot it reboots + +tried both UEFI boot (using https://github.com/khronokernel/khronokernel.github.io/blob/master/Binaries/OpenCore/EFI-LEGACY.img.zip?raw=true , currently integrated into hdd image) and Clover-5160-X64.iso + +if I remove -accel hvf and replace it with accel tcg guest boots. + +i tried to capture moment when it reboots on video but I can't catch anything :( diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2647 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2647 new file mode 100644 index 000000000..ccef48f11 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2647 @@ -0,0 +1,47 @@ +A code error in accel/tcg/user-exec.c +Description of problem: +accel/tcg/user-exec.c: +``` +static int probe_access_internal(CPUArchState *env, vaddr addr, + int fault_size, MMUAccessType access_type, + bool nonfault, uintptr_t ra) +{ + int acc_flag; + bool maperr; + + switch (access_type) { + case MMU_DATA_STORE: + acc_flag = PAGE_WRITE_ORG; + break; + case MMU_DATA_LOAD: + acc_flag = PAGE_READ; + break; + case MMU_INST_FETCH: + acc_flag = PAGE_EXEC; + break; + default: + g_assert_not_reached(); + } + + if (guest_addr_valid_untagged(addr)) { + int page_flags = page_get_flags(addr); + if (page_flags & acc_flag) { + if ((acc_flag == PAGE_READ || acc_flag == PAGE_WRITE) + && cpu_plugin_mem_cbs_enabled(env_cpu(env))) { + return TLB_MMIO; + } + return 0; /* success */ + } + maperr = !(page_flags & PAGE_VALID); + } else { + maperr = true; + } + + if (nonfault) { + return TLB_INVALID_MASK; + } + + cpu_loop_exit_sigsegv(env_cpu(env), addr, access_type, maperr, ra); +} +``` +The conditional judgment "acc_flag == PAGE_WRITE" seems to have an issue, because acc_flag can only be PAGE_WRITE_ORG, PAGE_READ or PAGE_EXEC from the previous code. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2648 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2648 new file mode 100644 index 000000000..4dfbd0b53 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2648 @@ -0,0 +1,11 @@ +Possible dereference of NULL in block/qapi.c +Description of problem: +qdict_get can return NULL if the "data" key is not found in the obj dictionary. Then if NULL is passed to the qobject_is_empty_dump function, it will be dereferenced when calling the qobject_type function. + +https://github.com/qemu/qemu/blob/92ec7805190313c9e628f8fc4eb4f932c15247bd/block/qapi.c#L891-L892 + +I think that data check for NULL should be added. + +Found by Linux Verification Center (portal.linuxtesting.ru) with SVACE. + +Author A. Burke. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2649 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2649 new file mode 100644 index 000000000..d8b6ad5a6 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2649 @@ -0,0 +1,40 @@ +Data corruption with qcow2 images +Steps to reproduce: +``` +# Create an example file with old version of qemu-img and fill it with random data. +$ qemu-img-8.2.2 create -f qcow2 file.qcow2 600000000000 +$ qemu-nbd-8.2.2 -c /dev/nbd0 file.qcow2 +$ dd if=/dev/random of=/dev/nbd0 bs=1000000 count=600000 +$ qemu-nbd-8.2.2 -d /dev/nbd0 +/dev/nbd0 disconnected + +# Get the correct checksum of both qcow2 file and its contents +$ sha256sum -b file.qcow2 +ca471f6822af4fcf3c81bc5cc671493be06a837b71b43c1f747042759da587b9 *file.qcow2 +$ qemu-nbd-8.2.2 -r -c /dev/nbd0 file.qcow2 +$ sha256sum -b /dev/nbd0 +5dac11e88f891740da3b655588b2e62037962d1ba6377efce30124d6224dd0d1 */dev/nbd0 +$ qemu-nbd-8.2.2 -d /dev/nbd0 +/dev/nbd0 disconnected + +# Use the qcow2 file with new version. +# We're using qemu-nbd here, but the same happens when qcow2 is attached to a guest +# running in the new version qemu-system-86_64-9.1.1 and can be seen through guest's +# /dev/vda. +# Note that the checksum is different than before, and also non-deterministic +# (running sha256sum twice produces different results even though the file is +# read-only and hasn't changed). +$ sha256sum -b file.qcow2 +ca471f6822af4fcf3c81bc5cc671493be06a837b71b43c1f747042759da587b9 *file.qcow2 +$ qemu-nbd-9.1.1 -r -c /dev/nbd0 file.qcow2 +$ sha256sum -b /dev/nbd0 +1793a38b9b964d3fc643629284722373e9d5dedea68e35900ace777b57688926 */dev/nbd0 +$ sha256sum -b /dev/nbd0 +98f900f9cd174493d0bfcf06e2bc86f5ee99dfa04c90d6832fa941e384b62d49 */dev/nbd0 +$ qemu-nbd-9.1.1 -d /dev/nbd0 +/dev/nbd0 disconnected +$ sha256sum -b file.qcow2 +ca471f6822af4fcf3c81bc5cc671493be06a837b71b43c1f747042759da587b9 *file.qcow2 +``` +Additional information: +No errors in either host or guest logs. When using a qcow2 with an actual filesystem, you may see reports of corruption from the filesystem driver. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2650 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2650 new file mode 100644 index 000000000..deb6c7c50 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2650 @@ -0,0 +1,192 @@ +qemu-system-x86_64: util/hbitmap.c:614: serialization_chunk: Assertion `(last >> hb->granularity) < hb->size' failed +Description of problem: +If a named dirty bitmap already exists on a disk and another disk is added via hotplug after the guest has booted, it will definitely cause the hot migration to fail. +Steps to reproduce: +1. Create 2 images of type qcow2 + + ``` + qemu-img create -f qcow2 vda.qcow2 50G + qemu-img create -f qcow2 vdb.qcow2 2G # set to 2G + ``` +2. Start the guest using the following libvirt xml + + ``` + # virsh create i-btacsctt.xml + + <domain xmlns:qemu="http://libvirt.org/schemas/domain/qemu/1.0" type="kvm"> + <name>i-btacsctt</name> + <uuid>973f7352-ad1d-31ea-9a9f-237f3e9a384f</uuid> + <memory unit="MiB">2048</memory> + <vcpu current="2">2</vcpu> + <os> + <type arch="x86_64" machine="pc">hvm</type> + </os> + <features> + <acpi/> + <apic/> + <pae/> + </features> + <devices> + <emulator>/opt/qemu-5.1.0.9/usr/bin/qemu-system-x86_64</emulator> + <disk device="disk" type="file"> + <driver cache="writeback" discard="ignore" io="threads" name="qemu" type="qcow2"/> + <source file="/tmp/echohu3/vda.qcow2"/> + <target dev="vda"/> + </disk> + <disk device="disk" type="file"> + <driver cache="none" io="threads" name="qemu" type="qcow2"/> + <source file="/tmp/echohu3/vdb.qcow2"/> + <target dev="vdb"/> + </disk> + </devices> + </domain> + ``` +3. Create bitmap for vda + + ``` + # The node name of vda is "libvirt-2-format" + virsh qemu-monitor-command i-btacsctt --hmp "info block" + libvirt-2-format: /tmp/echohu3/vda.qcow2 (qcow2) + Attached to: /machine/peripheral/virtio-disk0/virtio-backend + Cache mode: writethrough + + libvirt-1-format: /tmp/echohu3/vdb.qcow2 (qcow2) + Attached to: /machine/peripheral/virtio-disk1/virtio-backend + Cache mode: writeback, direct + + # Create bitmap + virsh qemu-monitor-command i-btacsctt '{"execute":"block-dirty-bitmap-add","arguments":{"node":"libvirt-2-format","name":"bitmap0","persistent":true}}' + ``` +4. Create vdc and run hotpluggin + + ``` + qemu-img create -f qcow2 vdc.qcow2 50G + + cat disk.xml + <disk device="disk" type="file"> + <driver cache="none" discard="ignore" io="threads" name="qemu" type="qcow2"/> + <source file="/tmp/echohu3/vdc.qcow2"/> + <target dev="vdc"/> + </disk> + + virsh attach-device i-btacsctt disk.xml + ``` +5. Start live migrationg + + ``` + # scp *.qcow2 172.31.68.42:/tmp/echohu3/ + virsh qemu-monitor-command i-btacsctt --hmp "migrate_set_capability dirty-bitmaps on" + virsh dumpxml --migratable i-btacsctt >/tmp/ivm-btacsctt.xml + virsh migrate --live --abort-on-error --xml /tmp/ivm-btacsctt.xml i-btacsctt qemu+tcp://172.31.68.42/system + error: internal error: qemu unexpectedly closed the monitor: qemu-system-x86_64: util/hbitmap.c:614: serialization_chunk: Assertion `(last >> hb->granularity) < hb->size' failed. + ``` +Additional information: +Set breakpoints on the source side + +``` +gdb -p $pid -ex "break add_bitmaps_to_list" -ex "handle SIGUSR1 nostop" -ex "continue" +(gdb) bt +#0 add_bitmaps_to_list (bs=bs@entry=0x55c5bbaf85d0, bs_name=0x55c5bbafc674 "libvirt-2-format", alias_map=alias_map@entry=0x0, s=<optimized out>) at migration/block-dirty-bitmap.c:502 +#1 0x000055c5ba3b2878 in init_dirty_bitmap_migration (s=0x55c5bb11a080 <dbm_state>) at migration/block-dirty-bitmap.c:660 +#2 dirty_bitmap_save_setup (f=0x55c5bc981c40, opaque=0x55c5bb11a080 <dbm_state>) at migration/block-dirty-bitmap.c:1226 +#3 0x000055c5ba3a3c4d in qemu_savevm_state_setup (f=0x55c5bc981c40) at migration/savevm.c:1176 +#4 0x000055c5ba39e16b in migration_thread (opaque=opaque@entry=0x55c5bbaa2400) at migration/migration.c:3487 +#5 0x000055c5ba530cf3 in qemu_thread_start (args=<optimized out>) at util/qemu-thread-posix.c:521 +#6 0x00007f39846d9609 in start_thread (arg=<optimized out>) at pthread_create.c:477 +#7 0x00007f3983d11293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 +(gdb) p bs->node_name +$4 = "libvirt-2-format", '\000' <repeats 15 times> +(gdb) p bitmap->name +$5 = 0x55c5bbaf13d0 "bitmap0" +``` + +Set a breakpoint on the target side after hitting the breakpoint on the source side. + +``` +gdb -p $pid -ex "break serialization_chunk if ((start + count - 1) >> hb->granularity) >= hb->size" -ex "break dirty_bitmap_load_header" -ex "handle SIGUSR1 nostop" -ex "continue" +(gdb) bt +#0 dirty_bitmap_load_header (alias_map=0x0, s=0x557488aef0a8 <dbm_state+40>, f=0x55748bcfd8f0) at migration/block-dirty-bitmap.c:1146 +#1 dirty_bitmap_load (f=0x55748bcfd8f0, opaque=0x557488aef080 <dbm_state>, version_id=<optimized out>) at migration/block-dirty-bitmap.c:1187 +#2 0x0000557487d7759a in vmstate_load (se=0x55748adfb8b0, f=0x55748bcfd8f0) at migration/savevm.c:883 +#3 vmstate_load (f=0x55748bcfd8f0, se=0x55748adfb8b0) at migration/savevm.c:879 +#4 0x0000557487d79fdd in qemu_loadvm_section_part_end (mis=0x55748ad55be0, f=0x55748bcfd8f0) at migration/savevm.c:2365 +#5 qemu_loadvm_state_main (f=f@entry=0x55748bcfd8f0, mis=mis@entry=0x55748ad55be0) at migration/savevm.c:2518 +#6 0x0000557487d7b2ad in qemu_loadvm_state (f=0x55748bcfd8f0) at migration/savevm.c:2590 +#7 0x0000557487d7078f in process_incoming_migration_co (opaque=<optimized out>) at migration/migration.c:480 +#8 0x0000557487f15283 in coroutine_trampoline (i0=<optimized out>, i1=<optimized out>) at util/coroutine-ucontext.c:173 +#9 0x00007f5360189660 in __start_context () at ../sysdeps/unix/sysv/linux/x86_64/__start_context.S:91 +``` + +in dirty_bitmap_load_header + +``` +s->bs = bdrv_lookup_bs(s->node_name, s->node_name, &local_err); // node_name is "libvirt-2-format" +s->bitmap = bdrv_find_dirty_bitmap(s->bs, s->bitmap_name); // bitmap_name is "bitmap0" + +# Target side: “libvirt-2-format” is the node name of vdb. +(gdb) p s->bs->node_name +$10 = "libvirt-2-format", '\000' <repeats 15 times> +(gdb) p s->bs->filename +$11 = "/tmp/echohu3/vdb.qcow2", '\000' <repeats 4073 times> +``` + +We can also see from the target /var/log/libvirt/qemu/i-btacsctt.log file that “libvirt-2-format” is the node name of the vdb，while the node name of vda is libvirt-3-format. + +``` +-blockdev '{"driver":"file","filename":"/tmp/echohu3/vda.qcow2","aio":"threads","node-name":"libvirt-3-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ +-blockdev '{"node-name":"libvirt-3-format","read-only":false,"discard":"ignore","cache":{"direct":false,"no-flush":false},"driver":"qcow2","file":"libvirt-3-storage","backing":null}' \ +-device virtio-blk-pci,bus=pci.0,addr=0x2,drive=libvirt-3-format,id=virtio-disk0,bootindex=1,write-cache=on \ +-blockdev '{"driver":"file","filename":"/tmp/echohu3/vdb.qcow2","aio":"threads","node-name":"libvirt-2-storage","cache":{"direct":true,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ +-blockdev '{"node-name":"libvirt-2-format","read-only":false,"cache":{"direct":true,"no-flush":false},"driver":"qcow2","file":"libvirt-2-storage","backing":null}' \ +-device virtio-blk-pci,bus=pci.0,addr=0x3,drive=libvirt-2-format,id=virtio-disk1,write-cache=on \ +-blockdev '{"driver":"file","filename":"/tmp/echohu3/vdc.qcow2","aio":"threads","node-name":"libvirt-1-storage","cache":{"direct":true,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ +-blockdev '{"node-name":"libvirt-1-format","read-only":false,"discard":"ignore","cache":{"direct":true,"no-flush":false},"driver":"qcow2","file":"libvirt-1-storage","backing":null}' \ +``` + +From the source code, we know that HBitmap.size is from vdb size (2G), but bitmap is from vda (50G), so it triggers assert exception in serialization_chunk. + +``` +(gdb) bt +#0 serialization_chunk (hb=hb@entry=0x55748ba28470, start=2147483648, count=536870912, first_el=first_el@entry=0x7f53503ffd20, el_count=el_count@entry=0x7f53503ffd18) at util/hbitmap.c:610 +#1 0x0000557487f18654 in hbitmap_deserialize_zeroes (hb=0x55748ba28470, start=start@entry=2147483648, count=count@entry=536870912, finish=finish@entry=false) at util/hbitmap.c:701 +#2 0x0000557487e7cfb0 in bdrv_dirty_bitmap_deserialize_zeroes (bitmap=<optimized out>, offset=offset@entry=2147483648, bytes=bytes@entry=536870912, finish=finish@entry=false) at block/dirty-bitmap.c:749 +#3 0x0000557487d86b51 in dirty_bitmap_load_bits (s=0x557488aef0a8 <dbm_state+40>, f=0x55748bcfd8f0) at migration/block-dirty-bitmap.c:992 +#4 dirty_bitmap_load (f=0x55748bcfd8f0, opaque=0x557488aef080 <dbm_state>, version_id=<optimized out>) at migration/block-dirty-bitmap.c:1198 +#5 0x0000557487d7759a in vmstate_load (se=0x55748adfb8b0, f=0x55748bcfd8f0) at migration/savevm.c:883 +#6 vmstate_load (f=0x55748bcfd8f0, se=0x55748adfb8b0) at migration/savevm.c:879 +#7 0x0000557487d79fdd in qemu_loadvm_section_part_end (mis=0x55748ad55be0, f=0x55748bcfd8f0) at migration/savevm.c:2365 +#8 qemu_loadvm_state_main (f=f@entry=0x55748bcfd8f0, mis=mis@entry=0x55748ad55be0) at migration/savevm.c:2518 +#9 0x0000557487d7b2ad in qemu_loadvm_state (f=0x55748bcfd8f0) at migration/savevm.c:2590 +#10 0x0000557487d7078f in process_incoming_migration_co (opaque=<optimized out>) at migration/migration.c:480 +#11 0x0000557487f15283 in coroutine_trampoline (i0=<optimized out>, i1=<optimized out>) at util/coroutine-ucontext.c:173 +#12 0x00007f5360189660 in __start_context () at ../sysdeps/unix/sysv/linux/x86_64/__start_context.S:91 +#13 0x00007ffffb29c410 in () +#14 0x0000000000000000 in () +(gdb) p *hb +$16 = {orig_size = 2147483648, size = 32768, count = 0, granularity = 16, meta = 0x0, levels = {0x55748ad55ad0, 0x55748acd8df0, 0x55748b0866a0, 0x55748acf8c10, 0x55748b1c4180, 0x55748b154f60, 0x55748adf2370}, sizes = {1, 1, 1, 1, 1, 8, + 512}} +``` + +``` +(gdb) f 4 +#4 dirty_bitmap_load (f=0x55748bcfd8f0, opaque=0x557488aef080 <dbm_state>, version_id=<optimized out>) at migration/block-dirty-bitmap.c:1198 +(gdb) p *s->bs +$21 = {open_flags = 10274, read_only = false, encrypted = false, sg = false, probed = false, force_share = false, implicit = false, drv = 0x557488aa2ee0 <bdrv_qcow2>, opaque = 0x55748acf8c90, aio_context = 0x55748acd1080, + aio_notifiers = {lh_first = 0x0}, walking_aio_notifiers = false, filename = "/tmp/echohu3/vdb.qcow2", '\000' <repeats 4073 times>, backing_file = '\000' <repeats 4095 times>, auto_backing_file = '\000' <repeats 4095 times>, + backing_format = '\000' <repeats 15 times>, full_open_options = 0x55748b3c68e0, exact_filename = "/tmp/echohu3/vdb.qcow2", '\000' <repeats 4073 times>, backing = 0x0, file = 0x55748aa5de40, bl = {request_alignment = 1, + max_pdiscard = 0, pdiscard_alignment = 65536, max_pwrite_zeroes = 0, pwrite_zeroes_alignment = 65536, opt_transfer = 0, max_transfer = 0, min_mem_alignment = 512, opt_mem_alignment = 4096, max_iov = 1024}, supported_write_flags = 0, + supported_zero_flags = 260, supported_truncate_flags = 2, node_name = "libvirt-2-format", '\000' <repeats 15 times>, node_list = {tqe_next = 0x55748adeb060, tqe_circ = {tql_next = 0x55748adeb060, tql_prev = 0x55748ad4d0e8}}, + bs_list = {tqe_next = 0x55748adeb060, tqe_circ = {tql_next = 0x55748adeb060, tql_prev = 0x55748ad4d0f8}}, monitor_list = {tqe_next = 0x55748adeb060, tqe_circ = {tql_next = 0x55748adeb060, tql_prev = 0x55748ad4d108}}, refcnt = 2, + op_blockers = {{lh_first = 0x0} <repeats 16 times>}, inherits_from = 0x0, children = {lh_first = 0x55748aa5de40}, parents = {lh_first = 0x55748bbc0380}, options = 0x55748ad4d2d0, explicit_options = 0x55748ad525a0, + detect_zeroes = BLOCKDEV_DETECT_ZEROES_OPTIONS_OFF, backing_blocker = 0x0, total_sectors = 4194304, before_write_notifiers = {notifiers = {lh_first = 0x0}}, write_threshold_offset = 0, write_threshold_notifier = {notify = 0x0, node = { + le_next = 0x0, le_prev = 0x0}}, dirty_bitmap_mutex = {lock = {__data = {__lock = 0, __count = 0, __owner = 0, __nusers = 0, __kind = 0, __spins = 0, __elision = 0, __list = {__prev = 0x0, __next = 0x0}}, + __size = '\000' <repeats 39 times>, __align = 0}, initialized = true}, dirty_bitmaps = {lh_first = 0x55748b4655f0}, wr_highest_offset = {value = 0}, copy_on_read = 0, in_flight = 0, serialising_in_flight = 0, io_plugged = 0, + enable_write_cache = 0, quiesce_counter = 0, recursive_quiesce_counter = 0, write_gen = 0, reqs_lock = {locked = 0, ctx = 0x0, from_push = {slh_first = 0x0}, to_pop = {slh_first = 0x0}, handoff = 0, sequence = 0, holder = 0x0}, + tracked_requests = {lh_first = 0x0}, flush_queue = {entries = {sqh_first = 0x0, sqh_last = 0x55748ad52570}}, active_flush_req = false, flushed_gen = 0, never_freeze = false} +``` + +When we merge into commit https://gitlab.com/qemu-project/qemu/-/commit/31e4c354b38cd42a051ad030eb7779d5e7ee32fe and then run `block-bitmap-mapping` before migration, the hot migration can be completed successfully. I would like to confirm with the community whether this solution is reasonable and if there are any other solutions to address this issue. + +``` +virsh qemu-monitor-command i-btacsctt '{"execute": "migrate-set-parameters", "arguments":{"block-bitmap-mapping":[{"node-name":"libvirt-2-format", "alias":"libvirt-3-format","bitmaps":[{"name":"bitmap0", "alias":"bitmap0"}]}]}}' +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2651 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2651 new file mode 100644 index 000000000..53488b350 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2651 @@ -0,0 +1,8 @@ +MPC5553/MPC5554 Emulation (information request) +Additional information: +If it is not planned, I'll most likely start educating myself on this project to try and patch it in as it's a need that is quite important for me. +I'll try not to waste your time and read as much as I can about your guidelines. +Would you advise me against trying to do this? +I'd like to know how hard you think this will be. + +DISCLAIMER : I am still very much a newbie in embedded systems, I'm only in the first year of my master's degree in embedded systems. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2653 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2653 new file mode 100644 index 000000000..d1bef7bf6 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2653 @@ -0,0 +1 @@ +Intel iGPU sriov diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2658 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2658 new file mode 100644 index 000000000..2ebf32cf0 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2658 @@ -0,0 +1 @@ +How to simulate the L2MERRSR_EL1 register in KVM mode？ diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2659 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2659 new file mode 100644 index 000000000..d20090044 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2659 @@ -0,0 +1 @@ +msys2-64bit test-aio intermittent CI failure with "test_timer_schedule: assertion failed: (aio_poll(ctx, true)) FAIL" diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2660 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2660 new file mode 100644 index 000000000..8e12a2ac8 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2660 @@ -0,0 +1 @@ +EDK2 subhook submodule missing diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2664 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2664 new file mode 100644 index 000000000..ca968e0be --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2664 @@ -0,0 +1,9 @@ +Building in Windows MSYS2/Mingw64 fails +Description of problem: + +Steps to reproduce: +1. +2. +3. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2667 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2667 new file mode 100644 index 000000000..b50fc5a67 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2667 @@ -0,0 +1,212 @@ +Heavy graphic glitches when using Virtio with 3D acceleration +Description of problem: +Virtio with 3D acceleration enabled under "Video" and the corresponding OpenGL activated under "Display" with Spice leads to heavy artifacts in the graphical console. + +This error has been observed on Arch Linux with Intel Meteor Lake CPU (Intel Arc Graphics iGPU) as well as on OpenSuse Tumbleweed with Intel Kaby Lake CPU (Intel HD 630 iGPU) +Steps to reproduce: +1. Enable Virtio Graphics with 3D acceleration under "Video". +2. Activate the corresponding OpenGL under "Spice". +3. Start the VM and open the graphical console. +Additional information: + +(virtio without acceleration enabled) + + +(Same VM, same settings, but with 3D acceleration and OpenGL enabled) + + +(Same issue on a fresh install of OpenSuse Tumbleweed on a system that is in no way linked to the first one) + +``` +<domain type='kvm'> + <name>debian12</name> + <uuid>1d39d86a-b341-47bb-9847-4c78da9df863</uuid> + <metadata> + <libosinfo:libosinfo xmlns:libosinfo="http://libosinfo.org/xmlns/libvirt/domain/1.0"> + <libosinfo:os id="http://debian.org/debian/12"/> + </libosinfo:libosinfo> + </metadata> + <memory unit='KiB'>4194304</memory> + <currentMemory unit='KiB'>4194304</currentMemory> + <vcpu placement='static'>4</vcpu> + <os firmware='efi'> + <type arch='x86_64' machine='pc-q35-9.1'>hvm</type> + <firmware> + <feature enabled='no' name='enrolled-keys'/> + <feature enabled='no' name='secure-boot'/> + </firmware> + <loader readonly='yes' type='pflash'>/usr/share/edk2/x64/OVMF_CODE.4m.fd</loader> + <nvram template='/usr/share/edk2/x64/OVMF_VARS.4m.fd'>/var/lib/libvirt/qemu/nvram/debian12_VARS.fd</nvram> + <boot dev='hd'/> + </os> + <features> + <acpi/> + <apic/> + <vmport state='off'/> + </features> + <cpu mode='host-passthrough' check='none' migratable='on'/> + <clock offset='utc'> + <timer name='rtc' tickpolicy='catchup'/> + <timer name='pit' tickpolicy='delay'/> + <timer name='hpet' present='no'/> + </clock> + <on_poweroff>destroy</on_poweroff> + <on_reboot>restart</on_reboot> + <on_crash>destroy</on_crash> + <pm> + <suspend-to-mem enabled='no'/> + <suspend-to-disk enabled='no'/> + </pm> + <devices> + <emulator>/usr/bin/qemu-system-x86_64</emulator> + <disk type='file' device='disk'> + <driver name='qemu' type='qcow2' discard='unmap'/> + <source file='/var/lib/libvirt/images/debian12.qcow2'/> + <target dev='vda' bus='virtio'/> + <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> + </disk> + <disk type='file' device='cdrom'> + <driver name='qemu' type='raw'/> + <target dev='sda' bus='sata'/> + <readonly/> + <address type='drive' controller='0' bus='0' target='0' unit='0'/> + </disk> + <controller type='usb' index='0' model='qemu-xhci' ports='15'> + <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> + </controller> + <controller type='pci' index='0' model='pcie-root'/> + <controller type='pci' index='1' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='1' port='0x10'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> + </controller> + <controller type='pci' index='2' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='2' port='0x11'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> + </controller> + <controller type='pci' index='3' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='3' port='0x12'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> + </controller> + <controller type='pci' index='4' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='4' port='0x13'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> + </controller> + <controller type='pci' index='5' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='5' port='0x14'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> + </controller> + <controller type='pci' index='6' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='6' port='0x15'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x5'/> + </controller> + <controller type='pci' index='7' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='7' port='0x16'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x6'/> + </controller> + <controller type='pci' index='8' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='8' port='0x17'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x7'/> + </controller> + <controller type='pci' index='9' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='9' port='0x18'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0' multifunction='on'/> + </controller> + <controller type='pci' index='10' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='10' port='0x19'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x1'/> + </controller> + <controller type='pci' index='11' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='11' port='0x1a'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x2'/> + </controller> + <controller type='pci' index='12' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='12' port='0x1b'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x3'/> + </controller> + <controller type='pci' index='13' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='13' port='0x1c'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x4'/> + </controller> + <controller type='pci' index='14' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='14' port='0x1d'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x5'/> + </controller> + <controller type='sata' index='0'> + <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> + </controller> + <controller type='virtio-serial' index='0'> + <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> + </controller> + <interface type='network'> + <mac address='52:54:00:d6:22:67'/> + <source network='default'/> + <model type='virtio'/> + <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> + </interface> + <serial type='pty'> + <target type='isa-serial' port='0'> + <model name='isa-serial'/> + </target> + </serial> + <console type='pty'> + <target type='serial' port='0'/> + </console> + <channel type='unix'> + <target type='virtio' name='org.qemu.guest_agent.0'/> + <address type='virtio-serial' controller='0' bus='0' port='1'/> + </channel> + <channel type='spicevmc'> + <target type='virtio' name='com.redhat.spice.0'/> + <address type='virtio-serial' controller='0' bus='0' port='2'/> + </channel> + <input type='tablet' bus='usb'> + <address type='usb' bus='0' port='1'/> + </input> + <input type='mouse' bus='ps2'/> + <input type='keyboard' bus='ps2'/> + <graphics type='spice'> + <listen type='none'/> + <image compression='off'/> + <gl enable='yes'/> + </graphics> + <sound model='ich9'> + <address type='pci' domain='0x0000' bus='0x00' slot='0x1b' function='0x0'/> + </sound> + <audio id='1' type='spice'/> + <video> + <model type='virtio' heads='1' primary='yes'> + <acceleration accel3d='yes'/> + </model> + <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> + </video> + <redirdev bus='usb' type='spicevmc'> + <address type='usb' bus='0' port='2'/> + </redirdev> + <redirdev bus='usb' type='spicevmc'> + <address type='usb' bus='0' port='3'/> + </redirdev> + <watchdog model='itco' action='reset'/> + <memballoon model='virtio'> + <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> + </memballoon> + <rng model='virtio'> + <backend model='random'>/dev/urandom</backend> + <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> + </rng> + </devices> +</domain> +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2668 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2668 new file mode 100644 index 000000000..38d26c27b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2668 @@ -0,0 +1,3 @@ +h.264 encoding/compression support +Additional information: +noVNC now support h.264 decoding. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2670 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2670 new file mode 100644 index 000000000..6d7dcc5b4 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2670 @@ -0,0 +1,44 @@ +The virglrenderer depency causes qemu native recipe building to fail for NXP QEMU +Description of problem: +nativesdk-qemu-8.2.2.imx-r0 do_compile: oe_runmake failed +... + [87/4472] Compiling C object libcommon.fa.p/hw_display_virtio-gpu.c.o +| FAILED: libcommon.fa.p/hw_display_virtio-gpu.c.o +... + ../hw/display/virtio-gpu.c:36:10: fatal error: virglrenderer.h: No such file or directory +| 36 | #include <virglrenderer.h> +| | ^~~~~~~~~~~~~~~~~ +| compilation terminated. + +This issue was originally exposed after updating Yocto release to Scarthgap + +https://lists.yoctoproject.org/g/yocto/topic/building_sdk_fails_after/109275322 + +which seems to relate to commit https://github.com/nxp-imx/imx-qemu/commit/628105edbd816458dbf154a128cc3dd3ac809c7e that seemingly induces dependency to virglrenderer.h for virtio_gpu driver. + +Enabling opengl in our Distribution features is not a solution because that pulls in VGA graphics dependencies to our target binaries and we have no graphics hardware on our system. I have tried to disable the virglrenderer through QEMU build configuration but that does not fix the issue. +Steps to reproduce: +1. Clone NXP BSP Scarthgap +``` +$ mkdir nxp-bsp +$ cd nxp-bsp +nxp-bsp$ repo init -u https://github.com/nxp-imx/imx-manifest -b scarthgap -m imx-6.6.36-2.1.0.xml +nxp-bsp$ repo sync +``` + +2. Remove opengl from `fsl-imx-xwayland` DISTRO_FEATURES + +``` +sources/meta-imx/meta-imx-sdk/conf/distro/fsl-imx-wayland.conf: +... ++DISTRO_FEATURES:remove = "opengl " +... +``` + +3. Build qemu-native_8.2.2.imx + +``` +$ bitbake qemu-native_8.2.2.imx +``` +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2671 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2671 new file mode 100644 index 000000000..4016d3e0f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2671 @@ -0,0 +1,17 @@ +[Virtio-GPU Venus] I compiled virglrenderer with Venus support on 1.1.0,but could not boot QEMU with virtio-gpu Venus +Description of problem: +When I tried to use virtio-gpu-gl with venus=true like the template,it shows: +{width=1251 height=75} +But I have already compile virglrenderer using: + meson setup build \ + -Dvenus=true \ + -Drender-server=true \ + -Drender-server-worker=thread \ + -Dbuildtype=release \ + -Dprefix=${INSTDIR} + +and run QEMU with designated environment variables,but it still cannot boot,but if I use QEMU-8.0 with Venus-v17 patch and it works😭 +Steps to reproduce: +Just use "-device virtio-gpu-gl,hostmem=4G,blob=true,venus=true" and it will show the problem +Additional information: +No diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2676 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2676 new file mode 100644 index 000000000..0155be972 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2676 @@ -0,0 +1,7 @@ +GTK+ UI has serious problems on macOS hosts +Description of problem: +The GTK+ UI simply does not work on macOS at this stage. One major reason is that there does not appear to be any regular polling of the (macOS) UI event loop. The Cocoa back-end for GTK [sets a custom event polling function in GLib's event handler](https://gitlab.gnome.org/GNOME/gtk/-/blob/main/gdk/macos/gdkmacoseventsource.c?ref_type=heads#L1089) but Qemu never actually calls GLib/GTK's event polling. + +Thanks to @bonzini for discovering this as part of a [discussion on a patch generalising runloop event handling on macOS](https://patchew.org/QEMU/20241113142343.40832-1-phil@philjordan.eu/20241113142343.40832-2-phil@philjordan.eu/#CABgObfat1JwiBFNKHK6wwMkW5kgaqZfKJa=rW._5F9VvEdMWJR75A@mail.gmail.com). + +There is also a reasonable chance that QEMU might not reliably call GTK+ functions from the main thread (thread 0), which causes problems when GTK then calls through to the native Cocoa APIs which must be called from thread 0. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2677 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2677 new file mode 100644 index 000000000..a322bc312 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2677 @@ -0,0 +1 @@ +edit doc on building diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2678 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2678 new file mode 100644 index 000000000..93de13b01 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2678 @@ -0,0 +1,9 @@ +virsh blockcommit failed, however the snapshot was merged into base successfully. +Description of problem: + +Steps to reproduce: +1. +2. +3. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2679 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2679 new file mode 100644 index 000000000..f2af31030 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2679 @@ -0,0 +1 @@ +TCX emulation missing 1152x900 mode diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2680 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2680 new file mode 100644 index 000000000..d221febc6 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2680 @@ -0,0 +1,14 @@ +GTK accelerators (including releasing input grab) don't work in keyboard layouts that utilize AltGr on Windows +Description of problem: +With a non-QWERTY (in my case, Colemak) layout active, it's not possible to ungrab input from the window using the Ctrl-Alt-G. The key combination is simply ignored, whether the G is typed using the physical key G on the keyboard or the one where it would be mapped by the keyboard layout (physical T key for Colemak). Thankfully, because of #2225, the mouse cursor isn't actually captured, which allows me to move the mouse outside the window and close QEMU from the taskbar instead. + +Temporarily switching back to a QWERTY layout before the grab happens allows input to be released using the key combo. However this needs to be done before the capture as otherwise QEMU will simply intercept any shortcuts to toggle the layout. + +I suspect there's some mismatch between the input grabbing code and the GTK UI, where one is using the keyboard scancode to determine when to forward the key, but the GTK UI then uses the mapped letter from the layout and fails to activate the shortcut. +Steps to reproduce: +1. Configure a non-QWERTY layout (such as Dvorak or Colemak) in the system settings +1. Launch QEMU (it's not necessary to load any guest, booting the BIOS is fine) +2. Click on the window which will automatically capture input +3. Try to release using the Ctrl-Shift-G shortcut (in either layout), which should be ignored +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2681 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2681 new file mode 100644 index 000000000..d4288569b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2681 @@ -0,0 +1 @@ +QEMU build system should halt, if glib version is lower than needed diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2682 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2682 new file mode 100644 index 000000000..d7c4037fc --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2682 @@ -0,0 +1,41 @@ +QEMU throws errors at the beginning of building +Description of problem: +QEMU throws errors at the beginning of building: +``` +ninja: no work to do. +/tmp/qemu-8.1.5/build/pyvenv/bin/meson introspect --targets --tests --benchmarks | /tmp/qemu-8.1.5/build/pyvenv/bin/python3 -B scripts/mtest2make.py > Makefile.mtest +pc-bios/optionrom: -fcf-protection=none detected +pc-bios/optionrom: -fno-pie detected +pc-bios/optionrom: -no-pie detected +pc-bios/optionrom: -fno-stack-protector detected +pc-bios/optionrom: -Wno-array-bounds detected +pc-bios/optionrom: Assembling multiboot.o +pc-bios/optionrom: Assembling linuxboot.o +pc-bios/optionrom: Assembling multiboot_dma.o +pc-bios/optionrom: Compiling linuxboot_dma.o +pc-bios/optionrom: Assembling pvh.o +pc-bios/optionrom: Assembling kvmvapic.o +pc-bios/optionrom: Compiling pvh_main.o +pc-bios/optionrom: Linking multiboot.img +pc-bios/optionrom: Linking linuxboot.img +pc-bios/optionrom: Linking kvmvapic.img +pc-bios/optionrom: Extracting raw object multiboot.raw +/bin/sh: 1: -O: not found +make[1]: *** [Makefile:53: multiboot.raw] Error 127 +make[1]: *** Waiting for unfinished jobs.... +pc-bios/optionrom: Linking multiboot_dma.img +pc-bios/optionrom: Extracting raw object linuxboot.raw +/bin/sh: 1: -O: not found +make[1]: *** [Makefile:53: linuxboot.raw] Error 127 +make: *** [Makefile:190: pc-bios/optionrom/all] Error 2 +make: *** Waiting for unfinished jobs.... +[1/10003] Generating trace/trace-hw_i2c.h with a custom command + +... +``` +Then proceeds the building. Whether it is failing at the end is not reliabily reproducible as it do fail one time and builds successfully at the next time. However, i don't know if these errors will cause runtime problems in the case of a successful build. +Steps to reproduce: +1. `../configure --enable-strip --audio-drv-list=alsa --enable-tools --enable-modules` +2. `make -j16` +Additional information: +Configuration log is available here: http://oscomp.hu/depot/qemu-8.1.5-configure.log diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2684 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2684 new file mode 100644 index 000000000..6b147dd83 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2684 @@ -0,0 +1 @@ +scripts/archive-source.sh is not documented diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2686 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2686 new file mode 100644 index 000000000..b5e3e27cd --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2686 @@ -0,0 +1,48 @@ +rng-seed addition causing test_loongarch64_virt.py to hang in EFI startup +Description of problem: +Since the rng-seed addition, the test_loongarch64_virt.py test will periodically hang. + +git bisect blames this + +``` +commit d9bd1ccbf1d84d872aed684c65fec33814b8ac1b +Author: Jason A. Donenfeld <Jason@zx2c4.com> +Date: Thu Sep 5 17:33:16 2024 +0200 + + hw/loongarch: virt: pass random seed to fdt + + If the FDT contains /chosen/rng-seed, then the Linux RNG will use it to + initialize early. Set this using the usual guest random number + generation function. + + This is the same procedure that's done in b91b6b5a2c ("hw/microblaze: + pass random seed to fdt"), e4b4f0b71c ("hw/riscv: virt: pass random seed + to fdt"), c6fe3e6b4c ("hw/openrisc: virt: pass random seed to fdt"), + 67f7e426e5 ("hw/i386: pass RNG seed via setup_data entry"), c287941a4d + ("hw/rx: pass random seed to fdt"), 5e19cc68fb ("hw/mips: boston: pass + random seed to fdt"), 6b23a67916 ("hw/nios2: virt: pass random seed to fdt") + c4b075318e ("hw/ppc: pass random seed to fdt"), and 5242876f37 + ("hw/arm/virt: dt: add rng-seed property"). + + These earlier commits later were amended to rerandomize the RNG seed on + snapshot load, but the LoongArch code somehow already does that, despite + not having this patch here, presumably due to some lucky copy and + pasting. + + Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com> + Reviewed-by: Song Gao <gaosong@loongson.cn> + Message-Id: <20240905153316.2038769-1-Jason@zx2c4.com> + Signed-off-by: Song Gao <gaosong@loongson.cn> +``` + +When it hangs, test_loongarch64_virt.py will get stuck waiting for serial console output from the guest. + +Looking at the console.log file shows it to be completely empty. + +This appears to indicate it has hung before EDK has even initialized, as it has not even printed the 'Entering C environment' message +Steps to reproduce: +1. ./configure --target-list=loongarch64-softmmu +2. make -j 20 +3. n=0 ; while true ; do n=$(expr $n + 1); echo $n ; QEMU_TEST_QEMU_BINARY=./build/qemu-system-loongarch64 PYTHONPATH=./python ./tests/functional/test_loongarch64_virt.py ; done + +Most commonly it will hang within 10 iterations, very occasionally needing upto 25 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2687 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2687 new file mode 100644 index 000000000..cffe5d989 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2687 @@ -0,0 +1,49 @@ +regression in qtest clock_set/clock_step +Description of problem: +As of QEMU 9.0 the script included below would increment the time via qtest, but it is now broken and time doesn't seem to be updated. I do note that the QEMU sources use clock_step extensively via qtest_clock_step, but nothing seems to be using the return value so maybe that's why it hasn't been noticed? + +It seems to have been broken in bc02be4508d8753d1f6071b77d10f4661587df6f which was trying to prevent some deadlock. You can prove that this breaks it by setting a breakpoint in `qemu_virtual_clock_set_ns` -- it never gets called. +Steps to reproduce: +Run this python script from your QEMU build directory: + +```python +#!/usr/bin/env python3 + +import subprocess +import socket +import typing + +qemu_path = "./qemu-system-x86_64" + + +def main(): + s1, s2 = socket.socketpair() + + qemu = subprocess.Popen( + [ + qemu_path, + "-S", + "-display", + "none", + "-chardev", f"socket,id=qtest,fd={s1.fileno()},nodelay=on", + "-qtest", "chardev:qtest", + "-qtest-log", "/dev/fd/2", + "-accel", "qtest", + ], + pass_fds=[s1.fileno()], + ) + + try: + + fp = s2.makefile("rw", buffering=1) + + fp.write(f"clock_set 1234\n") + result = fp.readline()[:-1].split(" ") + assert result == ["OK", "1234"], f"Unexpected result: {result}" + finally: + qemu.kill() + + +if __name__ == "__main__": + main() +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2688 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2688 new file mode 100644 index 000000000..82196e3f8 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2688 @@ -0,0 +1 @@ +Add `disable_host_loopback` for network user backend diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2690 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2690 new file mode 100644 index 000000000..baf3b4652 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2690 @@ -0,0 +1,20 @@ +"Guest says index 40947 is available" +Description of problem: +As discussed [here](https://github.com/danobi/vmtest/issues/96) I have been running several instances of QEMU in parallel at `SCHED_IDLE`, and I've been getting QGA setup failures. +Steps to reproduce: +1. Install [vmtest](https://github.com/danobi/vmtest) +2. Run lots of copies of the command in the [github issues](https://github.com/danobi/vmtest/issues/96) via `chrt --idle 0`. +3. Unclear if this is the cause, but then I use the computer in the meantime so probably starve the `SCHED_IDLE` QEMU threads running from 2. + +This leads to failures to connect to the guest agent and then at the end I see this: + +``` +Guest says index 40947 is available + qemu-system-x86_64: Guest says index 40947 is available + qemu-system-x86_64: Guest says index 40947 is available +``` + + +The developer of vmtest seemed to think this may be of interest to QEMU developers based on the tone of the [comment they found](https://github.com/danobi/vmtest/issues/96#issuecomment-2483860554) in the QEMU code. + +I've now installed QEMU from Git master so I can report back whether the bug still appeared. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2693 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2693 new file mode 100644 index 000000000..f564d4edf --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2693 @@ -0,0 +1,6 @@ +hv-balloon Migration +Description of problem: +since QEMU version 8.2, the hv-balloon feature has been officially merged, but migration is still not supported. +Are there any planned enhancements to the hv-balloon migration in the near future? +Steps to reproduce: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2694 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2694 new file mode 100644 index 000000000..7d6c2a1ea --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2694 @@ -0,0 +1,24 @@ +error: implicit declaration of function 'IOMainPort' is invalid in C99 +Description of problem: +Build in MacOS + Hardware Overview: + + Model Name: MacBook Air + Chip: Apple M1 + Total Number of Cores: 8 (4 performance and 4 efficiency) + Memory: 16 GB +Steps to reproduce: +1. ./configure --cpu=aarch64 --target-list=aarch64-softmmu --enable-slirp +2. make -j +Additional information: +``` +FAILED: libblock.a.p/block_file-posix.c.o +cc -Ilibblock.a.p -I. -I.. -Iqapi -Itrace -Iui -Iui/shader -Iblock -I/opt/homebrew/opt/zstd/include -I/opt/homebrew/Cellar/glib/2.82.2/include/glib-2.0 -I/opt/homebrew/Cellar/glib/2.82.2/lib/glib-2.0/include -I/opt/homebrew/opt/gettext/include -I/opt/homebrew/Cellar/pcre2/10.44/include -I/opt/homebrew/Cellar/glib/2.82.2/include -fdiagnostics-color=auto -Wall -Winvalid-pch -std=gnu11 -O2 -g -fstack-protector-strong -Wempty-body -Wendif-labels -Wexpansion-to-defined -Wformat-security -Wformat-y2k -Wignored-qualifiers -Winit-self -Wmissing-format-attribute -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wredundant-decls -Wstrict-prototypes -Wtype-limits -Wundef -Wvla -Wwrite-strings -Wno-gnu-variable-sized-type-not-at-end -Wno-initializer-overrides -Wno-missing-include-dirs -Wno-psabi -Wno-shift-negative-value -Wno-string-plus-int -Wno-tautological-type-limit-compare -Wno-typedef-redefinition -iquote . -iquote /Users/august/qemu/src -iquote /Users/august/qemu/src/include -iquote /Users/august/qemu/src/host/include/aarch64 -iquote /Users/august/qemu/src/host/include/generic -iquote /Users/august/qemu/src/tcg/aarch64 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -fno-strict-aliasing -fno-common -fwrapv -fno-pie -MD -MQ libblock.a.p/block_file-posix.c.o -MF libblock.a.p/block_file-posix.c.o.d -o libblock.a.p/block_file-posix.c.o -c ../block/file-posix.c +../block/file-posix.c:3940:18: error: implicit declaration of function 'IOMainPort' is invalid in C99 [-Werror,-Wimplicit-function-declaration] + kernResult = IOMainPort(MACH_PORT_NULL, &mainPort); + ^ +1 error generated. +ninja: build stopped: subcommand failed. +make[1]: *** [run-ninja] Error 1 +make: *** [build] Error 2 +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2695 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2695 new file mode 100644 index 000000000..5fb21c01a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2695 @@ -0,0 +1,3 @@ +how to onboard fw_cfg to other machines +Additional information: +Would it be doable for other machines actually? I didn't dig deeper into this device to understand, but I guess it is connected to the VM somehow and it has some memory mapped to the OS? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2697 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2697 new file mode 100644 index 000000000..3e70f439b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2697 @@ -0,0 +1 @@ +system/physmem: gdb memory rw no access on armv7m MPU diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/270 b/gitlab/issues_text/target_missing/host_missing/accel_missing/270 new file mode 100644 index 000000000..82d6aedc1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/270 @@ -0,0 +1 @@ +virtio only support packed ring size power of 2 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2700 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2700 new file mode 100644 index 000000000..ae5f2f5b1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2700 @@ -0,0 +1,8 @@ +Windows 11 24H2 (x64) fails to boot +Description of problem: +When trying to boot Windows 11 24H2 (including the installer), the guest will just restart. +Steps to reproduce: +1. Download Windows 11 ISO from: https://www.microsoft.com/en-us/software-download/windows11 +2. Run the command above +Additional information: +I tested it on an M4 Pro Mac running TCG. Other users have reported the same issue with M3 running TCG and Intel i9 running HVF. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2701 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2701 new file mode 100644 index 000000000..20d8c3e4a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2701 @@ -0,0 +1 @@ +VGPU migration under VFIO. nvidia-vgpu-mgr: Error saving page in pipelined mode on 550.90.05 driver (Debian12,libvirt 10.5.0 qemu 9.1.1) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2703 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2703 new file mode 100644 index 000000000..e3e129c53 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2703 @@ -0,0 +1,40 @@ +ptimer period sporadically too long +Description of problem: +A ptimer in a custom device with a frequency of 10kHz is sporadically called after more than 100,000ns in virtual time have elapsed. + +With a icount shift of 4 or 5 this happens almost everytime before the linux guest can even finish booting. + +With a shift of 0 this happens very rarely, but it does occur from time to time. +Steps to reproduce: +1. setup a ptimer with a frequency of 10kHz and assert that the time passed between callbacks is exactly 100,000ns +2. run +3. wait for boom +Additional information: +``` +// Timer setup +ptimer_transaction_begin(state->timer); + +ptimer_set_freq(state->timer, 10000); +ptimer_run(state->timer, 0); + +ptimer_transaction_commit(state->timer); +``` +``` +// timer callback +int64_t now = qemu_clock_get_ns(QEMU_CLOCK_VIRTUAL); +static int64_t last = 0; +if (last > 0) +{ + if (now - last != 100000) + { + fprintf(stderr, "error tick %ld after %ld is incorrect: %ld\n", now, last, now - last); + assert(0); + } +} +last = now; +``` + +``` +error tick 47867503135 after 47867400000 is incorrect: 103135 +qemu-system-x86_64: ../...file.c:119: timer_callback: Assertion `0' failed. +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2705 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2705 new file mode 100644 index 000000000..2d2b7cb70 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2705 @@ -0,0 +1,17 @@ +USB event delivery does not work correctly for macOS guests with XHCI controller without MSI(-X) +Steps to reproduce: +1. Get a macOS VM working. Either on x86-64 with a Q35 machine type, AppleSMC device, and OpenCore bootloader, or on aarch64 using the patch set and instructions linked above. +2. On x86-64, switch to a NEC XHCI controller with MSI and MSI-X support forcibly disabled: `-device nec-usb-xhci,id=xhci,msi=off,msix=off` +3. Boot macOS. + +USB events are now extremely laggy. A USB keyboard or mouse becomes almost unusable. + + +While narrowing down the problem, I established the following facts by experimentation, tracing, and code inspection: + + * Although the vmapple platform uses an emulated XHCI PCI device for connecting virtual USB devices, it does not support message-signalled interrupts, in either the MSI or MSI-X persuasion. (This is true in Apple's implementation as well, but the macOS guest's XHCI driver unsurprisingly does work with Apple's PCI/XHCI implementation.) + * macOS guests (and the iBoot bootloader) appear to refuse to drive XHCI controllers with `numintrs < 4`, for both aarch64 and x86-64 architectures. They will generally set up event rings 0, 1, and 2. + * QEMU's PCI XHCI implementation does not appear to implement (as of 9.2.0-rc2) any mitigations for when the controller is used in pin-based IRQ mode. It will happily attempt to use event rings >0 in this case, but interrupts are dropped. + * Linux and FreeBSD guests appear to use only interrupter 0 anyway, so these are not useful references. + +It's not entirely clear to me what component is ultimately responsible for the failure here - I suspect there might be some not-quite-right behaviour in both macOS's XHCI driver and Qemu's XHCI implementation, and that these conspire to a non-functional setup. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2706 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2706 new file mode 100644 index 000000000..230fd499f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2706 @@ -0,0 +1 @@ +MigrationCapability "dirty-bitmaps off" diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2707 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2707 new file mode 100644 index 000000000..7a5f25aee --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2707 @@ -0,0 +1,10 @@ +virtio-balloon crashes in a object assert when querying stats +Description of problem: +Fetch virtio-balloon stats will crash a QEMU crash with assert failures +Steps to reproduce: +1. ./qemu-system-x86_64 -device virtio-balloon,id=balloon -qmp qmp.sock +2. Connect to qmp.sock +3. Issue 'qom-get path=/machine/peripheral/balloon property=guest-stats' +4. QEMU go boom! +Additional information: +This is a regression caused by commit 0d2eeef77a33315187df8519491a900bde4a3d83, which failed to update `balloon_stat_names` with the new stats names, causing code to try to add a QDict entry with a NULL key. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2709 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2709 new file mode 100644 index 000000000..841ff0e5b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2709 @@ -0,0 +1 @@ +Contributing to docs is very confusing diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2714 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2714 new file mode 100644 index 000000000..7c04645cf --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2714 @@ -0,0 +1,7 @@ +Potential memory leak in virtio-crytpto +Description of problem: +There is a potential memory leak while using virtio-crypto with vhost-user backend. + +The problem is due to misuse of error_setg in [backends/cryptodev-vhost-user.c#L284](https://gitlab.com/qemu-project/qemu/-/blob/master/backends/cryptodev-vhost-user.c#L284). After invoking error_setg(&local_error, ...), current procedure should not return without freeing err object pointed by local_error. + +The same problem occured in cryptodev-builtin, which has been discussed in #2283 and fixed in f6abce29cc4afa0445cb3b29a265a114ac9fa744. The same fixes should be applied to cryptodev-vhost-user. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2716 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2716 new file mode 100644 index 000000000..54f28314f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2716 @@ -0,0 +1,7 @@ +migrate incoming with fd transfer issue +Steps to reproduce: +1. +2. +3. +Additional information: +# diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2717 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2717 new file mode 100644 index 000000000..980caff09 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2717 @@ -0,0 +1,12 @@ +semihosting link to risc-v details in document is changed +Description of problem: + +Steps to reproduce: +1. Open https://gitlab.com/qemu-project/qemu/-/blob/master/docs/about/emulation.rst +2. Goto Supported Targets section +3. Click RISC-V link in the table +4. Got 404 + +New url looks like https://github.com/riscv-non-isa/riscv-semihosting/blob/main/riscv-semihosting.adoc +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2719 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2719 new file mode 100644 index 000000000..55be575f7 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2719 @@ -0,0 +1 @@ +9.2.0 tarball contains unrelated files diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/272 b/gitlab/issues_text/target_missing/host_missing/accel_missing/272 new file mode 100644 index 000000000..d8051bc93 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/272 @@ -0,0 +1 @@ +QEMU: block/vvfat driver issues diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2720 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2720 new file mode 100644 index 000000000..9438fedb9 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2720 @@ -0,0 +1,70 @@ +migration failure from qemu 7.1.0 to qemu 9.2.0+ with multifd capability enabled +Description of problem: +Enabling multifd when doing migration from qemu 7.1.0 to 9.2.0+ causes the migration to fail. +The migration status reported is: + +``` +Migration status: failed (Unable to write to socket: Broken pipe) +``` + +I could reproduce on qemu 9.2.0 and from a build from master. The migration is successful if I don't enable multifd. + +I could not reproduce this issue migrating from 7.1.0 to 9.1.2. +Steps to reproduce: +Minimal setup to reproduce below, running both qemu instances on the same host. + +1. Start qemu instance receiving the migration: + +``` +$ qemu-system-x86_64 -version +QEMU emulator version 9.2.50 (v9.2.0-28-ga5ba0a7e4e) + +$ qemu-system-x86_64 -M pc-q35-7.1 -m 16G -nographic -incoming defer -net none -trace 'migration*' +[...] +(qemu) migrate_set_capability multifd on +(qemu) migrate_set_parameter multifd-channels 4 +(qemu) migrate_incoming tcp:0:12345 +[...] +(qemu) migration_socket_incoming_accepted +migration_set_incoming_channel ioc=0x5619735b1800 ioctype=qio-channel-socket +migration_socket_incoming_accepted +migration_set_incoming_channel ioc=0x561972dff670 ioctype=qio-channel-socket +migration_socket_incoming_accepted +migration_set_incoming_channel ioc=0x561972dad800 ioctype=qio-channel-socket +migration_socket_incoming_accepted +migration_set_incoming_channel ioc=0x561972c9d670 ioctype=qio-channel-socket +migration_socket_incoming_accepted +migration_set_incoming_channel ioc=0x561972c7b270 ioctype=qio-channel-socket + +``` + +2. Start the qemu instance that will be used to initiate the migration with multifd enabled, and initiate the migration + +``` +$ qemu-system-x86_64 -version +QEMU emulator version 7.1.0 (v7.1.0) + +$ qemu-system-x86_64 -M pc-q35-7.1 -m 16G -nographic -net none -trace 'migration*' +[...] +(qemu) migrate_set_capability multifd on +(qemu) migrate_set_parameter multifd-channels 4 +(qemu) migrate -d tcp:0:12345 +(qemu) migration_socket_outgoing_connected hostname=0 +migration_set_outgoing_channel ioc=0x558ea2051400 ioctype=qio-channel-socket hostname=0 err=(nil) +migration_bitmap_sync_start +migration_bitmap_sync_end dirty_pages 0 +migration_thread_setup_complete +migration_bitmap_clear_dirty rb pc.ram start 0x0 size 0x40000000 page 0x0 +migration_thread_after_loop +qemu-system-x86_64: Unable to write to socket: Broken pipe +(qemu) info migrate +globals: +store-global-state: on +only-migratable: off +send-configuration: on +send-section-footer: on +decompress-error-check: on +clear-bitmap-shift: 18 +Migration status: failed (Unable to write to socket: Broken pipe) +total time: 0 ms +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2722 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2722 new file mode 100644 index 000000000..5cd09cff3 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2722 @@ -0,0 +1,48 @@ +TLB Invalidation time out on i915 SR-IOV passthrough +Description of problem: +Hello, + +I tried to use SR-IOV on i915 driver freshly available on the [LTS intel kernel](https://github.com/intel/linux-intel-lts) with this [kernel version ](https://github.com/intel/linux-intel-lts/tree/lts-v6.6.34-linux-240626T131354Z) for pci passthrough purpose. +After setting up SR-IOV (kernel compilation, kernel cmdline, vfio-pci driver attribution to the new pci..) + I've got my two new pci. + +``` +00:02.0 VGA compatible controller: Intel Corporation Alder Lake-P Integrated Graphics Controller (rev 0c) +DeviceName: Onboard IGD + +Subsystem: Hewlett-Packard Company Alder Lake-P Integrated Graphics Controller +Kernel driver in use: i915 + +00:02.1 VGA compatible controller: Intel Corporation Alder Lake-P Integrated Graphics Controller (rev 0c) +Subsystem: Hewlett-Packard Company Alder Lake-P Integrated Graphics Controller +Kernel driver in use: vfio-pci + +00:02.2 VGA compatible controller: Intel Corporation Alder Lake-P Integrated Graphics Controller (rev 0c) +Subsystem: Hewlett-Packard Company Alder Lake-P Integrated Graphics Controller +Kernel driver in use: vfio-pci +``` +I gave one of those pci to my VM with this qemu cmdline: +``` +-cpu host,migratable=on,hv-time,hv-relaxed,hv-vapic,hv-spinlocks=0x1fff,hv-passthrough,hv-vendor-id=IrisXE +... +-device vfio-pci-nohotplug,host=0000:00:02.1,id=hostdev0,bus=pci.4,addr=0x0 +``` +Sometimes it working properly when I start the qemu cmdline but most of the time I've got those kernel errors and a GPU hang: +``` + kernel [ 2252.208134] i915 0000:00:02.0: [drm] ERROR GT0: GUC: TLB invalidation response timed out for seqno 9679 + kernel [ 2252.208134] i915 0000:00:02.0: [drm] ERROR GT0: GUC: TLB invalidation response timed out for seqno 9679 + kernel i915 0000:00:02.0: [drm] ERROR GT0: GUC: TLB invalidation response timed out for seqno 9679 + kernel i915 0000:00:02.0: [drm] ERROR GT0: GUC: TLB invalidation response timed out for seqno 9679 + .... + kernel Fence expiration time out i915-0000:00:02.0:renderThread22381:6e0! + kernel i915 0000:00:02.0: [drm] GT0: GuC firmware i915/adlp_guc_70.bin version 70.13.1 + kernel i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3 + kernel i915 0000:00:02.0: [drm] GT0: HuC: authenticated for all workloads + kernel i915 0000:00:02.0: [drm] GT0: GUC: submission enabled + kernel i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled + kernel [ 2730.991019] i915 0000:00:02.0: [drm] GPU HANG: ecode 12:1:85dfbfff, in renderThread [22381] + kernel [ 2730.991084] i915 0000:00:02.0: [drm] renderThread22381 context reset due to GPU hang +``` +It mostly appears when Qemu is starting.. + +Any help would be appreciate, thanks a lot diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2724 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2724 new file mode 100644 index 000000000..459be653a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2724 @@ -0,0 +1,8 @@ +Invalid DRM modifier in ScanoutDMABUF call +Description of problem: +`modifier` parameter in `ScanoutDMABUF` callback is always `0xffffffffffffff` (`DRM_FORMAT_RESERVED`) +Steps to reproduce: +1. Run QEMU with D-Bus display +2. Connect D-Bus display client and print modifier +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2726 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2726 new file mode 100644 index 000000000..ab29ea849 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2726 @@ -0,0 +1 @@ +please make qemu-img capable of using with pipes diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2727 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2727 new file mode 100644 index 000000000..031d10dec --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2727 @@ -0,0 +1 @@ +`Debian testing` (2024-12-16) - `qemu-system-x86_64 9.2.0` : bug with the `virtio-net` and a DHCP connection with a virtual bridge. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2728 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2728 new file mode 100644 index 000000000..3fbee1773 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2728 @@ -0,0 +1,15 @@ +QEMU/Virt-Manager + QXL 4k Resolution + Win 10 and Win 11 Guest freeze +Description of problem: +I use two 4k displays in my VM with 150% display scaling. After a random amount of time the screen locks up. It can lock up before i can log in or it can wait a few minutes into using it before it stops responding. It still pings but is unresponsive via the display. I've tried several different builds of the guest drivers but that did not work, the only solution has been to revert to QEMU v9.0.2-1. +Steps to reproduce: +1.Create new x86 VM using QXl video, Install Windows 10 or Windows 11 and latest guest drivers from spice and fedora +2.Open with virt viewer and resize both screens to 3840 x 2160 or use autosize +3.Set display scaling to 150% +4.Lockup occurs at some point after that but not more than 5 minutes. +Additional information: +There seems to be a similar bug here:https://gitlab.com/qemu-project/qemu/-/issues/1628#note_214460662 +also a debian forum post here: https://forums.debian.net/viewtopic.php?t=160631 +QEMU v9.0.2-1 does not have this problem, eliminating the guest drivers as a culprit + + +/label ~"kind::Bug" diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/273 b/gitlab/issues_text/target_missing/host_missing/accel_missing/273 new file mode 100644 index 000000000..5549ef899 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/273 @@ -0,0 +1 @@ +xhci_find_stream: Assertion `streamid != 0' failed. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2732 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2732 new file mode 100644 index 000000000..b640373be --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2732 @@ -0,0 +1,39 @@ +Segmentation fault with PCI GPU +Description of problem: +Upon attempting to launch the virtual machine, Qemu crashes with Segfault. The issue only occurs it's launched with a passthrough GPU with the vfio driver. It is an Nvidia RTX 3060 GPU. The VM boots fine without the GPU PCI device added. +Steps to reproduce: +1. Create a VM with the GPU PCI device added +2. Attempt to boot it +3. virt-manager will display: "libvirt.libvirtError: internal error: QEMU unexpectedly closed the monitor" +Additional information: +GDB backtrace: +``` +Thread 1 "qemu-system-x86" received signal SIGSEGV, Segmentation fault. +Downloading 116.51 K source file /usr/src/debug/qemu/build/../qemu-9.1.2/system/memory.c +memory_region_update_container_subregions () at ../qemu-9.1.2/system/memory.c:2616 +2616 QTAILQ_FOREACH(other, &mr->subregions, subregions_link) { +(gdb) bt +#0 memory_region_update_container_subregions () at ../qemu-9.1.2/system/memory.c:2616 +#1 memory_region_add_subregion_common () at ../qemu-9.1.2/system/memory.c:2640 +#2 0x0000555555ade66a in memory_region_add_subregion_overlap () at ../qemu-9.1.2/system/memory.c:2657 +#3 vfio_probe_nvidia_bar0_quirk () at ../qemu-9.1.2/hw/vfio/pci-quirks.c:966 +#4 vfio_bar_quirk_setup () at ../qemu-9.1.2/hw/vfio/pci-quirks.c:1259 +#5 0x0000555555ae8212 in vfio_realize () at ../qemu-9.1.2/hw/vfio/pci.c:3133 +#6 0x000055555586c3ab in pci_qdev_realize () at ../qemu-9.1.2/hw/pci/pci.c:2097 +#7 0x0000555555b924f3 in device_set_realized () at ../qemu-9.1.2/hw/core/qdev.c:510 +#8 0x0000555555b9c37f in property_set_bool () at ../qemu-9.1.2/qom/object.c:2354 +#9 0x0000555555b9a21a in object_property_set () at ../qemu-9.1.2/qom/object.c:1463 +#10 0x0000555555b9abbf in object_property_set_qobject () at ../qemu-9.1.2/qom/qom-qobject.c:28 +#11 object_property_set_bool () at ../qemu-9.1.2/qom/object.c:1533 +#12 0x000055555594dafb in qdev_device_add_from_qdict () at ../qemu-9.1.2/system/qdev-monitor.c:719 +#13 0x00005555559586f1 in qemu_create_cli_devices () at ../qemu-9.1.2/system/vl.c:2664 +#14 qmp_x_exit_preconfig () at ../qemu-9.1.2/system/vl.c:2721 +#15 0x0000555555962396 in qemu_init () at ../qemu-9.1.2/system/vl.c:3766 +#16 0x00005555556d2abd in main () at ../qemu-9.1.2/system/main.c:47 +``` + +dmesg: +``` +[ 4846.200960] qemu-system-x86[26518]: segfault at b8 ip 00006149e75a64e6 sp 00007fff4c85fbe0 error 4 in qemu-system-x86_64[5c24e6,6149e7155000+72c000] likely on CPU 4 (core 4, socket 0) +[ 4846.200968] Code: 2e 01 83 c0 01 89 05 0d cd 2e 01 48 8b 43 40 48 85 c0 74 16 ba 01 00 00 00 f0 0f c1 50 18 81 fa fe ff ff 7f 0f 87 c4 00 00 00 <49> 8b 84 24 b8 00 00 00 48 85 c0 74 55 8b 93 b0 00 00 00 eb 11 0f +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2735 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2735 new file mode 100644 index 000000000..b60957801 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2735 @@ -0,0 +1,10 @@ +Couldn't find rom image 'canon-a1100-rom1.bin'. +Description of problem: +``` +$ qemu-system-aarch64 -machine canon-a1100 +qemu-system-aarch64: Couldn't find rom image 'canon-a1100-rom1.bin'. +``` +Steps to reproduce: +``` +qemu-system-aarch64 -machine canon-a1100 +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2737 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2737 new file mode 100644 index 000000000..f3659b496 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2737 @@ -0,0 +1 @@ +Plans for Adding RISC-V Vector (RVV) Backend Support? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/274 b/gitlab/issues_text/target_missing/host_missing/accel_missing/274 new file mode 100644 index 000000000..639aeeb5d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/274 @@ -0,0 +1 @@ +FIXME xhci_alloc_device_streams:972 guest streams config not identical for all eps diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2740 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2740 new file mode 100644 index 000000000..409e61fd5 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2740 @@ -0,0 +1,67 @@ +Out-of-bounds access and heap-use-after-free in smc91c111_writeb() +Description of problem: +An out-of-bounds access bug was triggered by my fuzzer. + +The error is: + +``` +../hw/net/smc91c111.c:457:17: runtime error: index 48 out of bounds for type 'uint8_t[4][2048]' (aka 'unsigned char[4][2048]') +SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior ../hw/net/smc91c111.c:457:17 in +================================================================= +==60006==ERROR: AddressSanitizer: heap-use-after-free on address 0x6290000385b4 at pc 0x5de3d1ac6add bp 0x7ffc4d4b2b30 sp 0x7ffc4d4b2b28 +WRITE of size 1 at 0x6290000385b4 thread T0 +warning: DWARF unit at offset 0x00417a37 has unsupported address size: 31 (supported are 2, 4, 8) + #0 0x5de3d1ac6adc in smc91c111_writeb smc91c111.c + #1 0x5de3d1abf6e3 in smc91c111_writefn smc91c111.c + #2 0x5de3d2d9e2d3 in memory_region_write_accessor memory.c + #3 0x5de3d2d9da4a in access_with_adjusted_size memory.c + #4 0x5de3d2d9ce78 in memory_region_dispatch_write + #5 0x5de3d2df5e44 in flatview_write_continue_step physmem.c + #6 0x5de3d2de2d40 in flatview_write physmem.c + #7 0x5de3d2de29d7 in address_space_write + ... + +0x6290000385b4 is located 5044 bytes inside of 16176-byte region [0x629000037200,0x62900003b130) +freed by thread T0 here: + #0 0x5de3d1100027 in __interceptor_free.part.0 asan_malloc_linux.cpp + #1 0x5de3d2f35106 in object_unref + #2 0x5de3d24ac45c in qemu_get_nic_models + #3 0x5de3d24acead in qemu_create_nic_bus_devices + #4 0x5de3d2722553 in realview_init realview.c + #5 0x5de3d1468182 in machine_run_board_init + #6 0x5de3d237e40a in qmp_x_exit_preconfig + #7 0x5de3d238505c in qemu_init + ... + +previously allocated by thread T0 here: + #0 0x5de3d1101217 in malloc + #1 0x7ea39d40a738 in g_malloc + #2 0x5de3d24acead in qemu_create_nic_bus_devices + #3 0x5de3d2722553 in realview_init realview.c + #4 0x5de3d1468182 in machine_run_board_init + #5 0x5de3d237e40a in qmp_x_exit_preconfig + #6 0x5de3d238505c in qemu_init + ... +``` +Steps to reproduce: +``` +export QEMU_ARGS="-display none -machine accel=qtest, -m 512M -machine realview-eb" +cat << EOF | ./qemu-system-arm $QEMU_ARGS -qtest /dev/null -qtest stdio +clock_step +readw 0x4e000000 +readw 0x4e000000 +clock_step +writel 0x4e00000c 0x2402e660 +readb 0x4e000008 +readl 0x4e000000 +clock_step +readb 0x4e000000 +writel 0x4e000000 0x66308c81 +writew 0x4e000008 0xe40ba4c +readb 0x4e000000 +readw 0x4e000000 +readl 0x4e000008 +EOF +``` +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2742 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2742 new file mode 100644 index 000000000..8faf42a01 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2742 @@ -0,0 +1,66 @@ +heap-buffer-overflow in smc91c111_do_tx() +Description of problem: +A buffer-overflow bug was triggered by my fuzzer at smc91c111_do_tx(). + +I've patched hw/net/smc91c111.c with: + +``` +diff --git a/hw/net/smc91c111.c b/hw/net/smc91c111.c +index 702d0e8e83..286298bf06 100644 +--- a/hw/net/smc91c111.c ++++ b/hw/net/smc91c111.c +@@ -429,7 +429,7 @@ static void smc91c111_writeb(void *opaque, hwaddr offset, + /* Ignore. */ + return; + case 2: /* Packet Number Register */ +- s->packet_num = value; ++ s->packet_num = value & (NUM_PACKETS - 1); + return; + case 3: case 4: case 5: + /* Should be readonly, but linux writes to them anyway. Ignore. */ +``` + +The error is: + +``` +==2724739==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x629000022941 at pc 0x595ebbed687b bp 0x7fffa0098a50 sp 0x7fffa0098a48 +READ of size 1 at 0x629000022941 thread T0 + #0 0x595ebbed687a in smc91c111_do_tx hw/net/smc91c111.c:240:19 + #1 0x595ebbed687a in smc91c111_queue_tx hw/net/smc91c111.c:284:5 + #2 0x595ebbed687a in smc91c111_writeb hw/net/smc91c111.c:419:17 + #3 0x595ebbed687a in smc91c111_writefn hw/net/smc91c111.c:666:9 + #4 0x595ebd174d33 in memory_region_write_accessor system/memory.c:497:5 + #5 0x595ebd1744aa in access_with_adjusted_size system/memory.c:573:18 + #6 0x595ebd1738d8 in memory_region_dispatch_write system/memory.c + #7 0x595ebd1cc984 in flatview_write_continue_step system/physmem.c:2786:18 + #8 0x595ebd1b9880 in flatview_write_continue system/physmem.c:2816:19 + #9 0x595ebd1b9880 in flatview_write system/physmem.c:2847:12 + #10 0x595ebd1b9517 in address_space_write system/physmem.c:2967:18 + #11 0x595ebc77d5c3 in qtest_process_command system/qtest.c:522:13 + #12 0x595ebc77b83b in qtest_process_inbuf system/qtest.c:776:9 + ... +``` +Steps to reproduce: +``` +export QEMU_ARGS="-display none -machine accel=qtest, -m 512M -machine realview-eb" +cat << EOF | ./qemu-system-arm $QEMU_ARGS -qtest /dev/null -qtest stdio +clock_step +clock_step +writel 0x4e000000 0x2b1e08f5 +writew 0x4e000000 0x2b1e08f5 +writel 0x4e00000c 0x66027d24 +clock_step +readb 0x4e000000 +writel 0x4e000008 0x238e1f29 +writew 0x4e000000 0x41d9fe3b +writel 0x4e00000c 0x27022a2d +clock_step +readw 0x4e000004 +clock_step +readb 0x4e000008 +clock_step +writew 0x4e000000 0x620c5fdf +EOF +``` +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2743 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2743 new file mode 100644 index 000000000..05dfcfada --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2743 @@ -0,0 +1,3 @@ +The command Qemu-img did not work, cannot convert raw file to vhd file +Description of problem: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2744 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2744 new file mode 100644 index 000000000..fef28deb8 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2744 @@ -0,0 +1,5 @@ +Avoid defining custom machine-definition macros for each new machine type +Additional information: +There are already some semi-generic implementations of this macro, such as [`DEFINE_PC_VER_MACHINE()`](https://gitlab.com/qemu-project/qemu/-/blob/aa3a285b5bc56a4208b3b57d4a55291e9c260107/include/hw/i386/pc.h#L326), which is used for the 'q35', 'pc' and 'isapc' machine types. + +There does appear to be some deviation from the template macro in some cases. We would have to enumerate what the nature of these deviations is, why only some machine types need them, and how they would fit into the proposed generic macro. Still, if we could have a generic macro that simplifies 80% of machine types' version definitions, then that seems like a win. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2745 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2745 new file mode 100644 index 000000000..f8d500b57 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2745 @@ -0,0 +1,26 @@ +Qemu should send RARP for vhostuser regardless of whether virtio supports GUEST_ANNOUNCE +Description of problem: +When virtio reports to qemu that GUEST_ANNOUNCE is supported, qemu will not send RARP. The assumption, I think, is that guest kernel will do whatever is needed to announce the guest. The problem with this assumption is that 1) kernel won't send RARPs; 2) for IPv4 and IPv6 it will send GARPs and NAs; 3) for interfaces with no IP addresses, I think it won't send anything at all. + +RARPs are useful because they allow to notify regardless of IP configuration. I've [asked](https://issues.redhat.com/browse/RHEL-71919]) RHEL kernel folks to consider issuing RARPs from the guest kernel, but it won't happen overnight, and regardless, it's not a complete solution since we cannot expect all guests running a patched kernel with such feature. + +RARP packets are also often expected by underlying network components. For example, OVN controller has a special "activation-strategy=rarp" configuration that makes OVN wait for a RARP from destination chassis on live migration, and only then unblock traffic for the port. Since RARP is not issed by Qemu nor virtio-net, the OVN port is never unblocked (until its configuration is reset by CMS). + +I think what should be done from Qemu side is to send RARP for vhostuser ports regardless of whether virtio supports GUEST_ANNOUNCE. I **think** this can be achieved by removing this code: + +``` + /* If guest supports GUEST_ANNOUNCE do nothing */ + if (virtio_has_feature(dev->acked_features, VIRTIO_NET_F_GUEST_ANNOUNCE)) { + return 0; + } +``` +Steps to reproduce: +1. Start a VM with vhostuser* port and fresh virtio guest driver. +2. Live migrate it. +3. Observe that RARP is not sent from the migrated port. GARP (or NA for IPv6) is sent instead. +Additional information: +Some external bugs that may be relevant: + +- RHEL kernel request to send RARPs from virtio: https://issues.redhat.com/browse/RHEL-71919 (won't fix the issue for older unpatched kernels) +- Request for OVN to handle GARPs and NAs: https://issues.redhat.com/browse/FDP-1042 (won't solve for unaddressed ports!) +- An attempt to work around the issue in OpenStack Neutron OVN env by disabling activation strategy: https://issues.redhat.com/browse/OSPRH-12571 (not a great long term solution) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2746 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2746 new file mode 100644 index 000000000..a4d55d47b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2746 @@ -0,0 +1 @@ +NO_CAST.INTEGER_OVERFLOW in /hw/net/e1000.c diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2747 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2747 new file mode 100644 index 000000000..344924bbe --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2747 @@ -0,0 +1,9 @@ +External snapshots are created world-readable when connecting via qemu+ssh://root +Description of problem: +External snapshots are created with world-readable permissions when connecting via `qemu+ssh://root`. +Steps to reproduce: +1. Create a VM over `qemu+ssh://root@$SERVER/system` +2. Create an external snapshot via virt-manager or with `virsh snapshot-create-as --domain testvm --name test --disk-only --diskspec vda,file=/var/lib/libvirt/images/test.qcow2 --atomic` +3. `ls -l /var/lib/libvirt/images/test.qcow2` +Additional information: +Issue doesn't seem to go away by adding `umask 077` in `$HOME/.profile` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2749 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2749 new file mode 100644 index 000000000..008bbeb4a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2749 @@ -0,0 +1,79 @@ +TSAN/RaceHunter data race on bh->flags in aio_compute_bh_timeout +Description of problem: +Switching the TSAN build for `test-aio-multithread` unit test reveals the data race on `bh->flags` in `aio_compute_bh_timeout`. + +The same data race can be found in the list of warnings in #851 and #1496. + +I investigated the data race and I can reproduce the same race with our tool RaceHunter on the test `tests/unit/test-thread-pool.c` where two accesses may happen simultaneously. It is not false alarm, because RaceHunter introduces the delay and catches both accesses exactly at the same time, not just predicting the race due to missing happens-before as TSAN does. + +``` +WARNING: SMC RaceHunter: Data race found: + read access from thread 0 [handle=0] at pc=0x55b851f660b9, addr=7b1000000168 (4 bytes) + #0 aio_compute_bh_timeout util/async.c:259:18 + #1 aio_compute_timeout util/async.c:282:15 + #2 aio_poll util/aio-posix.c:628:26 (test-thread-pool+0xa4223f) + #3 test_submit_aio tests/unit/test-thread-pool.c:70:9 + #4 main tests/unit/test-thread-pool.c + + Previous atomic write access from thread 4 [handle=4] at pc=0x55b851f65e24, addr=7b1000000168 (4 bytes) + #0 aio_bh_enqueue util/async.c:81:17 + #1 qemu_bh_schedule util/async.c:235:5 + #2 worker_thread util/thread-pool.c:118:9 + #3 qemu_thread_start util/qemu-thread-posix.c:543:9 +``` + +Both are accesses to `flags` in `BHList` (`bh->flags`) +The write access in `aio_bh_enqueue` is protected by atomic operation `qatomic_fetch_or` while second read access is not atomic and not protected by locks. + +The read access in `aio_compute_bh_timeout` seems to rely on RCU mechanism `QSLIST_FOREACH_RCU(bh, head, next)`, but in this case the writer should also use RCU protected assign. +Steps to reproduce: +1. configure --enable-tsan --cc=clang --cxx=clang++ --enable-trace-backends=ust --enable-fdt=system --disable-slirp +2. make check-unit test-aio-multithread +3. See the warning in the log +``` +WARNING: ThreadSanitizer: data race (pid=3514443) + Atomic write of size 4 at 0x7b1000000168 by thread T17: + #0 aio_bh_enqueue /home/mordan/qemu/build/../util/async.c:81:17 (test-thread-pool+0xa5e933) + #1 qemu_bh_schedule /home/mordan/qemu/build/../util/async.c:235:5 (test-thread-pool+0xa5e933) + #2 worker_thread /home/mordan/qemu/build/../util/thread-pool.c:118:9 (test-thread-pool+0xa66153) + #3 qemu_thread_start /home/mordan/qemu/build/../util/qemu-thread-posix.c:543:9 (test-thread-pool+0xa496c0) + + Previous read of size 4 at 0x7b1000000168 by main thread: + #0 aio_compute_bh_timeout /home/mordan/qemu/build/../util/async.c:259:18 (test-thread-pool+0xa5ebc8) + #1 aio_compute_timeout /home/mordan/qemu/build/../util/async.c:282:15 (test-thread-pool+0xa5ebc8) + #2 aio_poll /home/mordan/qemu/build/../util/aio-posix.c:628:26 (test-thread-pool+0xa42d4f) + #3 do_test_cancel /home/mordan/qemu/build/../tests/unit/test-thread-pool.c:199:9 (test-thread-pool+0x50f0e8) + #4 test_cancel_async /home/mordan/qemu/build/../tests/unit/test-thread-pool.c:230:5 (test-thread-pool+0x50ec01) + #5 <null> <null> (libglib-2.0.so.0+0x7daed) (BuildId: e845b8fd2f396872c036976626389ffc4f50c9c5) + #6 __libc_start_call_main csu/../sysdeps/nptl/libc_start_call_main.h:58:16 (libc.so.6+0x29d8f) (BuildId: 490fef8403240c91833978d494d39e537409b92e) + + As if synchronized via sleep: + #0 nanosleep out/lib/clangrt-x86_64-unknown-linux-gnu/./out/lib/clangrt-x86_64-unknown-linux-gnu/./toolchain/llvm-project/compiler-rt/lib/tsan/rtl/tsan_interceptors_posix.cpp:365:3 (test-thread-pool+0x34507d) + #1 g_usleep <null> (libglib-2.0.so.0+0x7ff76) (BuildId: e845b8fd2f396872c036976626389ffc4f50c9c5) + #2 worker_thread /home/mordan/qemu/build/../util/thread-pool.c:111:15 (test-thread-pool+0xa66115) + #3 qemu_thread_start /home/mordan/qemu/build/../util/qemu-thread-posix.c:543:9 (test-thread-pool+0xa496c0) + + Location is heap block of size 56 at 0x7b1000000140 allocated by main thread: + #0 malloc out/lib/clangrt-x86_64-unknown-linux-gnu/./out/lib/clangrt-x86_64-unknown-linux-gnu/./toolchain/llvm-project/compiler-rt/lib/tsan/rtl/tsan_interceptors_posix.cpp:667:5 (test-thread-pool+0x346151) + #1 g_malloc <null> (libglib-2.0.so.0+0x5e738) (BuildId: e845b8fd2f396872c036976626389ffc4f50c9c5) + #2 thread_pool_init_one /home/mordan/qemu/build/../util/thread-pool.c:333:27 (test-thread-pool+0xa655c8) + #3 thread_pool_new /home/mordan/qemu/build/../util/thread-pool.c:348:5 (test-thread-pool+0xa655c8) + #4 aio_get_thread_pool /home/mordan/qemu/build/../util/async.c:441:28 (test-thread-pool+0xa5ed54) + #5 thread_pool_submit_aio /home/mordan/qemu/build/../util/thread-pool.c:246:24 (test-thread-pool+0xa64f0d) + #6 thread_pool_submit /home/mordan/qemu/build/../util/thread-pool.c:295:5 (test-thread-pool+0xa65362) + #7 test_submit /home/mordan/qemu/build/../tests/unit/test-thread-pool.c:49:5 (test-thread-pool+0x50e53f) + #8 <null> <null> (libglib-2.0.so.0+0x7daed) (BuildId: e845b8fd2f396872c036976626389ffc4f50c9c5) + #9 __libc_start_call_main csu/../sysdeps/nptl/libc_start_call_main.h:58:16 (libc.so.6+0x29d8f) (BuildId: 490fef8403240c91833978d494d39e537409b92e) + + Thread T17 'worker' (tid=3514461, running) created by thread T16 at: + #0 pthread_create out/lib/clangrt-x86_64-unknown-linux-gnu/./out/lib/clangrt-x86_64-unknown-linux-gnu/./toolchain/llvm-project/compiler-rt/lib/tsan/rtl/tsan_interceptors_posix.cpp:1022:3 (test-thread-pool+0x34793d) + #1 qemu_thread_create /home/mordan/qemu/build/../util/qemu-thread-posix.c:583:11 (test-thread-pool+0xa49550) + #2 do_spawn_thread /home/mordan/qemu/build/../util/thread-pool.c:146:5 (test-thread-pool+0xa65f5e) + #3 worker_thread /home/mordan/qemu/build/../util/thread-pool.c:83:5 (test-thread-pool+0xa65f5e) + #4 qemu_thread_start /home/mordan/qemu/build/../util/qemu-thread-posix.c:543:9 (test-thread-pool+0xa496c0) + +SUMMARY: ThreadSanitizer: data race /home/mordan/qemu/build/../util/async.c:81:17 in aio_bh_enqueue +``` + + +@hreitz, @kmwolf, @bonzini Are there any other synchronization that was intended to ensure that the accesses do not happen simultaneously? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/275 b/gitlab/issues_text/target_missing/host_missing/accel_missing/275 new file mode 100644 index 000000000..147469e3b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/275 @@ -0,0 +1 @@ +Error in user-mode calculation of ELF aux vector's AT_PHDR diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2750 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2750 new file mode 100644 index 000000000..2733ce924 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2750 @@ -0,0 +1,11 @@ +Data race in the goflag global variable in the rcutorture test. +Description of problem: +A data race involving the `goflag` global variable in `tests/unit/rcutorture.c` was identified using TSAN. +Steps to reproduce: +```sh +QEMU_BUILD_DIR=<path to the QEMU build directory> +QEMU_DIR=<path to the QEMU repository directory> +configure --enable-tsan --cc=clang --cxx=clang++ --enable-trace-backends=ust --enable-fdt=system --disable-slirp +make tests/unit/rcutorture +MALLOC_PERTURB_=194 G_TEST_BUILDDIR=$QEMU_BUILD_DIR/tests/unit G_TEST_SRCDIR=$QEMU_DIR/tests/unit $QEMU_BUILD_DIR/tests/unit/rcutorture --tap -k +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2751 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2751 new file mode 100644 index 000000000..7cd7e6816 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2751 @@ -0,0 +1 @@ +QEMU user emulation gdbstub emits incorrect file descriptor and errno values diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2752 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2752 new file mode 100644 index 000000000..056b6884c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2752 @@ -0,0 +1,277 @@ +Heap use after free in virtio-crypto with vhost-user backend +Description of problem: +An heap-use-after-free happens in virtio-crypto device with vhost-user backend created by a dpdk example program. +Steps to reproduce: +1.Build dpdk vhost-user crypto backend. Following instructions here: [DPDK installation](https://doc.dpdk.org/guides/prog_guide/build-sdk-meson.html) +``` +wget https://fast.dpdk.org/rel/dpdk-24.11.tar.xz +meson setup -Dexamples=all build +cd build +ninja +meson install +cd examples +sudo ./dpdk-vhost_crypto --vdev 'crypto_aesni_mb0' -- --config \(7,0,0\) --socket-file=7,/tmp/my-crypto.sock +``` +After setting up the backend, should see something like: +``` +EAL: Detected CPU lcores: 48 +EAL: Detected NUMA nodes: 2 +EAL: Detected static linkage of DPDK +EAL: Multi-process socket /var/run/dpdk/rte/mp_socket +EAL: Selected IOVA mode 'PA' +EAL: VFIO support initialized +CRYPTODEV: Creating cryptodev crypto_aesni_mb0 +CRYPTODEV: Initialisation parameters - name: crypto_aesni_mb0,socket id: 0, max queue pairs: 8 +IPSEC_MB: ipsec_mb_create() line 168: IPSec Multi-buffer library version used: 2.0.0 +USER1: Processing on Core 7 started +VHOST_CONFIG: (/tmp/my-crypto.sock) logging feature is disabled in async copy mode +VHOST_CONFIG: (/tmp/my-crypto.sock) vhost-user server: socket created, fd: 213 +VHOST_CONFIG: (/tmp/my-crypto.sock) binding succeeded +``` + +2.Build qemu with ASAN (i.e., --enable-asan) and vhost support (i.e., --enable-vhost-user --enable-vhost-crypto) + +3.Ensure that /dev/hugemaps and /tmp/my-crypto.sock can be accessed. You may need to change their permissions by chmod, or run qemu-system as root. + +4.Run the command below to reproduce UAF. Here, Setting ASAN_OPTIONS=max_malloc_fill_size=0 avoids capturing another unintialized read in vhost_user_backend_init, which happens ealier than the UAF. + +I can reproduce it 7 times in 10 runs, seems to be racing. +``` +cat << EOF | ASAN_OPTIONS=max_malloc_fill_size=0 \ +./qemu-system-x86_64 --enable-kvm -m 512M \ +-object \ +memory-backend-file,id=mem,size=512M,mem-path=/dev/hugepages,share=on \ +-numa node,memdev=mem -smp cpus=4 -machine q35 -chardev \ +socket,id=chardev0,path=/tmp/my-crypto.sock -object \ +cryptodev-vhost-user,id=cryptodev0,chardev=chardev0 -device \ +virtio-crypto-pci,id=crypto0,cryptodev=cryptodev0 -display none -qtest \ +stdio +outl 0xcf8 0x80001800 +inw 0xcfc +outl 0xcf8 0x80001814 +outl 0xcfc 0xffffffff +outl 0xcf8 0x80001814 +inl 0xcfc +outl 0xcf8 0x80001814 +outl 0xcfc 0xe0000000 +outl 0xcf8 0x80001820 +outl 0xcfc 0xffffffff +outl 0xcf8 0x80001820 +inl 0xcfc +outl 0xcf8 0x80001820 +outl 0xcfc 0xe0004000 +outl 0xcf8 0x80001804 +inw 0xcfc +outl 0xcf8 0x80001804 +outw 0xcfc 0x7 +outl 0xcf8 0x80001804 +inw 0xcfc +writeq 0xe0004023 0x5f5f5f5f5f5f0d00 +writeq 0xe0004015 0x10b2d007a210fff +writeq 0xe0004011 0xb2616007a006425 +writeq 0xe0004011 0x5a5546a2d40b6425 +EOF +``` +Additional information: +Here is the information reported by ASAN: +``` +==2277232==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases! +[I 0.000000] OPENED +qemu-system-x86_64: warning: vhost-user backend supports VHOST_USER_PROTOCOL_F_CONFIG but QEMU does not. +[R +0.119439] outl 0xcf8 0x80001800 +[S +0.119564] OK +OK +[R +0.119607] inw 0xcfc +[S +0.119667] OK 0x1af4 +OK 0x1af4 +[R +0.119721] outl 0xcf8 0x80001814 +[S +0.119770] OK +OK +[R +0.119817] outl 0xcfc 0xffffffff +[S +0.119889] OK +OK +[R +0.119929] outl 0xcf8 0x80001814 +[S +0.119977] OK +OK +[R +0.120037] inl 0xcfc +[S +0.120090] OK 0xfffff000 +OK 0xfffff000 +[R +0.120140] outl 0xcf8 0x80001814 +[S +0.120165] OK +OK +[R +0.120193] outl 0xcfc 0xe0000000 +[S +0.120242] OK +OK +[R +0.120303] outl 0xcf8 0x80001820 +[S +0.120324] OK +OK +[R +0.120343] outl 0xcfc 0xffffffff +[S +0.120390] OK +OK +[R +0.120431] outl 0xcf8 0x80001820 +[S +0.120487] OK +OK +[R +0.120541] inl 0xcfc +[S +0.120578] OK 0xffffc00c +OK 0xffffc00c +[R +0.120635] outl 0xcf8 0x80001820 +[S +0.120680] OK +OK +[R +0.120747] outl 0xcfc 0xe0004000 +[S +0.120815] OK +OK +[R +0.120858] outl 0xcf8 0x80001804 +[S +0.120881] OK +OK +[R +0.120930] inw 0xcfc +[S +0.120975] OK 0x0000 +OK 0x0000 +[R +0.121017] outl 0xcf8 0x80001804 +[S +0.121053] OK +OK +[R +0.121081] outw 0xcfc 0x7 +[S +0.132297] OK +OK +[R +0.132330] outl 0xcf8 0x80001804 +[S +0.132345] OK +OK +[R +0.132357] inw 0xcfc +[S +0.132373] OK 0x0007 +OK 0x0007 +[R +0.132392] writeq 0xe0004023 0x5f5f5f5f5f5f0d00 +[S +0.132409] OK +OK +[R +0.132419] writeq 0xe0004015 0x10b2d007a210fff +[S +0.132447] OK +OK +[R +0.132460] writeq 0xe0004011 0xb2616007a006425 +[S +0.132480] OK +OK +[R +0.132489] writeq 0xe0004011 0x5a5546a2d40b6425 +qemu-system-x86_64: Failed initializing vhost-user memory map, consider using -object memory-backend-file share=on +qemu-system-x86_64: vhost_set_mem_table failed: Invalid argument (22) +qemu-system-x86_64: Failed to write msg. Wrote -1 instead of 52. +qemu-system-x86_64: vhost_set_vring_addr failed: Invalid argument (22) +================================================================= +==2277232==ERROR: AddressSanitizer: heap-use-after-free on address 0x618000000b28 at pc 0x5570e3541a1b bp 0x7fff627ef550 sp 0x7fff627ef548 +READ of size 8 at 0x618000000b28 thread T0 + #0 0x5570e3541a1a in vhost_virtqueue_start /mnt/Hypervisor/qemu/build/master/fuzz/../hw/virtio/vhost.c:1359:33 + #1 0x5570e3562051 in vhost_dev_start /mnt/Hypervisor/qemu/build/master/fuzz/../hw/virtio/vhost.c:2041:13 + #2 0x5570e37c10c1 in cryptodev_vhost_start_one /mnt/Hypervisor/qemu/build/master/fuzz/../backends/cryptodev-vhost.c:96:9 + #3 0x5570e37c067f in cryptodev_vhost_start /mnt/Hypervisor/qemu/build/master/fuzz/../backends/cryptodev-vhost.c:213:13 + #4 0x5570e34f06ce in virtio_crypto_vhost_status /mnt/Hypervisor/qemu/build/master/fuzz/../hw/virtio/virtio-crypto.c:1189:13 + #5 0x5570e34ce991 in virtio_crypto_set_status /mnt/Hypervisor/qemu/build/master/fuzz/../hw/virtio/virtio-crypto.c:1205:5 + #6 0x5570e49725e5 in virtio_set_status /mnt/Hypervisor/qemu/build/master/fuzz/../hw/virtio/virtio.c:2242:9 + #7 0x5570e3496356 in virtio_pci_common_write /mnt/Hypervisor/qemu/build/master/fuzz/../hw/virtio/virtio-pci.c:1612:9 + #8 0x5570e4bbdc93 in memory_region_write_accessor /mnt/Hypervisor/qemu/build/master/fuzz/../system/memory.c:497:5 + #9 0x5570e4bbd385 in access_with_adjusted_size /mnt/Hypervisor/qemu/build/master/fuzz/../system/memory.c:573:18 + #10 0x5570e4bbb2f9 in memory_region_dispatch_write /mnt/Hypervisor/qemu/build/master/fuzz/../system/memory.c:1553:16 + #11 0x5570e4c64dfe in flatview_write_continue_step /mnt/Hypervisor/qemu/build/master/fuzz/../system/physmem.c:2786:18 + #12 0x5570e4c64694 in flatview_write_continue /mnt/Hypervisor/qemu/build/master/fuzz/../system/physmem.c:2816:19 + #13 0x5570e4c3b3eb in flatview_write /mnt/Hypervisor/qemu/build/master/fuzz/../system/physmem.c:2847:12 + #14 0x5570e4c3aec8 in address_space_write /mnt/Hypervisor/qemu/build/master/fuzz/../system/physmem.c:2967:18 + #15 0x5570e375da7c in qtest_process_command /mnt/Hypervisor/qemu/build/master/fuzz/../system/qtest.c:532:13 + #16 0x5570e375856d in qtest_process_inbuf /mnt/Hypervisor/qemu/build/master/fuzz/../system/qtest.c:776:9 + #17 0x5570e3767b6e in qtest_read /mnt/Hypervisor/qemu/build/master/fuzz/../system/qtest.c:788:5 + #18 0x5570e564cafd in qemu_chr_be_write_impl /mnt/Hypervisor/qemu/build/master/fuzz/../chardev/char.c:214:9 + #19 0x5570e564cbb9 in qemu_chr_be_write /mnt/Hypervisor/qemu/build/master/fuzz/../chardev/char.c:226:9 + #20 0x5570e5658a35 in fd_chr_read /mnt/Hypervisor/qemu/build/master/fuzz/../chardev/char-fd.c:72:9 + #21 0x5570e500cf6c in qio_channel_fd_source_dispatch /mnt/Hypervisor/qemu/build/master/fuzz/../io/channel-watch.c:84:12 + #22 0x7f8fc04adf7d in g_main_dispatch /home/lmy/glib-2.68.0/_build/../glib/gmain.c:3337:28 + #23 0x7f8fc04adf7d in g_main_context_dispatch /home/lmy/glib-2.68.0/_build/../glib/gmain.c:4055:7 + #24 0x5570e5a014e9 in glib_pollfds_poll /mnt/Hypervisor/qemu/build/master/fuzz/../util/main-loop.c:287:9 + #25 0x5570e59ffe23 in os_host_main_loop_wait /mnt/Hypervisor/qemu/build/master/fuzz/../util/main-loop.c:310:5 + #26 0x5570e59ff9ec in main_loop_wait /mnt/Hypervisor/qemu/build/master/fuzz/../util/main-loop.c:589:11 + #27 0x5570e376f217 in qemu_main_loop /mnt/Hypervisor/qemu/build/master/fuzz/../system/runstate.c:835:9 + #28 0x5570e5679ecc in qemu_default_main /mnt/Hypervisor/qemu/build/master/fuzz/../system/main.c:37:14 + #29 0x5570e5679f17 in main /mnt/Hypervisor/qemu/build/master/fuzz/../system/main.c:48:12 + #30 0x7f8fbe74f082 in __libc_start_main /build/glibc-LcI20x/glibc-2.31/csu/../csu/libc-start.c:308:16 + #31 0x5570e18f189d in _start (/mnt/Hypervisor/qemu/build/master/fuzz/qemu-system-x86_64+0x2c8b89d) + +0x618000000b28 is located 680 bytes inside of 800-byte region [0x618000000880,0x618000000ba0) +freed by thread T0 here: + #0 0x5570e196dde2 in __interceptor_free /home/brian/src/llvm_releases/llvm-project/llvm/utils/release/final/llvm-project/compiler-rt/lib/asan/asan_malloc_linux.cpp:111:3 + #1 0x5570e37befc1 in cryptodev_vhost_cleanup /mnt/Hypervisor/qemu/build/master/fuzz/../backends/cryptodev-vhost.c:45:5 + #2 0x5570e37ce272 in cryptodev_vhost_user_stop /mnt/Hypervisor/qemu/build/master/fuzz/../backends/cryptodev-vhost-user.c:86:9 + #3 0x5570e37cd728 in cryptodev_vhost_user_event /mnt/Hypervisor/qemu/build/master/fuzz/../backends/cryptodev-vhost-user.c:171:9 + #4 0x5570e5655ed1 in chr_be_event /mnt/Hypervisor/qemu/build/master/fuzz/../chardev/char.c:62:5 + #5 0x5570e564b465 in qemu_chr_be_event /mnt/Hypervisor/qemu/build/master/fuzz/../chardev/char.c:82:5 + #6 0x5570e5646076 in tcp_chr_disconnect_locked /mnt/Hypervisor/qemu/build/master/fuzz/../chardev/char-socket.c:482:9 + #7 0x5570e5632534 in tcp_chr_write /mnt/Hypervisor/qemu/build/master/fuzz/../chardev/char-socket.c:131:17 + #8 0x5570e564c1f5 in qemu_chr_write_buffer /mnt/Hypervisor/qemu/build/master/fuzz/../chardev/char.c:122:15 + #9 0x5570e564b8a2 in qemu_chr_write /mnt/Hypervisor/qemu/build/master/fuzz/../chardev/char.c:186:11 + #10 0x5570e5615f82 in qemu_chr_fe_write_all /mnt/Hypervisor/qemu/build/master/fuzz/../chardev/char-fe.c:52:12 + #11 0x5570e49ec22c in vhost_user_write /mnt/Hypervisor/qemu/build/master/fuzz/../hw/virtio/vhost-user.c:410:11 + #12 0x5570e4a0e512 in vhost_user_write_sync /mnt/Hypervisor/qemu/build/master/fuzz/../hw/virtio/vhost-user.c:1141:11 + #13 0x5570e49f84f9 in vhost_user_set_vring_addr /mnt/Hypervisor/qemu/build/master/fuzz/../hw/virtio/vhost-user.c:1384:12 + #14 0x5570e3543fcb in vhost_virtqueue_set_addr /mnt/Hypervisor/qemu/build/master/fuzz/../hw/virtio/vhost.c:979:9 + #15 0x5570e3540a0b in vhost_virtqueue_start /mnt/Hypervisor/qemu/build/master/fuzz/../hw/virtio/vhost.c:1321:9 + #16 0x5570e3562051 in vhost_dev_start /mnt/Hypervisor/qemu/build/master/fuzz/../hw/virtio/vhost.c:2041:13 + #17 0x5570e37c10c1 in cryptodev_vhost_start_one /mnt/Hypervisor/qemu/build/master/fuzz/../backends/cryptodev-vhost.c:96:9 + #18 0x5570e37c067f in cryptodev_vhost_start /mnt/Hypervisor/qemu/build/master/fuzz/../backends/cryptodev-vhost.c:213:13 + #19 0x5570e34f06ce in virtio_crypto_vhost_status /mnt/Hypervisor/qemu/build/master/fuzz/../hw/virtio/virtio-crypto.c:1189:13 + #20 0x5570e34ce991 in virtio_crypto_set_status /mnt/Hypervisor/qemu/build/master/fuzz/../hw/virtio/virtio-crypto.c:1205:5 + #21 0x5570e49725e5 in virtio_set_status /mnt/Hypervisor/qemu/build/master/fuzz/../hw/virtio/virtio.c:2242:9 + #22 0x5570e3496356 in virtio_pci_common_write /mnt/Hypervisor/qemu/build/master/fuzz/../hw/virtio/virtio-pci.c:1612:9 + #23 0x5570e4bbdc93 in memory_region_write_accessor /mnt/Hypervisor/qemu/build/master/fuzz/../system/memory.c:497:5 + #24 0x5570e4bbd385 in access_with_adjusted_size /mnt/Hypervisor/qemu/build/master/fuzz/../system/memory.c:573:18 + #25 0x5570e4bbb2f9 in memory_region_dispatch_write /mnt/Hypervisor/qemu/build/master/fuzz/../system/memory.c:1553:16 + #26 0x5570e4c64dfe in flatview_write_continue_step /mnt/Hypervisor/qemu/build/master/fuzz/../system/physmem.c:2786:18 + #27 0x5570e4c64694 in flatview_write_continue /mnt/Hypervisor/qemu/build/master/fuzz/../system/physmem.c:2816:19 + #28 0x5570e4c3b3eb in flatview_write /mnt/Hypervisor/qemu/build/master/fuzz/../system/physmem.c:2847:12 + #29 0x5570e4c3aec8 in address_space_write /mnt/Hypervisor/qemu/build/master/fuzz/../system/physmem.c:2967:18 + +previously allocated by thread T0 here: + #0 0x5570e196e04d in malloc /home/brian/src/llvm_releases/llvm-project/llvm/utils/release/final/llvm-project/compiler-rt/lib/asan/asan_malloc_linux.cpp:129:3 + #1 0x7f8fc04b3dc8 in g_malloc /home/lmy/glib-2.68.0/_build/../glib/gmem.c:106:13 + #2 0x5570e37cdca6 in cryptodev_vhost_user_start /mnt/Hypervisor/qemu/build/master/fuzz/../backends/cryptodev-vhost-user.c:108:30 + #3 0x5570e37cd599 in cryptodev_vhost_user_event /mnt/Hypervisor/qemu/build/master/fuzz/../backends/cryptodev-vhost-user.c:164:13 + #4 0x5570e5655ed1 in chr_be_event /mnt/Hypervisor/qemu/build/master/fuzz/../chardev/char.c:62:5 + #5 0x5570e564b465 in qemu_chr_be_event /mnt/Hypervisor/qemu/build/master/fuzz/../chardev/char.c:82:5 + #6 0x5570e5618d42 in qemu_chr_fe_set_handlers_full /mnt/Hypervisor/qemu/build/master/fuzz/../chardev/char-fe.c:283:13 + #7 0x5570e5618674 in qemu_chr_fe_set_handlers /mnt/Hypervisor/qemu/build/master/fuzz/../chardev/char-fe.c:297:5 + #8 0x5570e37cb960 in cryptodev_vhost_user_init /mnt/Hypervisor/qemu/build/master/fuzz/../backends/cryptodev-vhost-user.c:220:5 + #9 0x5570e37a4e98 in cryptodev_backend_complete /mnt/Hypervisor/qemu/build/master/fuzz/../backends/cryptodev.c:420:9 + #10 0x5570e4eb0c40 in user_creatable_complete /mnt/Hypervisor/qemu/build/master/fuzz/../qom/object_interfaces.c:28:9 + #11 0x5570e4eb16a8 in user_creatable_add_type /mnt/Hypervisor/qemu/build/master/fuzz/../qom/object_interfaces.c:125:10 + #12 0x5570e4eb1c74 in user_creatable_add_qapi /mnt/Hypervisor/qemu/build/master/fuzz/../qom/object_interfaces.c:157:11 + #13 0x5570e378882b in object_option_foreach_add /mnt/Hypervisor/qemu/build/master/fuzz/../system/vl.c:1809:13 + #14 0x5570e378553c in qemu_create_late_backends /mnt/Hypervisor/qemu/build/master/fuzz/../system/vl.c:2029:5 + #15 0x5570e3779efe in qemu_init /mnt/Hypervisor/qemu/build/master/fuzz/../system/vl.c:3726:5 + #16 0x5570e5679f11 in main /mnt/Hypervisor/qemu/build/master/fuzz/../system/main.c:47:5 + #17 0x7f8fbe74f082 in __libc_start_main /build/glibc-LcI20x/glibc-2.31/csu/../csu/libc-start.c:308:16 + +SUMMARY: AddressSanitizer: heap-use-after-free /mnt/Hypervisor/qemu/build/master/fuzz/../hw/virtio/vhost.c:1359:33 in vhost_virtqueue_start +Shadow bytes around the buggy address: + 0x0c307fff8110: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd + 0x0c307fff8120: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd + 0x0c307fff8130: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd + 0x0c307fff8140: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd + 0x0c307fff8150: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd +=>0x0c307fff8160: fd fd fd fd fd[fd]fd fd fd fd fd fd fd fd fd fd + 0x0c307fff8170: fd fd fd fd fa fa fa fa fa fa fa fa fa fa fa fa + 0x0c307fff8180: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa + 0x0c307fff8190: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 + 0x0c307fff81a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 + 0x0c307fff81b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +Shadow byte legend (one shadow byte represents 8 application bytes): + Addressable: 00 + Partially addressable: 01 02 03 04 05 06 07 + Heap left redzone: fa + Freed heap region: fd + Stack left redzone: f1 + Stack mid redzone: f2 + Stack right redzone: f3 + Stack after return: f5 + Stack use after scope: f8 + Global redzone: f9 + Global init order: f6 + Poisoned by user: f7 + Container overflow: fc + Array cookie: ac + Intra object redzone: bb + ASan internal: fe + Left alloca redzone: ca + Right alloca redzone: cb +==2277232==ABORTING +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2753 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2753 new file mode 100644 index 000000000..af1fefd1a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2753 @@ -0,0 +1,124 @@ +Uninitialized read in vhost_user_backend_init. +Description of problem: +In backends/cryptodev-vhost.c::cryptodev_vhost_init, crypto->dev.config_ops is not initialized (See code below). I think here `g_new0` should be used instead of `g_new`. +``` +struct CryptoDevBackendVhost * +cryptodev_vhost_init( + CryptoDevBackendVhostOptions *options) +{ + ... + crypto = g_new(CryptoDevBackendVhost, 1); + crypto->dev.max_queues = 1; + crypto->dev.nvqs = 1; + crypto->dev.vqs = crypto->vqs; + + crypto->cc = options->cc; + + crypto->dev.protocol_features = 0; + crypto->backend = -1; + ... +} +``` +In vhost_user_backend_init, crypto->dev.config_ops will be dereferenced. Since it is uninitialized with 0, it is possible that a random value pointer will be dereferenced. +``` +static int vhost_user_backend_init(struct vhost_dev *dev, void *opaque, + Error **errp) +{ + ... + if (virtio_has_feature(features, VHOST_USER_F_PROTOCOL_FEATURES)) { + bool supports_f_config = vus->supports_config || + (dev->config_ops && dev->config_ops->vhost_dev_config_notifier); + uint64_t protocol_features; + ... +``` + + +As a result, ASAN will capture this uninitialized, since it assigns 0xbe to every bytes of allocated but uninitilized memory. +Steps to reproduce: +1.Build dpdk vhost-user crypto backend. Following instructions here: [DPDK installation](https://doc.dpdk.org/guides/prog_guide/build-sdk-meson.html) +``` +wget https://fast.dpdk.org/rel/dpdk-24.11.tar.xz +meson setup -Dexamples=all build +cd build +ninja +meson install +cd examples +sudo ./dpdk-vhost_crypto --vdev 'crypto_aesni_mb0' -- --config \(7,0,0\) --socket-file=7,/tmp/my-crypto.sock +``` +After setting up the backend, should see something like: +``` +EAL: Detected CPU lcores: 48 +EAL: Detected NUMA nodes: 2 +EAL: Detected static linkage of DPDK +EAL: Multi-process socket /var/run/dpdk/rte/mp_socket +EAL: Selected IOVA mode 'PA' +EAL: VFIO support initialized +CRYPTODEV: Creating cryptodev crypto_aesni_mb0 +CRYPTODEV: Initialisation parameters - name: crypto_aesni_mb0,socket id: 0, max queue pairs: 8 +IPSEC_MB: ipsec_mb_create() line 168: IPSec Multi-buffer library version used: 2.0.0 +USER1: Processing on Core 7 started +VHOST_CONFIG: (/tmp/my-crypto.sock) logging feature is disabled in async copy mode +VHOST_CONFIG: (/tmp/my-crypto.sock) vhost-user server: socket created, fd: 213 +VHOST_CONFIG: (/tmp/my-crypto.sock) binding succeeded +``` + +2.Build qemu with ASAN (i.e., --enable-asan) and vhost support (i.e., --enable-vhost-user --enable-vhost-crypto) + +3.Ensure that /dev/hugemaps and /tmp/my-crypto.sock can be accessed. You may need to change their permissions by chmod, or run qemu-system as root. + +4.Run the command below to reproduce problem. +``` +cat << EOF | \ +./qemu-system-x86_64 --enable-kvm -m 512M \ +-object \ +memory-backend-file,id=mem,size=512M,mem-path=/dev/hugepages,share=on \ +-numa node,memdev=mem -smp cpus=4 -machine q35 -chardev \ +socket,id=chardev0,path=/tmp/my-crypto.sock -object \ +cryptodev-vhost-user,id=cryptodev0,chardev=chardev0 -device \ +virtio-crypto-pci,id=crypto0,cryptodev=cryptodev0 -display none -qtest \ +stdio +EOF +``` +Additional information: +Here is the information reported by ASAN: +``` +==2270320==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases! +[I 0.000000] OPENED +../hw/virtio/vhost-user.c:2183:50: runtime error: member access within misaligned address 0xbebebebebebebebe for type 'const VhostDevConfigOps' (aka 'const struct VhostDevConfigOps'), which requires 8 byte alignment +0xbebebebebebebebe: note: pointer points here +<memory cannot be printed> +SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior ../hw/virtio/vhost-user.c:2183:50 in +../hw/virtio/vhost-user.c:2183:50: runtime error: load of misaligned address 0xbebebebebebebebe for type 'int (*const)(struct vhost_dev *)', which requires 8 byte alignment +0xbebebebebebebebe: note: pointer points here +<memory cannot be printed> +SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior ../hw/virtio/vhost-user.c:2183:50 in +AddressSanitizer:DEADLYSIGNAL +================================================================= +==2270320==ERROR: AddressSanitizer: SEGV on unknown address (pc 0x5619d01bd606 bp 0x7fffc6d3add0 sp 0x7fffc6d3a4e0 T0) +==2270320==The signal is caused by a READ memory access. +==2270320==Hint: this fault was caused by a dereference of a high value address (see register values below). Disassemble the provided pc to learn which register was used. + #0 0x5619d01bd606 in vhost_user_backend_init /mnt/Hypervisor/qemu/build/master/fuzz/../hw/virtio/vhost-user.c:2183:50 + #1 0x5619ced13a08 in vhost_dev_init /mnt/Hypervisor/qemu/build/master/fuzz/../hw/virtio/vhost.c:1523:9 + #2 0x5619cef8cc30 in cryptodev_vhost_init /mnt/Hypervisor/qemu/build/master/fuzz/../backends/cryptodev-vhost.c:69:9 + #3 0x5619cef9aca6 in cryptodev_vhost_user_start /mnt/Hypervisor/qemu/build/master/fuzz/../backends/cryptodev-vhost-user.c:108:30 + #4 0x5619cef9a599 in cryptodev_vhost_user_event /mnt/Hypervisor/qemu/build/master/fuzz/../backends/cryptodev-vhost-user.c:164:13 + #5 0x5619d0e22ed1 in chr_be_event /mnt/Hypervisor/qemu/build/master/fuzz/../chardev/char.c:62:5 + #6 0x5619d0e18465 in qemu_chr_be_event /mnt/Hypervisor/qemu/build/master/fuzz/../chardev/char.c:82:5 + #7 0x5619d0de5d42 in qemu_chr_fe_set_handlers_full /mnt/Hypervisor/qemu/build/master/fuzz/../chardev/char-fe.c:283:13 + #8 0x5619d0de5674 in qemu_chr_fe_set_handlers /mnt/Hypervisor/qemu/build/master/fuzz/../chardev/char-fe.c:297:5 + #9 0x5619cef98960 in cryptodev_vhost_user_init /mnt/Hypervisor/qemu/build/master/fuzz/../backends/cryptodev-vhost-user.c:220:5 + #10 0x5619cef71e98 in cryptodev_backend_complete /mnt/Hypervisor/qemu/build/master/fuzz/../backends/cryptodev.c:420:9 + #11 0x5619d067dc40 in user_creatable_complete /mnt/Hypervisor/qemu/build/master/fuzz/../qom/object_interfaces.c:28:9 + #12 0x5619d067e6a8 in user_creatable_add_type /mnt/Hypervisor/qemu/build/master/fuzz/../qom/object_interfaces.c:125:10 + #13 0x5619d067ec74 in user_creatable_add_qapi /mnt/Hypervisor/qemu/build/master/fuzz/../qom/object_interfaces.c:157:11 + #14 0x5619cef5582b in object_option_foreach_add /mnt/Hypervisor/qemu/build/master/fuzz/../system/vl.c:1809:13 + #15 0x5619cef5253c in qemu_create_late_backends /mnt/Hypervisor/qemu/build/master/fuzz/../system/vl.c:2029:5 + #16 0x5619cef46efe in qemu_init /mnt/Hypervisor/qemu/build/master/fuzz/../system/vl.c:3726:5 + #17 0x5619d0e46f11 in main /mnt/Hypervisor/qemu/build/master/fuzz/../system/main.c:47:5 + #18 0x7efeef09a082 in __libc_start_main /build/glibc-LcI20x/glibc-2.31/csu/../csu/libc-start.c:308:16 + #19 0x5619cd0be89d in _start (/mnt/Hypervisor/qemu/build/master/fuzz/qemu-system-x86_64+0x2c8b89d) + +AddressSanitizer can not provide additional info. +SUMMARY: AddressSanitizer: SEGV /mnt/Hypervisor/qemu/build/master/fuzz/../hw/virtio/vhost-user.c:2183:50 in vhost_user_backend_init +==2270320==ABORTING +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2755 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2755 new file mode 100644 index 000000000..c29af7e7f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2755 @@ -0,0 +1,11 @@ +shrink attached rbd size is not allowed by default +Description of problem: + +Steps to reproduce: +1. attach a disk with size 100GiB to a running vm +2. writing some data to the attached disk +3. executing block_resize command and shrink the size to 1GiB + +the result is virtual disk is resized successfully and causing data lost. +Additional information: +Tested QEMU version is 4.2 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2756 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2756 new file mode 100644 index 000000000..c47a11b9c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2756 @@ -0,0 +1,42 @@ +Unexpected port id 2909357808 for device virtio-serial0.0 +Description of problem: +when the VM runs for a period of time.qemu log always print the error：“Unexpected port id 2909357808 for device virtio-serial0.0”.And the spice connet display black screen.Restart the vm,it recovery. my channel is 16,Normally it will always output port less than 16,but when error it report a lage port. why it get a lage port "2909357808",Is there a data overflow? +Steps to reproduce: +1.The VM runs for a period of time + +2.report the error: "Unexpected port id 2909357808 for device virtio-serial0.0". + +3.restart to recovery. +Additional information: +qemu log: + +when vm is ok: +``` +virtio serial port 16 send control message event = 1, value = 1 +virtio serial port 0 send control message event = 1, value = 1 +virtio serial port '1' handle control message event = 3, value = 1 +virtio serial port '2' handle control message event = 3, value = 1 +virtio serial port 2 send control message event = 6, value = 1 +virtio serial port '3' handle control message event = 3, value = 1 +virtio serial port 3 send control message event = 6, value = 1 +virtio serial port '4' handle control message event = 3, value = 1 +virtio serial port 4 send control message event = 6, value = 1 +``` + + +when error: + +``` +2024-11-07T07:19:50.969383Z qemu-system-x86_64: virtio-serial-bus: Unexpected port id 2909357808 for device virtio-serial0.0 +virtio serial port '2400366800' handle control message event = 49671, value = 65535 +2024-11-07T07:19:50.969706Z qemu-system-x86_64: virtio-serial-bus: Unexpected port id 2400366800 for device virtio-serial0.0 +virtio serial port '2909357808' handle control message event = 52747, value = 65535 +2024-11-07T07:20:00.944495Z qemu-system-x86_64: virtio-serial-bus: Unexpected port id 2909357808 for device virtio-serial0.0 +virtio serial port '2400366800' handle control message event = 49671, value = 65535 +2024-11-07T07:20:00.950544Z qemu-system-x86_64: virtio-serial-bus: Unexpected port id 2400366800 for device virtio-serial0.0 +virtio serial port '2909357808' handle control message event = 52747, value = 65535 +2024-11-07T07:20:47.923564Z qemu-system-x86_64: virtio-serial-bus: Unexpected port id 2909357808 for device virtio-serial0.0 +virtio serial port '2400366800' handle control message event = 49671, value = 65535 +2024-11-07T07:20:47.924422Z qemu-system-x86_64: virtio-serial-bus: Unexpected port id 2400366800 for device virtio-serial0.0 +virtio serial port '2909357808' handle control message event = 52747, value = 65535 +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2757 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2757 new file mode 100644 index 000000000..3fb480e46 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2757 @@ -0,0 +1 @@ +EGL can't handle multi plane textures diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2758 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2758 new file mode 100644 index 000000000..85598563b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2758 @@ -0,0 +1,23 @@ +Out-of-bounds access smc91c111_readb() +Description of problem: +An out-of-bounds bug was triggered by my fuzzer. + +It looks like the code doesn't have boundary checks for `data`'s access. + +The error is `hw/net/smc91c111.c:605:24: runtime error: index 2048 out of bounds for type 'uint8_t[2048]' (aka 'unsigned char[2048]')` + +It's likely that the line 457 also needs a check. +Steps to reproduce: +``` +export QEMU_ARGS="-display none -machine accel=qtest, -m 512M -machine realview-eb" +cat << EOF | ./qemu-system-arm $QEMU_ARGS -qtest /dev/null -qtest stdio +writew 0x4e00000c 0x46084a4a +writel 0x4e00000c 0x5c022fcc +clock_step +writel 0x4e000004 0x2fffa1b1 +clock_step +readl 0x4e000008 +EOF +``` +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2759 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2759 new file mode 100644 index 000000000..1f4e50c62 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2759 @@ -0,0 +1 @@ +hw/usb/redirect.c: usbredir_buffered_bulk_packet() may leak memory (or worse) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/276 b/gitlab/issues_text/target_missing/host_missing/accel_missing/276 new file mode 100644 index 000000000..8c8887d94 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/276 @@ -0,0 +1 @@ +Error in user-mode calculation of ELF program's brk diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2761 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2761 new file mode 100644 index 000000000..9851c07c5 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2761 @@ -0,0 +1,8 @@ +Emulation of x86_64 binary on ARM64 fails with "Unable to find a guest_base to satisfy all guest address mapping requirements" +Description of problem: +Virtualisation fails with error "Unable to find a guest_base to satisfy all guest address mapping requirements" + +``` +file /nix/store/razasrvdg7ckplfmvdxv4ia3wbayr94s-bootstrap-tools/bin/bash +/nix/store/razasrvdg7ckplfmvdxv4ia3wbayr94s-bootstrap-tools/bin/bash: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /nix/store/razasrvdg7ckplfmvdxv4ia3wbayr94s-bootstrap-tools/lib/ld-linux-x86-64.so.2, for GNU/Linux 3.10.0, BuildID[sha1]=2938b076ebbc4ea582b8eb1ea5c3f65d7a1b6261, stripped +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2762 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2762 new file mode 100644 index 000000000..7d3154d47 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2762 @@ -0,0 +1,5 @@ +virtio-net regression for aarch64 guests +Description of problem: +The host system is running DHCP via dnsmasq 2.88. QEMU 9.1 works properly and completes DHCP handshake. QEMU 9.2 fails the DHCP handshake after DHCPOFFER with "eth0: checksum failure from 10.2.83.1". + +I found by bisecting that the issue was introduced by commit 7987d2be5a8bc3a502f89ba8cf3ac3e09f64d1ce "virtio-net: Copy received header to buffer". Reverting that commit on 9.2.0 corrects the issue. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2764 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2764 new file mode 100644 index 000000000..84632bb9d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2764 @@ -0,0 +1,47 @@ +W32 Docker build fails +Description of problem: +Docker build fails: + +``` +make docker-test-mingw@fedora-win64-cross V=1 J=4 +``` + +with the following error: + +``` +Initialized empty Git repository in /tmp/qemu-test/src/subprojects/dtc/.git/ +fatal: unable to access 'https://gitlab.com/qemu-project/dtc.git/': Could not resolve host: gitlab.com + +../meson.build:2090:16: ERROR: Git command failed: ['/usr/bin/git', 'fetch', '--depth', '1', 'origin', 'b6910bec11614980a21e46fbccc35934b671bd81'] +``` +Steps to reproduce: +1. `make docker-test-mingw@fedora-win64-cross V=1 J=4 DEBUG=1` +2. `cd $QEMU_SRC` +3. `mkdir build` +4. `cd build` +5. `../configure --cross-prefix=x86_64-w64-mingw32-` +Additional information: +The problem can be worked around by changing the line + +``` +subprojects="keycodemapdb libvfio-user berkeley-softfloat-3 berkeley-testfloat-3" +``` + +to + +``` +subprojects="keycodemapdb libvfio-user berkeley-softfloat-3 berkeley-testfloat-3 dtc" +``` + +in `archive-source.sh`. + +Additionally, https://wiki.qemu.org/Hosts/W32#Docker_based_cross_builds is outdated. +``` +make docker-test-mingw@fedora V=1 DEBUG=1 J=4 +``` +should be +``` +make docker-test-mingw@fedora-win64-cross V=1 DEBUG=1 J=4 +``` + +Additionally, i would suggest to create and enter build directory before calling configure and also add the make commands as shown in the "Steps to reproduce" section of this ticket. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2765 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2765 new file mode 100644 index 000000000..c43fbf60e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2765 @@ -0,0 +1 @@ +InputMethodKit warnings on macOS Sequoia diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2766 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2766 new file mode 100644 index 000000000..4e7513ff3 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2766 @@ -0,0 +1,23 @@ +Qemu 9.2: stubs: build issue with --enable-user --disable-system --enable-tools +Description of problem: +Since commit "[stubs: avoid duplicate symbols in libqemuutil.a](https://gitlab.com/qemu-project/qemu/-/commit/388b849fb6c33882b481123568995a749a54f648)", Qemu doesn't build with: + + ./configure --enable-user --disable-system --enable-tools + + /usr/bin/ld: libhwcore.a.p/hw_core_qdev.c.o: in function 'device_finalize': \ + /home/autobuild/autobuild/instance-2/output-1/build/host-qemu-9.2.0/build/../hw/core/qdev.c:689:(.text+0x75c): undefined reference to 'qapi_event_send_device_deleted' + collect2: error: ld returned 1 exit status + +See Buildroot automated build results: +http://autobuild.buildroot.org/?reason=host-qemu-9.2.0 + +Indeed, with have_system = false and have_tools = true, Qemu needs the stubs for QAPI events added by stub_ss.add(files('qdev.c')) to provide qapi_event_send_device_deleted. + +Maybe the change in stubs/meson.build should have been: \ + +if not have_system and have_tools \ +stub_ss.add(files('qdev.c')) \ +endif + +Best regards, +Romain diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2767 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2767 new file mode 100644 index 000000000..e7fbd59ce --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2767 @@ -0,0 +1,37 @@ +sigfaul on netdev stream +Description of problem: +qemu sigfault if use netdev socket and hubport +Steps to reproduce: +1. Preconfigure network interface on /etc/network/interface or try connect from qemu server port another qemu process or other softvare (gnuradio, etc) +``` +auto qt-test0 +iface qt-test0 + address 192.168.10.1/30 + mtu 16384 + pre-up ip tuntap add $IFACE mode tap + post-down ip link del dev $IFACE +``` +2. Run qemu from the cmdline +Additional information: +``` +(gdb) bt +#0 0x0000555555b547d0 in object_get_class () +#1 0x0000555555b9d44c in qio_channel_writev () +#2 0x000055555598295c in ?? () +#3 0x000055555597cf67 in ?? () +#4 0x0000555555980eb9 in qemu_net_queue_send_iov () +#5 0x000055555597b8e4 in ?? () +#6 0x000055555597ce32 in ?? () +#7 0x0000555555980df5 in qemu_net_queue_send () +#8 0x000055555598fb52 in ?? () +#9 0x0000555555d26755 in ?? () +#10 0x0000555555d270d2 in aio_dispatch () +#11 0x0000555555d3f5ef in ?? () +#12 0x00007ffff70f100e in ?? () from /usr/lib/libglib-2.0.so.0 +#13 0x00007ffff70f4988 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 +#14 0x0000555555d40f69 in main_loop_wait () +#15 0x000055555592fc83 in qemu_main_loop () +#16 0x0000555555c7c817 in qemu_default_main () +#17 0x00007ffff7f9a496 in libc_start_main_stage2 (main=0x5555556cc0f0 <main>, argc=12, argv=0x7fffffffebd8) at src/env/__libc_start_main.c:95 +#18 0x00005555556cd0d8 in _start () +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/277 b/gitlab/issues_text/target_missing/host_missing/accel_missing/277 new file mode 100644 index 000000000..50063db7c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/277 @@ -0,0 +1 @@ +Multi-queue vhost-user fails to reconnect with qemu version >=4.2 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2770 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2770 new file mode 100644 index 000000000..2a082a565 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2770 @@ -0,0 +1,14 @@ +Build failure due to missing keyctl_pkey_encrypt +Description of problem: + +Steps to reproduce: +1. git checkout v7.2.0 +2. ./configure --target-list=arm-softmmu;make +3. ../backends/cryptodev-lkcf.c: In function ‘cryptodev_lkcf_execute_task’: +../backends/cryptodev-lkcf.c:358:19: error: implicit declaration of function ‘keyctl_pkey_encrypt’; did you mean ‘keyctl_reject’? [-Werror=implicit-function-declaration] + ret = keyctl_pkey_encrypt(key_id, op_desc, + ^~~~~~~~~~~~~~~~~~~ + keyctl_reject +../backends/cryptodev-lkcf.c:358:19: error: nested extern declaration of ‘keyctl_pkey_encrypt’ [-Werror=nested-externs] +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2771 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2771 new file mode 100644 index 000000000..bf4356347 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2771 @@ -0,0 +1 @@ +qemu-system-x86_64: ../block/block-backend.c:1290: blk_in_drain: Assertion `qemu_in_main_thread()' failed. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2772 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2772 new file mode 100644 index 000000000..827fe2fb1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2772 @@ -0,0 +1,74 @@ +qemu-img map command omits `offset` key in output for encrypted qcow2 files +Description of problem: +We use the `qemu-img map` command to retrieve metadata information from a qcow2 image. It functions as expected for non-encrypted qcow2 images. However, when the same command is executed on an encrypted qcow2 image, the output omits the `offset` key, which is critical for subsequent processing in our workflow. +Steps to reproduce: +1. Run qemu-img map on the encrypted incremental qcow2: +Command: + +``` + qemu-img map --object secret,id=sec0,data=trilio --output json -U --image-opts driver=qcow2,file.filename=incremental.qcow2,encrypt.format=luks,encrypt.key-secret=sec0 +``` +**Observed Output:** The command executes but does not include the offset key in the JSON output. +For example: +``` +[{ "start": 32191217664, "length": 65536, "depth": 1, "present": true, "zero": false, "data": true}, +{ "start": 32191283200, "length": 2031616, "depth": 1, "present": false, "zero": true, "data": false}, +{ "start": 32193314816, "length": 65536, "depth": 1, "present": true, "zero": false, "data": true}, +{ "start": 32193380352, "length": 2031616, "depth": 1, "present": false, "zero": true, "data": false}, +{ "start": 32195411968, "length": 65536, "depth": 1, "present": true, "zero": false, "data": true}, +{ "start": 32195477504, "length": 2031616, "depth": 1, "present": false, "zero": true, "data": false}, +{ "start": 32197509120, "length": 65536, "depth": 1, "present": true, "zero": false, "data": true}, +{ "start": 32197574656, "length": 2031616, "depth": 1, "present": false, "zero": true, "data": false}, +{ "start": 32199606272, "length": 65536, "depth": 1, "present": true, "zero": false, "data": true}, +{ "start": 32199671808, "length": 2031616, "depth": 1, "present": false, "zero": true, "data": false}, +{ "start": 32201703424, "length": 65536, "depth": 1, "present": true, "zero": false, "data": true}, +{ "start": 32201768960, "length": 2031616, "depth": 1, "present": false, "zero": true, "data": false}, +{ "start": 32203800576, "length": 65536, "depth": 1, "present": true, "zero": false, "data": true}, +{ "start": 32203866112, "length": 2031616, "depth": 1, "present": false, "zero": true, "data": false}, +{ "start": 32205897728, "length": 65536, "depth": 1, "present": true, "zero": false, "data": true}, +{ "start": 32205963264, "length": 2031616, "depth": 1, "present": false, "zero": true, "data": false}, +{ "start": 32207994880, "length": 65536, "depth": 1, "present": true, "zero": false, "data": true}, +{ "start": 32208060416, "length": 2031616, "depth": 1, "present": false, "zero": true, "data": false}, +{ "start": 32210092032, "length": 65536, "depth": 1, "present": true, "zero": false, "data": true}, +{ "start": 32210157568, "length": 2031616, "depth": 1, "present": false, "zero": true, "data": false}, +{ "start": 32212189184, "length": 65536, "depth": 1, "present": true, "zero": false, "data": true}] +``` + +2. Decrypt the same encrypted incremental qcow2 image and re-run the qemu-img map command: +**Decryption command:** +``` +qemu-img convert -t writeback --object secret,id=sec0,data=trilio -O qcow2 --image-opts driver=qcow2,encrypt.key-secret=sec0,file.filename=incremental.qcow2 decrypt.qcow2 +``` +3. Run qemu-img map on the decrypted image: +**Command:** +``` +qemu-img map --output json -U decrypt.qcow2 +``` +Here, we don't need to pass the encryption key as we have already decrypted the qcow2. + +**Observed Output:** The JSON output includes the offset key as expected. Example: +``` +[{ "start": 0, "length": 106954752, "depth": 0, "present": false, "zero": true, "data": false}, +{ "start": 106954752, "length": 2097152, "depth": 0, "present": true, "zero": false, "data": true, "offset": 327680}, +{ "start": 109051904, "length": 786432000, "depth": 0, "present": false, "zero": true, "data": false}, +{ "start": 895483904, "length": 2097152, "depth": 0, "present": true, "zero": false, "data": true, "offset": 2490368}, +{ "start": 897581056, "length": 1866924032, "depth": 0, "present": false, "zero": true, "data": false}, +{ "start": 2764505088, "length": 1638400, "depth": 0, "present": true, "zero": false, "data": true, "offset": 4653056}, +{ "start": 2766143488, "length": 402587648, "depth": 0, "present": false, "zero": true, "data": false}, +{ "start": 3168731136, "length": 2162688, "depth": 0, "present": true, "zero": false, "data": true, "offset": 6291456}, +{ "start": 3170893824, "length": 140443648, "depth": 0, "present": false, "zero": true, "data": false}, +{ "start": 3311337472, "length": 54394880, "depth": 0, "present": true, "zero": false, "data": true, "offset": 8519680}, +{ "start": 3365732352, "length": 2056388608, "depth": 0, "present": false, "zero": true, "data": false}, +{ "start": 5422120960, "length": 1114112, "depth": 0, "present": true, "zero": false, "data": true, "offset": 62980096}, +{ "start": 5423235072, "length": 4128768, "depth": 0, "present": false, "zero": true, "data": false}, +{ "start": 5427363840, "length": 2162688, "depth": 0, "present": true, "zero": false, "data": true, "offset": 64094208}, +{ "start": 5429526528, "length": 469696512, "depth": 0, "present": false, "zero": true, "data": false}, +{ "start": 5899223040, "length": 2162688, "depth": 0, "present": true, "zero": false, "data": true, "offset": 66256896}, +{ "start": 5901385728, "length": 90112000, "depth": 0, "present": false, "zero": true, "data": false}, +{ "start": 5991497728, "length": 1638400, "depth": 0, "present": true, "zero": false, "data": true, "offset": 68485120}, +{ "start": 5993136128, "length": 2086600704, "depth": 0, "present": false, "zero": true, "data": false}, +{ "start": 8079736832, "length": 2686976, "depth": 0, "present": true, "zero": false, "data": true, "offset": 70189056}, +{ "start": 8082423808, "length": 24129830912, "depth": 0, "present": false, "zero": true, "data": false}] +``` + +The missing `offset` key in the output of the `qemu-img map` command for encrypted qcow2 images disrupts downstream processes that rely on this metadata. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2774 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2774 new file mode 100644 index 000000000..cd620a535 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2774 @@ -0,0 +1,3 @@ +Consider adding an `aliases` node to RISC-V DTB that includes `serial0` alias +Additional information: +Example of an [aliases section for physical SoC](https://github.com/torvalds/linux/blob/b62cef9a5c673f1b8083159f5dc03c1c5daced2f/arch/riscv/boot/dts/sophgo/cv1800b-milkv-duo.dts#L14-L20). diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2776 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2776 new file mode 100644 index 000000000..8f1ddb734 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2776 @@ -0,0 +1 @@ +OHCI: Incorrectly reports an overrun error diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2777 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2777 new file mode 100644 index 000000000..4c48c61e4 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2777 @@ -0,0 +1,59 @@ +Assert failure in ahci-hd device +Description of problem: +Assert + +``` +qemu-system-x86_64: ../hw/ide/core.c:934: void ide_dma_cb(void *, int): Assertion `prep_size >= 0 && prep_size <= n * 512' failed. +``` +can be triggered with some qtest commands. This was found by fuzzing. +Steps to reproduce: +Command: + +``` +cat << EOF | ./qemu-system-x86_64 -display none -machine accel=qtest, -m 512M -machine q35 -nodefaults -drive file=null-co://,if=none,format=raw,id=disk0 -device ide-hd,drive=disk0 -qtest stdio +outl 0xcf8 0x8000fa24 +outl 0xcfc 0xe0000000 +outl 0xcf8 0x8000fa04 +outw 0xcfc 0x06 +write 0x0 0x1 0x27 +write 0x1 0x1 0x80 +write 0x2 0x1 0x25 +write 0xe00003b8 0x1 0x02 +write 0xe0000398 0x1 0x01 +EOF +``` + +Results in + +``` +[I 0.000001] OPENED +[R +0.076075] outl 0xcf8 0x8000fa24 +[S +0.076165] OK +OK +[R +0.076198] outl 0xcfc 0xe0000000 +[S +0.076242] OK +OK +[R +0.076320] outl 0xcf8 0x8000fa04 +[S +0.076344] OK +OK +[R +0.076379] outw 0xcfc 0x06 +[S +0.077676] OK +OK +[R +0.077760] write 0x0 0x1 0x27 +[S +0.079429] OK +OK +[R +0.079552] write 0x1 0x1 0x80 +[S +0.079592] OK +OK +[R +0.079618] write 0x2 0x1 0x25 +[S +0.079645] OK +OK +[R +0.079669] write 0xe00003b8 0x1 0x02 +[S +0.079709] OK +OK +[R +0.079733] write 0xe0000398 0x1 0x01 +qemu-system-x86_64: ../hw/ide/core.c:934: void ide_dma_cb(void *, int): Assertion `prep_size >= 0 && prep_size <= n * 512' failed. +Aborted +``` +Additional information: +Maybe we can just `goto eot;` instead of assert? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2778 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2778 new file mode 100644 index 000000000..4f540ae9c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2778 @@ -0,0 +1,99 @@ +Null Dereference in ahci-hd device +Description of problem: +Issue was found by fuzzing. With some qtest commands we can crash qemu-system-x86_64 because of Null dereference. +Steps to reproduce: +Command: + +``` +cat << EOF | ./qemu-system-x86_64 -display none -machine accel=qtest -m 512M -machine q35 -nodefaults -drive file=null-co://,if=none,format=raw,id=disk0 -device ide-hd,drive=disk0 -qtest stdio +outl 0xcf8 0x8000fa24 +outl 0xcfc 0xe0000000 +outl 0xcf8 0x8000fa04 +outw 0xcfc 0x06 +write 0xe00003b8 0x1 0x01 +write 0x0 0x1 0x27 +write 0x1 0x1 0x80 +write 0x2 0x1 0x20 +write 0x7 0x1 0x01 +write 0xe0000398 0x1 0x01 +write 0xe0000398 0x1 0x00 +write 0xe0000398 0x1 0x01 +EOF +``` + +Results in + +``` +[I 0.000001] OPENED +[R +0.082978] outl 0xcf8 0x8000fa24 +[S +0.083040] OK +OK +[R +0.083070] outl 0xcfc 0xe0000000 +[S +0.083115] OK +OK +[R +0.083132] outl 0xcf8 0x8000fa04 +[S +0.083152] OK +OK +[R +0.083180] outw 0xcfc 0x06 +[S +0.084233] OK +OK +[R +0.084291] write 0xe00003b8 0x1 0x01 +[S +0.084344] OK +OK +[R +0.084384] write 0x0 0x1 0x27 +[S +0.085007] OK +OK +[R +0.085041] write 0x1 0x1 0x80 +[S +0.085055] OK +OK +[R +0.085071] write 0x2 0x1 0x20 +[S +0.085084] OK +OK +[R +0.085096] write 0x7 0x1 0x01 +[S +0.085110] OK +OK +[R +0.085123] write 0xe0000398 0x1 0x01 +[S +0.085254] OK +OK +[R +0.085294] write 0xe0000398 0x1 0x00 +[S +0.085324] OK +OK +[R +0.085349] write 0xe0000398 0x1 0x01 +[S +0.085408] OK +OK +../hw/ide/ahci.c:1377:46: runtime error: member access within null pointer of type 'AHCICmdHdr' (aka 'struct AHCICmdHdr') +SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior ../hw/ide/ahci.c:1377:46 in +../hw/ide/ahci.c:1377:46: runtime error: load of null pointer of type 'uint16_t' (aka 'unsigned short') +SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior ../hw/ide/ahci.c:1377:46 in +AddressSanitizer:DEADLYSIGNAL +================================================================= +==2547739==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x55abf3a79f9c bp 0x7ffc213000d0 sp 0x7ffc212fffa0 T0) +==2547739==The signal is caused by a READ memory access. +==2547739==Hint: address points to the zero page. + #0 0x55abf3a79f9c in ahci_pio_transfer /home/artemiin/Work/original_qemu/build/../hw/ide/ahci.c:1377:46 + #1 0x55abf3a8a396 in ide_transfer_start_norecurse /home/artemiin/Work/original_qemu/build/../hw/ide/core.c:581:5 + #2 0x55abf3aab79e in ide_transfer_start /home/artemiin/Work/original_qemu/build/../hw/ide/core.c:588:9 + #3 0x55abf3aab79e in ide_sector_read_cb /home/artemiin/Work/original_qemu/build/../hw/ide/core.c:789:5 + #4 0x55abf3a8d6e2 in ide_buffered_readv_cb /home/artemiin/Work/original_qemu/build/../hw/ide/core.c:684:9 + #5 0x55abf4f31d33 in blk_aio_complete /home/artemiin/Work/original_qemu/build/../block/block-backend.c:1552:9 + #6 0x55abf545010b in aio_bh_call /home/artemiin/Work/original_qemu/build/../util/async.c:172:5 + #7 0x55abf545089f in aio_bh_poll /home/artemiin/Work/original_qemu/build/../util/async.c:219:13 + #8 0x55abf53e746a in aio_dispatch /home/artemiin/Work/original_qemu/build/../util/aio-posix.c:424:5 + #9 0x55abf545469a in aio_ctx_dispatch /home/artemiin/Work/original_qemu/build/../util/async.c:361:5 + #10 0x7f358845b7a8 in g_main_context_dispatch (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x547a8) (BuildId: 9f90bd7bbfcf84a1f1c5a6102f70e6264837b9d4) + #11 0x55abf5455787 in glib_pollfds_poll /home/artemiin/Work/original_qemu/build/../util/main-loop.c:287:9 + #12 0x55abf5455787 in os_host_main_loop_wait /home/artemiin/Work/original_qemu/build/../util/main-loop.c:310:5 + #13 0x55abf5455787 in main_loop_wait /home/artemiin/Work/original_qemu/build/../util/main-loop.c:589:11 + #14 0x55abf425c296 in qemu_main_loop /home/artemiin/Work/original_qemu/build/../system/runstate.c:835:9 + #15 0x55abf51df1c6 in qemu_default_main /home/artemiin/Work/original_qemu/build/../system/main.c:48:14 + #16 0x55abf51df1a1 in main /home/artemiin/Work/original_qemu/build/../system/main.c:76:9 + #17 0x7f3587219249 in __libc_start_call_main csu/../sysdeps/nptl/libc_start_call_main.h:58:16 + #18 0x7f3587219304 in __libc_start_main csu/../csu/libc-start.c:360:3 + #19 0x55abf353be60 in _start (/home/artemiin/Work/original_qemu/build/qemu-system-x86_64+0x1828e60) (BuildId: f91712a3af40a999ce35e39809ce00f92c35ae25) + +AddressSanitizer can not provide additional info. +SUMMARY: AddressSanitizer: SEGV /home/artemiin/Work/original_qemu/build/../hw/ide/ahci.c:1377:46 in ahci_pio_transfer +==2547739==ABORTING +``` +Additional information: +This issue may need a complicated patch so I ask developers to take a look at this issue. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/278 b/gitlab/issues_text/target_missing/host_missing/accel_missing/278 new file mode 100644 index 000000000..86c42cc46 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/278 @@ -0,0 +1 @@ +jack audio dev produces no sound diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2780 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2780 new file mode 100644 index 000000000..d16b99d57 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2780 @@ -0,0 +1,17 @@ +Out-of-bounds access in smc91c111_receive() +Description of problem: +An out-of-bounds access happens at hw/net/smc91c111.c:705. + +`hw/net/smc91c111.c:705:5: runtime error: index -1 out of bounds for type 'int[4]'` +Steps to reproduce: +``` +export QEMU_ARGS="-display none -machine accel=qtest, -m 512M -machine realview-eb" +cat << EOF | ./qemu-system-arm $QEMU_ARGS -qtest /dev/null -qtest stdio +writew 0x4e000005 0x227 +writel 0x4e00000b 0x25ab1f2 +writew 0x4e000000 0xaa6c +clock_step +EOF +``` +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2781 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2781 new file mode 100644 index 000000000..075a4210b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2781 @@ -0,0 +1 @@ +Open logfiles for append diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2785 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2785 new file mode 100644 index 000000000..d882eab95 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2785 @@ -0,0 +1,16 @@ +Cannot build qemu after the latest addition of NBD docs +Description of problem: +``` +[5584/5962] Generating docs/QEMU manual with a custom command +FAILED: docs/docs.stamp +"C:\msys64\usr\bin/env.EXE" "CONFDIR=etc/" "C:/msys64/home/user/qemu/build/pyvenv/bin/sphinx-build.exe" "-q" "-W" "-Dkerneldoc_werror=1" "-j" "auto" "-Dversion=9.2.50" "-Drelease=" "-Ddepfile=docs/docs.d" "-Ddepfile_stamp=docs/docs.stamp" "-b" "html" "-d" "C:/msys64/home/user/qemu/build/docs/manual.p" "C:/msys64/home/user/qemu/docs" "C:/msys64/home/user/qemu/build/docs/manual" +C:/msys64/home/user/qemu/docs/system/qemu-block-drivers.rst.inc:506: WARNING: duplicate label nbd, other instance in C:/msys64/home/user/qemu/docs/system/images.rst +[5593/5962] Compiling C object tests/qtest/ide-test.exe.p/ide-test.c.obj +ninja: build stopped: subcommand failed. +``` +Steps to reproduce: +1.meson compile +2. +3. +Additional information: +excluding NBD from the build targets allows successful compilation diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2786 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2786 new file mode 100644 index 000000000..00984e9e1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2786 @@ -0,0 +1,11 @@ +deleting files fails on vvfat (was: "error handling renames") +Description of problem: +When working with files, renaming or saving from IDE, QEMU halts with the error message: + +"Error handling renames (-2)" +Steps to reproduce: +1. +2. +3. +Additional information: +a previous del failed, the directories are not synced so the rename on the drive fails when the file with the target file name still exists on the real directory. So the real issue is a failed del. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2788 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2788 new file mode 100644 index 000000000..9f51a439e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2788 @@ -0,0 +1,13 @@ +[solved] input mouse and keyboard not working on a distro +Description of problem: +The distro work but does not take input from either keyboard or mouse. +At the boot menu (syslinux) where I have to choose the boot mode the keyboard works, but it stops working when the desktop has booted. +The distro is not blocked I can tell by observing that the clock in the panel keeps running and if I click in the qemu menubar on machine > power down, the distro correctly performs the shutdown procedure. +I have tried other distributions (porteus and tinycore) and both do not have this problem. +I also tried using as -display vnc and sdl but I have the same problem. +I am using a [portable version of qemu](https://gitlab.com/qemu-project/qemu/-/issues/new) but I also tried with the repository version having the same problem. +Steps to reproduce: +Simply boot the virtual machine with the distro, in my case with the portable qemu version: +./QEMU-git-x86_64.AppImage qemu-system-x86_64 -m 512 -enable-kvm -boot d -cdrom ./Nemesis-v25.01-XFCE-x86_64.iso +Additional information: +I am not expert in qemu, if you need some more data I can try to produce it diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2789 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2789 new file mode 100644 index 000000000..7915c6eb9 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2789 @@ -0,0 +1 @@ +Emulate a folder instead of creating the iso diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2793 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2793 new file mode 100644 index 000000000..cf2fb808e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2793 @@ -0,0 +1,242 @@ +Upgrading from qemu-kvm-* (17:9.1.0-7.el9) to (17:9.1.0-9.el9) causes VM to crash within cockpit-machines (v326-1.el9) with qemu-kvm: ../qapi/qobject-output-visitor.c:95: void qobject_output_add_obj(QObjectOutputVisitor *, const char *, QObject *): Assert +Description of problem: +** From the /var/log/libvirt/qemu/WinDesktop03-log ** + +2025-01-21 21:50:57.464+0000: Starting external device: TPM Emulator +/usr/bin/swtpm socket --ctrl type=unixio,path=/run/libvirt/qemu/swtpm/1-WinDesktop-03-swtpm.sock,mode=0600 --tpmstate dir=/var/lib/libvirt/swtpm/fb44aa6f-8127-4df7-afc3-2ba54b7b7790/tpm2,mode=0600 --log file=/var/log/swtpm/libvirt/qemu/WinDesktop-03-swtpm.log --terminate --tpm2 +2025-01-21 21:50:57.501+0000: starting up libvirt version: 10.10.0, package: 3.el9 (builder@centos.org, 2024-12-20-13:49:58, ), qemu version: 9.1.0qemu-kvm-9.1.0-7.el9, kernel: 6.12.9, hostname: amd-strat-3 +LC_ALL=C \ +PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin \ +HOME=/var/lib/libvirt/qemu/domain-1-WinDesktop-03 \ +XDG_DATA_HOME=/var/lib/libvirt/qemu/domain-1-WinDesktop-03/.local/share \ +XDG_CACHE_HOME=/var/lib/libvirt/qemu/domain-1-WinDesktop-03/.cache \ +XDG_CONFIG_HOME=/var/lib/libvirt/qemu/domain-1-WinDesktop-03/.config \ +/usr/libexec/qemu-kvm \ +-name guest=WinDesktop-03,debug-threads=on \ +-S \ +-object '{"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-1-WinDesktop-03/master-key.aes"}' \ +-blockdev '{"driver":"file","filename":"/usr/share/edk2/ovmf/OVMF_CODE.secboot.fd","node-name":"libvirt-pflash0-storage","auto-read-only":true,"discard":"unmap"}' \ +-blockdev '{"node-name":"libvirt-pflash0-format","read-only":true,"driver":"raw","file":"libvirt-pflash0-storage"}' \ +-blockdev '{"driver":"file","filename":"/var/lib/libvirt/qemu/nvram/WinDesktop-03_VARS.fd","node-name":"libvirt-pflash1-storage","read-only":false}' \ +-machine pc-q35-rhel9.6.0,usb=off,smm=on,dump-guest-core=off,memory-backend=pc.ram,pflash0=libvirt-pflash0-format,pflash1=libvirt-pflash1-storage,hpet=off,acpi=on \ +-accel kvm \ +-cpu host,migratable=on,hv-time=on,hv-relaxed=on,hv-vapic=on,hv-spinlocks=0x1fff,hv-vpindex=on,hv-runtime=on,hv-synic=on,hv-stimer=on,hv-frequencies=on,hv-tlbflush=on,hv-ipi=on,hv-avic=on \ +-global driver=cfi.pflash01,property=secure,value=on \ +-m size=8388608k \ +-object '{"qom-type":"memory-backend-ram","id":"pc.ram","size":8589934592}' \ +-overcommit mem-lock=off \ +-smp 8,sockets=1,dies=1,clusters=1,cores=8,threads=1 \ +-uuid fb44aa6f-8127-4df7-afc3-2ba54b7b7790 \ +-no-user-config \ +-nodefaults \ +-chardev socket,id=charmonitor,fd=23,server=on,wait=off \ +-mon chardev=charmonitor,id=monitor,mode=control \ +-rtc base=localtime,driftfix=slew \ +-global kvm-pit.lost_tick_policy=delay \ +-no-shutdown \ +-global ICH9-LPC.disable_s3=1 \ +-global ICH9-LPC.disable_s4=1 \ +-boot strict=on \ +-device '{"driver":"pcie-root-port","port":16,"chassis":1,"id":"pci.1","bus":"pcie.0","multifunction":true,"addr":"0x2"}' \ +-device '{"driver":"pcie-root-port","port":17,"chassis":2,"id":"pci.2","bus":"pcie.0","addr":"0x2.0x1"}' \ +-device '{"driver":"pcie-root-port","port":18,"chassis":3,"id":"pci.3","bus":"pcie.0","addr":"0x2.0x2"}' \ +-device '{"driver":"pcie-root-port","port":19,"chassis":4,"id":"pci.4","bus":"pcie.0","addr":"0x2.0x3"}' \ +-device '{"driver":"pcie-root-port","port":20,"chassis":5,"id":"pci.5","bus":"pcie.0","addr":"0x2.0x4"}' \ +-device '{"driver":"pcie-root-port","port":21,"chassis":6,"id":"pci.6","bus":"pcie.0","addr":"0x2.0x5"}' \ +-device '{"driver":"pcie-root-port","port":22,"chassis":7,"id":"pci.7","bus":"pcie.0","addr":"0x2.0x6"}' \ +-device '{"driver":"pcie-root-port","port":23,"chassis":8,"id":"pci.8","bus":"pcie.0","addr":"0x2.0x7"}' \ +-device '{"driver":"pcie-root-port","port":24,"chassis":9,"id":"pci.9","bus":"pcie.0","multifunction":true,"addr":"0x3"}' \ +-device '{"driver":"pcie-root-port","port":25,"chassis":10,"id":"pci.10","bus":"pcie.0","addr":"0x3.0x1"}' \ +-device '{"driver":"pcie-root-port","port":26,"chassis":11,"id":"pci.11","bus":"pcie.0","addr":"0x3.0x2"}' \ +-device '{"driver":"pcie-root-port","port":27,"chassis":12,"id":"pci.12","bus":"pcie.0","addr":"0x3.0x3"}' \ +-device '{"driver":"pcie-root-port","port":28,"chassis":13,"id":"pci.13","bus":"pcie.0","addr":"0x3.0x4"}' \ +-device '{"driver":"pcie-root-port","port":29,"chassis":14,"id":"pci.14","bus":"pcie.0","addr":"0x3.0x5"}' \ +-device '{"driver":"qemu-xhci","p2":15,"p3":15,"id":"usb","bus":"pci.2","addr":"0x0"}' \ +-device '{"driver":"virtio-serial-pci","id":"virtio-serial0","bus":"pci.4","addr":"0x0"}' \ +-blockdev '{"driver":"file","filename":"/stratistor/clustermounts/machines/WinDesktop-03/WinDesktop-03.qcow2","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' \ +-blockdev '{"node-name":"libvirt-1-format","read-only":false,"driver":"qcow2","file":"libvirt-1-storage","backing":null}' \ +-device '{"driver":"ide-hd","bus":"ide.0","drive":"libvirt-1-format","id":"sata0-0-0","bootindex":1}' \ +-netdev '{"type":"tap","fd":"25","vhost":true,"vhostfd":"27","id":"hostnet0"}' \ +-device '{"driver":"virtio-net-pci","netdev":"hostnet0","id":"net0","mac":"52:54:00:d4:af:c9","bus":"pci.1","addr":"0x0"}' \ +-chardev pty,id=charserial0 \ +-device '{"driver":"isa-serial","chardev":"charserial0","id":"serial0","index":0}' \ +-chardev socket,id=charchannel0,fd=22,server=on,wait=off \ +-device '{"driver":"virtserialport","bus":"virtio-serial0.0","nr":1,"chardev":"charchannel0","id":"channel0","name":"org.qemu.guest_agent.0"}' \ +-chardev socket,id=chrtpm,path=/run/libvirt/qemu/swtpm/1-WinDesktop-03-swtpm.sock \ +-tpmdev emulator,id=tpm-tpm0,chardev=chrtpm \ +-device '{"driver":"tpm-crb","tpmdev":"tpm-tpm0","id":"tpm0"}' \ +-device '{"driver":"usb-tablet","id":"input0","bus":"usb.0","port":"1"}' \ +-audiodev '{"id":"audio1","driver":"none"}' \ +-vnc 0.0.0.0:0,audiodev=audio1 \ +-device '{"driver":"virtio-vga","id":"video0","max_outputs":1,"bus":"pcie.0","addr":"0x1"}' \ +-global ICH9-LPC.noreboot=off \ +-watchdog-action reset \ +-incoming defer \ +-device '{"driver":"virtio-balloon-pci","id":"balloon0","bus":"pci.3","addr":"0x0"}' \ +-sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ +-msg timestamp=on +2025-01-21 21:50:57.502+0000: Domain id=1 is tainted: high-privileges +2025-01-21 21:50:57.502+0000: Domain id=1 is tainted: host-cpu +char device redirected to /dev/pts/0 (label charserial0) +2025-01-21 21:51:07.797+0000: Domain id=1 is tainted: custom-ga-command +2025-01-25T20:54:12.923119Z qemu-kvm: terminating on signal 15 from pid 279229 (/usr/sbin/virtqemud) +2025-01-25 20:54:13.215+0000: shutting down, reason=shutdown +2025-01-25 20:54:18.392+0000: Starting external device: TPM Emulator +/usr/bin/swtpm socket --ctrl type=unixio,path=/run/libvirt/qemu/swtpm/2-WinDesktop-03-swtpm.sock,mode=0600 --tpmstate dir=/var/lib/libvirt/swtpm/fb44aa6f-8127-4df7-afc3-2ba54b7b7790/tpm2,mode=0600 --log file=/var/log/swtpm/libvirt/qemu/WinDesktop-03-swtpm.log --terminate --tpm2 +2025-01-25 20:54:18.414+0000: starting up libvirt version: 10.10.0, package: 3.el9 (builder@centos.org, 2024-12-20-13:49:58, ), qemu version: 9.1.0qemu-kvm-9.1.0-9.el9, kernel: 6.12.9, hostname: amd-strat-3 +LC_ALL=C \ +PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin \ +HOME=/var/lib/libvirt/qemu/domain-2-WinDesktop-03 \ +XDG_DATA_HOME=/var/lib/libvirt/qemu/domain-2-WinDesktop-03/.local/share \ +XDG_CACHE_HOME=/var/lib/libvirt/qemu/domain-2-WinDesktop-03/.cache \ +XDG_CONFIG_HOME=/var/lib/libvirt/qemu/domain-2-WinDesktop-03/.config \ +/usr/libexec/qemu-kvm \ +-name guest=WinDesktop-03,debug-threads=on \ +-S \ +-object '{"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-2-WinDesktop-03/master-key.aes"}' \ +-blockdev '{"driver":"file","filename":"/usr/share/edk2/ovmf/OVMF_CODE.secboot.fd","node-name":"libvirt-pflash0-storage","auto-read-only":true,"discard":"unmap"}' \ +-blockdev '{"node-name":"libvirt-pflash0-format","read-only":true,"driver":"raw","file":"libvirt-pflash0-storage"}' \ +-blockdev '{"driver":"file","filename":"/var/lib/libvirt/qemu/nvram/WinDesktop-03_VARS.fd","node-name":"libvirt-pflash1-storage","read-only":false}' \ +-machine pc-q35-rhel9.6.0,usb=off,smm=on,dump-guest-core=off,memory-backend=pc.ram,pflash0=libvirt-pflash0-format,pflash1=libvirt-pflash1-storage,hpet=off,acpi=on \ +-accel kvm \ +-cpu host,migratable=on,hv-time=on,hv-relaxed=on,hv-vapic=on,hv-spinlocks=0x1fff,hv-vpindex=on,hv-runtime=on,hv-synic=on,hv-stimer=on,hv-frequencies=on,hv-tlbflush=on,hv-ipi=on,hv-avic=on \ +-global driver=cfi.pflash01,property=secure,value=on \ +-m size=8388608k \ +-object '{"qom-type":"memory-backend-ram","id":"pc.ram","size":8589934592}' \ +-overcommit mem-lock=off \ +-smp 8,sockets=1,dies=1,clusters=1,cores=8,threads=1 \ +-uuid fb44aa6f-8127-4df7-afc3-2ba54b7b7790 \ +-no-user-config \ +-nodefaults \ +-chardev socket,id=charmonitor,fd=25,server=on,wait=off \ +-mon chardev=charmonitor,id=monitor,mode=control \ +-rtc base=localtime,driftfix=slew \ +-global kvm-pit.lost_tick_policy=delay \ +-no-shutdown \ +-global ICH9-LPC.disable_s3=1 \ +-global ICH9-LPC.disable_s4=1 \ +-boot strict=on \ +-device '{"driver":"pcie-root-port","port":16,"chassis":1,"id":"pci.1","bus":"pcie.0","multifunction":true,"addr":"0x2"}' \ +-device '{"driver":"pcie-root-port","port":17,"chassis":2,"id":"pci.2","bus":"pcie.0","addr":"0x2.0x1"}' \ +-device '{"driver":"pcie-root-port","port":18,"chassis":3,"id":"pci.3","bus":"pcie.0","addr":"0x2.0x2"}' \ +-device '{"driver":"pcie-root-port","port":19,"chassis":4,"id":"pci.4","bus":"pcie.0","addr":"0x2.0x3"}' \ +-device '{"driver":"pcie-root-port","port":20,"chassis":5,"id":"pci.5","bus":"pcie.0","addr":"0x2.0x4"}' \ +-device '{"driver":"pcie-root-port","port":21,"chassis":6,"id":"pci.6","bus":"pcie.0","addr":"0x2.0x5"}' \ +-device '{"driver":"pcie-root-port","port":22,"chassis":7,"id":"pci.7","bus":"pcie.0","addr":"0x2.0x6"}' \ +-device '{"driver":"pcie-root-port","port":23,"chassis":8,"id":"pci.8","bus":"pcie.0","addr":"0x2.0x7"}' \ +-device '{"driver":"pcie-root-port","port":24,"chassis":9,"id":"pci.9","bus":"pcie.0","multifunction":true,"addr":"0x3"}' \ +-device '{"driver":"pcie-root-port","port":25,"chassis":10,"id":"pci.10","bus":"pcie.0","addr":"0x3.0x1"}' \ +-device '{"driver":"pcie-root-port","port":26,"chassis":11,"id":"pci.11","bus":"pcie.0","addr":"0x3.0x2"}' \ +-device '{"driver":"pcie-root-port","port":27,"chassis":12,"id":"pci.12","bus":"pcie.0","addr":"0x3.0x3"}' \ +-device '{"driver":"pcie-root-port","port":28,"chassis":13,"id":"pci.13","bus":"pcie.0","addr":"0x3.0x4"}' \ +-device '{"driver":"pcie-root-port","port":29,"chassis":14,"id":"pci.14","bus":"pcie.0","addr":"0x3.0x5"}' \ +-device '{"driver":"qemu-xhci","p2":15,"p3":15,"id":"usb","bus":"pci.2","addr":"0x0"}' \ +-device '{"driver":"virtio-serial-pci","id":"virtio-serial0","bus":"pci.4","addr":"0x0"}' \ +-blockdev '{"driver":"file","filename":"/stratistor/clustermounts/machines/WinDesktop-03/WinDesktop-03.qcow2","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' \ +-blockdev '{"node-name":"libvirt-1-format","read-only":false,"driver":"qcow2","file":"libvirt-1-storage","backing":null}' \ +-device '{"driver":"ide-hd","bus":"ide.0","drive":"libvirt-1-format","id":"sata0-0-0","bootindex":1}' \ +-netdev '{"type":"tap","fd":"27","vhost":true,"vhostfd":"34","id":"hostnet0"}' \ +-device '{"driver":"virtio-net-pci","netdev":"hostnet0","id":"net0","mac":"52:54:00:d4:af:c9","bus":"pci.1","addr":"0x0"}' \ +-chardev pty,id=charserial0 \ +-device '{"driver":"isa-serial","chardev":"charserial0","id":"serial0","index":0}' \ +-chardev socket,id=charchannel0,fd=23,server=on,wait=off \ +-device '{"driver":"virtserialport","bus":"virtio-serial0.0","nr":1,"chardev":"charchannel0","id":"channel0","name":"org.qemu.guest_agent.0"}' \ +-chardev socket,id=chrtpm,path=/run/libvirt/qemu/swtpm/2-WinDesktop-03-swtpm.sock \ +-tpmdev emulator,id=tpm-tpm0,chardev=chrtpm \ +-device '{"driver":"tpm-crb","tpmdev":"tpm-tpm0","id":"tpm0"}' \ +-device '{"driver":"usb-tablet","id":"input0","bus":"usb.0","port":"1"}' \ +-audiodev '{"id":"audio1","driver":"none"}' \ +-vnc 0.0.0.0:0,audiodev=audio1 \ +-device '{"driver":"virtio-vga","id":"video0","max_outputs":1,"bus":"pcie.0","addr":"0x1"}' \ +-global ICH9-LPC.noreboot=off \ +-watchdog-action reset \ +-device '{"driver":"virtio-balloon-pci","id":"balloon0","bus":"pci.3","addr":"0x0"}' \ +-sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ +-msg timestamp=on +2025-01-25 20:54:18.414+0000: Domain id=2 is tainted: high-privileges +char device redirected to /dev/pts/0 (label charserial0) +qemu-kvm: ../qapi/qobject-output-visitor.c:95: void qobject_output_add_obj(QObjectOutputVisitor *, const char *, QObject *): Assertion `name' failed. +2025-01-25 20:54:19.395+0000: shutting down, reason=crashed +2025-01-25 20:54:25.221+0000: Starting external device: TPM Emulator +/usr/bin/swtpm socket --ctrl type=unixio,path=/run/libvirt/qemu/swtpm/3-WinDesktop-03-swtpm.sock,mode=0600 --tpmstate dir=/var/lib/libvirt/swtpm/fb44aa6f-8127-4df7-afc3-2ba54b7b7790/tpm2,mode=0600 --log file=/var/log/swtpm/libvirt/qemu/WinDesktop-03-swtpm.log --terminate --tpm2 +2025-01-25 20:54:25.242+0000: starting up libvirt version: 10.10.0, package: 3.el9 (builder@centos.org, 2024-12-20-13:49:58, ), qemu version: 9.1.0qemu-kvm-9.1.0-9.el9, kernel: 6.12.9, hostname: amd-strat-3 +LC_ALL=C \ +PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin \ +HOME=/var/lib/libvirt/qemu/domain-3-WinDesktop-03 \ +XDG_DATA_HOME=/var/lib/libvirt/qemu/domain-3-WinDesktop-03/.local/share \ +XDG_CACHE_HOME=/var/lib/libvirt/qemu/domain-3-WinDesktop-03/.cache \ +XDG_CONFIG_HOME=/var/lib/libvirt/qemu/domain-3-WinDesktop-03/.config \ +/usr/libexec/qemu-kvm \ +-name guest=WinDesktop-03,debug-threads=on \ +-S \ +-object '{"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-3-WinDesktop-03/master-key.aes"}' \ +-blockdev '{"driver":"file","filename":"/usr/share/edk2/ovmf/OVMF_CODE.secboot.fd","node-name":"libvirt-pflash0-storage","auto-read-only":true,"discard":"unmap"}' \ +-blockdev '{"node-name":"libvirt-pflash0-format","read-only":true,"driver":"raw","file":"libvirt-pflash0-storage"}' \ +-blockdev '{"driver":"file","filename":"/var/lib/libvirt/qemu/nvram/WinDesktop-03_VARS.fd","node-name":"libvirt-pflash1-storage","read-only":false}' \ +-machine pc-q35-rhel9.6.0,usb=off,smm=on,dump-guest-core=off,memory-backend=pc.ram,pflash0=libvirt-pflash0-format,pflash1=libvirt-pflash1-storage,hpet=off,acpi=on \ +-accel kvm \ +-cpu host,migratable=on,hv-time=on,hv-relaxed=on,hv-vapic=on,hv-spinlocks=0x1fff,hv-vpindex=on,hv-runtime=on,hv-synic=on,hv-stimer=on,hv-frequencies=on,hv-tlbflush=on,hv-ipi=on,hv-avic=on \ +-global driver=cfi.pflash01,property=secure,value=on \ +-m size=8388608k \ +-object '{"qom-type":"memory-backend-ram","id":"pc.ram","size":8589934592}' \ +-overcommit mem-lock=off \ +-smp 8,sockets=1,dies=1,clusters=1,cores=8,threads=1 \ +-uuid fb44aa6f-8127-4df7-afc3-2ba54b7b7790 \ +-no-user-config \ +-nodefaults \ +-chardev socket,id=charmonitor,fd=25,server=on,wait=off \ +-mon chardev=charmonitor,id=monitor,mode=control \ +-rtc base=localtime,driftfix=slew \ +-global kvm-pit.lost_tick_policy=delay \ +-no-shutdown \ +-global ICH9-LPC.disable_s3=1 \ +-global ICH9-LPC.disable_s4=1 \ +-boot strict=on \ +-device '{"driver":"pcie-root-port","port":16,"chassis":1,"id":"pci.1","bus":"pcie.0","multifunction":true,"addr":"0x2"}' \ +-device '{"driver":"pcie-root-port","port":17,"chassis":2,"id":"pci.2","bus":"pcie.0","addr":"0x2.0x1"}' \ +-device '{"driver":"pcie-root-port","port":18,"chassis":3,"id":"pci.3","bus":"pcie.0","addr":"0x2.0x2"}' \ +-device '{"driver":"pcie-root-port","port":19,"chassis":4,"id":"pci.4","bus":"pcie.0","addr":"0x2.0x3"}' \ +-device '{"driver":"pcie-root-port","port":20,"chassis":5,"id":"pci.5","bus":"pcie.0","addr":"0x2.0x4"}' \ +-device '{"driver":"pcie-root-port","port":21,"chassis":6,"id":"pci.6","bus":"pcie.0","addr":"0x2.0x5"}' \ +-device '{"driver":"pcie-root-port","port":22,"chassis":7,"id":"pci.7","bus":"pcie.0","addr":"0x2.0x6"}' \ +-device '{"driver":"pcie-root-port","port":23,"chassis":8,"id":"pci.8","bus":"pcie.0","addr":"0x2.0x7"}' \ +-device '{"driver":"pcie-root-port","port":24,"chassis":9,"id":"pci.9","bus":"pcie.0","multifunction":true,"addr":"0x3"}' \ +-device '{"driver":"pcie-root-port","port":25,"chassis":10,"id":"pci.10","bus":"pcie.0","addr":"0x3.0x1"}' \ +-device '{"driver":"pcie-root-port","port":26,"chassis":11,"id":"pci.11","bus":"pcie.0","addr":"0x3.0x2"}' \ +-device '{"driver":"pcie-root-port","port":27,"chassis":12,"id":"pci.12","bus":"pcie.0","addr":"0x3.0x3"}' \ +-device '{"driver":"pcie-root-port","port":28,"chassis":13,"id":"pci.13","bus":"pcie.0","addr":"0x3.0x4"}' \ +-device '{"driver":"pcie-root-port","port":29,"chassis":14,"id":"pci.14","bus":"pcie.0","addr":"0x3.0x5"}' \ +-device '{"driver":"qemu-xhci","p2":15,"p3":15,"id":"usb","bus":"pci.2","addr":"0x0"}' \ +-device '{"driver":"virtio-serial-pci","id":"virtio-serial0","bus":"pci.4","addr":"0x0"}' \ +-blockdev '{"driver":"file","filename":"/stratistor/clustermounts/machines/WinDesktop-03/WinDesktop-03.qcow2","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' \ +-blockdev '{"node-name":"libvirt-1-format","read-only":false,"driver":"qcow2","file":"libvirt-1-storage","backing":null}' \ +-device '{"driver":"ide-hd","bus":"ide.0","drive":"libvirt-1-format","id":"sata0-0-0","bootindex":1}' \ +-netdev '{"type":"tap","fd":"27","vhost":true,"vhostfd":"34","id":"hostnet0"}' \ +-device '{"driver":"virtio-net-pci","netdev":"hostnet0","id":"net0","mac":"52:54:00:d4:af:c9","bus":"pci.1","addr":"0x0"}' \ +-chardev pty,id=charserial0 \ +-device '{"driver":"isa-serial","chardev":"charserial0","id":"serial0","index":0}' \ +-chardev socket,id=charchannel0,fd=23,server=on,wait=off \ +-device '{"driver":"virtserialport","bus":"virtio-serial0.0","nr":1,"chardev":"charchannel0","id":"channel0","name":"org.qemu.guest_agent.0"}' \ +-chardev socket,id=chrtpm,path=/run/libvirt/qemu/swtpm/3-WinDesktop-03-swtpm.sock \ +-tpmdev emulator,id=tpm-tpm0,chardev=chrtpm \ +-device '{"driver":"tpm-crb","tpmdev":"tpm-tpm0","id":"tpm0"}' \ +-device '{"driver":"usb-tablet","id":"input0","bus":"usb.0","port":"1"}' \ +-audiodev '{"id":"audio1","driver":"none"}' \ +-vnc 0.0.0.0:0,audiodev=audio1 \ +-device '{"driver":"virtio-vga","id":"video0","max_outputs":1,"bus":"pcie.0","addr":"0x1"}' \ +-global ICH9-LPC.noreboot=off \ +-watchdog-action reset \ +-device '{"driver":"virtio-balloon-pci","id":"balloon0","bus":"pci.3","addr":"0x0"}' \ +-sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ +-msg timestamp=on +2025-01-25 20:54:25.242+0000: Domain id=3 is tainted: high-privileges +char device redirected to /dev/pts/0 (label charserial0) +**qemu-kvm: ../qapi/qobject-output-visitor.c:95: void qobject_output_add_obj(QObjectOutputVisitor *, const char *, QObject *): Assertion `name' failed. +2025-01-25 20:54:29.967+0000: shutting down, reason=crashed** +Steps to reproduce: +1. Could not produce crash with qemu version 9.1.0-7, upgraded to 9.1.0-9. +2. Started VM using cockpit web interface +3. Crashes within 5 seconds of starting +4. Opening a ticket with cockpit-machines tracker as well as this only happens in cockpit-machines. I am able to open console using virt-manager without crashing, it's only with the cockpit-machines web interface on the VM summary page for the specific VM that appears to cause this. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2795 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2795 new file mode 100644 index 000000000..f99167c9e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2795 @@ -0,0 +1,160 @@ +qemu-system-aarch64 crash when issuing set_link net on in monitor +Description of problem: +Boot the guest. On the host, connect to the qemu monitor and issue the following commmands: +``` +set_link net0 off +ethtool enp0s1 on the guest now shows the link going down +set_link net0 on +``` + +qemu crashes as follows (virtio net): +``` +Thread 1 "qemu-system-aar" received signal SIGSEGV, Segmentation fault. +object_get_class (obj=obj@entry=0x0) at ../qemu/qom/object.c:1049 +1049 return obj->class; +(gdb) bt +#0 object_get_class (obj=obj@entry=0x0) at ../qemu/qom/object.c:1049 +#1 0x000055555602dd0f in QIO_CHANNEL_GET_CLASS (obj=0x0) + at /home/tsailer/src/daedalean/exp-bertcard-emu/qemu/include/io/channel.h:29 +#2 qio_channel_writev_full + (errp=0x0, flags=0, nfds=0, fds=0x0, niov=2, iov=0x7fffffff5190, ioc=0x0) + at ../qemu/io/channel.c:87 +#3 qio_channel_writev + (ioc=0x0, iov=iov@entry=0x7fffffff5190, niov=2, errp=errp@entry=0x0) + at ../qemu/io/channel.c:305 +#4 0x0000555555c42a66 in net_stream_receive + (nc=0x5555578477d0, buf=<optimized out>, size=90) + at ../qemu/net/stream.c:98 +#5 0x0000555555c3d327 in nc_sendv_compat + (flags=<optimized out>, iovcnt=1, iov=0x7fffffff52f0, nc=0x5555578477d0) + at ../qemu/net/net.c:784 +#6 qemu_deliver_packet_iov + (sender=<optimized out>, flags=<optimized out>, iov=0x7fffffff52f0, iovcnt=1, opaque=0x5555578477d0) at ../qemu/net/net.c:830 +#7 0x0000555555c4106c in qemu_net_queue_deliver_iov + (iovcnt=1, iov=0x7fffffff52f0, flags=0, sender=0x5555583049d8, queue=0x55555783c5e0) at ../qemu/net/queue.c:179 +#8 qemu_net_queue_send_iov + (queue=0x55555783c5e0, sender=0x5555583049d8, flags=flags@entry=0, iov=iov@entry=0x7fffffff52f0, iovcnt=iovcnt@entry=1, sent_cb=sent_cb@entry=0x555555f28fa0 <virtio_net_tx_complete>) at ../qemu/net/queue.c:235 +#9 0x0000555555c3ed63 in qemu_sendv_packet_async + (sent_cb=0x555555f28fa0 <virtio_net_tx_complete>, iovcnt=1, iov=0x7fffffff52f0, sender=<optimized out>) at ../qemu/net/net.c:875 +#10 0x0000555555f28c1d in virtio_net_flush_tx (q=q@entry=0x5555582fcb00) + at ../qemu/hw/net/virtio-net.c:2795 +#11 0x0000555555f28f18 in virtio_net_tx_bh (opaque=0x5555582fcb00) + at ../qemu/hw/net/virtio-net.c:2948 +#12 0x00005555561c2f47 in aio_bh_call (bh=bh@entry=0x5555582d0b30) + at ../qemu/util/async.c:172 +#13 0x00005555561c311e in aio_bh_poll (ctx=ctx@entry=0x5555574c3c10) + at ../qemu/util/async.c:219 +#14 0x00005555561ab382 in aio_dispatch (ctx=0x5555574c3c10) + at ../qemu/util/aio-posix.c:424 +#15 0x00005555561c2d82 in aio_ctx_dispatch + (source=<optimized out>, callback=<optimized out>, user_data=<optimized out>) at ../qemu/util/async.c:361 +#16 0x00007ffff7ad5d3b in g_main_context_dispatch () + at /lib/x86_64-linux-gnu/libglib-2.0.so.0 +#17 0x00005555561c45d8 in glib_pollfds_poll () at ../qemu/util/main-loop.c:287 +#18 os_host_main_loop_wait (timeout=0) at ../qemu/util/main-loop.c:310 +#19 main_loop_wait (nonblocking=nonblocking@entry=0) + at ../qemu/util/main-loop.c:589 +#20 0x0000555555bf2569 in qemu_main_loop () at ../qemu/system/runstate.c:835 +#21 0x00005555561047fa in qemu_default_main () at ../qemu/system/main.c:37 +#22 0x00007ffff7229d90 in __libc_start_call_main + (main=main@entry=0x5555558e5080 <main>, argc=argc@entry=44, argv=argv@entry=0x7fffffffd6c8) + at ../sysdeps/nptl/libc_start_call_main.h:58 +#23 0x00007ffff7229e40 in __libc_start_main_impl + (main=0x5555558e5080 <main>, argc=44, argv=0x7fffffffd6c8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffd6b8) + at ../csu/libc-start.c:392 +#24 0x00005555558e6095 in _start () + +Crash with e1000e: +[ 16.846673] e1000e 0000:00:02.0 enp0s2: NIC Link is Down +[ 18.495388] e1000e 0000:00:02.0 enp0s2: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx + +Thread 5 "qemu-system-aar" received signal SIGSEGV, Segmentation fault. +[Switching to Thread 0x7fffafe00640 (LWP 641377)] +object_get_class (obj=obj@entry=0x0) at ../qemu/qom/object.c:1049 +1049 return obj->class; +(gdb) bt +#0 object_get_class (obj=obj@entry=0x0) at ../qemu/qom/object.c:1049 +#1 0x000055555602dd0f in QIO_CHANNEL_GET_CLASS (obj=0x0) + at /home/tsailer/src/daedalean/exp-bertcard-emu/qemu/include/io/channel.h:29 +#2 qio_channel_writev_full + (errp=0x0, flags=0, nfds=0, fds=0x0, niov=2, iov=0x7fffafdfe9b0, ioc=0x0) + at ../qemu/io/channel.c:87 +#3 qio_channel_writev + (ioc=0x0, iov=iov@entry=0x7fffafdfe9b0, niov=2, errp=errp@entry=0x0) + at ../qemu/io/channel.c:305 +#4 0x0000555555c42a66 in net_stream_receive + (nc=0x5555578589b0, buf=<optimized out>, size=90) + at ../qemu/net/stream.c:98 +#5 0x0000555555c3d327 in nc_sendv_compat + (flags=<optimized out>, iovcnt=3, iov=0x55555850b280, nc=0x5555578589b0) + at ../qemu/net/net.c:784 +#6 qemu_deliver_packet_iov + (sender=<optimized out>, flags=<optimized out>, iov=0x55555850b280, iovcnt=3, opaque=0x5555578589b0) at ../qemu/net/net.c:830 +#7 0x0000555555c4106c in qemu_net_queue_deliver_iov + (iovcnt=3, iov=0x55555850b280, flags=0, sender=0x5555584facf8, queue=0x55555783c6d0) at ../qemu/net/queue.c:179 +#8 qemu_net_queue_send_iov + (queue=0x55555783c6d0, sender=0x5555584facf8, flags=0, iov=0x55555850b280, iovcnt=3, sent_cb=0x0) at ../qemu/net/queue.c:235 +#9 0x0000555555a62737 in net_tx_pkt_send_custom + (pkt=0x5555584fb200, offload=<optimized out>, callback=0x555555a61150 <net_tx_pkt_sendv>, context=0x5555584facf8) at ../qemu/hw/net/net_tx_pkt.c:847 +#10 0x0000555555a62819 in net_tx_pkt_send + (pkt=<optimized out>, nc=<optimized out>) + at ../qemu/hw/net/net_tx_pkt.c:816 +#11 0x0000555555a6dd2a in e1000e_tx_pkt_send + (queue_index=<optimized out>, tx=0x555558480cc8, core=0x555558460a60) + at ../qemu/hw/net/e1000e_core.c:654 +#12 e1000e_process_tx_desc + (queue_index=<optimized out>, dp=0x7fffafdfeb20, tx=0x555558480cc8, core=0x555558460a60) at ../qemu/hw/net/e1000e_core.c:731 +#13 e1000e_start_xmit (core=0x555558460a60, txr=txr@entry=0x7fffafdfeb90) + at ../qemu/hw/net/e1000e_core.c:921 +#14 0x0000555555a6dfcc in e1000e_set_tdt + (core=<optimized out>, index=<optimized out>, val=<optimized out>) + at ../qemu/hw/net/e1000e_core.c:2432 +#15 0x0000555555f72044 in memory_region_write_accessor + (mr=0x555558460610, addr=14360, value=<optimized out>, size=4, shift=<optimized out>, mask=<optimized out>, attrs=...) at ../qemu/system/memory.c:497 +#16 0x0000555555f7320e in access_with_adjusted_size + (addr=addr@entry=14360, value=value@entry=0x7fffafdfece8, size=size@entry=4, + access_size_min=<optimized out>, access_size_max=<optimized out>, access_fn=0x555555f71fc0 <memory_region_write_accessor>, mr=<optimized out>, attrs=...) at ../qemu/system/memory.c:573 +#17 0x0000555555f743ad in memory_region_dispatch_write + (mr=mr@entry=0x555558460610, addr=addr@entry=14360, data=<optimized out>, + data@entry=19, op=op@entry=MO_32, attrs=...) + at ../qemu/system/memory.c:1560 +#18 0x0000555555fc6cc9 in int_st_mmio_leN + (cpu=cpu@entry=0x55555789a140, full=full@entry=0x7fffa47eab90, val_le=val_le@entry=19, addr=addr@entry=18446743801007585304, size=size@entry=4, mmu_idx=mmu_idx@entry=2, ra=140736286290890, mr=0x555558460610, mr_offset=14360) + at ../qemu/accel/tcg/cputlb.c:2489 +#19 0x0000555555fc6ec8 in do_st_mmio_leN + (cpu=0x55555789a140, full=0x7fffa47eab90, val_le=19, addr=18446743801007585304, size=4, mmu_idx=2, ra=140736286290890) at ../qemu/accel/tcg/cputlb.c:2524 +#20 0x0000555555fcb55a in do_st_4 + (ra=<optimized out>, memop=<optimized out>, mmu_idx=<optimized out>, val=19, p=<optimized out>, cpu=<optimized out>) at ../qemu/accel/tcg/cputlb.c:2694 +#21 do_st4_mmu + (cpu=0x55555789a140, addr=140736144075184, val=19, oi=2, ra=140736286290890) at ../qemu/accel/tcg/cputlb.c:2770 +#22 0x00007fffb859f416 in code_gen_buffer () +#23 0x0000555555fbb6a6 in cpu_tb_exec + (cpu=cpu@entry=0x55555789a140, itb=itb@entry=0x7fffb859f2c0 <code_gen_buffer+140112531>, tb_exit=tb_exit@entry=0x7fffafdff444) + at ../qemu/accel/tcg/cpu-exec.c:458 +#24 0x0000555555fbbc2f in cpu_loop_exec_tb + (tb_exit=0x7fffafdff444, last_tb=<synthetic pointer>, pc=<optimized out>, tb=0x7fffb859f2c0 <code_gen_buffer+140112531>, cpu=0x55555789a140) + at ../qemu/accel/tcg/cpu-exec.c:908 +#25 cpu_exec_loop (cpu=cpu@entry=0x55555789a140, sc=sc@entry=0x7fffafdff4f0) + at ../qemu/accel/tcg/cpu-exec.c:1022 +#26 0x0000555555fbc3d1 in cpu_exec_setjmp + (cpu=cpu@entry=0x55555789a140, sc=sc@entry=0x7fffafdff4f0) + at ../qemu/accel/tcg/cpu-exec.c:1039 +#27 0x0000555555fbcb9d in cpu_exec (cpu=cpu@entry=0x55555789a140) + at ../qemu/accel/tcg/cpu-exec.c:1065 +#28 0x0000555555fd8123 in tcg_cpu_exec (cpu=cpu@entry=0x55555789a140) + at ../qemu/accel/tcg/tcg-accel-ops.c:78 +#29 0x0000555555fd8280 in mttcg_cpu_thread_fn (arg=arg@entry=0x55555789a140) + at ../qemu/accel/tcg/tcg-accel-ops-mttcg.c:95 +#30 0x00005555561ae740 in qemu_thread_start (args=0x555557883000) + at ../qemu/util/qemu-thread-posix.c:541 +#31 0x00007ffff7294ac3 in start_thread (arg=<optimized out>) + at ./nptl/pthread_create.c:442 +#32 0x00007ffff7326850 in clone3 () + at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 +``` +Steps to reproduce: +1. Boot guest +2. monitor: set_link net0 off +3. monitor: set_link net0 on +Additional information: +Same behaviour with d6430c17d7113d3c38480dc34e59d00b0504e2f7 (master as of 2025-01-19). diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2798 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2798 new file mode 100644 index 000000000..9a898d08d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2798 @@ -0,0 +1,38 @@ +Cannot disconnect Split VMDK +Description of problem: +I used to mount VDI with qemu-nbd and it worked, I could mount/unmount many times. Since VDI was 400 GB, I converted to Split2G VMDK. +In addition to file.vmdk, there are file-s001.vmdk, file-s002.vmdk..file-s201.vmdk +With that, I can mount, but disconnect does not work. Tried also with `blockdev`, did not help, not sure if that is needed. +I know that with LV deactivation of volume group is needed before disconnect. Not aware if there is equivalent with Split VMDK. +Cannot say if issue in qemu-nbd or qemu vmdk driver. +Experienced in qemu 6.2.0 and also when upgraded to 9.0.2. May try later with master that seems to build 9.2.50. +Steps to reproduce: +1. sudo modprobe nbd max_part=4 && sudo qemu-nbd -f vmdk -c /dev/nbd1 file.vmdk && sudo mount /dev/nbd1p1 /mnt/vmdk +2. sudo umount -l /mnt/vmdk && sleep 2 && sudo blockdev --flushbufs /dev/nbd1 && sleep 2 && sudo qemu-nbd -dv /dev/nbd1 +3. lsblk # see still nbd1 +Additional information: +``` +[ 424.020397] block nbd1: NBD_DISCONNECT +[ 424.020417] block nbd1: Disconnected due to user request. +[ 424.020420] block nbd1: shutting down sockets +[ 424.024278] I/O error, dev nbd1, sector 842468736 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 +[ 424.024318] I/O error, dev nbd1, sector 842468736 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 +[ 424.024327] Buffer I/O error on dev nbd1, logical block 105308592, async page read +[ 424.028202] I/O error, dev nbd1, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 +[ 424.028229] I/O error, dev nbd1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 +[ 424.028233] Buffer I/O error on dev nbd1, logical block 0, async page read +[ 424.028249] I/O error, dev nbd1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 +[ 424.028252] Buffer I/O error on dev nbd1, logical block 0, async page read +-- +[ 548.931610] block nbd1: NBD_DISCONNECT +[ 548.931620] block nbd1: Send disconnect failed -32 +[ 548.935594] blk_print_req_error: 6 callbacks suppressed +[ 548.935598] I/O error, dev nbd1, sector 842468736 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 +[ 548.935634] I/O error, dev nbd1, sector 842468736 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 +[ 548.935642] buffer_io_error: 2 callbacks suppressed +[ 548.935644] Buffer I/O error on dev nbd1, logical block 105308592, async page read +[ 548.940187] I/O error, dev nbd1, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 +[ 548.940211] I/O error, dev nbd1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 +[ 548.940215] Buffer I/O error on dev nbd1, logical block 0, async page read +[ 548.940230] I/O error, dev nbd1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2799 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2799 new file mode 100644 index 000000000..4f82daa7d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2799 @@ -0,0 +1,41 @@ +compile failure for linux-user when host libc defines "struct sched_attr" in its sched.h +Description of problem: +When I tried to build commit 871af84d the build process stopped in [3306/9698] Compiling C object libqemu...-linux-user.a.p/linux-user_syscall.c.o + +Here is the error log: + +``` +../linux-user/syscall.c:364:8: error: redefinition of 'struct sched_attr' + 364 | struct sched_attr { + | ^~~~~~~~~~ +In file included from /usr/include/bits/sched.h:63, + from /usr/include/sched.h:43, + from /usr/include/pthread.h:22, + from /usr/include/glib-2.0/glib/deprecated/gthread.h:126, + from /usr/include/glib-2.0/glib.h:115, + from /home/fred/qemu-git/src/qemu/include/glib-compat.h:32, + from /home/fred/qemu-git/src/qemu/include/qemu/osdep.h:161, + from ../linux-user/syscall.c:20: +/usr/include/linux/sched/types.h:98:8: note: originally defined here + 98 | struct sched_attr { + | ^~~~~~~~~~ +``` +Steps to reproduce: +1. Grab commit 871af84d +2. Use this configure command line: + +``` +--prefix=/usr \ + --sysconfdir=/etc \ + --localstatedir=/var \ + --libexecdir=/usr/lib/qemu \ + --smbd=/usr/bin/smbd \ + --enable-modules \ + --enable-sdl \ + --disable-werror \ + "${@:2}" +``` + +3. Launch ninja and wait. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2801 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2801 new file mode 100644 index 000000000..859fd4a7c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2801 @@ -0,0 +1 @@ +Implement Raspberry PI Zero 2 W. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2803 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2803 new file mode 100644 index 000000000..f2f0d201c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2803 @@ -0,0 +1,108 @@ +Assert failure in virtio-net device in address_space_lduw_le_cached +Description of problem: +Issue was found by fuzzing. Assert + +``` +qemu/include/exec/memory_ldst_cached.h.inc:30: uint16_t address_space_lduw_le_cached(MemoryRegionCache *, hwaddr, MemTxAttrs, MemTxResult *): Assertion `addr < cache->len && 2 <= cache->len - addr' failed. +``` +can be triggered with some qtest commands. This is pretty similar to [issue_302](https://gitlab.com/qemu-project/qemu/-/issues/302) and [issue_781](https://gitlab.com/qemu-project/qemu/-/issues/781), but kinda different. In [issue_781](https://gitlab.com/qemu-project/qemu/-/issues/781) there is a comment, that issue was `Possibly fixed by commit 10d35e58 ("virtio-pci: fix queue_enable write").`, but unfortunately it is not - we can still trigger this assert with other set of command-line arguments and qtest commands. +Steps to reproduce: +Command: + +``` +cat << EOF | ./qemu-system-x86_64 -display none -machine accel=qtest, -m 512M -M q35 -nodefaults -device virtio-net,netdev=net0,packed=on -netdev user,id=net0 -qtest stdio +outl 0xcf8 0x80000810 +outl 0xcfc 0xc000 +outl 0xcf8 0x80000820 +outl 0xcfc 0xe0004000 +outl 0xcf8 0x80000804 +outw 0xcfc 0x7 +write 0xe0004008 0x1 0x01 +write 0xe000400c 0x1 0x04 +outl 0xc00b 0x01000000 +outl 0xc006 0x38380000 +outl 0xc001 0x00 +outl 0xc00f 0x04000100 +write 0x3839003 0x1 0x01 +EOF +``` + +Results in + +``` +[I 0.000000] OPENED +[R +0.028638] outl 0xcf8 0x80000810 +[S +0.028692] OK +OK +[R +0.028705] outl 0xcfc 0xc000 +[S +0.028729] OK +OK +[R +0.028738] outl 0xcf8 0x80000820 +[S +0.028748] OK +OK +[R +0.028763] outl 0xcfc 0xe0004000 +[S +0.028784] OK +OK +[R +0.028800] outl 0xcf8 0x80000804 +[S +0.029483] OK +OK +[R +0.029509] outw 0xcfc 0x7 +[S +0.029820] OK +OK +[R +0.029833] write 0xe0004008 0x1 0x01 +[S +0.029846] OK +OK +[R +0.029853] write 0xe000400c 0x1 0x04 +[S +0.029882] OK +OK +[R +0.029894] outl 0xc00b 0x01000000 +[S +0.029909] OK +OK +[R +0.029923] outl 0xc006 0x38380000 +[S +0.029938] OK +OK +[R +0.029944] outl 0xc001 0x00 +[S +0.029953] OK +OK +[R +0.029959] outl 0xc00f 0x04000100 +[S +0.030073] OK +OK +[R +0.030091] write 0x3839003 0x1 0x01 +[S +0.030106] OK +OK +qemu-system-x86_64: /home/artemiin/Work/original_qemu/include/exec/memory_ldst_cached.h.inc:30: uint16_t address_space_lduw_le_cached(MemoryRegionCache *, hwaddr, MemTxAttrs, MemTxResult *): Assertion `addr < cache->len && 2 <= cache->len - addr' failed. +``` +Additional information: +There is a stack trace from libFuzzer output: + +``` +#0 0x5555561bcfc1 in __sanitizer_print_stack_trace (qemu/build/qemu-fuzz-x86_64+0xc68fc1) (BuildId: 97b846e788f9dda2a285e5ea004d922c4886a315) +<some_asert_calls> +#6 0x7ffff48d4471 in abort stdlib/abort.c:79:7 +#7 0x7ffff48d4394 in __assert_fail_base assert/assert.c:92:3 +#8 0x7ffff48e2eb1 in __assert_fail assert/assert.c:101:3 +#9 0x555557043c41 in address_space_lduw_le_cached qemu/include/exec/memory_ldst_cached.h.inc:30:5 +#10 0x555557043c41 in lduw_le_phys_cached qemu/include/exec/memory_ldst_phys.h.inc:67:12 +#11 0x555557043c41 in virtio_lduw_phys_cached qemu/include/hw/virtio/virtio-access.h:166:12 +#12 0x555557030a78 in vring_avail_ring qemu/build/../hw/virtio/virtio.c:389:12 +#13 0x555557030a78 in virtqueue_get_head qemu/build/../hw/virtio/virtio.c:1043:13 +#14 0x555557030a78 in virtqueue_split_pop qemu/build/../hw/virtio/virtio.c:1540:10 +#15 0x555557030a78 in virtqueue_pop qemu/build/../hw/virtio/virtio.c:1790:16 +#16 0x555556f9aaf9 in virtio_net_flush_tx qemu/build/../hw/net/virtio-net.c:2746:16 +#17 0x555556f9a4dc in virtio_net_tx_bh qemu/build/../hw/net/virtio-net.c:2953:11 +#18 0x5555577152e2 in aio_bh_call qemu/build/../util/async.c:171:5 +#19 0x555557715830 in aio_bh_poll qemu/build/../util/async.c:218:13 +#20 0x5555576ce2d7 in aio_dispatch qemu/build/../util/aio-posix.c:423:5 +#21 0x555557717918 in aio_ctx_dispatch qemu/build/../util/async.c:360:5 +#22 0x7ffff69837a8 in g_main_context_dispatch (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x547a8) (BuildId: 9f90bd7bbfcf84a1f1c5a6102f70e6264837b9d4) +#23 0x5555577187cd in glib_pollfds_poll qemu/build/../util/main-loop.c:287:9 +#24 0x5555577187cd in os_host_main_loop_wait qemu/build/../util/main-loop.c:310:5 +#25 0x5555577187cd in main_loop_wait qemu/build/../util/main-loop.c:589:11 +#26 0x5555571ce309 in flush_events qemu/build/../tests/qtest/fuzz/fuzz.c:50:9 +#27 0x5555571d662b in generic_fuzz qemu/build/../tests/qtest/fuzz/generic_fuzz.c:669:13 +#28 0x5555571ce7de in LLVMFuzzerTestOneInput qemu/build/../tests/qtest/fuzz/fuzz.c:158:5 +<fuzzer_init_calls> +#35 0x5555560e2510 in _start (qemu/build/qemu-fuzz-x86_64+0xb8e510) (BuildId: 97b846e788f9dda2a285e5ea004d922c4886a315 +``` + +FYI @mstredhat diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2804 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2804 new file mode 100644 index 000000000..e684164ba --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2804 @@ -0,0 +1 @@ +Unclear meson error when trying to build plugins on macOS diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2805 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2805 new file mode 100644 index 000000000..d8de99ac0 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2805 @@ -0,0 +1,22 @@ +vhost-device-snd does not report correctly the device conf size +Description of problem: +The vhost-user-snd frontend is incorrectly reporting the size of the device configuration space, which should be based on the features exposed by the device. For example, the `controls` field in the `virtio_snd_config` structure is optional and should only be included in the configuration size if the `VIRTIO_SND_F_CTLS` feature has been negotiated. + +This issue became apparent after commit `ab0c7fb2`, where `virtio_snd_config` was updated to include the `controls` field. The vhost-user-snd frontend, relying on this structure, started expecting `sizeof(virtio_snd_config)` when communicating with the backend, regardless of whether the `VIRTIO_SND_F_CTLS` feature was negotiated. As a result, any backend reporting a smaller configuration size—for example, one that does not support controls—cannot communicate with the frontend. We observed this problem in the vhost-device-sound rust-vmm device, which we partially fixed [here](https://github.com/rust-vmm/vhost-device/commit/8e7b7109316e1027548bc91cfcbb4b096b032c24). + +This behavior is incorrect because the configuration size should depend on the negotiated features. + +I am currently working on patch to fix this. +Steps to reproduce: +1. Run vhost-device-sound +```bash + cargo run --bin vhost-device-sound -- --socket=/tmp/vhost-sound.socket --backend=pipewire +``` +2. Run QEMU with the parameters above +3. In the guest run: +```bash +root@syzkaller:~# aplay /usr/share/sounds/alsa/Front_Left.wav +aplay: main:830: audio open error: No such file or directory +``` +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2806 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2806 new file mode 100644 index 000000000..40251c2bc --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2806 @@ -0,0 +1,9 @@ +Build from source failed on Arch Linux with target-list=arm-softmmu,arm-linux-user +Description of problem: +When I tried to build the latest QEMU version, the build process top at 'linking test-qos' +Steps to reproduce: +1. Clone the latest git version of QEMU +2. Configure --target-list=arm-softmmu,arm-linux-user +3. Make +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2809 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2809 new file mode 100644 index 000000000..03eb7c16d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2809 @@ -0,0 +1,11 @@ +Data races in TestBlockJob fields in test-block-iothread +Description of problem: +A data race in the access of `TestBlockJob` fields in `tests/unit/test-block-iothread.c` was identified using TSAN. +Steps to reproduce: +```sh +QEMU_BUILD_DIR=<path to the QEMU build directory> +QEMU_DIR=<path to the QEMU repository directory> +configure --enable-tsan --cc=clang --cxx=clang++ --enable-trace-backends=ust --enable-fdt=system --disable-slirp +make tests/unit/test-block-iothread +MALLOC_PERTURB_=67 G_TEST_SRCDIR=$QEMU_BUILD_DIR/tests/unit G_TEST_BUILDDIR=$QEMU_BUILD_DIR/tests/unit $QEMU_BUILD_DIR/tests/unit/test-block-iothread --tap -k +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2810 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2810 new file mode 100644 index 000000000..c3b5bad42 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2810 @@ -0,0 +1 @@ +Boot zboot images on riscv64 and loogarch64 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2811 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2811 new file mode 100644 index 000000000..55bd6a607 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2811 @@ -0,0 +1,94 @@ +The release artifact for 9.2.1 can not be authenticated with the accompanying OpenPGP signature +Description of problem: +Hi! :wave: + +I package this project for Arch Linux. +This ticket is to inform you that the release artifact for 9.2.1 can not be validated using the accompanying OpenPGP signature. +The signature has been created by the OpenPGP key with the fingerprint `CEACC9E15534EBABB82D3FA03353C9CEF108B584` (held by @mdroth). +However, I am not able to validate the downloaded archive with the provided signature. + +Please make sure that the archive has not been tampered with and ideally do a full re-release and re-sign cycle. +Steps to reproduce: +Download sources and create checksum: + +```bash +curl -O https://download.qemu.org/qemu-9.2.1.tar.xz +curl -O https://download.qemu.org/qemu-9.2.1.tar.xz.sig +b2sum qemu-9.2.1.tar.xz +062b2ef336dbc488bfd9e6c6a21cd95464ab76a98ce8f66bb314101d25a5dc72815ae4eb28028507c85ddade8a28e00cf8897302645ad6ddd2c093bde1cfba9a qemu-9.2.1.tar.xz +``` + +Get latest version of certificate that can be used to verify the signature: + +```bash +gpg --recv-keys CEACC9E15534EBABB82D3FA03353C9CEF108B584 +gpg: key 3353C9CEF108B584: "Michael Roth <michael.roth@amd.com>" not changed +gpg: Total number processed: 1 +gpg: unchanged: 1 +``` + +Export certificate to file: + +```bash +gpg --export CEACC9E15534EBABB82D3FA03353C9CEF108B584 > mdroth.pgp +``` + +Show info about the certificate: + +``` +gpg --list-sigs CEACC9E15534EBABB82D3FA03353C9CEF108B584 +pub rsa2048 2013-10-18 [SC] [expires: 2026-05-11] + CEACC9E15534EBABB82D3FA03353C9CEF108B584 + Keygrip = D85EA26924D8B15B55C659659E2864C375F1547D +uid [ unknown] Michael Roth <michael.roth@amd.com> +sig 3 3353C9CEF108B584 2020-10-27 [self-signature] +sig 3 3353C9CEF108B584 2024-05-11 [self-signature] +uid [ unknown] Michael Roth <flukshun@gmail.com> +sig 3 3353C9CEF108B584 2013-10-18 [self-signature] +uid [ unknown] Michael Roth <mdroth@utexas.edu> +sig 3 3353C9CEF108B584 2013-10-18 [self-signature] +sub rsa2048 2013-10-18 [E] + Keygrip = 9561B09210E2442DEE64237DBA17A9E9D7A58B04 +sig 3353C9CEF108B584 2013-10-18 [self-signature] +``` + +Try verifying the tarball using gpg: + +```bash +gpg --verify qemu-9.2.1.tar.xz.sig +gpg: assuming signed data in 'qemu-9.2.1.tar.xz' +gpg: Signature made 2025-02-12T03:22:55 CET +gpg: using RSA key CEACC9E15534EBABB82D3FA03353C9CEF108B584 +gpg: BAD signature from "Michael Roth <michael.roth@amd.com>" [unknown] +``` + +Try verifying the tarball using the SOP implementation rsop: + +```bash +rsop verify qemu-9.2.1.tar.xz.sig mdroth.pgp < qemu-9.2.1.tar.xz + No acceptable signatures found +``` + +Try verifying the tarball using sq: + +```bash +sq cert import mdroth.pgp + - ┌ CEACC9E15534EBABB82D3FA03353C9CEF108B584 + └ Michael Roth <michael.roth@amd.com> (UNAUTHENTICATED) + - imported + + +Imported 0 new certificates, updated 0 certificates, 1 certificate unchanged, 0 errors. + +sq verify --signature-file qemu-9.2.1.tar.xz.sig qemu-9.2.1.tar.xz +Error verifying signature made by CEACC9E15534EBABB82D3FA03353C9CEF108B584: + + Error: Message has been manipulated +0 authenticated signatures, 1 bad signature. + + Error: Verification failed: could not authenticate any signatures +``` +Additional information: +On Arch Linux we use the provided release tarball and verify it using the detached signature. +For validation we rely on the OpenPGP certificate with the fingerprint `CEACC9E15534EBABB82D3FA03353C9CEF108B584`. +The fingerprint is locked in our [build script](https://gitlab.archlinux.org/archlinux/packaging/packages/qemu/-/blob/7cddf5aa82542d6ba511a22aeaa8eca6d6e7d949/PKGBUILD#L158). diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2814 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2814 new file mode 100644 index 000000000..e32069520 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2814 @@ -0,0 +1 @@ +Convert gdb_core_xml_file to function for https://linaro.atlassian.net/browse/QEMU-487 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2818 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2818 new file mode 100644 index 000000000..0543a513a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2818 @@ -0,0 +1,7 @@ +Passing `-M microvm` and `-smbios type=11...` results in smbios args being silently dropped +Description of problem: +(reporting as requested by `danpb` on IRC) + +Using the `-machine microvm` flag with the `smbios type=11...` argument results in the smbios options being silently discarded, because the microvm target doesn't seem to support the smbios feature. + +danpb on IRC suggested that passing those two incompatible flags should result in an error. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/282 b/gitlab/issues_text/target_missing/host_missing/accel_missing/282 new file mode 100644 index 000000000..ed8c3dd4f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/282 @@ -0,0 +1 @@ +[Feature request] Provide a way to do TLS first in QEMU/NBD connections (not after NBD negotiation) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2822 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2822 new file mode 100644 index 000000000..0c7a5e1a5 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2822 @@ -0,0 +1,11 @@ +Data race with state field of ThreadPoolElement +Description of problem: +A data race in the access of `ThreadPoolElement` state field in `util/thread-pool.c` was identified using TSAN. +Steps to reproduce: +```sh +QEMU_BUILD_DIR=<path to the QEMU build directory> +QEMU_DIR=<path to the QEMU repository directory> +configure --enable-tsan --cc=clang --cxx=clang++ --enable-trace-backends=ust --enable-fdt=system --disable-slirp +make tests/unit/test-thread-pool +MALLOC_PERTURB_=111 G_TEST_SRCDIR=$QEMU_BUILD_DIR/tests/unit G_TEST_BUILDDIR=$QEMU_BUILD_DIR/tests/unit $QEMU_BUILD_DIR/tests/unit/test-thread-pool --tap -k +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2824 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2824 new file mode 100644 index 000000000..97ed11e2a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2824 @@ -0,0 +1 @@ +compile from source on macOS error: "found no usable tomli, please install it" diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2825 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2825 new file mode 100644 index 000000000..5d7787601 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2825 @@ -0,0 +1,37 @@ +execveat with file descriptor and empty filename returns ENOENT when cross architectures +Description of problem: +On my x86_64 debian host (with binfmt_misc configured), when calling execveat with a fd , and empty pathname "", and flag AT_EMPTY_PATH. Then only x86_64 and x86 can be called normally, while programs of other architectures (arm64, arm, riscv64, etc.) will return ENOENT errors. + +I first encountered this problem when trying to run lxc-attach with qemu-aarch64. Its reference is [lxc/stable-6.0/src/include/fexecve.c#L30](https://github.com/lxc/lxc/blob/stable-6.0/src/include/fexecve.c#L30), which is the implementation of the fexecve function. So I wrote a simple test and compiled it with `x86_64/aarch64-linux-gnu-gcc -static test.c -o test`. execveat works fine when running natively or using qemu-x86_64/qemu-i386. When running versions for other architectures, using AT_EMPTY_PATH will result in ENOENT (No such file or directory); use /proc/self/fd/%d as the pathname and execve, it will work fine (like the rest part of the fexecve function). If binfmt_misc is turned off and run forign architectures ver, both calls will result in ENOEXEC (Exec format error). +Steps to reproduce: +1. Install qemu-user and binfmt_misc. Install gcc-aarch64-linux-gnu/gcc-riscv64-linux-gnu etc. +2. Compile test.c with host gcc, then compile forign architectures ver with gcc-aarch64-linux-gnu/gcc-riscv64-linux-gnu etc. like `gcc -static test.c -o test` and `aarch64-linux-gnu-gcc -static test.c -o test-aarch64` +3. Run different versions of test +4. To disable/enable binfmt, you can `echo 0 > /proc/sys/fs/binfmt_misc/qemu-aarch64` or `echo 1 > /proc/sys/fs/binfmt_misc/qemu-aarch64` +5. Sample outputs + +``` +rrex@debian:~/Downloads$ ./test +****Running to prepare execve +fd=3 +File size: 772296 bytes + +execveat with AT_EMPTY_PATH: +**Running in execve + +execveat with fd path: /proc/self/fd/3 +**Running in execve + +rrex@debian:~/Downloads$ qemu-aarch64 ./test-aarch64 +****Running to prepare execve +fd=3 +File size: 706104 bytes + +execveat with AT_EMPTY_PATH: +!!execveat a fd failed with errno: No such file or directory + +execveat with fd path: /proc/self/fd/3 +**Running in execve +``` +Additional information: +# diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2827 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2827 new file mode 100644 index 000000000..cb6a7ead4 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2827 @@ -0,0 +1 @@ +Document how to use QEMU user mode networking with passt diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2829 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2829 new file mode 100644 index 000000000..393ee5a5e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2829 @@ -0,0 +1,21 @@ +SMB sharing on FIPS enabled hosts with Samba broken +Description of problem: +Similar to #2593 , newer security features on GNU+Linux host OSes are continuing +to break communication with guests running older OSes. + +QEMU executes the `smbd` process in [slirp.c](net/slirp.c) to facilitate the SMB +sharing between guest and host. + +The host `smbd` process links in GnuTLS for authentication ciphers and algorithm +primitives. When `smbd` processes SMB requests from these older OS's SMB implementations, +it errors out with error lines: + +`Failed to setup SPNEGO negTokenInit request` + +`Failed to start SPNEGO handler for negprot OID list!` +Steps to reproduce: +1. Access a GNU+Linux machine with GnuTLS library in FIPS mode which `smbd` links against +2. Run `qemu-system-*` with an older guest OS with a `smb` share to host +3. See errors in `/tmp/qemu.smb*/log.smbd` +Additional information: +# diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2830 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2830 new file mode 100644 index 000000000..70c403bcc --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2830 @@ -0,0 +1 @@ +gdbstub: breakpoint/watchpoint increments warp timer on single-core icount mode, breaking determinism diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2831 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2831 new file mode 100644 index 000000000..c37dadd3b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2831 @@ -0,0 +1,20 @@ +unable to build on Sequoia 15.3 +Description of problem: + +Steps to reproduce: +1. git clone https://gitlab.com/qemu-project/qemu.git +2. ../configure --target-list=riscv32-softmmu --enable-debug +3. make + +Error: +ld: multiple errors: archive member '/' not a mach-o file in '../qemu/build/subprojects/dtc/libfdt/libfdt.a'; archive member '/' not a mach-o file in '../qemu/build/libqemuutil.a' +Additional information: +I tried the more detailed "build for macos" instructions +./configure --cc=clang-7 --cxx=clang++-7 --host-cc=clang-7 \ +--extra-cflags=-mavx2 \ +--extra-cxxflags="-I/usr/local/opt/llvm/include" \ +--extra-ldflags="-L/usr/local/opt/llvm/lib -L/usr/local/opt/libffi/lib -L/usr/local/opt/llvm/lib -Wl,-rpath,/usr/local/opt/llvm/lib" \ +--target-list="<list of machines here>" + +but this didn't work for any version of clang I tried, giving me the error in all cases: +ERROR: C compiler "clang-xxx" either does not exist or does not work. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2835 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2835 new file mode 100644 index 000000000..f7fc4200c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2835 @@ -0,0 +1,122 @@ +qtest-x86_64/migration-test times out (hangs?) +Description of problem: +The `qemu:qtest+qtest-x86_64 / qtest-x86_64/migration-test` always times out, after updating QEMU from 8.2.2 to 9.1.3 on GNU Guix. Here's an excerpt from testlog.txt, attached in full below: +``` +test: qemu:qtest+qtest-x86_64 / qtest-x86_64/migration-test +start time: 15:24:17 +duration: 480.01s +result: killed by signal 15 SIGTERM +command: QTEST_QEMU_BINARY=./qemu-system-x86_64 MESON_TEST_ITERATION=1 MALLOC_PERTURB_=66 ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 PYTHON=/tmp/guix-build-qemu-9.1.3.drv-0/qemu-9.1.3/b/qemu/pyvenv/bin/python3 QTEST_QEMU_STORAGE_DAEMON_BINARY=./storage-daemon/qemu-storage-daemon QTEST_QEMU_IMG=./qemu-img MSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 G_TEST_DBUS_DAEMON=/tmp/guix-build-qemu-9.1.3.drv-0/qemu-9.1.3/tests/dbus-vmstate-daemon.sh UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 /tmp/guix-build-qemu-9.1.3.drv-0/qemu-9.1.3/b/qemu/tests/qtest/migration-test --tap -k +----------------------------------- stdout ----------------------------------- +TAP version 13 +# random seed: R02S840f7fe2af5c1c1e5b9ead2a7f451731 +# Skipping test: userfaultfd not available +1..56 +# Start of x86_64 tests +# Start of migration tests +# Running /x86_64/migration/bad_dest +# Using machine type: pc-q35-9.1 +# starting QEMU: exec ./qemu-system-x86_64 -qtest unix:/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.sock -qtest-log /dev/null -chardev socket,path=/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.qmp,id=char0 -mon chardev=char0,mode=control -display none -audio none -accel kvm -accel tcg -machine pc-q35-9.1, -name source,debug-threads=on -m 150M -serial file:/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/src_serial -drive if=none,id=d0,file=/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/bootsect,format=raw -device ide-hd,drive=d0,secs=1,cyls=1,heads=1 2>/dev/null -accel qtest +# starting QEMU: exec ./qemu-system-x86_64 -qtest unix:/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.sock -qtest-log /dev/null -chardev socket,path=/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.qmp,id=char0 -mon chardev=char0,mode=control -display none -audio none -accel kvm -accel tcg -machine pc-q35-9.1, -name target,debug-threads=on -m 150M -serial file:/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/dest_serial -incoming tcp:127.0.0.1:0 -drive if=none,id=d0,file=/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/bootsect,format=raw -device ide-hd,drive=d0,secs=1,cyls=1,heads=1 2>/dev/null -accel qtest +ok 1 /x86_64/migration/bad_dest +# slow test /x86_64/migration/bad_dest executed in 0.60 secs +# Running /x86_64/migration/analyze-script +# Using machine type: pc-q35-9.1 +# starting QEMU: exec ./qemu-system-x86_64 -qtest unix:/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.sock -qtest-log /dev/null -chardev socket,path=/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.qmp,id=char0 -mon chardev=char0,mode=control -display none -audio none -accel kvm -accel tcg -machine pc-q35-9.1, -name source,debug-threads=on -m 150M -serial file:/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/src_serial -drive if=none,id=d0,file=/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/bootsect,format=raw -device ide-hd,drive=d0,secs=1,cyls=1,heads=1 -uuid 11111111-1111-1111-1111-111111111111 -accel qtest +# starting QEMU: exec ./qemu-system-x86_64 -qtest unix:/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.sock -qtest-log /dev/null -chardev socket,path=/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.qmp,id=char0 -mon chardev=char0,mode=control -display none -audio none -accel kvm -accel tcg -machine pc-q35-9.1, -name target,debug-threads=on -m 150M -serial file:/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/dest_serial -incoming tcp:127.0.0.1:0 -drive if=none,id=d0,file=/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/bootsect,format=raw -device ide-hd,drive=d0,secs=1,cyls=1,heads=1 -accel qtest +ok 2 /x86_64/migration/analyze-script +# slow test /x86_64/migration/analyze-script executed in 0.88 secs +# Running /x86_64/migration/vmstate-checker-script +ok 3 /x86_64/migration/vmstate-checker-script # SKIP Test needs two different QEMU versions +# Running /x86_64/migration/validate_uuid +# Using machine type: pc-q35-9.1 +# starting QEMU: exec ./qemu-system-x86_64 -qtest unix:/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.sock -qtest-log /dev/null -chardev socket,path=/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.qmp,id=char0 -mon chardev=char0,mode=control -display none -audio none -accel kvm -accel tcg -machine pc-q35-9.1, -name source,debug-threads=on -m 150M -serial file:/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/src_serial -drive if=none,id=d0,file=/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/bootsect,format=raw -device ide-hd,drive=d0,secs=1,cyls=1,heads=1 -uuid 11111111-1111-1111-1111-111111111111 -accel qtest +# starting QEMU: exec ./qemu-system-x86_64 -qtest unix:/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.sock -qtest-log /dev/null -chardev socket,path=/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.qmp,id=char0 -mon chardev=char0,mode=control -display none -audio none -accel kvm -accel tcg -machine pc-q35-9.1, -name target,debug-threads=on -m 150M -serial file:/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/dest_serial -incoming unix:/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/migsocket -drive if=none,id=d0,file=/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/bootsect,format=raw -device ide-hd,drive=d0,secs=1,cyls=1,heads=1 -uuid 11111111-1111-1111-1111-111111111111 -accel qtest +ok 4 /x86_64/migration/validate_uuid +# slow test /x86_64/migration/validate_uuid executed in 32.74 secs +# Running /x86_64/migration/validate_uuid_error +# Using machine type: pc-q35-9.1 +# starting QEMU: exec ./qemu-system-x86_64 -qtest unix:/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.sock -qtest-log /dev/null -chardev socket,path=/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.qmp,id=char0 -mon chardev=char0,mode=control -display none -audio none -accel kvm -accel tcg -machine pc-q35-9.1, -name source,debug-threads=on -m 150M -serial file:/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/src_serial -drive if=none,id=d0,file=/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/bootsect,format=raw -device ide-hd,drive=d0,secs=1,cyls=1,heads=1 -uuid 11111111-1111-1111-1111-111111111111 2>/dev/null -accel qtest +# starting QEMU: exec ./qemu-system-x86_64 -qtest unix:/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.sock -qtest-log /dev/null -chardev socket,path=/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.qmp,id=char0 -mon chardev=char0,mode=control -display none -audio none -accel kvm -accel tcg -machine pc-q35-9.1, -name target,debug-threads=on -m 150M -serial file:/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/dest_serial -incoming unix:/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/migsocket -drive if=none,id=d0,file=/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/bootsect,format=raw -device ide-hd,drive=d0,secs=1,cyls=1,heads=1 -uuid 22222222-2222-2222-2222-222222222222 2>/dev/null -accel qtest +ok 5 /x86_64/migration/validate_uuid_error +# slow test /x86_64/migration/validate_uuid_error executed in 32.62 secs +# Running /x86_64/migration/validate_uuid_src_not_set +# Using machine type: pc-q35-9.1 +# starting QEMU: exec ./qemu-system-x86_64 -qtest unix:/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.sock -qtest-log /dev/null -chardev socket,path=/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.qmp,id=char0 -mon chardev=char0,mode=control -display none -audio none -accel kvm -accel tcg -machine pc-q35-9.1, -name source,debug-threads=on -m 150M -serial file:/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/src_serial -drive if=none,id=d0,file=/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/bootsect,format=raw -device ide-hd,drive=d0,secs=1,cyls=1,heads=1 2>/dev/null -accel qtest +# starting QEMU: exec ./qemu-system-x86_64 -qtest unix:/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.sock -qtest-log /dev/null -chardev socket,path=/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.qmp,id=char0 -mon chardev=char0,mode=control -display none -audio none -accel kvm -accel tcg -machine pc-q35-9.1, -name target,debug-threads=on -m 150M -serial file:/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/dest_serial -incoming unix:/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/migsocket -drive if=none,id=d0,file=/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/bootsect,format=raw -device ide-hd,drive=d0,secs=1,cyls=1,heads=1 -uuid 22222222-2222-2222-2222-222222222222 2>/dev/null -accel qtest +ok 6 /x86_64/migration/validate_uuid_src_not_set +# slow test /x86_64/migration/validate_uuid_src_not_set executed in 32.73 secs +# Running /x86_64/migration/validate_uuid_dst_not_set +# Using machine type: pc-q35-9.1 +# starting QEMU: exec ./qemu-system-x86_64 -qtest unix:/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.sock -qtest-log /dev/null -chardev socket,path=/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.qmp,id=char0 -mon chardev=char0,mode=control -display none -audio none -accel kvm -accel tcg -machine pc-q35-9.1, -name source,debug-threads=on -m 150M -serial file:/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/src_serial -drive if=none,id=d0,file=/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/bootsect,format=raw -device ide-hd,drive=d0,secs=1,cyls=1,heads=1 -uuid 11111111-1111-1111-1111-111111111111 2>/dev/null -accel qtest +# starting QEMU: exec ./qemu-system-x86_64 -qtest unix:/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.sock -qtest-log /dev/null -chardev socket,path=/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.qmp,id=char0 -mon chardev=char0,mode=control -display none -audio none -accel kvm -accel tcg -machine pc-q35-9.1, -name target,debug-threads=on -m 150M -serial file:/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/dest_serial -incoming unix:/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/migsocket -drive if=none,id=d0,file=/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/bootsect,format=raw -device ide-hd,drive=d0,secs=1,cyls=1,heads=1 2>/dev/null -accel qtest +ok 7 /x86_64/migration/validate_uuid_dst_not_set +# slow test /x86_64/migration/validate_uuid_dst_not_set executed in 32.74 secs +# Running /x86_64/migration/dirty_ring +# Using machine type: pc-q35-9.1 +# starting QEMU: exec ./qemu-system-x86_64 -qtest unix:/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.sock -qtest-log /dev/null -chardev socket,path=/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.qmp,id=char0 -mon chardev=char0,mode=control -display none -audio none -accel kvm,dirty-ring-size=4096 -accel tcg -machine pc-q35-9.1, -name source,debug-threads=on -m 150M -serial file:/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/src_serial -drive if=none,id=d0,file=/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/bootsect,format=raw -device ide-hd,drive=d0,secs=1,cyls=1,heads=1 -accel qtest +# starting QEMU: exec ./qemu-system-x86_64 -qtest unix:/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.sock -qtest-log /dev/null -chardev socket,path=/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.qmp,id=char0 -mon chardev=char0,mode=control -display none -audio none -accel kvm,dirty-ring-size=4096 -accel tcg -machine pc-q35-9.1, -name target,debug-threads=on -m 150M -serial file:/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/dest_serial -incoming unix:/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/migsocket -drive if=none,id=d0,file=/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/bootsect,format=raw -device ide-hd,drive=d0,secs=1,cyls=1,heads=1 -accel qtest +ok 8 /x86_64/migration/dirty_ring +# slow test /x86_64/migration/dirty_ring executed in 33.89 secs +# Running /x86_64/migration/vcpu_dirty_limit +# starting QEMU: exec ./qemu-system-x86_64 -qtest unix:/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.sock -qtest-log /dev/null -chardev socket,path=/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.qmp,id=char0 -mon chardev=char0,mode=control -display none -audio none -accel kvm,dirty-ring-size=4096 -name dirtylimit-test,debug-threads=on -m 150M -smp 1 -serial file:/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/vm_serial -drive file=/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/bootsect,format=raw -accel qtest +ok 9 /x86_64/migration/vcpu_dirty_limit +# slow test /x86_64/migration/vcpu_dirty_limit executed in 13.17 secs +# Start of precopy tests +# Running /x86_64/migration/precopy/file +# Using machine type: pc-q35-9.1 +# starting QEMU: exec ./qemu-system-x86_64 -qtest unix:/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.sock -qtest-log /dev/null -chardev socket,path=/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.qmp,id=char0 -mon chardev=char0,mode=control -display none -audio none -accel kvm -accel tcg -machine pc-q35-9.1, -name source,debug-threads=on -m 150M -serial file:/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/src_serial -drive if=none,id=d0,file=/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/bootsect,format=raw -device ide-hd,drive=d0,secs=1,cyls=1,heads=1 -accel qtest +# starting QEMU: exec ./qemu-system-x86_64 -qtest unix:/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.sock -qtest-log /dev/null -chardev socket,path=/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.qmp,id=char0 -mon chardev=char0,mode=control -display none -audio none -accel kvm -accel tcg -machine pc-q35-9.1, -name target,debug-threads=on -m 150M -serial file:/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/dest_serial -incoming defer -drive if=none,id=d0,file=/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/bootsect,format=raw -device ide-hd,drive=d0,secs=1,cyls=1,heads=1 -accel qtest +ok 10 /x86_64/migration/precopy/file +# slow test /x86_64/migration/precopy/file executed in 33.10 secs +# Start of unix tests +# Running /x86_64/migration/precopy/unix/plain +# Using machine type: pc-q35-9.1 +# starting QEMU: exec ./qemu-system-x86_64 -qtest unix:/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.sock -qtest-log /dev/null -chardev socket,path=/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.qmp,id=char0 -mon chardev=char0,mode=control -display none -audio none -accel kvm -accel tcg -machine pc-q35-9.1, -name source,debug-threads=on -m 150M -serial file:/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/src_serial -drive if=none,id=d0,file=/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/bootsect,format=raw -device ide-hd,drive=d0,secs=1,cyls=1,heads=1 -accel qtest +# starting QEMU: exec ./qemu-system-x86_64 -qtest unix:/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.sock -qtest-log /dev/null -chardev socket,path=/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.qmp,id=char0 -mon chardev=char0,mode=control -display none -audio none -accel kvm -accel tcg -machine pc-q35-9.1, -name target,debug-threads=on -m 150M -serial file:/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/dest_serial -incoming unix:/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/migsocket -drive if=none,id=d0,file=/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/bootsect,format=raw -device ide-hd,drive=d0,secs=1,cyls=1,heads=1 -accel qtest +ok 11 /x86_64/migration/precopy/unix/plain +# slow test /x86_64/migration/precopy/unix/plain executed in 33.89 secs +# Running /x86_64/migration/precopy/unix/xbzrle +# Using machine type: pc-q35-9.1 +# starting QEMU: exec ./qemu-system-x86_64 -qtest unix:/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.sock -qtest-log /dev/null -chardev socket,path=/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.qmp,id=char0 -mon chardev=char0,mode=control -display none -audio none -accel kvm -accel tcg -machine pc-q35-9.1, -name source,debug-threads=on -m 150M -serial file:/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/src_serial -drive if=none,id=d0,file=/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/bootsect,format=raw -device ide-hd,drive=d0,secs=1,cyls=1,heads=1 -accel qtest +# starting QEMU: exec ./qemu-system-x86_64 -qtest unix:/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.sock -qtest-log /dev/null -chardev socket,path=/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.qmp,id=char0 -mon chardev=char0,mode=control -display none -audio none -accel kvm -accel tcg -machine pc-q35-9.1, -name target,debug-threads=on -m 150M -serial file:/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/dest_serial -incoming unix:/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/migsocket -drive if=none,id=d0,file=/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/bootsect,format=raw -device ide-hd,drive=d0,secs=1,cyls=1,heads=1 -accel qtest +ok 12 /x86_64/migration/precopy/unix/xbzrle +# slow test /x86_64/migration/precopy/unix/xbzrle executed in 59.80 secs +# Start of suspend tests +# Running /x86_64/migration/precopy/unix/suspend/live +# Using machine type: pc-q35-9.1 +# starting QEMU: exec ./qemu-system-x86_64 -qtest unix:/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.sock -qtest-log /dev/null -chardev socket,path=/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.qmp,id=char0 -mon chardev=char0,mode=control -display none -audio none -accel kvm -accel tcg -machine pc-q35-9.1, -name source,debug-threads=on -m 150M -serial file:/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/src_serial -drive if=none,id=d0,file=/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/bootsect,format=raw -device ide-hd,drive=d0,secs=1,cyls=1,heads=1 -accel qtest +# starting QEMU: exec ./qemu-system-x86_64 -qtest unix:/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.sock -qtest-log /dev/null -chardev socket,path=/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.qmp,id=char0 -mon chardev=char0,mode=control -display none -audio none -accel kvm -accel tcg -machine pc-q35-9.1, -name target,debug-threads=on -m 150M -serial file:/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/dest_serial -incoming unix:/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/migsocket -drive if=none,id=d0,file=/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/bootsect,format=raw -device ide-hd,drive=d0,secs=1,cyls=1,heads=1 -accel qtest +ok 13 /x86_64/migration/precopy/unix/suspend/live +# slow test /x86_64/migration/precopy/unix/suspend/live executed in 65.90 secs +# Running /x86_64/migration/precopy/unix/suspend/notlive +# Using machine type: pc-q35-9.1 +# starting QEMU: exec ./qemu-system-x86_64 -qtest unix:/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.sock -qtest-log /dev/null -chardev socket,path=/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.qmp,id=char0 -mon chardev=char0,mode=control -display none -audio none -accel kvm -accel tcg -machine pc-q35-9.1, -name source,debug-threads=on -m 150M -serial file:/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/src_serial -drive if=none,id=d0,file=/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/bootsect,format=raw -device ide-hd,drive=d0,secs=1,cyls=1,heads=1 -accel qtest +# starting QEMU: exec ./qemu-system-x86_64 -qtest unix:/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.sock -qtest-log /dev/null -chardev socket,path=/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.qmp,id=char0 -mon chardev=char0,mode=control -display none -audio none -accel kvm -accel tcg -machine pc-q35-9.1, -name target,debug-threads=on -m 150M -serial file:/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/dest_serial -incoming unix:/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/migsocket -drive if=none,id=d0,file=/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/bootsect,format=raw -device ide-hd,drive=d0,secs=1,cyls=1,heads=1 -accel qtest +ok 14 /x86_64/migration/precopy/unix/suspend/notlive +# slow test /x86_64/migration/precopy/unix/suspend/notlive executed in 65.09 secs +# End of suspend tests +# Start of tls tests +# Running /x86_64/migration/precopy/unix/tls/psk +# Using machine type: pc-q35-9.1 +# starting QEMU: exec ./qemu-system-x86_64 -qtest unix:/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.sock -qtest-log /dev/null -chardev socket,path=/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.qmp,id=char0 -mon chardev=char0,mode=control -display none -audio none -accel kvm -accel tcg -machine pc-q35-9.1, -name source,debug-threads=on -m 150M -serial file:/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/src_serial -drive if=none,id=d0,file=/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/bootsect,format=raw -device ide-hd,drive=d0,secs=1,cyls=1,heads=1 -accel qtest +# starting QEMU: exec ./qemu-system-x86_64 -qtest unix:/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.sock -qtest-log /dev/null -chardev socket,path=/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.qmp,id=char0 -mon chardev=char0,mode=control -display none -audio none -accel kvm -accel tcg -machine pc-q35-9.1, -name target,debug-threads=on -m 150M -serial file:/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/dest_serial -incoming unix:/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/migsocket -drive if=none,id=d0,file=/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/bootsect,format=raw -device ide-hd,drive=d0,secs=1,cyls=1,heads=1 -accel qtest +ok 15 /x86_64/migration/precopy/unix/tls/psk +# slow test /x86_64/migration/precopy/unix/tls/psk executed in 33.28 secs +# Start of x509 tests +# Running /x86_64/migration/precopy/unix/tls/x509/default-host +# Using machine type: pc-q35-9.1 +# starting QEMU: exec ./qemu-system-x86_64 -qtest unix:/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.sock -qtest-log /dev/null -chardev socket,path=/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.qmp,id=char0 -mon chardev=char0,mode=control -display none -audio none -accel kvm -accel tcg -machine pc-q35-9.1, -name source,debug-threads=on -m 150M -serial file:/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/src_serial -drive if=none,id=d0,file=/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/bootsect,format=raw -device ide-hd,drive=d0,secs=1,cyls=1,heads=1 2>/dev/null -accel qtest +# starting QEMU: exec ./qemu-system-x86_64 -qtest unix:/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.sock -qtest-log /dev/null -chardev socket,path=/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.qmp,id=char0 -mon chardev=char0,mode=control -display none -audio none -accel kvm -accel tcg -machine pc-q35-9.1, -name target,debug-threads=on -m 150M -serial file:/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/dest_serial -incoming unix:/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/migsocket -drive if=none,id=d0,file=/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/bootsect,format=raw -device ide-hd,drive=d0,secs=1,cyls=1,heads=1 2>/dev/null -accel qtest +ok 16 /x86_64/migration/precopy/unix/tls/x509/default-host +# slow test /x86_64/migration/precopy/unix/tls/x509/default-host executed in 0.78 secs +# Running /x86_64/migration/precopy/unix/tls/x509/override-host +# Using machine type: pc-q35-9.1 +# starting QEMU: exec ./qemu-system-x86_64 -qtest unix:/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.sock -qtest-log /dev/null -chardev socket,path=/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.qmp,id=char0 -mon chardev=char0,mode=control -display none -audio none -accel kvm -accel tcg -machine pc-q35-9.1, -name source,debug-threads=on -m 150M -serial file:/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/src_serial -drive if=none,id=d0,file=/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/bootsect,format=raw -device ide-hd,drive=d0,secs=1,cyls=1,heads=1 -accel qtest +# starting QEMU: exec ./qemu-system-x86_64 -qtest unix:/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.sock -qtest-log /dev/null -chardev socket,path=/tmp/guix-build-qemu-9.1.3.drv-0/qtest-25307.qmp,id=char0 -mon chardev=char0,mode=control -display none -audio none -accel kvm -accel tcg -machine pc-q35-9.1, -name target,debug-threads=on -m 150M -serial file:/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/dest_serial -incoming unix:/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/migsocket -drive if=none,id=d0,file=/tmp/guix-build-qemu-9.1.3.drv-0/migration-test-N4XC22/bootsect,format=raw -device ide-hd,drive=d0,secs=1,cyls=1,heads=1 -accel qtest +============================================================================== +``` +Steps to reproduce: +1. Run `make check` +Additional information: +[testlog.txt.gz](/uploads/29c9c4f259b255297a6418e8f7493397/testlog.txt.gz) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2836 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2836 new file mode 100644 index 000000000..51ea21f2a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2836 @@ -0,0 +1,43 @@ +readconfig with [vnc] only causes assertion failure +Description of problem: +Given test.config containing +``` +[vnc] +``` + +``` +$ qemu-system-amd64 -readconfig test.config +qemu-system-amd64: ui/vnc.c:4294: vnc_init_func: Assertion `id' failed. +Aborted +``` + + +``` +(gdb) bt +#0 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) + at ./nptl/pthread_kill.c:44 +#1 0x00007ffff68f3e2f in __pthread_kill_internal (threadid=<optimized out>, signo=6) at ./nptl/pthread_kill.c:78 +#2 0x00007ffff689fd02 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 +#3 0x00007ffff68884f0 in __GI_abort () at ./stdlib/abort.c:79 +#4 0x00007ffff6888418 in __assert_fail_base (fmt=0x7ffff6a0cca0 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", + assertion=assertion@entry=0x55555608eef6 "id", file=file@entry=0x555556068a5e "ui/vnc.c", line=line@entry=4294, + function=function@entry=0x5555561c3fe0 <__PRETTY_FUNCTION__.0> "vnc_init_func") at ./assert/assert.c:96 +#5 0x00007ffff6898612 in __assert_fail (assertion=assertion@entry=0x55555608eef6 "id", + file=file@entry=0x555556068a5e "ui/vnc.c", line=line@entry=4294, + function=function@entry=0x5555561c3fe0 <__PRETTY_FUNCTION__.0> "vnc_init_func") at ./assert/assert.c:105 +#6 0x0000555555a03adb in vnc_init_func (opaque=<optimized out>, opts=<optimized out>, + errp=0x5555570db038 <error_fatal>) at ui/vnc.c:4294 +#7 0x0000555556037b31 in qemu_opts_foreach (list=<optimized out>, func=0x555555a039f0 <vnc_init_func>, + opaque=opaque@entry=0x0, errp=errp@entry=0x5555570db038 <error_fatal>) at util/qemu-option.c:1135 +#8 0x0000555555c41eff in qemu_init_displays () at system/vl.c:2619 +#9 qemu_init (argc=<optimized out>, argv=<optimized out>) at system/vl.c:3762 +#10 0x00005555559e1c0d in main (argc=<optimized out>, argv=<optimized out>) at system/main.c:47 +``` + +https://gitlab.com/qemu-project/qemu/-/blob/master/ui/vnc.c#L4294 + +Passing an invalid value to id results in `qemu-system-amd64: -readconfig test.config: Parameter 'id' expects an identifier +Identifiers consist of letters, digits, '-', '.', '_', starting with a letter.` so perhaps a missing value should cause a similar error? + + +PS: Where's the documentation for `-readconfig`? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2837 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2837 new file mode 100644 index 000000000..f71242d6b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2837 @@ -0,0 +1 @@ +qcow2 corruption MinGW64 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2838 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2838 new file mode 100644 index 000000000..e78e3133a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2838 @@ -0,0 +1,8 @@ +searchindex.js in HTML doc is not reproducible +Description of problem: +Builds should be reproducible, at least when `SOURCE_DATE_EPOCH` set to some value (see: <https://reproducible-builds.org/docs/source-date-epoch/>), but the QEMU HTML doc contains a file which isn't reproducible. +Steps to reproduce: +1. `guix build --no-grafts qemu && guix build --no-grafts --check --keep-failed qemu` +2. `diffoscope /gnu/store/3kym1ykv9r8n0hgbihqllch9ph136zx1-qemu-8.2.2-doc{,-check}` +Additional information: +[diffoscope-log.txt](/uploads/ab19f184082f343635df4fa7ef26b12e/diffoscope-log.txt) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2839 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2839 new file mode 100644 index 000000000..0bd8d286a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2839 @@ -0,0 +1,35 @@ +Physical memory usage spikes after migration for a VM using memory-backend-memfd memory +Description of problem: +When starting a virtual machine using the memory-backend-memfd type memory, configuring the virtual machine memory to 256GB or any other size, the QEMU process initially allocates only a little over 4GB of physical memory. However, after migrating the virtual machine, the physical memory occupied by the QEMU process almost equals 256GB. In an overcommitted memory environment, the increase in physical memory usage by the virtual machine can lead to insufficient host memory, triggering Out-Of-Memory (OOM). +Steps to reproduce: +1. start vm +./qemu-system-x86_64 -accel kvm -cpu SandyBridge -object memory-backend-memfd,id=mem1,size=256G -machine memory-backend=mem1 -smp 4 -drive file=/nvme0n1/luzhipeng/fusionos.qcow2,if=none,id=drive0,cache=none -device virtio-blk,drive=drive0,bootindex=1 -monitor stdio -vnc :0 +2. start vm on another host +./qemu-system-x86_64 -accel kvm -cpu SandyBridge -object memory-backend-memfd,id=mem1,size=256G -machine memory-backend=mem1 -smp 4 -drive file=/nvme0n1/luzhipeng/fusionos.qcow2,if=none,id=drive0,cache=none -device virtio-blk,drive=drive0,bootindex=1 -monitor stdio -vnc :0 -incoming tcp:0.0.0.0:4444 +3. migrate vm +migrate -d tcp:xx.xx.xx.xx:4444 +4. +Check QEMU process memory usage with the top command + +``` +top - 14:01:05 up 35 days, 20:16, 2 users, load average: 0.22, 0.23, 0.18 +Tasks: 1 total, 0 running, 1 sleeping, 0 stopped, 0 zombie +%Cpu(s): 0.2 us, 0.1 sy, 0.0 ni, 99.8 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st +MiB Mem : 514595.3 total, 2642.6 free, 401703.3 used, 506435.3 buff/cache +MiB Swap: 0.0 total, 0.0 free, 0.0 used. 112892.0 avail Mem + + PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND +3865345 root 20 0 257.7g 256.1g 256.0g S 1.3 51.0 3:14.44 qemu-system-x86 +``` +Additional information: +``` +The relevant code: +void ram_handle_zero(void *host, uint64_t size) +{ + if (!buffer_is_zero(host, size)) { + memset(host, 0, size); + } +} +``` + +In the memory migration process, for the migration of zero pages, the destination side calls buffer_is_zero to check whether the corresponding page is entirely zero. If it is not zero, it actively sets it as a full page. For memory of the memfd type, the first access will allocate physical memory, resulting in physical memory allocation for all zero pages of the virtual machine. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/284 b/gitlab/issues_text/target_missing/host_missing/accel_missing/284 new file mode 100644 index 000000000..897278569 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/284 @@ -0,0 +1 @@ +Assertion failed: (buf_len != 0), function soread, file socket.c, line 183. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2840 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2840 new file mode 100644 index 000000000..e8f1d39a4 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2840 @@ -0,0 +1,21 @@ +After converting the Windows 10 system disk from qcow2 to LUKS format with pre-allocated space, the system fails to boot +Description of problem: +When converting a qcow2 file containing an installed Windows 10 system to LUKS format, using the --target-is-zero parameter in the conversion command prevents the LUKS image from shrinking. However, when attempting to boot the virtual machine with the converted LUKS file, VNC login shows a black screen, and the system fails to start. If the conversion is performed without the --target-is-zero parameter, the system boots up normally +Steps to reproduce: +1. create a luks image +qemu-img create -f qcow2 --object secret,data=123,id=sec0 -o preallocation=full,encrypt.format=luks,encrypt.key-secret=sec0 encry_ok.qcow2 50G +2. +qemu-img convert -t none -T none --object secret,id=sec0,data=123 -f qcow2 ./windows10.qcow2 -n -m 1 --target-image-opts driver=qcow2,encrypt.key-secret=sec0,file.filename=encry_ok.qcow2 --target-is-zero + +windows10.qcow2 container windows20 system and it can be booted +3. +./qemu-system-x86_64 -accel kvm -cpu SandyBridge -object memory-backend-memfd,id=mem1,size=4G -machine memory-backend=mem1 -smp 4 -object secret,id=sec0,data=123,format=raw -drive if=none,driver=qcow2,file.filename=/sdc1/luzhipeng/encry_ok.qcow2,encrypt.key-secret=sec0,id=drive0,cache=none -device virtio-blk,drive=drive0,bootindex=1 -monitor stdio -vnc :4 + +4. vnc shows a black screen, and the system fails to start + +5. if use convert command: +qemu-img convert -t none -T none --object secret,id=sec0,data=123 -f qcow2 ./windows10.qcow2 -n -m 1 --target-image-opts driver=qcow2,encrypt.key-secret=sec0,file.filename=encry_ok.qcow2 + +6. the windows10 system can start successful +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2841 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2841 new file mode 100644 index 000000000..f7b29cba0 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2841 @@ -0,0 +1,11 @@ +QEMU is increasing memory swap, the only solution is to reboot after a freeze. +Description of problem: +Swap starts increasing suddenly and gets to around 60GB before laptop freezes and “dies”. +Steps to reproduce: +Seemingly random, didn’t notice any pattern.. it just started happening more often. + + + +age__4_.png) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2843 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2843 new file mode 100644 index 000000000..7515128b1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2843 @@ -0,0 +1,33 @@ +Strange stdin/out <-> console issue (paste problem) . May be char-win-stdio.c bug. +Description of problem: +I was trying to execute QEMU with VM from command line(shell) and work inside a VM within that initial console. All goes well except... pasting from clipboard. Pastings from clipboard are truncated to somewhat less (no more) then a terminal width (in columns). + +I understand that it seems to be far from QEMU but I tried different terminals/shells/guest systems with the same result. The only things remain the same - QEMU. +Steps to reproduce: +In Windows open a console (shell). Run QEMU with guest serial attached to QEMU stdio. Try to paste some text. Pasted text will be truncated to 15-35 characters. Before QEMU run and after QEMU exit text pasted normally. +Additional information: +- Shell probed: **cmd**, **powershell** +- Terminals probed: **Windows Terminal**, **Alacritty**, **Wezterm**, **Windows Terminal Preview** +- Guest probed: **Alpine Linux**, **FreeBSD** +- Setting inside guest probed: various terminal speed/options via **stty** +- QEMU arguments probed: from **-nographics** to manually define **-chardev/-serial** with/without **-mon**. + +Finally I gave up. But want to mention that there are may be bug in source. When I tried to study source to find a hint for my issue I found that (char-win-stdio.c, line 162): +``` +is_console = GetConsoleMode(stdio->hStdIn, &dwMode) != 0; + stdio->dwOldMode = dwMode; + + if (is_console) { +``` + +Documentation of **GetConsoleMode** function says: +``` +Return value: + +If the function succeeds, the return value is nonzero. +If the function fails, the return value is zero. +``` + +If understand correctly **is_console** will always be _true_. It will be _false_ only in case of invalid **stdio->hStdIn**. + +I don't how this is related to my issue just put here all info I have in hope of resolving. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2845 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2845 new file mode 100644 index 000000000..2e7f63600 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2845 @@ -0,0 +1,32 @@ +memory leak in virtio-pci devices +Description of problem: +The Use-After-Free bug mentioned by #2440 **has not been solved**, but the same crash is not reproducable in the later versions. After reviewing the code, I found an initiailized address space `proxy->modern_cfg_mem_as` introduced by [`55fa4be`](vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-sandbox/workbench/workbench.html "Inspect Commit Details") in `virtio_pci@hw/virtio/virtio-pci.c` will not be destroyed if the later realization is failed. +This will cause memory leak of the device object, which has unused reference and will not be destroyed. + +Relative Code in `virtio_pci_realize@virtio-pci.c`: + +```c +/* subclasses can enforce modern, so do this unconditionally */ +memory_region_init(&proxy->modern_bar, OBJECT(proxy), "virtio-pci", + /* PCI BAR regions must be powers of 2 */ + pow2ceil(proxy->notify.offset + proxy->notify.size)); + +address_space_init(&proxy->modern_cfg_mem_as, &proxy->modern_bar, + "virtio-pci-cfg-mem-as"); + +if (proxy->disable_legacy == ON_OFF_AUTO_AUTO) { + proxy->disable_legacy = pcie_port ? ON_OFF_AUTO_ON : ON_OFF_AUTO_OFF; +} +``` +Steps to reproduce: +```bash +cat <<EOF | qemu-system-i386 -M q35 -nodefaults -chardev stdio,id=char0 -mon char0 -device pcie-pci-bridge,id=br1,bus=pcie.0 +device_add virtio-net,failover=on,rx_queue_size=0,bus=br1,id=dev0 +device_add virtio-net,failover=on,bus=br1,id=dev0 +quit +EOF +``` + +**This will cause UAF report in version `9.0.2`, but will not in `9.2.0`,** despite the bug still existing in code. +Additional information: +For ASAN report, please refer to #2440. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2846 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2846 new file mode 100644 index 000000000..c10e0f7fc --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2846 @@ -0,0 +1 @@ +linux-user hangs if fd_trans_lock is held during fork diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2847 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2847 new file mode 100644 index 000000000..a04cb0419 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2847 @@ -0,0 +1 @@ +Provide short option for UEFI firmware diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2849 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2849 new file mode 100644 index 000000000..b74f6dfb7 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2849 @@ -0,0 +1,18 @@ +Qemu 9.2.x & Ubuntu 24.04 Network Issue +Description of problem: +After successfully starting, I cannot access the Internet with the virtual machine. I can connect to the VM via SSH and execute various commands. We want a simple NAT network.. + +We built the Qemu distribution ourselves with the following command: + +./configure --target-list=x86_64-softmmu --disable-install-blobs --enable-strip --enable-user --enable-system --enable-linux-user --disable-xen --enable-modules --enable-module-upgrades --enable-linux-aio --enable-fdt --enable-gnutls --enable-libiscsi --enable-libssh --enable-vnc --enable-kvm --enable-vhost-user +make -j 12 +sudo make install + +Check Libvirt: +$systemctl status libvirtd - active + +after the VM was successfully started, the IP 10.2.15 was set to ens3 altname enp0s3 assign. + +A ping to 8.8.8.8 can not be resolved. +Additional information: +We can rule out an image problem because this image runs without problems on the Windows Mac guest system and an Internet connection is possible. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2850 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2850 new file mode 100644 index 000000000..6e64bfc7c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2850 @@ -0,0 +1,3 @@ +Available in a version for Windows on arm +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2851 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2851 new file mode 100644 index 000000000..1689e3181 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2851 @@ -0,0 +1,51 @@ +Assert failure in ../util/error.c:68: void error_setv() +Description of problem: +If bdrv_snapshot_goto() returns an error, it is not handled immediately, +allowing *errp to be reassigned when qcow_open() fails, which triggers +assert(*errp == NULL) in util/error.c: void error_setv(). +Steps to reproduce: +1. [test.qed](/uploads/17005dfba241f5a355e3592e12e356f6/test.qed) +2. ./qemu-img snapshot -q -a test test.qed +Additional information: +<details> +<pre> +qemu-img-fuzz: ../util/error.c:68: void error_setv(Error **, const char *, int, const char *, ErrorClass, const char *, struct __va_list_tag *, const char *): Assertion `*errp == NULL' failed. +==20841== ERROR: libFuzzer: deadly signal + #0 0x56384b84a46a in __sanitizer_print_stack_trace /usr/src/RPM/BUILD/llvm-11.0.1.src/projects/compiler-rt/lib/asan/asan_stack.cpp:86:3 + #1 0x56384b79bb79 in fuzzer::PrintStackTrace() /usr/src/RPM/BUILD/llvm-11.0.1.src/projects/compiler-rt/lib/fuzzer/FuzzerUtil.cpp:210:38 + #2 0x56384b77d5a6 in fuzzer::Fuzzer::CrashCallback() (.part.0) /usr/src/RPM/BUILD/llvm-11.0.1.src/projects/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:233:18 + #3 0x56384b77d667 in fuzzer::Fuzzer::CrashCallback() /usr/src/RPM/BUILD/llvm-11.0.1.src/projects/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:205:1 + #4 0x56384b77d667 in fuzzer::Fuzzer::StaticCrashSignalCallback() /usr/src/RPM/BUILD/llvm-11.0.1.src/projects/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:204:19 + #5 0x7effd07c09df (/lib64/libpthread.so.0+0x139df) + #6 0x7effcf659450 in raise (/lib64/libc.so.6+0x3d450) + #7 0x7effcf642547 in abort (/lib64/libc.so.6+0x26547) + #8 0x7effcf642430 (/lib64/libc.so.6+0x26430) + #9 0x7effcf651ce1 in __assert_fail (/lib64/libc.so.6+0x35ce1) + #10 0x56384bf211dc in error_setv /home/gerben/qemu-img_fuzz/build/../util/error.c:68:5 + #11 0x56384bf213fc in error_setg_internal /home/gerben/qemu-img_fuzz/build/../util/error.c:105:5 + #12 0x56384bb2b71f in qcow_open /home/gerben/qemu-img_fuzz/build/../block/qcow.c:306:5 + #13 0x56384bb17654 in bdrv_snapshot_goto /home/gerben/qemu-img_fuzz/build/../block/snapshot.c:299:20 + #14 0x56384bdd52c1 in img_snapshot /home/gerben/qemu-img_fuzz/build/../qemu-img-wrapper.c:3476:15 + #15 0x56384bdbcede in qemu_img_main /home/gerben/qemu-img_fuzz/build/../qemu-img-wrapper.c:5624:20 + #16 0x56384bdb6e7d in command_snapshot /home/gerben/qemu-img_fuzz/build/../qemu-img_fuzz.c:309:20 + #17 0x56384bdb6e7d in generator_command /home/gerben/qemu-img_fuzz/build/../qemu-img_fuzz.c:1285:17 + #18 0x56384bdaf718 in LLVMFuzzerTestOneInput /home/gerben/qemu-img_fuzz/build/../qemu-img_fuzz.c:1303:5 + #19 0x56384b77e1c8 in fuzzer::Fuzzer::ExecuteCallback(unsigned char const*, unsigned long) /usr/src/RPM/BUILD/llvm-11.0.1.src/projects/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:559:17 + #20 0x56384b781af0 in fuzzer::Fuzzer::RunOne(unsigned char const*, unsigned long, bool, fuzzer::InputInfo*, bool*) /usr/src/RPM/BUILD/llvm-11.0.1.src/projects/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:471:18 + #21 0x56384b784796 in fuzzer::Fuzzer::ReadAndExecuteSeedCorpora(std::vector<fuzzer::SizedFile, fuzzer::fuzzer_allocator<fuzzer::SizedFile> >&) /usr/src/RPM/BUILD/llvm-11.0.1.src/projects/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:771:13 + #22 0x56384b784c7e in fuzzer::Fuzzer::Loop(std::vector<fuzzer::SizedFile, fuzzer::fuzzer_allocator<fuzzer::SizedFile> >&) /usr/src/RPM/BUILD/llvm-11.0.1.src/projects/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:800:28 + #23 0x56384b76bb57 in fuzzer::FuzzerDriver(int*, char***, int (*)(unsigned char const*, unsigned long)) /usr/src/RPM/BUILD/llvm-11.0.1.src/projects/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:847:10 + #24 0x56384b758fe2 in main /usr/src/RPM/BUILD/llvm-11.0.1.src/projects/compiler-rt/lib/fuzzer/FuzzerMain.cpp:20:30 + #25 0x7effcf643efc in __libc_start_main (/lib64/libc.so.6+0x27efc) + #26 0x56384b759089 in _start /usr/src/RPM/BUILD/glibc-2.32-alt5.p10.3/csu/../sysdeps/x86_64/start.S:120 + +NOTE: libFuzzer has rudimentary signal handlers. + Combine libFuzzer with AddressSanitizer or similar for better crash reports. +SUMMARY: libFuzzer: deadly signal +MS: 0 ; base unit: 0000000000000000000000000000000000000000 +0x2b,0x25,0xff,0xff,0xff,0xff,0x3a,0x9a,0xc9,0xff,0xa, ++%\xff\xff\xff\xff:\x9a\xc9\xff\x0a +artifact_prefix='./'; Test unit written to ./crash-e9c4f1b8a97ffa93544e87a5a819ac524aa82029 +Base64: KyX/////OprJ/wo= +</pre> +</details> diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2852 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2852 new file mode 100644 index 000000000..72efa2867 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2852 @@ -0,0 +1,80 @@ +heap-use-after-free in timer_pending() +Description of problem: +In the QED block driver, the need_check_timer timer is freed in +bdrv_qed_detach_aio_context, but the pointer to the timer is not +set to NULL. This can lead to a use-after-free scenario +in bdrv_qed_drain_begin(). +Steps to reproduce: +1. [test.qed](/uploads/c8820345bfcd562308da99d9f83df3cf/test.qed) +2. ./qemu-img snapshot -q -a test test.qed +Additional information: +<details> +<pre> +./qemu-img snapshot -q -a test test.qed +==21083==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases! +================================================================= +==21083==ERROR: AddressSanitizer: heap-use-after-free on address 0x60400004ca50 at pc 0x56050d1462b6 bp 0x7fff14d0d870 sp 0x7fff14d0d868 +READ of size 8 at 0x60400004ca50 thread T0 + #0 0x56050d1462b5 in timer_pending /home/gerben/qemu-img_fuzz/build/../util/qemu-timer.c:483:16 + #1 0x56050cddf82e in bdrv_qed_drain_begin /home/gerben/qemu-img_fuzz/build/../block/qed.c:378:32 + #2 0x56050cb9bb65 in bdrv_do_drained_begin /home/gerben/qemu-img_fuzz/build/../block/io.c:364:13 + #3 0x56050cb9ca03 in bdrv_drain_all_begin_nopoll /home/gerben/qemu-img_fuzz/build/../block/io.c:506:9 + #4 0x56050cb96318 in bdrv_graph_wrlock /home/gerben/qemu-img_fuzz/build/../block/graph-lock.c:116:5 + #5 0x56050cd0cbc4 in bdrv_snapshot_goto /home/gerben/qemu-img_fuzz/build/../block/snapshot.c:294:9 + #6 0x56050cf95dd2 in img_snapshot /home/gerben/qemu-img_fuzz/build/../qemu-img.c:3500:15 + #7 0x7f4adeddbefc in __libc_start_main (/lib64/libc.so.6+0x27efc) + #8 0x56050c96a9f9 in _start /usr/src/RPM/BUILD/glibc-2.32-alt5.p10.3/csu/../sysdeps/x86_64/start.S:120 + +0x60400004ca50 is located 0 bytes inside of 48-byte region [0x60400004ca50,0x60400004ca80) +freed by thread T0 here: + #0 0x56050ca0daef in free /usr/src/RPM/BUILD/llvm-11.0.1.src/projects/compiler-rt/lib/asan/asan_malloc_linux.cpp:123:3 + #1 0x56050cde6b86 in bdrv_qed_do_close /home/gerben/qemu-img_fuzz/build/../block/qed.c:619:5 + #2 0x56050cddbe85 in bdrv_qed_close /home/gerben/qemu-img_fuzz/build/../block/qed.c:639:5 + #3 0x56050cd0cbb2 in bdrv_snapshot_goto /home/gerben/qemu-img_fuzz/build/../block/snapshot.c:290:13 + #4 0x56050cf95dd2 in img_snapshot /home/gerben/qemu-img_fuzz/build/../qemu-img.c:3500:15 + #5 0x7f4adeddbefc in __libc_start_main (/lib64/libc.so.6+0x27efc) + +previously allocated by thread T0 here: + #0 0x56050ca0dfa7 in calloc /usr/src/RPM/BUILD/llvm-11.0.1.src/projects/compiler-rt/lib/asan/asan_malloc_linux.cpp:154:3 + #1 0x7f4adf359670 in g_malloc0 (/lib64/libglib-2.0.so.0+0x5c670) + #2 0x56050cde4bd0 in bdrv_qed_do_open /home/gerben/qemu-img_fuzz/build/../block/qed.c:543:5 + #3 0x56050cde21a2 in bdrv_qed_open_entry /home/gerben/qemu-img_fuzz/build/../block/qed.c:569:16 + #4 0x56050d137706 in coroutine_trampoline /home/gerben/qemu-img_fuzz/build/../util/coroutine-ucontext.c:175:9 + #5 0x7f4adee066cf (/lib64/libc.so.6+0x526cf) + +SUMMARY: AddressSanitizer: heap-use-after-free /home/gerben/qemu-img_fuzz/build/../util/qemu-timer.c:483:16 in timer_pending +Shadow bytes around the buggy address: + 0x0c08800018f0: fa fa 00 00 00 00 00 fa fa fa 00 00 00 00 00 fa + 0x0c0880001900: fa fa 00 00 00 00 00 fa fa fa 00 00 00 00 00 fa + 0x0c0880001910: fa fa 00 00 00 00 00 fa fa fa 00 00 00 00 00 fa + 0x0c0880001920: fa fa fd fd fd fd fd fa fa fa fd fd fd fd fd fd + 0x0c0880001930: fa fa 00 00 00 00 01 fa fa fa 00 00 00 00 00 fa +=>0x0c0880001940: fa fa 00 00 00 00 00 fa fa fa[fd]fd fd fd fd fd + 0x0c0880001950: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa + 0x0c0880001960: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa + 0x0c0880001970: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa + 0x0c0880001980: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa + 0x0c0880001990: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa +Shadow byte legend (one shadow byte represents 8 application bytes): + Addressable: 00 + Partially addressable: 01 02 03 04 05 06 07 + Heap left redzone: fa + Freed heap region: fd + Stack left redzone: f1 + Stack mid redzone: f2 + Stack right redzone: f3 + Stack after return: f5 + Stack use after scope: f8 + Global redzone: f9 + Global init order: f6 + Poisoned by user: f7 + Container overflow: fc + Array cookie: ac + Intra object redzone: bb + ASan internal: fe + Left alloca redzone: ca + Right alloca redzone: cb + Shadow gap: cc +==21083==ABORTING +</pre> +</details> diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2853 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2853 new file mode 100644 index 000000000..cf0fb1825 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2853 @@ -0,0 +1,54 @@ +double-free in vmdk_add_extent() +Description of problem: +A double-free issue in the VMDK driver occurs when handling snapshots. +The memory allocated for extent structures is freed twice: first in +vmdk_close (block/vmdk.c) and then in vmdk_add_extent (block/vmdk.c). +Steps to reproduce: +1. [test.raw](/uploads/deeb9dc3cab1916adadd211173cd175a/test.raw) +2. ./qemu-img snapshot -q -a test test.raw +Additional information: +<details> +<pre> +./qemu-img snapshot -q -a test test.raw +==18180==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases! +================================================================= +==18180==ERROR: AddressSanitizer: attempting double-free on 0x612000011bc0 in thread T0: + #0 0x5605ba505168 in realloc /usr/src/RPM/BUILD/llvm-11.0.1.src/projects/compiler-rt/lib/asan/asan_malloc_linux.cpp:164:3 + #1 0x7f22be5fd6b7 in g_realloc (/lib64/libglib-2.0.so.0+0x5c6b7) + #2 0x5605ba866a79 in vmdk_add_extent /home/gerben/qemu-img_fuzz/build/../block/vmdk.c:570:18 + #3 0x5605ba86122e in vmdk_open_vmdk4 /home/gerben/qemu-img_fuzz/build/../block/vmdk.c:1059:11 + #4 0x5605ba86122e in vmdk_open_sparse /home/gerben/qemu-img_fuzz/build/../block/vmdk.c:1127:20 + #5 0x5605ba85723a in vmdk_open /home/gerben/qemu-img_fuzz/build/../block/vmdk.c:1371:19 + #6 0x5605ba803ca4 in bdrv_snapshot_goto /home/gerben/qemu-img_fuzz/build/../block/snapshot.c:299:20 + #7 0x5605baa8cdd2 in img_snapshot /home/gerben/qemu-img_fuzz/build/../qemu-img.c:3500:15 + #8 0x7f22bd559efc in __libc_start_main (/lib64/libc.so.6+0x27efc) + #9 0x5605ba4619f9 in _start /usr/src/RPM/BUILD/glibc-2.32-alt5.p10.3/csu/../sysdeps/x86_64/start.S:120 + +0x612000011bc0 is located 0 bytes inside of 272-byte region [0x612000011bc0,0x612000011cd0) +freed by thread T0 here: + #0 0x5605ba504aef in free /usr/src/RPM/BUILD/llvm-11.0.1.src/projects/compiler-rt/lib/asan/asan_malloc_linux.cpp:123:3 + #1 0x5605ba857e6d in vmdk_close /home/gerben/qemu-img_fuzz/build/../block/vmdk.c:2889:5 + #2 0x5605ba803bb2 in bdrv_snapshot_goto /home/gerben/qemu-img_fuzz/build/../block/snapshot.c:290:13 + #3 0x5605baa8cdd2 in img_snapshot /home/gerben/qemu-img_fuzz/build/../qemu-img.c:3500:15 + #4 0x7f22bd559efc in __libc_start_main (/lib64/libc.so.6+0x27efc) + +previously allocated by thread T0 here: + #0 0x5605ba505168 in realloc /usr/src/RPM/BUILD/llvm-11.0.1.src/projects/compiler-rt/lib/asan/asan_malloc_linux.cpp:164:3 + #1 0x7f22be5fd6b7 in g_realloc (/lib64/libglib-2.0.so.0+0x5c6b7) + #2 0x5605ba86122e in vmdk_open_vmdk4 /home/gerben/qemu-img_fuzz/build/../block/vmdk.c:1059:11 + #3 0x5605ba86122e in vmdk_open_sparse /home/gerben/qemu-img_fuzz/build/../block/vmdk.c:1127:20 + #4 0x5605ba85723a in vmdk_open /home/gerben/qemu-img_fuzz/build/../block/vmdk.c:1371:19 + #5 0x5605ba56e3a2 in bdrv_open_driver /home/gerben/qemu-img_fuzz/build/../block.c:1660:15 + #6 0x5605ba57ea50 in bdrv_open_common /home/gerben/qemu-img_fuzz/build/../block.c:1985:11 + #7 0x5605ba57ea50 in bdrv_open_inherit /home/gerben/qemu-img_fuzz/build/../block.c:4153:11 + #8 0x5605ba585cb8 in bdrv_open /home/gerben/qemu-img_fuzz/build/../block.c:4248:12 + #9 0x5605ba637d4c in blk_new_open /home/gerben/qemu-img_fuzz/build/../block/block-backend.c:457:10 + #10 0x5605baa9193b in img_open_file /home/gerben/qemu-img_fuzz/build/../qemu-img.c:405:11 + #11 0x5605baa9143e in img_open /home/gerben/qemu-img_fuzz/build/../qemu-img.c:450:15 + #12 0x5605baa8cc71 in img_snapshot /home/gerben/qemu-img_fuzz/build/../qemu-img.c:3468:11 + #13 0x7f22bd559efc in __libc_start_main (/lib64/libc.so.6+0x27efc) + +SUMMARY: AddressSanitizer: double-free /usr/src/RPM/BUILD/llvm-11.0.1.src/projects/compiler-rt/lib/asan/asan_malloc_linux.cpp:164:3 in realloc +==18180==ABORTING +</pre> +</details> diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2854 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2854 new file mode 100644 index 000000000..70c3d3bf9 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2854 @@ -0,0 +1,24 @@ +https://www.qemu.org/ is missing chance to provide (or at least link) some starting guide +Description of problem: +as a completely new (potential) user https://www.qemu.org/ main page is missing chance to easily link some hello world documentation +Steps to reproduce: +1. open https://www.qemu.org/ +2. try to click "Full-system emulation" with hope that it will link some starting hello world how to do so +Additional information: +On https://www.qemu.org/ you can click "support" + +Then you can click "documentation" + +Then "main documentation section" + +Then "system emulation" + +Then "introduction" + +At this point you have something that sort-of is viable as hello world. + +Maybe link https://www.qemu.org/docs/master/system/introduction.html from main page ("Full-system emulation")? + +Unless there is a better documentation? + +Though maybe someone who will not go through this link maze should not try to use QEMU at all? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2856 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2856 new file mode 100644 index 000000000..d8048b216 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2856 @@ -0,0 +1,90 @@ +segfault when passing x-vga=on on gpu(old) passthrough +Description of problem: +When using x-vga=on on the ati x550 gpu passthrough, qemu-system-x86 segfault occurs.(I think it may happen with other ati cards from same era, ati x300, ati x600, ati x800) +Similar bug from 2017 on nvidia 7300GS: +https://bugs.launchpad.net/qemu/+bug/1678466 +Additional information: +``` +dmesg: +[ 5050.113978] qemu-system-x86[8288]: segfault at b8 ip 000055c4f459ad47 sp 00007fff81f966e0 error 4 in qemu-system-x86_64[57ed47,55c +4f418f000+69f000] likely on CPU 11 (core 20, socket 0) +[ 5050.113987] Code: c0 75 f0 48 8b 6b 60 48 89 b3 80 00 00 00 67 e8 9f 82 00 00 48 8b 7b 40 83 05 b0 11 2e 01 01 48 85 ff 74 06 67 e +8 59 1e 08 00 <48> 8b 85 b8 00 00 00 48 85 c0 74 7d 8b 93 b0 00 00 00 eb 11 0f 1f +[ 5050.272446] vfio-pci 0000:07:00.0: Refused to change power state from D0 to D3hot +``` +``` +lspci -vv: +07:00.0 1002:5b63 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV370 [Radeon X300/X550/X1050 Series] (prog-if 00 [VGA controller]) + Subsystem: PC Partner Limited / Sapphire Technology Device 1500 + Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- + Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- + Interrupt: pin A routed to IRQ 3 + IOMMU group: 18 + Region 0: Memory at 54000000 (32-bit, prefetchable) [disabled] [size=64M] + Region 1: I/O ports at 3000 [disabled] [size=256] + Region 2: Memory at 59c30000 (32-bit, non-prefetchable) [disabled] [size=64K] + Expansion ROM at 59c00000 [disabled] [size=128K] + Capabilities: [50] Power Management version 2 + Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) + Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- + Capabilities: [58] Express (v1) Endpoint, IntMsgNum 0 + DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <128ns, L1 <2us + ExtTag+ AttnBtn- AttnInd- PwrInd- RBE- FLReset- SlotPowerLimit 10W TEE-IO- + DevCtl: CorrErr+ NonFatalErr+ FatalErr+ UnsupReq+ + RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ + MaxPayload 128 bytes, MaxReadReq 128 bytes + DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- + LnkCap: Port #0, Speed 2.5GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <128ns, L1 <1us + ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp- + LnkCtl: ASPM Disabled; RCB 64 bytes, LnkDisable- CommClk+ + ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- + LnkSta: Speed 2.5GT/s, Width x1 (downgraded) + TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- + Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit+ + Address: 0000000000000000 Data: 0000 + Capabilities: [100 v1] Advanced Error Reporting + UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- + ECRC- UnsupReq- ACSViol- UncorrIntErr- BlockedTLP- AtomicOpBlocked- TLPBlockedErr- + PoisonTLPBlocked- DMWrReqBlocked- IDECheck- MisIDETLP- PCRC_CHECK- TLPXlatBlocked- + UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- + ECRC- UnsupReq- ACSViol- UncorrIntErr- BlockedTLP- AtomicOpBlocked- TLPBlockedErr- + PoisonTLPBlocked- DMWrReqBlocked- IDECheck- MisIDETLP- PCRC_CHECK- TLPXlatBlocked- + UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ + ECRC- UnsupReq- ACSViol- UncorrIntErr- BlockedTLP- AtomicOpBlocked- TLPBlockedErr- + PoisonTLPBlocked- DMWrReqBlocked- IDECheck- MisIDETLP- PCRC_CHECK- TLPXlatBlocked- + CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr- CorrIntErr- HeaderOF- + CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr- CorrIntErr- HeaderOF- + AERCap: First Error Pointer: 00, ECRCGenCap- ECRCGenEn- ECRCChkCap- ECRCChkEn- + MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap- + HeaderLog: 04000001 0000030f 07070000 7efb9a03 + +07:00.1 1002:5b73 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] RV370 [Radeon X300/X550/X1050 Series] (Secondary) + Subsystem: PC Partner Limited / Sapphire Technology Device 1501 + Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- + Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- + IOMMU group: 18 + Region 0: Memory at 59c20000 (32-bit, non-prefetchable) [disabled] [size=64K] + Capabilities: [50] Power Management version 2 + Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) + Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- + Capabilities: [58] Express (v1) Endpoint, IntMsgNum 0 + DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <128ns, L1 <2us + ExtTag- AttnBtn- AttnInd- PwrInd- RBE- FLReset- SlotPowerLimit 0W TEE-IO- + DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- + RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- + MaxPayload 128 bytes, MaxReadReq 128 bytes + DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- + LnkCap: Port #0, Speed 2.5GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <128ns, L1 <1us + ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp- + LnkCtl: ASPM Disabled; RCB 64 bytes, LnkDisable- CommClk+ + ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- + LnkSta: Speed 2.5GT/s, Width x1 (downgraded) + TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- +``` + +(In win7 when the "07:00.1 Display controller" uses the gpu driver, dmesg spam errors occur and VM functions very very slow. I don't know where to report this, libvirt?. This I tested only in virt-manager. "07:00.1 Display controller" can be disabled in Win7 device manager and problems disappear. Independent if this, booting with x-vga=off image is corrupted on the monitor connected to passthrough gpu until driver is loaded. Image is white with vertical dark stripes.) +``` +[ 3160.598553] DMAR: [INTR-REMAP] Request device [07:00.1] fault index 0x50 [fault reason 0x26] Blocked an interrupt request due to source-id verification failure +[ 3161.098536] DMAR: DRHD: handling fault status reg 2 +[ 3165.098584] dmar_fault: 23 callbacks suppressed +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2857 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2857 new file mode 100644 index 000000000..efa5f3978 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2857 @@ -0,0 +1,100 @@ +segmentation fault issue in qemu-option.c for both qemu-system-x86_64 and qemu-system-aarch64 +Description of problem: + +Steps to reproduce: +1. Compile with; +``` +| PKG_CONFIG_PATH="$PWD/../../lib/pkgconfig" ../../source/qemu-9.2.1/configure \ | +|------------------------------------------------------------------------------------| +| --extra-cflags="-I$PWD/../../source/angle/include -march=armv8-a+crc+crypto" \ | +| --extra-ldflags="-L$PWD/../angle" \ | +| --disable-cocoa \ | +| --enable-sdl \ | +| --prefix="$PWD/../.." | +``` +2.`./bin/qemu-system-aarch64 -machine virt,accel=hvf -cpu host` +3. Single liner for building: +``` +curl -L https://gist.github.com/startergo/0d9a7425876c2b42f8b797af80fbe3d8/raw/run-arm-3dfx-sdl.sh | bash - +``` +Additional information: +``` + +lldb -- ./bin/qemu-system-aarch64 -machine virt,accel=hvf -cpu host +(lldb) target create "./bin/qemu-system-aarch64" +Current executable set to '/Users/macbookpro/Downloads/qemu-3dfx-arch/bin/qemu-system-aarch64' (arm64). +(lldb) settings set -- target.run-args "-machine" "virt,accel=hvf" "-cpu" "host" +(lldb) run +Process 64856 launched: '/Users/macbookpro/Downloads/qemu-3dfx-arch/bin/qemu-system-aarch64' (arm64) +Process 64856 stopped +* thread #1, queue = 'com.apple.main-thread', stop reason = signal SIGUSR2 + frame #0: 0x0000000199d78cc0 libsystem_kernel.dylib`__sigsuspend + 8 +libsystem_kernel.dylib`__sigsuspend: +-> 0x199d78cc0 <+8>: b.lo 0x199d78ce0 ; <+40> + 0x199d78cc4 <+12>: pacibsp + 0x199d78cc8 <+16>: stp x29, x30, [sp, #-0x10]! + 0x199d78ccc <+20>: mov x29, sp +Target 0: (qemu-system-aarch64) stopped. +(lldb) continue +Process 64856 resuming +Process 64856 stopped +* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x0) + frame #0: 0x0000000000000000 +error: memory read failed for 0x0 +Target 0: (qemu-system-aarch64) stopped. +(lldb) bt +* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x0) + * frame #0: 0x0000000000000000 + frame #1: 0x00000001008539ec qemu-system-aarch64`get_opt_name_value [inlined] qemu_strchrnul(s="nic", c=44) at cutils.h:144:12 [opt] + frame #2: 0x00000001008539e0 qemu-system-aarch64`get_opt_name_value [inlined] get_opt_value(p="nic", value=0x000000016fdff058) at qemu-option.c:71:18 [opt] + frame #3: 0x00000001008539dc qemu-system-aarch64`get_opt_name_value(params=<unavailable>, firstname=<unavailable>, warn_on_flag=<unavailable>, help_wanted=0x0000000000000000, name=<unavailable>, value=0x000000016fdff058) at qemu-option.c:760:17 [opt] + frame #4: 0x0000000100853c84 qemu-system-aarch64`opts_do_parse(opts=0x0000600002e30460, params="nic", firstname=<unavailable>, warn_on_flag=false, help_wanted=0x0000000000000000, errp=0x00000001018fd500) at qemu-option.c:808:13 [opt] + frame #5: 0x0000000100853fbc qemu-system-aarch64`opts_parse(list=<unavailable>, params="nic", permit_abbrev=<unavailable>, warn_on_flag=false, help_wanted=0x0000000000000000, errp=0x00000001018fd500) at qemu-option.c:898:10 [opt] + frame #6: 0x0000000100853ea0 qemu-system-aarch64`qemu_opts_parse(list=<unavailable>, params=<unavailable>, permit_abbrev=<unavailable>, errp=<unavailable>) at qemu-option.c:917:12 [opt] [artificial] + frame #7: 0x00000001002937b4 qemu-system-aarch64`qemu_init [inlined] qemu_create_default_devices at vl.c:1446:9 [opt] + frame #8: 0x0000000100293640 qemu-system-aarch64`qemu_init(argc=<unavailable>, argv=0x000000016fdff500) at vl.c:3692:5 [opt] + frame #9: 0x00000001007b58c0 qemu-system-aarch64`main(argc=<unavailable>, argv=<unavailable>) at main.c:47:5 [opt] + frame #10: 0x0000000199a2c274 dyld`start + 2840 + +lldb -- ./bin/qemu-system-x86_64 -machine q35,accel=hvf -cpu host +(lldb) target create "./bin/qemu-system-x86_64" +Current executable set to '/Users/macbookpro/Downloads/qemu-3dfx-arch/bin/qemu-system-x86_64' (arm64). +(lldb) settings set -- target.run-args "-machine" "q35,accel=hvf" "-cpu" "host" +(lldb) run +Process 65669 launched: '/Users/macbookpro/Downloads/qemu-3dfx-arch/bin/qemu-system-x86_64' (arm64) +Process 65669 stopped +* thread #1, queue = 'com.apple.main-thread', stop reason = signal SIGUSR2 + frame #0: 0x0000000199d78cc0 libsystem_kernel.dylib`__sigsuspend + 8 +libsystem_kernel.dylib`__sigsuspend: +-> 0x199d78cc0 <+8>: b.lo 0x199d78ce0 ; <+40> + 0x199d78cc4 <+12>: pacibsp + 0x199d78cc8 <+16>: stp x29, x30, [sp, #-0x10]! + 0x199d78ccc <+20>: mov x29, sp +Target 0: (qemu-system-x86_64) stopped. +(lldb) continue +Process 65669 resuming +Process 65669 stopped +* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x0) + frame #0: 0x0000000000000000 +error: memory read failed for 0x0 +Target 0: (qemu-system-x86_64) stopped. +(lldb) bt +* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x0) + * frame #0: 0x0000000000000000 + frame #1: 0x000000010053c7f0 qemu-system-x86_64`get_opt_name_value [inlined] qemu_strchrnul(s="nic", c=44) at cutils.h:144:12 [opt] + frame #2: 0x000000010053c7e4 qemu-system-x86_64`get_opt_name_value [inlined] get_opt_value(p="nic", value=0x000000016fdff058) at qemu-option.c:71:18 [opt] + frame #3: 0x000000010053c7e0 qemu-system-x86_64`get_opt_name_value(params=<unavailable>, firstname=<unavailable>, warn_on_flag=<unavailable>, help_wanted=0x0000000000000000, name=<unavailable>, value=0x000000016fdff058) at qemu-option.c:760:17 [opt] + frame #4: 0x000000010053ca88 qemu-system-x86_64`opts_do_parse(opts=0x0000600002476ee0, params="nic", firstname=<unavailable>, warn_on_flag=false, help_wanted=0x0000000000000000, errp=0x00000001014fa230) at qemu-option.c:808:13 [opt] + frame #5: 0x000000010053cdc0 qemu-system-x86_64`opts_parse(list=<unavailable>, params="nic", permit_abbrev=<unavailable>, warn_on_flag=false, help_wanted=0x0000000000000000, errp=0x00000001014fa230) at qemu-option.c:898:10 [opt] + frame #6: 0x000000010053cca4 qemu-system-x86_64`qemu_opts_parse(list=<unavailable>, params=<unavailable>, permit_abbrev=<unavailable>, errp=<unavailable>) at qemu-option.c:917:12 [opt] [artificial] + frame #7: 0x00000001001d6b00 qemu-system-x86_64`qemu_init [inlined] qemu_create_default_devices at vl.c:1446:9 [opt] + frame #8: 0x00000001001d698c qemu-system-x86_64`qemu_init(argc=<unavailable>, argv=0x000000016fdff500) at vl.c:3692:5 [opt] + frame #9: 0x000000010049e7c0 qemu-system-x86_64`main(argc=<unavailable>, argv=<unavailable>) at main.c:47:5 [opt] + frame #10: 0x0000000199a2c274 dyld`start + 2840 + +--> + +``` +The line below ensures that proper tags are added to the issue. +Please do not remove it. +--> diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2858 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2858 new file mode 100644 index 000000000..e0b37e19c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2858 @@ -0,0 +1 @@ +QEMU Command Not Working diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2859 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2859 new file mode 100644 index 000000000..e0b37e19c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2859 @@ -0,0 +1 @@ +QEMU Command Not Working diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2860 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2860 new file mode 100644 index 000000000..3406638e7 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2860 @@ -0,0 +1,33 @@ +ps2 keyboard not work after boot and use libspice to connect it +Description of problem: +When I start almost 10 qemu virtual machines, there will always be one or two that have the ps2 keyboard not work well after booted.But I use mstsc to connect to the desktop, the keyboard works fine. But when reboot or migrate it well recovery. +Steps to reproduce: +1.Asynchronously start 40 qemu virtual machines, each with 4 cores and 4 threads + +2.there will always be one or two that have the ps2 keyboard not work well. + +4.And when i gdb debug it, i found i hang at the func "prepare_mmio_access" + +5.reboot or migrate it well recovery +Additional information: +the gdb debug as fllow: + +gdb attach $pid + +gdb>b kbd_push_key //spice input + +gdb>b kbd_read_data + +gdb>b ps2_keyboard_event + +gdb>c + +After continue, the code run on ps2_keyboard_event,but no work to "kbd_read_data".This Proves that the keyboard input has been added to the queue, but has not been read from the queue. + +gdb> thread 4 //switch to thread "CPU 0/KVM" + +gdb> bt + + + +I guess there is no event to notify the device to read after writing to the queue, or is it deadlocked? I'm not sure diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2862 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2862 new file mode 100644 index 000000000..50332a184 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2862 @@ -0,0 +1,24 @@ +unable to complete install when i try to load into qemu +Description of problem: +when i load up a vm, i get the message Unable to complete install: 'internal error: process exited while connecting to monitor: 2025-03-14T01:54:54.436804Z qemu-system-aarch64: can't apply global host-arm-cpu.hv-relaxed=on: Property 'host-arm-cpu.hv-relaxed' not found' + +Traceback (most recent call last): + File "/usr/share/virt-manager/virtManager/asyncjob.py", line 72, in cb_wrapper + callback(asyncjob, *args, **kwargs) + File "/usr/share/virt-manager/virtManager/createvm.py", line 2008, in _do_async_install + installer.start_install(guest, meter=meter) + File "/usr/share/virt-manager/virtinst/install/installer.py", line 695, in start_install + domain = self._create_guest( + ^^^^^^^^^^^^^^^^^^^ + File "/usr/share/virt-manager/virtinst/install/installer.py", line 637, in _create_guest + domain = self.conn.createXML(initial_xml or final_xml, 0) + ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + File "/usr/lib/python3/dist-packages/libvirt.py", line 4481, in createXML + raise libvirtError('virDomainCreateXML() failed') +libvirt.libvirtError: internal error: process exited while connecting to monitor: 2025-03-14T01:54:54.436804Z qemu-system-aarch64: can't apply global host-arm-cpu.hv-relaxed=on: Property 'host-arm-cpu.hv-relaxed' not found. If it's important, vmm recognizes my windows 10 iso as a windows 11. +Steps to reproduce: +1.i just tried to use the vm. +2. +3. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2863 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2863 new file mode 100644 index 000000000..083dbacb5 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2863 @@ -0,0 +1 @@ +Invalid read reason: rejected diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2866 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2866 new file mode 100644 index 000000000..688ca17c1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2866 @@ -0,0 +1,185 @@ +In Win98 vm gpu driver issues with old ati gpu if it has BAR0: 64 bit, BAR4: I/O; no issue if it has BAR0: 32 bit, BAR1: I/O +Description of problem: +In win98se vm no errors in device manager,ati control panel complains that the driver is not loaded and desktop can only be used in 16 color 640x480. The problematic old ati gpus work correctly when booting win98 directly(no qemu vm, same host hardware) + +Drivers fail to load in win98 vm for old ati gpu(x600, x700, x800, x850) that has: +``` + Region 0: Memory at 4020000000 (64-bit, prefetchable) [size=256M] + Region 2: Memory at 41b30000 (64-bit, non-prefetchable) [size=64K] + Region 4: I/O ports at 3000 [size=256] + Expansion ROM at 41b00000 [disabled] [size=128K] +``` +Old ati gpu(x300, x550) that have this, load/work correctly in win98 vm: +``` + Region 0: Memory at 40000000 (32-bit, prefetchable) [size=64M] + Region 1: I/O ports at 3000 [size=256] + Region 2: Memory at 45b30000 (32-bit, non-prefetchable) [size=64K] + Expansion ROM at 45b00000 [disabled] [size=128K] +``` +Additional information: +I am using a QEMU build from branch master from a few days ago, with a fix for segfault when using 'x-vga=on' on some old ati gpu(Region 0: Memory at 40000000 (32-bit),Region 1: I/O ports) https://gitlab.com/qemu-project/qemu/-/issues/2856. (Win98 gpu driver issues with old ati gpu if it has "BAR0: 64 bit, BAR4: I/O" was the same with QEMU version 9.12). + +x700: +``` +QEMU 9.2.50v9.2.0-2799-g0462a32b4f monitor> info pci: +Bus 0, device 2, function 0: + VGA controller: PCI device 1002:5e4d + PCI subsystem 148c:2129 + IRQ 10, pin A + BAR0: 64 bit prefetchable memory at 0xe0000000 [0xefffffff]. + BAR2: 64 bit memory at 0x00010000 [0x0001ffff]. + BAR4: I/O at 0xc000 [0xc0ff]. + BAR6: 32 bit memory at (not mapped) + id "" + Bus 0, device 2, function 1: + Display controller: PCI device 1002:5e6d + PCI subsystem 148c:2128 + BAR0: 64 bit memory at 0xfebf0000 [0xfebfffff]. + id "" +``` +``` +lspci -vv: + +08:00.0 0300: 1002:5e4d VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV410 [Radeon X700] (prog-if 00 [VGA controller]) + Subsystem: Tul Corporation / PowerColor Device 2129 + Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- + Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- + Interrupt: pin A routed to IRQ 16 + Region 0: Memory at 4020000000 (64-bit, prefetchable) [size=256M] + Region 2: Memory at 41b30000 (64-bit, non-prefetchable) [size=64K] + Region 4: I/O ports at 3000 [size=256] + Expansion ROM at 41b00000 [disabled] [size=128K] + Capabilities: [50] Power Management version 2 + Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) + Status: D3 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- + Capabilities: [58] Express (v1) Endpoint, MSI 00 + DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <256ns, L1 <4us + ExtTag+ AttnBtn- AttnInd- PwrInd- RBE- FLReset- SlotPowerLimit 25.000W + DevCtl: Report errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+ + RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ + MaxPayload 128 bytes, MaxReadReq 128 bytes + DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- + LnkCap: Port #0, Speed 2.5GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <256ns, L1 <2us + ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp- + LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ + ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- + LnkSta: Speed 2.5GT/s, Width x4, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- + Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit+ + Address: 0000000000000000 Data: 0000 + Capabilities: [100 v1] Advanced Error Reporting + UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- + UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- + UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- + CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr- + CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr- + AERCap: First Error Pointer: 00, ECRCGenCap- ECRCGenEn- ECRCChkCap- ECRCChkEn- + MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap- + HeaderLog: 40000001 00000003 000b0000 ffff0000 + Kernel driver in use: vfio-pci + Kernel modules: radeon, amdgpu + +08:00.1 0380: 1002:5e6d Display controller: Advanced Micro Devices, Inc. [AMD/ATI] RV410 [Radeon X700] (Secondary) + Subsystem: Tul Corporation / PowerColor Device 2128 + Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- + Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- + Region 0: Memory at 41b20000 (64-bit, non-prefetchable) [size=64K] + Capabilities: [50] Power Management version 2 + Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) + Status: D3 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- + Capabilities: [58] Express (v1) Endpoint, MSI 00 + DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <256ns, L1 <4us + ExtTag- AttnBtn- AttnInd- PwrInd- RBE- FLReset- SlotPowerLimit 0.000W + DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- + RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- + MaxPayload 128 bytes, MaxReadReq 128 bytes + DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- + LnkCap: Port #0, Speed 2.5GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <256ns, L1 <2us + ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp- + LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ + ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- + LnkSta: Speed 2.5GT/s, Width x4, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- + Kernel driver in use: vfio-pci + Kernel modules: amdgpu +``` + +x550: +``` +QEMU 9.2.50v9.2.0-2799-g0462a32b4f monitor> info pci: +us 0, device 2, function 0: + VGA controller: PCI device 1002:5b63 + PCI subsystem 174b:1500 + IRQ 10, pin A + BAR0: 32 bit prefetchable memory at 0xef800000 [0xfbffffff]. + BAR1: I/O at 0xc000 [0xc0ff]. + BAR2: 32 bit memory at 0x00010000 [0xfebdffff]. + BAR6: 32 bit memory at (not mapped) + id "" + Bus 0, device 2, function 1: + Display controller: PCI device 1002:5b73 + PCI subsystem 174b:1501 + BAR0: 32 bit memory at 0xfebf0000 [0xfebfffff]. + id "" + + +lspci -vv: +08:00.0 1002:5b63 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV370 [Radeon X300/X550/X1050 Series] (prog-if 00 [VGA controller]) + Subsystem: PC Partner Limited / Sapphire Technology Device 1500 + Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- + Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- + Interrupt: pin A routed to IRQ 16 + Region 0: Memory at 40000000 (32-bit, prefetchable) [size=64M] + Region 1: I/O ports at 3000 [size=256] + Region 2: Memory at 45b30000 (32-bit, non-prefetchable) [size=64K] + Expansion ROM at 45b00000 [disabled] [size=128K] + Capabilities: [50] Power Management version 2 + Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) + Status: D3 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- + Capabilities: [58] Express (v1) Endpoint, MSI 00 + DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <128ns, L1 <2us + ExtTag+ AttnBtn- AttnInd- PwrInd- RBE- FLReset- SlotPowerLimit 25.000W + DevCtl: Report errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+ + RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ + MaxPayload 128 bytes, MaxReadReq 128 bytes + DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- + LnkCap: Port #0, Speed 2.5GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <128ns, L1 <1us + ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp- + LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ + ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- + LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- + Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit+ + Address: 0000000000000000 Data: 0000 + Capabilities: [100 v1] Advanced Error Reporting + UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- + UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- + UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- + CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr- + CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr- + AERCap: First Error Pointer: 00, ECRCGenCap- ECRCGenEn- ECRCChkCap- ECRCChkEn- + MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap- + HeaderLog: 02000001 00000002 000003c8 037bbfae + Kernel driver in use: vfio-pci + Kernel modules: radeon, amdgpu + +08:00.1 1002:5b73 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] RV370 [Radeon X300/X550/X1050 Series] (Secondary) + Subsystem: PC Partner Limited / Sapphire Technology Device 1501 + Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- + Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- + Region 0: Memory at 45b20000 (32-bit, non-prefetchable) [size=64K] + Capabilities: [50] Power Management version 2 + Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) + Status: D3 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- + Capabilities: [58] Express (v1) Endpoint, MSI 00 + DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <128ns, L1 <2us + ExtTag- AttnBtn- AttnInd- PwrInd- RBE- FLReset- SlotPowerLimit 0.000W + DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- + RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- + MaxPayload 128 bytes, MaxReadReq 128 bytes + DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- + LnkCap: Port #0, Speed 2.5GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <128ns, L1 <1us + ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp- + LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ + ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- + LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- + Kernel driver in use: vfio-pci + Kernel modules: amdgpu +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2867 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2867 new file mode 100644 index 000000000..82edfdf4c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2867 @@ -0,0 +1,13 @@ +qemu:block / io-qcow2-161 fails non-deterministically +Description of problem: +The test suite failed non-deterministically with failure: +``` +729/838 qemu:block / io-qcow2-161 ERROR 2.08s exit status 1 +``` +Steps to reproduce: +1. guix time-machine --commit=d706c1b -- build qemu +2. or git clone, build and run `make check -j32 V=1` +Additional information: +[qemu-9.1.3-io-qcow2-041-failure-build-log.txt](/uploads/077f61d9dd1a26bcd351c0995009131c/qemu-9.1.3-io-qcow2-041-failure-build-log.txt) + +[testlog.txt](/uploads/0b0244a337f2175bdba9e258c778481d/testlog.txt) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/287 b/gitlab/issues_text/target_missing/host_missing/accel_missing/287 new file mode 100644 index 000000000..eb9765d26 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/287 @@ -0,0 +1 @@ +block copy job sometimes hangs on the last block for minutes diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2872 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2872 new file mode 100644 index 000000000..2e252cec3 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2872 @@ -0,0 +1 @@ +hw/net: Parameter 'driver' expects a pluggable device type diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2873 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2873 new file mode 100644 index 000000000..b27d259b3 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2873 @@ -0,0 +1,9 @@ +[chardev] In case of stdin redirection, SYS_READC semihost call will block in the chardev backend when EOF is reached. +Description of problem: +The previous command hangs, EOF is not detected. +Steps to reproduce: +1. +2. +3. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2875 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2875 new file mode 100644 index 000000000..1875d6fc1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2875 @@ -0,0 +1,29 @@ +[Virtio-GPU Venus] QEMU Virtio-GPU Venus with Lavapipe ICD shows corrupted graphical output along with error prints +Description of problem: +QEMU Virtio-GPU Venus with Lavapipe ICD shows corrupted graphical output (screenshots attached ahead) along with the following error prints, as guest_errors are enabled in QEMU command line `-d guest_errors`: +``` +VK_DRIVER_FILES=/usr/share/vulkan/icd.d/lvp_icd.x86_64.json ./qemu-system-x86_64 -enable-kvm -M q35 -smp 4 -m 4G -cpu host -net nic,model=virtio -net user,hostfwd=tcp::2222-:22 -d guest_errors -device virtio-vga-gl,hostmem=4G,blob=true,venus=true -vga none -display gtk,gl=on,show-cursor=on -usb -device usb-tablet -object memory-backend-memfd,id=mem1,size=4G -machine memory-backend=mem1 -hda ubuntu-2504.qcow2 +virtio_gpu_virgl_unmap_resource_blob: failed to unmap virgl resource: Invalid argument +virtio_gpu_virgl_process_cmd: ctrl 0x209, error 0x1200 +virtio_gpu_virgl_unmap_resource_blob: failed to unmap virgl resource: Invalid argument +virtio_gpu_virgl_process_cmd: ctrl 0x209, error 0x1200 +virtio_gpu_virgl_unmap_resource_blob: failed to unmap virgl resource: Invalid argument +virtio_gpu_virgl_process_cmd: ctrl 0x209, error 0x1200 +virtio_gpu_virgl_unmap_resource_blob: failed to unmap virgl resource: Invalid argument +virtio_gpu_virgl_process_cmd: ctrl 0x209, error 0x1200 +virtio_gpu_virgl_unmap_resource_blob: failed to unmap virgl resource: Invalid argument +virtio_gpu_virgl_process_cmd: ctrl 0x209, error 0x1200 +virtio_gpu_virgl_unmap_resource_blob: failed to unmap virgl resource: Invalid argument +virtio_gpu_virgl_process_cmd: ctrl 0x209, error 0x1200 +``` +Steps to reproduce: +1. Used steps mentioned here: https://gist.github.com/peppergrayxyz/fdc9042760273d137dddd3e97034385f, to build virglrenderer-1.1.0 with Venus support, and to build QEMU (latest: v10.0.0-rc1) with virglrenderer support. +2. Run QEMU with Lavapipe ICD using the command shared above. +3. When the QEMU guest is up, install required packages such as `sudo apt-get install -y mesa* vulkan* libvulkan* vkmark` and run vkcube / vkmark with VirtIO ICD: +``` +VK_DRIVER_FILES=/usr/share/vulkan/icd.d/virtio_icd.x86_64.json vkcube --wsi wayland +``` +Additional information: +Attaching screenshots for the error observed on guest side: +,  +Collected logs with tracing enabled (`meson setup -Dvenus=true -Dvenus-validate=true -Dvideo=true -Dtracing=stderr build`) in virglrenderer as well: [virgl-tracing-stderr.log](/uploads/202c698b7c265cde7c83b441a6a7abdb/virgl-tracing-stderr.log). Search for error in the log file. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2876 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2876 new file mode 100644 index 000000000..0da636a92 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2876 @@ -0,0 +1,14 @@ +IPv6 support for hostfwd + guestfwd +Description of problem: +When using hostfwd, only IPv4 connections are forwarded. +Steps to reproduce: +1. Start vm with the aforementioned command using a system image that comes with a socket listening on both IPv4 and IPv6. (I used Arch Linux Box which comes with `sshd` enabled by default). +2. Connect to the forwarded socket: + - IPv4 succeeds: + - `ssh -oPasswordAuthentication=yes arch@127.0.0.1 -p 52022` + - `nc -zv 127.0.0.1 52022` + - IPv6 does not: + - `ssh -oPasswordAuthentication=yes arch@::1 -p 52022` + - `nc -zv ::1 52022` +Additional information: +# diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2879 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2879 new file mode 100644 index 000000000..98ff41869 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2879 @@ -0,0 +1 @@ +-smbios type=11,path=xxx results in buffer overrun due to missing null terminator diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2880 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2880 new file mode 100644 index 000000000..463833bed --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2880 @@ -0,0 +1,3 @@ +how to migrate storage live for the vm with vhostuser disk +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2881 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2881 new file mode 100644 index 000000000..6764786b6 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2881 @@ -0,0 +1,10 @@ +segfault on loadvm after migrate_set_capability multifd on +Description of problem: +A segfault occurs when running `loadvm` having set `migrate_set_capability multifd on` from the monitor. +EDIT: also `savevm` segfaults. +Steps to reproduce: +1. Take a snapshot with `savevm test` +2. From the monitor run `migrate_set_capability multifd on` +3. Try to restore the snapshot with `loadvm test` +Additional information: +Sorry for not having triaged this much, I think it is worth reporting anyway. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2883 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2883 new file mode 100644 index 000000000..0d55c87a5 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2883 @@ -0,0 +1 @@ +Advice regarding implementation of smooth scrolling diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2888 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2888 new file mode 100644 index 000000000..dacfe7d61 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2888 @@ -0,0 +1,14 @@ +mouse pointer does not move in USB pass in. +Description of problem: +I have this script to start qemu that passes in my mouse, keyboard and xbox controller. When I use it, it does not move the cursor(for my mouse) but the mouse is working because the hot corners do. Moving my mouse in a up left direction in GNOME will show the menu and apps. Key board works, My controller works, and My mouse works, but the cursor does not move. +Steps to reproduce: +1. use the script above with the right USB IDs for you mouse and keyboard (and controller if you want) +2. When the VM boots it will not move the cursor. The mouse will work but the pointer stays still. +Additional information: +I am using thees patches in qemu but it does not work in vanilla ether: +https://lore.kernel.org/all/20241010182427.1434605-1-seanjc@google.com/ + +and this in the kernel (6.14.0): +https://github.com/torvalds/linux/commit/377b2f359d1f71c75f8cc352b5c81f2210312d83 + +I am ruining qemu 10.0.0-rc1 (but 9.2.2 also does not work), kernel 6.14.0. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2889 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2889 new file mode 100644 index 000000000..bfe1e42ce --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2889 @@ -0,0 +1,22 @@ +mouse does not work in pass in +Description of problem: +I have this script to start qemu that passes in my mouse, keyboard and xbox controler. When I use it, it does not move the cursor(for my mouse) but the mouse is working because the hot corners do work. Moving my mouse in a up left direction in GNOME will show the menu and apps. Key board works, My controller works, and My mouse works, but the cursor does not move. Here is the script: +Steps to reproduce: +1. run the script above with the right variables. +2. Move your mouse in the screen. It will not move the pointer. +Additional information: +I am using thees patches in qemu but it does not work in vanilla ether: +https://lore.kernel.org/all/20241010182427.1434605-1-seanjc@google.com/ + +and this in the kernel (6.14.0): +https://github.com/torvalds/linux/commit/377b2f359d1f71c75f8cc352b5c81f2210312d83 + +I am ruining qemu 10.0.0-rc1 (but 9.2.2 also does not work), kernel 6.14.0. + +I am runing mint on my host and arch on my guest. on my host I have virglrenderer on and on my guest I installed the pacman package lib32-vulkan-virtio and vulkan-virtio. + +If it helps I can remove the pass throws and insted use: + +-usbdevice tablet -usbdevice mouse -usbdevice keyboard +or +-device virtio-mouse -device virtio-keyboard -device virtio-tablet diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2890 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2890 new file mode 100644 index 000000000..d88715d19 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2890 @@ -0,0 +1 @@ +RFE: Individual ON_SHUTDOWN diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2900 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2900 new file mode 100644 index 000000000..aa79102cf --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2900 @@ -0,0 +1,11 @@ +Data races in test-bdrv-drain test +Description of problem: +Data races in the access of `Job` fields in the `test-bdrv-drain` test were identified using TSAN. +Steps to reproduce: +```sh +QEMU_BUILD_DIR=<path to the QEMU build directory> +QEMU_DIR=<path to the QEMU repository directory> +configure --enable-tsan --cc=clang --cxx=clang++ --enable-trace-backends=ust --enable-fdt=system --disable-slirp +make tests/unit/test-bdrv-drain +MALLOC_PERTURB_=186 G_TEST_SRCDIR=$QEMU_BUILD_DIR/tests/unit G_TEST_BUILDDIR=$QEMU_BUILD_DIR/tests/unit $QEMU_BUILD_DIR/tests/unit/test-bdrv-drain --tap -k +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2901 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2901 new file mode 100644 index 000000000..70a4f3b9c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2901 @@ -0,0 +1 @@ +Critical typo in qemu_source_dir/plugins/loader.c diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2902 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2902 new file mode 100644 index 000000000..2c205135b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2902 @@ -0,0 +1,11 @@ +Data Race with slh_first Field in test-aio-multithread +Description of problem: +Potential data races in the `QSLIST_INSERT_HEAD_ATOMIC` macro were identified using TSAN. +Steps to reproduce: +```sh +QEMU_BUILD_DIR=<path to the QEMU build directory> +QEMU_DIR=<path to the QEMU repository directory> +configure --enable-tsan --cc=clang --cxx=clang++ --enable-trace-backends=ust --enable-fdt=system --disable-slirp +make tests/unit/test-bdrv-drain +MALLOC_PERTURB_=102 G_TEST_SRCDIR=$QEMU_BUILD_DIR/tests/unit G_TEST_BUILDDIR=$QEMU_BUILD_DIR/tests/unit $QEMU_BUILD_DIR/tests/unit/test-aio-multithread --tap -k +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2903 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2903 new file mode 100644 index 000000000..07ffbe1e5 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2903 @@ -0,0 +1,11 @@ +Data Race in assertion in aio-posix.c +Description of problem: +Potential data races in the assertion in `test-aio-multithread` were identified using TSAN. +Steps to reproduce: +```sh +QEMU_BUILD_DIR=<path to the QEMU build directory> +QEMU_DIR=<path to the QEMU repository directory> +configure --enable-tsan --cc=clang --cxx=clang++ --enable-trace-backends=ust --enable-fdt=system --disable-slirp +make tests/unit/test-bdrv-drain +MALLOC_PERTURB_=102 G_TEST_SRCDIR=$QEMU_BUILD_DIR/tests/unit G_TEST_BUILDDIR=$QEMU_BUILD_DIR/tests/unit $QEMU_BUILD_DIR/tests/unit/test-aio-multithread --tap -k +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2904 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2904 new file mode 100644 index 000000000..7f4722641 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2904 @@ -0,0 +1,11 @@ +Data Race in data->cb() call and cb assignment in test-aio-multithread +Description of problem: +Potential data races between the `data->cb()` call and the assignment of `cb` in `test-aio-multithread` were identified using TSAN. +Steps to reproduce: +```sh +QEMU_BUILD_DIR=<path to the QEMU build directory> +QEMU_DIR=<path to the QEMU repository directory> +configure --enable-tsan --cc=clang --cxx=clang++ --enable-trace-backends=ust --enable-fdt=system --disable-slirp +make tests/unit/test-bdrv-drain +MALLOC_PERTURB_=102 G_TEST_SRCDIR=$QEMU_BUILD_DIR/tests/unit G_TEST_BUILDDIR=$QEMU_BUILD_DIR/tests/unit $QEMU_BUILD_DIR/tests/unit/test-aio-multithread --tap -k +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2905 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2905 new file mode 100644 index 000000000..281d18e3a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2905 @@ -0,0 +1,24 @@ +Windows Curses Display Infinite Loop +Description of problem: +The out-of-the-box `qemu-system-x86_64 -display curses` on Windows loops forever while displaying "VGA Blank Mode" instead of booting like `qemu-system-x86_64` does. + +This is caused by an infinite loop in the below simplified code in `curses_refresh` in `ui/curses.c`: +``` + int chr; + // ...trimmed + while (1) { + /* while there are any pending key strokes to process */ + chr = console_getch(&maybe_keycode); + + if (chr == -1) + break; + // ...trimmed + } +``` +`console_getch` has return type `wint_t`. However, on Windows, `wint_t` is `unsigned short`. Therefore when `console_getch` returns -1, the -1 value of `unsigned short` will be silently converted into the `int` value 65535. This causes `65535 == -1` to always be false, and the loop will never break. I can send a patch to qemu-devel which retypes `chr` to `wint_t` and replaces occurences of -1 with `WEOF` (an alias for `(wint_t) -1`). +Steps to reproduce: +1. Install `qemu-w64-setup-20250326.exe` Windows qemu from https://qemu.weilnetz.de/w64/2025/ +2. Run `./qemu-system-x86_64 -display curses` +3. "VGA Blank Mode" will appear on the screen forever +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2908 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2908 new file mode 100644 index 000000000..3a945f6c2 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2908 @@ -0,0 +1,10 @@ +Display Output Not Sane After Driver Installation +Description of problem: +Using an S3 Diamond Stealth 3000 card through VFIO, after installing an official driver, either from the Windows disc or an updated download, the displayed output from the graphics card is not sane. +Additional information: +Driver: [https://theretroweb.com/expansioncards/s/diamond-stealth-3d-3000-pci#driver](https://theretroweb.com/expansioncards/s/diamond-stealth-3d-3000-pci#driver) +[https://diamond.retropc.se/driver/stealth/st3d3xx0/files.htm](https://diamond.retropc.se/driver/stealth/st3d3xx0/files.htm) + +Followed the instructions in the Readme. To install Standard VGA driver first then the Diamond 3000 driver. No change. It is not the only S3 card that I have tried that behaves like this. I have also used the bios rom downloaded directly from the card, again with no change. + +# diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2909 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2909 new file mode 100644 index 000000000..f77ab3620 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2909 @@ -0,0 +1,18 @@ +Corrupt qcow2 images with broken bitmap unfixable +Description of problem: +During a backup of a VM (via bitmaps), the disk of the VM/Snapshot went out of space. +The VM was stopped, leaving the image in a bad state. + +But now when trying to repair it, it was stuck: +``` +# qemu-img check -r all /dev/mapper/e1d2ff33--c3fd--4c1a--bcd1--2047e4efc362-efbd8056--720a--47b6--bede--4325d576ffb9 +qemu-img: Could not open '/dev/mapper/e1d2ff33--c3fd--4c1a--bcd1--2047e4efc362-efbd8056--720a--47b6--bede--4325d576ffb9': Bitmap '' doesn't satisfy the constraints +``` + +But if you want to remove the bitmap: +``` +# qemu-img bitmap --remove /dev/mapper/e1d2ff33--c3fd--4c1a--bcd1--2047e4efc362-efbd8056--720a--47b6--bede--4325d576ffb9 '' +qemu-img: Could not open '/dev/mapper/e1d2ff33--c3fd--4c1a--bcd1--2047e4efc362-efbd8056--720a--47b6--bede--4325d576ffb9': qcow2: Image is corrupt; cannot be opened read/write +``` + +It seems like qemu-img check needs some option to clear invalid bitmaps. So the image can be repaired including dropping the invalid bitmap. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/291 b/gitlab/issues_text/target_missing/host_missing/accel_missing/291 new file mode 100644 index 000000000..637ab7246 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/291 @@ -0,0 +1 @@ +deadlock in e1000e diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2912 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2912 new file mode 100644 index 000000000..e5b24839d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2912 @@ -0,0 +1,13 @@ +qcow2 image corrupted after snapshot+bitmap action +Description of problem: +When taking a backup of the VM via snapshot + bitmap, the qcow2 image became corrupt: +`qcow2: Marking image as corrupt: Preventing invalid write on metadata (overlaps with bitmap directory); further corruption events will be suppressed` + +This resulted in a corrupt (unfix-able) image (see #2909). + +While this process is something that happens multiple times a day, we never hit any issue. +The underlying storage didn't report any error, so it seems like something inside qemu broke the image. +Steps to reproduce: +Unfortunately, I was unable to reproduce this issue yet. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2915 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2915 new file mode 100644 index 000000000..fdc5a8daf --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2915 @@ -0,0 +1,29 @@ +qemu: error reading initrd /home/build/pooldir/w.linux.initramfs +Description of problem: +occasionally, qemu can't open the initrd file it's been supplied on the command line (I'm guessing this is qemu and not libvirt) + +``` +sudo virsh --connect qemu:///system start w.east --console +error: Failed to start domain 'w.east'\r\nerror: internal error: QEMU unexpectedly closed the monitor (vm='w.east'): qemu: error reading initrd /home/build/pooldir/w.linux-transmogrify.initramfs: Failed to open file \xe2\x80\x9c/home/build/pooldir/w.linux-transmogrify.initramfs\xe2\x80\x9d: open() failed: Permission denied\r\n\r\n" +``` +Steps to reproduce: +1. create, using libvirt, a config that direct boots from initrd and kernel +it creates a domain call linux, and from that creates {w.,w1,w2,w3}{east,west,north,road} +1. boots and then destroys these domains 1000's of times +2. occasionally above error occurs while trying to boot the domain +Additional information: +I suspect it is this: +``` + mapped_file = g_mapped_file_new(initrd_filename, false, &gerr); + if (!mapped_file) { + fprintf(stderr, "qemu: error reading initrd %s: %s\n", + initrd_filename, gerr->message); + exit(1); + } + x86ms->initrd_mapped_file = mapped_file; +``` +in `hw/i386/x86-common.c`. Which would suggest `g_mapped_file_new()` occasionally fails, which is worrying. + +The test framework is [Libreswan](https://testing.libreswan.org/), unresolved test results indicate a failed boot, for instance [debug log of failure](https://testing.libreswan.org/v5.2-370-ga09c7f410b/interop-ikev2-strongswan-20-strongswan-eap/OUTPUT/debug.log). + +The problem didn't happen with f40. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2919 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2919 new file mode 100644 index 000000000..31ca12ab0 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2919 @@ -0,0 +1,13 @@ +qemu-ga update resetting VssOption Registry key to default +Description of problem: +Before I installed the .exe from iso `virtio-win-0.1.271.iso`, I had value 5 in registry key `HKLM:\SYSTEM\CurrentControlSet\Services\QEMU Guest Agent VSS Provider\VssOption`. +After the driver update by the .exe, the value was set to 1. + +This registry key shouldn't change in driver update, as its value was manually set to 5 and it is important to preserve MSSQL backups in Proxmox. +Source: +https://blog.datact.ch/backup-mssql-server-with-proxmox +https://forum.proxmox.com/threads/pbs-breaking-customer-sql-backups-backups-without-fs-freeze.111526/ +Steps to reproduce: +1. Set a value to `HKLM:\SYSTEM\CurrentControlSet\Services\QEMU Guest Agent VSS Provider\VssOption` other than 1. +2. Install the .exe from version 0.1.271. +3. Check the key value. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/292 b/gitlab/issues_text/target_missing/host_missing/accel_missing/292 new file mode 100644 index 000000000..b0748e1af --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/292 @@ -0,0 +1 @@ +keyboard errors in DOS, found links to similar errors for reference diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2920 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2920 new file mode 100644 index 000000000..7694e5cc1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2920 @@ -0,0 +1,12 @@ +VGA Passthrough I/O Lag on DOS (FreeDOS) System. +Description of problem: +VGA performance lags with passthrough when the OS is in graphics mode. It also seems to affect when key presses are registered with noticeable delay. +Steps to reproduce: +1. Install Doom (v1.9 Shareware.) +2. Run setup and disable sound. +3. Play game or watch demo. +Additional information: +I have tried multiple cards with no change in performance: + +**VGA compatible controller: S3 Graphics Ltd. 86c375 [ViRGE/DX] or 86c385 [ViRGE/GX] (rev 01) (prog-if 00 [VGA controller]) +VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] R480 [Radeon X800 GTO] (prog-if 00 [VGA controller])** diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2923 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2923 new file mode 100644 index 000000000..7387c33e9 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2923 @@ -0,0 +1,13 @@ +Audio crackling issue when USB headset is pass thru via usb-host,hostbus=bus,hostaddr=addr +Description of problem: +When we pass thru USB headset via usb port pass-thru, and if the headset supports only 44100 Hz sampling rate, we hear the crackling sound. + +The headsets which support 48000Hz works fine. +Steps to reproduce: +1. Pass the usb device using hostbus,port. +2. Connect a usb headset like Logitech H340 which supports only 44100Hz sampling rate. +3. Play any audio file or youtube video, there is constant crackling sound. + +This issue is observed irrespective of the guest OS. Both ubuntu and windows guest, exhibit similar problem. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2924 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2924 new file mode 100644 index 000000000..75328c2b2 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2924 @@ -0,0 +1,15 @@ +qemu-user not responding to Ctrl-C from gdb +Description of problem: +When attached to qemu-x84_64's gdbserver via gdb, it is not possible to interrupt the binary being emulated. Usually, Ctrl-C will interrupt a running binary from gdb and I believe (though have not tested) it works in qemu-system. + +First Ctrl-C will do nothing and second will prompt to stop debugging. +``` +(gdb) c +Continuing. +^C^CThe target is not responding to interrupt requests. +Stop debugging it? (y or n) +``` +Steps to reproduce: +1. Run `./qemu-x86_64 -g 1234 ~/Downloads/base64-x64_64-static` or any static binary that will pause/hang +2. Connect from gdb `(gdb) target remote :1234` +3. Ctrl-C in gdb diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2925 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2925 new file mode 100644 index 000000000..2f3db5ab5 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2925 @@ -0,0 +1,25 @@ +Cannot exec certain QMP guest commands using unix socket but Virsh can +Description of problem: +There are two channels configured to communicate the guest. + - a) qemu.guest_agent.0 + - b) unix socket: -qmp unix:/tmp/qmp_win7-101.sock,server,nowait + + +**For unix socket connection, certain commands like ```guest-info``` and other guest functions are missing.** However, invoking guest-xx functions successfully in Virsh (through qemu.guest_agent.0). +Steps to reproduce: +``` +$sudo socat unix-connect:/tmp/qmp_win7-101.sock readline +{"QMP": {"version": {"qemu": {"micro": 0, "minor": 2, "major": 4}, "package": "qemu-kvm-4.2.0-59.module_el8.5.0+1063+c9b9feff.1"}, "capabilities": ["oob"]}} + +{"execute":"qmp_capabilities"} +{"return": {}} + +{"execute": "guest-info"} +{"error": {"class": "CommandNotFound", "desc": "The command guest-info has not been found"}} +``` + +I checked ```/etc/sysconfig/qemu-ga``` and unmarked blacklist functions, but it did not solve this problem. +``` +# original contents of qemu-ga +#BLACKLIST_RPC=guest-file-open,guest-file-close,guest-file-read,guest-file-write,guest-file-seek,guest-file-flush,guest-exec,guest-exec-status +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2926 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2926 new file mode 100644 index 000000000..f04e1ed87 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2926 @@ -0,0 +1,36 @@ +Excessive memory allocation on guest and host with gpu passthrough +Description of problem: +While gpu passthrough is enabled, the maximum amount of ram is allocated on the host (64 GB), even if the guest only has 8 GB configured as "currently allocated". +If I disable the physical gpu, the guest only takes the 8 GB. +Steps to reproduce: +1. Install qemu-kvm virt-manager libvirt-daemon-system virtinst libvirt-clients and bridge-utils. +1. Create a Windows vm with virt-manager +1. Insert discrete GPU on a secondary pcie slot. +1. Add `intel_iommu=on iommu=pt vfio-pci.ids=10de:17c8,10de:0fb0` to the GRUB kernel parameters. +1. Add `options vfio-pci ids=10de:17c8,10de:0fb0` and `softdep nvidia pre: vfio-pci` to `/etc/modprobe.d/vfio.conf`. +1. Update initrmfs image. +1. Add pcie hardware on virt-manager. +1. Install virtio and nvidia drivers on guest. +Additional information: +I'm using an Nvidia gtx 980Ti on a secondary slot for the guest. +The first slot has an rtx 4090 used by the host. + +``` +OS: Linux Mint 22.1 x86_64 +Host: MS-7E07 2.0 +Kernel: 6.8.0-51-generic +Shell: bash 5.2.21 +Resolution: 3840x2160, 3840x2160 +DE: Cinnamon 6.4.8 +WM: Mutter (Muffin) +Terminal: gnome-terminal +CPU: Intel i9-14900K (32) @ 5.700GHz +GPU: NVIDIA GeForce GTX 980 Ti +GPU: NVIDIA GeForce RTX 4090 +GPU: Intel Raptor Lake-S GT1 [UHD Graphics 770] +Memory: 73717MiB / 96317MiB +``` + +[vWin.xml](/uploads/3fe8133f67577f8724b060908b390c32/vWin.xml) +[vWin.log](/uploads/efa029460a62b62cbcff464af7cdb72a/vWin.log) + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2927 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2927 new file mode 100644 index 000000000..f38c6e7bd --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2927 @@ -0,0 +1,171 @@ +Getting bare metal code running on tricore +Description of problem: +My code is stuck in +Steps to reproduce: +1. Open Infineon Aurix Development Studio (on Windows) +2. Compile project (two examples that I've tested) +a) New -> Project -> Board -> KIT_AURIX_TC277_TFT_DC-Step -> Build +b) the example from here: https://github.com/Infineon/AURIX_code_examples/tree/master/code_examples/Blinky_LED_1_KIT_TC277_TFT +3. Copy the elf and run qemu on the debian system +Additional information: +When running a blank binary on QEMU with the TriCore TC27x target, the CPU starts executing at address 0x80000020 and enters an infinite loop. +The code seems to be stuck and waiting for some hardware signal. The binary (sample.elf) from this issue qemu-project/qemu#1363 works. + +I know it's probably a rookie problem, but what am I missing? How can I get an example from Infineon running? Or any other example? + +Please let me know if you need additional information! + +```:~/qemu$ ./build/qemu-system-tricore -M KIT_AURIX_TC277_TRB -cpu tc27x -nographic -kernel ../qemu-examples/aurix_tricore_example_bins/Blank_project_TC277.elf -d in_asm +QEMU 9.2.50 monitor - type 'help' for more information +(qemu) ---------------- +IN: _START +0x80000020: +OBJD-T: 91000028d9220681dc02 + +---------------- +IN: _Core0_start +0x80001206: +OBJD-T: 9130002f192200469120003737026e21d92200468ff2838180321b026029602a +OBJD-T: 0d0080043b009820cd42e00f + +---------------- +IN: _Core0_start +0x8000120a: +OBJD-T: 19220046 + +---------------- +IN: _Core0_start +0x8000120e: +OBJD-T: 9120003737026e21d92200468ff2838180321b026029602a0d0080043b009820 +OBJD-T: cd42e00f + +---------------- +IN: _Core0_start +0x80001232: +OBJD-T: 4d00e02fb7021420cd02e00f8212cd4220094dc0e12f8f720021012203260122 +OBJD-T: 02265422542337026e218ff283216f134381 + +---------------- +IN: _Core0_start +0x80001254: +OBJD-T: 5422 + +---------------- +IN: _Core0_start +0x80001256: +OBJD-T: 542337026e218ff283216f134381 + +---------------- +IN: _Core0_start +0x80001256: +OBJD-T: 5423 + +---------------- +IN: _Core0_start +0x80001258: +OBJD-T: 37026e218ff283216f134381 + +---------------- +IN: _Core0_start +0x80001264: +OBJD-T: 8f2200305422b7021020a6328f224021742254226f02ffff + +---------------- +IN: _Core0_start +0x80001268: +OBJD-T: 5422 + +---------------- +IN: _Core0_start +0x8000126a: +OBJD-T: b7021020a6328f224021742254226f02ffff + +---------------- +IN: _Core0_start +0x80001274: +OBJD-T: 7422 + +---------------- +IN: _Core0_start +0x80001276: +OBJD-T: 54226f02ffff + +---------------- +IN: _Core0_start +0x80001276: +OBJD-T: 5422 + +---------------- +IN: _Core0_start +0x80001278: +OBJD-T: 6f02ffff + +---------------- +IN: _Core0_start +0x8000127c: +OBJD-T: 8202cdc2200954226f120900 + +---------------- +IN: _Core0_start +0x80001282: +OBJD-T: 5422 + +---------------- +IN: _Core0_start +0x80001284: +OBJD-T: 6f120900 + +---------------- +IN: _Core0_start +0x80001296: +OBJD-T: 5422b7021020a6328f324021742254226f02ff7f + +---------------- +IN: _Core0_start +0x80001296: +OBJD-T: 5422 + +---------------- +IN: _Core0_start +0x80001298: +OBJD-T: b7021020a6328f324021742254226f02ff7f + +---------------- +IN: _Core0_start +0x800012a2: +OBJD-T: 7422 + +---------------- +IN: _Core0_start +0x800012a4: +OBJD-T: 54226f02ff7f + +---------------- +IN: _Core0_start +0x800012a4: +OBJD-T: 5422 + +---------------- +IN: _Core0_start +0x800012a6: +OBJD-T: 6f02ff7f + + +(qemu) q +``` + +When I run it with the `-d in_asm,cpu,exec` flag it logs this infinitely often: +``` +Trace 0: 0x7fb5205e9940 [00000000/00000000800012a4/00000002/ff011001] _Core0_start +PC: 800012a4 PSW: 00000980 ICR: 00000000 +PCXI: 00000000 FCX: 00000000 LCX: 00000000 +GPR A00: 00000000 00000000 f0036100 70020000 +GPR A04: 00000000 00000000 00000000 00000000 +GPR A08: 00000000 00000000 70019600 00000000 +GPR A12: 00000000 00000000 00000000 00000000 +GPR D00: 00000000 00000000 00000000 000000fc +GPR D04: 00000000 00000000 00000000 00000000 +GPR D08: 0000003f 00000000 00000000 00000000 +GPR D12: 00000000 00000000 00000000 00000000 +cpu_io_recompile: rewound execution of TB to 00000000800012a4 +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2928 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2928 new file mode 100644 index 000000000..a0bf8a0e8 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2928 @@ -0,0 +1,56 @@ +Segmentation fault in most qemu-system commands on macOS ARM +Description of problem: +Most qemu-system binaries produce a segmentation fault: +``` +raptor@fnord rust_os % qemu-system-x86_64 +zsh: segmentation fault qemu-system-x86_64 +raptor@fnord rust_os % qemu-system-mips +zsh: segmentation fault qemu-system-mips +raptor@fnord rust_os % qemu-system-sparc +zsh: segmentation fault qemu-system-sparc +... +``` + +Some of them work properly: +``` +raptor@fnord rust_os % qemu-system-aarch64 +qemu-system-aarch64: No machine specified, and there is no default +Use -machine help to list supported machines +raptor@fnord rust_os % qemu-system-arm +qemu-system-arm: No machine specified, and there is no default +Use -machine help to list supported machines +raptor@fnord rust_os % qemu-system-avr +qemu-system-avr: No machine specified, and there is no default +Use -machine help to list supported machines +... +``` +Steps to reproduce: +1. Install qemu via homebrew +2. Run `qemu-system-x86_64` +3. A segmentation fault error is produced +Additional information: +``` +raptor@fnord ~ % brew config +HOMEBREW_VERSION: 4.4.32 +ORIGIN: https://github.com/Homebrew/brew +HEAD: 12a3d4a6f1eedf483855716b989d828443438f79 +Last commit: 18 hours ago +Branch: stable +Core tap JSON: 23 Apr 08:36 UTC +Core cask tap JSON: 23 Apr 08:36 UTC +HOMEBREW_PREFIX: /opt/homebrew +HOMEBREW_CASK_OPTS: [] +HOMEBREW_MAKE_JOBS: 8 +Homebrew Ruby: 3.3.8 => /opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.8/bin/ruby +CPU: octa-core 64-bit arm_ibiza +Clang: 16.0.0 build 1600 +Git: 2.39.5 => /Library/Developer/CommandLineTools/usr/bin/git +Curl: 8.7.1 => /usr/bin/curl +macOS: 15.3.2-arm64 +CLT: 16.2.0.0.1.1733547573 +Xcode: N/A +Rosetta 2: false + +raptor@fnord ~ % brew doctor +Your system is ready to brew. +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2929 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2929 new file mode 100644 index 000000000..44fca4195 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2929 @@ -0,0 +1,7 @@ +Ask to extend vhost-user protocol to carry implementation defined error contexts +Additional information: +I am working on the Google [crosvm](https://chromium.googlesource.com/crosvm/crosvm/) project, which implements some `vhost-user` clients/servers defined by [this QEMU doc](https://qemu-project.gitlab.io/qemu/interop/vhost-user.html). I am wondering if we could add a protocol feature/protocol header flag bit to allow the payload of the reply to carry detailed implementation defined error contexts? + +Specifically, I am working on the `vhost-user-gpu` device, which needs to send some memory mapping request to the frontend(the main process where VCPU lives), so that we can map some GPU memory to the guest. We are trying to diagnose a bug where the frontend can sometimes fail to perform the operation. However, we don't have access to the logs on the main process, so we are left with only very limited information on the `vhost-user-gpu` process. It could be helpful if we could send detailed implementation defined error contexts in the payload of the reply. + +I am wondering in order for the upstream QEMU to accept such "spec" change to the `vhost-user` protocol, what the process should be like? Thanks. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2931 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2931 new file mode 100644 index 000000000..03dfc9304 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2931 @@ -0,0 +1,26 @@ +riscv: satp invalid while kvm set to cpu host +Description of problem: +After boot, no "mmu-type" in dtb +``` + cpu@0 { + + phandle = <0x7>; + device_type = "cpu"; + reg = <0x0>; + status = "okay"; + compatible = "riscv"; + riscv,isa-extensions = "i", "m", "a", "f", "d", "c", "zicntr", "zicsr", "zifencei", "zi +bb"; + riscv,isa-base = "rv64i"; + riscv,isa = "rv64imafdc_zicntr_zicsr_zifencei_zihpm_zba_zbb"; + interrupt-controller { + + #interrupt-cells = <0x1>; + interrupt-controller; + compatible = "riscv,cpu-intc"; + phandle = <0x8>; + }; + }; +``` +Steps to reproduce: +1. boot any qemu with `-cpu host` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2932 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2932 new file mode 100644 index 000000000..6bcec1fd3 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2932 @@ -0,0 +1 @@ +QEMU flag fuzz targets not WAI diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2933 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2933 new file mode 100644 index 000000000..3be0d30ab --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2933 @@ -0,0 +1,22 @@ +After updating QEMU to 10.0, XNU kernel of OS X 10.8 throws kernel panic (type=0 divide error) +Description of problem: +Before updating to QEMU 10.0, my OS X 10.8 installation has worked pretty clear, but after QEMU update, XNU kernel now throws divide error during the boot. +Steps to reproduce: +1. Install OS X 10.8 on QEMU <10.0, for example 9.2.3. +2. Update QEMU to 10.0 version +3. Launch OS X +Additional information: +Screenshot of the issue: + + +OpenCore config (not changed before update, so above suspicion): +[config.plist](/uploads/4b80b60f9497e5ecd9237e4eeddcce8a/config.plist) + +Full OS X folder (without Installer.dmg): +[OS_X_10.8.zip](/uploads/1af6150869495a8f196e18d18127011b/OS_X_10.8.zip) + +How I've done Installer.dmg: +1. Go [here](https://updates.cdn-apple.com/2021/macos/031-0627-20210614-90D11F33-1A65-42DD-BBEA-E1D9F43A6B3F/InstallMacOSX.dmg) +2. `xar -xf` to .pkg +3. Show package contents to extracted .pkg +4. Here it is: InstallESD.dmg, which I've renamed to Installer.dmg diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2934 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2934 new file mode 100644 index 000000000..586ed9577 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2934 @@ -0,0 +1,64 @@ +RSS eBPF failed to load +Description of problem: +I am seeing a failure to load the eBPF program for rss steering. +Steps to reproduce: +1. Using libvirt, enable rss='on' for the vhost driver. +2. +3. +Additional information: +Libvirt log: +``` +libbpf: prog 'tun_rss_steering_prog': BPF program load failed: Invalid argument +libbpf: prog 'tun_rss_steering_prog': -- BEGIN PROG LOAD LOG -- +back-edge from insn 587 to 501 +processed 0 insns (limit 1000000) max_states_per_insn 0 total_states 0 peak_states 0 mark_read 0 +-- END PROG LOAD LOG -- +libbpf: prog 'tun_rss_steering_prog': failed to load: -22 +libbpf: failed to load object 'rss_bpf' +libbpf: failed to load BPF skeleton 'rss_bpf': -22 +2025-04-26T09:22:19.054471Z qemu-system-x86_64: -device {"driver":"virtio-net-pci","packed":true,"tx":"bh","ioeventfd":true,"event_idx":true,"host_ecn":true,"mrg_rxbuf":true,"guest_ecn":true,"mq":true,"vectors":14,"rx_queue_size":1024,"tx_queue_size":256,"rss":true,"netdev":"hostnet0","id":"net0","mac":"52:54:00:c3:6f:c2","bus":"pci.1","addr":"0x0"}: warning: Unable to load eBPF program +``` +[qemu-log.txt](/uploads/2d5e49a38a54297586a4b1f16423fc27/qemu-log.txt) + +XML: +```xml + <interface type='bridge'> + <mac address='52:54:00:be:49:ff'/> + <source bridge='inet'/> + <model type='virtio'/> + <driver name='vhost' txmode='iothread' ioeventfd='on' event_idx='on' queues='6' rx_queue_size='1024' tx_queue_size='256' rss='on' packed='on'> + <host ecn='on' mrg_rxbuf='on'/> + <guest ecn='on'/> + </driver> + <link state='up'/> + <address type='pci' domain='0x0000' bus='0x08' slot='0x00' function='0x0'/> + </interface> +``` + +Host kernel .config: +``` +❯ zcat /proc/config.gz |grep -i bpf +CONFIG_BPF=y +CONFIG_HAVE_EBPF_JIT=y +CONFIG_ARCH_WANT_DEFAULT_BPF_JIT=y +# BPF subsystem +CONFIG_BPF_SYSCALL=y +CONFIG_BPF_JIT=y +CONFIG_BPF_JIT_ALWAYS_ON=y +CONFIG_BPF_JIT_DEFAULT_ON=y +CONFIG_BPF_UNPRIV_DEFAULT_OFF=y +# CONFIG_BPF_PRELOAD is not set +# CONFIG_BPF_LSM is not set +# end of BPF subsystem +CONFIG_CGROUP_BPF=y +CONFIG_NETFILTER_BPF_LINK=y +CONFIG_NETFILTER_XT_MATCH_BPF=m +CONFIG_NET_CLS_BPF=m +CONFIG_NET_ACT_BPF=m +CONFIG_BPF_STREAM_PARSER=y +CONFIG_LWTUNNEL_BPF=y +# HID-BPF support +CONFIG_HID_BPF=y +# end of HID-BPF support +CONFIG_BPF_EVENTS=y +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2935 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2935 new file mode 100644 index 000000000..45fd099d1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2935 @@ -0,0 +1,24 @@ +strchrnul detection not suitable for macOS +Description of problem: +When qemu is compiled on macOS 15.4, targeting an earlier macOS version (e.g., 15.1), and then run on this earlier macOS version (15.1), it segfaults. This is because: + +- the meson test for strchrnul succeeds (the function is present in the library) +- the strchrnul function is therefore used +- but that function was introduced in the system's libc in 15.4 only + +The root cause for the bug is that the meson test for strchrnul does not include the appropriate header. Indeed, see the documentation for meson on compiler.has_function (https://mesonbuild.com/Compiler-properties.html#does-a-function-exist) + +> Note that, on macOS programs can be compiled targeting older macOS versions than the one that the program is compiled on. It can't be assumed that the OS version that is compiled on matches the OS version that the binary will run on. +> +> Therefore when detecting function availability with compiler.has_function(), it is important to specify the correct header in the prefix argument. + +The correct fix would be, in qemu's meson.build, to change: + +`cc.has_function('strchrnul')` + +into `cc.has_function('strchrnul', prefix : '#include <string>')` + +This is the recommended best practice and would allow correct detection on all platforms, including macOS. +Steps to reproduce: +1. Install qemu from Homebrew, which is built on macOS 15.4 +2. Run it on a machine with macOS < 15.4 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2937 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2937 new file mode 100644 index 000000000..7924cd50f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2937 @@ -0,0 +1 @@ +Request for Assistance: Properly Emulating USB Devices in QEMU for Custom USB Driver Testing diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2939 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2939 new file mode 100644 index 000000000..8e2d45bb7 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2939 @@ -0,0 +1 @@ +Add m68k board name called Macintosh llci diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/294 b/gitlab/issues_text/target_missing/host_missing/accel_missing/294 new file mode 100644 index 000000000..f998e37ab --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/294 @@ -0,0 +1 @@ +Keyboard keys get stuck diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2940 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2940 new file mode 100644 index 000000000..88267d9c1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2940 @@ -0,0 +1 @@ +Fix i cant boot nextstep os in qemu m68k using next-cube diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2941 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2941 new file mode 100644 index 000000000..4ea71fd79 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2941 @@ -0,0 +1 @@ +last chance add board called Macintosh llci diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2943 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2943 new file mode 100644 index 000000000..0f90795e4 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2943 @@ -0,0 +1,7 @@ +Please add a configurable for disabling, or by default disable, KVM_X86_QUIRK_IGNORE_GUEST_PAT on Intel host CPU +Additional information: +I am not familiar with QEMU code base or much programming in general. I did a quick grep through the latest QEMU sources pulled from this repository for the string `KVM_X86_QUIRK_IGNORE_GUEST_PAT`. It does not seem to occur anywhere which makes me think its existence and effect on QEMU users has gone unnoticed. + +If there is a handling of this flag which I have not noticed in the QEMU source code or documentation please guide me to where I can read about and probably configure it. + +Thank you. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2945 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2945 new file mode 100644 index 000000000..a29740c31 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2945 @@ -0,0 +1,29 @@ +Commit da954d0e introduces a regression on sifive_unleashed when booting from SD card +Description of problem: +In U-Boot CI, we started to update from v8.2.0 to v9.2.3 and found that the sifive_unleashed target was failing to boot from SD card in our tests (we also test via SPI and this is fine). I have bisected the problem down to commit [da954d0e ("hw/sd/sdcard: Add spi_cmd_SEND_CSD/CID handlers (CMD9 & CMD10)")](https://gitlab.com/qemu-project/qemu/-/commit/da954d0e32444f122a41c24948d4d1c718bf66d4). + +When running QEMU we see the following output in the failure case as the only output: +``` +U-Boot SPL 2025.07-rc1-00033-gad60d9792896 (May 01 2025 - 17:08:34 +0000) +Trying to boot from MMC1 +spl: mmc init failed with error: -110 +Error: -110 +SPL: failed to boot from all boot devices +# +Steps to reproduce: +1. wget -O - https://github.com/pengutronix/genimage/releases/download/v14/genimage-14.tar.xz | tar -C /tmp -xJ ; cd /tmp/genimage-14 +2. ./configure && make -j$(nproc) +3. git clone https://source.denx.de/u-boot/u-boot.git; cd u-boot +4. wget -O - https://github.com/riscv-software-src/opensbi/releases/download/v1.3.1/opensbi-1.3.1-rv-bin.tar.xz | tar -C /tmp -xJ +5. export OPENSBI=/tmp/opensbi-1.3.1-rv-bin/share/opensbi/lp64/generic/firmware/fw_dynamic.bin +6. make O=/tmp/sifive_unleashed CROSS_COMPILE=riscv64-linux- sifive_unleashed_defconfig +7. make O=/tmp/sifive_unleashed CROSS_COMPILE=riscv64-linux- -sj$(nproc) +8. mkdir -p root +9. cp /tmp/sifive_unleashed/spl/u-boot-spl.bin . +10. cp /tmp/sifive_unleashed/u-boot.itb . +11. rm -rf tmp +12. genimage --inputpath . --config board/sifive/unleashed/genimage_sdcard.cfg +13. cp images/sdcard.img /tmp/sifive_unleashed/ +14. qemu-system-riscv64 -smp 5 -m 8G -nographic -M sifive_u,msel=11 -bios /tmp/sifive_unleashed/spl/u-boot-spl.bin -drive file=/tmp/sifive_unleashed/sdcard.img,format=raw,if=sd +Additional information: +The genimage tool is required for making the disk images used here. If building everything here is too much, I can provide the U-Boot binaries needed here out of band. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2946 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2946 new file mode 100644 index 000000000..953717b95 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2946 @@ -0,0 +1,10 @@ +crypto/aes.c (used for emulating aes instructions) has a timing side-channel +Description of problem: +https://gitlab.com/qemu-project/qemu/-/blob/a9cd5bc6399a80fcf233ed0fffe6067b731227d8/crypto/aes.c#L1021 + +much of the code in crypto/aes.c accesses memory arrays where the array index is based on the secret data being encrypted/decrypted. because of cpu caches and other things that can delay memory accesses based on their address, this is a timing side-channel, potentially allowing leaking secrets over a network based on timing how long cryptography operations take. + +compare to openssl which uses an algorithm where its execution time doesn't depend on the data being processed: +https://github.com/openssl/openssl/commit/0051746e03c65f5970d8ca424579d50f58a877e0 + +I initially reported this as a security issue, but was told that since it's only used by TCG, it isn't a security issue, since TCG isn't considered secure. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2947 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2947 new file mode 100644 index 000000000..8fc910878 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2947 @@ -0,0 +1,10 @@ +Tablet-like mouse under Linux guest even if no -device usb-tablet is specified +Description of problem: +Arch Linux guest has absolute mouse tracking even when there is `-nodefaults` and no -device usb-tablet is provided. The guest does not have qemu guest agent installed. This is the unwanted behavior. The expected behavior is that it has a separate mouse pointer under guest, like with Windows guest. +Steps to reproduce: +1. Install guest operating system +2. Install gnome metapackage and enable GDM +3. Reboot +4. GDM has absolute mouse tracking and the mouse gets captured automatically, without having to click on the window or pressing Ctrl+Alt+G +Additional information: +[journalctl](/uploads/356952b8e2454c98e76ad82b700c518e/journalctl) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2948 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2948 new file mode 100644 index 000000000..ab3831f86 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2948 @@ -0,0 +1,13 @@ +-display sdl causes mice with relative movement to read garbage offsets +Description of problem: +`-device virtio-mouse` and `-device usb-mouse` (and probably other mice which send relative mouse movement data) are behaving incorrectly under linux guest and jitter a lot. In this specific case it only seems to happen with `-display sdl` as I could not reproduce this same issue with other of the following configurations: `-display gtk` and `-display spice-app` running with virt-viewer. +This behavior is not present when running a Windows guest with the same configuration using `-display sdl` + +Another weird side note: this behavior is less apparent when running `evtest` on the exact mouse device having issues. + + +Steps to reproduce: +1. Install guest operating system +2. Install gnome metapackage and enable GDM +3. Reboot +4. The mouse shows jittery motion on the GDM screen. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2949 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2949 new file mode 100644 index 000000000..2ac83975e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2949 @@ -0,0 +1,17 @@ +VNC: virtio-gpu outputs not displayed by VNC client +Description of problem: +When combining virtio-gpu multiple outputs with VNC display, only output 0 is enabled. +Additional output are enabled when VNC client sent SetDesktopSize command. + +The following statement assumes that all displays (gtk, sdl) are disabled except VNC: + +# +Steps to reproduce: +1. Start Qemu +2. Start a VNC client on 5900 +3. Start the second VNC client on 5901 +Additional information: +The state of an output is controlled by the [enabled_output_bitmask](https://gitlab.com/qemu-project/qemu/-/blob/master/include/hw/virtio/virtio-gpu.h#L158) which is initialized to `1` at [device realization](https://gitlab.com/qemu-project/qemu/-/blob/master/hw/display/virtio-gpu-base.c#L204), thus VNC0 is always enabled. + +Other devices will set this parameter during inititliazation by calling [dpy_set_ui_info](https://gitlab.com/qemu-project/qemu/-/blob/master/ui/console.c#L754) which schedules a call to [virtio_gpu_ui_info](https://gitlab.com/qemu-project/qemu/-/blob/master/hw/display/virtio-gpu-base.c#L89). However VNC calls this function only when handling [VNC_MSG_CLIENT_SET_DESKTOP_SIZE](https://gitlab.com/qemu-project/qemu/-/blob/master/ui/vnc.c#L2607) client command.\ +If the client does not support this command or never changes the size of the default window, the respective display will remain disabled. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2950 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2950 new file mode 100644 index 000000000..08989a94e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2950 @@ -0,0 +1,65 @@ +QEMU 10 breaks Incus' NVME handling +Description of problem: +Incus is an open-source container and VM manager. +For VMs we naturally use QEMU where we basically: + - Use QMP as much as possible to put together the VM prior to starting emulation + - Put the static pre-start stuff in a config file + use readconfig + - Keep the command line to a bare minimum + +This isn't particularly relevant to this issue except for the first point which is our use of QMP for most device handling. That means qemu is spawned without any disk or network attached. We have a `virtio-scsi` controller in the base config file but that's it. + +When doing NVME, we hotplug a new drive and a new nvme device pointing to that drive. +This means that our setup has a 1:1 mapping between NVME controllers on the PCIe bus and drives. + +This worked great up until QEMU 10. With QEMU 10, I believe this commit https://gitlab.com/qemu-project/qemu/-/commit/cd59f50ab017183805a0dd82f5e85159ecc355ce by @birkelund now effectively causes the creation of a `nvme-subsys` device when we add a `nvme` device without a pre-existing subsystem. + +As `nvme-subsys` doesn't support hotplugging, this immediately breaks all our VMs that rely on NVME. + +``` +stgraber@dakara:~$ incus start test-nvme +Error: Failed setting up device via monitor: Failed adding block device for disk device "root": Failed adding device: Device 'nvme-subsys' does not support hotplugging +Try `incus info --show-log test-nvme` for more info +``` + +As you can see, QEMU returns `Device 'nvme-subsys' does not support hotplugging`. + +On the QMP front, we did: +``` +stgraber@dakara:~$ sudo cat /var/log/incus/test-nvme/qemu.qmp.log +[2025-05-06T11:42:30-04:00] QUERY: {"execute":"qom-get","arguments":{"path":"/machine","property":"type"}} +[2025-05-06T11:42:30-04:00] REPLY: {"return": "pc-q35-10.0-machine"} + +[2025-05-06T11:42:30-04:00] QUERY: {"execute":"query-cpus-fast"} +[2025-05-06T11:42:30-04:00] REPLY: {"return": [{"thread-id": 3885061, "props": {"core-id": 0, "thread-id": 0, "node-id": 0, "socket-id": 0}, "qom-path": "/machine/unattached/device[0]", "cpu-index": 0, "target": "x86_64"}]} + +[2025-05-06T11:42:30-04:00] QUERY: {"execute":"netdev_add","arguments":{"fds":"/dev/net/tun.0:/dev/net/tun.1","id":"incus_eth0","type":"tap","vhost":true,"vhostfds":"/dev/vhost-net.0:/dev/vhost-net.1"}} +[2025-05-06T11:42:30-04:00] REPLY: {"return": {}} + +[2025-05-06T11:42:30-04:00] QUERY: {"execute":"device_add","arguments":{"addr":"00.0","bootindex":1,"bus":"qemu_pcie4","driver":"virtio-net-pci","id":"dev-incus_eth0","mac":"10:66:6a:30:97:66","mq":true,"netdev":"incus_eth0","vectors":6}} +[2025-05-06T11:42:30-04:00] REPLY: {"return": {}} + +[2025-05-06T11:42:30-04:00] QUERY: {"execute":"blockdev-add","arguments":{"aio":"native","cache":{"direct":true,"no-flush":false},"discard":"unmap","driver":"host_device","filename":"/dev/fdset/0","locking":"off","node-name":"incus_root","read-only":false}} +[2025-05-06T11:42:30-04:00] REPLY: {"return": {}} + +[2025-05-06T11:42:30-04:00] QUERY: {"execute":"device_add","arguments":{"addr":"00.0","bootindex":0,"bus":"qemu_pcie5","drive":"incus_root","driver":"nvme","id":"dev-incus_root","serial":"incus_root"}} +[2025-05-06T11:42:30-04:00] QUERY: {"execute":"blockdev-del","arguments":{"node-name":"incus_root"}} +[2025-05-06T11:42:30-04:00] REPLY: {"return": {}} + +[2025-05-06T11:42:30-04:00] QUERY: {"execute":"query-fdsets"} +[2025-05-06T11:42:30-04:00] REPLY: {"return": [{"fds": [{"fd": 49, "opaque": "rdwr:incus_root"}], "fdset-id": 0}]} + +[2025-05-06T11:42:30-04:00] QUERY: {"execute":"remove-fd","arguments":{"fdset-id":0}} +[2025-05-06T11:42:30-04:00] REPLY: {"return": {}} +``` +Additional information: +My limited understanding of NVME concepts is that NVME controllers are tied to a subsystem, then drives are tied to namespaces which themselves are tied to subsystems. + +So in a world where we need to deal with QEMU not supporting hotplugging subsystems, we would be able to create a single subsystem with a single controller and then hot plug/remove drives+namespaces into that. + +I've not actually tested this because to us it's not really an option. +We have users that for better or for worse currently rely on the current behavior of having each drive have its own controller, and so on the Linux side expect to see one PCIe device per drive and then one `/dev/nvmeXn1` device per drive. + +Changing this to be multiple namespaces on controller 0 would break anyone who ever hardcoded /dev/nvmeXn1 on their system and may also lead to different performance characteristics due to now using a single controller. Multiple controllers would still be an option of course, but they'd be tied to the same subsystem and namespaces so effectively now having the guest do NVME multipath. + + +Anyway, let me know if I'm missing a way to get QEMU 10 to behave as we did in releases prior, where I can start a VM with 0 NVME controllers, then add a couple of drives, each showing up as their own controller with the drive as namespace 1 on that. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2951 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2951 new file mode 100644 index 000000000..a1dc70090 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2951 @@ -0,0 +1,21 @@ +First byte of USB NIC is hardcoded to 0x40 +Description of problem: +Incus recently added support for USB attached network interfaces. +As with any network device, we generate a MAC address (using our MAC OUI) and allow the user to override that to a value of their choice. + +That's when we noticed that no matter what MAC address we set, the resulting MAC always has the prefix swapped to "40:". Looking into the code, this is done on purpose here: + +https://gitlab.com/qemu-project/qemu/-/blob/master/hw/usb/dev-network.c?ref_type=heads#L1386 + +Unfortunately there is no comment in the code or in any of the commits touching that code as far as why that is. + +We've also looked at the libvirt code handling those devices and that code seems to also assume that a user provided MAC will be correctly passed through to the guest, no mention of the odd prefix override. + +This is a bit concerning as there are valid IEEE OUI with the "40:" prefix. +So this means that QEMU may be generating collisions with actual physical MAC addresses... + +For a few months now, I've been applying this small patch to my own Incus packages (which bundle QEMU) and haven't heard or seen any obvious issue from the change. + +https://github.com/zabbly/incus/blob/daily/patches/qemu-0001-usb-net-mac.patch + +Does anyone know why this hardcoded MAC address prefix exists? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2952 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2952 new file mode 100644 index 000000000..15628b8c8 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2952 @@ -0,0 +1,14 @@ +Truncated bits while writing value to registers of RISC-V +Description of problem: +As mentioned above +Steps to reproduce: +``` +# 1. Compile the `test.S`: +riscv32-unknown-linux-gnu-gcc -g -static -nostartfiles -o test hello.S + +# 2. Execute the binary: +qemu-riscv32 ./test + +# 3. Check exit code +echo $? +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2953 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2953 new file mode 100644 index 000000000..e4a265961 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2953 @@ -0,0 +1,66 @@ +"DMAR: DRHD: handling fault status reg 2" with vfio on kernel 6.13.11-200.fc41.x86_64, works with 6.13.9-200.fc41.x86_64 +Description of problem: +Since kernel 6.13.11-200.fc41.x86_64, I cannot use VFIO to pass an NVIDIA GeForce GTX 1070 card to a Windows guest. The same setup works just fine in 6.13.9-200.fc41.x86_64. The issue symptoms are the same regardless if I use kernel command line arguments to isolate cpus or not. + +Symptoms: +- qemu logs show: +``` +2025-05-07T09:59:49.957891Z qemu-system-x86_64: vfio: Cannot reset device 0000:36:00.1, no available reset mechanism. +2025-05-07T09:59:49.958444Z qemu-system-x86_64: vfio: Cannot reset device 0000:36:00.0, no available reset mechanism. +2025-05-07T09:59:49.959119Z qemu-system-x86_64: vfio: Cannot reset device 0000:36:00.1, no available reset mechanism. +2025-05-07T09:59:49.959635Z qemu-system-x86_64: vfio: Cannot reset device 0000:36:00.0, no available reset mechanism. +``` +- in dmesg I see: +``` +kernel: DMAR: DRHD: handling fault status reg 2 +kernel: DMAR: [INTR-REMAP] Request device [36:00.0] fault index 0x50 [fault reason 0x22] Present field in the IRTE entry is clear +``` +- the VM hangs at boot (please see the notes below (*)). +Steps to reproduce: +Boot the same libvirt domain in kernel 6.13.9-200.fc41.x86_64 (works) and any other more recent kernel (>= 6.13.11-200.fc41.x86_64). +Additional information: +(*) Note that in a working kernel, the boot process is in any case finicky, and it shows these phases: +1. tianocore logo shows, and one single cpu is fully utilized by the guest +2. slowly, the loader find the Windows bootloader, and prints a message that it is loading and running it +3. some time passes, while cpus seem idle +4. finally the spinning wheel of the Windows bootloader appears + +Phase 1-3 can take anywhere from 0 to 60 seconds, in an apparently random manner. + +When running on the faulty kernels, it seems that the virtual machine gets stuck in phase 1, and I must use `virsh destroy` to interrupt it. + +lspci output: +``` +-[0000:00]-+-00.0 Intel Corporation Tiger Lake-UP3/H35 4 cores Host Bridge/DRAM Registers + +-02.0 Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] + +-04.0 Intel Corporation TigerLake-LP Dynamic Tuning Processor Participant + +-06.0-[01]----00.0 Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 + +-07.0-[02-33]-- + +-0a.0 Intel Corporation Tigerlake Telemetry Aggregator Driver + +-0d.0 Intel Corporation Tiger Lake-LP Thunderbolt 4 USB Controller + +-0d.2 Intel Corporation Tiger Lake-LP Thunderbolt 4 NHI #0 + +-14.0 Intel Corporation Tiger Lake-LP USB 3.2 Gen 2x1 xHCI Host Controller + +-14.2 Intel Corporation Tiger Lake-LP Shared SRAM + +-15.0 Intel Corporation Tiger Lake-LP Serial IO I2C Controller #0 + +-15.1 Intel Corporation Tiger Lake-LP Serial IO I2C Controller #1 + +-15.2 Intel Corporation Tiger Lake-LP Serial IO I2C Controller #2 + +-16.0 Intel Corporation Tiger Lake-LP Management Engine Interface + +-1c.0-[34]----00.0 Intel Corporation Wi-Fi 6 AX200 + +-1c.5-[35]----00.0 Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader + +-1d.0-[36]--+-00.0 NVIDIA Corporation GP104 [GeForce GTX 1070] + | \-00.1 NVIDIA Corporation GP104 High Definition Audio Controller + +-1f.0 Intel Corporation Tiger Lake-LP LPC Controller + +-1f.3 Intel Corporation Tiger Lake-LP Smart Sound Technology Audio Controller + +-1f.4 Intel Corporation Tiger Lake-LP SMBus Controller + \-1f.5 Intel Corporation Tiger Lake-LP SPI Controller +``` + +kernel command line arguments (optimized with cpu isolation): +``` +intel_pstate=per_cpu_perf_limits rd.driver.blacklist=nouveau modprobe.blacklist=nouveau module_blacklist=nouveau default_hugepagesz=1G hugepagesz=1G hugepages=13 i2c_i801.disable_features=0x10 rd.driver.pre=vfio_pci,vfio,vfio_iommu_type1 vfio-pci.ids=10de:1b81,10de:10f0 modprobe.blacklist=xpad systemd.unit=multi-user.target systemd.wants=bluetooth.service isolcpus=domain,managed_irq,1-3,5-7 rcu_nocbs=1-3,5-7 irqaffinity=0,4 nospectre_v2 +``` + +kernel command line arguments (without cpu isolation, same symptoms): +``` +intel_pstate=per_cpu_perf_limits rd.driver.blacklist=nouveau modprobe.blacklist=nouveau module_blacklist=nouveau default_hugepagesz=1G hugepagesz=1G hugepages=13 rd.driver.pre=vfio_pci,vfio,vfio_iommu_type1 vfio-pci.ids=10de:1b81,10de:10f0 modprobe.blacklist=xpad systemd.unit=multi-user.target systemd.wants=bluetooth.service +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2955 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2955 new file mode 100644 index 000000000..ad8db235e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2955 @@ -0,0 +1 @@ +Mellanox IRQs Still Showing In Host OS After Passthrough diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2958 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2958 new file mode 100644 index 000000000..589177916 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2958 @@ -0,0 +1,18 @@ +Vvfat crashes in WinXP-64 installation. +Description of problem: + +Steps to reproduce: +1. Download ISO (see above) +2. Set up qemu +3. Run command above + +Termux output: +qemu-system-x86_64: Slirp: Failed to send packet, ret: -1 [repeated] + +../block/vvfat.c:105: void *array_get(array_t *, unsigned int): assertion "index < array->next" failed +Aborted +~ $ +Additional information: +This was extremely annoying because the total abort occurs far into the installation, while setting up the network. The devices (presumably including the vvfat) had been installed OK. The XP installation can be restarted without the CD but starts at the beginning, needing location, passwords, licence key etc. all over again! I have XP64 installed now, without vvfat which is a marvellously convenient way of transferring files. + +BTW "vfat" usually means extended FAT, handling files over 4GB but vvfat does not. Can you fix that? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2959 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2959 new file mode 100644 index 000000000..177f4e752 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2959 @@ -0,0 +1,77 @@ +int 0x10 teletype output cuts final character in custom MBR on QEMU (i386 real mode) +Description of problem: +When using QEMU to test a custom bootloader in 16-bit real mode (i386), the BIOS interrupt `int 0x10` with AH=0x0E (teletype output) fails to display the last character of the printed message. For example, printing `"hello"` only renders `"hell"`. + +This happens only with this exact combination: + +real mode `int 0x10` teletype output + +message ends with `13, 10, 0` + +`QEMU` output cuts off the last character consistently + +All buffer and code logic has been verified to be correct. The same code, when run on Bochs or physical hardware, prints properly. +Steps to reproduce: +1.Assemble the following boot.asm: +```nasm +[org 0x7C00] +[BITS 16] + +_start: + cli + xor ax, ax + mov ds, ax + mov es, ax + mov ss, ax + mov sp, 0x7C00 + + mov si, msg + call print + + hlt + jmp $ + +print: + pusha +.loop: + lodsb + or al, al + jz .done + mov ah, 0x0E + int 0x10 + jmp .loop +.done: + popa + ret + +msg db 'hello', 13, 10, 0 +times 510 - ($ - $$) db 0 +dw 0xAA55 +``` + +2. Compile and run: +```bash +$ nasm -f bin boot.asm -o boot.img +$ qemu-system-i386 -nographic -boot a -drive format=raw,file=boot.img,index=0,if=floppy +``` + +3. Output will be: +```text +Booting from Floppy... +hell +``` +Expected output: +```text +Booting from Floppy... +hello +``` +Additional information: +- Adding padding (extra 13, 10) does not solve the problem. + +- Confirmed that boot.img includes all bytes (xxd dump is correct). + +- Tested on multiple machines with same QEMU version. + +- May relate to VGA character output buffer not flushing after last INT 0x10? + +- This makes QEMU inaccurate for BIOS-level debugging of bootloaders. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/296 b/gitlab/issues_text/target_missing/host_missing/accel_missing/296 new file mode 100644 index 000000000..4d3f6ac99 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/296 @@ -0,0 +1 @@ +Enabling OpenGL for GUI doesn't work on old laptop diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2960 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2960 new file mode 100644 index 000000000..2af7f34f6 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2960 @@ -0,0 +1,10 @@ +Mouse doesn't work correctly with SDL display backend +Description of problem: +The mouse starts moving like crazy, up and down or left and right. +I tested it with -accel on and off, I make some test and seems to be the SDL display backed(GTK just crash before start execution of the vm). +Steps to reproduce: +1.Install Linux Mint 22.1 +2.Execute the command above. +3.Log in and the problems start. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2962 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2962 new file mode 100644 index 000000000..43f4258c3 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2962 @@ -0,0 +1,22 @@ +DHCP UDP checksum workaround code appears to be broken +Description of problem: +I am running dnsmasq DHCP server in an lxc-container. It is using a VETH pair for the network. The VETH device on the host is in a bridge. I create a TAP device and place it in the bridge. When booting the guest, I notice that the DHCP OFFER has an invalid UDP checksum all the way through the bridge and into the guest. I am able to fix this by disabling checksum offload inside the container, or adding an nftables rule that zeros out the checksum, or by reverting commit 7987d2be5a8bc3a502f89ba8cf3ac3e09f64d1ce. +Steps to reproduce: +1. From a debian 12 host, `apt-get install lxc lxc-templates` +2. `ip link add brtest type bridge` +3. `ip link set brtest up` +4. Create a container: `lxc-create -n dhcp -t debian -- --package=dnsmasq` +5. Edit the lxc container file `/var/lib/lxc/dhcp/config` and make sure the link is properly set to `lxc.net.0.link = brtest`, the type is set to `veth`, and give it an IP `lxc.net.0.ipv4.address = 192.168.255.1/24` +6. Start the container: `lxc-start -n dhcp` +7. Attach to the container: `lxc-attach -n dhcp` +8. Stop dnsmasq and networking: `systemctl stop dnsmasq.service networking.service` +9. Run a DHCP server: `dnsmasq --dhcp-authoritative --dhcp-range=192.168.255.2,192.168.255.254,255.255.255.0,1h --dns-loop-detect` +10. Exit the container: `exit` +11. Download the linux mint 22.1 installer: https://linuxmint.com/edition.php?id=319 +12. Create a TAP device and throw it in the bridge: `ip tuntap add dev taptest mode tap` .. `ip link set dev taptest up master brtest` +13. Run qemu: `qemu-system-x86_64 -enable-kvm -smp 4,sockets=1,threads=1 -machine pc-q35-9.2,accel=kvm,kernel_irqchip=on -m 4096 -device virtio-net-pci,netdev=nic91 -netdev tap,id=nic91,ifname=taptest,script=no,downscript=no -cdrom linuxmint-22.1-cinnamon-64bit.iso` .. I run it with vnc as this is on a headless server. +14. Once the guest has booted, you can run a tcpdump on the NIC and see that the guest receives the DHCP offer, but the UDP checksum is bunk. +Additional information: +I was able to test reverting the commit 7987d2be5a8bc3a502f89ba8cf3ac3e09f64d1ce and that appears to function once again. + +{width=901 height=38} diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2963 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2963 new file mode 100644 index 000000000..e791869df --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2963 @@ -0,0 +1,24 @@ +QEMU crash with `qemu_mutex_unlock_impl: Operation not permitted` during block device operations +Description of problem: +We got a crash when I use a blockdev-add command while a blockdev-backup operation was nearly complete. The crash does not reproduce consistently. + +This message was printed in the QEMU debug log. +`qemu: qemu_mutex_unlock_impl: Operation not permitted` + +We also collected a coredump at the time of the crash. but, when analyzing the coredump using gdb, the call stack only shows ?? for all frames, making it difficult to diagnose the root cause. + +so I have two main questions: + +1. Under what circumstances does `qemu_mutex_unlock_impl: Operation not permitted` occur? +Is there any known cause or workaround for this kind of crash? + +2. What should be done to ensure that the call stack in a coredump is visible? +Are there specific build flags or debug symbol requirements we should be aware of? +We built QEMU with --enable-debug, but the call stack still shows only ?? in gdb when analyzing the core dump. +Steps to reproduce: +1. Start a VM with block devices configured. +2. Begin a blockdev-backup operation. +3. Near the completion of the blockdev-backup, issue a blockdev-add command for another device. +4. Observe a crash. (The crash does not reproduce consistently) +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2964 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2964 new file mode 100644 index 000000000..94df21207 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2964 @@ -0,0 +1,9 @@ +How to get the icount value after qemu terminal exit +Description of problem: + +Steps to reproduce: +1. +2. +3. +Additional information: +/label ~"kind::Bug" diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2965 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2965 new file mode 100644 index 000000000..98bedb9d4 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2965 @@ -0,0 +1,14 @@ +crash when interacting with the UI in any way during record/replay mode on macOS +Description of problem: +``` +** +ERROR:../replay/replay-events.c:119:replay_add_event: assertion failed: (replay_mutex_locked()) +Bail out! ERROR:../replay/replay-events.c:119:replay_add_event: assertion failed: (replay_mutex_locked()) +fish: Job 1, 'qemu-system-x86_64 -icount shif…' terminated by signal SIGABRT (Abort) +``` +Steps to reproduce: +1. run the qemu command +2. click in the window +3. observe crash +Additional information: +[qemu-system-x86_64-2025-05-15-032037.ips](/uploads/2cccc7b967dacc8a18be8a3d0a0cf297/qemu-system-x86_64-2025-05-15-032037.ips) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2967 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2967 new file mode 100644 index 000000000..8b86b143a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2967 @@ -0,0 +1,214 @@ +Heavy graphic glitches when using Virtio with 3D acceleration +Description of problem: +Virtio with 3D acceleration enabled under "Video" and the corresponding OpenGL activated under "Display" with Spice leads to heavy artifacts in the graphical console. + +This error has been observed on Arch Linux with Intel Meteor Lake CPU (Intel Arc Graphics iGPU) as well as on OpenSuse Tumbleweed with Intel Kaby Lake CPU (Intel HD 630 iGPU) + + +(virtio without acceleration enabled) + + +(Same VM, same settings, but with 3D acceleration and OpenGL enabled) + + +(Same issue on a fresh install of OpenSuse Tumbleweed on a system that is in no way linked to the first one) +Steps to reproduce: +1. Enable Virtio Graphics with 3D acceleration under "Video". +2. Activate the corresponding OpenGL under "Spice". +3. Start the VM and open the graphical console. +Additional information: +XML config: + +``` +<domain type='kvm'> + <name>debian12</name> + <uuid>1d39d86a-b341-47bb-9847-4c78da9df863</uuid> + <metadata> + <libosinfo:libosinfo xmlns:libosinfo="http://libosinfo.org/xmlns/libvirt/domain/1.0"> + <libosinfo:os id="http://debian.org/debian/12"/> + </libosinfo:libosinfo> + </metadata> + <memory unit='KiB'>4194304</memory> + <currentMemory unit='KiB'>4194304</currentMemory> + <vcpu placement='static'>4</vcpu> + <os firmware='efi'> + <type arch='x86_64' machine='pc-q35-9.1'>hvm</type> + <firmware> + <feature enabled='no' name='enrolled-keys'/> + <feature enabled='no' name='secure-boot'/> + </firmware> + <loader readonly='yes' type='pflash'>/usr/share/edk2/x64/OVMF_CODE.4m.fd</loader> + <nvram template='/usr/share/edk2/x64/OVMF_VARS.4m.fd'>/var/lib/libvirt/qemu/nvram/debian12_VARS.fd</nvram> + <boot dev='hd'/> + </os> + <features> + <acpi/> + <apic/> + <vmport state='off'/> + </features> + <cpu mode='host-passthrough' check='none' migratable='on'/> + <clock offset='utc'> + <timer name='rtc' tickpolicy='catchup'/> + <timer name='pit' tickpolicy='delay'/> + <timer name='hpet' present='no'/> + </clock> + <on_poweroff>destroy</on_poweroff> + <on_reboot>restart</on_reboot> + <on_crash>destroy</on_crash> + <pm> + <suspend-to-mem enabled='no'/> + <suspend-to-disk enabled='no'/> + </pm> + <devices> + <emulator>/usr/bin/qemu-system-x86_64</emulator> + <disk type='file' device='disk'> + <driver name='qemu' type='qcow2' discard='unmap'/> + <source file='/var/lib/libvirt/images/debian12.qcow2'/> + <target dev='vda' bus='virtio'/> + <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> + </disk> + <disk type='file' device='cdrom'> + <driver name='qemu' type='raw'/> + <target dev='sda' bus='sata'/> + <readonly/> + <address type='drive' controller='0' bus='0' target='0' unit='0'/> + </disk> + <controller type='usb' index='0' model='qemu-xhci' ports='15'> + <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> + </controller> + <controller type='pci' index='0' model='pcie-root'/> + <controller type='pci' index='1' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='1' port='0x10'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> + </controller> + <controller type='pci' index='2' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='2' port='0x11'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> + </controller> + <controller type='pci' index='3' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='3' port='0x12'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> + </controller> + <controller type='pci' index='4' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='4' port='0x13'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> + </controller> + <controller type='pci' index='5' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='5' port='0x14'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> + </controller> + <controller type='pci' index='6' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='6' port='0x15'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x5'/> + </controller> + <controller type='pci' index='7' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='7' port='0x16'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x6'/> + </controller> + <controller type='pci' index='8' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='8' port='0x17'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x7'/> + </controller> + <controller type='pci' index='9' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='9' port='0x18'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0' multifunction='on'/> + </controller> + <controller type='pci' index='10' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='10' port='0x19'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x1'/> + </controller> + <controller type='pci' index='11' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='11' port='0x1a'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x2'/> + </controller> + <controller type='pci' index='12' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='12' port='0x1b'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x3'/> + </controller> + <controller type='pci' index='13' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='13' port='0x1c'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x4'/> + </controller> + <controller type='pci' index='14' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='14' port='0x1d'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x5'/> + </controller> + <controller type='sata' index='0'> + <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> + </controller> + <controller type='virtio-serial' index='0'> + <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> + </controller> + <interface type='network'> + <mac address='52:54:00:d6:22:67'/> + <source network='default'/> + <model type='virtio'/> + <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> + </interface> + <serial type='pty'> + <target type='isa-serial' port='0'> + <model name='isa-serial'/> + </target> + </serial> + <console type='pty'> + <target type='serial' port='0'/> + </console> + <channel type='unix'> + <target type='virtio' name='org.qemu.guest_agent.0'/> + <address type='virtio-serial' controller='0' bus='0' port='1'/> + </channel> + <channel type='spicevmc'> + <target type='virtio' name='com.redhat.spice.0'/> + <address type='virtio-serial' controller='0' bus='0' port='2'/> + </channel> + <input type='tablet' bus='usb'> + <address type='usb' bus='0' port='1'/> + </input> + <input type='mouse' bus='ps2'/> + <input type='keyboard' bus='ps2'/> + <graphics type='spice'> + <listen type='none'/> + <image compression='off'/> + <gl enable='yes'/> + </graphics> + <sound model='ich9'> + <address type='pci' domain='0x0000' bus='0x00' slot='0x1b' function='0x0'/> + </sound> + <audio id='1' type='spice'/> + <video> + <model type='virtio' heads='1' primary='yes'> + <acceleration accel3d='yes'/> + </model> + <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> + </video> + <redirdev bus='usb' type='spicevmc'> + <address type='usb' bus='0' port='2'/> + </redirdev> + <redirdev bus='usb' type='spicevmc'> + <address type='usb' bus='0' port='3'/> + </redirdev> + <watchdog model='itco' action='reset'/> + <memballoon model='virtio'> + <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> + </memballoon> + <rng model='virtio'> + <backend model='random'>/dev/urandom</backend> + <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> + </rng> + </devices> +</domain> +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2968 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2968 new file mode 100644 index 000000000..1b49d64bb --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2968 @@ -0,0 +1,22 @@ +Regression: x-igd-opregion=off ignored in VFIO IGD quirk handling +Description of problem: +A regression in QEMU’s VFIO IGD initialization causes the `x-igd-opregion=off` parameter to be ignored, resulting in an error when passing through an Intel iGPU SR-IOV Virtual Function (VF) at PCI address `00:02.1`: `qemu-system-x86_64: -device vfio-pci,host=0000:00:02.1,...: Device does not supports IGD OpRegion feature: No such device` +Automatic detection of IGD-OpRegion assumes any Intel iGPU (including GVT-g) will have it but SR-IOV VFs do not. +Steps to reproduce: +1. Configure an Intel iGPU with SR-IOV enabled, creating a VF at `00:02.1`. +2. Bind the VF to the `vfio-pci` driver: +``` + echo 0000:00:02.1 > /sys/bus/pci/drivers/i915/unbind + either: + echo "8086 4680" > /sys/bus/pci/drivers/vfio-pci/new_id + or: + echo 0000:00:02.1 > /sys/bus/pci/drivers/vfio-pci/bind +``` +3. Run QEMU with the command line above, including `-device vfio-pci,host=0000:00:02.1,...,x-igd-opregion=off`. +Additional information: +- **Hardware details**: + - `00:02.1 VGA compatible controller [0300]: Intel Corporation AlderLake-S GT1 [8086:4680] (rev 0c)` + - Host motherboard: MSI PRO Z690-A DDR4 + - CPU: Intel Core i5 12600K +- **Regression cause**: The issue was introduced by commit 7be29f2f1a3f5b037d27eedbd5df9f441e8c8c16, which changed `vfio_pci_igd_config_quirk` to detect OpRegion automatically, ignoring `vdev->igd_opregion=false`. +- **Proposed fix**: I have a patch that adds checks for `vdev->igd_opregion` in `vfio_pci_igd_config_quirk` and `vfio_pci_kvmgt_config_quirk`, skipping OpRegion handling when `x-igd-opregion=off`. The patch has been tested, confirming the VM starts without errors. I will submit it to qemu-devel@nongnu.org with a reference to this issue. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2969 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2969 new file mode 100644 index 000000000..ebe071dc1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2969 @@ -0,0 +1,212 @@ +Raspberry Pi 4 Model B Rev 1.5 ("raspi4b"): No keyboard input after booting; "raspi3b" works +Description of problem: +I am using a `non-root` setup. + +# +Steps to reproduce: +1. Install `latest` QEMU version from `Master branch`. As of writing commit hash `757a34115e7491744a63dfc3d291fd1de5297ee2`: +```bash +$ ACCEPT_KEYWORDS="**" \ +USE="qemu_softmmu_targets_aarch64 qemu_softmmu_targets_x86_64 qemu_user_targets_aarch64 qemu_user_targets_x86_64 -ncurses slirp spice virtfs aio alsa bzip2 curl dock fdt filecaps gnutls jpeg oss pam pin-upstream-blobs png pulseaudio python_targets_python3_12 python_targets_python3_13 seccomp slirp spice udev usb vhost-net virtfs vnc xattr zstd" \ +emerge --oneshot =app-emulation/qemu-9999 +``` + +All `USE flags` can be found [below](#use-flags-app-emulationqemu). + +2. Install `slirp4netns`, `libslirp` and `tigervnc`: +```bash +$ USE="-opengl -server" emerge --oneshot =app-containers/slirp4netns-1.2.0 =net-libs/libslirp-4.7.0 =net-misc/tigervnc-1.15.0 +``` + +All `USE flags` can be found [below](#use-flags-net-misctigervnc). + +3. Prepare directory structure in the `current working directory`: +```bash +$ mkdir "rpi3_model_b/" "rpi4_model_b_rev1.5/" +``` + +4. Download `DTB` and `Kernel image files` from the [`Raspberry Pi firmware Git repository`](https://github.com/raspberrypi/firmware/tree/0ea28740607daed588912930379ed6ad40cfc4be/boot): +```bash +$ wget "https://github.com/raspberrypi/firmware/raw/0ea28740607daed588912930379ed6ad40cfc4be/boot/bcm2710-rpi-3-b.dtb" \ + --output-document="./rpi3_model_b/bcm2710-rpi-3-b_from_master_branch_0ea28740607daed588912930379ed6ad40cfc4be.dtb" +$ wget "https://github.com/raspberrypi/firmware/raw/0ea28740607daed588912930379ed6ad40cfc4be/boot/bcm2711-rpi-4-b.dtb" \ + --output-document="./rpi4_model_b_rev1.5/bcm2711-rpi-4-b_from_master_branch_0ea28740607daed588912930379ed6ad40cfc4be.dtb" +$ wget "https://github.com/raspberrypi/firmware/raw/0ea28740607daed588912930379ed6ad40cfc4be/boot/kernel8.img" \ + --output-document="./kernel8_from_master_branch_0ea28740607daed588912930379ed6ad40cfc4be.img" +``` + +5. Download, verify and extract `Raspberry Pi OS Lite` image files: +```bash +$ wget \ + "https://downloads.raspberrypi.com/raspios_lite_arm64/images/raspios_lite_arm64-2024-11-19/2024-11-19-raspios-bookworm-arm64-lite.img.xz" \ + "https://downloads.raspberrypi.com/raspios_lite_arm64/images/raspios_lite_arm64-2024-11-19/2024-11-19-raspios-bookworm-arm64-lite.img.xz.sha256" \ + "https://downloads.raspberrypi.com/raspios_lite_arm64/images/raspios_lite_arm64-2024-11-19/2024-11-19-raspios-bookworm-arm64-lite.img.xz.sig" \ + "https://downloads.raspberrypi.com/raspios_lite_arm64/images/raspios_lite_arm64-2025-05-13/2025-05-13-raspios-bookworm-arm64-lite.img.xz" \ + "https://downloads.raspberrypi.com/raspios_lite_arm64/images/raspios_lite_arm64-2025-05-13/2025-05-13-raspios-bookworm-arm64-lite.img.xz.sha256" \ + "https://downloads.raspberrypi.com/raspios_lite_arm64/images/raspios_lite_arm64-2025-05-13/2025-05-13-raspios-bookworm-arm64-lite.img.xz.sig" +$ sha256sum --check *.sha256 +2024-11-19-raspios-bookworm-arm64-lite.img.xz: OK +2025-05-13-raspios-bookworm-arm64-lite.img.xz: OK +$ for i in *.sig; do echo "${i}"; gpg --verify "${i}" "${i%\.sig}"; done +2024-11-19-raspios-bookworm-arm64-lite.img.xz.sig +gpg: Signature made Tue Nov 19 15:51:51 2024 CET +gpg: using RSA key 54C3DD610D9D1B4AF82A37758738CD6B956F460C +gpg: Good signature from "Raspberry Pi Downloads Signing Key" [full] +2025-05-13-raspios-bookworm-arm64-lite.img.xz.sig +gpg: Signature made Tue May 13 08:52:21 2025 CEST +gpg: using RSA key 54C3DD610D9D1B4AF82A37758738CD6B956F460C +gpg: Good signature from "Raspberry Pi Downloads Signing Key" [full] +$ for i in *.xz; do pixz -d "${i}"; done +$ LS_COLORS="" tree -FC --noreport +./ +├── 2024-11-19-raspios-bookworm-arm64-lite.img.xz.sha256 +├── 2024-11-19-raspios-bookworm-arm64-lite.img.xz.sig +├── 2024-11-19-raspios-bookworm-arm64-lite.img +├── 2025-05-13-raspios-bookworm-arm64-lite.img.xz.sha256 +├── 2025-05-13-raspios-bookworm-arm64-lite.img.xz.sig +├── 2025-05-13-raspios-bookworm-arm64-lite.img +├── kernel8_from_master_branch_0ea28740607daed588912930379ed6ad40cfc4be.img +├── rpi3_model_b/ +│ ├── bcm2710-rpi-3-b_from_master_branch_0ea28740607daed588912930379ed6ad40cfc4be.dtb +└── rpi4_model_b_rev1.5/ + └── bcm2711-rpi-4-b_from_master_branch_0ea28740607daed588912930379ed6ad40cfc4be.dtb +``` + +6. Grow `image size` to make it be a `power of 2`: +```bash +$ qemu-img resize -f raw "./2024-11-19-raspios-bookworm-arm64-lite.img" 4G +Image resized. +$ qemu-img resize -f raw "./2025-05-13-raspios-bookworm-arm64-lite.img" 4G +Image resized. +``` + +7. Get `DTB` and `Kernel images files` from the `Raspberry Pi OS image files`, prepare a `user` and `SSHD`: +```bash +$ losetup --find --partscan --show "./2024-11-19-raspios-bookworm-arm64-lite.img" +/dev/loop0 +$ mount "/dev/loop0p1" "/mnt/" +$ cp "/mnt/bcm2710-rpi-3-b.dtb" "./rpi3_model_b/bcm2710-rpi-3-b_2024-11-19.dtb" +$ cp "/mnt/bcm2711-rpi-4-b.dtb" "./rpi4_model_b_rev1.5/bcm2711-rpi-4-b_2024-11-19.dtb" +$ cp "/mnt/kernel8.img" "./kernel8_2024-11-19.img" +$ touch "/mnt/ssh" +$ echo "pi:$(openssl passwd -6)" > "/mnt/userconf" +Password: 1234 +Verifying - Password: 1234 +$ umount "/mnt/" +$ losetup --find --partscan --show "./2025-05-13-raspios-bookworm-arm64-lite.img" +/dev/loop1 +$ mount "/dev/loop1p1" "/mnt/" +$ cp "/mnt/bcm2710-rpi-3-b.dtb" "./rpi3_model_b/bcm2710-rpi-3-b_2025-05-13.dtb" +$ cp "/mnt/bcm2711-rpi-4-b.dtb" "./rpi4_model_b_rev1.5/bcm2711-rpi-4-b_2025-05-13.dtb" +$ cp "/mnt/kernel8.img" "./kernel8_2025-05-13.img" +$ touch "/mnt/ssh" +$ echo "pi:$(openssl passwd -6)" > "/mnt/userconf" +Password: 1234 +Verifying - Password: 1234 +$ umount "/mnt/" +$ losetup --list +NAME SIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE DIO LOG-SEC +/dev/loop1 0 0 0 0 /home/<some_username>/qemu/2025-05-13-raspios-bookworm-arm64-lite.img 0 512 +/dev/loop0 0 0 0 0 /home/<some_username>/qemu/2024-11-19-raspios-bookworm-arm64-lite.img 0 512 +$ losetup --detach "/dev/loop0" "/dev/loop1" +$ losetup --list +$ LS_COLORS="" tree -FC --noreport +./ +├── 2024-11-19-raspios-bookworm-arm64-lite.img +├── 2024-11-19-raspios-bookworm-arm64-lite.img.xz.sha256 +├── 2024-11-19-raspios-bookworm-arm64-lite.img.xz.sig +├── 2025-05-13-raspios-bookworm-arm64-lite.img +├── 2025-05-13-raspios-bookworm-arm64-lite.img.xz.sha256 +├── 2025-05-13-raspios-bookworm-arm64-lite.img.xz.sig +├── kernel8_2024-11-19.img +├── kernel8_2025-05-13.img +├── kernel8_from_master_branch_0ea28740607daed588912930379ed6ad40cfc4be.img +├── rpi3_model_b/ +│ ├── bcm2710-rpi-3-b_2024-11-19.dtb +│ ├── bcm2710-rpi-3-b_2025-05-13.dtb +│ ├── bcm2710-rpi-3-b_from_master_branch_0ea28740607daed588912930379ed6ad40cfc4be.dtb +└── rpi4_model_b_rev1.5/ + ├── bcm2711-rpi-4-b_2024-11-19.dtb + ├── bcm2711-rpi-4-b_2025-05-13.dtb + └── bcm2711-rpi-4-b_from_master_branch_0ea28740607daed588912930379ed6ad40cfc4be.dtb +``` + +8. Execute the first `qemu-system-aarch64` command at `QEMU command line` [above](#host-environment): +```bash +$ qemu-system-aarch64 \ + -vnc "unix:/run/user/$(id --user)/qemu-vnc.sock" + [...] +``` + +8.1. Warnings will be returned: + +`raspi4b`: +```no-highlight +qemu-system-aarch64: warning: bcm2711 dtc: brcm,bcm2711-pcie has been disabled! +qemu-system-aarch64: warning: bcm2711 dtc: brcm,bcm2711-rng200 has been disabled! +qemu-system-aarch64: warning: bcm2711 dtc: brcm,bcm2711-thermal has been disabled! +qemu-system-aarch64: warning: bcm2711 dtc: brcm,bcm2711-genet-v5 has been disabled! +``` + +`raspi3b`: +```no-highlight +usbnet: failed control transaction: request 0x8006 value 0x600 index 0x0 length 0xa +usbnet: failed control transaction: request 0x8006 value 0x600 index 0x0 length 0xa +usbnet: failed control transaction: request 0x8006 value 0x600 index 0x0 length 0xa +``` + +9. Connect via `VNC` via `UNIX socket`: +```bash +$ vncviewer "/run/user/$(id --user)/qemu-vnc.sock" +``` + +10. Press and hold the `f key` or `right arrow` in the `tigervnc window`, even while booting. There should be **no** characters at all. For `raspi3b` there will be. + +11. Open the `QEMU console` via `CTRL+ALT+2`. + +11.1. Try to send a `reboot command`: +```bash +> sendkey ctrl-alt-delete +``` + +11.2. `Raspberry Pi OS` will **not** reboot or receive any keyboard inputs, but `raspi3b` will. + +12. Try to connect via `SSH` from `another shell`: +```bash +$ ssh -p 2222 pi@127.0.0.1 +``` + +12.1. The connection will time out: +```no-highlight +Connection timed out during banner exchange +Connection to 127.0.0.1 port 2222 timed out +``` + +12.2. `slirp4netns` will continuously return errors in the shell, where `qemu-system-aarch64` was executed: +```no-highlight +[...] +qemu-system-aarch64: Slirp: Failed to send packet, ret: -1 +qemu-system-aarch64: Slirp: Failed to send packet, ret: -1 +[...] +``` + +13. Go to the shell, where `qemu-system-aarch64` was executed and send a `SIGTERM (15)` signal to the process: +```no-highlight +Press CTRL+C +``` + +13.1. If this does not work, `terminate` the process form `another shell`: +```bash +$ ps aux | grep "qemu-system-aarch64" +<some_username> 24399 149 3.1 4265780 522276 pts/2 SNl+ 21:32 4:21 qemu-system-aarch64 -vnc unix:/run/user/[...] +$ kill -SIGTERM 24399 +``` + +13.2. In the worst case, `kill` the process in a dirty way: +```bash +$ kill -SIGKILL 24339 +``` + +14. Repeat step `8` to `13` with the next `qemu-system-aarch64` command at `QEMU command line` [above](#host-environment). `Keyboard inputs` will only work for `raspi3` and `SSH` only for number `4` and `6`. If keyboard inputs are possible, one can log in with the user `pi` and password `1234` or use the `QEMU console` (`CTRL+ALT+2`) to reboot: `sendkey ctrl-alt-delete`. +Additional information: +# diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/297 b/gitlab/issues_text/target_missing/host_missing/accel_missing/297 new file mode 100644 index 000000000..0300dc8f0 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/297 @@ -0,0 +1 @@ +SD card size constraint conceptually wrong diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2970 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2970 new file mode 100644 index 000000000..67940962b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2970 @@ -0,0 +1 @@ +qemu version 10.0.0 fails to build with clang-21 (current trunk) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2971 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2971 new file mode 100644 index 000000000..6706be6f5 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2971 @@ -0,0 +1,44 @@ +loongarch64 crashes caused by lenient instruction decoding of vldi and xvldi +Description of problem: +Lenient instruction decoding of `vldi` and `xvldi` leads to Qemu crashes. + +The decoding of `vldi` and `xvldi` instruction allows for instructions with illegal immediates. + +`target/loongarch/insns.decode`: + +``` +vldi 0111 00111110 00 ............. ..... @v_i13 +xvldi 0111 01111110 00 ............. ..... @v_i13 +``` + +This is considered in `target/loongarch/tcg/insn_trans/trans_vec.c.inc`: + +```C + /* + * imm bit [11:8] is mode, mode value is 0-12. + * other values are invalid. + */ +``` + +However, an assertion error is raised when this condition is violated and qemu crashes: + +``` +** +ERROR:target/loongarch/insn_trans/trans_vec.c.inc:3574:vldi_get_value: code should not be reached +Bail out! ERROR:target/loongarch/insn_trans/trans_vec.c.inc:3574:vldi_get_value: code should not be reached +``` + +On hardware (Loongson 3A5000), these instructions cause a SIGILL. +Steps to reproduce: +1. compile the `test_inv_vldi` test program for loongarch64 (see additional information) +2. run `qemu-loongarch64-static ./test_inv_vldi` +Additional information: +I will post a patch for this issue to the mailing list soon. + +`test_inv_vldi` source code: + +```C +int main(int argc, char** argv) { + asm volatile(".4byte 0x73e3a000"); +} +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2972 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2972 new file mode 100644 index 000000000..e92fadc03 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2972 @@ -0,0 +1,637 @@ +loongarch64 inconsistencies between hardware and qemu due too lenient decoding of floating point comparisons +Description of problem: +(Related to #2971 ) + +Lenient instruction decoding of floating point comparisons leads to instructions that do not exist on hardware (Loongson 3A5000). + +The decoding of floating point compare instruction allows for instructions with illegal fcmp modes. + +The following are affected (`target/loongarch/insns.decode`): + +``` +vfcmp_cond_s 0000 11000101 ..... ..... ..... ..... @vvv_fcond +vfcmp_cond_d 0000 11000110 ..... ..... ..... ..... @vvv_fcond +xvfcmp_cond_s 0000 11001001 ..... ..... ..... ..... @vvv_fcond +xvfcmp_cond_d 0000 11001010 ..... ..... ..... ..... @vvv_fcond +fcmp_cond_s 0000 11000001 ..... ..... ..... 00 ... @cff_fcond +fcmp_cond_d 0000 11000010 ..... ..... ..... 00 ... @cff_fcond +``` + +The `get_fcmp_flags` function in `target/loongarch/tcg/insn_trans/trans_fcmp.c.inc` allows decoding all possible 4-bit condition values even though some are invalid on hardware (Loongson 3A5000): + +<details><summary>qemu-loongarch64-static</summary> + +``` + --- fcond = 0b0 () --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b1 () --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b10 (LT) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b11 (LT) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b100 (EQ) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b101 (EQ) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b110 (LT | EQ) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b111 (LT | EQ) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b1000 (UN) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b1001 (UN) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b1010 (LT | UN) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b1011 (LT | UN) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b1100 (EQ | UN) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b1101 (EQ | UN) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b1110 (LT | EQ | UN) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b1111 (LT | EQ | UN) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b10000 (LT | GT) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b10001 (LT | GT) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b10010 (LT | LT | GT) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b10011 (LT | LT | GT) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b10100 (EQ | LT | GT) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b10101 (EQ | LT | GT) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b10110 (LT | EQ | LT | GT) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b10111 (LT | EQ | LT | GT) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b11000 (UN | LT | GT) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b11001 (UN | LT | GT) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b11010 (LT | UN | LT | GT) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b11011 (LT | UN | LT | GT) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b11100 (EQ | UN | LT | GT) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b11101 (EQ | UN | LT | GT) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b11110 (LT | EQ | UN | LT | GT) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b11111 (LT | EQ | UN | LT | GT) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True +``` + +</details> + + +<details><summary>Loongson 3A5000</summary> + +``` + --- fcond = 0b0 () --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b1 () --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b10 (LT) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b11 (LT) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b100 (EQ) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b101 (EQ) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b110 (LT | EQ) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b111 (LT | EQ) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b1000 (UN) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b1001 (UN) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b1010 (LT | UN) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b1011 (LT | UN) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b1100 (EQ | UN) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b1101 (EQ | UN) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b1110 (LT | EQ | UN) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b1111 (LT | EQ | UN) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b10000 (LT | GT) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b10001 (LT | GT) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b10010 (LT | LT | GT) --- +vfcmp_cond_s False +vfcmp_cond_d False +xvfcmp_cond_s False +xvfcmp_cond_d False +fcmp_cond_s False +fcmp_cond_d False + + --- fcond = 0b10011 (LT | LT | GT) --- +vfcmp_cond_s False +vfcmp_cond_d False +xvfcmp_cond_s False +xvfcmp_cond_d False +fcmp_cond_s False +fcmp_cond_d False + + --- fcond = 0b10100 (EQ | LT | GT) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b10101 (EQ | LT | GT) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b10110 (LT | EQ | LT | GT) --- +vfcmp_cond_s False +vfcmp_cond_d False +xvfcmp_cond_s False +xvfcmp_cond_d False +fcmp_cond_s False +fcmp_cond_d False + + --- fcond = 0b10111 (LT | EQ | LT | GT) --- +vfcmp_cond_s False +vfcmp_cond_d False +xvfcmp_cond_s False +xvfcmp_cond_d False +fcmp_cond_s False +fcmp_cond_d False + + --- fcond = 0b11000 (UN | LT | GT) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b11001 (UN | LT | GT) --- +vfcmp_cond_s True +vfcmp_cond_d True +xvfcmp_cond_s True +xvfcmp_cond_d True +fcmp_cond_s True +fcmp_cond_d True + + --- fcond = 0b11010 (LT | UN | LT | GT) --- +vfcmp_cond_s False +vfcmp_cond_d False +xvfcmp_cond_s False +xvfcmp_cond_d False +fcmp_cond_s False +fcmp_cond_d False + + --- fcond = 0b11011 (LT | UN | LT | GT) --- +vfcmp_cond_s False +vfcmp_cond_d False +xvfcmp_cond_s False +xvfcmp_cond_d False +fcmp_cond_s False +fcmp_cond_d False + + --- fcond = 0b11100 (EQ | UN | LT | GT) --- +vfcmp_cond_s False +vfcmp_cond_d False +xvfcmp_cond_s False +xvfcmp_cond_d False +fcmp_cond_s False +fcmp_cond_d False + + --- fcond = 0b11101 (EQ | UN | LT | GT) --- +vfcmp_cond_s False +vfcmp_cond_d False +xvfcmp_cond_s False +xvfcmp_cond_d False +fcmp_cond_s False +fcmp_cond_d False + + --- fcond = 0b11110 (LT | EQ | UN | LT | GT) --- +vfcmp_cond_s False +vfcmp_cond_d False +xvfcmp_cond_s False +xvfcmp_cond_d False +fcmp_cond_s False +fcmp_cond_d False + + --- fcond = 0b11111 (LT | EQ | UN | LT | GT) --- +vfcmp_cond_s False +vfcmp_cond_d False +xvfcmp_cond_s False +xvfcmp_cond_d False +fcmp_cond_s False +fcmp_cond_d False +``` + +</details> +Steps to reproduce: +1. compile the `test_instr_valid` test program for loongarch64 (see additional information). +2. run the `check_defined.py` python script to print out information about defined instructions. +3. All tested fcmp instructions are defined when run using qemu, but some are invalid (SIGILL) on actual hardware. +Additional information: +I will post a patch for this issue to the mailing list soon. + +`test_instr_valid` source code: + +```C +#include <signal.h> +#include <errno.h> +#include <stdio.h> +#include <stddef.h> +#include <stdint.h> +#include <stdlib.h> +#include <sys/mman.h> + +#define PAGE_SIZE 0x4000 + +#define ret 0x4c000020 + +typedef void (*instr_fun)(void); + +static __attribute__((aligned(PAGE_SIZE))) uint32_t code[PAGE_SIZE / sizeof(uint32_t)]; + +void handler(int signo, siginfo_t *info, void *context) { + printf("False"); + exit(0); +} + +int main(int argc, char** argv) { + struct sigaction act = { 0 }; + act.sa_flags = SA_SIGINFO | SA_ONSTACK; + act.sa_sigaction = &handler; + sigaction(SIGILL, &act, NULL); + uint32_t instr = (uint32_t)strtoull(argv[1], NULL, 0); + code[0] = instr; + code[1] = ret; + mprotect(code, sizeof(code), PROT_READ | PROT_EXEC); + instr_fun f = (instr_fun)(void*)code; + f(); + printf("True"); + exit(0); +} +``` + +`check_defined.py`: + +```py +import subprocess + +CMD = ["qemu-loongarch64-static", "./test_instr_valid"] # remove "qemu-loongarch64-static" when running without emulation + +def is_defined(instr): + try: + return eval(subprocess.check_output(CMD + [hex(instr)]).decode()) + except: + return False + +bases = [ + ("vfcmp_cond_s ", 0b00001100010100000000000000000000), # vfcmp_cond_s 0000 11000101 ..... ..... ..... ..... @vvv_fcond + ("vfcmp_cond_d ", 0b00001100011000000000000000000000), # vfcmp_cond_d 0000 11000110 ..... ..... ..... ..... @vvv_fcond + ("xvfcmp_cond_s", 0b00001100100100000000000000000000), # xvfcmp_cond_s 0000 11001001 ..... ..... ..... ..... @vvv_fcond + ("xvfcmp_cond_d", 0b00001100101000000000000000000000), # xvfcmp_cond_d 0000 11001010 ..... ..... ..... ..... @vvv_fcond +] + +bases_2 = [ + ("fcmp_cond_s ", 0b00001100000100000000000000000000), # fcmp_cond_s 0000 11000001 ..... ..... ..... 00 ... @cff_fcond + ("fcmp_cond_d ", 0b00001100001000000000000000000000), # fcmp_cond_d 0000 11000010 ..... ..... ..... 00 ... @cff_fcond +] + +def format_fcond(val): + x = ["LT", "EQ", "UN", "LT | GT"] + return " | ".join(x[i] for i in range(4) if (val >> 1) & (1 << i)) + +fcond_shift = 15 + +# use r1, r2, r3 for vector instructions +reg_mask = 0b000110001000001 + +# use c0, r1, r2 for normal instructions +reg_mask_2 = 0b000100000100000 + +for fcond in range(1 << 5): + print(f" --- fcond = {bin(fcond)} ({format_fcond(fcond)}) --- ") + for name, mask in bases: + print(name, is_defined(mask | reg_mask | (fcond << fcond_shift))) + for name, mask in bases_2: + print(name, is_defined(mask | reg_mask_2 | (fcond << fcond_shift))) + print("") +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2974 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2974 new file mode 100644 index 000000000..1fe6ae545 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2974 @@ -0,0 +1 @@ +Remove the "51 Franklin Street, Fifth Floor, Boston" from the QEMU code base diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2975 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2975 new file mode 100644 index 000000000..a4e1a1802 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2975 @@ -0,0 +1,68 @@ +qemu-system-x86_64: VFIO_MAP_DMA failed: -22 IVSHMEM +Description of problem: +QEMU do not run with looking glass KVMFR and with host model cpu +It only works when I set cpu to `Snowridge,vmx=on,fma=on,avx=on,f16c=on,hypervisor=on...` (you can see in kvm.sh) +Steps to reproduce: +1. I have a script ( search for 'WITH VFIO') +Additional information: +UPD +Some additional debug info from GDB + +``` +=== vfio_listener_region_add === +Arguments: +listener = 0x55555a4dd2f0 +section = 0x7fffedb389c0 + +Section details: + section->offset_within_address_space: 0x382000000000 + Memory region: 0x555558120dd0 + Memory region name: shmmem-shmem0 + Memory region size: 0x10000000 + Memory region addr: 0x382000000000 +Error accessing section details: There is no member named offset. + +=== vfio_get_section_iova_range ENTRY === +Arguments: +bcontainer = 0x55555a4dd2c0 +section = 0x7fffedb389c0 +out_iova = 0x7fffedb388b0 +out_end = 0x7fffedb388b8 +out_llend = 0x7fffedb38900 + +Local variables at entry: +llend = 140737181354144 +iova = 140737181354432 + +Thread 4 "CPU 0/KVM" hit Breakpoint -96, 0x0000555555b8511a in vfio_listener_region_add (listener=0x55555a4dd2f0, + section=0x7fffedb389c0) at ../../../hw/vfio/listener.c:467 +467 if (!vfio_get_section_iova_range(bcontainer, section, &iova, &end, +(gdb) +Continuing. +2025-05-20T22:46:27.819893Z qemu-system-x86_64: vfio_container_dma_map(0x55555a4dd2c0, 0x382000000000, 0x10000000, 0x7fffcffff000) = -22 (Invalid argument) +qemu: hardware error: vfio: DMA mapping failed, unable to continue +CPU #0: +RAX=00000000e0000000 RBX=00000000e0608004 RCX=0000000000608004 RDX=0000000000000003 +RSI=0000000000000003 RDI=0000000000000000 RBP=000000007ef6b640 RSP=000000007ef6b5f0 +R8 =0000000000000000 R9 =000000007ef6b70f R10=0000000000000000 R11=0000000000000004 +R12=000000007ef6b800 R13=0000000000000003 R14=0000000000000000 R15=000000007ef6b7fe +RIP=000000007e1fe2eb RFL=00000246 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0 + +``` + +Tested with latest QEMU 2af4a82ab2cce3412ffc92cd4c96bd870e33bc8e same error +``` +sudo dnf builddep qemu +../../../configure --enable-debug +``` + +[ERROR-QEMU-GIT-2af4a82ab2cce3412ffc92cd4c96bd870e33bc8e.txt](/uploads/060b26f091f0391f0491ea91dbe78f6d/ERROR-QEMU-GIT-2af4a82ab2cce3412ffc92cd4c96bd870e33bc8e.txt) + +[ERROR-trace-iova-values.txt](/uploads/22cacf4a5cb2c91ff6375c792a25dde1/ERROR-trace-iova-values.txt) + +[WORKINg-trace-iova-values.txt](/uploads/d4d53c2e743cf5f2d5bf810d61b9f1e6/WORKINg-trace-iova-values.txt) + + +[kvm.log.txt](/uploads/ac31eebf6e63aa6abe2498d1a4064bef/kvm.log.txt) + +[kvm.sh](/uploads/7f656f7cf0d623a240309ee61b024dc9/kvm.sh) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2976 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2976 new file mode 100644 index 000000000..0473acdf8 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2976 @@ -0,0 +1,25 @@ +attach-ns doesn't work correctly in SR-IOV, cannot attach NS to VF if it is attached to a PF +Description of problem: +We can't attach namespace to a VF (Secondary controller) unless it is not attached to a primary controller first + +Lately in the commit https://github.com/qemu/qemu/commit/6ccca4b6bb9f994cc04e71004e1767a3476d2b23 the file qemu/hw/nvme/ctrl.c got changed -\> in function "nvme_ns_attachment" -\> line 6819 (At the time I'm writing the bug) which is the condation in attach ns to check if the namespace is attached "`if (nvme_ns(n, nsid)) {`" + +This change will always result in checking the namespace attach to the PF even if we are trying to attach it to the VF. +Steps to reproduce: +1. Enable a VF: + +``` +echo 1 > /sys/bus/pci/devices/0000:01:00.0/reset +sleep 1 + +echo 2 > /sys/bus/pci/devices/0000:01:00.0/sriov_numvfs +sleep 1 + +nvme virt-mgmt /dev/nvme0 -c 1 -r 1 -a 8 -n 1 +nvme virt-mgmt /dev/nvme0 -c 1 -r 0 -a 8 -n 2 +nvme virt-mgmt /dev/nvme0 -c 1 -a 9 +sleep 1 +``` + +2. attach namespace 1 to the PF (e.g. `vme attach-ns /dev/nvme0 -n1 -c0` ) +3. try to attach it using the nvme_cli command from the PF (e.g. `nvme attach-ns /dev/nvme0 -n1 -c1`) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2977 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2977 new file mode 100644 index 000000000..63545e09f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2977 @@ -0,0 +1,11 @@ +QEMU SVM VMCB exit_code is uint32_t when AMD spec requires uint64_t +Description of problem: +QEMU's SVM implementation incorrectly uses a 32-bit parameter for the exit code in the `cpu_vmexit` function, despite the AMD SVM specification requiring a 64-bit exit code field in the VMCB (Virtual Machine Control Block). + +I think the issue is in `target/i386/svm.c` in the `cpu_vmexit` function. + +The `exit_code` parameter is declared as `uint32_t` but should be `uint64_t` according to the AMD SVM specification. This causes exit codes to be truncated to 32 bits, resulting in values like 0xffff_ffff instead of the expected 0xffff_ffff_ffff_ffff. +Steps to reproduce: + +Additional information: +[this](https://stackoverflow.com/questions/79632531/qemu-svm-vmcb-exit-code-is-uint32-t-when-amd-spec-requires-uint64-t?noredirect=1#comment140448815_79632531) question I posted on stack overflow diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2978 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2978 new file mode 100644 index 000000000..d9f9aa712 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2978 @@ -0,0 +1,23 @@ +Qemu assertion issue +Description of problem: +This issue is **not caused by my OS**, as it runs perfectly under VMware and other emulators. + +However, when using QEMU, the emulator sometimes randomly **crashes or aborts** during boot or early execution. The crash is **inconsistent** — sometimes it runs, sometimes it fails immediately. + +QEMU fails with an **assertion failure** in `qemu_mutex_lock_iothread_impl` +Steps to reproduce: +Unfortunately, I do not know exactly what causes this issue. It may be specific to my system or configuration. + +1. +2. +Additional information: +Qemu stdout: + +``` +ERROR:system/cpus.c:504:qemu_mutex_lock_iothread_impl: assertion failed: (!qemu_mutex_iothread_locked()) Bail out! ERROR:system/cpus.c:504:qemu_mutex_lock_iothread_impl: assertion failed: (!qemu_mutex_iothread_locked()) ./run: line 3: 3544 Aborted (core dumped) +``` + +Command line: +``` + qemu-system-x86_64 -debugcon file:OxizeOS.log -drive file=output/OxizeOS.hdd,format=raw -serial stdio +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/298 b/gitlab/issues_text/target_missing/host_missing/accel_missing/298 new file mode 100644 index 000000000..fa9e80d41 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/298 @@ -0,0 +1 @@ +OpenGL, Virtio-VGA, Virtio-GPU-PCI, GTK diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2980 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2980 new file mode 100644 index 000000000..2ad3f471c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2980 @@ -0,0 +1,264 @@ +QEMU Crashes During Snapshot: bdrv_co_write_req_prepare Assertion child->perm & BLK_PERM_WRITE Failed +Description of problem: +After taking a external snapshot (w/ memory state) with libvirt, the QEMU process crashed with an assertion + +``` +qemu-system-x86_64: ../block/io.c:2052: bdrv_co_write_req_prepare: Assertion `child->perm & BLK_PERM_WRITE` failed. +``` +Steps to reproduce: +1. Start the qemu process +2. Take an external (w/ memory) snapshot by libvirt Python API + + ```python + domain.snapshotCreateXML(<xml_string>, + libvirt.VIR_DOMAIN_SNAPSHOT_CREATE_ATOMIC | + libvirt.VIR_DOMAIN_SNAPSHOT_CREATE_REUSE_EXT | + libvirt.VIR_DOMAIN_SNAPSHOT_CREATE_LIVE) + ``` + +3. The qemu process crashed by hitting the assertion +Additional information: +Libvirt domain XML +```xml +<domain type='kvm'> + <name>1a3dabc5-c33b-4308-acc5-2245f3b64163</name> + <uuid>1a3dabc5-c33b-4308-acc5-2245f3b64163</uuid> + <metadata xmlns:qvs="http://www.qnap.com/schemas/qvs/1.0"> + </metadata> + <memory unit='KiB'>16777216</memory> + <currentMemory unit='KiB'>16777216</currentMemory> + <memoryBacking> + <nosharepages/> + </memoryBacking> + <vcpu placement='static' cpuset='0-23'>5</vcpu> + <sysinfo type='smbios'> + <system> + <entry name='manufacturer'>qemu</entry> + <entry name='product'>qemu</entry> + </system> + </sysinfo> + <os> + <type arch='x86_64' machine='pc-i440fx-7.0'>hvm</type> + <boot dev='cdrom'/> + <boot dev='hd'/> + <bootmenu enable='no'/> + <smbios mode='sysinfo'/> + </os> + <features> + <acpi/> + <apic/> + <pae/> + </features> + <cpu mode='host-passthrough' check='none' migratable='on'> + <topology sockets='1' dies='1' cores='5' threads='1'/> + <numa> + <cell id='0' cpus='0-4' memory='16777216' unit='KiB' memAccess='private'/> + </numa> + </cpu> + <clock offset='localtime'/> + <on_poweroff>destroy</on_poweroff> + <on_reboot>restart</on_reboot> + <on_crash>restart</on_crash> + <pm> + <suspend-to-mem enabled='no'/> + <suspend-to-disk enabled='no'/> + </pm> + <devices> + <emulator>/QVS/usr/bin/qemu-system-x86_64</emulator> + <disk type='file' device='disk'> + <driver name='qemu' type='qcow2' cache='writeback'/> + <source file='/share/Virtualization Main/Win 10 x64 - Home VM/Win 10 x64 - Home VM_00.1747803601' startupPolicy='optional'/> + <backingStore type='file'> + <format type='qcow2'/> + <source file='/share/Virtualization Main/Win 10 x64 - Home VM/Win 10 x64 - Home VM_00.1747630800'/> + <backingStore type='file'> + <format type='qcow2'/> + <source file='/share/Virtualization Main/Win 10 x64 - Home VM/Win 10 x64 - Home VM_00.1747371601'/> + <backingStore type='file'> + <format type='qcow2'/> + <source file='/share/Virtualization Main/Win 10 x64 - Home VM/Win 10 x64 - Home VM_00.1747198801'/> + <backingStore type='file'> + <format type='qcow2'/> + <source file='/share/Virtualization Main/Win 10 x64 - Home VM/Win 10 x64 - Home VM_00.1747026001'/> + <backingStore type='file'> + <format type='qcow2'/> + <source file='/share/Virtualization Main/Win 10 x64 - Home VM/Win 10 x64 - Home VM_00.1746594001'/> + <backingStore type='file'> + <format type='qcow2'/> + <source file='/share/Virtualization Main/Win 10 x64 - Home VM/Win 10 x64 - Home VM_00.1746421201'/> + <backingStore type='file'> + <format type='qcow2'/> + <source file='/share/Virtualization Main/Win 10 x64 - Home VM/Win 10 x64 - Home VM_00.1745557200'/> + <backingStore type='file'> + <format type='qcow2'/> + <source file='/share/Virtualization Main/Win 10 x64 - Home VM/Win 10 x64 - Home VM_00.1745211600'/> + <backingStore type='file'> + <format type='qcow2'/> + <source file='/share/Virtualization Main/Win 10 x64 - Home VM/Win 10 x64 - Home VM_00.1744174801'/> + <backingStore type='file'> + <format type='qcow2'/> + <source file='/share/Virtualization Main/Win 10 x64 - Home VM/Win 10 x64 - Home VM_00.1743570001'/> + <backingStore type='file'> + <format type='qcow2'/> + <source file='/share/Virtualization Main/Win 10 x64 - Home VM/Win 10 x64 - Home VM_00.1743138001'/> + <backingStore type='file'> + <format type='qcow2'/> + <source file='/share/Virtualization Main/Win 10 x64 - Home VM/Win 10 x64 - Home VM_00.1742965201'/> + <backingStore type='file'> + <format type='qcow2'/> + <source file='/share/Virtualization Main/Win 10 x64 - Home VM/Win 10 x64 - Home VM_00.1742360400'/> + <backingStore type='file'> + <format type='qcow2'/> + <source file='/share/Virtualization Main/Win 10 x64 - Home VM/Win 10 x64 - Home VM_00.1742187600'/> + <backingStore type='file'> + <format type='qcow2'/> + <source file='/share/Virtualization Main/Win 10 x64 - Home VM/Win 10 x64 - Home VM_00.1741928400'/> + <backingStore type='file'> + <format type='qcow2'/> + <source file='/share/Virtualization Main/Win 10 x64 - Home VM/Win 10 x64 - Home VM_00.1741755601'/> + <backingStore type='file'> + <format type='qcow2'/> + <source file='/share/Virtualization Main/Win 10 x64 - Home VM/Win 10 x64 - Home VM_00.1741323600'/> + <backingStore type='file'> + <format type='qcow2'/> + <source file='/share/Virtualization Main/Win 10 x64 - Home VM/Win 10 x64 - Home VM_00.1740718800'/> + <backingStore type='file'> + <format type='qcow2'/> + <source file='/share/Virtualization Main/Win 10 x64 - Home VM/Win 10 x64 - Home VM_00.1740546000'/> + <backingStore type='file'> + <format type='qcow2'/> + <source file='/share/Virtualization Main/Win 10 x64 - Home VM/Win 10 x64 - Home VM_00.1740373200'/> + <backingStore type='file'> + <format type='qcow2'/> + <source file='/share/Virtualization Main/Win 10 x64 - Home VM/Win 10 x64 - Home VM_00.1740114000'/> + <backingStore type='file'> + <format type='qcow2'/> + <source file='/share/Virtualization Main/Win 10 x64 - Home VM/Win 10 x64 - Home VM_00.1739941201'/> + <backingStore type='file'> + <format type='qcow2'/> + <source file='/share/Virtualization Main/Win 10 x64 - Home VM/Win 10 x64 - Home VM_00.1739768400'/> + <backingStore type='file'> + <format type='qcow2'/> + <source file='/share/Virtualization Main/Win 10 x64 - Home VM/Win 10 x64 - Home VM_00.1739509200'/> + <backingStore type='file'> + <format type='qcow2'/> + <source file='/share/Virtualization Main/Win 10 x64 - Home VM/Win 10 x64 - Home VM_00.1739336400'/> + <backingStore type='file'> + <format type='qcow2'/> + <source file='/share/Virtualization Main/Win 10 x64 - Home VM/Win 10 x64 - Home VM_00.1739163600'/> + <backingStore type='file'> + <format type='qcow2'/> + <source file='/share/Virtualization Main/Win 10 x64 - Home VM/Win 10 x64 - Home VM_00.1738904400'/> + <backingStore type='file'> + <format type='qcow2'/> + <source file='/share/Virtualization Main/Win 10 x64 - Home VM/Win 10 x64 - Home VM_00.1738558801'/> + <backingStore type='file'> + <format type='qcow2'/> + <source file='/share/Virtualization Main/Win 10 x64 - Home VM/Win 10 x64 - Home VM_00.1724816945'/> + <backingStore type='file'> + <format type='qcow2'/> + <source file='/share/Virtualization Main/Win 10 x64 - Home VM/Win 10 x64 - Home VM_00.1724045214_1'/> + <backingStore type='file'> + <format type='qcow2'/> + <source file='/share/Virtualization Main/Win 10 x64 - Home VM/Win 10 x64 - Home VM_00.1721622169'/> + <backingStore type='file'> + <format type='qcow2'/> + <source file='/share/Virtualization Main/Win 10 x64 - Home VM/Win 10 x64 - Home VM_00.img'/> + <backingStore/> + </backingStore> + </backingStore> + </backingStore> + </backingStore> + </backingStore> + </backingStore> + </backingStore> + </backingStore> + </backingStore> + </backingStore> + </backingStore> + </backingStore> + </backingStore> + </backingStore> + </backingStore> + </backingStore> + </backingStore> + </backingStore> + </backingStore> + </backingStore> + </backingStore> + </backingStore> + </backingStore> + </backingStore> + </backingStore> + </backingStore> + </backingStore> + </backingStore> + </backingStore> + </backingStore> + </backingStore> + </backingStore> + <target dev='vdb' bus='virtio'/> + <serial>1a3dabc5c33b4308ac01</serial> + <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> + </disk> + <disk type='file' device='cdrom'> + <driver name='qemu' type='raw'/> + <source startupPolicy='optional'/> + <target dev='hda' bus='ide'/> + <readonly/> + <address type='drive' controller='0' bus='0' target='0' unit='0'/> + </disk> + <controller type='ide' index='0'> + <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> + </controller> + <controller type='usb' index='0' model='nec-xhci' ports='6'> + <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> + </controller> + <controller type='pci' index='0' model='pci-root'/> + <controller type='virtio-serial' index='0'> + <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> + </controller> + <interface type='bridge'> + <mac address='52:54:00:a2:a4:e3'/> + <source bridge='qvs0'/> + <model type='virtio'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> + </interface> + <channel type='unix'> + <source mode='bind' path='/QVS/var/lib/libvirt/qemu/1a3dabc5-c33b-4308-acc5-2245f3b64163.agent'/> + <target type='virtio' name='org.qemu.guest_agent.0'/> + <address type='virtio-serial' controller='0' bus='0' port='1'/> + </channel> + <input type='tablet' bus='usb'> + <address type='usb' bus='0' port='1'/> + </input> + <input type='mouse' bus='ps2'/> + <input type='keyboard' bus='ps2'/> + <tpm model='tpm-tis'> + <backend type='emulator' version='2.0'/> + </tpm> + <graphics type='vnc' port='-1' autoport='yes' listen='127.0.0.1' keymap='en-us'> + <listen type='address' address='127.0.0.1'/> + </graphics> + <graphics type='spice' autoport='yes' listen='127.0.0.1' keymap='en-us'> + <listen type='address' address='127.0.0.1'/> + <image compression='off'/> + <jpeg compression='never'/> + <zlib compression='never'/> + <playback compression='off'/> + <streaming mode='all'/> + </graphics> + <sound model='ich6'> + <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> + </sound> + <audio id='1' type='spice'/> + <video> + <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> + </video> + <memballoon model='virtio'> + <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> + </memballoon> + </devices> +</domain> +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2981 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2981 new file mode 100644 index 000000000..584015228 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2981 @@ -0,0 +1,25 @@ +Assert error with accel=hvf:tcg when hvf is unavailable +Description of problem: +Trying to start qemu with `-machine virt,accel=hvf:tcg` in a Mac OS guest under Mac OS host, both arm64. I expect it to try hvf (unavailable - nested virtualization not supported) and fallback to tcg. Documentation for accel option says "If there is more than one accelerator specified, the next one is used if the previous one fails to initialize." This works fine with kvm, but for hvf it crashes in some auxiliary function when trying it: + +``` +% qemu-system-aarch64 -machine virt,accel=hvf:tcg +qemu-system-aarch64: Error: ret = HV_UNSUPPORTED (0xfae9400f, at ../target/arm/hvf/hvf.c:949) +``` + +Stack trace +``` + * frame #0: 0x0000000193a18388 libsystem_kernel.dylib`__pthread_kill + 8 + frame #1: 0x0000000193a5188c libsystem_pthread.dylib`pthread_kill + 296 + frame #2: 0x000000019395ac60 libsystem_c.dylib`abort + 124 + frame #3: 0x00000001005ee7f4 qemu-system-aarch64`assert_hvf_ok_impl + 92 + frame #4: 0x000000010032a550 qemu-system-aarch64`hvf_arm_get_max_ipa_bit_size + 64 + frame #5: 0x0000000100334928 qemu-system-aarch64`virt_hvf_get_physical_address_range + 68 + frame #6: 0x00000001005ee9b8 qemu-system-aarch64`hvf_accel_init + 68 + frame #7: 0x00000001002ef8e4 qemu-system-aarch64`accel_init_machine + 92 + frame #8: 0x00000001002a6640 qemu-system-aarch64`do_configure_accelerator + 208 + frame #9: 0x0000000100782bdc qemu-system-aarch64`qemu_opts_foreach + 112 + frame #10: 0x00000001002a3180 qemu-system-aarch64`qemu_init + 11344 + frame #11: 0x00000001006ea76c qemu-system-aarch64`main + 36 + frame #12: 0x00000001936b2b4c dyld`start + 6000 +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2983 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2983 new file mode 100644 index 000000000..4070f2023 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2983 @@ -0,0 +1,115 @@ +qemu-system-riscv64 randomly turns MPP bits to 0 in the mstatus word. +Description of problem: +ToyOs runs the kernel in machine mode and user programs in user mode. This is specific choice on my part to make sure the kernel code runs with machine address and user code runs with virtual addresses. This is different than Linux, NetBSD or other OSes I know that run the kernel in supervisor mode. When running in machine mode and running kernel code, I get a a trap. My error message looks like this: + +PANIC: Unexpected trap from machine mode! + mepc = 0x800002a8, mcause = 2, mtval=0xe78023 mstatus=0xa00000080 + +Notice, the mstatus bits show the trap was due to a privileged instruction being run by a "user" mode instruction. In the "assignment version" used for the above, no user code was run. It was just multiple threads running in machine mode. Also, the trap function is run with the MPP bits of 0, so even trying to recover from this trap can't be done as trying to manipulate the mstatus will generate yet again another trap to the same place and still running in "user" mode. + +This change does not happen on every run. It happens more consistently recently when trying to debug the kernel with gdb. This must be a race condition somewhere. + +The kernel is written in C++ with C libraries. +Steps to reproduce: +1. You will need to have access to my kernel and possibly my code base. This is a code base that I want to stay at WWU (Western Washington University). +2. Give the command "bmake run". It often completes with no problems, but if you run it often enough it will generate this trap from "machine mode". The example above had four good runs with no errors and on the fifth run it blew up. There is not guaranteed way to get this to have a problem. (This is why I haven't reported it before, I kept trying to get a minimal code set that had the problem, but I couldn't do it.) +Additional information: +This is a bug has been a problem for several years. It didn't strike very often on some versions of qemu. I think one of the 7.x.x versions happened not too often. But with newer, faster machines and a different version of Linux, this bug has become a big problem for me and my students. + +Here is a sample bad run: (All compilation has been done before so this just makes sure everything is up-to-date and then runs qemu-system-riscv64. In this assignment, no user mode code is being run. Threads are all running in machine mode for the entire time. I am getting clock interrupts on the CPU, but that does not appear to be the problem.) + +$ bmake run +if ! [ -e toolbin ] ; then mkdir toolbin ; fi; +(cd tools; bmake install) +(cd toy_fs; bmake) +`toyfs' is up to date. +(cd mkdep; bmake) +`mkdep' is up to date. +(cd toy_fs; bmake install) +(cd mkdep; bmake install) +Making in /home/phil/447/csci447_s25/lib +Making in /home/phil/447/csci447_s25/kernel +`DISK' is up to date. +qemu-system-riscv64 -machine virt -bios none -m 1G -smp 1 -nographic -global virtio-mmio.force-legacy=false -drive file=DISK,if=none,format=raw,id=x0 -device virtio-blk-device,drive=x0,bus=virtio-mmio-bus.0 -kernel kernel/kernel -gdb tcp::27277 +Initializing scheduler ... +Initializing frame set... +Initializing thread set ... +Initializing process set ... +Initializing fcb set ... +Initializing OpenFile set ... +Initializing pipe set ... +Initializing vertio ... +Initializing filesystem ... +Starting os_main ... +PANIC: Unexpected trap from machine mode! + mepc = 0x800002a8, mcause = 2, mtval=0xe78023 mstatus=0xa00000080 +attach with gdb! +QEMU: Terminated + +$ riscv64-unknown-elf-addr2line -e kernel/kernel 0x800002a8 +/home/phil/447/csci447_s25/kernel/runtime.S:350 + +And that instruction turns out to be "mret", the return from the clock interrupt. + +The following is a error free run of this. + +$ bmake run +if ! [ -e toolbin ] ; then mkdir toolbin ; fi; +(cd tools; bmake install) +(cd toy_fs; bmake) +`toyfs' is up to date. +(cd mkdep; bmake) +`mkdep' is up to date. +(cd toy_fs; bmake install) +(cd mkdep; bmake install) +Making in /home/phil/447/csci447_s25/lib +Making in /home/phil/447/csci447_s25/kernel +`DISK' is up to date. +qemu-system-riscv64 -machine virt -bios none -m 1G -smp 1 -nographic -global virtio-mmio.force-legacy=false -drive file=DISK,if=none,format=raw,id=x0 -device virtio-blk-device,drive=x0,bus=virtio-mmio-bus.0 -kernel kernel/kernel -gdb tcp::27277 +Initializing scheduler ... +Initializing frame set... +Initializing thread set ... +Initializing process set ... +Initializing fcb set ... +Initializing OpenFile set ... +Initializing pipe set ... +Initializing vertio ... +Initializing filesystem ... +Starting os_main ... + +Welcome to Toy OS, hartid = 0 +Assignment 3 ... + +********** Frame Tester ********** +1.3.2.4.5.6.7.8.9.10.12.11.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.61.62.63.64.65.66.67.68.69.70.71.72.73.74.75.76.77.78.79.80.81.82.83.85.84.87.86.88.89.91.92.90.93.94.95.96.97.98.99.100.101.102.103.104.105.106.107.108.109.110.111.113.112.114.115.116.117.119.118.120.121.122.123.124.125.126.127.128.129.130.131.132.133.134.135.136.137.138.139.140.161.162.163.164.166.165.167.168.169.170.171.172.173.174.175.177.178.176.179.180.181.182.183.184.185.186.187.188.189.190.191.194.193.192.195.197.196.198.200.199.201.202.203.204.206.205.207.209.208.210.211.212.214.213.215.216.217.218.219.220.221.222.223.224.225.226.227.228.230.231.229.232.233.234.235.236.237.238.239.240.241.242.243.244.245.246.247.248.249.250.252.253.251.254.255.256.257.258.259.260.261.262.263.264.265.266.267.268.269.270.271.273.272.274.275.276.277.278.279.280.281.282.283.284.285.286.287.288.289.290.291.292.293.294.295.296.297.298.299.300.301.302.303.304.305.306.308.307.309.310.311.312.313.314.315.316.317.318.319.320.341.342.343.344.345.346.347.348.349.350.351.353.352.354.356.355.357.358.359.360.361.362.363.364.365.366.367.368.369.370.371.372.373.374.375.376.377.378.379.380.382.381.383.384.385.386.387.388.389.390.391.392.394.395.393.396.397.398.399.400.401.402.403.404.405.406.407.409.408.410.411.412.413.414.415.416.417.418.420.419.421.422.423.425.426.424.427.428.429.430.432.431.433.434.435.436.437.438.439.440.441.442.443.444.445.446.447.448.449.450.451.452.453.455.454.457.456.458.459.460.461.462.463.464.465.466.467.468.469.470.471.472.473.474.475.476.477.478.479.480.481.482.483.484.485.486.487.488.489.490.491.492.493.494.495.496.497.498.499.500.521.523.522.524.525.526.528.527.529.530.531.532.533.534.535.536.537.538.539.540.542.544.543.541.545.546.548.547.549.551.550.553.552.555.554.557.556.559.558.560.561.562.563.564.565.566.567.568.569.570.571.572.573.574.575.576.577.578.579.580.581.582.583.584.585.586.587.588.589.590.591.592.593.594.595.596.597.598.599.600.601.602.603.604.605.606.607.608.609.610.611.612.613.614.615.616.617.618.619.620.621.622.623.624.625.626.627.628.629.630.631.632.633.634.635.636.637.638.639.640.641.642.643.644.645.646.647.648.649.650.651.652.653.654.655.656.657.658.659.660.661.662.663.664.665.666.667.668.669.670.671.672.673.675.674.676.677.678.679.680.701.702.704.703.705.706.707.708.709.711.710.712.713.714.715.716.717.718.719.720.723.722.721.724.725.727.726.728.729.730.731.732.733.734.735.737.736.738.739.741.740.742.744.743.746.747.745.748.749.750.751.752.753.754.756.755.757.758.759.761.760.762.763.764.765.766.767.768.769.770.771.772.773.774.775.776.777.778.780.779.781.782.783.784.785.786.787.788.789.790.791.792.793.794.795.797.796.798.799.800.801.802.803.804.805.806.807.808.809.810.811.812.813.814.815.816.817.818.819.820.821.822.823.825.824.826.827.828.829.830.831.832.833.834.835.836.837.838.839.840.841.842.843.844.845.846.847.848.849.850.851.852.853.854.855.856.857.858.859.860.882.881.884.883.885.886.888.887.890.889.891.892.893.894.895.896.897.898.899.901.900.902.903.904.905.906.907.908.909.910.911.913.912.914.915.916.917.918.919.920.921.922.923.924.925.926.928.927.929.930.931.932.933.934.935.936.937.939.938.940.941.942.943.944.945.946.947.948.949.950.951.952.953.954.955.956.957.958.959.961.960.962.963.964.965.966.967.968.969.970.971.972.973.974.975.976.977.978.979.980.981.982.983.984.985.986.987.988.989.990.991.992.993.994.995.996.997.998.999.1000.1001.1002.1003.1004.1005.1006.1008.1007.1009.1010.1011.1012.1014.1013.1015.1016.1017.1018.1019.1020.1021.1022.1023.1024.1025.1026.1027.1028.1029.1030.1031.1032.1033.1034.1035.1036.1037.1038.1039.1040.1061.1062.1063.1065.1064.1066.1069.1067.1068.1070.1071.1072.1073.1074.1075.1076.1077.1078.1079.1080.1082.1081.1084.1083.1085.1086.1087.1088.1089.1090.1091.1093.1092.1094.1095.1097.1096.1098.1099.1100.1101.1102.1103.1104.1105.1106.1107.1109.1108.1110.1111.1112.1113.1114.1115.1117.1116.1118.1119.1120.1121.1122.1123.1124.1125.1126.1127.1128.1129.1130.1131.1132.1133.1134.1135.1136.1137.1138.1139.1140.1141.1142.1143.1144.1145.1146.1147.1148.1149.1150.1151.1152.1153.1154.1155.1156.1157.1158.1159.1160.1161.1162.1163.1164.1165.1166.1167.1168.1169.1170.1172.1171.1173.1174.1175.1176.1177.1178.1179.1180.1181.1182.1183.1184.1185.1186.1187.1188.1189.1190.1191.1192.1193.1194.1195.1196.1197.1198.1199.1201.1200.1202.1203.1204.1205.1207.1206.1208.1209.1210.1211.1212.1213.1214.1215.1216.1217.1218.1219.1220.1241.1242.1244.1243.1245.1246.1247.1248.1249.1251.1250.1252.1253.1254.1255.1256.1257.1258.1259.1260.1261.1262.1263.1264.1265.1266.1267.1269.1268.1270.1272.1271.1274.1273.1275.1276.1277.1278.1279.1280.1281.1283.1282.1284.1285.1287.1286.1288.1290.1289.1291.1292.1293.1294.1295.1296.1297.1299.1298.1300.1301.1302.1303.1304.1305.1306.1307.1308.1309.1310.1311.1312.1313.1315.1314.1316.1317.1318.1319.1320.1321.1322.1323.1324.1325.1326.1327.1328.1329.1330.1331.1332.1333.1335.1334.1336.1337.1338.1339.1340.1341.1342.1343.1344.1345.1346.1347.1348.1349.1350.1351.1352.1353.1354.1355.1356.1357.1358.1360.1361.1359.1362.1364.1363.1365.1366.1367.1370.1369.1368.1371.1372.1373.1375.1374.1376.1377.1378.1379.1380.1381.1382.1383.1384.1385.1386.1387.1388.1389.1390.1391.1392.1393.1394.1395.1396.1397.1398.1400.1401.1419.1422.1423.1424.1426.1425.1427.1428.1429.1431.1430.1432.1434.1435.1433.1437.1436.1438.1440.1439.1441.1447.1442.1443.1444.1445.1446.1448.1449.1450.1452.1453.1451.1454.1455.1456.1457.1459.1458.1461.1460.1462.1463.1464.1465.1466.1467.1468.1469.1470.1471.1472.1473.1474.1475.1476.1477.1478.1479.1480.1481.1482.1483.1484.1486.1485.1487.1488.1489.1490.1491.1492.1493.1494.1495.1496.1498.1497.1499.1500.1501.1502.1503.1504.1505.1506.1507.1508.1509.1510.1511.1512.1513.1514.1515.1516.1517.1519.1518.1520.1521.1522.1523.1524.1525.1526.1527.1528.1529.1530.1531.1532.1533.1534.1535.1536.1537.1538.1539.1540.1541.1542.1543.1544.1545.1547.1546.1548.1549.1550.1551.1553.1552.1554.1555.1556.1557.1558.1559.1560.1561.1562.1563.1564.1565.1566.1567.1568.1569.1570.1571.1572.1573.1574.1575.1576.1577.1578.1579.1581.1600.1602.1603.1604.1605.1607.1606.1608.1609.1610.1612.1611.1613.1614.1616.1615.1617.1618.1619.1622.1621.1620.1623.1624.1625.1626.1627.1628.1629.1630.1631.1632.1633.1635.1634.1636.1637.1638.1639.1640.1641.1642.1643.1644.1646.1645.1647.1648.1650.1649.1652.1651.1653.1654.1655.1656.1657.1658.1659.1660.1661.1663.1662.1664.1665.1666.1667.1668.1669.1670.1671.1672.1673.1674.1675.1676.1677.1678.1679.1680.1681.1682.1683.1685.1684.1686.1687.1688.1689.1691.1690.1692.1693.1694.1695.1696.1698.1697.1699.1700.1701.1702.1703.1704.1705.1706.1707.1708.1709.1710.1711.1713.1712.1714.1715.1717.1716.1718.1719.1720.1721.1722.1723.1724.1725.1726.1727.1728.1729.1730.1731.1732.1733.1734.1735.1736.1737.1738.1739.1740.1741.1742.1743.1744.1745.1746.1747.1748.1749.1751.1750.1752.1753.1754.1755.1756.1757.1758.1759.1762.1780.1781.1784.1785.1783.1787.1788.1786.1789.1790.1791.1792.1794.1793.1795.1796.1799.1797.1800.1798. +Frame 0, used 0x Frame 1, used 0x Frame 2, used 0x +Frame 3, used 438x Frame 4, used 435x Frame 5, used 429x +Frame 6, used 420x Frame 7, used 414x Frame 8, used 407x +Frame 9, used 396x Frame 10, used 391x Frame 11, used 386x +Frame 12, used 374x Frame 13, used 372x Frame 14, used 367x +Frame 15, used 361x Frame 16, used 353x Frame 17, used 345x +Frame 18, used 342x Frame 19, used 335x Frame 20, used 330x +Frame 21, used 329x Frame 22, used 325x Frame 23, used 319x +Frame 24, used 271x Frame 25, used 262x Frame 26, used 255x +Frame 27, used 141x Frame 28, used 108x Frame 29, used 95x +********** Test Done ********** + +********** Thread Tester ********** +3.4.5.6.7.8.9.10.11.12.13.14.15.16.17.18.19.2.22.20.30.31.24.21.23.25.26.32.27.33.39.40.41.28.29.35.34.36.42.44.48.49.50.37.51.38.45.46.52.55.57.43.58.60.53.61.62.56.63.65.67.68.47.70.71.64.72.73.74.69.54.77.78.59.81.82.75.83.76.85.79.86.89.91.92.84.93.66.87.80.94.96.98.101.102.103.95.88.104.97.99.105.108.110.111.112.113.100.114.107.115.109.117.119.120.122.106.116.124.125.90.126.129.130.131.132.133.127.134.135.128.136.138.139.141.142.143.144.123.145.140.146.148.149.151.153.152.154.118.147.156.121.159.160.161.162.163.157.164.150.137.166.169.170.171.172.158.174.167.175.155.176.178.173.181.182.168.183.184.179.185.165.187.177.188.189.186.180.190.192.191.193.195.196.197.194.198.199.200.201. +********** Test Done ********** + +********** Process Tester ********** +5.6.7.8.9.10.2.3.11.4.23.22.24.19.21.12.13.14.25.26.29.28.15.16.17.30.18.20.34.35.38.39.32.40.31.27.41.33.43.44.48.49.50.42.36.51.37.45.52.54.56.58.59.60.61.46.47.53.62.57.67.68.69.70.71.55.63.64.65.73.76.78.79.72.81.66.74.82.75.83.86.88.90.91.77.84.92.85.93.80.95.97.99.101.87.102.94.89.103.96.98.100.108.112.104.113.105.114.106.107.109.115.110.122.123.124.116.111.117.118.119.125.120.132.134.121.126.127.135.130.128.136.129.139.133.131.145.138.137.142.140.143.146.141.155.147.148.144.149.152.150.151.153.156.157.158.154.162.159.160.161.163.166.164.167.165.168.172.170.169.180.173.176.171.174.181.175.177.178.179.188.189.182.185.183.190.186.184.187.191.193.194.192.195.196.197.198.199.200.201. +********** Test Done ********** + +********** OpenFile Tester ********** +3.4.5.2.8.6.9.7.11.10.13.12.14.16.15.17.18.19.21.20.22.23.24.26.25.27.28.29.31.30.32.33.34.36.35.37.39.38.40.41.42.43.45.44.47.46.49.48.50.52.51.53.55.54.56.58.57.59.60.62.61.63.65.66.64.67.69.68.70.71.72.74.73.76.77.75.78.80.79.81.82.83.85.84.86.87.88.90.89.91.92.94.95.93.97.96.98.99.100.102.101.103.105.104.106.108.107.109.111.110.113.112.115.114.116.117.118.119.120.121.122.123.124.125.126.127.128.129.130.131.132.133.134.135.136.138.137.139.140.141.142.143.144.145.146.147.148.149.150.152.151.153.154.155.156.157.158.159.160.161.162.163.164.166.165.167.168.169.170.172.171.173.174.176.175.177.178.180.179.181.183.182.185.184.186.187.188.189.190.191.192.194.193.195.197.196.198.199.200.201. +********** Test Done ********** + +********** FileControlBlock Tester ********** +2.3.4.5.6.7.8.9.10.2!W1.3!W2.5!W3.4!W4.6!W5.7!W6.8!W7.9!W8.10!F12.2!12.3!W1.12.5!W2.12.W3.12.12.12.12.12.10!4!W4.6!W5.7!9!W6.W7.8!W8.F12.12.12.20.12.12.12.20.12.12.12.20.20.20.20.20.20.20. +********** Test Done ********** + +All Assignment 3 tests done. + +I call this a "heisenbug" as I never know when it will strike and stop ToyOS from running. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2984 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2984 new file mode 100644 index 000000000..b5180a69d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2984 @@ -0,0 +1,53 @@ +CPU hotplug crashed the guest when using virt-type as qemu! +Description of problem: +Guest is getting crashing and getting into shutoff state when I am trying to hotplug much more cpus than present in the host! This is happening only when i give virt-type as qemu. +Additional information: +Tried reproducing while attaching gdb shows below backtrace which happened after hotplugging 249 CPUs in TCG mode: + +``` +Thread 261 "CPU 249/TCG" received signal SIGABRT, Aborted. +[Switching to Thread 0x7ff97c00ea20 (LWP 51567)] +0x00007fff84cac3e8 in __pthread_kill_implementation () from target:/lib64/glibc-hwcaps/power10/libc.so.6 +(gdb) bt +#0 0x00007fff84cac3e8 in __pthread_kill_implementation () from target:/lib64/glibc-hwcaps/power10/libc.so.6 +#1 0x00007fff84c46ba0 in raise () from target:/lib64/glibc-hwcaps/power10/libc.so.6 +#2 0x00007fff84c29354 in abort () from target:/lib64/glibc-hwcaps/power10/libc.so.6 +#3 0x00007fff850f1e30 in g_assertion_message () from target:/lib64/libglib-2.0.so.0 +#4 0x00007fff850f1ebc in g_assertion_message_expr () from target:/lib64/libglib-2.0.so.0 +#5 0x00000001376c6f00 in tcg_region_initial_alloc__locked (s=0x7fff7c000f30) at ../tcg/region.c:396 +#6 0x00000001376c6fa8 in tcg_region_initial_alloc (s=0x7fff7c000f30) at ../tcg/region.c:402 +#7 0x00000001376dae08 in tcg_register_thread () at ../tcg/tcg.c:1011 +#8 0x000000013768b7e4 in mttcg_cpu_thread_fn (arg=0x143e884f0) at ../accel/tcg/tcg-accel-ops-mttcg.c:77 +#9 0x0000000137bbb2d0 in qemu_thread_start (args=0x143b4aff0) at ../util/qemu-thread-posix.c:542 +#10 0x00007fff84ca9be0 in start_thread () from target:/lib64/glibc-hwcaps/power10/libc.so.6 +#11 0x00007fff84d4ef3c in __clone3 () from target:/lib64/glibc-hwcaps/power10/libc.so.6 +(gdb) +``` + +which points to below code: + +``` +/* + * Perform a context's first region allocation. + * This function does _not_ increment region.agg_size_full. + */ +static void tcg_region_initial_alloc__locked(TCGContext *s) +{ + bool err = tcg_region_alloc__locked(s); + g_assert(!err); +} +``` + +Here, tcg_region_alloc__locked returns true on failure when max region allocation is reached and therefore intentionally asserted as TCG can't proceed without it. + +``` +static bool tcg_region_alloc__locked(TCGContext *s) +{ + if (region.current == region.n) { + return true; + } + tcg_region_assign(s, region.current); + region.current++; + return false; +} +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2985 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2985 new file mode 100644 index 000000000..844eb959d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2985 @@ -0,0 +1,8 @@ +throttle group limit feature request for discard +Additional information: +- Need to add particular options in [ThrottleGroupProperties](https://qemu-project.gitlab.io/qemu/interop/qemu-qmp-ref.html#object-QMP-block-core.ThrottleGroupProperties) which like this +```txt +x-discard-iops-total +x-discard-iops-total-max +.... +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2986 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2986 new file mode 100644 index 000000000..cc8340b29 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2986 @@ -0,0 +1 @@ +ARM register DBGDTR_EL0 incorrectly causes undefined exception diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2988 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2988 new file mode 100644 index 000000000..49598abd6 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2988 @@ -0,0 +1,7 @@ +Absolute mouse mode is broken in SDL2 +Description of problem: +Absolute mouse mode is broken in SDL2. Bisected at 30aa105640b0a2a541744b6584d57c9a4b86debd. + +Relative mouse mode has never worked in stretched SDL2 Display for display controllers that passed through cursor data and have positions warped by HOST UI backend. It looks like 30aa105640b0a2a541744b6584d57c9a4b86debd tried to fix this but it didn't work out. Scaling **"relative motions"** isn't straight-forward as what the commit had expected. + +Absolute mouse mode mode has always worked in stretched SDL2 Display. 30aa105640b0a2a541744b6584d57c9a4b86debd broke it without fixing anything. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/300 b/gitlab/issues_text/target_missing/host_missing/accel_missing/300 new file mode 100644 index 000000000..868612479 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/300 @@ -0,0 +1 @@ +qemu-system-i386 virtio-vga: Assertion in address_space_stw_le_cached failed again diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/301 b/gitlab/issues_text/target_missing/host_missing/accel_missing/301 new file mode 100644 index 000000000..f229c74f4 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/301 @@ -0,0 +1 @@ +Assertion `addr < cache->len && 2 <= cache->len - addr' in virtio-blk diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/302 b/gitlab/issues_text/target_missing/host_missing/accel_missing/302 new file mode 100644 index 000000000..9237e4682 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/302 @@ -0,0 +1 @@ +[Fuzz] qemu-system-i386 virtio-mouse: Assertion in address_space_lduw_le_cached failed diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/303 b/gitlab/issues_text/target_missing/host_missing/accel_missing/303 new file mode 100644 index 000000000..1fe2e7975 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/303 @@ -0,0 +1 @@ +assert issue locates in hw/usb/core.c:727: usb_ep_get: Assertion `pid == USB_TOKEN_IN || pid == USB_TOKEN_OUT' failed diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/304 b/gitlab/issues_text/target_missing/host_missing/accel_missing/304 new file mode 100644 index 000000000..f3faeb78b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/304 @@ -0,0 +1 @@ +assertion failure in mptsas1068 emulator diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/305 b/gitlab/issues_text/target_missing/host_missing/accel_missing/305 new file mode 100644 index 000000000..0856bcf5f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/305 @@ -0,0 +1 @@ +assertion failure in lsi53c810 emulator diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/306 b/gitlab/issues_text/target_missing/host_missing/accel_missing/306 new file mode 100644 index 000000000..c9c23af05 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/306 @@ -0,0 +1 @@ +Option to constrain linux-user exec() to emulated CPU only diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/307 b/gitlab/issues_text/target_missing/host_missing/accel_missing/307 new file mode 100644 index 000000000..b0363161d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/307 @@ -0,0 +1 @@ +qemu may freeze during drive-mirroring on fragmented FS diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/308 b/gitlab/issues_text/target_missing/host_missing/accel_missing/308 new file mode 100644 index 000000000..4fdc7c95a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/308 @@ -0,0 +1 @@ +QEMU: net: vmxnet: integer overflow may crash guest diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/309 b/gitlab/issues_text/target_missing/host_missing/accel_missing/309 new file mode 100644 index 000000000..521629795 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/309 @@ -0,0 +1 @@ +assert issue locates in hw/net/vmxnet3.c:1793:vmxnet3_io_bar1_write: code should not be reach diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/310 b/gitlab/issues_text/target_missing/host_missing/accel_missing/310 new file mode 100644 index 000000000..e76640050 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/310 @@ -0,0 +1 @@ +unable to migrate non shared storage when TLS is used diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/311 b/gitlab/issues_text/target_missing/host_missing/accel_missing/311 new file mode 100644 index 000000000..c0496864c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/311 @@ -0,0 +1 @@ +qemu user mode: rt signals not implemented for sparc guests diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/313 b/gitlab/issues_text/target_missing/host_missing/accel_missing/313 new file mode 100644 index 000000000..1531161e9 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/313 @@ -0,0 +1 @@ +-daemonize not working on macOS diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/315 b/gitlab/issues_text/target_missing/host_missing/accel_missing/315 new file mode 100644 index 000000000..49e2d2eac --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/315 @@ -0,0 +1 @@ +3d accel does not take care of 1280x960 setting diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/316 b/gitlab/issues_text/target_missing/host_missing/accel_missing/316 new file mode 100644 index 000000000..ecdca3a85 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/316 @@ -0,0 +1 @@ +[feature request] webcam support diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/321 b/gitlab/issues_text/target_missing/host_missing/accel_missing/321 new file mode 100644 index 000000000..b515a6c48 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/321 @@ -0,0 +1 @@ +qemu 5.2.0 configure script explodes when in read only directory diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/322 b/gitlab/issues_text/target_missing/host_missing/accel_missing/322 new file mode 100644 index 000000000..d71c62fc0 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/322 @@ -0,0 +1 @@ +Can't(?) disable default floppy drive any more in qemu 6.0 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/323 b/gitlab/issues_text/target_missing/host_missing/accel_missing/323 new file mode 100644 index 000000000..821a28431 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/323 @@ -0,0 +1 @@ +qemu 5.2.0: Add reconnect option support for netdev socket diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/324 b/gitlab/issues_text/target_missing/host_missing/accel_missing/324 new file mode 100644 index 000000000..ccd57dfa3 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/324 @@ -0,0 +1 @@ +chrome based apps can not be run under qemu user mode diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/327 b/gitlab/issues_text/target_missing/host_missing/accel_missing/327 new file mode 100644 index 000000000..69c446086 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/327 @@ -0,0 +1 @@ +Storage | Two decimal digits precision diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/328 b/gitlab/issues_text/target_missing/host_missing/accel_missing/328 new file mode 100644 index 000000000..45180a8b9 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/328 @@ -0,0 +1 @@ +numerical keypad disabled by default in the guest diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/332 b/gitlab/issues_text/target_missing/host_missing/accel_missing/332 new file mode 100644 index 000000000..2d9d673e2 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/332 @@ -0,0 +1 @@ +VirtIO drivers don't work on Windows: "GLib: Too many handles to wait for!" crash diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/334 b/gitlab/issues_text/target_missing/host_missing/accel_missing/334 new file mode 100644 index 000000000..447ad007a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/334 @@ -0,0 +1 @@ +macOS App Nap feature gradually freezes QEMU process diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/335 b/gitlab/issues_text/target_missing/host_missing/accel_missing/335 new file mode 100644 index 000000000..e9fce88d3 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/335 @@ -0,0 +1 @@ +Broken tap networking on macOS host diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/336 b/gitlab/issues_text/target_missing/host_missing/accel_missing/336 new file mode 100644 index 000000000..e70bf173c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/336 @@ -0,0 +1 @@ +Built-in DHCP server: SiAddr diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/338 b/gitlab/issues_text/target_missing/host_missing/accel_missing/338 new file mode 100644 index 000000000..8c131dc8a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/338 @@ -0,0 +1 @@ +QEMU: Null Pointer Failure in fdctrl_read() in hw/block/fdc.c diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/341 b/gitlab/issues_text/target_missing/host_missing/accel_missing/341 new file mode 100644 index 000000000..2488fcc2e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/341 @@ -0,0 +1 @@ +Null-ptr dereference on AHCICmdHdr in ahci_pio_transfer diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/342 b/gitlab/issues_text/target_missing/host_missing/accel_missing/342 new file mode 100644 index 000000000..bcca31390 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/342 @@ -0,0 +1 @@ +Assertion `child->perm & BLK_PERM_WRITE' failed in bdrv_co_write_req_prepare through atapi diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/344 b/gitlab/issues_text/target_missing/host_missing/accel_missing/344 new file mode 100644 index 000000000..f09d798d3 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/344 @@ -0,0 +1 @@ +Option "-loadvm" cannot load VM snapshot, created from QMP API diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/345 b/gitlab/issues_text/target_missing/host_missing/accel_missing/345 new file mode 100644 index 000000000..2b60167e0 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/345 @@ -0,0 +1 @@ +Sector translation bug in scsi_unmap_complete_noio diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/347 b/gitlab/issues_text/target_missing/host_missing/accel_missing/347 new file mode 100644 index 000000000..7d4b21825 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/347 @@ -0,0 +1 @@ +Forward host UNIX socket to guest TCP port diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/348 b/gitlab/issues_text/target_missing/host_missing/accel_missing/348 new file mode 100644 index 000000000..76e344892 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/348 @@ -0,0 +1 @@ +qemu-user fails to run container using systemd-networkd: "Could not create manager: Protocol not supported" diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/349 b/gitlab/issues_text/target_missing/host_missing/accel_missing/349 new file mode 100644 index 000000000..d1e969c8c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/349 @@ -0,0 +1 @@ +USB folder sharing causing segment fault diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/350 b/gitlab/issues_text/target_missing/host_missing/accel_missing/350 new file mode 100644 index 000000000..7b757be42 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/350 @@ -0,0 +1 @@ +lsisas1068 not supported (for VMDK manipulation) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/351 b/gitlab/issues_text/target_missing/host_missing/accel_missing/351 new file mode 100644 index 000000000..3ffe774c3 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/351 @@ -0,0 +1 @@ +German keyboard vnc issue diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/354 b/gitlab/issues_text/target_missing/host_missing/accel_missing/354 new file mode 100644 index 000000000..0f14f4c2f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/354 @@ -0,0 +1 @@ +Emulation error when calling the SIOCGIFNETMASK ioctl through qemu-user diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/355 b/gitlab/issues_text/target_missing/host_missing/accel_missing/355 new file mode 100644 index 000000000..78053cf41 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/355 @@ -0,0 +1 @@ +A possible divide by zero bug in get_whole_cluster diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/357 b/gitlab/issues_text/target_missing/host_missing/accel_missing/357 new file mode 100644 index 000000000..a3a3797d9 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/357 @@ -0,0 +1 @@ +race condition in hw/input/pckbd.c causes wrong data to be read on interrupts diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/359 b/gitlab/issues_text/target_missing/host_missing/accel_missing/359 new file mode 100644 index 000000000..ce7dbaa8f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/359 @@ -0,0 +1 @@ +In the "tests/qtests/meson.build" line 92 need dbus-vmstate1.h and dbus-vmstate1.c files, but in "tests/qtests/" not include this files. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/362 b/gitlab/issues_text/target_missing/host_missing/accel_missing/362 new file mode 100644 index 000000000..c86fa33c9 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/362 @@ -0,0 +1 @@ +check of PMR capability is missing for PMRCTL register write diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/365 b/gitlab/issues_text/target_missing/host_missing/accel_missing/365 new file mode 100644 index 000000000..ac5b0c2b5 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/365 @@ -0,0 +1 @@ +virtiofsd: Directory for PID file hardcoded diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/366 b/gitlab/issues_text/target_missing/host_missing/accel_missing/366 new file mode 100644 index 000000000..d4968d280 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/366 @@ -0,0 +1 @@ +How to make OVMF diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/369 b/gitlab/issues_text/target_missing/host_missing/accel_missing/369 new file mode 100644 index 000000000..eb61187e4 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/369 @@ -0,0 +1 @@ +Remove leading underscores from #defines diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/370 b/gitlab/issues_text/target_missing/host_missing/accel_missing/370 new file mode 100644 index 000000000..29f077bd6 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/370 @@ -0,0 +1 @@ +Indentation should be done with spaces, not with TABs, in the UI, graphics, audio and USB subsystem diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/371 b/gitlab/issues_text/target_missing/host_missing/accel_missing/371 new file mode 100644 index 000000000..7ed23dfd8 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/371 @@ -0,0 +1 @@ +Indentation should be done with spaces, not with TABs, in the block subsystem diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/377 b/gitlab/issues_text/target_missing/host_missing/accel_missing/377 new file mode 100644 index 000000000..0e4dc88a6 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/377 @@ -0,0 +1 @@ +Indentation should be done with spaces, not with TABs, in the net subsystem diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/378 b/gitlab/issues_text/target_missing/host_missing/accel_missing/378 new file mode 100644 index 000000000..5c6da66e1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/378 @@ -0,0 +1 @@ +Indentation should be done with spaces, not with TABs diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/379 b/gitlab/issues_text/target_missing/host_missing/accel_missing/379 new file mode 100644 index 000000000..f1cf1b26b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/379 @@ -0,0 +1 @@ +Update the FSF address to their current location diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/383 b/gitlab/issues_text/target_missing/host_missing/accel_missing/383 new file mode 100644 index 000000000..a2fab8abd --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/383 @@ -0,0 +1 @@ +virtio-gpu: heap-buffer-overflow in virtio_gpu_disable_scanout diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/384 b/gitlab/issues_text/target_missing/host_missing/accel_missing/384 new file mode 100644 index 000000000..f284de94a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/384 @@ -0,0 +1 @@ +qemu-monitor-event command gets stuck randomly diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/388 b/gitlab/issues_text/target_missing/host_missing/accel_missing/388 new file mode 100644 index 000000000..565200914 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/388 @@ -0,0 +1 @@ +Can not pass hw device names as alsa input and output devices diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/392 b/gitlab/issues_text/target_missing/host_missing/accel_missing/392 new file mode 100644 index 000000000..f3927ae36 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/392 @@ -0,0 +1 @@ +`-hda` and `-drive` differ with respect to path handling diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/393 b/gitlab/issues_text/target_missing/host_missing/accel_missing/393 new file mode 100644 index 000000000..51c5e1b52 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/393 @@ -0,0 +1 @@ +tests/vm: Warn when cross-build VM is run with TCG accelerator diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/395 b/gitlab/issues_text/target_missing/host_missing/accel_missing/395 new file mode 100644 index 000000000..393b30778 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/395 @@ -0,0 +1 @@ +Write a python style guide document diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/396 b/gitlab/issues_text/target_missing/host_missing/accel_missing/396 new file mode 100644 index 000000000..1b6025551 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/396 @@ -0,0 +1 @@ +Investigate moving other packages in ./scripts to ./python diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/397 b/gitlab/issues_text/target_missing/host_missing/accel_missing/397 new file mode 100644 index 000000000..ec7b93eb6 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/397 @@ -0,0 +1 @@ +Cannot run qemu at all diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/398 b/gitlab/issues_text/target_missing/host_missing/accel_missing/398 new file mode 100644 index 000000000..071c6a2b9 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/398 @@ -0,0 +1 @@ +qemu-system-aarch64 could not open 'ubuntu-16.04-server-cloudimg-arm64-uefi1.img' qemu6.0 on windows 10 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/399 b/gitlab/issues_text/target_missing/host_missing/accel_missing/399 new file mode 100644 index 000000000..ddcbd9c6a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/399 @@ -0,0 +1 @@ +drive-backup job hangs in a 'paused' state after unsuccessful first attempt diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/400 b/gitlab/issues_text/target_missing/host_missing/accel_missing/400 new file mode 100644 index 000000000..ff9830c4e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/400 @@ -0,0 +1 @@ +Build error -Werror=stringop-overflow in util/qemu-thread-posix.c diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/401 b/gitlab/issues_text/target_missing/host_missing/accel_missing/401 new file mode 100644 index 000000000..e1848f511 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/401 @@ -0,0 +1 @@ +Wishlist: nvme-ns: allow specifying eui-64 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/402 b/gitlab/issues_text/target_missing/host_missing/accel_missing/402 new file mode 100644 index 000000000..0158b4369 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/402 @@ -0,0 +1 @@ +e1000 / e1000e randomly stop sending packets to VM with DPDK app in VM diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/405 b/gitlab/issues_text/target_missing/host_missing/accel_missing/405 new file mode 100644 index 000000000..a3b3af79f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/405 @@ -0,0 +1 @@ +Assertion failure in e1000e_intrmgr_on_throttling_timer diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/406 b/gitlab/issues_text/target_missing/host_missing/accel_missing/406 new file mode 100644 index 000000000..a4a19191b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/406 @@ -0,0 +1 @@ +vhost-user net device sends SET_VRING_ENABLE before feature negotiation diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/407 b/gitlab/issues_text/target_missing/host_missing/accel_missing/407 new file mode 100644 index 000000000..b48e15f40 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/407 @@ -0,0 +1 @@ +migration: Build failure on MacOS with Homebrew (gnutls/gnutls.h not found) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/408 b/gitlab/issues_text/target_missing/host_missing/accel_missing/408 new file mode 100644 index 000000000..3ba91f600 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/408 @@ -0,0 +1 @@ +DLLs not installing on 32bit version diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/409 b/gitlab/issues_text/target_missing/host_missing/accel_missing/409 new file mode 100644 index 000000000..e8a3f5e09 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/409 @@ -0,0 +1 @@ +tar can only read 4096 bytes from some files on 9p diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/413 b/gitlab/issues_text/target_missing/host_missing/accel_missing/413 new file mode 100644 index 000000000..df3ed1e4e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/413 @@ -0,0 +1 @@ +Error handling: Audit callers of load_image_targphys, get_image_size, event_notifier_init, msix_init diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/414 b/gitlab/issues_text/target_missing/host_missing/accel_missing/414 new file mode 100644 index 000000000..0fa409d62 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/414 @@ -0,0 +1 @@ +Error handling: Use &error_abort instead of NULL for errp parameters for may-not-fail invocations diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/415 b/gitlab/issues_text/target_missing/host_missing/accel_missing/415 new file mode 100644 index 000000000..72903db55 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/415 @@ -0,0 +1 @@ +Error handling: Use TFR() macro where applicable diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/416 b/gitlab/issues_text/target_missing/host_missing/accel_missing/416 new file mode 100644 index 000000000..52d33d6b9 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/416 @@ -0,0 +1 @@ +Error handling: Audit unsafe usages of strerror() diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/417 b/gitlab/issues_text/target_missing/host_missing/accel_missing/417 new file mode 100644 index 000000000..0db7dfb93 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/417 @@ -0,0 +1 @@ +allow qemu_thread_create to return with error diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/418 b/gitlab/issues_text/target_missing/host_missing/accel_missing/418 new file mode 100644 index 000000000..76aa13d56 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/418 @@ -0,0 +1 @@ +qemu-img commit on Windows 10 fails diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/419 b/gitlab/issues_text/target_missing/host_missing/accel_missing/419 new file mode 100644 index 000000000..22a93085e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/419 @@ -0,0 +1 @@ +bsd-user dumps core for all binaries emulated diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/423 b/gitlab/issues_text/target_missing/host_missing/accel_missing/423 new file mode 100644 index 000000000..71a750c12 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/423 @@ -0,0 +1 @@ +NVME disk cannot be hotplugged after removal diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/424 b/gitlab/issues_text/target_missing/host_missing/accel_missing/424 new file mode 100644 index 000000000..166c5422b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/424 @@ -0,0 +1 @@ +the option for vdagent communication needed for qxl scren resizing is not documented diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/425 b/gitlab/issues_text/target_missing/host_missing/accel_missing/425 new file mode 100644 index 000000000..fc53354e3 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/425 @@ -0,0 +1 @@ +QEMU prepends pathnames to command lines of Multiboot kernels and modules, contrary to the specification diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/428 b/gitlab/issues_text/target_missing/host_missing/accel_missing/428 new file mode 100644 index 000000000..a81b09e59 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/428 @@ -0,0 +1 @@ +Windows: Very low network throughput with tap-netdev & virtio-serial diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/429 b/gitlab/issues_text/target_missing/host_missing/accel_missing/429 new file mode 100644 index 000000000..02a02c08a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/429 @@ -0,0 +1 @@ +Build failure on MacOS with Homebrew after upgrade diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/431 b/gitlab/issues_text/target_missing/host_missing/accel_missing/431 new file mode 100644 index 000000000..98e9e0856 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/431 @@ -0,0 +1 @@ +USB passthrough in Windows Host non functional diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/432 b/gitlab/issues_text/target_missing/host_missing/accel_missing/432 new file mode 100644 index 000000000..d3d9d649a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/432 @@ -0,0 +1 @@ +QAPI: Avoid generating empty source files diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/433 b/gitlab/issues_text/target_missing/host_missing/accel_missing/433 new file mode 100644 index 000000000..53e94bbde --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/433 @@ -0,0 +1 @@ +chardev: Windows stdio eats characters diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/434 b/gitlab/issues_text/target_missing/host_missing/accel_missing/434 new file mode 100644 index 000000000..5e0f5da13 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/434 @@ -0,0 +1 @@ +Mouse pointer disappears when it is over console window diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/436 b/gitlab/issues_text/target_missing/host_missing/accel_missing/436 new file mode 100644 index 000000000..ad8d15b9e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/436 @@ -0,0 +1 @@ +window 8 stuck during boot on Qemu diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/437 b/gitlab/issues_text/target_missing/host_missing/accel_missing/437 new file mode 100644 index 000000000..d8b52e190 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/437 @@ -0,0 +1 @@ +[AHCI] crash when running a GNU/Hurd guest diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/440 b/gitlab/issues_text/target_missing/host_missing/accel_missing/440 new file mode 100644 index 000000000..3950273c8 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/440 @@ -0,0 +1 @@ +/usr/share/applications/qemu.desktop should have an "Exec=" key. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/441 b/gitlab/issues_text/target_missing/host_missing/accel_missing/441 new file mode 100644 index 000000000..9e9e25105 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/441 @@ -0,0 +1 @@ +qemu-img: "Could not open backing image to determine size" when backing image is encrypted diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/445 b/gitlab/issues_text/target_missing/host_missing/accel_missing/445 new file mode 100644 index 000000000..84c4e8f6f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/445 @@ -0,0 +1 @@ +QEMU + DOS keyboard behavior diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/446 b/gitlab/issues_text/target_missing/host_missing/accel_missing/446 new file mode 100644 index 000000000..261a65943 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/446 @@ -0,0 +1 @@ +usb-audio does not work with Mac OS diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/450 b/gitlab/issues_text/target_missing/host_missing/accel_missing/450 new file mode 100644 index 000000000..fa56e5c55 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/450 @@ -0,0 +1 @@ +sdhci: Assertion wpnum < sd->wpgrps_size failed diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/451 b/gitlab/issues_text/target_missing/host_missing/accel_missing/451 new file mode 100644 index 000000000..7b0d52780 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/451 @@ -0,0 +1 @@ +sdhci: Heap-buffer-overflow in sdhci_read_dataport diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/453 b/gitlab/issues_text/target_missing/host_missing/accel_missing/453 new file mode 100644 index 000000000..505271470 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/453 @@ -0,0 +1,3 @@ +tests/acceptance: Allow to overwrite smp and memory values set by `avocado_qemu.LinuxTest` +Additional information: +Refer to the discussion in https://lore.kernel.org/qemu-devel/20210621080824.789274-1-eric.auger@redhat.com/ diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/455 b/gitlab/issues_text/target_missing/host_missing/accel_missing/455 new file mode 100644 index 000000000..4651c7170 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/455 @@ -0,0 +1,34 @@ +Pressing special keys (specially ctrl) sticks the key or makes it repeat the next key until ESC or Ctrl is pressed. +Description of problem: +Well, I'm using it in a daily basis, since it is my VM to isolate the environment for work. + +It was compiled from source for _jack_ support, the only thing that I cared about. I'll be honest : I don't remember the special parameters, nothing unusual though. I'm not in the need for _rt_ kernels. + +When I press `Ctrl` and sometimes when I press other special keys, one of the three options occur : +1. It repeats all the keys pressed next, like if I was pressing it for a long time. + - Example : `a` turns into `aaaaaaaaaaaaaaa...`(continues) + - It repeats until I press `Esc` or `Ctrl` again. +1. `Ctrl` continues as pressed and everything I type occurs with `Ctrl`. + - Example : `a` turns into `Ctrl-A` + - Probably caused by the previous option. +1. It does what is expected, like `Ctrl-C` +Steps to reproduce: +1. Run the specified config. +1. Test `Ctrl-C` + `Ctrl-V` using text editors. + - I think that using a graphical one is faster to see it happening. + - Examples + - Atom + - Eclipse + - Kate + - VsCode + - It also occurred using a _pty_ but since I generally use the _middle-mouse-button_ with _ptys_. + - I'm not aware of the frequency that it happens. + - It also occurs with the mouse (`Ctrl-mouseclick`). + - For example: instead of going to a _Firefox_'s tab, it selects it. + +I don't know any other step here, the use case is trivial coding. +Additional information: +- I have already tried to disable "keyboard repeat" in config. + - At first it seems to work but the `Ctrl` key can get stuck like in the description and then I'm unable to get out of it (everything is sent as if it was with `Ctrl`) without pressing `Ctrl`+`ESC`. I have no idea of why. + - The problem seems to occur less frequently. +- It also happened before setting up `qemu-guest-agent`. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/456 b/gitlab/issues_text/target_missing/host_missing/accel_missing/456 new file mode 100644 index 000000000..484667fe4 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/456 @@ -0,0 +1,29 @@ +Qemu User (x86_64) Hangs after futex function not implemented error +Description of problem: +Qemu User hangs on futex call with the following last strace +``` +futex(0x0000004001a01654,FUTEX_PRIVATE_FLAG|FUTEX_UNLOCK_PI,0,NULL,NULL,0) = -1 errno=38 (Function not implemented) +``` +This is the last call until giving a SIGINT with CTRL + C where the following strace is output +``` +futex(0x00000040b0085180,FUTEX_PRIVATE_FLAG|FUTEX_WAIT,2,NULL,NULL,0) = -1 errno=4 (Interrupted system call) +--- SIGINT {si_signo=SIGINT, si_code=SI_KERNEL, si_pid=0, si_uid=0} --- + +``` +Steps to reproduce: +1. Install steamcmd https://developer.valvesoftware.com/wiki/SteamCMD +2. In the steamcmd shell install Valheim dedicated server with `app_update 896660` +3. Navigate to the downloaded app `cd ~/Steam/steamapps/common/Valheim\ dedicated\ server/` +4. Run `qemu-x86_64 valheim_server.x86_64` +5. The process hangs as per description. +Additional information: +The issue was originally encountered on a raspberry pi ARM64 host using the ubuntu 5.2.0 version of qemu. Installed cross libararies: +* libc6-amd64-cross +* libgcc-s1-amd64-cross + +It was then replicated on the x86 host fedora with a build of the qemu master branch. +The full qemu -strace output is provided below +[qemu_strace_output.log](/uploads/96e0e31b1e63191a94d73f05023c5173/qemu_strace_output.log) + +The expected output found when running `strace ./valheim_server.x86_64` without qemu on the x86_64 host is attached below +[expected_output.log](/uploads/b3b25618103de8a3b9c0ef227bbffc9c/expected_output.log) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/458 b/gitlab/issues_text/target_missing/host_missing/accel_missing/458 new file mode 100644 index 000000000..730e31358 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/458 @@ -0,0 +1 @@ +Xfer:features:read truncating xml sent to gdb frontends diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/46 b/gitlab/issues_text/target_missing/host_missing/accel_missing/46 new file mode 100644 index 000000000..0b5054d2d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/46 @@ -0,0 +1 @@ +Investigate suitibility of GitLab Issue Tracker for QEMU diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/460 b/gitlab/issues_text/target_missing/host_missing/accel_missing/460 new file mode 100644 index 000000000..52c311eb2 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/460 @@ -0,0 +1 @@ +vmxnet3: Assertion failure in eth_setup_ip4_fragmentation diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/462 b/gitlab/issues_text/target_missing/host_missing/accel_missing/462 new file mode 100644 index 000000000..b03cf0a1d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/462 @@ -0,0 +1,43 @@ +mirror: the block-job-cancel command can put qemu to the endless error loop +Description of problem: +If the destination VM will crash (or network is down) right before the completion of the block device mirroring job (`block-job-cancel`), then there will be a possibility to put QEMU in the error loop. +Steps to reproduce: +1. Run both QEMU VMs: source + target. +2. On the target side prepare NBD server for blockdev mirroring process by using QMP commands similar to the one below: +``` +{"execute": "nbd-server-start", "arguments": { "addr": { "data": { "host": "::", "port": "49153" }, "type": "inet" } } } +{ "execute": "nbd-server-add", "arguments": { "device": "drive_main01", "writable": true } } +``` +3. On the source side, prepare VM for the migration and start driver mirror job: +``` +{"execute":"migrate-set-capabilities","arguments":{"capabilities":[{"capability":"pause-before-switchover","state":true}]}} +{ "execute": "drive-mirror", "arguments": { "device": "drive_main01", "mode": "existing", "job-id": "job0", "target": "nbd:127.0.0.1:49153:exportname=drive_main01", "sync": "top", "on-source-error": "stop", "on-target-error": "stop", "format": "raw", "speed": 0 } } +``` +4. On the source side wait for the `BLOCK_JOB_READY` event: +``` +{"timestamp": {"seconds": 1625586327, "microseconds": 833805}, "event": "BLOCK_JOB_READY", "data": {"device": "job0", "len": 21474836480, "offset": 21474836480, "speed": 0, "type": "mirror"}} +``` +5. Start migration on the source side: +``` +{ "execute": "migrate", "arguments": { "uri": "tcp:127.0.0.1:8091" } } +``` +6. Wait for the `pre-switchover` state of the migration: +``` +{ "execute": "query-migrate" } +{"return": {"expected-downtime": 300, "status": "pre-switchover", "setup-time": 3, "total-time": 11343, "ram": {"total": 8725020672, "postcopy-requests": 0, "dirty-sync-count": 2, "multifd-bytes": 0, "pages-per-second": 39550, "page-size": 4096, "remaining": 2871296, "mbps": 1073.7734399999999, "transferred": 963647065, "duplicate": 1899491, "dirty-pages-rate": 84, "skipped": 0, "normal-bytes": 944705536, "normal": 230641}}} +``` +7. Kill target QEMU to reproduce an issue. +8. Cancel the job on the source side: +``` +{ "execute": "block-job-cancel", "arguments": { "device": "job0" } } +``` + +Got the endless errror loop: +``` +... +{"timestamp": {"seconds": 1625586487, "microseconds": 413847}, "event": "BLOCK_JOB_ERROR", "data": {"device": "job0", "operation": "write", "action": "stop"}} +{"timestamp": {"seconds": 1625586487, "microseconds": 413865}, "event": "BLOCK_JOB_ERROR", "data": {"device": "job0", "operation": "write", "action": "stop"}} +{"timestamp": {"seconds": 1625586487, "microseconds": 413885}, "event": "BLOCK_JOB_ERROR", "data": {"device": "job0", "operation": "write", "action": "stop"}} +... +``` +Source qemu could be stopped only by using SIGKILL. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/463 b/gitlab/issues_text/target_missing/host_missing/accel_missing/463 new file mode 100644 index 000000000..e91a06a3b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/463 @@ -0,0 +1,25 @@ +[Build][git]Build process stop in libqemuutil.a.p/qobject_json-streamer.c.o +Description of problem: +Hello. + +I tried qemu to get build with revision 9aef0954195cc592e86846dbbe7f3c2c5603690a but it stops really quick at task 238/9335. + +Here is the beginning of the error log: + +``` +[238/9335] Compiling C object libqemuutil.a.p/qobject_json-streamer.c.o +FAILED: libqemuutil.a.p/qobject_json-streamer.c.o +cc -Ilibqemuutil.a.p -I. -I.. -Isubprojects/libvhost-user -I../subprojects/libvhost-user -Itrace -Iqapi -Iui -Iui/shader -I/usr/include/p11-kit-1 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gio-unix-2.0 -I/usr/include/pixman-1 -fdiagnostics-color=auto -pipe -Wall -Winvalid-pch -std=gnu11 -O2 -g -isystem /build/qemu-git/src/qemu/linux-headers -isystem linux-headers -iquote . -iquote /build/qemu-git/src/qemu -iquote /build/qemu-git/src/qemu/include -iquote /build/qemu-git/src/qemu/disas/libvixl -iquote /build/qemu-git/src/qemu/tcg/i386 -pthread -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -m64 -mcx16 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fno-common -fwrapv -Wold-style-declaration -Wold-style-definition -Wtype-limits -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body -Wnested-externs -Wendif-labels -Wexpansion-to-defined -Wimplicit-fallthrough=2 -Wno-missing-include-dirs -Wno-shift-negative-value -Wno-psabi -fstack-protector-strong -march=x86-64 -mtune=generic -O2 -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -fPIC -MD -MQ libqemuutil.a.p/qobject_json-streamer.c.o -MF libqemuutil.a.p/qobject_json-streamer.c.o.d -o libqemuutil.a.p/qobject_json-streamer.c.o -c ../qobject/json-streamer.c +In file included from ../qobject/json-streamer.c:14: +/build/qemu-git/src/qemu/include/qemu/osdep.h:259:58: error: operator '&&' has no right operand + 259 | #if defined(HAVE_BROKEN_SIZE_MAX) && HAVE_BROKEN_SIZE_MAX + | +``` +Steps to reproduce: +1. Grab qemu-git code at commit 9aef0954195cc592e86846dbbe7f3c2c5603690a +2. use these configure options: --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libexecdir=/usr/lib/qemu --smbd=/usr/bin/smbd --enable-modules --enable-sdl --disable-werror --enable-vhost-user --enable-slirp=system --enable-xfsctl --audio-drv-list="pa alsa sdl" +3. run building process. +Additional information: +Attaching full build log. + +I'm using gcc 11.1.0. My last complete build was based on commit 9bef7ea9 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/464 b/gitlab/issues_text/target_missing/host_missing/accel_missing/464 new file mode 100644 index 000000000..2803cae62 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/464 @@ -0,0 +1 @@ +The virtio disk shows offline when try to install windows version v6.0.5 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/465 b/gitlab/issues_text/target_missing/host_missing/accel_missing/465 new file mode 100644 index 000000000..ea8e837ee --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/465 @@ -0,0 +1,7 @@ +Support network virtualization for Macos Big Sur+ +Additional information: +The following implementation are already submitted as a patch and they seem to work well on my mbp 2019 Big Sur. The only prob is that the qemu-system command should be run as root. + +[https://patchwork.kernel.org/project/qemu-devel/list/?series=502533](https://patchwork.kernel.org/project/qemu-devel/list/?series=502533) + +[https://patchwork.kernel.org/project/qemu-devel/patch/20210708054451.9374-1-akihiko.odaki@gmail.com/](https://patchwork.kernel.org/project/qemu-devel/patch/20210708054451.9374-1-akihiko.odaki@gmail.com/) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/469 b/gitlab/issues_text/target_missing/host_missing/accel_missing/469 new file mode 100644 index 000000000..11313a5ed --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/469 @@ -0,0 +1 @@ +SB16 audio playback freezes emulation in Windows 95 guest diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/471 b/gitlab/issues_text/target_missing/host_missing/accel_missing/471 new file mode 100644 index 000000000..55f186f95 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/471 @@ -0,0 +1,64 @@ +Clipboard sharing with `qemu_vdagent` does not work with SDL backend +Description of problem: +Clipboard sharing doesn't work: qemu does not send clipboard-grab messages when selecting on the host, nor does it respond to clipboard-grab messages from the guest. +Steps to reproduce: +1. Start QEMU with `qemu_vdagent` and `-display sdl` +2. Try to copy on the host or the guest +3. Observe that the clipboard is not shared +Additional information: +It appears as though `vdagent_clipboard_notify` function is not called. + +Logs: + +With SDL: +``` +vdagent_open +vdagent_recv_chunk size 28 +vdagent_recv_msg msg announce-capabilities, size 8 +vdagent_peer_cap cap mouse-state +vdagent_peer_cap cap monitors-config +vdagent_peer_cap cap reply +vdagent_peer_cap cap clipboard-by-demand +vdagent_peer_cap cap clipboard-selection +vdagent_peer_cap cap sparse-monitors-config +vdagent_peer_cap cap guest-lineend-lf +vdagent_peer_cap cap max-clipboard +vdagent_peer_cap cap audio-volume-sync +vdagent_send msg announce-capabilities +# tried to copy on host -- nothing happens here. +# trying to copy on guest: +vdagent_recv_chunk size 28 +vdagent_recv_msg msg clipboard-grab, size 8 +vdagent_cb_grab_selection selection clipboard +vdagent_cb_grab_type type text +# no response sent +``` +With GTK: +``` +vdagent_open +vdagent_recv_chunk size 28 +vdagent_recv_msg msg announce-capabilities, size 8 +vdagent_peer_cap cap mouse-state +vdagent_peer_cap cap monitors-config +vdagent_peer_cap cap reply +vdagent_peer_cap cap clipboard-by-demand +vdagent_peer_cap cap clipboard-selection +vdagent_peer_cap cap sparse-monitors-config +vdagent_peer_cap cap guest-lineend-lf +vdagent_peer_cap cap max-clipboard +vdagent_peer_cap cap audio-volume-sync +vdagent_send msg announce-capabilities +# trying to copy on host: +vdagent_send msg clipboard-grab +vdagent_recv_chunk size 28 +vdagent_recv_msg msg clipboard-request, size 8 +vdagent_send msg clipboard +vdagent_recv_chunk size 28 +# trying to copy on guest: +vdagent_recv_msg msg clipboard-grab, size 8 +vdagent_cb_grab_selection selection clipboard +vdagent_cb_grab_type type text +vdagent_send msg clipboard-request +vdagent_recv_chunk size 29 +vdagent_recv_msg msg clipboard, size 9 +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/473 b/gitlab/issues_text/target_missing/host_missing/accel_missing/473 new file mode 100644 index 000000000..eebf94a5b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/473 @@ -0,0 +1 @@ +QEMU 6.0.0 - NSIS installer script issues diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/474 b/gitlab/issues_text/target_missing/host_missing/accel_missing/474 new file mode 100644 index 000000000..71be4a68b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/474 @@ -0,0 +1,30 @@ +[build][git]Build process stops while linking qemu-aarch64_be in util/async.c:426 +Description of problem: +Looks like this is a followup of bug #463. Even if this bug is fixed, build process breaks later. + +This time, build process is stop while processing linking qemu-aarch64_be, really late at step 6492/9511. + +Error log start with: + +``` +[6492/9511] Linking target qemu-aarch64_be +FAILED: qemu-aarch64_be +``` + +And later I can read: + +``` +/usr/bin/ld: libqemuutil.a(util_async.c.o): in function `aio_setup_linux_io_uring': +/build/qemu-git/src/qemu/build-full/../util/async.c:421: undefined reference to `luring_init' +/usr/bin/ld: /build/qemu-git/src/qemu/build-full/../util/async.c:426: undefined reference to `luring_attach_aio_context' +/usr/bin/ld: libqemuutil.a(util_async.c.o): in function `aio_ctx_finalize': +/build/qemu-git/src/qemu/build-full/../util/async.c:334: undefined reference to `luring_detach_aio_context' +/usr/bin/ld: /build/qemu-git/src/qemu/build-full/../util/async.c:335: undefined reference to `luring_cleanup' +collect2: error: ld returned 1 exit status +``` +Steps to reproduce: +1. Grab source code at commit bd38ae2 +2. use these configure options: --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libexecdir=/usr/lib/qemu --smbd=/usr/bin/smbd --enable-modules --enable-sdl --disable-werror --enable-vhost-user --enable-slirp=system --enable-xfsctl --audio-drv-list="pa alsa sdl" +3. Launch build process. +Additional information: +Adding building process log.[qemu-git-13_6.0.0.r2577.gbd38ae26ce-1-x86_64-build.log](/uploads/419d2323799aad3a0f4a7719ce123f35/qemu-git-13_6.0.0.r2577.gbd38ae26ce-1-x86_64-build.log) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/476 b/gitlab/issues_text/target_missing/host_missing/accel_missing/476 new file mode 100644 index 000000000..411933c06 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/476 @@ -0,0 +1 @@ +QEMU with x86-64 EFI disk image and 'nographic' option crashes WSL2 window diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/479 b/gitlab/issues_text/target_missing/host_missing/accel_missing/479 new file mode 100644 index 000000000..c6564eb53 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/479 @@ -0,0 +1,12 @@ +qemu-6.0.0: Assertion 'p_rcu_reader->depth != 0' failed +Description of problem: +assertion failure: +``` +qemu-system-aarch64: /home/aileen/Downloads/qemu-6.0.0/include/qemu/rcu.h:93: rcu_read_unlock: Assertion `p_rcu_reader->depth != 0' failed. +``` +Steps to reproduce: +1. You cannot +2. unless I give +3. you the ELF file. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/48 b/gitlab/issues_text/target_missing/host_missing/accel_missing/48 new file mode 100644 index 000000000..52fafa183 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/48 @@ -0,0 +1 @@ +Hover effect color for "Full list of releases" button is low contrast diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/480 b/gitlab/issues_text/target_missing/host_missing/accel_missing/480 new file mode 100644 index 000000000..2c4dbec21 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/480 @@ -0,0 +1 @@ +Supported ARMv8.? Opcodes diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/483 b/gitlab/issues_text/target_missing/host_missing/accel_missing/483 new file mode 100644 index 000000000..1b3cf7ae4 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/483 @@ -0,0 +1,25 @@ +qemu doesn't process -object secret when read from a config file +Description of problem: +Qemu doesn't process -object secret lines when read from a config file. This results in the new spice password-secret option failing with error: No secret with id '\<theid\>' +Steps to reproduce: +1. Create a password file +``` +printf "password" > passfile.pw +``` +2. Start qemu with command line options and also write to a config file +``` +qemu-system-x86_64 \ + -object secret,id=spicepwd,format=raw,file=passfile.pw \ + -spice port=5901,password-secret=spicepwd \ + -writeconfig qemu.cfg +``` +3. Optional: Connect using spice client and password: "password" +4. Exit qemu and cat qemu.cfg and verify it looks okay with equivalent options to what was specified on the command line +5. Now attempt to start qemu and read the options using the config file +``` +qemu-system-x86_64 -readconfig qemu.cfg +``` +6. This fails with an error: +``` +qemu-system-x86_64: No secret with id 'spicepwd' +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/484 b/gitlab/issues_text/target_missing/host_missing/accel_missing/484 new file mode 100644 index 000000000..64adaac5b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/484 @@ -0,0 +1 @@ +6.1 Regression: machine pflash parsing diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/486 b/gitlab/issues_text/target_missing/host_missing/accel_missing/486 new file mode 100644 index 000000000..41042bd3b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/486 @@ -0,0 +1 @@ +/dev/input/mouse0: is not an evdev device diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/487 b/gitlab/issues_text/target_missing/host_missing/accel_missing/487 new file mode 100644 index 000000000..3e3e0e14b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/487 @@ -0,0 +1 @@ +sdhci: out of bounds read on sd->sd_status diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/488 b/gitlab/issues_text/target_missing/host_missing/accel_missing/488 new file mode 100644 index 000000000..bd17cb17c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/488 @@ -0,0 +1,30 @@ +[git]Virt-Manager cannot start any previously created virtual machine with Qemu commit bd306cfe: 'spicevmc' is not a valid char driver name +Description of problem: +With qemu built on commit bd306cfe, I'm unable to start a previously created VM. + +Because of both bug #463 and #474 I was blocked from building qemu from git for something like a week or so. My last built and working Qemu is based on commit 9bef7ea9d9. + +Doing a git bissect won't be an easy task :( +Steps to reproduce: +1. Build qemu using commit bd306cfe +2. Launch Virt-Manager +3. Try to launch a previously created VM or try to boot a new one. +Additional information: +Every single time I tried to launch a VM, I get a dialog box with this error message: + +``` +Error starting domain: internal error: qemu unexpectedly closed the monitor: 2021-07-18T07:56:50.116480Z qemu-system-x86_64: -chardev spicevmc,id=charchannel1,name=vdagent: 'spicevmc' is not a valid char driver name + +Traceback (most recent call last): + File "/usr/share/virt-manager/virtManager/asyncjob.py", line 65, in cb_wrapper + callback(asyncjob, *args, **kwargs) + File "/usr/share/virt-manager/virtManager/asyncjob.py", line 101, in tmpcb + callback(*args, **kwargs) + File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 57, in newfn + ret = fn(self, *args, **kwargs) + File "/usr/share/virt-manager/virtManager/object/domain.py", line 1329, in startup + self._backend.create() + File "/usr/lib/python3.9/site-packages/libvirt.py", line 1353, in create + raise libvirtError('virDomainCreate() failed') +libvirt.libvirtError: internal error: qemu unexpectedly closed the monitor: 2021-07-18T07:56:50.116480Z qemu-system-x86_64: -chardev spicevmc,id=charchannel1,name=vdagent: 'spicevmc' is not a valid char driver name +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/49 b/gitlab/issues_text/target_missing/host_missing/accel_missing/49 new file mode 100644 index 000000000..37b311875 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/49 @@ -0,0 +1 @@ +[Feature request] MDIO bus diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/490 b/gitlab/issues_text/target_missing/host_missing/accel_missing/490 new file mode 100644 index 000000000..b93e97e9e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/490 @@ -0,0 +1,829 @@ +Compilation FAILED: libblock.fa.p/block_vpc.c.o +Description of problem: +Compilation failed +Steps to reproduce: +``` +git checkout v5.2.0 +./configure --target-list=riscv64-softmmu +make +``` +Additional information: +``` +changing dir to build for make ""... +make[1]: Entering directory '/home/peterlin/Labs/riscv64-linux/qemu/build' +/usr/bin/ninja build.ninja && touch build.ninja.stamp +ninja: no work to do. +/usr/bin/meson introspect --targets --tests --benchmarks | /usr/bin/python3 -B scripts/mtest2make.py > Makefile.mtest + AS multiboot.o + AS linuxboot.o + CC linuxboot_dma.o + AS pvh.o + AS kvmvapic.o + BUILD linuxboot.img + BUILD kvmvapic.img + CC pvh_main.o + BUILD multiboot.img + BUILD linuxboot_dma.img +ld: Error: unable to disambiguate: -no-pie (did you mean --no-pie ?) +make[2]: *** [Makefile:57: kvmvapic.img] Error 1 +make[2]: *** Waiting for unfinished jobs.... +ld: Error: unable to disambiguate: -no-pie (did you mean --no-pie ?) +make[2]: *** [Makefile:57: linuxboot.img] Error 1 +ld: Error: unable to disambiguate: -no-pie (did you mean --no-pie ?) +ld: Error: unable to disambiguate: -no-pie (did you mean --no-pie ?) +make[2]: *** [Makefile:57: multiboot.img] Error 1 +make[2]: *** [Makefile:57: linuxboot_dma.img] Error 1 +make[1]: *** [Makefile:206: pc-bios/optionrom/all] Error 2 +make[1]: *** Waiting for unfinished jobs.... +[1/2124] Compiling C object libcapstone.a.p/capstone_MCInstrDesc.c.o +[2/2124] Compiling C object libcapstone.a.p/capstone_MCRegisterInfo.c.o +[3/2124] Compiling C object libcapstone.a.p/capstone_arch_X86_X86Module.c.o +[4/2124] Compiling C object libcapstone.a.p/capstone_SStream.c.o +[5/2124] Compiling C object libcapstone.a.p/capstone_arch_X86_X86InstPrinterCommon.c.o +[6/2124] Compiling C object libcapstone.a.p/capstone_utils.c.o +[7/2124] Compiling C object libcapstone.a.p/capstone_MCInst.c.o +[8/2124] Compiling C object libcapstone.a.p/capstone_cs.c.o +[9/2124] Generating qemu-version.h with a custom command (wrapped by meson to capture output) +[10/2124] Generating hmp-commands.h with a custom command (wrapped by meson to capture output) +[11/2124] Generating qemu-img-cmds.h with a custom command (wrapped by meson to capture output) +[12/2124] Generating hmp-commands-info.h with a custom command (wrapped by meson to capture output) +[13/2124] Generating qemu-options.def with a custom command (wrapped by meson to capture output) +[14/2124] Compiling C object contrib/libvhost-user/libvhost-user.a.p/libvhost-user-glib.c.o +[15/2124] Compiling C object libcapstone.a.p/capstone_arch_X86_X86Disassembler.c.o +[16/2124] Generating trace-hw_audio.h with a custom command (wrapped by meson to capture output) +[17/2124] Generating trace-hw_9pfs.h with a custom command (wrapped by meson to capture output) +[18/2124] Generating trace-hw_audio.c with a custom command (wrapped by meson to capture output) +[19/2124] Generating trace-hw_block_dataplane.h with a custom command (wrapped by meson to capture output) +[20/2124] Compiling C object libcapstone.a.p/capstone_arch_X86_X86ATTInstPrinter.c.o +[21/2124] Generating trace-hw_block.c with a custom command (wrapped by meson to capture output) +[22/2124] Generating trace-hw_block.h with a custom command (wrapped by meson to capture output) +[23/2124] Compiling C object libcapstone.a.p/capstone_arch_X86_X86IntelInstPrinter.c.o +[24/2124] Generating trace-hw_arm.h with a custom command (wrapped by meson to capture output) +[25/2124] Generating trace-hw_alpha.c with a custom command (wrapped by meson to capture output) +[26/2124] Generating trace-hw_arm.c with a custom command (wrapped by meson to capture output) +[27/2124] Compiling C object contrib/libvhost-user/libvhost-user.a.p/libvhost-user.c.o +[28/2124] Linking static target contrib/libvhost-user/libvhost-user.a +[29/2124] Generating trace-hw_char.c with a custom command (wrapped by meson to capture output) +[30/2124] Generating trace-hw_9pfs.c with a custom command (wrapped by meson to capture output) +[31/2124] Generating trace-hw_block_dataplane.c with a custom command (wrapped by meson to capture output) +[32/2124] Generating trace-hw_char.h with a custom command (wrapped by meson to capture output) +[33/2124] Compiling C object libcapstone.a.p/capstone_arch_X86_X86Mapping.c.o +[34/2124] Generating trace-hw_alpha.h with a custom command (wrapped by meson to capture output) +[35/2124] Generating trace-hw_acpi.c with a custom command (wrapped by meson to capture output) +[36/2124] Generating trace-hw_acpi.h with a custom command (wrapped by meson to capture output) +[37/2124] Generating trace-accel_kvm.h with a custom command (wrapped by meson to capture output) +[38/2124] Generating trace-root.c with a custom command (wrapped by meson to capture output) +[39/2124] Generating trace-accel_tcg.h with a custom command (wrapped by meson to capture output) +[40/2124] Generating trace-accel_kvm.c with a custom command (wrapped by meson to capture output) +[41/2124] Generating trace-crypto.h with a custom command (wrapped by meson to capture output) +[42/2124] Generating trace-accel_tcg.c with a custom command (wrapped by meson to capture output) +[43/2124] Generating trace-crypto.c with a custom command (wrapped by meson to capture output) +[44/2124] Generating trace-authz.c with a custom command (wrapped by meson to capture output) +[45/2124] Generating trace-authz.h with a custom command (wrapped by meson to capture output) +[46/2124] Generating trace-monitor.h with a custom command (wrapped by meson to capture output) +[47/2124] Generating trace-monitor.c with a custom command (wrapped by meson to capture output) +[48/2124] Compiling C object libcapstone.a.p/capstone_arch_X86_X86DisassemblerDecoder.c.o +[49/2124] Linking static target libcapstone.a +[50/2124] Generating trace-root.h with a custom command (wrapped by meson to capture output) +[51/2124] Generating trace-block.h with a custom command (wrapped by meson to capture output) +[52/2124] Generating trace-hw_watchdog.h with a custom command (wrapped by meson to capture output) +[53/2124] Generating trace-hw_virtio.c with a custom command (wrapped by meson to capture output) +[54/2124] Generating trace-hw_watchdog.c with a custom command (wrapped by meson to capture output) +[55/2124] Generating trace-block.c with a custom command (wrapped by meson to capture output) +[56/2124] Generating trace-io.c with a custom command (wrapped by meson to capture output) +[57/2124] Generating trace-nbd.h with a custom command (wrapped by meson to capture output) +[58/2124] Generating trace-nbd.c with a custom command (wrapped by meson to capture output) +[59/2124] Generating trace-io.h with a custom command (wrapped by meson to capture output) +[60/2124] Generating trace-scsi.h with a custom command (wrapped by meson to capture output) +[61/2124] Generating trace-scsi.c with a custom command (wrapped by meson to capture output) +[62/2124] Generating trace-audio.h with a custom command (wrapped by meson to capture output) +[63/2124] Generating trace-backends.h with a custom command (wrapped by meson to capture output) +[64/2124] Generating trace-backends.c with a custom command (wrapped by meson to capture output) +[65/2124] Generating trace-audio.c with a custom command (wrapped by meson to capture output) +[66/2124] Generating trace-backends_tpm.h with a custom command (wrapped by meson to capture output) +[67/2124] Generating trace-backends_tpm.c with a custom command (wrapped by meson to capture output) +[68/2124] Generating shared QAPI source files with a custom command +[69/2124] Generating trace-chardev.h with a custom command (wrapped by meson to capture output) +[70/2124] Generating trace-chardev.c with a custom command (wrapped by meson to capture output) +[71/2124] Generating trace-hw_display.h with a custom command (wrapped by meson to capture output) +[72/2124] Generating trace-hw_display.c with a custom command (wrapped by meson to capture output) +[73/2124] Generating trace-hw_dma.h with a custom command (wrapped by meson to capture output) +[74/2124] Generating trace-hw_dma.c with a custom command (wrapped by meson to capture output) +[75/2124] Generating trace-hw_hppa.h with a custom command (wrapped by meson to capture output) +[76/2124] Generating trace-hw_hppa.c with a custom command (wrapped by meson to capture output) +[77/2124] Generating trace-hw_hyperv.h with a custom command (wrapped by meson to capture output) +[78/2124] Generating trace-hw_hyperv.c with a custom command (wrapped by meson to capture output) +[79/2124] Generating trace-hw_i2c.h with a custom command (wrapped by meson to capture output) +[80/2124] Generating trace-hw_i386_xen.c with a custom command (wrapped by meson to capture output) +[81/2124] Generating trace-hw_i386.h with a custom command (wrapped by meson to capture output) +[82/2124] Generating trace-hw_i386.c with a custom command (wrapped by meson to capture output) +[83/2124] Generating trace-hw_i2c.c with a custom command (wrapped by meson to capture output) +[84/2124] Generating trace-hw_i386_xen.h with a custom command (wrapped by meson to capture output) +[85/2124] Generating trace-hw_ide.c with a custom command (wrapped by meson to capture output) +[86/2124] Generating trace-hw_ide.h with a custom command (wrapped by meson to capture output) +[87/2124] Generating trace-hw_input.h with a custom command (wrapped by meson to capture output) +[88/2124] Generating trace-hw_input.c with a custom command (wrapped by meson to capture output) +[89/2124] Generating trace-hw_isa.h with a custom command (wrapped by meson to capture output) +[90/2124] Generating trace-hw_intc.h with a custom command (wrapped by meson to capture output) +[91/2124] Generating trace-hw_intc.c with a custom command (wrapped by meson to capture output) +[92/2124] Generating trace-hw_mem.h with a custom command (wrapped by meson to capture output) +[93/2124] Generating trace-hw_mem.c with a custom command (wrapped by meson to capture output) +[94/2124] Generating trace-hw_isa.c with a custom command (wrapped by meson to capture output) +[95/2124] Generating trace-hw_misc.h with a custom command (wrapped by meson to capture output) +[96/2124] Generating trace-hw_mips.h with a custom command (wrapped by meson to capture output) +[97/2124] Generating trace-hw_mips.c with a custom command (wrapped by meson to capture output) +[98/2124] Generating trace-hw_misc.c with a custom command (wrapped by meson to capture output) +[99/2124] Generating trace-hw_misc_macio.c with a custom command (wrapped by meson to capture output) +[100/2124] Generating trace-hw_misc_macio.h with a custom command (wrapped by meson to capture output) +[101/2124] Generating trace-hw_net.h with a custom command (wrapped by meson to capture output) +[102/2124] Generating trace-hw_nvram.h with a custom command (wrapped by meson to capture output) +[103/2124] Generating trace-hw_net.c with a custom command (wrapped by meson to capture output) +[104/2124] Generating trace-hw_pci.h with a custom command (wrapped by meson to capture output) +[105/2124] Generating trace-hw_nvram.c with a custom command (wrapped by meson to capture output) +[106/2124] Generating trace-hw_pci_host.h with a custom command (wrapped by meson to capture output) +[107/2124] Generating trace-hw_pci.c with a custom command (wrapped by meson to capture output) +[108/2124] Generating trace-hw_pci_host.c with a custom command (wrapped by meson to capture output) +[109/2124] Generating trace-hw_ppc.h with a custom command (wrapped by meson to capture output) +[110/2124] Generating trace-hw_ppc.c with a custom command (wrapped by meson to capture output) +[111/2124] Generating trace-hw_rdma.c with a custom command (wrapped by meson to capture output) +[112/2124] Generating trace-hw_rdma_vmw.c with a custom command (wrapped by meson to capture output) +[113/2124] Generating trace-hw_rdma_vmw.h with a custom command (wrapped by meson to capture output) +[114/2124] Generating trace-hw_rdma.h with a custom command (wrapped by meson to capture output) +[115/2124] Generating trace-hw_rtc.h with a custom command (wrapped by meson to capture output) +[116/2124] Generating trace-hw_rtc.c with a custom command (wrapped by meson to capture output) +[117/2124] Generating trace-hw_s390x.c with a custom command (wrapped by meson to capture output) +[118/2124] Generating trace-hw_s390x.h with a custom command (wrapped by meson to capture output) +[119/2124] Generating trace-hw_scsi.c with a custom command (wrapped by meson to capture output) +[120/2124] Generating trace-hw_scsi.h with a custom command (wrapped by meson to capture output) +[121/2124] Generating trace-hw_sd.h with a custom command (wrapped by meson to capture output) +[122/2124] Generating trace-hw_sd.c with a custom command (wrapped by meson to capture output) +[123/2124] Generating trace-hw_sparc.h with a custom command (wrapped by meson to capture output) +[124/2124] Generating trace-hw_sparc64.c with a custom command (wrapped by meson to capture output) +[125/2124] Generating trace-hw_sparc.c with a custom command (wrapped by meson to capture output) +[126/2124] Generating trace-hw_sparc64.h with a custom command (wrapped by meson to capture output) +[127/2124] Generating trace-hw_ssi.h with a custom command (wrapped by meson to capture output) +[128/2124] Generating trace-hw_ssi.c with a custom command (wrapped by meson to capture output) +[129/2124] Generating trace-hw_timer.h with a custom command (wrapped by meson to capture output) +[130/2124] Generating trace-hw_timer.c with a custom command (wrapped by meson to capture output) +[131/2124] Generating trace-hw_tpm.h with a custom command (wrapped by meson to capture output) +[132/2124] Generating trace-hw_usb.h with a custom command (wrapped by meson to capture output) +[133/2124] Generating trace-hw_tpm.c with a custom command (wrapped by meson to capture output) +[134/2124] Generating trace-hw_usb.c with a custom command (wrapped by meson to capture output) +[135/2124] Generating trace-hw_vfio.c with a custom command (wrapped by meson to capture output) +[136/2124] Generating trace-hw_vfio.h with a custom command (wrapped by meson to capture output) +[137/2124] Generating trace-hw_xen.h with a custom command (wrapped by meson to capture output) +[138/2124] Generating trace-hw_virtio.h with a custom command (wrapped by meson to capture output) +[139/2124] Generating trace-hw_xen.c with a custom command (wrapped by meson to capture output) +[140/2124] Generating trace-hw_gpio.h with a custom command (wrapped by meson to capture output) +[141/2124] Generating trace-hw_gpio.c with a custom command (wrapped by meson to capture output) +[142/2124] Generating trace-migration.h with a custom command (wrapped by meson to capture output) +[143/2124] Generating trace-net.c with a custom command (wrapped by meson to capture output) +[144/2124] Generating trace-migration.c with a custom command (wrapped by meson to capture output) +[145/2124] Generating trace-softmmu.h with a custom command (wrapped by meson to capture output) +[146/2124] Generating trace-net.h with a custom command (wrapped by meson to capture output) +[147/2124] Generating trace-softmmu.c with a custom command (wrapped by meson to capture output) +[148/2124] Generating trace-ui.h with a custom command (wrapped by meson to capture output) +[149/2124] Generating trace-ui.c with a custom command (wrapped by meson to capture output) +[150/2124] Generating trace-hw_core.c with a custom command (wrapped by meson to capture output) +[151/2124] Generating trace-hw_core.h with a custom command (wrapped by meson to capture output) +[152/2124] Generating trace-qapi.h with a custom command (wrapped by meson to capture output) +[153/2124] Generating trace-qom.h with a custom command (wrapped by meson to capture output) +[154/2124] Generating trace-qapi.c with a custom command (wrapped by meson to capture output) +[155/2124] Generating trace-qom.c with a custom command (wrapped by meson to capture output) +[156/2124] Generating trace-target_arm.h with a custom command (wrapped by meson to capture output) +[157/2124] Generating trace-target_arm.c with a custom command (wrapped by meson to capture output) +[158/2124] Generating trace-target_hppa.h with a custom command (wrapped by meson to capture output) +[159/2124] Generating trace-target_hppa.c with a custom command (wrapped by meson to capture output) +[160/2124] Generating trace-target_i386.h with a custom command (wrapped by meson to capture output) +[161/2124] Generating trace-target_i386.c with a custom command (wrapped by meson to capture output) +[162/2124] Generating trace-target_mips.h with a custom command (wrapped by meson to capture output) +[163/2124] Generating trace-target_ppc.h with a custom command (wrapped by meson to capture output) +[164/2124] Generating trace-target_mips.c with a custom command (wrapped by meson to capture output) +[165/2124] Generating trace-target_ppc.c with a custom command (wrapped by meson to capture output) +[166/2124] Generating trace-target_riscv.h with a custom command (wrapped by meson to capture output) +[167/2124] Generating trace-target_riscv.c with a custom command (wrapped by meson to capture output) +[168/2124] Generating trace-target_s390x.h with a custom command (wrapped by meson to capture output) +[169/2124] Generating trace-target_s390x.c with a custom command (wrapped by meson to capture output) +[170/2124] Generating trace-target_sparc.h with a custom command (wrapped by meson to capture output) +[171/2124] Generating trace-util.h with a custom command (wrapped by meson to capture output) +[172/2124] Generating trace-target_sparc.c with a custom command (wrapped by meson to capture output) +[173/2124] Generating trace-util.c with a custom command (wrapped by meson to capture output) +[174/2124] Generating generated-helpers.c with a custom command (wrapped by meson to capture output) +[175/2124] Generating generated-tcg-tracers.h with a custom command (wrapped by meson to capture output) +[176/2124] Generating generated-helpers.h with a custom command (wrapped by meson to capture output) +[177/2124] Generating trace-events-all with a custom command (wrapped by meson to capture output) +[178/2124] Generating generated-helpers-wrappers.h with a custom command (wrapped by meson to capture output) +[179/2124] Generating input-keymap-linux-to-qcode.c.inc with a custom command (wrapped by meson to capture output) +[180/2124] Generating input-keymap-qcode-to-atset1.c.inc with a custom command (wrapped by meson to capture output) +[181/2124] Generating input-keymap-qcode-to-atset2.c.inc with a custom command (wrapped by meson to capture output) +[182/2124] Generating input-keymap-atset1-to-qcode.c.inc with a custom command (wrapped by meson to capture output) +[183/2124] Generating input-keymap-qcode-to-linux.c.inc with a custom command (wrapped by meson to capture output) +[184/2124] Generating input-keymap-qcode-to-qnum.c.inc with a custom command (wrapped by meson to capture output) +[185/2124] Generating input-keymap-qcode-to-atset3.c.inc with a custom command (wrapped by meson to capture output) +[186/2124] Generating input-keymap-qcode-to-sun.c.inc with a custom command (wrapped by meson to capture output) +[187/2124] Generating input-keymap-qnum-to-qcode.c.inc with a custom command (wrapped by meson to capture output) +[188/2124] Generating input-keymap-win32-to-qcode.c.inc with a custom command (wrapped by meson to capture output) +[189/2124] Generating input-keymap-usb-to-qcode.c.inc with a custom command (wrapped by meson to capture output) +[190/2124] Generating module_block.h with a custom command +[191/2124] Generating block-gen.c with a custom command +[192/2124] Compiling C object tests/fp/libsoftfloat.a.p/berkeley-softfloat-3_source_f128_lt_quiet.c.o +[193/2124] Compiling C object tests/fp/libsoftfloat.a.p/berkeley-softfloat-3_source_f128_isSignalingNaN.c.o +[194/2124] Compiling C object tests/fp/libsoftfloat.a.p/berkeley-softfloat-3_source_f128M_to_i64.c.o +[195/2124] Compiling C object tests/fp/libsoftfloat.a.p/berkeley-softfloat-3_source_f128M_to_ui32.c.o +[196/2124] Compiling C object tests/fp/libsoftfloat.a.p/berkeley-softfloat-3_source_f128M_to_ui64.c.o +[197/2124] Compiling C object tests/fp/libsoftfloat.a.p/berkeley-softfloat-3_source_f128M_to_i32.c.o +[198/2124] Generating 'libqemu-riscv64-softmmu.fa.p/decode-insn16.c.inc'. +[199/2124] Generating input-keymap-xorgevdev-to-qcode.c.inc with a custom command (wrapped by meson to capture output) +[200/2124] Generating input-keymap-xorgxwin-to-qcode.c.inc with a custom command (wrapped by meson to capture output) +[201/2124] Generating texture-blit-frag.h with a custom command (wrapped by meson to capture output) +[202/2124] Generating texture-blit-vert.h with a custom command (wrapped by meson to capture output) +[203/2124] Generating input-keymap-xorgxquartz-to-qcode.c.inc with a custom command (wrapped by meson to capture output) +[204/2124] Generating input-keymap-xorgkbd-to-qcode.c.inc with a custom command (wrapped by meson to capture output) +[205/2124] Generating 'libqemu-riscv64-softmmu.fa.p/decode-insn32.c.inc'. +[206/2124] Generating input-keymap-x11-to-qcode.c.inc with a custom command (wrapped by meson to capture output) +[207/2124] Generating QGA QAPI files with a custom command +[208/2124] Generating bepo with a custom command +[209/2124] Generating input-keymap-osx-to-qcode.c.inc with a custom command (wrapped by meson to capture output) +[210/2124] Generating ar with a custom command +[211/2124] Generating cz with a custom command +[212/2124] Generating texture-blit-flip-vert.h with a custom command (wrapped by meson to capture output) +[213/2124] Generating de with a custom command +[214/2124] Generating da with a custom command +[215/2124] Compiling C object contrib/elf2dmp/elf2dmp.p/download.c.o +[216/2124] Compiling C object contrib/elf2dmp/elf2dmp.p/addrspace.c.o +[217/2124] Compiling C object contrib/elf2dmp/elf2dmp.p/qemu_elf.c.o +[218/2124] Compiling C object contrib/ivshmem-client/ivshmem-client.p/main.c.o +[219/2124] Compiling C object contrib/elf2dmp/elf2dmp.p/pdb.c.o +[220/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-types-qdev.c.o +[221/2124] Compiling C object libqemuutil.a.p/stubs_ram-block.c.o +[222/2124] Generating riscv64-softmmu-gdbstub-xml.c with a custom command (wrapped by meson to capture output) +[223/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-types-acpi.c.o +[224/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-visit-acpi.c.o +[225/2124] Compiling C object contrib/ivshmem-client/ivshmem-client.p/ivshmem-client.c.o +[226/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-commands-acpi.c.o +[227/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-events-acpi.c.o +[228/2124] Compiling C object contrib/elf2dmp/elf2dmp.p/main.c.o +[229/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-events-authz.c.o +[230/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-builtin-types.c.o +[231/2124] Generating QAPI files for qemu-storage-daemon with a custom command +[232/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-events-audio.c.o +[233/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_mips.c.o +[234/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-builtin-visit.c.o +[235/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-types-audio.c.o +[236/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-types-authz.c.o +[237/2124] Compiling C object libblock.fa.p/block_qed-check.c.o +[238/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-commands-audio.c.o +[239/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-visit-authz.c.o +[240/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-types-misc.c.o +[241/2124] Compiling C object libqemu-riscv64-softmmu.fa.p/hw_virtio_vhost-user-input-pci.c.o +[242/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-visit-audio.c.o +[243/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-commands-block.c.o +[244/2124] Compiling C object libqemu-riscv64-softmmu.fa.p/hw_virtio_vhost-vsock-common.c.o +[245/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-block.c.o +[246/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-commands-authz.c.o +[247/2124] Compiling C object libqemu-riscv64-softmmu.fa.p/hw_virtio_virtio-input-host-pci.c.o +[248/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-types-block.c.o +[249/2124] Compiling C object libblock.fa.p/block_qed-cluster.c.o +[250/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-authz.c.o +[251/2124] Compiling C object libblock.fa.p/block_qed-l2-cache.c.o +[252/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-events-block.c.o +[253/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-types-block-export.c.o +[254/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-visit-misc.c.o +[255/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-visit-block.c.o +[256/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-events-block-export.c.o +[257/2124] Compiling C object libqemu-riscv64-softmmu.fa.p/hw_virtio_virtio-rng-pci.c.o +[258/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-types-char.c.o +[259/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-events-char.c.o +[260/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-events-block-core.c.o +[261/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-commands-block-export.c.o +[262/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-visit-block-export.c.o +[263/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-types-common.c.o +[264/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-events-common.c.o +[265/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-commands-common.c.o +[266/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-visit-common.c.o +[267/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-commands-char.c.o +[268/2124] Compiling C object libqemuutil.a.p/util_getauxval.c.o +[269/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-visit-char.c.o +[270/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-types-control.c.o +[271/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-types-block-core.c.o +[272/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-visit-control.c.o +[273/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-events-control.c.o +[274/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-commands-block-core.c.o +[275/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-commands-control.c.o +[276/2124] Compiling C object libqemu-riscv64-softmmu.fa.p/hw_virtio_vhost-user-vsock-pci.c.o +[277/2124] Compiling C object libqemuutil.a.p/util_uuid.c.o +[278/2124] Compiling C object libqemu-riscv64-softmmu.fa.p/hw_virtio_vhost-user-blk-pci.c.o +[279/2124] Compiling C object libqemuutil.a.p/util_rcu.c.o +[280/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-events-crypto.c.o +[281/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-types-crypto.c.o +[282/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-commands-crypto.c.o +[283/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-events-dump.c.o +[284/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-events-error.c.o +[285/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-types-dump.c.o +[286/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-visit-dump.c.o +[287/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-types-error.c.o +[288/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-commands-dump.c.o +[289/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-visit-error.c.o +[290/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-commands-error.c.o +[291/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-events-introspect.c.o +[292/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-types-introspect.c.o +[293/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-commands-introspect.c.o +[294/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-visit-crypto.c.o +[295/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-types-job.c.o +[296/2124] Compiling C object libqemuutil.a.p/stubs_cpu-get-clock.c.o +[297/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-events-job.c.o +[298/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-visit-job.c.o +[299/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-commands-job.c.o +[300/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-events-machine.c.o +[301/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-events-misc.c.o +[302/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-types-migration.c.o +[303/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-visit-introspect.c.o +[304/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-events-migration.c.o +[305/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-types-machine.c.o +[306/2124] Compiling C object libqemu-riscv64-softmmu.fa.p/hw_virtio_virtio-balloon-pci.c.o +[307/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-crypto.c.o +[308/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-commands-machine.c.o +[309/2124] Compiling C object libqemuutil.a.p/util_crc32c.c.o +[310/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-monitor.c.o +[311/2124] Compiling C object libqemu-riscv64-softmmu.fa.p/hw_virtio_virtio-9p-pci.c.o +[312/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-commands-migration.c.o +[313/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-visit-migration.c.o +[314/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-types-pragma.c.o +[315/2124] Compiling C object libqemu-riscv64-softmmu.fa.p/hw_virtio_vhost-scsi-pci.c.o +[316/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-events-net.c.o +[317/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-visit-pragma.c.o +[318/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-types-net.c.o +[319/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-commands-net.c.o +[320/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-events-pragma.c.o +[321/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-commands-pragma.c.o +[322/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-commands-misc.c.o +[323/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-events-qdev.c.o +[324/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-visit-qdev.c.o +[325/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-types-qom.c.o +[326/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-types-pci.c.o +[327/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-commands-qdev.c.o +[328/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-visit-net.c.o +[329/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-events-qom.c.o +[330/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-events-pci.c.o +[331/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-commands-pci.c.o +[332/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-visit-machine.c.o +[333/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-types-rdma.c.o +[334/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-visit-rocker.c.o +[335/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-commands-rdma.c.o +[336/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-visit-rdma.c.o +[337/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-visit-qom.c.o +[338/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-visit-pci.c.o +[339/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-commands-qom.c.o +[340/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-events-rdma.c.o +[341/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-types-replay.c.o +[342/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-events-replay.c.o +[343/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-visit-replay.c.o +[344/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-commands-replay.c.o +[345/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-types-rocker.c.o +[346/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-events-rocker.c.o +[347/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-commands-run-state.c.o +[348/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-commands-rocker.c.o +[349/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-types-run-state.c.o +[350/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-types-sockets.c.o +[351/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-events-sockets.c.o +[352/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-commands-sockets.c.o +[353/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-events-run-state.c.o +[354/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-events-tpm.c.o +[355/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-types-tpm.c.o +[356/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-visit-run-state.c.o +[357/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-visit-trace.c.o +[358/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-events-trace.c.o +[359/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-commands-tpm.c.o +[360/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-visit-sockets.c.o +[361/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-types-trace.c.o +[362/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-visit-tpm.c.o +[363/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-types-transaction.c.o +[364/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-commands-trace.c.o +[365/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-events-transaction.c.o +[366/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-events-ui.c.o +[367/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-commands-transaction.c.o +[368/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-types-ui.c.o +[369/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-root.c.o +[370/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-accel_kvm.c.o +[371/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-visit-transaction.c.o +[372/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-commands-ui.c.o +[373/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-accel_tcg.c.o +[374/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-nbd.c.o +[375/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-audio.c.o +[376/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-io.c.o +[377/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-scsi.c.o +[378/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-backends.c.o +[379/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-chardev.c.o +[380/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-backends_tpm.c.o +[381/2124] Compiling C object libblock.fa.p/block_dmg-bz2.c.o +[382/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_9pfs.c.o +[383/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_acpi.c.o +[384/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_alpha.c.o +[385/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_audio.c.o +[386/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_block_dataplane.c.o +[387/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_arm.c.o +[388/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_char.c.o +[389/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_block.c.o +[390/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_hyperv.c.o +[391/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_dma.c.o +[392/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_display.c.o +[393/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_i2c.c.o +[394/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-visit-ui.c.o +[395/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_hppa.c.o +[396/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_ide.c.o +[397/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_i386_xen.c.o +[398/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_i386.c.o +[399/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_input.c.o +[400/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_mem.c.o +[401/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_isa.c.o +[402/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_nvram.c.o +[403/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_intc.c.o +[404/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_misc_macio.c.o +[405/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_misc.c.o +[406/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_pci_host.c.o +[407/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_pci.c.o +[408/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_ppc.c.o +[409/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_rdma.c.o +[410/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_rdma_vmw.c.o +[411/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_net.c.o +[412/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_s390x.c.o +[413/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_rtc.c.o +[414/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_sparc.c.o +[415/2124] Compiling C object libqemuutil.a.p/meson-generated_.._qapi_qapi-visit-block-core.c.o +[416/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_sd.c.o +[417/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_timer.c.o +[418/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_sparc64.c.o +[419/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_scsi.c.o +[420/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_tpm.c.o +[421/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_ssi.c.o +[422/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_virtio.c.o +[423/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_xen.c.o +[424/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_vfio.c.o +[425/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_usb.c.o +[426/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_watchdog.c.o +[427/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_gpio.c.o +[428/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-ui.c.o +[429/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-qapi.c.o +[430/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-net.c.o +[431/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-softmmu.c.o +[432/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-hw_core.c.o +[433/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-migration.c.o +[434/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-qom.c.o +[435/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-target_arm.c.o +[436/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-target_hppa.c.o +[437/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-target_mips.c.o +[438/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-target_i386.c.o +[439/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-target_riscv.c.o +[440/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-target_ppc.c.o +[441/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-util.c.o +[442/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-target_s390x.c.o +[443/2124] Compiling C object libqemuutil.a.p/meson-generated_.._trace_trace-target_sparc.c.o +[444/2124] Compiling C object libqemuutil.a.p/qapi_qapi-dealloc-visitor.c.o +[445/2124] Compiling C object libqemuutil.a.p/qapi_qapi-util.c.o +[446/2124] Compiling C object libqemuutil.a.p/qapi_qapi-clone-visitor.c.o +[447/2124] Compiling C object libqemuutil.a.p/qapi_qmp-event.c.o +[448/2124] Compiling C object libqemuutil.a.p/qapi_opts-visitor.c.o +[449/2124] Compiling C object libqemuutil.a.p/qapi_qmp-dispatch.c.o +[450/2124] Compiling C object libqemuutil.a.p/qobject_qnull.c.o +[451/2124] Compiling C object libqemuutil.a.p/qapi_qobject-output-visitor.c.o +[452/2124] Compiling C object libqemuutil.a.p/qapi_qmp-registry.c.o +[453/2124] Compiling C object libqemuutil.a.p/qapi_string-input-visitor.c.o +[454/2124] Compiling C object libqemuutil.a.p/qobject_qstring.c.o +[455/2124] Compiling C object libqemuutil.a.p/qobject_qnum.c.o +[456/2124] Compiling C object libqemuutil.a.p/qapi_string-output-visitor.c.o +[457/2124] Compiling C object libqemuutil.a.p/qobject_qobject.c.o +[458/2124] Compiling C object libqemuutil.a.p/qobject_qbool.c.o +[459/2124] Compiling C object libqemuutil.a.p/qapi_qapi-visit-core.c.o +[460/2124] Compiling C object libqemuutil.a.p/qobject_qlist.c.o +[461/2124] Compiling C object libqemuutil.a.p/qapi_qobject-input-visitor.c.o +[462/2124] Compiling C object libqemuutil.a.p/qobject_qlit.c.o +[463/2124] Compiling C object libqemuutil.a.p/qobject_json-lexer.c.o +[464/2124] Compiling C object libqemuutil.a.p/qobject_qdict.c.o +[465/2124] Compiling C object libqemuutil.a.p/qobject_qjson.c.o +[466/2124] Compiling C object libqemuutil.a.p/util_unicode.c.o +[467/2124] Compiling C object libqemuutil.a.p/qobject_json-streamer.c.o +[468/2124] Compiling C object libqemuutil.a.p/util_qemu-timer-common.c.o +[469/2124] Compiling C object libqemuutil.a.p/util_fdmon-poll.c.o +[470/2124] Compiling C object libqemuutil.a.p/qobject_json-parser.c.o +[471/2124] Compiling C object libqemuutil.a.p/util_compatfd.c.o +[472/2124] Compiling C object libqemuutil.a.p/util_event_notifier-posix.c.o +[473/2124] Compiling C object libqemuutil.a.p/util_fdmon-epoll.c.o +[474/2124] Compiling C object libqemuutil.a.p/util_qemu-openpty.c.o +[475/2124] Compiling C object libqemuutil.a.p/qobject_block-qdict.c.o +[476/2124] Compiling C object libqemuutil.a.p/util_mmap-alloc.c.o +[477/2124] Compiling C object libqemuutil.a.p/util_fdmon-io_uring.c.o +[478/2124] Compiling C object libqemuutil.a.p/util_osdep.c.o +[479/2124] Compiling C object libqemuutil.a.p/util_module.c.o +[480/2124] Compiling C object libqemuutil.a.p/util_cutils.c.o +[481/2124] Compiling C object libqemuutil.a.p/util_host-utils.c.o +[482/2124] Compiling C object libqemuutil.a.p/util_memfd.c.o +[483/2124] Compiling C object libqemuutil.a.p/util_envlist.c.o +[484/2124] Compiling C object libqemuutil.a.p/util_path.c.o +[485/2124] Compiling C object libqemuutil.a.p/util_aio-posix.c.o +[486/2124] Compiling C object libqemuutil.a.p/util_fifo8.c.o +[487/2124] Compiling C object libqemuutil.a.p/util_bitops.c.o +[488/2124] Compiling C object libqemuutil.a.p/util_cacheinfo.c.o +[489/2124] Compiling C object libqemuutil.a.p/util_qemu-thread-posix.c.o +[490/2124] Compiling C object libqemuutil.a.p/util_id.c.o +[491/2124] Compiling C object libqemuutil.a.p/util_qemu-print.c.o +[492/2124] Compiling C object libqemuutil.a.p/util_oslib-posix.c.o +[493/2124] Compiling C object libqemuutil.a.p/util_error.c.o +[494/2124] Compiling C object libqemuutil.a.p/util_notify.c.o +[495/2124] Compiling C object libqemuutil.a.p/util_qemu-progress.c.o +[496/2124] Compiling C object libqemuutil.a.p/util_bitmap.c.o +[497/2124] Compiling C object libqemuutil.a.p/util_qemu-error.c.o +[498/2124] Compiling C object libqemuutil.a.p/util_keyval.c.o +[499/2124] Compiling C object libqemu-riscv64-softmmu.fa.p/hw_virtio_virtio-input-pci.c.o +[500/2124] Compiling C object libqemuutil.a.p/util_qemu-config.c.o +[501/2124] Compiling C object libqemuutil.a.p/util_pagesize.c.o +[502/2124] Compiling C object libqemuutil.a.p/util_log.c.o +[503/2124] Compiling C object libqemuutil.a.p/util_range.c.o +[504/2124] Compiling C object libqemuutil.a.p/util_drm.c.o +[505/2124] Compiling C object libqemuutil.a.p/util_stats64.c.o +[506/2124] Compiling C object libqemuutil.a.p/util_qdist.c.o +[507/2124] Compiling C object libqemuutil.a.p/util_systemd.c.o +[508/2124] Compiling C object libqemuutil.a.p/util_aiocb.c.o +[509/2124] Compiling C object libblock.fa.p/block_dmg.c.o +[510/2124] Compiling C object libqemuutil.a.p/util_guest-random.c.o +[511/2124] Compiling C object libqemuutil.a.p/util_base64.c.o +[512/2124] Compiling C object libqemuutil.a.p/util_qht.c.o +[513/2124] Compiling C object libqemuutil.a.p/util_aio-wait.c.o +[514/2124] Compiling C object libqemuutil.a.p/util_async.c.o +[515/2124] Compiling C object libqemuutil.a.p/util_qemu-option.c.o +[516/2124] Compiling C object libqemuutil.a.p/util_dbus.c.o +[517/2124] Compiling C object libqemuutil.a.p/util_qsp.c.o +[518/2124] Compiling C object libqemuutil.a.p/util_hexdump.c.o +[519/2124] Compiling C object libblock.fa.p/block_curl.c.o +[520/2124] Compiling C object libqemuutil.a.p/util_coroutine-ucontext.c.o +[521/2124] Compiling C object libqemuutil.a.p/util_buffer.c.o +[522/2124] Compiling C object libqemuutil.a.p/util_iova-tree.c.o +[523/2124] Compiling C object libqemuutil.a.p/util_main-loop.c.o +[524/2124] Compiling C object libqemuutil.a.p/util_qemu-coroutine-io.c.o +[525/2124] Compiling C object libqemuutil.a.p/util_lockcnt.c.o +[526/2124] Compiling C object libqemuutil.a.p/util_nvdimm-utils.c.o +[527/2124] Compiling C object libqemuutil.a.p/util_qemu-coroutine.c.o +[528/2124] Compiling C object libqemuutil.a.p/util_iov.c.o +[529/2124] Compiling C object libqemuutil.a.p/util_hbitmap.c.o +[530/2124] Compiling C object libqemuutil.a.p/util_qemu-coroutine-sleep.c.o +[531/2124] Compiling C object libqemuutil.a.p/util_bufferiszero.c.o +[532/2124] Compiling C object libqemuutil.a.p/util_qemu-coroutine-lock.c.o +[533/2124] Compiling C object libqemuutil.a.p/util_block-helpers.c.o +[534/2124] Compiling C object libqemuutil.a.p/util_qemu-co-shared-resource.c.o +[535/2124] Compiling C object libqemuutil.a.p/util_vhost-user-server.c.o +[536/2124] Compiling C object libqemuutil.a.p/util_qemu-sockets.c.o +[537/2124] Compiling C object libqemuutil.a.p/util_timed-average.c.o +[538/2124] Compiling C object libqemuutil.a.p/crypto_random-gnutls.c.o +[539/2124] Compiling C object libqemuutil.a.p/crypto_init.c.o +[540/2124] Compiling C object libqemuutil.a.p/util_filemonitor-inotify.c.o +[541/2124] Compiling C object libqemuutil.a.p/util_readline.c.o +[542/2124] Compiling C object libqemuutil.a.p/util_thread-pool.c.o +[543/2124] Compiling C object libqemuutil.a.p/stubs_arch_type.c.o +[544/2124] Compiling C object libqemuutil.a.p/util_qemu-timer.c.o +[545/2124] Compiling C object libqemuutil.a.p/crypto_aes.c.o +[546/2124] Compiling C object libqemuutil.a.p/trace_qmp.c.o +[547/2124] Compiling C object libqemuutil.a.p/util_throttle.c.o +[548/2124] Compiling C object libqemuutil.a.p/util_uri.c.o +[549/2124] Compiling C object libqemuutil.a.p/stubs_blockdev-close-all-bdrv-states.c.o +[550/2124] Compiling C object libqemuutil.a.p/stubs_bdrv-next-monitor-owned.c.o +[551/2124] Compiling C object libqemuutil.a.p/stubs_blk-exp-close-all.c.o +[552/2124] Compiling C object libqemuutil.a.p/stubs_change-state-handler.c.o +[553/2124] Compiling C object libqemuutil.a.p/stubs_blk-commit-all.c.o +[554/2124] Compiling C object libqemuutil.a.p/stubs_cpus-get-virtual-clock.c.o +[555/2124] Compiling C object libqemuutil.a.p/stubs_cmos.c.o +[556/2124] Compiling C object libqemuutil.a.p/stubs_qemu-timer-notify-cb.c.o +[557/2124] Compiling C object libqemuutil.a.p/stubs_dump.c.o +[558/2124] Compiling C object libqemuutil.a.p/trace_control.c.o +[559/2124] Compiling C object libqemuutil.a.p/util_vfio-helpers.c.o +[560/2124] Compiling C object libqemuutil.a.p/stubs_error-printf.c.o +[561/2124] Compiling C object libqemuutil.a.p/stubs_gdbstub.c.o +[562/2124] Compiling C object libqemuutil.a.p/stubs_icount.c.o +[563/2124] Compiling C object libqemuutil.a.p/stubs_io_uring.c.o +[564/2124] Compiling C object libqemuutil.a.p/stubs_iothread.c.o +[565/2124] Compiling C object libqemuutil.a.p/stubs_get-vm-name.c.o +[566/2124] Compiling C object libqemuutil.a.p/stubs_fw_cfg.c.o +[567/2124] Compiling C object libqemuutil.a.p/stubs_is-daemonized.c.o +[568/2124] Compiling C object libqemuutil.a.p/stubs_iothread-lock.c.o +[569/2124] Compiling C object libqemuutil.a.p/stubs_fdset.c.o +[570/2124] Compiling C object libqemuutil.a.p/stubs_machine-init-done.c.o +[571/2124] Compiling C object libqemuutil.a.p/stubs_migr-blocker.c.o +[572/2124] Compiling C object libqemuutil.a.p/stubs_linux-aio.c.o +[573/2124] Compiling C object libqemuutil.a.p/stubs_isa-bus.c.o +[574/2124] Compiling C object libqemuutil.a.p/stubs_runstate-check.c.o +[575/2124] Compiling C object libqemuutil.a.p/stubs_qtest.c.o +[576/2124] Compiling C object libqemuutil.a.p/stubs_monitor.c.o +[577/2124] Compiling C object libqemuutil.a.p/stubs_ramfb.c.o +[578/2124] Compiling C object libqemuutil.a.p/stubs_pci-bus.c.o +[579/2124] Compiling C object libqemuutil.a.p/stubs_qmp_memory_device.c.o +[580/2124] Compiling C object libqemuutil.a.p/stubs_monitor-core.c.o +[581/2124] Compiling C object libqemuutil.a.p/stubs_sysbus.c.o +[582/2124] Compiling C object libqemuutil.a.p/stubs_pci-host-piix.c.o +[583/2124] Compiling C object libqemuutil.a.p/stubs_replay.c.o +[584/2124] Compiling C object libqemuutil.a.p/stubs_target-monitor-defs.c.o +[585/2124] Compiling C object libqemuutil.a.p/stubs_set-fd-handler.c.o +[586/2124] Compiling C object libqemuutil.a.p/stubs_target-get-monitor-def.c.o +[587/2124] Compiling C object libqemuutil.a.p/stubs_tpm.c.o +[588/2124] Compiling C object libqemuutil.a.p/stubs_trace-control.c.o +[589/2124] Compiling C object libqemuutil.a.p/stubs_uuid.c.o +[590/2124] Compiling C object libqemuutil.a.p/stubs_vmstate.c.o +[591/2124] Compiling C object libqemuutil.a.p/stubs_vm-stop.c.o +[592/2124] Compiling C object libqemuutil.a.p/stubs_win32-kbd-hook.c.o +[593/2124] Compiling C object libcommon.fa.p/hw_net_rocker_rocker_of_dpa.c.o +[594/2124] Compiling C object libqemuutil.a.p/stubs_vmgenid.c.o +[595/2124] Compiling C object libqemu-riscv64-softmmu.fa.p/target_riscv_cpu.c.o +[596/2124] Compiling C object libqemuutil.a.p/stubs_cpu-synchronize-state.c.o +[597/2124] Compiling C object libqemuutil.a.p/stubs_replay-tools.c.o +[598/2124] Compiling C object libqemu-riscv64-softmmu.fa.p/target_riscv_fpu_helper.c.o +[599/2124] Compiling C object libqemu-riscv64-softmmu.fa.p/target_riscv_csr.c.o +[600/2124] Compiling C object libqemuutil.a.p/stubs_semihost.c.o +[601/2124] Compiling C object tests/qtest/libqos/libqos.fa.p/qos_external.c.o +[602/2124] Compiling C object fsdev/virtfs-proxy-helper.p/9p-marshal.c.o +[603/2124] Compiling C object libqemuutil.a.p/stubs_xen-hw-stub.c.o +[604/2124] Compiling C object fsdev/virtfs-proxy-helper.p/9p-iov-marshal.c.o +[605/2124] Compiling C object fsdev/virtfs-proxy-helper.p/virtfs-proxy-helper.c.o +[606/2124] Compiling C object tests/qtest/libqos/libqos.fa.p/malloc-spapr.c.o +[607/2124] Compiling C object tests/qtest/libqos/libqos.fa.p/libqos.c.o +[608/2124] Compiling C object tests/qtest/libqos/libqos.fa.p/malloc.c.o +[609/2124] Linking static target libqemuutil.a +[610/2124] Compiling C object tests/qtest/libqos/libqos.fa.p/rtas.c.o +[611/2124] Compiling C object tests/qtest/libqos/libqos.fa.p/fw_cfg.c.o +[612/2124] Compiling C object tests/qtest/libqos/libqos.fa.p/libqos-spapr.c.o +[613/2124] Compiling C object tests/qtest/libqos/libqos.fa.p/qgraph.c.o +[614/2124] Compiling C object tests/qtest/libqos/libqos.fa.p/pci.c.o +[615/2124] Linking target fsdev/virtfs-proxy-helper +[616/2124] Compiling C object tests/qtest/libqos/libqos.fa.p/pci-spapr.c.o +[617/2124] Compiling C object tests/qtest/libqos/libqos.fa.p/malloc-pc.c.o +[618/2124] Compiling C object tests/qtest/libqos/libqos.fa.p/libqos-pc.c.o +[619/2124] Compiling C object tests/qtest/libqos/libqos.fa.p/usb.c.o +[620/2124] Compiling C object tests/qtest/libqos/libqos.fa.p/pci-pc.c.o +[621/2124] Compiling C object tests/qtest/libqos/libqos.fa.p/e1000e.c.o +[622/2124] Compiling C object libqemu-riscv64-softmmu.fa.p/target_riscv_cpu_helper.c.o +[623/2124] Compiling C object tests/qtest/libqos/libqos.fa.p/i2c.c.o +[624/2124] Compiling C object tests/qtest/libqos/libqos.fa.p/i2c-omap.c.o +[625/2124] Compiling C object tests/qtest/libqos/libqos.fa.p/i2c-imx.c.o +[626/2124] Compiling C object tests/qtest/libqos/libqos.fa.p/tpci200.c.o +[627/2124] Compiling C object tests/qtest/libqos/libqos.fa.p/.._libqtest.c.o +[628/2124] Compiling C object tests/qtest/libqos/libqos.fa.p/virtio-balloon.c.o +[629/2124] Compiling C object tests/qtest/libqos/libqos.fa.p/virtio-9p.c.o +[630/2124] Compiling C object tests/qtest/libqos/libqos.fa.p/virtio-blk.c.o +[631/2124] Compiling C object tests/qtest/libqos/libqos.fa.p/sdhci.c.o +[632/2124] Compiling C object tests/qtest/libqos/libqos.fa.p/virtio-mmio.c.o +[633/2124] Compiling C object tests/qtest/libqos/libqos.fa.p/virtio-rng.c.o +[634/2124] Compiling C object tests/qtest/libqos/libqos.fa.p/aarch64-xlnx-zcu102-machine.c.o +[635/2124] Compiling C object tests/qtest/libqos/libqos.fa.p/arm-imx25-pdk-machine.c.o +[636/2124] Compiling C object tests/qtest/libqos/libqos.fa.p/virtio-net.c.o +[637/2124] Compiling C object tests/qtest/libqos/libqos.fa.p/virtio-scsi.c.o +[638/2124] Compiling C object tests/qtest/libqos/libqos.fa.p/arm-n800-machine.c.o +[639/2124] Compiling C object tests/qtest/libqos/libqos.fa.p/virtio.c.o +[640/2124] Compiling C object tests/qtest/libqos/libqos.fa.p/virtio-serial.c.o +[641/2124] Compiling C object tests/qtest/libqos/libqos.fa.p/virtio-pci-modern.c.o +[642/2124] Compiling C object tests/qtest/libqos/libqos.fa.p/arm-smdkc210-machine.c.o +[643/2124] Compiling C object tests/qtest/libqos/libqos.fa.p/arm-raspi2-machine.c.o +[644/2124] Compiling C object tests/qtest/libqos/libqos.fa.p/arm-sabrelite-machine.c.o +[645/2124] Compiling C object tests/qtest/libqos/libqos.fa.p/arm-xilinx-zynq-a9-machine.c.o +[646/2124] Compiling C object tests/qtest/libqos/libqos.fa.p/virtio-pci.c.o +[647/2124] Compiling C object tests/qtest/libqos/libqos.fa.p/ppc64_pseries-machine.c.o +[648/2124] Compiling C object tests/qtest/libqos/libqos.fa.p/arm-virt-machine.c.o +[649/2124] Compiling C object tests/qtest/libqos/libqos.fa.p/x86_64_pc-machine.c.o +[650/2124] Compiling C object tests/qtest/libqos/libqos.fa.p/ahci.c.o +[651/2124] Compiling C object libqom.fa.p/qom_container.c.o +[652/2124] Compiling C object libauthz.fa.p/authz_base.c.o +[653/2124] Linking static target tests/qtest/libqos/libqos.fa +[654/2124] Compiling C object libqom.fa.p/qom_qom-qobject.c.o +[655/2124] Compiling C object libqom.fa.p/hw_nvram_fw_cfg-interface.c.o +[656/2124] Generating block.syms with a custom command (wrapped by meson to capture output) +[657/2124] Compiling C object libauthz.fa.p/authz_simple.c.o +[658/2124] Compiling C object libqom.fa.p/qom_object_interfaces.c.o +[659/2124] Compiling C object libauthz.fa.p/authz_list.c.o +[660/2124] Generating qemu.syms with a custom command (wrapped by meson to capture output) +[661/2124] Compiling C object libauthz.fa.p/authz_listfile.c.o +[662/2124] Compiling C object libauthz.fa.p/authz_pamacct.c.o +[663/2124] Linking static target libauthz.fa +[664/2124] Compiling C object libcrypto.fa.p/crypto_afsplit.c.o +[665/2124] Compiling C object libcrypto.fa.p/crypto_block-qcow.c.o +[666/2124] Compiling C object libcrypto.fa.p/crypto_hash.c.o +[667/2124] Compiling C object libcrypto.fa.p/crypto_ivgen-plain64.c.o +[668/2124] Compiling C object libcrypto.fa.p/crypto_block.c.o +[669/2124] Compiling C object libcrypto.fa.p/crypto_ivgen-essiv.c.o +[670/2124] Compiling C object libcrypto.fa.p/crypto_hmac.c.o +[671/2124] Compiling C object libcrypto.fa.p/crypto_ivgen-plain.c.o +[672/2124] Compiling C object libcrypto.fa.p/crypto_desrfb.c.o +[673/2124] Compiling C object libcrypto.fa.p/crypto_ivgen.c.o +[674/2124] Compiling C object libcrypto.fa.p/crypto_pbkdf.c.o +[675/2124] Compiling C object libcrypto.fa.p/crypto_secret.c.o +[676/2124] Compiling C object libcrypto.fa.p/crypto_tlscreds.c.o +[677/2124] Compiling C object libcrypto.fa.p/crypto_secret_common.c.o +[678/2124] Compiling C object libcrypto.fa.p/crypto_tlscredsanon.c.o +[679/2124] Compiling C object libcrypto.fa.p/crypto_hash-nettle.c.o +[680/2124] Compiling C object libcrypto.fa.p/crypto_tlscredspsk.c.o +[681/2124] Compiling C object libcrypto.fa.p/crypto_block-luks.c.o +[682/2124] Compiling C object libcrypto.fa.p/crypto_pbkdf-nettle.c.o +[683/2124] Compiling C object libcrypto.fa.p/crypto_secret_keyring.c.o +[684/2124] Compiling C object libcrypto.fa.p/crypto_tlscredsx509.c.o +[685/2124] Compiling C object libcrypto.fa.p/crypto_hmac-nettle.c.o +[686/2124] Compiling C object libio.fa.p/io_channel-command.c.o +[687/2124] Compiling C object libcrypto.fa.p/crypto_tlssession.c.o +[688/2124] Compiling C object libcrypto.fa.p/crypto_cipher.c.o +[689/2124] Compiling C object libcrypto.fa.p/crypto_tls-cipher-suites.c.o +[690/2124] Compiling C object libio.fa.p/io_channel-buffer.c.o +[691/2124] Compiling C object libmigration.fa.p/migration_page_cache.c.o +[692/2124] Compiling C object libio.fa.p/io_channel-util.c.o +[693/2124] Linking static target libcrypto.fa +[694/2124] Compiling C object libio.fa.p/io_channel-file.c.o +[695/2124] Compiling C object libio.fa.p/io_channel-watch.c.o +[696/2124] Compiling C object libqom.fa.p/qom_object.c.o +[697/2124] Compiling C object libio.fa.p/io_channel-tls.c.o +[698/2124] Linking static target libqom.fa +[699/2124] Compiling C object libio.fa.p/io_dns-resolver.c.o +[700/2124] Compiling C object libmigration.fa.p/migration_xbzrle.c.o +[701/2124] Compiling C object libio.fa.p/io_channel.c.o +[702/2124] Compiling C object libio.fa.p/io_task.c.o +[703/2124] Compiling C object libio.fa.p/io_channel-socket.c.o +[704/2124] Compiling C object libmigration.fa.p/migration_qemu-file-channel.c.o +[705/2124] Compiling C object libmigration.fa.p/migration_qjson.c.o +[706/2124] Compiling C object libio.fa.p/io_net-listener.c.o +[707/2124] Compiling C object libio.fa.p/io_channel-websock.c.o +[708/2124] Linking static target libio.fa +[709/2124] Compiling C object libblock.fa.p/replication.c.o +[710/2124] Compiling C object libmigration.fa.p/migration_vmstate.c.o +[711/2124] Compiling C object libmigration.fa.p/migration_vmstate-types.c.o +[712/2124] Compiling C object libblock.fa.p/meson-generated_.._block_block-gen.c.o +[713/2124] Compiling C object libmigration.fa.p/migration_qemu-file.c.o +[714/2124] Compiling C object libblock.fa.p/blockjob.c.o +[715/2124] Linking static target libmigration.fa +[716/2124] Compiling C object libblock.fa.p/nbd_common.c.o +[717/2124] Compiling C object libblock.fa.p/scsi_utils.c.o +[718/2124] Compiling C object libblock.fa.p/scsi_pr-manager.c.o +[719/2124] Compiling C object libblock.fa.p/block_aio_task.c.o +[720/2124] Compiling C object libblock.fa.p/block_nfs.c.o +[721/2124] Compiling C object libblock.fa.p/job.c.o +[722/2124] Compiling C object libblock.fa.p/block_amend.c.o +[723/2124] Compiling C object libblock.fa.p/scsi_pr-manager-helper.c.o +[724/2124] Compiling C object libblock.fa.p/block_accounting.c.o +[725/2124] Compiling C object libblock.fa.p/block_blklogwrites.c.o +[726/2124] Compiling C object libblock.fa.p/block_backup-top.c.o +[727/2124] Compiling C object libblock.fa.p/block_blkverify.c.o +[728/2124] Compiling C object libblock.fa.p/qemu-io-cmds.c.o +[729/2124] Compiling C object libblock.fa.p/block_backup.c.o +[730/2124] Compiling C object libblock.fa.p/block_commit.c.o +[731/2124] Compiling C object libblock.fa.p/nbd_client.c.o +[732/2124] Compiling C object libblock.fa.p/block_blkdebug.c.o +[733/2124] Compiling C object libblock.fa.p/block_create.c.o +[734/2124] Compiling C object libblock.fa.p/block_copy-on-read.c.o +[735/2124] Compiling C object libblock.fa.p/block_dirty-bitmap.c.o +[736/2124] Compiling C object libblock.fa.p/block_block-copy.c.o +[737/2124] Compiling C object libblock.fa.p/block_null.c.o +[738/2124] Compiling C object libblock.fa.p/block_filter-compress.c.o +[739/2124] Compiling C object libblock.fa.p/block_crypto.c.o +[740/2124] Compiling C object libblock.fa.p/block_qapi.c.o +[741/2124] Compiling C object libblock.fa.p/block_block-backend.c.o +[742/2124] Compiling C object libblock.fa.p/block_raw-format.c.o +[743/2124] Compiling C object libblock.fa.p/block_mirror.c.o +[744/2124] Compiling C object libblock.fa.p/block_snapshot.c.o +[745/2124] Compiling C object libblock.fa.p/block_qcow2-cache.c.o +[746/2124] Compiling C object libblock.fa.p/block_quorum.c.o +[747/2124] Compiling C object libblock.fa.p/block_nbd.c.o +[748/2124] Compiling C object libblock.fa.p/block_qcow2-bitmap.c.o +[749/2124] Compiling C object libblock.fa.p/block_throttle-groups.c.o +[750/2124] Compiling C object libblock.fa.p/block_qcow2-threads.c.o +[751/2124] Compiling C object libblock.fa.p/block_qcow2-snapshot.c.o +[752/2124] Compiling C object libblock.fa.p/block_cloop.c.o +[753/2124] Compiling C object libblock.fa.p/block_bochs.c.o +[754/2124] Compiling C object libblock.fa.p/block_vpc.c.o +FAILED: libblock.fa.p/block_vpc.c.o +cc -Ilibblock.fa.p -I. -I.. -Iqapi -Itrace -Iui -Iui/shader -Iblock -I/usr/include/libxml2 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -fdiagnostics-color=auto -Wall -Winvalid-pch -Werror -std=gnu99 -O2 -g -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -m64 -mcx16 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fno-common -fwrapv -Wold-style-declaration -Wold-style-definition -Wtype-limits -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body -Wnested-externs -Wendif-labels -Wexpansion-to-defined -Wno-missing-include-dirs -Wno-shift-negative-value -Wno-psabi -fstack-protector-strong -isystem /home/peterlin/Labs/riscv64-linux/qemu/linux-headers -isystem linux-headers -iquote /home/peterlin/Labs/riscv64-linux/qemu/tcg/i386 -iquote . -iquote /home/peterlin/Labs/riscv64-linux/qemu -iquote /home/peterlin/Labs/riscv64-linux/qemu/accel/tcg -iquote /home/peterlin/Labs/riscv64-linux/qemu/include -iquote /home/peterlin/Labs/riscv64-linux/qemu/disas/libvixl -pthread -fPIE -DHAVE_LIBSSH_0_8 -MD -MQ libblock.fa.p/block_vpc.c.o -MF libblock.fa.p/block_vpc.c.o.d -o libblock.fa.p/block_vpc.c.o -c ../block/vpc.c +../block/vpc.c: In function ‘vpc_open’: +../block/vpc.c:358:51: error: array subscript ‘VHDDynDiskHeader {aka struct vhd_dyndisk_header}[0]’ is partly outside array bounds of ‘uint8_t[512]’ {aka ‘unsigned char[512]’} [-Werror=array-bounds] + 358 | s->block_size = be32_to_cpu(dyndisk_header->block_size); + | ^~ +../block/vpc.c:223:13: note: while referencing ‘buf’ + 223 | uint8_t buf[HEADER_SIZE]; + | ^~~ +../block/vpc.c:366:58: error: array subscript ‘VHDDynDiskHeader {aka struct vhd_dyndisk_header}[0]’ is partly outside array bounds of ‘uint8_t[512]’ {aka ‘unsigned char[512]’} [-Werror=array-bounds] + 366 | s->max_table_entries = be32_to_cpu(dyndisk_header->max_table_entries); + | ^~ +../block/vpc.c:223:13: note: while referencing ‘buf’ + 223 | uint8_t buf[HEADER_SIZE]; + | ^~~ +../block/vpc.c:398:51: error: array subscript ‘VHDDynDiskHeader {aka struct vhd_dyndisk_header}[0]’ is partly outside array bounds of ‘uint8_t[512]’ {aka ‘unsigned char[512]’} [-Werror=array-bounds] + 398 | s->bat_offset = be64_to_cpu(dyndisk_header->table_offset); + | ^~ +../block/vpc.c:223:13: note: while referencing ‘buf’ + 223 | uint8_t buf[HEADER_SIZE]; + | ^~~ +cc1: all warnings being treated as errors +[755/2124] Compiling C object libblock.fa.p/block.c.o +[756/2124] Compiling C object libblock.fa.p/block_vhdx.c.o +[757/2124] Compiling C object libblock.fa.p/block_throttle.c.o +[758/2124] Compiling C object libblock.fa.p/block_vhdx-endian.c.o +[759/2124] Compiling C object libblock.fa.p/block_io.c.o +[760/2124] Compiling C object libblock.fa.p/block_qcow2-refcount.c.o +[761/2124] Compiling C object libblock.fa.p/block_qed-table.c.o +[762/2124] Compiling C object libblock.fa.p/block_qcow2-cluster.c.o +[763/2124] Compiling C object libblock.fa.p/block_vmdk.c.o +[764/2124] Compiling C object libblock.fa.p/block_qcow2.c.o +[765/2124] Compiling C object libblock.fa.p/block_vvfat.c.o +ninja: build stopped: subcommand failed. +make[1]: *** [Makefile:171: run-ninja] Error 1 +make[1]: Leaving directory '/home/peterlin/Labs/riscv64-linux/qemu/build' +make: *** [GNUmakefile:11: all] Error 2 +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/491 b/gitlab/issues_text/target_missing/host_missing/accel_missing/491 new file mode 100644 index 000000000..4d4e02fcc --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/491 @@ -0,0 +1 @@ +There is a code error here diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/492 b/gitlab/issues_text/target_missing/host_missing/accel_missing/492 new file mode 100644 index 000000000..78fc8460c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/492 @@ -0,0 +1,27 @@ +[git] "qemu-system-x86_64: Parameter 'drive' is missing" when I tried to launch an existing VM in Virt-Manager. +Description of problem: +This bug is related in some way to bug #488. + +I cannot start an existing virtual machine using qemu-git. +Additional information: +``` +internal error: process exited while connecting to monitor: 2021-07-19T19:24:27.044654Z qemu-system-x86_64: Parameter 'drive' is missing + +Traceback (most recent call last): + File "/usr/share/virt-manager/virtManager/asyncjob.py", line 65, in cb_wrapper + callback(asyncjob, *args, **kwargs) + File "/usr/share/virt-manager/virtManager/asyncjob.py", line 101, in tmpcb + callback(*args, **kwargs) + File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 57, in newfn + ret = fn(self, *args, **kwargs) + File "/usr/share/virt-manager/virtManager/object/domain.py", line 1329, in startup + self._backend.create() + File "/usr/lib/python3.9/site-packages/libvirt.py", line 1353, in create + raise libvirtError('virDomainCreate() failed') +libvirt.libvirtError: internal error: process exited while connecting to monitor: 2021-07-19T19:24:27.044654Z qemu-system-x86_64: Parameter 'drive' is missing + +``` + +My last working build was made using commit 9bef7ea9. Using Peter Maydell commits as milestone, I noticed commit 9aef0954 was the first showing the bug. + +I'll try to do bisect between these two commits and report asap. There is about 40 commits to verify. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/495 b/gitlab/issues_text/target_missing/host_missing/accel_missing/495 new file mode 100644 index 000000000..4a9ada740 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/495 @@ -0,0 +1 @@ +sdhci: Another way to trigger Assertion wpnum < sd->wpgrps_size failed diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/497 b/gitlab/issues_text/target_missing/host_missing/accel_missing/497 new file mode 100644 index 000000000..f5ef9574d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/497 @@ -0,0 +1,19 @@ +GVT-g + -spice error since qemu 6 +Description of problem: +It doesn't work: +``` +qemu-system-x86_64: The console requires display DMABUF support. +``` + +If I add `gl=on` to `-spice`, it reports: +``` +can't register two opengl displays (spice-egl, egl-headless) +``` +Steps to reproduce: +1. Setup an Intel GVT-g vGPU +2. Run the command +3. See the error +Additional information: +Before 6.0.0 it worked. + +Using VNC instead of SPICE works. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/498 b/gitlab/issues_text/target_missing/host_missing/accel_missing/498 new file mode 100644 index 000000000..5b24594bb --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/498 @@ -0,0 +1,42 @@ +Cannot focus QEMU window on macOS Big Sur (11.4) +Description of problem: +I'm not sure when the problem has been started, but I recently noticed that key inputs to QEMU window are not processed and the input goes other focused windows (e.g. terminal). QEMU window itself is shown but it looks like they are not focused. Also, the Dock icon for QEMU is also disappeared (it was displayed before). +Steps to reproduce: +1. build & install the latest qemu with `./configure --target-list=x86_64-softmmu` + - (`a146af86c8247f41b641783428b95ee71eb0e43f` was the revision I used) +2. run `qemu-system-x86_64` from terminal +3. click the QEMU window. + - Expected behavior: menu bar title will be switched to "QEMU", key inputs are handled by QEMU, Dock icon will be shown. + - Actual behavior: menu bar shows different app name that were focused before clicking the qemu, key inputs went to other app that was focused, dock icon is not showing up. +Additional information: +I tried to see if the events are delivered to QemuCocoaView by putting `NSLog(@"handleEventLocked: %@\n", event);` at the beginning of `handleEventLocked` @ `ui/cocoa.m`. It looks like the mouse events are delivered but not NSEventTypeKeyDown. + +(logs after clicked the QEMU window and type some 'a') +``` +$ qemu-system-x86_64 +2021-07-24 16:58:00.767 qemu-system-x86_64[3752:7837649] handleEventLocked: NSEvent: type=Kitdefined loc=(0,428) time=682409.7 flags=0 win=0x7fe2b5e48960 winNum=10355 ctxt=0x0 subtype=4 data1=1144258560 data2=1138098176 +2021-07-24 16:58:00.768 qemu-system-x86_64[3752:7837649] handleEventLocked: NSEvent: type=Kitdefined loc=(0,228) time=682409.7 flags=0 win=0x7fe2b5fb0ee0 winNum=10356 ctxt=0x0 subtype=4 data1=1137180672 data2=1130627072 +2021-07-24 16:58:06.462 qemu-system-x86_64[3752:7837649] handleEventLocked: NSEvent: type=Kitdefined loc=(0,428) time=682415.4 flags=0 win=0x7fe2b5e48960 winNum=10355 ctxt=0x0 subtype=9 data1=1129 data2=0 +2021-07-24 16:58:06.462 qemu-system-x86_64[3752:7837649] handleEventLocked: NSEvent: type=LMouseDown loc=(591.031,166.896) time=682415.4 flags=0 win=0x7fe2b5e48960 winNum=10355 ctxt=0x0 evNum=6096 click=1 buttonNumber=0 pressure=1 deviceID:0x0 subtype=0 +2021-07-24 16:58:06.462 qemu-system-x86_64[3752:7837649] handleEventLocked: NSEvent: type=Kitdefined loc=(0,0) time=0.0 flags=0 win=0x7fe2b5e48960 winNum=10355 ctxt=0x0 subtype=1 data1=1129 data2=0 +2021-07-24 16:58:06.487 qemu-system-x86_64[3752:7837649] handleEventLocked: NSEvent: type=Kitdefined loc=(0,428) time=682415.4 flags=0 win=0x7fe2b5e48960 winNum=10355 ctxt=0x0 subtype=22 data1=0 data2=0 +2021-07-24 16:58:06.487 qemu-system-x86_64[3752:7837649] handleEventLocked: NSEvent: type=Kitdefined loc=(0,428) time=682415.4 flags=0 win=0x7fe2b5e48960 winNum=10355 ctxt=0x0 subtype=23 data1=0 data2=0 +2021-07-24 16:58:06.565 qemu-system-x86_64[3752:7837649] handleEventLocked: NSEvent: type=LMouseUp loc=(591.031,166.896) time=682415.5 flags=0 win=0x7fe2b5e48960 winNum=10355 ctxt=0x0 evNum=6096 click=1 buttonNumber=0 pressure=0 deviceID:0x0 subtype=0 +2021-07-24 16:58:12.997 qemu-system-x86_64[3752:7837649] handleEventLocked: NSEvent: type=MouseEntered loc=(174.184,408.859) time=682421.9 flags=0 win=0x7fe2b5e48960 winNum=10355 ctxt=0x0 evNum=0 trackNum=7fe2b5e81d60 userData=0x0 +2021-07-24 16:58:13.013 qemu-system-x86_64[3752:7837649] handleEventLocked: NSEvent: type=MouseExited loc=(152.704,428.804) time=682422.0 flags=0 win=0x7fe2b5e48960 winNum=10355 ctxt=0x0 evNum=0 trackNum=7fe2b5e81d60 userData=0x0 +2021-07-24 16:58:24.181 qemu-system-x86_64[3752:7837649] handleEventLocked: NSEvent: type=Kitdefined loc=(0,428) time=682433.1 flags=0 win=0x7fe2b5e48960 winNum=10355 ctxt=0x0 subtype=9 data1=1131 data2=0 +2021-07-24 16:58:24.181 qemu-system-x86_64[3752:7837649] handleEventLocked: NSEvent: type=LMouseDown loc=(268.333,208.222) time=682433.1 flags=0 win=0x7fe2b5e48960 winNum=10355 ctxt=0x0 evNum=6098 click=1 buttonNumber=0 pressure=1 deviceID:0x0 subtype=0 +2021-07-24 16:58:24.262 qemu-system-x86_64[3752:7837649] handleEventLocked: NSEvent: type=LMouseUp loc=(268.333,208.222) time=682433.2 flags=0 win=0x7fe2b5e48960 winNum=10355 ctxt=0x0 evNum=6098 click=1 buttonNumber=0 pressure=0 deviceID:0x0 subtype=0 +2021-07-24 16:58:24.877 qemu-system-x86_64[3752:7837649] handleEventLocked: NSEvent: type=MouseEntered loc=(3.83252,400.359) time=682433.8 flags=0 win=0x7fe2b5e48960 winNum=10355 ctxt=0x0 evNum=0 trackNum=7fe2b5e81d60 userData=0x0 +2021-07-24 16:58:25.053 qemu-system-x86_64[3752:7837649] handleEventLocked: NSEvent: type=MouseEntered loc=(7.08813,408.091) time=682434.0 flags=0 win=0x7fe2b5e48960 winNum=10355 ctxt=0x0 evNum=0 trackNum=7fe295c0f090 userData=0x1 +2021-07-24 16:58:25.054 qemu-system-x86_64[3752:7837649] handleEventLocked: NSEvent: type=MouseEntered loc=(7.08813,408.091) time=682434.0 flags=0 win=0x7fe2b5e48960 winNum=10355 ctxt=0x0 evNum=0 trackNum=7fe2b5e80e30 userData=0x0 +2021-07-24 16:58:25.302 qemu-system-x86_64[3752:7837649] handleEventLocked: NSEvent: type=LMouseDown loc=(10.917,420.558) time=682434.2 flags=0 win=0x7fe2b5e48960 winNum=10355 ctxt=0x0 evNum=6099 click=1 buttonNumber=0 pressure=1 deviceID:0x0 subtype=0 +2021-07-24 16:58:25.365 qemu-system-x86_64[3752:7837649] handleEventLocked: NSEvent: type=LMouseUp loc=(10.917,420.558) time=682434.3 flags=0 win=0x7fe2b5e48960 winNum=10355 ctxt=0x0 evNum=6099 click=1 buttonNumber=0 pressure=0 deviceID:0x0 subtype=0 +2021-07-24 16:58:25.845 qemu-system-x86_64[3752:7837649] handleEventLocked: NSEvent: type=MouseExited loc=(11.9221,422.759) time=682434.8 flags=0 win=0x7fe2b5e48960 winNum=10355 ctxt=0x0 evNum=0 trackNum=7fe295c0f090 userData=0x1 +2021-07-24 16:58:25.846 qemu-system-x86_64[3752:7837649] handleEventLocked: NSEvent: type=MouseExited loc=(11.9221,422.759) time=682434.8 flags=0 win=0x7fe2b5e48960 winNum=10355 ctxt=0x0 evNum=0 trackNum=7fe2b5e80e30 userData=0x0 +2021-07-24 16:58:25.855 qemu-system-x86_64[3752:7837649] handleEventLocked: NSEvent: type=MouseExited loc=(14.2417,428.558) time=682434.8 flags=0 win=0x7fe2b5e48960 winNum=10355 ctxt=0x0 evNum=0 trackNum=7fe2b5e81d60 userData=0x0 + +``` + +Possibly related discussion on Apple Developer Forums: +- https://developer.apple.com/forums/thread/667004 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/50 b/gitlab/issues_text/target_missing/host_missing/accel_missing/50 new file mode 100644 index 000000000..aa4e17893 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/50 @@ -0,0 +1 @@ +Create PyPI installable package for the Python library diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/500 b/gitlab/issues_text/target_missing/host_missing/accel_missing/500 new file mode 100644 index 000000000..cdb65628f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/500 @@ -0,0 +1 @@ +6.1.0-rc0 Regression: Parameter 'audiodev' is missing diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/501 b/gitlab/issues_text/target_missing/host_missing/accel_missing/501 new file mode 100644 index 000000000..8ba77f6bc --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/501 @@ -0,0 +1 @@ +6.1.0-rc0 Regression: No keyboard input possible diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/502 b/gitlab/issues_text/target_missing/host_missing/accel_missing/502 new file mode 100644 index 000000000..e1f9dacea --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/502 @@ -0,0 +1 @@ +6.1.0-rc0 Regression: No mouse input possible diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/506 b/gitlab/issues_text/target_missing/host_missing/accel_missing/506 new file mode 100644 index 000000000..a12bcc0ac --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/506 @@ -0,0 +1 @@ +ga: auto-discover virtio port using sysfs diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/511 b/gitlab/issues_text/target_missing/host_missing/accel_missing/511 new file mode 100644 index 000000000..8a4252c02 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/511 @@ -0,0 +1 @@ +usbredirparser: bulk transfer length exceeds limits (can't use any USB storage) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/515 b/gitlab/issues_text/target_missing/host_missing/accel_missing/515 new file mode 100644 index 000000000..53f5977b6 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/515 @@ -0,0 +1,31 @@ +qemu-system-x86_64 fails to run with regular user after following arch wiki article +Description of problem: +When `qemu-system-x86_64` binary is run with a regular user, it fails with no output. No matter if it's run with `--help`, `--version` or any other parameter. By checking the resulting error code (`echo $?`) it is possible to see that it finished with error code 1. + +After seeing this [post](https://www.reddit.com/r/archlinux/comments/b9emxp/qemusystemx86_64_does_not_execute_how_can_i/ek47btb/) on reddit, it became clear that the reason was that my `/etc` directory had a subdirectory qemu, in which my regular user did not have access to. That is, qemu binary looks for `/etc/qemu/qemu.conf` and if it can't determine if the file is there or not, it fails. + +Here goes the logic: +strace showed the permission error (even though there was no output to indicate that). + +``` +$ strace /usr/bin/qemu-system-x86_64 +… +mmap(NULL, 4928, PROT_READ|PROT_WRITE, MAP_SHARED|MAP_POPULATE, 3, 0) = 0x7f4d01e6e000 +mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_SHARED|MAP_POPULATE, 3, 0x10000000) = 0x7f4d01e6c000 +eventfd2(0, EFD_CLOEXEC|EFD_NONBLOCK) = 4 +sysinfo({uptime=92539, loads=[109952, 80640, 118144], totalram=16643309568, freeram=5314445312, sharedram=2590158848, bufferram=1301561344, totalswap=20479733760, freeswap=19551150080, procs=1202, totalhigh=0, freehigh=0, mem_unit=1}) = 0 +rt_sigaction(SIGPIPE, {sa_handler=SIG_IGN, sa_mask=~[RTMIN RT_1], sa_flags=SA_RESTORER, sa_restorer=0x7f4d01ad7960}, NULL, 8) = 0 +openat(AT_FDCWD, "/etc/qemu/qemu.conf", O_RDONLY) = -1 EACCES (Permission denied) +exit_group(1) = ? ++++ exited with 1 +++ +``` + +The thing was that initially that folder did not exist, and I created it to make the qemu bridges work, like indicated in this arch wiki [article](https://wiki.archlinux.org/title/QEMU#Bridged_networking_using_qemu-bridge-helper). I will be suggesting modifications to that article. + +When the directory did not exit, qemu noticed that the folder didn't exist and moved on, once it was created, in case the regular user had no access to it, it fails with no warning. + +I just gave access to the folder ant it worked again (if you delete the folder it works too). + +If you use libvirt, by using virsh for example, you may not notice this issue as it may be running as system (by setting the following system variable `export LIBVIRT_DEFAULT_URI='qemu:///system'`) + +So, to fix this issue, in my opinion a warning should be printed out to the stderr. Otherwise, qemu could move on if it doens't have access to `/etc/qemu/qemu.conf`. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/516 b/gitlab/issues_text/target_missing/host_missing/accel_missing/516 new file mode 100644 index 000000000..e282e7b46 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/516 @@ -0,0 +1,42 @@ +Configure option `--enable-plugins` makes modules in shared library not loadable on macOS +Description of problem: +The title mentions `--enable-plugins` option, however as it's enabled by default, not providing `--disable-plugins` would also cause this to happen. + +If TCG plugin support is enabled, symbols in `qemu-system-*` binaries will be missing, and module libraries would fail to load as they expect those symbols to exist in the main binary. + +Configure options used: `STRIP="strip -x" ./configure --enable-user --enable-tools --enable-parallels --enable-libxml2 --enable-spice --enable-hvf --enable-cocoa --enable-guest-agent --enable-curses --enable-plugins --enable-modules --objcc=gcc --enable-libusb --enable-usb-redir` + +After inspecting the compiler command line, I've found the linker option `-Wl,-exported_symbols_list,qemu-plugins-ld64.symbols` is causing this to happen: only symbols listed in `qemu-plugins-ld64.symbols` would be kept in `qemu-system-*` binaries and all other symbols will be hidden. + +Note that this is not caused by stripping (although I had to use custom strip command line on macOS to successfully compile qemu); the option `-exported_symbols_list` works by only exposing the provided symbols and treating all other symbols as `visibility=hidden`. + +Replacing `--enable-plugins` to `--disable-plugins` in the above configure command line would "fix" it, although it means TCG plugins will not be supported. +Steps to reproduce: +1. Build QEMU on macOS with plugin support enabled +2. Try to use modules in shared library like qxl +Additional information: +Some examples: + +``` +$ qemu-system-x86_64 -device qxl +Failed to open module: dlopen(/usr/local/bin/../lib/qemu/ui-spice-core.dylib, 10): Symbol not found: __TRACE_QEMU_SPICE_ADD_MEMSLOT_DSTATE + Referenced from: /usr/local/bin/../lib/qemu/ui-spice-core.dylib + Expected in: flat namespace + in /usr/local/bin/../lib/qemu/ui-spice-core.dylib +Failed to open module: dlopen(/usr/local/bin/../lib/qemu/hw-display-qxl.dylib, 2): Symbol not found: __TRACE_QXL_CLIENT_MONITORS_CONFIG_CAPPED_DSTATE + Referenced from: /usr/local/bin/../lib/qemu/hw-display-qxl.dylib + Expected in: flat namespace + in /usr/local/bin/../lib/qemu/hw-display-qxl.dylib +qemu-system-x86_64: -device qxl: 'qxl' is not a valid device model name +``` + +``` +$ qemu-system-x86_64 -spice port=5901 +Failed to open module: dlopen(/usr/local/bin/../lib/qemu/ui-spice-core.dylib, 10): Symbol not found: __TRACE_QEMU_SPICE_ADD_MEMSLOT_DSTATE + Referenced from: /usr/local/bin/../lib/qemu/ui-spice-core.dylib + Expected in: flat namespace + in /usr/local/bin/../lib/qemu/ui-spice-core.dylib +qemu-system-x86_64: -spice port=5901: spice support is disabled +``` + +After disabling plugin support I could run virtual machines locally through libvirt with full spice and qxl video support. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/517 b/gitlab/issues_text/target_missing/host_missing/accel_missing/517 new file mode 100644 index 000000000..764c25b74 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/517 @@ -0,0 +1 @@ +Abort in vmxnet3_setup_tx_offloads diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/520 b/gitlab/issues_text/target_missing/host_missing/accel_missing/520 new file mode 100644 index 000000000..1d63a7cef --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/520 @@ -0,0 +1,33 @@ +qemu-ga fsfreeze crashes the kernel +Description of problem: +Hello, + +Still required your attention, duplicate from: +https://bugs.launchpad.net/bugs/1807073 +https://bugs.launchpad.net/bugs/1813045 + +We use mainly Cloudlinux, Debian and Centos. +We experienced many crashes on our qemu instances based on Cloudlinux during a snapshot. +The issue is not related to CloudLinux directly, but to Qemu agent, which does not freeze the file system(s) correctly. What is actually happening: + +When VM backup is invoked, Qemu agent freezes the file systems, so no single change will be made during the backup. But Qemu agent does not respect the loop* devices in freezing order (we have checked its sources), which leads to the next situation: +1) freeze loopback fs + ---> send async reqs to loopback thread +2) freeze main fs +3) loopback thread wakes up and trying to write data to the main fs, which is still frozen, and this finally leads to the hung task and kernel crash. + +Moreover, a lot of Proxmox users are complaining about the issue as well: +https://forum.proxmox.com/threads/error-vm-100-qmp-command-guest-fsfreeze-thaw-failed-got-timeout.68082/ +https://forum.proxmox.com/threads/problem-with-fsfreeze-freeze-and-qemu-guest-agent.65707/ +Steps to reproduce: +1. Manually start backup for the VM with qemu-agent enabled. +2. The backup process stuck at "INFO: issuing guest-agent 'fs-freeze' command" +3. The VM become unavailable, you can only unlock it and force reset. +Additional information: +/var/log/messages logs: +Aug 6 21:54:00 cpanel qemu-ga: info: guest-ping called +Aug 6 21:54:01 cpanel qemu-ga: info: guest-fsfreeze called +Aug 6 21:54:01 cpanel qemu-ga: info: executing fsfreeze hook with arg 'freeze' + + +after this the VM becomes completely unavailable. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/521 b/gitlab/issues_text/target_missing/host_missing/accel_missing/521 new file mode 100644 index 000000000..b95918801 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/521 @@ -0,0 +1 @@ +Assert mr != NULL through megaraid diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/522 b/gitlab/issues_text/target_missing/host_missing/accel_missing/522 new file mode 100644 index 000000000..48b180688 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/522 @@ -0,0 +1,54 @@ +qemu gets SIGSEGV when starting with vhost-user-blk-pci device +Description of problem: +as subject +Steps to reproduce: +1. Prepare an qemu-storage-daemon process for vhost-user +``` +qemu-img create /tmp/test 100M +``` +``` +/usr/bin/qemu-storage-daemon --blockdev '{"driver":"file","filename":"/var/lib/libvirt/images/test.img","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' --blockdev '{"node-name":"libvirt-1-format","read-only":false,"driver":"raw","file":"libvirt-1-storage"}' --export vhost-user-blk,id=vhost-user-blk0,node-name=libvirt-1-format,addr.type=unix,addr.path=/tmp/vhost.sock,writable=on --chardev stdio,mux=on,id=char0 +``` +2. Run the qemu cmdline above. Then SIGSEGV. +And the error of qemu-storage-daemon:`qemu-storage-daemon: vu_panic: Invalid queue index: 1` +Additional information: +Backtrace: +``` +#0 0x0000557105198937 in vhost_user_read_cb (source=0x55710677be90, condition=<optimized out>, opaque=0x7ffe8b208ee0) at ../hw/virtio/vhost-user.c:313 +#1 0x00007f7e7ec422af in g_main_dispatch (context=0x557107b02070) at ../glib/gmain.c:3344 +#2 g_main_context_dispatch (context=0x557107b02070) at ../glib/gmain.c:4062 +#3 0x00007f7e7ec96df8 in g_main_context_iterate.constprop.0 (context=0x557107b02070, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/gmain.c:4138 +#4 0x00007f7e7ec41873 in g_main_loop_run (loop=0x557107b02570) at ../glib/gmain.c:4336 +#5 0x000055710519770a in vhost_user_read (dev=dev@entry=0x7f7df46443f8, msg=msg@entry=0x7ffe8b208f50) at ../hw/virtio/vhost-user.c:402 +#6 0x000055710519808f in vhost_user_get_config (dev=0x7f7df46443f8, config=0x7f7df46443ac "", config_len=60) at ../hw/virtio/vhost-user.c:2133 +#7 0x0000557105152af1 in vhost_user_blk_device_realize (dev=0x7f7df46441b0, errp=<optimized out>) at ../hw/block/vhost-user-blk.c:503 +#8 0x000055710518cb9c in virtio_device_realize (dev=0x7f7df46441b0, errp=0x7ffe8b2092e0) at ../hw/virtio/virtio.c:3660 +#9 0x00005571051d7abd in device_set_realized (obj=<optimized out>, value=<optimized out>, errp=0x7ffe8b209360) at ../hw/core/qdev.c:761 +#10 0x00005571051da62a in property_set_bool (obj=0x7f7df46441b0, v=<optimized out>, name=<optimized out>, opaque=0x55710653c150, errp=0x7ffe8b209360) at ../qom/object.c:2257 +#11 0x00005571051dd3ac in object_property_set (obj=obj@entry=0x7f7df46441b0, name=name@entry=0x55710541bab9 "realized", v=v@entry=0x557107afbc80, errp=errp@entry=0x7ffe8b209470) + at ../qom/object.c:1402 +#12 0x00005571051e08f4 in object_property_set_qobject + (obj=obj@entry=0x7f7df46441b0, name=name@entry=0x55710541bab9 "realized", value=value@entry=0x557107afbbc0, errp=errp@entry=0x7ffe8b209470) at ../qom/qom-qobject.c:28 +#13 0x00005571051dd9c9 in object_property_set_bool (obj=0x7f7df46441b0, name=0x55710541bab9 "realized", value=<optimized out>, errp=0x7ffe8b209470) at ../qom/object.c:1472 +#14 0x0000557104fe813c in pci_qdev_realize (qdev=<optimized out>, errp=<optimized out>) at ../hw/pci/pci.c:2117 +#15 0x00005571051d7abd in device_set_realized (obj=<optimized out>, value=<optimized out>, errp=0x7ffe8b209590) at ../hw/core/qdev.c:761 +#16 0x00005571051da62a in property_set_bool (obj=0x7f7df463c010, v=<optimized out>, name=<optimized out>, opaque=0x55710653c150, errp=0x7ffe8b209590) at ../qom/object.c:2257 +#17 0x00005571051dd3ac in object_property_set (obj=obj@entry=0x7f7df463c010, name=name@entry=0x55710541bab9 "realized", v=v@entry= + 0x557107af5e80, errp=errp@entry=0x5571057e2db0 <error_fatal>) at ../qom/object.c:1402 +#18 0x00005571051e08f4 in object_property_set_qobject + (obj=obj@entry=0x7f7df463c010, name=name@entry=0x55710541bab9 "realized", value=value@entry=0x557107af5e40, errp=errp@entry=0x5571057e2db0 <error_fatal>) at ../qom/qom-qobject.c:28 +#19 0x00005571051dd9c9 in object_property_set_bool (obj=0x7f7df463c010, name=name@entry=0x55710541bab9 "realized", value=value@entry=true, errp=errp@entry=0x5571057e2db0 <error_fatal>) + at ../qom/object.c:1472 +#20 0x00005571051d8052 in qdev_realize (dev=<optimized out>, bus=bus@entry=0x5571073ffeb0, errp=errp@entry=0x5571057e2db0 <error_fatal>) at ../hw/core/qdev.c:389 +#21 0x0000557104ec5e28 in qdev_device_add (opts=0x557106534000, errp=errp@entry=0x5571057e2db0 <error_fatal>) at ../softmmu/qdev-monitor.c:674 +#22 0x00005571050f4bf3 in device_init_func (opaque=<optimized out>, opts=<optimized out>, errp=0x5571057e2db0 <error_fatal>) at ../softmmu/vl.c:1212 +#23 0x0000557105302282 in qemu_opts_foreach (list=<optimized out>, func=func@entry=0x5571050f4be0 <device_init_func>, opaque=opaque@entry=0x0, errp=errp@entry=0x5571057e2db0 <error_fatal>) + at ../util/qemu-option.c:1168 +#24 0x00005571050f7532 in qemu_create_cli_devices () at ../softmmu/vl.c:2587 +#25 qmp_x_exit_preconfig (errp=<optimized out>) at ../softmmu/vl.c:2635 +#26 0x00005571050fb5ac in qmp_x_exit_preconfig (errp=<optimized out>) at ../softmmu/vl.c:2629 +#27 qemu_init (argc=<optimized out>, argv=<optimized out>, envp=<optimized out>) at ../softmmu/vl.c:3669 +#28 0x0000557104e87b1d in main (argc=<optimized out>, argv=<optimized out>, envp=<optimized out>) at ../softmmu/main.c:49 +``` + +Get full threads backtrace on the attachment [gdb.zip](/uploads/3cbc168cad60a1472e9e3f323207de9d/gdb.zip) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/523 b/gitlab/issues_text/target_missing/host_missing/accel_missing/523 new file mode 100644 index 000000000..cf0ec97fc --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/523 @@ -0,0 +1,126 @@ +Some iotests failing with --enable-block-drv-whitelist-in-tools +Description of problem: +Building latest RC with Fedora, some of the iotests now report fail. We could track it down to the --enable-block-drv-whitelist-in-tools option. +Steps to reproduce: +1. ```configure --enable-block-drv-whitelist-in-tools``` +2. ```make``` +3. ```make check``` +Additional information: +``` +... + TEST iotest-qcow2: 049 [fail] +QEMU -- "/builddir/build/BUILD/qemu-6.1.0-rc3/qemu_kvm_build/tests/qemu-iotests/../../qemu-system-x86_64" -nodefaults -display none -accel qtest +QEMU_IMG -- "/builddir/build/BUILD/qemu-6.1.0-rc3/qemu_kvm_build/tests/qemu-iotests/../../qemu-img" +QEMU_IO -- "/builddir/build/BUILD/qemu-6.1.0-rc3/qemu_kvm_build/tests/qemu-iotests/../../qemu-io" --cache writeback --aio threads -f qcow2 +QEMU_NBD -- "/builddir/build/BUILD/qemu-6.1.0-rc3/qemu_kvm_build/tests/qemu-iotests/../../qemu-nbd" +IMGFMT -- qcow2 +IMGPROTO -- file +PLATFORM -- Linux/x86_64 buildvm-x86-11.iad2.fedoraproject.org 5.12.13-300.fc34.x86_64 +TEST_DIR -- /builddir/build/BUILD/qemu-6.1.0-rc3/qemu_kvm_build/tests/qemu-iotests/scratch +SOCK_DIR -- /tmp/tmpr6u1m61s +SOCKET_SCM_HELPER -- /builddir/build/BUILD/qemu-6.1.0-rc3/qemu_kvm_build/tests/qemu-iotests/socket_scm_helper +--- /builddir/build/BUILD/qemu-6.1.0-rc3/tests/qemu-iotests/049.out ++++ 049.out.bad +@@ -199,6 +199,8 @@ + qemu-img create -f qcow2 --object secret,id=sec0,data=123456 -o encryption=on,encrypt.key-secret=sec0 TEST_DIR/t.qcow2 64M + Formatting 'TEST_DIR/t.qcow2', fmt=qcow2 encryption=on encrypt.key-secret=sec0 cluster_size=65536 extended_l2=off compression_type=zlib size=67108864 lazy_refcounts=off refcount_bits=16 ++qemu-img: TEST_DIR/t.qcow2: Use of AES-CBC encrypted qcow2 images is no longer supported in system emulators ++You can use 'qemu-img convert' to convert your image to an alternative supported format, such as unencrypted qcow2, or raw with the LUKS format instead. + == Check lazy_refcounts option (only with v3) == +... + TEST iotest-qcow2: 134 [fail] +QEMU -- "/builddir/build/BUILD/qemu-6.1.0-rc3/qemu_kvm_build/tests/qemu-iotests/../../qemu-system-x86_64" -nodefaults -display none -accel qtest +QEMU_IMG -- "/builddir/build/BUILD/qemu-6.1.0-rc3/qemu_kvm_build/tests/qemu-iotests/../../qemu-img" +QEMU_IO -- "/builddir/build/BUILD/qemu-6.1.0-rc3/qemu_kvm_build/tests/qemu-iotests/../../qemu-io" --cache writeback --aio threads -f qcow2 +QEMU_NBD -- "/builddir/build/BUILD/qemu-6.1.0-rc3/qemu_kvm_build/tests/qemu-iotests/../../qemu-nbd" +IMGFMT -- qcow2 +IMGPROTO -- file +PLATFORM -- Linux/x86_64 buildvm-x86-11.iad2.fedoraproject.org 5.12.13-300.fc34.x86_64 +TEST_DIR -- /builddir/build/BUILD/qemu-6.1.0-rc3/qemu_kvm_build/tests/qemu-iotests/scratch +SOCK_DIR -- /tmp/tmpr6u1m61s +SOCKET_SCM_HELPER -- /builddir/build/BUILD/qemu-6.1.0-rc3/qemu_kvm_build/tests/qemu-iotests/socket_scm_helper +--- /builddir/build/BUILD/qemu-6.1.0-rc3/tests/qemu-iotests/134.out ++++ 134.out.bad +@@ -1,30 +1,24 @@ + QA output created by 134 + Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=134217728 encryption=on ++qemu-img: TEST_DIR/t.IMGFMT: Use of AES-CBC encrypted IMGFMT images is no longer supported in system emulators ++You can use 'qemu-img convert' to convert your image to an alternative supported format, such as unencrypted IMGFMT, or raw with the LUKS format instead. + == reading whole image == +-read 134217728/134217728 bytes at offset 0 +-128 MiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec) ++qemu-io: can't open: Could not open '/builddir/build/BUILD/qemu-6.1.0-rc3/qemu_kvm_build/tests/qemu-iotests/scratch/t.qcow2': No such file or directory + == rewriting cluster part == +-wrote 512/512 bytes at offset 512 +-512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec) ++qemu-io: can't open: Could not open '/builddir/build/BUILD/qemu-6.1.0-rc3/qemu_kvm_build/tests/qemu-iotests/scratch/t.qcow2': No such file or directory + == verify pattern == +-read 512/512 bytes at offset 0 +-512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec) +-read 512/512 bytes at offset 512 +-512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec) ++qemu-io: can't open: Could not open '/builddir/build/BUILD/qemu-6.1.0-rc3/qemu_kvm_build/tests/qemu-iotests/scratch/t.qcow2': No such file or directory ++qemu-io: can't open: Could not open '/builddir/build/BUILD/qemu-6.1.0-rc3/qemu_kvm_build/tests/qemu-iotests/scratch/t.qcow2': No such file or directory + == rewriting whole image == +-wrote 134217728/134217728 bytes at offset 0 +-128 MiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec) ++qemu-io: can't open: Could not open '/builddir/build/BUILD/qemu-6.1.0-rc3/qemu_kvm_build/tests/qemu-iotests/scratch/t.qcow2': No such file or directory + == verify pattern == +-read 134217728/134217728 bytes at offset 0 +-128 MiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec) ++qemu-io: can't open: Could not open '/builddir/build/BUILD/qemu-6.1.0-rc3/qemu_kvm_build/tests/qemu-iotests/scratch/t.qcow2': No such file or directory + == verify pattern failure with wrong password == +-Pattern verification failed at offset 0, 134217728 bytes +-read 134217728/134217728 bytes at offset 0 +-128 MiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec) ++qemu-io: can't open: Could not open '/builddir/build/BUILD/qemu-6.1.0-rc3/qemu_kvm_build/tests/qemu-iotests/scratch/t.qcow2': No such file or directory + *** done +... + TEST iotest-qcow2: 158 [fail] +QEMU -- "/builddir/build/BUILD/qemu-6.1.0-rc3/qemu_kvm_build/tests/qemu-iotests/../../qemu-system-x86_64" -nodefaults -display none -accel qtest +QEMU_IMG -- "/builddir/build/BUILD/qemu-6.1.0-rc3/qemu_kvm_build/tests/qemu-iotests/../../qemu-img" +QEMU_IO -- "/builddir/build/BUILD/qemu-6.1.0-rc3/qemu_kvm_build/tests/qemu-iotests/../../qemu-io" --cache writeback --aio threads -f qcow2 +QEMU_NBD -- "/builddir/build/BUILD/qemu-6.1.0-rc3/qemu_kvm_build/tests/qemu-iotests/../../qemu-nbd" +IMGFMT -- qcow2 +IMGPROTO -- file +PLATFORM -- Linux/x86_64 buildvm-x86-11.iad2.fedoraproject.org 5.12.13-300.fc34.x86_64 +TEST_DIR -- /builddir/build/BUILD/qemu-6.1.0-rc3/qemu_kvm_build/tests/qemu-iotests/scratch +SOCK_DIR -- /tmp/tmpr6u1m61s +SOCKET_SCM_HELPER -- /builddir/build/BUILD/qemu-6.1.0-rc3/qemu_kvm_build/tests/qemu-iotests/socket_scm_helper +--- /builddir/build/BUILD/qemu-6.1.0-rc3/tests/qemu-iotests/158.out ++++ 158.out.bad +@@ -1,26 +1,25 @@ + QA output created by 158 + == create base == + Formatting 'TEST_DIR/t.IMGFMT.base', fmt=IMGFMT size=134217728 encryption=on ++qemu-img: TEST_DIR/t.IMGFMT.base: Use of AES-CBC encrypted IMGFMT images is no longer supported in system emulators ++You can use 'qemu-img convert' to convert your image to an alternative supported format, such as unencrypted IMGFMT, or raw with the LUKS format instead. + == writing whole image == +-wrote 134217728/134217728 bytes at offset 0 +-128 MiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec) ++qemu-io: can't open: Could not open '/builddir/build/BUILD/qemu-6.1.0-rc3/qemu_kvm_build/tests/qemu-iotests/scratch/t.qcow2.base': No such file or directory + == verify pattern == +-read 134217728/134217728 bytes at offset 0 +-128 MiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec) ++qemu-io: can't open: Could not open '/builddir/build/BUILD/qemu-6.1.0-rc3/qemu_kvm_build/tests/qemu-iotests/scratch/t.qcow2.base': No such file or directory + == create overlay == + Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=134217728 backing_file=TEST_DIR/t.IMGFMT.base backing_fmt=IMGFMT encryption=on ++qemu-img: TEST_DIR/t.IMGFMT: Use of AES-CBC encrypted IMGFMT images is no longer supported in system emulators ++You can use 'qemu-img convert' to convert your image to an alternative supported format, such as unencrypted IMGFMT, or raw with the LUKS format instead. + == writing part of a cluster == +-wrote 1024/1024 bytes at offset 0 +-1 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec) ++qemu-io: can't open: Could not open '/builddir/build/BUILD/qemu-6.1.0-rc3/qemu_kvm_build/tests/qemu-iotests/scratch/t.qcow2': No such file or directory + == verify pattern == +-read 1024/1024 bytes at offset 0 +-1 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec) ++qemu-io: can't open: Could not open '/builddir/build/BUILD/qemu-6.1.0-rc3/qemu_kvm_build/tests/qemu-iotests/scratch/t.qcow2': No such file or directory + == verify pattern == +-read 64512/64512 bytes at offset 1024 +-63 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec) ++qemu-io: can't open: Could not open '/builddir/build/BUILD/qemu-6.1.0-rc3/qemu_kvm_build/tests/qemu-iotests/scratch/t.qcow2': No such file or directory + *** done +... +Failures: 049 134 158 +Failed 3 of 122 iotests +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/524 b/gitlab/issues_text/target_missing/host_missing/accel_missing/524 new file mode 100644 index 000000000..d2cd09adc --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/524 @@ -0,0 +1 @@ +Giving -smp option a negative argument makes QEMU dump core diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/526 b/gitlab/issues_text/target_missing/host_missing/accel_missing/526 new file mode 100644 index 000000000..eba131553 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/526 @@ -0,0 +1,15 @@ +MacBook German Keyboard <> and ^° Key not working +Description of problem: +Using a German keyboard on my 2018 MacBook Pro I can't type the <> Key or the ^ Key. +When pressing the <> Key it gets interpreted as the ^ Key, the ^ Key is dead. + +Problem is not caused by the guest system, Ubuntu VMs also can't type <>. (Ubuntu VMs ran inside UTM, which internally uses QEMU. https://mac.getutm.app/ ) + +VirtualBox maps the <> Key and ^ Key correctly. +Steps to reproduce: +0. Use a MacBook with a German Keyboard +1. Install TempleOS +2. Install German Keyboard Layout from https://github.com/Rion96/GKey (mount the ISO as a CD Drive) +3. Every key works except for <> and ^. +Additional information: +Doing the same steps in VirtualBox results in <> and ^ working, so it must be a QEMU error. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/527 b/gitlab/issues_text/target_missing/host_missing/accel_missing/527 new file mode 100644 index 000000000..8556234c4 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/527 @@ -0,0 +1 @@ +Plain text files in docs/ should be converted to rst diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/531 b/gitlab/issues_text/target_missing/host_missing/accel_missing/531 new file mode 100644 index 000000000..68c334cc9 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/531 @@ -0,0 +1 @@ +Replace DMA processing in I/O handlers by asynchronous BH diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/532 b/gitlab/issues_text/target_missing/host_missing/accel_missing/532 new file mode 100644 index 000000000..24db93b42 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/532 @@ -0,0 +1 @@ +USB-EHCI: Replace DMA processing in I/O handlers by asynchronous BH diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/533 b/gitlab/issues_text/target_missing/host_missing/accel_missing/533 new file mode 100644 index 000000000..c2d86a5bf --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/533 @@ -0,0 +1 @@ +Assertion failure in vmxnet3_get_next_body_rx_descr: d->btype == VMXNET3_RXD_BTYPE_BODY diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/534 b/gitlab/issues_text/target_missing/host_missing/accel_missing/534 new file mode 100644 index 000000000..1bad520ca --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/534 @@ -0,0 +1 @@ +Memcpy param-overlap through e1000e_write_to_rx_buffers diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/535 b/gitlab/issues_text/target_missing/host_missing/accel_missing/535 new file mode 100644 index 000000000..13f281aa6 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/535 @@ -0,0 +1 @@ +Assertion failure in iov_from_buf_full through the e1000e diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/537 b/gitlab/issues_text/target_missing/host_missing/accel_missing/537 new file mode 100644 index 000000000..90ab1f56e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/537 @@ -0,0 +1 @@ +Assertion failure in e1000e_write_to_rx_buffers diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/539 b/gitlab/issues_text/target_missing/host_missing/accel_missing/539 new file mode 100644 index 000000000..398cadcc9 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/539 @@ -0,0 +1 @@ +Abort in vmxnet3_validate_interrupt_idx diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/540 b/gitlab/issues_text/target_missing/host_missing/accel_missing/540 new file mode 100644 index 000000000..ab1232185 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/540 @@ -0,0 +1 @@ +Heap-use-after-free in usb_packet_unmap through xhci diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/541 b/gitlab/issues_text/target_missing/host_missing/accel_missing/541 new file mode 100644 index 000000000..d23bf0c57 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/541 @@ -0,0 +1 @@ +Heap-use-after-free through ehci_flush_qh diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/542 b/gitlab/issues_text/target_missing/host_missing/accel_missing/542 new file mode 100644 index 000000000..aa3c41f1f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/542 @@ -0,0 +1 @@ +Stack-overflow in ldl_le_dma through intel-hda (CVE-2021-3611) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/543 b/gitlab/issues_text/target_missing/host_missing/accel_missing/543 new file mode 100644 index 000000000..700d5da81 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/543 @@ -0,0 +1 @@ +virtio-blk: ASSERT: !s->dataplane_started diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/544 b/gitlab/issues_text/target_missing/host_missing/accel_missing/544 new file mode 100644 index 000000000..d9d7c5f91 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/544 @@ -0,0 +1 @@ +Assert xfer->packet.status != USB_RET_NAK in xhci diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/545 b/gitlab/issues_text/target_missing/host_missing/accel_missing/545 new file mode 100644 index 000000000..663a9ee75 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/545 @@ -0,0 +1 @@ +Abort in ohci_frame_boundary diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/546 b/gitlab/issues_text/target_missing/host_missing/accel_missing/546 new file mode 100644 index 000000000..4003cb23c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/546 @@ -0,0 +1 @@ +Global-buffer-overflow in mode_sense_page diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/547 b/gitlab/issues_text/target_missing/host_missing/accel_missing/547 new file mode 100644 index 000000000..389aa167f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/547 @@ -0,0 +1 @@ +e1000: Loop blocking QEMU with high CPU usage diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/548 b/gitlab/issues_text/target_missing/host_missing/accel_missing/548 new file mode 100644 index 000000000..9098ca7ea --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/548 @@ -0,0 +1 @@ +Null-ptr dereference in megasas_finish_dcmd diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/55 b/gitlab/issues_text/target_missing/host_missing/accel_missing/55 new file mode 100644 index 000000000..d5227695b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/55 @@ -0,0 +1 @@ +Can't install Windows 7 with q35 (SATA) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/551 b/gitlab/issues_text/target_missing/host_missing/accel_missing/551 new file mode 100644 index 000000000..1d3fd5ee1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/551 @@ -0,0 +1 @@ +Null-ptr dereference in megasas_command_complete diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/552 b/gitlab/issues_text/target_missing/host_missing/accel_missing/552 new file mode 100644 index 000000000..be9c9c977 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/552 @@ -0,0 +1 @@ +assert issue locates in hw/scsi/lsi53c895a.c:624: lsi_do_dma: Assertion `s->current' failed diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/553 b/gitlab/issues_text/target_missing/host_missing/accel_missing/553 new file mode 100644 index 000000000..82a64f197 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/553 @@ -0,0 +1,25 @@ +Virtio-vga with blobs on fails, when qemu compiled with enabled modules +Description of problem: +When using qemu configured with `--enabled-modules` and starting qemu with command line above, qemu crashes with following output: +``` +qemu-system-x86_64: -device virtio-vga,blob=on: cannot enable blob resources without udmabuf +``` +While qemu configured without `--enabled-modules` runs this command successfully. +Steps to reproduce: +1. Get latest qemu source code +2. Build qemu `mkdir build && cd build && ../configure && ninja` +3. Check if following command runs without errors and show sdl qemu window + ``` + sudo ./qemu-system-x86_64 \ + -object memory-backend-memfd,id=mem1,size=512M \ + -machine memory-backend=mem1 \ + -display sdl \ + -device virtio-vga,blob=on + + ``` +4. Then try to build with modules enabled `mkdir build && cd build && ../configure --enable-modules && ninja` +5. Try to do step 3 again +Additional information: +I tried to debug this bug, and found that problem is with function `virtio_gpu_have_udmabuf`: when qemu is build without modules this function is from `hw/display/virtio-gpu-udmabuf.c` (which is correct), but when qemu compiled with modules this function comes from `stubs/virtio-gpu-udmabuf.c` and when `hw-display-virtio-gpu.so` is loaded, `virtio_gpu_have_udmabuf` is not replaced, and remains function from stub (which always return 0) and command fails. + +I think I will submit patch that fix it tomorrow diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/556 b/gitlab/issues_text/target_missing/host_missing/accel_missing/556 new file mode 100644 index 000000000..a8914e21a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/556 @@ -0,0 +1,19 @@ +Fix DMA MMIO reentrancy issues +Additional information: +List of `DMA reentrancy` issues (usually found by [fuzzer](https://gitlab.com/qemu-project/qemu/-/issues?label_name[]=Fuzzer)): +- #62 (AHCI) +- #84, #305, #552 (SCSI) +- #451, #1282 (SDHCI) +- #540 (xHCI) +- #541 (EHCI) +- #542 (HDA) +- #557 (pcnet) +- #782 (NVMe) +- [eepro100](https://lore.kernel.org/qemu-devel/20210218140629.373646-1-ppandit@redhat.com/) +- #827 (virtio-blk) +- #1171 (tulip) +- #1543 (e1000e) +- #1563 (lsi53c895a) + + +Usually coredump backtrace includes multiple calls to `access_with_adjusted_size()` from the Memory API. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/557 b/gitlab/issues_text/target_missing/host_missing/accel_missing/557 new file mode 100644 index 000000000..8ba506c6e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/557 @@ -0,0 +1 @@ +Stack-overflow through pcnet_tmd_load diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/558 b/gitlab/issues_text/target_missing/host_missing/accel_missing/558 new file mode 100644 index 000000000..2d6178e4a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/558 @@ -0,0 +1,57 @@ +gtk UI interprets double/triple click as button release +Description of problem: +When using the GTK interface clicking rapidly in a down-up-down pattern, the final "down" event is erroneously followed by an immediate "up" event and the mouse device in the guest reports the pressed button as no longer being held. +Steps to reproduce: +1. Start a VM using the GTK interface. +2. Open a tool to examine guest mouse input events, such as `xev` or `yutani-test` +3. Click twice with any button, without releasing on the second click. +4. Observe erroneous 'up' event in guest. +5. Move the mouse while keeping the button pressed. +6. Observe the guest reports the button is not held. +Additional information: +GTK 3 sends an additional `GDK_2BUTTON_PRESS` event after the initial `GDK_BUTTON_PRESS` event, which QEMU is misinterpreting as a release event. I confirmed this with the addition of some logging of `button->type` in `gd_button_event`: + +``` +button = 1, type = 4 +button = 1, type = 7 +button = 1, type = 4 +button = 1, type = 7 +button = 1, type = 4 # = PRESS +button = 1, type = 5 # = 2BUTTON_PRESS +button = 1, type = 7 +button = 1, type = 4 +button = 1, type = 7 +button = 1, type = 4 +button = 1, type = 5 +button = 1, type = 7 +button = 1, type = 4 +button = 1, type = 7 +button = 1, type = 4 +button = 1, type = 7 +button = 1, type = 4 +button = 1, type = 7 +button = 1, type = 4 +button = 1, type = 5 +button = 1, type = 7 +``` + +```diff +diff --git a/ui/gtk.c b/ui/gtk.c +index cfb0728d1f..b9979f0e11 100644 +--- a/ui/gtk.c ++++ b/ui/gtk.c +@@ -925,6 +925,13 @@ static gboolean gd_button_event(GtkWidget *widget, GdkEventButton *button, + return TRUE; + } + ++ /* ignore additional events for double- and triple- press, as they are ++ * sent to us after a regular press event; otherwise we will misinterpret ++ * these as release events and eat the button! */ ++ if (button->type == GDK_2BUTTON_PRESS || button->type == GDK_3BUTTON_PRESS) { ++ return TRUE; ++ } ++ + qemu_input_queue_btn(vc->gfx.dcl.con, btn, + button->type == GDK_BUTTON_PRESS); + qemu_input_event_sync(); +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/559 b/gitlab/issues_text/target_missing/host_missing/accel_missing/559 new file mode 100644 index 000000000..422ece192 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/559 @@ -0,0 +1 @@ +info does not recognize file format of vpc with subformat=fixed diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/56 b/gitlab/issues_text/target_missing/host_missing/accel_missing/56 new file mode 100644 index 000000000..56147c284 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/56 @@ -0,0 +1 @@ +Regression report: Disk subsystem I/O failures/issues surfacing in DOS/early Windows [two separate issues: one bisected, one root-caused] diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/560 b/gitlab/issues_text/target_missing/host_missing/accel_missing/560 new file mode 100644 index 000000000..7ca729665 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/560 @@ -0,0 +1 @@ +User-emu documentation mentions inexistent "runtime" downloads diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/562 b/gitlab/issues_text/target_missing/host_missing/accel_missing/562 new file mode 100644 index 000000000..159304d3e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/562 @@ -0,0 +1 @@ +`ShaderTranslator.h` and `ShaderTranslator.cpp` files are missing and are not in ANGLE_ROOT/src/libShaderTranslator diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/563 b/gitlab/issues_text/target_missing/host_missing/accel_missing/563 new file mode 100644 index 000000000..036bd268e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/563 @@ -0,0 +1 @@ +KVM ubuntu 20 VPS on Ryzen 9 5950X diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/564 b/gitlab/issues_text/target_missing/host_missing/accel_missing/564 new file mode 100644 index 000000000..3b9291885 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/564 @@ -0,0 +1,13 @@ +Enable opengl virtio-gpu virgl vulkan in windows build +Additional information: +``` +PS E:\scoopg\apps\qemu\current> ./qemu-system-x86_64.exe -drive file=E:\groot_02\vdisks\gparted-live.iso,if=virtio -boot c -m 4096 -machine type=pc,accel=whpx,kernel-irqchip=off -smp 8,sockets=1,cores=8,threads=1 -vga virtio -display sdl,gl=on +E:\scoopg\apps\qemu\current\qemu-system-x86_64.exe: OpenGL support is disabled +``` + +``` +PS E:\scoopg\apps\qemu\current> E:\scoopg\apps\qemu\current\qemu-system-x86_64.exe --version +QEMU emulator version 6.0.93 (v6.1.0-rc3-11879-ge232c1bc00-dirty) +Copyright (c) 2003-2021 Fabrice Bellard and the QEMU Project developers +``` +# diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/566 b/gitlab/issues_text/target_missing/host_missing/accel_missing/566 new file mode 100644 index 000000000..c0951630c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/566 @@ -0,0 +1 @@ +Fail to build linux-user on Alpine diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/567 b/gitlab/issues_text/target_missing/host_missing/accel_missing/567 new file mode 100644 index 000000000..63611b1e0 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/567 @@ -0,0 +1 @@ +qemu 6.1.0 build fail on alpine linux diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/568 b/gitlab/issues_text/target_missing/host_missing/accel_missing/568 new file mode 100644 index 000000000..a94dd3a9c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/568 @@ -0,0 +1,26 @@ +video memory option not working with Mac OS or Windows guest +Description of problem: +The vgamem_mb option tells the guest how much video memory it has access to. When I used this command '-device VGA,vgamem_mb=128', I expect the guest to report there is 128 MB of video memory. What actually happens is the guest does not seem to know how much video memory is actually available. +Steps to reproduce: +**Mac OS guest:** +1. Run a Mac OS guest with this command: -device VGA,vgamem_mb=128 +2. In Mac OS X open the System Information application -> /Applications/Utilities/System Information. +3. Click on "Graphics/Displays". +4. Look at the 'VRAM (Total)' field. +The field only shows 3 MB of video ram. + +**Windows guest:** +1. Run a Windows (Windows XP in my case) guest with this command: -device VGA,vgamem_mb=128 +2. Click on Start->Run. +3. Enter 'dxdiag'. +4. Push the OK button. +5. Click on the Display tap in the DirectX Diagnostic Tool. +6. Look at the Approv. Total Memory field. +The field should say 128 MB but actually says N/A. +Additional information: +**Mac OS 8.5<br>** +<br><br><br> +**Windows XP<br>** +<br><br><br> +**Windows 7<br>** + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/569 b/gitlab/issues_text/target_missing/host_missing/accel_missing/569 new file mode 100644 index 000000000..b68f03d0d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/569 @@ -0,0 +1 @@ +ESP SCSI adapter not working with DOS ASPI drivers diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/57 b/gitlab/issues_text/target_missing/host_missing/accel_missing/57 new file mode 100644 index 000000000..7d9cac89b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/57 @@ -0,0 +1 @@ +IDE short PRDT abort diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/574 b/gitlab/issues_text/target_missing/host_missing/accel_missing/574 new file mode 100644 index 000000000..2cfd7b02f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/574 @@ -0,0 +1 @@ +ui/sdl2: warning: redundant redeclaration of 'direct_waitqueue_init' diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/575 b/gitlab/issues_text/target_missing/host_missing/accel_missing/575 new file mode 100644 index 000000000..bd68a7e4d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/575 @@ -0,0 +1 @@ +maybe-uninitialized warning in load_fit() diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/576 b/gitlab/issues_text/target_missing/host_missing/accel_missing/576 new file mode 100644 index 000000000..bd97089ca --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/576 @@ -0,0 +1 @@ +New Cocoa clipboard support raises minimum macos version to 10.14 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/578 b/gitlab/issues_text/target_missing/host_missing/accel_missing/578 new file mode 100644 index 000000000..a68830075 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/578 @@ -0,0 +1,30 @@ +getdomainname() is not implemented in QEMU user mode on Linux/sparc64 +Description of problem: +The `getdomainname()` function fails, instead of succeeding. +Steps to reproduce: +[foo.c](/uploads/7586c9aab788855b232a5c2f6aaeb4fc/foo.c) + +1. +``` +# apt install g++-10-sparc64-linux-gnu +# mkdir -p /usr/sparc64-linux-gnu/etc +# touch /usr/sparc64-linux-gnu/etc/ld.so.cache +``` +2. +``` +$ sparc64-linux-gnu-gcc-10 -Wall -static foo.c +``` +[a.out](/uploads/39d291b95caa182d74b0b622a82667e8/a.out) + +3. Transfer the a.out file to a Linux/sparc64 machine; execute it there. It prints +``` +result: (none) +``` +4. +``` +$ QEMU_LD_PREFIX=/usr/sparc64-linux-gnu ~/inst-qemu/6.1.0/bin/qemu-sparc64 ./a.out +``` +Expected: `result: (none)` +Actual: `getdomainname: Function not implemented` +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/579 b/gitlab/issues_text/target_missing/host_missing/accel_missing/579 new file mode 100644 index 000000000..efc4639bc --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/579 @@ -0,0 +1,50 @@ +chown() fails when it should succeed in QEMU user mode on Linux/sparc64 +Description of problem: +The `chown()` function fails, instead of succeeding, in a particular situation. +Steps to reproduce: +[foo.c](/uploads/630d9b83671a071f4ded4da43b6c1b9b/foo.c) + +1. +``` +# apt install g++-10-sparc64-linux-gnu +# mkdir -p /usr/sparc64-linux-gnu/etc +# touch /usr/sparc64-linux-gnu/etc/ld.so.cache +``` +2. +``` +$ sparc64-linux-gnu-gcc-10 -Wall -static foo.c +``` +[a.out](/uploads/bbab43a1b78e6d16ee13e0eff5e963a5/a.out) + +3. Transfer the a.out file to a Linux/sparc64 machine; execute these commands there: +``` +$ id +``` +Verify that you are in 2 or more groups. +``` +$ touch file +$ ln -s file link +$ ln -s link link2 +$ ./a.out; echo $? +``` +It prints `0`. + +4. +``` +$ id +``` +Verify that you are in 2 or more groups. +``` +$ touch file +$ ln -s file link +$ ln -s link link2 +$ QEMU_LD_PREFIX=/usr/sparc64-linux-gnu ~/inst-qemu/6.1.0/bin/qemu-sparc64 ./a.out; echo $? +``` +Expected: `0` +Actual: +``` +chown: Operation not permitted +1 +``` +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/58 b/gitlab/issues_text/target_missing/host_missing/accel_missing/58 new file mode 100644 index 000000000..ae6c43d41 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/58 @@ -0,0 +1 @@ +Bitmaps with Extra Data cannot be removed diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/580 b/gitlab/issues_text/target_missing/host_missing/accel_missing/580 new file mode 100644 index 000000000..3ea5dfe3d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/580 @@ -0,0 +1,17 @@ +access internet from guest +Description of problem: +I can ssh back to host using ssh 10.0.2.2. +Also I can login to guest from host using ssh riscv@localhost -p 3333. +However, +I could not get internet access from the guest os system, such as: +``` +[riscv@fedora-riscv ~]$ wget www.google.com +--2019-12-15 05:53:04-- http://www.google.com/ +Resolving www.google.com (www.google.com)... 216.58.194.164, 2607:f8b0:4005:804::2004 +Connecting to www.google.com (www.google.com)|216.58.194.164|:80... failed: Connection refused. +Connecting to www.google.com (www.google.com)|2607:f8b0:4005:804::2004|:80... failed: Network is unreachable. +``` +Therefore, I could not use dnf to install packages. +Any help will be appreciated. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/581 b/gitlab/issues_text/target_missing/host_missing/accel_missing/581 new file mode 100644 index 000000000..b32518869 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/581 @@ -0,0 +1 @@ +QEMU should warn if the user passes a '-vga something' option and we ignore it diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/582 b/gitlab/issues_text/target_missing/host_missing/accel_missing/582 new file mode 100644 index 000000000..d16a275a2 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/582 @@ -0,0 +1 @@ +Possible regression in qemu-user-static v5.7 from Fedora 34 Repo? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/583 b/gitlab/issues_text/target_missing/host_missing/accel_missing/583 new file mode 100644 index 000000000..fbd960572 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/583 @@ -0,0 +1 @@ +Last cylinder of CHS disk image is not declared as accessible in image diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/586 b/gitlab/issues_text/target_missing/host_missing/accel_missing/586 new file mode 100644 index 000000000..25a0ffab1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/586 @@ -0,0 +1 @@ +virtio-gpu: qemu 6.1.0 no longer enables virgl when using '-vga virtio' diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/587 b/gitlab/issues_text/target_missing/host_missing/accel_missing/587 new file mode 100644 index 000000000..f4ac6779b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/587 @@ -0,0 +1 @@ +qemu show no error but the virtual machine stuck in boot (GPU passthrough) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/589 b/gitlab/issues_text/target_missing/host_missing/accel_missing/589 new file mode 100644 index 000000000..7225b9c0d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/589 @@ -0,0 +1 @@ +Error installing QGA file under virtual machine of windows system diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/59 b/gitlab/issues_text/target_missing/host_missing/accel_missing/59 new file mode 100644 index 000000000..dec48bf86 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/59 @@ -0,0 +1 @@ +ide/core.c ATA Major Version reporting incorrect diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/590 b/gitlab/issues_text/target_missing/host_missing/accel_missing/590 new file mode 100644 index 000000000..1d556fc6d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/590 @@ -0,0 +1 @@ +NSIS Windows installer generator warnings when cross-building on MinGW diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/591 b/gitlab/issues_text/target_missing/host_missing/accel_missing/591 new file mode 100644 index 000000000..47bdee0b4 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/591 @@ -0,0 +1 @@ +Sphinx documentation jobs fail on fork with no version tag diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/592 b/gitlab/issues_text/target_missing/host_missing/accel_missing/592 new file mode 100644 index 000000000..9e5946507 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/592 @@ -0,0 +1,108 @@ +CloudLinux / CageFS - guest-fsfreeze hangs system +Description of problem: +Since CloudLinux provides CageFS (virtualized file system), each time guest-fsfreeze for Proxmox backup, the system is hangs up and become unavailable. It's caused by cagefs-skeleton mount points: + +``` +sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) +proc on /proc type proc (rw,nosuid,nodev,noexec,relatime,gid=1002,hidepid=2) +devtmpfs on /dev type devtmpfs (rw,nosuid,size=3993656k,nr_inodes=998414,mode=755) +securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) +tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) +devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) +tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755) +tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,mode=755) +cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd) +pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime) +configfs on /sys/kernel/config type configfs (rw,relatime) +/dev/sda2 on / type ext4 (rw,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=34,pipe_ino=10005,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=10005) +mqueue on /dev/mqueue type mqueue (rw,relatime) +hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime) +debugfs on /sys/kernel/debug type debugfs (rw,relatime) +fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime) +/dev/sda1 on /boot type ext4 (rw,relatime,data=ordered) +/usr/tmpDSK on /tmp type ext4 (rw,nosuid,noexec,relatime,discard,data=ordered) +/usr/tmpDSK on /var/tmp type ext4 (rw,nosuid,noexec,relatime,discard,data=ordered) +cgroup on /sys/fs/cgroup/freezer type cgroup (rw,relatime,freezer) +cgroup on /sys/fs/cgroup/devices type cgroup (rw,relatime,devices) +cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,relatime,cpuacct,cpu) +cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,relatime,cpuset) +cgroup on /sys/fs/cgroup/memory type cgroup (rw,relatime,memory) +/dev/sda2 on /usr/share/cagefs-skeleton type ext4 (rw,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +devpts on /usr/share/cagefs-skeleton/dev/pts type devpts (rw,nosuid,relatime,gid=5,mode=620,ptmxmode=000) +/dev/sda2 on /usr/share/cagefs-skeleton/lib type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/lib64 type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/opt type ext4 (rw,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/usr/include type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/usr/lib type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/usr/lib64 type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/usr/local/apache/domlogs type ext4 (rw,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/usr/local/cpanel/3rdparty/bin type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/usr/local/cpanel/3rdparty/lib type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/usr/local/cpanel/3rdparty/lib64 type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/usr/local/cpanel/3rdparty/perl type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/usr/local/cpanel/3rdparty/php type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/usr/local/cpanel/3rdparty/share type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/usr/local/cpanel/Cpanel type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/usr/local/cpanel/Whostmgr type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/usr/local/cpanel/base type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/usr/local/cpanel/cgi-priv type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/usr/local/cpanel/cpaddons type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/usr/local/cpanel/etc type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/usr/local/cpanel/hooks type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/usr/local/cpanel/htdocs type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/usr/local/cpanel/img-sys type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/usr/local/cpanel/install type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/usr/local/cpanel/lang type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/usr/local/cpanel/lib type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/usr/local/cpanel/libexec type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/usr/local/cpanel/locale type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/usr/local/cpanel/php type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/usr/local/cpanel/scripts type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/usr/local/cpanel/share type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/usr/local/cpanel/shared type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/usr/local/cpanel/sys_cpanel/boxtrapper-message type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/usr/local/cpanel/var type ext4 (rw,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/usr/local/cpanel/whostmgr type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/usr/local/cpanel/whostmgr/docroot/cgi/softaculous type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/usr/share/l.v.e-manager/cl.nodejs type ext4 (rw,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/usr/share/l.v.e-manager/cl.python type ext4 (rw,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/usr/share/locale type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/usr/share/man type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/usr/share/terminfo type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/usr/share/vim type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/usr/share/zoneinfo type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/var/cpanel/ea4 type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/var/lib/mysql type ext4 (rw,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/var/lib/proxyexec/cagefs.sock type ext4 (rw,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/var/lib/spamassassin type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +tmpfs on /usr/share/cagefs-skeleton/run/dbus type tmpfs (rw,nosuid,mode=755) +tmpfs on /usr/share/cagefs-skeleton/run/nscd type tmpfs (rw,nosuid,mode=755) +/dev/sda2 on /usr/share/cagefs-skeleton/var/softaculous type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/var/spool/at type ext4 (rw,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/var/www/cgi-bin type ext4 (rw,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/var/www/html type ext4 (rw,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/opt/suphp/sbin type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/opt/cpanel/ea-php73/root/usr/bin type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/opt/cpanel/ea-php73/root/etc type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/opt/cpanel/ea-php74/root/usr/bin type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/opt/cpanel/ea-php74/root/etc type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/opt/cpanel/ea-php80/root/usr/bin type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/opt/cpanel/ea-php80/root/etc type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +/dev/sda2 on /usr/share/cagefs-skeleton/var/lve/lveinfo.ver.cagefs type ext4 (ro,nosuid,relatime,data=ordered,jqfmt=vfsv1,usrjquota=quota.user) +proc on /usr/share/cagefs-skeleton/proc type proc (rw,nosuid,relatime,gid=1002,hidepid=2) +systemd-1 on /usr/share/cagefs-skeleton/proc/sys/fs/binfmt_misc type autofs (rw,nosuid,relatime,fd=34,pipe_ino=10005,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=10005) +tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=800880k,mode=700) +``` + +Is there anyway qemu-guest-agent can handle this? I saw a lot of users faced this problem since CloudLinux becomes more popular after RHEL halted future CentOS releases. + +CloudLinux has an option to umount/mount cagefs-skeleton, maybe it's something can be implemented - https://docs.cloudlinux.com/command-line_tools/ + +The same issue happens when JailShell is enabled on cPanel servers (OVH reported about) - https://docs.ovh.com/ca/en/vps/cpanel_auto_backup/ + +Thank you for your time. +Steps to reproduce: +1. Manually start backup for the VM with qemu-agent enabled. +2. The backup process stuck at "INFO: issuing guest-agent 'fs-freeze' command" +3. The VM become unavailable, you can only unlock it and force reset. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/593 b/gitlab/issues_text/target_missing/host_missing/accel_missing/593 new file mode 100644 index 000000000..888ee3bb6 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/593 @@ -0,0 +1,7 @@ +USB ECM network device does not work under XHCI +Description of problem: +No data is ever received by the USB ECM network device when it is attached to an XHCI controller. (USB 1.0 controllers work OK.) +Additional information: +There are some patches it appears were submitted to the GitHub mirror that resolve the problem (I tested them applied to git master, and confirmed they work): https://github.com/qemu/qemu/pull/100 + +I guess they never were submitted to the mailing list, or somehow got missed? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/595 b/gitlab/issues_text/target_missing/host_missing/accel_missing/595 new file mode 100644 index 000000000..30ab92735 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/595 @@ -0,0 +1,11 @@ +QEMU VNC mouse doesn't move in tablet mode os9 +Description of problem: +What I am trying to do is have a headless os9 running in QEMU on ubuntu and use the native vnc support in QEMU to access the screen. That is setup and works as expected but the mouse only works in ps/2 mode and that is clearly very undesirable (mouse is never lined up). I set it up in tablet mode and when I am in the QEMU window on the host the mouse works perfect (I added tablet mode to os9 with: https://github.com/kanjitalk755/macos9-usb-tablet). That same tablet mode results in the mouse not moving at all over vnc, if I ctrl+alt 2 and switch the mouse type from tablet mode it starts working again but not lined up at all as expected, cant get to any buttons on edges. Is there anyone in here that ran into this? Am I the only one using QEMU VNC? + +Iv thought about running a vnc application on the vm itself but performance was meh at best. Any tips would be worth a lot to me, its a sin to say but I am trying to adapt this into a production environment... + +Upon further investigation this seems to be a issue on Linux. I am testing the QEMU on windows and its working as expected over VNC. That is to say if QEMU is running on a windows host, it just works over vnc with tablet mode. So what could be causing Linux version to not work? I did compile it from source, are there any configure flags I am missing? I am trying to run it on Ubuntu server 21.04 +Steps to reproduce: +1.add vnc option to parameters +2.enable tablet mode and install driver in os9 +3.connect to vnc and mouse doesn't move diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/598 b/gitlab/issues_text/target_missing/host_missing/accel_missing/598 new file mode 100644 index 000000000..c24c0609d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/598 @@ -0,0 +1 @@ +QEMU boot kernel for ppc e300c3 problem diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/599 b/gitlab/issues_text/target_missing/host_missing/accel_missing/599 new file mode 100644 index 000000000..e4d8a747b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/599 @@ -0,0 +1,11 @@ +Q35: Windows BSOD running on 6.1.0 +Description of problem: +Starting with QEMU 6.1.0, Windows no longer boots with Q35 (including `pc-q35-6.0` as well). When booting an existing Windows 7 installation, BSOD appears during boot (0x0000007B). If you try to install Windows from an ISO, the follow error appears when you try to start setup. + + + +Other people also reported similar issues booting Windows 10, as well as during use of Windows XP. +Steps to reproduce: +Enter commands from above. +Additional information: +This was not an issue in QEMU 6.0.0. I can reproduce it at `master`. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/600 b/gitlab/issues_text/target_missing/host_missing/accel_missing/600 new file mode 100644 index 000000000..132cf76c6 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/600 @@ -0,0 +1 @@ +Have 'info mtree' accept an (optional) 'name' parameter to pick a specific address space diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/603 b/gitlab/issues_text/target_missing/host_missing/accel_missing/603 new file mode 100644 index 000000000..91ec0d639 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/603 @@ -0,0 +1 @@ +Unable to use mps2-an386 machine with qemu-6.0.0 version code diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/604 b/gitlab/issues_text/target_missing/host_missing/accel_missing/604 new file mode 100644 index 000000000..6ff8faec6 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/604 @@ -0,0 +1 @@ +QEMU crashes with "-global driver=isa-fdc" diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/605 b/gitlab/issues_text/target_missing/host_missing/accel_missing/605 new file mode 100644 index 000000000..43b84900c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/605 @@ -0,0 +1,15 @@ +QEMU crashes when receiving network connection on NetBSD +Description of problem: +After booting the VM, connecting to the TCP port 2222 of the host immediately crashes the VM and qemu prints: + +** +Slirp:ERROR:../slirp/src/tcp_subr.c:477:tcp_connect: assertion failed: (ret == 0) +Bail out! Slirp:ERROR:../slirp/src/tcp_subr.c:477:tcp_connect: assertion failed: (ret == 0) +Steps to reproduce: +1. start VM as indicated +2. telnet localhost 2222 +3. crash +Additional information: +** +Slirp:ERROR:../slirp/src/tcp_subr.c:477:tcp_connect: assertion failed: (ret == 0) +Bail out! Slirp:ERROR:../slirp/src/tcp_subr.c:477:tcp_connect: assertion failed: (ret == 0) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/606 b/gitlab/issues_text/target_missing/host_missing/accel_missing/606 new file mode 100644 index 000000000..c534ac3e2 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/606 @@ -0,0 +1 @@ +Gtk: gtk_clipboard_set_with_data: assertion 'targets != NULL' failed diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/607 b/gitlab/issues_text/target_missing/host_missing/accel_missing/607 new file mode 100644 index 000000000..7b9ea6848 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/607 @@ -0,0 +1,59 @@ +socket_sockaddr_to_address_unix: Assertion `salen >= sizeof(su->sun_family) + 1 && salen <= sizeof(struct sockaddr_un)' failed. +Description of problem: + +Steps to reproduce: +1. Run Qemu command line +2. Start console in virt-manager +Additional information: +_/var/log/libvirt/qemu_ + +``` +2021-09-08 13:08:22.003+0000: starting up libvirt version: 7.6.0, qemu version: 6.1.0, kernel: 5.4.143-1-MANJARO, hostname: pjehrsohmehj +LC_ALL=C \ +PATH=/usr/local/sbin:/usr/local/bin:/usr/bin \ +HOME=/var/lib/libvirt/qemu/domain-81-Vagrant_default \ +XDG_DATA_HOME=/var/lib/libvirt/qemu/domain-81-Vagrant_default/.local/share \ +XDG_CACHE_HOME=/var/lib/libvirt/qemu/domain-81-Vagrant_default/.cache \ +XDG_CONFIG_HOME=/var/lib/libvirt/qemu/domain-81-Vagrant_default/.config \ +/usr/bin/qemu-system-x86_64 \ +-name guest=Vagrant_default,debug-threads=on \ +-S \ +-object '{"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-81-Vagrant_default/master-key.aes"}' \ +-machine pc-i440fx-6.1,accel=kvm,usb=off,dump-guest-core=off,memory-backend=pc.ram \ +-cpu Snowridge,ss=on,vmx=on,hypervisor=on,tsc-adjust=on,mpx=on,rdpid=on,md-clear=on,stibp=on,xsaves=on,ibpb=on,ibrs=on,amd-stibp=on,amd-ssbd=on,rdctl-no=on,ibrs-all=on,skip-l1dfl-vmentry=on,mds-no=on,pschange-mc-no=on,clwb=off,gfni=off,cldemote=off,movdiri=off,movdir64b=off,core-capability=off,split-lock-detect=off \ +-m 512 \ +-object '{"qom-type":"memory-backend-ram","id":"pc.ram","size":536870912}' \ +-overcommit mem-lock=off \ +-smp 1,sockets=1,cores=1,threads=1 \ +-uuid cde944bb-cfc2-473b-b605-580382c3f944 \ +-no-user-config \ +-nodefaults \ +-chardev socket,id=charmonitor,fd=32,server=on,wait=off \ +-mon chardev=charmonitor,id=monitor,mode=control \ +-rtc base=utc \ +-no-shutdown \ +-boot strict=on \ +-device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 \ +-blockdev '{"driver":"file","filename":"/var/lib/libvirt/images/Zelec-VAGRANTSLASH-manjarolinux_vagrant_box_image_20210901.1551100290_box.img","node-name":"libvirt-2-storage","auto-read-only":true,"discard":"unmap"}' \ +-blockdev '{"node-name":"libvirt-2-format","read-only":true,"driver":"qcow2","file":"libvirt-2-storage","backing":null}' \ +-blockdev '{"driver":"file","filename":"/var/lib/libvirt/images/Vagrant_default.img","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' \ +-blockdev '{"node-name":"libvirt-1-format","read-only":false,"driver":"qcow2","file":"libvirt-1-storage","backing":"libvirt-2-format"}' \ +-device virtio-blk-pci,bus=pci.0,addr=0x3,drive=libvirt-1-format,id=virtio-disk0,bootindex=1 \ +-netdev tap,fd=34,id=hostnet0,vhost=on,vhostfd=35 \ +-device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:cf:27:78,bus=pci.0,addr=0x5 \ +-chardev pty,id=charserial0 \ +-device isa-serial,chardev=charserial0,id=serial0 \ +-audiodev id=audio1,driver=none \ +-vnc 127.0.0.1:0,audiodev=audio1 \ +-k en-us \ +-device cirrus-vga,id=video0,bus=pci.0,addr=0x2 \ +-device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 \ +-sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ +-msg timestamp=on +char device redirected to /dev/pts/0 (label charserial0) +2021-09-08T13:08:22.188784Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(48FH).vmx-exit-load-perf-global-ctrl [bit 12] +2021-09-08T13:08:22.188905Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(490H).vmx-entry-load-perf-global-ctrl [bit 13] +qemu-system-x86_64: ../qemu-6.1.0/util/qemu-sockets.c:1348: socket_sockaddr_to_address_unix: Assertion `salen >= sizeof(su->sun_family) + 1 && salen <= sizeof(struct sockaddr_un)' failed. +2021-09-08 13:08:28.059+0000: shutting down, reason=crashed +2 +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/608 b/gitlab/issues_text/target_missing/host_missing/accel_missing/608 new file mode 100644 index 000000000..1e42c7f22 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/608 @@ -0,0 +1 @@ +incremental_live_backup: Error prompt info when do incremental backup with an invalid "bitmap-mode" diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/609 b/gitlab/issues_text/target_missing/host_missing/accel_missing/609 new file mode 100644 index 000000000..41bd53271 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/609 @@ -0,0 +1,9 @@ +Can't build system emulation with static on qemu 6.1 +Description of problem: + +Steps to reproduce: +1. +2. +3. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/610 b/gitlab/issues_text/target_missing/host_missing/accel_missing/610 new file mode 100644 index 000000000..ee7537a72 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/610 @@ -0,0 +1,31 @@ +after upgrade to 6.1.0, snapshot creation fails with "pre-save failed: qxl" +Description of problem: +When trying to create a snapshot using `virsh --connect qemu:///system snapshot-create-as <domain-name> <snapshot-name>` or virt-manager GUI, I get the following error: + +``` +Error: Error while writing VM state: Unknown error -1 + + +Traceback (most recent call last): + File "/usr/share/virt-manager/virtManager/asyncjob.py", line 65, in cb_wrapper + callback(asyncjob, *args, **kwargs) + File "/usr/share/virt-manager/virtManager/details/snapshots.py", line 237, in _do_create_snapshot + self.vm.create_snapshot(xml) + File "/usr/share/virt-manager/virtManager/object/domain.py", line 1124, in create_snapshot + self._backend.snapshotCreateXML(xml, flags) + File "/usr/lib/python3.9/site-packages/libvirt.py", line 3059, in snapshotCreateXML + raise libvirtError('virDomainSnapshotCreateXML() failed') +libvirt.libvirtError: operation failed: Failed to take snapshot: pre-save failed: qxl +Error: Error while writing VM state: Unknown error -1 +``` +Additional information: +I'm using Arch Linux distro packages. +The issue appeared after upgrading qemu-headless from 6.0.0 to 6.1.0. +Downgrading back to 6.0.0 fixes the problem (snapshot are created +successfully and work as expected). + +In a reply to my message to libvirt-users describing the issue [1], +Daniel P. Berrangé confirmed that the error comes from QEMU and +recommended reporting it here. + +[1] https://listman.redhat.com/archives/libvirt-users/2021-September/msg00007.html diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/611 b/gitlab/issues_text/target_missing/host_missing/accel_missing/611 new file mode 100644 index 000000000..bc25d9ed2 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/611 @@ -0,0 +1,127 @@ +qemu-system-m68k: hw/scsi/scsi-disk.c assertion failure +Description of problem: +QEMU assertion failure (crash): +qemu-system-m68k: ../hw/scsi/scsi-disk.c:550: scsi_write_data: Assertion `r->req.aiocb == NULL' failed. +Steps to reproduce: +``` +$ xz -d initramfs-stress-ng.cpio.xz vmlinux-5.14-multi.xz +$ cat rootfs.ext2.xz-part? | xz -dc > rootfs.ext2 +$ qemu-system-m68k -M q800 -m 128M -serial none -serial mon:stdio -g 800x600x4 -rtc base=localtime -drive file=rootfs.ext2,format=raw -kernel vmlinux-5.14-multi -append "console=ttyS0" -initrd initramfs-stress-ng.cpio + +ABCFGHIJK +[ 0.000000] Linux version 5.14.0-multi (fthain@nippy) (m68k-linux-gnu-gcc (btc) 6.4.0, GNU ld (btc) 2.28) #5 Sat Sep 4 16:09:41 AEST 2021 +[ 0.000000] Saving 140 bytes of bootinfo +[ 0.000000] Detected Macintosh model: 35 +[ 0.000000] Apple Macintosh Quadra 800 +[ 0.000000] Zone ranges: +[ 0.000000] DMA [mem 0x0000000000000000-0x0000007fffffffff] +[ 0.000000] Normal empty +[ 0.000000] Movable zone start for each node +[ 0.000000] Early memory node ranges +[ 0.000000] node 0: [mem 0x0000000000000000-0x0000000007ffffff] +[ 0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x0000000007ffffff] +[ 0.000000] initrd: 07d3e000 - 07fff600 +[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 32480 +[ 0.000000] Kernel command line: console=ttyS0 +[ 0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes, linear) +[ 0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes, linear) +[ 0.000000] Sorting __ex_table... +[ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off +[ 0.000000] Memory: 121420K/131072K available (4074K kernel code, 327K rwdata, 752K rodata, 148K init, 117K bss, 9652K reserved, 0K cma-reserved) +[ 0.000000] SLUB: HWalign=16, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 +[ 0.000000] NR_IRQS: 200 +[ 0.000000] clocksource: via1: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 2439823894983 ns +[ 0.000000] Console: colour dummy device 80x25 +[ 0.010000] printk: console [ttyS0] enabled +[ 0.020000] Calibrating delay loop... 841.31 BogoMIPS (lpj=4206592) +[ 0.110000] pid_max: default: 32768 minimum: 301 +[ 0.110000] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear) +[ 0.110000] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear) +[ 0.150000] devtmpfs: initialized +[ 0.160000] random: get_random_u32 called from bucket_table_alloc.isra.28+0x70/0x1a6 with crng_init=0 +[ 0.160000] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns +[ 0.160000] futex hash table entries: 256 (order: -1, 3072 bytes, linear) +[ 0.160000] NET: Registered PF_NETLINK/PF_ROUTE protocol family +[ 0.170000] DMA: preallocated 128 KiB GFP_KERNEL pool for atomic allocations +[ 0.170000] DMA: preallocated 128 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations +[ 0.200000] wait_for_initramfs() called before rootfs_initcalls +[ 0.220000] NuBus: Scanning NuBus slots. +[ 0.220000] Slot 9: Board resource not found! +[ 0.220000] SCSI subsystem initialized +[ 0.240000] clocksource: Switched to clocksource via1 +[ 0.260000] NET: Registered PF_INET protocol family +[ 0.260000] IP idents hash table entries: 2048 (order: 2, 16384 bytes, linear) +[ 0.270000] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes, linear) +[ 0.270000] TCP established hash table entries: 1024 (order: 0, 4096 bytes, linear) +[ 0.270000] TCP bind hash table entries: 1024 (order: 0, 4096 bytes, linear) +[ 0.270000] TCP: Hash tables configured (established 1024 bind 1024) +[ 0.270000] UDP hash table entries: 256 (order: 0, 4096 bytes, linear) +[ 0.270000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes, linear) +[ 0.270000] NET: Registered PF_UNIX/PF_LOCAL protocol family +[ 0.280000] RPC: Registered named UNIX socket transport module. +[ 0.280000] RPC: Registered udp transport module. +[ 0.280000] RPC: Registered tcp transport module. +[ 0.280000] RPC: Registered tcp NFSv4.1 backchannel transport module. +[ 0.290000] Trying to unpack rootfs image as initramfs... +[ 0.290000] workingset: timestamp_bits=30 max_order=15 bucket_order=0 +[ 0.310000] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) +[ 0.310000] io scheduler mq-deadline registered +[ 0.310000] macfb: framebuffer at 0xf9001000, mapped to 0x(ptrval), size 234k +[ 0.310000] macfb: mode is 800x600x4, linelength=400 +[ 0.330000] Console: switching to colour frame buffer device 100x37 +[ 0.350000] fb0: DAFB frame buffer device +[ 0.350000] pmac_zilog: 0.6 (Benjamin Herrenschmidt <benh@kernel.crashing.org>) +[ 0.350000] scc.0: ttyS0 at MMIO 0x5000c022 (irq = 4, base_baud = 230400) is a Z85c30 ESCC - Serial port +[ 0.350000] scc.1: ttyS1 at MMIO 0x5000c020 (irq = 4, base_baud = 230400) is a Z85c30 ESCC - Serial port +[ 0.350000] Non-volatile memory driver v1.3 +[ 0.390000] brd: module loaded +[ 0.390000] adb: Mac II ADB Driver v1.0 for Unified ADB +[ 0.410000] Detected ADB keyboard, type ANSI. +[ 0.410000] input: ADB keyboard as /devices/virtual/input/input0 +[ 0.420000] random: fast init done +[ 0.420000] input: ADB mouse as /devices/virtual/input/input1 +[ 0.430000] Freeing initrd memory: 2820K +[ 0.430000] mac_esp: using PDMA for controller 0 +[ 0.430000] mac_esp mac_esp.0: esp0: regs[(ptrval):0] irq[19] +[ 0.430000] mac_esp mac_esp.0: esp0: is a ESP236, 16 MHz (ccf=4), SCSI ID 7 +[ 3.520000] scsi host0: esp +[ 3.530000] scsi 0:0:0:0: Direct-Access QEMU QEMU HARDDISK 2.5+ PQ: 0 ANSI: 5 +[ 3.540000] scsi target0:0:0: Beginning Domain Validation +[ 3.540000] scsi target0:0:0: Domain Validation skipping write tests +[ 3.540000] scsi target0:0:0: Ending Domain Validation +[ 3.550000] scsi 0:0:2:0: CD-ROM QEMU QEMU CD-ROM 2.5+ PQ: 0 ANSI: 5 +[ 3.550000] scsi target0:0:2: Beginning Domain Validation +[ 3.560000] scsi target0:0:2: Domain Validation skipping write tests +[ 3.560000] scsi target0:0:2: Ending Domain Validation +[ 3.560000] sr 0:0:2:0: Power-on or device reset occurred +[ 3.570000] sr 0:0:2:0: [sr0] scsi3-mmc drive: 16x/50x cd/rw xa/form2 cdda tray +[ 3.570000] cdrom: Uniform CD-ROM driver Revision: 3.20 +[ 3.570000] sd 0:0:0:0: Power-on or device reset occurred +[ 3.580000] sd 0:0:0:0: [sda] 322560 512-byte logical blocks: (165 MB/158 MiB) +[ 3.580000] sd 0:0:0:0: [sda] Write Protect is off +[ 3.580000] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA +[ 3.590000] sd 0:0:0:0: Attached scsi generic sg0 type 0 +[ 3.590000] sr 0:0:2:0: Attached scsi generic sg1 type 5 +[ 3.590000] Onboard/comm-slot SONIC, revision 0x0004, 32 bit DMA, register offset 2 +[ 3.590000] SONIC ethernet @50f0a000, MAC 08:00:07:12:34:56, IRQ 3 +[ 3.600000] sd 0:0:0:0: [sda] Attached SCSI disk +[ 3.610000] aoe: AoE v85 initialised. +[ 3.610000] mousedev: PS/2 mouse device common for all mice +[ 3.610000] rtc-generic rtc-generic: registered as rtc0 +[ 3.620000] NET: Registered PF_PACKET protocol family +[ 3.630000] Freeing unused kernel image (initmem) memory: 148K +[ 3.630000] This architecture does not have kernel memory protection. +[ 3.630000] Run /init as init process +/init: line 11: ifconfig: not found +# mount /dev/sda /mnt +[ 9.030000] EXT4-fs (sda): mounting ext2 file system using the ext4 subsystem +[ 9.080000] EXT4-fs (sda): mounted filesystem without journal. Opts: (null). Quota mode: disabled. +# cd /mnt +# /root/stress-ng --mmap -1 --mmap-file --mmap-bytes=100% +stress-ng: info: [42] defaulting to a 86400 second (1 day, 0.00 secs) run per stressor +stress-ng: info: [42] dispatching hogs: 1 mmap +qemu-system-m68k: ../hw/scsi/scsi-disk.c:550: scsi_write_data: Assertion `r->req.aiocb == NULL' failed. +Aborted +``` +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/614 b/gitlab/issues_text/target_missing/host_missing/accel_missing/614 new file mode 100644 index 000000000..1d5bf40f5 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/614 @@ -0,0 +1 @@ +Newly introduced dependency on GCC 7.5.0 should allow any version of GCC 7 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/615 b/gitlab/issues_text/target_missing/host_missing/accel_missing/615 new file mode 100644 index 000000000..d69e499bd --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/615 @@ -0,0 +1,10 @@ +Not sure if this is a qemu issue but SD card is not correctly read. blk_update_request: I/O error on Manjaro libvirt OS. +Description of problem: + +Steps to reproduce: +1. Run vagrant command line +2. Start console in virt-manager +3. Add USB SD card reader device with SD card. +4. Go back to console +Additional information: +I've bought a new SD card reader and SD card, tried it on other ports and the problem persists. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/617 b/gitlab/issues_text/target_missing/host_missing/accel_missing/617 new file mode 100644 index 000000000..98d937313 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/617 @@ -0,0 +1,26 @@ +USB passthrough with Conbee 2 failing after upgrade to Fedora 34 / Libvirt 7.0.0 +Description of problem: +Hi, + +I upgraded recently from Fedora 32 to 34. + +For a little under a year, I've been running reliably a Home Assistant instance with Deconz add-on in a VM, with a Conbee 2 zigbee gateway in USB passthrough, controlling about 15 devices (door/window sensors, thermometers, leak sensors and push buttons). + +It has worked flawlessly but stopped working after upgrading Fedora. The Conbee shows up on the Linux guest but the serial can't be read by the Deconz application and it just does not work, the app can't get past the device connection screen. + +This is the state of what works and what doesn't: + +- Home Assistant Linux VM: NOK +- Ubuntu Linux 20.04 VM: NOK +- Windows 10 VM: NOK +- Windows 10 physical machine: OK, can connect and pair a door sensor + +All running the latest Deconz app. + +The fact that the physical Windows machine works excludes a bricked device. I used the physical Windows to upgrade the Conbee 2 firmware with no improvement. + +This does not seem to be an isolated issue: https://old.reddit.com/r/homeassistant/comments/o04sgw/conbee_ii_usb_passthrough_with_libvirt_660/ + +Apologies if this has already been reported. Let me know what kind of logs you might want. + +Thanks! diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/62 b/gitlab/issues_text/target_missing/host_missing/accel_missing/62 new file mode 100644 index 000000000..f6dd00704 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/62 @@ -0,0 +1 @@ +[OSS-Fuzz] ahci: stack overflow in ahci_cond_start_engines diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/621 b/gitlab/issues_text/target_missing/host_missing/accel_missing/621 new file mode 100644 index 000000000..1dd7649e8 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/621 @@ -0,0 +1 @@ +make after configure not working diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/623 b/gitlab/issues_text/target_missing/host_missing/accel_missing/623 new file mode 100644 index 000000000..6da549064 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/623 @@ -0,0 +1,8 @@ +Allow direct access to windows disks on hyper-V as well as virtiofsd, DAX +Additional information: +Depends on, first needs fixing of, Issue #346 / Issue #430 , Essentially accel=whpx is not working/is broken/has regression. +``` +J:\>E:\scoopg\shims\qemu-system-x86_64.exe --version +QEMU emulator version 6.1.0 (v6.1.0-11882-g7deea770bf-dirty) +Copyright (c) 2003-2021 Fabrice Bellard and the QEMU Project developers +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/630 b/gitlab/issues_text/target_missing/host_missing/accel_missing/630 new file mode 100644 index 000000000..1777d5a75 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/630 @@ -0,0 +1 @@ +ubuntu-18.04-s390x-all job timeouts at 1h diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/631 b/gitlab/issues_text/target_missing/host_missing/accel_missing/631 new file mode 100644 index 000000000..6328d70dd --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/631 @@ -0,0 +1,25 @@ +QEMU locks out user interface after waking from laptop sleep +Description of problem: +If qemu is started on laptop from command line and set to full screen, screen activated with mouse click, then put to sleep by closing lid; after waking up by opening lid the user interface locks out, the mouse cursor doesn't show, mouse clicks and keys are unresponsive. + +A Ctrl-ALt-Fn terminal must then be used to locate and kill the qemu process. After which the system can recover if it is terminated. The system tends to be affected in other ways such as wifi being disabled and needs to manually enabled after. So it looks like it disrupts the system from fully restoring the awoken state. + +The terminal from which QEMU is running is also filled with debug output. The issue looks to be caused by the SDL backend not knowing what to do with a wake up code. The terminal window is filled with the following text: +`The key you just pressed is not recognized by SDL. To help get this fixed, please report this to the SDL forums/mailing list <https://discourse.libsdl.org/> X11 KeyCode 151 (143), X11 KeySym 0x1008FF2B (XF86WakeUp).` + +I have reduced the steps causing the bug to as little as needed with low dependencies. +Steps to reproduce: +1. Using a laptop, start a qemu session in full screen like so: + `./qemu-system-ppc -machine mac99,via=pmu -serial stdio -full-screen` +2. Shut the lid so it sleeps. +3. Shortly after open the lid. +Additional information: +I downloaded the 6.1.0 stable build and compiled it myself. + +The SDL issue appears to be low priority. I found some reports here but see no evidence of it being discussed. +https://discourse.libsdl.org/t/key-not-recognised-by-sdl/24181 + + + + + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/632 b/gitlab/issues_text/target_missing/host_missing/accel_missing/632 new file mode 100644 index 000000000..d119846f3 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/632 @@ -0,0 +1 @@ +We should document "make install DESTDIR=wherever" diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/634 b/gitlab/issues_text/target_missing/host_missing/accel_missing/634 new file mode 100644 index 000000000..37ae497a5 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/634 @@ -0,0 +1,81 @@ +usbredir: assertion failure after suspend/resume when stopped +Description of problem: +Accessing a USB smart card ([Yubikey 5 NFC](https://www.yubico.com/product/yubikey-5-nfc/)) from the guest after host suspend/resume while the guest is stopped and the device is redirected causes QEMU to crash with "Segmentation fault" (with master) or the assertion failure (with Debian 1:6.1+dfsg-5): + + qemu-system-x86_64: ../../hw/usb/core.c:470: usb_packet_complete_one: Assertion `p->stream || QTAILQ_FIRST(&ep->queue) == p' failed. +Steps to reproduce: +1. Run `qemu-system-x86_64` with command line listed above. +2. Run `remote-viewer spice://localhost:3001` in another terminal. +3. Redirect the smart card to the guest in remote-viewer. +4. Run `gpg --card-status` in the guest. +5. Run `stop` in the QEMU monitor. +6. Run `rtcwake --mode mem --seconds 1` as root to suspend the host to S3, then resume. (or `ehco mem >/sys/power/state` or `systemctl suspend` then wake manually) +7. Run `cont` in QEMU monitor to resume the guest. +8. Stop redirecting the smart card to the guest in remote-viewer. +9. Start redirecting the smart card to the guest in remote-viewer. +10. Run `gpg --card-status` in the guest. Repeat if necessary. + +Note that after step 7 the train has left the rails. Executing `gpg --card-status` in the guest at this point would print: + + gpg: selecting card failed: no such device + gpg: OpenPGP card not available: no such device + +However, stopping and resuming redirection appears to be necessary to trigger the assertion failure. + +Also note that on Windows, it's not necessary to execute any `gpg` commands. QEMU will hit the assertion failure after step 9. +Additional information: +<details> +<summary>backtrace with version built from 2c3e83f92d</summary> + + Program terminated with signal SIGSEGV, Segmentation fault. + #0 0x00005623c09a5754 in usb_handle_packet + (dev=0x5623c3592500, p=p@entry=0x7f92e43c81c8) at ../hw/usb/core.c:441 + #1 0x00005623c09be239 in xhci_submit + (epctx=<optimized out>, xfer=<optimized out>, xhci=<optimized out>) + at ../hw/usb/hcd-xhci.c:1783 + #2 xhci_fire_transfer + (epctx=<optimized out>, xfer=<optimized out>, xhci=<optimized out>) + at ../hw/usb/hcd-xhci.c:1792 + #3 xhci_kick_epctx (epctx=0x7f92e43c7c30, streamid=0) + at ../hw/usb/hcd-xhci.c:1951 + #4 0x00005623c09bea1b in xhci_kick_ep + (xhci=<optimized out>, slotid=<optimized out>, epid=<optimized out>, streamid=<optimized out>) at ../hw/usb/hcd-xhci.c:1817 + #5 0x00005623c09bebd8 in xhci_doorbell_write + (ptr=0x7f92ec137970, reg=1, val=4, size=<optimized out>) + at ../hw/usb/hcd-xhci.c:3118 + #6 0x00005623c0abbc7f in memory_region_write_accessor + (mr=mr@entry=0x7f92ec137ed0, addr=4, value=value@entry=0x7f92eda403e8, size=size@entry=4, shift=<optimized out>, mask=mask@entry=4294967295, attrs=...) + at ../softmmu/memory.c:492 + #7 0x00005623c0ab953e in access_with_adjusted_size + (addr=addr@entry=4, value=value@entry=0x7f92eda403e8, size=size@entry=4, access_size_min=<optimized out>, access_size_max=<optimized out>, access_fn= + 0x5623c0abbc00 <memory_region_write_accessor>, mr=0x7f92ec137ed0, attrs=...) at ../softmmu/memory.c:554 + #8 0x00005623c0abd650 in memory_region_dispatch_write + (mr=mr@entry=0x7f92ec137ed0, addr=4, data=<optimized out>, op=<optimized out>, attrs=attrs@entry=...) at ../softmmu/memory.c:1511 + #9 0x00005623c0aad417 in flatview_write_continue + (fv=fv@entry=0x7f92e43c7140, addr=addr@entry=4227932164, attrs=attrs@entry=..., ptr=ptr@entry=0x7f92ef17f028, len=len@entry=4, addr1=<optimized out>, l=<optimized out>, mr=0x7f92ec137ed0) + at /home/kevin/tmp/qemu/include/qemu/host-utils.h:165 + #10 0x00005623c0ab09db in flatview_write + (len=4, buf=0x7f92ef17f028, attrs=..., addr=4227932164, fv=0x7f92e43c7140) + at ../softmmu/physmem.c:2820 + #11 address_space_write + (as=<optimized out>, addr=4227932164, attrs=..., buf=buf@entry=0x7f92ef17f028, len=4) at ../softmmu/physmem.c:2912 + #12 0x00005623c0ab0a9f in address_space_rw + (as=<optimized out>, addr=<optimized out>, attrs=..., + attrs@entry=..., buf=buf@entry=0x7f92ef17f028, len=<optimized out>, is_write=<optimized out>) at ../softmmu/physmem.c:2922 + #13 0x00005623c0ba2890 in kvm_cpu_exec (cpu=cpu@entry=0x5623c2729bc0) + at ../accel/kvm/kvm-all.c:2893 + #14 0x00005623c0ba3bbd in kvm_vcpu_thread_fn (arg=arg@entry=0x5623c2729bc0) + at ../accel/kvm/kvm-accel-ops.c:49 + #15 0x00005623c0d0a959 in qemu_thread_start (args=0x7f92eda40610) + at ../util/qemu-thread-posix.c:557 + #16 0x00007f92fd431eae in start_thread (arg=0x7f92eda45640) + at pthread_create.c:463 + #17 0x00007f92fca2fa5f in clone () + at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 + +</details> + +Let me know if there are any additional logs or information that would be useful. + +Thanks,\ +Kevin diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/637 b/gitlab/issues_text/target_missing/host_missing/accel_missing/637 new file mode 100644 index 000000000..f8264de17 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/637 @@ -0,0 +1,4 @@ +qemu drive-mirror live migration sparse copy +Additional information: +Please reference this Proxmox post where the developers mention this feature not being available: +https://forum.proxmox.com/threads/migration-on-lvm-thin.50429/ diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/640 b/gitlab/issues_text/target_missing/host_missing/accel_missing/640 new file mode 100644 index 000000000..a0e703192 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/640 @@ -0,0 +1,6 @@ +qemu-system-x86_64 behaving as 32 bits +Description of problem: +Qemu is throwing the error ```file '/grub/i386-pc/normal.mod' not found.``` and going into rescue mode while booting my pendrive with a dual boot installation from scratch from [link](https://wiki.archlinux.org/title/Multiboot_USB_drive). +The files like normal.mod aren't in the i386-pc folder because it's a x86 architecture install. The path it was supposed to see it is ```/grub/x86_64-efi/normal.mod``` +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/642 b/gitlab/issues_text/target_missing/host_missing/accel_missing/642 new file mode 100644 index 000000000..131e354f6 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/642 @@ -0,0 +1,4 @@ +Slow QEMU I/O on macOS host +Description of problem: +QEMU on macOS host gives very low I/O speed. Tested with fio tool, compared to linux host +Tested on QEMU v6.1.0, and the recent master diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/643 b/gitlab/issues_text/target_missing/host_missing/accel_missing/643 new file mode 100644 index 000000000..ceaa06cd7 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/643 @@ -0,0 +1 @@ +how to add include path and library path when building qemu-4.1.1 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/645 b/gitlab/issues_text/target_missing/host_missing/accel_missing/645 new file mode 100644 index 000000000..4837836f6 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/645 @@ -0,0 +1 @@ +Centos6.8 compiling qeum-2.12.0 failed, Does centos6.8 not support qeum-2.12.0? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/646 b/gitlab/issues_text/target_missing/host_missing/accel_missing/646 new file mode 100644 index 000000000..b462ef18d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/646 @@ -0,0 +1,18 @@ +Infinite loop in xhci_ring_chain_length() in hw/usb/hcd-xhci.c (CVE-2020-14394) +Description of problem: +An infinite loop issue was found in the USB xHCI controller emulation of QEMU. Specifically, function `xhci_ring_chain_length()` in hw/usb/hcd-xhci.c may get stuck while fetching empty TRBs from guest memory, since the exit conditions of the loop depend on values that are fully controlled by guest. A privileged guest user may exploit this issue to hang the QEMU process on the host, resulting in a denial of service. +Steps to reproduce: +Build and load `xhci.ko` from within the guest: + +1) make +2) insmod xhci.ko + +[Makefile](/uploads/98dbf7b4facc9b100817b3c8f63b5cb2/Makefile) + +[usb-xhci.h](/uploads/f225524b1553d8cf6c1dfa89369b6edc/usb-xhci.h) + +[xhci.c](/uploads/c635f742d12a2bba6ea472ddfe006d56/xhci.c) +Additional information: +This issue was reported by Gaoning Pan (Zhejiang University) and Xingwei Li (Ant Security Light-Year Lab). + +RH bug: https://bugzilla.redhat.com/show_bug.cgi?id=1908004. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/647 b/gitlab/issues_text/target_missing/host_missing/accel_missing/647 new file mode 100644 index 000000000..c50c0bdea --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/647 @@ -0,0 +1,301 @@ +scsi_device_purge_requests() waits infinietly +Description of problem: +QEMU hangs typing `system_reset` in the monitor, the monitor becomes unresponsive, as does VNC. +Steps to reproduce: +1. In the guest as root: `dd if=/dev/sda ibs=2K obs=1M of=/dev/null` +2. In the host monitor: `(qemu) system_reset` +3. Attach with gdb +4. Press ^C in the unresponsive monitor +``` +Thread 1 "qemu-system-x86" received signal SIGINT, Interrupt. +0x00007ffff749796e in ppoll () from /lib64/libc.so.6 +(gdb) bt +#0 0x00007ffff749796e in ppoll () at /lib64/libc.so.6 +#1 0x00005555570e829a in ppoll () +#2 0x0000555559624473 in qemu_poll_ns (fds=0x6060000204e0, nfds=1, timeout=-1) at ../util/qemu-timer.c:336 +#3 0x0000555559651973 in fdmon_poll_wait (ctx=0x61300004d900, ready_list=0x7fffffffb200, timeout=-1) at ../util/fdmon-poll.c:80 +#4 0x00005555595f48f1 in aio_poll (ctx=0x61300004d900, blocking=true) at ../util/aio-posix.c:607 +#5 0x0000555559041dac in bdrv_do_drained_begin (bs=0x62900000a200, recursive=false, parent=0x0, ignore_bds_parents=false, poll=true) at ../block/io.c:473 +#6 0x00005555590414a3 in bdrv_drained_begin (bs=0x62900000a200) at ../block/io.c:479 +#7 0x000055555916f180 in blk_drain (blk=0x618000001080) at ../block/block-backend.c:1732 +#8 0x000055555778f140 in scsi_device_purge_requests (sdev=0x617000004d80, sense=...) at ../hw/scsi/scsi-bus.c:1638 +#9 0x0000555557842df9 in scsi_disk_reset (dev=0x617000004d80) at ../hw/scsi/scsi-disk.c:2248 +#10 0x00005555592a557e in device_transitional_reset (obj=0x617000004d80) at ../hw/core/qdev.c:1028 +#11 0x00005555592a7eb7 in resettable_phase_hold (obj=0x617000004d80, opaque=0x0, type=RESET_TYPE_COLD) at ../hw/core/resettable.c:182 +#12 0x000055555928a2e8 in bus_reset_child_foreach (obj=0x62d0000268d8, cb=0x5555592a78e0 <resettable_phase_hold>, opaque=0x0, type=RESET_TYPE_COLD) at ../hw/core/bus.c:97 +#13 0x00005555592aaaac in resettable_child_foreach (rc=0x60e000026f40, obj=0x62d0000268d8, cb=0x5555592a78e0 <resettable_phase_hold>, opaque=0x0, type=RESET_TYPE_COLD) at ../hw/core/resettable.c:96 +#14 0x00005555592a7b9a in resettable_phase_hold (obj=0x62d0000268d8, opaque=0x0, type=RESET_TYPE_COLD) at ../hw/core/resettable.c:173 +#15 0x00005555592a1c55 in device_reset_child_foreach (obj=0x62d000026680, cb=0x5555592a78e0 <resettable_phase_hold>, opaque=0x0, type=RESET_TYPE_COLD) at ../hw/core/qdev.c:366 +#16 0x00005555592aaaac in resettable_child_foreach (rc=0x60e000040a80, obj=0x62d000026680, cb=0x5555592a78e0 <resettable_phase_hold>, opaque=0x0, type=RESET_TYPE_COLD) at ../hw/core/resettable.c:96 +#17 0x00005555592a7b9a in resettable_phase_hold (obj=0x62d000026680, opaque=0x0, type=RESET_TYPE_COLD) at ../hw/core/resettable.c:173 +#18 0x000055555928a2e8 in bus_reset_child_foreach (obj=0x62d0000265f8, cb=0x5555592a78e0 <resettable_phase_hold>, opaque=0x0, type=RESET_TYPE_COLD) at ../hw/core/bus.c:97 +#19 0x00005555592aaaac in resettable_child_foreach (rc=0x60e000026680, obj=0x62d0000265f8, cb=0x5555592a78e0 <resettable_phase_hold>, opaque=0x0, type=RESET_TYPE_COLD) at ../hw/core/resettable.c:96 +#20 0x00005555592a7b9a in resettable_phase_hold (obj=0x62d0000265f8, opaque=0x0, type=RESET_TYPE_COLD) at ../hw/core/resettable.c:173 +#21 0x00005555592a1c55 in device_reset_child_foreach (obj=0x62d00001e400, cb=0x5555592a78e0 <resettable_phase_hold>, opaque=0x0, type=RESET_TYPE_COLD) at ../hw/core/qdev.c:366 +#22 0x00005555592aaaac in resettable_child_foreach (rc=0x60e000042300, obj=0x62d00001e400, cb=0x5555592a78e0 <resettable_phase_hold>, opaque=0x0, type=RESET_TYPE_COLD) at ../hw/core/resettable.c:96 +#23 0x00005555592a7b9a in resettable_phase_hold (obj=0x62d00001e400, opaque=0x0, type=RESET_TYPE_COLD) at ../hw/core/resettable.c:173 +#24 0x000055555928a2e8 in bus_reset_child_foreach (obj=0x62200005c260, cb=0x5555592a78e0 <resettable_phase_hold>, opaque=0x0, type=RESET_TYPE_COLD) at ../hw/core/bus.c:97 +#25 0x00005555592aaaac in resettable_child_foreach (rc=0x60e00002e2c0, obj=0x62200005c260, cb=0x5555592a78e0 <resettable_phase_hold>, opaque=0x0, type=RESET_TYPE_COLD) at ../hw/core/resettable.c:96 +#26 0x00005555592a7b9a in resettable_phase_hold (obj=0x62200005c260, opaque=0x0, type=RESET_TYPE_COLD) at ../hw/core/resettable.c:173 +#27 0x00005555592a1c55 in device_reset_child_foreach (obj=0x62200005b900, cb=0x5555592a78e0 <resettable_phase_hold>, opaque=0x0, type=RESET_TYPE_COLD) at ../hw/core/qdev.c:366 +#28 0x00005555592aaaac in resettable_child_foreach (rc=0x60e000030940, obj=0x62200005b900, cb=0x5555592a78e0 <resettable_phase_hold>, opaque=0x0, type=RESET_TYPE_COLD) at ../hw/core/resettable.c:96 +#29 0x00005555592a7b9a in resettable_phase_hold (obj=0x62200005b900, opaque=0x0, type=RESET_TYPE_COLD) at ../hw/core/resettable.c:173 +#30 0x000055555928a2e8 in bus_reset_child_foreach (obj=0x61d00008a280, cb=0x5555592a78e0 <resettable_phase_hold>, opaque=0x0, type=RESET_TYPE_COLD) at ../hw/core/bus.c:97 +#31 0x00005555592aaaac in resettable_child_foreach (rc=0x60e00002e2c0, obj=0x61d00008a280, cb=0x5555592a78e0 <resettable_phase_hold>, opaque=0x0, type=RESET_TYPE_COLD) at ../hw/core/resettable.c:96 +#32 0x00005555592a7b9a in resettable_phase_hold (obj=0x61d00008a280, opaque=0x0, type=RESET_TYPE_COLD) at ../hw/core/resettable.c:173 +#33 0x00005555592a1c55 in device_reset_child_foreach (obj=0x62a000006200, cb=0x5555592a78e0 <resettable_phase_hold>, opaque=0x0, type=RESET_TYPE_COLD) at ../hw/core/qdev.c:366 +#34 0x00005555592aaaac in resettable_child_foreach (rc=0x60e000030160, obj=0x62a000006200, cb=0x5555592a78e0 <resettable_phase_hold>, opaque=0x0, type=RESET_TYPE_COLD) at ../hw/core/resettable.c:96 +#35 0x00005555592a7b9a in resettable_phase_hold (obj=0x62a000006200, opaque=0x0, type=RESET_TYPE_COLD) at ../hw/core/resettable.c:173 +#36 0x000055555928a2e8 in bus_reset_child_foreach (obj=0x60c000020a40, cb=0x5555592a78e0 <resettable_phase_hold>, opaque=0x0, type=RESET_TYPE_COLD) at ../hw/core/bus.c:97 +#37 0x00005555592aaaac in resettable_child_foreach (rc=0x60e00002fde0, obj=0x60c000020a40, cb=0x5555592a78e0 <resettable_phase_hold>, opaque=0x0, type=RESET_TYPE_COLD) at ../hw/core/resettable.c:96 +#38 0x00005555592a7b9a in resettable_phase_hold (obj=0x60c000020a40, opaque=0x0, type=RESET_TYPE_COLD) at ../hw/core/resettable.c:173 +#39 0x00005555592a6e04 in resettable_assert_reset (obj=0x60c000020a40, type=RESET_TYPE_COLD) at ../hw/core/resettable.c:60 +#40 0x00005555592a6cb7 in resettable_reset (obj=0x60c000020a40, type=RESET_TYPE_COLD) at ../hw/core/resettable.c:45 +#41 0x00005555592a9337 in resettable_cold_reset_fn (opaque=0x60c000020a40) at ../hw/core/resettable.c:269 +#42 0x00005555592a6c35 in qemu_devices_reset () at ../hw/core/reset.c:69 +#43 0x00005555582fb4f5 in pc_machine_reset (machine=0x616000000380) at ../hw/i386/pc.c:1764 +#44 0x0000555558a58e56 in qemu_system_reset (reason=SHUTDOWN_CAUSE_HOST_QMP_SYSTEM_RESET) at ../softmmu/runstate.c:443 +#45 0x0000555558a5a746 in main_loop_should_exit () at ../softmmu/runstate.c:688 +#46 0x0000555558a5a57e in qemu_main_loop () at ../softmmu/runstate.c:722 +#47 0x00005555571acaef in main (argc=58, argv=0x7fffffffd8f8, envp=0x7fffffffdad0) at ../softmmu/main.c:50 +(gdb) +(gdb) fr 5 +#5 0x0000555559041dac in bdrv_do_drained_begin (bs=0x62900000a200, recursive=false, parent=0x0, ignore_bds_parents=false, poll=true) at ../block/io.c:473 +473 BDRV_POLL_WHILE(bs, bdrv_drain_poll_top_level(bs, recursive, parent)); +(gdb) p *bs +$1 = {open_flags = 24578, encrypted = false, sg = false, probed = false, force_share = false, implicit = false, drv = 0x55555b0b0c60 <bdrv_qcow2>, opaque = 0x615000015200, aio_context = 0x6130000df080, + aio_notifiers = {lh_first = 0x0}, walking_aio_notifiers = false, filename = "nvme://0000:bc:00.0/1", '\000' <repeats 4074 times>, backing_file = '\000' <repeats 4095 times>, + auto_backing_file = '\000' <repeats 4095 times>, backing_format = '\000' <repeats 15 times>, full_open_options = 0x621002ba2100, exact_filename = "nvme://0000:bc:00.0/1", '\000' <repeats 4074 times>, + backing = 0x0, file = 0x608000002ba0, bl = {request_alignment = 1, max_pdiscard = 0, pdiscard_alignment = 65536, max_pwrite_zeroes = 0, pwrite_zeroes_alignment = 65536, opt_transfer = 0, + max_transfer = 131072, max_hw_transfer = 0, min_mem_alignment = 512, opt_mem_alignment = 4096, max_iov = 1024}, supported_read_flags = 0, supported_write_flags = 0, supported_zero_flags = 260, + supported_truncate_flags = 2, node_name = "drive_nvme1", '\000' <repeats 20 times>, node_list = {tqe_next = 0x0, tqe_circ = {tql_next = 0x0, tql_prev = 0x6290000092d0}}, bs_list = {tqe_next = 0x0, + tqe_circ = {tql_next = 0x0, tql_prev = 0x6290000092e0}}, monitor_list = {tqe_next = 0x0, tqe_circ = {tql_next = 0x0, tql_prev = 0x6290000092f0}}, refcnt = 2, op_blockers = {{ + lh_first = 0x0} <repeats 16 times>}, inherits_from = 0x0, children = {lh_first = 0x608000002ba0}, parents = {lh_first = 0x608000003620}, options = 0x621000019100, explicit_options = 0x62100001a500, + detect_zeroes = BLOCKDEV_DETECT_ZEROES_OPTIONS_OFF, backing_blocker = 0x0, total_sectors = 41943040, write_threshold_offset = 0, dirty_bitmap_mutex = {lock = {__data = {__lock = 0, __count = 0, __owner = 0, + __nusers = 0, __kind = 0, __spins = 0, __elision = 0, __list = {__prev = 0x0, __next = 0x0}}, __size = '\000' <repeats 39 times>, __align = 0}, file = 0x0, line = 0, initialized = true}, + dirty_bitmaps = {lh_first = 0x0}, wr_highest_offset = {value = 17686634496}, copy_on_read = 0, in_flight = 128, serialising_in_flight = 0, io_plugged = 0, enable_write_cache = 0, quiesce_counter = 1, + recursive_quiesce_counter = 0, write_gen = 101, reqs_lock = {locked = 0, ctx = 0x0, from_push = {slh_first = 0x0}, to_pop = {slh_first = 0x0}, handoff = 0, sequence = 0, holder = 0x0}, tracked_requests = { + lh_first = 0x7ffc251b48a0}, flush_queue = {entries = {sqh_first = 0x0, sqh_last = 0x62900000e470}}, active_flush_req = false, flushed_gen = 81, never_freeze = false} +(gdb) fr 4 +#4 0x00005555595f48f1 in aio_poll (ctx=0x61300004d900, blocking=true) at ../util/aio-posix.c:607 +607 ret = ctx->fdmon_ops->wait(ctx, &ready_list, timeout); +(gdb) p timeout +$5 = -1 +(gdb) p blocking +$6 = true +(gdb) p *ctx +$3 = {source = {callback_data = 0x0, callback_funcs = 0x0, source_funcs = 0x55555b42d900 <aio_source_funcs>, ref_count = 2, context = 0x60f000000400, priority = 0, flags = 33, source_id = 1, + poll_fds = 0x615000001790 = {0x60d000000860}, prev = 0x0, next = 0x61300004d3c0, name = 0x602000010a10 "aio-context", priv = 0x619000003830}, lock = {m = {lock = {__data = {__lock = 0, __count = 0, + __owner = 0, __nusers = 0, __kind = 1, __spins = 0, __elision = 0, __list = {__prev = 0x0, __next = 0x0}}, __size = '\000' <repeats 16 times>, "\001", '\000' <repeats 22 times>, __align = 0}, + file = 0x0, line = 0, initialized = true}}, aio_handlers = {lh_first = 0x60d000000860}, deleted_aio_handlers = {lh_first = 0x0}, notify_me = 2, list_lock = {count = 4}, bh_list = {slh_first = 0x0}, + bh_slice_list = {sqh_first = 0x0, sqh_last = 0x61300004d9b8}, notified = false, notifier = {rfd = 7, wfd = 7, initialized = true}, scheduled_coroutines = {slh_first = 0x0}, co_schedule_bh = 0x604000001110, + thread_pool = 0x0, tlg = {tl = {0x60b00000a1d0, 0x60b00000a280, 0x60b00000a330, 0x60b00000a3e0}}, external_disable_cnt = 0, poll_disable_cnt = 0, poll_ns = 0, poll_max_ns = 0, poll_grow = 0, + poll_shrink = 0, aio_max_batch = 0, poll_aio_handlers = {lh_first = 0x60d000000860}, poll_started = false, epollfd = 6, fdmon_ops = 0x55555a4ebbc0 <fdmon_poll_ops>} +(gdb) p ctx->bh_list +$8 = {slh_first = 0x0} +(gdb) p ctx->bh_slice_list +$9 = {sqh_first = 0x0, sqh_last = 0x61300004d9b8} +(gdb) p *ctx->bh_slice_list.sqh_last +$11 = (struct BHListSlice *) 0x0 +(gdb) p ctx->tlg +$12 = {tl = {0x60b00000a1d0, 0x60b00000a280, 0x60b00000a330, 0x60b00000a3e0}} +(gdb) p timerlist_deadline_ns(ctx->tlg.tl[0]) +$14 = -1 +(gdb) p timerlist_deadline_ns(ctx->tlg.tl[1]) +$15 = -1 +(gdb) p timerlist_deadline_ns(ctx->tlg.tl[2]) +$16 = -1 +(gdb) p timerlist_deadline_ns(ctx->tlg.tl[3]) +$17 = -1 +``` +What I see is: +- timerlistgroup_deadline_ns() -> -1 +- aio_compute_timeout() -> -1 +- aio_poll() -> -1 + +So scsi_device_purge_requests() waits indefinitively. +Additional information: +``` +../configure --enable-trace-backends=log --disable-docs --enable-debug --extra-cflags='-ggdb -fPIE' --disable-user --disable-tools --target-list=x86_64-softmmu --cc=clang --cxx=clang++ --enable-sanitizers --disable-vhost-user +qemu 6.1.0 + + Directories + Install prefix: /usr/local + BIOS directory: share/qemu + firmware path: /usr/local/share/qemu-firmware + binary directory: bin + library directory: lib + module directory: lib/qemu + libexec directory: libexec + include directory: include + config directory: /usr/local/etc + local state directory: /usr/local/var + Manual directory: share/man + Doc directory: /usr/local/share/doc + Build directory: /home/philmd/qemu/build + Source path: /home/philmd/qemu + GIT submodules: ui/keycodemapdb meson tests/fp/berkeley-testfloat-3 tests/fp/berkeley-softfloat-3 dtc capstone slirp + + Host binaries + git: git + make: make + python: /usr/bin/python3 (version: 3.9) + sphinx-build: NO + gdb: /usr/bin/gdb + genisoimage: /usr/bin/mkisofs + smbd: "/usr/sbin/smbd" + + Configurable features + Documentation: NO + system-mode emulation: YES + user-mode emulation: NO + block layer: YES + Install blobs: YES + module support: NO + fuzzing support: NO + Audio drivers: oss + Trace backends: log + QOM debugging: YES + vhost-kernel support: YES + vhost-net support: YES + vhost-crypto support: NO + vhost-scsi support: YES + vhost-vsock support: YES + vhost-user support: NO + vhost-user-blk server support: NO + vhost-user-fs support: NO + vhost-vdpa support: YES + build guest agent: YES + + Compilation + host CPU: x86_64 + host endianness: little + C compiler: clang + Host C compiler: clang + C++ compiler: clang++ + CFLAGS: -O0 -g + CXXFLAGS: -O0 -g + QEMU_CFLAGS: -fsanitize=undefined -fsanitize=address -m64 -mcx16 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fno-common -fwrapv -ggdb -fPIE -Wold-style-definition -Wtype-limits -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body -Wnested-externs -Wendif-labels -Wexpansion-to-defined -Wno-initializer-overrides -Wno-missing-include-dirs -Wno-shift-negative-value -Wno-string-plus-int -Wno-typedef-redefinition -Wno-tautological-type-limit-compare -Wno-psabi -fstack-protector-strong + QEMU_LDFLAGS: -Wl,--warn-common -fsanitize=undefined -fsanitize=address -Wl,-z,relro -Wl,-z,now -m64 -ggdb -fPIE -fstack-protector-strong + profiler: NO + link-time optimization (LTO): NO + PIE: YES + static build: NO + malloc trim support: YES + membarrier: NO + debug stack usage: NO + mutex debugging: YES + memory allocator: system + avx2 optimization: NO + avx512f optimization: NO + gprof enabled: NO + gcov: NO + thread sanitizer: NO + CFI support: NO + strip binaries: NO + sparse: NO + mingw32 support: NO + x86_64 tests: x86_64-linux-gnu-gcc via debian-amd64-cross + + Targets and accelerators + KVM support: YES + HAX support: NO + HVF support: NO + WHPX support: NO + NVMM support: NO + Xen support: NO + TCG support: YES + TCG backend: native (x86_64) + TCG plugins: YES + TCG debug enabled: YES + target list: x86_64-softmmu + default devices: YES + out of process emulation: YES + + Block layer support + coroutine backend: ucontext + coroutine pool: YES + Block whitelist (rw): + Block whitelist (ro): + Use block whitelist in tools: NO + VirtFS support: NO + build virtiofs daemon: NO + Live block migration: YES + replication support: YES + bochs support: YES + cloop support: YES + dmg support: YES + qcow v1 support: YES + vdi support: YES + vvfat support: YES + qed support: YES + parallels support: YES + FUSE exports: NO + + Crypto + TLS priority: "NORMAL" + GNUTLS support: YES + GNUTLS crypto: YES + libgcrypt: NO + nettle: NO + crypto afalg: NO + rng-none: NO + Linux keyring: YES + + Dependencies + SDL support: NO + SDL image support: NO + GTK support: NO + pixman: YES + VTE support: NO + slirp support: internal + libtasn1: YES + PAM: NO + iconv support: YES + curses support: YES + virgl support: NO + curl support: NO + Multipath support: NO + VNC support: YES + VNC SASL support: YES + VNC JPEG support: YES + VNC PNG support: NO + brlapi support: NO + vde support: NO + netmap support: NO + Linux AIO support: NO + Linux io_uring support: NO + ATTR/XATTR support: YES + RDMA support: NO + PVRDMA support: NO + fdt support: internal + libcap-ng support: NO + bpf support: NO + spice support: NO + rbd support: NO + xfsctl support: NO + smartcard support: NO + U2F support: NO + libusb: NO + usb net redir: NO + OpenGL support: NO + GBM: NO + libiscsi support: NO + libnfs support: NO + seccomp support: NO + GlusterFS support: NO + TPM support: YES + libssh support: NO + lzo support: NO + snappy support: NO + bzip2 support: NO + lzfse support: NO + zstd support: NO + NUMA host support: NO + libxml2: NO + capstone: internal + libpmem support: NO + libdaxctl support: NO + libudev: NO + FUSE lseek: NO + ``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/648 b/gitlab/issues_text/target_missing/host_missing/accel_missing/648 new file mode 100644 index 000000000..61b5d36bd --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/648 @@ -0,0 +1 @@ +util/vfio-helpers: misaligned address for struct vfio_iova_range, which requires 8 byte alignment diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/649 b/gitlab/issues_text/target_missing/host_missing/accel_missing/649 new file mode 100644 index 000000000..029f6fbf1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/649 @@ -0,0 +1,8 @@ +qemu-6.1.0 causes I/O errors in VMs leading to data corruption +Description of problem: +after upgrading around 10 gentoo hosts from qemu-6.0.0-r53 to 6.1.0 most VMs (around 85 of 100, our VMs with PostgreSQL have 100% chance of hitting this) after some time (few minutes) will have I/O Errors, causing crashes and data corruption. +The VMs are stored on ZFS volumes. +Downgrading to qemu-6.0.0-r53 instantly fixes this. +Happens on completely different hardware (quad core Xeons to 32C Epyc2). + +Reproducible: Always diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/65 b/gitlab/issues_text/target_missing/host_missing/accel_missing/65 new file mode 100644 index 000000000..677430a8c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/65 @@ -0,0 +1 @@ +Assigning NVMe disk to a domain causes VFIO_MAP_DMA errors diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/650 b/gitlab/issues_text/target_missing/host_missing/accel_missing/650 new file mode 100644 index 000000000..96282cb94 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/650 @@ -0,0 +1,24 @@ +Monitor device_add triggers deadlock when calling drain_call_rcu on QEMU >= 6.0.0 +Description of problem: +It hangs +Steps to reproduce: +1. Run the QEMU: + ``` + ./qemu-system-mips64 -nographic + ``` +2. Enter into the QEMU monitor: press ctrl-a c +3. Execute command `device_add` without arguments: +``` +(qemu) device_add +``` +4. It hangs so bad that only `kill -9` helps +Additional information: +I didn't test versions between 4.2.0 and 6.0.0, but I can confirm that 6.0.0, 6.1.0 and the latest master pull have this bug, while version 4.2.0 doesn't have it. + +I've tracked the problem and found this. + +1. Command `device_add` calls function `drain_call_rcu`. `drain_call_rcu` waits indefinitely for drain_complete_event. +2. Function `cpu_exec` in accel/tcg/cpu-exec.c calls `rcu_read_lock` but does not call `rcu_read_unlock()`. `cpu_exec` just spins in its inner loop. +3. Function `call_rcu_thread` hanged in calling the `synchronize_rcu` which calls `wait_for_readers`. + +If I execute `stop` command in QEMU monitor before calling `device_add` command, no hang happen. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/654 b/gitlab/issues_text/target_missing/host_missing/accel_missing/654 new file mode 100644 index 000000000..818a62a51 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/654 @@ -0,0 +1,23 @@ +Strace Log Output Mangled +Description of problem: +The syscall log entries from the strace logging capability can be interrupted by other log messages before the full syscall line is +complete. +This makes parsing the strace syscall lines from the log output difficult. +Steps to reproduce: +1. Run the supplied command with a simple dynamically linked binary, or a binary that performs mmaps +2. Notice that the strace 'mmap' syscall log entries in the trace file are interrupted by the page log output +Additional information: +I have attached an example log from a dynamically linked 'hello world' binary, which demonstrates the bug in the mmap syscall strace entries. [output.trace](/uploads/88c83273582d00241fbf95af735dcc61/output.trace) + + +I believe this bug caused by a couple of things: +Firstly, in the linux-user/syscall.c file: the strace syscall entry is not output atomically, but instead split across two calls: +The first half is at `print_syscall`: https://gitlab.com/qemu-project/qemu/-/blob/master/linux-user/syscall.c#L13153 +And the return value (and new line) is printed in `print_syscall_ret`: https://gitlab.com/qemu-project/qemu/-/blob/master/linux-user/syscall.c#L13160 + +In the case of the mmap syscall, the function `log_page_dump` is called between these two functions resulting in the mangled log output: +https://gitlab.com/qemu-project/qemu/-/blob/master/linux-user/mmap.c#L633 +There may be other syscalls that behave similarly, but this was noticed due to the mmap behavior. + + +Internally to the `print_syscall` and `print_syscall_ret` functions, `qemu_log` is called multiple times to compose the full log entry, and it seems that it is inside `qemu_log` that the logfile lock is obtained and dropped - so theoretically another thread can output to the log during the printing of a single syscall entry between these `qemu_log` calls. I do not know if this actually happens in practice besides the mmap scenario described above. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/657 b/gitlab/issues_text/target_missing/host_missing/accel_missing/657 new file mode 100644 index 000000000..91a2240b0 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/657 @@ -0,0 +1 @@ +qemu no valid state has been set by load or init-program Mac OS X Tiger diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/659 b/gitlab/issues_text/target_missing/host_missing/accel_missing/659 new file mode 100644 index 000000000..8e5c77ee6 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/659 @@ -0,0 +1,41 @@ +Qemu6 regression causing disabled usb controller upon usbredir device_add +Description of problem: +I'm encountering a nagging issue with usbredir and a windows guest, but although I did pinpoint the commit that caused the issue, I have a hard time understanding it. + +The issue occurs when two usbredir devices are added to a guest windows vm (any vm installed from the official iso will reproduce the issue). When the second device is added, the UHCI usb controller is disabled by windows with an error code 43 (can be seen with in the usb adapters section of the device manager). +Steps to reproduce: +1. take/create an intalled windows image and run it with `qemu-system-x86_64 -M pc -cpu host,hv_time,hv_synic,hv_stimer,hv_vpindex -enable-kvm -m 4096 -device piix3-usb-uhci,id=uhci -qmp tcp:127.0.0.1:4444,server=on,wait=off,ipv4 -drive <disk-parameters> --snapshot` (snapshot not necessary but useful for multiples testing to avoid side effects as the usb status sometime lingers after a shutdown, not sure why) +2. Open windows device manager +3. add devices via [this qmp python script](/uploads/5f2f9240dce1b55ceb148b32f3d6073c/qmp-usb-adds.py) +Additional information: +The commit causing the issue (everything works well when reverting it) is 7bed89958bfbf40df9ca681cefbdca63abdde39d : device_core: use `drain_call_rcu` in in `qmp_device_add`. + +I narrowed the problem to the unlock of the iothread: the minimum `drain_call_rcu` code that still reproduce the issue is: + +```c +void drain_call_rcu(void) +{ + bool locked = qemu_mutex_iothread_locked(); + if (locked) { + qemu_mutex_unlock_iothread(); + } + usleep(50000); // time spent draining the rcu on a few slow cases. + + if (locked) { + qemu_mutex_lock_iothread(); + } +} +``` + +About the qemu command line: The hv parameters are needed to trigger the issue I do not know why. + +I tried to find what was able to take advantage of the free iothread lock, but the only thing I got so far is that the iothread lock is not taken during the first drain (from the first device add), but is taken many times during the second drain by physmem's IOs (from kvm-accel, but at this point, I'm a bit lost). + +I'm looking for pointers as to what could trigger the issue in order to narrow it down, as, so far, I do not understand exactly what causes the regression. +I am unsure of how this would even transcribe in a linux vm so i didn't try to reproduce the issue with one. + +With the attached [reproduction python script](/uploads/5f2f9240dce1b55ceb148b32f3d6073c/qmp-usb-adds.py), the issue triggers nearly 100% of the time. + +Note 1: Related to #650 as the commit causing the regression is the same, although the cause is probably different since the rcu is not implied. + +Note 2: This is a restranscription of [this ml report](https://lore.kernel.org/qemu-devel/20210930134844.f4kh72vpeknr2vmk@gmail.com/) as i wasn't aware, the correct way to report issue was through gitlab now. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/66 b/gitlab/issues_text/target_missing/host_missing/accel_missing/66 new file mode 100644 index 000000000..961e6dbd3 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/66 @@ -0,0 +1 @@ +-hda FAT:. limited to 504MBytes diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/660 b/gitlab/issues_text/target_missing/host_missing/accel_missing/660 new file mode 100644 index 000000000..5dc3b4e98 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/660 @@ -0,0 +1,9 @@ +User emulation does not use host GPU +Description of problem: + +Steps to reproduce: +1. Make a Arch Linux chroot (though any Linux system should work) on Linux +2. run `glxinfo | grep OpenGL +3. It's using llvmpipe, not whatever GPU/driver that the hosts use +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/662 b/gitlab/issues_text/target_missing/host_missing/accel_missing/662 new file mode 100644 index 000000000..440a78e75 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/662 @@ -0,0 +1,11 @@ +Assertion `!s->do_cmd' failed in am53c974 emulator +Description of problem: + +Steps to reproduce: +``` +1../configure --target-list=i386-softmmu --disable-werror --enable-sanitizers +2.make -j12 +3.qemu-system-i386 -m 512 -drive file=./hyfuzz.img,index=0,media=disk,format=raw -device am53c974,id=scsi -device scsi-hd,drive=SysDisk -drive id=SysDisk,if=none,file=./disk.img +``` +Additional information: +# diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/663 b/gitlab/issues_text/target_missing/host_missing/accel_missing/663 new file mode 100644 index 000000000..335cc259d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/663 @@ -0,0 +1,11 @@ +Assertion `r->req.aiocb == NULL' in am53c974 emulator +Description of problem: + +Steps to reproduce: +``` +1../configure --target-list=i386-softmmu --disable-werror --enable-sanitizers +2.make -j12 +3.qemu-system-i386 -m 512 -drive file=./hyfuzz.img,index=0,media=disk,format=raw -device am53c974,id=scsi -device scsi-hd,drive=SysDisk -drive id=SysDisk,if=none,file=./disk.img +``` +Additional information: +# diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/665 b/gitlab/issues_text/target_missing/host_missing/accel_missing/665 new file mode 100644 index 000000000..ef5f8d563 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/665 @@ -0,0 +1,52 @@ +Cannot boot from emulated NVMe with seabios +Description of problem: +SeaBIOS doesn't boot from NVMe disk. + +This is regression compared to version 5.1.0. The exact same SeaBIOS binary that works with QEMU 5.1.0, doesn't detect NVMe with QEMU 6.0.0, nor QEMU 6.1.0. Booting from NVMe via OVMF works on all those versions. +Steps to reproduce: +1. Start the above command +2. Press ESC to open boot menu in SeaBIOS +3. Observe lack of NVMe entry +Additional information: +I've bisected it to this commit: +``` +7f0f1acedf159d00684d495d7a14d52220c1d16b is the first bad commit +commit 7f0f1acedf159d00684d495d7a14d52220c1d16b +Author: Klaus Jensen <k.jensen@samsung.com> +Date: Wed Jun 26 08:51:06 2019 +0200 + + hw/block/nvme: support multiple namespaces + + This adds support for multiple namespaces by introducing a new 'nvme-ns' + device model. The nvme device creates a bus named from the device name + ('id'). The nvme-ns devices then connect to this and registers + themselves with the nvme device. + + This changes how an nvme device is created. Example with two namespaces: + + -drive file=nvme0n1.img,if=none,id=disk1 + -drive file=nvme0n2.img,if=none,id=disk2 + -device nvme,serial=deadbeef,id=nvme0 + -device nvme-ns,drive=disk1,bus=nvme0,nsid=1 + -device nvme-ns,drive=disk2,bus=nvme0,nsid=2 + + The drive property is kept on the nvme device to keep the change + backward compatible, but the property is now optional. Specifying a + drive for the nvme device will always create the namespace with nsid 1. + + Signed-off-by: Klaus Jensen <k.jensen@samsung.com> + Reviewed-by: Keith Busch <kbusch@kernel.org> + Reviewed-by: Minwoo Im <minwoo.im.dev@gmail.com> + + hw/block/meson.build | 2 +- + hw/block/nvme-ns.c | 167 ++++++++++++++++++++++++++++++++++ + hw/block/nvme-ns.h | 74 +++++++++++++++ + hw/block/nvme.c | 245 ++++++++++++++++++++++++++++++++------------------ + hw/block/nvme.h | 46 +++++----- + hw/block/trace-events | 6 +- + 6 files changed, 426 insertions(+), 114 deletions(-) + create mode 100644 hw/block/nvme-ns.c + create mode 100644 hw/block/nvme-ns.h +``` + +Using `-device nvme-ns` as shown above doesn't help either. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/666 b/gitlab/issues_text/target_missing/host_missing/accel_missing/666 new file mode 100644 index 000000000..5a03d6d17 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/666 @@ -0,0 +1,7 @@ +ivshmem-plain cannot be used on non-Linux hosts +Additional information: +I would like to propose this patch as-is on the mailing list (the trivial one?) as soon as I figure patch submission out fully: + +https://github.com/fredldotme/qemu/commit/e929b8db8078aede6df7b02d8c0b71d1e2d6afcb + +It's just `#ifdef`ing out doorbell support on non-Linux builds which seems to be enough for basic functionality. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/667 b/gitlab/issues_text/target_missing/host_missing/accel_missing/667 new file mode 100644 index 000000000..00ec3cd07 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/667 @@ -0,0 +1 @@ +Wacom EMR pen pressure support diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/668 b/gitlab/issues_text/target_missing/host_missing/accel_missing/668 new file mode 100644 index 000000000..61055b2ae --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/668 @@ -0,0 +1,21 @@ +No trace verbs +Description of problem: +I am trying to follow [this tutorial](https://github.com/ryanprescott/realtek-verb-tools/wiki/How-to-sniff-verbs-from-a-Windows-sound-driver) to get my sound working again, but I am stuck at the step where I have to analyse the verbs, because I get none. They say I should get things similar to this: +``` +CORB[1] = 0xf0000 (caddr:0x0 nid:0x0 control:0xf00 param:0x0) +CORB[2] = 0xf0002 (caddr:0x0 nid:0x0 control:0xf00 param:0x2) +CORB[3] = 0xf0004 (caddr:0x0 nid:0x0 control:0xf00 param:0x4) +RIRBWP advance to 3, last WP 0 +CORB caddr:0x0 nid:0x0 control:0xf00 param:0x0 response:0x10ec0245 (ex 0x0) +CORB caddr:0x0 nid:0x0 control:0xf00 param:0x2 response:0x100001 (ex 0x0) +CORB caddr:0x0 nid:0x0 control:0xf00 param:0x4 response:0x10001 (ex 0x0) +``` +in the `qemu-output.txt` file, but instead I am getting [this](https://github.com/ryanprescott/realtek-verb-tools/files/7331986/qemu-output.txt) in the console. + +How do I get verbs in the first format ? + +I tried compiling qemu from source with this: `./configure --enable-trace-backends=log --target-list=x86_64-softmmu`, but that produced the same result as using the `qemu-system-x86_64` command that I got by installing qemu with my package manager. +Steps to reproduce: +https://github.com/ryanprescott/realtek-verb-tools/wiki/How-to-sniff-verbs-from-a-Windows-sound-driver +Additional information: +I don't know, as me if I am missing something diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/669 b/gitlab/issues_text/target_missing/host_missing/accel_missing/669 new file mode 100644 index 000000000..8d0d824c3 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/669 @@ -0,0 +1,23 @@ +QEMU Segmentation fault - UnRaid 9.3.2 when passing nvidia k620 GPU inserted into Lenovo x3550 M5 server +Description of problem: +When I pass the following GPU to any Virtual Machine: +IOMMU group 33:[10de:13bb] 81:00.0 VGA compatible controller: NVIDIA Corporation GM107GL [Quadro K620] (rev a2) +I receive this error as soon as i try to boot the VM (any OS). + +Oct 13 03:06:12 MyUnraid-1U kernel: vfio-pci 0000:81:00.0: enabling device (0140 -> 0141) +Oct 13 03:06:12 MyUnraid-1U kernel: vfio-pci 0000:81:00.0: vfio_ecap_init: hiding ecap 0x1e@0x258 +Oct 13 03:06:12 MyUnraid-1U kernel: vfio-pci 0000:81:00.0: vfio_ecap_init: hiding ecap 0x19@0x900 +**Oct 13 03:06:12 MyUnraid-1U kernel: qemu-system-x86[6080]: segfault at a8 ip 00005618620c812a sp 00007ffc610531b0 error 4 in qemu-system-x86_64[561861fbb000+51d000] +Oct 13 03:06:12 MyUnraid-1U kernel: Code: ef ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 55 53 48 89 fb 48 83 ec 08 48 8b 6f 58 e8 4e de ff ff 48 89 df e8 16 e9 ff ff <48> 8b 85 a8 00 00 00 48 85 c0 74 52 8b 93 a0 00 00 00 eb 0e 66 90** +Oct 13 03:06:13 MyUnraid-1U avahi-daemon[3536]: Interface vnet0.IPv6 no longer relevant for mDNS. + +This is one example of W10 VM: +In attach my VM template + +[VM_example.txt](/uploads/428ca5a10ef3338d5d408583fc552b25/VM_example.txt) +Steps to reproduce: +1. +2. +3. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/670 b/gitlab/issues_text/target_missing/host_missing/accel_missing/670 new file mode 100644 index 000000000..a86f99479 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/670 @@ -0,0 +1,10 @@ +qemu x86_64 for microsoft windows hangs when booting a Debian Live 11.1 iso file +Description of problem: +qemu displays the boot screen from the live linux iso and starts the boot, but no more display is performed even when waiting for approximately 30 minutes +Steps to reproduce: +1. Get hold of a Live Linux iso from Debian 11.1 +2. Set up the Microsoft Windows version of qemu from https://qemu.weilnetz.de/ +3. Attempt to boot the Live Linux iso +Additional information: +I also tested older versions of QEMU from the Weilnetz web site. 6.0.0 and 5.2.0 are bad; 5.1.0 and older are good. I then tested the same command line ( no acceleration ) under Linux Tumbleweed 20211014 with qemu 6.1.0 and the iso booted successfully. I have not tried with isos from distributions other than Debian 11.1 . So there is a bug with the Microsoft Windows-specific code in qemu. +If you need the specific Live Linux that I was using, let me know and I will get it to you somehow. It is several GB in size so I cannot upload it anywhere conveniently. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/671 b/gitlab/issues_text/target_missing/host_missing/accel_missing/671 new file mode 100644 index 000000000..866788782 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/671 @@ -0,0 +1,18 @@ +gtk with virtio and opengl black screen +Description of problem: +Running the provided command line, the screen is black, and the vm still starts. +I can confirm that turning off gl (with gl=off), everything works. + +These are line outputs printed out by QEMU: +``` +gl_version 45 - core profile enabled +vrend_renderer_fill_caps: Entering with stale GL error: 1280 +GLSL feature level 430 +virtio_input_hid_handle_status: unknown type 20 +virtio_input_hid_handle_status: unknown type 20 +``` +Steps to reproduce: +1. Execute the provided command +2. Wait +Additional information: +The bug was opened on launchpad by Ethan (ethannij). However, after the migration to github issues, the bug expired and no one reported here. This is the full launchpad discussion: https://bugs.launchpad.net/qemu/+bug/1898490 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/675 b/gitlab/issues_text/target_missing/host_missing/accel_missing/675 new file mode 100644 index 000000000..d8634c49f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/675 @@ -0,0 +1,10 @@ +Attaching WinDbg to a Windows guest on Windows host causes hang +Description of problem: +Attempting to attach WinDbg to a Windows guest on a Windows host causes qemu to lockup while using real serial ports. This has been an issue for some time (years if I'm remembering correctly) I just haven't reported it. +Steps to reproduce: +1. Enable debug in Windows guest +2. Create a DB9 between 2 COM ports +3. Power guest +4. Attach WinDbg to 2nd COM port not in use by the guest +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/677 b/gitlab/issues_text/target_missing/host_missing/accel_missing/677 new file mode 100644 index 000000000..c1e336f1a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/677 @@ -0,0 +1 @@ +Qemu crashes when trying to load kernel inside of WSL2 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/678 b/gitlab/issues_text/target_missing/host_missing/accel_missing/678 new file mode 100644 index 000000000..bb79e4edc --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/678 @@ -0,0 +1,47 @@ +eject (monitor command) not work for blockdev cdrom +Description of problem: +cdrom1 device work fine, all files reads, but when i whant to eject CD-ROM disk from device by telnet monitor, it not work. +Steps to reproduce: +1. Connect to monitor with +``` +telnet 127.0.0.1 9100 +(QEMU 5.2.0 monitor - type 'help' for more information) +``` + +2. Show block devices +``` +info block +cdrom1-format: /mnt/soft/QEMU/Windows VirtIO Drivers/virtio-win-0.1.208-1.iso (raw, read-only) + Attached to: cdrom1 + Removable device: not locked, tray closed + Cache mode: writeback +``` + +3. Send eject commands +``` +eject cdrom1 +Error: Device 'cdrom1' not found +eject cdrom1-format +Error: Device 'cdrom1-format' not found +eject cdrom1-storage +Error: Device 'cdrom1-storage' not found +``` +Additional information: +When i run qemu with next lines (replace -blockdev to -drive): +``` +-device ide-cd,bus=ide.1,drive=cdrom1,id=idecd1,bootindex=2 +-drive if=none,id=cdrom1,media=cdrom,readonly=on,file="/mnt/soft/QEMU/Windows VirtIO Drivers/virtio-win-0.1.208-1.iso" +``` + +eject cdrom1 command work fine + +``` +info block +cdrom1 (#block133): /mnt/soft/QEMU/Windows VirtIO Drivers/virtio-win-0.1.208-1.iso (raw, read-only) + Attached to: idecd1 + Removable device: not locked, tray closed + Cache mode: writeback +eject cdrom1 +``` + +Also i found a similar bug description on this link https://bugs.launchpad.net/qemu/+bug/1799766 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/68 b/gitlab/issues_text/target_missing/host_missing/accel_missing/68 new file mode 100644 index 000000000..d5c64b0f9 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/68 @@ -0,0 +1 @@ +Solaris can't be powered off with ACPI shutdown/poweroff diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/680 b/gitlab/issues_text/target_missing/host_missing/accel_missing/680 new file mode 100644 index 000000000..f0f069e7c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/680 @@ -0,0 +1 @@ +multi-threaded qemu instance and pci bar diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/681 b/gitlab/issues_text/target_missing/host_missing/accel_missing/681 new file mode 100644 index 000000000..62094a42b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/681 @@ -0,0 +1,25 @@ +Error saving memory to disk +Description of problem: +When trying to save the state of the machine using virt-manager (3.2.0) it fails with this error: + +Error saving domain: operation failed: domain save job: unexpectedly failed +```bash +Traceback (most recent call last): + File "/usr/share/virt-manager/virtManager/asyncjob.py", line 65, in cb_wrapper + callback(asyncjob, *args, **kwargs) + File "/usr/share/virt-manager/virtManager/vmmenu.py", line 182, in cb + vm.save(meter=asyncjob.get_meter()) + File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 57, in newfn + ret = fn(self, *args, **kwargs) + File "/usr/share/virt-manager/virtManager/object/domain.py", line 1377, in save + self._backend.managedSave(0) + File "/usr/lib/python3.9/site-packages/libvirt.py", line 1780, in managedSave + raise libvirtError('virDomainManagedSave() failed') +libvirt.libvirtError: operation failed: domain save job: unexpectedly failed +``` +Steps to reproduce: +1. setup a virtual machine +2. setup a linux distro +3. try to save the memory to disk +Additional information: +Will be provided when needed diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/684 b/gitlab/issues_text/target_missing/host_missing/accel_missing/684 new file mode 100644 index 000000000..105e6970c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/684 @@ -0,0 +1 @@ +xHCI Port Status Change Event at port powered diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/686 b/gitlab/issues_text/target_missing/host_missing/accel_missing/686 new file mode 100644 index 000000000..ff0e56146 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/686 @@ -0,0 +1,39 @@ +Qemu crashes if it is paused and migrated twice +Description of problem: +If the vm is in PAUSED state (in Openstack parlance) (I think libvirt calls that paused as well but uses the command `virsh suspend`), and live-migrated twice, the second time the Qemu process terminates. + +This is perfectly repeatable. + +If the VM is unpaused and re-paused after the first migration, then the problem does not occur on the next migration. +Steps to reproduce: +See also the referenced bug report to openstack, above. +1. `$ openstack stack create ....` +2. `$ openstack server pause <UUID>` +(wait until done) +3. `$ openstack server migrate --live-migration <UUID>` +(wait until done) +4. `$ openstack server migrate --live-migration <UUID>` + +The VM is now in ERROR state because it has disappeared: `libvirt.libvirtError: Domain not found: no domain with matching uuid '<UUID>'` +Additional information: +The last few lines from the instance-00000ba2.log seem pertinent (this is from the receiving Qemu instance): +``` +2021-10-22 15:32:53.829+0000: initiating migration +qemu-system-x86_64: /build/qemu-lb4V37/qemu-4.2/block.c:5523: bdrv_inactivate_recurse: Assertion `!(bs->open_flags & BDRV_O_INACTIVE)' failed. +2021-10-22 15:32:59.122+0000: shutting down, reason=crashed +``` +This is logged by libvirt (also on the receiving side): +``` +Oct 22 15:29:04 ybk140931 ovs-vsctl[20174]: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap3a71aa63-6a +Oct 22 15:31:31 ybk140931 ovs-vsctl[21412]: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap3a71aa63-6a -- add-port br-int tap3a71aa63-6a -- set Interface tap3a71aa63-6a "external-ids:attached-mac=\"fa:16:3e:da:03:56\"" -- set Interface tap3a71aa63-6a "external-ids:iface-id=\"3a71aa63-6a39-41d8-9602-04b84834db9e\"" -- set Interface tap3a71aa63-6a "external-ids:vm-id=\"de2b27d2-345c-45fc-8f37-2fa0ed1a1151\"" -- set Interface tap3a71aa63-6a external-ids:iface-status=active +Oct 22 15:32:58 ybk140931 libvirtd[3237]: Unable to read from monitor: Connection reset by peer +Oct 22 15:32:59 ybk140931 ovs-vsctl[22001]: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap3a71aa63-6a +Oct 22 15:32:59 ybk140931 libvirtd[3237]: operation failed: domain is not running +Oct 22 15:32:59 ybk140931 libvirtd[3237]: internal error: qemu unexpectedly closed the monitor: 2021-10-22T15:32:58.845667Z qemu-system-x86_64: Failed to load virtio_pci/modern_queue_state:used + 2021-10-22T15:32:58.845687Z qemu-system-x86_64: Failed to load virtio_pci/modern_state:vqs + 2021-10-22T15:32:58.845690Z qemu-system-x86_64: Failed to load virtio/extra_state:extra_state + 2021-10-22T15:32:58.845692Z qemu-system-x86_64: Failed to load virtio-rng:virtio + 2021-10-22T15:32:58.845695Z qemu-system-x86_64: error while loading state for instance 0x0 of device '0000:00:06.0/virtio-rng' + 2021-10-22T15:32:58.847860Z qemu-system-x86_64: load of migration failed: Input/output error +Oct 22 15:32:59 ybk140931 libvirtd[3237]: operation failed: domain 'instance-00000ba2' is not running +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/687 b/gitlab/issues_text/target_missing/host_missing/accel_missing/687 new file mode 100644 index 000000000..e615c8202 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/687 @@ -0,0 +1 @@ +what is the DMAR? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/688 b/gitlab/issues_text/target_missing/host_missing/accel_missing/688 new file mode 100644 index 000000000..0203ec61a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/688 @@ -0,0 +1,47 @@ +Shrinking an image with qemu-img does not reduce image file size +Description of problem: +I have a macOS 10.9 VM using a qcow2 image that was 151GB. The image was originally converted from a VMware image with: +``` +qemu-img convert macOS-10.9.vmdk -O qcow2 -o preallocation=falloc macOS-10.9.qcow2 +``` +This resulted in `macOS-10.9.qcow2` being 151GB big: +``` +$ du -h macOS-10.9.qcow2 +151G macOS-10.9.qcow2 +``` +After reducing the filesystem size from within macOS to 25GB with DiskUtil, I shut down the VM and resized the image to 30GB with: +``` +qemu-img resize -f qcow2 --shrink macOS-10.9.qcow2 30G +``` +This succeeded. However, the file still consumes 151GB of space: +``` +$ du -h macOS-10.9.qcow2 +151G macOS-10.9.qcow2 +``` +Even though `qemu-img info` shows: +``` +$ qemu-img info macOS-10.9.qcow2 +image: macOS-10.9.qcow2 +file format: qcow2 +virtual size: 30 GiB (32212254720 bytes) +disk size: 30 GiB +cluster_size: 65536 +Format specific information: + compat: 1.1 + compression type: zlib + lazy refcounts: false + refcount bits: 16 + corrupt: false + extended l2: false +``` +The size inside the VM is also reported as being 30GB. + +The whole point of resizing that image was to free up disk space on the host. But this doesn't seem to be happening. + +My filesystem is ext4. +Steps to reproduce: +1. Create a vmdk image with `qemu-img create -f vmdk test.vmdk 5G` +2. Convert the vmdk image to qcow2 with `qemu-img convert test.vmdk -O qcow2 -o preallocation=falloc test.qcow2` +3. Shrink the new image with `qemu-img resize -f qcow2 --shrink test.qcow2 3G` + +The resulting `test.qcow2` file should be 3GB, but it's not. It's 5GB. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/69 b/gitlab/issues_text/target_missing/host_missing/accel_missing/69 new file mode 100644 index 000000000..1663daf84 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/69 @@ -0,0 +1 @@ +ALSA underruns occurr when using QEMU diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/691 b/gitlab/issues_text/target_missing/host_missing/accel_missing/691 new file mode 100644 index 000000000..329a20f2d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/691 @@ -0,0 +1,6 @@ +`-nic model=help` on qemu-system-riscv64 doesn't output supported models +Description of problem: +`-nic model=help` doesn't list out the supported NIC models and instead launches QEMU with warnings. + +Steps to reproduce: +1. run `qemu-system-riscv64 -machine virt -nic model=help` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/692 b/gitlab/issues_text/target_missing/host_missing/accel_missing/692 new file mode 100644 index 000000000..08a21c798 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/692 @@ -0,0 +1 @@ +remove_fd_in_watch does not call g_source_unref diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/696 b/gitlab/issues_text/target_missing/host_missing/accel_missing/696 new file mode 100644 index 000000000..588b5d114 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/696 @@ -0,0 +1,9 @@ +EDID does not reflected to window size when added through the commandline +Description of problem: +It seems some odd behavior on the guest screen. it shows me the size of default window (640x480) instead of override the value to 1740x720. This size (640x480) is first initialized on ui/console.c => QemuConsole *graphic_console_init and I did noticed that in hw/display/virtio-gpu-base.c=> static int virtio_gpu_ui_info the override value is not taking place instead it just took the value from ui/console.c (640x480). May I know, how do I achieved the right override edid value from the current provided interface. + +##Additional information +I did noticed that the edid flag is always true (running this command) It is contradiction from the doc. +Steps to reproduce: +1. Run the qemu with the command mentioned +2. Check the resolution of guest OS diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/697 b/gitlab/issues_text/target_missing/host_missing/accel_missing/697 new file mode 100644 index 000000000..1bc175fad --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/697 @@ -0,0 +1 @@ +linux-user create default CPU type before parsing the ELF header for specific CPU type diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/698 b/gitlab/issues_text/target_missing/host_missing/accel_missing/698 new file mode 100644 index 000000000..a11a7840f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/698 @@ -0,0 +1,358 @@ +linux-user: emulated process reading /proc/self/mem doesn't see guest view of memory map +Description of problem: +QEMU user-mode emulation of a 32-bit guest on a 64-bit host doesn't seem to emulate `/proc/self/mem` (or `/proc/$pid/mem`) correctly. Based on the contents of `/proc/self/maps`, there seems to be some sort of address translation happening that `/proc/self/mem` doesn't honor. + +The following source file: + +```c +#include <fcntl.h> +#include <inttypes.h> +#include <stdbool.h> +#include <stdio.h> +#include <stdlib.h> +#include <string.h> +#include <unistd.h> +#include <sys/wait.h> + +static const char string[] = "Hello, world!\n"; + +static bool copy_to_stdout(const char *path) +{ + bool success = false; + + int fd = open(path, O_RDONLY); + if (fd < 0) { + perror("open"); + return false; + } + + char buf[16 * 1024]; + while (true) { + ssize_t bytes_read = read(fd, buf, sizeof(buf)); + if (bytes_read == 0) { + success = true; + goto out; + } else if (bytes_read < 0) { + perror("read"); + goto out; + } + ssize_t bytes_written = 0; + while (bytes_written < bytes_read) { + ssize_t ret = write(STDOUT_FILENO, buf + bytes_written, + bytes_read - bytes_written); + if (ret < 0) { + perror("write"); + goto out; + } + bytes_written += ret; + } + } + +out: + close(fd); + return success; +} + +static bool dump_maps(void) +{ + printf("Maps read by self:\n"); + fflush(stdout); + if (!copy_to_stdout("/proc/self/maps")) + return false; + + printf("\nMaps read by child process:\n"); + fflush(stdout); + pid_t pid = fork(); + if (pid < 0) { + perror("fork"); + return false; + } + if (pid == 0) { + char parent_maps[32]; + sprintf(parent_maps, "/proc/%u/maps", (unsigned int)getppid()); + if (copy_to_stdout(parent_maps)) + _exit(EXIT_SUCCESS); + else + _exit(EXIT_FAILURE); + } + int wstatus; + if (waitpid(pid, &wstatus, 0) < 0 || + !WIFEXITED(wstatus) || WEXITSTATUS(wstatus) != EXIT_SUCCESS) + return false; + + printf("\n"); + return true; +} + +int main(void) +{ + if (!dump_maps()) + return EXIT_FAILURE; + + int fd = open("/proc/self/mem", O_RDONLY); + if (fd < 0) { + perror("open: /proc/self/mem"); + return EXIT_FAILURE; + } + + char buf[sizeof(string)]; + printf("Reading %zu bytes from %p (%" PRIuPTR ") to %p of PID %u\n", + sizeof(buf), string, (uintptr_t)string, buf, + (unsigned int)getpid()); + fflush(stdout); + + if (pread(fd, buf, sizeof(buf), (uintptr_t)string) < 0) { + perror("pread: /proc/self/mem"); + return EXIT_FAILURE; + } + + if (memcmp(buf, string, sizeof(buf)) != 0) { + fprintf(stderr, "buffer doesn't match\n"); + return EXIT_FAILURE; + } + + return EXIT_SUCCESS; +} +``` + +when compiled for 32-bit ARM produces the following output: + +``` +Maps read by self: +10000-7c000 r-xp 00000000 00:19 8275924 /home/osandov/repro +7c000-8b000 ---p 00000000 00:00 0 +8b000-8c000 r--p 0006b000 00:19 8275924 /home/osandov/repro +8c000-8d000 rw-p 0006c000 00:19 8275924 /home/osandov/repro +8d000-b0000 rw-p 00000000 00:00 0 +3ffff000-40000000 r-xp 00000000 00:00 0 +40000000-40001000 ---p 00000000 00:00 0 +40001000-40801000 rw-p 00000000 00:00 0 [stack] + +Maps read by child process: +00010000-00020000 ---p 00000000 00:00 0 +00020000-0008c000 r--p 00000000 00:19 8275924 /home/osandov/repro +0008c000-0009b000 ---p 00000000 00:00 0 +0009b000-0009c000 r--p 0006b000 00:19 8275924 /home/osandov/repro +0009c000-0009d000 rw-p 0006c000 00:19 8275924 /home/osandov/repro +0009d000-000c0000 rw-p 00000000 00:00 0 +000c0000-4000f000 ---p 00000000 00:00 0 +4000f000-40010000 r--p 00000000 00:00 0 +40010000-40011000 ---p 00000000 00:00 0 +40011000-40811000 rw-p 00000000 00:00 0 +40811000-100000000 ---p 00000000 00:00 0 +100000000-100001000 r--p 00000000 00:00 0 +5636dd7a2000-5636dd8a4000 r--p 00000000 00:19 8270028 /home/osandov/repos/qemu/build/qemu-arm +5636dd8a4000-5636ddb13000 r-xp 00102000 00:19 8270028 /home/osandov/repos/qemu/build/qemu-arm +5636ddb13000-5636ddf69000 r--p 00371000 00:19 8270028 /home/osandov/repos/qemu/build/qemu-arm +5636ddf6a000-5636ddfe7000 r--p 007c7000 00:19 8270028 /home/osandov/repos/qemu/build/qemu-arm +5636ddfe7000-5636ddff3000 rw-p 00844000 00:19 8270028 /home/osandov/repos/qemu/build/qemu-arm +5636ddff3000-5636de010000 rw-p 00000000 00:00 0 +5636df67b000-5636df80c000 rw-p 00000000 00:00 0 [heap] +7f3008000000-7f300ffff000 rwxp 00000000 00:00 0 +7f300ffff000-7f3010000000 ---p 00000000 00:00 0 +7f3010000000-7f3010021000 rw-p 00000000 00:00 0 +7f3010021000-7f3014000000 ---p 00000000 00:00 0 +7f3017119000-7f301719a000 rw-p 00000000 00:00 0 +7f301719a000-7f301719b000 ---p 00000000 00:00 0 +7f301719b000-7f30179a1000 rw-p 00000000 00:00 0 +7f30179a1000-7f30179a3000 r--p 00000000 00:19 3660771 /usr/lib/libffi.so.8.1.0 +7f30179a3000-7f30179a9000 r-xp 00002000 00:19 3660771 /usr/lib/libffi.so.8.1.0 +7f30179a9000-7f30179ab000 r--p 00008000 00:19 3660771 /usr/lib/libffi.so.8.1.0 +7f30179ab000-7f30179ac000 r--p 00009000 00:19 3660771 /usr/lib/libffi.so.8.1.0 +7f30179ac000-7f30179ad000 rw-p 0000a000 00:19 3660771 /usr/lib/libffi.so.8.1.0 +7f30179ad000-7f30179be000 r--p 00000000 00:19 1476709 /usr/lib/libgmp.so.10.4.1 +7f30179be000-7f3017a32000 r-xp 00011000 00:19 1476709 /usr/lib/libgmp.so.10.4.1 +7f3017a32000-7f3017a49000 r--p 00085000 00:19 1476709 /usr/lib/libgmp.so.10.4.1 +7f3017a49000-7f3017a4a000 ---p 0009c000 00:19 1476709 /usr/lib/libgmp.so.10.4.1 +7f3017a4a000-7f3017a4c000 r--p 0009c000 00:19 1476709 /usr/lib/libgmp.so.10.4.1 +7f3017a4c000-7f3017a4d000 rw-p 0009e000 00:19 1476709 /usr/lib/libgmp.so.10.4.1 +7f3017a4d000-7f3017a56000 r--p 00000000 00:19 2871144 /usr/lib/libhogweed.so.6.4 +7f3017a56000-7f3017a69000 r-xp 00009000 00:19 2871144 /usr/lib/libhogweed.so.6.4 +7f3017a69000-7f3017a93000 r--p 0001c000 00:19 2871144 /usr/lib/libhogweed.so.6.4 +7f3017a93000-7f3017a95000 r--p 00045000 00:19 2871144 /usr/lib/libhogweed.so.6.4 +7f3017a95000-7f3017a96000 rw-p 00047000 00:19 2871144 /usr/lib/libhogweed.so.6.4 +7f3017a96000-7f3017a98000 rw-p 00000000 00:00 0 +7f3017a98000-7f3017aa4000 r--p 00000000 00:19 2871147 /usr/lib/libnettle.so.8.4 +7f3017aa4000-7f3017ac5000 r-xp 0000c000 00:19 2871147 /usr/lib/libnettle.so.8.4 +7f3017ac5000-7f3017adb000 r--p 0002d000 00:19 2871147 /usr/lib/libnettle.so.8.4 +7f3017adb000-7f3017adc000 ---p 00043000 00:19 2871147 /usr/lib/libnettle.so.8.4 +7f3017adc000-7f3017ade000 r--p 00043000 00:19 2871147 /usr/lib/libnettle.so.8.4 +7f3017ade000-7f3017adf000 rw-p 00045000 00:19 2871147 /usr/lib/libnettle.so.8.4 +7f3017adf000-7f3017ae2000 r--p 00000000 00:19 2550729 /usr/lib/libtasn1.so.6.6.1 +7f3017ae2000-7f3017aee000 r-xp 00003000 00:19 2550729 /usr/lib/libtasn1.so.6.6.1 +7f3017aee000-7f3017af2000 r--p 0000f000 00:19 2550729 /usr/lib/libtasn1.so.6.6.1 +7f3017af2000-7f3017af3000 ---p 00013000 00:19 2550729 /usr/lib/libtasn1.so.6.6.1 +7f3017af3000-7f3017af4000 r--p 00013000 00:19 2550729 /usr/lib/libtasn1.so.6.6.1 +7f3017af4000-7f3017af5000 rw-p 00014000 00:19 2550729 /usr/lib/libtasn1.so.6.6.1 +7f3017af5000-7f3017b06000 r--p 00000000 00:19 937656 /usr/lib/libunistring.so.2.1.0 +7f3017b06000-7f3017b3b000 r-xp 00011000 00:19 937656 /usr/lib/libunistring.so.2.1.0 +7f3017b3b000-7f3017c72000 r--p 00046000 00:19 937656 /usr/lib/libunistring.so.2.1.0 +7f3017c72000-7f3017c76000 r--p 0017c000 00:19 937656 /usr/lib/libunistring.so.2.1.0 +7f3017c76000-7f3017c77000 rw-p 00180000 00:19 937656 /usr/lib/libunistring.so.2.1.0 +7f3017c77000-7f3017c79000 r--p 00000000 00:19 3212638 /usr/lib/libidn2.so.0.3.7 +7f3017c79000-7f3017c7d000 r-xp 00002000 00:19 3212638 /usr/lib/libidn2.so.0.3.7 +7f3017c7d000-7f3017c97000 r--p 00006000 00:19 3212638 /usr/lib/libidn2.so.0.3.7 +7f3017c97000-7f3017c98000 r--p 0001f000 00:19 3212638 /usr/lib/libidn2.so.0.3.7 +7f3017c98000-7f3017c99000 rw-p 00020000 00:19 3212638 /usr/lib/libidn2.so.0.3.7 +7f3017c99000-7f3017cc2000 r--p 00000000 00:19 3663986 /usr/lib/libp11-kit.so.0.3.0 +7f3017cc2000-7f3017d60000 r-xp 00029000 00:19 3663986 /usr/lib/libp11-kit.so.0.3.0 +7f3017d60000-7f3017dba000 r--p 000c7000 00:19 3663986 /usr/lib/libp11-kit.so.0.3.0 +7f3017dba000-7f3017dc4000 r--p 00120000 00:19 3663986 /usr/lib/libp11-kit.so.0.3.0 +7f3017dc4000-7f3017dce000 rw-p 0012a000 00:19 3663986 /usr/lib/libp11-kit.so.0.3.0 +7f3017dce000-7f3017dd0000 r--p 00000000 00:19 2549813 /usr/lib/libdl-2.33.so +7f3017dd0000-7f3017dd2000 r-xp 00002000 00:19 2549813 /usr/lib/libdl-2.33.so +7f3017dd2000-7f3017dd3000 r--p 00004000 00:19 2549813 /usr/lib/libdl-2.33.so +7f3017dd3000-7f3017dd4000 r--p 00004000 00:19 2549813 /usr/lib/libdl-2.33.so +7f3017dd4000-7f3017dd5000 rw-p 00005000 00:19 2549813 /usr/lib/libdl-2.33.so +7f3017dd5000-7f3017dd7000 rw-p 00000000 00:00 0 +7f3017dd7000-7f3017dd9000 r--p 00000000 00:19 3020974 /usr/lib/libpcre.so.1.2.13 +7f3017dd9000-7f3017e2f000 r-xp 00002000 00:19 3020974 /usr/lib/libpcre.so.1.2.13 +7f3017e2f000-7f3017e4c000 r--p 00058000 00:19 3020974 /usr/lib/libpcre.so.1.2.13 +7f3017e4c000-7f3017e4d000 r--p 00074000 00:19 3020974 /usr/lib/libpcre.so.1.2.13 +7f3017e4d000-7f3017e4e000 rw-p 00075000 00:19 3020974 /usr/lib/libpcre.so.1.2.13 +7f3017e4e000-7f3017e74000 r--p 00000000 00:19 2549806 /usr/lib/libc-2.33.so +7f3017e74000-7f3017fbf000 r-xp 00026000 00:19 2549806 /usr/lib/libc-2.33.so +7f3017fbf000-7f301800b000 r--p 00171000 00:19 2549806 /usr/lib/libc-2.33.so +7f301800b000-7f301800e000 r--p 001bc000 00:19 2549806 /usr/lib/libc-2.33.so +7f301800e000-7f3018011000 rw-p 001bf000 00:19 2549806 /usr/lib/libc-2.33.so +7f3018011000-7f301801a000 rw-p 00000000 00:00 0 +7f301801a000-7f3018021000 r--p 00000000 00:19 2549847 /usr/lib/libpthread-2.33.so +7f3018021000-7f3018030000 r-xp 00007000 00:19 2549847 /usr/lib/libpthread-2.33.so +7f3018030000-7f3018034000 r--p 00016000 00:19 2549847 /usr/lib/libpthread-2.33.so +7f3018034000-7f3018035000 ---p 0001a000 00:19 2549847 /usr/lib/libpthread-2.33.so +7f3018035000-7f3018036000 r--p 0001a000 00:19 2549847 /usr/lib/libpthread-2.33.so +7f3018036000-7f3018037000 rw-p 0001b000 00:19 2549847 /usr/lib/libpthread-2.33.so +7f3018037000-7f301803b000 rw-p 00000000 00:00 0 +7f301803b000-7f301803e000 r--p 00000000 00:19 2550528 /usr/lib/libgcc_s.so.1 +7f301803e000-7f3018050000 r-xp 00003000 00:19 2550528 /usr/lib/libgcc_s.so.1 +7f3018050000-7f3018053000 r--p 00015000 00:19 2550528 /usr/lib/libgcc_s.so.1 +7f3018053000-7f3018054000 ---p 00018000 00:19 2550528 /usr/lib/libgcc_s.so.1 +7f3018054000-7f3018055000 r--p 00018000 00:19 2550528 /usr/lib/libgcc_s.so.1 +7f3018055000-7f3018056000 rw-p 00019000 00:19 2550528 /usr/lib/libgcc_s.so.1 +7f3018056000-7f3018065000 r--p 00000000 00:19 2549819 /usr/lib/libm-2.33.so +7f3018065000-7f30180ff000 r-xp 0000f000 00:19 2549819 /usr/lib/libm-2.33.so +7f30180ff000-7f3018197000 r--p 000a9000 00:19 2549819 /usr/lib/libm-2.33.so +7f3018197000-7f3018198000 ---p 00141000 00:19 2549819 /usr/lib/libm-2.33.so +7f3018198000-7f3018199000 r--p 00141000 00:19 2549819 /usr/lib/libm-2.33.so +7f3018199000-7f301819a000 rw-p 00142000 00:19 2549819 /usr/lib/libm-2.33.so +7f301819a000-7f3018233000 r--p 00000000 00:19 2550558 /usr/lib/libstdc++.so.6.0.29 +7f3018233000-7f3018333000 r-xp 00099000 00:19 2550558 /usr/lib/libstdc++.so.6.0.29 +7f3018333000-7f301839f000 r--p 00199000 00:19 2550558 /usr/lib/libstdc++.so.6.0.29 +7f301839f000-7f30183ac000 r--p 00204000 00:19 2550558 /usr/lib/libstdc++.so.6.0.29 +7f30183ac000-7f30183ad000 rw-p 00211000 00:19 2550558 /usr/lib/libstdc++.so.6.0.29 +7f30183ad000-7f30183b2000 rw-p 00000000 00:00 0 +7f30183b2000-7f30183e6000 r--p 00000000 00:19 2907924 /usr/lib/libgnutls.so.30.30.0 +7f30183e6000-7f3018508000 r-xp 00034000 00:19 2907924 /usr/lib/libgnutls.so.30.30.0 +7f3018508000-7f301859d000 r--p 00156000 00:19 2907924 /usr/lib/libgnutls.so.30.30.0 +7f301859d000-7f301859e000 ---p 001eb000 00:19 2907924 /usr/lib/libgnutls.so.30.30.0 +7f301859e000-7f30185af000 r--p 001eb000 00:19 2907924 /usr/lib/libgnutls.so.30.30.0 +7f30185af000-7f30185b1000 rw-p 001fc000 00:19 2907924 /usr/lib/libgnutls.so.30.30.0 +7f30185b1000-7f30185b3000 rw-p 00000000 00:00 0 +7f30185b3000-7f30185b5000 r--p 00000000 00:19 3662215 /usr/lib/libgmodule-2.0.so.0.7000.0 +7f30185b5000-7f30185b7000 r-xp 00002000 00:19 3662215 /usr/lib/libgmodule-2.0.so.0.7000.0 +7f30185b7000-7f30185b8000 r--p 00004000 00:19 3662215 /usr/lib/libgmodule-2.0.so.0.7000.0 +7f30185b8000-7f30185b9000 r--p 00004000 00:19 3662215 /usr/lib/libgmodule-2.0.so.0.7000.0 +7f30185b9000-7f30185ba000 rw-p 00005000 00:19 3662215 /usr/lib/libgmodule-2.0.so.0.7000.0 +7f30185ba000-7f30185d7000 r--p 00000000 00:19 3662212 /usr/lib/libglib-2.0.so.0.7000.0 +7f30185d7000-7f3018664000 r-xp 0001d000 00:19 3662212 /usr/lib/libglib-2.0.so.0.7000.0 +7f3018664000-7f30186ec000 r--p 000aa000 00:19 3662212 /usr/lib/libglib-2.0.so.0.7000.0 +7f30186ec000-7f30186ed000 ---p 00132000 00:19 3662212 /usr/lib/libglib-2.0.so.0.7000.0 +7f30186ed000-7f30186ee000 r--p 00132000 00:19 3662212 /usr/lib/libglib-2.0.so.0.7000.0 +7f30186ee000-7f30186ef000 rw-p 00133000 00:19 3662212 /usr/lib/libglib-2.0.so.0.7000.0 +7f30186ef000-7f30186f0000 rw-p 00000000 00:00 0 +7f30186f0000-7f30186f2000 r--p 00000000 00:19 3440204 /usr/lib/liburing.so.2.1.0 +7f30186f2000-7f30186f4000 r-xp 00002000 00:19 3440204 /usr/lib/liburing.so.2.1.0 +7f30186f4000-7f30186f5000 r--p 00004000 00:19 3440204 /usr/lib/liburing.so.2.1.0 +7f30186f5000-7f30186f6000 r--p 00004000 00:19 3440204 /usr/lib/liburing.so.2.1.0 +7f30186f6000-7f30186f7000 rw-p 00005000 00:19 3440204 /usr/lib/liburing.so.2.1.0 +7f30186f7000-7f30186fa000 r--p 00000000 00:19 2549855 /usr/lib/librt-2.33.so +7f30186fa000-7f30186fe000 r-xp 00003000 00:19 2549855 /usr/lib/librt-2.33.so +7f30186fe000-7f3018700000 r--p 00007000 00:19 2549855 /usr/lib/librt-2.33.so +7f3018700000-7f3018701000 r--p 00008000 00:19 2549855 /usr/lib/librt-2.33.so +7f3018701000-7f3018702000 rw-p 00009000 00:19 2549855 /usr/lib/librt-2.33.so +7f3018702000-7f3018705000 r--p 00000000 00:19 15838 /usr/lib/libz.so.1.2.11 +7f3018705000-7f3018713000 r-xp 00003000 00:19 15838 /usr/lib/libz.so.1.2.11 +7f3018713000-7f3018719000 r--p 00011000 00:19 15838 /usr/lib/libz.so.1.2.11 +7f3018719000-7f301871a000 ---p 00017000 00:19 15838 /usr/lib/libz.so.1.2.11 +7f301871a000-7f301871b000 r--p 00017000 00:19 15838 /usr/lib/libz.so.1.2.11 +7f301871b000-7f301871c000 rw-p 00018000 00:19 15838 /usr/lib/libz.so.1.2.11 +7f301871c000-7f301871e000 rw-p 00000000 00:00 0 +7f301871e000-7f301871f000 r--p 00000000 00:19 2549795 /usr/lib/ld-2.33.so +7f301871f000-7f3018743000 r-xp 00001000 00:19 2549795 /usr/lib/ld-2.33.so +7f3018743000-7f301874c000 r--p 00025000 00:19 2549795 /usr/lib/ld-2.33.so +7f301874c000-7f301874e000 r--p 0002d000 00:19 2549795 /usr/lib/ld-2.33.so +7f301874e000-7f3018750000 rw-p 0002f000 00:19 2549795 /usr/lib/ld-2.33.so +7ffc5c8f6000-7ffc5c917000 rw-p 00000000 00:00 0 [stack] +7ffc5c935000-7ffc5c939000 r--p 00000000 00:00 0 [vvar] +7ffc5c939000-7ffc5c93b000 r-xp 00000000 00:00 0 [vdso] +ffffffffff600000-ffffffffff601000 --xp 00000000 00:00 0 [vsyscall] + +Reading 15 bytes from 0x6377c (407420) to 0x40800638 of PID 278331 +buffer doesn't match +``` + +The program is trying to read from 0x6377c, which according to the emulated maps is in this mapping: + +``` +10000-7c000 r-xp 00000000 00:19 8275924 /home/osandov/repro +``` + +but on the host, it's mapped differently: + +``` +00020000-0008c000 r--p 00000000 00:19 8275924 /home/osandov/repro +``` + +When using `qemu-arm-static` (version `6.1.0 (Debian 1:6.1+dfsg-6)`) via `binfmt_misc`, I also saw a case where the address isn't mapped in the host at all: + +``` +Maps read by self: +10000-7c000 r-xp 00000000 00:19 8275924 /home/osandov/repro +7c000-8b000 ---p 00000000 00:00 0 +8b000-8c000 r--p 0006b000 00:19 8275924 /home/osandov/repro +8c000-8d000 rw-p 0006c000 00:19 8275924 /home/osandov/repro +8d000-b0000 rw-p 00000000 00:00 0 +40000000-40001000 ---p 00000000 00:00 0 +40001000-40801000 rw-p 00000000 00:00 0 [stack] + +Maps read by child process: +00400000-00401000 r--p 00000000 00:19 297 /usr/bin/qemu-arm-static +00401000-00769000 r-xp 00001000 00:19 297 /usr/bin/qemu-arm-static +00769000-00abe000 r--p 00369000 00:19 297 /usr/bin/qemu-arm-static +00abe000-00c58000 r--p 006bd000 00:19 297 /usr/bin/qemu-arm-static +00c58000-00cd3000 rw-p 00857000 00:19 297 /usr/bin/qemu-arm-static +00cd3000-00cf7000 rw-p 00000000 00:00 0 +0253c000-0268e000 rw-p 00000000 00:00 0 [heap] +42645000-42655000 ---p 00000000 00:00 0 +42655000-426c1000 r--p 00000000 00:19 8275924 /home/osandov/repro +426c1000-426d0000 ---p 00000000 00:00 0 +426d0000-426d1000 r--p 0006b000 00:19 8275924 /home/osandov/repro +426d1000-426d2000 rw-p 0006c000 00:19 8275924 /home/osandov/repro +426d2000-426f5000 rw-p 00000000 00:00 0 +426f5000-82645000 ---p 00000000 00:00 0 +82645000-82646000 ---p 00000000 00:00 0 +82646000-82e46000 rw-p 00000000 00:00 0 +82e46000-142635000 ---p 00000000 00:00 0 +142635000-142636000 r--p 00000000 00:00 0 +7f5584000000-7f558bfff000 rwxp 00000000 00:00 0 +7f558bfff000-7f558c000000 ---p 00000000 00:00 0 +7f558c000000-7f558c021000 rw-p 00000000 00:00 0 +7f558c021000-7f5590000000 ---p 00000000 00:00 0 +7f55929b5000-7f5592a36000 rw-p 00000000 00:00 0 +7f5592a36000-7f5592a37000 ---p 00000000 00:00 0 +7f5592a37000-7f5593237000 rw-p 00000000 00:00 0 +7ffc4971a000-7ffc4973b000 rw-p 00000000 00:00 0 [stack] +7ffc497fa000-7ffc497fe000 r--p 00000000 00:00 0 [vvar] +7ffc497fe000-7ffc49800000 r-xp 00000000 00:00 0 [vdso] +ffffffffff600000-ffffffffff601000 --xp 00000000 00:00 0 [vsyscall] + +Reading 15 bytes from 0x6377c (407420) to 0x40800648 of PID 278443 +pread: /proc/self/mem: Input/output error +``` +Steps to reproduce: +1. Download statically-linked ARM [reproducer](/uploads/5563ad67d01f0ec4a10f27d1967216c4/repro). +2. Run `qemu-arm ./repro`. +Additional information: +I encountered this when trying out a CI system that uses QEMU user-mode emulation for 32-bit ARM builds. My project is a debugger that uses `/proc/self/mem`, and a test case tripped over this. See https://github.com/osandov/drgn/pull/126. + +This also seems to happen with a i386 guest, but not with an aarch64 guest, so I'm assuming that it's a 32-bit guest issue. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/699 b/gitlab/issues_text/target_missing/host_missing/accel_missing/699 new file mode 100644 index 000000000..82a3d26e2 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/699 @@ -0,0 +1 @@ +SGX QEMU release diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/70 b/gitlab/issues_text/target_missing/host_missing/accel_missing/70 new file mode 100644 index 000000000..d8dd4e8ba --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/70 @@ -0,0 +1 @@ +hda sound capture broken with VNC diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/700 b/gitlab/issues_text/target_missing/host_missing/accel_missing/700 new file mode 100644 index 000000000..da0634da8 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/700 @@ -0,0 +1 @@ +GTK display refresh rate is throttled diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/701 b/gitlab/issues_text/target_missing/host_missing/accel_missing/701 new file mode 100644 index 000000000..6879aa169 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/701 @@ -0,0 +1 @@ +Setup a gitlab shared runner for linux-user testing diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/702 b/gitlab/issues_text/target_missing/host_missing/accel_missing/702 new file mode 100644 index 000000000..60f10fa7d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/702 @@ -0,0 +1 @@ +Setup a gitlab shared runner for bsd-user testing diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/703 b/gitlab/issues_text/target_missing/host_missing/accel_missing/703 new file mode 100644 index 000000000..71ab9026c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/703 @@ -0,0 +1,17 @@ +Resizable BAR (ReBAR) support on VFIO +Additional information: +Currently `vfio_add_ext_cap()` doesn't pass ReBAR support option to VFIO. + +There was a report that removing the line you see below makes it boot, but the system is not stable. +Needs investigation. + +[https://github.com/qemu/qemu/blob/2255564fd21059960966b47212def9069cb56077/hw/vfio/pci.c#L2089](https://github.com/qemu/qemu/blob/2255564fd21059960966b47212def9069cb56077/hw/vfio/pci.c#L2089) +``` switch (cap_id) { + case 0: /* kernel masked capability */ + case PCI_EXT_CAP_ID_SRIOV: /* Read-only VF BARs confuse OVMF */ + case PCI_EXT_CAP_ID_ARI: /* XXX Needs next function virtualization */ + case PCI_EXT_CAP_ID_REBAR: /* Can't expose read-only */ + trace_vfio_add_ext_cap_dropped(vdev->vbasedev.name, cap_id, next); +``` + +[Discussion link](https://forum.level1techs.com/t/smart-access-memory-vs-qemu-kvm/169447) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/704 b/gitlab/issues_text/target_missing/host_missing/accel_missing/704 new file mode 100644 index 000000000..c90992a0e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/704 @@ -0,0 +1 @@ +linux-user: misaligned address for type 'struct linux_dirent64' diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/707 b/gitlab/issues_text/target_missing/host_missing/accel_missing/707 new file mode 100644 index 000000000..dd3cb3f53 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/707 @@ -0,0 +1,62 @@ +The QEMU emulator incorrectly interprets the contents of the SLIC table. See attached image. +Description of problem: +The QEMU emulator incorrectly interprets the contents of the SLIC table. + +The SLIC table read on pure hardware and in a virtual machine in the fedora 34 and 35: + + +Steps to reproduce: +Steps to Reproduce: + +1. Install Fedora 34 + +2. Install virtualization group: + + dnf group install virtualization + +4. Place SLIC binary image(slic.bin) into the direcrory /var/lib/libvirt/images + +3. Create Virtual Machine with Virtual Machine Manager. + +4. Modify xml description of virtual machine: + `... + <os> + ... + <acpi> + <table type='slic'>/var/lib/libvirt/images/slic.bin</table> + </acpi> + </os> + ...` + +5. Install Microsoft Windows 7 64-bit into Virtual machine. + +6. Place sertificate into Windows 7. + +7. Run with admin rights: + + slmgr.vbs /ilc <sertificate> + slmgr.vbs /ipk <key> + +8. Windows 7 will be activated ! + +9. Save Virtual Machine Image and it's xml description anywere. + +10. Install Fedora 35 + +11. Install virtualization group. + +12. Place saved Virtual Machine Image and slic.bin into the directory /var/lib/libvirt/images/ + +13. Register virtual machine: + + virsh -c qemu:///system define <xml_file> + +15. Run virtual machine - Windows 7 will lose it activation. +Additional information: +Fedora 34 has: + kernel-5.14.15-200.fc34.x86_64, qemu-system-x86-5.2.0-8.fc34.x86_64 + +Fedora 35 has: + kernel-5.14.15-300.fc35.x86_64, qemu-system-x86-6.1.0-9.fc35.x86_64 + +Slick Binary Image: [slic.bin](/uploads/da94a96516c3dbe52803fb84738f434c/slic.bin) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/708 b/gitlab/issues_text/target_missing/host_missing/accel_missing/708 new file mode 100644 index 000000000..da665aec0 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/708 @@ -0,0 +1,10 @@ +some TPM related files are missing in sysfs when enable passthrough TPM +Description of problem: +When enable passthrough TPM, there are some files in sysfs are missing, like description, uid file. +under the host linux, we have those file in it: +root@intel-x86-64:/sys/class/tpm/tpm0/device/firmware_node# cat description +TPM 2.0 Device +root@intel-x86-64:/sys/class/tpm/tpm0/device/firmware_node# cat uid +1 +Steps to reproduce: +after boot into system, check sysfs, there is no description and uid file in /sys/class/tpm/tpm0/device/firmware_node diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/709 b/gitlab/issues_text/target_missing/host_missing/accel_missing/709 new file mode 100644 index 000000000..90badcf86 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/709 @@ -0,0 +1 @@ +make command fail diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/71 b/gitlab/issues_text/target_missing/host_missing/accel_missing/71 new file mode 100644 index 000000000..91510a0fa --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/71 @@ -0,0 +1 @@ +AC97 can allocate ~500MB of host RAM diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/711 b/gitlab/issues_text/target_missing/host_missing/accel_missing/711 new file mode 100644 index 000000000..4df5ca103 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/711 @@ -0,0 +1 @@ +ATI Rage video card emulation diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/712 b/gitlab/issues_text/target_missing/host_missing/accel_missing/712 new file mode 100644 index 000000000..a1a0fd436 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/712 @@ -0,0 +1,14 @@ +Build fails if build directory name includes a comma +Description of problem: +Builds fail if the build directory name contains a comma. +Steps to reproduce: +1. `mkdir build,demo && cd build,demo` +2. `../configure && make` + +The linker fails because it uses a wrong build path (comma and trailing part of directory name is missing): + +``` +ld: can't read -exported_symbols_list file: /Users/stefan/src/gitlab/qemu-project/qemu/build +clang: error: linker command failed with exit code 1 (use -v to see invocation) +ninja: build stopped: subcommand failed. +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/713 b/gitlab/issues_text/target_missing/host_missing/accel_missing/713 new file mode 100644 index 000000000..9ef53322e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/713 @@ -0,0 +1 @@ +Missing safe-syscall.inc.S for mips diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/716 b/gitlab/issues_text/target_missing/host_missing/accel_missing/716 new file mode 100644 index 000000000..8a26baf1f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/716 @@ -0,0 +1,3 @@ +using "-device scsi-cd" option on arm64 platform +Description of problem: +When using OpenStack to create a virtual machine instance, I need to configure the password of the root user through cloud-init. I use the ConfigDriver method, in which OpenStack will mount a virtual disk in iso9660 format to the virtual machine instance. The command line generated by OpenStack is shown above. You can see that this ConfigDrive virtual disk is mounted via "--device scsi-cd". But when I entered the virtual machine instance and used lsblk, blkid and searched in /dev/disk/by-label, I did not find the virtual disk that should be mounted. In addition, I don't have more debugging messages or error messages. I want to know if the "scsi-cd" is not fully adapted to arm64 platform. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/718 b/gitlab/issues_text/target_missing/host_missing/accel_missing/718 new file mode 100644 index 000000000..2a98037a5 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/718 @@ -0,0 +1,6 @@ +option to take screenshot with screendump as PNG +Additional information: +Libvirt already have preparation for PNG MIME type: https://github.com/libvirt/libvirt/blob/master/tools/virsh-domain.c#L5526 + + +Thanks diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/719 b/gitlab/issues_text/target_missing/host_missing/accel_missing/719 new file mode 100644 index 000000000..66c48c6ae --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/719 @@ -0,0 +1,19 @@ +live migration's performance with compression enabled is much worse than compression disabled +Description of problem: + +Steps to reproduce: +1. Run QEMU the Guests with 1Gpbs network on source host and destination host with QEMU command line +2. Run some memory work loads on Guest, for example, ./memtester 1G 1 +3. Set migration parameters in QEMU monitor. On source and destination, + execute: #migrate_set_capability compress on + Other compression parameters are all default. +4. Run migrate command, # migrate -d tcp:10.156.208.154:4000 +5. The results: + - without compression： total time: 197366 ms throughput: 937.81 mbps transferred Ram: 22593703 kbytes + - with compression: total time: 281711 ms throughput: 90.24 mbps transferred Ram: 3102898 kbytes + +When compression is enabled, the compression transferred ram is reduced a lot. But the throughput is down badly. +The total time of live migration with compression is longer than without compression. +I tried with 100G network bandwidth, it also has the same problem. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/72 b/gitlab/issues_text/target_missing/host_missing/accel_missing/72 new file mode 100644 index 000000000..8afb1d3d2 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/72 @@ -0,0 +1 @@ +mouse offset or invisible wall 2.11.0-3 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/721 b/gitlab/issues_text/target_missing/host_missing/accel_missing/721 new file mode 100644 index 000000000..b73473722 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/721 @@ -0,0 +1,30 @@ +Build failed at libqemu-aarch64-softmmu.fa.p/accel_tcg_cputlb.c.o +Steps to reproduce: +1. Download and build from source + +``` +wget https://download.qemu.org/qemu-6.1.0.tar.xz +tar xvJf qemu-6.1.0.tar.xz +cd qemu-6.1.0 +./configure +make +``` +Additional information: +``` +[2150/9644] Compiling C object libqemu-alpha-softmmu.fa.p/migration_dirtyrate.c.o +[2151/9644] Compiling C object libqemu-alpha-softmmu.fa.p/migration_ram.c.o +[2152/9644] Compiling C object libqemu-alpha-softmmu.fa.p/target_alpha_fpu_helper.c.o +[2153/9644] Compiling C object libqemu-aarch64-softmmu.fa.p/accel_tcg_translate-all.c.o +[2154/9644] Compiling C object libqemu-alpha-softmmu.fa.p/migration_target.c.o +[2155/9644] Compiling C object libqemu-aarch64-softmmu.fa.p/accel_tcg_cputlb.c.o +FAILED: libqemu-aarch64-softmmu.fa.p/accel_tcg_cputlb.c.o +gcc -Ilibqemu-aarch64-softmmu.fa.p -I. -I.. -Itarget/arm -I../target/arm -I../dtc/libfdt -I../capstone/include/capstone -Iqapi -Itrace -Iui -Iui/shader -I/usr/include/pixman-1 -I/usr/include/libdrm -I/usr/include/valgrind -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -fdiagnostics-color=auto -Wall -Winvalid-pch -std=gnu11 -O2 -g -isystem /home/intel/Sources/qemu-6.1.0/linux-headers -isystem linux-headers -iquote . -iquote /home/intel/Sources/qemu-6.1.0 -iquote /home/intel/Sources/qemu-6.1.0/include -iquote /home/intel/Sources/qemu-6.1.0/disas/libvixl -iquote /home/intel/Sources/qemu-6.1.0/tcg/i386 -pthread -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -m64 -mcx16 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fno-common -fwrapv -Wold-style-declaration -Wold-style-definition -Wtype-limits -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body -Wnested-externs -Wendif-labels -Wexpansion-to-defined -Wimplicit-fallthrough=2 -Wno-missing-include-dirs -Wno-shift-negative-value -Wno-psabi -fstack-protector-strong -g -O3 -feliminate-unused-debug-types -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -Wformat -Wformat-security -m64 -fasynchronous-unwind-tables -Wp,-D_REENTRANT -ftree-loop-distribute-patterns -Wl,-z -Wl,now -Wl,-z -Wl,relro -fno-semantic-interposition -ffat-lto-objects -fno-trapping-math -Wl,-sort-common -Wl,--enable-new-dtags -mtune=skylake -fPIE -isystem../linux-headers -isystemlinux-headers -DNEED_CPU_H '-DCONFIG_TARGET="aarch64-softmmu-config-target.h"' '-DCONFIG_DEVICES="aarch64-softmmu-config-devices.h"' -MD -MQ libqemu-aarch64-softmmu.fa.p/accel_tcg_cputlb.c.o -MF libqemu-aarch64-softmmu.fa.p/accel_tcg_cputlb.c.o.d -o libqemu-aarch64-softmmu.fa.p/accel_tcg_cputlb.c.o -c ../accel/tcg/cputlb.c +during GIMPLE pass: fab +In file included from /home/intel/Sources/qemu-6.1.0/include/qemu/osdep.h:37, + from ../accel/tcg/cputlb.c:20: +../accel/tcg/atomic_common.c.inc: In function ‘helper_atomic_fetch_andb’: +/home/intel/Sources/qemu-6.1.0/include/exec/helper-head.h:21:27: internal compiler error: in optimize_atomic_bit_test_and, at tree-ssa-ccp.c:3245 + 21 | #define HELPER(name) glue(helper_, name) + | ^~~~~~~ +/home/intel/Sources/qemu-6.1.0/include/qemu/compiler.h:35:21: note: in definition of macro ‘xglue’ + 35 | #define xglue(x, y) x diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/722 b/gitlab/issues_text/target_missing/host_missing/accel_missing/722 new file mode 100644 index 000000000..011ccd9c2 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/722 @@ -0,0 +1,12 @@ +Qemu slirp connectivity lost when host enters vpn(openvpn or wireguard) +Description of problem: +No connectivity after host enters a vpn, tested with valid openvpn +and wireguard. +Steps to reproduce: +1. Open the vpn. +2. Open a virtual machine using slirp +3. Ping 8.8.8.8(if you can...) +Additional information: +The bug is independent on the order of execution, if you start the vm +to see it works, and run the vpn script, the connectivity in the vm +will drop, and come back when the tunneled connection is over. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/723 b/gitlab/issues_text/target_missing/host_missing/accel_missing/723 new file mode 100644 index 000000000..1b939140f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/723 @@ -0,0 +1,31 @@ +multiple displays VGA + qxl forces Spice mouse-mode=server and breaks usb-tablet/seamless mode +Description of problem: +qxl causes a totally unexpected mouse conflict with the default VGA in OSX Catalina and newer guests using AppleVirtualGraphics.kext + +usb-tablet is unusable - only clicks are received +usb-mouse works but grabs focus +Steps to reproduce: +1. install and run OSX guest +2. connect to Spice port +3. can't move mouse if usb-tablet is used. usb-mouse pointer but is grabbed +4. removing qxl fixed the issue for me. Mouse is seamless/not grabbed now +5. added -spice agent-mouse=on just in case +Additional information: +qmp from broken shows mouse-mode server. Working guests show mouse-mode client + +``` +{ "execute": "query-spice" } +... "mouse-mode": "server"}} +``` +- spice works with multiple displays in OSX if both are VGA but I had the same focus problem, will need to recheck because Qemu 6.1 seems stuck on mouse-mode=server. + + +Working VGA +``` +/usr/bin/qemu-system-x86_64 -name macos-big-sur,process=macos-big-sur -pidfile macos-big-sur/macos-big-sur.pid -enable-kvm -machine q35,smm=off,vmport=off -device isa-applesmc,osk=ourhardworkbythesewordsguardedpleasedontsteal\(c\)AppleComputerInc -no-hpet -global kvm-pit.lost_tick_policy=discard -cpu host,kvm=on,vendor=GenuineIntel,+hypervisor,+invtsc,+kvm_pv_eoi,+kvm_pv_unhalt -smp cores=2,threads=1,sockets=1 -m 8G -device virtio-balloon -smbios type=2,manufacturer="Wimpys World",product=Quickemu,version=2.3.1,serial=jvzclfjbeyq.pbz,location=wimpysworld.com,asset=macos-big-sur -device VGA,vgamem_mb=128 -display none -device usb-ehci,id=input -device usb-kbd,bus=input.0 -device usb-tablet,bus=input.0 -rtc base=localtime,clock=host,driftfix=slew -spice disable-ticketing=on,agent-mouse=on,port=5930 -device virtio-serial-pci -chardev socket,id=agent0,path=macos-big-sur/macos-big-sur-agent.sock,server=on,wait=off -device virtserialport,chardev=agent0,name=org.qemu.guest_agent.0 -device virtio-rng-pci,rng=rng0 -object rng-random,id=rng0,filename=/dev/urandom -chardev socket,id=monitor0,path=macos-big-sur/macos-big-sur-monitor.sock,server=on,wait=off -mon chardev=monitor0,id=monitor,mode=control -monitor none -serial mon:stdio -audiodev spice,id=audio0 -device ich9-intel-hda -device hda-duplex,audiodev=audio0 -device virtio-net,netdev=nic -netdev user,hostname=macos-big-sur,hostfwd=tcp::22220-:22,id=nic -global driver=cfi.pflash01,property=secure,value=on -drive if=pflash,format=raw,unit=0,file=macos-big-sur/OVMF_CODE.fd,readonly=on -drive if=pflash,format=raw,unit=1,file=macos-big-sur/OVMF_VARS-1024x768.fd -device ahci,id=ahci -device ide-hd,bus=ahci.0,drive=BootLoader,bootindex=0 -drive id=BootLoader,if=none,format=qcow2,file=macos-big-sur/OpenCore.qcow2 -device virtio-blk-pci,drive=SystemDisk -drive id=SystemDisk,if=none,format=qcow2,file=macos-big-sur/disk.qcow2 -device qemu-xhci,id=spicepass -chardev spicevmc,id=usbredirchardev1,name=usbredir -device usb-redir,chardev=usbredirchardev1,id=usbredirdev1 -chardev spicevmc,id=usbredirchardev2,name=usbredir -device usb-redir,chardev=usbredirchardev2,id=usbredirdev2 -chardev spicevmc,id=usbredirchardev3,name=usbredir -device usb-redir,chardev=usbredirchardev3,id=usbredirdev3 -device usb-ccid -chardev spicevmc,id=ccid,name=smartcard -device ccid-card-passthru,chardev=ccid -device virtio-serial-pci -chardev spiceport,id=webdav0,name=org.spice-space.webdav.0 -device virtserialport,chardev=webdav0,name=org.spice-space.webdav.0 -fsdev local,id=fsdev0,path=/home/jmorrison/Public,security_model=mapped-xattr -device virtio-9p-pci,fsdev=fsdev0,mount_tag=Public-jmorrison +``` + +Broken usb-tablet qxl +``` +/usr/bin/qemu-system-x86_64 -name macos-big-sur,process=macos-big-sur -pidfile macos-big-sur/macos-big-sur.pid -enable-kvm -machine q35,smm=off,vmport=off -device isa-applesmc,osk=ourhardworkbythesewordsguardedpleasedontsteal\(c\)AppleComputerInc -no-hpet -global kvm-pit.lost_tick_policy=discard -cpu host,kvm=on,vendor=GenuineIntel,+hypervisor,+invtsc,+kvm_pv_eoi,+kvm_pv_unhalt -smp cores=2,threads=1,sockets=1 -m 8G -device virtio-balloon -smbios type=2,manufacturer="Wimpys World",product=Quickemu,version=2.3.1,serial=jvzclfjbeyq.pbz,location=wimpysworld.com,asset=macos-big-sur -device qxl -display none -device usb-ehci,id=input -device usb-kbd,bus=input.0 -device usb-tablet,bus=input.0 -rtc base=localtime,clock=host,driftfix=slew -spice disable-ticketing=on,port=5930 -device virtio-serial-pci -chardev socket,id=agent0,path=macos-big-sur/macos-big-sur-agent.sock,server=on,wait=off -device virtserialport,chardev=agent0,name=org.qemu.guest_agent.0 -device virtio-rng-pci,rng=rng0 -object rng-random,id=rng0,filename=/dev/urandom -chardev socket,id=monitor0,path=macos-big-sur/macos-big-sur-monitor.sock,server=on,wait=off -mon chardev=monitor0,id=monitor,mode=control -monitor none -serial mon:stdio -audiodev spice,id=audio0 -device ich9-intel-hda -device hda-duplex,audiodev=audio0 -device virtio-net,netdev=nic -netdev user,hostname=macos-big-sur,hostfwd=tcp::22220-:22,id=nic -global driver=cfi.pflash01,property=secure,value=on -drive if=pflash,format=raw,unit=0,file=macos-big-sur/OVMF_CODE.fd,readonly=on -drive if=pflash,format=raw,unit=1,file=macos-big-sur/OVMF_VARS-1024x768.fd -device ahci,id=ahci -device ide-hd,bus=ahci.0,drive=BootLoader,bootindex=0 -drive id=BootLoader,if=none,format=qcow2,file=macos-big-sur/OpenCore.qcow2 -device virtio-blk-pci,drive=SystemDisk -drive id=SystemDisk,if=none,format=qcow2,file=macos-big-sur/disk.qcow2 -device qemu-xhci,id=spicepass -chardev spicevmc,id=usbredirchardev1,name=usbredir -device usb-redir,chardev=usbredirchardev1,id=usbredirdev1 -chardev spicevmc,id=usbredirchardev2,name=usbredir -device usb-redir,chardev=usbredirchardev2,id=usbredirdev2 -chardev spicevmc,id=usbredirchardev3,name=usbredir -device usb-redir,chardev=usbredirchardev3,id=usbredirdev3 -device usb-ccid -chardev spicevmc,id=ccid,name=smartcard -device ccid-card-passthru,chardev=ccid -device virtio-serial-pci -chardev spiceport,id=webdav0,name=org.spice-space.webdav.0 -device virtserialport,chardev=webdav0,name=org.spice-space.webdav.0 -fsdev local,id=fsdev0,path=/home/jmorrison/Public,security_model=mapped-xattr -device virtio-9p-pci,fsdev=fsdev0,mount_tag=Public-jmorrison +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/724 b/gitlab/issues_text/target_missing/host_missing/accel_missing/724 new file mode 100644 index 000000000..c6bbe4d5f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/724 @@ -0,0 +1 @@ +esp: heap-buffer-overflow in esp_fifo_pop_buf diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/726 b/gitlab/issues_text/target_missing/host_missing/accel_missing/726 new file mode 100644 index 000000000..0740ba5a4 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/726 @@ -0,0 +1 @@ +Missing 6.2.0-rc0 tarball on https://download.qemu.org/ diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/727 b/gitlab/issues_text/target_missing/host_missing/accel_missing/727 new file mode 100644 index 000000000..2ed6bc8e5 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/727 @@ -0,0 +1,156 @@ +VHDX is corrupted on expansion +Description of problem: +Fresh VHDX corrupts with data loss upon copying data into it. +Steps to reproduce: +1. Create new dynamic vhdx file of about 93Gib (unexpanded, starting size is small ~205Mib, freshly created and NTFS formatted in windows.) +2. Connect drive using qemu-nbd to /dev/nbd0 +3. Ensure partition using gdisk +4. format partition with ntfs/ExFAT volume +5. mount volume +6. copy/rsync data of about 85Gib of data into the mounted volume +7. unmount volume +8. disconnect /dev/nbd0 +9. reconnect /dev/nbd0 +10. attempt mount, sometimes mount may fail if corrupted +11. If mount succeeds, verify data/all-files using some method like sha256sum. Some data is likely to fail + +Given the amount of data I am rsync-ing into the volume, there is very high chance of corruption. + +The corruption is not apparent until **disconnection and reconnection** of virtual-disk. Simply unmounting and remounting without disconnecting is unlikely to cause one to suspect corruption. + +If the expanded corrupted volume is again disconnected, reconnected, reformatted and data is again re-copied onto it, then the volume is less likely to experience a corruption, perhaps because new block allocation is not required. + +Errors vary and include: +- sometimes mount fails +- sometimes ls -l output is garbled +- sometimes one cannot cd into a directory +- several consecutive errors in shasum256 start midway through the file-list processing. Error is shown as if rsync failed and files do not exist. + ``` + sha256sum: ./201207/IMG_2406.JPG: No such file or directory + ./201207/IMG_2406.JPG: FAILED open or read + ``` +- Doing chdsk on windows may just create FOUND.000/FILE0000.CHK files. +Additional information: +See comment https://gitlab.com/qemu-project/qemu/-/issues/136#note_731044761 from where this all began. Some summary included here. + +``` +[root@sirius a16]# uname -a +Linux sirius 5.15.0-60.fc35.x86_64 #1 SMP Tue Nov 2 15:38:03 IST 2021 x86_64 x86_64 x86_64 GNU/Linux + +[root@sirius ~]# qemu-system-x86_64 --version +QEMU emulator version 6.1.0 (qemu-6.1.0-10.fc35) +Copyright (c) 2003-2021 Fabrice Bellard and the QEMU Project developers + +[root@sirius ~]# cat /etc/mtab | grep -E "a16|a17" | grep ntfs3 +/dev/sda16 /mnt/a16 ExFAT rw,relatime,fmask=0022,dmask=0022,iocharset=utf8,errors=remount-ro 0 0 +/dev/sda17 /mnt/a17 ntfs3 rw,relatime,uid=0,gid=0,iocharset=utf8 0 0 + +[root@sirius ~]# uname -a # self-built rpmbuild kernel from fedora rawhide kernel-src rpm +Linux sirius 5.15.0-60.fc35.x86_64 #1 SMP Tue Nov 2 15:38:03 IST 2021 x86_64 x86_64 x86_64 GNU/Linux +``` + +Test/Activity being done: About 85Gib of data is copied onto a size 93Gib VHDX on host-FS ntfs3 with guest-FS ntfs3. +``` +Prefer windows method: Inside windows-10, using powershell command New-VHD, one may a 93Gib VHDX + New-VHD -Path I:\gkpics01.vhdx -SizeBytes 99723771904 -Dynamic + Then attach disk and format volume inside to ntfs. +or Alternatively, Linux method (less preferred) + qemu-img create -f qcow2 /mnt/a16/gkpics01.qcow2 99723771904 + qemu-img create -f vhdx -o subformat=dynamic /mnt/a16/gkpics01.vhdx 99723771904 +: +sync ; sleep 1 ; qemu-nbd -c /dev/nbd0 /mnt/a16/gkpics01.vhdx +: +create appropriate partitions on /dev/nbd0 if not already partitioned +gdisk /dev/nbd0 +: +format volume with filesystem ntfs, or ext4 etc if not already formatted +mkfs -t ntfs -Q -L fs_gkpics01 /dev/nbd0p2 +: +mount partition +sync ; sleep 1 ; mount -t ntfs3 /dev/nbd0p2 /mnt/t1 +: +do copy/rsync etc +( fl="photos001" ; src="/mnt/c13" ; dst="/mnt/t1" ; cd "$src" ;rsync -avH "$fl" "$dst" ; sudo -u gana DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus DISPLAY=:0.0 -- notify-send "$src/$fl" "rsync $src/$fl" ) +: +sync ; sleep 1 ; umount /mnt/t1 +: +sync ; sleep 1 ; blockdev --flushbufs /dev/nbd0 ; sleep 2 ; qemu-nbd -d /dev/nbd0 ; sleep 1 ; sync +: +sync ; sleep 1 ; qemu-nbd -c /dev/nbd0 /mnt/a16/gkpics01.vhdx +: +sync ; sleep 1 ; mount -t ntfs3 /dev/nbd0p2 /mnt/t1 +: +do ls-l/verify/sha256sum-c etc +( fl="photos001" ; rtpt="/mnt/t1" ; cd "${rtpt}/${fl}" ; sdate=`date` ; echo "$sdate" ; sha256sum -c "$rtpt/$fl/find.CHECKSUM" --quiet ; echo "$sdate" ; date ; sudo -u gana DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus DISPLAY=:0.0 -- notify-send "$src/$fl" "checksum $src/$fl" ) +``` + +In the below list detailing under what circumstance corruption occurs + +- Format: kernel-version/ disk-attaching-sw/ hostFS/ VDISK/ guestFS with any parameters in parenthesis. +- Corruption does happen with kernel-5.15.0-60/qemu-6.1.0-10/ntfs3/VHDX/ntfs3 +- Corruption does happen with kernel-5.15.0-60/qemu-6.1.0-10/ntfs3/VHDX/ext4 +- Corruption does happen with kernel-5.15.0-60/guestfish-1.46.0(backend=direct)/ntfs3/VHDX/ntfs3 +- Corruption does happen with kernel-5.15.0-60/guestfish-1.46.0(backend=libvirt-7.6.0-3)/ntfs3/VHDX/ntfs3 +- Corruption does happen on host-FS **ExFAT too** with kernel-5.15.0-60/qemu-6.1.0-10/ExFAT/VHDX/ntfs3 +- Corruption does happen with kernel-5.15.0-60/qemu-6.0.0-10/ExFAT/VHDX/ntfs3 +- Corruption does happen with kernel-5.14.18-300/qemu-6.0.0-12/ExFAT/VHDX/ntfs3g-fuseblk +- Corruption does happen with kernel-5.14.18-300/qemu-6.0.0-12/ExFAT/VHDX(created by qemu-img)/ntfs3g-fuseblk + ``` Failed to mount '/dev/nbd0p2': Input/output error NTFS is either inconsistent, or there is a hardware fault,``` +- Corruption does **not** happen with kernel-5.14.18-300/qemu-6.0.0-12/ExFAT/qcow2/ext4 +- Corruption does **not** happen with kernel-5.14.18-300/qemu-6.0.0-12/ExFAT/qcow2/ntfs3g-fuseblk +- Corruption does happen with kernel-5.15.0-60/qemu-6.1.0-10/ExFAT/VHDX(cache=none,aio=threads)/ntfs3 +- Corruption does happen with kernel-5.15.0-60/qemu-6.1.0-10/ExFAT/VHDX(cache=none,aio=io_uring)/ntfs3 +- VHDX fixed disk grows in size. Filed as different bug: https://gitlab.com/qemu-project/qemu/-/issues/806 + - Corruption **does happen** with kernel-5.15.0-60/qemu-6.1.0-10/ExFAT/VHDX(fixed)/ntfs3 + A fixed vhdx disk should not grow in size. It is as if the blocks are added to a vhdx-journal instead of overwriting preallocated blocks. +- Corruption does happen with kernel-5.15.0-60/qemu-6.1.0-10/ext4/VHDX/ntfs3 +- Corruption does happen with kernel-5.15.2-200/**qemu-6.2.0-rc1**/ExFAT/VHDX/ntfs3 +- Corruption does **not** happen with kernel-5.15.2-200/qemu-6.2.0-rc1/ExFAT/**VMDK**(v4,monolithicSparse)/ntfs3 +- Corruption does not happen with kernel-5.15.2-200/qemu-6.2.0-rc1/ExFAT/VMDK(compat6,monolithicSparse)/ntfs3 +- Corruption does **not** happen with kernel-5.15.2-200/qemu-6.2.0-rc1/ExFAT/**VDI**/ntfs3 +- Corruption does **not** happen with kernel-5.15.2-200/qemu-6.2.0-rc1/ExFAT/**VPC**(dynamic)/ntfs3 +- Corruption does happen with kernel-5.15.2-200/**qemu-5.2.0-8**/ExFAT/VHDX/ntfs3 +- Corruption does happen with kernel-5.15.2-200/**qemu-4.2.1-1**/ExFAT/VHDX/ntfs3 +- Corruption does happen with vhdx-file is on 2Tb NTFS 1Tb partition of **external USB HDD** 2Tb, with kernel-5.15.2-200/qemu-6.2.0-rc1/ntfs3/VHDX/ntfs3 +- Corruption does happen when using src is on ntfs3 partition on external USB drive, which is **generated synthetic data (sgdata)** sgdata/kernel-5.15.2-200/qemu-6.2.0-rc1/ExFat/VHDX/ntfs3 +- Corruption does happen when starting with qemu-img created vhdx image with sgdata/kernel-5.15.2-200/qemu-6.2.0-rc1/ExFat/VHDX(created by qemu-img)/ext4 superblock mount fail +- Corruption does happen older fc34-kernel on Fedora-35, sgdata/kernel-5.13.19-200/qemu-6.2.0-rc2/ExFAT/VHDX/ntfs3g-fuseblk , different, fewer files 3 small files affected +- Corruption does happen with older fc32-kernel on Fedora-35, sgdata/kernel-5.11.22-100/qemu-6.2.0-rc2/ExFAT/VHDX/ntfs3g-fuseblk , fewer files, different, but same as above 3 small files affected, +- Corruption does happen with older fc32-kernel on Fedora-35, sgdata/kernel-5.11.22-100/qemu-6.2.0-rc2/ExFAT/VHDX/ext4 +- Corruption does happen with self-built 5.10 LTS kernel on Fedora-35, sgdata/kernel-5.10.90-200/qemu-6.2.0-1/ExFAT/VHDX/ext4 (sgdata accessed using ntfs-fuseblk) +- As the host kernel invoking qemu-nbd, these kernels showed less errors than if they were run inside a VM as a guest. If run as a guest VM, These kernels, 5.15.4 and above, may also have kernel bugs https://bugzilla.kernel.org/show_bug.cgi?id=215460 or https://bugzilla.kernel.org/show_bug.cgi?id=215563 resulting in additional compounded errors in the failure test results, even in raw-img and qcow2(fixed). + - Corruption does happen with sgdata/kernel-5.15.4-201/qemu-6.2.0-rc1/ExFAT/VHDX(created by qemu-img)/ext4 + - Corruption does happen with sgdata/kernel-5.15.4-201/**qemu-6.2.0-rc2**/ExFAT/VHDX(created by qemu-img)/ext4 + - Corruption does not happen with synthetic-data sgdata/kernel-5.15.4-201/qemu-6.2.0-rc2/ExFAT/VMDK(created by qemu-img)/ext4 + - Corruption does happen with sgdata/kernel-5.15.5-200/qemu-6.2.0-rc2/ExFAT/VHDX(created by qemu-img)/ext4 + - Corruption does not happen with sgdata/kernel-5.15.4-201/nbdkit-1.28.2-nbdplugin-qemu-6.2.0-0.rc2/ExFAT/vmdk/ntfs3 + - Corruption does not happen with sgdata/kernel-5.15.4-201/nbdkit-1.28.2-nbdplugin/ExFAT/vmdk-nbd-vddkplugin/ntfs3 + - Corruption does happen with sgdata/kernel-5.15.4-201/nbdkit-1.28.2-nbdplugin-qemu-6.2.0-0.rc2/ExFAT/VHDX/ntfs3 + - Corruption does happen with sgdata/kernel-5.15.6-200 to kernel-5.15.13-200 /qemu-6.2.0-0.rc2/ExFAT/VHDX/ntfs3 +- On Windows-10, these tests may possibly be different bug. Also causes system-wide DiskIO stuck in addition to corruption https://github.com/cloudbase/wnbd/issues/63 + - Corruption does happen with sgdata/**WIN10**-21H2-19044-1415/**WNBD**-0.2.2-4-g10c1fbe/qemu-6.2.0-rc4/ExFAT/VHDX/NTFS + - Corruption **does happen** with sgdata/**WIN10**-21H2-19044-1415/**WNBD**-0.2.2-4-g10c1fbe/qemu-6.2.0-rc4/ExFAT/**qcow2**/NTFS +- Possibly different bug, on Windows-10, corruption of virtual-disk from inside VM, no nbd . Maybe https://bugzilla.kernel.org/show_bug.cgi?id=215460 or https://bugzilla.kernel.org/show_bug.cgi?id=215563 + - Win10-21H2-19044-1415/WHPX/ExFAT/qemu-6.2.0-rc4/alpine-linux-3.15/kernel-5.15.4/VHDX/ntfs3 + - Win10-21H2-19044-1415/WHPX/ExFAT/qemu-6.2.0-rc4/alpine-linux-3.15/kernel-5.15.4/**qcow2**/ext4 +- Corruption does **not** happen with Fedora-35/kernel-5.17.0-0.rc3.89(SB)/qemu-6.2.0-2/Fedora-Rawhide-202208/kernel-5.17.0-0.rc3.89/ExFAT/**qcow2(dyn)**/ntfs3 data-src: VHDX(dyn)/ntfs3/sgdata +- Corruption does **not** happen with Fedora-35/kernel-5.17.0-0.rc3.89(SB)/qemu-6.2.0-2/Fedora-Rawhide-202208/kernel-5.17.0-0.rc3.89/ExFAT/qcow2(dyn)/ntfs3 data-src: VHDX(dyn)/**ntfs-fuseblk**/sgdata +- Corruption **does** happen with Fedora-35/kernel-5.17.0-0.rc3.89(SB)/qemu-6.2.0-2/Fedora-Rawhide-202208/kernel-5.17.0-0.rc3.89/ExFAT/**VHDX**/ntfs3 data-src: VHDX(dyn)/ntfs3/sgdata +- Corruption **does** happen with Fedora-35/kernel-5.17.0-0.rc3.89(SB)/qemu-6.2.0-2/Fedora-Rawhide-202208/kernel-5.17.0-0.rc3.89/ExFAT/VHDX/ext4 data-src: VHDX(dyn)/**ntfs-fuseblk**/sgdata +- Corruption **does** happen with Fedora-35/kernel-5.17.0-0.rc3.89(SB)/qemu-6.2.0-2/**Rocky-8.5-Workstation-20211114.iso**/**kernel-4.18.0-348.el8.0.2.x86_64**/ExFAT/VHDX/ext4 data-src: VHDX(dyn)/**ntfs-fuseblk**/sgdata + +ExFAT filesystem was considered because it does not have concept of sparse files eliminating that factor from troubleshooting. Furthermore, it may be incorrect to suspect NTFS3, ExFAT or NTFS3g-fuseblk only because they are new/recently mainstreamed filesystems, as there aren't any intense/complex filesystem operations. The filesystem is experiencing only though-put and files are simply copied into it without further operations. Furthermore, ext4 also experiences corruption if on VHDX. + +It just seems to me the VHDX support implementation has bugs, corrupts and hence is not reliable. + +The qemu test-suite needs test-cases added for testing for vhdx-stress and vhdx-throughput . + +More troubleshooting test results are summarized in https://gitlab.com/qemu-project/qemu/-/issues/727#note_745711084 + +Chief suspect files +- ~~kernel: nbd: [drivers/block/nbd.c](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/block/nbd.c)~~ can be made to happen via VM +- ~~kernel: ntfs3~~ no ntfs3 partition required +- ~~kernel 5.x series~~ bug exists in 4.18.0.348 +- ~~qemu: block~~ doesn't happen to other virtual-disk formats (raw,qcow2) +- qemu/VM : seems to happen only when using qemu-nbd or inside qemu-VM +- qemu: [block/vhdx.c](https://gitlab.com/qemu-project/qemu/-/blob/master/block/vhdx.c) , [block/vhdx_log.c](https://gitlab.com/qemu-project/qemu/-/blob/master/block/vhdx-log.c) , [block/vhdx-endian.c](https://gitlab.com/qemu-project/qemu/-/blob/master/block/vhdx-endian.c) , [block/vhdx.h](https://gitlab.com/qemu-project/qemu/-/blob/master/block/vhdx.h), diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/728 b/gitlab/issues_text/target_missing/host_missing/accel_missing/728 new file mode 100644 index 000000000..977620779 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/728 @@ -0,0 +1,16 @@ +Catch up to latest VHDX v2(=0x01) rev-7.0 specification +Additional information: +Below issues need to be addressed before or during the tackling of this issue. +- ~#727 VHDX is corrupted on expansion.~ +- #136 windows qemu-img create vpc/vhdx error due to sparse files +- #1605 On windows, 2nd kind vhdx-dyn bug, crash on Unexpected error in bdrv_check_qiov_request() in io.c +- #806 Fixed VHDX inflates beyond its fixed size when data is copied onto it and also corrupts +- +This VHDX support applies to qemu build on any architecture, not just the windows-build. + +It is very likely, that the native hypervisor on windows WHPX will be the main hypervisor displacing haxm/vbox etc. VHDX, if it works, seems to be the virtual-disk format that is ideal +- for Linux/windows dual-boot machines, +- for clusters with Linux/windows servers sharing images from a network-storage +- for WSL2/Hyper-V + +Following a similar line of thought, NTFS/ExFat may be ideal for sharing data/images between Linux and Windows. So the storing, modification and drive attachment of VHDX files on these filesystems need to be just as well-tested as native Linux filesystems. As their driver are internal-kernel-drivers and not fuse/dokan-drivers, on both operating-systems, they are also performant. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/731 b/gitlab/issues_text/target_missing/host_missing/accel_missing/731 new file mode 100644 index 000000000..32acc7bfd --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/731 @@ -0,0 +1,21 @@ +Display resolution fixed by 800x600 with latest VirtIO drivers and guest additions +Description of problem: +Display resolution can't be changed to anything else than 800x600. +Steps to reproduce: +1. Install qemu/kvm +2. Create virtual machine +3. Setup Windows 10 +4. Install VirtIO-Drivers +5. Install guest-agent +6. Install qxl-drivers + +Steps 5 and 6 enable use of QXL-Display, but do not lead to allow for higher display resolutions than before. +Additional information: + + + +Screen resolution is fixed by 800x600. +Driver is installed, but seems to have a problem (Attention sign. Warning, Error: digital signatur could not be checked -- at least there is no how to to make the existing signature work). +Latest available VirtIO-drivers where used as available from https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/stable-virtio/virtio-win.iso + +Older available drivers did not work too as expected. Same problem. Could not check older Windows 10 versions, because of lack of older install media. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/732 b/gitlab/issues_text/target_missing/host_missing/accel_missing/732 new file mode 100644 index 000000000..0bcc01b4f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/732 @@ -0,0 +1 @@ +Can not use --enable-fuzzing on Ubuntu 20.04 Aarch64 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/733 b/gitlab/issues_text/target_missing/host_missing/accel_missing/733 new file mode 100644 index 000000000..e711bc356 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/733 @@ -0,0 +1,33 @@ +Qemu Adventcalendar 2020 ELKS fails to run with error "qemu-system-x86_64: at most one isa-vga device is permitted" +Description of problem: +Running ELKS from Qemu Advent calendar results in: +qemu-system-x86_64: at most one isa-vga device is permitted +Steps to reproduce: +(with ELKS) +1. Untar https://download.qemu.org/qemu-6.2.0-rc0.tar.xz +1. Build qemu-system-x86_64 +2. Download https://www.qemu-advent-calendar.org/2020/download/day23.tar.gz +3. Execute ELKS as described in run.sh +Additional information: +A git bisect was performed to identify the culprit commit: +``` +qemu$ git bisect good +binäre Suche: danach noch 1 Commit zum Testen übrig (ungefähr 1 Schritt) +[2b3a98255c90d8d2f9f87a73eb33371961508517] hw/display/xlnx_dp: fix an out-of-bounds read in xlnx_dp_read + +qemu$ ./configure --target-list=x86_64-softmmu --disable-linux-user && make -j2 + +qemu$ build/qemu-system-x86_64 -machine isapc -vga std +qemu-system-x86_64: at most one isa-vga device is permitted + +qemu$ git bisect bad +binäre Suche: danach noch 0 Commits zum Testen übrig (ungefähr 0 Schritte) +[7852a77f598635a67a222b6c1463c8b46098aed2] vga: don't abort when adding a duplicate isa-vga device + +qemu$ cat .git/refs/bisect/bad +2b3a98255c90d8d2f9f87a73eb33371961508517 + +qemu$ git status +HEAD losgelöst bei 7852a77f59 + +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/739 b/gitlab/issues_text/target_missing/host_missing/accel_missing/739 new file mode 100644 index 000000000..1e96c74fd --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/739 @@ -0,0 +1,17 @@ +qemu option -snapshot not work for blockdev disk +Description of problem: +If disk image configured with a -blockdev option, option -snapshot not work: all changes write to disk image instead of temporary files. +Steps to reproduce: +1. Run qemu guest with -blockdev disk image file and -snapshot options +2. Create file test.txt on guest disk +3. Power off guest +4. Run qemu guest again +5. File test.txt present on guest disk +Additional information: +When i replace -blockdev options to legacy -drive option +``` +-snapshot +-drive if=none,id=ssd1-format,media=disk,cache=none,aio=native,discard=unmap,detect-zeroes=unmap,format=qcow2,file=images/windows21h2.qcow2 +-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,device_id=drive-scsi0-0-0-0,drive=ssd1-format,id=scsi0-0-0-0,write-cache=on,bootindex=1 +``` +-snapshot option work fine diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/74 b/gitlab/issues_text/target_missing/host_missing/accel_missing/74 new file mode 100644 index 000000000..767454b6f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/74 @@ -0,0 +1 @@ +AUD_set_volume_out takes SWVoiceOut as parameter, but controls HWVoiceOut diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/741 b/gitlab/issues_text/target_missing/host_missing/accel_missing/741 new file mode 100644 index 000000000..b5d772e3a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/741 @@ -0,0 +1 @@ +Document "net/net.h" API diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/746 b/gitlab/issues_text/target_missing/host_missing/accel_missing/746 new file mode 100644 index 000000000..d4226b1c2 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/746 @@ -0,0 +1 @@ +Current file VERSION of tag 6.2.0-rc2 contains 6.2.92, not 6.1.92 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/749 b/gitlab/issues_text/target_missing/host_missing/accel_missing/749 new file mode 100644 index 000000000..2765381cb --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/749 @@ -0,0 +1 @@ +Enhance QEMU live patching diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/75 b/gitlab/issues_text/target_missing/host_missing/accel_missing/75 new file mode 100644 index 000000000..98325b531 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/75 @@ -0,0 +1 @@ +Add -display SDL grab-on-hover option diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/750 b/gitlab/issues_text/target_missing/host_missing/accel_missing/750 new file mode 100644 index 000000000..db373a7af --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/750 @@ -0,0 +1,33 @@ +/proc/cpuinfo doesn't present guest cpuinfo for most architectures (including M1 Macs) +Description of problem: +I tried to start Blender inside an amd docker container, emulated on M1 Mac, running noVNC to access the the GUI via Chrome. +From Blender versions 2.8 and higher I get the following error message: + +``` + ArchError: Could not find 'cpu MHz' in /proc/cpuinfo + Function: Arch_InitTickTimer + File: /home/sybren/buildbot-builder/linux_glibc217_x86_64_cmake/build_deps/deps/build/usd/src/external_usd/pxr/base/arch/timing.cpp + Line: 133 +qemu: uncaught target signal 6 (Aborted) - core dumped +Aborted +``` + +I posted the problem to Blender [here](https://developer.blender.org/T92956) as well as to docker [here](https://github.com/docker/for-mac/issues/6047). +Steps to reproduce: +You need: +- ✅ M1 Mac +- ✅ Docker Desktop 4.1.1 (69879) + +Setup the Container: + +1. Unzip the attached file +2. In a terminal go to the unzipped folder +3. run `source build-and-launch.sh` to build the image and spin up a container +4. open a browser and go to [http://localhost:6901](http://localhost:6901) +5. login using password `pass` +6. see the README.txt on the Desktop you just logged into +7. == Follow the README instructions == + + + +[blender-bug-report-202111091146.zip](/uploads/340ada45a9ee0585cfc0cdfcc1932fb4/blender-bug-report-202111091146.zip) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/751 b/gitlab/issues_text/target_missing/host_missing/accel_missing/751 new file mode 100644 index 000000000..a5866c07a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/751 @@ -0,0 +1 @@ +Default set of CI tasks is quite broad for forks of non-developer respositories diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/753 b/gitlab/issues_text/target_missing/host_missing/accel_missing/753 new file mode 100644 index 000000000..75d1d1565 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/753 @@ -0,0 +1 @@ +qemu unable to convert file above 2 TB diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/757 b/gitlab/issues_text/target_missing/host_missing/accel_missing/757 new file mode 100644 index 000000000..03411df36 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/757 @@ -0,0 +1 @@ +intel-hda: stream reset bits are broken diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/759 b/gitlab/issues_text/target_missing/host_missing/accel_missing/759 new file mode 100644 index 000000000..72b934fb1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/759 @@ -0,0 +1,12 @@ +Copy&Paste does not work on VNC +Description of problem: +Cannot copy&paste between host and guest when vnc is used (gtk works fine). +Steps to reproduce: +1. Build qemu 6.2-rc2 using the following `./configure` options: +``` +--prefix=$HOME/.bin --target-list=x86_64-softmmu --enable-kvm --enable-vnc --enable-gtk --enable-vte --enable-xkbcommon --enable-sdl --enable-spice --enable-spice-protocol --enable-virglrenderer --enable-opengl --enable-guest-agent --enable-avx2 --enable-hax --enable-system --enable-linux-user --enable-libssh --enable-linux-aio --enable-linux-io-uring --enable-modules --enable-fuse --enable-fuse-lseek +``` +2. Run the above qemu command using vnc server. Connect to the VM desktop using `vncviewer :5900` where vncviewer is downloaded from [here](https://www.realvnc.com/en/connect/download/viewer/). +3. Try to copy and paste something in the terminal between host and guest. It doesn't work. +Additional information: +I'm following [this article](https://www.kraxel.org/blog/2021/05/qemu-cut-paste/) which says copy&paste is supported on vnc. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/76 b/gitlab/issues_text/target_missing/host_missing/accel_missing/76 new file mode 100644 index 000000000..999c83196 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/76 @@ -0,0 +1 @@ +Mouse cursor sometimes can't pass the invisible border on the right side of the screen diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/760 b/gitlab/issues_text/target_missing/host_missing/accel_missing/760 new file mode 100644 index 000000000..7b4bcf9cf --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/760 @@ -0,0 +1,3 @@ +Feature request: QEMU can report its building option +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/761 b/gitlab/issues_text/target_missing/host_missing/accel_missing/761 new file mode 100644 index 000000000..482435480 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/761 @@ -0,0 +1,12 @@ +With -display gtk,gl=on, the position of mouse does not show correctly +Description of problem: +With `-display gtk,gl=on`, the cursor of the mouse does not show correctly. So, it's very hard to use mouse on guest OS desktop to, say, open an application or to close it. The displayed mouse cursor is about 300x300 away from the actual mouse position. +Steps to reproduce: +1. Build qemu 6.2.0-rc2 using the following `./configure` options: +``` +--prefix=$HOME/.bin --target-list=x86_64-softmmu --enable-kvm --enable-vnc --enable-gtk --enable-vte --enable-xkbcommon --enable-sdl --enable-spice --enable-spice-protocol --enable-virglrenderer --enable-opengl --enable-guest-agent --enable-avx2 --enable-hax --enable-system --enable-linux-user --enable-libssh --enable-linux-aio --enable-linux-io-uring --enable-modules --enable-fuse --enable-fuse-lseek +``` +2. Run the above QEMU command with `-display gtk,gl=on`. +3. Try to open an application by clicking its icon on desktop and to close it by clicking the "X" icon. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/762 b/gitlab/issues_text/target_missing/host_missing/accel_missing/762 new file mode 100644 index 000000000..5481f6d3e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/762 @@ -0,0 +1 @@ +Assertion failure in iov_from_buf_full `offset == 0' failed through virtio-net diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/764 b/gitlab/issues_text/target_missing/host_missing/accel_missing/764 new file mode 100644 index 000000000..fce227518 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/764 @@ -0,0 +1,45 @@ +qemu-system-x86 crash (reason: use after free in socket_reconnect_timeout when reconnecting vhost-user dev) +Description of problem: +(gdb) bt<br/> +#0 0x00007f205976b78b in raise () from /usr/lib64/libc.so.6<br/> +#1 0x00007f205976cab1 in abort () from /usr/lib64/libc.so.6<br/> +#2 0x00007f205976404a in ?? () from /usr/lib64/libc.so.6<br/> +#3 0x00007f20597640c2 in __assert_fail () from /usr/lib64/libc.so.6<br/> +#4 0x00007f20594ea556 in **qemu_mutex_lock_impl**(mutex=<optimized out>, file=<optimized out>, line=<optimized out>)<br/> +#5 0x00007f205957a4ef in **socket_reconnect_timeout** (opaque=<optimized out>)<br/> +#6 0x00007f205993b68d in ?? () from /usr/lib64/libglib-2.0.so.0<br/> +#7 0x00007f205993aba4 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0<br/> +#8 0x00007f20594e5d49 in glib_pollfds_poll () at /usr/src/debug/qemu-4.1.0-666.x86_64/util/main-loop.c:218<br/> +#9 0x00007f20594e5dc2 in os_host_main_loop_wait (timeout=<optimized out>)<br/> +#10 0x00007f20594e5f5d in main_loop_wait (nonblocking=nonblocking@entry=0)<br/> +... ...<br/> +#14 0x0000560919e13180 in main (argc=80, argv=0x7ffebc1d0598, envp=0x7ffebc1d0820)<br/> + +at the moment, chr had be free by hot unplug vhost-user dev<br/> + +I think the bug cause reason as following:<br/> +1. when vhost-user dev is connecting state, io-task-worker thread will try call tcp_chr_connect_client_async <br/> + again and again to reconnect.<br/> +2. if reconnect fail, io-task-worker thread will switch to main-thread to handle error, and main-thread will <br/> +call qemu_chr_socket_restart_timer again to reconnect again. <br/> + +3. But, if a hot unplug operation insert to main-thread before io-task-worker switch to main-thread,<br/> + the qemu_chr_socket_restart_timer->socket_reconnect_timeout process will use the released chardev and <br/> + trigger qemu crash + +in short, the primary cause of this bug is io-task-worker reconnect process and <br/> +main-thread hot unplug vhost-user-dev process in a race.<br/> +Steps to reproduce: +1. in qio_task_thread_worker func, add sleep in the following position: <br/> +  task->thread->completion = g_idle_source_new(); <br/> +  g_source_set_callback(task->thread->completion,<br/> + qio_task_thread_result, task, NULL);<br/> +  **sleep(8);**<br/> +  g_source_attach(task->thread->completion,<br/> + task->thread->context);<br/> +  g_source_unref(task->thread->completion); <br/> +2. kill spdk proces or dpdk process, qemu will reconnect to the disconnected vhost-user dev of spdk or dpdk <br/> +3. hot unplug the disconnected vhost-user dev when reconnect logic goto upper sleep position <br/> +4. qemu_chr_socket_restart_timer will use the chr after free, and trigger qemu crash +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/765 b/gitlab/issues_text/target_missing/host_missing/accel_missing/765 new file mode 100644 index 000000000..57be47ea2 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/765 @@ -0,0 +1,65 @@ +Issue with Docker on M1 Mac +Description of problem: +I'm trying to run a docker container using the following command: + +``` +docker run --platform=linux/amd64 --rm uphold/litecoin-core \ + -printtoconsole \ + -regtest=1 \ + -rpcallowip=172.17.0.0/16 \ + -rpcauth='foo:1e72f95158becf7170f3bac8d9224$957a46166672d61d3218c167a223ed5290389e9990cc57397d24c979b4853f8e' +``` + +It should run the docker container, instead it throws the following error: +``` +/entrypoint.sh: assuming arguments for litecoind +/entrypoint.sh: setting data directory to /home/litecoin/.litecoin +runtime: failed to create new OS thread (have 2 already; errno=22) +fatal error: newosproc + +runtime stack: +runtime.throw(0x4cb21f, 0x9) + /usr/local/go/src/runtime/panic.go:566 +0x95 +runtime.newosproc(0xc420028000, 0xc420037fc0) + /usr/local/go/src/runtime/os_linux.go:160 +0x194 +runtime.newm(0x4d6db8, 0x0) + /usr/local/go/src/runtime/proc.go:1572 +0x132 +runtime.main.func1() + /usr/local/go/src/runtime/proc.go:126 +0x36 +runtime.systemstack(0x53ae00) + /usr/local/go/src/runtime/asm_amd64.s:298 +0x79 +runtime.mstart() + /usr/local/go/src/runtime/proc.go:1079 + +goroutine 1 [running]: +runtime.systemstack_switch() + /usr/local/go/src/runtime/asm_amd64.s:252 fp=0xc420022768 sp=0xc420022760 +runtime.main() + /usr/local/go/src/runtime/proc.go:127 +0x6c fp=0xc4200227c0 sp=0xc420022768 +runtime.goexit() + /usr/local/go/src/runtime/asm_amd64.s:2086 +0x1 fp=0xc4200227c8 sp=0xc4200227c0 +``` +Steps to reproduce: +1. Run the following in a terminal window on a Mac with an M1 chip: +``` +docker run --platform=linux/amd64 --rm uphold/litecoin-core \ + -printtoconsole \ + -regtest=1 \ + -rpcallowip=172.17.0.0/16 \ + -rpcauth='foo:1e72f95158becf7170f3bac8d9224$957a46166672d61d3218c167a223ed5290389e9990cc57397d24c979b4853f8e' +``` +Additional information: +I increased the limits using ``ulimit`` as follows: + +``` +clemens@M1-MacBook-Pro ~ % ulimit -a +-t: cpu time (seconds) unlimited +-f: file size (blocks) unlimited +-d: data seg size (kbytes) unlimited +-s: stack size (kbytes) 8176 +-c: core file size (blocks) 0 +-v: address space (kbytes) unlimited +-l: locked-in-memory size (kbytes) unlimited +-u: processes 5333 +-n: file descriptors 256 +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/768 b/gitlab/issues_text/target_missing/host_missing/accel_missing/768 new file mode 100644 index 000000000..a90467e95 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/768 @@ -0,0 +1,12 @@ +Mouse cursor disappears in RHEL guest when using "-device virtio-vga-gl -display gtk,gl=on" option +Description of problem: +Mouse cursor disappears in RHEL guest when using -device virtio-vga-gl -display gtk,gl=on +Steps to reproduce: +1. Build qemu using the following `./configure` options: +``` +--prefix=$HOME/.bin --target-list=x86_64-softmmu --enable-kvm --enable-vnc --enable-gtk --enable-vte --enable-xkbcommon --enable-sdl --enable-spice --enable-spice-protocol --enable-virglrenderer --enable-opengl --enable-guest-agent --enable-avx2 --enable-avx512f --enable-hax --enable-system --enable-linux-user --enable-libssh --enable-linux-aio --enable-linux-io-uring --enable-modules --enable-gio --enable-fuse --enable-fuse-lseek +``` +2. Install Red Hat Enterprise Linux 8.5 in qemu +3. Run qemu using the above command line. The mouse cursor disappears once it moves into the VM. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/769 b/gitlab/issues_text/target_missing/host_missing/accel_missing/769 new file mode 100644 index 000000000..1b62c4c7c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/769 @@ -0,0 +1,16 @@ +When the VM is about to enter GUI desktop or quit the system, the screen turns upside down. +Description of problem: +When the VM is about to enter GUI desktop, the remaining booting message on the screen turns upside down. I was wondering if it is a designed feature or a bug. I like it because when I see it I'm ensured I'll enter the VM's GUI desktop soon without any problem. + +An edit: This happens also at the quitting time when I type "sudo shutdown now" in the terminal. +Steps to reproduce: +1. Build qemu using the following `./configure` options: +``` +--prefix=$HOME/.bin --target-list=x86_64-softmmu --enable-kvm --enable-vnc --enable-gtk --enable-vte --enable-xkbcommon --enable-sdl --enable-spice --enable-spice-protocol --enable-virglrenderer --enable-opengl --enable-guest-agent --enable-avx2 --enable-avx512f --enable-hax --enable-system --enable-linux-user --enable-libssh --enable-linux-aio --enable-linux-io-uring --enable-modules --enable-gio --enable-fuse --enable-fuse-lseek +``` +2. Install Red Hat Enterprise Linux 8.5 in qemu +3. Run qemu using the above command line, or type "sudo shutdown now" in the terminal after VM starts. +Additional information: + + + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/774 b/gitlab/issues_text/target_missing/host_missing/accel_missing/774 new file mode 100644 index 000000000..ada08ec11 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/774 @@ -0,0 +1,15 @@ +Win(PE) NIC issue with pc-q35-6.1 +Description of problem: +When booting WinPE (via PXE via WDS) on a `pc-q35-6.1` machine, the NIC will not initialize. + +What I got with `pnputil.exe /enum-devices /class net` is `Device has problem: 56 0x38 (CM_PROB_NEED_CLASS_CONFIG)` See: [CM_PROB_NEED_CLASS_CONFIG](https://docs.microsoft.com/en-us/windows-hardware/drivers/install/cm-prob-need-class-config) + +I'm using virt manager and I've tried both `e1000e` and `virtio` network adapters (virtio with drivers injected into the image of course). Both yield the aforementioned error and `ipconfig` remains empty. This is an obscure problem - I haven't checked if a normal windows install behaves the same way, but it might be unique to winpe. + +However, with `pc-q35-5.2`, the NIC initializes without a problem. +Steps to reproduce: +1. Create `pc-q35-6.1` based vm in virt manager with default settings (network bridged to network bridge) +2. PXE boot Windows Setup +3. Observe hang (observe errors with console `SHIFT+F10`) +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/775 b/gitlab/issues_text/target_missing/host_missing/accel_missing/775 new file mode 100644 index 000000000..975835612 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/775 @@ -0,0 +1,4 @@ +Backup always use Microsoft VSS-FULL Option and breaks other Backups +Additional information: +MS VSS-Options +[https://docs.microsoft.com/en-us/windows/win32/api/vss/ne-vss-vss_backup_type](https://docs.microsoft.com/en-us/windows/win32/api/vss/ne-vss-vss_backup_type) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/776 b/gitlab/issues_text/target_missing/host_missing/accel_missing/776 new file mode 100644 index 000000000..ec68848ba --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/776 @@ -0,0 +1,25 @@ +Windows guest fails to start on 6.1.0 - opengl is not available +Description of problem: +I've created a Windows 10 guest with virt-manager. The VM started successfully with qemu 6.0.0-3. After upgrading to 6.1.0 +it fails with the following error: + +``` +2021-12-14T19:11:52.884272Z qemu-system-x86_64: warning: This feature depends on other features that were not requested: CPUID.8000000AH:EDX.svme-addr-chk [bit 28] +2021-12-14T19:11:52.885199Z qemu-system-x86_64: warning: This feature depends on other features that were not requested: CPUID.8000000AH:EDX.svme-addr-chk [bit 28] +2021-12-14T19:11:52.885852Z qemu-system-x86_64: warning: This feature depends on other features that were not requested: CPUID.8000000AH:EDX.svme-addr-chk [bit 28] +2021-12-14T19:11:52.886485Z qemu-system-x86_64: warning: This feature depends on other features that were not requested: CPUID.8000000AH:EDX.svme-addr-chk [bit 28] +2021-12-14T19:11:52.887098Z qemu-system-x86_64: warning: This feature depends on other features that were not requested: CPUID.8000000AH:EDX.svme-addr-chk [bit 28] +2021-12-14T19:11:52.887773Z qemu-system-x86_64: warning: This feature depends on other features that were not requested: CPUID.8000000AH:EDX.svme-addr-chk [bit 28] +2021-12-14T19:11:52.912523Z qemu-system-x86_64: -device virtio-vga-gl,id=video0,max_outputs=1,bus=pcie.0,addr=0x1: opengl is not available +2021-12-14 19:11:53.109+0000: shutting down, reason=failed +``` + +Upgrading to 6.2.0.rc4 did not fix it. Downgrading to 6.0.0-3 made it work again. This makes it clear to me that the bug was introduce in qemu > 6.0.0 and seems to be not fix by now. + +I was able to start the guest on 6.1.0 by disabling 3D acceleration. +Steps to reproduce: +1. Create Windows 10 guest VM +2. Start with qemu 6.0.0 -> Works +3. Start with qemu 6.1.0 -> Broken +Additional information: +People on Reddit mention the same characteristic of this bug -> https://www.reddit.com/r/Fedora/comments/qqw3sq/qemu_video_virtio_opengl_not_available_after/ diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/778 b/gitlab/issues_text/target_missing/host_missing/accel_missing/778 new file mode 100644 index 000000000..77ec3d0ca --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/778 @@ -0,0 +1 @@ +heap-buffer-overflow in megasas_sgl_get_len diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/779 b/gitlab/issues_text/target_missing/host_missing/accel_missing/779 new file mode 100644 index 000000000..b0aad8d49 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/779 @@ -0,0 +1,13 @@ +VNC server not work +Description of problem: +I've created a sandbox guest with kata containers. The VM started successfully, but vnc server not listen unix socket. + +`root@bootstrap02:~# netstat -anp | grep 1989153` +`unix 3 [ ] STREAM CONNECTED 369610592 1989153/qemu-system /run/vc/vm/bash/qmp.sock` +`root@bootstrap02:~# lsof -p 1989153 | grep unix` +`qemu-syst 1989153 root 108u unix 0xffff912740d3b800 0t0 369610592 /run/vc/vm/bash/qmp.sock type=STREAM` +Steps to reproduce: +1.Create Linux sandbox guest VM +2.connect vnc server +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/781 b/gitlab/issues_text/target_missing/host_missing/accel_missing/781 new file mode 100644 index 000000000..93d5b052e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/781 @@ -0,0 +1 @@ +Assertion `addr < cache->len && 2 <= cache->len - addr' failed in address_space_stw_le_cached diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/782 b/gitlab/issues_text/target_missing/host_missing/accel_missing/782 new file mode 100644 index 000000000..b69e00482 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/782 @@ -0,0 +1,5 @@ +nvme: DMA reentrancy issue leads to use-after-free (CVE-2021-3929) +Description of problem: +A DMA reentrancy issue was found in the NVM Express Controller (NVMe) emulation. Functions dma_buf_write() or dma_buf_read() in hw/nvme/ctrl.c:nvme_tx() can be called without checking if the destination region overlaps with device's MMIO. This is similar to CVE-2021-3750 (https://gitlab.com/qemu-project/qemu/-/issues/541) and, just like it, when the reentrancy write triggers the reset function nvme_ctrl_reset(), data structs will be freed leading to a use-after-free issue. A malicious guest could use this flaw to crash the QEMU process on the host, resulting in a denial of service condition or, potentially, executing arbitrary code within the context of the QEMU process on the host. + +This issue was reported by Qiuhao Li. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/784 b/gitlab/issues_text/target_missing/host_missing/accel_missing/784 new file mode 100644 index 000000000..010463a37 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/784 @@ -0,0 +1,13 @@ +max_hostmem does not work with virtio-vga-gl +Description of problem: +With property `max_hostmem=1000`, I hope the virgl VGA device can have 1GB video memory. But, after the VM starts, the command `glxinfo -B` returns "Video memory: 0MB", which I think means the virgl VGA does not obtain any video memory, or `max_hostmem=1000` does not work with `virtio-vga-gl`. Is it a bug or virgl has other property parameter to specify video memory? +Steps to reproduce: +1. Build qemu using the following `./configure` options: +``` +--prefix=$HOME/.bin --target-list=x86_64-softmmu --enable-kvm --enable-vnc --enable-gtk --enable-vte --enable-xkbcommon --enable-sdl --enable-spice --enable-spice-protocol --enable-virglrenderer --enable-opengl --enable-guest-agent --enable-avx2 --enable-avx512f --enable-hax --enable-system --enable-linux-user --enable-libssh --enable-linux-aio --enable-linux-io-uring --enable-modules --enable-gio --enable-fuse --enable-fuse-lseek +``` +2. Install Red Hat Enterprise Linux 8.5 in qemu +3. Run qemu using the above command line. +4. Type `glxinfo -B` in VM terminal +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/785 b/gitlab/issues_text/target_missing/host_missing/accel_missing/785 new file mode 100644 index 000000000..fe2a9e713 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/785 @@ -0,0 +1 @@ +Build failure on macOS with jack diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/787 b/gitlab/issues_text/target_missing/host_missing/accel_missing/787 new file mode 100644 index 000000000..f485be199 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/787 @@ -0,0 +1,12 @@ +6.2.0 Regression with Intel GVT-g +Description of problem: +Until version 6.1.0 the Intel GVT-g graphics passtrought was working flawless. But, since the version 6.2.0 the machine with the exact same configuration is not working anymore, presenting an error that the graphics device was not found. + +``` +qemu-system-x86_64: -set device.hostdev0.x-igd-opregion=on: there is no device "hostdev0" defined +``` + +Downgrade to 6.1.0 fixes the problem. +Steps to reproduce: +1. Create a virtual machine with GVT-g +2. Try to run the machine. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/79 b/gitlab/issues_text/target_missing/host_missing/accel_missing/79 new file mode 100644 index 000000000..6f677cbda --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/79 @@ -0,0 +1 @@ +support horisontal mouse wheel diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/793 b/gitlab/issues_text/target_missing/host_missing/accel_missing/793 new file mode 100644 index 000000000..b133940e4 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/793 @@ -0,0 +1 @@ +Wrong pci express bus type - qemu 6.1.0-5 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/794 b/gitlab/issues_text/target_missing/host_missing/accel_missing/794 new file mode 100644 index 000000000..2da57a24a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/794 @@ -0,0 +1,9 @@ +Documentation: Broken links to removed features in old changelog pages +Description of problem: +In QEMU changelogs prior to 6.1 (notably 6.0 at least) the removed features link goes to https://qemu-project.gitlab.io/qemu/system/removed-features.html instead of https://qemu-project.gitlab.io/qemu/about/removed-features.html. The deprecated features links are also broken. + +This caused me some amount of confusion while trying to find the cause of several emulation issues. +Additional information: +Would have fixed myself but I cannot create a QEMU wiki account to do so. If there is a process for approval for that I will happily follow it and fix the issue when approved. I also can't see anywhere else to report this so apologies if this is the wrong place. + +Perhaps the main changelog page could include links to the removed and deprecated features pages too? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/795 b/gitlab/issues_text/target_missing/host_missing/accel_missing/795 new file mode 100644 index 000000000..221c33218 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/795 @@ -0,0 +1 @@ +meson.build: coreaudio check failed diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/796 b/gitlab/issues_text/target_missing/host_missing/accel_missing/796 new file mode 100644 index 000000000..63c25872c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/796 @@ -0,0 +1,17 @@ +make -j126 check failed in qemu@6.2.0 on ubuntu_aarch64 +Steps to reproduce: +the issue + +```console +[root@localhost build]#make -j126 check +Running test fp-test-sqrt +Running test fp-test-sub +Running test fp-test-log2 +** +ERROR:../tests/unit/test-qga.c:718:test_qga_config: assertion failed (err == ""): ("/home/stage/root/spack-stage-qemu-6.2.0-532ksrh2smva65sb3ghqox222237khs5/spack-src/build/qga/qemu-ga: symbol lookup error: /home/stage/root/spack-stage-qemu-6.2.0-532ksrh2smva65sb3ghqox222237khs5/spack-src/build/qga/qemu-ga: undefined symbol: g_unix_get_passwd_entry\n" == "") +ERROR test-qga - Bail out! ERROR:../tests/unit/test-qga.c:718:test_qga_config: assertion failed (err == ""): ("/home/stage/root/spack-stage-qemu-6.2.0-532ksrh2smva65sb3ghqox222237khs5/spack-src/build/qga/qemu-ga: symbol lookup error: /home/stage/root/spack-stage-qemu-6.2.0-532ksrh2smva65sb3ghqox222237khs5/spack-src/build/qga/qemu-ga: undefined symbol: g_unix_get_passwd_entry\n" == "") +make: *** [Makefile.mtest:1472: run-test-182] Error 1 +make: *** Waiting for unfinished jobs.... +…… +``` +I don't know why happen,can you help me? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/798 b/gitlab/issues_text/target_missing/host_missing/accel_missing/798 new file mode 100644 index 000000000..b56e51c02 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/798 @@ -0,0 +1,15 @@ +The sandbox option elevelateprivileges=deny does not work with -daemonize +Description of problem: +qemu will not launch if `-sandbox on,elevateprivileges=deny` and `-daemonize` are set at the same time. +Steps to reproduce: +``` +qemu-system-x86_64 -sandbox on,elevateprivileges=deny -nodefaults -daemonize +``` +-> fails to launch + +``` +qemu-system-x86_64 -sandbox on -nodefaults -daemonize +``` +-> runs normally +Additional information: +[journal.txt](/uploads/c0e2a973e749011c3b1ac2158420a4e8/journal.txt) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/80 b/gitlab/issues_text/target_missing/host_missing/accel_missing/80 new file mode 100644 index 000000000..e1c6942ad --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/80 @@ -0,0 +1 @@ +[Feature request] qemu-img multi-threaded compressed image conversion diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/800 b/gitlab/issues_text/target_missing/host_missing/accel_missing/800 new file mode 100644 index 000000000..a29195b05 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/800 @@ -0,0 +1,25 @@ +Cannot write to MTP Devices in Qemu 6.0.0+ +Description of problem: +QEMU versions above 6.0.0 are no longer able to write to MTP devices, the kernel prints a warning which is unique to versions above 6.0.0: +``` +usb-mtp: file monitoring init failed: File monitoring not available on this platform is just warning +``` +Steps to reproduce: +1. Launch a QEMU virtual machine with `-usb -device usb-mtp,rootdir=/tmp,readonly=false` using any QEMU version above 6.0.0 +2. Mount the MTP device using something: + ``` + mkdir mtpDevice && jmtpfs mtpDevice + ``` +3. Try to write to the mtp device: + ``` + touch mtpDevice/test + ``` +4. Observe that you will get an input/output error when trying to write to the device, like this: + ``` + vm-test-run-mtp> client: must succeed: /nix/store/xmib7222ybr72iyycra4w386s8p1k4av-jmtpfsTest.sh >&2 + vm-test-run-mtp> client # Device 0 (VID=46f4 and PID=0004) is a QEMU Virtual MTP. + vm-test-run-mtp> client # qemu-system-x86_64: usb-mtp: file monitoring init failed: File monitoring not available on this platform + vm-test-run-mtp> client # /nix/store/xmib7222ybr72iyycra4w386s8p1k4av-jmtpfsTest.sh: line 4: phone/tmp/testFile: Input/output error + ``` +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/801 b/gitlab/issues_text/target_missing/host_missing/accel_missing/801 new file mode 100644 index 000000000..c123af02a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/801 @@ -0,0 +1,12 @@ +QEMU test build failure with --enable-modules +Description of problem: + +Steps to reproduce: +1. ./configure --target-list=x86_64-softmmu --enable-kvm --enable-modules +2. make -j8 check-qtest-x86_64 V=1 + + - A problem happens "qemu-system-x86_64: -accel qtest: invalid accelerator qtest" + - The file accel-qtest-x86_64.so is not built + - This problem happens since 69c4c5c1c47f5dac140eb6485c5281a9f145dcf3 Mon Sep 17 00:00:00 2001 +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/802 b/gitlab/issues_text/target_missing/host_missing/accel_missing/802 new file mode 100644 index 000000000..64604e30c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/802 @@ -0,0 +1,26 @@ +Devices created using '-device' JSON syntax don't emit DEVICE_DELETED when unplugged +Description of problem: +Run the following sequence: + +``` + $ ./qemu-system-x86_64 -qmp stdio \ + -device '{"driver": "virtio-mouse-pci", "id": "dev0"}' \ + -device virtio-mouse-pci,id=dev1 +{"QMP": {"version": {"qemu": {"micro": 50, "minor": 2, "major": 6}, "package": "v6.2.0-105-g7494244ffc-dirty"}, "capabilities": ["oob"]}} +{ "execute": "qmp_capabilities" } +{"return": {}} +{ "execute": "device_del", "arguments": { "id": "dev0"} } +{"return": {}} +{ "execute": "device_del", "arguments": { "id": "dev1"} } +{"return": {}} +{ "execute": "system_reset" } +{"return": {}} +{"timestamp": {"seconds": 1641385071, "microseconds": 120178}, "event": "RESET", "data": {"guest": false, "reason": "host-qmp-system-reset"}} +{"timestamp": {"seconds": 1641385071, "microseconds": 121431}, "event": "DEVICE_DELETED", "data": {"path": "/machine/peripheral/dev1/virtio-backend"}} +{"timestamp": {"seconds": 1641385071, "microseconds": 121684}, "event": "DEVICE_DELETED", "data": {"device": "dev1", "path": "/machine/peripheral/dev1"}} +{"timestamp": {"seconds": 1641385071, "microseconds": 122297}, "event": "DEVICE_DELETED", "data": {"path": "/machine/peripheral/dev0/virtio-backend"}} +{"timestamp": {"seconds": 1641385071, "microseconds": 198581}, "event": "RESET", "data": {"guest": true, "reason": "guest-reset"}} + + ``` + +Notice the lack of a "DEVICE_DELETED" event with path "/machine/peripheral/dev0" - the device created with JSON syntax diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/804 b/gitlab/issues_text/target_missing/host_missing/accel_missing/804 new file mode 100644 index 000000000..5a89392bb --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/804 @@ -0,0 +1,9 @@ +savevm - QXL preventing save +Description of problem: +Attempting to savevm with a QXL VGA device attached causes the error "pre-save failed: qxl" to appear. +Steps to reproduce: +1. Start a QEMU instance with a QXL device +2. Attempt to savevm +3. See error +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/806 b/gitlab/issues_text/target_missing/host_missing/accel_missing/806 new file mode 100644 index 000000000..da512a822 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/806 @@ -0,0 +1,63 @@ +Fixed VHDX inflates beyond its fixed size when data is copied onto it and also corrupts +Description of problem: +Fixed VHDX inflates beyond its fixed size when data is copied onto it +Possibly also corrupted + +Filing this bug as separate from #727, that issue is for corruption during expansion of a dynamic disk. +The effect seen here is different. There may or may not be a chance of common cause. New blocks should not have to be allocated to the VHDX spec Block-Allocation-Table (BAT), there may be a simpler and different fix for this issue. + +Perhaps blocks are written to a VHDX journal without being committed to allocated blocks. +Perhaps the host's ExFAT filesystem, does not allow reclaiming the blocks that are to be replaced by punching holes and so must be over-written instead of punching holes. +Steps to reproduce: +1. Prepare virtual-disk1 + Create fixed vhdx + ``` + [root@sirius gana]# qemu-img create -f vhdx /mnt/a16/gkpics01.vhdx -o subformat=fixed 99723771904 + Formatting '/mnt/a16/gkpics01.vhdx', fmt=vhdx size=99723771904 log_size=1048576block_size=0 subformat=fixed``` +2. Prepare virtual-disk2 + Put 85 GiB synthetic generated data sgdata as mentioned in https://gitlab.com/qemu-project/qemu/-/issues/727#note_739930694 +3. Start qemu (command invocation given above) +4. Partition /dev/sda, put ext4-fs on /dev/sda1 +5. Mount -t ext4 /dev/sda1 /mnt/a +6. Mount /dev/sdb2 /mnt/b (mounts using fuse-blk tuxera ntfs driver) +7. Do rsync: + ``` + (sdate=`date` ; cd /mnt/b ; rsync -avH ./photos001 /mnt/a | tee /tmp/rst.txt ; echo $sdate ; date) + ``` +8. In a host terminal, do ls -l on the vhdx file, and observe that it grows in size (see logs below) +Additional information: +* virtual-disk-1 (<90 GiB) is on ExFAT partition (150 GiB) on SSD +* virtual-disk-2 (~85 Gib) is on NTFS3 partition (1 TiB) on HDD + + +``` +[root@sirius gana]# qemu-img create -f vhdx /mnt/a16/gkpics01.vhdx -o subformat=fixed 99723771904 +Formatting '/mnt/a16/gkpics01.vhdx', fmt=vhdx size=99723771904 log_size=1048576block_size=0 subformat=fixed +[root@sirius gana]# ls -l /mnt/a16/gkpics01.vhdx +-rwxr-xr-x. 1 root root 99732160512 Jan 8 13:11 /mnt/a16/gkpics01.vhdx +[root@sirius gana]# ls -l /mnt/a16/gkpics01.vhdx +-rwxr-xr-x. 1 root root 99732160512 Jan 8 13:11 /mnt/a16/gkpics01.vhdx +[root@sirius gana]# ls -l /mnt/a16/gkpics01.vhdx +-rwxr-xr-x. 1 root root 99732160512 Jan 8 13:11 /mnt/a16/gkpics01.vhdx +[root@sirius gana]# ls -l /mnt/a16/gkpics01.vhdx +-rwxr-xr-x. 1 root root 99765714944 Jan 8 13:35 /mnt/a16/gkpics01.vhdx +[root@sirius gana]# ls -l /mnt/a16/gkpics01.vhdx + +do gdisk and partition in guestvm +-rwxr-xr-x. 1 root root 100705239040 Jan 8 13:36 /mnt/a16/gkpics01.vhdx + +do mkfs -t ext4 in guestvm +[root@sirius gana]# ls -l /mnt/a16/gkpics01.vhdx +-rwxr-xr-x. 1 root root 101342773248 Jan 8 13:36 /mnt/a16/gkpics01.vhdx + +start rsyncing data in guestvm +[root@sirius gana]# ls -l /mnt/a16/gkpics01.vhdx +-rwxr-xr-x. 1 root root 102097747968 Jan 8 13:38 /mnt/a16/gkpics01.vhdx +[root@sirius gana]# ls -l /mnt/a16/gkpics01.vhdx +-rwxr-xr-x. 1 root root 102215188480 Jan 8 13:38 /mnt/a16/gkpics01.vhdx +[root@sirius gana]# ls -l /mnt/a16/gkpics01.vhdx +-rwxr-xr-x. 1 root root 149375942656 Jan 8 13:50 /mnt/a16/gkpics01.vhdx +[root@sirius gana]# ls -l /mnt/a16/gkpics01.vhdx +-rwxr-xr-x. 1 root root 156170715136 Jan 8 13:58 /mnt/a16/gkpics01.vhdx +``` +in my case partition fills up and not completed. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/807 b/gitlab/issues_text/target_missing/host_missing/accel_missing/807 new file mode 100644 index 000000000..aa00dda6a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/807 @@ -0,0 +1,18 @@ +TigerVNC client to built-in VNC server causes VM to crash/freeze +Description of problem: +Connecting to the built-in VNC server via TigerVNC upon disconnect the whole VM process freezes/crashes. The process continues to exist but does not respond to any network connection and the monitor socket is dead too. Killing it with TERM doesn't work. + +Using tigervnc-viewer 1.10.1+dfsg-3 (Ubuntu 20.04) with default options like `vncviwer localhost:0` +Steps to reproduce: +* `qemu-system-x86_64 -vnc 127.0.0.1:0` + * Connect to built-in VNC server via TigerVNC + * Keep the VNC connection open and wait some period of time (usually 5-10 minutes is enough though sometimes hours) then disconnect/reconnect VNC. If the reconnect succeeds then wait again for a period of time then disconnect and try again until failure. Often just connecting and disconnecting to the VNC once is enough to make the VM eventually crash/freeze even if running only in the background but this is less reproducible. + * Observe VM is no longer responsive to anything + +If TigerVNC is never connected/disconnected from the VM then this doesn't happen. +Additional information: +Note due to the nature of this issue it might be hard to reproduce for unknown reasons. The VM always eventually freezes though. The qemu process has no output when it freezes. + +As far as I can tell connecting to the built-in VNC server via `gvncviwer` seems to be OK and doesn't cause an issue (?). I'm not sure about other VNC clients (eg. TurboVNC). + +I am connecting to the VNC server from a completely different machine than the host via SSH port redirection (the host is headless). Not sure if that matters. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/808 b/gitlab/issues_text/target_missing/host_missing/accel_missing/808 new file mode 100644 index 000000000..b78635821 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/808 @@ -0,0 +1,18 @@ +virtio-scsi in Windows guests cause QEMU to abort/crash +Description of problem: +* Attempting to load the virtio-scsi drivers in a Windows guest causes the VM to abort/crash. +Steps to reproduce: +* `qemu-system-x86_64 -accel kvm -m 4G -device virtio-scsi-pci,id=scsi0 -drive media=cdrom,file=windows7-x64.iso -drive media=cdrom,file=virtio-win-0.1.173.iso` + * Boot the installer ISO, click through all the menus to eventually get to Custom Install + * In "Where do you want to install" click Load driver + * Browse E: drive and pick the first amd64/w7 folder + * Should show "Red Had VirtIO SCSI pass-through controller" + * Click Next + * Abort/crash + +Same thing happens with VM's that used to work already running the virtio-scsi drivers. When they boot the VM aborts. +Additional information: +``` +qemu-system-x86_64: ../accel/kvm/kvm-all.c:1760: kvm_irqchip_commit_routes: Assertion `ret == 0' failed. +Aborted (core dumped) +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/81 b/gitlab/issues_text/target_missing/host_missing/accel_missing/81 new file mode 100644 index 000000000..164ea2465 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/81 @@ -0,0 +1 @@ +[Feature request] qemu-img option about recompressing diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/811 b/gitlab/issues_text/target_missing/host_missing/accel_missing/811 new file mode 100644 index 000000000..268c13918 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/811 @@ -0,0 +1 @@ +qemu_irq_split() callers should use TYPE_SPLIT_IRQ device instead diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/812 b/gitlab/issues_text/target_missing/host_missing/accel_missing/812 new file mode 100644 index 000000000..08e604c89 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/812 @@ -0,0 +1,124 @@ +Multicast packets (mDNS) are not sent out of VM +Description of problem: +The app is sending multicast packets (mDNS), but they are not sent out of VM. +Here is the configuration of the network: `-netdev user,id=net0,hostfwd=tcp::2222-:22,hostfwd=tcp::50051-:50051,hostfwd=tcp::50050-:50050` +Steps to reproduce: +1. Install arduino-cli from https://github.com/arduino/arduino-cli/releases (eg. 0.20.2) +2. `arduino-cli config init` +3. `vi ~/.arduino15/arduino-cli.yaml` +4. edit it to have it as follows: +``` +board_manager: + additional_urls: ["http://arduino.esp8266.com/stable/package_esp8266com_index.json"] +daemon: + port: "50051" +directories: + data: /root/app/data + downloads: /root/app/downloads + user: /root/app/user +library: + enable_unsafe_install: false +logging: + file: "" + format: text + level: info +metrics: + addr: :9090 + enabled: false +output: + no_color: false +sketch: + always_export_binaries: false +updater: + enable_notification: true +``` + +5. `arduino-cli core update-index` +6. `arduino-cli core install esp8266:esp8266` +7. `arduino-cli board list -v` + +This will give an output similar to: +``` +INFO[0000] Using config file: /root/.arduino15/arduino-cli.yaml +INFO[0000] arduino-cli.x86_64 version git-snapshot +INFO[0000] Checking if CLI is Bundled into the IDE +INFO[0000] Adding libraries dir dir=/root/app/user/libraries location=user +INFO[0000] Checking signature index=/root/app/data/package_index.json signatureFile=/root/app/data/package_index.json.sig = +INFO[0000] Checking signature error="opening signature file: open /root/app/data/package_esp8266com_index.json.sig: no such file or d= +INFO[0000] Loading hardware from: /root/app/data/packages +INFO[0000] Loading package builtin from: /root/app/data/packages/builtin +INFO[0000] Checking existence of 'tools' path: /root/app/data/packages/builtin/tools +INFO[0000] Loading tools from dir: /root/app/data/packages/builtin/tools +INFO[0000] Loaded tool tool="builtin:ctags@5.8-arduino11" +INFO[0000] Loaded tool tool="builtin:mdns-discovery@1.0.2" +INFO[0000] Loaded tool tool="builtin:serial-discovery@1.3.1" +INFO[0000] Loaded tool tool="builtin:serial-monitor@0.9.1" +INFO[0000] Loading package esp8266 from: /root/app/data/packages/esp8266/hardware +INFO[0000] Checking signature error="opening signature file: open /root/app/data/packages/esp8266/hardware/esp8266/3.0.2/installed.js= +INFO[0000] Adding monitor tool protocol=serial tool="builtin:serial-monitor" +INFO[0000] Loaded platform platform="esp8266:esp8266@3.0.2" +INFO[0000] Checking existence of 'tools' path: /root/app/data/packages/esp8266/tools +INFO[0000] Loading tools from dir: /root/app/data/packages/esp8266/tools +INFO[0000] Loaded tool tool="esp8266:mklittlefs@3.0.4-gcc10.3-1757bed" +INFO[0000] Loaded tool tool="esp8266:mkspiffs@3.0.4-gcc10.3-1757bed" +INFO[0000] Loaded tool tool="esp8266:python3@3.7.2-post1" +INFO[0000] Loaded tool tool="esp8266:xtensa-lx106-elf-gcc@3.0.4-gcc10.3-1757bed" +INFO[0000] Adding libraries dir dir=/root/app/data/packages/esp8266/hardware/esp8266/3.0.2/libraries location=platform +INFO[0007] Executing `arduino-cli board list` +INFO[0007] starting discovery builtin:serial-discovery process +INFO[0007] started discovery builtin:serial-discovery process +INFO[0007] sending command HELLO 1 "arduino-cli git-snapshot" to discovery builtin:serial-discovery +INFO[0007] starting discovery builtin:mdns-discovery process +INFO[0007] started discovery builtin:mdns-discovery process +INFO[0007] sending command HELLO 1 "arduino-cli git-snapshot" to discovery builtin:mdns-discovery +INFO[0007] from discovery builtin:serial-discovery received message type: hello, message: OK, protocol version: 1 +INFO[0007] from discovery builtin:mdns-discovery received message type: hello, message: OK, protocol version: 1 +INFO[0007] sending command START to discovery builtin:serial-discovery +INFO[0007] sending command START to discovery builtin:mdns-discovery +INFO[0007] from discovery builtin:mdns-discovery received message type: start, message: OK +INFO[0007] from discovery builtin:serial-discovery received message type: start, message: OK +INFO[0008] sending command LIST to discovery builtin:serial-discovery +INFO[0008] sending command LIST to discovery builtin:mdns-discovery +INFO[0008] from discovery builtin:mdns-discovery received message type: list +INFO[0008] from discovery builtin:serial-discovery received message type: list, ports: [/dev/ttyS0] +INFO[0008] sending command STOP to discovery builtin:serial-discovery +INFO[0008] sending command STOP to discovery builtin:mdns-discovery +INFO[0008] from discovery builtin:mdns-discovery received message type: stop, message: OK +INFO[0008] from discovery builtin:serial-discovery received message type: stop, message: OK +Port Protocol Type Board Name FQBN Core +/dev/ttyS0 serial Unknown +``` + +Note `builtin:mdns-discovery` discovery started. It is expected to send the packets as follows (the screenshot from the host with Wireshark): + + + +The screenshot is taken if running the same app (but for macOS) from the host and **i can't see the packets sent if executed from the QEMU guest os**. +I believe i either configured it the wrong way (`-netdev user,id=net0,...`) or it's a QEMU bug. +Additional information: +I've tested on macOS host with qemu 6.0.0 and on Linux (Android) host with qemu 6.1.0 and both were not working. + +the network interface seems to be configured for multicasting: +``` +# ifconfig +eth0 Link encap:Ethernet HWaddr 52:54:00:12:34:57 + inet addr:10.0.2.15 Bcast:0.0.0.0 Mask:255.255.255.0 + inet6 addr: fec0::5054:ff:fe12:3457/64 Scope:Site + inet6 addr: fe80::5054:ff:fe12:3457/64 Scope:Link + UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 + RX packets:91955 errors:0 dropped:0 overruns:0 frame:0 + TX packets:25203 errors:0 dropped:0 overruns:0 carrier:0 + collisions:0 txqueuelen:1000 + RX bytes:119904373 (114.3 MiB) TX bytes:1868274 (1.7 MiB) + +lo Link encap:Local Loopback + inet addr:127.0.0.1 Mask:255.0.0.0 + inet6 addr: ::1/128 Scope:Host + UP LOOPBACK RUNNING MTU:65536 Metric:1 + RX packets:0 errors:0 dropped:0 overruns:0 frame:0 + TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 + collisions:0 txqueuelen:1000 + RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) +``` + +It might be easier to skip using arduino-cli and just use any mdns discovery app. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/813 b/gitlab/issues_text/target_missing/host_missing/accel_missing/813 new file mode 100644 index 000000000..e1938a63f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/813 @@ -0,0 +1,15 @@ +On windows, preallocation=full qcow2 not creatable, qcow2 not resizable +Description of problem: +Not possible to create a fixed-virtual-disk qcow as one may do on linux. +One sometimes may want to create a fixed size qcow2, as can be done with the fixed variants of VHDX, VMDK, VDI, + +The advantage of a fixed virtual-disk format, such as fixed-VHDX, fixed-VMDK, fixed-VDI is that it keeps the disk-meta-data as a header bundled along with that is essentially a raw image, allowing for seamless tooling and management of virtual-disks + +Workaround use a raw file as diskimage. (see workaround given below) + +To be very general, the implementation of this may need to factor in what underlying operations (fallocate, fallocate_punchhole, truncate, sparse) are supported by what filesystems (NTFS, ExFAT, ext4), choice of filesystem-driver (sometimes the driver may not have yet implemented an underlying operation), and operating systems (Linux/Win), and possible workarounds to achieve the same effect in the absence of underlying-operation. +Steps to reproduce: +1. open command shell +2. run the qemu-img command. In my case, qcow2 file is attempted to be created on a drive with ExFAT filesystem. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/814 b/gitlab/issues_text/target_missing/host_missing/accel_missing/814 new file mode 100644 index 000000000..4aaa94721 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/814 @@ -0,0 +1,37 @@ +On Windows, qcow2 is corrupted on expansion +Description of problem: +On Windows, the qcow2 loses blocks on account of which the filesystem withing is corrupted as data is copied to it, just the same way as in #727 VHDX is corrupted on expansion on both Linux/Windows. + +After filing a bug for WNBD https://github.com/cloudbase/wnbd/issues/63 , I was suggested to try raw and qcow2. In the process I found that qcow2 is also affected. But it is also true that the kernel-5.15.4 ... 5.15.13 series have also been buggy https://bugzilla.kernel.org/show_bug.cgi?id=215460 . +On Linux, qcow2 never showed any signs of corruption. +On Windows, however, qcow2 does corrupt. + +It is possible that, as Linux is so much more efficient at files and disk-IO, the kernel-block-code, qemu-block-code and qemu-qcow2-code do not hit the bug, and so the corruption does not show up as easily in Linux. Windows, being a little slower at this, might be causing the bug to show up in this qcow2 test. Possibly, the issue more likely to show up on slower machines. I am using an 2013-era intel-4rth gen i7-4700mq Haswell machine. + +It is possible that, the resolution for this issue and that for #727 could be the same or very closely related. The bug may not be in qcow2.c or vhdx.c but maybe in the qemu/block subsystem. If the data-block that arrives from the VM-interface/nbd-interface which has to be written to file, but never gets to the virtual-disk code, not allocated and written to, then the data-block is lost. +Steps to reproduce: +1. Prepare virtual-disk1 as empty qcow2. In my-setup, the qcow2 file resides on an 150 GiB ExFAT partition on 512 GiB SSD. I use ExFAT as the ExFAT-filesystem does not have a concept of sparse files, eliminating that factor from troubleshooting. + ```qemu-img.exe create -f qcow2 H:\gkpics01.qcow2 99723771904``` +2. Prepare virtual-disk2 VHDX with synthetic generated data (sgdata). Scriptlets to recreate sgdata are described in https://gitlab.com/qemu-project/qemu/-/issues/727#note_739930694 . In my-setup, the vhdx file resides on an 1 TiB NTFS partition on a 2 TiB HDD. +3. Start qemu with arguments as given above. +4. Inside VM, boot and bringup livecd desktop, close the installer and open a terminal +5. Use gdisk to put an ext4 partition on /dev/sda +6. Put ext4 partition on sda1 ```mkfs.ext4 -L fs_gkpics01 /dev/sda1``` +7. Create mount directories ```mkdir /mnt/a /mnt/b``` +8. Mount the empty partition from virtual-disk-1 ```mount -t ext4 /dev/sda1 /mnt/a``` +9. Mount the sgdata partition from virtual-disk-2 ```mount.ntfs-3g /dev/sdb2 /mnt/b``` or ```mount -t ntfs3 /dev/sdb2 /mnt/b``` +10. Keep a terminal tab open with ```dmesg -w``` running +11. Rsync sgdata ```( sdate=`date` ; cd /mnt/b ; rsync -avH ./photos001 /mnt/a | tee /tmp/rst.txt ; echo $sdate ; date )``` +12. Check sha256sum ```( sdate=`date` ; cd /mnt/a/photos001 ; shas256sum -c ./find.CHECKSUM --quiet ; echo $sdate ; date )``` + corruption will show even without needing to unmount-remount or reboot-remount. + +- About 1.4 GiB free-space left on the ext4 partition. +- Compared to #727, The number of files corrupted are less ``` sha256sum: WARNING: 31 computed checksums did not match ``` +- After, VM guest OS warm reboot, a recheck of the sha256sum shows the same 31 files as corrupted +- After, qemu poweroff, restart qemu, VM guest OS cold boot, a recheck of the sha256sum shows the same 31 files as corrupted +- df shows: sda1 has 95271336 1k-blocks, of which 88840860 are used, 1544820 available, 99% used. The numbers don't add up. Either file-blocks are lost in lost-clusters or the ext4-filesystem has a large journal or the file-system-metadata is too large, or the ext4-filesystem has large cluster-size which results in inefficient space usage. +- An ```unmount /dev/sda1 ; fsck -y /dev/sda1 ; mount -t ext4 /dev/sda1 /mnt/a``` did not find any lost clusters. + +The reason I don't think this is a kernel bug, is because the raw-file as virtual-disk-1 doesn't show this issue. Also, it happens regardless of whether sgdata is on ntfs-3g or ntfs3-paragon. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/815 b/gitlab/issues_text/target_missing/host_missing/accel_missing/815 new file mode 100644 index 000000000..1d85c0335 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/815 @@ -0,0 +1 @@ +Using spdk Vhost to accelerate QEMU, which QEMU version is the most appropriate？ diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/816 b/gitlab/issues_text/target_missing/host_missing/accel_missing/816 new file mode 100644 index 000000000..4b00a017f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/816 @@ -0,0 +1,47 @@ +Some errors were encountered while compiling QEMU source code +Description of problem: +When I try to download the source code from gitlab and compile it, the output is as follows: + +``` +FAILED: subprojects/libvhost-user/libvhost-user.a.p/libvhost-user.c.o +clang -m64 -mcx16 -Isubprojects/libvhost-user/libvhost-user.a.p -Isubprojects/libvhost-user -I../subprojects/libvhost-user -fcolor-diagnostics -Wall -Winvalid-pch -Werror -std=gnu11 -O2 -g -fsanitize=fuzzer-no-link -fsanitize=undefined -fsanitize=address -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fno-common -fwrapv -Wold-style-definition -Wtype-limits -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body -Wnested-externs -Wendif-labels -Wexpansion-to-defined -Wno-initializer-overrides -Wno-missing-include-dirs -Wno-shift-negative-value -Wno-string-plus-int -Wno-typedef-redefinition -Wno-tautological-type-limit-compare -fstack-protector-strong -fprofile-instr-generate -fcoverage-mapping -fPIE -pthread -D_GNU_SOURCE -MD -MQ subprojects/libvhost-user/libvhost-user.a.p/libvhost-user.c.o -MF subprojects/libvhost-user/libvhost-user.a.p/libvhost-user.c.o.d -o subprojects/libvhost-user/libvhost-user.a.p/libvhost-user.c.o -c ../subprojects/libvhost-user/libvhost-user.c +In file included from ../subprojects/libvhost-user/libvhost-user.c:43: +../subprojects/libvhost-user/include/atomic.h:1:1: error: expected identifier or '(' +../../../include/qemu/atomic.h +^ +In file included from ../subprojects/libvhost-user/libvhost-user.c:45: +../subprojects/libvhost-user/libvhost-user.h:23:10: fatal error: 'standard-headers/linux/virtio_ring.h' file not found +#include "standard-headers/linux/virtio_ring.h" + ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +2 errors generated. +[69/1511] Compiling C object subprojects/libvhost-user/libvhost-user-glib.a.p/libvhost-user-glib.c.o +FAILED: subprojects/libvhost-user/libvhost-user-glib.a.p/libvhost-user-glib.c.o +clang -m64 -mcx16 -Isubprojects/libvhost-user/libvhost-user-glib.a.p -Isubprojects/libvhost-user -I../subprojects/libvhost-user -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -fcolor-diagnostics -Wall -Winvalid-pch -Werror -std=gnu11 -O2 -g -fsanitize=fuzzer-no-link -fsanitize=undefined -fsanitize=address -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fno-common -fwrapv -Wold-style-definition -Wtype-limits -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body -Wnested-externs -Wendif-labels -Wexpansion-to-defined -Wno-initializer-overrides -Wno-missing-include-dirs -Wno-shift-negative-value -Wno-string-plus-int -Wno-typedef-redefinition -Wno-tautological-type-limit-compare -fstack-protector-strong -fprofile-instr-generate -fcoverage-mapping -fPIE -pthread -Wno-unused-function -MD -MQ subprojects/libvhost-user/libvhost-user-glib.a.p/libvhost-user-glib.c.o -MF subprojects/libvhost-user/libvhost-user-glib.a.p/libvhost-user-glib.c.o.d -o subprojects/libvhost-user/libvhost-user-glib.a.p/libvhost-user-glib.c.o -c ../subprojects/libvhost-user/libvhost-user-glib.c +In file included from ../subprojects/libvhost-user/libvhost-user-glib.c:15: +In file included from ../subprojects/libvhost-user/libvhost-user-glib.h:19: +../subprojects/libvhost-user/libvhost-user.h:23:10: fatal error: 'standard-headers/linux/virtio_ring.h' file not found +#include "standard-headers/linux/virtio_ring.h" + ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +1 error generated. +[70/1511] Generating trace-hw_alpha.h with a custom command +[71/1511] Generating hmp-commands-info.h with a custom command (wrapped by meson to capture output) +[72/1511] Generating qemu-img-cmds.h with a custom command (wrapped by meson to capture output) +[73/1511] Generating hmp-commands.h with a custom command (wrapped by meson to capture output) +[74/1511] Generating qemu-options.def with a custom command (wrapped by meson to capture output) +[75/1511] Compiling C object libslirp.a.p/slirp_src_tcp_input.c.o +[76/1511] Compiling C object libcapstone.a.p/capstone_arch_SystemZ_SystemZDisassembler.c.o +[77/1511] Generating qemu-version.h with a custom command (wrapped by meson to capture output) +[78/1511] Compiling C object libcapstone.a.p/capstone_arch_AArch64_AArch64Disassembler.c.o +[79/1511] Compiling C object libcapstone.a.p/capstone_arch_ARM_ARMInstPrinter.c.o +[80/1511] Compiling C object libcapstone.a.p/capstone_arch_ARM_ARMDisassembler.c.o +[81/1511] Compiling C object libcapstone.a.p/capstone_arch_AArch64_AArch64InstPrinter.c.o +ninja: build stopped: subcommand failed. +Makefile:163: recipe for target 'run-ninja' failed +make: *** [run-ninja] Error 1 +``` + +I looked for the missing file standard-headers/linux/virtio_ring.h and found that the file existed. +Steps to reproduce: +1. ``git clone https://gitlab.com/qemu-project/qemu`` +2. ``CC=clang CXX=clang++ ../configure --enable-fuzzing --enable-sanitizers`` +3. ``make qemu-fuzz-i386`` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/817 b/gitlab/issues_text/target_missing/host_missing/accel_missing/817 new file mode 100644 index 000000000..88c413a23 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/817 @@ -0,0 +1 @@ +linux-user: waitid leaves target siginfo uninitialized when info.si_pid is zero diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/818 b/gitlab/issues_text/target_missing/host_missing/accel_missing/818 new file mode 100644 index 000000000..ab7cc4371 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/818 @@ -0,0 +1,5 @@ +qemu with invalid arg will cause monitor error +Steps to reproduce: +``` +qemu-system-ppc.exe -m 1024M -monitor +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/819 b/gitlab/issues_text/target_missing/host_missing/accel_missing/819 new file mode 100644 index 000000000..9562c7cf8 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/819 @@ -0,0 +1,75 @@ +watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [swapper/1:0] +Description of problem: +During virtual disk live move/migration, VMs get severe stuttering and even cpu soft lockups, as described here: + +https://bugzilla.kernel.org/show_bug.cgi?id=199727 + +This also happens on some of our virtual machines when i/o load inside VM is high or workload is fsync centric. + +i'm searching for a solution to mitigate this problem, i.e. i can live with the stuttering/delays of several seconds, but getting cpu soft lockups of 22s or higher is inacceptable. + +i have searched the web for a long long time now, but did not find a solution , nor did i find a way on how to troubleshoot this more in depth to find the real root cause. + +if this issue report will not getting accepted because of "non native qemu" (i.e. proxmox platform) , please tell me which qemu/distro i can/should use instead (which has easy usable live migration feature) to try reproducing the problem. +Steps to reproduce: +1. do a live migration of one or more virtual machine disks +2. watch "ioping -WWWYy test.dat" inside VM (being moved) for disk latency +3. you disk latency is heavily varying , from time to time it goes up to vaues of tens seconds, even leading to kernel messages like " kernel:[ 2155.520846] watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [swapper/1:0]" + +``` +4 KiB >>> test.dat (ext4 /dev/sda1): request=55 time=1.07 s +4 KiB >>> test.dat (ext4 /dev/sda1): request=56 time=1.24 s +4 KiB >>> test.dat (ext4 /dev/sda1): request=57 time=567.4 ms (fast) +4 KiB >>> test.dat (ext4 /dev/sda1): request=58 time=779.0 ms (fast) +4 KiB >>> test.dat (ext4 /dev/sda1): request=59 time=589.0 ms (fast) +4 KiB >>> test.dat (ext4 /dev/sda1): request=60 time=1.57 s +4 KiB >>> test.dat (ext4 /dev/sda1): request=61 time=847.7 ms (fast) +4 KiB >>> test.dat (ext4 /dev/sda1): request=62 time=933.0 ms +4 KiB >>> test.dat (ext4 /dev/sda1): request=63 time=891.4 ms (fast) +4 KiB >>> test.dat (ext4 /dev/sda1): request=64 time=820.8 ms (fast) +4 KiB >>> test.dat (ext4 /dev/sda1): request=65 time=1.02 s +4 KiB >>> test.dat (ext4 /dev/sda1): request=66 time=2.44 s +4 KiB >>> test.dat (ext4 /dev/sda1): request=67 time=620.7 ms (fast) +4 KiB >>> test.dat (ext4 /dev/sda1): request=68 time=1.03 s +4 KiB >>> test.dat (ext4 /dev/sda1): request=69 time=1.24 s +4 KiB >>> test.dat (ext4 /dev/sda1): request=70 time=1.42 s +4 KiB >>> test.dat (ext4 /dev/sda1): request=71 time=1.36 s +4 KiB >>> test.dat (ext4 /dev/sda1): request=72 time=1.41 s +4 KiB >>> test.dat (ext4 /dev/sda1): request=73 time=1.33 s +4 KiB >>> test.dat (ext4 /dev/sda1): request=74 time=2.36 s +4 KiB >>> test.dat (ext4 /dev/sda1): request=75 time=1.46 s +4 KiB >>> test.dat (ext4 /dev/sda1): request=76 time=1.45 s +4 KiB >>> test.dat (ext4 /dev/sda1): request=77 time=1.28 s +4 KiB >>> test.dat (ext4 /dev/sda1): request=78 time=1.41 s +4 KiB >>> test.dat (ext4 /dev/sda1): request=79 time=2.33 s +4 KiB >>> test.dat (ext4 /dev/sda1): request=80 time=1.39 s +4 KiB >>> test.dat (ext4 /dev/sda1): request=81 time=1.35 s +4 KiB >>> test.dat (ext4 /dev/sda1): request=82 time=1.54 s +4 KiB >>> test.dat (ext4 /dev/sda1): request=83 time=1.52 s +4 KiB >>> test.dat (ext4 /dev/sda1): request=84 time=1.50 s +4 KiB >>> test.dat (ext4 /dev/sda1): request=85 time=2.00 s +4 KiB >>> test.dat (ext4 /dev/sda1): request=86 time=1.47 s +4 KiB >>> test.dat (ext4 /dev/sda1): request=87 time=1.26 s +4 KiB >>> test.dat (ext4 /dev/sda1): request=88 time=1.29 s +4 KiB >>> test.dat (ext4 /dev/sda1): request=89 time=2.05 s +4 KiB >>> test.dat (ext4 /dev/sda1): request=90 time=1.44 s +4 KiB >>> test.dat (ext4 /dev/sda1): request=91 time=1.43 s +4 KiB >>> test.dat (ext4 /dev/sda1): request=92 time=1.72 s +4 KiB >>> test.dat (ext4 /dev/sda1): request=93 time=1.77 s +4 KiB >>> test.dat (ext4 /dev/sda1): request=94 time=2.56 s + +Message from syslogd@iotest2 at Jan 14 14:51:12 ... + kernel:[ 2155.520846] watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [swapper/1:0] +4 KiB >>> test.dat (ext4 /dev/sda1): request=95 time=22.5 s (slow) +4 KiB >>> test.dat (ext4 /dev/sda1): request=96 time=3.56 s +4 KiB >>> test.dat (ext4 /dev/sda1): request=97 time=1.52 s (fast) +4 KiB >>> test.dat (ext4 /dev/sda1): request=98 time=1.69 s +4 KiB >>> test.dat (ext4 /dev/sda1): request=99 time=1.90 s +4 KiB >>> test.dat (ext4 /dev/sda1): request=100 time=1.15 s (fast) +4 KiB >>> test.dat (ext4 /dev/sda1): request=101 time=890.0 ms (fast) +4 KiB >>> test.dat (ext4 /dev/sda1): request=102 time=959.6 ms (fast) +4 KiB >>> test.dat (ext4 /dev/sda1): request=103 time=926.5 ms (fast) +4 KiB >>> test.dat (ext4 /dev/sda1): request=104 time=791.5 ms (fast) +4 KiB >>> test.dat (ext4 /dev/sda1): request=105 time=577.8 ms (fast) +4 KiB >>> test.dat (ext4 /dev/sda1): request=106 time=867.7 ms (fast) +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/82 b/gitlab/issues_text/target_missing/host_missing/accel_missing/82 new file mode 100644 index 000000000..c37fcb5c9 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/82 @@ -0,0 +1 @@ +[Feature request] acceptance test class to run user-mode binaries diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/820 b/gitlab/issues_text/target_missing/host_missing/accel_missing/820 new file mode 100644 index 000000000..bd3b36e5a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/820 @@ -0,0 +1,13 @@ +Hang During Initramfs +Description of problem: +[Hang During Initramfs](https://wiki.archlinux.org/title/QEMU#Hang_during_VM_initramfs) +Is this still not fixed? I hang at startup. Previously I tried WIN11 and it booted fine. +Steps to reproduce: +1. Download Windows10 ISO +2. qemu-img create -f raw Windows10 15G +3. qemu-system-x86_64 -cdrom Win10.iso -boot order=d -drive file=Windows10,format=raw -m 4G +Additional information: + + + +`-enable-kvm` works but i removed it to slow down a bit to see what is going on. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/821 b/gitlab/issues_text/target_missing/host_missing/accel_missing/821 new file mode 100644 index 000000000..dde4c6f85 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/821 @@ -0,0 +1 @@ +[SOLVED] ReactOS video problems... diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/823 b/gitlab/issues_text/target_missing/host_missing/accel_missing/823 new file mode 100644 index 000000000..f96528f76 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/823 @@ -0,0 +1,21 @@ +rcutorture: ../tests/unit/rcutorture.c:321: rcu_update_stress_test: Assertion `p != cp' failed. +Description of problem: +qemu rcutorture tests are failing when building qemu for Rawhide. See the scratch build I did here and the follow log files: + +https://koji.fedoraproject.org/koji/taskinfo?taskID=81316487 +https://kojipkgs.fedoraproject.org//work/tasks/6509/81316509/build.log +https://kojipkgs.fedoraproject.org//work/tasks/6508/81316508/build.log +https://kojipkgs.fedoraproject.org//work/tasks/6510/81316510/build.log + +The full error is: + +``` +MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} G_TEST_SRCDIR=/builddir/build/BUILD/qemu-6.2.0/tests/unit G_TEST_BUILDDIR=/builddir/build/BUILD/qemu-6.2.0/qemu_kvm_build/tests/unit tests/unit/rcutorture --tap -k +ERROR rcutorture - too few tests run (expected 2, got 0) +rcutorture: ../tests/unit/rcutorture.c:321: rcu_update_stress_test: Assertion `p != cp' failed. +make: *** [Makefile.mtest:1208: run-test-149] Error 1 +``` +Steps to reproduce: +1. Compile qemu and run the test suite. +Additional information: +The only significant recent change since it was built successfully is adoption of GCC 12. Could it be a change in compiler that causes this? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/825 b/gitlab/issues_text/target_missing/host_missing/accel_missing/825 new file mode 100644 index 000000000..d2172a801 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/825 @@ -0,0 +1,38 @@ +compilation error - "VIRTIO_F_VERSION" +Description of problem: +Encountered problem while "make" + +.... +`[65/2464] Compiling C object subprojects/libvhost-user/libvhost-user.a.p/libvhost-user.c.o +FAILED: subprojects/libvhost-user/libvhost-user.a.p/libvhost-user.c.o +cc -m64 -mcx16 -Isubprojects/libvhost-user/libvhost-user.a.p -Isubprojects/libvhost-user -I../subprojects/libvhost-user -fdiagnostics-color=auto -Wall -Winvalid-pch -Werror -std=gnu11 -O2 -g -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fno-common -fwrapv -Wold-style-declaration -Wold-style-definition -Wtype-limits -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body -Wnested-externs -Wendif-labels -Wexpansion-to-defined -Wimplicit-fallthrough=2 -Wno-missing-include-dirs -Wno-shift-negative-value -Wno-psabi -fstack-protector-strong -fPIE -pthread -D_GNU_SOURCE -MD -MQ subprojects/libvhost-user/libvhost-user.a.p/libvhost-user.c.o -MF subprojects/libvhost-user/libvhost-user.a.p/libvhost-user.c.o.d -o subprojects/libvhost-user/libvhost-user.a.p/libvhost-user.c.o -c ../subprojects/libvhost-user/libvhost-user.c +../subprojects/libvhost-user/libvhost-user.c: In function 'vu_get_features_exec': +../subprojects/libvhost-user/libvhost-user.c:508:17: error: 'VIRTIO_F_VERSION_1' undeclared (first use in this function); did you mean 'INFLIGHT_VERSION'? + 1ULL << VIRTIO_F_VERSION_1 | + ^~~~~~~~~~~~~~~~~~ + INFLIGHT_VERSION +../subprojects/libvhost-user/libvhost-user.c:508:17: note: each undeclared identifier is reported only once for each function it appears in +../subprojects/libvhost-user/libvhost-user.c: In function 'vu_set_features_exec': +../subprojects/libvhost-user/libvhost-user.c:542:30: error: 'VIRTIO_F_VERSION_1' undeclared (first use in this function); did you mean 'INFLIGHT_VERSION'? + if (!vu_has_feature(dev, VIRTIO_F_VERSION_1)) { + ^~~~~~~~~~~~~~~~~~ + INFLIGHT_VERSION +../subprojects/libvhost-user/libvhost-user.c: In function 'generate_faults': +../subprojects/libvhost-user/libvhost-user.c:612:13: error: unused variable 'ret' [-Werror=unused-variable] + int ret; + ^~~ +../subprojects/libvhost-user/libvhost-user.c:611:22: error: unused variable 'dev_region' [-Werror=unused-variable] + VuDevRegion *dev_region = &dev->regions[i]; + ^~~~~~~~~~ +cc1: all warnings being treated as errors +ninja: build stopped: subcommand failed. +make[1]: *** [Makefile:163: run-ninja] Error 1 +make[1]: Leaving directory '/users/oneuser/qemu/qemu/build' +make: *** [GNUmakefile:11: all] Error 2 +` +Steps to reproduce: +1. ./configure --prefix=/users/oneuser/qemu/myqemu-1 --enable-kvm --target-list=x86_64-softmmu +2. make +3. +Additional information: +Please let me know if more info is needed. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/827 b/gitlab/issues_text/target_missing/host_missing/accel_missing/827 new file mode 100644 index 000000000..b94355c12 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/827 @@ -0,0 +1 @@ +Stack-overflow through virtio_blk_get_request diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/828 b/gitlab/issues_text/target_missing/host_missing/accel_missing/828 new file mode 100644 index 000000000..09f99ffa0 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/828 @@ -0,0 +1,11 @@ +using qemu-system-x86_64 to start multiple windows 10 guests concurrently , the mac address of the guests is incorrect +Description of problem: +I plan to run multiple windows 10 guests concurrently, I choose NAT network and specify a unique MAC addr for each guest. and I choose dnsmasq as a dhcp server. but I found that all guests MAC addresses are the same as the guest started first. +This situation also occurs in windows 8. But the strange thing is that this never happened to windows7 guests. +I'm Chinese and my English is pool, please forgive my bad expressions. +Steps to reproduce: +1.make a windows 10 image +2.qemu-system-x86_64 command assign unique MAC addr +3. python multiprocess lib running command above +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/829 b/gitlab/issues_text/target_missing/host_missing/accel_missing/829 new file mode 100644 index 000000000..e9d023e43 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/829 @@ -0,0 +1,14 @@ +user space emulation: openat() seems to defeat sysroot path translation +Description of problem: +It appears that the user space emulation code is doing some path manipulation of some syscalls to sometimes prefix them with the sysroot. This seems to be interacting badly sometimes with certain usage patterns. This was noticed because a test suite of various libc calls was failing under `qemu-arm`, and a `strace` of the qemu-arm process revealed that the translated paths were being inconsistently applied. + +In particular, the sequence which fails is: +* create a file in `/tmp/`. +* open `/tmp` itself. This succeeds, but `strace` reveals that it actually opened `SYSROOT/tmp/`. +* `openat(tmpfd, tmpfile_name)` then fails, as the fd provided to openat is actually inside the sysroot, not at `/tmp` as expected. +Steps to reproduce: +1. Get toolchain https://toolchains.bootlin.com/downloads/releases/toolchains/armv7-eabihf/tarballs/armv7-eabihf--uclibc--bleeding-edge-2021.11-1.tar.bz2 +2. Compile attached test program [test_openat.c](/uploads/69eb997256ff29d2178be85531c6b3c6/test_openat.c) +3. Try to run under `qemu-arm`. + +This code passes in non-emulated situations, but fails under user-space emulation. Presumably it would also pass under full system emulation. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/830 b/gitlab/issues_text/target_missing/host_missing/accel_missing/830 new file mode 100644 index 000000000..dd8b67af6 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/830 @@ -0,0 +1 @@ +QEMU aarch64 support for Windows TPM driver (TIS, CRB interfaces) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/832 b/gitlab/issues_text/target_missing/host_missing/accel_missing/832 new file mode 100644 index 000000000..aef0c12ae --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/832 @@ -0,0 +1,13 @@ +error "# mkdir('/..../qtest-9p-local-M33XsI') failed: File exists" on every run of 'qos-test' +Description of problem: +``` +$ ./build//tests/qtest/qos-test -h +# mkdir('/home/berrange/src/virt/qemu/qtest-9p-local-qThj5y') failed: File exists +Usage: + ./build//tests/qtest/qos-test [OPTION...] +...snip... +``` + +Notice the error message from 'mkdir()' whic appears every time you run this program. +Steps to reproduce: +1. Run qos-test diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/833 b/gitlab/issues_text/target_missing/host_missing/accel_missing/833 new file mode 100644 index 000000000..4d46108c3 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/833 @@ -0,0 +1,42 @@ +linux-user: sendmsg fails to send messages without iov +Description of problem: +When run via qemu `sendmsg` fails to send messages which contain a zero length `iov` but _do_ contain ancillary data. This works fine on plain Linux. + +A practical example: the `ell` library relies on this for setting the IV on a kernel crypto (`AF_ALG`) socket: https://git.kernel.org/pub/scm/libs/ell/ell.git/tree/ell/cipher.c#n526 + +A message without data but only ancillary data is used to set the IV. +Steps to reproduce: +See [qemu_ancillary.c](/uploads/84ee20aa3b9178022847d6cd7fcf0048/qemu_ancillary.c) for a self contained testcase which sends two mesages (one with `msg_iovlen=0`, one with `msg_iovlen=1`). + +(Test case is to be considered GPL, as I've copied bits from `ell`) + +Native: +``` +$ strace -esendmsg ./a.out +sendmsg(6, {msg_name=NULL, msg_namelen=0, msg_iov=NULL, msg_iovlen=0, msg_control=[{cmsg_len=36, cmsg_level=SOL_ALG, cmsg_type=0x2}], msg_controllen=40, msg_flags=0}, 0) = 0 +sendmsg(6, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0", iov_len=16}], msg_iovlen=1, msg_control=[{cmsg_len=36, cmsg_level=SOL_ALG, cmsg_type=0x2}], msg_controllen=40, msg_flags=0}, 0) = 16 ++++ exited with 0 +++ +``` + + +Qemu (observe missing sendmsg call): +``` +$ strace -esendmsg ~/debug/qemu/build/qemu-x86_64 ./a.out +sendmsg(6, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0", iov_len=16}], msg_iovlen=1, msg_control=[{cmsg_len=36, cmsg_level=SOL_ALG, cmsg_type=0x2}], msg_controllen=40, msg_flags=0}, 0) = 16 ++++ exited with 0 +++ +``` + +For a practical reproducer: + +1. Compile and run `ell`'s `test-cipher` test case: + +``` +$ ~/debug/qemu/build/qemu-x86_64 ./unit/test-cipher +TEST: unsupported +TEST: aes +TEST: aes_ctr +test-cipher: unit/test-cipher.c:102: test_aes_ctr: Assertion `!r' failed. +Aborted (core dumped) +``` + +A strace will look similar. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/834 b/gitlab/issues_text/target_missing/host_missing/accel_missing/834 new file mode 100644 index 000000000..a6057d041 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/834 @@ -0,0 +1,59 @@ +linux-user: fails to deliver signals raised during pselect +Description of problem: +When run via qemu a program which blocks signals but unmasks them during `pselect` does not catch these signals when returning from `pselect`. + +Used as reference on expected behavior: [The new pselect() system call](https://lwn.net/Articles/176911/) +Steps to reproduce: +A minimal test case below mimics behavior as encountered in the test suite of `p11-kit` ([link](https://github.com/p11-glue/p11-kit)) (which attempts to catch `SIGTERM` in a similar way and results in lingering processes after running the test suite). + +```C +#include <stdio.h> +#include <unistd.h> +#include <signal.h> +#include <sys/select.h> + +static void handler(int sig) +{ + puts("SIGNAL"); +} + +int main(int argc, char *argv[]) +{ + struct sigaction sa; + + fd_set rfds; + sigset_t emptyset, blockset; + + sigemptyset (&blockset); + sigemptyset (&emptyset); + sigaddset (&blockset, SIGUSR1); + + sa.sa_handler = handler; + sigemptyset(&sa.sa_mask); + sa.sa_flags = 0; + sigaction(SIGUSR1, &sa, NULL); + + sigprocmask (SIG_BLOCK, &blockset, NULL); + + FD_ZERO(&rfds); + + while(1) { + pselect(0, &rfds, NULL, NULL, NULL, &emptyset); + } + + return 0; +} +``` + +Running this without qemu should print _SIGNAL_ when sent `SIGUSR1`: + +``` +$ ./a.out & +[1] 1683587 +$ kill -USR1 %1 +$ SIGNAL +``` + +When run with `qemu-x86_64` however, it does not (also qemu's `-strace` confirms the signal isn't received whereas a strace of qemu shows it's in fact delivered). + +The pselect call itself _is_ interrupted, but the signal goes missing. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/835 b/gitlab/issues_text/target_missing/host_missing/accel_missing/835 new file mode 100644 index 000000000..b8bc502be --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/835 @@ -0,0 +1,9 @@ +SDL display does not handle ps2 relative packets +Description of problem: +The main problem: while tracing relative events input_event_rel all mouse events are positive and seems to be the absolute x and y mouse position. When that happens ps2 sends a +x -y of a full 127 count. +Steps to reproduce: +1. Trace input_event_rel +2. Observe that when moving the mouse the trace always shows positive values, that doesn't depend on what direction you move the mouse +3. Observe that the xrel and yrel is more like absolute positions +Additional information: +I noticed searching on sdl2 docs and some issues related to SDL2 mouse events that when you do not specify SDL_HINT_MOUSE_RELATIVE_MODE_WARP weird things happens, i tried adding SDL_SetHint(SDL_HINT_MOUSE_RELATIVE_MODE_WARP, "1"); at the end of the sdl2 init function and the mouse events started to show normal values. I'm not sure if that's the correct way to solve the bug, but it seems to be. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/839 b/gitlab/issues_text/target_missing/host_missing/accel_missing/839 new file mode 100644 index 000000000..34bc7a50a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/839 @@ -0,0 +1,50 @@ +qxl in COLO secondary node cause QEMU to segmentation fault +Description of problem: +After COLO checkpoint, the Secondary VM's qemu received segmentation fault while releasing qxl resources in interface_release_resource() routine. +i have used gdb and qemu trace to debug Secondary VM's qemu. the object 'qxl->last_release' is null and object 'ring->items[prod].el' != 0, it leads to null pointer dereference. +During COLO checkpoint,the Secondary VM's qemu has loaded Primary VM's qxl states,so i think it not need to release qxl resources. +Steps to reproduce: +1.Startup Primary VM and Secondary VM of COLO mode, and gdb to Secondary VM's qemu. +2.Connect to Primary VM's spice server. +3.Secondary VM's qemu will receiveing segmentation fault. +Additional information: +gdb to Secondary VM's qemu: + ``` +Program received signal SIGSEGV, Segmentation fault. +[Switching to Thread 0x7ff9e3bff700 (LWP 44703)] +0x0000555555b2e8d6 in interface_release_resource (sin=0x555557d7c8a8, ext=...) at ../hw/display/qxl.c:783 +783 qxl->last_release->next = ext.info->id; +(gdb) bt +#0 0x0000555555b2e8d6 in interface_release_resource (sin=0x555557d7c8a8, ext=...) at ../hw/display/qxl.c:783 +#1 0x00007fffd7751dd1 in red_drawable_unref () at /lib64/libspice-server.so.1 +#2 0x00007fffd771eabe in drawable_unref () at /lib64/libspice-server.so.1 +#3 0x00007fffd77206a7 in draw_until () at /lib64/libspice-server.so.1 +#4 0x00007fffd771f7cd in display_channel_draw () at /lib64/libspice-server.so.1 +#5 0x00007fffd7721b51 in display_channel_process_draw () at /lib64/libspice-server.so.1 +#6 0x00007fffd7752142 in red_process_display () at /lib64/libspice-server.so.1 +#7 0x00007fffd77521fb in worker_source_dispatch () at /lib64/libspice-server.so.1 +#8 0x00007fffd6c2f049 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 +#9 0x00007fffd6c2f3a8 in g_main_context_iterate.isra.19 () at /lib64/libglib-2.0.so.0 +#10 0x00007fffd6c2f67a in g_main_loop_run () at /lib64/libglib-2.0.so.0 +#11 0x00007fffd775166a in red_worker_main () at /lib64/libspice-server.so.1 +#12 0x00007fffd5658dd5 in start_thread () at /lib64/libpthread.so.0 +#13 0x00007fffd538202d in clone () at /lib64/libc.so.6 +(gdb) frame 0 +#0 0x0000555555b2e8d6 in interface_release_resource (sin=0x555557d7c8a8, ext=...) at ../hw/display/qxl.c:783 +783 qxl->last_release->next = ext.info->id; +(gdb) print qxl->last_release +$1 = (QXLReleaseInfo *) 0x0 + ``` + +qemu trace log: + ``` +44840@1643012769.363844:colo_send_message Send 'checkpoint-reply' message +44840@1643012773.579053:colo_receive_message Receive 'vmstate-send' message +44840@1643012773.978838:colo_receive_message Receive 'vmstate-size' message +44840@1643012773.979041:colo_send_message Send 'vmstate-received' message +44840@1643012774.180598:qxl_pre_load 0 +44703@1643012774.180660:qxl_ring_res_put 0 #res=20 +44840@1643012774.182627:qxl_post_load 0 native +44840@1643012774.197993:colo_vm_state_change Change 'stop' => 'run' +44840@1643012774.198030:colo_send_message Send 'vmstate-loaded' message + ``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/84 b/gitlab/issues_text/target_missing/host_missing/accel_missing/84 new file mode 100644 index 000000000..23cd25e06 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/84 @@ -0,0 +1 @@ +Machine shut off after tons of lsi_scsi: error: MSG IN data too long diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/841 b/gitlab/issues_text/target_missing/host_missing/accel_missing/841 new file mode 100644 index 000000000..bedc6841d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/841 @@ -0,0 +1,78 @@ +SIGSEGV in memcpy in v9fs_co_readdir_many +Description of problem: +When running btrfs tests in vm (using `virtme`-like setup with 9pfs) occasionally qemu crashes with (`coredumpctl info` output): +``` +... +Message: Process 1764494 (qemu-system-x86) of user 502 dumped core. +Stack trace of thread 1764817: + #0 0x00005555559ebeed v9fs_co_readdir_many (/usr/bin/qemu-system-x86_64 + 0x497eed) + #1 0x00005555559ec2e9 v9fs_readdir (/usr/bin/qemu-system-x86_64 + 0x4982e9) + #2 0x0000555555eb7983 coroutine_trampoline (/usr/bin/qemu-system-x86_64 + 0x963983) + #3 0x00007ffff73e0be0 n/a (n/a + 0x0) +``` +Additional information: +coredumpctl debug: +``` +Failed to read a valid object file image from memory. +Core was generated by `qemu-system-x86_64 -enable-kvm -m 40270M -smp cores=20 -nodefaults -nographic -'. +Program terminated with signal SIGSEGV, Segmentation fault. +#0 0x00005555559ebeed in memcpy (__len=<optimized out>, __src=<optimized out>, __dest=<optimized out>, __dest=<optimized out>, __src=<optimized out>, + __len=<optimized out>) at /usr/include/bits/string_fortified.h:29 +29 return __builtin___memcpy_chk (__dest, __src, __len, +[Current thread is 1 (LWP 1764817)] +(gdb) list ../hw/9pfs/codir.c:147 +142 *entries = e = g_malloc0(sizeof(V9fsDirEnt)); +143 } else { +144 e = e->next = g_malloc0(sizeof(V9fsDirEnt)); +145 } +146 e->dent = g_malloc0(sizeof(struct dirent)); +147 memcpy(e->dent, dent, sizeof(struct dirent)); +148 +149 /* perform a full stat() for directory entry if requested by caller */ +150 if (dostat) { +151 err = s->ops->name_to_path( +(gdb) bt +#0 0x00005555559ebeed in memcpy (__len=<optimized out>, __src=<optimized out>, __dest=<optimized out>, __dest=<optimized out>, __src=<optimized out>, + __len=<optimized out>) at /usr/include/bits/string_fortified.h:29 +#1 do_readdir_many (dostat=<optimized out>, maxsize=<optimized out>, offset=<optimized out>, entries=<optimized out>, fidp=<optimized out>, + pdu=0x555557353500) at ../hw/9pfs/codir.c:147 +#2 v9fs_co_readdir_many (pdu=pdu@entry=0x555557353500, fidp=fidp@entry=0x555556cdd280, entries=entries@entry=0x7ff5bf7f7f58, offset=<optimized out>, + maxsize=<optimized out>, dostat=<optimized out>) at ../hw/9pfs/codir.c:226 +#3 0x00005555559ec2e9 in v9fs_do_readdir (max_count=<optimized out>, offset=<optimized out>, fidp=0x555556cdd280, pdu=0x555557353500) at ../hw/9pfs/9p.c:2430 +#4 v9fs_readdir (opaque=0x555557353500) at ../hw/9pfs/9p.c:2543 +#5 0x0000555555eb7983 in coroutine_trampoline (i0=<optimized out>, i1=<optimized out>) at ../util/coroutine-ucontext.c:173 +#6 0x00007ffff73e0be0 in ?? () +#7 0x00007fffffffd480 in ?? () +#8 0x0000000000000000 in ?? () +(gdb) x/11i 0x00005555559ebeed - 27 + 0x5555559ebed2 <v9fs_co_readdir_many+530>: call 0x555555928480 <g_malloc0@plt> + 0x5555559ebed7 <v9fs_co_readdir_many+535>: mov %rbp,%rsi + 0x5555559ebeda <v9fs_co_readdir_many+538>: mov %rax,(%r12) + 0x5555559ebede <v9fs_co_readdir_many+542>: mov 0x0(%rbp),%rdx + 0x5555559ebee2 <v9fs_co_readdir_many+546>: lea 0x8(%rax),%rdi + 0x5555559ebee6 <v9fs_co_readdir_many+550>: and $0xfffffffffffffff8,%rdi + 0x5555559ebeea <v9fs_co_readdir_many+554>: mov %rdx,(%rax) +=> 0x5555559ebeed <v9fs_co_readdir_many+557>: mov 0x110(%rbp),%rdx + 0x5555559ebef4 <v9fs_co_readdir_many+564>: mov %rdx,0x110(%rax) + 0x5555559ebefb <v9fs_co_readdir_many+571>: sub %rdi,%rax + 0x5555559ebefe <v9fs_co_readdir_many+574>: sub %rax,%rsi +(gdb) i r rdx rax rip +rdx 0x29287d 2697341 +rax 0x7ff4bc12ccf0 140689104096496 +rip 0x5555559ebeed 0x5555559ebeed <v9fs_co_readdir_many+557> +(gdb) x/11x 0x7ff4bc12ccf0 +0x7ff4bc12ccf0: 0x0029287d 0x00000000 0x00000000 0x00000000 +0x7ff4bc12cd00: 0x00000000 0x00000000 0x00000000 0x00000000 +0x7ff4bc12cd10: 0x00000000 0x00000000 0x00000000 +(gdb) frame 1 +#1 do_readdir_many (dostat=<optimized out>, maxsize=<optimized out>, offset=<optimized out>, entries=<optimized out>, fidp=<optimized out>, + pdu=0x555557353500) at ../hw/9pfs/codir.c:147 +147 memcpy(e->dent, dent, sizeof(struct dirent)); +(gdb) p e +$3 = (struct V9fsDirEnt *) 0x7ff4bc12caa0 +(gdb) p e->dent +$4 = (struct dirent *) 0x7ff4bc12ccf0 +(gdb) p dent +$5 = (struct dirent *) 0x7ff4ec04cef0 + +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/845 b/gitlab/issues_text/target_missing/host_missing/accel_missing/845 new file mode 100644 index 000000000..05af39fc8 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/845 @@ -0,0 +1,59 @@ +Heap-use-after-free in remote_object_finalize +Description of problem: +While I was working with `QIOChannel` in my downstream QEMU fork, I looked at `hw/remote/remote-obj.c` as a usage example. + +I did the same thing to `remote_object_finalize` function in order to free the QIOChannel when the connection closed: + +```c + if (o->ioc) { + qio_channel_shutdown(o->ioc, QIO_CHANNEL_SHUTDOWN_BOTH, NULL); + qio_channel_close(o->ioc, NULL); + } + + object_unref(OBJECT(o->ioc)); +``` + +After the connection is closed for a while, my program SIGSEGV: + +``` +Thread 2 Crashed: +0 qemu-system-aarch64 0x000000010164513c qemu_coroutine_get_aio_context + 12 (qemu-coroutine.c:203) +1 qemu-system-aarch64 0x000000010145ad82 qio_channel_restart_read + 50 +2 qemu-system-aarch64 0x0000000101614c8a aio_dispatch_handler + 378 (aio-posix.c:332) +3 qemu-system-aarch64 0x0000000101613fad aio_dispatch_handlers + 125 (aio-posix.c:372) +4 qemu-system-aarch64 0x0000000101613ef3 aio_dispatch + 51 (aio-posix.c:383) +5 qemu-system-aarch64 0x0000000101631e18 aio_ctx_dispatch + 104 (async.c:307) +6 libglib-2.0.0.dylib 0x000000010284b90c g_main_context_dispatch + 364 +7 qemu-system-aarch64 0x0000000101644728 glib_pollfds_poll + 88 (main-loop.c:233) +8 qemu-system-aarch64 0x0000000101644170 os_host_main_loop_wait + 128 (main-loop.c:256) +9 qemu-system-aarch64 0x000000010164403c main_loop_wait + 188 (main-loop.c:530) +10 qemu-system-aarch64 0x00000001012f3014 qemu_main_loop + 36 (runstate.c:721) +11 qemu-system-aarch64 0x0000000100c25e38 qemu_main + 40 (main.c:51) +12 qemu-system-aarch64 0x0000000100c7b1f4 call_qemu_main + 52 (cocoa.m:1746) +13 qemu-system-aarch64 0x000000010161a459 qemu_thread_start + 185 (qemu-thread-posix.c:521) +14 libsystem_pthread.dylib 0x00007fff6a6e2109 _pthread_start + 148 +15 libsystem_pthread.dylib 0x00007fff6a6ddb8b thread_start + 15 +``` + +So apparently, there is a dangling pointer of the QIOChannel in AIOContext. + +And indeed, that caused by the fact that when the fd read/write is blocked, it sets the fd handlers to the AIO context before yielding the coroutine (https://gitlab.com/qemu-project/qemu/-/blob/master/io/channel.c#L544). + +So after the fd is closed, the AIO still dispatches the fd readable event when the main loop dispatches again, using the dangling QIOChannel pointer (When the fd is reused I think). + +I suggest adding a `qio_channel_detach_aio_context()` call before the channel is shutdown in `remote-obj.c`, or before the fd is closed in `qio_channel_close()` in `io/channel.c` + +```c + + if (o->ioc) { + qio_channel_detach_aio_context(o->ioc); + qio_channel_shutdown(o->ioc, QIO_CHANNEL_SHUTDOWN_BOTH, NULL); + qio_channel_close(o->ioc, NULL); + } + + object_unref(OBJECT(o->ioc)); +``` + +This bug might have slipped through the cracks because `mpqemu_remote_msg_loop_co` issues a shutdown request immediately after an I/O error occured on the QIOChannel. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/846 b/gitlab/issues_text/target_missing/host_missing/accel_missing/846 new file mode 100644 index 000000000..9aa81305a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/846 @@ -0,0 +1 @@ +Why qemu crashes and calling SYS_SECCOMP function diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/848 b/gitlab/issues_text/target_missing/host_missing/accel_missing/848 new file mode 100644 index 000000000..9ad2208a4 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/848 @@ -0,0 +1,48 @@ +`checkinstall` on Devuan Chimaera (equiv to Debian Bullseye) fails with `FileNotFoundError:` +Description of problem: +Configure and compile work without errors, but `checkinstall` fails with following error. + +``` +Installing with make install... + +========================= Installation results =========================== +changing dir to build for make "install"... +make[1]: Entering directory '/root/go/src/github.com/qemu/qemu/build' + GIT ui/keycodemapdb meson tests/fp/berkeley-testfloat-3 tests/fp/berkeley-softfloat-3 dtc capstone slirp +[1/20] Generating qemu-version.h with a meson_exe.py custom command +[1/2] Installing files. +Traceback (most recent call last): + File "/root/go/src/github.com/qemu/qemu/meson/mesonbuild/mesonmain.py", line 140, in run + return options.run_func(options) + File "/root/go/src/github.com/qemu/qemu/meson/mesonbuild/minstall.py", line 544, in run + installer.do_install(datafilename) + File "/root/go/src/github.com/qemu/qemu/meson/mesonbuild/minstall.py", line 362, in do_install + self.install_targets(d) + File "/root/go/src/github.com/qemu/qemu/meson/mesonbuild/minstall.py", line 472, in install_targets + file_copied = self.do_copyfile(fname, outname, makedirs=(d.dirmaker, outdir)) + File "/root/go/src/github.com/qemu/qemu/meson/mesonbuild/minstall.py", line 277, in do_copyfile + shutil.copystat(from_file, to_file) + File "/usr/lib/python3.9/shutil.py", line 375, in copystat + lookup("utime")(dst, ns=(st.st_atime_ns, st.st_mtime_ns), +FileNotFoundError: [Errno 2] No such file or directory +Installing subdir /root/go/src/github.com/qemu/qemu/qga/run to /usr/local/var/run +Installing trace/trace-events-all to /usr/local/share/qemu +FAILED: meson-install +/usr/bin/python3 /root/go/src/github.com/qemu/qemu/meson/meson.py install --no-rebuild +ninja: build stopped: subcommand failed. +make[1]: *** [Makefile:156: run-ninja] Error 1 +make[1]: Leaving directory '/root/go/src/github.com/qemu/qemu/build' +make: *** [GNUmakefile:11: install] Error 2 + +**** Installation failed. Aborting package creation. + +Cleaning up...OK + +Bye. + +``` +Additional information: +- All packages from [requirements](https://wiki.qemu.org/Hosts/Linux#Fedora_Linux_.2F_Debian_GNU_Linux_.2F_Ubuntu_Linux_.2F_Linux_Mint_distributions) installed. +- command `utime` is available from `atfs` package + +I believe error may be related to the `from_file`/`to_file`in: `meson/mesonbuild/minstall.py` line 277. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/850 b/gitlab/issues_text/target_missing/host_missing/accel_missing/850 new file mode 100644 index 000000000..26e94f995 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/850 @@ -0,0 +1,59 @@ +virtio-gpu: bogus descriptor or out of resources +Description of problem: +The guest which I use have 1GB memory, also the guest contains 8GB swap, when I open lot of applications in the guest, the guest kernel starts using swap, after some time, I get this error + +<code> +qemu-system-x86_64: virtio: bogus descriptor or out of resources +</code> + +I tried to see which virtio device causing this issue, it seems this issue is happening in "virtio-gpu", I modified the sources ad added this line to see the device name + +virtio.c:1312: virtio_error(vdev, "virtio: %s: bogus descriptor or out of resources", vdev->name); +Steps to reproduce: +1. create a vm with 8GB swap +2. run that vm with above mentioned commandline (memory = 1MB) +3. open huge applications which eats ram in guest +Additional information: +Seems suddenly condition "if (!memory_access_is_direct(mr, is_write))" [physmem.c:1385] becomes true, this is the stack trace when "if (qatomic_xchg(&bounce.in_use, true)) {" [physmem.c:1386] line gets hit for the first time, + +<code> +#0 address_space_map (as=<optimized out>, addr=addr@entry=45251811299328, plen=plen@entry=0x7fffffff7e30, is_write=is_write@entry=false, attrs=..., attrs@entry=...) at ../qemu-6.2.0/softmmu/physmem.c:3186 +#1 0x0000555555cb8cf4 in dma_memory_map (dir=DMA_DIRECTION_TO_DEVICE, len=<synthetic pointer>, addr=45251811299328, as=<optimized out>) at /home/mohan/Downloads/qemu/src/qemu-6.2.0/include/sysemu/dma.h:202 +#2 virtqueue_map_desc + (vdev=vdev@entry=0x5555579d3bb0, p_num_sg=p_num_sg@entry=0x7fffffff7ed8, addr=addr@entry=0x7fffffff7f70, iov=0x7fffffff9f70, max_num_sg=max_num_sg@entry=1024, is_write=is_write@entry=false, pa=45251811299328, sz=65536) at ../qemu-6.2.0/hw/virtio/virtio.c:1307 +#3 0x0000555555cb8f9e in virtqueue_packed_pop (vq=<optimized out>, sz=<optimized out>) at ../qemu-6.2.0/hw/virtio/virtio.c:1624 +#4 0x00007fffec0b329e in virtio_gpu_gl_handle_ctrl (vdev=<optimized out>, vq=0x7fffdced6010) at ../qemu-6.2.0/hw/display/virtio-gpu-gl.c:77 +#5 0x0000555555f74134 in aio_bh_call (bh=0x555556d02bc0) at ../qemu-6.2.0/util/async.c:141 +#6 aio_bh_poll (ctx=ctx@entry=0x555556958750) at ../qemu-6.2.0/util/async.c:169 +#7 0x0000555555f5f784 in aio_dispatch (ctx=0x555556958750) at ../qemu-6.2.0/util/aio-posix.c:381 +#8 0x0000555555f73d63 in aio_ctx_dispatch (source=<optimized out>, callback=<optimized out>, user_data=<optimized out>) at ../qemu-6.2.0/util/async.c:311 +#9 0x00007ffff787dfd3 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 +#10 0x0000555555f80129 in glib_pollfds_poll () at ../qemu-6.2.0/util/main-loop.c:232 +#11 os_host_main_loop_wait (timeout=0) at ../qemu-6.2.0/util/main-loop.c:255 +#12 main_loop_wait (nonblocking=nonblocking@entry=0) at ../qemu-6.2.0/util/main-loop.c:531 +#13 0x0000555555c48fe5 in qemu_main_loop () at ../qemu-6.2.0/softmmu/runstate.c:726 +#14 0x000055555597b664 in main (argc=<optimized out>, argv=<optimized out>, envp=<optimized out>) at ../qemu-6.2.0/softmmu/main.c:50 +</code> +<br/> +address_space_map() returns valid pointer in the first hit, but it returns NULL on the second hit because qatomic_xchg(bounce.in_use, true) returns true, I think it should suppose to return false. this is the stack trace when it happens for the second time +<br/> +<code> +#0 address_space_map (as=<optimized out>, addr=addr@entry=45251811303424, plen=plen@entry=0x7fffffff7e30, is_write=is_write@entry=false, attrs=..., attrs@entry=...) at ../qemu-6.2.0/softmmu/physmem.c:3186 +#1 0x0000555555cb8cf4 in dma_memory_map (dir=DMA_DIRECTION_TO_DEVICE, len=<synthetic pointer>, addr=45251811303424, as=<optimized out>) at /home/mohan/Downloads/qemu/src/qemu-6.2.0/include/sysemu/dma.h:202 +#2 virtqueue_map_desc + (vdev=vdev@entry=0x5555579d3bb0, p_num_sg=p_num_sg@entry=0x7fffffff7ed8, addr=addr@entry=0x7fffffff7f70, iov=0x7fffffff9f70, max_num_sg=max_num_sg@entry=1024, is_write=is_write@entry=false, pa=45251811303424, sz=61440) at ../qemu-6.2.0/hw/virtio/virtio.c:1307 +#3 0x0000555555cb8f9e in virtqueue_packed_pop (vq=<optimized out>, sz=<optimized out>) at ../qemu-6.2.0/hw/virtio/virtio.c:1624 +#4 0x00007fffec0b329e in virtio_gpu_gl_handle_ctrl (vdev=<optimized out>, vq=0x7fffdced6010) at ../qemu-6.2.0/hw/display/virtio-gpu-gl.c:77 +#5 0x0000555555f74134 in aio_bh_call (bh=0x555556d02bc0) at ../qemu-6.2.0/util/async.c:141 +#6 aio_bh_poll (ctx=ctx@entry=0x555556958750) at ../qemu-6.2.0/util/async.c:169 +#7 0x0000555555f5f784 in aio_dispatch (ctx=0x555556958750) at ../qemu-6.2.0/util/aio-posix.c:381 +#8 0x0000555555f73d63 in aio_ctx_dispatch (source=<optimized out>, callback=<optimized out>, user_data=<optimized out>) at ../qemu-6.2.0/util/async.c:311 +#9 0x00007ffff787dfd3 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 +#10 0x0000555555f80129 in glib_pollfds_poll () at ../qemu-6.2.0/util/main-loop.c:232 +#11 os_host_main_loop_wait (timeout=0) at ../qemu-6.2.0/util/main-loop.c:255 +#12 main_loop_wait (nonblocking=nonblocking@entry=0) at ../qemu-6.2.0/util/main-loop.c:531 +#13 0x0000555555c48fe5 in qemu_main_loop () at ../qemu-6.2.0/softmmu/runstate.c:726 +#14 0x000055555597b664 in main (argc=<optimized out>, argv=<optimized out>, envp=<optimized out>) at ../qemu-6.2.0/softmmu/main.c:50 +</code> +<br/> +It seems virtqueue_packed_pop() receives one desc with desc.len=65536 (or -1) which should not suppose to happen. I dont know why this is happening diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/851 b/gitlab/issues_text/target_missing/host_missing/accel_missing/851 new file mode 100644 index 000000000..989a387c0 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/851 @@ -0,0 +1,233 @@ +qemu-img create results in tsan warnings +Description of problem: +Running qemu-img w/ tsan enabled results in a bunch of data races reported: + +``` +Formatting 'delta.img', fmt=qcow2 cluster_size=65536 extended_l2=off compression_type=zlib size=0 backing_file=base.img backing_fmt=raw lazy_refcounts=off refcount_bits=16 +================== +WARNING: ThreadSanitizer: data race (pid=217825) + Atomic write of size 8 at 0x7b4800000228 by main thread: + #0 __tsan_atomic64_exchange <null> (qemu-img+0xb6a55) + #1 aio_bh_poll /usr/local/google/home/pefoley/qemu/build/../util/async.c:151:5 (qemu-img+0x239931) + #2 aio_poll /usr/local/google/home/pefoley/qemu/build/../util/aio-posix.c:707:17 (qemu-img+0x220822) + #3 bdrv_create /usr/local/google/home/pefoley/qemu/build/../block.c:549:13 (qemu-img+0xf88b1) + #4 bdrv_img_create /usr/local/google/home/pefoley/qemu/build/../block.c:6911:11 (qemu-img+0x107c1b) + #5 img_create /usr/local/google/home/pefoley/qemu/build/../qemu-img.c:585:5 (qemu-img+0xe2dad) + #6 main /usr/local/google/home/pefoley/qemu/build/../qemu-img.c:5449:20 (qemu-img+0xddfc3) + + Previous read of size 8 at 0x7b4800000228 by thread T5 (mutexes: write M42): + #0 aio_bh_enqueue /usr/local/google/home/pefoley/qemu/build/../util/async.c:82:9 (qemu-img+0x239c4c) + #1 qemu_bh_schedule /usr/local/google/home/pefoley/qemu/build/../util/async.c:186:5 (qemu-img+0x239c4c) + #2 worker_thread /usr/local/google/home/pefoley/qemu/build/../util/thread-pool.c:113:9 (qemu-img+0x24fe7c) + #3 qemu_thread_start /usr/local/google/home/pefoley/qemu/build/../util/qemu-thread-posix.c:556:9 (qemu-img+0x225960) + + Location is heap block of size 336 at 0x7b4800000180 allocated by main thread: + #0 calloc <null> (qemu-img+0x68ff9) + #1 g_malloc0 <null> (libglib-2.0.so.0+0x59e70) + #2 qemu_init_main_loop /usr/local/google/home/pefoley/qemu/build/../util/main-loop.c:169:24 (qemu-img+0x24bd47) + #3 main /usr/local/google/home/pefoley/qemu/build/../qemu-img.c:5397:5 (qemu-img+0xddcd7) + + Mutex M42 (0x7b3800000010) created at: + #0 pthread_mutex_init <null> (qemu-img+0x6bc0f) + #1 qemu_mutex_init /usr/local/google/home/pefoley/qemu/build/../util/qemu-thread-posix.c:57:11 (qemu-img+0x223f69) + #2 thread_pool_init_one /usr/local/google/home/pefoley/qemu/build/../util/thread-pool.c:306:5 (qemu-img+0x24f24d) + #3 thread_pool_new /usr/local/google/home/pefoley/qemu/build/../util/thread-pool.c:319:5 (qemu-img+0x24f24d) + #4 aio_get_thread_pool /usr/local/google/home/pefoley/qemu/build/../util/async.c:390:28 (qemu-img+0x239fd4) + #5 raw_thread_pool_submit /usr/local/google/home/pefoley/qemu/build/../block/file-posix.c:2045:24 (qemu-img+0x1b51f7) + #6 raw_regular_truncate /usr/local/google/home/pefoley/qemu/build/../block/file-posix.c:2231:12 (qemu-img+0x1b51f7) + #7 raw_co_create /usr/local/google/home/pefoley/qemu/build/../block/file-posix.c:2519:14 (qemu-img+0x1b51f7) + #8 raw_co_create_opts /usr/local/google/home/pefoley/qemu/build/../block/file-posix.c:2635:12 (qemu-img+0x1b5678) + #9 bdrv_create_co_entry /usr/local/google/home/pefoley/qemu/build/../block.c:516:11 (qemu-img+0xf87c5) + #10 bdrv_create /usr/local/google/home/pefoley/qemu/build/../block.c:544:9 (qemu-img+0xf87c5) + #11 bdrv_create_file /usr/local/google/home/pefoley/qemu/build/../block.c:734:11 (qemu-img+0xf8d3d) + #12 qcow2_co_create_opts /usr/local/google/home/pefoley/qemu/build/../block/qcow2.c:3842:11 (qemu-img+0x170c63) + #13 bdrv_create_co_entry /usr/local/google/home/pefoley/qemu/build/../block.c:516:11 (qemu-img+0xf8975) + #14 coroutine_trampoline /usr/local/google/home/pefoley/qemu/build/../util/coroutine-ucontext.c:173:9 (qemu-img+0x23d008) + #15 <null> <null> (libc.so.6+0x51a2f) + + Thread T5 'worker' (tid=217829, running) created by main thread at: + #0 pthread_create <null> (qemu-img+0x6a49d) + #1 qemu_thread_create /usr/local/google/home/pefoley/qemu/build/../util/qemu-thread-posix.c:596:11 (qemu-img+0x225800) + #2 do_spawn_thread /usr/local/google/home/pefoley/qemu/build/../util/thread-pool.c:134:5 (qemu-img+0x24fac3) + #3 spawn_thread_bh_fn /usr/local/google/home/pefoley/qemu/build/../util/thread-pool.c:142:5 (qemu-img+0x24fac3) + #4 aio_bh_call /usr/local/google/home/pefoley/qemu/build/../util/async.c:141:5 (qemu-img+0x239a96) + #5 aio_bh_poll /usr/local/google/home/pefoley/qemu/build/../util/async.c:169:13 (qemu-img+0x239a96) + #6 aio_poll /usr/local/google/home/pefoley/qemu/build/../util/aio-posix.c:707:17 (qemu-img+0x220822) + #7 bdrv_create /usr/local/google/home/pefoley/qemu/build/../block.c:549:13 (qemu-img+0xf88b1) + #8 bdrv_img_create /usr/local/google/home/pefoley/qemu/build/../block.c:6911:11 (qemu-img+0x107c1b) + #9 img_create /usr/local/google/home/pefoley/qemu/build/../qemu-img.c:585:5 (qemu-img+0xe2dad) + #10 main /usr/local/google/home/pefoley/qemu/build/../qemu-img.c:5449:20 (qemu-img+0xddfc3) + +SUMMARY: ThreadSanitizer: data race (/usr/local/google/home/pefoley/qemu/build/qemu-img+0xb6a55) in __tsan_atomic64_exchange +================== +================== +WARNING: ThreadSanitizer: data race (pid=217825) + Write of size 4 at 0x7b1c000005f0 by thread T5 (mutexes: write M42): + #0 worker_thread /usr/local/google/home/pefoley/qemu/build/../util/thread-pool.c:101:20 (qemu-img+0x24fde3) + #1 qemu_thread_start /usr/local/google/home/pefoley/qemu/build/../util/qemu-thread-posix.c:556:9 (qemu-img+0x225960) + + Previous read of size 4 at 0x7b1c000005f0 by main thread (mutexes: write M19): + #0 thread_pool_completion_bh /usr/local/google/home/pefoley/qemu/build/../util/thread-pool.c:170:19 (qemu-img+0x24f7ae) + #1 aio_bh_call /usr/local/google/home/pefoley/qemu/build/../util/async.c:141:5 (qemu-img+0x239a96) + #2 aio_bh_poll /usr/local/google/home/pefoley/qemu/build/../util/async.c:169:13 (qemu-img+0x239a96) + #3 aio_poll /usr/local/google/home/pefoley/qemu/build/../util/aio-posix.c:707:17 (qemu-img+0x220822) + #4 bdrv_create /usr/local/google/home/pefoley/qemu/build/../block.c:549:13 (qemu-img+0xf88b1) + #5 bdrv_img_create /usr/local/google/home/pefoley/qemu/build/../block.c:6911:11 (qemu-img+0x107c1b) + #6 img_create /usr/local/google/home/pefoley/qemu/build/../qemu-img.c:585:5 (qemu-img+0xe2dad) + #7 main /usr/local/google/home/pefoley/qemu/build/../qemu-img.c:5449:20 (qemu-img+0xddfc3) + + Location is heap block of size 104 at 0x7b1c000005b0 allocated by thread T4: + #0 malloc <null> (qemu-img+0x68e0d) + #1 g_malloc <null> (libglib-2.0.so.0+0x59e18) + #2 thread_pool_submit_aio /usr/local/google/home/pefoley/qemu/build/../util/thread-pool.c:249:11 (qemu-img+0x24edc8) + #3 thread_pool_submit_co /usr/local/google/home/pefoley/qemu/build/../util/thread-pool.c:287:5 (qemu-img+0x24f0fe) + #4 raw_thread_pool_submit /usr/local/google/home/pefoley/qemu/build/../block/file-posix.c:2046:12 (qemu-img+0x1b5334) + #5 raw_regular_truncate /usr/local/google/home/pefoley/qemu/build/../block/file-posix.c:2231:12 (qemu-img+0x1b5334) + #6 raw_co_create /usr/local/google/home/pefoley/qemu/build/../block/file-posix.c:2562:14 (qemu-img+0x1b5334) + #7 raw_co_create_opts /usr/local/google/home/pefoley/qemu/build/../block/file-posix.c:2635:12 (qemu-img+0x1b5678) + #8 bdrv_create_co_entry /usr/local/google/home/pefoley/qemu/build/../block.c:516:11 (qemu-img+0xf87c5) + #9 bdrv_create /usr/local/google/home/pefoley/qemu/build/../block.c:544:9 (qemu-img+0xf87c5) + #10 bdrv_create_file /usr/local/google/home/pefoley/qemu/build/../block.c:734:11 (qemu-img+0xf8d3d) + #11 qcow2_co_create_opts /usr/local/google/home/pefoley/qemu/build/../block/qcow2.c:3842:11 (qemu-img+0x170c63) + #12 bdrv_create_co_entry /usr/local/google/home/pefoley/qemu/build/../block.c:516:11 (qemu-img+0xf8975) + #13 coroutine_trampoline /usr/local/google/home/pefoley/qemu/build/../util/coroutine-ucontext.c:173:9 (qemu-img+0x23d008) + #14 <null> <null> (libc.so.6+0x51a2f) + + Mutex M42 (0x7b3800000010) created at: + #0 pthread_mutex_init <null> (qemu-img+0x6bc0f) + #1 qemu_mutex_init /usr/local/google/home/pefoley/qemu/build/../util/qemu-thread-posix.c:57:11 (qemu-img+0x223f69) + #2 thread_pool_init_one /usr/local/google/home/pefoley/qemu/build/../util/thread-pool.c:306:5 (qemu-img+0x24f24d) + #3 thread_pool_new /usr/local/google/home/pefoley/qemu/build/../util/thread-pool.c:319:5 (qemu-img+0x24f24d) + #4 aio_get_thread_pool /usr/local/google/home/pefoley/qemu/build/../util/async.c:390:28 (qemu-img+0x239fd4) + #5 raw_thread_pool_submit /usr/local/google/home/pefoley/qemu/build/../block/file-posix.c:2045:24 (qemu-img+0x1b51f7) + #6 raw_regular_truncate /usr/local/google/home/pefoley/qemu/build/../block/file-posix.c:2231:12 (qemu-img+0x1b51f7) + #7 raw_co_create /usr/local/google/home/pefoley/qemu/build/../block/file-posix.c:2519:14 (qemu-img+0x1b51f7) + #8 raw_co_create_opts /usr/local/google/home/pefoley/qemu/build/../block/file-posix.c:2635:12 (qemu-img+0x1b5678) + #9 bdrv_create_co_entry /usr/local/google/home/pefoley/qemu/build/../block.c:516:11 (qemu-img+0xf87c5) + #10 bdrv_create /usr/local/google/home/pefoley/qemu/build/../block.c:544:9 (qemu-img+0xf87c5) + #11 bdrv_create_file /usr/local/google/home/pefoley/qemu/build/../block.c:734:11 (qemu-img+0xf8d3d) + #12 qcow2_co_create_opts /usr/local/google/home/pefoley/qemu/build/../block/qcow2.c:3842:11 (qemu-img+0x170c63) + #13 bdrv_create_co_entry /usr/local/google/home/pefoley/qemu/build/../block.c:516:11 (qemu-img+0xf8975) + #14 coroutine_trampoline /usr/local/google/home/pefoley/qemu/build/../util/coroutine-ucontext.c:173:9 (qemu-img+0x23d008) + #15 <null> <null> (libc.so.6+0x51a2f) + + Mutex M19 (0x7b48000001e0) created at: + #0 pthread_mutex_init <null> (qemu-img+0x6bc0f) + #1 qemu_rec_mutex_init /usr/local/google/home/pefoley/qemu/build/../util/qemu-thread-posix.c:120:11 (qemu-img+0x224625) + #2 aio_context_new /usr/local/google/home/pefoley/qemu/build/../util/async.c:555:5 (qemu-img+0x23a226) + #3 qemu_init_main_loop /usr/local/google/home/pefoley/qemu/build/../util/main-loop.c:169:24 (qemu-img+0x24bd47) + #4 main /usr/local/google/home/pefoley/qemu/build/../qemu-img.c:5397:5 (qemu-img+0xddcd7) + + Thread T5 'worker' (tid=217829, running) created by main thread at: + #0 pthread_create <null> (qemu-img+0x6a49d) + #1 qemu_thread_create /usr/local/google/home/pefoley/qemu/build/../util/qemu-thread-posix.c:596:11 (qemu-img+0x225800) + #2 do_spawn_thread /usr/local/google/home/pefoley/qemu/build/../util/thread-pool.c:134:5 (qemu-img+0x24fac3) + #3 spawn_thread_bh_fn /usr/local/google/home/pefoley/qemu/build/../util/thread-pool.c:142:5 (qemu-img+0x24fac3) + #4 aio_bh_call /usr/local/google/home/pefoley/qemu/build/../util/async.c:141:5 (qemu-img+0x239a96) + #5 aio_bh_poll /usr/local/google/home/pefoley/qemu/build/../util/async.c:169:13 (qemu-img+0x239a96) + #6 aio_poll /usr/local/google/home/pefoley/qemu/build/../util/aio-posix.c:707:17 (qemu-img+0x220822) + #7 bdrv_create /usr/local/google/home/pefoley/qemu/build/../block.c:549:13 (qemu-img+0xf88b1) + #8 bdrv_img_create /usr/local/google/home/pefoley/qemu/build/../block.c:6911:11 (qemu-img+0x107c1b) + #9 img_create /usr/local/google/home/pefoley/qemu/build/../qemu-img.c:585:5 (qemu-img+0xe2dad) + #10 main /usr/local/google/home/pefoley/qemu/build/../qemu-img.c:5449:20 (qemu-img+0xddfc3) + + Thread T4 (tid=0, running) created by main thread at: + #0 on_new_fiber /usr/local/google/home/pefoley/qemu/build/../util/coroutine-ucontext.c:90:25 (qemu-img+0x23cead) + #1 qemu_coroutine_new /usr/local/google/home/pefoley/qemu/build/../util/coroutine-ucontext.c:219:5 (qemu-img+0x23cead) + #2 qemu_coroutine_create /usr/local/google/home/pefoley/qemu/build/../util/qemu-coroutine.c:75:14 (qemu-img+0x24c7be) + #3 bdrv_create /usr/local/google/home/pefoley/qemu/build/../block.c:546:14 (qemu-img+0xf8884) + #4 bdrv_img_create /usr/local/google/home/pefoley/qemu/build/../block.c:6911:11 (qemu-img+0x107c1b) + #5 img_create /usr/local/google/home/pefoley/qemu/build/../qemu-img.c:585:5 (qemu-img+0xe2dad) + #6 main /usr/local/google/home/pefoley/qemu/build/../qemu-img.c:5449:20 (qemu-img+0xddfc3) + +SUMMARY: ThreadSanitizer: data race /usr/local/google/home/pefoley/qemu/build/../util/thread-pool.c:101:20 in worker_thread +================== +================== +WARNING: ThreadSanitizer: data race (pid=217825) + Atomic write of size 4 at 0x7b0c000000e8 by thread T5 (mutexes: write M42): + #0 __tsan_atomic32_fetch_or <null> (qemu-img+0xb9ec1) + #1 aio_bh_enqueue /usr/local/google/home/pefoley/qemu/build/../util/async.c:80:17 (qemu-img+0x239c23) + #2 qemu_bh_schedule /usr/local/google/home/pefoley/qemu/build/../util/async.c:186:5 (qemu-img+0x239c23) + #3 worker_thread /usr/local/google/home/pefoley/qemu/build/../util/thread-pool.c:113:9 (qemu-img+0x24fe7c) + #4 qemu_thread_start /usr/local/google/home/pefoley/qemu/build/../util/qemu-thread-posix.c:556:9 (qemu-img+0x225960) + + Previous read of size 4 at 0x7b0c000000e8 by main thread: + #0 aio_compute_bh_timeout /usr/local/google/home/pefoley/qemu/build/../util/async.c:209:18 (qemu-img+0x239e7f) + #1 aio_compute_timeout /usr/local/google/home/pefoley/qemu/build/../util/async.c:232:15 (qemu-img+0x239e7f) + #2 aio_poll /usr/local/google/home/pefoley/qemu/build/../util/aio-posix.c:624:26 (qemu-img+0x21f9c2) + #3 bdrv_create /usr/local/google/home/pefoley/qemu/build/../block.c:549:13 (qemu-img+0xf88b1) + #4 bdrv_img_create /usr/local/google/home/pefoley/qemu/build/../block.c:6911:11 (qemu-img+0x107c1b) + #5 img_create /usr/local/google/home/pefoley/qemu/build/../qemu-img.c:585:5 (qemu-img+0xe2dad) + #6 main /usr/local/google/home/pefoley/qemu/build/../qemu-img.c:5449:20 (qemu-img+0xddfc3) + + Location is heap block of size 48 at 0x7b0c000000c0 allocated by thread T4: + #0 malloc <null> (qemu-img+0x68e0d) + #1 g_malloc <null> (libglib-2.0.so.0+0x59e18) + #2 thread_pool_init_one /usr/local/google/home/pefoley/qemu/build/../util/thread-pool.c:305:27 (qemu-img+0x24f235) + #3 thread_pool_new /usr/local/google/home/pefoley/qemu/build/../util/thread-pool.c:319:5 (qemu-img+0x24f235) + #4 aio_get_thread_pool /usr/local/google/home/pefoley/qemu/build/../util/async.c:390:28 (qemu-img+0x239fd4) + #5 raw_thread_pool_submit /usr/local/google/home/pefoley/qemu/build/../block/file-posix.c:2045:24 (qemu-img+0x1b51f7) + #6 raw_regular_truncate /usr/local/google/home/pefoley/qemu/build/../block/file-posix.c:2231:12 (qemu-img+0x1b51f7) + #7 raw_co_create /usr/local/google/home/pefoley/qemu/build/../block/file-posix.c:2519:14 (qemu-img+0x1b51f7) + #8 raw_co_create_opts /usr/local/google/home/pefoley/qemu/build/../block/file-posix.c:2635:12 (qemu-img+0x1b5678) + #9 bdrv_create_co_entry /usr/local/google/home/pefoley/qemu/build/../block.c:516:11 (qemu-img+0xf87c5) + #10 bdrv_create /usr/local/google/home/pefoley/qemu/build/../block.c:544:9 (qemu-img+0xf87c5) + #11 bdrv_create_file /usr/local/google/home/pefoley/qemu/build/../block.c:734:11 (qemu-img+0xf8d3d) + #12 qcow2_co_create_opts /usr/local/google/home/pefoley/qemu/build/../block/qcow2.c:3842:11 (qemu-img+0x170c63) + #13 bdrv_create_co_entry /usr/local/google/home/pefoley/qemu/build/../block.c:516:11 (qemu-img+0xf8975) + #14 coroutine_trampoline /usr/local/google/home/pefoley/qemu/build/../util/coroutine-ucontext.c:173:9 (qemu-img+0x23d008) + #15 <null> <null> (libc.so.6+0x51a2f) + + Mutex M42 (0x7b3800000010) created at: + #0 pthread_mutex_init <null> (qemu-img+0x6bc0f) + #1 qemu_mutex_init /usr/local/google/home/pefoley/qemu/build/../util/qemu-thread-posix.c:57:11 (qemu-img+0x223f69) + #2 thread_pool_init_one /usr/local/google/home/pefoley/qemu/build/../util/thread-pool.c:306:5 (qemu-img+0x24f24d) + #3 thread_pool_new /usr/local/google/home/pefoley/qemu/build/../util/thread-pool.c:319:5 (qemu-img+0x24f24d) + #4 aio_get_thread_pool /usr/local/google/home/pefoley/qemu/build/../util/async.c:390:28 (qemu-img+0x239fd4) + #5 raw_thread_pool_submit /usr/local/google/home/pefoley/qemu/build/../block/file-posix.c:2045:24 (qemu-img+0x1b51f7) + #6 raw_regular_truncate /usr/local/google/home/pefoley/qemu/build/../block/file-posix.c:2231:12 (qemu-img+0x1b51f7) + #7 raw_co_create /usr/local/google/home/pefoley/qemu/build/../block/file-posix.c:2519:14 (qemu-img+0x1b51f7) + #8 raw_co_create_opts /usr/local/google/home/pefoley/qemu/build/../block/file-posix.c:2635:12 (qemu-img+0x1b5678) + #9 bdrv_create_co_entry /usr/local/google/home/pefoley/qemu/build/../block.c:516:11 (qemu-img+0xf87c5) + #10 bdrv_create /usr/local/google/home/pefoley/qemu/build/../block.c:544:9 (qemu-img+0xf87c5) + #11 bdrv_create_file /usr/local/google/home/pefoley/qemu/build/../block.c:734:11 (qemu-img+0xf8d3d) + #12 qcow2_co_create_opts /usr/local/google/home/pefoley/qemu/build/../block/qcow2.c:3842:11 (qemu-img+0x170c63) + #13 bdrv_create_co_entry /usr/local/google/home/pefoley/qemu/build/../block.c:516:11 (qemu-img+0xf8975) + #14 coroutine_trampoline /usr/local/google/home/pefoley/qemu/build/../util/coroutine-ucontext.c:173:9 (qemu-img+0x23d008) + #15 <null> <null> (libc.so.6+0x51a2f) + + Thread T5 'worker' (tid=217829, running) created by main thread at: + #0 pthread_create <null> (qemu-img+0x6a49d) + #1 qemu_thread_create /usr/local/google/home/pefoley/qemu/build/../util/qemu-thread-posix.c:596:11 (qemu-img+0x225800) + #2 do_spawn_thread /usr/local/google/home/pefoley/qemu/build/../util/thread-pool.c:134:5 (qemu-img+0x24fac3) + #3 spawn_thread_bh_fn /usr/local/google/home/pefoley/qemu/build/../util/thread-pool.c:142:5 (qemu-img+0x24fac3) + #4 aio_bh_call /usr/local/google/home/pefoley/qemu/build/../util/async.c:141:5 (qemu-img+0x239a96) + #5 aio_bh_poll /usr/local/google/home/pefoley/qemu/build/../util/async.c:169:13 (qemu-img+0x239a96) + #6 aio_poll /usr/local/google/home/pefoley/qemu/build/../util/aio-posix.c:707:17 (qemu-img+0x220822) + #7 bdrv_create /usr/local/google/home/pefoley/qemu/build/../block.c:549:13 (qemu-img+0xf88b1) + #8 bdrv_img_create /usr/local/google/home/pefoley/qemu/build/../block.c:6911:11 (qemu-img+0x107c1b) + #9 img_create /usr/local/google/home/pefoley/qemu/build/../qemu-img.c:585:5 (qemu-img+0xe2dad) + #10 main /usr/local/google/home/pefoley/qemu/build/../qemu-img.c:5449:20 (qemu-img+0xddfc3) + + Thread T4 (tid=0, running) created by main thread at: + #0 on_new_fiber /usr/local/google/home/pefoley/qemu/build/../util/coroutine-ucontext.c:90:25 (qemu-img+0x23cead) + #1 qemu_coroutine_new /usr/local/google/home/pefoley/qemu/build/../util/coroutine-ucontext.c:219:5 (qemu-img+0x23cead) + #2 qemu_coroutine_create /usr/local/google/home/pefoley/qemu/build/../util/qemu-coroutine.c:75:14 (qemu-img+0x24c7be) + #3 bdrv_create /usr/local/google/home/pefoley/qemu/build/../block.c:546:14 (qemu-img+0xf8884) + #4 bdrv_img_create /usr/local/google/home/pefoley/qemu/build/../block.c:6911:11 (qemu-img+0x107c1b) + #5 img_create /usr/local/google/home/pefoley/qemu/build/../qemu-img.c:585:5 (qemu-img+0xe2dad) + #6 main /usr/local/google/home/pefoley/qemu/build/../qemu-img.c:5449:20 (qemu-img+0xddfc3) + +SUMMARY: ThreadSanitizer: data race (/usr/local/google/home/pefoley/qemu/build/qemu-img+0xb9ec1) in __tsan_atomic32_fetch_or +================== +ThreadSanitizer: reported 3 warnings +``` +Steps to reproduce: +1. ./configure --target-list=x86_64-softmmu --enable-tsan --cc=clang --cxx=clang++ +2. make -j12 +3. touch base.img +4. build/qemu-img create -b base.img -f qcow2 -F raw delta.img + +./configure --target-list=x86_64-softmmu --enable-tsan --cc=clang --cxx=clang++ +touch base.img +build/qemu-img create -b base.img -f qcow2 -F raw delta.img diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/853 b/gitlab/issues_text/target_missing/host_missing/accel_missing/853 new file mode 100644 index 000000000..589ef59f1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/853 @@ -0,0 +1,10 @@ +Quaint English in qemu-options.hx +Description of problem: +qemu-options.hx contains grammar that a native English-speaking person would never use. I had to read a sentence in that file very slowly and more than once to understand it. +Steps to reproduce: +1. Install QEMU +2. Run a command to display documentation that includes qemu-options.hx for instance "man qemu-system-x86_64" +3. Observe "This option defines where is connected the drive ..." +4. Scratch head, figure out that "This option defines where the drive is connected ..." is the meaning. +Additional information: +It is very difficult to report QEMU documentation bugs. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/854 b/gitlab/issues_text/target_missing/host_missing/accel_missing/854 new file mode 100644 index 000000000..b200c4e14 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/854 @@ -0,0 +1,62 @@ +rsync to ext4-fs on dynamic expanding qcow2 fails +Description of problem: +Firstly, this issue does not seem to happen when the virtual-disk is dd-raw-img or fixed qcow2 (preallocation=falloc). The guest-kernel has multiple tracebacks during rsync to dst folder on ext4-fs on qcow2. +I ctrl-C-ed the rsync process after the first traceback, which happened after copying around 52 GiB. +On a previous run, wherein I had let it continue, somewhere near the end, around 83 GiB, dmesg would bloat with a zillion trace-backs and stall. The sha256sum verify seems to have succeeded for all files copied so far and correctly gives error "Failed open or read" on subsequent files that were not copied. +In this test, the partial-rsync completed files were not corrupted. However, as qemu's disk emulation allocates blocks, qemu may be inducing paging-bugs into the guest-kernel. Paging issues like these may also lead to corruption. The guest-kernel should see the same full emulated disk regardless of whether qemu provided a fixed disk, dynamic disk, or even a different type of virtual-disk-format. The guest-vm should not detect/perceive any difference between them. + +There may be upcoming trouble round the 5.17 corner. + +It is beyond me to figure out if this is due to +* qemu-6.2 block code +* guest-kernel ( kernel-5.17 folio/page management or ntfs3 driver or something else ) + +It may be necessary to ascertain if this is a new bug on account of qemu not being ready for folio type page-management or a bug in upstream kernel.org. My apologies in advance if it turns out that this is not a qemu bug. + +There there does seem to be some problem with qemu dealing with expanding virtual disks, with bugs that show up only if the underlying virtual-disk is dynamic and expanding. + +I just think that storage/block-code should be made rock solid with a much higher priority than adding new features. +If storage code is undependable, then qemu/vm cannot be used, and there is no point in any other feature. qcow2 in particular is the qemu's native virtual-disk format. + +I had to stop testing on Issue #727 , Issue #814 , on account of what I thought was a bug in 5.15 kernels. I filed the bug as "fs/ntfs3: page_cache_ra_unbounded on rsync from ntfs3 to ext4" https://bugzilla.kernel.org/show_bug.cgi?id=215460 . I assume that bug is different because it happens even on raw image. + +setup is as follows: +- Host: Fedora-35 with kernel-5.17.0-0.rc2.83.fc35.x86_64 self-built from srpm ( https://koji.fedoraproject.org/koji/buildinfo?buildID=1910212 ) +- Guest: Fedora-Workstation-Live-x86_64-Rawhide-20220201.n.0.iso with 5.17.0-0.rc2.83.fc36.x86_64 ( https://koji.fedoraproject.org/koji/buildinfo?buildID=1910892 ) +- qemu: 6.2.0 (qemu-6.2.0-2.fc35.1) self-built from srpm ( https://koji.fedoraproject.org/koji/buildinfo?buildID=1897713 ) +- hda: qcow2(dyn) with ext4 and also 4 combinations of raw_img/fixed_qcow2 with ext4/ntfs3 +- hdb: vhdx, ntfs3 (pre-prepared sgdata https://gitlab.com/qemu-project/qemu/-/issues/727#note_739930694 ) + +qcow2 image is created as follows: +``` +[root@sirius ~]# qemu-img create -f qcow2 /mnt/a16/gkpics01.qcow2 99723771904 +Formatting '/mnt/a16/gkpics01.qcow2', fmt=qcow2 cluster_size=65536 extended_l2=off compression_type=zlib size=99723771904 lazy_refcounts=off refcount_bits=16 +``` + +qemu command is as follows: +``` +[root@sirius ~]# qemu-system-x86_64 -cpu qemu64 -m 4096 -machine "type=q35" -accel "kvm" -smp "sockets=1,cores=8,threads=1" -boot "d" -cdrom "/vol/15KJ_Images/transcend/Fedora-Workstation-Live-x86_64-Rawhide-20220201.n.0.iso" -hda "/mnt/a16/gkpics01.raw" -hdb "/vol/15KJ_Images/test/sgdata.vhdx" -device "virtio-vga" -display "gtk,gl=on" -rtc "base=utc" -net "user" -device "virtio-net,netdev=vmnic" -netdev "user,id=vmnic,net=192.168.20.0/24,dns=192.168.20.3,dhcpstart=192.168.20.15" +``` +Steps to reproduce: +1. Inside booted vm, use gdisk to partition /dev/sda1 if necessary +2. ```dmesg -w (in another pty)``` +3. ```mkfs.ext4 /dev/sda1 -L fs_gkpics001``` +4. ```mkdir /mnt/a /mnt/b``` +5. ```mount -t ext4 /dev/sda1 /mnt/a``` +6. ```mount -t ntfs3 /dev/sdb2 /mnt/b``` +7. rsync testdata: ```(sdate=`date` ; echo "$sdate" ; cd /mnt/b ; rsync -avH ./photos001 /mnt/a | tee /tmp/rst.txt ; echo "$sdate" ; date )``` +8. ```umount /mnt/a ; ``` +9. ```mount -t ext4 /dev/sda1 /mnt/a``` +10. verify: ```(sdate=`date` ; echo "$sdate" ; cd /mnt/a/photos001 ; sha256sum -c ./find.CHECKSUM --quiet ; echo "$sdate" ; date )``` +11. ```umount /mnt/a ; umount /mnt/b;``` +Additional information: +**Test attempts** +- Bug does not happen with 5.17.0-0.rc2.83/qemu-6.2.0-2/5.17.0-0.rc2.83/ExFAT/rawimg/ext4 with vhdx/ntfs3/sgdata +- Bug does not happen with 5.17.0-0.rc2.83/qemu-6.2.0-2/5.17.0-0.rc2.83/ExFAT/rawimg/ntfs3 with vhdx/ntfs3/sgdata +- Bug does not happen with 5.17.0-0.rc2.83/qemu-6.2.0-2/5.17.0-0.rc2.83/ExFAT/qcow2(fixed)/ext4 with vhdx/ntfs3/sgdata +- Bug does not happen with 5.17.0-0.rc2.83/qemu-6.2.0-2/5.17.0-0.rc2.83/ExFAT/qcow2(fixed)/ntfs3 with vhdx/ntfs3/sgdata +- Bug **does** happen with 5.17.0-0.rc2.83/qemu-6.2.0-2/5.17.0-0.rc2.83/ExFAT/**qcow2(dyn)**/ext4 with vhdx/ntfs3/sgdata +- Bug does not happen directly on Host with 5.17.0-0.rc2.83/ExFat with ntfs3/sgdata +- Bug does not happen directly on Host with 5.17.0-0.rc2.83/ntfs3 with ntfs3/sgdata + +Also filed a linux-kernel bug titled "during rsync, vm guest kernel trace arising from memcg_kmem_charge_page alloc_pages" https://bugzilla.kernel.org/show_bug.cgi?id=215563 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/857 b/gitlab/issues_text/target_missing/host_missing/accel_missing/857 new file mode 100644 index 000000000..f5bb7f777 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/857 @@ -0,0 +1,12 @@ +qemu-x86_64 uses host libraries instead of emulated system libraries +Description of problem: +I'm using Buildroot to build a cross-compiled embedded Linux system. During the build process there is a little hack to create some header file using a cross-compiled application. For this hack they use qemu to run this application. Building this embedded system for aarch64 work fine, but for x86_64 I get the following messages: + +bytecode_builtins_list_generator: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by bytecode_builtins_list_generator) +bytecode_builtins_list_generator: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by bytecode_builtins_list_generator) +bytecode_builtins_list_generator: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by bytecode_builtins_list_generator) +bytecode_builtins_list_generator: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by bytecode_builtins_list_generator) + +The path of the libraries in this error message is from my host system. The embedded system uses /lib64 or /usr/lib64. It seems to me that the linker search for the libraries at first on the host system and later uses the path from the command line. So you have a mixed up of host and embedded system libraries (as you can see in the attached strace log). +Additional information: +[qemu-1.log](/uploads/f53e98b6b15cce7cbf94d14dffa39f90/qemu-1.log) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/861 b/gitlab/issues_text/target_missing/host_missing/accel_missing/861 new file mode 100644 index 000000000..696dbd835 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/861 @@ -0,0 +1 @@ +Using qemu+kvm is slower than using qemu in rv6(xv6 rust porting) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/865 b/gitlab/issues_text/target_missing/host_missing/accel_missing/865 new file mode 100644 index 000000000..fa1798385 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/865 @@ -0,0 +1,45 @@ +virtio-vga gtk,gl=on Black Screen or GLXGears picture +Description of problem: +Blank screen for tab with name `virtio-vga` on GTK interface, however, if I run `glxgears` before running the machine, I see the following image: + + +Steps to reproduce: +1.Run the invocation command provided above + +# +Additional information: +The host when the problem is occurring is a Dell Precision 5110 laptop that have Hybrid Graphics. I am running X11 with nvidia as the main driver, I am not using nouveau, I am using the nvidia drivers installed by the debian package, here the corresponding information for the nvida card: + +``` +nvidia-smi +``` +``` +Thu Feb 10 23:32:21 2022 ++-----------------------------------------------------------------------------+ +| NVIDIA-SMI 460.91.03 Driver Version: 460.91.03 CUDA Version: 11.2 | +|-------------------------------+----------------------+----------------------+ +| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC | +| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | +| | | MIG M. | +|===============================+======================+======================| +| 0 Quadro M1000M On | 00000000:01:00.0 Off | N/A | +| N/A 44C P8 N/A / N/A | 846MiB / 2004MiB | 6% Default | +| | | N/A | ++-------------------------------+----------------------+----------------------+ + ++-----------------------------------------------------------------------------+ +| Processes: | +| GPU GI CI PID Type Process name GPU Memory | +| ID ID Usage | +|=============================================================================| +| 0 N/A N/A 6926 G /usr/lib/xorg/Xorg 528MiB | +| 0 N/A N/A 7223 G ...b/firefox-esr/firefox-esr 238MiB | +| 0 N/A N/A 7363 G ...b/firefox-esr/firefox-esr 0MiB | +| 0 N/A N/A 276992 G ...b/firefox-esr/firefox-esr 0MiB | +| 0 N/A N/A 282023 G ...b/firefox-esr/firefox-esr 0MiB | +| 0 N/A N/A 282630 G ...b/firefox-esr/firefox-esr 0MiB | +| 0 N/A N/A 322305 G qemu-system-x86_64 70MiB | ++-----------------------------------------------------------------------------+ +``` + +## diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/866 b/gitlab/issues_text/target_missing/host_missing/accel_missing/866 new file mode 100644 index 000000000..7b3a28218 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/866 @@ -0,0 +1,53 @@ +linux-user: substantial memory leak when threads are created and destroyed +Description of problem: +Substantial memory leak when the following simple program is executed on `qemu-arm`, +```c +// compile with `arm-none-linux-gnueabihf-gcc test_qemu.c -o test_qemu.out -pthread` + +#include <assert.h> +#include <pthread.h> + +#define MAGIC_RETURN ((void *)42) + +void *thread_main(void *arg) +{ + return MAGIC_RETURN; +} + +int main(int argc, char *argv[]) +{ + size_t i; + for (i = 0;; i++) + { + pthread_t thread; + assert(pthread_create(&thread, NULL, thread_main, NULL) == 0); + void *ret; + assert(pthread_join(thread, &ret) == 0); + assert(ret == MAGIC_RETURN); + } + + return 0; +} +``` +Steps to reproduce: +1. +``` +export TOOLCHAIN_PREFIX=arm-none-linux-gnueabihf +export ARMSDK=/${TOOLCHAIN_PREFIX} +export SYSROOT=${ARMSDK}/${TOOLCHAIN_PREFIX}/libc +export CC=${ARMSDK}/bin/${TOOLCHAIN_PREFIX}-gcc +``` +2. Download the arm toolchain: `curl --output ${TOOLCHAIN_PREFIX}.tar.xz -L 'https://developer.arm.com/-/media/Files/downloads/gnu-a/10.2-2020.11/binrel/gcc-arm-10.2-2020.11-x86_64-arm-none-linux-gnueabihf.tar.xz?revision=d0b90559-3960-4e4b-9297-7ddbc3e52783&la=en&hash=985078B758BC782BC338DB947347107FBCF8EF6B'` +3. `mkdir -p ${ARMSDK} && tar xf ${TOOLCHAIN_PREFIX}.tar.xz -C ${ARMSDK} --strip-components=1` +4. `$CC test_qemu.c -o test_qemu.out -pthread` +5. `qemu-arm -L $SYSROOT ./test_qemu.out` +6. Observe memory usage keeps ramping up and crashes the process once out of memory. +Additional information: +Valgrind annotation logs [annot.log](/uploads/f8d05d8f216d5a589e8da0758a345de6/annot.log) generated by a local build on master@0a301624c2f4ced3331ffd5bce85b4274fe132af from +```bash +valgrind --xtree-memory=full --xtree-memory-file=xtmemory.kcg bin/debug/native/qemu-arm -L $SYSROOT /mnt/f/test_qemu3.out +# Send CTRL-C before the process crashes due to oom +callgrind_annotate --auto=yes --inclusive=yes --sort=curB:100,curBk:100,totB:100,totBk:100,totFdB:100,totFdBk:100 xtmemory.kcg > annot.log +``` + +# diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/867 b/gitlab/issues_text/target_missing/host_missing/accel_missing/867 new file mode 100644 index 000000000..c74eb0e46 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/867 @@ -0,0 +1,13 @@ +qemu-system-x86_64: warning: usb-redir connection broken during migration +Description of problem: +Create Snapshot, Restore snapshot, crash +Steps to reproduce: +1. Create Snapshot +2. Restore Snapshot +3. Crash +Additional information: + + +No redirecting: + + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/868 b/gitlab/issues_text/target_missing/host_missing/accel_missing/868 new file mode 100644 index 000000000..0c43bffff --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/868 @@ -0,0 +1,15 @@ +Graphic session freezes and logs out +Description of problem: +Graphic session freezes and logs out resetting user session. I've tried with both X and Wayland. +The session does not last longer than 10-15 mins while working with: + VSCode + Firefox browser (no more than 5 open tabs - nothing heavy) + +If only using console, the problem does not seem occur, or maybe it takes longer, but haven't been able to reproduce it. +Steps to reproduce: +No steps. Just using common apps (vscode editor and ffox browser) for 10-15 mins causes the problem. Standard sites: gitlab, stacoverflow. +Additional information: +I used this configuration for +1 year without issues. I guess some updates to either Ubuntu or Lubuntu causes the problem. +I deleted the guest VM and started with a fresh new Lubuntu 20.04 LTS AS IS no exttra software and the problem persists. + +Happy to provide any info you may require. I've looked around in the logs but couldnn't find anything useful. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/87 b/gitlab/issues_text/target_missing/host_missing/accel_missing/87 new file mode 100644 index 000000000..3953d6107 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/87 @@ -0,0 +1 @@ +doesn't clear screen on boot diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/872 b/gitlab/issues_text/target_missing/host_missing/accel_missing/872 new file mode 100644 index 000000000..c0f32bfca --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/872 @@ -0,0 +1 @@ +linux-user getsockopt(fd, SOL_SOCKET, SO_ERROR) returns host errno to target diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/873 b/gitlab/issues_text/target_missing/host_missing/accel_missing/873 new file mode 100644 index 000000000..04913bbde --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/873 @@ -0,0 +1 @@ +Meson warns about a broken Python install on Debian/Ubuntu diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/874 b/gitlab/issues_text/target_missing/host_missing/accel_missing/874 new file mode 100644 index 000000000..f1ad2f771 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/874 @@ -0,0 +1 @@ +New Python QMP library races on NetBSD diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/875 b/gitlab/issues_text/target_missing/host_missing/accel_missing/875 new file mode 100644 index 000000000..6c866e0fe --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/875 @@ -0,0 +1 @@ +Failure to build using GCC on macOS diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/878 b/gitlab/issues_text/target_missing/host_missing/accel_missing/878 new file mode 100644 index 000000000..867659272 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/878 @@ -0,0 +1,42 @@ +Can't bind PCI device behind a PCI bridge (No such device) +Description of problem: +Qemu fails to assign the device with : +``` +qemu-system-x86_64: -device vfio-pci,host=3b:00.0: vfio 0000:3b:00.0: error getting device from group 72: No such device +Verify all devices in group 72 are bound to vfio-<bus> or pci-stub and not already in use +``` + +Looking at strace, we can see that the device is behind a PCI bridge: +``` +lstat("/sys", {st_mode=S_IFDIR|0555, st_size=0, ...}) = 0 +lstat("/sys/bus", {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0 +lstat("/sys/bus/pci", {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0 +lstat("/sys/bus/pci/devices", {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0 +lstat("/sys/bus/pci/devices/0000:3b:00.0", {st_mode=S_IFLNK|0777, st_size=0, ...}) = 0 +readlink("/sys/bus/pci/devices/0000:3b:00.0", "../../../devices/pci0000:3a/0000"..., 4095) = 53 +lstat("/sys/devices", {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0 +lstat("/sys/devices/pci0000:3a", {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0 +lstat("/sys/devices/pci0000:3a/0000:3a:02.0", {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0 +lstat("/sys/devices/pci0000:3a/0000:3a:02.0/0000:3b:00.0", {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0 +lstat("/sys/devices/pci0000:3a/0000:3a:02.0/0000:3b:00.0/subsystem", {st_mode=S_IFLNK|0777, st_size=0, ...}) = 0 +readlink("/sys/devices/pci0000:3a/0000:3a:02.0/0000:3b:00.0/subsystem", "../../../../bus/pci", 4095) = 19 +lstat("/sys/bus", {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0 +lstat("/sys/bus/pci", {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0 +ioctl(14, VFIO_GROUP_GET_DEVICE_FD, 0x56267b3b1320) = -1 ENODEV (No such device) +``` + +The issue is that the PCI bridge `0000:3a:02.0`, is used by "pcieport" kernel driver and not "vfio-pci". +After manually unbinding the PCI bridge from it's driver and binding it to vfio-pci qemu successfully attaches it to the VM. + +I saw online that qemu is suposed to automaticly unbind devices from the host, make them available to the VM and restore them to their previous state once the VM is shutdown. +This is not happening here. +Steps to reproduce: +1. Have a PCI device behind a PCI bridge +2. Launch a VM with the PCI device attached +3. Observe similar error messages +Additional information: +After reading [kernel vfio doc](https://www.kernel.org/doc/html/latest/driver-api/vfio.html#vfio-usage-example), I can see that `ls -l /sys/bus/pci/devices/0000:3b:00.0/iommu_group/devices` was supposed to list the PCI bridge, but it is not the case for me. + +I could only notice the presence of the bridge by looking in the `/sys/bus/pci/devices/0000:3b:00.0` symlink. + +Maybe qemu misses it because of that ? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/879 b/gitlab/issues_text/target_missing/host_missing/accel_missing/879 new file mode 100644 index 000000000..2c828bf87 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/879 @@ -0,0 +1,3 @@ +Microphone support for Macbooks +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/88 b/gitlab/issues_text/target_missing/host_missing/accel_missing/88 new file mode 100644 index 000000000..9d4980c18 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/88 @@ -0,0 +1 @@ +VNC server does not work with Mac Screen Sharing diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/880 b/gitlab/issues_text/target_missing/host_missing/accel_missing/880 new file mode 100644 index 000000000..f3e53d6bb --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/880 @@ -0,0 +1 @@ +Documentation needs some updates diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/881 b/gitlab/issues_text/target_missing/host_missing/accel_missing/881 new file mode 100644 index 000000000..f3ef4545b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/881 @@ -0,0 +1,20 @@ +qemu-ga fs-freeze causes VM to +Description of problem: +I have fresh install of Debian 11 and installed MariaDB 10.7 from MariaDB's Repo. Guest is fully up to date. +When Proxmox goes to do a backup it will call fs-freeze to the VM via the agent which then causes the backup process to hang and the VM will lockup or causes kernel message such as `**task qemu-ga:370 blocked for more than 120 seconds**`. The VM from what I can tell no longer is able to write to disk, and the only fix is to force reset the VM. + +The issue doesn't happen when the VM has first started or the agent has been restart from what I can tell, but if you leave it and wait for the nightly backup to run of the VM, it will then cause this issue to happen. + +There are other reports of this happening on the [proxmox forums](https://forum.proxmox.com/threads/snapshot-backup-not-working-guest-agent-fs-freeze-gets-timeout.99887/) More details on this topic. Other reports with the issue with MariaDB 10.6. + +My other Debian 11 VMs which were also setup recently, do not experience this problem, only difference is this VM is running the MariaDB. I have Gitlab, Docker, Mailcow, PowerDNS, OPNsense (each of these separate VM) in the other VMs and they do not experience this issue. All these VMs are running Debian 11. + +Agent Info +``` +qemu-guest-agent/stable,stable-security,now 1:5.2+dfsg-11+deb11u1 amd64 +``` +Steps to reproduce: +1. Install Proxmox (although I would assume any QEMU 6.1.1) +2. Create a Debian 11 guest with MariaDB 10.7 from MariaDB repo +3. Wait good few hours +4. Issue a backup or fs-freeze diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/882 b/gitlab/issues_text/target_missing/host_missing/accel_missing/882 new file mode 100644 index 000000000..0850871d4 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/882 @@ -0,0 +1,473 @@ +Build fails: error: ‘struct statx’ has no member named ‘stx_mnt_id’ +Description of problem: +When trying to build qemu (both version 6.2.0 and upstream git), the build fails with the mentioned error message +Steps to reproduce: +1. Configure qemu with the following arguments (target list removed for the sake of brevity): +``` +./configure \ + --prefix=/usr \ + --sysconfdir=/etc \ + --localstatedir=/var \ + --libexecdir=/usr/lib/qemu \ + --smbd=/usr/bin/smbd \ + --enable-modules \ + --enable-sdl \ + --enable-slirp=system \ + --disable-werror +``` +2. Try to build qemu +3. Build fails on target tools/virtiofsd/virtiofsd.p/passthrough_ll.c.o +Additional information: +Meson output: +``` ++ ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libexecdir=/usr/lib/qemu --smbd=/usr/bin/smbd --enable-modules --enable-sdl --enable-slirp=system --disable-werror --target-list=x86_64-softmmu,x86_64-linux-user,aarch64-softmmu,aarch64-linux-user,ppc64-softmmu,ppc64-linux-user,riscv32-softmmu,riscv32-linux-user,riscv64-softmmu,riscv64-linux-user,arm-softmmu,arm-linux-user,avr-softmmu +Using './build' as the directory for build output +The Meson build system +Version: 0.61.2 +Source dir: /home/mae/dev/qemubuild/qemu +Build dir: /home/mae/dev/qemubuild/qemu/build +Build type: native build +Project name: qemu +Project version: 6.2.50 +C compiler for the host machine: gcc -m64 -mcx16 (gcc 11.2.0 "gcc (GCC) 11.2.0") +C linker for the host machine: gcc -m64 -mcx16 ld.bfd 2.37 +Host machine cpu family: x86_64 +Host machine cpu: x86_64 +Program sh found: YES (/usr/bin/sh) +Program python3 found: YES (/usr/bin/python) +Program bzip2 found: YES (/usr/bin/bzip2) +C++ compiler for the host machine: g++ -m64 -mcx16 (gcc 11.2.0 "g++ (GCC) 11.2.0") +C++ linker for the host machine: g++ -m64 -mcx16 ld.bfd 2.37 +Program cgcc found: NO +Library m found: YES +Run-time dependency threads found: YES +Library util found: YES +Run-time dependency appleframeworks found: NO (tried framework) +Found pkg-config: /usr/bin/pkg-config (1.8.0) +Run-time dependency pixman-1 found: YES 0.40.0 +Run-time dependency zlib found: YES 1.2.11 +Has header "libaio.h" : YES +Library aio found: YES +Run-time dependency liburing found: YES 2.0 +Run-time dependency libnfs found: YES 5.0.1 +Run-time dependency appleframeworks found: NO (tried framework) +Run-time dependency libseccomp found: YES 2.5.3 +Has header "cap-ng.h" : YES +Library cap-ng found: YES +Run-time dependency xkbcommon found: YES 1.4.0 +Has header "libvdeplug.h" : YES +Library vdeplug found: YES +Run-time dependency libpulse found: YES 15.0 +Run-time dependency alsa found: YES 1.2.6.1 +Run-time dependency jack found: NO (tried pkgconfig) +Run-time dependency spice-protocol found: YES 0.14.4 +Run-time dependency spice-server found: YES 0.15.0 +Library rt found: YES +Run-time dependency libiscsi found: YES 1.19.0 +Run-time dependency libzstd found: YES 1.5.2 +Run-time dependency virglrenderer found: YES 0.9.1 +Run-time dependency libcurl found: YES 7.81.0 +Run-time dependency libudev found: YES 250 +Library mpathpersist found: NO +Run-time dependency ncursesw found: YES 6.3.20211021 +Has header "brlapi.h" : NO +Run-time dependency sdl2 found: YES 2.0.18 +Run-time dependency sdl2_image found: YES 2.0.5 +Library rados found: NO +Has header "rbd/librbd.h" : NO +Run-time dependency glusterfs-api found: NO (tried pkgconfig) +Run-time dependency libssh found: YES 0.9.6 +Has header "bzlib.h" : YES +Library bz2 found: YES +Has header "lzfse.h" : NO +Has header "sys/soundcard.h" : YES +Run-time dependency gbm found: YES 21.3.1 +Run-time dependency gnutls found: YES 3.7.3 +Run-time dependency gtk+-3.0 found: YES 3.24.31 +Run-time dependency gtk+-x11-3.0 found: YES 3.24.31 +Run-time dependency vte-2.91 found: YES 0.66.2 +Run-time dependency x11 found: YES 1.7.3.1 +Run-time dependency libpng found: YES 1.6.37 +Run-time dependency libjpeg found: YES 2.1.2 +Has header "sasl/sasl.h" : YES +Library sasl2 found: YES +Has header "security/pam_appl.h" : YES +Library pam found: YES +Has header "snappy-c.h" : YES +Library snappy found: YES +Has header "lzo/lzo1x.h" : YES +Library lzo2 found: YES +Run-time dependency libcacard found: YES 2.7.0 +Run-time dependency u2f-emu found: NO (tried pkgconfig) +Run-time dependency libusbredirparser-0.5 found: YES 0.12.0 +Run-time dependency libusb-1.0 found: YES 1.0.25 +Run-time dependency libpmem found: NO (tried pkgconfig) +Run-time dependency libdaxctl found: YES 72.1+ +Run-time dependency libtasn1 found: YES 4.18.0 +Run-time dependency libkeyutils found: YES 1.6.3 +Checking for function "gettid" : YES +Run-time dependency libselinux found: NO (tried pkgconfig) +Run-time dependency fuse3 found: YES 3.10.5 +Run-time dependency libbpf found: YES 0.7.0 +Has header "sys/epoll.h" : YES +Has header "linux/magic.h" : YES +Has header "valgrind/valgrind.h" : YES +Has header "linux/btrfs.h" : YES +Has header "libdrm/drm.h" : YES +Has header "pty.h" : YES +Has header "sys/disk.h" : NO +Has header "sys/ioccom.h" : NO +Has header "sys/kcov.h" : NO +Checking for function "accept4" : YES +Checking for function "clock_adjtime" : YES +Checking for function "dup3" : YES +Checking for function "fallocate" : YES +Checking for function "posix_fallocate" : YES +Checking for function "posix_memalign" : YES +Checking for function "ppoll" : YES +Checking for function "preadv" : YES +Checking for function "sem_timedwait" with dependency threads: YES +Checking for function "sendfile" : YES +Checking for function "setns" : YES +Checking for function "unshare" : YES +Checking for function "syncfs" : YES +Checking for function "sync_file_range" : YES +Checking for function "timerfd_create" : YES +Checking for function "copy_file_range" : YES +Checking for function "openpty" with dependency -lutil: YES +Checking for function "strchrnul" : YES +Checking for function "system" : YES +Header <byteswap.h> has symbol "bswap_32" : YES +Header <sys/epoll.h> has symbol "epoll_create1" : YES +Header <unistd.h> has symbol "environ" : YES +Header <linux/falloc.h> has symbol "FALLOC_FL_PUNCH_HOLE" : YES +Header <linux/falloc.h> has symbol "FALLOC_FL_KEEP_SIZE" : YES +Header <linux/falloc.h> has symbol "FALLOC_FL_ZERO_RANGE" : YES +Has header "linux/fiemap.h" : YES +Header <linux/fs.h> has symbol "FS_IOC_FIEMAP" : YES +Checking for function "getrandom" : YES +Header <sys/random.h> has symbol "GRND_NONBLOCK" : YES +Header <sys/inotify.h> has symbol "inotify_init" : YES +Header <sys/inotify.h> has symbol "inotify_init1" : YES +Header <machine/bswap.h> has symbol "bswap32" : NO +Header <sys/prctl.h> has symbol "PR_SET_TIMERSLACK" : YES +Header <linux/rtnetlink.h> has symbol "IFLA_PROTO_DOWN" : YES +Header <sys/sysmacros.h> has symbol "makedev" : YES +Header <getopt.h> has symbol "optreset" : NO +Header <netinet/in.h> has symbol "IPPROTO_MPTCP" : YES +Checking whether type "struct sigevent" has member "sigev_notify_thread_id" : NO +Checking whether type "struct stat" has member "st_atim" : YES +Checking for type "struct iovec" : YES +Checking for type "struct utmpx" : YES +Checking for type "struct mmsghdr" : YES +Program scripts/minikconf.py found: YES (/usr/bin/python /home/mae/dev/qemubuild/qemu/scripts/minikconf.py) +Configuring x86_64-softmmu-config-target.h using configuration +Configuring x86_64-softmmu-config-devices.mak with command +Reading depfile: /home/mae/dev/qemubuild/qemu/build/meson-private/x86_64-softmmu-config-devices.mak.d +Configuring x86_64-softmmu-config-devices.h using configuration +Configuring x86_64-linux-user-config-target.h using configuration +Configuring aarch64-softmmu-config-target.h using configuration +Configuring aarch64-softmmu-config-devices.mak with command +Reading depfile: /home/mae/dev/qemubuild/qemu/build/meson-private/aarch64-softmmu-config-devices.mak.d +Configuring aarch64-softmmu-config-devices.h using configuration +Configuring aarch64-linux-user-config-target.h using configuration +Configuring ppc64-softmmu-config-target.h using configuration +Configuring ppc64-softmmu-config-devices.mak with command +Reading depfile: /home/mae/dev/qemubuild/qemu/build/meson-private/ppc64-softmmu-config-devices.mak.d +Configuring ppc64-softmmu-config-devices.h using configuration +Configuring ppc64-linux-user-config-target.h using configuration +Configuring riscv32-softmmu-config-target.h using configuration +Configuring riscv32-softmmu-config-devices.mak with command +Reading depfile: /home/mae/dev/qemubuild/qemu/build/meson-private/riscv32-softmmu-config-devices.mak.d +Configuring riscv32-softmmu-config-devices.h using configuration +Configuring riscv32-linux-user-config-target.h using configuration +Configuring riscv64-softmmu-config-target.h using configuration +Configuring riscv64-softmmu-config-devices.mak with command +Reading depfile: /home/mae/dev/qemubuild/qemu/build/meson-private/riscv64-softmmu-config-devices.mak.d +Configuring riscv64-softmmu-config-devices.h using configuration +Configuring riscv64-linux-user-config-target.h using configuration +Configuring arm-softmmu-config-target.h using configuration +Configuring arm-softmmu-config-devices.mak with command +Reading depfile: /home/mae/dev/qemubuild/qemu/build/meson-private/arm-softmmu-config-devices.mak.d +Configuring arm-softmmu-config-devices.h using configuration +Configuring arm-linux-user-config-target.h using configuration +Configuring avr-softmmu-config-target.h using configuration +Configuring avr-softmmu-config-devices.mak with command +Reading depfile: /home/mae/dev/qemubuild/qemu/build/meson-private/avr-softmmu-config-devices.mak.d +Configuring avr-softmmu-config-devices.h using configuration +Program scripts/make-config-poison.sh found: YES (/home/mae/dev/qemubuild/qemu/scripts/make-config-poison.sh) +Run-time dependency capstone found: NO (tried pkgconfig) +Configuring capstone-defs.h using configuration +Run-time dependency slirp found: YES 4.6.1 +Library fdt found: YES +Configuring config-host.h using configuration +Program scripts/hxtool found: YES (/home/mae/dev/qemubuild/qemu/scripts/hxtool) +Program scripts/shaderinclude.pl found: YES (/usr/bin/env perl /home/mae/dev/qemubuild/qemu/scripts/shaderinclude.pl) +Program scripts/qapi-gen.py found: YES (/usr/bin/python /home/mae/dev/qemubuild/qemu/scripts/qapi-gen.py) +Program scripts/qemu-version.sh found: YES (/home/mae/dev/qemubuild/qemu/scripts/qemu-version.sh) + +Executing subproject libvhost-user + +libvhost-user| Project name: libvhost-user +libvhost-user| Project version: undefined +libvhost-user| C compiler for the host machine: gcc -m64 -mcx16 (gcc 11.2.0 "gcc (GCC) 11.2.0") +libvhost-user| C linker for the host machine: gcc -m64 -mcx16 ld.bfd 2.37 +libvhost-user| Dependency threads found: YES unknown (cached) +libvhost-user| Dependency glib-2.0 found: YES 2.71.2 (overridden) +libvhost-user| Build targets in project: 10 +libvhost-user| Subproject libvhost-user finished. + +Program scripts/decodetree.py found: YES (/usr/bin/python /home/mae/dev/qemubuild/qemu/scripts/decodetree.py) +Program ../scripts/modules/module_block.py found: YES (/usr/bin/python /home/mae/dev/qemubuild/qemu/block/../scripts/modules/module_block.py) +Program ../scripts/block-coroutine-wrapper.py found: YES (/usr/bin/python /home/mae/dev/qemubuild/qemu/block/../scripts/block-coroutine-wrapper.py) +Program scripts/modinfo-collect.py found: YES (/home/mae/dev/qemubuild/qemu/scripts/modinfo-collect.py) +Program scripts/modinfo-generate.py found: YES (/home/mae/dev/qemubuild/qemu/scripts/modinfo-generate.py) +Program nm found: YES +Program scripts/undefsym.py found: YES (/usr/bin/python /home/mae/dev/qemubuild/qemu/scripts/undefsym.py) +Program scripts/feature_to_c.sh found: YES (/bin/sh /home/mae/dev/qemubuild/qemu/scripts/feature_to_c.sh) +Configuring 50-qemu-gpu.json using configuration +Configuring 50-qemu-virtiofsd.json using configuration +Configuring 50-edk2-i386-secure.json using configuration +Configuring 50-edk2-x86_64-secure.json using configuration +Configuring 60-edk2-aarch64.json using configuration +Configuring 60-edk2-arm.json using configuration +Configuring 60-edk2-i386.json using configuration +Configuring 60-edk2-x86_64.json using configuration +Program qemu-keymap found: NO +Program cp found: YES (/usr/bin/cp) +Program sphinx-build-3 sphinx-build found: NO +Program python3 found: YES (/usr/bin/python) +Program diff found: YES (/usr/bin/diff) +Program dbus-daemon found: YES (/usr/bin/dbus-daemon) +Program initrd-stress.sh found: YES (/home/mae/dev/qemubuild/qemu/tests/migration/initrd-stress.sh) +Program xgettext found: YES (/usr/bin/xgettext) +Build targets in project: 744 + +qemu 6.2.50 + + Directories + Install prefix : /usr + BIOS directory : share/qemu + firmware path : /usr/share/qemu-firmware + binary directory : bin + library directory : lib + module directory : lib/qemu + libexec directory : lib/qemu + include directory : include + config directory : /etc + local state directory : /var + Manual directory : share/man + Doc directory : /usr/share/doc + Build directory : /home/mae/dev/qemubuild/qemu/build + Source path : /home/mae/dev/qemubuild/qemu + GIT submodules : ui/keycodemapdb tests/fp/berkeley-testfloat-3 tests/fp/berkeley-softfloat-3 dtc capstone + + Host binaries + git : git + make : make + python : /usr/bin/python (version: 3.10) + sphinx-build : NO + gdb : /usr/bin/gdb + genisoimage : + smbd : "/usr/bin/smbd" + + Configurable features + Documentation : NO + system-mode emulation : YES + user-mode emulation : YES + block layer : YES + Install blobs : YES + module support : YES + alternative module path : NO + fuzzing support : NO + Audio drivers : pa oss + Trace backends : log + D-Bus display : YES + QOM debugging : YES + vhost-kernel support : YES + vhost-net support : YES + vhost-crypto support : YES + vhost-scsi support : YES + vhost-vsock support : YES + vhost-user support : YES + vhost-user-blk server support: YES + vhost-user-fs support : YES + vhost-vdpa support : YES + build guest agent : YES + + Compilation + host CPU : x86_64 + host endianness : little + C compiler : gcc -m64 -mcx16 + Host C compiler : gcc -m64 -mcx16 + C++ compiler : g++ -m64 -mcx16 + CFLAGS : -march=native -mtune=native -O3 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -O2 -g + CXXFLAGS : -march=native -mtune=native -O3 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -Wp,-D_GLIBCXX_ASSERTIONS -O2 -g + LDFLAGS : -march=native -mtune=native -O3 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -Wp,-D_GLIBCXX_ASSERTIONS -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now + QEMU_CFLAGS : -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fno-common -fwrapv -Wold-style-declaration -Wold-style-definition -Wtype-limits -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body -Wnested-externs -Wendif-labels -Wexpansion-to-defined -Wimplicit-fallthrough=2 -Wno-missing-include-dirs -Wno-shift-negative-value -Wno-psabi -fstack-protector-strong + QEMU_LDFLAGS : -Wl,--warn-common -Wl,-z,relro -Wl,-z,now -fstack-protector-strong + profiler : NO + link-time optimization (LTO) : NO + PIE : YES + static build : NO + malloc trim support : YES + membarrier : NO + debug stack usage : NO + mutex debugging : NO + memory allocator : system + avx2 optimization : YES + avx512f optimization : NO + gprof enabled : NO + gcov : NO + thread sanitizer : NO + CFI support : NO + strip binaries : NO + sparse : NO + mingw32 support : NO + x86_64 tests : gcc + + Targets and accelerators + KVM support : YES + HAX support : NO + HVF support : NO + WHPX support : NO + NVMM support : NO + Xen support : NO + TCG support : YES + TCG backend : native (x86_64) + TCG plugins : YES + TCG debug enabled : NO + target list : x86_64-softmmu x86_64-linux-user aarch64-softmmu aarch64-linux-user ppc64-softmmu ppc64-linux-user riscv32-softmmu riscv32-linux-user riscv64-softmmu riscv64-linux-user arm-softmmu arm-linux-user avr-softmmu + default devices : YES + out of process emulation : YES + + Block layer support + coroutine backend : ucontext + coroutine pool : YES + Block whitelist (rw) : + Block whitelist (ro) : + Use block whitelist in tools : NO + VirtFS support : YES + build virtiofs daemon : YES + Live block migration : YES + replication support : YES + bochs support : YES + cloop support : YES + dmg support : YES + qcow v1 support : YES + vdi support : YES + vvfat support : YES + qed support : YES + parallels support : YES + FUSE exports : YES 3.10.5 + + Crypto + TLS priority : "NORMAL" + GNUTLS support : YES 3.7.3 + GNUTLS crypto : YES + libgcrypt : NO + nettle : NO + crypto afalg : NO + rng-none : NO + Linux keyring : YES + + Dependencies + SDL support : YES + SDL image support : YES 2.0.5 + GTK support : YES + pixman : YES 0.40.0 + VTE support : YES 0.66.2 + slirp support : YES 4.6.1 + libtasn1 : YES 4.18.0 + PAM : YES + iconv support : YES + curses support : YES + virgl support : YES 0.9.1 + curl support : YES 7.81.0 + Multipath support : NO + VNC support : YES + VNC SASL support : YES + VNC JPEG support : YES 2.1.2 + VNC PNG support : YES 1.6.37 + OSS support : YES + ALSA support : YES 1.2.6.1 + PulseAudio support : YES 15.0 + JACK support : NO + brlapi support : NO + vde support : YES + netmap support : NO + l2tpv3 support : YES + Linux AIO support : YES + Linux io_uring support : YES 2.0 + ATTR/XATTR support : YES + RDMA support : NO + PVRDMA support : NO + fdt support : system + libcap-ng support : YES + bpf support : YES 0.7.0 + spice protocol support : YES 0.14.4 + spice server support : YES 0.15.0 + rbd support : NO + smartcard support : YES 2.7.0 + U2F support : NO + libusb : YES 1.0.25 + usb net redir : YES 0.12.0 + OpenGL support : YES + GBM : YES 21.3.1 + libiscsi support : YES 1.19.0 + libnfs support : YES 5.0.1 + seccomp support : YES 2.5.3 + GlusterFS support : NO + TPM support : YES + libssh support : YES 0.9.6 + lzo support : YES + snappy support : YES + bzip2 support : YES + lzfse support : NO + zstd support : YES 1.5.2 + NUMA host support : YES + capstone : internal + libpmem support : NO + libdaxctl support : YES 72.1+ + libudev : YES 250 + FUSE lseek : YES + selinux : NO + + Subprojects + libvhost-user : YES + + User defined options + Native files : config-meson.cross + bindir : /usr/bin + datadir : /usr/share + debug : true + includedir : /usr/include + libdir : /usr/lib + libexecdir : /usr/lib/qemu + localedir : /usr/share/locale + localstatedir : /var + mandir : /usr/share/man + optimization : 2 + prefix : /usr + sysconfdir : /etc + werror : false + b_coverage : false + b_lto : false + b_pie : true + audio_drv_list : default + capstone : auto + cfi : false + default_devices : true + docdir : /usr/share/doc + fdt : auto + qemu_firmwarepath : /usr/share/qemu-firmware + qemu_suffix : qemu + sdl : enabled + slirp : system + sphinx_build : + tcg : enabled + trace_file : trace + xen : disabled + +Found ninja-1.10.2 at /usr/bin/ninja +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/883 b/gitlab/issues_text/target_missing/host_missing/accel_missing/883 new file mode 100644 index 000000000..19a138388 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/883 @@ -0,0 +1,27 @@ +DRBG: could not allocate CTR cipher TFM handle: ctr(aes) +Description of problem: + +Steps to reproduce: +1. Install Debian in Qemu using the command: +``` +REM example to create disk +REM qemu-img create -f qcow2 debian-qcow2.img 32G + +qemu-system-x86_64.exe -hda debian-qcow2.img -cdrom debian-11.2.0-amd64-netinst.iso -boot d -m 8G -accel hax +``` + +2. Fight with installer and partitions to finally get this: + + +3. System boots and shows a bunch of FAILED messages with crypto error: + + + + +I am new at using Qemu so may need pointers to provide more information. + +The system seems to be working to some degree. + +Color me impressed!!! +Additional information: +Related: #880 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/884 b/gitlab/issues_text/target_missing/host_missing/accel_missing/884 new file mode 100644 index 000000000..087503a4e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/884 @@ -0,0 +1,8 @@ +Stuck when using virtio driver to rotate the screen +Description of problem: +Configure the virtual machine's graphics card as Virtio, and use `xrandr -o left` to rotate the screen and it will get stuck. + +Configure the graphics card as VGA, and use `xrandr -o left` to rotate the screen normally. +Steps to reproduce: +1. Configure the virtual machine's graphics card as Virtio +2. use `xrandr -o left` to rotate the screen diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/885 b/gitlab/issues_text/target_missing/host_missing/accel_missing/885 new file mode 100644 index 000000000..630e91076 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/885 @@ -0,0 +1 @@ +linux-user: `getsockopt` on `SO_RCVTIMEO_NEW`/`SO_SNDTIMEO_NEW` writes unexpected `int` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/889 b/gitlab/issues_text/target_missing/host_missing/accel_missing/889 new file mode 100644 index 000000000..3ab04cbfa --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/889 @@ -0,0 +1 @@ +cc1: error: ‘-fcf-protection’ is not compatible with this target diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/89 b/gitlab/issues_text/target_missing/host_missing/accel_missing/89 new file mode 100644 index 000000000..c8fbd900d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/89 @@ -0,0 +1 @@ +Documentation for mtdblock, option-rom, and pflash is non-existent diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/891 b/gitlab/issues_text/target_missing/host_missing/accel_missing/891 new file mode 100644 index 000000000..4b2788640 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/891 @@ -0,0 +1 @@ +how to know jpeg-wan-compression is in force diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/892 b/gitlab/issues_text/target_missing/host_missing/accel_missing/892 new file mode 100644 index 000000000..921b114f6 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/892 @@ -0,0 +1,5 @@ +Ensure qemu-storage-daemon builds, works and is included in win10 setup +Additional information: +- Job run on 20220315 "msys2-64bit build target" seems to have created binary: https://gitlab.com/qemu-project/qemu/-/jobs/2201739711 + - ```2456 [1324/1586] Linking target storage-daemon/qemu-storage-daemon.exe``` + - I hope it will be included in final distributed setup files diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/894 b/gitlab/issues_text/target_missing/host_missing/accel_missing/894 new file mode 100644 index 000000000..c501d480c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/894 @@ -0,0 +1,31 @@ +target/riscv64 qemu-iotests 040 failed +Description of problem: +I cross-compiled a riscv64 QEMU flavor based on the most updated code, then make check. Some qemu-iotests failed, 040 041 127 256 267. I mainly focused on test 040 and tried to find out what happened. +Steps to reproduce: +1. change directory to QEMU source tree root +2. ./configure --prefix=~/temp --target-list=riscv64-softmmu +3. make +4. cd build/tests/qemu-iotests/ +5. ./check -qcow2 040 + +Then a lot of error messages(please see attachment). The following log might hint the root cause I thought: +``` ++ Command: /home/qemu/qemu/build/tests/qemu-iotests/../../qemu-system-riscv64 -display none -vga none -chardev socket,id=mon,path=/tmp/tmpwhnx3jq0/qemu-28363-monitor.sock -mon chardev=mon,mode=control -qtest unix:path=/tmp/tmpwhnx3jq0/qemu-28363-qtest.sock -accel qtest -nodefaults -display none -accel qtest -drive if=none,id=drive0,file=/home/qemu/qemu/build/tests/qemu-iotests/scratch/test.img,format=qcow2,cache=writeback,aio=threads,node-name=top,backing.node-name=mid,backing.backing.node-name=base -device virtio-scsi -device scsi-hd,id=scsi0,drive=drive0 ++ Output: [I 1646574338.669217] OPENED ++qemu-system-riscv64: -device virtio-scsi: No 'PCI' bus found for device 'virtio-scsi-pci' +``` +The command had no '-machine' argument. For riscv64 target, 'spike' will be the default machine. Maybe 'spike' have no PCI bus? Then I tried to change it to 'virt' machine but failed, nothing new happen. +``` +QEMU_DEFAULT_MACHINE=virt ./check -qcow2 040 +``` +``` +QEMU_OPTIONS="-machine virt" ./check -qcow2 040 +``` +Last, I modified [testenv.py](https://gitlab.com/qemu-project/qemu/-/blob/master/tests/qemu-iotests/testenv.py#L239) and added one line in machine-map, all tests passed! +``` +('riscv64', 'virt'), +``` + +Is there any way to easy the issue or do I miss something? Thank you! +Additional information: +[zlog.riscv.xz](/uploads/cbbad7c5c256d2b49d220aa6425e2b17/zlog.riscv.xz) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/895 b/gitlab/issues_text/target_missing/host_missing/accel_missing/895 new file mode 100644 index 000000000..27f449a42 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/895 @@ -0,0 +1,38 @@ +can't find table device while call qemu_input_is_absolute function +Description of problem: +vnc service can‘t run with mouse absolute mode +Steps to reproduce: +1.create a virtual machine with vnc service via virt-manager. + +2.delete mouse and table device if exists. + +3.add table devices first,next add mouse device. + +4.gdb attach corresponding qemu thread, run command +print "%d",qemu_input_is_absolute() +display function return false ,so I can't use mouse with absolute mode. +Additional information: +code in qemu_input_is_absolute() is +``` +bool qemu_input_is_absolute(void) +{ + QemuInputHandlerState *s; + + s = qemu_input_find_handler(INPUT_EVENT_MASK_REL | INPUT_EVENT_MASK_ABS, + NULL); + return (s != NULL) && (s->handler->mask & INPUT_EVENT_MASK_ABS); +} +``` +qemu_input_find_handler function find a handler INPUT_EVENT_MASK_REL or INPUT_EVENT_MASK_ABS,but just compare with INPUT_EVENT_MASK_ABS, +I think it should be +``` +bool qemu_input_is_absolute(void) +{ + QemuInputHandlerState *s; + + s = qemu_input_find_handler(INPUT_EVENT_MASK_ABS, + NULL); + return (s != NULL) && (s->handler->mask & INPUT_EVENT_MASK_ABS); +} +``` +thanks for your help. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/90 b/gitlab/issues_text/target_missing/host_missing/accel_missing/90 new file mode 100644 index 000000000..73cf9a18d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/90 @@ -0,0 +1 @@ +vga/std lacks few wide screen modes. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/900 b/gitlab/issues_text/target_missing/host_missing/accel_missing/900 new file mode 100644 index 000000000..54801f632 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/900 @@ -0,0 +1 @@ +how to install gemu guest agent without configure script ? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/901 b/gitlab/issues_text/target_missing/host_missing/accel_missing/901 new file mode 100644 index 000000000..9887c8a05 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/901 @@ -0,0 +1,10 @@ +Bad screen behavior with adaptive sync +Description of problem: +KDE Wayland has freesync automatically enabled for full screen applications[[1]](https://wiki.archlinux.org/title/Variable_refresh_rate#Wayland_configuration). When using a VM in full screen mode, the screen starts having a strange behavior, like "blinking". I've tried windows 10, Linux Mint, MX Linux and Ubuntu 21.10. +The problem disappears if using Xorg or disabling freesync trough KDE settings. +Steps to reproduce: +1. On KDE Wayland, check if freesync is activated in settings> screen> adaptive synchronization +2. Launch any vm in fuul screen mode +3. Observe the screen +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/905 b/gitlab/issues_text/target_missing/host_missing/accel_missing/905 new file mode 100644 index 000000000..70e590984 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/905 @@ -0,0 +1 @@ +Null-ptr dereference in blk_bs diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/907 b/gitlab/issues_text/target_missing/host_missing/accel_missing/907 new file mode 100644 index 000000000..c8a2d736e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/907 @@ -0,0 +1,7 @@ +qemu-system-x86_64 -blockdev fails with "CURL: Error opening file" when supplied url of ISO file +Steps to reproduce: +1. Run: qemu-system-x86_64 -blockdev driver=https,url=https://archive.fedoraproject.org:443/pub/archive/fedora/linux/releases/28/Server/x86_64/os/images/boot.iso,node-name=libvirt-1-storage,auto-read-only=true + +The command returns error: qemu-system-x86_64: -blockdev driver=https,url=https://archive.fedoraproject.org:443/pub/archive/fedora/linux/releases/28/Server/x86_64/os/images/boot.iso,node-name=libvirt-1-storage,auto-read-only=true,discard=unmap: CURL: Error opening file: +Additional information: +This bug is not present in qemu 6.1.0, it surfaced with an update to 6.2.0 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/908 b/gitlab/issues_text/target_missing/host_missing/accel_missing/908 new file mode 100644 index 000000000..3b844642c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/908 @@ -0,0 +1 @@ +since when is qemu-guest-agent included in the qemu package ? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/911 b/gitlab/issues_text/target_missing/host_missing/accel_missing/911 new file mode 100644 index 000000000..675a31b17 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/911 @@ -0,0 +1,17 @@ +Unable to strace execve calls in mipsel user mode +Description of problem: +Used 6.2.0 ZIP and git to build, configured with +``` +./configure --target-list=mipsel-linux-user --static --disable-system --enable-linux-user +``` + +When trying to strace a mipsel-arch application, I cannot see traces for the `execve` syscall. It looks like the call to `safe_execve` is not returning, so the strace printout is never completed. I'm assuming this has to do with `execve` syscall not returning on success, but older versions appeared to be able to do it. I tried it with QEMU 4.2.1 from the package manager on Ubuntu and I saw the `execve` syscall (see qemu-4.2.1.log). +Steps to reproduce: +1. Build mipsel app: ` mipsel-linux-gnu-gcc -o test.mipsel test.c` (Test code is attached as `test.c`) +2. Run qemu-mipsel: `./build/qemu-mipsel -L /usr/mipsel-linux-gnu/ -strace ../test.mipsel` +3. Note that even though the app uses both `system` and `popen` to create subprocesses, no `execve` syscall is shown in the strace output. +Additional information: +[qemu-6.2.90.log](/uploads/ca03e6f40b3b0ea79a042786a123760a/qemu-6.2.90.log) +[qemu-6.2.0.log](/uploads/ca15057398377d49b396e9e77a5cb639/qemu-6.2.0.log) +[qemu-4.2.1.log](/uploads/1087250dd9fc4d8d106d2cbc58c2b14a/qemu-4.2.1.log) +[test.c](/uploads/9d242a724b10b296cfd7a945ae4d6c4d/test.c) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/912 b/gitlab/issues_text/target_missing/host_missing/accel_missing/912 new file mode 100644 index 000000000..0c155c123 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/912 @@ -0,0 +1 @@ +Cannot access RHEL8_s390x installed OS using SSH from host OS network diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/913 b/gitlab/issues_text/target_missing/host_missing/accel_missing/913 new file mode 100644 index 000000000..5690f280d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/913 @@ -0,0 +1 @@ +QEMU Sharing Host files with Guest diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/917 b/gitlab/issues_text/target_missing/host_missing/accel_missing/917 new file mode 100644 index 000000000..01b8b1c03 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/917 @@ -0,0 +1 @@ +FireWire Device Passthrough? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/918 b/gitlab/issues_text/target_missing/host_missing/accel_missing/918 new file mode 100644 index 000000000..cd3ecea52 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/918 @@ -0,0 +1 @@ +TILE Cpu Host & Emulator support? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/919 b/gitlab/issues_text/target_missing/host_missing/accel_missing/919 new file mode 100644 index 000000000..4a5447986 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/919 @@ -0,0 +1,5 @@ +Slow in Windows +Description of problem: +Eg . Win8.1 in QEMU on Windows is very slow and other os also are very slow +Steps to reproduce: +Just run a qemu instance diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/92 b/gitlab/issues_text/target_missing/host_missing/accel_missing/92 new file mode 100644 index 000000000..c6188f1a4 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/92 @@ -0,0 +1 @@ +qemu 1.3.0: usb devices shouldn't have same vendor/product ID and same serial diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/926 b/gitlab/issues_text/target_missing/host_missing/accel_missing/926 new file mode 100644 index 000000000..118354df6 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/926 @@ -0,0 +1 @@ +block-backend assertion with Cocoa UI diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/927 b/gitlab/issues_text/target_missing/host_missing/accel_missing/927 new file mode 100644 index 000000000..9d3d21a31 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/927 @@ -0,0 +1,32 @@ +linux-user: openat on /proc/self/exe can return a closed file descriptor +Description of problem: +`open("/proc/self/exe", ...)` returns a closed file descriptor if qemu-user was executed as an interpreter, passing a file descriptor in the `AT_EXECFD` auxval. + +When the `AT_EXECFD` auxval is nonzero the user program is loaded through `load_elf_binary()` (in `linux-user/elfload.c`) which ultimately calls `load_elf_image()` with that same file descriptor, and `load_elf_image()` closes the file descriptor before returning. + +`do_openat` in `linux-user/syscall.c` will return that file descriptor to the user if the opened path satisfies `is_proc_myself(pathname, "exe")`, which is obviously wrong both in that the file descriptor is closed as part of the initialization process of qemu itself, and that the user program would then close that file descriptor and thus the next invocation of `open` would have the same problem. +Steps to reproduce: +This program prints `3 3` in a x86_64 docker container on my machine (arm64 macos, which docker desktop handles by running containers in a native linux VM under qemu-user). + +```c +#include <fcntl.h> +#include <stdio.h> + +int main(int argc, char **argv) { + int selfexe = open("/proc/self/exe", O_RDONLY | O_CLOEXEC); + if (selfexe < 0) { + perror("open self"); + return 1; + } + + int devnull = open("/dev/null", O_WRONLY | O_CLOEXEC); + if (devnull < 0) { + perror("open devnull"); + return 1; + } + + printf("%d %d\n", selfexe, devnull); +} +``` +Additional information: +Thanks to @pm215 for helping me pinpoint the exact issue I was encountering. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/929 b/gitlab/issues_text/target_missing/host_missing/accel_missing/929 new file mode 100644 index 000000000..45ab9e1f1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/929 @@ -0,0 +1,33 @@ +qemu-user syscall clone fails +Description of problem: +This seems very similar to the issue reported here (https://bugs.launchpad.net/qemu/+bug/1926996). When attempting to perform the clone syscall, an error of -1 is returned where I would expect it to succeed. Running the same executable outside of qemu works as expected. +Steps to reproduce: +1. gcc clone.c +2. qemu-x86_64 a.out +Additional information: +I've tried building with gcc, zig cc, and clang and the output of each works fine when running natively, but running under qemu fails. I originally discovered it when cross compiling to riscv64 but it doesn't seem to be limited to that architecture. + +``` +// clone.c + +#include <linux/sched.h> +#include <sched.h> +#include <sys/syscall.h> +#include <unistd.h> +#include <stdio.h> + +int main(void) { + + long pid = syscall( SYS_clone, 0, 0, 0, 0, 0 ); + + if (pid < 0) { + printf( "error %ld\n", pid ); + } else if (pid == 0) { + printf( "child %ld\n", pid ); + } else { + printf( "parent %ld\n", pid ); + } + + return 0; +} +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/93 b/gitlab/issues_text/target_missing/host_missing/accel_missing/93 new file mode 100644 index 000000000..8a9fa56b5 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/93 @@ -0,0 +1 @@ +qemu 1.4.2: usb keyboard not fully working diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/931 b/gitlab/issues_text/target_missing/host_missing/accel_missing/931 new file mode 100644 index 000000000..79a73839d --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/931 @@ -0,0 +1 @@ +Create GitLab 7.1 milestone diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/932 b/gitlab/issues_text/target_missing/host_missing/accel_missing/932 new file mode 100644 index 000000000..a73014e88 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/932 @@ -0,0 +1,14 @@ +Snapshot created with 6.2.0 cannot be loaded with 7.0.0-rc1 +Description of problem: +Loading the snapshot will fail with: + +```` +qemu-system-x86_64: Missing section footer for 0000:00:01.3/piix4_pm +qemu-system-x86_64: Error -22 while loading VM state +```` +Steps to reproduce: +1. Start VM with `6.2.0`. +2. Create a snapshot `takenwith620` with `snapshot-save` QMP command. +3. Stop VM and try to load snapshot with `v7.0.0-rc1`. +Additional information: +Bisecting led to `5ead62185d ("memory: Make memory_region_is_mapped() succeed when mapped via an alias")`, but reverting that alone wasn't enough, so I continued and got to `7c0fa8dff8 ("pcie: Add support for Single Root I/O Virtualization (SR/IOV)")`. Only reverting both seems to fix the issue. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/933 b/gitlab/issues_text/target_missing/host_missing/accel_missing/933 new file mode 100644 index 000000000..3ca0949a9 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/933 @@ -0,0 +1,26 @@ +Changing CD ROM medium sometimes fails with 'Tray of device is not open' +Description of problem: +QEMU reports that a CD ROM tray is not open when exchanging media: +`unable to execute QEMU command 'blockdev-remove-medium': Tray of device 'ide0-1-0' is not open` + +We see the issue in upstream libvirt integration tests. However, this issue is a race and the reproducibility rate is <15%. +Steps to reproduce: +On the high level this is what we do: +1. eject medium that the machine was started with +2. insert a different medium into the CD ROM + +Translating the above to QEMU QMP commands this is what the test exercises: +1. blockdev-open-tray +2. blockdev-remove-medium +3. blockdev-del +4. blockdev-close-tray +5. blockdev-open-tray +6. blockdev-remove-medium +7. blockdev-add +8. blockdev-insert-medium <<< This is where the test fails +9. blockdev-close-tray +Additional information: +I bisected the code (3 times just to be sure since it's a race) and the following commit fell out of it: +55adb3c45620c31f29978f209e2a44a08d34e2da + +I'm attaching QEMU trace events and a bunch of libvirt test logs (good and bad for comparison). If you think of anything else I should provide in order to help with the issue analysis, please let me know what other option should be turned on.[qemu_traces.tar.gz](/uploads/32e48c92efce3484e552df063795af4d/qemu_traces.tar.gz) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/935 b/gitlab/issues_text/target_missing/host_missing/accel_missing/935 new file mode 100644 index 000000000..899aaf0b6 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/935 @@ -0,0 +1,59 @@ +insert ivshmem device into pci-bridge, but vm network disconnects +Description of problem: +To extend PCI slot number in Windows vm, a new pci-bridge is created in Windows vm as bus.1. But when I insert a ivshmem file in host to this pci-bridge(bus.1), the Windows vm disconnects(lose remote desktop connection). +Steps to reproduce: +1. add new pci-bridge into windows vm, add windows vm xml configuration like this: +```xml +<devices> + <controller type='pci' index='0' model='pci-root'/> + <controller type='pci' index='1' model='pci-bridge'> + <address type='pci' domain='0' bus='0' slot='0x0d' function='0' multifunction='off'/> + </controller> +</devices> +``` + +2.restart this Windows vm, new pci-bridge has been created, its name is pci.1 and bus is bus.1: +```sh +$ virsh qemu-monitor-command --hmp --domain 56 --cmd info pci + Bus 0, device 13, function 0: + PCI bridge: PCI device 1b36:0001 + IRQ 10. + BUS 0. + secondary bus 1. + subordinate bus 1. + IO range [0xc000, 0xcfff] + memory range [0xfe000000, 0xfe1fffff] + prefetchable memory range [0xe4000000, 0xe41fffff] + BAR0: 64 bit memory at 0xfe422000 [0xfe4220ff]. + id "pci.1" +``` +3. create a shm file `/dev/shm/test1` in host using `shm_open()`, size is 32M + +4. create new object: +```sh +virsh qemu-monitor-command --hmp --domain 56 --cmd object_add memory-backend-file,share=on,id=objtest1,size=32M,mem-path=/dev/shm/test1 +``` + +5. insert this ivshmem file into new pci-bridge and use bus.1 slot number(1:1.0): +```sh +virsh qemu-monitor-command --hmp --domain 56 --cmd device_add ivshmem-plain,memdev=objtest1,id=test1,bus=pci.1,addr=0x01.0x00 +``` + +6. After inserting this ivshmem file into new pci-bridge, the remote desktop connection of this windows vm disconnects. + +7. New ivshmem file has been created: +``` +$ virsh qemu-monitor-command --hmp --domain 57 --cmd info pci + Bus 1, device 1, function 0: + RAM controller: PCI device 1af4:1110 + BAR0: 32 bit memory at 0xfe1fff00 [0xfe1fffff]. + BAR2: 64 bit prefetchable memory at 0x4bc000000 [0x4bfffffff]. + id "test1" + +``` +Additional information: +When insert ivshmem file into bus.1(pci-bridge), the remote desktop connection of Windows vm is sometimes disconnected, and sometimes it is normal. + +The newly added ivshmem device can be found in the device manager of the Windows vm, but sometimes it cannot be found. + +Thanks for your help! diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/936 b/gitlab/issues_text/target_missing/host_missing/accel_missing/936 new file mode 100644 index 000000000..a78153ebb --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/936 @@ -0,0 +1,16 @@ +Serial output mangled in terminal +Description of problem: +My hobby OS uses the serial port at `0x3f8` to log messages to QEMU's stdout. This used to work fine, I can even emit ANSI escape codes to get color output and it renders in my terminal as expected. I left this project for about a year and just returned to it with the latest version of QEMU. Now, all of the QEMU serial output from my OS in the terminal seems to be missing carriage returns and buffering strangely. It's as if every log line ends up on the same line in the stdout buffer, but with newlines (without returning to the start of the line) between them. For example (these aren't my real logs but demonstrate the issue): +``` +[KERNEL] startup + [KERNEL] initializing heap + [KERNEL] initializing drivers + [KERNEL] ready! +``` +Also, when QEMU exits, I notice that my shell indicates that the last command's output didn't end in a newline which is strange. + +I tried debugging this myself by piping the output to a file and inspecting it in a hex editor, but it looks like just normal newlines in the output. I tried piping the output to `tr '\n' '\r\n'` to add carriage returns, but that ends up rendering all the output on a single line which resets to the first column every line. I tried sending the output to a file and watching the file, but it seems to get buffered and the data only shows up once QEMU exits. My best guess is that the output hasn't changed, but this new version of QEMU is changing some kind of buffering setting on its output which is causing this, but I'm really not sure what's going on. +Steps to reproduce: +I can provide the boot image if that would be helpful to reproduce. +Additional information: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/937 b/gitlab/issues_text/target_missing/host_missing/accel_missing/937 new file mode 100644 index 000000000..654f53ea1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/937 @@ -0,0 +1,68 @@ +I/O errors occur when qcow2 files created via gluster fuse mount are accessed via libgfapi (gluster://) +Description of problem: +Environment: a Gluster volume 'v0' (Gluster versions tested were 9.2-1 and 10.1) is built on 3 nodes on top of 3 ZFS pools. It is mounted to check fuse mount functionality. Mount point is `/mnt/gl`. +When an empty qcow2 is created via fuse mount (qemu-img create -f qcow2 /mnt/gl/123.qcow2 10G) and then this qcow2 is attached to qemu guest -- error appears: +``` +qemu-system-x86_64: -blockdev {"node-name":"libvirt-2-format","read-only":false,"cache":{"direct":true,"no-flush":false},"driver":"qcow2","file":"libvirt-2-storage","backing":null}: Could not read L1 table: Input/output error +``` +When the same file is attached to qemu guest via fuse mount there is no error. When the same file is created via GFAPI (gluster://) there is no error too. +Steps to reproduce: +1. Create file via fuse-mount: `qemu-img create -f qcow2 /mnt/gl/123.qcow2 10G` +2. Attach this file via gluster:// to qemu guest and observe an error +3. Attach this file via fuse mount, run a guest -- no error. +4. Create file via gluster:// : `qemu-img create -f qcow2 gluster://v0/234.qcow2 10g` +5. Attach this file (via GFAPI or via fuse mount) to qemu guest and run guest -- there is no error. +Additional information: +When an empty qcow2 file with virtual size 10G with default cluster size is created, its proper size is 196768 (0x300a0) bytes. If file is created via fuse mount, that is true and file size is 0x300a0 bytes. +In the end of file L1 table resides, its offset is 0x30000 and size is 0xa0. When this qcow2 is attached via fuse mount it seems that i/o requests are conforming to file size and file is read without errors. +But when file with size 0x300a0 is attached via gluster://, qemu aligns i/o requests by 0x200 bytes boundary (see dump below, frame #12. NB: dump is taken from qemu-img create cmd so there are write requests). Thus, request goes beyond the file end and read error occurs. + +When file is created via gluster:// its size is 197120 (0x30200) bytes because write requests are aligned to 512 bytes too. And guest runs normally with it regardless of connection type. + +``` +Thread 1 "qemu-img" hit Breakpoint 1, 0x00007fffec014f10 in ec_gf_writev () from /usr/lib64/glusterfs/11dev/xlator/cluster/disperse.so +(gdb) bt +#0 0x00007fffec014f10 in ec_gf_writev () from /usr/lib64/glusterfs/11dev/xlator/cluster/disperse.so +#1 0x00007ffff68eeea6 in default_writev () from /lib64/libglusterfs.so.0 +#2 0x00007ffff4024ab8 in gf_utime_writev (frame=0x555556126aa8, this=0x7fffe40113d8, fd=0x555556126b88, vector=0x555556130868, count=1, off=196608, flags=0, iobref=0x555556130608, xdata=0x0) at utime-autogen-fops.c:81 +#3 0x00007ffff68eeea6 in default_writev () from /lib64/libglusterfs.so.0 +#4 0x00007ffff4013c39 in ob_writev (frame=frame@entry=0x555556126aa8, this=0x7fffe4012408, fd=fd@entry=0x555556126b88, iov=iov@entry=0x555556130868, count=count@entry=1, offset=offset@entry=196608, flags=0, + iobref=0x555556130608, xdata=0x0) at open-behind.c:584 +#5 0x00007fffdff37774 in mdc_writev (frame=frame@entry=0x5555561522d8, this=0x7fffe40139e8, fd=fd@entry=0x555556126b88, vector=vector@entry=0x555556130868, count=count@entry=1, offset=offset@entry=196608, flags=0, + iobref=0x555556130608, xdata=0x0) at md-cache.c:2151 +#6 0x00007fffdff143fb in io_stats_writev (frame=0x55555611dc08, this=0x7fffe4015468, fd=0x555556126b88, vector=0x555556130868, count=1, offset=196608, flags=0, iobref=0x555556130608, xdata=0x0) at io-stats.c:2952 +#7 0x00007ffff68eeea6 in default_writev () from /lib64/libglusterfs.so.0 +#8 0x00007fffdfee88ca in meta_writev (frame=0x55555611dc08, this=0x7fffe40173d8, fd=0x555556126b88, iov=0x555556130868, count=1, offset=196608, flags=0, iobref=0x555556130608, xdata=0x0) at meta.c:131 +#9 0x00007ffff6942f22 in glfs_pwritev_async_common () from /lib64/libgfapi.so.0 +#10 0x00007ffff69462f6 in glfs_pwritev_async () from /lib64/libgfapi.so.0 +#11 0x00007ffff7fc5839 in qemu_gluster_co_writev () from /usr/lib64/qemu/block-gluster.so +#12 0x0000555555623b7e in bdrv_driver_pwritev (bs=bs@entry=0x55555611eda0, offset=offset@entry=196608, bytes=bytes@entry=512, qiov=qiov@entry=0x7ffff5e9cb40, qiov_offset=qiov_offset@entry=0, flags=flags@entry=0) + at /usr/src/debug/qemu-5.1.0-9.fc33.x86_64/block/io.c:1243 +#13 0x00005555556244d2 in bdrv_aligned_pwritev (child=child@entry=0x55555611e3a0, req=req@entry=0x7ffff5e9ca80, offset=196608, bytes=512, align=align@entry=512, qiov=0x7ffff5e9cb40, qiov_offset=0, flags=0) + at /usr/src/debug/qemu-5.1.0-9.fc33.x86_64/block/io.c:2020 +#14 0x0000555555625433 in bdrv_co_pwritev_part (child=0x55555611e3a0, offset=<optimized out>, bytes=<optimized out>, qiov=<optimized out>, qiov_offset=<optimized out>, flags=0) + at /usr/src/debug/qemu-5.1.0-9.fc33.x86_64/block/io.c:2188 +#15 0x00005555556267a0 in bdrv_run_co (opaque=0x7ffff5e9cbb0, entry=0x5555556260a0 <bdrv_rw_co_entry>, bs=0x55555611eda0) at /usr/src/debug/qemu-5.1.0-9.fc33.x86_64/block/io.c:915 +#16 bdrv_prwv_co (flags=0, is_write=true, qiov=0x7ffff5e9cbd0, offset=196608, child=0x55555611e3a0) at /usr/src/debug/qemu-5.1.0-9.fc33.x86_64/block/io.c:966 +#17 bdrv_pwritev (qiov=0x7ffff5e9cbd0, offset=196608, child=0x55555611e3a0) at /usr/src/debug/qemu-5.1.0-9.fc33.x86_64/block/io.c:1048 +#18 bdrv_pwrite (bytes=160, buf=0x555556116000, offset=196608, child=0x55555611e3a0) at /usr/src/debug/qemu-5.1.0-9.fc33.x86_64/block/io.c:1070 +#19 bdrv_pwrite_sync (child=0x55555611e3a0, offset=offset@entry=196608, buf=buf@entry=0x555556116000, count=count@entry=160) at /usr/src/debug/qemu-5.1.0-9.fc33.x86_64/block/io.c:1084 +#20 0x00005555555f60de in qcow2_grow_l1_table (bs=bs@entry=0x55555610d0a0, min_size=min_size@entry=20, exact_size=exact_size@entry=true) at /usr/src/debug/qemu-5.1.0-9.fc33.x86_64/block/qcow2-cluster.c:161 +#21 0x00005555555ec252 in qcow2_co_truncate (bs=0x55555610d0a0, offset=<optimized out>, exact=<optimized out>, prealloc=PREALLOC_MODE_OFF, flags=0, errp=0x7ffff5e9cfa0) + at /usr/src/debug/qemu-5.1.0-9.fc33.x86_64/block/qcow2.c:4172 +#22 0x000055555562758d in bdrv_co_truncate (child=0x55555617b290, offset=10737418240, exact=<optimized out>, prealloc=PREALLOC_MODE_OFF, flags=0, errp=0x7ffff5e9cfa0) + at /usr/src/debug/qemu-5.1.0-9.fc33.x86_64/block/io.c:3394 +#23 0x0000555555627a01 in bdrv_truncate_co_entry (opaque=0x7ffff5e9ceb0) at /usr/src/debug/qemu-5.1.0-9.fc33.x86_64/block/io.c:3437 +#24 bdrv_run_co (opaque=0x7ffff5e9ceb0, entry=0x555555627980 <bdrv_truncate_co_entry>, bs=0x55555610d0a0) at /usr/src/debug/qemu-5.1.0-9.fc33.x86_64/block/io.c:915 +#25 bdrv_truncate (child=<optimized out>, offset=<optimized out>, exact=<optimized out>, prealloc=<optimized out>, flags=flags@entry=0, errp=errp@entry=0x7ffff5e9cfa0) + at /usr/src/debug/qemu-5.1.0-9.fc33.x86_64/block/io.c:3453 +#26 0x0000555555611d32 in blk_truncate (blk=blk@entry=0x55555611e420, offset=<optimized out>, exact=exact@entry=false, prealloc=<optimized out>, flags=flags@entry=0, errp=errp@entry=0x7ffff5e9cfa0) + at /usr/src/debug/qemu-5.1.0-9.fc33.x86_64/block/block-backend.c:2184 +#27 0x00005555555e9a0f in qcow2_co_create (create_options=0x55555612c000, errp=errp@entry=0x7ffff5e9cfa0) at /usr/src/debug/qemu-5.1.0-9.fc33.x86_64/block/qcow2.c:3614 +#28 0x00005555555ea0ec in qcow2_co_create_opts (drv=<optimized out>, filename=<optimized out>, opts=0x5555557a3f90, errp=0x7ffff5e9cfa0) at /usr/src/debug/qemu-5.1.0-9.fc33.x86_64/block/qcow2.c:3795 +#29 0x00005555555bd631 in bdrv_create_co_entry (opaque=0x7fffffffdff0) at /usr/src/debug/qemu-5.1.0-9.fc33.x86_64/block.c:487 +#30 0x00005555556a7d8b in coroutine_trampoline (i0=<optimized out>, i1=<optimized out>) at /usr/src/debug/qemu-5.1.0-9.fc33.x86_64/util/coroutine-ucontext.c:173 +#31 0x00007ffff76a01c0 in ?? () at ../sysdeps/unix/sysv/linux/x86_64/__start_context.S:91 from /lib64/libc.so.6 +#32 0x00007fffffffd820 in ?? () +#33 0x0000000000000000 in ?? () +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/938 b/gitlab/issues_text/target_missing/host_missing/accel_missing/938 new file mode 100644 index 000000000..bd1485719 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/938 @@ -0,0 +1 @@ +Impossible to cross compile from Ubuntu or Debian to Windows with the tutorial diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/940 b/gitlab/issues_text/target_missing/host_missing/accel_missing/940 new file mode 100644 index 000000000..6d3d5ccbb --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/940 @@ -0,0 +1 @@ +"analyze-migration.py -m" does not appear to account for the pci-hole diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/941 b/gitlab/issues_text/target_missing/host_missing/accel_missing/941 new file mode 100644 index 000000000..1211f9670 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/941 @@ -0,0 +1,41 @@ +qemu-img cannot repair a qcow2 in an LV because size is mis-detected when qcow2 is on an LV +Description of problem: +This is RHEV with Tb's of VMs which need to be repaired due to a datacenter-wide (the real datacenter) power outage. + +Each of these VMs are on individual LVs but qemu-img check fails to perform repairs: + + +``` +ERROR cluster 24481205 refcount=0 reference=1 +ERROR cluster 24481206 refcount=0 reference=1 +Rebuilding refcount structure +ERROR writing refblock: No space left on device <============ +qemu-img: Check failed: No space left on device +``` + +Running qemu-img check or info on the LV (/dev/dm-*) works well but repairs cannot be completed: + +``` +# qemu-img info /dev/cdd4e215-8c6b-4877-b2be-fdba383e7eb0/fb32333b-2334-4e10-8c42-02bc97e826cc +image: /dev/cdd4e215-8c6b-4877-b2be-fdba383e7eb0/fb32333b-2334-4e10-8c42-02bc97e826cc +file format: qcow2 +virtual size: 1.5 TiB (1649267441664 bytes) +disk size: 0 B <================================ +cluster_size: 65536 +Format specific information: + compat: 1.1 + compression type: zlib + lazy refcounts: true + refcount bits: 16 + corrupt: false + extended l2: false +``` +Steps to reproduce: +1. Have a damaged VM with its qcow2 in an LV +2. run 'qemu-img check <device>' verify that it properly detects the blocks which need fixing. +3. run 'qemu-img check -r all <device>', it exits with 'no space left on device´ after a few seconds. +Additional information: +https://bugzilla.redhat.com/show_bug.cgi?id=1519071 + + +Here is one example: diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/943 b/gitlab/issues_text/target_missing/host_missing/accel_missing/943 new file mode 100644 index 000000000..fbd4a3ec0 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/943 @@ -0,0 +1 @@ +Calling get-fsinfo on a virtual machine does not include ZFS (zfsonlinux, debian guest tested) volumes diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/944 b/gitlab/issues_text/target_missing/host_missing/accel_missing/944 new file mode 100644 index 000000000..b2058d84f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/944 @@ -0,0 +1,28 @@ +9p virtfs issue under MacOS in 7.0.0-rc1 +Description of problem: +9p virtfs under MacOS has an issue with sed inline replacements (sed -i). +The issue somewhere in xattr I believe +Steps to reproduce: +1. /Users/sid/ is mounted via 9p virtfs from MacOS host +2. +``` +[core@localhost ~]$ sed -i 's/aaa/zzz/g' /Users/sid/q/123 +sed: preserving permissions for ‘/Users/sid/q/sed3MLMjp’: Protocol not supported +``` +Additional information: +strace part with error +``` +openat(AT_FDCWD, "/proc/thread-self/attr/fscreate", O_RDWR|O_CLOEXEC) = 5 +write(5, NULL, 0) = 0 +close(5) = 0 +newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=12, ...}, AT_EMPTY_PATH) = 0 +read(3, "qqq\nzzz\nsss\n", 8192) = 12 +newfstatat(4, "", {st_mode=S_IFREG|0600, st_size=0, ...}, AT_EMPTY_PATH) = 0 +read(3, "", 8192) = 0 +fchown(4, 501, 1000) = 0 +fgetxattr(3, "system.posix_acl_access", 0x7ffd6dbd18b0, 132) = -1 ENODATA (No data available) +newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=12, ...}, AT_EMPTY_PATH) = 0 +fsetxattr(4, "system.posix_acl_access", "\2\0\0\0\1\0\6\0\377\377\377\377\4\0\4\0\377\377\377\377 \0\4\0\377\377\377\377", 28, 0) = -1 EPROTONOSUPPORT (Protocol not supported) +fsetxattr(4, "system.posix_acl_access", "\2\0\0\0\1\0\6\0\377\377\377\377\4\0\4\0\377\377\377\377 \0\4\0\377\377\377\377", 28, 0) = -1 EPROTONOSUPPORT (Protocol not supported) +fchmod(4, 0100644) = 0 +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/945 b/gitlab/issues_text/target_missing/host_missing/accel_missing/945 new file mode 100644 index 000000000..eed71935e --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/945 @@ -0,0 +1,10 @@ +For QEMU 7.0.0-rc1, nbd-server-add fails with qcow2 image with iothread in migration context +Description of problem: +Upon adding the drive for NBD (via QMP), there is an error message +````kvm: ../block.c:3657: bdrv_open_child: Assertion `qemu_in_main_thread()' failed.```` +and then the process aborts. +Steps to reproduce: +1. Create image: `qemu-img create -f qcow2 /root/target-disk.qcow2 4G` +2. Start QEMU as mentioned above. +3. Issue `nbd-server-start` QMP command (I used type unix). +4. Issue `nbd-server-add` command for the single disk. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/946 b/gitlab/issues_text/target_missing/host_missing/accel_missing/946 new file mode 100644 index 000000000..127275555 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/946 @@ -0,0 +1,12 @@ +qemu-img can't create qcow2 file on nfs path，which report error(Image is not in qcow2 format) +Description of problem: +I mount a nfs disk on my host,and use qemu-img to create a qcow2 file on this nfs path,but it not work,i have no idea,This problem has come up before in red-hat community: +[BUGID:1817640](https://bugzilla.redhat.com/show_bug.cgi?id=1817640#) +Steps to reproduce: + + +**strace file:** +[qemu-img-strace.log](/uploads/85517b7550ba1ea459f85cfd37b74332/qemu-img-strace.log) + +See form this strace file,in the line 1077,we can see pread64 read result is empty,it casuse the error,but i don't know why the resulut is empty. + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/948 b/gitlab/issues_text/target_missing/host_missing/accel_missing/948 new file mode 100644 index 000000000..51f59d1f5 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/948 @@ -0,0 +1,32 @@ +7.0.0-rc1, -rc2 cannot build - config-poison.h is not generated +Description of problem: +`make` halts with: + +``` +[557/2583] Generating module_block.h with a custom command +[558/2583] Generating block-gen.c with a custom command +[559/2583] Generating x86_64-softmmu-gdbstub-xml.c with a custom command (wrapped by meson to capture output) +[560/2583] Compiling C object libpage-vary-common.a.p/page-vary-common.c.o +[561/2583] Generating trace-target_sparc.c with a custom command +[562/2583] Generating trace-target_s390x_kvm.c with a custom command +ninja: job failed: clang -m64 -mcx16 -Ilibpage-vary-common.a.p -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -flto -fcolor-diagnostics -Wall -Winvalid-pch -std=gnu11 -O2 -g -isystem /home/dummy/qemu-7.0.0-rc2/linux-headers -isystem linux-headers -iquote . -iquote /home/dummy/qemu-7.0.0-rc2 -iquote /home/dummy/qemu-7.0.0-rc2/include -iquote /home/dummy/qemu-7.0.0-rc2/disas/libvixl -iquote /home/dummy/qemu-7.0.0-rc2/tcg/i386 -pthread -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fno-common -fwrapv -Wold-style-definition -Wtype-limits -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body -Wnested-externs -Wendif-labels -Wexpansion-to-defined -Wno-initializer-overrides -Wno-missing-include-dirs -Wno-shift-negative-value -Wno-string-plus-int -Wno-typedef-redefinition -Wno-tautological-type-limit-compare -Wno-psabi -fstack-protector-strong -fsanitize=cfi-icall -fsanitize-cfi-icall-generalize-pointers -fPIE -fno-lto -fno-sanitize=cfi-icall -MD -MQ libpage-vary-common.a.p/page-vary-common.c.o -MF libpage-vary-common.a.p/page-vary-common.c.o.d -o libpage-vary-common.a.p/page-vary-common.c.o -c ../page-vary-common.c +In file included from ../page-vary-common.c:22: +In file included from /home/dummy/qemu-7.0.0-rc2/include/qemu/osdep.h:34: +/home/dummy/qemu-7.0.0-rc2/include/exec/poison.h:7:10: fatal error: 'config-poison.h' file not found +#include "config-poison.h" + ^~~~~~~~~~~~~~~~~ +1 error generated. +ninja: subcommand failed +make[1]: *** [Makefile:163: run-ninja] Error 1 +make[1]: Leaving directory '/home/dummy/qemu-7.0.0-rc2/build' +make: *** [GNUmakefile:11: all] Error 2 + +``` + +It seems that `config-poison.h` is not generated in `configure` and is not explicitly a dependency for some of necessary object file. +Steps to reproduce: +1. `docker pull alpine:3.15` +2. `docker build -t qemubad .` with the attached dockerfile +Additional information: +6.2.0 is good +7.0.0-rc0, 7.0.0-rc1, 7.0.0-rc2 exhibits the issue diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/950 b/gitlab/issues_text/target_missing/host_missing/accel_missing/950 new file mode 100644 index 000000000..49492139a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/950 @@ -0,0 +1,23 @@ +7.0.0-rc2 hw/9pfs/9p.h cannot find XATTR_SIZE_MAX +Description of problem: +``` +[844/2583] Compiling C object tests/qtest/qos-test.p/virtio-rng-test.c.o +ninja: job failed: clang -m64 -mcx16 -Itests/qtest/qos-test.p -Itests/qtest -I../tests/qtest -I. -Iqapi -Itrace -Iui -Iui/shader -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -flto -fcolor-diagnostics -Wall -Winvalid-pch -std=gnu11 -O2 -g -isystem /home/dummy/qemu-7.0.0-rc2/linux-headers -isystem linux-headers -iquote . -iquote /home/dummy/qemu-7.0.0-rc2 -iquote /home/dummy/qemu-7.0.0-rc2/include -iquote /home/dummy/qemu-7.0.0-rc2/disas/libvixl -iquote /home/dummy/qemu-7.0.0-rc2/tcg/i386 -pthread -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fno-common -fwrapv -Wold-style-definition -Wtype-limits -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body -Wnested-externs -Wendif-labels -Wexpansion-to-defined -Wno-initializer-overrides -Wno-missing-include-dirs -Wno-shift-negative-value -Wno-string-plus-int -Wno-typedef-redefinition -Wno-tautological-type-limit-compare -Wno-psabi -fstack-protector-strong -fsanitize=cfi-icall -fsanitize-cfi-icall-generalize-pointers -fPIE -MD -MQ tests/qtest/qos-test.p/virtio-9p-test.c.o -MF tests/qtest/qos-test.p/virtio-9p-test.c.o.d -o tests/qtest/qos-test.p/virtio-9p-test.c.o -c ../tests/qtest/virtio-9p-test.c +In file included from ../tests/qtest/virtio-9p-test.c:18: +/home/dummy/qemu-7.0.0-rc2/hw/9pfs/9p.h:497:2: error: Missing definition for P9_XATTR_SIZE_MAX for this host system +#error Missing definition for P9_XATTR_SIZE_MAX for this host system + ^ +1 error generated. +ninja: subcommand failed +make[1]: *** [Makefile:163: run-ninja] Error 1 +make[1]: Leaving directory '/home/dummy/qemu-7.0.0-rc2/build' +make: *** [GNUmakefile:11: all] Error 2 +The command '/bin/sh -c make -j"`grep -c '^processor' /proc/cpuinfo`"' returned a non-zero code: 2 + +``` +Steps to reproduce: +1. build with attached Dockerfile +Additional information: +This problem is introduced by lore.kernel.org/all/20220227223522.91937-7-wwcohen@gmail.com/ + +`XATTR_SIZE_MAX` is in `<linux/limits.h>` which is included by `9p.c` but not `9p.h`. However the `9p.h` checks existence of XATTR_SIZE_MAX, so any other file including `9p.h` would be illegal. This is clearly misplacement of header including. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/951 b/gitlab/issues_text/target_missing/host_missing/accel_missing/951 new file mode 100644 index 000000000..71d7ba4ae --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/951 @@ -0,0 +1,195 @@ +Build error +Description of problem: +``` +changing dir to build for make ""... +make[1]: Entering directory '/qemu-git/qemu/build' + GIT ui/keycodemapdb meson tests/fp/berkeley-testfloat-3 tests/fp/berkeley-softfloat-3 dtc capstone slirp +[1/1037] Generating ar with a custom command +[2/1037] Generating bepo with a custom command +[3/1037] Generating cz with a custom command +[4/1037] Generating da with a custom command +[5/1037] Generating de with a custom command +[6/1037] Generating de-ch with a custom command +[7/1037] Generating en-gb with a custom command +[8/1037] Generating en-us with a custom command +[9/1037] Generating es with a custom command +[10/1037] Generating et with a custom command +[11/1037] Generating fi with a custom command +[12/1037] Generating fo with a custom command +[13/1037] Generating fr-be with a custom command +[14/1037] Generating fr with a custom command +[15/1037] Generating fr-ca with a custom command +[16/1037] Generating fr-ch with a custom command +[17/1037] Generating hr with a custom command +[18/1037] Generating hu with a custom command +[19/1037] Generating is with a custom command +[20/1037] Generating it with a custom command +[21/1037] Generating ja with a custom command +[22/1037] Generating lt with a custom command +[23/1037] Generating mk with a custom command +[24/1037] Generating lv with a custom command +[25/1037] Generating nl with a custom command +[26/1037] Generating no with a custom command +[27/1037] Generating pt with a custom command +[28/1037] Generating pl with a custom command +[29/1037] Generating ru with a custom command +[30/1037] Generating pt-br with a custom command +[31/1037] Generating th with a custom command +[32/1037] Generating tr with a custom command +[33/1037] Compiling C object tests/fp/libtestfloat.a.p/berkeley-testfloat-3_source_genCases_i64.c.o +[34/1037] Compiling C object tests/fp/libtestfloat.a.p/berkeley-testfloat-3_source_genCases_common.c.o +[35/1037] Compiling C object tests/fp/libtestfloat.a.p/berkeley-testfloat-3_source_genCases_ui32.c.o +[36/1037] Compiling C object tests/fp/libtestfloat.a.p/berkeley-testfloat-3_source_random.c.o +[37/1037] Generating Test QAPI files with a custom command +[38/1037] Generating QAPI test (include) with a custom command +[39/1037] Compiling C object tests/fp/libtestfloat.a.p/berkeley-testfloat-3_source_uint128.c.o +[40/1037] Compiling C object tests/fp/libtestfloat.a.p/berkeley-testfloat-3_source_functions_common.c.o +[41/1037] Compiling C object tests/fp/libtestfloat.a.p/berkeley-testfloat-3_source_genCases_extF80.c.o +[42/1037] Compiling C object tests/fp/libtestfloat.a.p/berkeley-testfloat-3_source_functionInfos.c.o +[43/1037] Compiling C object tests/fp/libtestfloat.a.p/berkeley-testfloat-3_source_genCases_ui64.c.o +[44/1037] Compiling C object tests/fp/libtestfloat.a.p/berkeley-testfloat-3_source_genCases_f16.c.o +[45/1037] Compiling C object tests/fp/libtestfloat.a.p/berkeley-testfloat-3_source_genCases_i32.c.o +[46/1037] Generating edk2-i386-vars.fd with a custom command (wrapped by meson to capture output) +[47/1037] Compiling C object tests/fp/libtestfloat.a.p/berkeley-testfloat-3_source_uint128_inline.c.o +[48/1037] Compiling C object tests/fp/libtestfloat.a.p/berkeley-testfloat-3_source_standardFunctionInfos.c.o +[49/1037] Compiling C object tests/fp/libtestfloat.a.p/berkeley-testfloat-3_source_fail.c.o +[50/1037] Generating qemu-version.h with a custom command (wrapped by meson to capture output) +[51/1034] Compiling C object tests/fp/libtestfloat.a.p/berkeley-testfloat-3_source_genCases_f32.c.o +[52/1034] Compiling C object tests/fp/libsoftfloat.a.p/berkeley-softfloat-3_source_s_eq128.c.o +[53/1034] Compiling C object tests/fp/libtestfloat.a.p/berkeley-testfloat-3_source_genCases_writeTestsTotal.c.o +[54/1034] Compiling C object tests/fp/libtestfloat.a.p/berkeley-testfloat-3_source_genCases_f64.c.o +[55/1034] Generating edk2-x86_64-code.fd with a custom command (wrapped by meson to capture output) +[56/1034] Compiling C object tests/fp/libtestfloat.a.p/berkeley-testfloat-3_source_genCases_f128.c.o +[57/1034] Generating edk2-x86_64-secure-code.fd with a custom command (wrapped by meson to capture output) +[58/1034] Compiling C object libqemu-x86_64-softmmu.fa.p/hw_virtio_vhost-iova-tree.c.o +[59/1034] Compiling C object libqemu-x86_64-softmmu.fa.p/hw_virtio_vhost-shadow-virtqueue.c.o +[60/1034] Compiling C object libqemu-x86_64-softmmu.fa.p/hw_vfio_pci-quirks.c.o +FAILED: libqemu-x86_64-softmmu.fa.p/hw_vfio_pci-quirks.c.o +cc -m64 -mcx16 -Ilibqemu-x86_64-softmmu.fa.p -I. -I.. -Itarget/i386 -I../target/i386 -I../capstone/include/capstone -Iqapi -Itrace -Iui -Iui/shader -I/usr/include/pixman-1 -I/usr/include/spice-server -I/usr/include/spice-1 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -fdiagnostics-color=auto -Wall -Winvalid-pch -Werror -std=gnu11 -O2 -g -isystem /qemu-git/qemu/linux-headers -isystem linux-headers -iquote . -iquote /qemu-git/qemu -iquote /qemu-git/qemu/include -iquote /qemu-git/qemu/disas/libvixl -iquote /qemu-git/qemu/tcg/i386 -pthread -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fno-common -fwrapv -Wold-style-declaration -Wold-style-definition -Wtype-limits -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body -Wnested-externs -Wendif-labels -Wexpansion-to-defined -Wimplicit-fallthrough=2 -Wno-missing-include-dirs -Wno-shift-negative-value -Wno-psabi -fstack-protector-strong -fPIE -isystem../linux-headers -isystemlinux-headers -DNEED_CPU_H '-DCONFIG_TARGET="x86_64-softmmu-config-target.h"' '-DCONFIG_DEVICES="x86_64-softmmu-config-devices.h"' -MD -MQ libqemu-x86_64-softmmu.fa.p/hw_vfio_pci-quirks.c.o -MF libqemu-x86_64-softmmu.fa.p/hw_vfio_pci-quirks.c.o.d -o libqemu-x86_64-softmmu.fa.p/hw_vfio_pci-quirks.c.o -c ../hw/vfio/pci-quirks.c +../hw/vfio/pci-quirks.c: In function ‘vfio_igd_gtt_max’: +../hw/vfio/pci-quirks.c:1356:55: error: ‘IGD_GMCH’ undeclared (first use in this function) + 1356 | uint32_t gmch = vfio_pci_read_config(&vdev->pdev, IGD_GMCH, sizeof(gmch)); + | ^~~~~~~~ +../hw/vfio/pci-quirks.c:1356:55: note: each undeclared identifier is reported only once for each function it appears in +../hw/vfio/pci-quirks.c:1357:21: error: implicit declaration of function ‘igd_gen’ [-Werror=implicit-function-declaration] + 1357 | int ggms, gen = igd_gen(vdev); + | ^~~~~~~ +../hw/vfio/pci-quirks.c:1357:21: error: nested extern declaration of ‘igd_gen’ [-Werror=nested-externs] +../hw/vfio/pci-quirks.c: In function ‘vfio_igd_quirk_data_read’: +../hw/vfio/pci-quirks.c:1384:5: error: unknown type name ‘VFIOIGDQuirk’; did you mean ‘VFIOQuirk’? + 1384 | VFIOIGDQuirk *igd = opaque; + | ^~~~~~~~~~~~ + | VFIOQuirk +../hw/vfio/pci-quirks.c:1385:30: error: request for member ‘vdev’ in something not a structure or union + 1385 | VFIOPCIDevice *vdev = igd->vdev; + | ^~ +../hw/vfio/pci-quirks.c:1387:8: error: request for member ‘index’ in something not a structure or union + 1387 | igd->index = ~0; + | ^~ +../hw/vfio/pci-quirks.c: In function ‘vfio_igd_quirk_data_write’: +../hw/vfio/pci-quirks.c:1395:5: error: unknown type name ‘VFIOIGDQuirk’; did you mean ‘VFIOQuirk’? + 1395 | VFIOIGDQuirk *igd = opaque; + | ^~~~~~~~~~~~ + | VFIOQuirk +../hw/vfio/pci-quirks.c:1396:30: error: request for member ‘vdev’ in something not a structure or union + 1396 | VFIOPCIDevice *vdev = igd->vdev; + | ^~ +../hw/vfio/pci-quirks.c:1414:13: error: request for member ‘index’ in something not a structure or union + 1414 | if ((igd->index % 4 == 1) && igd->index < vfio_igd_gtt_max(vdev)) { + | ^~ +../hw/vfio/pci-quirks.c:1414:37: error: request for member ‘index’ in something not a structure or union + 1414 | if ((igd->index % 4 == 1) && igd->index < vfio_igd_gtt_max(vdev)) { + | ^~ +../hw/vfio/pci-quirks.c:1415:28: error: request for member ‘index’ in something not a structure or union + 1415 | if (gen < 8 || (igd->index % 8 == 1)) { + | ^~ +../hw/vfio/pci-quirks.c:1418:53: error: ‘IGD_BDSM’ undeclared (first use in this function) + 1418 | base = pci_get_long(vdev->pdev.config + IGD_BDSM); + | ^~~~~~~~ +../hw/vfio/pci-quirks.c:1420:17: error: implicit declaration of function ‘hw_error’; did you mean ‘herror’? [-Werror=implicit-function-declaration] + 1420 | hw_error("vfio-igd: Guest attempted to program IGD GTT before " + | ^~~~~~~~ + | herror +../hw/vfio/pci-quirks.c:1420:17: error: nested extern declaration of ‘hw_error’ [-Werror=nested-externs] +../hw/vfio/pci-quirks.c:1424:29: error: request for member ‘bdsm’ in something not a structure or union + 1424 | val = data - igd->bdsm + base; + | ^~ +../hw/vfio/pci-quirks.c:1430:42: error: request for member ‘index’ in something not a structure or union + 1430 | igd->index, data, val); + | ^~ +../hw/vfio/pci-quirks.c:1435:8: error: request for member ‘index’ in something not a structure or union + 1435 | igd->index = ~0; + | ^~ +../hw/vfio/pci-quirks.c: In function ‘vfio_igd_quirk_index_read’: +../hw/vfio/pci-quirks.c:1447:5: error: unknown type name ‘VFIOIGDQuirk’; did you mean ‘VFIOQuirk’? + 1447 | VFIOIGDQuirk *igd = opaque; + | ^~~~~~~~~~~~ + | VFIOQuirk +../hw/vfio/pci-quirks.c:1448:30: error: request for member ‘vdev’ in something not a structure or union + 1448 | VFIOPCIDevice *vdev = igd->vdev; + | ^~ +../hw/vfio/pci-quirks.c:1450:8: error: request for member ‘index’ in something not a structure or union + 1450 | igd->index = ~0; + | ^~ +../hw/vfio/pci-quirks.c: In function ‘vfio_igd_quirk_index_write’: +../hw/vfio/pci-quirks.c:1458:5: error: unknown type name ‘VFIOIGDQuirk’; did you mean ‘VFIOQuirk’? + 1458 | VFIOIGDQuirk *igd = opaque; + | ^~~~~~~~~~~~ + | VFIOQuirk +../hw/vfio/pci-quirks.c:1459:30: error: request for member ‘vdev’ in something not a structure or union + 1459 | VFIOPCIDevice *vdev = igd->vdev; + | ^~ +../hw/vfio/pci-quirks.c:1461:8: error: request for member ‘index’ in something not a structure or union + 1461 | igd->index = data; + | ^~ +../hw/vfio/pci-quirks.c: At top level: +../hw/vfio/pci-quirks.c:1472:13: error: static declaration of ‘vfio_probe_igd_bar4_quirk’ follows non-static declaration + 1472 | static void vfio_probe_igd_bar4_quirk(VFIOPCIDevice *vdev, int nr) + | ^~~~~~~~~~~~~~~~~~~~~~~~~ +In file included from ../hw/vfio/pci-quirks.c:27: +../hw/vfio/pci.h:211:6: note: previous declaration of ‘vfio_probe_igd_bar4_quirk’ was here + 211 | void vfio_probe_igd_bar4_quirk(VFIOPCIDevice *vdev, int nr); + | ^~~~~~~~~~~~~~~~~~~~~~~~~ +../hw/vfio/pci-quirks.c: In function ‘vfio_probe_igd_bar4_quirk’: +../hw/vfio/pci-quirks.c:1477:5: error: unknown type name ‘VFIOIGDQuirk’; did you mean ‘VFIOQuirk’? + 1477 | VFIOIGDQuirk *igd; + | ^~~~~~~~~~~~ + | VFIOQuirk +../hw/vfio/pci-quirks.c:1511:46: error: ‘IGD_GMCH’ undeclared (first use in this function) + 1511 | gmch = vfio_pci_read_config(&vdev->pdev, IGD_GMCH, 4); + | ^~~~~~~~ +../hw/vfio/pci-quirks.c:1603:32: error: ‘ERR_PREFIX’ undeclared (first use in this function) + 1603 | error_reportf_err(err, ERR_PREFIX, vdev->vbasedev.name); + | ^~~~~~~~~~ +../hw/vfio/pci-quirks.c:1638:8: error: request for member ‘vdev’ in something not a structure or union + 1638 | igd->vdev = vdev; + | ^~ +../hw/vfio/pci-quirks.c:1639:8: error: request for member ‘index’ in something not a structure or union + 1639 | igd->index = ~0; + | ^~ +../hw/vfio/pci-quirks.c:1640:8: error: request for member ‘bdsm’ in something not a structure or union + 1640 | igd->bdsm = vfio_pci_read_config(&vdev->pdev, IGD_BDSM, 4); + | ^~ +../hw/vfio/pci-quirks.c:1640:51: error: ‘IGD_BDSM’ undeclared (first use in this function) + 1640 | igd->bdsm = vfio_pci_read_config(&vdev->pdev, IGD_BDSM, 4); + | ^~~~~~~~ +../hw/vfio/pci-quirks.c:1641:8: error: request for member ‘bdsm’ in something not a structure or union + 1641 | igd->bdsm &= ~((1 << 20) - 1); /* 1MB aligned */ + | ^~ +cc1: all warnings being treated as errors +[61/1034] Compiling C object libqemu-x86_64-softmmu.fa.p/hw_virtio_virtio-crypto-pci.c.o +[62/1034] Compiling C object libqemu-x86_64-softmmu.fa.p/hw_virtio_virtio-crypto.c.o +[63/1034] Compiling C object libqemu-x86_64-softmmu.fa.p/hw_virtio_vhost-user-fs.c.o +[64/1034] Compiling C object libqemu-x86_64-softmmu.fa.p/hw_virtio_vhost-user-fs-pci.c.o +[65/1034] Compiling C object libqemu-x86_64-softmmu.fa.p/hw_virtio_vhost-vdpa.c.o +[66/1034] Compiling C object libqemu-x86_64-softmmu.fa.p/hw_virtio_virtio-balloon.c.o +[67/1034] Compiling C object libqemu-x86_64-softmmu.fa.p/hw_virtio_vhost-user.c.o +ninja: build stopped: subcommand failed. +make[1]: *** [Makefile:163: run-ninja] Error 1 +make[1]: Leaving directory '/qemu-git/qemu/build' +make: *** [GNUmakefile:11: all] Error 2 +``` +Steps to reproduce: +1. git clone git://git.qemu.org/qemu.git +2. ./configure --prefix=/usr \--target-list=x86_64-softmmu +3. make -j8 diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/956 b/gitlab/issues_text/target_missing/host_missing/accel_missing/956 new file mode 100644 index 000000000..3c412080a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/956 @@ -0,0 +1,42 @@ +ARM: When 'virsh dump' exports vmcore, specifies --format compression format, virtual machine assert hangs +Description of problem: +**ARM: virsh dump exports vmcore, specifies --format compression format, virtual machine assert hangs** + +**why 'virsh dump' page size configured as target page size (64KiB), but 'Implement kvm-steal-time' page size configured as host page size (4KB)?** +Steps to reproduce: +The vm image page size is configured as 64KiB, and the host page size is configured as 4KiB + +1.start vm + +2.Execute the virsh dump command to export vmcore + +Specify the compression format of vmcore, --format (kdump-zlib, kdump-snappy, kdump-lzo) + +/usr/bin/virsh dump avocado-vt-vm1 /var/tmp/vm.core --memory-only --format kdump-zlib + +/usr/bin/virsh dump avocado-vt-vm1 /var/tmp/vm.core --memory-only --format kdump-lzo + +/usr/bin/virsh dump avocado-vt-vm1 /var/tmp/vm.core --memory-only --format kdump-snappy + +**expected results**: The vmcore file is successfully exported and the virtual machine is running normally. + +**actual results**: The vmcore file is not exported normally, and the virtual machine is shut down abnormally. +Additional information: +qemu log: + + +host page size: + + +vm page size: + + +dump.c: get_next_page assert: + + +The code for the error assert exit is shown above. Here, it will check whether the memory to be dumped is actually aligned with the termination address. It needs to be aligned with the page size of the virtual machine. You can see through gdb that it is 64KiB. + + + +After binary search, it was found that a feature of kvm_steal_time was added to arm in version 5.2. Added the following code: + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/959 b/gitlab/issues_text/target_missing/host_missing/accel_missing/959 new file mode 100644 index 000000000..0d00f781c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/959 @@ -0,0 +1,9 @@ +100% CPU utilization when the guest is idle (FreeBSD on M1 Mac) +Description of problem: +100% CPU utilization when the guest is idle. +Steps to reproduce: +1. Download the FreeBSD qcow2 image and decompress it: https://download.freebsd.org/releases/VM-IMAGES/13.0-RELEASE/aarch64/Latest/ +2. Execute the above command. +3. The QEMU process consumes 100% CPU. +4. + diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/96 b/gitlab/issues_text/target_missing/host_missing/accel_missing/96 new file mode 100644 index 000000000..c5058ca12 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/96 @@ -0,0 +1 @@ +qemu-1.5.0 savevm error -95 while writing vm with ceph-rbd as storage-backend diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/960 b/gitlab/issues_text/target_missing/host_missing/accel_missing/960 new file mode 100644 index 000000000..fb6a9d774 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/960 @@ -0,0 +1 @@ +Windows host / win98 guest, i don't understand how to use network diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/962 b/gitlab/issues_text/target_missing/host_missing/accel_missing/962 new file mode 100644 index 000000000..8cae31303 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/962 @@ -0,0 +1,19 @@ +Screenshot images are skewed +Description of problem: +1. Start a guest with SPICE +2. Connect with a SPICE client +3. Resize screen to a width that is not a multiple of 4 (e. g. 487x956) +4. Take a screenshot + +The screenshot ppm file will contain the actual dimensions in the header, e. g. +``` +P6 +487 956 +255 +``` +but the image data will contain more than that (e. g. 488 * 956 * 3 bytes). +As a result, when displaying the image it appears skewed. +Steps to reproduce: +See above. +Additional information: +I'm not familiar with qemu code nor the pixman library, but I assume that in [this line](https://gitlab.com/qemu-project/qemu/-/blob/bc6ec396d471d9e4aae7e2ff8b72e11da9a97665/ui/console.c#L316) `get_stride` is wrong. Instead, it should write `width*3` bytes. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/963 b/gitlab/issues_text/target_missing/host_missing/accel_missing/963 new file mode 100644 index 000000000..b1336a94a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/963 @@ -0,0 +1 @@ +qemu-7.0.0-rc2/migration/ram.c:1292: possible wrong operator ? diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/965 b/gitlab/issues_text/target_missing/host_missing/accel_missing/965 new file mode 100644 index 000000000..f8960f22b --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/965 @@ -0,0 +1 @@ +Creating a NVME disk using qemu in the Host not in the VM diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/967 b/gitlab/issues_text/target_missing/host_missing/accel_missing/967 new file mode 100644 index 000000000..2b351d25f --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/967 @@ -0,0 +1,224 @@ +qemu 6.2 user mode memory leak when mmap + munmap is called +Description of problem: +Launch a program with qemu user mode emulator, +If this program calls mmap to allocate 40GB virtual memory and call munmap to free it later, the memory const of qemu user mode emulator grows to a very big value. + +Excepted behavior: qemu-x86_64 costs very less memory after munmap is called. +Observed behavior: qemu-x86_64 costs around 2.5GiB after munmap is called. Most of the memory is consumed by [heap]. +Steps to reproduce: +1.Compile this code with g++. +```shell +g++ -o main.bin main.cpp +``` +```cpp +#include <chrono> +#include <cstdio> +#include <sys/types.h> +#include <unistd.h> +#include <cstdlib> +#include <sys/mman.h> + +#include <thread> + +static constexpr size_t pageSize = 4096; + +int main(){ + constexpr size_t size = 1024*100*pageSize*1000; + + void* data = mmap(nullptr, size, PROT_NONE, MAP_ANONYMOUS | MAP_PRIVATE, -1, 0); + + if(data == nullptr){ + perror("mmap failed"); + exit(1); + } + + int error = munmap(data, size); + + if(error !=0){ + perror("munmap failed"); + exit(1); + } + + + printf("mmap munmap test done\n"); + while(true){ + std::this_thread::sleep_for(std::chrono::seconds(10000)); + } + + return 0; +} +``` +2. run main.bin with qemu-x86_64 +```shell +$ qemu-x86_64 ./main.bin +mmap munmap test done +``` +3. check memory usage by top +``` +$ top -p `pgrep "qemu"` +top - 16:00:39 up 6:41, 1 user, load average: 0.08, 0.12, 0.10 +Tasks: 1 total, 0 running, 1 sleeping, 0 stopped, 0 zombie +%Cpu(s): 0.0 us, 0.0 sy, 0.0 ni,100.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st +MiB Mem : 15969.1 total, 8249.3 free, 6048.2 used, 1671.5 buff/cache +MiB Swap: 2048.0 total, 1209.6 free, 838.4 used. 9544.3 avail Mem + + PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND + 38521 jcq 20 0 2634324 2.3g 7840 S 0.0 14.8 0:04.48 qemu-x86_64 +``` + +4. check memory usage by mmap. Heap is 5611ca5e0000-56125d125000, the size of heap is more than 2GiB. +```shell +$ cat /proc/38521/maps +4000000000-4000001000 r--p 00000000 00:35 49812 /mnt/hgfs/workspace/LearningProjects/CMakeLearn/src/main.bin +4000001000-4000002000 r--p 00001000 00:35 49812 /mnt/hgfs/workspace/LearningProjects/CMakeLearn/src/main.bin +4000002000-4000003000 r--p 00002000 00:35 49812 /mnt/hgfs/workspace/LearningProjects/CMakeLearn/src/main.bin +4000003000-4000004000 r--p 00002000 00:35 49812 /mnt/hgfs/workspace/LearningProjects/CMakeLearn/src/main.bin +4000004000-4000005000 rw-p 00003000 00:35 49812 /mnt/hgfs/workspace/LearningProjects/CMakeLearn/src/main.bin +4000005000-4000026000 rw-p 00000000 00:00 0 +4001005000-4001006000 ---p 00000000 00:00 0 +4001006000-4001806000 rw-p 00000000 00:00 0 +4001806000-400183d000 r--p 00000000 08:05 4456513 /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 +400183d000-400183e000 ---p 00000000 00:00 0 +400183e000-4001840000 r--p 00037000 08:05 4456513 /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 +4001840000-4001842000 rw-p 00039000 08:05 4456513 /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 +4001842000-4001844000 rw-p 00000000 00:00 0 +4001863000-4001a78000 r--p 00000000 08:05 4456541 /usr/lib/x86_64-linux-gnu/libc.so.6 +4001a78000-4001a7c000 r--p 00214000 08:05 4456541 /usr/lib/x86_64-linux-gnu/libc.so.6 +4001a7c000-4001a7e000 rw-p 00218000 08:05 4456541 /usr/lib/x86_64-linux-gnu/libc.so.6 +4001a7e000-4001a8d000 rw-p 00000000 00:00 0 +5611c96af000-5611c9734000 r--p 00000000 08:05 4467878 /usr/bin/qemu-x86_64 +5611c9734000-5611c9885000 r-xp 00085000 08:05 4467878 /usr/bin/qemu-x86_64 +5611c9885000-5611c9901000 r--p 001d6000 08:05 4467878 /usr/bin/qemu-x86_64 +5611c9902000-5611c993c000 r--p 00252000 08:05 4467878 /usr/bin/qemu-x86_64 +5611c993c000-5611c9950000 rw-p 0028c000 08:05 4467878 /usr/bin/qemu-x86_64 +5611c9950000-5611c996e000 rw-p 00000000 00:00 0 +5611ca5e0000-56125d125000 rw-p 00000000 00:00 0 [heap] +7f2038000000-7f203ffff000 rwxp 00000000 00:00 0 +7f203ffff000-7f2040000000 ---p 00000000 00:00 0 +7f2040000000-7f2040021000 rw-p 00000000 00:00 0 +7f2040021000-7f2044000000 ---p 00000000 00:00 0 +7f2047def000-7f2047e70000 rw-p 00000000 00:00 0 +7f2047e70000-7f2047e71000 ---p 00000000 00:00 0 +7f2047e71000-7f2048676000 rw-p 00000000 00:00 0 +7f2048676000-7f2048678000 r--p 00000000 08:05 4456538 /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0 +7f2048678000-7f204867f000 r-xp 00002000 08:05 4456538 /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0 +7f204867f000-7f2048680000 r--p 00009000 08:05 4456538 /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0 +7f2048680000-7f2048681000 ---p 0000a000 08:05 4456538 /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0 +7f2048681000-7f2048682000 r--p 0000a000 08:05 4456538 /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0 +7f2048682000-7f2048683000 rw-p 0000b000 08:05 4456538 /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0 +7f2048683000-7f204868d000 r--p 00000000 08:05 4457088 /usr/lib/x86_64-linux-gnu/libgmp.so.10.4.1 +7f204868d000-7f20486ec000 r-xp 0000a000 08:05 4457088 /usr/lib/x86_64-linux-gnu/libgmp.so.10.4.1 +7f20486ec000-7f2048703000 r--p 00069000 08:05 4457088 /usr/lib/x86_64-linux-gnu/libgmp.so.10.4.1 +7f2048703000-7f2048704000 r--p 0007f000 08:05 4457088 /usr/lib/x86_64-linux-gnu/libgmp.so.10.4.1 +7f2048704000-7f2048705000 rw-p 00080000 08:05 4457088 /usr/lib/x86_64-linux-gnu/libgmp.so.10.4.1 +7f2048705000-7f204870d000 r--p 00000000 08:05 4461541 /usr/lib/x86_64-linux-gnu/libhogweed.so.6.4 +7f204870d000-7f2048720000 r-xp 00008000 08:05 4461541 /usr/lib/x86_64-linux-gnu/libhogweed.so.6.4 +7f2048720000-7f204874a000 r--p 0001b000 08:05 4461541 /usr/lib/x86_64-linux-gnu/libhogweed.so.6.4 +7f204874a000-7f204874b000 ---p 00045000 08:05 4461541 /usr/lib/x86_64-linux-gnu/libhogweed.so.6.4 +7f204874b000-7f204874c000 r--p 00045000 08:05 4461541 /usr/lib/x86_64-linux-gnu/libhogweed.so.6.4 +7f204874c000-7f204874d000 rw-p 00046000 08:05 4461541 /usr/lib/x86_64-linux-gnu/libhogweed.so.6.4 +7f204874d000-7f2048757000 r--p 00000000 08:05 4464736 /usr/lib/x86_64-linux-gnu/libnettle.so.8.4 +7f2048757000-7f204877a000 r-xp 0000a000 08:05 4464736 /usr/lib/x86_64-linux-gnu/libnettle.so.8.4 +7f204877a000-7f2048790000 r--p 0002d000 08:05 4464736 /usr/lib/x86_64-linux-gnu/libnettle.so.8.4 +7f2048790000-7f2048792000 r--p 00042000 08:05 4464736 /usr/lib/x86_64-linux-gnu/libnettle.so.8.4 +7f2048792000-7f2048793000 rw-p 00044000 08:05 4464736 /usr/lib/x86_64-linux-gnu/libnettle.so.8.4 +7f2048793000-7f2048795000 rw-p 00000000 00:00 0 +7f2048795000-7f2048798000 r--p 00000000 08:05 4459610 /usr/lib/x86_64-linux-gnu/libtasn1.so.6.6.2 +7f2048798000-7f20487a6000 r-xp 00003000 08:05 4459610 /usr/lib/x86_64-linux-gnu/libtasn1.so.6.6.2 +7f20487a6000-7f20487aa000 r--p 00011000 08:05 4459610 /usr/lib/x86_64-linux-gnu/libtasn1.so.6.6.2 +7f20487aa000-7f20487ab000 ---p 00015000 08:05 4459610 /usr/lib/x86_64-linux-gnu/libtasn1.so.6.6.2 +7f20487ab000-7f20487ac000 r--p 00015000 08:05 4459610 /usr/lib/x86_64-linux-gnu/libtasn1.so.6.6.2 +7f20487ac000-7f20487ad000 rw-p 00016000 08:05 4459610 /usr/lib/x86_64-linux-gnu/libtasn1.so.6.6.2 +7f20487ad000-7f20487be000 r--p 00000000 08:05 4460136 /usr/lib/x86_64-linux-gnu/libunistring.so.2.2.0 +7f20487be000-7f20487f4000 r-xp 00011000 08:05 4460136 /usr/lib/x86_64-linux-gnu/libunistring.so.2.2.0 +7f20487f4000-7f2048952000 r--p 00047000 08:05 4460136 /usr/lib/x86_64-linux-gnu/libunistring.so.2.2.0 +7f2048952000-7f2048956000 r--p 001a5000 08:05 4460136 /usr/lib/x86_64-linux-gnu/libunistring.so.2.2.0 +7f2048956000-7f2048957000 rw-p 001a9000 08:05 4460136 /usr/lib/x86_64-linux-gnu/libunistring.so.2.2.0 +7f2048957000-7f2048959000 r--p 00000000 08:05 4465922 /usr/lib/x86_64-linux-gnu/libidn2.so.0.3.7 +7f2048959000-7f204895d000 r-xp 00002000 08:05 4465922 /usr/lib/x86_64-linux-gnu/libidn2.so.0.3.7 +7f204895d000-7f2048976000 r--p 00006000 08:05 4465922 /usr/lib/x86_64-linux-gnu/libidn2.so.0.3.7 +7f2048976000-7f2048977000 r--p 0001e000 08:05 4465922 /usr/lib/x86_64-linux-gnu/libidn2.so.0.3.7 +7f2048977000-7f2048978000 rw-p 0001f000 08:05 4465922 /usr/lib/x86_64-linux-gnu/libidn2.so.0.3.7 +7f2048978000-7f20489a1000 r--p 00000000 08:05 4459606 /usr/lib/x86_64-linux-gnu/libp11-kit.so.0.3.0 +7f20489a1000-7f2048a45000 r-xp 00029000 08:05 4459606 /usr/lib/x86_64-linux-gnu/libp11-kit.so.0.3.0 +7f2048a45000-7f2048a9f000 r--p 000cd000 08:05 4459606 /usr/lib/x86_64-linux-gnu/libp11-kit.so.0.3.0 +7f2048a9f000-7f2048aa9000 r--p 00126000 08:05 4459606 /usr/lib/x86_64-linux-gnu/libp11-kit.so.0.3.0 +7f2048aa9000-7f2048ab3000 rw-p 00130000 08:05 4459606 /usr/lib/x86_64-linux-gnu/libp11-kit.so.0.3.0 +7f2048ab3000-7f2048ab5000 r--p 00000000 08:05 4456747 /usr/lib/x86_64-linux-gnu/libpcre.so.3.13.3 +7f2048ab5000-7f2048b0a000 r-xp 00002000 08:05 4456747 /usr/lib/x86_64-linux-gnu/libpcre.so.3.13.3 +7f2048b0a000-7f2048b27000 r--p 00057000 08:05 4456747 /usr/lib/x86_64-linux-gnu/libpcre.so.3.13.3 +7f2048b27000-7f2048b28000 r--p 00073000 08:05 4456747 /usr/lib/x86_64-linux-gnu/libpcre.so.3.13.3 +7f2048b28000-7f2048b29000 rw-p 00074000 08:05 4456747 /usr/lib/x86_64-linux-gnu/libpcre.so.3.13.3 +7f2048b29000-7f2048b51000 r--p 00000000 08:05 4456541 /usr/lib/x86_64-linux-gnu/libc.so.6 +7f2048b51000-7f2048ce6000 r-xp 00028000 08:05 4456541 /usr/lib/x86_64-linux-gnu/libc.so.6 +7f2048ce6000-7f2048d3e000 r--p 001bd000 08:05 4456541 /usr/lib/x86_64-linux-gnu/libc.so.6 +7f2048d3e000-7f2048d42000 r--p 00214000 08:05 4456541 /usr/lib/x86_64-linux-gnu/libc.so.6 +7f2048d42000-7f2048d44000 rw-p 00218000 08:05 4456541 /usr/lib/x86_64-linux-gnu/libc.so.6 +7f2048d44000-7f2048d53000 rw-p 00000000 00:00 0 +7f2048d53000-7f2048d56000 r--p 00000000 08:05 4457972 /usr/lib/x86_64-linux-gnu/libgcc_s.so.1 +7f2048d56000-7f2048d6d000 r-xp 00003000 08:05 4457972 /usr/lib/x86_64-linux-gnu/libgcc_s.so.1 +7f2048d6d000-7f2048d71000 r--p 0001a000 08:05 4457972 /usr/lib/x86_64-linux-gnu/libgcc_s.so.1 +7f2048d71000-7f2048d72000 r--p 0001d000 08:05 4457972 /usr/lib/x86_64-linux-gnu/libgcc_s.so.1 +7f2048d72000-7f2048d73000 rw-p 0001e000 08:05 4457972 /usr/lib/x86_64-linux-gnu/libgcc_s.so.1 +7f2048d73000-7f2048d81000 r--p 00000000 08:05 4456717 /usr/lib/x86_64-linux-gnu/libm.so.6 +7f2048d81000-7f2048dfd000 r-xp 0000e000 08:05 4456717 /usr/lib/x86_64-linux-gnu/libm.so.6 +7f2048dfd000-7f2048e58000 r--p 0008a000 08:05 4456717 /usr/lib/x86_64-linux-gnu/libm.so.6 +7f2048e58000-7f2048e59000 r--p 000e4000 08:05 4456717 /usr/lib/x86_64-linux-gnu/libm.so.6 +7f2048e59000-7f2048e5a000 rw-p 000e5000 08:05 4456717 /usr/lib/x86_64-linux-gnu/libm.so.6 +7f2048e5a000-7f2048e8b000 r--p 00000000 08:05 4456481 /usr/lib/x86_64-linux-gnu/libgnutls.so.30.31.0 +7f2048e8b000-7f2048fb4000 r-xp 00031000 08:05 4456481 /usr/lib/x86_64-linux-gnu/libgnutls.so.30.31.0 +7f2048fb4000-7f2049031000 r--p 0015a000 08:05 4456481 /usr/lib/x86_64-linux-gnu/libgnutls.so.30.31.0 +7f2049031000-7f2049041000 r--p 001d6000 08:05 4456481 /usr/lib/x86_64-linux-gnu/libgnutls.so.30.31.0 +7f2049041000-7f2049043000 rw-p 001e6000 08:05 4456481 /usr/lib/x86_64-linux-gnu/libgnutls.so.30.31.0 +7f2049043000-7f2049045000 rw-p 00000000 00:00 0 +7f2049045000-7f2049047000 r--p 00000000 08:05 4465165 /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0.7200.0 +7f2049047000-7f2049049000 r-xp 00002000 08:05 4465165 /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0.7200.0 +7f2049049000-7f204904a000 r--p 00004000 08:05 4465165 /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0.7200.0 +7f204904a000-7f204904b000 r--p 00004000 08:05 4465165 /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0.7200.0 +7f204904b000-7f204904c000 rw-p 00005000 08:05 4465165 /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0.7200.0 +7f204904c000-7f2049069000 r--p 00000000 08:05 4465132 /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7200.0 +7f2049069000-7f20490f8000 r-xp 0001d000 08:05 4465132 /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7200.0 +7f20490f8000-7f2049182000 r--p 000ac000 08:05 4465132 /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7200.0 +7f2049182000-7f2049183000 ---p 00136000 08:05 4465132 /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7200.0 +7f2049183000-7f2049184000 r--p 00136000 08:05 4465132 /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7200.0 +7f2049184000-7f2049185000 rw-p 00137000 08:05 4465132 /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7200.0 +7f2049185000-7f2049186000 rw-p 00000000 00:00 0 +7f2049186000-7f2049188000 r--p 00000000 08:05 4463546 /usr/lib/x86_64-linux-gnu/liburing.so.2.1.0 +7f2049188000-7f204918a000 r-xp 00002000 08:05 4463546 /usr/lib/x86_64-linux-gnu/liburing.so.2.1.0 +7f204918a000-7f204918b000 r--p 00004000 08:05 4463546 /usr/lib/x86_64-linux-gnu/liburing.so.2.1.0 +7f204918b000-7f204918c000 r--p 00004000 08:05 4463546 /usr/lib/x86_64-linux-gnu/liburing.so.2.1.0 +7f204918c000-7f204918d000 rw-p 00005000 08:05 4463546 /usr/lib/x86_64-linux-gnu/liburing.so.2.1.0 +7f20491ac000-7f20491ae000 rw-p 00000000 00:00 0 +7f20491ae000-7f20491b0000 r--p 00000000 08:05 4456513 /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 +7f20491b0000-7f20491da000 r-xp 00002000 08:05 4456513 /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 +7f20491da000-7f20491e5000 r--p 0002c000 08:05 4456513 /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 +7f20491e6000-7f20491e8000 r--p 00037000 08:05 4456513 /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 +7f20491e8000-7f20491ea000 rw-p 00039000 08:05 4456513 /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 +7fffe17ee000-7fffe1810000 rw-p 00000000 00:00 0 [stack] +7fffe19d1000-7fffe19d5000 r--p 00000000 00:00 0 [vvar] +7fffe19d5000-7fffe19d7000 r-xp 00000000 00:00 0 [vdso] +ffffffffff600000-ffffffffff601000 --xp 00000000 00:00 0 [vsyscall] +``` +Additional information: +qemu is installed by ubuntu's apt. + +sudo apt install qemu-user + +compiler version: +``` +g++ --version +g++ (Ubuntu 11.2.0-19ubuntu1) 11.2.0 +Copyright (C) 2021 Free Software Foundation, Inc. +This is free software; see the source for copying conditions. There is NO +warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. +``` + +libc version: +``` +ldd --version +ldd (Ubuntu GLIBC 2.35-0ubuntu3) 2.35 +Copyright (C) 2022 Free Software Foundation, Inc. +This is free software; see the source for copying conditions. There is NO +warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. +Written by Roland McGrath and Ulrich Drepper. +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/968 b/gitlab/issues_text/target_missing/host_missing/accel_missing/968 new file mode 100644 index 000000000..022932eaf --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/968 @@ -0,0 +1,95 @@ +QEMU guest agent fails to install if COM+ Application: QEMU Guest Agent VSS Provider not properly uninstalled +Description of problem: +QEMU guest agent fails to install if COM+ Application: QEMU Guest Agent VSS Provider not properly uninstalled +Steps to reproduce: +1. Install QEMU guest agent +2. Uninstall QEMU guest agent (in rare cases it didn't uninstall the COM+ component) +3. Install QEMU guest agent and get error: `Product: QEMU guest agent -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action RegisterCom, location: cmd.exe, command: /c "C:\Program Files\Qemu-ga\qemu-ga.exe" -s vss-install` +Additional information: +1. **Qemu GA is already uninstalled:** + +``` +gwmi Win32_Product + + +IdentifyingNumber : {EE3877E4-07B0-41F2-ADB8-B45133DDCE37} +Name : Spice Agent 0.10.0-5 (64-bit) +Vendor : Red Hat, Inc. +Version : 0.10.5 +Caption : Spice Agent 0.10.0-5 (64-bit) + +IdentifyingNumber : {4C49C419-DE39-421B-B0F8-5F0DE1486869} +Name : Virtio-win-driver-installer +Vendor : Red Hat, Inc. +Version : 0.1.189 +Caption : Virtio-win-driver-installer + +IdentifyingNumber : {85F4CBCB-9BBC-4B50-A7D8-E1106771498D} +Name : Orca +Vendor : Microsoft Corporation +Version : 3.1.5299.0000 +Caption : Orca + +IdentifyingNumber : {89F4137D-6C26-4A84-BDB8-2E5A4BB71E00} +Name : Microsoft Silverlight +Vendor : Microsoft Corporation +Version : 5.1.50918.0 +Caption : Microsoft Silverlight + +IdentifyingNumber : {AB392F9F-0C0C-4098-B5BA-B1E84E62D6CE} +Name : Icinga 2 +Vendor : Icinga GmbH +Version : 2.11.0 +Caption : Icinga 2 +``` + +2. **Extract files from installer and run `qemu-ga.exe -s vss-install`** + +It fails with: `QGA VSS Provider is already installed. (Error: 80004004) Vorgang abgebrochen` + +3. **Uninstall COM+ component: `qemu-ga.exe -s vss-uninstall`** + +`Removing COM+ Application: QEMU Guest Agent VSS Provider` + +4. **Now you can install GA** + +``` +gwmi Win32_Product + + +IdentifyingNumber : {EE3877E4-07B0-41F2-ADB8-B45133DDCE37} +Name : Spice Agent 0.10.0-5 (64-bit) +Vendor : Red Hat, Inc. +Version : 0.10.5 +Caption : Spice Agent 0.10.0-5 (64-bit) + +IdentifyingNumber : {4C49C419-DE39-421B-B0F8-5F0DE1486869} +Name : Virtio-win-driver-installer +Vendor : Red Hat, Inc. +Version : 0.1.189 +Caption : Virtio-win-driver-installer + +IdentifyingNumber : {85F4CBCB-9BBC-4B50-A7D8-E1106771498D} +Name : Orca +Vendor : Microsoft Corporation +Version : 3.1.5299.0000 +Caption : Orca + +IdentifyingNumber : {99AD6A3C-F854-4E6E-865F-11D4A5E46172} +Name : QEMU guest agent +Vendor : RedHat +Version : 101.1.0 +Caption : QEMU guest agent + +IdentifyingNumber : {89F4137D-6C26-4A84-BDB8-2E5A4BB71E00} +Name : Microsoft Silverlight +Vendor : Microsoft Corporation +Version : 5.1.50918.0 +Caption : Microsoft Silverlight + +IdentifyingNumber : {AB392F9F-0C0C-4098-B5BA-B1E84E62D6CE} +Name : Icinga 2 +Vendor : Icinga GmbH +Version : 2.11.0 +Caption : Icinga 2 +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/969 b/gitlab/issues_text/target_missing/host_missing/accel_missing/969 new file mode 100644 index 000000000..1ed29d895 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/969 @@ -0,0 +1 @@ +qemu: Georgian translation diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/97 b/gitlab/issues_text/target_missing/host_missing/accel_missing/97 new file mode 100644 index 000000000..920e4ef17 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/97 @@ -0,0 +1 @@ +-serial tcp should hang up when DTR goes low diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/972 b/gitlab/issues_text/target_missing/host_missing/accel_missing/972 new file mode 100644 index 000000000..7b412d9c2 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/972 @@ -0,0 +1 @@ +LSI SCSI Use After Free (CVE-2022-0216) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/974 b/gitlab/issues_text/target_missing/host_missing/accel_missing/974 new file mode 100644 index 000000000..c279f5aae --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/974 @@ -0,0 +1,3 @@ +Enable virtio-9pfs on windows hosts +Additional information: +attn: @schoenebeck diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/976 b/gitlab/issues_text/target_missing/host_missing/accel_missing/976 new file mode 100644 index 000000000..d2db3b18c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/976 @@ -0,0 +1 @@ +Qemu - Bridge direct network connection not working diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/978 b/gitlab/issues_text/target_missing/host_missing/accel_missing/978 new file mode 100644 index 000000000..d19b0f0b2 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/978 @@ -0,0 +1 @@ +Running QEMU with "-vga help" crashes if there is no default VGA card diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/98 b/gitlab/issues_text/target_missing/host_missing/accel_missing/98 new file mode 100644 index 000000000..bdce8bc53 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/98 @@ -0,0 +1 @@ +Curses Keyboard Broken On OS X diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/980 b/gitlab/issues_text/target_missing/host_missing/accel_missing/980 new file mode 100644 index 000000000..b872d5408 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/980 @@ -0,0 +1,16 @@ +Binary emulation of a Solaris-8-compiled dynamically linked C program gives a bus error immediately on startup when running with qemu-sparc +Description of problem: +I am currently trying to use binary emulation to run a dynamically-linked executable C program that was written and compiled on a Solaris 8 VM. However, when I do so, I immediately get a bus error, and I'm not sure what the cause is. Below I'll delineate all of the steps I took to recreate this. +Steps to reproduce: +1. Start Solaris 8 VM (this was done via QEMU, actually, and there are no issues here) +2. Write a simple `.c` program. +3. Compile that program with `/usr/local/bin/gcc`. The name of the program is `binary_emulation`. +4. Test program on the VM to ensure functionality. +5. Stop VM. +6. Mount `.qcow2` on the Linux host so I can easily extract files from it. +7. Copy the entire `/` directory off to `~/binary_emulation/target` +8. Copy `binary_emulation` to a separate directory. +9. `cd` to `.../qemu/build` +10. Run `./qemu-sparc -L ~/binary_emulation/target ~/binary_emulation/binary_emulation` +Additional information: +# diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/981 b/gitlab/issues_text/target_missing/host_missing/accel_missing/981 new file mode 100644 index 000000000..620d5df45 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/981 @@ -0,0 +1,10 @@ +VNC UNIX sockets are not deleted +Description of problem: +After exiting QEMU a unix VNC socket file is left behind. Upon termination I would expect it to remove the socket file like it does for example with a monitor unix socket. +Steps to reproduce: +``` + rm -f foo.socket + qemu-system-x86_64 -vnc unix:foo.socket + # Exit QEMU + ls foo.socket + ``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/982 b/gitlab/issues_text/target_missing/host_missing/accel_missing/982 new file mode 100644 index 000000000..30572e6e4 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/982 @@ -0,0 +1,37 @@ +linux-user: --strace incorrectly decodes writev arguments for 64-bit binaries on 32-bit machine +Description of problem: +With `--strace`, the arguments to `writev` appear to be decoded incorrectly. +The syscall still succeeds and has the expected effects. +Steps to reproduce: +``` +$ cat main.c +#include <sys/uio.h> + +int main(void) { + struct iovec iov; + iov.iov_base = "hello, world!\n"; + iov.iov_len = 14; + return writev(1, &iov, 1); +} + +$ aarch64-unknown-linux-gnu-gcc -static -o aarch64-main main.c + +$ x86_64-pc-linux-gnu-gcc -static -o x86_64-main main.c + +$ i686-pc-linux-gnu-gcc -static -o i686-main main.c + +$ ./i686-main +hello, world! + +$ strace ./i686-main |& grep writev +writev(1, [{iov_base="hello, world!\n", iov_len=14}], 1hello, world! + +$ qemu-i386 --strace ./i686-main |& grep writev +21953 writev(1,0x407ffe54,0x1) = 14 + +$ qemu-x86_64 --strace ./x86_64-main |& grep writev +22218 writev(1,(nil),0x407ffcc0) = 14 + +$ qemu-aarch64 --strace ./aarch64-main |& grep writev +22523 writev(1,(nil),0x407ffcc8) = 14 +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/983 b/gitlab/issues_text/target_missing/host_missing/accel_missing/983 new file mode 100644 index 000000000..23c36b037 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/983 @@ -0,0 +1,8 @@ +Qemu Wiki Database Query Error +Steps to reproduce: +1. Access the Qemu Wiki. https://wiki.qemu.org/Main_Page +2. Type "serial" in the search bar and hit the enter key. +3. Crash ensues. +Additional information: +Crash info attached. +[qemu_wiki_bug.txt](/uploads/06fb534ea65c486f72dce14e75c834bd/qemu_wiki_bug.txt) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/985 b/gitlab/issues_text/target_missing/host_missing/accel_missing/985 new file mode 100644 index 000000000..257c5357a --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/985 @@ -0,0 +1,59 @@ +pkg_add is working very slow on NetBSD +Description of problem: +pkg_add is working very slow, it installs one package in ~30 minutes although network speed is normal. +Steps to reproduce: +1. `wget https://cdn.netbsd.org/pub/NetBSD/NetBSD-9.2/images/NetBSD-9.2-amd64.iso` +2. `qemu-img create -f qcow2 disk.qcow2 15G` +3. Install +``` +qemu-system-x86_64 -m 2048 -enable-kvm \ + -drive if=virtio,file=disk.qcow2,format=qcow2 \ + -netdev user,id=mynet0,hostfwd=tcp::7722-:22 \ + -device e1000,netdev=mynet0 \ + -cdrom NetBSD-9.2-amd64.iso +``` + # Installation steps + - 1) Boot Normally + - a) Installation messages in English + - a) unchanged + - a) Install NetBSD to hard disk + - b) Yes + - a) 15G + - a) GPT + - a) This is the correct geometry + - b) Use default partition sizes + - x) Partition sizes are ok + - b) Yes + - a) Use BIOS console + - b) Installation without X11 + - a) CD-ROM / DVD / install image media + - Hit enter to continue + - a) configure network (Select defaults here, perform autoconf) + - x) Finished configuring + - Hit enter to continue + - x) Exit Install System + - Close QEMU +4. Run +``` + qemu-system-x86_64 -m 2048 \ + -drive if=virtio,file=disk.qcow2,format=qcow2 \ + -enable-kvm \ + -netdev user,id=mynet0,hostfwd=tcp:127.0.0.1:7722-:22 \ + -device e1000,netdev=mynet0 +``` +5. Login as root +6. In NetBSD +``` +export PKG_PATH="http://cdn.NetBSD.org/pub/pkgsrc/packages/NetBSD/$(uname -p)/$(uname -r)/All/" && \ +pkg_add pkgin + +``` +You should see that each of the package's installation takes ~30 minutes. +Additional information: +NetBSD 9.2 is also tested in Debian 11 with 'QEMU 6.2.0' and encountered same slowness. + +NetBSD 7.1 and 8.1 are tested on openSUSE Tumbleweed and encountered same slowness. + +OpenBSD's pkg_add is working correctly. + +I am not sure if it will help but Virtualbox(at least 6.1) is working correctly. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/986 b/gitlab/issues_text/target_missing/host_missing/accel_missing/986 new file mode 100644 index 000000000..ceee89eb0 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/986 @@ -0,0 +1,39 @@ +vpc images are created with bigger virtual size than required +Description of problem: +Required virtual size is 895287296, but as qemu-img info reports it is 895426560. +Steps to reproduce: +1. qemu-img create -f vpc img1.vpc 895287296 +2. qemu-img info img1.vpc +Additional information: +Converting back and forth is not possible as a result + ``` +$ qemu-img info openSUSE-Leap-15.3-GNOME-Live-x86_64-Media.iso +image: openSUSE-Leap-15.3-GNOME-Live-x86_64-Media.iso +file format: raw +virtual size: 854 MiB (895287296 bytes) +disk size: 854 MiB + +$ qemu-img create -f vpc img1.vpc 895287296 +Formatting 'img1.vpc', fmt=vpc size=895287296 + +$ qemu-img convert -n \ + -f raw openSUSE-Leap-15.3-GNOME-Live-x86_64-Media.iso \ + -O vpc img1.vpc + +$ qemu-img compare \ + -f raw openSUSE-Leap-15.3-GNOME-Live-x86_64-Media.iso \ + -F vpc img1.vpc +Warning: Image size mismatch! +Images are identical. + +$ qemu-img create -f raw img2.raw 895287296 +Formatting 'img2.raw', fmt=raw size=895287296 + +$ qemu-img convert -n -f vpc img1.vpc -O raw img2.raw +qemu-img: output file is smaller than input file + +$ qemu-img compare \ + -f raw openSUSE-Leap-15.3-GNOME-Live-x86_64-Media.iso \ + -F raw img2.raw +Content mismatch at offset 0! + ``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/987 b/gitlab/issues_text/target_missing/host_missing/accel_missing/987 new file mode 100644 index 000000000..1a9ce9ce1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/987 @@ -0,0 +1,49 @@ +compiling issue +Description of problem: +compilation error issue while building for qemu-riscv32-static +Steps to reproduce: +1.git clone https://github.com/qemu/qemu.git + +2. ./configure --static --disable-system --target-list=riscv32-linux-user + + +issue output: +``` +/usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/libglib-2.0.a(libglib_2_0_la-gutils.o): In function `g_get_user_database_entry': +(.text+0x267): warning: Using 'getpwuid' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking +(.text+0xdd): warning: Using 'getpwnam_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking +(.text+0x11b): warning: Using 'getpwuid_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking +[954/960] Compiling C object tests/unit/test-string-output-visitor.p/test-string-output-visitor.c.o +[955/960] Linking target tests/unit/test-string-output-visitor +/usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/libglib-2.0.a(libglib_2_0_la-gutils.o): In function `g_get_user_database_entry': +(.text+0x267): warning: Using 'getpwuid' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking +(.text+0xdd): warning: Using 'getpwnam_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking +(.text+0x11b): warning: Using 'getpwuid_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking +[956/960] Compiling C object tests/unit/test-string-input-visitor.p/test-string-input-visitor.c.o +[957/960] Linking target tests/unit/test-string-input-visitor +/usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/libglib-2.0.a(libglib_2_0_la-gutils.o): In function `g_get_user_database_entry': +(.text+0x267): warning: Using 'getpwuid' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking +(.text+0xdd): warning: Using 'getpwnam_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking +(.text+0x11b): warning: Using 'getpwuid_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking +[958/960] Linking target tests/unit/test-x86-cpuid +/usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/libglib-2.0.a(libglib_2_0_la-gutils.o): In function `g_get_user_database_entry': +(.text+0x267): warning: Using 'getpwuid' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking +(.text+0xdd): warning: Using 'getpwnam_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking +(.text+0x11b): warning: Using 'getpwuid_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking +[959/960] Compiling C object tests/unit/test-visitor-serialization.p/test-visitor-serialization.c.o +[960/960] Linking target tests/unit/test-visitor-serialization +/usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/libglib-2.0.a(libglib_2_0_la-gutils.o): In function `g_get_user_database_entry': +(.text+0x267): warning: Using 'getpwuid' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking +(.text+0xdd): warning: Using 'getpwnam_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking +(.text+0x11b): warning: Using 'getpwuid_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking +make[1]: Leaving directory '/home/sadiq/work/qemu/build' +changing dir to build for make ""... +make[1]: Entering directory '/home/sadiq/work/qemu/build' + GIT ui/keycodemapdb meson tests/fp/berkeley-testfloat-3 tests/fp/berkeley-softfloat-3 dtc capstone slirp +[1/3] Generating qemu-version.h with a custom command (wrapped by meson to capture output) +make[1]: Leaving directory '/home/sadiq/work/qemu/build' +``` + +Any suggestions to resolve the issue would be helpful + +Thanks diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/988 b/gitlab/issues_text/target_missing/host_missing/accel_missing/988 new file mode 100644 index 000000000..1100490e8 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/988 @@ -0,0 +1 @@ +Cirrus video, graphical corruption, bad fonts diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/989 b/gitlab/issues_text/target_missing/host_missing/accel_missing/989 new file mode 100644 index 000000000..2d35e4899 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/989 @@ -0,0 +1,100 @@ +Segmentation fault on Apple M1 inside a docker container +Description of problem: +I cannot build a Rust dependency (`regex-syntax`) in a docker container for the platform linux/amd64 using Rancher Desktop (v1.2.1; Kubernetes v1.22.7) on Apple M1 hardware. +I suppose it is a QEMU issue because I didn't observe it on x86_64 hardware where the exact same docker container was built and executed natively without emulation. +Moreover, valgrind does not detect an invalid memory access either. +Steps to reproduce: +1. `nerdctl build --platform linux/amd64 -t rust-x86_64 .` +2. `nerdctl run --platform linux/amd64 -it rust-x86_64` +3. `cargo new hello` +4. `cd hello` +5. `echo 'regex-syntax = "0.6.25"' >> Cargo.toml` +6. `cargo build --release -v` +Additional information: +Dockerfile: +``` +FROM ubuntu:21.10 + +# Install a basic environment needed for our build tools +ARG DEBIAN_FRONTEND=noninteractive +RUN apt -yq update && \ + apt -yqq install --no-install-recommends curl ca-certificates \ + build-essential pkg-config libssl-dev llvm-dev liblmdb-dev clang cmake + +# Install Rust and Cargo in /opt +ARG rust_version=1.60.0 +ARG platform=x86_64 +ENV RUSTUP_HOME=/opt/rustup \ + CARGO_HOME=/opt/cargo \ + PATH=/opt/cargo/bin:$PATH +RUN curl --fail https://sh.rustup.rs -sSf \ + | sh -s -- -y --default-toolchain ${rust_version}-${platform}-unknown-linux-gnu --no-modify-path && \ + rustup default ${rust_version}-${platform}-unknown-linux-gnu +``` + + + +Output inside the docker container: + +``` +# cargo build --release -v + Updating crates.io index + Downloaded regex-syntax v0.6.25 + Downloaded 1 crate (293.3 KB) in 0.84s + Compiling regex-syntax v0.6.25 + Running `rustc --crate-name regex_syntax --edition=2018 /opt/cargo/registry/src/github.com-1ecc6299db9ec823/regex-syntax-0.6.25/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no --cfg 'feature="default"' --cfg 'feature="unicode"' --cfg 'feature="unicode-age"' --cfg 'feature="unicode-bool"' --cfg 'feature="unicode-case"' --cfg 'feature="unicode-gencat"' --cfg 'feature="unicode-perl"' --cfg 'feature="unicode-script"' --cfg 'feature="unicode-segment"' -C metadata=fc954162c3ed8ec3 -C extra-filename=-fc954162c3ed8ec3 --out-dir /hello/target/release/deps -L dependency=/hello/target/release/deps --cap-lints allow` +/opt/rustup/toolchains/1.60.0-x86_64-unknown-linux-gnu/bin/../lib/librustc_driver-75e5f32fc3580f6c.so(+0x4b3d23)[0x400215fd23] +/lib/x86_64-linux-gnu/libc.so.6(+0x42520)[0x4005cab520] +/opt/rustup/toolchains/1.60.0-x86_64-unknown-linux-gnu/bin/../lib/../lib/libLLVM-14-rust-1.60.0-stable.so(_ZNK4llvm13AttributeList19addAttributeAtIndexERNS_11LLVMContextEjNS_9AttributeE+0x834)[0x40088d3484] +/opt/rustup/toolchains/1.60.0-x86_64-unknown-linux-gnu/bin/../lib/../lib/libLLVM-14-rust-1.60.0-stable.so(_ZN4llvm8Function19addAttributeAtIndexEjNS_9AttributeE+0x18)[0x40088d2c48] +/opt/rustup/toolchains/1.60.0-x86_64-unknown-linux-gnu/bin/../lib/librustc_driver-75e5f32fc3580f6c.so(_RNvXs4_NtCsfrnhObXyzQM_18rustc_codegen_llvm3abiINtNtNtCsaEkRwEFRwNk_12rustc_target3abi4call5FnAbiNtNtCs12ixbLjc5mB_12rustc_middle2ty2TyENtB5_12FnAbiLlvmExt16apply_attrs_llfn+0x14d)[0x40033d532d] +/opt/rustup/toolchains/1.60.0-x86_64-unknown-linux-gnu/bin/../lib/librustc_driver-75e5f32fc3580f6c.so(_RNvXNtCsfrnhObXyzQM_18rustc_codegen_llvm9mono_itemNtNtB4_7context9CodegenCxNtNtNtCsegTyfRY58Oj_17rustc_codegen_ssa6traits7declare16PreDefineMethods12predefine_fn+0x56a)[0x40033bba5a] +/opt/rustup/toolchains/1.60.0-x86_64-unknown-linux-gnu/bin/../lib/librustc_driver-75e5f32fc3580f6c.so(+0x17007c0)[0x40033ac7c0] +/opt/rustup/toolchains/1.60.0-x86_64-unknown-linux-gnu/bin/../lib/librustc_driver-75e5f32fc3580f6c.so(+0x23761e6)[0x40040221e6] +/opt/rustup/toolchains/1.60.0-x86_64-unknown-linux-gnu/bin/../lib/librustc_driver-75e5f32fc3580f6c.so(+0x2373a6f)[0x400401fa6f] +/opt/rustup/toolchains/1.60.0-x86_64-unknown-linux-gnu/bin/../lib/librustc_driver-75e5f32fc3580f6c.so(+0x23a1e45)[0x400404de45] +/opt/rustup/toolchains/1.60.0-x86_64-unknown-linux-gnu/bin/../lib/librustc_driver-75e5f32fc3580f6c.so(_RNvXs5_CsfrnhObXyzQM_18rustc_codegen_llvmNtB5_18LlvmCodegenBackendNtNtNtCsegTyfRY58Oj_17rustc_codegen_ssa6traits7backend14CodegenBackend13codegen_crate+0xda)[0x400400e70a] +/opt/rustup/toolchains/1.60.0-x86_64-unknown-linux-gnu/bin/../lib/librustc_driver-75e5f32fc3580f6c.so(+0x23544e7)[0x40040004e7] +/opt/rustup/toolchains/1.60.0-x86_64-unknown-linux-gnu/bin/../lib/librustc_driver-75e5f32fc3580f6c.so(+0x233ac88)[0x4003fe6c88] +/opt/rustup/toolchains/1.60.0-x86_64-unknown-linux-gnu/bin/../lib/librustc_driver-75e5f32fc3580f6c.so(_RNvMs0_NtCsf5CM6ndXTHU_15rustc_interface7queriesNtB5_7Queries15ongoing_codegen+0xaf)[0x4003fdd02f] +/opt/rustup/toolchains/1.60.0-x86_64-unknown-linux-gnu/bin/../lib/librustc_driver-75e5f32fc3580f6c.so(+0x2308b04)[0x4003fb4b04] +/opt/rustup/toolchains/1.60.0-x86_64-unknown-linux-gnu/bin/../lib/librustc_driver-75e5f32fc3580f6c.so(+0x22ee134)[0x4003f9a134] +/opt/rustup/toolchains/1.60.0-x86_64-unknown-linux-gnu/bin/../lib/librustc_driver-75e5f32fc3580f6c.so(+0x23213e9)[0x4003fcd3e9] +/opt/rustup/toolchains/1.60.0-x86_64-unknown-linux-gnu/bin/../lib/libstd-8d61b92a0a02f53a.so(rust_metadata_std_cd3cf6af28dff6de+0xa7d03)[0x400598fd03] +/lib/x86_64-linux-gnu/libc.so.6(+0x94947)[0x4005cfd947] +/lib/x86_64-linux-gnu/libc.so.6(clone+0x44)[0x4005d8da44] +error: could not compile `regex-syntax` + +Caused by: + process didn't exit successfully: `rustc --crate-name regex_syntax --edition=2018 /opt/cargo/registry/src/github.com-1ecc6299db9ec823/regex-syntax-0.6.25/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no --cfg 'feature="default"' --cfg 'feature="unicode"' --cfg 'feature="unicode-age"' --cfg 'feature="unicode-bool"' --cfg 'feature="unicode-case"' --cfg 'feature="unicode-gencat"' --cfg 'feature="unicode-perl"' --cfg 'feature="unicode-script"' --cfg 'feature="unicode-segment"' -C metadata=fc954162c3ed8ec3 -C extra-filename=-fc954162c3ed8ec3 --out-dir /hello/target/release/deps -L dependency=/hello/target/release/deps --cap-lints allow` (signal: 11, SIGSEGV: invalid memory reference) + +# valgrind rustc --crate-name regex_syntax --edition=2018 /opt/cargo/registry/src/github.com-1ecc6299db9ec823/regex-syntax-0.6.25/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no --cfg 'feature="default"' --cfg 'feature="unicode"' --cfg 'feature="unicode-age"' --cfg 'feature="unicode-bool"' --cfg 'feature="unicode-case"' --cfg 'feature="unicode-gencat"' --cfg 'feature="unicode-perl"' --cfg 'feature="unicode-script"' --cfg 'feature="unicode-segment"' -C metadata=fc954162c3ed8ec3 -C extra-filename=-fc954162c3ed8ec3 --out-dir /hello/target/release/deps -L dependency=/hello/target/release/deps --cap-lints allow +==977== Memcheck, a memory error detector +==977== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. +==977== Using Valgrind-3.17.0 and LibVEX; rerun with -h for copyright info +==977== Command: rustc --crate-name regex_syntax --edition=2018 /opt/cargo/registry/src/github.com-1ecc6299db9ec823/regex-syntax-0.6.25/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no --cfg feature="default" --cfg feature="unicode" --cfg feature="unicode-age" --cfg feature="unicode-bool" --cfg feature="unicode-case" --cfg feature="unicode-gencat" --cfg feature="unicode-perl" --cfg feature="unicode-script" --cfg feature="unicode-segment" -C metadata=fc954162c3ed8ec3 -C extra-filename=-fc954162c3ed8ec3 --out-dir /hello/target/release/deps -L dependency=/hello/target/release/deps --cap-lints allow +==977== +{"artifact":"/hello/target/release/deps/regex_syntax-fc954162c3ed8ec3.d","emit":"dep-info"} +{"artifact":"/hello/target/release/deps/libregex_syntax-fc954162c3ed8ec3.rmeta","emit":"metadata"} +/opt/rustup/toolchains/1.60.0-x86_64-unknown-linux-gnu/bin/../lib/librustc_driver-75e5f32fc3580f6c.so(+0x4b3d23)[0x400215fd23] +/lib/x86_64-linux-gnu/libc.so.6(+0x42520)[0x4005cab520] +/opt/rustup/toolchains/1.60.0-x86_64-unknown-linux-gnu/bin/../lib/../lib/libLLVM-14-rust-1.60.0-stable.so(_ZNK4llvm13AttributeList19addAttributeAtIndexERNS_11LLVMContextEjNS_9AttributeE+0x834)[0x40088d3484] +/opt/rustup/toolchains/1.60.0-x86_64-unknown-linux-gnu/bin/../lib/../lib/libLLVM-14-rust-1.60.0-stable.so(_ZN4llvm8Function19addAttributeAtIndexEjNS_9AttributeE+0x18)[0x40088d2c48] +/opt/rustup/toolchains/1.60.0-x86_64-unknown-linux-gnu/bin/../lib/librustc_driver-75e5f32fc3580f6c.so(_RNvXs4_NtCsfrnhObXyzQM_18rustc_codegen_llvm3abiINtNtNtCsaEkRwEFRwNk_12rustc_target3abi4call5FnAbiNtNtCs12ixbLjc5mB_12rustc_middle2ty2TyENtB5_12FnAbiLlvmExt16apply_attrs_llfn+0x101)[0x40033d52e1] +/opt/rustup/toolchains/1.60.0-x86_64-unknown-linux-gnu/bin/../lib/librustc_driver-75e5f32fc3580f6c.so(_RNvXNtCsfrnhObXyzQM_18rustc_codegen_llvm9mono_itemNtNtB4_7context9CodegenCxNtNtNtCsegTyfRY58Oj_17rustc_codegen_ssa6traits7declare16PreDefineMethods12predefine_fn+0x56a)[0x40033bba5a] +/opt/rustup/toolchains/1.60.0-x86_64-unknown-linux-gnu/bin/../lib/librustc_driver-75e5f32fc3580f6c.so(+0x17007c0)[0x40033ac7c0] +/opt/rustup/toolchains/1.60.0-x86_64-unknown-linux-gnu/bin/../lib/librustc_driver-75e5f32fc3580f6c.so(+0x23761e6)[0x40040221e6] +/opt/rustup/toolchains/1.60.0-x86_64-unknown-linux-gnu/bin/../lib/librustc_driver-75e5f32fc3580f6c.so(+0x2373a6f)[0x400401fa6f] +/opt/rustup/toolchains/1.60.0-x86_64-unknown-linux-gnu/bin/../lib/librustc_driver-75e5f32fc3580f6c.so(+0x23a1e45)[0x400404de45] +/opt/rustup/toolchains/1.60.0-x86_64-unknown-linux-gnu/bin/../lib/librustc_driver-75e5f32fc3580f6c.so(_RNvXs5_CsfrnhObXyzQM_18rustc_codegen_llvmNtB5_18LlvmCodegenBackendNtNtNtCsegTyfRY58Oj_17rustc_codegen_ssa6traits7backend14CodegenBackend13codegen_crate+0xda)[0x400400e70a] +/opt/rustup/toolchains/1.60.0-x86_64-unknown-linux-gnu/bin/../lib/librustc_driver-75e5f32fc3580f6c.so(+0x23544e7)[0x40040004e7] +/opt/rustup/toolchains/1.60.0-x86_64-unknown-linux-gnu/bin/../lib/librustc_driver-75e5f32fc3580f6c.so(+0x233ac88)[0x4003fe6c88] +/opt/rustup/toolchains/1.60.0-x86_64-unknown-linux-gnu/bin/../lib/librustc_driver-75e5f32fc3580f6c.so(_RNvMs0_NtCsf5CM6ndXTHU_15rustc_interface7queriesNtB5_7Queries15ongoing_codegen+0xaf)[0x4003fdd02f] +/opt/rustup/toolchains/1.60.0-x86_64-unknown-linux-gnu/bin/../lib/librustc_driver-75e5f32fc3580f6c.so(+0x2308b04)[0x4003fb4b04] +/opt/rustup/toolchains/1.60.0-x86_64-unknown-linux-gnu/bin/../lib/librustc_driver-75e5f32fc3580f6c.so(+0x22ee134)[0x4003f9a134] +/opt/rustup/toolchains/1.60.0-x86_64-unknown-linux-gnu/bin/../lib/librustc_driver-75e5f32fc3580f6c.so(+0x23213e9)[0x4003fcd3e9] +/opt/rustup/toolchains/1.60.0-x86_64-unknown-linux-gnu/bin/../lib/libstd-8d61b92a0a02f53a.so(rust_metadata_std_cd3cf6af28dff6de+0xa7d03)[0x400598fd03] +/lib/x86_64-linux-gnu/libc.so.6(+0x94947)[0x4005cfd947] +/lib/x86_64-linux-gnu/libc.so.6(clone+0x44)[0x4005d8da44] +Segmentation fault (core dumped) +``` diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/99 b/gitlab/issues_text/target_missing/host_missing/accel_missing/99 new file mode 100644 index 000000000..b48878e5c --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/99 @@ -0,0 +1 @@ +Feature Request: Please add TCG OPAL 2 emulation support to the virtio disk emulation diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/991 b/gitlab/issues_text/target_missing/host_missing/accel_missing/991 new file mode 100644 index 000000000..881a1de20 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/991 @@ -0,0 +1,6 @@ +Failed to get write lock on qcow2 image from a sigkilled vm +Additional information: +That feature will solve an issue i have with qemu that i muself created +by sending a `kill -9` to a qemu VM after it stopped accepting vnc connections. +I can't use the same qcow2 image currently. Maybe a reboot will fix it, but i did +check `lslocks` and there was no lock on it there. diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/994 b/gitlab/issues_text/target_missing/host_missing/accel_missing/994 new file mode 100644 index 000000000..6d3808551 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/994 @@ -0,0 +1,5 @@ +7.0.0-rc4 doesn't launch on Windows +Description of problem: +The program immediately exits, without even printing version information (or anything). +Steps to reproduce: +1. Run the command above diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/996 b/gitlab/issues_text/target_missing/host_missing/accel_missing/996 new file mode 100644 index 000000000..8a3a71c38 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/996 @@ -0,0 +1,26 @@ +Alt-TAB minimizes a full screen key-grabbed SDL window +Description of problem: +I was made aware of a case where a qemu seems to respond to a keyboard event `Alt+Tab` that isn't meant for it. + +When running in "SDL + full-screen + keys being grabbed by the guest" (see steps to reproduce below) one would expect `Alt+Tab` to do nothing on the host. But it does minimize the qemu window. + +This does not happen if: +- using GTK instead of SDL +- not being in full-screen mode + +No error message or warning appears while this happens. +Steps to reproduce: +You do not need and workload to run inside qemu for this + +1. `qemu-system-x86_64 -display sdl` +2. Get your key grabbed: `click inside the window` +3. Go full screen: `Alt+Ctrl+F` +4. Press `Alt+Tab` +5. Expected: nothing, Experienced: window minimizes + +Note: it even is reproducible if running the qemu binary from another system through SSH with X11 forwarding. + +P.S. +I haven't had a chance yet to try qemu 7.0 from git, but will in a bit. +It is easy enough to reproduce that I considered it worth filing without. +For the start it would be great to hear if others see that as well or not. In case of the latter we'd have to compare library versions (currently I use sdl 2.0.20+dfsg-2build1). diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/997 b/gitlab/issues_text/target_missing/host_missing/accel_missing/997 new file mode 100644 index 000000000..1c19b47b4 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/997 @@ -0,0 +1,17 @@ +Iothread is stuck at 100% CPU usage with virtio-scsi on QEMU 7.0.0 +Description of problem: +Starting with QEMU 7.0.0, the iothread associated attached to a virtio-scsi controller is stuck at 100% CPU usage. Bisected to: https://gitlab.com/qemu-project/qemu/-/commit/826cc32423db2a99d184dbf4f507c737d7e7a4ae + +- Works as expected without the iothread +- No issue with virtio-blk + iothread +- Same behavior regardless of io=threads/native/io_uring +- Same behavior with default vs increased queue count +- The issue is triggered when the guest OS initializes the virtio driver +Steps to reproduce: +1. Add virtio-scsi controller with iothread +2. Boot VM +3. Check per-thread CPU usage such as in htop +Additional information: +[fedora.log](/uploads/776fbf8e5b823d0ab326946684ef9022/fedora.log) + +[fedora.xml](/uploads/54879e5adfb227ddef79d382e86fc608/fedora.xml) diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/999 b/gitlab/issues_text/target_missing/host_missing/accel_missing/999 new file mode 100644 index 000000000..279b74590 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/999 @@ -0,0 +1,6 @@ +Update ipv4 function calls +Description of problem: +Qemu still uses obsolete ipv4 functions, it would be fine to convert them to their ipv6 counterparts: +* gethostbyname +* inet_aton +* inet_ntoa |