Recent changes to VirtualMachine

VirtualMachine modified by Ulf Lorenz

Ulf Lorenz — Thu, 06 Jan 2022 21:43:06 -0000

--- v22
+++ v23
@@ -1,3 +1,9 @@
+**Note: As of version 0.3.4, this page is obsolete. Check out the file README_VirtualMachine in the root directory of WavePacket for the new and simpler workflow!**
+
+
+
+
+
 For documentation on the buildsystems prior to v7, see [here](VirtualMachine_v6) (and descend recursively if you need really older build systems).

 In simplistic terms, a virtual machine is a program that emulates a computer. On this virtual machine, you can then install another operating system (the guest). This document describes how to use a virtual machine to simplify the setup of a Wavepacket system. Everything needed to compile Wavepacket (or compile and run your programs that use the library) is done in the Linux guest system, then you can share data for easier manipulation with your "real" system (the host).

VirtualMachine modified by Ulf Lorenz

Ulf Lorenz — Tue, 28 Jul 2020 20:17:36 -0000

--- v21
+++ v22
@@ -35,6 +35,7 @@
     * Pick a tag or branch and make it the current one "git checkout <tag_or_branch_name>"
 9. Follow the normal instructions in the readme for compilation
     * "less README" lets you browse the readme; q exits the viewer
+        * Note: for the installation, you get admin privileges with "sudo make install" and entering the password again.
     * "less README.Python" explains the setup process for Python

 ## Optional steps ##

VirtualMachine modified by Ulf Lorenz

Ulf Lorenz — Tue, 28 Jul 2020 19:57:53 -0000

--- v20
+++ v21
@@ -28,7 +28,7 @@
 The script "prepareAll.sh" now installs all required programs for compilations. It upgrades the system and installs all required packages, downloads and installs CMake, downloads and compiles the tensor library, on which Wavepacket relies, and finally downloads the WavePacket git repository. Altogether, you should expect around 400 MB of downloaded data and a few minutes of waiting.

 7. Type "source .bashrc". The background is that prepareAll.sh added the downloaded CMake to the program path, but this only becomes valid after you open a new shell or reload this initialization file.
-7. Enter the Wavepacket directory "cd wavepacket"
+7. Enter the Wavepacket directory "cd src/wavepacket"
 8. Check which version (or branch) you want to compile
     * "git tag" lists all available tags (one for each release)
     * "git branch -r" lists all available development branches

VirtualMachine modified by Ulf Lorenz

Ulf Lorenz — Mon, 03 Feb 2020 19:36:50 -0000

--- v19
+++ v20
@@ -110,4 +110,4 @@
         * Type "startx" to start up the window manager
         * If this does not work, try to reboot "sudo reboot" and login again.
         (This should not be required in principle. Probably a packaging bug, but I did not follow up on this issue)
-    8 If you want to integrate the GUI into the host system seamlessly, you need to reinstall the VirtualBox guest utilities after you installed the graphical interfaces (I think).
+    * If you want to integrate the GUI into the host system seamlessly, you need to reinstall the VirtualBox guest utilities after you installed the graphical interfaces (I think).

VirtualMachine modified by Ulf Lorenz

Ulf Lorenz — Mon, 03 Feb 2020 19:35:15 -0000

--- v18
+++ v19
@@ -97,10 +97,9 @@
     * Switch to the "System" display
     * Now you can assign more memory and CPUs to the virtual machine if you need them. There are also lots of other settings, but they are probably less relevant.

-* You can upgrade the guest system programs (packages) or install some new ones.
+* You can install more packages if you want
     * Update the list of packages "apt update"
-    * You can upgrade the installed packages with "apt upgrade"
-    * Or you can install new packages
+    * install new packages
         * Use "apt search <keyword>" to search for packages by keyword
         * Use "apt show <packagename>" to get more detailed information
         * Use "sudo apt install <packagename>" to install new packages
</packagename></packagename></keyword>

VirtualMachine modified by Ulf Lorenz

Ulf Lorenz — Sat, 01 Feb 2020 14:44:23 -0000

--- v17
+++ v18
@@ -1,15 +1,15 @@
-For documentation on the buildsystems prior to v6, see [here](VirtualMachine_v5)
+For documentation on the buildsystems prior to v7, see [here](VirtualMachine_v6) (and descend recursively if you need really older build systems).

 In simplistic terms, a virtual machine is a program that emulates a computer. On this virtual machine, you can then install another operating system (the guest). This document describes how to use a virtual machine to simplify the setup of a Wavepacket system. Everything needed to compile Wavepacket (or compile and run your programs that use the library) is done in the Linux guest system, then you can share data for easier manipulation with your "real" system (the host).

