Hello,
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?
Why doesn't qemu have a dependency on nbd? I don't find any relevant
USE flags.
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 ha
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
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
On Thu, 5 Dec 2019 at 08:11, n952162 wrote:
>
> 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 h
The documentation emerged with sys-block/nbd includes this:
/usr/share/doc/nbd-3.19/README.md.bz2:
# modprobe nbd
but there's no module emerged by nbd-3.19.ebuild. There doesn't seem to
be any relevant USE flags to cause it to be generated.
How can I get nbd.ko?
On 12/05/19 08:17, Arve Barsnes wrote:
On Thu, 5 Dec 2019 at 08:11, n952162 wrote:
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.
Okay, I see from /proc/config.gz that NBD probably needs to be
configured with the kernel
# CONFIG_BLK_DEV_NBD is not set
Bummer. At work, I could just do a apt-get install qemu-nbd (or
similar) without any more effort.
The emerge should have checked for this and failed.
On 12/05/19 08:23, n
8 matches
Mail list logo
