New pages

New pages
Hide registered users | Hide bots | Show redirects
  • 16:24, 9 February 2024Dynamic machine and heterogeneous emulation roadmap (hist | edit) ‎[762 bytes]F4bug (talk | contribs) (Start roadmap with minutes from community call from 2024 Feb 6)
  • 22:43, 6 February 2024Internships/ProjectIdeas/TCGBinaryTracing (hist | edit) ‎[2,045 bytes]Paolo Bonzini (talk | contribs) (Created page with "=== Binary tracing of TCG === '''Summary:''' Right now, most logging for the TCG accelerator can only be produced on stderr: this includes input and output assembly, unoptimized and optimized TCG opcodes, and exceptions/interrupts. Text output is easy to interpret but it is more expensive to produce and harder to filter. This project will consist of integrating three new kinds of "trace events" into the "simple" trace backend: target assembly (as used by <tt>-d in_as...")
  • 14:32, 31 January 2024Internships/ProjectIdeas/RISCVVectorFrontendOptimization (hist | edit) ‎[1,650 bytes]Stefanha (talk | contribs) (Created page with "=== RISC-V Vector TCG Frontend Optimization === '''Summary:''' Improve QEMU's performance on RISC-V vector instructions. The RISC-V vector extension has been implemented in QEMU, but we have some performance pathologies mapping it to existing TCG backends. This project aims to improve the performance of the RISC-V vector ISA's mappings to QEMU TCG just-in-time compiler. The RISC-V TCG frontend (ie, decoding RISC-V instructions and emitting TCG calls to emulate them)...")
  • 20:13, 30 January 2024Internships/ProjectIdeas/NitroEnclaves (hist | edit) ‎[2,750 bytes]Stefanha (talk | contribs) (Created page with "=== Implement -M nitro-enclave in QEMU === '''Summary:''' AWS EC2 provides the ability to create an isolated sibling VM context from within a VM. This project implements the machine model and input data format parsing needed to run these sibling VMs stand alone in QEMU. [https://aws.amazon.com/ec2/nitro/nitro-enclaves/ Nitro Enclaves] are the first widely adopted implementation of hypervisor assisted compute isolation. Similar to technologies like Intel SGX, it allows...")
  • 19:29, 30 January 2024Internships/ProjectIdeas/VhostUserMemoryIsolation (hist | edit) ‎[3,326 bytes]Stefanha (talk | contribs) (Created page with "=== vhost-user memory isolation === '''Summary:''' Add a new mode for vhost-user devices that does not expose guest RAM as shared memory. vhost-user enables VIRTIO devices to be implemented as separate processes outside of QEMU. This allows device emulation code to be written in any programming language, sharing of device emulation code with other emulators besides QEMU, and complex device implementations that would not fit well into the QEMU process. vhost-user achie...")
  • 19:34, 29 January 2024Internships/ProjectIdeas/PackedShadowVirtqueue (hist | edit) ‎[2,788 bytes]Stefanha (talk | contribs) (Created page with "=== Add packed virtqueue to Shadow Virtqueue === '''Summary:''' Add the packed virtqueue format support to QEMU's Shadow Virtqueue. To live migrate a guest with a passthrough device, QEMU needs a way to know which memory the device modifies so it is able to migrate it every time it is modified. Otherwise the migrated guest would resume with outdated memory contents after live migration. This is especially hard with passthrough hardware devices, as transports like PCI i...")
  • 20:23, 25 January 2024Internships/ProjectIdeas/GStreamerVhostDeviceSound (hist | edit) ‎[2,952 bytes]Stefanha (talk | contribs) (Created page with "=== GStreamer Backend for vhost-device-sound === '''Summary:''' Implement a GStreamer audio backend in rust-vmm's vhost-device-sound crate. '''Project Size:''' 180 hrs '''Project Description:''' virtio-sound device emulation has recently been developed in the Rust [https://github.com/rust-vmm/vhost-device vhost-device-sound] crate. The crate currently contains audio backends for the ALSA and PipeWire sound APIs. The aim of this project is to build a new [https://gstr...")
  • 16:23, 15 January 2024Google Summer of Code 2024 (hist | edit) ‎[7,472 bytes]Stefanha (talk | contribs) (Created page with "= Introduction = QEMU is applying for [https://summerofcode.withgoogle.com/ Google Summer of Code 2024]. This page contains our ideas list and information for applicants and mentors. Google Summer of Code is an open source internship program offering paid remote work. '''Status: Google will publish the list of accepted GSoC organizations at 18:00 UTC on February 21st. Applicants may get in touch with mentors before that date, but please don't invest too much time befor...")
  • 17:57, 20 December 2023Planning/9.0 (hist | edit) ‎[896 bytes]Pm215 (talk | contribs) (Created page with "== Release Schedule == {| border="1" | 2023-12-20 | Beginning of development phase |- | 2024-xx-xx | Soft feature freeze. Only bug fixes after this point. All feature changes must be already in a sub maintainer tree and all pull requests from submaintainers must have been sent to the list by this date. |- | 2024-xx-xx | Hard feature freeze. Tag rc0 |- | 2024-xx-xx | Tag rc1 |- | 2024-xx-xx | Tag rc2 |- | 20...")
  • 17:22, 20 December 2023ChangeLog/9.0 (hist | edit) ‎[10,363 bytes]Pm215 (talk | contribs) (Created page with "== System emulation == === Removed features and incompatible changes === Consult the [https://qemu-project.gitlab.io/qemu/about/removed-features.html 'Removed features'] page for details of suggested replacement functionality. * Running QEMU with KVM requires Linux 4.4 or newer. A future version of QEMU will increase the minimum requirement for Arm hosts to Linux 4.19 (also when running KVM); if this is too restrictive for your use case, please contact us at qemu-deve...")