[Qemu-devel] [Bug 1838066] [NEW] unexpected error: raw_reconfigure_getfd(): qemu-system-x86_64: Could not reopen file

[Steffen (Daode) Nurpmeso]

Public bug reported:

  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!!

** Affects: qemu
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1838066

Title:
  unexpected error: raw_reconfigure_getfd(): qemu-system-x86_64: Could
  not reopen file

Status in QEMU:
  New

Bug description:
    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!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1838066/+subscriptions