Bug 1671281 - VM failed to boot
Summary: VM failed to boot
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 4.3.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact: Nisim Simsolo
URL:
Whiteboard:
Depends On:
Blocks: 1611889
TreeView+ depends on / blocked
 
Reported: 2019-01-31 09:57 UTC by Pedut
Modified: 2019-03-07 12:05 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-07 12:05:11 UTC
oVirt Team: Virt
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
screenshot (14.87 KB, image/png)
2019-01-31 09:57 UTC, Pedut
no flags Details

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


Note You need to log in before you can comment on or make changes to this bug.