Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 2234653
Summary: | unable to boot Fedora 39 beta live image in the VMWare Workstation 17 Player | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | MartinKG <mgansser> |
Component: | systemd | Assignee: | systemd-maint |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 39 | CC: | awilliam, fedoraproject, filbranden, lnykryn, lukas, msekleta, ryncsn, systemd-maint, yuwatana, zbyszek |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | AcceptedFreezeException | ||
Fixed In Version: | systemd-254.2-6.fc40 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2023-10-11 17:47:44 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 2143447 |
Description
MartinKG
2023-08-25 07:02:52 UTC
Any other messages before that? Try removing 'rhgb' from the boot options too. more error messages w/o quiet & rhgb boot option. https://martinkg.fedorapeople.org/ErrorReports/fc39/bootmsgfc39-1.png Hmm, still no reason for the failure. Please also add 'systemd.log-level=debug systemd.log-target=console' to the boot options and show the output. I don't know how to copy the complete messages from the console window, so I have only taken 3 screeshots, hopefully there is some useful information here. https://martinkg.fedorapeople.org/ErrorReports/fc39/a1.png https://martinkg.fedorapeople.org/ErrorReports/fc39/a2.png https://martinkg.fedorapeople.org/ErrorReports/fc39/a3.png It does, thanks. The relevant part: Set up TFD_TIMER_CANCEL_ON_SET timerfd. bpf-lsm: LSM BPF program attached Enabling (yes) showing of status (commandline). Serializing systemd-environment-generators to memfd. Successfully forked off ('sd-executor)' as PID 891. Serializing 60-flatpak-system-only to memfd. Successfully forked off ('direxec)' as PID 892. (sd-executor) terminated by signal ALRM. Closing set fd 39 ... Closing set fd 58 [!!!!!!!] Failed to start up manager. Freezing execution. https://github.com/systemd/systemd/issues/28965 might be the same issue. when will the change in systemd be included in the current fc39 iso image ? Just to make sure it's mentioned and completeness, experiencing the same issue on VMware Workstation 17.0.2 Pro and VMware ESXi 8.0U1c. Same errors. Right now we still don't exactly know what the issue is and how to fix it. If the issue is widespread enough (and it seems like it might be), we'll probably make it a blocker bug. It looks like this is the same issue. There'll be an update soon, please holler if it turns out not to fix the issue. FEDORA-2023-6305159732 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-6305159732 FEDORA-2023-6305159732 has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-6305159732` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-6305159732 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. just tried to boot in vmware workstation 17.02 player from the current fedora-workstation-live-x86_64-39-20230913.n.0.iso, but it still gives the error message: "Failed to start up manager." in which iso image will the error be solved ? We're in beta freeze. After the freeze ends, the first image that is built should have the updated version of the package. FEDORA-2023-3355cdb0a8 has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-3355cdb0a8` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-3355cdb0a8 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2023-2561021d71 has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2023-2561021d71 FEDORA-2023-2561021d71 has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2023-3355cdb0a8 has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-3355cdb0a8` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-3355cdb0a8 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2023-3355cdb0a8 has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-3355cdb0a8` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-3355cdb0a8 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. Re-opening as the update is not stable for F39, and proposing for a Final freeze exception - booting on VMware Player is a thing we want to do. FEDORA-2023-3355cdb0a8 has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report. +4 in https://pagure.io/fedora-qa/blocker-review/issue/1383 , marking accepted. This should be resolved now. Can the reporter confirm that it works OK with current nightlies - https://openqa.fedoraproject.org/nightlies.html ? Thanks. i can now confirm that from the current nightly Version Fedora-Workstation-Live-x86_64-39-20231011.n.0.iso can be booted and a virtual machine can be created. The ticket can thus be closed Many Thanks Thanks! |