On Mon, 27 Apr 2009 16:16:57 +0200 "Erwin van Maanen" <[email protected]> wrote:
> Running OpenBSD on a vmware esxi server, whenever i boot the amd64 > bsd.mp version i get stuck with kernel panic. > > panic: fp_save ipi didn't > > > > I've tried several things: > > - amd64 bsd.mp, without network card(s): boots normal > > - amd64 bsd.mp, with tricked network card to flexible (pcn device): > same panic just right after the httpd loads > > - i386 bsd.mp: no problems so far > > - amd64 without mp: no problems > > > > dmesg (of the normal bsd boot, not mp): > > http://www.hutmeel.nl/panic/dmesg.txt > > > > I've made a few screenshots of the panic message, trace, ps and show > registers. > > http://www.hutmeel.nl/panic/panic0-2.gif > > http://www.hutmeel.nl/panic/panic0.gif > > http://www.hutmeel.nl/panic/panic1.gif > > http://www.hutmeel.nl/panic/panic2.gif > > http://www.hutmeel.nl/panic/panic3.gif > > http://www.hutmeel.nl/panic/panic4.gif > > > > As you can see on the first screenshot, it looks like it happens as > soon as ntpd starts. > > Any help in the right direction would be greatly appreciated. (was > searching the archives, but couldn't find a similar problem) > > > > -- Erwin > First of all, running OpenBSD on anything other than real hardware is not supported. --The developers have better things to do than fight with imaginary bugs on imaginary hardware (i.e. "virtualization"). If you hit a bug running under virtualization, then the problem is the responsibility of the vendor of said virtualization because they are obviously failing to emulate hardware exactly. Secondly, what part of the following message did you fail to understand? "RUN AT LEAST 'trace' AND 'ps' AND INCLUDE THE OUTPUT WHEN REPORTING THIS PANIC! DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THIS INFORMATION" O.K. Now with stating the obvious above out of the way, I did get an ESX license last week for the lab, but I'm still waiting on Dell to deliver the T610 hardware. If you can explain what you mean by, "tricked network card to flexible," it would help. Also, even though we are off topic for m...@openbsd, it might help to state the exact, *real* hardware you're using to run ESX. As I found out the hard way, ESX is *very* picky and doesn't play well with most real hardware. Did you realize you are *supposed* have two (2) populated processor sockets (2 physical processors) in order to run *any* 64-bit operating system as a guest on top of ESX? --I found this limitation buried deep in the ESX docs, and hence the question about the real hardware you're using to run ESX. -- J.C. Roberts
