Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't start a Qemu VM if I shutdown it from the OS #1898

Closed
Raizo62 opened this issue Mar 2, 2017 · 1 comment
Closed

Can't start a Qemu VM if I shutdown it from the OS #1898

Raizo62 opened this issue Mar 2, 2017 · 1 comment
Labels
Milestone

Comments

@Raizo62
Copy link

Raizo62 commented Mar 2, 2017

Hi

I create a template device Qemu with linux-tinycore-linux-6.4-2.img

  • Default name : TinyCore
  • qemu-system-x86_64
  • vnc mode

Then

  • On topology, i create 3 devices TinyCore connected to ethernet switch.
  • I start TinyCore-3
  • In vnc, i click on shutdown button in graphical interface of TinyCore-3
  • GNS3 seems to detect than TinyCore-3 is shutdown (red button)
  • I re-start TinyCore-3
  • I have this error message :
2017-03-02 08:03:19 ERROR node.py:446 error while starting TinyCore-3: Cannot send command 'bridge create QEMU-a5f15f07-f570-400b-9857-eeefc6b1afe9-0': uBridge is not running
2017-03-02 08:03:19 CRITICAL __init__.py:110 Cannot send command 'bridge create QEMU-a5f15f07-f570-400b-9857-eeefc6b1afe9-0': uBridge is not running
@julien-duponchelle julien-duponchelle added this to the 2.0 milestone Mar 2, 2017
@julien-duponchelle julien-duponchelle changed the title [2.0] Bug : Cannot send command 'bridge create...' Can't start a Qemu VM if I shutdown it from the OS Mar 2, 2017
julien-duponchelle added a commit to GNS3/gns3-server that referenced this issue Mar 3, 2017
@julien-duponchelle
Copy link
Contributor

Thanks it's fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants