EECS Technical Database

User Tools

Site Tools

You are here: Technical Database » Departmental Services » EECSVM Service
Trace:
services:eecsvm

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
services:eecsvm [2025/02/25 15:41] – [Access Your EECS Home Directory From Inside Your VM] jasservices:eecsvm [2025/05/30 11:58] (current) – [VM Images] jas
Line 1: Line 1:
 ====== EECSVM Service ====== ====== EECSVM Service ======
  
-The EECSVM service allow students to use virtual machines required by courses they are taking.  The service is only available to students enrolled in those courses.+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.
  
-** IMPORTANT NOTE: During EECSVM test phase, please login to ea75-ea78 in remotelab for testing EECSVM service.  It is not yet available on all lab workstations.**+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]].
  
-Users will use [[https://www.virtualbox.org|VirtualBox]] to access virtual machines from either a **lab machine** (in Lassonde Building), or, remotely using a limited set of machines available in [[https://remotelab.eecs.yorku.ca|remotelab]] which are dedicated to EECSVM access.+These lab workstations support EECSVM service:
  
-The current machine configurations in Lassonde Building labs include:+^ Lab ^ Cores per Workstation ^ Memory ^ 
 +| LAS1002  | 6  | 16 GB | 
 +| LAS1002b | 6  | 16 GB | 
 +| LAS1004  | 16 | 32 GB | 
 +| LAS1006  | 12 | 32 GB | (*) 
 +| WSC105   | 6  | 16 GB |  
 +| WSC106   | 12 | 16 GB | 
 +| WSC108   | 12 | 16 GB |
  
-^  Lab     ^ Processor     ^ Cores                                  ^ Memory       ^ +(*) LAS1006 hosts (ea01-ea78) appear in remotelab, and can be used remotely.  These hosts are often used for labtest during the day, and remote sessions may be interrupted.  They may not be the best choice for remote access unless in the late evening, weekends, or holidays.
-| LAS1002  | Core i7-8700T | 6 cores                                | 16 GB memory | +
-| LAS1002b | Core i7-8700T | 6 cores                                | 16 GB memory | +
-| LAS1004  | Core i7-13700 | 8 performance cores, 8 efficient cores | 32 GB memory | +
-| LAS1006 (*) | Core i7-12700 | 8 performance cores, 4 efficient cores | 32 GB memory |+
  
-The advantage of relying on lab machines for CPU and memory is that as we upgrade lab machines, the EECSVM service will also be upgraded. In addition, if a course is holding a lab across multiple rooms, and there are many students who need to work on VMs simultaneously, then each student will have their own dedicated CPU cores and memory.+The following servers are available in remotelab for supporting remote use of the EECSVM service:
  
-**NOTE: Due to Microsoft restrictions, Windows VMs can only be used by students who are sitting at a lab seat, on campus, and not remotely.**+^ Server ^ Cores per Server ^ Memory ^ 
 +| rose    | 20 | 256 GB |  
 +| ruby    | 20 | 256 GB |  
 +| scarlet | 24 | 256 GB |
  
-(*) While the lab machines in LAS1006 are all available in remotelab, labtests could cause disruption to remote service.  The EECSVM service can be used on lab machines locally during course labs or when the lab is not in use.  It can can be used via remotelab in the late evening and weekend hours when no labtests are scheduled.  +**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 ===== ===== Check If You Have Access =====
Line 27: Line 33:
 <code> <code>
 % eecsvm access % eecsvm access
 +
 You have access to EECSVM service. 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 you're granted access.
 +
 +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.  
 +      
 ===== List Available Virtual Machines ===== ===== List Available Virtual Machines =====
  
Line 35: Line 47:
  
 <code> <code>
-% eecsvm list available +% eecsvm list vms
- +
-Available VMs To Install:+
  
 3482-w24-win10 3482-w24-win10
 4421 4421
 flarevm flarevm
-kali-linux-2024.4-virtualbox-amd64+kali-linux-2025.1c (alias: kali)
 metasploitable2 metasploitable2
-metasploitable3+metasploitable3-ubuntu14 
 +metasploitable3-win2k8
 SEED-Ubuntu20.04 SEED-Ubuntu20.04
-ubuntu-24.04.2-server+ubuntu-24.04.2-lts-server (alias: ubuntu) 
 +windows11 
 +</code> 
 + 
 +===== List Available Virtual Machine Bundles ===== 
 + 
 +If you are enrolled in a course to which multiple virtual machines will be installed, a VM bundle has likely already been created for the course.  A VM bundle allows you to install multiple virtual machines with specific installation options with a single command. 
 + 
 +To list available virtual machine bundles: 
 + 
 +<code> 
 +% eecsvm list bundles 
 + 
 +eecs3481-alomari: 
 + --netname secnet SEED-Ubuntu20.04 seed 
 + 
 +eecs3482-alomari: 
 + --netname secnet kali-linux-2025.1c kali 
 + --netname secnet SEED-Ubuntu20.04 seed 
 + --netname secnet metasploitable3-ubuntu14 
 + --netname secnet metasploitable3-win2k8
  
-Available VM Bundles To Install:+eecs3482-rts: 
 + --netname secnet kali-linux-2025.1c kali 
 + --netname secnet metasploitable3-ubuntu14 
 + --netname secnet windows11
  
-security1+eecs4484-alomari: 
 + --netname secnet SEED-Ubuntu20.04 seed 
 + --netname secnet flarevm
 </code> </code>
  
-Single VMs can be available (such as Ubuntu), or a VM bundle can be available (eg. "security1").  A VM bundle is just a way to install several VMs at once.+For example, you can see that the "eecs3482-alomari" bundle includes Kali Linux, SEED, and Metasploitable Ubuntu and Windows versions.
  
 ===== Install A Virtual Machine ===== ===== Install A Virtual Machine =====
Line 60: Line 96:
  
 <code> <code>
-% eecsvm install ubuntu-24.04.2-server +% eecsvm install ubuntu-24.04.2-lts-server 
-Installing ubuntu-24.04.2-server ... + 
-Virtual machine 'ubuntu-24.04.2-server' is created and registered. +ubuntu-24.04.2-lts-server VM: 
-UUID: f93a7c04-cc83-4956-936b-b9794f3a1b93 +Virtual machine 'ubuntu-24.04.2-lts-server' is created and registered. 
-Settings file: '/eecs/vm/user/jas/ubuntu-24.04.2-server/ubuntu-24.04.2-server.vbox'+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'
 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
-Medium created. UUID: 1040c942-aea6-4b48-bca4-07547f4a222e+Medium created. UUID: eebee866-d94d-4751-81ad-f538962e14be
 </code> </code>
  
-Ubuntu server is installed immediately.+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:
 +
 +<code>
 +% eecsvm install ubuntu
 +
 +ubuntu VM:
 +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'
 +0%...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 ===== ===== Installing a Virtual Machine Multiple Times =====
  
-If you need to install multiple copies of the same VM (say, 3 copies of Ubuntu), then you can give each install its own name:+If you need to install multiple copies of the same virtual machine (say, 3 copies of Ubuntu Server), then you can give each install its own name:
  
 <code> <code>
-% eecsvm install ubuntu-24.04.2-server ubuntu1 +% eecsvm install ubuntu ubuntu1 
-Installing ubuntu1 ...+ 
 +ubuntu VM:
 Virtual machine 'ubuntu1' is created and registered. Virtual machine 'ubuntu1' is created and registered.
-UUID: 53a44de9-3a68-488b-ad27-e73a365061bf+UUID: 8ccb442a-4e77-4b01-bf04-20573072de7e
 Settings file: '/eecs/vm/user/jas/ubuntu1/ubuntu1.vbox' Settings file: '/eecs/vm/user/jas/ubuntu1/ubuntu1.vbox'
 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
-Medium created. UUID: 05972878-a145-4b8d-bbc5-9ffa1c0492b6+Medium created. UUID: 354c50c3-d424-4582-881d-60fcd2623092
  
-% eecsvm install ubuntu-24.04.2-server ubuntu2 +% eecsvm install ubuntu ubuntu2 
-Installing ubuntu2 ...+ 
 +ubuntu VM:
 Virtual machine 'ubuntu2' is created and registered. Virtual machine 'ubuntu2' is created and registered.
-UUID: 7257af04-747d-4040-bbc2-d4c51e808300+UUID: ab673026-1ba9-4166-82b0-dcc7da5c35d0
 Settings file: '/eecs/vm/user/jas/ubuntu2/ubuntu2.vbox' Settings file: '/eecs/vm/user/jas/ubuntu2/ubuntu2.vbox'
 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
-Medium created. UUID: 66180e9a-f0c0-4dc3-bbc5-c17a1337e0cc+Medium created. UUID: 42d86496-d566-4f19-b8ab-68a42e07fdd6
  
-% eecsvm install ubuntu-24.04.2-server ubuntu3 +% eecsvm install ubuntu ubuntu3 
-Installing ubuntu3 ...+ 
 +ubuntu VM:
 Virtual machine 'ubuntu3' is created and registered. Virtual machine 'ubuntu3' is created and registered.
-UUID: 9d27ce5e-d2a9-4db0-b15e-720aaa896e45+UUID: 61aeaf0e-b0a7-4e17-9efc-702e312f1040
 Settings file: '/eecs/vm/user/jas/ubuntu3/ubuntu3.vbox' Settings file: '/eecs/vm/user/jas/ubuntu3/ubuntu3.vbox'
 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
-Medium created. UUID: 5b277adf-a72d-4bcd-92d9-1ba4249291a5+Medium created. UUID: e9456026-7214-4ed0-b7d2-4be551af7fa8 
 </code> </code>
  
-==== Optional Installation Options ====+==== Optional Virtual Machine Installation Options ====
  
-Other options which you can use when installing a vm with "eecsvm install" include:+Other options which you can use when installing a virtual machine with "eecsvm install" include:
  
-  * -f = force the install to overwrite a previous install +  * --force         Force install even if the VM is already installed. 
-  * --immutable = changes that you make to the VM will not be saved on exit +  * --immutable     Mark VM disk as immutable (changes thrown away on exit). 
-  * --netname "<network-name>" - All VMs with the same network name will share the same network, and can communicate.+  * --netname NAME  Attach the VM to VirtualBox network NAME. By default, each VM will only share the network with other instances of the same VM.  Using this option, you can install various VMs which will share the same private network. 
  
 For example, to overwrite a previous Ubuntu install, and to create an immutable VM which uses the network name "mynet": For example, to overwrite a previous Ubuntu install, and to create an immutable VM which uses the network name "mynet":
  
 <code> <code>
-% eecsvm install -f --immutable --netname mynet ubuntu-24.04.2-server ubuntu1 +% eecsvm install --force --immutable --netname mynet ubuntu ubuntu1 
-Installing ubuntu1 ...+ 
 +ubuntu VM:
 Virtual machine 'ubuntu1' is created and registered. Virtual machine 'ubuntu1' is created and registered.
-UUID: 69b51513-ef2e-4b40-99ec-24f88abe20e3 +UUID: 3565008e-f109-486a-b47d-dc6b4df96d66 
-Settings file: '/eecs/vm/user/cs911089/ubuntu1/ubuntu1.vbox'+Settings file: '/eecs/vm/user/jas/ubuntu1/ubuntu1.vbox'
 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
-Medium created. UUID: 16e12d00-4933-43c9-8eb0-53e1bb4106ad+Medium created. UUID: 34f31b21-f166-40c5-ae14-9a8b619ac5f8 
 +</code> 
 + 
 +If you haven't used --force, the the system would not have been able to re-install the VM since it is already installed: 
 + 
 +<code> 
 +% eecsvm install --immutable --netname mynet ubuntu ubuntu1 
 + 
 +ubuntu VM: 
 +error: VM ubuntu1 already exists.  Repeat install command and add --force to reinstall. 
 </code> </code>
  
 ===== Installing a Virtual Machine Bundle ===== ===== Installing a Virtual Machine Bundle =====
  
-To install a virtual machine bundle, pass the bundle name to the "eecsvm installbundle" command:+To install a virtual machine bundle, pass the bundle name to the "eecsvm installbundle" command.  For example, to install the eecs3482-alomari bundle:
  
 <code> <code>
-% eecsvm installbundle security1+% eecsvm installbundle eecs3482-alomari
  
-Installing bundle security1  ...+Installing bundle eecs3482-alomari  ...
  
-Installing kali ...+kali-linux-2025.1c VM:
 Virtual machine 'kali' is created and registered. Virtual machine 'kali' is created and registered.
-UUID: 282a38e4-3c50-44dc-8790-f9ee1f1fffbb+UUID: cbecf8ce-82d8-4a57-902b-fab703cba247
 Settings file: '/eecs/vm/user/jas/kali/kali.vbox' Settings file: '/eecs/vm/user/jas/kali/kali.vbox'
 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
-Medium created. UUID: e11d9fa2-b85e-4d8a-81ce-c490b31f1020+Medium created. UUID: fc52bb41-15d1-4e50-ae17-5bcfb3ffbf0a
  
-Installing metasploitable2 ... + 
-Virtual machine 'metasploitable2' is created and registered. +SEED-Ubuntu20.04 VM: 
-UUID: b0006681-f4be-4dd8-852e-c4f5f71a365e +Virtual machine 'seed' is created and registered. 
-Settings file: '/eecs/vm/user/jas/metasploitable2/metasploitable2.vbox'+UUID: 4bf8a938-5763-4a49-bb34-d0e11b0e9037 
 +Settings file: '/eecs/vm/user/jas/seed/seed.vbox'
 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
-Medium created. UUID: 53df409e-a87b-4cbe-ae31-f93ea3374208+Medium created. UUID: 44f7da66-2b92-4a46-8df2-89c05a067200
  
-Installing metasploitable3 ... + 
-Virtual machine 'metasploitable3' is created and registered. +metasploitable3-ubuntu14 VM: 
-UUID: 22565bc6-42e8-43ff-a034-0f058f578022 +Virtual machine 'metasploitable3-ubuntu14' is created and registered. 
-Settings file: '/eecs/vm/user/jas/metasploitable3/metasploitable3.vbox'+UUID: aa47dfd9-4d31-4a73-9a3f-528eb0e15de0 
 +Settings file: '/eecs/vm/user/jas/metasploitable3-ubuntu14/metasploitable3-ubuntu14.vbox'
 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
-Medium created. UUID: 265021f3-6245-42fa-bd9d-f12f75e1e289+Medium created. UUID: 38197c23-6888-4d5d-8663-fb67b36b98dd
  
-Installing seed ... + 
-Virtual machine 'seed' is created and registered. +metasploitable3-win2k8 VM: 
-UUID: 44e26de0-71a5-4e12-a653-9c83e0afe7a6 +Virtual machine 'metasploitable3-win2k8' is created and registered. 
-Settings file: '/eecs/vm/user/jas/seed/seed.vbox'+UUID: 8bdb8e93-fe59-40a9-a5be-f9217aece9ff 
 +Settings file: '/eecs/vm/user/jas/metasploitable3-win2k8/metasploitable3-win2k8.vbox'
 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
-Medium created. UUID: 3f81cfc4-2159-4010-bebe-f0190fdbd901+Medium created. UUID: 78655949-b181-40de-ae97-12e4eb8835b8 
 </code> </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.
  
 ===== Check Which Virtual Machines You Have Installed ===== ===== Check Which Virtual Machines You Have Installed =====
  
-To check which virtual machines that you you have installed:+To check which virtual machines that you have installed:
  
 <code> <code>
 % eecsvm list installed % eecsvm list installed
- 
-User installed VMs: 
  
 kali kali
-metasploitable2 +metasploitable3-ubuntu14 
-metasploitable3+metasploitable3-win2k8
 seed seed
 </code> </code>
Line 179: Line 248:
  
 <code> <code>
-% eecsvm delete ubuntu1 +% eecsvm delete kali 
-Deleting VM ubuntu1 ...+ 
 +Deleting VM kali ... 
 </code> </code>
  
 ===== Starting a Virtual Machine ===== ===== Starting a Virtual Machine =====
  
-To start a virtual machine, start the VirtualBox GUI using the "virtualbox" command, then click on the VM 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, 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:
  
 <code> <code>
Line 191: Line 262:
 </code> </code>
  
-You can also start the VM from the command line:+You can also start the virtual machine from the command line:
  
 <code> <code>
Line 203: Line 274:
 ===== Stopping A Virtual Machine ===== ===== Stopping A Virtual Machine =====
  
-You can stop a running virtual machine from the VirtualBox GUI.  Right-click on the VM in the left side of the display, and choose "Stop" then your shutdown option.  The VM will be shut down.+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.
  
-You can also shut down your VM from the command line:+You can also shut down your virtual machine from the command line:
  
 <code> <code>
-vboxmange controlvm kali shutdown+% vboxmange controlvm kali shutdown
 </code> </code>
  
Line 217: Line 288:
 <code> <code>
 % eecsvm quota % eecsvm quota
-Quota:  0.0 of 39062.5 MB used+ 
 +Quota: 98.1 of 195312.5 MB used 
 </code> </code>
  
-By default, you have a 40 GB storage quota.  When you install VMs, the original VM disk does not count toward your quota.  Only changes that you make to the VM count toward your quota.+By default, you have a 20 GB storage quota.  When you install VMs, the original VM disk does not count toward your quota.  For example, if you install an Ubuntu VM from the repository, it will take up very little of your space, no matter how big the default install is.  Anything you add to the VM will be counted toward your VM quota.  If you run out of space, you won't be able to get more, so please use your space wisely.
  
 ===== Reset Your EECSVM Environment ===== ===== Reset Your EECSVM Environment =====
  
-If you would like to clear your EECSVM storage, and VirtualBox settings, use the "eecsvm reset" command:+If you would like to clear your EECSVM storage, and VirtualBox settings, use the "eecsvm reset" command.  Please make sure you have exited VirtualBox:
  
 <code> <code>
 % eecsvm reset % eecsvm reset
  
-*** WARNING ***+************************* WARNING *************************
  
-This operation will delete ALL of your virtual machines, and  +This operation will delete ***ALL*** of your virtual machines, AND  
-VirtualBox configuration.  This operation is NOT recoverable.+your VirtualBox configuration.  This operation is NOT recoverable. 
 + 
 +Please ensure that VirtualBox is NOT running. 
 + 
 +Do you wish to proceed (YES/[no]) ?YES 
 + 
 +Deleting /cs/home/jas/.config/VirtualBox ... 
 +Deleting VMs ... 
 +Done
  
-Do you wish to proceed (YES/no) ?YES 
 </code> </code>
  
-===== Access Your EECS Home Directory From Inside Your VM =====+===== Access Your EECS Home Directory From Inside Your Virtual Machine =====
  
-Your EECS home directory is shared with certain VMs.  The method of accessing it will be different depending on the O/S:+Your EECS home directory can be shared with virtual machines.  The method of accessing it will vary depending on the O/S:
  
 **Linux** **Linux**
  
-With Linux, your EECS home directory will be available as:  /media/sf_homes+With Linux, your EECS home directory will be available as: /media/sf_homes
  
-NOTE: If you are setting up a new virtual machine, or adding additional users, you need to ensure that the user who is accessing the VM is in the vboxsf group to be able to access this folder:+NOTE: If you are setting up a new virtual machine, or adding additional users to an existing VM, you need to ensure that: 
  
-<code>+  * 1) The VirtualBox "Guest Additions" package is installed, and  
 +  * 2) The "vboxsf" group exists ("Virtualbox Shared Folder"). 
 +  * 3) the user who should be able to access your EECS home directory is in the vboxsf group.  You enter this command on the guest VM:<code>
 % sudo usermod -aG vboxsf $(whoami) % sudo usermod -aG vboxsf $(whoami)
 </code> </code>
