oxidecomputer / oxidecomputer/helios-engvm

Helios vm error on bootup

Open
#5 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
64
Forks
9
PR merge metrics
No merged PRs in 30d

Description

Not sure if this is a problem yet, but I see this error message when running the vm seed image on osx with VMware fusion:

helios console login: Just a moment...
Just a moment...
Just a moment...
May 14 10:48:49 helios svc.startd[9]: system/illumos/userscript:default failed: transitioned to maintenance (see 'svcs -xv' for details)

SUNW-MSG-ID: SMF-8000-YX, TYPE: defect, VER: 1, SEVERITY: major
EVENT-TIME: Fri May 14 10:48:49 UTC 2021
PLATFORM: VMware-Virtual-Platform, CSN: VMware-56-4d-36-6f-65-2c-25-c0-6d-ef-f5-12-e9-1f-b6-61, HOSTNAME: helios
SOURCE: software-diagnosis, REV: 0.1
EVENT-ID: 2fd2d908-7e93-ef0e-a01e-c695275ec5e8
DESC: A service failed - a method is failing in a retryable manner but too often.
  Refer to http://illumos.org/msg/SMF-8000-YX for more information.
AUTO-RESPONSE: The service has been placed into the maintenance state.
IMPACT: svc:/system/illumos/userscript:default is unavailable.
REC-ACTION: Run 'svcs -xv svc:/system/illumos/userscript:default' to determine the generic reason why the service failed, the location of any logfiles, and a list of other services impacted.

This may not actually be a problem? unclear, leaving it here in case anyone has seen this before.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the Helios seed image boot on OS X with VMware Fusion, then run svcs -xv svc:/system/illumos/userscript:default as the message recommends. Determine whether the userscript service failure is expected or indicates a boot problem, and record the confirmed behavior and resolution.

Written by the indexing model from the issue text.

Assessment

Domain
operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
18/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.