You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Rajani Karuturi (JIRA)" <ji...@apache.org> on 2015/08/13 11:54:46 UTC

[jira] [Resolved] (CLOUDSTACK-8298) xenserver VR start failed when the VR start config size is more

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-8298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rajani Karuturi resolved CLOUDSTACK-8298.
-----------------------------------------
    Resolution: Fixed

> xenserver VR start failed when the VR start config size is more
> ---------------------------------------------------------------
>
>                 Key: CLOUDSTACK-8298
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8298
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Network Controller, Network Devices
>    Affects Versions: 4.5.0
>            Reporter: Jayapal Reddy
>            Assignee: Jayapal Reddy
>             Fix For: 4.6.0, 4.5.1
>
>
> On VR restart/start CS sends the configuration to VR via vmops 'createFileInDomr' method. The createFileInDomr method receives the content and create temp file in xenserver and push this file to VR using SCP.
> When the VR configuration is more than ARG_MAX size of the xenserver host then it command got failed.
> The below is the command to get the ARG_MAX value in the host.
> #getconf ARG_MAX
> 131072
> Reproducing steps:
> 1. create an isolated network and deploy vm in that network.
> 2. Create large size configuration to VR by creating more number of VMs or configure more set of network rules on the network.
> 3. After this restart the VR. On starting the VR CS sends the configuration to VR, You can see the configuration in MS log.
>  Error: callHostPlugin failed for cmd: createFileInDomr with args 
>    



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)