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.
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.
Not sure that this is a RHV bug, being the host running on ESXi so VMs are going to run in nested virtualization
Paolo, is nested virtualization on VMWare a supported case?
Any updates on this?
(In reply to Sandro Bonazzola from comment #3) > Paolo, is nested virtualization on VMWare a supported case?
No, it's not as far as I know.
This type of deployment may work for running ovirt-engine but not for ovirt nodes.