The Disk Management menus
As with much of computing, users will benefit from some basic understanding of English
However:
THIS PAGE IS INTENDED FOR PARALLEL TRANSLATION
Click here to GOOGLE AUTO-TRANSLATE THIS PAGE
Disk Snapshots
These webpages use a React sub-system. The contents lists, on the right, have problems with auto-translation >>
Where available, use these:
Top - - Disk Snapshots - - Create - - Delete - - Shared and Second drives - - Boot from ISO - - QF Disk Views - - Tidy and repair - - Other
[sc] create [sd] delete [sa] apply [sl] list > SNAPSHOTS
[sc] create
[sd] delete
[sa] apply
[sl] list
Create
Top - - Disk Snapshots - - Create - - Delete - - Shared and Second drives - - Boot from ISO - - QF Disk Views - - Tidy and repair - - Other
> sc
Shared Drive:
Snapshot list:
ID TAG VM SIZE DATE VM CLOCK ICOUNT
1 Oct07.08.42 0 B 2024-10-07 08:42:40 00:00:00.000 0
Health Status: Okay > No errors
Main Drive:
Snapshot list:
ID TAG VM SIZE DATE VM CLOCK ICOUNT
1 May18.15.41 0 B 2025-05-18 15:41:14 00:00:00.000 0
2 May18.15.57 0 B 2025-05-18 15:57:36 00:00:00.000 0
Health Status: Okay > No errors
SELECT: [enter] MAIN DRIVE (or back to main menu) [3] Shared Drive
>
Selected Drive = Main Drive
Shared Drive:
Snapshot list:
Health Status: Okay > No errors
Main Drive:
Snapshot list:
Health Status: Okay > No errors
SELECT:
[enter] MAIN DRIVE (or back to main menu)
[3] Shared Drive
Selected Drive = Main Drive
image: windows-11/disk.qcow2
file format: qcow2
virtual size: 128 GiB (137438953472 bytes)
disk size: 49.7 GiB
cluster_size: 65536
Snapshot list:
ID TAG VM SIZE DATE VM CLOCK ICOUNT
1 May18.15.41 0 B 2025-05-18 15:41:14 00:00:00.000 0
2 May18.15.57 0 B 2025-05-18 15:57:36 00:00:00.000 0
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: windows-11/disk.qcow2
protocol type: file
file length: 49.7 GiB (53386870784 bytes)
disk size: 49.7 GiB
Health Status: Okay (Main Drive) > No errors
IMPORTANT > For disk operations, the virtual machine must *not* be running & not started elsewhere.
[enter] Create snap with date.time title [text input] Create with text descriptor [b] back to main menu
IMPORTANT > For disk operations, the virtual machine must not be running & not started elsewhere.
[enter] Create snap with date.time title
[text input] Create with text descriptor
[b] back to main menu
Drive Updated ...
[enter] to return to menu [sd] delete older snaps
Drive Updated ...
[enter] to return to menu
[sd] delete older snaps
Delete
Top - - Disk Snapshots - - Create - - Delete - - Shared and Second drives - - Boot from ISO - - QF Disk Views - - Tidy and repair - - Other
IMPORTANT > For disk operations, the virtual machine must *not* be running & not started elsewhere.
qqX Snapshot Delete function
Main Drive (reselection & cancel prompts are given before starting)
ID Array Name
1 0 May18.15.41
2 1 May18.15.57
3 2 Aug17.15.21
Enter ARRAY number [0] to [2], either for individual snapshot, or for the start of snapshot range
or [full individual name] for difficult names only showing correctly in the FULL listing
or [enter] to return to main menu
IMPORTANT > For disk operations, the virtual machine must not be running & not started elsewhere.
qqX Snapshot Delete function
Main Drive (reselection & cancel prompts are given before starting)
ID
Array
Name
Enter ARRAY number [0] to [2], either for individual snapshot, or for the start of snapshot range
or [full individual name] for difficult names only showing correctly in the FULL listing
or [enter] to return to main menu
> 0
[enter] for an individual snapshot or to correct an error
Or ARRAY [number] for end of range (inclusive)
>
Delete = ARRAY entry 0
1 May18.15.41 0 B 2025-05-18 15:41:14 00:00:00.000 0
[enter] to delete [b] back to main menu (or reselect)
[enter] for an individual snapshot or to correct an error
Or ARRAY [number] for end of range (inclusive)
[enter]
Delete = ARRAY entry 0
[enter] to delete
[b] back to main menu (or reselect)
Deleting SnapShot 1 0 May18.15.41
image: windows-11/disk.qcow2
file format: qcow2
virtual size: 128 GiB (137438953472 bytes)
disk size: 48.1 GiB
cluster_size: 65536
Snapshot list:
ID TAG VM SIZE DATE VM CLOCK ICOUNT
2 May18.15.57 0 B 2025-05-18 15:57:36 00:00:00.000 0
3 Aug17.15.21 0 B 2025-08-17 15:21:17 00:00:00.000 0
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: windows-11/disk.qcow2
protocol type: file
file length: 49.7 GiB (53386936832 bytes)
disk size: 48.1 GiB
Initial Disk Size: 49.7 GiB - Space Saved: 1.6 GiB
[enter] to return to menu [sc] create new snap
Deleting SnapShot
Initial Disk Size: 49.7 GiB - Space Saved: 1.6 GiB
[enter] to return to menu
[sc] create new snap
Creating a Shared or Extra Drive
Top - - Disk Snapshots - - Shared and Second drives - - Boot from ISO - - QF Disk Views - - Tidy and repair - - Other
[2c] create [2d] delete a second virtual hard-drive [3c] create [3m] unmount shared drive (guest boot)
[2c] create
[2d] delete a second virtual hard-drive
[3c] create
[3m] unmount shared drive (guest boot)
> 2c
Create a SECOND virtual hard-drive for this VM instance:
Suggest 32G or higher, especially if expecting to create snapshots. Note that
qcow2 disks auto-compress & will normally occupy much less of your hard drive
than that allocated. An empty disk only takes up 70Mb when formatted.
It is easier make them larger now than to resize later ...
[enter] create 64G [integer] create int G [b] go back
Create a SECOND virtual hard-drive for this VM instance:
Suggest 32G or higher, especially if expecting to create snapshots. Note that
qcow2 disks auto-compress & will normally occupy much less of your hard drive
than that allocated. An empty disk only takes up 70Mb when formatted.
It is easier make them larger now than to resize later ...
[enter] create 64G
[integer] create int G
[b] go back
A Storage Drive will be created in the VM's folder
windows-11
[enter] to continue [b] to go back
>
The Created Drive should now be formatted from inside a VM:
Use Gparted or similar to set a device table and add partition(s)
Read notes in main settings if older MacOS or if Windows present.
If your new drives only have root access and your file manager won't change them,
the following commands can help give general user permissions:
sudo chown $USER:$USER "mounted-drive-name"
chmod 775 "mounted-drive-name"
[enter] to return
A Storage Drive will be created in the VM's folder
windows-11
[enter] to continue
[b] to go back
[enter]
The Created Drive should now be formatted from inside a VM:
Use Gparted or similar to set a device table and add partition(s)
Read notes in main settings if older MacOS or if Windows present.
If your new drives only have root access and your file manager won't change them, the following commands can help give general user permissions:
sudo chown $USER:$USER "mounted-drive-name" chmod 775 "mounted-drive-name"
[enter] to return
-
qqX will normally auto-install the Second Drive auto-mount parameters for you, via the .conf file.
-
Shared Drives will function and are installed in much the same way but will place the parameters in the general settings file.
Boot from or Mount ISO
Top - - Disk Snapshots - - Shared and Second drives - - Boot from ISO - - QF Disk Views - - Tidy and repair - - Other
[iso] mount iso to guest, allow boot or read from iso [bm] boot menu > allow guest efi/bios
[iso] mount iso to guest, allow boot or read from iso
[bm] boot menu > allow guest efi/bios
ISO formated disk images may be copied into the individual VM folder
A shared 'live boot' ISO can be added to the Shared Drive folder, if Shared Drive has been set up.
One or more may be added. If more than one, an ISO should be selected from the list.
Current Quickemu code is restricted to one only being mounted at a time.
To auto-mount an ISO when the VM is selected, set 'fixed_iso="VM_InstanceName/name.iso"' in the .conf file
A 'live boot' ISO such as from https://gparted.org/download.php is normally required for partition management.
Some iso's may not work as secondary boots, notably Kolibri.
Use [bm] main menu utility to toggle boot manager and ISO boot selection. Current status: (fastboot)
1) windows-11/unattended.iso
2) /media/xxx/Files/VMQs/SharedDrive/gparted-live-1.6.0-3-amd64.iso
3) /media/xxx/Files/VMQs/SharedDrive/ubuntu-22.04.2-desktop-amd64.iso
Currently, no ISO is mounted additionally to guest
[number] to select and mount/unmount [b] to go back
ISO formated disk images may be copied into the individual VM folder
A shared 'live boot' ISO can be added to the Shared Drive folder, if Shared Drive has been set up.
One or more may be added. If more than one, an ISO should be selected from the list.
Current Quickemu code is restricted to one only being mounted at a time.
To auto-mount an ISO when the VM is selected, set 'fixed_iso="VM_InstanceName/name.iso"' in the .conf file
A 'live boot' ISO such as from https://gparted.org/download.php is normally required for partition management.
Some iso's may not work as secondary boots, notably Kolibri.
Use [bm] main menu utility to toggle boot manager and ISO boot selection. Current status: (fastboot)
Currently, no ISO is mounted additionally to guest
[number] to select and mount/unmount
[b] to go back
[bm] > boot menu enabled (toggle)
[d] [s] start with ...
[bm] > boot menu enabled (toggle)
[d] or [s] > start with ...
> d
Press 'esc' when 'Start boot Option' appears ... to access the BIOS or boot an ISO,
Mounted ISO: Select 'Boot manager' and select 'QEMU DVD-ROM' from the list.
A 'live boot' ISO such as from https://gparted.org/download.php is normally required for disk management.
Current ISO/DVD: 'gparted-live-1.6.0-3-amd64.iso'
Use the qqX [iso] utility to select a specific bootable image file
[enter] to continue [b] to go back
Press 'esc' when 'Start boot Option' appears ... to access the BIOS or boot an ISO,
Mounted ISO: Select 'Boot manager' and select 'QEMU DVD-ROM' from the list.
A 'live boot' ISO such as from https://gparted.org/download.php is normally required for disk management.
Current ISO/DVD: 'gparted-live-1.6.0-3-amd64.iso'
Use the qqX [iso] utility to select a specific bootable image file
[enter] to continue
[b] to go back
QF Disk Mounting and Viewing
Top - - Disk Snapshots - - Shared and Second drives - - Boot from ISO - - QF Disk Views - - Tidy and repair - - Other
[qf]
File Manager Utility for mounting/unmounting and for connecting QCOW2 drives
This terminal window is PROCESS SEPARATED from qqX and may be LEFT OPEN, repositioned or minimized
The elevated permissions required to prepare the drives will remain isolated.
Any opening of new qqF windows will terminate other qqF instances that are running.
Run option 'qqf' from the qqX menu if the VM is swapped. Follow with [r] to refresh
Mounting of the connected drives is to be carried out as standard in the file-manager.
WINDOWS-11
Available Drive(s): Main Shared
Connected Drive(s):
Mounted Drive(s):
[1] Main Drive [2] Second Drive [3] Shared Drive [i] Input Drive [A] All Drives [a] all Non-Shared Drives
See main utilities for general disk tools and for disk creation
Selected = Shared Drive '/media/xxx/Files/VMQs/SharedDrive/shared.qcow2'
[enter] to change SHARED DRIVE connections or [option] for different selection
[r] to refresh vars [f] open drive in file-manager [h] help [q] to quit
File Manager Utility for mounting/unmounting and for connecting QCOW2 drives
This terminal window is PROCESS SEPARATED from qqX and may be LEFT OPEN, repositioned or minimized
The elevated permissions required to prepare the drives will remain isolated.
Any opening of new qqF windows will terminate other qqF instances that are running.
Run option 'qqf' from the qqX menu if the VM is swapped. Follow with [r] to refresh
Mounting of the connected drives is to be carried out as standard in the file-manager.
WINDOWS-11
Available Drive(s): Main Shared
Connected Drive(s):
Mounted Drive(s):
[1] Main Drive
[2] Second Drive
[3] Shared Drive
[i] Input Drive
[A] All Drives
[a] all Non-Shared Drives
See main utilities for general disk tools and for disk creation
Selected = Shared Drive '/media/xxx/Files/VMQs/SharedDrive/shared.qcow2'
[enter] to change SHARED DRIVE connections or
[option] for different selection
[r] to refresh vars
[f] open drive in file-manager
[h] help
[q] to quit
Disk Tidying and Repair
Top - - Disk Snapshots - - Shared and Second drives - - Boot from ISO - - QF Disk Views - - Tidy and repair - - Other
[disk]
Selected Drive = Main Drive
image: windows-11/disk.qcow2
file format: qcow2
virtual size: 128 GiB (137438953472 bytes)
disk size: 49.7 GiB
cluster_size: 65536
Snapshot list:
ID TAG VM SIZE DATE VM CLOCK ICOUNT
1 May18.15.41 0 B 2025-05-18 15:41:14 00:00:00.000 0
2 May18.15.57 0 B 2025-05-18 15:57:36 00:00:00.000 0
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: windows-11/disk.qcow2
protocol type: file
file length: 49.7 GiB (53386870784 bytes)
disk size: 49.7 GiB
Selected Drive = Main Drive
image: windows-11/disk.qcow2
file format: qcow2
virtual size: 128 GiB (137438953472 bytes)
disk size: 49.7 GiB
cluster_size: 65536
Snapshot list:
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: windows-11/disk.qcow2
protocol type: file
file length: 49.7 GiB (53386870784 bytes)
disk size: 49.7 GiB
Status: Okay > No errors
Theoretical Envelope: 128 GiB (137438953472 bytes) containing 49.7 GiB
Copy on Write and snapshots can sometimes make envelope size appear to be lower than the contents ...
File Length greater than Disk Size can cause size mis-reportage and indicate a need to tidy and compress
Small differences may be ignored and may later become self adjusted by Qemu background operations
Space required for creating a mandatory BACK-UP: 49.7G
Available disk space on host drive: 115G
Status: Okay > No errors
Theoretical Envelope: 128 GiB (137438953472 bytes) containing 49.7 GiB
Copy on Write and snapshots can sometimes make envelope size appear to be lower than the contents ...
File Length greater than Disk Size can cause size mis-reportage and indicate a need to tidy and compress
Small differences may be ignored and may later become self adjusted by Qemu background operations
Space required for creating a mandatory BACK-UP: 49.7G
Available disk space on host drive: 115G
[rd] reduce only - clear ALL snapshots, remove deleted files & tidy 'empty' space [rz] resize the envelope
The virtual machine should not be running & not started elsewhere
Backups may be easily renamed and reused as previously using the file manager
All snapshots and data will be SAFELY retained ... [b] return to main menu
>
[rd] reduce only - clear ALL snapshots, remove deleted files & tidy 'empty' space
[rz] resize the envelope
The virtual machine should not be running & not started elsewhere
Backups may be easily renamed and reused as previously using the file manager
All snapshots and data will be SAFELY retained ...
[b] return to main menu
Other possible messages
Top - - Disk Snapshots - - Shared and Second drives - - Boot from ISO - - QF Disk Views - - Tidy and repair - - Other
Standard repair uses multithreads. Use slow method if standard fails.
WARNING - Full repair may cause some data loss if there are damaged data clusters ...
WARNING - insufficient or very low space
[lk] basic leaks repair [LK] slow method
[full] attempt complex repair [FULL] slow method
VIRTUAL MACHINE ACTIVITY has been DETECTED
The virtual machine should not be running & not started elsewhere
ERROR moving drive to backup - Cancelling process
Attemping repair ....
Processing > monitor the hard drive activity light ...
ERROR: a NEW drive could not be created from the backup ??
Check the VM folder with a file manager - The backup may be renamed and reused as previously.
Standard repair uses multithreads. Use slow method if standard fails
WARNING - Full repair may cause some data loss if there are damaged data clusters ...
WARNING - insufficient or very low space
[lk] basic leaks repair
[LK] slow method
[full] attempt complex repair
[FULL] slow method
VIRTUAL MACHINE ACTIVITY has been DETECTED
The virtual machine should not be running and not started elsewhere
ERROR moving drive to backup - Cancelling process
Attemping repair ....
Processing > monitor the hard drive activity light ...
ERROR: a NEW drive could not be created from the backup ??
Check the VM folder with a file manager.
The backup may be renamed and reused as previously.