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

Cannot install/run multipass on Windows 10 unable to set driver to hyperv #3763

Open
brucejo75 opened this issue Nov 1, 2024 · 7 comments
Open
Labels

Comments

@brucejo75
Copy link

Describe the bug
Multipass cannot connect to the multipassd.exe socket.

Suspect that latest version of Windows 10 may have changed something.

To Reproduce

  1. Installed latest version of Multipass on Windows 10.
  2. Goes into a loop Attempting to set driver to hyperv infinite loop
  3. Clicked Show details:
  • Attempting to set driver to hyperv
  • set failed: cannot connect to multipass socket
  • Please ensure multipassd is running and "localhost:40041' is accessible
  1. I checked that multipassd.exe is running.

It finally stopped attempting but the program is not running and I keep getting socket connection errors.

I tried this on versions: 1.10.1, 1.10.1, 1.13.1 & 1.14.1

Expected behavior
expected Multipass to install without errors.

Logs
Tried to run the install that had errors, captured logs.

Multipass Logs
2024-11-01 14:02:50.266880 ERROR Error on polling info
	gRPC Error (code: 14, codeName: UNAVAILABLE, message: Error connecting: SocketException: The remote computer refused the network connection.
	 (OS Error: The remote computer refused the network connection.
	, errno = 1225), address = localhost, port = 58403, details: null, rawResponse: null, trailers: {})
2024-11-01 14:02:52.431113 ERROR Error on polling info
	gRPC Error (code: 14, codeName: UNAVAILABLE, message: Error connecting: SocketException: The remote computer refused the network connection.
	 (OS Error: The remote computer refused the network connection.
	, errno = 1225), address = localhost, port = 58405, details: null, rawResponse: null, trailers: {})
2024-11-01 14:02:54.580980 ERROR Error on polling info
	gRPC Error (code: 14, codeName: UNAVAILABLE, message: Error connecting: SocketException: The remote computer refused the network connection.
	 (OS Error: The remote computer refused the network connection.
	, errno = 1225), address = localhost, port = 58407, details: null, rawResponse: null, trailers: {})
2024-11-01 14:02:56.731846 ERROR Error on polling info
	gRPC Error (code: 14, codeName: UNAVAILABLE, message: Error connecting: SocketException: The remote computer refused the network connection.
	 (OS Error: The remote computer refused the network connection.
	, errno = 1225), address = localhost, port = 58409, details: null, rawResponse: null, trailers: {})

Additional info

  • OS: Windows 10 Version 22H2 (OS Build 19045.5073)
  • multipass version: 1.14.1+win
  • multipass info: "info failed: cannot connect to the multipass socket"
  • multipass get local.driver: "get failed: cannot connect to the multipass socket"

Additional context

  1. I added multipassd.exe to the allowed apps list for the Windows Firewall. Both Private and Public. Noticed that all ports were already opened multipass.exe & multipassd.exe.
  2. Verified that multipassd.exe is running
  3. Verified that Multipass Service is running
  4. I had installed one of the earlier versions before without issue. Maybe it is the update of Windows 10?
@brucejo75 brucejo75 added bug needs triage Issue needs to be triaged labels Nov 1, 2024
@2021400278zzc
Copy link

Failed to set driver. Will try again in 1 second. Please use 'multipass authenticate' before proceeding. Failed to set driver. Will try again in 1 second. Attempting to set driver to hyperv[2K [OA [OEset failed: The client is not authenticated with the... Please use 'multipass authenticate' before proceeding. Failed to set driver. Will try again in 1 second. Attempting to set driver to 'hyperv'[2K [OA [OEset failed: The client is not authenticated with the. Please use 'multipass authenticate' before proceeding. Failed to set driver. Will try again in 1 second.

@2021400278zzc
Copy link

This appears during installation

@2021400278zzc
Copy link

I wonder why

@levkropp
Copy link
Contributor

levkropp commented Nov 5, 2024

Hi @2021400278zzc , this appears to be a different issue than the OP, please make a new issue and follow the issue template so that we can help you better with this!

@levkropp
Copy link
Contributor

levkropp commented Nov 5, 2024

Hi @brucejo75 , would you be able to access the logs on your Windows machine and send them here as files?

Additionally, can you provide us with more information on your Windows 10 installation, such as whether it is Home/Pro/Enterprise?

@brucejo75
Copy link
Author

brucejo75 commented Nov 5, 2024

Hi @levkropp,

I am running Windows 10 Pro Version 22H2 (OS Build 19045.5073)

To reproduce a 1st install I did these steps:

  1. Uninstall Multipass
  2. Delete %APPDATA%\com.canonical
  3. Start install.

Install completes, but the installer never resolved an error connecting the multipass service.

At this point the %APPDATA%\com.canonical folder is not created. I copied out the Event Viewer log for multipass: Multipass Events.txt

To generate GUI logs, I started the Multipass App, which sits in an infinite loop "Waiting for daemon". This does produce a log in the Multipass GUI folder: multipass_gui.log

Hope this helps!

PS: I repeated steps 1-3 as admin and got the same results with these logs:
Multipass Events-admin.txt
multipass_gui.log

@ricab
Copy link
Collaborator

ricab commented Nov 6, 2024

Hi @brucejo75, I couldn't find anything wrong in your daemon logs. It could be that, for some reason, it just takes a long time to initialize and doesn't come up on time for the client to reach it from the installer.

What's puzzling to me is the port numbers you report: 40041 (CLI, I believe) and 58403, 58405... (GUI). I don't suppose you have MULTIPASS_SERVER_ADDRESS set in your environment? The default port is 50051 and that is the one that your daemon is listening on, as per your event logs. No idea why the clients would try to connect somewhere else.

One thing you could try is this package, to see if you observe the same thing. We're changing our Windows packaging to MSI and hopefully the problem does not occur there.

@ricab ricab removed the needs triage Issue needs to be triaged label Nov 15, 2024
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

4 participants