diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 07:27:52 +0000 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 07:27:52 +0000 |
| commit | d0c85e36e4de67af628d54e9ab577cc3fad7796a (patch) | |
| tree | f8f784b0f04343b90516a338d6df81df3a85dfa2 /results/classifier/deepseek-2-tmp/output/permissions | |
| parent | 7f4364274750eb8cb39a3e7493132fca1c01232e (diff) | |
| download | emulator-bug-study-d0c85e36e4de67af628d54e9ab577cc3fad7796a.tar.gz emulator-bug-study-d0c85e36e4de67af628d54e9ab577cc3fad7796a.zip | |
add deepseek and gemma results
Diffstat (limited to 'results/classifier/deepseek-2-tmp/output/permissions')
33 files changed, 0 insertions, 682 deletions
diff --git a/results/classifier/deepseek-2-tmp/output/permissions/1018530 b/results/classifier/deepseek-2-tmp/output/permissions/1018530 deleted file mode 100644 index a460f1a8..00000000 --- a/results/classifier/deepseek-2-tmp/output/permissions/1018530 +++ /dev/null @@ -1,53 +0,0 @@ - -No write access in a 9p/virtfs shared folder - -Ubuntu version: Ubuntu 12.04 LTS -Kernel: 3.2.0-25-generic -Version of qemu-kvm: 1.0+noroms-0ubuntu13 - -I have created an shared folder for an virtual machine which is managed by libvirt. - -<filesystem type='mount' accessmode='passthrough'> -<source dir='/storage/data'/> -<target dir='data'/> -<address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> -</filesystem> - -I mounted it in the virtual machine with this command: mount -t 9p -o trans=virtio,version=9p2000.L data /data -The filesystem permissions of all files an folders in the shared folder are set to 777. I expected that I have the full permissions also in the virtual machine. - -Regardless of the permissions on the filesystem I cannot write or create files and folders in the virtual machine. The original filesystem (/storage) is XFS. -In another shared folder (similar config in libvirt) which is originally NTFS I have no problems. - -ProblemType: Bug -DistroRelease: Ubuntu 12.04 -Package: qemu-kvm 1.0+noroms-0ubuntu13 -ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 -Uname: Linux 3.2.0-25-generic x86_64 -ApportVersion: 2.0.1-0ubuntu8 -Architecture: amd64 -Date: Wed Jun 27 20:15:20 2012 -InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Beta amd64 (20120409) -MachineType: To be filled by O.E.M. To be filled by O.E.M. -ProcEnviron: - TERM=xterm - LANG=de_DE.UTF-8 - SHELL=/bin/bash -ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-25-generic root=/dev/mapper/system-root ro -SourcePackage: qemu-kvm -UpgradeStatus: No upgrade log present (probably fresh install) -dmi.bios.date: 04/18/2012 -dmi.bios.vendor: American Megatrends Inc. -dmi.bios.version: 1208 -dmi.board.asset.tag: To be filled by O.E.M. -dmi.board.name: M5A99X EVO -dmi.board.vendor: ASUSTeK COMPUTER INC. -dmi.board.version: Rev 1.xx -dmi.chassis.asset.tag: To Be Filled By O.E.M. -dmi.chassis.type: 3 -dmi.chassis.vendor: To Be Filled By O.E.M. -dmi.chassis.version: To Be Filled By O.E.M. -dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1208:bd04/18/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99XEVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: -dmi.product.name: To be filled by O.E.M. -dmi.product.version: To be filled by O.E.M. -dmi.sys.vendor: To be filled by O.E.M.
\ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/permissions/1027525 b/results/classifier/deepseek-2-tmp/output/permissions/1027525 deleted file mode 100644 index b7b73027..00000000 --- a/results/classifier/deepseek-2-tmp/output/permissions/1027525 +++ /dev/null @@ -1,30 +0,0 @@ - -Unable to insert cd media located on ro nfs mount - -When issuing a "change" command via the monitor, qemu is unable to open the iso file if it is mounted on a read-only nfs share. If I mount read-write (and make sure the file is writable by the qemu process), then the change command succeeds. Note that this doesn't affect media specified on the command line when starting qemu, only when changing via the monitor. - -To reproduce, mount cd images directory read only, e.g. - -[root@kvmhost0 ~]# grep iso /etc/fstab -10.48.50.20:/iso /srv/kvm/iso nfs4 defaults,ro 0 0 - -Start qemu with minimal options, just need access to the monitor: - -[root@kvmhost0 ~]# kvm -vnc 127.0.0.1:0 -S - -Connect to the monitor and issue a change command: - -(qemu) change ide1-cd0 /srv/kvm/iso/ubuntu-12.04-server-amd64.iso -Could not open '/srv/kvm/iso/ubuntu-12.04-server-amd64.iso - -Re-mount the iso directory read-write and notice that the command succeeds: - -[root@kvmhost0 ~]# mount -o remount,rw /srv/kvm/iso - -(qemu) change ide1-cd0 /srv/kvm/iso/ubuntu-12.04-server-amd64.iso -(qemu) - -[root@kvmhost0 ~]# kvm --version -QEMU emulator version 1.1.1 (qemu-kvm-1.1.1), Copyright (c) 2003-2008 Fabrice Bellard -[root@kvmhost0 ~]# uname -a -Linux kvmhost0 3.4.5-1-ARCH #1 SMP PREEMPT Mon Jul 16 21:35:54 CEST 2012 x86_64 GNU/Linux
\ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/permissions/1066 b/results/classifier/deepseek-2-tmp/output/permissions/1066 deleted file mode 100644 index f62a6bf1..00000000 --- a/results/classifier/deepseek-2-tmp/output/permissions/1066 +++ /dev/null @@ -1,33 +0,0 @@ - -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/results/classifier/deepseek-2-tmp/output/permissions/122 b/results/classifier/deepseek-2-tmp/output/permissions/122 deleted file mode 100644 index b7d924ad..00000000 --- a/results/classifier/deepseek-2-tmp/output/permissions/122 +++ /dev/null @@ -1,2 +0,0 @@ - -linux-user does not check PROT_EXEC diff --git a/results/classifier/deepseek-2-tmp/output/permissions/1432103 b/results/classifier/deepseek-2-tmp/output/permissions/1432103 deleted file mode 100644 index a963011e..00000000 --- a/results/classifier/deepseek-2-tmp/output/permissions/1432103 +++ /dev/null @@ -1,4 +0,0 @@ - -error in x86 executable segment permission check - -When the code segment register (%cs) selects an executable segment with no read permission, mov instructions that read from the segment via %cs prefix can still succeed without causing a general protection error.
\ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/permissions/1500265 b/results/classifier/deepseek-2-tmp/output/permissions/1500265 deleted file mode 100644 index 26339ab8..00000000 --- a/results/classifier/deepseek-2-tmp/output/permissions/1500265 +++ /dev/null @@ -1,6 +0,0 @@ - -nested 9p filesystem with security_model=mapped-xattr - -I do not know whether this is a bug or a feature request, but on a 9p virtfs with security_model=mapped-xattr, access to extended attributes starting with "user.virtfs" coming from the guest seem to be silently ignored. Would it not be more correct to use some sort of "escaping", say map to "user.virtfs.x" on guest to "user.virtfs.virtfs.x" on host or something like that, so that the guest can use arbitrary attributes. - -In particular, this would allow nested virtual machines to use nested 9p virtfs with security_model=mapped-xattr.
\ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/permissions/1505652 b/results/classifier/deepseek-2-tmp/output/permissions/1505652 deleted file mode 100644 index 7bab0d55..00000000 --- a/results/classifier/deepseek-2-tmp/output/permissions/1505652 +++ /dev/null @@ -1,53 +0,0 @@ - -An IO error happen when qemu snapshot-create - -My qemu version is 1.7.1,but when I try to make live snapshot by libvirt,the libvirt sometimes report an error :qemuMonitorJSONCheckError:377 : internal error: unable to execute QEMU command 'transaction': An IO error has occurred. - -Here is the command being snpshot create by virsh: -virsh snapshot-create snapshot-test.vm snapshot.xml --no-metadata --disk-only --reuse-external -the snapshot.xml: -<domainsnapshot> - <description>test</description> - <disks> - <disk name='vda' snapshot="external"> - <source dev='/home/disk/sbd8' file='/home/disk/sdb8' type="block"/> - </disk> - </disks> -</domainsnapshot> - - -I have read the qemu code about the snapshot create, and I find the qemu when call the function handle_aiocb_rw_linear(): -static ssize_t handle_aiocb_rw_linear(RawPosixAIOData *aiocb, char *buf) -{ - ssize_t offset = 0; - ssize_t len; - - while (offset < aiocb->aio_nbytes) { - if (aiocb->aio_type & QEMU_AIO_WRITE) { - len = pwrite(aiocb->aio_fildes, - (const char *)buf + offset, - aiocb->aio_nbytes - offset, - aiocb->aio_offset + offset); - } else { - len = pread(aiocb->aio_fildes, - buf + offset, - aiocb->aio_nbytes - offset, - aiocb->aio_offset + offset); - } - if (len == -1 && errno == EINTR) { - continue; - } else if (len == -1) { - offset = -errno; - break; - } else if (len == 0) { - break; - } - offset += len; - } - - return offset; -} - -The function pwrite happen error,the errono is 1,and the error describe:"pwrite failed, Operation not permitted (1, EPERM) because the process does not have the appropriate privileges to use the pwrite system call". -The qemu call stack about is: -external_snapshot_prepare()->bdrv_flush()->...->paio_submit->...->handle_aiocb_rw_linear.
\ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/permissions/1548471 b/results/classifier/deepseek-2-tmp/output/permissions/1548471 deleted file mode 100644 index 619c0662..00000000 --- a/results/classifier/deepseek-2-tmp/output/permissions/1548471 +++ /dev/null @@ -1,10 +0,0 @@ - -Lost of log file during block migration - - Hello, i've discovered that during live block migration -log file is copied(or created on destination) but it actually empty. -When regular(cold) migration is called log file migrates successfully. -I'm working on nova project in openstack and i've tried to fix it by adding -simple scp from source to destination, but log file is owned by libvirt-qemu user -and i cannot do that from regular user created by openstack. -Could explain how can i migrate logs safely?
\ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/permissions/1626972 b/results/classifier/deepseek-2-tmp/output/permissions/1626972 deleted file mode 100644 index 41cdf8ad..00000000 --- a/results/classifier/deepseek-2-tmp/output/permissions/1626972 +++ /dev/null @@ -1,37 +0,0 @@ - -QEMU memfd_create fallback mechanism change for security drivers - -And, when libvirt starts using apparmor, and creating apparmor profiles for every virtual machine created in the compute nodes, mitaka qemu (2.5 - and upstream also) uses a fallback mechanism for creating shared memory for live-migrations. This fall back mechanism, on kernels 3.13 - that don't have memfd_create() system-call, try to create files on /tmp/ directory and fails.. causing live-migration not to work. - -Trusty with kernel 3.13 + Mitaka with qemu 2.5 + apparmor capability = can't live migrate. - -From qemu 2.5, logic is on : - -void *qemu_memfd_alloc(const char *name, size_t size, unsigned int seals, int *fd) -{ - if (memfd_create)... ### only works with HWE kernels - - else ### 3.13 kernels, gets blocked by apparmor - tmpdir = g_get_tmp_dir - ... - mfd = mkstemp(fname) -} - -And you can see the errors: - -From the host trying to send the virtual machine: - -2016-08-15 16:36:26.160 1974 ERROR nova.virt.libvirt.driver [req-0cac612b-8d53-4610-b773-d07ad6bacb91 691a581cfa7046278380ce82b1c38ddd 133ebc3585c041aebaead8c062cd6511 - - -] [instance: 2afa1131-bc8c-43d2-9c4a-962c1bf7723e] Migration operation has aborted -2016-08-15 16:36:26.248 1974 ERROR nova.virt.libvirt.driver [req-0cac612b-8d53-4610-b773-d07ad6bacb91 691a581cfa7046278380ce82b1c38ddd 133ebc3585c041aebaead8c062cd6511 - - -] [instance: 2afa1131-bc8c-43d2-9c4a-962c1bf7723e] Live Migration failure: internal error: unable to execute QEMU command 'migrate': Migration disabled: failed to allocate shared memory - -From the host trying to receive the virtual machine: - -Aug 15 16:36:19 tkcompute01 kernel: [ 1194.356794] type=1400 audit(1471289779.791:72): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-2afa1131-bc8c-43d2-9c4a-962c1bf7723e" pid=12565 comm="apparmor_parser" -Aug 15 16:36:19 tkcompute01 kernel: [ 1194.357048] type=1400 audit(1471289779.791:73): apparmor="STATUS" operation="profile_load" profile="unconfined" name="qemu_bridge_helper" pid=12565 comm="apparmor_parser" -Aug 15 16:36:20 tkcompute01 kernel: [ 1194.877027] type=1400 audit(1471289780.311:74): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-2afa1131-bc8c-43d2-9c4a-962c1bf7723e" pid=12613 comm="apparmor_parser" -Aug 15 16:36:20 tkcompute01 kernel: [ 1194.904407] type=1400 audit(1471289780.343:75): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="qemu_bridge_helper" pid=12613 comm="apparmor_parser" -Aug 15 16:36:20 tkcompute01 kernel: [ 1194.973064] type=1400 audit(1471289780.407:76): apparmor="DENIED" operation="mknod" profile="libvirt-2afa1131-bc8c-43d2-9c4a-962c1bf7723e" name="/tmp/memfd-tNpKSj" pid=12625 comm="qemu-system-x86" requested_mask="c" denied_mask="c" fsuid=107 ouid=107 -Aug 15 16:36:20 tkcompute01 kernel: [ 1194.979871] type=1400 audit(1471289780.411:77): apparmor="DENIED" operation="open" profile="libvirt-2afa1131-bc8c-43d2-9c4a-962c1bf7723e" name="/tmp/" pid=12625 comm="qemu-system-x86" requested_mask="r" denied_mask="r" fsuid=107 ouid=0 -Aug 15 16:36:20 tkcompute01 kernel: [ 1194.979881] type=1400 audit(1471289780.411:78): apparmor="DENIED" operation="open" profile="libvirt-2afa1131-bc8c-43d2-9c4a-962c1bf7723e" name="/var/tmp/" pid=12625 comm="qemu-system-x86" requested_mask="r" denied_mask="r" fsuid=107 ouid=0 - -When leaving libvirt without apparmor capabilities (thus not confining virtual machines on compute nodes, the live migration works as expected, so, clearly, apparmor is stepping into the live migration). I'm sure that virtual machines have to be confined and that this isn't the desired behaviour...
\ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/permissions/1649236 b/results/classifier/deepseek-2-tmp/output/permissions/1649236 deleted file mode 100644 index 35220edb..00000000 --- a/results/classifier/deepseek-2-tmp/output/permissions/1649236 +++ /dev/null @@ -1,20 +0,0 @@ - -Commit snapshot fails with Permission denied when daemonized - -When running qemu with daemonize option it is impossible to run "commit all" in monitor. - -I run qemu 2.7.0 under gentoo 64 bit distribution with following command line: - -qemu-system-x86_64 -m 4096 -cpu host -smp 2 -enable-kvm -snapshot \ - -drive file=vm.img,if=virtio \ - -net nic,model=virtio,macaddr=11:11:11:11:11:11 \ - -net tap,ifname=tap$PORT,script=no,downscript=no \ - -vnc :1 -daemonize \ - -chardev vc,id=mon0 -mon chardev=mon0,mode=readline \ - -chardev socket,id=mon1,host=localhost,port=10001,server,nowait -mon chardev=mon1,mode=control - -I connect to vm through VNC viewer and press CTRL+ALT+2 and run "commit all" command. -Following error is shown: -`commit` error for `all`: Permission denied - -When I run my VM without `daemonize` option the command "commit all" works without errors.
\ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/permissions/1653577 b/results/classifier/deepseek-2-tmp/output/permissions/1653577 deleted file mode 100644 index 7c009f25..00000000 --- a/results/classifier/deepseek-2-tmp/output/permissions/1653577 +++ /dev/null @@ -1,4 +0,0 @@ - -Ability to set umask for 9pfs - -We should be able to specify the umask for 9pfs so that files created by the guest can be accessed by other users on the host. Currently they're only accessible by the user running qemu (and of course, root).
\ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/permissions/1700380 b/results/classifier/deepseek-2-tmp/output/permissions/1700380 deleted file mode 100644 index af7531d2..00000000 --- a/results/classifier/deepseek-2-tmp/output/permissions/1700380 +++ /dev/null @@ -1,13 +0,0 @@ - -commit snapshot image got Permission denied error - -qemu 2.9.0, adm64, start image with -snapshot param, make some changes in the image, then: - -$telnet localhost 7000 - -(qemu) commit virtio0 -'commit' error for 'virtio0': Permission denied - -Nerver met this problem before, commit is ok. I recently compiled v2.9.0, so is there some new param in qemu-qemu-system-x86_64 to avoid commit Permission denied? - -Regards.
\ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/permissions/1779955 b/results/classifier/deepseek-2-tmp/output/permissions/1779955 deleted file mode 100644 index bc711e54..00000000 --- a/results/classifier/deepseek-2-tmp/output/permissions/1779955 +++ /dev/null @@ -1,31 +0,0 @@ - -qemu linux-user requires read permissions on memory passed to syscalls that should only need write access - -When read() function takes an mmap'ed address as output buffer, it returns EFAULT. The expected behavior is it should just work. - -The following code works for qemu-system-arm, but not for qemu-arm-static. - - - -Steps to reproduce (please substitute /path/to/qemu-arm-static with the path of the binary, and /tmp/a.cpp with the example source code attached): - -# First register binfmt_misc -[hidden]$ docker run --rm --privileged multiarch/qemu-user-static:register --reset - -# Compile the code and run -[hidden]$ docker run --rm -it -v /tmp/a.cpp:/tmp/a.cpp -v /path/to/qemu-arm-static:/usr/bin/qemu-arm-static arm32v7/ubuntu:18.04 bash -c '{ apt update -y && apt install -y g++; } >& /dev/null && g++ -std=c++14 /tmp/a.cpp -o /tmp/a.out && echo hehe > /tmp/haha.txt && /tmp/a.out' -ofd=3 -ftruncate=0 -mmap=0xff3f5000 -fd=4 -0xff3f5023 -1 14 - - - -The expected result in qemu-system-arm as well as natively on x86_64 host: -hidden$ ./a.out -ofd=3 -ftruncate=0 -mmap=0xb6fb7000 -fd=4 -0xb6fb7023 5 0
\ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/permissions/1810400 b/results/classifier/deepseek-2-tmp/output/permissions/1810400 deleted file mode 100644 index 9d6ebc5b..00000000 --- a/results/classifier/deepseek-2-tmp/output/permissions/1810400 +++ /dev/null @@ -1,33 +0,0 @@ - - Failed to make dirty bitmaps writable: Can't update bitmap directory: Operation not permitted - -blockcommit does not work if there is dirty block. - -virsh version -Compiled against library: libvirt 4.10.0 -Using library: libvirt 4.10.0 -Using API: QEMU 4.10.0 -Running hypervisor: QEMU 2.12.0 - -Scenario: -1. Create an instance -2. Add dirty bitmap to vm disk. -3. create a snapshot(external or internal) -4. revert snapshot or blockcommit disk - -virsh blockcommit rota-test vda --active -Active Block Commit started - -virsh blockjob rota-test vda --info -No current block job for vda - - -rota-test.log: - starting up libvirt version: 4.10.0, package: 1.el7 (CBS <email address hidden>, 2018-12-05-12:27:12, c1bk.rdu2.centos.org), qemu version: 2.12.0qemu-kvm-ev-2.12.0-18.el7_6.1.1, kernel: 4.1.12-103.9.7.el7uek.x86_64, hostname: vm-kvm07 -LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin QEMU_AUDIO_DRV=spice /usr/libexec/qemu-kvm -name guest=rota-test,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-101-rota-test/master-key.aes -machine pc-i440fx-rhel7.0.0,accel=kvm,usb=off,dump-guest-core=off -cpu SandyBridge,hypervisor=on,xsaveopt=on -m 8192 -realtime mlock=off -smp 3,sockets=3,cores=1,threads=1 -uuid 50dec55c-a80a-4adc-a788-7ba23230064e -no-user-config -nodefaults -chardev socket,id=charmonitor,fd=59,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x5.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x5 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x5.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x5.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x6 -drive file=/var/lib/libvirt/images/rota-0003,format=qcow2,if=none,id=drive-virtio-disk0,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1,write-cache=on -netdev tap,fd=61,id=hostnet0,vhost=on,vhostfd=62 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:e8:09:94,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -spice port=5902,addr=0.0.0.0,disable-ticketing,seamless-migration=on -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x2 -chardev spicevmc,id=charredir0,name=usbredir -device usb-redir,chardev=charredir0,id=redir0,bus=usb.0,port=2 -chardev spicevmc,id=charredir1,name=usbredir -device usb-redir,chardev=charredir1,id=redir1,bus=usb.0,port=3 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg timestamp=on -2019-01-03T07:50:43.810142Z qemu-kvm: -chardev pty,id=charserial0: char device redirected to /dev/pts/3 (label charserial0) -main_channel_link: add main channel client -red_qxl_set_cursor_peer: -inputs_connect: inputs channel client create -inputs_channel_detach_tablet: -#block339: Failed to make dirty bitmaps writable: Can't update bitmap directory: Operation not permitted
\ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/permissions/1832877 b/results/classifier/deepseek-2-tmp/output/permissions/1832877 deleted file mode 100644 index 4483e3a6..00000000 --- a/results/classifier/deepseek-2-tmp/output/permissions/1832877 +++ /dev/null @@ -1,30 +0,0 @@ - -qemu-bridge-helper undocumented and broken - -qemu output: - -access denied by acl file -qemu-system-ppc64: bridge helper failed - -Option description: - - -netdev bridge,id=id[,br=bridge][,helper=helper] - Connect a host TAP network interface to a host bridge device. - - Use the network helper helper to configure the TAP interface and attach it to the bridge. The default network - helper executable is /path/to/qemu-bridge-helper and the default bridge device is br0. - - Examples: - - #launch a QEMU instance with the default network helper to - #connect a TAP device to bridge br0 - qemu-system-i386 linux.img -netdev bridge,id=n1 -device virtio-net,netdev=n1 - - - - #launch a QEMU instance with the default network helper to - #connect a TAP device to bridge qemubr0 - qemu-system-i386 linux.img -netdev bridge,br=qemubr0,id=n1 -device virtio-net,netdev=n1 - - -What is the acl file? What is the interface to qemu-bridge-helper?
\ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/permissions/1832916 b/results/classifier/deepseek-2-tmp/output/permissions/1832916 deleted file mode 100644 index 18ff6dd9..00000000 --- a/results/classifier/deepseek-2-tmp/output/permissions/1832916 +++ /dev/null @@ -1,6 +0,0 @@ - -linux-user does not check PROT_EXEC - -At no point do we actually verify that a page is PROT_EXEC before translating. All we end up verifying is that the page is readable. Not the same thing, obviously. - -The following test case should work for any architecture, though I've only validated it for x86_64 and aarch64.
\ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/permissions/1838066 b/results/classifier/deepseek-2-tmp/output/permissions/1838066 deleted file mode 100644 index b94ecc0a..00000000 --- a/results/classifier/deepseek-2-tmp/output/permissions/1838066 +++ /dev/null @@ -1,25 +0,0 @@ - -unexpected error: raw_reconfigure_getfd(): qemu-system-x86_64: Could not reopen file - - Unexpected error in raw_reconfigure_getfd() at block/file-posix.c:923: - qemu-system-x86_64: Could not reopen file: Permission denied - Aborted - -Is what i sometimes (only) get, mostly for Linux guests i'd say (Arch just a few moments ago). -This is on CRUX-Linux, thus a self-compiled qemu 4.0.0 with default recipe, without special compiler flags (-O2 -march=x86-64 -pipe) on an Intel i5 laptop. -But what i do is running this via sudo: - - sudo='sudo --preserve-env=VMNAME,VMADDR' runas='-runas vm -chroot .' - fi - - VMADDR=$addr VMNAME=$vmname - export VMADDR VMNAME - eval exec $sudo qemu-system-x86_64 -name $vmname $runas \ - $host $accel $display $net $vmcustom $vmimg $redir - -the last run ends up like (via sudo) - - qemu-system-x86_64 -name arch-2019 -runas vm -chroot . -cpu host -m size=1984 -smp cpus=2 -enable-kvm -accel accel=kvm,thread=multi -display curses -net nic,netdev=net0,macaddr=.. -netdev tap,id=net0,script=./.ifup.sh,downscript=./.ifdown.sh,ifname=vm_arch-2019 - -vm is a user effectively living in the chroot only without any rights anywhere. -Hope this helps, thanks a lot for qemu!!
\ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/permissions/1838569 b/results/classifier/deepseek-2-tmp/output/permissions/1838569 deleted file mode 100644 index 9386f8e3..00000000 --- a/results/classifier/deepseek-2-tmp/output/permissions/1838569 +++ /dev/null @@ -1,25 +0,0 @@ - -virtio-balloon change breaks post 4.0 upgrade - -We upgraded the libvirt UCA packages from 3.6 to 4.0 as part of a queens upgrade and noticed that -virtio-ballon is broken when instances live migrate (started with a prior 3.6 version) with: - - -2019-07-24T06:46:49.487109Z qemu-system-x86_64: warning: Unknown firmware file in legacy mode: etc/msr_feature_control -2019-07-24T06:47:22.187749Z qemu-system-x86_64: VQ 2 size 0x80 < last_avail_idx 0xb57 - used_idx 0xb59 -2019-07-24T06:47:22.187768Z qemu-system-x86_64: Failed to load virtio-balloon:virtio -2019-07-24T06:47:22.187771Z qemu-system-x86_64: error while loading state for instance 0x0 of device '0000:00:05.0/virtio-balloon' -2019-07-24T06:47:22.188194Z qemu-system-x86_64: load of migration failed: Operation not permitted -2019-07-24 06:47:22.430+0000: shutting down, reason=failed - -This seem to be the exact problem as reported by https://lists.gnu.org/archive/html/qemu-devel/2019-07/msg02228.html - -Listed the packages which changed: - -Start-Date: 2019-07-06 06:40:55 -Commandline: /usr/bin/apt-get -y -o Dpkg::Options::=--force-confdef -o Dpkg::Options::=--force-confold install libvirt-bin python-libvirt qemu qemu-utils qemu-system qemu-system-arm qemu-system-mips qemu-system-ppc qemu-system-sparc qemu-system-x86 qemu-system-misc qemu-block-extra qemu-utils qemu-user qemu-kvm -Install: librdmacm1:amd64 (17.1-1ubuntu0.1~cloud0, automatic), libvirt-daemon-driver-storage-rbd:amd64 (4.0.0-1ubuntu8.10~cloud0, automatic), ipxe-qemu-256k-compat-efi-roms:amd64 (1.0.0+git-20150424.a25a16d-0ubuntu2~cloud0, automatic) -Upgrade: qemu-system-mips:amd64 (1:2.10+dfsg-0ubuntu3.8~cloud1, 1:2.11+dfsg-1ubuntu7.13~cloud0), qemu-system-misc:amd64 (1:2.10+dfsg-0ubuntu3.8~cloud1, 1:2.11+dfsg-1ubuntu7.13~cloud0), qemu-system-ppc:amd64 (1:2.10+dfsg-0ubuntu3.8~cloud1, 1:2.11+dfsg-1ubuntu7.13~cloud0), python-libvirt:amd64 (3.5.0-1build1~cloud0, 4.0.0-1~cloud0), qemu-system-x86:amd64 (1:2.10+dfsg-0ubuntu3.8~cloud1, 1:2.11+dfsg-1ubuntu7.13~cloud0), libvirt-clients:amd64 (3.6.0-1ubuntu6.8~cloud0, 4.0.0-1ubuntu8.10~cloud0), qemu-user:amd64 (1:2.10+dfsg-0ubuntu3.8~cloud1, 1:2.11+dfsg-1ubuntu7.13~cloud0), libvirt-bin:amd64 (3.6.0-1ubuntu6.8~cloud0, 4.0.0-1ubuntu8.10~cloud0), qemu:amd64 (1:2.10+dfsg-0ubuntu3.8~cloud1, 1:2.11+dfsg-1ubuntu7.13~cloud0), qemu-utils:amd64 (1:2.10+dfsg-0ubuntu3.8~cloud1, 1:2.11+dfsg-1ubuntu7.13~cloud0), libvirt-daemon-system:amd64 (3.6.0-1ubuntu6.8~cloud0, 4.0.0-1ubuntu8.10~cloud0), qemu-system-sparc:amd64 (1:2.10+dfsg-0ubuntu3.8~cloud1, 1:2.11+dfsg-1ubuntu7.13~cloud0), qemu-user-binfmt:amd64 (1:2.10+dfsg-0ubuntu3.8~cloud1, 1:2.11+dfsg-1ubuntu7.13~cloud0), qemu-kvm:amd64 (1:2.10+dfsg-0ubuntu3.8~cloud1, 1:2.11+dfsg-1ubuntu7.13~cloud0), libvirt0:amd64 (3.6.0-1ubuntu6.8~cloud0, 4.0.0-1ubuntu8.10~cloud0), qemu-system-arm:amd64 (1:2.10+dfsg-0ubuntu3.8~cloud1, 1:2.11+dfsg-1ubuntu7.13~cloud0), qemu-block-extra:amd64 (1:2.10+dfsg-0ubuntu3.8~cloud1, 1:2.11+dfsg-1ubuntu7.13~cloud0), qemu-system-common:amd64 (1:2.10+dfsg-0ubuntu3.8~cloud1, 1:2.11+dfsg-1ubuntu7.13~cloud0), qemu-system:amd64 (1:2.10+dfsg-0ubuntu3.8~cloud1, 1:2.11+dfsg-1ubuntu7.13~cloud0), libvirt-daemon:amd64 (3.6.0-1ubuntu6.8~cloud0, 4.0.0-1ubuntu8.10~cloud0) -End-Date: 2019-07-06 06:41:08 - -At this point the instances would have to be hard rebooted or stopped/started to fix the issue for future live migration attemps
\ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/permissions/1875139 b/results/classifier/deepseek-2-tmp/output/permissions/1875139 deleted file mode 100644 index 9d4594cb..00000000 --- a/results/classifier/deepseek-2-tmp/output/permissions/1875139 +++ /dev/null @@ -1,20 +0,0 @@ - -Domain fails to start when 'readonly' device not writable - -This issue is introduced in QEMU 4.2.0 (4.1.0 is working fine) - -My root disk is a LVM2 volume thin snapshot that is marked as read-only -But when I try to start the domain (using virt-manager) I get the following error: - -Error starting domain: internal error: process exited while connecting to monitor: 2020-04-26T06:55:06.342700Z qemu-system-x86_64: -blockdev {"driver":"host_device","filename":"/dev/vg/vmroot-20200425","aio":"native","node-name":"libvirt-3-storage","cache":{"direct":true,"no-flush":false},"auto-read-only":true,"discard":"unmap"} The device is not writable: Permission denied - -Changing the lvm snapshot to writeable allows me to start the domain. -(Making it changes possible during domain is running) - -I don't think QEMU should fail when it can't open a (block) device when the read-only option is set. -(why is write access needed?) - -Reproduce steps: -* Create LVM read-only volume (I don't think any data is needed) -* Create domain with read-only volume as block device -* Try to start the domain
\ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/permissions/1891748 b/results/classifier/deepseek-2-tmp/output/permissions/1891748 deleted file mode 100644 index f52d0552..00000000 --- a/results/classifier/deepseek-2-tmp/output/permissions/1891748 +++ /dev/null @@ -1,15 +0,0 @@ - -qemu-arm-static 5.1 can't run gcc - -Issue discovered while trying to build pikvm (1) - -Long story short: when using qemu-arm-static 5.1, gcc exits whith message: - -Allocating guest commpage: Operation not permitted - - -when using qemu-arm-static v5.0, gcc "works" - -Steps to reproduce will follow - -(1) https://github.com/pikvm/pikvm/blob/master/pages/building_os.md
\ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/permissions/1903833 b/results/classifier/deepseek-2-tmp/output/permissions/1903833 deleted file mode 100644 index bc5f97ff..00000000 --- a/results/classifier/deepseek-2-tmp/output/permissions/1903833 +++ /dev/null @@ -1,12 +0,0 @@ - -User mode qemu-aarch: SIGGSEGV signal handler works wrong - -I have a user mode qemu-aarch issue. Program with SIGSEGV signal handler works wrong under qemu-aarch: -once the progam handles the SEGV signal, qemu marks the program's page protected, and signal handler gets SEGV on each subsequent memory access instruction within a program. - -The issue is reproduced on WSL Ubuntu 20.04 under Windows 10, qemu-aarch64 version 5.1.50 -The issue is also reproducible on the latest upstream qemu-aarch build. - -The following workaround disables mprotect call and fixes the issue: https://github.com/BorisUlasevich/qemu/commit/3063d9a64f8395185d65c6b6710d28ee92cd8be5 - -The issue can be reproduced on OpenJDK which reports SIGSEGV immediately after start. The small reproducer program is attached.
\ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/permissions/1922625 b/results/classifier/deepseek-2-tmp/output/permissions/1922625 deleted file mode 100644 index 9f8acfa0..00000000 --- a/results/classifier/deepseek-2-tmp/output/permissions/1922625 +++ /dev/null @@ -1,34 +0,0 @@ - -qemu 5.2.0 configure script explodes when in read only directory - -I extracted the qemu 5.2.0 source as one user, and then tried to run `./configure --help` in that directory as a different user. Normal autoconf configure scripts have no problem with this but yours goes into an infinite loop printing nonsense: - -Using './build' as the directory for build output -mkdir: build: Permission denied -touch: build/auto-created-by-configure: No such file or directory -./configure: line 37: GNUmakefile: Permission denied -./configure: line 59: cd: build: No such file or directory -Using './build' as the directory for build output -mkdir: build: Permission denied -touch: build/auto-created-by-configure: No such file or directory -/path/to/qemu-5.2.0/configure: line 37: GNUmakefile: Permission denied -/path/to/qemu-5.2.0/configure: line 59: cd: build: No such file or directory -Using './build' as the directory for build output -mkdir: build: Permission denied -touch: build/auto-created-by-configure: No such file or directory -/path/to/qemu-5.2.0/configure: line 37: GNUmakefile: Permission denied -/path/to/qemu-5.2.0/configure: line 59: cd: build: No such file or directory -Using './build' as the directory for build output -mkdir: build: Permission denied -touch: build/auto-created-by-configure: No such file or directory -/path/to/qemu-5.2.0/configure: line 37: GNUmakefile: Permission denied -/path/to/qemu-5.2.0/configure: line 59: cd: build: No such file or directory -Using './build' as the directory for build output -mkdir: build: Permission denied -touch: build/auto-created-by-configure: No such file or directory -/path/to/qemu-5.2.0/configure: line 37: GNUmakefile: Permission denied -/path/to/qemu-5.2.0/configure: line 59: cd: build: No such file or directory -Using './build' as the directory for build output -mkdir: build: Permission denied - -etc.
\ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/permissions/2039 b/results/classifier/deepseek-2-tmp/output/permissions/2039 deleted file mode 100644 index 11ef68e2..00000000 --- a/results/classifier/deepseek-2-tmp/output/permissions/2039 +++ /dev/null @@ -1,12 +0,0 @@ - -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/results/classifier/deepseek-2-tmp/output/permissions/2624 b/results/classifier/deepseek-2-tmp/output/permissions/2624 deleted file mode 100644 index cbd1954f..00000000 --- a/results/classifier/deepseek-2-tmp/output/permissions/2624 +++ /dev/null @@ -1,40 +0,0 @@ - -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/results/classifier/deepseek-2-tmp/output/permissions/2747 b/results/classifier/deepseek-2-tmp/output/permissions/2747 deleted file mode 100644 index 03297273..00000000 --- a/results/classifier/deepseek-2-tmp/output/permissions/2747 +++ /dev/null @@ -1,10 +0,0 @@ - -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/results/classifier/deepseek-2-tmp/output/permissions/2915 b/results/classifier/deepseek-2-tmp/output/permissions/2915 deleted file mode 100644 index 0839a4e8..00000000 --- a/results/classifier/deepseek-2-tmp/output/permissions/2915 +++ /dev/null @@ -1,30 +0,0 @@ - -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/results/classifier/deepseek-2-tmp/output/permissions/321 b/results/classifier/deepseek-2-tmp/output/permissions/321 deleted file mode 100644 index 508cead0..00000000 --- a/results/classifier/deepseek-2-tmp/output/permissions/321 +++ /dev/null @@ -1,2 +0,0 @@ - -qemu 5.2.0 configure script explodes when in read only directory diff --git a/results/classifier/deepseek-2-tmp/output/permissions/342 b/results/classifier/deepseek-2-tmp/output/permissions/342 deleted file mode 100644 index d5a8ab8d..00000000 --- a/results/classifier/deepseek-2-tmp/output/permissions/342 +++ /dev/null @@ -1,2 +0,0 @@ - -Assertion `child->perm & BLK_PERM_WRITE' failed in bdrv_co_write_req_prepare through atapi diff --git a/results/classifier/deepseek-2-tmp/output/permissions/465 b/results/classifier/deepseek-2-tmp/output/permissions/465 deleted file mode 100644 index 94b1a45f..00000000 --- a/results/classifier/deepseek-2-tmp/output/permissions/465 +++ /dev/null @@ -1,8 +0,0 @@ - -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/results/classifier/deepseek-2-tmp/output/permissions/515 b/results/classifier/deepseek-2-tmp/output/permissions/515 deleted file mode 100644 index f20a395d..00000000 --- a/results/classifier/deepseek-2-tmp/output/permissions/515 +++ /dev/null @@ -1,32 +0,0 @@ - -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/results/classifier/deepseek-2-tmp/output/permissions/798 b/results/classifier/deepseek-2-tmp/output/permissions/798 deleted file mode 100644 index 8da1f944..00000000 --- a/results/classifier/deepseek-2-tmp/output/permissions/798 +++ /dev/null @@ -1,16 +0,0 @@ - -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/results/classifier/deepseek-2-tmp/output/permissions/807893 b/results/classifier/deepseek-2-tmp/output/permissions/807893 deleted file mode 100644 index 19cbdc2d..00000000 --- a/results/classifier/deepseek-2-tmp/output/permissions/807893 +++ /dev/null @@ -1,32 +0,0 @@ - -qemu privilege escalation - -If qemu is started as root, with -runas, the extra groups is not dropped correctly - -/proc/`pidof qemu`/status -.. -Uid: 100 100 100 100 -Gid: 100 100 100 100 -FDSize: 32 -Groups: 0 1 2 3 4 6 10 11 26 27 -... - -The fix is to add initgroups() or setgroups(1, [gid]) where appropriate to os-posix.c. - -The extra gid's allow read or write access to other files (such as /dev etc). - -Emulating the qemu code: - -# python -... ->>> import os ->>> os.setgid(100) ->>> os.setuid(100) ->>> os.execve("/bin/sh", [ "/bin/sh" ], os.environ) -sh-4.1$ xxd /dev/sda | head -n2 -0000000: eb48 9000 0000 0000 0000 0000 0000 0000 .H.............. -0000010: 0000 0000 0000 0000 0000 0000 0000 0000 ................ -sh-4.1$ ls -l /dev/sda -brw-rw---- 1 root disk 8, 0 Jul 8 11:54 /dev/sda -sh-4.1$ id -uid=100(qemu00) gid=100(users) groups=100(users),0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel),11(floppy),26(tape),27(video)
\ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/permissions/913 b/results/classifier/deepseek-2-tmp/output/permissions/913 deleted file mode 100644 index 7d08003b..00000000 --- a/results/classifier/deepseek-2-tmp/output/permissions/913 +++ /dev/null @@ -1,2 +0,0 @@ - -QEMU Sharing Host files with Guest |