root@eve-ng:/opt/unetlab/tmp/0/1a6ad409-bfd8-4d4a-98de-f85d84a5feab/52# ls
dev jail l1up_0 l1up_1 lib lib64 opt sys usr virtioa.qcow2
root@eve-ng:/opt/unetlab/tmp/0/1a6ad409-bfd8-4d4a-98de-f85d84a5feab/52# /opt/qemu/bin/qemu-img commit virtioa.qcow2
Co-routine re-entered recursively
Aborted (core dumped)
root@eve-ng:/opt/unetlab/tmp/0/1a6ad409-bfd8-4d4a-98de-f85d84a5feab/52#
I've restarted the whole eve-ng bare metal server same result.
5.0.1-106-PRO
Cannot created new base image , any thoughts ?
Moderator: mike
-
- Posts: 59
- Joined: Wed Feb 12, 2020 7:43 am
- Location: UK
- Contact:
-
- Posts: 5178
- Joined: Wed Mar 15, 2017 4:44 pm
- Location: London
- Contact:
Re: Cannot created new base image , any thoughts ?
use again:
cd /opt/unetlab/tmp/0/1a6ad409-bfd8-4d4a-98de-f85d84a5feab/52
and commit again
Sometimes happens if your path session is getting old and commit will not work, need redo path command again, even you are seems in correct location
cd /opt/unetlab/tmp/0/1a6ad409-bfd8-4d4a-98de-f85d84a5feab/52
and commit again
Sometimes happens if your path session is getting old and commit will not work, need redo path command again, even you are seems in correct location