Things seem really slow on clean install of FreeBSD

I've done a clean install of FreeBSD in a virtual machine. I noticed that it takes a much longer time doing some things that are pretty much instant in Ubuntu (which is where I'm coming from). For one, when booting up, the SSH Daemon (sshd) takes like 25 seconds just to finish. I installed emacs and that takes like 20 seconds to load as well... I did install gnome but had nothing but problems with it. Keyboard wouldn't work, kept freezing up, and eventually the damn VM starting going through a boot loop. Whats the deal? I mostly want to get the EMACS thing fixed.
 
The responsiveness of the virtual machine is dependent upon a few factors:

  • VM type:
    Is it qemu, virtualbox, vmware, or some other?
  • Processor:
    64 or 32 bit? Virtual capabilities based upon PAE or AMD-V or Intel-VTx
  • Base system:
    Are you running a heavy desktop or a minimalist for the host?
  • Other hardware:
    This is for every OS>
 
This is using VirtualBox.I've assigned the guest 1024MB of RAM and left it with a single processor. My host is running Windows 7 64 bit with an i5 2500. Total RAM in this system is 8GB.
 
codeblox said:
I've done a clean install of FreeBSD in a virtual machine. I noticed that it takes a much longer time doing some things that are pretty much instant in Ubuntu (which is where I'm coming from). For one, when booting up, the SSH Daemon (sshd) takes like 25 seconds just to finish.

If it's slow but shouldn't be, suspect DNS timeouts. Is there a localhost entry in /etc/hosts?

I installed emacs and that takes like 20 seconds to load as well... I did install gnome but had nothing but problems with it. Keyboard wouldn't work, kept freezing up, and eventually the damn VM starting going through a boot loop. Whats the deal? I mostly want to get the EMACS thing fixed.

Possibly DNS also, maybe with the editor trying to look up localhost or some network resource.
 
Currently installing xorg. I did check my hosts earlier and it was empty O_O. I'll add the local host entry once this is done. So EMACS does name lookups as well?
 
I edited /boot/loader.conf earlier as something in a google search suggested adding

Code:
kern.hz=100
Didn't seem to make a difference though.
 
codeblox said:
I edited /boot/loader.conf earlier as something in a google search suggested adding

Code:
kern.hz=100
Didn't seem to make a difference though.

A kernel hertz rate of 1000 to 2500 is sufficient for a desktop system.
Did you install a complete system- such as with window manager and applications- or just the base system?
 
I only installed Xorg. But this issue was and still is happening before that. Even a startx takes quite a bit of time. Before I try the PC-BSD thing, I'm trying to build the vbox guest additions and install them. Jeez, building things on this OS consumes an unacceptable amount of disk space too.
 
You would be better off in the following fields if you would find yourself some older hardware on which you can install FreeBSD:
  • System responsiveness
  • Learning
  • Maintenance
  • Et cetera, et al
Even with multiple cores, the host system will determine the basic stress and requirements on the machine.
 
Not sure if you're being sarcastic or not. Are you saying FreeBSD is better off not installed in a VM? I'm willing to go this route if you're serious. My whole point in trying to get FreeBSD up and running is to learn how it works. I've been obviously spoonfed everything with all the Ubuntu use and wanted to see if I could get a working install of FreeBSD and install the desktop environment myself.
 
My host machine has more than enough resources to handle FreeBSD. What are some more possibilities for things going SO_SLOW?
 
The rules for kern.hz changed recently, at least on i386/amd64 architectures, and setting it to 100 is now recommended... although I can't remember where.

Is it slow in a real console? Turning off our old friend AllowEmptyInput for xorg can make X seem very slow due to input not being read correctly.
 
It's slow in console and with the x window system. Disappointing, I was really looking forward to learning this OS. Is this how it really is for people? Should I try reinstalling it? Note ** When I got gnome installed, my keyboard wasn't even working with it after a few keystrokes of logging in...
 
codeblox said:
It's slow in console and with the x window system. Disappointing, I was really looking forward to learning this OS. Is this how it really is for people?

Hasn't been that way for me, although I guess I haven't used Windows for a VirtualBox host much.

Should I try reinstalling it? Note ** When I got gnome installed, my keyboard wasn't even working with it after a few keystrokes of logging in...

Possibly a HAL thing. Again, try PC-BSD. All of the configuration is already done.
 
I'll give it a whirl and see what happens. I'll probably go back to this and try again, even though I have reinstalled this twice already for different reasons with the same result. I haven't had this problem with other guest OS on this machine.
 
Well, things seem to work fine in PC-BSD. I downloaded the virtualbox disk image which looks like someone else already did the installation. Very nice.
 
I got Xfce installed in freebsd FreeBSD and I like the sleek simple look a lot. More satisfied with this than gnome. This would be perfect if my slow response issue would go away.
 
A lot of us like xfce. :)

Wait, you mean the slow response problem didn't go away? When creating the VM, did you change any of the defaults in VirtualBox?
 
For PC-BSD, everything worked fine and emacs came right up which was great - and by the way, PC-BSD looks awesome -. I went back to FreeBSD and reinstalled again and this time installed XFCE instead of GNOME. When launching my applications like firefox or emacs there's a 20 or so second delay. Stuff that was already installed with FreeBSD comes right up without a delay - Vi for example-. I left all the defaults settings in Virtualbox for both PC-BSD and FreeBSD.
 
Back
Top