On Mon, Aug 18, 2014 at 05:48:45PM +0400, Denis Kirjanov wrote: > sendkeys would work (ctrl alt backspace), but it's not implemented in my version( > > (vdsm-cli-0:4.10.2-22.0.el6.noarch) > > ----- Исходное сообщение ----- > От: "Denis Kirjanov" <kda(a)itsirius.su&gt; > Кому: devel(a)ovirt.org > Отправленные: Понедельник, 18 Август 2014 г 16:07:58 > Тема: [ovirt-devel] vdsClient desktopLogoff bug > > Hi, > > I'm using RHEV 3.1.0-53. > I can successfully invoke the desktopLock command, but the desktopLogoff command returns "Virtual machine does not exist". > Command looks like the following one: > vdsClient -s --truststore <path> <host> desktopLogoff true <VMID> Could you show the relevant parts of vdsm.log for both commands?

----- Исходное сообщение ----- От: "Vinzenz Feenstra" <vfeenstr(a)redhat.com&gt; Кому: "Dan Kenigsberg" <danken(a)redhat.com&gt;, "Denis Kirjanov" <kda(a)itsirius.su&gt; Копия: devel(a)ovirt.org Отправленные: Вторник, 19 Август 2014 г 10:08:48 Тема: Re: [ovirt-devel] vdsClient desktopLogoff bug On 08/18/2014 06:17 PM, Dan Kenigsberg wrote: > On Mon, Aug 18, 2014 at 05:48:45PM +0400, Denis Kirjanov wrote: >> sendkeys would work (ctrl alt backspace), but it's not implemented in my version( >> >> (vdsm-cli-0:4.10.2-22.0.el6.noarch) >> >> ----- Исходное сообщение ----- >> От: "Denis Kirjanov" <kda(a)itsirius.su&gt; >> Кому: devel(a)ovirt.org >> Отправленные: Понедельник, 18 Август 2014 г 16:07:58 >> Тема: [ovirt-devel] vdsClient desktopLogoff bug >> >> Hi, >> >> I'm using RHEV 3.1.0-53. >> I can successfully invoke the desktopLock command, but the desktopLogoff command returns "Virtual machine does not exist". >> Command looks like the following one: >> vdsClient -s --truststore <path> <host> desktopLogoff true <VMID> > Could you show the relevant parts of vdsm.log for both commands? Desktop Logoff is currently a noop in the guest agent. It'll be implemented sometime later. Ok, I see. Thanks. I'm asking this question since I want to avoid the gdm lock screen window: 1) On a specific event I do the lock screen command to vm 2) I do the logout from the host system 3) I do the login on the host system .The process sets up the vm ticket, queries the ports from the VM manager and _performs the desktopLogin_! 4) Spice session takes place. Here I do expect to see the VM destop, not the lock screen window. I've found that the SSO in the previous scenario works if I do the logout from the VM manually.