| 1 |
But qemu includes qemu-nbd, and it seems that qemu-nbd requires nbd.ko, |
| 2 |
which is presumably provided by sys-block/nbd. |
| 3 |
|
| 4 |
In other words, qemu provides a facility which seems to only work with |
| 5 |
nbd - or is that a wrong assumption? |
| 6 |
|
| 7 |
|
| 8 |
On 12/05/19 07:03, Walter Dnes wrote: |
| 9 |
> On Wed, Dec 04, 2019 at 04:28:26PM +0100, n952162 wrote |
| 10 |
> |
| 11 |
>> do I understand this correctly? In order to run qemu-nbd, you emerge |
| 12 |
>> app-emulation/qemu |
| 13 |
>> |
| 14 |
>> but that isn't all, you've also got to emerge sys-block/nbd? |
| 15 |
> nbd is a "Network Block Device" driver along the lines of NFS, but it |
| 16 |
> doesn't handle concurrency. https://nbd.sourceforge.io/ But it's |
| 17 |
> generic, and can handle any *REGULAR* file system, not just NFS. QCOW2, |
| 18 |
> or raw, or whatever, is a special QEMU format. So it requires QEMU libs |
| 19 |
> (i.e. qemu-nbd) to decode QCOW2/RAW. |
| 20 |
> |
| 21 |
>> Why doesn't qemu have a dependency on nbd? |
| 22 |
> Why doesn't qemu have a dependency on NFS? Same answer; they're both |
| 23 |
> remote network block device systems that most linux users don't need, |
| 24 |
> and they're both unrelated to the core functionality of QEMU. |
| 25 |
> |
Archives