Anthony PERARD

Anthony PERARD
QEMU vs. qemu-traditional update
09/20/2013

Here is an update about feature completeness of QEMU compared to the old qemu-traditional. But first, what is the difference between QEMU and qemu-traditional? QEMU is the software that can be found at qemu.org, we can also call it QEMU upstream. It’s where all new features are supposed

Bringing Xen on the Chromebook and the Arndale Board: the journey so far
05/23/2013

I’ve started to work on the Xen on ARM project by trying to get Xen running on the nice little Samsung Chromebook which run an ARM processor with the virtualization extensions. The Chromebook uses Exynos 5250 dual core platform with 2GB of RAM, which could be perfect for a

Linux Stub-Domain
12/12/2012
RC2

The “Normal” Case To explain what is a Stub-Domain (often called stubdom), let’s start with the basics. When you start a new guest with Xen, you would need a Device Model which does some emulation if the guest does not have PV drivers. This is the case for

PCI Passthrough in QEMU
07/16/2012

We now have PCI passthrough support in QEMU upstream, this was one of the missing pieces needed to have a full featured QEMU device model. But there is still more work to do on it. Why do we use QEMU? We use QEMU in Xen to emulate a part of

Xen support upstreamed to QEMU
05/13/2011

My name is Anthony Perard and I have been working on up-streaming Xen patches to the QEMU mainline. The good news is that the bulk of the changes for Xen are in the QEMU mainline as of yesterday. Let me begin a year ago, when I started working on this