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

Incorrect Qemu binary selected when importing template #3216

Closed
eantowne opened this issue Aug 6, 2021 · 1 comment
Closed

Incorrect Qemu binary selected when importing template #3216

eantowne opened this issue Aug 6, 2021 · 1 comment
Labels
Milestone

Comments

@eantowne
Copy link
Contributor

eantowne commented Aug 6, 2021

Describe the bug
When importing an appliance/template, if you have Qemu binaries with similar names to the binary defined in the template, the wrong binary may be selected by default.

GNS3 version and operating system (please complete the following information):

  • OS: Linux
  • GNS3 version: 2.2.23 (also was present in 2.2.22)
  • Any use of the GNS3 VM or remote server (ESXi, bare metal etc.): Bare-metal installed via PIP

To Reproduce
Steps to reproduce the behavior:

  1. Install Rust's cross compiling via cargo install cross
  2. Import template from server (IOSv)
  3. /usr/bin/qemu-system-x86_64-microvm (v5.2.0) is selected by default instead of /usr/bin/qemu-system-x86_64 (v5.2.0)

Screenshots or videos
If applicable, add screenshots (e.g. of the topology and/or error message) or links to videos to help explain the problem. This will help us a lot to quickly find the bug and fix it.

Screenshot from 2021-08-06 07-56-51

Additional context
My guess is that this finding the "first match" not an "exact match".

@grossmj
Copy link
Member

grossmj commented Aug 24, 2021

Fixed, thanks 👍

@grossmj grossmj closed this as completed Aug 24, 2021
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