Error ret=-1 with EINTR in nbd_connect_systemd_socket_activation()

Error ret=-1 with EINTR in nbd_connect_systemd_socket_activation()

[Motohiro Kawahito]

[-- Attachment #1: Type: text/plain, Size: 753 bytes --]

Hi, I'd like to connect to an encrypted QCOW2 file by nbd_connect_systemd_socket_activation(), but I got ret=-1 with EINTR.
The arg parameter I used is
qemu-nbd --object secret,id=sec0,data=abc123 --image-opts driver=qcow2,encrypt.format=luks,encrypt.key-secret=sec0,file.filename=/tmp/empty.qcow2

Can you find what a problem is? The version of qemu-nbd is
$ qemu-nbd -V
qemu-nbd 4.2.1 (Debian 1:4.2-3ubuntu6.23)

I created this encrypted QCOW2 image by the following command.
qemu-img create --object secret,id=sec0,data=abc123 -f qcow2 -o encrypt.format=luks,encrypt.key-secret=sec0 /tmp/empty.qcow2 8539292672

Note that I can connect to a normal QCOW2 file by this function without any error. (arg: qemu-nbd -f qcow2 /tmp/normal.qcow2)

[-- Attachment #2: Type: text/html, Size: 3497 bytes --]

Re: Error ret=-1 with EINTR in nbd_connect_systemd_socket_activation()

[Philippe Mathieu-Daudé via]

Cc'ing qemu-block@

On 11/7/22 08:38, Motohiro Kawahito wrote:
> Hi, I’d like to connect to an encrypted QCOW2 file by 
> nbd_connect_systemd_socket_activation(), but I got ret=-1 with EINTR.
> 
> The arg parameter I used is
> 
> qemu-nbd --object secret,id=sec0,data=abc123 --image-opts 
> driver=qcow2,encrypt.format=luks,encrypt.key-secret=sec0,file.filename=/tmp/empty.qcow2
> 
> Can you find what a problem is? The version of qemu-nbd is
> 
> $ qemu-nbd -V
> 
> qemu-nbd 4.2.1 (Debian 1:4.2-3ubuntu6.23)
> 
> I created this encrypted QCOW2 image by the following command.
> 
> qemu-img create --object secret,id=sec0,data=abc123 -f qcow2 -o 
> encrypt.format=luks,encrypt.key-secret=sec0 /tmp/empty.qcow2 8539292672
> 
> Note that I can connect to a normal QCOW2 file by this function without 
> any error. (arg: qemu-nbd -f qcow2 /tmp/normal.qcow2)
>