From owner-freebsd-xen@FreeBSD.ORG Mon Jun 10 14:48:25 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 4A4C1B68; Mon, 10 Jun 2013 14:48:25 +0000 (UTC) (envelope-from roger.pau@citrix.com) Received: from SMTP.EU.CITRIX.COM (smtp.eu.citrix.com [46.33.159.39]) by mx1.freebsd.org (Postfix) with ESMTP id 986311CB9; Mon, 10 Jun 2013 14:48:24 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.87,837,1363132800"; d="scan'208";a="5490830" Received: from lonpex01cl01.citrite.net ([10.30.203.101]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/AES128-SHA; 10 Jun 2013 14:48:18 +0000 Received: from Roger-2.local (10.30.203.1) by LONPEX01CL01.citrite.net (10.30.203.101) with Microsoft SMTP Server id 14.2.342.3; Mon, 10 Jun 2013 15:48:17 +0100 Message-ID: <51B5E730.6070007@citrix.com> Date: Mon, 10 Jun 2013 16:48:16 +0200 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: "freebsd-xen@freebsd.org" Subject: Re: FreeBSD PVHVM call for testing References: <519131D8.9010307@citrix.com> <519E54DE.5090304@citrix.com> In-Reply-To: <519E54DE.5090304@citrix.com> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.30.203.1] Cc: "xen-users@lists.xen.org" , "Justin T. Gibbs" , "freebsd-virtualization@freebsd.org" , xen-devel X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 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, 10 Jun 2013 14:48:25 -0000 Hello, I've pushed a new branch, pvhvm_v14 that contains support for live migration. While there I've also rebased the changes on top of current HEAD, so now it contains the recent fixes to blkfront and netfront. http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=shortlog;h=refs/heads/pvhvm_v14 Some notes on this branch, I've mainly tested it with Xen 4.3 (unstable) because previous Xen versions have problems with the PV clock used in PVHVM when migrating. In order to be able to migrate a PVHVM guest you will need to add tsc_mode="native_paravirt" to your config file or apply the following patch to Xen: http://marc.info/?l=xen-devel&m=137036010517331 I would say that migration across the 4.x series will work without problems (because they all have support for vector callback injection), but migrating from 4.x to 3.x will certainly not work. On the other hand, migrating a guest started on 3.4 to 4.0 should work, although I have not tested it. Also, if the migration process fails for some reason, resuming the original guest on the sender side will leave the VM without working nics and disks, this is a problem with netfront and blkfront not being able to resume after suspension if the guest was not actually migrated. Roger.