Line 253: Line 335:
 **Windows** **Windows**
  
-If the share is available to a Windows VM, it can be mounted as \\vboxsrv\homes +  * 1) The VirtualBox "Guest Additions" package must be installed. 
- +  * 2) Your home directory is accessible as Windows share "\\vboxsrv\homes".
- +
  
 ===== Creating Your Own Virtual Machine ===== ===== Creating Your Own Virtual Machine =====
Line 265: Line 345:
  
 <code> <code>
-% eecsvm install ubuntu-24.04.2-server my-custom-ubuntu+% eecsvm install ubuntu my-custom-ubuntu 
 + 
 +ubuntu VM: 
 +Virtual machine 'my-custom-ubuntu' is created and registered. 
 +UUID: 6e317972-2718-46c8-aa9e-501cf8c1c5ba 
 +Settings file: '/eecs/vm/user/jas/my-custom-ubuntu/my-custom-ubuntu.vbox' 
 +0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% 
 +Medium created. UUID: 6ceff68d-d00a-44dd-958d-714085bcfeed 
 </code> </code>
  
-Next, modify the VM to include the required components.  For example, you could change the configuration of the VM, or install certain software.+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 machine, and let tech know.  We will create a disk image which consists of the original VM plus your changes, and make it available to all EECSVM users by cloning your VM disk into the EECSVM repository as follows:+When you're done testing, shut down the VM, and export the VM to tech:
  
 <code> <code>
