I'm wondering if it's because of the QEMU_BIN is different on RHEL so bcvk cannot find it, because I cannot find the qemu-kvm process in the running pod
$ rustc --version
rustc 1.91.0 (f8297e351 2025-10-28)
$ cargo --version
cargo 1.91.0 (ea2d97820 2025-10-10)
$ rpm -q qemu-kvm
qemu-kvm-9.1.0-15.el10_0.3.x86_64
$ rpm -q virtiofsd
virtiofsd-1.13.2-1.el10_0.x86_64
$ rpm -q podman
podman-5.4.0-13.el10_0.x86_64
$ RUST_LOG=debug bcvk ephemeral run-ssh quay.io/centos-bootc/centos-bootc:stream10
DEBUG Starting ephemeral VM...
DEBUG Running QEMU inside hybrid container for quay.io/centos-bootc/centos-bootc:stream10
DEBUG Podman command: "podman" "run" "--label=bcvk.ephemeral=1" "--mount=type=tmpfs,target=/run" "--rm" "-d" "--cap-add=all" "--security-opt=label=disable" "--security-opt=seccomp=unconfined
" "--security-opt=unmask=/proc/*" "-v" "/sys:/sys:ro" "-v" "/var/tmp:/var/tmp" "--device=/dev/kvm" "--device=/dev/vhost-vsock" "-v" "/usr:/run/hostusr:ro" "-v" "/tmp/.tmpEeJV5A/entrypoint:/v
ar/lib/bcvk/entrypoint" "-v" "/home/wshi/bin/bcvk:/run/selfexe:ro" "--stop-signal=SIGKILL" "--mount=type=image,source=quay.io/centos-bootc/centos-bootc:stream10,target=/run/source-image,rw=t
rue" "-e" "BCK_CONFIG={\"image\":\"quay.io/centos-bootc/centos-bootc:stream10\",\"common\":{\"memory\":{\"memory\":\"4G\"},\"vcpus\":null,\"console\":false,\"debug\":false,\"virtio_serial_ou
t\":[],\"execute\":[],\"ssh_keygen\":true},\"podman\":{\"tty\":false,\"interactive\":false,\"detach\":true,\"rm\":true,\"name\":null,\"network\":null,\"label\":[],\"env\":[]},\"bind_mounts\"
:[],\"ro_bind_mounts\":[],\"systemd_units_dir\":null,\"bind_storage_ro\":false,\"add_swap\":null,\"mount_disk_files\":[],\"kernel_args\":[]}" "quay.io/centos-bootc/centos-bootc:stream10" "/v
ar/lib/bcvk/entrypoint"
DEBUG Ephemeral VM started with container ID: 4ad06fb4e816e72766465a25363d71543aefc6d39d154329c2ee4bf6950d358e
DEBUG Using container ID: 4ad06fb4e816e72766465a25363d71543aefc6d39d154329c2ee4bf6950d358e
⠁ Starting VM...
DEBUG Waiting for VM readiness via supervisor status file (timeout: 240s)...
⠉ Starting VM...
DEBUG Status update: Some(WaitingForSystemd)
⠉ Waiting for systemd...
DEBUG Waiting for systemd to initialize...
⠒ Waiting for systemd...
DEBUG Status update: Some(WaitingForSystemd)
⠒ Waiting for systemd...
DEBUG Waiting for systemd to initialize...
⠤ Waiting for systemd...
$ podman exec -ti naughty_burnell bash
bash-5.2# ps auxwf
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 58 0.0 0.0 4260 3504 pts/0 Ss 02:02 0:00 bash
root 59 0.0 0.0 6196 3456 pts/0 R+ 02:02 0:00 \_ ps auxwf
root 34 0.0 0.0 3996 3304 ? Ss 02:01 0:00 /bin/bash /var/lib/bcvk/entrypoint monitor-status
root 37 0.0 0.0 3584 1940 ? S 02:01 0:00 \_ bwrap --as-pid-1 --unshare-pid --bind /run/tmproot / --proc /proc --dev-bind /dev /dev --bind /var/tmp /var/tmp --tmpfs
root 38 0.0 0.0 955796 6652 ? Sl 02:01 0:00 \_ /run/selfexe container-entrypoint monitor-status
root 1 0.0 0.0 3996 3048 ? Ss 02:01 0:00 /bin/bash /var/lib/bcvk/entrypoint
root 15 0.0 0.0 3584 2072 ? S 02:01 0:00 bwrap --as-pid-1 --unshare-pid --bind /run/tmproot / --proc /proc --dev-bind /dev /dev --bind /var/tmp /var/tmp --tmpfs /ru
root 16 0.0 0.0 955652 6776 ? Sl 02:01 0:00 \_ /run/selfexe container-entrypoint run-ephemeral
root 54 0.0 0.0 72900 3924 ? Sl 02:01 0:00 \_ /usr/libexec/virtiofsd --socket-path /run/inner-shared/virtiofs.sock --shared-dir /run/source-image --cache=never -
I'm wondering if it's because of the QEMU_BIN is different on RHEL so bcvk cannot find it, because I cannot find the qemu-kvm process in the running pod