Or maybe the assumption is wrong - after emerging *nbd*, I still get
this when I try to modprobe nbd, which is required for running *qemu-nbd*:
modprobe: FATAL: Module ndb not found in directory
/lib/modules/4.19.72-gentoo
Can anyone explain how to run *qemu-nbd* on gentoo?
On ubuntu, one would do this:
sudo modprobe nbd
qemu-nbd -c /dev/nbd0 drive.vdi
On 12/05/19 07:34, n952162 wrote:
But qemu includes qemu-nbd, and it seems that qemu-nbd requires nbd.ko,
which is presumably provided by sys-block/nbd.
In other words, qemu provides a facility which seems to only work with
nbd - or is that a wrong assumption?
On 12/05/19 07:03, Walter Dnes wrote:
On Wed, Dec 04, 2019 at 04:28:26PM +0100, n952162 wrote
do I understand this correctly? In order to run qemu-nbd, you emerge
app-emulation/qemu
but that isn't all, you've also got to emerge sys-block/nbd?
nbd is a "Network Block Device" driver along the lines of NFS, but it
doesn't handle concurrency. https://nbd.sourceforge.io/ But it's
generic, and can handle any *REGULAR* file system, not just NFS. QCOW2,
or raw, or whatever, is a special QEMU format. So it requires QEMU libs
(i.e. qemu-nbd) to decode QCOW2/RAW.
Why doesn't qemu have a dependency on nbd?
Why doesn't qemu have a dependency on NFS? Same answer; they're both
remote network block device systems that most linux users don't need,
and they're both unrelated to the core functionality of QEMU.