-% eecsvm clone /eecs/vm/user/bob/my-custom-ubuntu/my-custom-ubuntu.vdi /eecs/vm/image/my-custom-ubuntu.vdi +% eecsvm export my-custom-ubuntu
-</code>+
  
-NOTE: Once users have started to use your new image, it cannot be changed.+Exporting my-custom-ubuntu (this will take some time) ... 
 +0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% 
 +Successfully exported 1 machine(s). 
 +Export success. 
 +</code>
  
-WARNING: While you can install a VM from an ISO image, if you do this, you are bound to use your quota entirely.  +This will automatically package up your VM, put it into a holding directory, and send an e-mail to tech to let them know that you've exported a VM.  It's a good idea to follow this up with an email to tech to let us know your intention.  Tech will then install your VM into the image repository, and make it available to all users of the EECSVM service.
  
-===== Clear VirtualBox Configuration =====+NOTE: Once a user has installed a VM from the repository, we can no longer change the base image.
  
-To clear your VirtualBox Configuration:+WARNING: While you can install a VM from an ISO image, if you do this, ALL of the disk usage will be counted in your VM quota, and you will likely run out of space.
  
 ===== Other Important Information About EECSVM Service ===== ===== Other Important Information About EECSVM Service =====
  
-  * Data is the EECSVM area is not backed up.  If you corrupt your disk image, you will have to start again.+  * Data in the EECSVM area is **not backed up**.  If you corrupt your VM disk image, you will need to start again. 
  
