-
Notifications
You must be signed in to change notification settings - Fork 662
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
Cannot launch Ubuntu 22.04 multipass on my Ubuntu 24.04 machine #3911
Comments
@sjg20
This is the command for starting the jammy instance. This implies that have launched an instance jammy and stopped it. Is that the case? By scanning your log.txt, I noticed
which points to |
Thanks for the response.
which is:
Perhaps the 'bind-dynamic' is a problem? |
@sjg20
|
After 'snap remove multipass':
Then I updated my 24.04 host with 'apt dist-upgrade' and rebooted! Then install it:
$ multipass launch 22.04 -vvv and it works! I'm not sure what was wrong. Thank you for your help! |
Hmm but it seems to be broken on my 24.04 laptop too. I filed an issue in case it helps:
took about 5 minutes If it is helpful I will keep this laptop in its current state in case you want to login and take a look. I'm going to remove and install multipass on the laptop.... Hmmm , that fixed it (snap remove multipass, snap install multipass), without any updates or a reboot. |
Describe the bug
I am trying to launch Ubuntu 22.04 multipass on my Ubuntu 24.04 machine. But I must be doing something horribly wrong as it just hangs.
To Reproduce
How, and what happened?
Expected behavior
I expect it to start quickly and give me a shell
Logs
log.txt
Additional info
OS: Ubuntu 24.04
CPU architecture or model: x86 (amd64)
multipass version
multipass 1.15.0
multipassd 1.15.0
multipass info
Name: jammy
State: Unknown
Snapshots: 0
IPv4: --
Release: --
Image hash: 610e1d37fe06 (Ubuntu 22.04 LTS)
CPU(s): --
Load: --
Disk usage: --
Memory usage: --
Mounts:
multipass get local.driver
qemu
Additional context
Add any other context about the problem here.
I tried to watch the network, but it seems there is no bootp server running. My local network has one on 192.168.4.1 but I'm not sure if multipass is trying to use that or its own?
sudo tcpdump -i mpqemubr0 -n udp port 67 and port 68
libibverbs: Warning: couldn't open config directory '/etc/libibverbs.d'.
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on mpqemubr0, link-type EN10MB (Ethernet), snapshot length 262144 bytes
14:01:02.405819 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 52:54:00:dd:a6:5b, length 277
14:01:06.181737 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 52:54:00:dd:a6:5b, length 277
14:01:13.543157 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 52:54:00:dd:a6:5b, length 277
14:01:28.836497 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 52:54:00:dd:a6:5b, length 277
14:02:01.535738 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 52:54:00:dd:a6:5b, length 277
The text was updated successfully, but these errors were encountered: