Posted on November 6, 2015 12:42 pm
 |  Asked by Steven Wong
 |  831 views
Tags:
0
0
Print Friendly, PDF & Email

Hello all,

Recently I tried to install the vEOS on KVM/OpenStack.

In OpenStack, I created two images for Aboot and vEOS vmdk files. An instance is created with the Aboot image to get it loaded properly and the vEOS vmdk image is attached as a storage (Attached To vEOS 4.15.0F on /dev/vda).

Unfortunately, the instance loads and stopped with error in the attached screenshot.

It seems the Aboot image is unable to find the attached storage in order to load the EOS image.

Wondering if you experienced this and have a solution / workaround.

Thanks,
Steven

Attachments:
0
Posted by Juerg Gerber
Answered on November 12, 2015 10:12 am

Try using Interface IDE instad of virtio. VM sees the disk as /dev/hda with IDE.

Thanks Juerg. We finally got the 4.12 up and running but not the latest EOS version. Still trying to get the latest version up and running.

(Steven Wong at January 4, 2016 2:50 am)
0
Posted by Juerg Gerber
Answered on November 12, 2015 10:41 am

BTW: We are using vEOS on RHEV/ovirt

http://www.ovirt.org

 

Aboot-veos-2.1.0.iso is not working.

Aboot-veos-2.0.8.iso is working with KVM, ovirt, RHEV

 

Thanks for the tips. Will give it a try. However my goal is a bit challenging because we need to build an identical network same as production for managing the changes. That means all vEOS instances have to have 52 ports.

(Steven Wong at January 4, 2016 2:51 am)

Post your Answer

You must be logged in to post an answer.