Bug 1827826 - Cannot power on any virtual machines on a new install
Summary: Cannot power on any virtual machines on a new install
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-node
Classification: oVirt
Component: General
Version: 4.3
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Nir Levy
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-24 21:55 UTC by Ranvir Mankoo
Modified: 2020-06-15 11:43 UTC (History)
15 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-06-15 11:43:11 UTC
oVirt Team: Node
Embargoed:


Attachments (Terms of Use)
Relevant logs (1.97 MB, application/zip)
2020-04-24 21:55 UTC, Ranvir Mankoo
no flags Details

Description Ranvir Mankoo 2020-04-24 21:55:39 UTC
Created attachment 1681649 [details]
Relevant logs

Description of problem:
I have created a new RHV lab setup, the setup was smooth and completed without a single error but virtual machines fail to boot. The console is hung on the initial SeaBIOS screen. At this time, the CPU usage for the virtual machine is also very high.

This is a single node, standalone manager deployment with local storage. 
Both nodes (Host and Manager) are virtual running on ESXi 6.x

Version-Release number of selected component (if applicable):
4.3

How reproducible:
Power on the virtual machine

Steps to Reproduce:
1. Create a new virtual machine and power it on.

Actual results:
Virtual machine should boot

Expected results:
Virtual machine does not boot, hung on the initial SeaBIOS screen.

Additional info:
The following details are attached:

-Screenshot of the console
-Screenshot showing the CPU usage of the virtual machine
-process details for the qemu-kvm process
-xml dump of the virtual machine configuration
-All logs in /var/log/ directory on the manager and on the host are attached. 
-System information (OS, installed packages, CPU info, etc) from the manager and the hosts is also attached.

I am fairly new to RHV and have gathered logs I thought would be relevant to provide details about the issue, please feel free to let me know if you need any other specific logs.

Comment 1 RHEL Program Management 2020-04-26 01:06:30 UTC
The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again.

Comment 2 Sandro Bonazzola 2020-04-28 07:48:33 UTC
Not sure that this is a RHV bug, being the host running on ESXi so VMs are going to run in nested virtualization

Comment 3 Sandro Bonazzola 2020-04-28 07:50:23 UTC
Paolo, is nested virtualization on VMWare a supported case?

Comment 4 Ranvir Mankoo 2020-05-04 11:46:20 UTC
Any updates on this?

Comment 5 Arik 2020-06-11 11:11:33 UTC
(In reply to Sandro Bonazzola from comment #3)
> Paolo, is nested virtualization on VMWare a supported case?

Comment 6 Paolo Bonzini 2020-06-11 12:52:10 UTC
No, it's not as far as I know.

Comment 7 Arik 2020-06-15 11:43:11 UTC
This type of deployment may work for running ovirt-engine but not for ovirt nodes.


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