How to Organize and Manage Virtual Machine Groups in Oracle VirtualBox

Learn how to create, rename, manage, and safely operate Oracle VirtualBox VM groups for labs, development stacks, and test environments.

A virtual machine (VM) is a software-defined computer managed by Oracle VirtualBox. When you work with several VMs, the VirtualBox Manager can become difficult to navigate. A VM group solves this organizational problem by displaying related VMs together and allowing selected lifecycle actions to be applied to the group.

This lesson explains how to create and manage groups, move VMs in or out of them, and safely start or stop several VMs together. The exact labels or toolbar locations can vary slightly between VirtualBox versions, but the basic workflow is the same.

What a VirtualBox VM Group Does

A VM group is a logical collection of existing virtual machines shown together in the VirtualBox Manager. For example, a group named Development Lab might contain a Linux application server, a database server, and a client VM.

Each member remains an independent VM. It keeps its own virtual disks, memory settings, virtual hardware, operating system, snapshots, and power state. A group does not merge the machines into one larger computer. Instead, it provides a convenient organizational relationship and a way to request certain actions for multiple members.

Feature	Purpose
VM group	Organizes existing VMs and supports selected collective lifecycle actions.
Clone	Creates a separate copy of a VM. Grouping does not duplicate anything.
Snapshot	Records a VM's state at a point in time so it can later be restored. A snapshot is not a group.
Shared folder	Provides a file-sharing mechanism between the host and a guest, or between supported guests. It does not organize VMs.
Virtual networking	Connects VMs through network modes such as NAT, bridged, host-only, or internal networking. It is separate from Manager organization.

Grouping also does not alter a VM's hardware configuration. After a VM is grouped, you can still start, stop, configure, snapshot, or rename that VM individually.

When VM Groups Are Useful

Lab environments: Keep a client, application server, database server, and directory or infrastructure server together.
Development stacks: Organize frontend, backend, database, and testing machines under one workload name.
Test systems: Separate machines used for a particular operating-system, application, or networking test.
Role-based collections: Group VMs by roles such as web servers, security testing, training, or administration.

Groups make navigation faster because a group can be collapsed when you do not need to see its members and expanded when you do. They also make coordinated work more convenient: you can select the group when beginning a lab session and use an appropriate group action when finishing.

For example, a Development Lab group could contain:

Linux application server: Runs the code under development.
Database server: Supplies the application's data service.
Client VM: Runs a browser or test client.

Creating a VM Group in VirtualBox Manager

There are several GUI methods for creating a group. Before using any method, open the VirtualBox Manager and make sure the VMs you want to organize are visible in the machine list.

Method 1: Use the Group command

Select one or more VMs in the Manager list.
Use the Manager's Group command. Depending on the VirtualBox version, this may appear on a toolbar, in a context menu, or under a menu associated with machine organization.
If the selected VMs are not already in a group, VirtualBox creates a group relationship and places the VMs beneath a group entry.
Give the group a descriptive name, such as Development Lab, Ubuntu Testing, or Web Stack.

If the command is unavailable, check that you selected VM entries rather than a non-VM item, and verify that the VMs are in a state that permits the requested organization operation.

Selecting adjacent and nonadjacent VMs

To select several consecutive entries, select the first VM and use the standard range-selection method for your host operating system, commonly holding Shift while selecting the last VM. The entire range is selected.

To select VMs that are separated in the list, use the standard multiple-selection method, commonly holding Ctrl on Windows or Linux, or Command on macOS, while selecting each entry. The exact key can depend on the host platform and VirtualBox interface.

Once the desired adjacent or nonadjacent VMs are selected, invoke the Group action. Review the selection before confirming so that an unrelated VM is not included.

Method 2: Drag one VM onto another

In the VirtualBox Manager list, click and hold one existing VM.
Drag it onto another VM entry.
Release the pointer when the Manager indicates that a grouping relationship can be created.
Expand the resulting group and confirm that both VMs appear beneath it.
Rename the group so it identifies the environment or workload rather than relying on an automatically chosen name.

This method is useful when you are organizing a small number of machines quickly. It creates a common grouping relationship; it does not clone either VM.

Understanding the Group Display

A group appears as a parent entry in the Manager's machine list. Its member VMs are displayed beneath it, usually with an indentation that shows the hierarchy. Select the group control to expand or collapse the member list.

