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