This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
other:vb:use [2015/01/18 17:53] jypeter Added instructions to restart the VM network |
other:vb:use [2015/06/08 14:55] jypeter Added the shared folders section |
||
---|---|---|---|
Line 45: | Line 45: | ||
See the //Power off the machine// option above | See the //Power off the machine// option above | ||
+ | |||
+ | ===== Using shared folders ===== | ||
+ | |||
+ | * The shared folders make it possible for the guest to access directories of the host | ||
+ | * The guest additions have to be installed in order to use the shared folders! | ||
+ | * The Linux account on the guest that will use the Shared Folders has to be a member of the //vboxsf// Linux group | ||
+ | |||
+ | ==== Configuration and use ==== | ||
+ | |||
+ | * Shut down the VM if it is running | ||
+ | * Select the VM in the //VB Manager// window | ||
+ | * Settings => Shared Folders | ||
+ | * Click on the '+' sign and fill the fields of the //Add Share// window | ||
+ | * Folder Path: e.g. ''H:\Scratch\<user_login>'' | ||
+ | * Folder Name: e.g. ''Scratch'' | ||
+ | * Auto-mount: selected | ||
+ | * The newly configured folder will appear in the //Machine Folders// list | ||
+ | * Start the VM and login | ||
+ | * Type ''df -h'' and check that the defined shared folder appears as /media/sf_Scratch | ||
===== Basic use of the VB ===== | ===== Basic use of the VB ===== | ||
Line 54: | Line 73: | ||
You can reboot the VM, or more simply just restart the network (in the VM), with the following:\\ ''sudo service network restart'' | You can reboot the VM, or more simply just restart the network (in the VM), with the following:\\ ''sudo service network restart'' | ||
+ | |||
+ | ==== Problems when mounting LSCE disks in the VM ==== | ||
+ | |||
+ | When your host is connected **to the LSCE network**, your VM should be able to access/mount directly all the LSCE disks in the VM (e.g., you can type ''cd /home/users/your_login'' directly in local terminal of your VM to access your LSCE home directory). | ||
+ | |||
+ | If you get an error message, there is probably a kerberos related problems... You can try typing ''klist'' and ''kinit'' in your local terminal and see if you can then access the LSCE disks! | ||
+ | |||
+ | If you still can't mount the disks, check the status of autofs, and restart it if necessary: | ||
+ | |||
+ | * ''sudo systemctl status autofs'' | ||
+ | * ''sudo systemctl start autofs'' | ||
+ | |||
===== Some useful things to configure ===== | ===== Some useful things to configure ===== | ||
Line 67: | Line 98: | ||
* to add an xterm launcher:\\ Name: xterm\\ Command\\ xterm -ls -sl 1000 -bg black -fg white\\ Click on the icon in the upper left corner and choose an icon (eg in /usr/share/icons/gnome) | * to add an xterm launcher:\\ Name: xterm\\ Command\\ xterm -ls -sl 1000 -bg black -fg white\\ Click on the icon in the upper left corner and choose an icon (eg in /usr/share/icons/gnome) | ||
+ | ===== Dealing with weird and unforeseen problems ===== | ||
+ | |||
+ | ==== Accessing the Linux system messages and logs ==== | ||
+ | |||
+ | If something is not behaving as it should, it can be useful to check the system messages! | ||
+ | |||
+ | * **dmesg**: //print or control the kernel ring buffer//\\ ''dmesg -Hw'' | ||
+ | * ''sudo tail -f /var/log/messages'' | ||
+ | |||
+ | Once you have a bit **more technical information** about what's going on, it's easier to frame a price query for [[https://www.google.com|Google]] or search the [[https://forums.virtualbox.org/|VB forums]] | ||
+ | Example: [[https://forums.virtualbox.org/viewtopic.php?f=6&t=66086|Dealing with an unstable network connection after upgrading VB from 4.3.20 to 4.3.22]] | ||
===== Updating VB ===== | ===== Updating VB ===== |