[jira] [Commented] (CLOUDSTACK-8295) max data volume limits to be updated with new values for all hypervisors

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14348128#comment-14348128 ] satoru nakaya commented on CLOUDSTACK-8295: --- Hi I want to do so, But I do

[jira] [Commented] (CLOUDSTACK-8295) max data volume limits to be updated with new values for all hypervisors

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14348075#comment-14348075 ] Harikrishna Patnala commented on CLOUDSTACK-8295: - Thank you, Can you

[jira] [Commented] (CLOUDSTACK-8295) max data volume limits to be updated with new values for all hypervisors

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14347900#comment-14347900 ] satoru nakaya commented on CLOUDSTACK-8295: --- Hi Fixed. http://docs.clouds

[jira] [Commented] (CLOUDSTACK-8079) If the cluster capacity threshold is reached, HA-enabled VM is not migrated on another host during HA

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14347470#comment-14347470 ] Prachi Damle commented on CLOUDSTACK-8079: -- yes to both. > If the cluster c

[jira] [Created] (CLOUDSTACK-8300) Add index on archived field in cloud.event table

Remi Bergsma created CLOUDSTACK-8300: Summary: Add index on archived field in cloud.event table Key: CLOUDSTACK-8300 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8300 Project: CloudStack

[jira] [Commented] (CLOUDSTACK-8299) Add test case to verify ingress rule for security group for specific IP set

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14346853#comment-14346853 ] ASF GitHub Bot commented on CLOUDSTACK-8299: GitHub user gauravaradhye op

[jira] [Created] (CLOUDSTACK-8299) Add test case to verify ingress rule for security group for specific IP set

Gaurav Aradhye created CLOUDSTACK-8299: -- Summary: Add test case to verify ingress rule for security group for specific IP set Key: CLOUDSTACK-8299 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8299

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14346784#comment-14346784 ] ASF subversion and git services commented on CLOUDSTACK-8298: -

[jira] [Issue Comment Deleted] (CLOUDSTACK-7477) [LXC] the workaround for cpu,cpuacct are co-mounted problem of libvirt is removed when agent shutsdown and restarted

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Star Guo updated CLOUDSTACK-7477: - Comment: was deleted (was: How to solve the co-mounted problem with libvirt+qemu-kvm on RHEL7

[jira] [Commented] (CLOUDSTACK-8296) VMs cannot be migrated with XenMotion as network is not available

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14346787#comment-14346787 ] Rohit Yadav commented on CLOUDSTACK-8296: - [~sanjay.tripathi] - do you think

[jira] [Commented] (CLOUDSTACK-8016) return code of the call to cloudstack-setup-agent is not checked

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14346785#comment-14346785 ] ASF subversion and git services commented on CLOUDSTACK-8016: -

[jira] [Commented] (CLOUDSTACK-8296) VMs cannot be migrated with XenMotion as network is not available

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14346786#comment-14346786 ] ASF subversion and git services commented on CLOUDSTACK-8296: -

[jira] [Commented] (CLOUDSTACK-7477) [LXC] the workaround for cpu,cpuacct are co-mounted problem of libvirt is removed when agent shutsdown and restarted

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14346783#comment-14346783 ] Star Guo commented on CLOUDSTACK-7477: -- How to solve the co-mounted problem with

[jira] [Commented] (CLOUDSTACK-7477) [LXC] the workaround for cpu,cpuacct are co-mounted problem of libvirt is removed when agent shutsdown and restarted

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14346782#comment-14346782 ] Star Guo commented on CLOUDSTACK-7477: -- How to solve the co-mounted problem with

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14346778#comment-14346778 ] Rohit Yadav commented on CLOUDSTACK-8298: - [~jayapal] - what should I do to c

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14346674#comment-14346674 ] ASF subversion and git services commented on CLOUDSTACK-8298: -

[jira] [Commented] (CLOUDSTACK-4807) Add unittests for methods in NetUtils

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14346673#comment-14346673 ] ASF subversion and git services commented on CLOUDSTACK-4807: -

[jira] [Commented] (CLOUDSTACK-8016) return code of the call to cloudstack-setup-agent is not checked

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14346675#comment-14346675 ] ASF subversion and git services commented on CLOUDSTACK-8016: -

[jira] [Commented] (CLOUDSTACK-8079) If the cluster capacity threshold is reached, HA-enabled VM is not migrated on another host during HA

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14346659#comment-14346659 ] Daan Hoogland commented on CLOUDSTACK-8079: --- Is this a 4.4 issue as well? C

[jira] [Resolved] (CLOUDSTACK-8016) return code of the call to cloudstack-setup-agent is not checked

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laszlo Hornyak resolved CLOUDSTACK-8016. Resolution: Fixed Fix Version/s: 4.6.0 > return code of the call to clou