Thanks Frank!

Let me try to give you the text of the error message from memory, since 
I won't be back at that machine for several hours.

1.   On attempting to start a VM (power on), the prompts tell me to run 
/etc/init.d/vboxdrv  setup
2.   When I do that, the prompt tells me that vboxdrv is already running.
3.   When I run  ps aux | grep VBoxSVC   (or VB*, or vb*) no running 
process appears except grep.
4.   I cannot find a line in the log which says either "failure" or 
"error," but there may be something named in another way.
5.   I can run another recompile and look carefully at the log as it 
rolls by to see if there is indeed some kind of failure in compilation 
that I have missed.   Oddly, though, the control screen comes up just fine.

Let me ask a question that is backing up a bit--are there installations 
running on Fedora 7?  Or is it possible that
 the raw newness of the Fedora releases always builds in features that 
software developers cannot easily trace or debug? 

Frank Mehnert wrote:
> On Wednesday 24 October 2007, Lawrence H. Nitz wrote:
>   
>> Unfortunately, there does not appear to be a VBoxSVC or any othe  VB or
>> vbox routine running.  I have scanned the log for the words "error" and
>> "fail" but fin not mention of failure in the compilation.Can you suggest
>> a two or three step procedure that would help me verify the integrity of
>> the complile, and then of the results of  the "make install." procdure?
>>     
>
> Again, what is the error message VBox gives you?
>
> Once the vboxdrv module was successfully loaded the module integrity is
> proved.
>
> Kind regards,
>
> Frank
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> vbox-users mailing list
> [email protected]
> http://vbox.innotek.de/mailman/listinfo/vbox-users
>   

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

Reply via email to