From owner-freebsd-xen@freebsd.org Mon Dec 12 10:32:00 2016 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A5B59C71431; Mon, 12 Dec 2016 10:32:00 +0000 (UTC) (envelope-from prvs=1477f1691=roger.pau@citrix.com) Received: from SMTP.EU.CITRIX.COM (smtp.ctxuk.citrix.com [185.25.65.24]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.citrix.com", Issuer "DigiCert SHA2 Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0457B21A; Mon, 12 Dec 2016 10:31:58 +0000 (UTC) (envelope-from prvs=1477f1691=roger.pau@citrix.com) X-IronPort-AV: E=Sophos;i="5.33,335,1477958400"; d="scan'208";a="36611840" Date: Mon, 12 Dec 2016 10:31:48 +0000 From: Roger Pau =?iso-8859-1?Q?Monn=E9?= To: "Hoyer-Reuther, Christian" , CC: "freebsd-xen@freebsd.org" , "owner-freebsd-xen@freebsd.org" Subject: Re: 11-RELEASE and live migration Message-ID: <20161212103148.5prkggi3ix4zoxyv@dhcp-3-221.uk.xensource.com> References: <001f01d250a6$05ca4160$115ec420$@ezwind.net> <003501d250af$032dd580$09898080$@ezwind.net> <41E487BC91654544B2B8F31096F2D9D4D1B060A925@ex1> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <41E487BC91654544B2B8F31096F2D9D4D1B060A925@ex1> User-Agent: NeoMutt/20161126 (1.7.1) X-ClientProxiedBy: AMSPEX02CAS01.citrite.net (10.69.22.112) To AMSPEX02CL02.citrite.net (10.69.22.126) X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2016 10:32:00 -0000 On Thu, Dec 08, 2016 at 10:33:37AM +0100, Hoyer-Reuther, Christian wrote: > I did some tests and I see the problem too. > > XenServer 6.5 SP1 with almost all patches (3 hosts in pool), FreeBSD 11.0-RELEASE-p2, xe-guest-utilities-6.2.0_2 installed via pkg. > > First migration from host 3 to host 1 is ok. > > Some seconds later I start a new migration from host 1 to host 2 and when migration finishes (as seen in XenCenter) then the VM switches to the VGABios screen ("Plex86/Bochs VGABios (PCI) current-cvs 01 Sep 2016 ... cirrus-compatible VGA is detected"). The VM seem to hang and does not respond. In XenCenter I see that all the CPU's of the VM go up to 100 percent. > > Then after 17 minutes the VGABios screen disappears and I see the console, the CPU usage as seen in XenCenter goes down. I logged in as root before I started the first migration and root is still logged in. So it was a hang and not a reboot. > > 20 minutes later I start a new migration from host 2 to host 3 and the problem occurs again. > > This problem does not exist with 10.3-RELEASE on the same hosts. Hello, So far I've only tested local migration (migration using the same host as source and destination), and that seems to work fine (I've done +50 consecutive migrations with only 10s separation between them). Is there a change that you could also try to reproduce this with local migration? Are you using the same exact hardware on the source and the destination? Are you all using iSCSI as the disk backend for this VMs? Thanks, Roger.