Posted on November 23, 2015 2:26 pm
 |  Asked by Roger Wilco
 |  1043 views
Tags:
RESOLVED
0
0
Print Friendly, PDF & Email
Marked as spam
0
Posted by Roger Wilco
Answered on November 23, 2015 8:44 pm

Huh. Look’s like trying to edit the post wiped out. Weird.

Anyway, my question changed a little. If I run vEOS-lab-4.15.2F from the CLI like this:

qemu-system-x86_64 -hda vEOS-lab-4.15.2F.vmdk -boot order=d -cdrom Aboot-veos-serial-2.0.8.iso -m 2048 -enable-kvm -netdev user,id=network0 -device e1000,netdev=network0 -serial telnet::3355,server,nowait

I can get the image booted, and can manipulate the management 1 interface. What I’m missing out on, is how to get E1 running in Qemu, so I can use that interface to get out onto the internet, to use yumdownloader to snag RPMs. If i do it via GSN3 (Cloud Object->Cisco NAT-> EOS switch), it’ll work, but is abysmally slow.

Any thoughts?

Marked as spam
0
Posted by Roger Wilco
Answered on December 2, 2015 12:48 pm

BTW, even though my configuration above will result on vEOS booting via Qemu outside GNS3, configuring Management 0 will give an error about ”ip routing not supported by this hardware”. What Qemu setup am I missing to get e1 online?

Post your Answer

You must be logged in to post an answer.