---
title: "Discussion on \"How QEMU Emulates Hardware: Device Models, MMIO, and TCG\" | Hashnode"
description: "Discussion on \"How QEMU Emulates Hardware: Device Models, MMIO, and TCG\". Every device your guest VM sees is C code responding to memory addresses. QEMU is not mysterious if you understand this."
url: "https://hashnode.com/posts/how-qemu-emulates-hardware-device-models-mmio-and-tcg/6a9a9ee7f709a9309a5192c1"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [How QEMU Emulates Hardware: Device Models, MMIO, and TCG](https://supun.hashnode.dev/how-qemu-emulates-hardware-device-models-mmio-and-tcg?utm_source=hashnode&utm_medium=feed)

Every device your guest VM sees is C code responding to memory addresses. QEMU is not mysterious if you understand this.

Sep 4 · 12 min read · supun.hashnode.dev  
Read the article

-   [#linux](https://hashnode.com/tag/linux)
-   [#devops](https://hashnode.com/tag/devops)
-   [#virtualization](https://hashnode.com/tag/virtualization)
-   [#kvm](https://hashnode.com/tag/kvm)

## Written by

[Supun Sriyananda](https://hashnode.com/@ranaweerasupun)

@ranaweerasupun

  
[View profile](https://hashnode.com/@ranaweerasupun)

Lead Embedded Engineer working on secure edge devices.

Lead Embedded Engineer building secure IoT and Edge Computing systems across Embedded Linux and RTOS. I work on device hardening, TrustZone and Secure Boot, and OTA pipelines for remote fleets. I write down the problems I had to solve alone, in case you hit the same ones.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
