Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1671281

Summary: VM failed to boot
Product: Red Hat Enterprise Virtualization Manager Reporter: Pedut <pchocron>
Component: ovirt-engineAssignee: Nobody <nobody>
Status: CLOSED WORKSFORME QA Contact: Nisim Simsolo <nsimsolo>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.3.0CC: mavital, michal.skrivanek, nsimsolo, ratamir, rbarry, Rhev-m-bugs
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: 2019-03-07 12:05:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1611889    
Attachments:
Description Flags
screenshot none

Description Pedut 2019-01-31 09:57:49 UTC 
Created attachment 1525302 [details]
screenshot

Description of problem:
VM failed to boot.

Version-Release number of selected component (if applicable):
Engine Version: 4.3.0-0.8.master.20190122121624.git9a8a519.el7
OS Version: RHEL - 7.6 - 4.el7
LIBVIRT Version: libvirt-4.5.0-10.el7_6.4
VDSM Version: vdsm-4.30.8-9.el7

How reproducible:
100%

Steps to Reproduce:
1. Upload the latest version of rhel6.10 from Brew to the glance.
2. Import the image as disk(not as template).
3. Create a vm with the following parameters:
 - Operating System - Red Hat Enterprise Linux 6.x x64
 - Attach the disk from 2 to the VM.
 - Instantiate VM network interfaces by adding the ovirtmgmt/ovirtmgmt nic.
 - In the initial run section mark Use Cloud-Init/Sysprep and in the Authentication sub section fill the username and password.
4. Run the VM from 3.
5. Enable root loging over ssh in the VM according to https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/v2v_guide/preparation_before_the_p2v_migration-enable_root_login_over_ssh
6. Seal the VM according to - https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.5/html/Administration_Guide/sect-Sealing_Virtual_Machines_in_Preparation_for_Deployment_as_Templates.html
7. Upload the VM disk to the glance.
8. Import the image from the glance(the image that was uploaded in 7) as template.
9. Create other VM based on the template from 8 and run the VM.

Actual results:
VM failed to boot.

Expected results:
VM boot successfully.

Additional info:
Comment 1 Ryan Barry 2019-02-01 00:20:19 UTC 
The VM succeeds booting here from a qemu perspective, and the screenshot is system-lwvel. This is not a virt issue.

Instead, it's likely that there is a problem with the installed system somewhere. Troubleshooting would involve removing "quiet" from the kernel command line, and potential enabling a dracut shell plus serial console in order to see logs while the system is booting.

Without this, there's really no way to know what's wrong with the system
Comment 3 Ryan Barry 2019-03-05 23:04:50 UTC 
Nisim, reproducible?
Comment 4 Nisim Simsolo 2019-03-07 11:42:58 UTC 
no