Date: Thu, 29 Mar 2012 17:07:47 -0500 From: Mark Felder <feld@feld.me> To: freebsd-hackers@freebsd.org, freebsd-questions@FreeBSD.org Cc: Adam Vande More <amvandemore@gmail.com> Subject: Re: Please help me diagnose this crazy VMWare/FreeBSD 8.x crash Message-ID: <op.wbyc29ag34t2sn@tech304> In-Reply-To: <CA%2BtpaK3UAx4cU3zRWPOo=PqmA0wZH9GbVZ9vAEeenUpD8Mitgw@mail.gmail.com> References: <201203291549.q2TFnUc7080406@aurora.sol.net> <201203291755.36651.hselasky@c2i.net> <op.wbxxb9cz34t2sn@tech304> <CAJUyCcNn%2B8uDrWGJMUD8vmmJKLA0iJjy6bhDSZvGB82X6awAPw@mail.gmail.com> <op.wbx2n80s34t2sn@tech304> <CA%2BtpaK3UAx4cU3zRWPOo=PqmA0wZH9GbVZ9vAEeenUpD8Mitgw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 29 Mar 2012 15:53:52 -0500, Adam Vande More =20 <amvandemore@gmail.com> wrote: > > Doesn't VMWare offer different types of emulated disk controllers? If = =20 > so, > that might be the easiest way to narrow the field. Another thing = maybe =20 > to > try would be to backport the mpt Yes, they offer Paravirtual (not applicable for FreeBSD), LSI Parallel =20 (default option), LSI SAS, and Buslogic (not available for 64bit). Both LSI SAS and LSI Parallel use the mpt driver. > > Also, it's not VMWare's place to claim "not our problem" when you are > paying for support. If this doesn't happen on bare metal, it's a = VMWare > issue, or they need to demonstrate it's not their issue. At least that > would be the expectation I have. You're right, but we've thrown a ton of money at their support and had =20 direct phone access to their engineers. The best we can get out of them = is =20 "no indication this is a VMWare problem". It's easy for them to blow =20 people off when they're as big as they've grown to be. > There is also a comment on this post indicating someone else with the =20 > issue > and who has received unofficial vmware feedback. > > http://www.hailang.me/tech/virtual/freebsd-vmware-esx-a-weird-error-wit= h-san-storage/ I found that post ages ago and that's me, "mf", as the only person to =20 comment on it. Unfortunately our problem does not align with what he's =20 describing. > > And then there is this one with similar symptoms and a workaround: > > http://forums.freebsd.org/showthread.php?t=3D27899 > I'm now investigating those loader.conf options. I have my crashy = machine =20 set to use them on next boot so we'll see if it crashes now that I'm = using =20 LSI SAS emulated controller. If it still crashes, we'll see what happens = =20 after that with those loader.conf options enabled.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.wbyc29ag34t2sn>