To run a previously encrypted Linux Mint host (now decrypted) in Virtual Machine Manager (virt-manager) on Debian 13 GNOME, follow these steps:

1. Prepare the Decrypted Disk for Use in a VM

Since you’ve already decrypted the partition using:

sudo cryptsetup open /dev/nvme0n1p5 linux_mint_encrypted

The decrypted partition is now accessible at /dev/mapper/linux_mint_encrypted.

Create a Disk Image for the VM

You need to create a raw disk image or QCOW2 file from the decrypted partition to use it in a VM.

Option A: Directly Use the Physical Partition (Advanced)

If you want to use the physical partition directly (not recommended for beginners):

• Ensure the partition is not mounted on the host.
• In virt-manager, when creating a new VM, select "Import existing disk image" and point to /dev/mapper/linux_mint_encrypted.

⚠️ Warning: This method can lead to data corruption if the host and VM try to access the partition simultaneously.

Option B: Create a Disk Image (Recommended)

Use dd or qemu-img to create a copy of the decrypted partition:

sudo dd if=/dev/mapper/linux_mint_encrypted of=~/linux_mint.img bs=4M status=progress

or (for QCOW2 format):

qemu-img convert -f raw -O qcow2 /dev/mapper/linux_mint_encrypted ~/linux_mint.qcow2

2. Set Up the VM in Virtual Machine Manager

1. Open Virtual Machine Manager:

   bash

   Copy

   sudo virt-manager

2. Create a New VM:

   • Click "Create a new virtual machine".
   • Select "Import existing disk image" and browse to the .img or .qcow2 file you created.
   • Choose "Linux" as the OS type and select the appropriate version (e.g., Linux Mint 21).
   • Allocate RAM and CPU resources (recommend at least 2GB RAM and 2 CPU cores for smooth performance).
   • Configure the firmware (UEFI or BIOS) to match the original system.

3. Adjust Boot Settings (If Needed):

   • If the original system used UEFI, ensure the VM is set to UEFI in the "Boot Options" section.
   • If the system was BIOS-based, select "BIOS" instead.

4. Start the VM:

   • Click "Finish" and start the VM.
   • If the VM fails to boot, check the boot order in the VM settings and ensure the disk is set as the primary boot device.

3. Post-Setup Configuration

• Networking: Ensure the VM has NAT or Bridged networking enabled in virt-manager (under "Virtual Hardware" > "NIC").

• Drivers: If the VM fails to boot due to missing drivers (e.g., for NVMe), you may need to:

  • Modify the VM’s libvirt XML to use IDE/SATA instead of NVMe (edit via virsh edit <vm-name>).
  • Or, install the required drivers in the VM after booting from a Live ISO.

• Graphics: If the VM has graphical issues, try enabling "Spice" or "VNC" for better video support.

4. Clean Up (After VM Creation)

Once the VM is working, you can close the decrypted partition on the host:

sudo cryptsetup close linux_mint_encrypted

Troubleshooting

Final Notes

• Backup your data before proceeding.
• If the original system used LVM, ensure the VM can detect the volume groups (sudo vgscan inside the VM).
• For UEFI systems, ensure the VM is configured with OVMF (UEFI support in QEMU/KVM).