Thanks claydon_dan for the integration of the new release into the PPA.
Now I have GNS3 0.8.7.1 with dynamips 0.2.13.1.

Everything seems to work fine, except with Qemu images: apparently, when I start a Qemu guest, the node interfaces turn green, the floating window indicates that the node is running, but nothing happens; I have no connection to that node; the CPU activity is flat, as if the node was actually not running.

This was working fine with the previous release.

_________________
A Collection of GNS3 Labs: https://learningnetwork.cisco.com/message/232820
i7 4700MQ quad-core 2.6 Ghz and 16 GB RAM
CCNA - CCDA
Beta Test Team
GNS3 0.8.6 on Windows 7 64 bits
GNS3 0.8.6 on Ubuntu 13.10 and Qemu 1.5.2
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

Hmm... I can't see any reason why that should be. Obviously I just take the source from github and package it.

Looking at the diff between 0.8.6 and 0.8.7 the only changes I can see that even mention Qemu are here: https://github.com/GNS3/gns3-legacy/commit/a110f9e but that doesn't look to me like it would cause any great problems.

Has your version of Qemu changed?

_________________
Daniel
Forum Moderator & Debian Package Maintainer for GNS3, Dynamips & VPCS.
Standalone DEB Packages are available from http://gns3.serverb.co.uk - To be updated!

Well, I think I have found the flaw, but it is very strange...

A while ago, I moved the vmdk image on my disk and changed the path to it inside the lab, but only at each node level ("Configure" menu), instead of changing the path at the "Edit -> Preferences -> Qemu -> Qemu Guest" level: my mistake.
However, when I look at the topology.net file, the image path under [QemuDevice] reflects the correct current path.
This should still work, right? But it doesn't and creates a "Zombie process":


Now, if I change the path under the Qemu guest definition with "Edit -> Preferences -> Qemu -> Qemu Guest", save it, and insert a new Qemu guest on the topology, start it, now the CPU reflects the load, and the node really starts.

It seems that what really matters is the general Qemu guest image path, instead of the specific node configuration...And hovering the mouse above the node says "Running" when it's not the case with the specific node configuration.
I think that state probing should be changed to reflect the real CPU usage of that particular node; there is one "qemu-system-x86_64" (64 bits) per running node with the CPU available. For example, with 2 nodes (the first process below has nothing to do with our discussion):

_________________
A Collection of GNS3 Labs: https://learningnetwork.cisco.com/message/232820
i7 4700MQ quad-core 2.6 Ghz and 16 GB RAM
CCNA - CCDA
Beta Test Team
GNS3 0.8.6 on Windows 7 64 bits
GNS3 0.8.6 on Ubuntu 13.10 and Qemu 1.5.2
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

I have edited previous post to show the creation of a zombie process.

_________________
A Collection of GNS3 Labs: https://learningnetwork.cisco.com/message/232820
i7 4700MQ quad-core 2.6 Ghz and 16 GB RAM
CCNA - CCDA
Beta Test Team
GNS3 0.8.6 on Windows 7 64 bits
GNS3 0.8.6 on Ubuntu 13.10 and Qemu 1.5.2
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

Hey claydon_dan,

I've posted a question about the upgrade of your PPA to Ubuntu utopic https://community.gns3.com/message/6736#6736
Regards.

_________________
A Collection of GNS3 Labs: https://learningnetwork.cisco.com/message/232820
i7 4700MQ quad-core 2.6 Ghz and 16 GB RAM
CCNA - CCDA
Beta Test Team
GNS3 0.8.6 on Windows 7 64 bits
GNS3 0.8.6 on Ubuntu 13.10 and Qemu 1.5.2
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@