try connecting something to the ASA, like a GNS3 switch, and then start the ASA.
If you still get the memory dump, open a linux terminal (try Ctrl+Alt+T from the Ubuntu desktop), run the following command:
Code:
ps aux | grep qemu
and post the results. When you are not running qemu, you should be getting an output very similar to this:
Code:
[email protected]:~$ ps aux | grep qemu
wizard 3353 0.0 0.0 13600 936 pts/0 S+ 19:46 0:00 grep --color=auto qemu
[email protected]:~$
if this is the only output you get, run GNS3, connect an ASA to a GNS3 switch, start the ASA, issue the ps aux command in the terminal and post the command's output.
another suggestion would be to try the following:
issue the following two commands into a terminal, and post the results here:
Code:
which qemu
which qemu-system-i386
and then issue the following command:
Code:
qemu-system-i386 -m 1024 -nographic -cpu coreduo -icount auto -hdachs 980,16,32 -kernel asa842-vmlinuz -initrd asa842-initrd.gz -append "ide_generic.probe_mask=0x01 ide_core.chs=0.0:980,16,32 auto nousb console=ttyS0,9600 bigphysarea=65536 ide1=noprobe no-hlt" -net nic,vlan=0 -net nic,vlan=1 -net nic,vlan=2 -net nic,vlan=3 -net nic,vlan=5 -net nic,vlan=6 -serial telnet::4444,server -writeconfig working.cfg
then telnet into localhost 4444 using the following command:
Code:
telnet 127.0.0.1 4444
and see whether you get a memory dump.
post any command output you get here, maybe we can figure out what's wrong
By the way, fyi
of the qemu executables, ASA uses qemu-system-i386.
a more general suggestion would be to try the troubleshooting steps/style and reporting style that i used in the thread at
topic8304.html
Login
FAQ
Search
