From owner-freebsd-xen@FreeBSD.ORG Sun Aug 12 12:50:49 2012 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A6D4810656D1 for ; Sun, 12 Aug 2012 12:50:49 +0000 (UTC) (envelope-from jwest@ezwind.net) Received: from ezwind.net (bobby.ezwind.net [209.145.140.14]) by mx1.freebsd.org (Postfix) with ESMTP id 6D3418FC16 for ; Sun, 12 Aug 2012 12:50:49 +0000 (UTC) Received: from LENOVOD6B52A6B by ezwind.net (MDaemon.PRO.v8.1.3.R) with ESMTP id 56-md50000135217.msg for ; Sun, 12 Aug 2012 07:50:20 -0500 From: "Jay West" To: "'Mark Felder'" , "'moto kawasaki'" , "'Egoitz Aurrekoetxea'" References: <61BCA99E-2574-4987-ACD9-E84A3AEBD2A3@ramattack.net> <20120810.034203.52110126.moto@kawasaki3.org> <69EAC334-C51A-4F12-98BE-C25674F10A36@ramattack.net> <20120810.103728.219947649.moto@kawasaki3.org> In-Reply-To: Date: Sun, 12 Aug 2012 07:50:16 -0500 Message-ID: <000001cd7889$05e15ac0$11a41040$@ezwind.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQHxWby8upHQXKmKvSMOkvVwyLCuCAH/pSmwAkgpUVkBldnuGQOAYma9ArzuchaWrXruIA== Content-Language: en-us X-Authenticated-Sender: jwest@ezwind.net X-Spam-Processed: gateway.ezwind.net, Sun, 12 Aug 2012 07:50:20 -0500 (not processed: message from valid local sender) X-MDRemoteIP: 71.81.129.230 X-Return-Path: jwest@ezwind.net X-MDaemon-Deliver-To: freebsd-xen@freebsd.org Cc: freebsd-xen@freebsd.org Subject: RE: Citrix Xenserver and FreeBSD migration/suspend scripts X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 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: Sun, 12 Aug 2012 12:50:49 -0000 Just tried the migration scripts on 64bit FreeBSD 9.0-Release & 9.1-Beta XENHVM kernel with PV drivers. Seems to work under Xenserver 6.0 and Xenserver 5.6SP2. I can't say how awesome that is, thank you VERY much to the people who worked on it. Not having stable virtualization with migration for FreeBSD under Xenserver has been a severe shortcoming for this FreeBSD zealot, finally we can roll out a new infrastructure with our preferred OS. Questions: 1) on the stock 64bit 9.0 & 9.1-beta XENHVM kernels, we still had the boot problem where after installing the kernel and rebooting, the boot failed as being unable to find the boot device. We had to pass a boot string of ad0p2 instead of the default ada0p2, and then edit fstab accordingly. I assume others here had to do that as well? 2) I'm sure this will show a lack of understanding on my part, but I'm just curious about the xen-tools port that has been in the ports collection for a little while. As per the pdf on the migration/suspend scripts, this needs to be installed first. I would think the current port - being called "xen-tools", would/should include these migration/suspend scripts. It's not xen-tools (in Citrix parlance) without that capability. So, is this a case of the new scripts just "finish off" the work that went into the current xen-tools script and the xen-tools port in the ports collection is functionally incomplete? I guess I'm unclear as to the history/relationship/status of the xen-tools port and these migration/suspend scripts. 3) In some of my googling on 64 bit XENHVM "how-to's", one of them (can't find it at the moment) mentioned 64 bit Freebsd not working right under Xen with regards to SMP, and the how-to offered several patches to disable SMP amongst other related items. To run the new migration/suspend scripts, did other people here need to use those patches? Jay West EZwind.net PO Box 460474 Saint Louis, MO 63146 Voice: (314) 262-4143 ext 1000 Toll Free: (866) 343-2589 Fax: (314) 558-9284 jwest@ezwind.net -------------------------------------------- This e-mail transmission may contain information that is proprietary, privileged and/or confidential and is intended exclusively for the person(s) to whom it is addressed. Any use, copying, retention or disclosure by any person other than the intended recipient or the intended recipient's designees is strictly prohibited. If you are not the intended recipient or their designee, please notify the sender immediately by return e-mail and delete all copies.