Jon LaBadie さんは書きました:
> Daniel Hauck wrote:
>> Jon LaBadie さんは書きました:
>>> On a Fedora 9 system I've been running VirtualBox 2.0.6. Skipped 2.1.0
>>> but just upgraded to 2.1.2. Things were fine, guest os booted and ran
>>> ok. But after a Fedora reboot the guest os would not restart.
>>>
>>> I tracked it down to my ethernet interface (vbox0) was not starting on
>>> reboot. This was due to /etc/init.d/vboxnet being removed by the
>>> upgrade. (BTW it also appears to be missing in the 2.1.0 Fedora rpm)
>>> When I reloaded the vboxnet file from a 2.0.6 rpm, things are running
>>> fine again.
>>>
>>> Am I overlooking some change in 2.0.6 -> 2.1.{10|12} the obviates the
>>> need for /etc/init.d/vboxnet to start the virtual nic?
>>>
>> In the past I have run into similar glitches. But if you, as root, run:
>>
>> # /etc/init.d/vboxdrv setup
>>
>> That should cause the rebuilding and installing of the kernel modules
>> needed for the service to load and run.
>
> I was skeptical that this suggestion would work, but tried it anyway.
> The reasons for my skepticism:
> - the shell script is included in the 2.0.6 rpm
> - my ubuntu system has exactly the same script
> - it really isn't "buildable" nor a kernel module
> - I thought I did do a vboxdrv setup already
>
> But as noted, I tried vboxdrv setup after moving vboxnet. But it did
> not create a new vboxnet file.
>
> Thanks for the thought, any others?
>
> jl
I do not have a "vboxnet" script either. Perhaps it is not needed? If
you are doing host networking, just set it up to run against eth0 or
your wireless or whatever. You will find the switch from 2.0.x to 2.1.x
to be quite pleasant in that way. The other networking options are
there as well.
If you created any process in rc.local for bridging and stuff, you will
want to remove that code. Then things should work fine.
_______________________________________________
vbox-users mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-users
