On Thursday 07 June 2007, Frank Mehnert wrote:
> On Thursday 07 June 2007, David Baron wrote:
> > On Wednesday 06 June 2007, Brian Green wrote:
> > > David Baron wrote:
> > > > On Wednesday 06 June 2007, Brian Green wrote:
> > > >> David Baron wrote:
> > > >>> On Wednesday 06 June 2007, Frank Mehnert wrote:
> > > >>>> On Wednesday 06 June 2007, David Baron wrote:
> > > >>>>> Use the init.d script. It first disables NMI. I would suppose
> > > >>>>> that if NMI is active, modprobe alone would fail.
> > > >>>>
> > > >>>> No, it does not. Please add the kernel parameter 'nmi_watchdog=0'
> > > >>>> (at the kernel command line when booting the kernel. We will try
> > > >>>> to disable the watchdog in from within the module in the next
> > > >>>> release.
> > > >>>
> > > >>> I get the message,
> > > >>> "Trying to permamently stop nmi watchdog ...."
> > > >>> "successful"
> > > >>> From the init script.
> > > >>>
> > > >>> Putting it in the commandline is a good idea. How do I get there
> > > >>> from a simple menu in lilo? options: nmi_watchdog=0 ?
> > > >>
> > > >> Yeah - I can confirm that "/etc/init.d/vboxdrv start" {etc} fails.
> > > >
> > > > Mine works
> > > >
> > > >> Similarly, how do I insert the "nmi_watchdog=0" in the command line
> > > >> - I use grub.
> > > >
> > > > For lilo, I am trying append="nmi_watchdog=0"
> >
> > Did it.
> > Still get the "stopping nmi_watchdog permantently message ... success"
> > So maybe the command needs be a bit different?
> >
> > Anyway, mine works in any event.
>
> This message is ok. 'nmi_watchodog=0' means that the watchdog is not
> enabled during boot. Then the vboxdrv module tries to disable it
> permanently. This is not possible if the watchdog was enabled once during
> boot. So if your module loads without an error everything should be fine
> for you.
>
Cool. I have three kernels around:
A 2.6.21 and two version of 2.6.21 with real time premption patches.
The plain 2.6.21 .config has no entry for NMI (I unchecked that for the above 
reason, I suppose :-) )
The -rt versions have NMI instrumentation support =y.

The vboxdrv startup is the same in all of them.

But as we have seen, this is not the "invalid argument" poster's problem.

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

Reply via email to