-Note that compilation with a reasonably current build image should always work, no matter what. If you experience problems while following the instructions here, drop a note on the mailing list or per private mail, so that the issue is fixed (and your problem solved).
+Note that the build systems are usually linked to certain versions of Wavepacket. Compilation with the appropriate build image should always work, no matter what. If you experience problems while following the instructions here, drop a note on the mailing list or per private mail, so that the issue is fixed (and your problem solved).

 [TOC]

 ## Minimal instructions ##

 1. Download and install the VirtualBox emulation software  from http://www.virtualbox.org
-2. Download the image for the already prepared operating system from https://sourceforge.net/projects/cpp.wavepacket.p/files/Compilation%20images/. You need at least version 6 of the build system for the instructions on this page.
+2. Download the image for the already prepared operating system from https://sourceforge.net/projects/cpp.wavepacket.p/files/Compilation%20images/. You need at least version 7 of the build system for the instructions on this page.
 3. Start VirtualBox, select File / Import Appliance, and select the downloaded .ova image.
 4. Start the created virtual machine

@@ -25,8 +25,9 @@
 6. Start the preparation of everything by typing "bash prepareAll.sh". 
 7. When asked for a password, enter the user password. When asked for any decision, whatever you pick should be fine.

-The script "prepareAll.sh" now installs all required programs for compilations. It then downloads and compiles the tensor library, on which Wavepacket relies, and finally downloads the WavePacket git repository. Altogether, you should expect around 400 MB of downloaded data and a few minutes of waiting.
+The script "prepareAll.sh" now installs all required programs for compilations. It upgrades the system and installs all required packages, downloads and installs CMake, downloads and compiles the tensor library, on which Wavepacket relies, and finally downloads the WavePacket git repository. Altogether, you should expect around 400 MB of downloaded data and a few minutes of waiting.

+7. Type "source .bashrc". The background is that prepareAll.sh added the downloaded CMake to the program path, but this only becomes valid after you open a new shell or reload this initialization file.
 7. Enter the Wavepacket directory "cd wavepacket"
 8. Check which version (or branch) you want to compile
     * "git tag" lists all available tags (one for each release)
@@ -34,20 +35,27 @@
     * Pick a tag or branch and make it the current one "git checkout <tag_or_branch_name>"
 9. Follow the normal instructions in the readme for compilation
     * "less README" lets you browse the readme; q exits the viewer
-    * If you also want to install the python bindings, type "sudo apt install python-pip" (or python-pip3 if you want to do everything with python3). You then still need to download the requirements as documented in README.Python
-
+    * "less README.Python" explains the setup process for Python

 ## Optional steps ##

-1. Sharing a folder between guest and host system. That allows you to exchange data between the two.
+1. Installing the VirtualBox add-ons. These are required for sharing folders between guest and host or integrating the GUI seamlessly.
+    * When you have started the guest system, go to the menu and select "Devices / Insert Guest Additions CD Image"
+    * mount it "mount /media/cdrom"
+    * run the installation script "sudo bash /media/cdrom/VBoxLinuxAdditions.run"
+    * After typing your password, everything should be done automatically
+    * Restart the system for the add-ons to become active
+        * "sudo halt"
+        * Turn off the VM (if it does not stop on its own)
+        * start it again
+2. Sharing a folder between guest and host system. This allows you to exchange data between the two.
     * Create a directory on your host that will hold the shared content
     * Tell VirtualBox about this shared folder
         * In the VirtualBox GUI, right-click on the virtual machine, select "Settings"
         * Select "Shared Folders", add the created directory as shared folder with some name, say "my_share"
+        * the folder should be set to "permanent"
     * Tell the guest system about the shared folder
         * Create a new directory that later hosts the shared folder, say "sudo mkdir /mnt/shared".
-        * Reboot the system if you have not done so yet (we installed a new OS version, and the VirtualBox utils were compiled against that version)
-        "sudo reboot" and login again afterwards
         * You should now be able to mount the shared folder
             * "sudo mount -t vboxsf my_share /mnt/shared" should work without error
             * "ls /mnt/shared" should show you changes if you add/remove files from within the host system
@@ -70,6 +78,7 @@

 ## Trouble shooting / Problems ##

+* If your mouse is captured by the VM, pressing the system key (by default: Right Ctrl key) should release it.
 * If you manage to screw up the boot process (e.g., mistype something when setting up the shared folder below), there is no simple way to recover. Reason: I locked the root (/admin) account, but if there are problems with the boot process, the system wants to boot into the root account. Such a problem can be fixed, but that requires some deeper Linux/Unix skills.
 * I observed occasional black screens when rebooting. Probably something broken with the VM console display (?). If the screen is black when there should be a login screen, just type username and password blindly. After a successful login eveything is refreshed, and you see the console again.

@@ -102,3 +111,4 @@
         * Type "startx" to start up the window manager
         * If this does not work, try to reboot "sudo reboot" and login again.
         (This should not be required in principle. Probably a packaging bug, but I did not follow up on this issue)
