Thanks, I'll make a note of that. Running on Windows 8 at present. Qemu creates stederr.txt and stdout.txt in the directory where the .exe resides (Windows specific) - I use these a lot for debugging too. One of the really annoying thing on the earlier Windows ports for Qemu/Pemu was the working directory being created somewhere in the user's temp directory structure. I discovered that this has changed in 0.8.4-RCx to be under the project working directory - great move! I can now find and manage those FLASH files much easier!

_________________
GNS3 0.8.4 running on Windows 8.1
GNS3 0.8.4 running on CentOS 6.5

This doesn't work for me with RC3 on Windows 8. I had to start it as qemuwrapper -n. Checked with netstat -p tcp and it's listening on 10525 tcp. When I start GNS3 and create a new ASA project I can see a connection to port 10525. Once I start the ASA this connection closes. I can't see qemu console listening on port 3001.

It all works perfectly from within GNS3, I can see the parameters when I hover over the ASA. And yes, I probably should try RC4 too...

_________________
GNS3 0.8.4 running on Windows 8.1
GNS3 0.8.4 running on CentOS 6.5

@ nickbeee
Curious. The output I posted was from Win8 (standard). All I did was:

Then started GNS3, added an ASA device and hit START.

You are correct, qemuwrapper listens on port 10525 by default [Trivia: it is port 10525 because, as Thomas Pani explained to me "The PIX 525 was highest model pemu emulated at that time, but we wanted an unprivileged port, 1525 is IANA registered, so 10525 seemed nice."]

In fact, you could even telnet to 127.0.0.1 10525 and issue some commands - if you knew what the commands were! Best to leave that to GNS3
Here's a couple of commands you could use:
qemu version
qemuwrapper close
qemuwrapper stop

See the source code for more.

_________________
RedNectar
http://rednectar.net
@rednectarchris
GNS3 WorkBench-a VMware image of Ubuntu with GNS3 and VPCS installed and a collection of exercises/labs

OK, I found my problem. If you run qemuwrapper.exe stand-alone it expects to find qemu.exe in the same directory or the later qemu-system-i386w.exe in a subdirectory qemu\ ...



I'm using the latter (1.5.0 Win64). Thanks for those pointers, I've grabbed the source code and compiled it.

I'm currently exploring options to get the console listening on other interfaces for console connections - it's only listening on 127.0.0.1. If I wanted to use a router in GNS3 as a console server then I would need to configure it to listen on, say, the MS loopback interface. If I run it outside GNS3 it listens on all interfaces by default but when called by GNS3 it's only listening on 127.0.0.1. Edit - found that in advenced settings -



Nick.

_________________
GNS3 0.8.4 running on Windows 8.1
GNS3 0.8.4 running on CentOS 6.5