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

instances do not start: crashed program qemu-system-x86_64 #2354

Closed
ShinobiX9X opened this issue Nov 24, 2021 · 3 comments
Closed

instances do not start: crashed program qemu-system-x86_64 #2354

ShinobiX9X opened this issue Nov 24, 2021 · 3 comments
Labels

Comments

@ShinobiX9X
Copy link

Describe the bug
Launching an instance hangs: timed out waiting for response
Starting that instance gives error

To Reproduce
How, and what happened?

  1. multipass start foo
  2. [2021-11-24T17:18:57.155] [error] [foo] process error occurred Crashed program: qemu-system-x86_64; error: Process crashed [2021-11-24T17:18:57.156] [error] [foo] error: program: qemu-system-x86_64; error: Process crashed start failed: cannot connect to the multipass socket Please ensure multipassd is running and '/var/snap/multipass/common/multipass_socket' is accessible

Expected behavior
What did you expect to happen?
Start the instance without an error

Logs
see attached file
multipass.multipassd.logs.txt

Additional info

  • OS: Arch Linux (kernel 5.15.4-arch1-1)
  • multipass(d) 1.8.0
  • Name: foo State: Stopped IPv4: -- Release: -- Image hash: 91740d72ffff (Ubuntu 20.04 LTS) Load: -- Disk usage: -- Memory usage: -- Mounts: --
@ShinobiX9X ShinobiX9X added the bug label Nov 24, 2021
@Saviq
Copy link
Collaborator

Saviq commented Nov 24, 2021

Hi @ShinobiX9X, is that all the logs that you got? There's nothing in the logs about the instance being launched / started.

Can you try a fresh multipass launch -vvvv?

@ShinobiX9X
Copy link
Author

Hello, was quick
multipass launch -vvv:
multipass.launch-vvv.txt
and then snap logs multipass.multipassd
multipass.multipassd.logs.txt

thank you

@Saviq
Copy link
Collaborator

Saviq commented Nov 24, 2021

Oh so no crash now. @ShinobiX9X do you have a firewall enabled? You need to let traffic on mpqemubr0 through. Have a look at #1448 and possibly #1236 for some more details.

I'll close this for now, will reopen if you find it's not that.

@Saviq Saviq closed this as completed Nov 24, 2021
@Saviq Saviq added invalid and removed bug labels Nov 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