On 19/08/10 00:33, Istvan Gabor wrote: > Hello: > > I am new on this list as well as to virtual box. > I use openSUSE 11.2. I could successfully install > VBox 3.2.8 and set up windows 2000 as guest OS. > For communication between the host and guest I > have set up a host only network in VBox which works > well. The only thing I have problem with is that > the vboxnet0 virtual interface is not created until > Virtualbox and the guest machine is not started. > > It would be important the interface to be created > at computer boot since samba daemon (smbd) can not > start until the interface does not show up. > > (Samba is configured to bind only to this inerface; > if the interface is not present smbd dies at boot.) > > My question is if it is possible and how to force > the creation of vboxnet0 interface at computer startup. > > Any help is appreciated. > Thanks, > > Istvan > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > _______________________________________________ > VBox-users-community mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/vbox-users-community > > Istvan,
I'm behind on reading this list, so delayed response. But apparently this question was not answered yet. Hope you got a solution in the mean time; but if not... You do not mention what components of Samba you use; if it is just the SMB server, the easiest way is to use vbox shared folders instead of smb. If of course you use things like the domain controller, or print server, this would not be an option. In that case, please try the following: Since in your case smbd maps to vboxnet0 only, I assume smbd has no other dependees in the boot sequence, so you could change the order of boot script execution by making sure the script starting the smb daemon runs after the vboxdrv script (which loads the vboxnet0 device drivers). So fi. starting vboxdrv as S20vboxdrv, then starting smbd as S21samba (iso the S20... default) should work OK. Simply rename the script in your /etc/rc[235].d directories (where appropriate), then reboot. Revert to original setting (and frustration :-( if this poses issues -- but as said, I do not think there will be side effects. ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ VBox-users-community mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/vbox-users-community
