Posted on November 17, 2017 7:41 pm
 |  Asked by shuja naqvi
 |  1398 views
0
0
Print Friendly, PDF & Email

Hi Guys

I am running vEOS-lab-4.17.5M.vmdk as an IDE on virtual box version 5.0.0 r101573. The Aboot image is Aboot-veos-21.1.0.iso. the bootable drive has been set to IDE and i also tested it with setting it to Aboot image but when I load the VM it gives me the error  “Timeout waiting for /mnt/flash. The VM is FEDORA 64 BIT. My host system is windows 7 professional 64 bit.

0
Posted by Tamas Plugor
Answered on November 22, 2017 12:10 am

Hi Shuja,

Can you please try the following settings(this has worked for me):

OS: Linux Other 64-bit

vEOS-lab-4.17.5M.vmdk as IDE Primary Master

Aboot-veos-8.0.0.iso as IDE Primary Slave //We recommend the latest Aboot for newer EOS releases. I’ve tested it with Aboot 2.1 and it wasn’t working.

I’ve used Virtual Box Version 5.1.22 r115126 (Qt5.6.2) but it should work on your version too.

 

Thanks,

Tamas

I have the same issue,
My OS is 8.0
vmdk is 4.190F
I have correct IDE settings

and I get same error “Timeout waiting for /mnt/flash”

Let me know also what the fix is or will be?

Thanks

(Ashraf at December 9, 2017 5:18 am)
0
Posted by Tamas Plugor
Answered on December 12, 2017 10:19 pm

Hi Ashraf,

I’ve now tested it again on a Windows 10 machine and on macOS Sierra and have no issues. Can you share your settings? Here are mine:

Used image: vEOS-lab-4.19.0F.vmdk (IDE Primary Master)  <— Please make sure it is vEOS-lab and not EOS-

Bootloader: Aboot-veos-8.0.0.iso (IDE Secondary Master or IDE Primary Slave)

Make sure to allocate at least 2 GB of memory

I hope this helps. If you have the same settings you shouldn’t have any issues, let us know if you do!

Thanks,

Tamas

0
Posted by hiroshi nakamoto
Answered on June 15, 2018 1:05 am

scsi controle device delete on up

0
Answered on March 7, 2019 11:18 pm

Hi,
I have found this thread looking for help with my problem.
I’m running Win 10 Pro (1803) with Hyper-V installed. I’ve downloaded the most recent files:
– Aboot-veos-8.0.0.iso
– vEOS-lab-4.21.1.1F.vmdk
Checked SHA checksum – it’s correct.
Using guide available at https://eos.arista.com/veos-lab-on-hyper-v/ I’ve converted virtual disk to Hyper-V format. I did everything in details but still got “Timeout waiting for /mnt/flash” error. What’s more frustrating I’ve managed to run vEOS using the same set of files with VMWare Workstation Player without any problems.
Attached you will find my Hyper-V settings and error screen.
Please help!

Attachments:
0
Answered on March 11, 2019 8:45 am

Hi,
I have found this thread looking for help with my problem.
I’m running Win 10 Pro (1803) with Hyper-V installed. I’ve downloaded the most recent files:
– Aboot-veos-8.0.0.iso
– vEOS-lab-4.21.1.1F.vmdk
Checked SHA checksum – it’s correct.
Using guide available at https://eos.arista.com/veos-lab-on-hyper-v/ I’ve converted virtual disk to Hyper-V format. I did everything in details but still got “Timeout waiting for /mnt/flash” error. What’s more frustrating I’ve managed to run vEOS using the same set of files with VMWare Workstation Player without any problems.
Attached you will find my Hyper-V settings and error screen.
Please help!

0
Posted by René Ditlevsen
Answered on November 22, 2019 10:14 am

Hi folks.
For the record I stumbled upon this article as I was having issues with the vEOS LabRouter (found on https://www.arista.com/en/support/software-download under vEOS-lab) version 4.23.0.1F. I also tried 4.22.2.1F, which also failed.
My setup is a 6.5 vCenter, 6.5 ESXi host.
The VM was a 5.5, I tried the disk as both IDE0:0 and IDE0:1 with the Aboot ISO, but as I understand it from 4.20 and above, the VMDK is a combined (which I can confirm because even without the ISO I was able to boot into Aboot) disk.

I was also able to find that for the two mentioned versions (4.22.2.1F and 4.23.0.1F), the problem was the mounting part of the boot process which failed. I was able to mount /dev/sda2 in /mnt/flash and run boot /mnt/flash/vEOS(...), and succesfully boot EOS, but I was not able to understand/find the correct config in the Aboot OS to fix the issue.

So in short; If the above versions of vEOS-lab don't work for you; Get an earlier version.
4.19 worked for me.

Post your Answer

You must be logged in to post an answer.