From dev-return-80078-apmail-cloudstack-dev-archive=cloudstack.apache.org@cloudstack.apache.org Fri Sep 11 11:37:04 2015 Return-Path: X-Original-To: apmail-cloudstack-dev-archive@www.apache.org Delivered-To: apmail-cloudstack-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D782717A4E for ; Fri, 11 Sep 2015 11:37:04 +0000 (UTC) Received: (qmail 10067 invoked by uid 500); 11 Sep 2015 11:37:04 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 10009 invoked by uid 500); 11 Sep 2015 11:37:04 -0000 Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list dev@cloudstack.apache.org Received: (qmail 9998 invoked by uid 99); 11 Sep 2015 11:37:04 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Sep 2015 11:37:04 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id EB802DFF67; Fri, 11 Sep 2015 11:37:03 +0000 (UTC) From: bhaisaab To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack pull request: CLOUDSTACK-8820: Showing error when try t... Content-Type: text/plain Message-Id: <20150911113703.EB802DFF67@git1-us-west.apache.org> Date: Fri, 11 Sep 2015 11:37:03 +0000 (UTC) Github user bhaisaab commented on the pull request: https://github.com/apache/cloudstack/pull/806#issuecomment-139521285 Great PR @sureshanaparti I was going to work on supporting this as ESXi6 works well on top of KVM; I can test this for you next week; LGTM on code change (not tested though) --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---