System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down when systemctl start virtqemud about wsl HOT 6 CLOSED

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Open similar issues:

• System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down (#8883), similarity score: 0.82

Closed similar issues:

• System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down (#8921), similarity score: 0.82
• "System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down" (#9368), similarity score: 0.81
• System has not been booted with systemd as init system (PID 1). Can't operate. (#6197), similarity score: 0.73
• System has not been booted with systemd as init system (PID 1). Can't operate. (#3707), similarity score: 0.73

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

from wsl.

Hi @Windows98SE-dev, first time I see the AI bot searching for issues, that is nice, but in case someone real you would prefer to hear, here is a few parts from those links:

• check if you restarted your pc and then WSL properly: systemd will need a restart of at least the WSL
• check the existence, location and content of wsl config file, conforming to linux standards
• check a few required packages for the distro you are trying to use, like dbus.

I will keep the post short as we have accumulated many solutions in the linked issues, some short some long, it would be few pages long to trying to post them here again. Please take your time and read them. (8883 has solutions, it is just kept open for awareness).

from wsl.

/logs

from wsl.

Hello! Could you please provide more logs to help us better diagnose your issue?

To collect WSL logs, download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The scipt will output the path of the log file once done.

Once completed please upload the output files to this Github issue.

Click here for more info on logging

If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue.

Thank you!

from wsl.

Unfortuantely I don't have admin perms on my PC and .ps1 scripts have been disabled

from wsl.

Unfortunately we need to logs to diagnose this issue. I'll close this for now but feel free to reopen if you get the permissions to collect logs on your machine.

from wsl.