From nobody Fri Apr 26 03:53:34 2024 Delivered-To: importer@patchew.org Received-SPF: pass (zohomail.com: domain of redhat.com designates 207.211.31.120 as permitted sender) client-ip=207.211.31.120; envelope-from=libvir-list-bounces@redhat.com; helo=us-smtp-1.mimecast.com; Authentication-Results: mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 207.211.31.120 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com; dmarc=pass(p=none dis=none) header.from=redhat.com ARC-Seal: i=1; a=rsa-sha256; t=1578990370; cv=none; d=zohomail.com; s=zohoarc; b=duL+GodhrhAw8aNkrzSbLObleIMba9KPC2ke++uVIwtae3frCrZnNnfKW2Z/mwv0GuUEnHmbn+vEAMQ7WVURptLiNvcfo2kkb21L12pYpCKUkxlvqHLixsI8joWmUCkDZenpCzMzLPzhRuy0EzJatc/YA8lmeAtvEMAXFNHGzE4= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1578990370; h=Content-Type:Content-Transfer-Encoding:Date:From:List-Subscribe:List-Post:List-Id:List-Archive:List-Help:List-Unsubscribe:MIME-Version:Message-ID:Sender:Subject:To; bh=odu5t9l9toc2+eNE4xRAyNzmfo6hmyhZ+KrZ/1k+cqs=; b=dqhm+Gz/n3fCmZoFZoss2AEUMR2LePOrieF3Nz7oj1oVizrZMPyUQs9QT3k5/AuuKwdpeJ09NNbYww6GjifDX+LQw8g8fWrx/VZf+UA1CHX1Aq1O1jtAupIir3w6gZ9/QWjDA/2tvokGP5+Rhwdhm9CcvtkuYFFNrnXIegi+zI8= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 207.211.31.120 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com; dmarc=pass header.from= (p=none dis=none) header.from= Return-Path: Received: from us-smtp-1.mimecast.com (us-smtp-delivery-1.mimecast.com [207.211.31.120]) by mx.zohomail.com with SMTPS id 15789903703471014.2470466856446; Tue, 14 Jan 2020 00:26:10 -0800 (PST) Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-313-Pdd0TGjrNgyP_MAOU0QECw-1; Tue, 14 Jan 2020 03:26:08 -0500 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 47C83189DF41; Tue, 14 Jan 2020 08:26:02 +0000 (UTC) Received: from colo-mx.corp.redhat.com (colo-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.21]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 7B79C87EE4; Tue, 14 Jan 2020 08:26:01 +0000 (UTC) Received: from lists01.pubmisc.prod.ext.phx2.redhat.com (lists01.pubmisc.prod.ext.phx2.redhat.com [10.5.19.33]) by colo-mx.corp.redhat.com (Postfix) with ESMTP id 1DF768250D; Tue, 14 Jan 2020 08:26:00 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id 00E8PwAo022664 for ; Tue, 14 Jan 2020 03:25:58 -0500 Received: by smtp.corp.redhat.com (Postfix) id 2ECBC80F68; Tue, 14 Jan 2020 08:25:58 +0000 (UTC) Received: from moe.redhat.com (unknown [10.43.2.30]) by smtp.corp.redhat.com (Postfix) with ESMTP id AB62180F57 for ; Tue, 14 Jan 2020 08:25:55 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1578990369; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding:list-id:list-help: list-unsubscribe:list-subscribe:list-post; bh=odu5t9l9toc2+eNE4xRAyNzmfo6hmyhZ+KrZ/1k+cqs=; b=TPfGs48bJrIhbWQ3p9L18PmfAG6TUkKbNTssDTiEDYuANuqlE6p/QS2v11rrcCrqGnklcN oD6AISloJmofobZXs0X4CkeZypR5CwgpNKp05LUaJuy8PFfII+4fnnxKyBAq/w8esATzO8 Xr8Z0B8CEH/JZnr0603NIUkYsDeOCpE= From: Michal Privoznik To: libvir-list@redhat.com Date: Tue, 14 Jan 2020 09:25:22 +0100 Message-Id: <99263d87d5aca4d96c8a4348f4d109ad27c5b6df.1578990310.git.mprivozn@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 X-loop: libvir-list@redhat.com Subject: [libvirt] [PATCH for 6.0.0] news: Document X-BeenThere: libvir-list@redhat.com X-Mailman-Version: 2.1.12 Precedence: junk List-Id: Development discussions about the libvirt library & tools List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: libvir-list-bounces@redhat.com Errors-To: libvir-list-bounces@redhat.com X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 X-MC-Unique: Pdd0TGjrNgyP_MAOU0QECw-1 X-Mimecast-Spam-Score: 0 Content-Transfer-Encoding: quoted-printable X-ZohoMail-DKIM: pass (identity @redhat.com) Content-Type: text/plain; charset="utf-8" Signed-off-by: Michal Privoznik Reviewed-by: Andrea Bolognani --- docs/news.xml | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/docs/news.xml b/docs/news.xml index acb63709da..e9863dacf3 100644 --- a/docs/news.xml +++ b/docs/news.xml @@ -106,6 +106,22 @@ hostname and the information stored in its TLS certificate. + + + qemu: Allow accessing NVMe disks directly + + + Before this release there were two ways to configure a NVMe disk= for + a domain. The first was using <disk/> with the <source= /> + pointing to the /dev/nvmeXXXX. The other was using = PCI + assignment via <hostdev/> element. Both have their + disadvantages: the former adds latency of file system and block + layers of the host kernel, the latter prohibits domain migration= . In + this release the third way of configuring NVMe disk is added whi= ch + combines the advantages and drops disadvantages of the previous = two + ways. It's accessible via <disk type=3D'nvme'/>. + +
--=20 2.24.1 -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list