exos vm gns3 and virl

  • 0
  • 1
  • Question
  • Updated 2 years ago
  • Answered
how to get it working properly...

i have been attempting a number of different ways to implement the 16.1.2 vm in both gns3 and virl...

i have the most success at the command line with qemu

here is the procedure whereby i can get it to boot in a window at the cmd line:

make an image container

sudo qemu-img create -f qcow2 /var/lib/libvirt/images/exos_cmd.img 3G

add x86 config commands

sudo qemu-system-x86_64 -m 1024 -hda  /var/lib/libvirt/images/exos_cmd.img -cdrom /home/ccie/images/ios/exospc- -boot d

and this final command will get me to a login:

sudo qemu-system-x86_64  -hda   exos.img -cpu core2duo

i have been attempting a combination of virsh and virt-manager with little success... seems the hang up is with -cpu core2duo support in virt-manager. see my xml below:

<domain type='kvm' id='20'>
  <memory unit='KiB'>1048576</memory>
  <currentMemory unit='KiB'>1048576</currentMemory>
  <vcpu placement='static'>1</vcpu>
    <type arch='x86_64' machine='pc-i440fx-trusty'>hvm</type>
    <boot dev='cdrom'/>
    <boot dev='hd'/>
  <clock offset='utc'/>
    <disk type='file' device='disk'>
      <driver name='qemu' type='qcow2'/>
      <source file='/var/lib/libvirt/images/exos_cmd.img'/>
      <target dev='vda' bus='virtio'/>
      <alias name='virtio-disk0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/home/ccie/images/ios/exospc-'/>
      <target dev='hdc' bus='ide'/>
      <alias name='ide0-1-0'/>
      <address type='drive' controller='0' bus='1' target='0' unit='0'/>
    <controller type='usb' index='0'>
      <alias name='usb0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/>
    <controller type='pci' index='0' model='pci-root'>
      <alias name='pci.0'/>
    <controller type='ide' index='0'>
      <alias name='ide0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
    <interface type='bridge'>
      <mac address='52:54:00:a2:b8:15'/>
      <source bridge='br0'/>
      <target dev='vnet1'/>
      <model type='virtio'/>
      <alias name='net0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    <serial type='pty'>
      <source path='/dev/pts/10'/>
      <target port='0'/>
      <alias name='serial0'/>
    <console type='pty' tty='/dev/pts/10'>
      <source path='/dev/pts/10'/>
      <target type='serial' port='0'/>
      <alias name='serial0'/>
    <input type='mouse' bus='ps2'/>
    <input type='keyboard' bus='ps2'/>
    <graphics type='vnc' port='5901' autoport='yes' listen=''>
      <listen type='address' address=''/>
      <model type='cirrus' vram='9216' heads='1'/>
      <alias name='video0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    <memballoon model='virtio'>
      <alias name='balloon0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
  <seclabel type='dynamic' model='apparmor' relabel='yes'>

it seems i cannot pass the cpu command core2duo as an argument during runtime in virsh, nor in virt manager... in fact virt-manager errors out when i try to select core2duo complaining it is incompatible with host cpu (dual intel xeons, btw)

i understand that there are methods to pass cmd line args from qemu into virsh, although i have not had success with that yet...

if there is anyone who might have an idea how to proceed i'd appreciate it.. also anyone with any luck using UNL or VIRL..

i have vmware 12 ws pro that i will attempt making exos vm in, however i'd prefer to use kvm...

Photo of brian osgoiod

brian osgoiod

  • 170 Points 100 badge 2x thumb

Posted 2 years ago

  • 0
  • 1
Photo of Daniel Flouret

Daniel Flouret, Employee

  • 7,470 Points 5k badge 2x thumb

Please download one of these qcow2 images to use with qemu:
- v16.1.1.4: https://www.dropbox.com/s/0vkzfy3wgt3o7hb/EXOS-VM_v16.1.1.4-disk1.qcow2?dl=0
- v21.1.1.4: https://www.dropbox.com/s/9w5mh58uchoug6y/EXOS-VM_v21.1.1.4-disk1.qcow2?dl=0

Using those I created qemu VM's in GNS3 an the cli used by GNS3 is:

/usr/bin/qemu-system-i386 -name EXOS VM -m 256M -smp cpus=1
-enable-kvm -boot order=c -drive
-serial telnet:,server,nowait -monitor
tcp:,server,nowait -net none -device
rtl8139,mac=00:00:ab:fd:a4:00 -device rtl8139,mac=00:00:ab:fd:a4:01
-device rtl8139,mac=00:00:ab:fd:a4:02 -device
rtl8139,mac=00:00:ab:fd:a4:03 -device rtl8139,mac=00:00:ab:fd:a4:04
-device rtl8139,mac=00:00:ab:fd:a4:05 -device
rtl8139,mac=00:00:ab:fd:a4:06 -device rtl8139,mac=00:00:ab:fd:a4:07
-device rtl8139,mac=00:00:ab:fd:a4:08 -device
rtl8139,mac=00:00:ab:fd:a4:09 -device rtl8139,mac=00:00:ab:fd:a4:0a
-device rtl8139,mac=00:00:ab:fd:a4:0b -device
rtl8139,mac=00:00:ab:fd:a4:0c -nographic -cpu core2duo -nographic

Where it says
you should replace that with one of the two qcow2 images I've pointed you to. In this case, it was the v21.1.1.4.qcow2 image.

I guess you can drop all the -netdev entries, unless you want to specify the mac addresses of the different ports

I hope this helps you.