qemu disk image path
Posted: Sat Jul 28, 2018 7:47 am
How is relative path passed to qemu? only filename is passed to qemu, I wonder how qemu determines the path to find the file.
I ran into a issue where I have both veos- and veos-lab- folders in /opt/unetlab/addons/qemu. All images show up correctly in UI but qemu always uses hda.qcow2 in voes- folder, so the image selected in webui is not actually the version ran by qemu.
I named it veos-lab because Arista releases both veos vmdk and veos-lab vmdk. It looks like front panel ports don't work in VM with veos vmdk as noted in https://eos.arista.com/veos-running-eos-in-a-vm/
http://www.eve-ng.net/documentation/how ... ystem-veos
I ran into a issue where I have both veos- and veos-lab- folders in /opt/unetlab/addons/qemu. All images show up correctly in UI but qemu always uses hda.qcow2 in voes- folder, so the image selected in webui is not actually the version ran by qemu.
I named it veos-lab because Arista releases both veos vmdk and veos-lab vmdk. It looks like front panel ports don't work in VM with veos vmdk as noted in https://eos.arista.com/veos-running-eos-in-a-vm/
veos how to page can use an update. It looks like combined vmdk is now supported so no need to use aboot any moreAt this point, official EOS releases do not support running in an EOS VM with front panel interfaces. A couple of minor changes were required support front-panel interfaces. These changes will eventually make it back to an official release, at which point you will once again be able to run the exact same image on your switch as on your VM.
http://www.eve-ng.net/documentation/how ... ystem-veos