Paolo Bonzini writes:
> Adding an NBD server inside QEMU is trivial, since all the logic is
> in nbd.c and can be shared easily between qemu-nbd and QEMU itself.
> The main difference is that qemu-nbd serves a single unnamed export,
> while QEMU serves named exports.
For NBD noobs like me, a sho
Il 11/10/2012 15:14, Eric Blake ha scritto:
+##
+# @nbd-server-add:
+#
+# Export a device to QEMU's embedded NBD server.
+#
+# @device: Block device to be exported
+#
+# @writable: Whether clients should be able to write to the device via the
+# NBD
On 10/11/2012 07:06 AM, Paolo Bonzini wrote:
> Il 10/10/2012 22:41, Eric Blake ha scritto:
>> On 10/10/2012 08:03 AM, Paolo Bonzini wrote:
>>> Adding an NBD server inside QEMU is trivial, since all the logic is
>>> in nbd.c and can be shared easily between qemu-nbd and QEMU itself.
>>> The main dif
Il 10/10/2012 22:41, Eric Blake ha scritto:
> On 10/10/2012 08:03 AM, Paolo Bonzini wrote:
>> Adding an NBD server inside QEMU is trivial, since all the logic is
>> in nbd.c and can be shared easily between qemu-nbd and QEMU itself.
>> The main difference is that qemu-nbd serves a single unnamed ex
On 10/10/2012 08:03 AM, Paolo Bonzini wrote:
> Adding an NBD server inside QEMU is trivial, since all the logic is
> in nbd.c and can be shared easily between qemu-nbd and QEMU itself.
> The main difference is that qemu-nbd serves a single unnamed export,
> while QEMU serves named exports.
>
> Ack
Adding an NBD server inside QEMU is trivial, since all the logic is
in nbd.c and can be shared easily between qemu-nbd and QEMU itself.
The main difference is that qemu-nbd serves a single unnamed export,
while QEMU serves named exports.
Acked-by: Luiz Capitulino
Signed-off-by: Paolo Bonzini
---
