This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
other:vb:use [2015/01/12 10:04] jypeter More stop/start details |
other:vb:use [2015/02/23 14:16] jypeter Added the systemctl autofs commands |
||
---|---|---|---|
Line 47: | Line 47: | ||
===== Basic use of the VB ===== | ===== Basic use of the VB ===== | ||
+ | |||
+ | ==== Network problems ==== | ||
+ | |||
+ | If the host is correctly connected to the network, but you can't access the network from the VM and you get the following kind of ssh error message from the VM:\\ ''ssh user@machine''\\ ''ssh: Could not resolve hostname machine: Name or service not known | ||
+ | '' | ||
+ | |||
+ | 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'' | ||
Line 61: | Line 79: | ||
* 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 ===== |