Op maandag 13 april 2009 09:37:18 schreef Frank Mehnert:
> On Monday 13 April 2009, 赵华龙 wrote:
> > hi
> >
> > I installed VirtualBox-2.2.0_45846_rhel5-1.x86_64.rpm on my server CentOS
> > 5.2.
> >
> > [r...@bogon2 tmp]# rpm -ivh VirtualBox-2.1.4_42893_rhel4-1.i386.rpm
> > Preparing...                ###########################################
> > [100%]
> >    1:VirtualBox             ###########################################
> > [100%]
> >
> > Creating group 'vboxusers'. VM users must be member of that group!
> >
> > No precompiled module for this kernel found -- trying to build one.
> > Messages emitted during module compilation will be logged to
> > /var/log/vbox-install.log.
> >
> > Success!
> >
> > then, it seems to reboot!!
> > And it reboot again and again. Every time when system loads virtualbox
> > kernel, it crashed and reboot again.
>
> Seems that loading the kernel modules causes your system to reboot.
> To prevent loading the modules, do the following:
>
> Try to boot your system in single user mode. During the GRUB prompt,
> edit the command line (press 'e') and append the word
>
>   single
>
> to the command line. Finish with <Enter> and boot with 'b'. Then edit
> the file /etc/init.d/vboxdrv and add
>
>   exit 0
>
> at the begin of that file. After that, reboot and your system should
> come up again. Please look at /var/log/messages for any strange error
> messages.
>
> You could also try to load the modules manually:
>
>   modprobe vboxdrv
>
> -- does your system reboot? If not,
>
>   modprobe vboxnetflt
>
> -- then it will probably reboot now. No worry, after your system
> rebooted, the modules will not be loaded automatically the next time.
>
> The output of 'dmesg' could also help us investigating the problem.
>
> Kind regards,
>
> Frank

I am having the same problem with 2.2.0, however the server is 50 km from 
where I am.

It is a bad idea to do a reboot in an update process. Not even installing a 
new kernel will automatically do a reboot (at least in openSUSE). Only a 
warning that the system needs a reboot to make the kernel active is displayed.

-- 
fr.gr.

Freek de Kruijf

_______________________________________________
vbox-users mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-users

Reply via email to