Template for vIOS

[jmfasha]

Newb here. I have a vmdk of IOSvL2 that works fine with GNS3 qemu. I moved it to the appropriate directory for eve (/opt/unetlab/addons/addons/qemu). Create a directory called vios and place the vmdk there. Then run qemu-img to convert it to qcow2 in that same directory. Then run the fixpermissions command. When I go to add a new node in my lab, all the templates are disabled/greyed-out. I have followed the instructions exactly and VT-x is enabled. Any help is appreciated. Also, I am running Eve-ng on a Server 2012 VM.

[ramindia]

Newb here. I have a vmdk of IOSvL2 that works fine with GNS3 qemu. I moved it to the appropriate directory for eve (/opt/unetlab/addons/addons/qemu). Create a directory called vios and place the vmdk there. Then run qemu-img to convert it to qcow2 in that same directory. Then run the fixpermissions command. When I go to add a new node in my lab, all the templates are disabled/greyed-out. I have followed the instructions exactly and VT-x is enabled. Any help is appreciated. Also, I am running Eve-ng on a Server 2012 VM.

If you converted good as per the documents mentioned, and you need to create a directly example: vios-adventerprisek9-m-15.4.3M , place the file in that folder and fix the permission. try test in test lab, add node vios and start the node.

it should work !

R!

[Uldis (UD)]

virtioa.qcow2

is correct image name inside vios dir

[jmfasha]

file is name virtioa.qcow2.

[jmfasha]

Newb here. I have a vmdk of IOSvL2 that works fine with GNS3 qemu. I moved it to the appropriate directory for eve (/opt/unetlab/addons/addons/qemu). Create a directory called vios and place the vmdk there. Then run qemu-img to convert it to qcow2 in that same directory. Then run the fixpermissions command. When I go to add a new node in my lab, all the templates are disabled/greyed-out. I have followed the instructions exactly and VT-x is enabled. Any help is appreciated. Also, I am running Eve-ng on a Server 2012 VM.

If you converted good as per the documents mentioned, and you need to create a directly example: vios-adventerprisek9-m-15.4.3M , place the file in that folder and fix the permission. try test in test lab, add node vios and start the node.

it should work !

R!

Can you elaborate on the "create a directly example" portion?

[Uldis (UD)]

It is given under how to section

[ramindia]

It is given under how to section

In the future will refer that how to.

R!

[itexlabs]

hi, have the same issue. So that means it's mandatory to name the file "virtioa.qcow2" ? it can't be named "some_name.qcow2" ?

[ramindia]

hi, have the same issue. So that means it's mandatory to name the file "virtioa.qcow2" ? it can't be named "some_name.qcow2" ?

Make it mandatory as per the guided.

R!