# \#qemux86-64

**URL:** https://hub.mender.io/tag/qemux86-64/183.md

[Latest](https://hub.mender.io/latest.md) · [Categories](https://hub.mender.io/categories.md) · [Tags](https://hub.mender.io/tags.md)

---

## [Same image for QEMU and Raspberry Pi](https://hub.mender.io/t/same-image-for-qemu-and-raspberry-pi/8146)

<div class="topic-metadata">

**Author:** [@pratish](https://hub.mender.io/u/pratish)\
**Replies:** 2\
**Last updated:** [December 18, 2025, 2:35pm UTC](https://hub.mender.io/t/same-image-for-qemu-and-raspberry-pi/8146 "2025-12-18T14:35:52Z")

</div>

I am trying to build an image that supports both QEMU (For testing purposes before actual update rollouts) and actual hardware (Raspberry pi 3 or Intel NUC devices). I have tried using yocto project but facing difficulti…

---

## [ERROR: core-image-apd-devel-1.0-r0 do\_rootfs: Could not invoke dnf](https://hub.mender.io/t/error-core-image-apd-devel-1-0-r0-do-rootfs-could-not-invoke-dnf/3405)

<div class="topic-metadata">

**Author:** [@girishb](https://hub.mender.io/u/girishb)\
**Replies:** 20\
**Last updated:** [August 7, 2024, 9:30am UTC](https://hub.mender.io/t/error-core-image-apd-devel-1-0-r0-do-rootfs-could-not-invoke-dnf/3405 "2024-08-07T09:30:27Z")

</div>

HI Experts, My question:- ERROR: core-image-apd-devel-1.0-r0 do\_rootfs: Could not invoke dnf. How to fix this dnf errors ?? I had downloaded meta-mender zeus branch and cross compiled with my yocto build environment …

---

## [Corrupted grub env when calling grub-mender-grubenv-set during early boot](https://hub.mender.io/t/corrupted-grub-env-when-calling-grub-mender-grubenv-set-during-early-boot/5516)

<div class="topic-metadata">

**Author:** [@clementp](https://hub.mender.io/u/clementp)\
**Replies:** 3\
**Last updated:** [January 20, 2023, 7:32am UTC](https://hub.mender.io/t/corrupted-grub-env-when-calling-grub-mender-grubenv-set-during-early-boot/5516 "2023-01-20T07:32:29Z")

</div>

Hi, I have a machine which is a QEMU x86\_64 with VirtIO Storage based on meta-mender kirkstone-v2022.09. Just before starting the systemd network, I check and set if a hostname variable exist in the grub env and if not…

---

## [QEMU KVM vs Hyper-V /dev/sdX or /dev/vdX](https://hub.mender.io/t/qemu-kvm-vs-hyper-v-dev-sdx-or-dev-vdx/5254)

<div class="topic-metadata">

**Author:** [@clementp](https://hub.mender.io/u/clementp)\
**Replies:** 9\
**Last updated:** [September 30, 2022, 3:31pm UTC](https://hub.mender.io/t/qemu-kvm-vs-hyper-v-dev-sdx-or-dev-vdx/5254 "2022-09-30T15:31:50Z")

</div>

Hi, I first used mender with a IMX board and now I also use it with QEMU machine for testing and easy deployement as a Virtual Machine. My issue is that with KVM the disk is launched as a paravirtualized disk and Linux…

---

## [Mender-client fails to build on kirkstone for qemux86-64](https://hub.mender.io/t/mender-client-fails-to-build-on-kirkstone-for-qemux86-64/5072)

<div class="topic-metadata">

**Author:** [@brgl](https://hub.mender.io/u/brgl)\
**Replies:** 2\
**Last updated:** [July 5, 2022, 11:27am UTC](https://hub.mender.io/t/mender-client-fails-to-build-on-kirkstone-for-qemux86-64/5072 "2022-07-05T11:27:18Z")

</div>

I have a system that works on two different boards with mender-client building and working fine on kirkstone (using the master-next branch) and I want to build the same system as a virtual machine using yocto’s qemux86-6…

---

## [Building for demo with machine=qemux86-64](https://hub.mender.io/t/building-for-demo-with-machine-qemux86-64/4891)

<div class="topic-metadata">

**Author:** [@bug.spencor](https://hub.mender.io/u/bug.spencor)\
**Replies:** 3\
**Last updated:** [May 24, 2022, 4:26pm UTC](https://hub.mender.io/t/building-for-demo-with-machine-qemux86-64/4891 "2022-05-24T16:26:02Z")

</div>

I’m evaluating Mender and Yocto for a project, so I try to reproduce the “Building for demo” tutorial. I first walked through the Yocto tutorial (Yocto Project Quick Build — The Yocto Project ® 4.2.999 documentation). Sa…
