From owner-freebsd-questions@FreeBSD.ORG Fri May 8 11:43:45 2009 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C3A59106564A for ; Fri, 8 May 2009 11:43:45 +0000 (UTC) (envelope-from seklecki@noc.cfi.pgh.pa.us) Received: from mx00.pub.collaborativefusion.com (drpmx.lab02.pitbpa0.pub.collaborativefusion.com [206.210.89.232]) by mx1.freebsd.org (Postfix) with ESMTP id 7432A8FC18 for ; Fri, 8 May 2009 11:43:45 +0000 (UTC) (envelope-from seklecki@noc.cfi.pgh.pa.us) Received: from [192.168.2.161] (soundwave.ws.pitbpa0.priv.collaborativefusion.com [::ffff:192.168.2.161]) (AUTH: LOGIN seklecki, TLS: TLSv1/SSLv3,256bits,CAMELLIA256-SHA) by wingspan with esmtp; Fri, 08 May 2009 07:38:40 -0400 id 001BAC33.000000004A0419C0.00011513 From: "Brian A. Seklecki" To: Daniels Vanags In-Reply-To: References: Date: Fri, 08 May 2009 07:34:21 -0400 Message-Id: <1241782461.2053.5.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit X-Mailer: Evolution 2.24.5 (2.24.5-1.fc10) Cc: questions@freebsd.org Subject: Re: FreeBSD on VMware ESXi X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 May 2009 11:43:46 -0000 On Wed, 2009-05-06 at 13:44 +0300, Daniels Vanags wrote: > We moved Hard Disk Drives from HP ProLiant DL 385 G2 with 4GB RAM, AMD > Opteron processor to HP ProLiant DL 380 G5, 4GB RAM, Intel Xeon > processor. > > Disks contain FreeBSD Virtual Machines running in VMware ESXi Server. > When trying to boot, getting error: BTX halted. > > Please explain, how to start FreeBSD on different hardware. Well, assuming that HFUX's RAID, VMWare and Linux doesn't totally shit the bed from the hypervisor CPU type change, the VMs are controllable from the spiffy AJAX/.Net20 VMWare management console. There's plenty of debugging available from there. Presumably all of the virtual hardware presented to the VM will be the same, except the CPU details. ~BAS