Date: Fri, 08 May 2009 07:34:21 -0400 From: "Brian A. Seklecki" <seklecki@noc.cfi.pgh.pa.us> To: Daniels Vanags <daniels.vanags@smpbank.lv> Cc: questions@freebsd.org Subject: Re: FreeBSD on VMware ESXi Message-ID: <1241782461.2053.5.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com> In-Reply-To: <E8298C3B2FC1CC43B3FBAC70544780A602D45135@EXCH-01.mbint.multibanka.com> References: <E8298C3B2FC1CC43B3FBAC70544780A602D45135@EXCH-01.mbint.multibanka.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1241782461.2053.5.camel>