You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@vcl.apache.org by "Christopher Wolfe (JIRA)" <ji...@apache.org> on 2013/08/30 20:57:55 UTC

[jira] [Commented] (VCL-721) libvirt get_domain_info fails to properly identify vmhost's domains

    [ https://issues.apache.org/jira/browse/VCL-721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755020#comment-13755020 ] 

Christopher Wolfe commented on VCL-721:
---------------------------------------

Note: this is fixed in 2.3.2
                
> libvirt get_domain_info fails to properly identify vmhost's domains
> -------------------------------------------------------------------
>
>                 Key: VCL-721
>                 URL: https://issues.apache.org/jira/browse/VCL-721
>             Project: VCL
>          Issue Type: Bug
>          Components: vcld (backend)
>    Affects Versions: 2.3
>         Environment: Centos 6.2 (vm, hosted on vmhost which is ubuntu 12.04)
>            Reporter: Christopher Wolfe
>            Priority: Minor
>              Labels: KVM, capture, get_domain_info, libvirt
>         Attachments: apache-VCL-2.3-get_domain_info.patch
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> During capture, when ascertaining domain names from virsh, libvirt.pm's get_domain_info function incorrectly parses the output of "virsh list --all". The regular expression to split the output line into id, name, status only captures a single space between id and name, thus resulting in additional space assigned to the name field. This extra space causes subsequent 'virsh dumpxml "<name>"' command to produce an error as virsh interprets the space to be part of the name, etc. The solution is to add a "+" in the regex after the whitespace-capture. Also for good measure, I've trimmed leading and trailing whitespace from $name after the capture.
> I can't remember, off-hand, what the resulting CRITICAL error message ends up being, but it's something along the lines of "XXXHOSTXXX does not correspond to any defined virtual machine", or possibly "cannot determine the MAC address of XXXHOSTXXX

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira