I've tried to do include the panic and trace with the screenshots i attached, i'm afraid i dont know another way to get the info across. I can appreciate the devs not being able to look at the/each virtualization issue, i was just hopeing someone knew what was going on.
Before reading on: the system seems to work fine with the bsd.mp of the 4.5 snapshot of 26/4/2009 as Stuart Henderson suggested. Now to be of some use atleast: " tricked network card to flexible " Default the vmware esxi only makes the E1000 network card available to the "Other 64-bit" guest os. (which is also recommended by vmware) If you set it to linux 32-bit or something along those lines, you can add a "flexible" network card, which openbsd picks up on as a pcn/AMD PCnet-PCI device. After which, you can switch back to "Other 64-bit" and the network card will stay as flexible. With a bit of testing on performance, i found this "network card" to perform much better than the e1000 over a virtual switch in vmware with no actual network card attached to it. (This was OpenBSD 4.4 unpatched). I'd be happy to test this out with 4.5 current as well. The actual (relevant?) hardware in the server: proc: AMD Phenom 9350e Quad-Core processor 4x2Ghz mobo: Supermicro H8SMI-2 rev 2 (MCP55 Pro chipset, incl dual lan) mem: 8GB ECC bank interleaving set (still waiting on the raid card and the ipmi device) That is not actually 2 physical sockets/processors on the board, but the hardware chosen is in the supported list on the vmware site. I will look into this a bit further, cheers! Thanks for taking the time to answer :) -----Original Message----- From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] On Behalf Of J.C. Roberts Sent: maandag 27 april 2009 17:48 To: Erwin van Maanen Cc: misc@openbsd.org Subject: Re: vmware esxi 3.5u4: amd64 4.4 generic bsd.mp kernel panic On Mon, 27 Apr 2009 16:16:57 +0200 "Erwin van Maanen" <maa...@acmeweb.nl> 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 __________ Information from ESET NOD32 Antivirus, version of virus signature database 4036 (20090427) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __________ Information from ESET NOD32 Antivirus, version of virus signature database 4036 (20090427) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com