-  * VirtualBox will not monitor if you are running your VM simultaneously on multiple machines.  This will, however, cause data loss!  Always ensure that you exit VirtualBox, and shutdown your virtual machines when you're done.+  * 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 machine, check the [[https://www.eecs.yorku.ca/schedule/pcmode|pcmode schedule]] to ensure that the machine that you are using will not be rebooted into labtest while you are working.+  * 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.
  
-  * All supported VMs must run on the current VirtualBox version.  If the VM reports that it cannot be used with the latest VirtualBox, we won't be able to use it.+  * 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.
  
-  * The EECSVM service is intended for education students.  It is not intended for research whatsoever. +  * The EECSVM service is intended for **education** students.  This service is not intended for research purposes.  
  
-  * At the end of each term, ALL student storage on the EECSVM service will be cleared.+  * 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 likely find that they fill their storage space.  Additional quota for students is not available.+  * 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/|online documentation]].+  * For additional VirtualBox assistance, refer to the [[https://docs.oracle.com/en/virtualization/virtualbox/|VirtualBox online documentation]].
  
   * For more information on VirtualBox command line options, use command "vboxmanage".   * For more information on VirtualBox command line options, use command "vboxmanage".
  
-Here's information on the currently installed VMs for use with the EECSVM service:+Here's additional information on the currently installed VMs for use with the EECSVM service:
  
 ===== Currently Installed VMs ===== ===== Currently Installed VMs =====
Line 313: Line 404:
 |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|
-|kali-linux-2024.4-virtualbox-amd64|Kali Linux|u: kali, p: kali|+|flarevm|Windows 11 FlareVM with default packages|u: common, p: common| 
 +|kali-linux-2025.1c|Kali Linux|u: kali, p: kali|
 |metasploitable2|Metasploitable 2|u: mfsadmin, p: mfsadmin| |metasploitable2|Metasploitable 2|u: mfsadmin, p: mfsadmin|
-|metasploitable3|Metasploitable 3|u: vagrant, p: vagrant|+|metasploitable3-ubuntu14|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-server|Generic Ubuntu 24.04.2 Server VM|u: common, p: common| +|ubuntu-24.04.2-lts-server|Generic Ubuntu 24.04.2 LTS Server VM|u: common, p: common| 
-|flarevm|Windows 10 FlareVM with all packages|na|+|windows11|Generic Windows 11|u: common, p: common|
  
 ===== VM Bundles ===== ===== VM Bundles =====
  
 ^Name^Description^ ^Name^Description^
-|security1|Installs Kali, metasploitable2, metasploitable3, SEED, all at once on a shared private network.| +|eecs3481-alomari|SEED| 
 +|eecs3482-alomari|Kali, SEED, Metasploitable3 Ubuntu, Metasploitable3 Windows| 
 +|eecs3482-rts|Kali, Metasploitable3 Ubuntu, Windows 11| 
 +|eecs4484-alomari|SEED, FlareVM|
  
services/eecsvm.1740516097.txt.gz · Last modified: by jas