]> git.ipfire.org Git - thirdparty/libvirt.git/commit
projects / thirdparty / libvirt.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 8d9bf73) | patch
bhyve: do not allow more than one NVMe device per controller
authorRoman Bogorodskiy <bogorodskiy@gmail.com>
Sat, 25 Oct 2025 08:15:57 +0000 (10:15 +0200)
committerJiri Denemark <jdenemar@redhat.com>
Wed, 29 Oct 2025 10:45:42 +0000 (11:45 +0100)
commita997aee58f8f594c34fa1c666c967aece30c9824
treed8642522d314270a492a31a42a8ef4f5d3ebfd80tree | snapshot
parent8d9bf732a7aea05d7311bb391f928ab83a8cb21acommit | diff
bhyve: do not allow more than one NVMe device per controller

As bhyve does not have explicit notion of controllers, and for NVMe
devices it allows to specify one a single source for for a given PCI
address, it effectively means that there could be only one device per
controller.

Update validation code to check this case.

Signed-off-by: Roman Bogorodskiy <bogorodskiy@gmail.com>
Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
src/bhyve/bhyve_domain.c diff | blob | blame | history
tests/bhyvexml2argvdata/bhyvexml2argv-2-nvme-same-controller.args [new file with mode: 0644] blob
tests/bhyvexml2argvdata/bhyvexml2argv-2-nvme-same-controller.ldargs [new file with mode: 0644] blob
tests/bhyvexml2argvdata/bhyvexml2argv-2-nvme-same-controller.xml [new file with mode: 0644] blob
tests/bhyvexml2argvtest.c diff | blob | blame | history
Mirror of https://github.com/libvirt/libvirt.git