On Monday 13 April 2009, Freek de Kruijf wrote: > Op maandag 13 april 2009 20:15:51 schreef Frank Mehnert: > > On Monday 13 April 2009, Freek de Kruijf wrote: > > > 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. > > > > Let me underline two things: > > 1. There is obviously a bug which causes a reboot when one of the kernel > > module is loaded. So we didn't see this problem on any of our > > testboxes. 2. We need more information to investigate this problem. Does > > this spontaneous reboot occur only on CentOS 5.2? > > No, I did have it on openSUSE 11.1 (i568), I saw the message that the > system was doing a reboot, so somehow "shutdown -r +?" has been done. > However openSUSE just went down and after a powerup it started normally > with 2.2.0 properly installed and vboxdrv loaded. > I used zypper to update the package, and zypper just calls rpm. I saw also > a message it was building vboxdrv. However i did have a VM running, > apparently not very smart.
In that case this might be a known problem. VirtualBox releases 2.1.0 til 2.1.4 have a bug which allows to unload the vboxnetflt kernel module even if there are host-only networks active. The result is normally a kernel panic. This problem is fixed as of VirtualBox 2.2.0 where the kernel module can't be unloaded as long as at least one VM uses the netfilter code. Kind regards, Frank -- Dr.-Ing. Frank Mehnert Sun Microsystems http://www.sun.com/
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
