mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-08-29 20:11:16 +00:00
news: Document <disk type='nvme'/>
Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Andrea Bolognani <abologna@redhat.com>
This commit is contained in:
parent
8475234dbc
commit
2b611db882
@ -115,6 +115,22 @@
|
|||||||
<code>virsh domstats --memory</code>.
|
<code>virsh domstats --memory</code>.
|
||||||
</description>
|
</description>
|
||||||
</change>
|
</change>
|
||||||
|
<change>
|
||||||
|
<summary>
|
||||||
|
qemu: Allow accessing NVMe disks directly
|
||||||
|
</summary>
|
||||||
|
<description>
|
||||||
|
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 <code>/dev/nvmeXXXX</code>. 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 which
|
||||||
|
combines the advantages and drops disadvantages of the previous two
|
||||||
|
ways. It's accessible via <disk type='nvme'/>.
|
||||||
|
</description>
|
||||||
|
</change>
|
||||||
</section>
|
</section>
|
||||||
<section title="Removed features">
|
<section title="Removed features">
|
||||||
<change>
|
<change>
|
||||||
|
Loading…
Reference in New Issue
Block a user