[
https://issues.apache.org/jira/browse/CLOUDSTACK-8911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14934991#comment-14934991
]
ASF GitHub Bot commented on CLOUDSTACK-8911:
--------------------------------------------
Github user koushik-das commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/895#discussion_r40657679
--- Diff:
server/src/com/cloud/agent/manager/allocator/impl/FirstFitAllocator.java ---
@@ -297,6 +297,7 @@
s_logger.debug("Host name: " + host.getName() + ",
hostId: " + host.getId() +
" already has max Running VMs(count includes
system VMs), skipping this and trying other available hosts");
}
+ avoid.addHost(host.getId());
--- End diff --
@SudharmaJain There is another check for GPU device immediately below and
the pattern is similar to the guest VM check. The issue you have mentioned can
happen even for this. Can you check and verify?
> VM start job got stuck in loop looking for suitable host
> --------------------------------------------------------
>
> Key: CLOUDSTACK-8911
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8911
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.3.0
> Reporter: sudharma jain
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
