Re: IOSXRv9000 - ether-channel / port-channel support on EVE-NG
Posted: Sun Jun 16, 2019 5:44 am
Hi
Thanks again.
Understand that all works on EVE-NG community edition.
But my questions was issue related image commit with "/opt/qemu/bin/qemu-img commit virtioa.qcow2" after 2nd reboot and it only seems to work on the 1st time/note when it runs and subsequent commit, does not work - see the error below. This behavior is very constant.
So my questions are as below and can you please answer the 2 questions to be clear:
1. Is this behavior present on Pro version and Community version?
2. Is there a solution to do this automatically, maybe via a script on Community edition?
root@eve-ng: /opt/unetlab/tmp/0/bb080b1c-9074-4c7a-a71a-fafdf5da0c84/1# /opt/qemu/bin/qemu-img commit virtioa.qcow2
Image committed.
root@eve-ng: /opt/unetlab/tmp/0/bb080b1c-9074-4c7a-a71a-fafdf5da0c84/1# /opt/qemu/bin/qemu-img commit virtioa.qcow2
Co-routine re-entered recursively
Aborted
root@eve-ng: /opt/unetlab/tmp/0/bb080b1c-9074-4c7a-a71a-fafdf5da0c84/2#
Mathew
Thanks again.
Understand that all works on EVE-NG community edition.
But my questions was issue related image commit with "/opt/qemu/bin/qemu-img commit virtioa.qcow2" after 2nd reboot and it only seems to work on the 1st time/note when it runs and subsequent commit, does not work - see the error below. This behavior is very constant.
So my questions are as below and can you please answer the 2 questions to be clear:
1. Is this behavior present on Pro version and Community version?
2. Is there a solution to do this automatically, maybe via a script on Community edition?
root@eve-ng: /opt/unetlab/tmp/0/bb080b1c-9074-4c7a-a71a-fafdf5da0c84/1# /opt/qemu/bin/qemu-img commit virtioa.qcow2
Image committed.
root@eve-ng: /opt/unetlab/tmp/0/bb080b1c-9074-4c7a-a71a-fafdf5da0c84/1# /opt/qemu/bin/qemu-img commit virtioa.qcow2
Co-routine re-entered recursively
Aborted
root@eve-ng: /opt/unetlab/tmp/0/bb080b1c-9074-4c7a-a71a-fafdf5da0c84/2#
Mathew