If updates fail or nothing seems to work, your installation may have been corrupted.is lacking a base version, it needs to be retagged with trunk/distrib/retag_all.py" run update-labtainer.sh (from the labtainer-student directory) to update your distribution. If you see this error: " Remote image.When starting a new Labtainer, if you see an error such as "No JSON object could be decoded", try updating your installation (per above).The CyberCIEGE lab on VirtualBox running on OSX Catalina is not usable due to mouse problems as described here. ![]() ![]() If labs are unable to reach the Internet, e.g., to ping google, and you are connected to a VPN, try disconnecting the VPN.Resizing the window, or closing it (e.g., via Esc) and then reopening it will usually force the window to repaint. GUI windows may sometimes display as solid black boxes.Get updates by running update-labtainer.sh (These include fixes to student and instructor environments.).Ubuntu 22 and other recent Linux distributions having systemd 248 and later will not work with Labtainers.If it does not, you may need to reboot your VM. On the VM, an ls -l /tmp/.X11-unix should display a socket named "X0". If a GUIs fail to open (e.g., firefox or wireshark), and you see an error such as "cannot open display: :0", your X11 socket on the VM may have been corrupted.Yeah, that sounds stupid, but it often works. If a VirtualBox VM network becomes outrageously slow, power off the VM and change the network adaptor type in Settings / Networks / Advanced.You will need to change the file name back to ova before you can import the appliance. If you "opened" the download link rather than downloading the file, your computer may have changed the name of the file from.If your VM disk fills up, e.g., the "df" command shows Use of 100% on the root file system, you can reclaim space by deleting the current lab (or some other) from the labtainer-student directory: removelab.py (this will cause you to lose work). ![]() Ubuntu Package manager error (red stop symbol in upper right of desktop): If an Ubuntu VM reports package errors, try using the "sudo apt-get install -f" command and then reboot.When first starting a VM on Mac OSX, if the VM seems to freeze, i.e., you cannot type or click in the desktop: use preferences/security/unlock/privacy "Allow apps below to control your computer".sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli –start.sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli -stop.sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli -configure.Alternately, these commands often work from within a terminal on the Mac: If a VMWare virtual machine becomes unable to reach your network, this can usually be resolved by rebooting your system, e.g., your Mac.Make sure you have at least 30GB of disk on the drive hosting the "base folder". If VirtualBox fails to import the appliance, they give the same error code regardless of the reason (thanks Oracle!).If VMs will not boot, confirm you have enabled VT-x/AMD-v in your BIOS.Or, run bcdedit /set hypervisorlaunchtype off from an elevated command prompt. If you have trouble installing a 64-bit guest on VirtualBox on Windows 10, refer to this link:.Try using: "View" / "Autosize" / select "Autofit Guest". ![]()
0 Comments
Leave a Reply. |