Date: Mon, 29 Jul 2013 21:19:22 +0200 From: Rasmus Fauske <rasmus@postboks.org> To: freebsd-isp@freebsd.org Subject: Re: Virtualizing FreeBSD... Message-ID: <51F6C03A.3050508@postboks.org> In-Reply-To: <1375125021.26149.2939727.6C668A92@webmail.messagingengine.com> References: <E1772891B3BA6EDA2EC23274@Mail-PC.tdx.co.uk> <91400827-DCA1-4B2F-AC6F-3287E0C85600@gmail.com> <1375125021.26149.2939727.6C668A92@webmail.messagingengine.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Den 29.07.2013 21:10, skrev Mark Felder: > On Mon, Jul 29, 2013, at 13:51, Florian Heigl wrote: >> - VMWare ESXi >> This is what I have also tried. I'm quite sure I have had the >> e1000/vmxnet autoswitching working fine and the overall experience was >> just fine. >> No bugs, no troubles. >> The platform is perfectly robust and plays nice with FreeBSD (what I'm >> trying to say: You can completely skip worrying about platform issues) >> > I completely disagree. I've even started a ridiculously long thread > about FreeBSD's nonstop crashing on VMWare ESXi. We moved to entirely > new hardware, rebuilt the VMs from scratch, new SANs, different ESXi > versions, etc. Never fixed it. VMWare kept saying "not a bug" and > refused to support FreeBSD, even though they claim to. > I have been running FreeBSD on several ESXi setups and have never had any other problem then not so speedy io. No crashes or anything. What problems did you have ? -- RF
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51F6C03A.3050508>