Date: Mon, 24 Jan 2011 16:31:38 -0500 From: Kevin Wilcox <kevin.wilcox@gmail.com> To: Outback Dingo <outbackdingo@gmail.com> Cc: questions@freebsd.org, Peter Harrison <peter.piggybox@virgin.net> Subject: Re: Managing ESXi from FreeBSD... Message-ID: <AANLkTi=p0s6nfQ-gmi8SMD8dtK9iwkoh0H%2BX3LBWRebN@mail.gmail.com> In-Reply-To: <AANLkTi=zGy9yzabWVvWh-56g7mHJ7Oxhz5gZ=4q9Nvcw@mail.gmail.com> References: <xPkfkhgcLFCg.GgMPLljv@smtp.virgin.net> <AANLkTi=zGy9yzabWVvWh-56g7mHJ7Oxhz5gZ=4q9Nvcw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 24 January 2011 13:42, Outback Dingo <outbackdingo@gmail.com> wrote: > loose ESucksXi and install XCP 1.0 and for management xencenter / > =C2=A0openxencenter will run on FreeBSD, I wish I could recommend XCP and/or Xen to the average user but trying to install FreeBSD 8.1-amd64 in Xen, even running in HVM, doesn't come close to the "boot and go" ease of FreeBSD in VMWare products. That opinion may change once I get a template similar to the provided Linux templates but until then, as far as I'm concerned, Xen can't touch ESXi. I would *love* for someone like RootBSD, who specialises in FreeBSD on Xen, to come through with tips on how they get it to work so well. In a stock install, running in an HVM environment, I get boot failures approximately two-thirds of the time, *usually* right after the ACPI APIC TABLE <Xen HVM> line but it does vary. By "boot failure" I mean vCPU usage drops to 0% for at least 10 - 15 minutes before I give up and reboot. kmw
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTi=p0s6nfQ-gmi8SMD8dtK9iwkoh0H%2BX3LBWRebN>