Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 1E961200B26 for ; Mon, 27 Jun 2016 09:37:38 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 1D2D7160A5B; Mon, 27 Jun 2016 07:37:38 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 5EA38160A3C for ; Mon, 27 Jun 2016 09:37:37 +0200 (CEST) Received: (qmail 63892 invoked by uid 500); 27 Jun 2016 07:37:36 -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 63841 invoked by uid 99); 27 Jun 2016 07:37:36 -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; Mon, 27 Jun 2016 07:37:36 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 0092DE9423; Mon, 27 Jun 2016 07:37:35 +0000 (UTC) From: remibergsma To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack issue #1596: CLOUDSTACK-9353: [XenServer] Fixed VM migration with... Content-Type: text/plain Message-Id: <20160627073736.0092DE9423@git1-us-west.apache.org> Date: Mon, 27 Jun 2016 07:37:35 +0000 (UTC) archived-at: Mon, 27 Jun 2016 07:37:38 -0000 Github user remibergsma commented on the issue: https://github.com/apache/cloudstack/pull/1596 Same approach as proposed in #925, although both address different problems. I'd say let's test this stuff and get it in to resolve these issues. We may want to look to the other PR as well, although we cannot merge both without some tweaks. --- 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. ---