Bug 1911177
| Summary: | virt-builder + virt-install creates a VM that cannot boot fedora 33 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | John Schmitt <marmalodak> | ||||
| Component: | libguestfs | Assignee: | Richard W.M. Jones <rjones> | ||||
| Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 33 | CC: | mikecicc01, rjones | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2021-03-21 14:34:01 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Created attachment 1746816 [details]
picture of the failed boot process for virtual fedora33 instance
I'm having the same issue with a very similar script. Fedora 32 boots fine but fedora 33 fails with: "[FAILED] Failed to start Switching Root. See 'systemctl status initrd switch root.service' for details." If do not bring up the console right away you might not see the above message. I've attached an image of the error I'm seeing. thanks, Mike I just kicked off another build of the Fedora 33 template in the hope that whatever was broken in Fedora before is now fixed. That didn't work. There's something broken in Fedora that prevents virt-install installations from working. I wasn't able to work out what had gone wrong last time, but enabling debugging to try to get to the true error (somehow) would be helpful. Seems as if we have a fix now. Try revision 2 of the image which virt-builder should pull automatically. Success! Thanks for taking a look at this and getting it fixed... using virt-builder makes everything so much easier for quick homelab deployments! I was going to test it yesterday but got sidetracked several times... I wasn't the original poster of this bug but it's working for me... thanks, Mike This has been fixed for a while, closing. |
Description of problem: I can create a fedora 32 VM successfully with virt-builder and virt-install. The fedora 33 VM I create with these steps fails to boot. Version-Release number of selected component (if applicable): Version : 1.43.2 Release : 2.fc33 How reproducible: Always Steps to Reproduce: This script will successfully create a VM that boots to a login prompt: #!zsh set -e set -x set -u set -o pipefail IMAGES_PATH=. OS=fedora-32 OS_VARIANT=fedora32 OS_IMAGE=${OS}.qcow2 virt-builder ${OS} \ --output ${IMAGES_PATH}/${OS_IMAGE} \ --ssh-inject root:file:${HOME}/.ssh/id_rsa.pub \ --root-password password:password echo virt-install \ --connect qemu:///system \ --name ${OS} \ --ram 2048 \ --vcpus 2 \ --nographics \ --os-variant ${OS_VARIANT}\ --network none \ --import \ --disk path=${IMAGES_PATH}/${OS_IMAGE} This script will create a VM that prompts for a root password to enter a rescue shell. The root password provided does not allow me to launch the rescue shell: #!zsh set -e set -x set -u set -o pipefail IMAGES_PATH=. OS=fedora-33 OS_VARIANT=fedora33 OS_IMAGE=${OS}.qcow2 virt-builder ${OS} \ --output ${IMAGES_PATH}/${OS_IMAGE} \ --ssh-inject root:file:${HOME}/.ssh/id_rsa.pub \ --root-password password:password echo virt-install \ --connect qemu:///system \ --name ${OS} \ --ram 2048 \ --vcpus 2 \ --nographics \ --os-variant ${OS_VARIANT}\ --network none \ --import \ --disk path=${IMAGES_PATH}/${OS_IMAGE}