[libvirt] Add a new api, get this error.gnutls_record_recv: A TLS packet with unexpected length was received.
hi all, Sorry to disturb you. I wanna to add a new api to get some sheepdog cluster info, but I has get this error, I don't know how to do. I have add a function to daemon/remote.c that call the libvirt.c 's api, remoteDispatchConnectExecuteCommand, and here i get the return value. struct remote_connect_execute_command_ret { remote_nonnull_string ret_val; }; typedef struct remote_connect_execute_command_ret remote_connect_execute_command_ret; static int remoteDispatchConnectExecuteCommand (struct qemud_server *server ATTRIBUTE_UNUSED, struct qemud_client *client ATTRIBUTE_UNUSED, virConnectPtr conn, remote_message_header *hdr ATTRIBUTE_UNUSED, remote_error *rerr, remote_connect_execute_command_args *args, remote_connect_execute_command_ret *ret) the return value has been in ret->ret_val. I know the func remoteDispatchDomainDumpXml returns it's values by ret->xml. And after this, the things is the same, but when I dump xml, it's ok, but when i wanna to get my value, it's cause this error: error : qemudClientReadBuf:1708 : gnutls_record_recv: A TLS packet with unexpected length was received. Could any body tell me, if I wanna to get a string data, do I need to do any additional actions?
Sorry, I just add the function prototypes in libvirt.h libvirt.in<http://libvirt.in>, implement it in libvirt.c and call a hypervisor function in qemu_drivier.h. basicly no other codes. 2012/2/13 chang liu <lingjiao.lc@gmail.com<mailto:lingjiao.lc@gmail.com>> hi all, Sorry to disturb you. I wanna to add a new api to get some sheepdog cluster info, but I has get this error, I don't know how to do. I have add a function to daemon/remote.c that call the libvirt.c 's api, remoteDispatchConnectExecuteCommand, and here i get the return value. struct remote_connect_execute_command_ret { remote_nonnull_string ret_val; }; typedef struct remote_connect_execute_command_ret remote_connect_execute_command_ret; static int remoteDispatchConnectExecuteCommand (struct qemud_server *server ATTRIBUTE_UNUSED, struct qemud_client *client ATTRIBUTE_UNUSED, virConnectPtr conn, remote_message_header *hdr ATTRIBUTE_UNUSED, remote_error *rerr, remote_connect_execute_command_args *args, remote_connect_execute_command_ret *ret) the return value has been in ret->ret_val. I know the func remoteDispatchDomainDumpXml returns it's values by ret->xml. And after this, the things is the same, but when I dump xml, it's ok, but when i wanna to get my value, it's cause this error: error : qemudClientReadBuf:1708 : gnutls_record_recv: A TLS packet with unexpected length was received. Could any body tell me, if I wanna to get a string data, do I need to do any additional actions? -- 技术保障-系统部 灵矫（刘畅） 分机 0571-88155188-11731 手机 18911205251 ________________________________ This email (including any attachments) is confidential and may be legally privileged. If you received this email in error, please delete it immediately and do not copy it or use it for any purpose or disclose its contents to any other person. Thank you. 本电邮(包括任何附件)可能含有机密资料并受法律保护。如您不是正确的收件人，请您立即删除本邮件。请不要将本电邮进行复制并用作任何其他用途、或透露本邮件之内容。谢谢。
On 02/12/2012 11:26 AM, 灵矫 wrote: [please don't top-post on technical lists]
Sorry, I just add the function prototypes in libvirt.h libvirt.in<http://libvirt.in>, implement it in libvirt.c and call a hypervisor function in qemu_drivier.h. basicly no other codes.
It's easier to review your code for errors if you post the actual patches you have written so far.
2012/2/13 chang liu <lingjiao.lc@gmail.com<mailto:lingjiao.lc@gmail.com>> hi all, Sorry to disturb you. I wanna to add a new api to get some sheepdog cluster info, but I has get this error, I don't know how to do.
I have add a function to daemon/remote.c that call the libvirt.c 's api, remoteDispatchConnectExecuteCommand, and here i get the return value.
struct remote_connect_execute_command_ret { remote_nonnull_string ret_val; }; typedef struct remote_connect_execute_command_ret remote_connect_execute_command_ret;
static int remoteDispatchConnectExecuteCommand (struct qemud_server *server ATTRIBUTE_UNUSED, struct qemud_client *client ATTRIBUTE_UNUSED, virConnectPtr conn, remote_message_header *hdr ATTRIBUTE_UNUSED, remote_error *rerr, remote_connect_execute_command_args *args, remote_connect_execute_command_ret *ret)
If you're lucky, your new API won't need you to write any code in daemon/remote.c, but can instead be autogenerated as part of adding your new API to src/remote/remote_protocol.x. But it's hard to see what you might be doing wrong without seeing your full patch. -- Eric Blake eblake@redhat.com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
Oh, thanks. I have found that if my return type is remote_nonnull_string, the error will be happen, but if the return type is int, it works ok. 2012/2/14 Eric Blake <eblake@redhat.com>
On 02/12/2012 11:26 AM, 灵矫 wrote:
[please don't top-post on technical lists]
Sorry, I just add the function prototypes in libvirt.h libvirt.in< http://libvirt.in>, implement it in libvirt.c and call a hypervisor function in qemu_drivier.h. basicly no other codes.
It's easier to review your code for errors if you post the actual patches you have written so far.
2012/2/13 chang liu <lingjiao.lc@gmail.com<mailto:lingjiao.lc@gmail.com
hi all, Sorry to disturb you. I wanna to add a new api to get some sheepdog cluster info, but I has
get this error, I don't know how to do.
I have add a function to daemon/remote.c that call the libvirt.c 's
api, remoteDispatchConnectExecuteCommand, and here i get the return value.
struct remote_connect_execute_command_ret { remote_nonnull_string ret_val; }; typedef struct remote_connect_execute_command_ret
remote_connect_execute_command_ret;
static int remoteDispatchConnectExecuteCommand (struct qemud_server *server
ATTRIBUTE_UNUSED,
struct qemud_client *client
ATTRIBUTE_UNUSED,
virConnectPtr conn, remote_message_header *hdr ATTRIBUTE_UNUSED, remote_error *rerr, remote_connect_execute_command_args *args, remote_connect_execute_command_ret *ret)
If you're lucky, your new API won't need you to write any code in daemon/remote.c, but can instead be autogenerated as part of adding your new API to src/remote/remote_protocol.x. But it's hard to see what you might be doing wrong without seeing your full patch.
-- Eric Blake eblake@redhat.com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
-- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
participants (3)
-
chang liu -
Eric Blake -
灵矫