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/01/19 16:43] jypeter Section about LSCE disk mounting problems |
||
---|---|---|---|
Line 48: | Line 48: | ||
===== 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! | ||
===== Some useful things to configure ===== | ===== Some useful things to configure ===== |