Re: FreeBSD 6.0 rc1 guest under vmware-workstation-5.0.0.13124-r2 on linux host (boot error)
Ralph Hempel wrote: Robin wrote: Hello all, I thought I'd give the new RC a whirl under vmware, after setting the guest to boot from the CDROM (which was the CD1 .ISO), shortly I recieved this error: http://xs.mw/temp/freebsd6rc1_vmware_boot_error.png (BTX halted) Yep. Me too. I googled this and it appears to be a known issue with the IDE CDROM driver in 6.0 One way to work around the problem is to connect the virtual CD to the FreeBSD ISO image instead of burning an actual CD. Another is to do an FTP install using FileZilla or some other FTP server program on the host Windows system. All in all VMWare really is a pretty cool way to experiment with different FreeBSD installs before committing to a real box! Cheers, Ralph ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
kmem_malloc(4096): kmem_map too small: 536870912 total allocated
We have 2xOpteron/2Gb RAM server with extrensive disk load. Every week or two it suddenly hangs with kmem_malloc(4096): kmem_map too small 335bla-bla allocated. I look onto handbook and put vm.kmem_size_max=536870912 onto /boot/loader.conf. Today was the same with the new parameters. Is there any other solutions ? # sysctl -a | grep kmem vm.kmem_size: 536870912 vm.kmem_size_max: 536870912 vm.kmem_size_scale: 3 The only vm.kmem_size_max on loader.conf, no vm.kmem_size. We're running FreeBSD 6.0-BETA5 #0: Wed Sep 28 16:54:33 EEST 2005 in i386 mode. The same was with 5.3/5.4 and NetBSD 2.0 on this machine. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kmem_malloc(4096): kmem_map too small: 536870912 total allocated
On Sun, Oct 23, 2005 at 10:43:42AM +0300, Vladimir Sharun wrote: We have 2xOpteron/2Gb RAM server with extrensive disk load. Every week or two it suddenly hangs with kmem_malloc(4096): kmem_map too small 335bla-bla allocated. I look onto handbook and put vm.kmem_size_max=536870912 onto /boot/loader.conf. Today was the same with the new parameters. Is there any other solutions ? If that's not enough, try making it larger. Kris pgp2i0Ml6rdux.pgp Description: PGP signature
Re: kmem_malloc(4096): kmem_map too small: 536870912 total allocated
Kris Kennaway wrote: KK On Sun, Oct 23, 2005 at 10:43:42AM +0300, Vladimir Sharun wrote: We have 2xOpteron/2Gb RAM server with extrensive disk load. Every week or two it suddenly hangs with kmem_malloc(4096): kmem_map too small 335bla-bla allocated. I look onto handbook and put vm.kmem_size_max=536870912 onto /boot/loader.conf. Today was the same with the new parameters. Is there any other solutions ? KK If that's not enough, try making it larger. On what size we can be sure, that that's enough ? -- UKR.NET Postmaster ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kmem_malloc(4096): kmem_map too small: 536870912 total allocated
On Sun, Oct 23, 2005 at 11:21:10AM +0300, Vladimir Sharun wrote: Kris Kennaway wrote: KK On Sun, Oct 23, 2005 at 10:43:42AM +0300, Vladimir Sharun wrote: We have 2xOpteron/2Gb RAM server with extrensive disk load. Every week or two it suddenly hangs with kmem_malloc(4096): kmem_map too small 335bla-bla allocated. I look onto handbook and put vm.kmem_size_max=536870912 onto /boot/loader.conf. Today was the same with the new parameters. Is there any other solutions ? KK If that's not enough, try making it larger. On what size we can be sure, that that's enough ? It depends on your workload, so keep increasing it until the problem stops or you discover that you need more RAM to handle your workload. Kris pgpRpq2GKrEow.pgp Description: PGP signature
Re: kmem_malloc(4096): kmem_map too small: 536870912 total allocated
Kris Kennaway wrote: We have 2xOpteron/2Gb RAM server with extrensive disk load. Every week or two it suddenly hangs with kmem_malloc(4096): kmem_map too small 335bla-bla allocated. I look onto handbook and put vm.kmem_size_max=536870912 onto /boot/loader.conf. Today was the same with the new parameters. Is there any other solutions ? KK If that's not enough, try making it larger. The second issue: I can't set it too high: 700M and more result to kernel panic during boot. 600M is acceptable. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kmem_malloc(4096): kmem_map too small: 536870912 total allocated
On Sun, Oct 23, 2005 at 12:05:26PM +0300, Vladimir Sharun wrote: Kris Kennaway wrote: We have 2xOpteron/2Gb RAM server with extrensive disk load. Every week or two it suddenly hangs with kmem_malloc(4096): kmem_map too small 335bla-bla allocated. I look onto handbook and put vm.kmem_size_max=536870912 onto /boot/loader.conf. Today was the same with the new parameters. Is there any other solutions ? KK If that's not enough, try making it larger. The second issue: I can't set it too high: 700M and more result to kernel panic during boot. 600M is acceptable. That probably indicates you're running close to the point where you need more RAM in your system. Kris pgpw0E6L5mgsZ.pgp Description: PGP signature
Re: FreeBSD 6.0 rc1 guest under vmware-workstation-5.0.0.13124-r2 on linux host (boot error)
One way to work around the problem is to connect the virtual CD to the FreeBSD ISO image instead of burning an actual CD. Actually this is what I tried, and still got the error. Today, I shall attempt an ftp install. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kmem_malloc(4096): kmem_map too small: 536870912 total allocated
Kris Kennaway wrote: We have 2xOpteron/2Gb RAM server with extrensive disk load. Every week or two it suddenly hangs with kmem_malloc(4096): kmem_map too small 335bla-bla allocated. I look onto handbook and put vm.kmem_size_max=536870912 onto /boot/loader.conf. Today was the same with the new parameters. Is there any other solutions ? KK If that's not enough, try making it larger. On what size we can be sure, that that's enough ? KK It depends on your workload, so keep increasing it until the problem KK stops or you discover that you need more RAM to handle your workload. Looks like kernel leak (thanks for tip to Gleb Smirnov) in lockf. # vmstat -zm | grep lock lockf 2257779 70556K - 19476940 32,64 ... and keep raising. That's another one machine with 1Gb RAM, having 512M for vm.kmem_size_max too. -- UKR.NET Postmaster ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
