How to access logs

Logs are our first go-to when something goes wrong. Multipass is comprised of a daemon process (service) and the command line and GUI clients, each of them reporting on their own health. The multipass command accepts the --verbose option (-v for short), which can be repeated to go from the default (error) level through warning, info, debug up to trace.

We use the underlying platform’s logging facilities to ensure you get the familiar behavior wherever you are.

Contents:

Linux

On Linux, systemd-journald is used, integrating with the de-facto standard for this on modern Linux systems.

To access the daemon (and its child processes’) logs:

$ journalctl --unit 'snap.multipass*'

macOS

On macOS, log files are stored in /Library/Logs/Multipass, where multipassd.log has the daemon messages. You can also see instance logs here - the filename pattern is <instance>-hyperkit.log. You will need sudo to access any of those files by default.

Windows

On Windows, the Event system is used and Event Viewer lets you access them. Our logs are currently under “Windows Logs/Application”, where you can filter by “Multipass” Event source. You can then export the selected events to a file.

1 Like
$ journalctl --unit "snap.multipass*"

Thanks @abitrolly, quoted.