On 12/5/19 12:22 PM, n952162 wrote:
But, since it's included in the package, and apparently (from the name)
will use a NBD device, then I think the dependency is logical
I disagree.
QEMU itself does not use NBD. Thus QEMU does not need to depend on
qemu-nbd. QEMU uses files on mounted file
On 12/5/19 12:50 PM, Neil Bothwick wrote:
No, but since it is provided by the ebuild, the ebuild should check
that the target system is capable of supporting it. The qemu ebuild
already spits out warnings about missing kernel options, not all of them
essential, so why not this one too?
I thin
On Thu, 5 Dec 2019 12:01:33 -0700, Grant Taylor wrote:
> qemu-nbd is a utility to act as a NBD server to allow the Linux kernel
> to be an NBD client to access qcow(2) image files.
>
> qemu-nbd is not /needed/ for normal QEMU operation.
No, but since it is provided by the ebuild, the ebuild sho
Very informative explanation.
On 12/05/19 20:01, Grant Taylor wrote:
On 12/4/19 11:03 PM, Walter Dnes wrote:
nbd is a "Network Block Device" driver along the lines of NFS, but it
doesn't handle concurrency. https://nbd.sourceforge.io/
I think I'd liken NBD to iSCSI more so than NFS. Primari
On 12/4/19 11:03 PM, Walter Dnes wrote:
nbd is a "Network Block Device" driver along the lines of NFS, but
it doesn't handle concurrency. https://nbd.sourceforge.io/
I think I'd liken NBD to iSCSI more so than NFS. Primarily because both
NBD and iSCSI provide local block devices that are bac
On Thu, 5 Dec 2019 08:05:46 +0100, 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
The assumpt
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.
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
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
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
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
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.
12 matches
Mail list logo
