Re: Kernel Panic in 3.7
Ted, Is it possible to fix that out of memory condition panic() so that instead of a panic system closes one or more of the processes to continue to run? cheers, Masoud Sharbiani Ted Unangst wrote: On Mon, 18 Jul 2005, Gordon Ross wrote: I've got an OpneBSD 3.7 machine (no patches - just the standard 3.7 CD install) running under VMWare GSX Server V3.1 Today, the machine had stopped with a panic. I did a trace and ps as per the instructions. Below is the result of these extracted from /var/adm/messages after I rebooted the machine. Is there anything else I should provide ? Anything else I should do if it happens again ? running out of memeory is an unsupported configuration. buy some more.
Re: Kernel Panic in 3.7
On Wed, Jul 20, 2005 at 10:46:34AM -0400, Masoud Sharbiani wrote: | Is it possible to fix that out of memory condition panic() so that | instead of a panic system closes one or more of the processes to | continue to run? Great Idea ! That way, your server will just keep running and shooting of random processes as time goes by. Sort of like russian roulette - it may be that silly cronjob that should've been killed months ago, or it might be your sshd. All bets are on ! Hmm - might not be such a good idea after all. Perhaps we can mark certain processes as 'not killable' for this use, then you can rest assured that your memory will soon be filled with non-killable processes. The panic may not be the best solution to this problem, but killing processes is far worse. Feel free to think up a better solution, write a patch and submit it for review but let's not go the linux way, please ;P Cheers, Paul 'WEiRD' de Weerd -- [++-]+++.+++[---].+++[+ +++-].++[-]+.--.[-] http://www.weirdnet.nl/ [demime 1.01d removed an attachment of type application/pgp-signature]
Re: Kernel Panic in 3.7
So that's what the kernel panic really means: Out of memory ? GTG Ted Unangst [EMAIL PROTECTED] 19/07/2005 03:36 On Mon, 18 Jul 2005, Gordon Ross wrote: I've got an OpneBSD 3.7 machine (no patches - just the standard 3.7 CD install) running under VMWare GSX Server V3.1 Today, the machine had stopped with a panic. I did a trace and ps as per the instructions. Below is the result of these extracted from /var/adm/messages after I rebooted the machine. Is there anything else I should provide ? Anything else I should do if it happens again ? running out of memeory is an unsupported configuration. buy some more. -- And that's why you should cast your ballot today.
Re: Kernel Panic in 3.7
On Tue, 19 Jul 2005, Gordon Ross wrote: So that's what the kernel panic really means: Out of memory ? yes and no. it means what it says, but the root cause is being out of memory. -- And that's why we're leaving California.
Re: Kernel Panic in 3.7
+++ Rico [Mon Jul 18, 2005 at 05:31:59PM +0200]: You should not run OpenBSD under VMWare. What makes you say that? If you need serveral virtual machines, you can run OpenBSD chrooted as many times as you need, without running it under VMWare. That simply is not true. OpenBSD runs great under VMWare. In fact, virtualization has enabled admins to have one server running several instances of Open/NetBSD and Windows 2003 EE (with exchange + AD) running fine. As for the original author, try adding more ram/swap to the GSX server and see if you can reproduce the crash
Re: Kernel Panic in 3.7
Bruno Delbono wrote: +++ Rico [Mon Jul 18, 2005 at 05:31:59PM +0200]: You should not run OpenBSD under VMWare. What makes you say that? I did explain this.
Re: Kernel Panic in 3.7
On Mon, July 18, 2005 11:31 am, Rico wrote: You should not run OpenBSD under VMWare. Runing any OS under a product like VMWare makes it hard to trust which product is actually causing the errors, incl. kernel panics. That's ridiculous. Sure, it adds a layer of complexity, but not much more than using varied hardware. For example, you could rewrite your statements: --- You should not run OpenBSD on PC clones. Running any OS on a product like PC clones makes it hard to trust which product is actually causing the errors, incl. kernel panics. --- (Which is completely true...) That said, I've run OpenBSD on GSX 3.0, 3.1 and 3.2 on Windows, as well as ESX 2.1 and 2.5, without any major problems. Some things are annoying (like using X without their proprietary mouse driver) but no problems. In fact, at least the mpt driver has VMWare-specific checks, so arguably it's supported.
Re: Kernel Panic in 3.7
+++ Rico [Mon Jul 18, 2005 at 06:07:31PM +0200]: Bruno Delbono wrote: +++ Rico [Mon Jul 18, 2005 at 05:31:59PM +0200]: You should not run OpenBSD under VMWare. What makes you say that? I did explain this. Well then looking at what your wrote initially, there is no merit to your argument.
Re: Kernel Panic in 3.7
Bruno Delbono wrote: +++ Rico [Mon Jul 18, 2005 at 06:07:31PM +0200]: Bruno Delbono wrote: +++ Rico [Mon Jul 18, 2005 at 05:31:59PM +0200]: You should not run OpenBSD under VMWare. What makes you say that? I did explain this. Well then looking at what your wrote initially, there is no merit to your argument. There is indeed, but it depends on who reads the answer.
Re: Kernel Panic in 3.7
On Tue, Jul 19, 2005 at 02:17:19AM +0200, Rico wrote: [EMAIL PROTECTED] wrote: On Mon, July 18, 2005 11:31 am, Rico wrote: You should not run OpenBSD under VMWare. Runing any OS under a product like VMWare makes it hard to trust which product is actually causing the errors, incl. kernel panics. That's ridiculous. No. But I trust you have full access to the source of VMWare so that you really know what you talk about? Do I have access to that? No, but let the dude run OpenBSD on the exact same hardware as before but without VMWare and lets see if the problems still exists! Sure, it adds a layer of complexity, but not much more than using varied hardware. Based on what do you state that? It not only adds a layer of complexity, it adds a layer of tons of possible errors, which might or might not show up. For example, you could rewrite your statements: --- You should not run OpenBSD on PC clones. No, you could not rewrite my answer into to gobble like that. That said, I've run OpenBSD on GSX 3.0, 3.1 and 3.2 on Windows, as well as ESX 2.1 and 2.5, without any major problems. Good for you. I never said you can't run it, I just said that he or onyone should not. Unless you can provide a waranty that the kernel panic isn't caused by VMWare. This issue has been reported in the past on real hardware. Now shut up and go away. You're creating unnecessary noise on this list for no good reason. Enough!
Re: Kernel Panic in 3.7
On Mon, 18 Jul 2005, Gordon Ross wrote: I've got an OpneBSD 3.7 machine (no patches - just the standard 3.7 CD install) running under VMWare GSX Server V3.1 Today, the machine had stopped with a panic. I did a trace and ps as per the instructions. Below is the result of these extracted from /var/adm/messages after I rebooted the machine. Is there anything else I should provide ? Anything else I should do if it happens again ? running out of memeory is an unsupported configuration. buy some more. -- And that's why you should cast your ballot today.
