Differences

This shows you the differences between two versions of the page.

--- services:eecsvm [2025/05/30 11:54] – [Install A Virtual Machine] jas
+++ services:eecsvm [2025/10/09 10:24] (current) – [VM Images] jas
@@ Line 1: / Line 1: @@
 ====== EECSVM Service ======
-The EECSVM service allows students to use virtual machines required by courses they are taking.  The service is only available to students enrolled in courses requiring this service, and the respective faculty.  Once a course completes, the student VMs will deleted to ensure there is enough space for use the next term.
+The EECSVM service allows students to use virtual machines required by courses they are taking.  The service is only available to students enrolled in courses requiring this service, and the respective faculty and TAs.  Once a course completes, students and TAs will lose access to the service.  Faculty who are using the service for their courses will retain access, but **all storage will be cleared between terms**.
 Users will use [[https://www.virtualbox.org|VirtualBox]] to access virtual machines from either a lab workstation, or, remotely using a set of servers available in [[https://remotelab.eecs.yorku.ca|remotelab]].
@@ Line 21: / Line 21: @@
 ^ Server ^ Cores per Server ^ Memory ^
-| rose    | 20 | 256 GB |
+| ruby    | 24 cores, 48 threads | 256 GB |
-| ruby    | 20 | 256 GB |
+| rose    | 28 cores, 56 threads | 512 GB |
-| scarlet | 24 | 256 GB |
+| scarlet | 28 cores, 56 threads | 768 GB |
-**NOTE: Due to Microsoft restrictions, Windows VMs must only be used by students who are sitting at a workstation **in a lab** on campus.  You must not use Windows VMs remotely.  Please respect this policy.**
+**NOTE: Due to Microsoft restrictions, Windows VMs must only be used by students who are sitting at a workstation in a lab on campus.  You must not use Windows VMs remotely.  Please respect this policy.**
 ===== Check If You Have Access =====
@@ Line 33: / Line 33: @@
 <code>
 % eecsvm access
 You have access to EECSVM service.
+</code>
-</code>
+If you see, "You do not have access to EECSVM service.", then you are not enrolled in a course to which access has been granted.  You can email tech if you have any questions.  If you have just enrolled in a course, it make take up to 24 hours before access is granted.
-If you see, "You do not have access to EECSVM service.", then you are not enrolled in a course to which access has been granted.  You can email tech if you have any questions.  If you have just enrolled in a course, it make take up to 24 hours before you're granted access.
+If you see the following error, then you are attempting to use the EECSVM service from from a system which is not in the above list of workstations or servers:
-If you see, "EECSVM service is not available on this system.", then you are trying to access EECSVM service from a system which is not in the above list of workstations or servers.
+<code>
+EECSVM service is not available on this system.
+Please view this webpage to see where you can access the EECSVM service:
+https://wiki.eecs.yorku.ca/dept/tdb/services:eecsvm
+</code>
 ===== List Available Virtual Machines =====
@@ Line 48: / Line 52: @@
 <code>
 % eecsvm list vms
 -w24-win10
 flarevm
-kali-linux-2025.1c (alias: kali)
+kali-linux-2025.1c (alias: @kali)
 metasploitable2
 metasploitable3-ubuntu14
 metasploitable3-win2k8
 SEED-Ubuntu20.04
-ubuntu-24.04.2-lts-server (alias: ubuntu)
+ubuntu-24.04.2-lts-server (alias: @ubuntu)
 windows11
 </code>
@@ Line 69: / Line 72: @@
 <code>
 % eecsvm list bundles
 eecs3481-alomari:
  --netname secnet SEED-Ubuntu20.04 seed
 eecs3482-alomari:
  --netname secnet kali-linux-2025.1c kali
@@ Line 78: / Line 79: @@
  --netname secnet metasploitable3-ubuntu14
  --netname secnet metasploitable3-win2k8
+...
-eecs3482-rts:
- --netname secnet kali-linux-2025.1c kali
- --netname secnet metasploitable3-ubuntu14
- --netname secnet windows11
-eecs4484-alomari:
- --netname secnet SEED-Ubuntu20.04 seed
- --netname secnet flarevm
 </code>
@@ Line 96: / Line 89: @@
 <code>
-% eecsvm install ubuntu-24.04.2-lts-server
+% eecsvm install ubuntu-24.04.3-lts-server
+ubuntu-24.04.3-lts-server VM:
-ubuntu-24.04.2-lts-server VM:
+Virtual machine 'ubuntu-24.04.3-lts-server' is created and registered.
-Virtual machine 'ubuntu-24.04.2-lts-server' is created and registered.
 UUID: 3d9d73f1-f655-453a-8555-aa38f84fd350
-Settings file: '/eecs/vm/user/jas/ubuntu-24.04.2-lts-server/ubuntu-24.04.2-lts-server.vbox'
+Settings file: '/eecs/vm/user/jas/ubuntu-24.04.3-lts-server/ubuntu-24.04.3-lts-server.vbox'
 %...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
 Medium created. UUID: eebee866-d94d-4751-81ad-f538962e14be
@@ Line 108: / Line 100: @@
 Ubuntu server is installed immediately.  It takes very little time.
-In the listing of available VMs, you can see that ubuntu-24.04.2-lts-server is also aliased to just "ubuntu".  This means you can install it like this as well:
+In the listing of available VMs, you can see that ubuntu-24.04.3-lts-server is also aliased to just "@ubuntu".  This means you can install it like this as well:
 <code>
-% eecsvm install ubuntu
+% eecsvm install @ubuntu
+@ubuntu VM:
-ubuntu VM:
+Virtual machine 'ubuntu-24.04.3-lts-server' is created and registered.
-Virtual machine 'ubuntu-24.04.2-lts-server' is created and registered.
 UUID: 69d452a3-d2d5-4f93-98ac-65c6ce921884
 Settings file: '/eecs/vm/user/jas/ubuntu-24.04.2-lts-server/ubuntu-24.04.2-lts-server.vbox'
 %...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
 Medium created. UUID: 5e33e04b-53c2-4e60-b17b-0669b9a390dc
 </code>
 ===== Installing a Virtual Machine Multiple Times =====
@@ Line 126: / Line 117: @@
 <code>
-% eecsvm install ubuntu ubuntu1
+% eecsvm install @ubuntu ubuntu1
+@ubuntu VM:
-ubuntu VM:
 Virtual machine 'ubuntu1' is created and registered.
 UUID: 8ccb442a-4e77-4b01-bf04-20573072de7e
@@ Line 134: / Line 124: @@
 %...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
 Medium created. UUID: 354c50c3-d424-4582-881d-60fcd2623092
+% eecsvm install @ubuntu ubuntu2
-% eecsvm install ubuntu ubuntu2
+@ubuntu VM:
-ubuntu VM:
 Virtual machine 'ubuntu2' is created and registered.
 UUID: ab673026-1ba9-4166-82b0-dcc7da5c35d0
@@ Line 143: / Line 131: @@
 %...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
 Medium created. UUID: 42d86496-d566-4f19-b8ab-68a42e07fdd6
+% eecsvm install @ubuntu ubuntu3
-% eecsvm install ubuntu ubuntu3
+@ubuntu VM:
-ubuntu VM:
 Virtual machine 'ubuntu3' is created and registered.
 UUID: 61aeaf0e-b0a7-4e17-9efc-702e312f1040
@@ Line 152: / Line 138: @@
 %...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
 Medium created. UUID: e9456026-7214-4ed0-b7d2-4be551af7fa8
 </code>
@@ Line 166: / Line 151: @@
 <code>
-% eecsvm install --force --immutable --netname mynet ubuntu ubuntu1
+% eecsvm install --force --immutable --netname mynet @ubuntu ubuntu1
+@ubuntu VM:
-ubuntu VM:
 Virtual machine 'ubuntu1' is created and registered.
 UUID: 3565008e-f109-486a-b47d-dc6b4df96d66
@@ Line 179: / Line 163: @@
 <code>
-% eecsvm install --immutable --netname mynet ubuntu ubuntu1
+% eecsvm install --immutable --netname mynet @ubuntu ubuntu1
+@ubuntu VM:
-ubuntu VM:
 error: VM ubuntu1 already exists.  Repeat install command and add --force to reinstall.
 </code>
@@ Line 191: / Line 173: @@
 <code>
-% eecsvm installbundle eecs3482-alomari
+ % eecsvm installbundle eecs3482-alomari
 Installing bundle eecs3482-alomari  ...
+Processing install --netname secnet @kali kali:
-kali-linux-2025.1c VM:
+@kali VM:
 Virtual machine 'kali' is created and registered.
-UUID: cbecf8ce-82d8-4a57-902b-fab703cba247
+UUID: af129284-d005-44d1-9aa3-7131715aff61
 Settings file: '/eecs/vm/user/jas/kali/kali.vbox'
 %...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
-Medium created. UUID: fc52bb41-15d1-4e50-ae17-5bcfb3ffbf0a
+Medium created. UUID: 28924d4e-1f5f-45ba-8943-f2a846f40ec6
+Processing install --netname secnet SEED-Ubuntu20.04 seed:
 SEED-Ubuntu20.04 VM:
 Virtual machine 'seed' is created and registered.
-UUID: 4bf8a938-5763-4a49-bb34-d0e11b0e9037
+UUID: 1bd49822-7659-4453-8202-54ec1eb727b8
 Settings file: '/eecs/vm/user/jas/seed/seed.vbox'
 %...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
-Medium created. UUID: 44f7da66-2b92-4a46-8df2-89c05a067200
+Medium created. UUID: 94bb4f2b-adc6-42dd-8d2d-a22a9a4289a7
+Processing install --netname secnet metasploitable3-ubuntu14:
 metasploitable3-ubuntu14 VM:
 Virtual machine 'metasploitable3-ubuntu14' is created and registered.
-UUID: aa47dfd9-4d31-4a73-9a3f-528eb0e15de0
+UUID: ac4d5677-59b0-42a4-aa8e-5d0b51e9335f
 Settings file: '/eecs/vm/user/jas/metasploitable3-ubuntu14/metasploitable3-ubuntu14.vbox'
 %...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
-Medium created. UUID: 38197c23-6888-4d5d-8663-fb67b36b98dd
+Medium created. UUID: 4bf81283-1a79-43f8-bb26-f4362c3457e6
+Processing install --netname secnet metasploitable3-win2k8:
 metasploitable3-win2k8 VM:
 Virtual machine 'metasploitable3-win2k8' is created and registered.
-UUID: 8bdb8e93-fe59-40a9-a5be-f9217aece9ff
+UUID: a10d10de-5e73-429f-a012-1bf16c89e936
 Settings file: '/eecs/vm/user/jas/metasploitable3-win2k8/metasploitable3-win2k8.vbox'
 %...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
-Medium created. UUID: 78655949-b181-40de-ae97-12e4eb8835b8
+Medium created. UUID: be6e3f0b-3c0d-4227-8838-69b5f498c4f7
 </code>
-Here, we can see that several virtual machines were installed: Kali, SEED, and Metasploitable3 Windows, and Ubuntu versions.  What you don't see here is that they are all configured to use the shared network "secnet", so all of these VMs will share a private network, 10.0.2.0/24.
+Here, we can see that several virtual machines were installed: Kali, SEED, and Metasploitable3 Windows, and Ubuntu versions.  We can see they are installed using a shared network "secnet", so all of the VMs will share a private network, 10.0.2.0/24.
 ===== Check Which Virtual Machines You Have Installed =====
-To check which virtual machines that you have installed:
+To check which virtual machines you have installed:
 <code>
 % eecsvm list installed
 kali
 metasploitable3-ubuntu14
@@ Line 249: / Line 225: @@
 <code>
 % eecsvm delete kali
 Deleting VM kali ...
 </code>
 ===== Starting a Virtual Machine =====
-To start a virtual machine, start the VirtualBox GUI using the "virtualbox" command, then click on the virtual machine on the left side of the display (underneath the VM name it will say: "Powered Off"), then click "Start" on the right side of the display:
+To start a virtual machine:
 <code>
-% virtualbox
+% eecsvm start kali
+Waiting for VM "kali" to power on...
+VM "kali" has been successfully started.
 </code>
-You can also start the virtual machine from the command line:
+The virtual machine starts, and you see the VM output in a separate window.
+If you want to start the VM in the background (AKA headless), do it like this:
 <code>
-% vboxmanage startvm kali
+% eecsvm start kali --headless
 Waiting for VM "kali" to power on...
 VM "kali" has been successfully started.
 </code>
-**WARNING:** On some older O/S, the VirtualBox guest additions do not work.  In these cases, when you click on the VM window, your mouse will be locked to that window, and you will not be able to exit it unless you hit the right CTRL key on your keyboard.
+Since EECSVM is a wrapper for VirtualBox, you can also start VMs in the VirtualBox GUI.  Start VirtualBox by using the "virtualbox" command from a terminal, or by selecting the Activities menu, then searching for "virtualbox".
+**WARNING:** On some older O/S, the VirtualBox Guest Additions do not work.  In these cases, when you click on the VM window, your mouse will be locked to that window, and you will not be able to exit it unless you hit the right CTRL key on your keyboard.
 ===== Stopping A Virtual Machine =====
-You can stop a running virtual machine from the VirtualBox GUI.  Right-click on the virtual machine in the left side of the display, and choose "Stop" then your shutdown option.  The VM will be shut down.
+To stop a virtual machine (issue an O/S shutdown):
-You can also shut down your virtual machine from the command line:
+<code>
+% eecsvm stop kali
+Stop sent to VM "kali".
+</code>
+The virtual machine shuts down.
+You can also shutdown VMs in the VirtualBox GUI.  Right-click on the virtual machine in the left side of the display, and choose "Stop" then your shutdown option.  The VM will be shut down.
+===== SSH Access =====
+If your VM is running VirtualBox Guest Additions, and an SSH server, then you can SSH to it from the EECS system where you are running the VM.
+For example, if "kali" VM is started, and running an SSH server (which it does not run by default):
 <code>
-vboxmange controlvm kali shutdown
+% eecsvm ssh kali
+ssh into the VM kali with: ssh <user>@localhost -p 26600
+% ssh kali@localhost -p 26600
+The authenticity of host '[localhost]:26600 ([127.0.0.1]:26600)' can't be established.
+ED25519 key fingerprint is SHA256:i3EHIF7IDsuyQ9pwOf/FAXEVG+dNzxbK5MZB3/yj0Qg.
+This key is not known by any other names.
+Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
+Warning: Permanently added '[localhost]:26600' (ED25519) to the list of known hosts.
+kali@localhost's password:
+Linux kali 6.12.13-amd64 #1 SMP PREEMPT_DYNAMIC Kali 6.12.13-1kali1 (2025-02-11) x86_64
+The programs included with the Kali GNU/Linux system are free software;
+the exact distribution terms for each program are described in the
+individual files in /usr/share/doc/*/copyright.
+Kali GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
+permitted by applicable law.
+┌──(kali㉿kali)-[~]
+└─$
 </code>
+NOTE: Every time you run the "eecsvm ssh" command, the system reconfigures SSH access to the VM, so a new port may be used.
+NOTE: As most VMs have well documented username and password, if you are enabling SSH access on a VM, please make sure that you've changed the username or password on your local VM copy.  Otherwise, another student could connect to your running VM.
 ===== Check Your Virtual Machine Storage Quota =====
@@ Line 288: / Line 303: @@
 <code>
 % eecsvm quota
 Quota: 98.1 of 195312.5 MB used
 </code>
@@ Line 301: / Line 314: @@
 <code>
 % eecsvm reset
+************************* WARNING ******************************************
-************************* WARNING *************************
 This operation will delete ***ALL*** of your virtual machines, AND
 your VirtualBox configuration.  This operation is NOT recoverable.
-Please ensure that VirtualBox is NOT running.
+Please ensure that VirtualBox and your VMs are not running on any system.
 Do you wish to proceed (YES/[no]) ?YES
 Deleting /cs/home/jas/.config/VirtualBox ...
 Deleting VMs ...
 Done
 </code>
@@ Line 345: / Line 355: @@
 <code>
-% eecsvm install ubuntu my-custom-ubuntu
+% eecsvm install @ubuntu my-custom-ubuntu
+@ubuntu VM:
-ubuntu VM:
 Virtual machine 'my-custom-ubuntu' is created and registered.
 UUID: 6e317972-2718-46c8-aa9e-501cf8c1c5ba
@@ Line 353: / Line 362: @@
 %...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
 Medium created. UUID: 6ceff68d-d00a-44dd-958d-714085bcfeed
 </code>
-Next, start the VM, and all the required components.  For example, you could change the system configuration of the VM, or install software packages.
+Next, start the VM, and make any required adjustments.  For example, you could install various software packages, and configure the VM in custom ways.
 When you're done testing, shut down the VM, and export the VM to tech:
@@ Line 362: / Line 370: @@
 <code>
 % eecsvm export my-custom-ubuntu
 Exporting my-custom-ubuntu (this will take some time) ...
 %...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
@@ Line 381: / Line 388: @@
   * VirtualBox will not monitor if you are running your VM simultaneously on multiple machines.  If you do this, it **will** cause corruption and data loss and you will lose your work and need to start over.  Always ensure that you shutdown your virtual machines cleanly, and exit VirtualBox whenever you are done.
-  * If you're using a lab workstation, please check the [[https://www.eecs.yorku.ca/schedule/pcmode|pcmode schedule]] to ensure that the workstation that you choose will not be rebooted into labtest while you are working.  This will interrupt your session, and could corrupt your VM.
+  * If you're using a lab workstation, please check the [[https://www.eecs.yorku.ca/schedule/pcmode|pcmode schedule]] to ensure that the workstation that you choose will not be rebooted into labtest while you are working.  This will interrupt your session, and could corrupt your VMs.
   * All supported VMs must run on the current VirtualBox version.  If the VM reports that it cannot be used with the latest VirtualBox version, we won't be able to use it.
@@ Line 389: / Line 396: @@
   * At the end of each term, ALL student storage on the EECSVM service will be **deleted** without notice.  Once this happens, the data is not recoverable.  Please ensure that you've backed up your data before the start of the next term.
-  * Each user can choose which VMs they install in their storage space.  Users who install VMs from ISOs will find that they run out of disk space. Additional quota for students is not available. Likewise, since installation of updates will consume your quota, it is not recommended to install updates unless necessary.
+  * Each user can choose which VMs they install in their storage space.  Users who install VMs from ISOs will find that they run out of disk space. Additional quota for students is not available. Likewise, since installation of updates will consume your quota, **it is not recommended to install updates unless necessary**.
   * For additional VirtualBox assistance, refer to the [[https://docs.oracle.com/en/virtualization/virtualbox/|VirtualBox online documentation]].
@@ Line 401: / Line 408: @@
 ===== VM Images =====
-^Name^Description^Username/Password^
+^Name^Alias^Description^Username/Password^
-|3482-w24-win10|3482 Winter 24 Windows 10 VM|na|
+|3482-w24-win10| |3482 Winter 24 Windows 10 VM|na|
-|4421|4421 VM|na|
+|4421| |4421 VM|na|
-|flarevm|Windows 11 FlareVM with default packages|u: common, p: common|
+|flarevm| |Windows 11 FlareVM with default packages|u: common, p: common|
-|kali-linux-2025.1c||Kali Linux|u: kali, p: kali|
+|kali-linux-2025.2|@kali|Kali Linux|u: kali, p: kali|
-|metasploitable2|Metasploitable 2|u: mfsadmin, p: mfsadmin|
+|metasploitable2| |Metasploitable 2|u: mfsadmin, p: mfsadmin|
-|metasploitable3-ubuntu14|Metasploitable 3|u: vagrant, p: vagrant|
+|metasploitable3-ubuntu14| |Metasploitable 3|u: vagrant, p: vagrant|
-|metasploitable3-win2k|Metasploitable 3|u: vagrant, p: vagrant|
+|metasploitable3-win2k| |Metasploitable 3|u: vagrant, p: vagrant|
-|SEED-Ubuntu20.04|SEED|u: seed, p: dees|
+|SEED-Ubuntu20.04| |SEED|u: seed, p: dees|
-|ubuntu-24.04.2-lts-server|Generic Ubuntu 24.04.2 LTS Server VM|u: common, p: common|
+|ubuntu-24.04.3-lts-server|@ubuntu|Generic Ubuntu 24.04.3 LTS Server VM|u: common, p: common|
-|windows11|Generic Windows 11|u: common, p: common|
+|windows11| |Generic Windows 11|u: common, p: common|
 ===== VM Bundles =====
@@ Line 420: / Line 427: @@
 |eecs3482-rts|Kali, Metasploitable3 Ubuntu, Windows 11|
 |eecs4484-alomari|SEED, FlareVM|
+|eecs6446-hkh|3 x Ubuntu LTS VMs|
+**NOTE: Due to Microsoft restrictions, Windows VMs must only be used by students who are sitting at a workstation in a lab on campus. You must not use Windows VMs remotely. Please respect this policy.**