Ideally, we should use names like nvme0n1, which follow the typical naming
convention for NVMe devices (even if they don't necessarily match the actual
device names inside the guest). However, using this approach in libvirt would
tightly couple the device name with the controller relationship, m
On Wed, May 07, 2025 at 04:43:29PM +0200, Peter Krempa wrote:
On Wed, May 07, 2025 at 15:56:52 +0200, Martin Kletzander wrote:
On Sun, Apr 27, 2025 at 07:48:02PM +0800, honglei.w...@smartx.com wrote:
> From: hongleiwang
>
> QEMU has supported nvme disk emulation for a long time,
> see: https://
On Wed, May 07, 2025 at 15:56:52 +0200, Martin Kletzander wrote:
> On Sun, Apr 27, 2025 at 07:48:02PM +0800, honglei.w...@smartx.com wrote:
> > From: hongleiwang
> >
> > QEMU has supported nvme disk emulation for a long time,
> > see: https://qemu-project.gitlab.io/qemu/system/devices/nvme.html.
On Sun, Apr 27, 2025 at 07:48:02PM +0800, honglei.w...@smartx.com wrote:
From: hongleiwang
QEMU has supported nvme disk emulation for a long time,
see: https://qemu-project.gitlab.io/qemu/system/devices/nvme.html.
The following patches introduce nvme-ns disk bus type:
Thanks for the v2. I h
From: hongleiwang
QEMU has supported nvme disk emulation for a long time,
see: https://qemu-project.gitlab.io/qemu/system/devices/nvme.html.
The following patches introduce nvme-ns disk bus type:
A disk with nvme-ns as bus is represented as an nvme namespace
and needs to be attached to an nvme c
