On Tue, Dec 6, 2016 at 9:43 PM, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
I changed the answer file this way
old = < new = >
< OVEHOSTED_VDSM/consoleType=str:qxl ---
OVEHOSTED_VDSM/consoleType=str:vnc
and the deploy went ahead creating the VM
[ INFO ] Creating VM You can now connect to the VM with the following command: hosted-engine --console You can also graphically connect to the VM from your system with the following command: remote-viewer vnc://ovirt41.localdomain.local:5900 Use temporary password "0979VeaN" to connect to vnc console. Please ensure that your Guest OS is properly configured to support serial console according to your distro documentation. Follow http://www.ovirt.org/Serial_Console_Setup#I_need_to_ access_the_console_the_old_way for more info. If you need to reboot the VM you will need to start it manually using the command: hosted-engine --vm-start You can then set a temporary password using the command: hosted-engine --add-console-password [ INFO ] Running engine-setup on the appliance
But it seems stuck in the bios.... see: https://drive.google.com/file/d/0BwoPbcrMv8mvSE1mWFVIUEhiRTg/ view?usp=sharing
Here the HostedEngine.log generated under /var/log/libvirt/qemu https://drive.google.com/file/d/0BwoPbcrMv8mvZ0V5RTFBZXJfMzA/view?usp=sharin... I see at the end of it the line warning: host doesn't support requested feature: CPUID.07H:EBX.erms [bit 9]