On 2-11-2015 13:23, Simone Tiraboschi wrote:

On Mon, Nov 2, 2015 at 11:41 AM, Joop <jvdwege@xs4all.nl> wrote:

On 2-11-2015 11:18, Gianluca Cecchi wrote:

On Mon, Nov 2, 2015 at 10:57 AM, noc <noc@nieuwland.nl> wrote:

Anything else I can provide let me know please.

Regards,

Joop

Hi Joop,

are you able to access the engine console after deploy, using the command

I have done that in the past but that was 3.5.x.
I generally don't need vnc access to the engine since ssh works fine.
Whats your use case?

hosted-engine --add-console-password=<password>

? 

Have you configured engine VM with spice or vnc?

VNC

BTW: is there a way from command line to change console for the sh engine after deploy?

Probably is but the vm.conf has been moved to the storage domain but don't know where, Simone??

Yes, when we solved the auto-import of the hosted-engine storage domain issue (including the sanlock issue) you will able to edit the engine VM from the engine itself as for regular VMs.

 

Got a BZ id that tracks this?

Joop

_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users