If a VM seems to have disappeared after grouping, first expand the relevant group. The VM is normally still present as a member. A collapsed group can make the machine list appear shorter than expected.

Managing Group Membership

Moving an existing VM into a group

You can add an existing VM to a group without recreating it. Select the VM and use the Manager's Group command or the relevant context-menu option. Choose an existing group when the interface presents a group destination. In some versions, dragging the VM entry onto the target group is also available.

Adding a VM changes its organization in the Manager. It does not move the VM's files, change its virtual hardware, alter its network mode, or create a copy.

Removing a VM from a group

Expand the group.
Select the member VM that should no longer belong to it.
Use the command to remove or move the VM out of the group. The wording can vary by VirtualBox version.
Confirm that the VM appears as an individual entry in the Manager list.

Removing a VM from a group does not delete the VM. It remains registered with VirtualBox and can still be started, configured, renamed, or placed in another group.

Dissolving a group

To dissolve a group, use the group's organization or context-menu command to remove the group relationship. The member VMs should remain available as individual machines. Read the confirmation dialog carefully: dissolving a group is different from removing or deleting a VM.

Renaming a group

Select the group entry and use its rename command. Choose a name that describes the environment, project, workload, or test purpose, such as Development Lab, Customer Demo, or Network Test.

Changing the group name is not the same as changing an individual VM name. A group name labels the collection in the Manager; a VM name identifies one virtual machine. Renaming a group does not rename any of its members.

If you need to change a member's name, select that VM separately and use its individual rename workflow. You can also review how to change a virtual machine name.

Applying Actions to a VM Group

Select a group and open its lifecycle controls from the toolbar or context menu. A group action is a command requested for the VMs in that group. The action affects the member VMs individually; it never creates a combined VM.

Action	What happens to each VM	Typical use	Safety considerations
Start	Each powered-off member is booted or launched.	Begin work on a lab or development stack.	Check that the host has enough memory, CPU, and storage resources for all members.
Pause	Execution of each applicable running VM is temporarily suspended.	Temporarily free CPU time without ending the guest session.	Paused guests do not continue processing. Resume them before expecting services or network activity.
Reset	Each applicable VM is immediately restarted without a normal guest shutdown.	Recover a VM that is unresponsive when a normal shutdown is impossible.	Unsaved application data and filesystem activity can be lost. Treat it like pressing a physical reset button.
Save State	The current execution state of each applicable VM is saved so it can continue later.	End a session quickly while preserving open programs and the guest session.	State files consume host storage. For important services, a clean shutdown is usually preferable.
Shutdown	VirtualBox requests a normal operating-system shutdown in each guest, where supported.	Close a lab while allowing services and filesystems to stop cleanly.	Guest integration and suitable guest configuration may be required. Monitor members that do not respond.
Power Off	Each applicable VM stops immediately, as if power were removed.	Use only when a guest is frozen or a forced stop is necessary.	Can cause data loss, incomplete writes, filesystem checks, or service recovery problems.
Close	Opens the close workflow for selected VMs, commonly offering shutdown, save state, or power off choices.	Choose how to close a group at the end of a session.	Do not select a forced option without considering the state of every member.

Starting all members

Select the group and choose Start. VirtualBox requests startup for the member VMs that can be started. Startup timing can vary, and a machine that is already running, paused, or in another state may not respond in the same way as a powered-off machine.

For the Development Lab example, start the group when beginning work. After the members boot, verify that the database service is available before testing the application, and verify that the client can reach the application server.

Pausing, resetting, and saving state

Pause temporarily stops execution while preserving the current running session. It is useful for a short interruption, but paused servers do not process requests.

Reset immediately restarts a VM. It is an emergency-style operation, not a normal way to reboot a guest. Use the guest operating system's restart or shutdown command when possible.

Save State stores the current VM execution state. When the VM is started again, it can resume instead of performing a complete boot. This is convenient for interactive work, but cleanly shutting down an active server is generally safer and easier to reason about.

Closing or shutting down all members

Select the group and choose Close. Select the close behavior appropriate for the workload. For active systems, choose a normal guest shutdown when available. If you use Save State, understand that each guest resumes its previous session later rather than starting from a clean boot.