+    8 If you want to integrate the GUI into the host system seamlessly, you need to reinstall the VirtualBox guest utilities after you installed the graphical interfaces (I think).

VirtualMachine modified by Ulf Lorenz

Ulf Lorenz — Sun, 28 Apr 2019 12:27:56 -0000

--- v16
+++ v17
@@ -34,6 +34,7 @@
     * Pick a tag or branch and make it the current one "git checkout <tag_or_branch_name>"
 9. Follow the normal instructions in the readme for compilation
     * "less README" lets you browse the readme; q exits the viewer
+    * If you also want to install the python bindings, type "sudo apt install python-pip" (or python-pip3 if you want to do everything with python3). You then still need to download the requirements as documented in README.Python

 ## Optional steps ##

VirtualMachine modified by Ulf Lorenz

Ulf Lorenz — Sun, 28 Apr 2019 11:51:57 -0000

--- v15
+++ v16
@@ -23,7 +23,7 @@
         * In the URLs with the form "ftp.de.\*", replace "de" by the country code where you are in (e.g., "ftp.dk.debian.org" for Danish). 
         * Save the changes ("Ctrl-x", "y", "Return")
 6. Start the preparation of everything by typing "bash prepareAll.sh". 
-7. When asked for a password, enter the user password
+7. When asked for a password, enter the user password. When asked for any decision, whatever you pick should be fine.

 The script "prepareAll.sh" now installs all required programs for compilations. It then downloads and compiles the tensor library, on which Wavepacket relies, and finally downloads the WavePacket git repository. Altogether, you should expect around 400 MB of downloaded data and a few minutes of waiting.

VirtualMachine modified by Ulf Lorenz

Ulf Lorenz — Sun, 28 Apr 2019 11:50:11 -0000

--- v14
+++ v15
@@ -31,7 +31,7 @@
 8. Check which version (or branch) you want to compile
     * "git tag" lists all available tags (one for each release)
     * "git branch -r" lists all available development branches
-    * Pick a tag or branch and make it the current one "git checkout <tag_or_branch_name>"
+    * Pick a tag or branch and make it the current one "git checkout <tag_or_branch_name>"
 9. Follow the normal instructions in the readme for compilation
     * "less README" lets you browse the readme; q exits the viewer

</tag_or_branch_name>

VirtualMachine modified by Ulf Lorenz

Ulf Lorenz — Thu, 08 Nov 2018 21:33:09 -0000

--- v13
+++ v14
@@ -64,17 +64,28 @@
 3. Changing the password
     * Type "passwd" and follow the instructions
 4. Power off the system
-    * Use "sudo halt" to stop the system, then turn the VM off or just save the state (one of the options when you close the VM).
+    * Close the VM window and select the option "Send shutdown signal".
+    * You could also type "sudo halt", then turn the VM off (the "Power off" option when you close the VM).
+
+## Trouble shooting / Problems ##
+
+* If you manage to screw up the boot process (e.g., mistype something when setting up the shared folder below), there is no simple way to recover. Reason: I locked the root (/admin) account, but if there are problems with the boot process, the system wants to boot into the root account. Such a problem can be fixed, but that requires some deeper Linux/Unix skills.
+* I observed occasional black screens when rebooting. Probably something broken with the VM console display (?). If the screen is black when there should be a login screen, just type username and password blindly. After a successful login eveything is refreshed, and you see the console again.

 ## Details of the system ##

-The system installed on the guest is a 64 bit Debian stretch. The hard disk file for the guest system can grow up to 20 GB, which should be enough for almost all purposes.
+The system installed on the guest is a 64 bit Debian stretch. By default, the virtual machine is set up with 1GB of RAM, one CPU and a 20 GB hard disk (written to a file)

 ## Where to go from here ##

 * If Linux and Command lines are completely new, study a basic tutorial. Chances are you will come across them again anyway in science contexts
     * For example https://ryanstutorials.net/linuxtutorial/
     * Or one of the various books on the subject Linux / Unix / Bash / Command line interface
+
+* You can change the VirtualMachine resources.
+    * Select "Machine / Settings"  in the VirtualBox menu
+    * Switch to the "System" display
+    * Now you can assign more memory and CPUs to the virtual machine if you need them. There are also lots of other settings, but they are probably less relevant.

 * You can upgrade the guest system programs (packages) or install some new ones.
     * Update the list of packages "apt update"
@@ -87,4 +98,6 @@
     * To get a window manager in the host
         * Install the "icewm" package (minimal window manager) or "kde-full" for a more Windows-like desktop
         * Install the "xinit" package to setup the graphical system
-        * Whenever you see a command-line interface, type "startx" to start up the window manager
+        * Type "startx" to start up the window manager
+        * If this does not work, try to reboot "sudo reboot" and login again.
+        (This should not be required in principle. Probably a packaging bug, but I did not follow up on this issue)