Quote from
jeff on July 28, 2018, 2:39 pm
This is probably overkill, but it worked.
- Your running systems are <systemname>.qcow2 files, or similar. You can find them by entering "ls /antlets/<systemname>" or "ls /hdd/<systemname>" as is appropriate.
- I cloned the system I wanted to move from my testing system to my production system (yes, I purchased two Antsle systems -- it was a great investment).
- Using the SFTP command, I copied the cloned .qcow2 file to my second server.
- Using the instructions to import a virtual machine (part of the regular documentation found on the main web site), I selected "Path" rather than drag-and-drop to create the template.
- Once the template was completed, I installed a new virtual machine on the production server using that template.
The process, for a 6gb system, took about 20 minutes.
Once the system was installed, I set up the new network addresses, system name, etc., in the /etc directory as appropriate.
This is probably overkill, but it worked.
- Your running systems are <systemname>.qcow2 files, or similar. You can find them by entering "ls /antlets/<systemname>" or "ls /hdd/<systemname>" as is appropriate.
- I cloned the system I wanted to move from my testing system to my production system (yes, I purchased two Antsle systems -- it was a great investment).
- Using the SFTP command, I copied the cloned .qcow2 file to my second server.
- Using the instructions to import a virtual machine (part of the regular documentation found on the main web site), I selected "Path" rather than drag-and-drop to create the template.
- Once the template was completed, I installed a new virtual machine on the production server using that template.
The process, for a 6gb system, took about 20 minutes.
Once the system was installed, I set up the new network addresses, system name, etc., in the /etc directory as appropriate.