In a client, application-server, and database-server lab, dependencies may matter. Stop the client first, then the application server, and finally the database server if that order matches the design of your environment. Before shutting down, confirm that important services have stopped or that their data has been committed.

Safe VM Group Lifecycle Practices

Prefer a normal guest shutdown for servers and systems writing important data.
Use Save State for a convenient pause in interactive work when preserving the exact session is useful.
Use Reset only when a VM is unresponsive or a forced restart is specifically required.
Use Power Off only when graceful shutdown is unavailable or the guest must be stopped immediately.
Check each member's power state before applying a group action. A group can contain powered-off, running, paused, and saved-state VMs at the same time.
Consider service dependencies. For example, stop clients before application services and application services before databases when the workload requires that order.
Ensure the host has enough resources before starting a large group.

Practical Example: Create a Development Lab Group

Open VirtualBox Manager.
Locate the Linux application-server VM, database-server VM, and client VM.
Select all three machines. Use range selection if they are adjacent, or multiple selection if they are separated in the list.
Choose the Group action.
Name the new group Development Lab.
Expand the group and verify that all three intended members are beneath it.
When beginning work, select the group and choose Start.
When finished, stop the client, application, and database services in an appropriate order, then use the group close workflow and select a normal guest shutdown where possible.

If you only need a short interruption and want to preserve open guest sessions, Save State may be suitable. For a clean end to a development session, normal shutdown is usually the better choice.

Practical Example: Create a Group by Drag and Drop

In the Manager list, drag one existing VM entry onto another VM entry.
Release it when the interface shows that the entries can be grouped.
Expand the new group and verify the common grouping relationship.
Rename the group to identify its purpose, such as Web Stack Test.
Add other related VMs by moving them into the group with the Group command or an available drag-and-drop operation.

The result is still a set of separate VMs. Their disks, settings, snapshots, and guest operating systems remain independent.

Practical Example: Remove an Individual VM

Expand the test-environment group.
Select the VM that no longer belongs to the test environment.
Use the command to remove or move it out of the group.
Verify that the VM is listed independently.
Start or configure it individually to confirm that it remains usable.

This operation changes only the Manager organization. It does not delete the VM or its virtual disk. Be careful not to choose a separate remove or delete command when your intention is only to change group membership.

Groups Compared with Related VirtualBox Tasks

Use a group when you want organization and coordinated lifecycle control. Use a clone when you need a separate duplicate VM. Use snapshots when you need a recoverable point in a VM's history. Use shared folders or virtual networking when you need communication or file exchange.

Grouping does not:

Clone or duplicate a virtual machine.
Change CPU, memory, disk, network, or other virtual hardware settings.
Combine the member operating systems into one guest.
Automatically create a shared folder or network connection.
Make the member VMs dependent on a single combined runtime.

Troubleshooting VM Groups

I grouped a VM, but I intended to clone it

Grouping only organizes existing VMs. It does not create a second machine. If you need an independent duplicate, use the clone workflow. Use a group when you want to manage or display existing machines together.

A group shutdown did not behave the same way for every VM

Members can be in different power states, and guests may differ in their ability to respond to a graceful shutdown request. Review each VM's current state. Apply an action appropriate to the guest and workload, and handle any member that remains running individually.

Data or service state was lost after a group action

Reset or Power Off may have been used while guests were writing data. Prefer an orderly guest shutdown for active systems. Reserve forced actions for unresponsive VMs, and check services and filesystems after an interrupted stop.

I cannot find a VM after organizing groups

The VM may be nested beneath a collapsed group. Expand the group and verify its members. If the VM should be listed independently, remove it from the group and confirm that it appears at the top level of the Manager list.

Key Points to Remember

A VM group is a logical collection of independent VMs in VirtualBox Manager.
You can create a group with the Group command after selecting one or multiple VMs, or by dragging one VM onto another.
Adjacent VMs can be range-selected; nonadjacent VMs can be selected individually with the host platform's multiple-selection key.
You can rename a group, move VMs into it, remove members, or dissolve the group without deleting the VMs.
Group actions request Start, Pause, Reset, Save State, Shutdown, or Power Off for member VMs.
Normal guest shutdown is safer than Reset or Power Off for running services and important data.
Grouping is not cloning, snapshotting, shared-folder configuration, or virtual networking.