subject:"\[ovirt\-users\] engine upgrade 4.1.0 => 4.1.1, no more engine console available"

Re: [ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more engine console available

2017-06-18 Thread Evgenia Tokar

Hi Gianluca,

So sorry for the late reply, we have tried reproducing this bug and tried
to figure out a solution.

As Sharon mentioned earlier the graphics configuration for the vm is wrong
and unsupported.
We weren't able to reproduce this, and we don't have a solution for this.

Are you experiencing this issue in any other environment? If not, it might
be that something was misconfigured at some earlier stage and caused the
error now.

Thanks,
Jenny


On Fri, Jun 16, 2017 at 11:10 PM, Yaniv Kaul  wrote:

>
>
> On Fri, Jun 16, 2017 at 5:20 PM, Gianluca Cecchi <
> gianluca.cec...@gmail.com> wrote:
>
>> On Thu, Apr 27, 2017 at 11:25 AM, Evgenia Tokar 
>> wrote:
>>
>>> Hi,
>>>
>>> It looks like the graphical console fields are not editable for hosted
>>> engine vm.
>>> We are trying to figure out how to solve this issue, it is not
>>> recommended to change db values manually.
>>>
>>> Thanks,
>>> Jenny
>>>
>>>
>>> On Thu, Apr 27, 2017 at 10:49 AM, Gianluca Cecchi <
>>> gianluca.cec...@gmail.com> wrote:
>>>
 On Thu, Apr 27, 2017 at 9:46 AM, Gianluca Cecchi <
 gianluca.cec...@gmail.com> wrote:

>
>
> BTW: if I try to set the video type to Cirrus from web admin gui (and
> automatically the Graphics Protocol becomes "VNC"), I get this when I 
> press
> the OK button:
>
> Error while executing action:
>
> HostedEngine:
>
>- There was an attempt to change Hosted Engine VM values that are
>locked.
>
> The same if I choose "VGA"
> Gianluca
>


 I verified that I already have in place this parameter:

 [root@ractorshe ~]# engine-config -g AllowEditingHostedEngine
 AllowEditingHostedEngine: true version: general
 [root@ractorshe ~]#


>>>
>> Hello is there a solution for this problem?
>> I'm now in 4.1.2 but still not able to access the engine console
>>
>
> I thought https://bugzilla.redhat.com/show_bug.cgi?id=1441570 was
> supposed to handle it...
> Can you share more information in the bug?
> Y.
>
>
>>
>> [root@ractor ~]# hosted-engine --add-console-password --password=pippo
>> no graphics devices configured
>> [root@ractor ~]#
>>
>> In web admin
>>
>> Graphics protocol: None  (while in edit vm screen it appears as "SPICE"
>> and still I can't modify it)
>> Video Type: QXL
>>
>> Any chance for upcoming 4.1.3? Can I test it it there is new changes
>> related to this problem.
>>
>> the qemu-kvm command line for hosted engine is now this one:
>>
>> qemu  8761 1  0 May30 ?01:33:29 /usr/libexec/qemu-kvm
>> -name guest=c71,debug-threads=on -S -object secret,id=masterKey0,format=ra
>> w,file=/var/lib/libvirt/qemu/domain-3-c71/master-key.aes -machine
>> pc-i440fx-rhel7.3.0,accel=kvm,usb=off -cpu Nehalem -m
>> size=1048576k,slots=16,maxmem=4194304k -realtime mlock=off -smp
>> 1,maxcpus=16,sockets=16,cores=1,threads=1 -numa
>> node,nodeid=0,cpus=0,mem=1024 -uuid 202e6f2e-f8a1-4e81-a079-c775e86a58d5
>> -smbios type=1,manufacturer=oVirt,product=oVirt
>> Node,version=7-3.1611.el7.centos,serial=4C4C4544-0054-5910-
>> 8056-C4C04F30354A,uuid=202e6f2e-f8a1-4e81-a079-c775e86a58d5
>> -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/va
>> r/lib/libvirt/qemu/domain-3-c71/monitor.sock,server,nowait -mon
>> chardev=charmonitor,id=monitor,mode=control -rtc
>> base=2017-05-30T13:18:37,driftfix=slew -global
>> kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on
>> -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device
>> virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x4 -device
>> virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x5
>> -drive if=none,id=drive-ide0-1-0,readonly=on -device
>> ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive
>> file=/rhev/data-center/0001-0001-0001-0001-00ec/
>> 556abaa8-0fcc-4042-963b-f27db5e03837/images/7d5dd44f-
>> f5d1-4984-9e76-2b2f5e42a915/6d873dbd-c59d-4d6c-958f-
>> a4a389b94be5,format=raw,if=none,id=drive-virtio-disk0,
>> serial=7d5dd44f-f5d1-4984-9e76-2b2f5e42a915,cache=none,
>> werror=stop,rerror=stop,aio=threads -device
>> virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virti
>> o-disk0,id=virtio-disk0,bootindex=1 -netdev
>> tap,fd=33,id=hostnet0,vhost=on,vhostfd=35 -device
>> virtio-net-pci,netdev=hostnet0,id=net0,mac=00:1a:4a:16:01:51,bus=pci.0,addr=0x3
>> -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/2
>> 02e6f2e-f8a1-4e81-a079-c775e86a58d5.com.redhat.rhevm.vdsm,server,nowait
>> -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel
>> 0,id=channel0,name=com.redhat.rhevm.vdsm -chardev
>> socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/2
>> 02e6f2e-f8a1-4e81-a079-c775e86a58d5.org.qemu.guest_agent.0,server,nowait
>> -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel
>> 1,id=channel1,name=org.qemu.guest_agent.0 -chardev
>> spicevmc,id=charchannel2,name=vdagent -device
>>

Re: [ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more engine console available

2017-06-16 Thread Yaniv Kaul

On Fri, Jun 16, 2017 at 5:20 PM, Gianluca Cecchi 
wrote:

> On Thu, Apr 27, 2017 at 11:25 AM, Evgenia Tokar  wrote:
>
>> Hi,
>>
>> It looks like the graphical console fields are not editable for hosted
>> engine vm.
>> We are trying to figure out how to solve this issue, it is not
>> recommended to change db values manually.
>>
>> Thanks,
>> Jenny
>>
>>
>> On Thu, Apr 27, 2017 at 10:49 AM, Gianluca Cecchi <
>> gianluca.cec...@gmail.com> wrote:
>>
>>> On Thu, Apr 27, 2017 at 9:46 AM, Gianluca Cecchi <
>>> gianluca.cec...@gmail.com> wrote:
>>>


 BTW: if I try to set the video type to Cirrus from web admin gui (and
 automatically the Graphics Protocol becomes "VNC"), I get this when I press
 the OK button:

 Error while executing action:

 HostedEngine:

- There was an attempt to change Hosted Engine VM values that are
locked.

 The same if I choose "VGA"
 Gianluca

>>>
>>>
>>> I verified that I already have in place this parameter:
>>>
>>> [root@ractorshe ~]# engine-config -g AllowEditingHostedEngine
>>> AllowEditingHostedEngine: true version: general
>>> [root@ractorshe ~]#
>>>
>>>
>>
> Hello is there a solution for this problem?
> I'm now in 4.1.2 but still not able to access the engine console
>

I thought https://bugzilla.redhat.com/show_bug.cgi?id=1441570 was supposed
to handle it...
Can you share more information in the bug?
Y.


>
> [root@ractor ~]# hosted-engine --add-console-password --password=pippo
> no graphics devices configured
> [root@ractor ~]#
>
> In web admin
>
> Graphics protocol: None  (while in edit vm screen it appears as "SPICE"
> and still I can't modify it)
> Video Type: QXL
>
> Any chance for upcoming 4.1.3? Can I test it it there is new changes
> related to this problem.
>
> the qemu-kvm command line for hosted engine is now this one:
>
> qemu  8761 1  0 May30 ?01:33:29 /usr/libexec/qemu-kvm
> -name guest=c71,debug-threads=on -S -object secret,id=masterKey0,format=
> raw,file=/var/lib/libvirt/qemu/domain-3-c71/master-key.aes -machine
> pc-i440fx-rhel7.3.0,accel=kvm,usb=off -cpu Nehalem -m
> size=1048576k,slots=16,maxmem=4194304k -realtime mlock=off -smp
> 1,maxcpus=16,sockets=16,cores=1,threads=1 -numa
> node,nodeid=0,cpus=0,mem=1024 -uuid 202e6f2e-f8a1-4e81-a079-c775e86a58d5
> -smbios type=1,manufacturer=oVirt,product=oVirt Node,version=7-3.1611.el7.
> centos,serial=4C4C4544-0054-5910-8056-C4C04F30354A,uuid=
> 202e6f2e-f8a1-4e81-a079-c775e86a58d5 -no-user-config -nodefaults -chardev
> socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-3-c71/monitor.sock,server,nowait
> -mon chardev=charmonitor,id=monitor,mode=control -rtc
> base=2017-05-30T13:18:37,driftfix=slew -global 
> kvm-pit.lost_tick_policy=discard
> -no-hpet -no-shutdown -boot strict=on -device 
> piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2
> -device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x4 -device
> virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x5
> -drive if=none,id=drive-ide0-1-0,readonly=on -device
> ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive
> file=/rhev/data-center/0001-0001-0001-0001-00ec/556abaa8-0fcc-
> 4042-963b-f27db5e03837/images/7d5dd44f-f5d1-4984-9e76-
> 2b2f5e42a915/6d873dbd-c59d-4d6c-958f-a4a389b94be5,format=
> raw,if=none,id=drive-virtio-disk0,serial=7d5dd44f-f5d1-
> 4984-9e76-2b2f5e42a915,cache=none,werror=stop,rerror=stop,aio=threads
> -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-
> virtio-disk0,id=virtio-disk0,bootindex=1 -netdev
> tap,fd=33,id=hostnet0,vhost=on,vhostfd=35 -device virtio-net-pci,netdev=
> hostnet0,id=net0,mac=00:1a:4a:16:01:51,bus=pci.0,addr=0x3 -chardev
> socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/
> 202e6f2e-f8a1-4e81-a079-c775e86a58d5.com.redhat.rhevm.vdsm,server,nowait
> -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=
> charchannel0,id=channel0,name=com.redhat.rhevm.vdsm -chardev
> socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/
> 202e6f2e-f8a1-4e81-a079-c775e86a58d5.org.qemu.guest_agent.0,server,nowait
> -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=
> charchannel1,id=channel1,name=org.qemu.guest_agent.0 -chardev
> spicevmc,id=charchannel2,name=vdagent -device virtserialport,bus=virtio-
> serial0.0,nr=3,chardev=charchannel2,id=channel2,name=com.redhat.spice.0
> -spice tls-port=5901,addr=10.4.168.81,x509-dir=/etc/pki/vdsm/
> libvirt-spice,tls-channel=default,tls-channel=main,tls-
> channel=display,tls-channel=inputs,tls-channel=cursor,tls-
> channel=playback,tls-channel=record,tls-channel=smartcard,
> tls-channel=usbredir,seamless-migration=on -device
> qxl-vga,id=video0,ram_size=67108864,vram_size=33554432,
> vram64_size_mb=0,vgamem_mb=16,bus=pci.0,addr=0x2 -msg timestamp=on
>
>
> Thanks in advance,
> Gianluca
>
> ___
> Users mailing list
> Users@ovirt.org
>

Re: [ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more engine console available

2017-06-16 Thread Gianluca Cecchi

On Thu, Apr 27, 2017 at 11:25 AM, Evgenia Tokar  wrote:

> Hi,
>
> It looks like the graphical console fields are not editable for hosted
> engine vm.
> We are trying to figure out how to solve this issue, it is not recommended
> to change db values manually.
>
> Thanks,
> Jenny
>
>
> On Thu, Apr 27, 2017 at 10:49 AM, Gianluca Cecchi <
> gianluca.cec...@gmail.com> wrote:
>
>> On Thu, Apr 27, 2017 at 9:46 AM, Gianluca Cecchi <
>> gianluca.cec...@gmail.com> wrote:
>>
>>>
>>>
>>> BTW: if I try to set the video type to Cirrus from web admin gui (and
>>> automatically the Graphics Protocol becomes "VNC"), I get this when I press
>>> the OK button:
>>>
>>> Error while executing action:
>>>
>>> HostedEngine:
>>>
>>>- There was an attempt to change Hosted Engine VM values that are
>>>locked.
>>>
>>> The same if I choose "VGA"
>>> Gianluca
>>>
>>
>>
>> I verified that I already have in place this parameter:
>>
>> [root@ractorshe ~]# engine-config -g AllowEditingHostedEngine
>> AllowEditingHostedEngine: true version: general
>> [root@ractorshe ~]#
>>
>>
>
Hello is there a solution for this problem?
I'm now in 4.1.2 but still not able to access the engine console

[root@ractor ~]# hosted-engine --add-console-password --password=pippo
no graphics devices configured
[root@ractor ~]#

In web admin

Graphics protocol: None  (while in edit vm screen it appears as "SPICE" and
still I can't modify it)
Video Type: QXL

Any chance for upcoming 4.1.3? Can I test it it there is new changes
related to this problem.

the qemu-kvm command line for hosted engine is now this one:

qemu  8761 1  0 May30 ?01:33:29 /usr/libexec/qemu-kvm -name
guest=c71,debug-threads=on -S -object
secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-3-c71/master-key.aes
-machine pc-i440fx-rhel7.3.0,accel=kvm,usb=off -cpu Nehalem -m
size=1048576k,slots=16,maxmem=4194304k -realtime mlock=off -smp
1,maxcpus=16,sockets=16,cores=1,threads=1 -numa
node,nodeid=0,cpus=0,mem=1024 -uuid 202e6f2e-f8a1-4e81-a079-c775e86a58d5
-smbios type=1,manufacturer=oVirt,product=oVirt
Node,version=7-3.1611.el7.centos,serial=4C4C4544-0054-5910-8056-C4C04F30354A,uuid=202e6f2e-f8a1-4e81-a079-c775e86a58d5
-no-user-config -nodefaults -chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-3-c71/monitor.sock,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -rtc
base=2017-05-30T13:18:37,driftfix=slew -global
kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on
-device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device
virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x4 -device
virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x5 -drive
if=none,id=drive-ide0-1-0,readonly=on -device
ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive
file=/rhev/data-center/0001-0001-0001-0001-00ec/556abaa8-0fcc-4042-963b-f27db5e03837/images/7d5dd44f-f5d1-4984-9e76-2b2f5e42a915/6d873dbd-c59d-4d6c-958f-a4a389b94be5,format=raw,if=none,id=drive-virtio-disk0,serial=7d5dd44f-f5d1-4984-9e76-2b2f5e42a915,cache=none,werror=stop,rerror=stop,aio=threads
-device
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
-netdev tap,fd=33,id=hostnet0,vhost=on,vhostfd=35 -device
virtio-net-pci,netdev=hostnet0,id=net0,mac=00:1a:4a:16:01:51,bus=pci.0,addr=0x3
-chardev
socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/202e6f2e-f8a1-4e81-a079-c775e86a58d5.com.redhat.rhevm.vdsm,server,nowait
-device
virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.rhevm.vdsm
-chardev
socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/202e6f2e-f8a1-4e81-a079-c775e86a58d5.org.qemu.guest_agent.0,server,nowait
-device
virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=org.qemu.guest_agent.0
-chardev spicevmc,id=charchannel2,name=vdagent -device
virtserialport,bus=virtio-serial0.0,nr=3,chardev=charchannel2,id=channel2,name=com.redhat.spice.0
-spice
tls-port=5901,addr=10.4.168.81,x509-dir=/etc/pki/vdsm/libvirt-spice,tls-channel=default,tls-channel=main,tls-channel=display,tls-channel=inputs,tls-channel=cursor,tls-channel=playback,tls-channel=record,tls-channel=smartcard,tls-channel=usbredir,seamless-migration=on
-device
qxl-vga,id=video0,ram_size=67108864,vram_size=33554432,vram64_size_mb=0,vgamem_mb=16,bus=pci.0,addr=0x2
-msg timestamp=on


Thanks in advance,
Gianluca
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more engine console available

2017-04-27 Thread Evgenia Tokar

Hi,

It looks like the graphical console fields are not editable for hosted
engine vm.
We are trying to figure out how to solve this issue, it is not recommended
to change db values manually.

Thanks,
Jenny


On Thu, Apr 27, 2017 at 10:49 AM, Gianluca Cecchi  wrote:

> On Thu, Apr 27, 2017 at 9:46 AM, Gianluca Cecchi <
> gianluca.cec...@gmail.com> wrote:
>
>>
>>
>> BTW: if I try to set the video type to Cirrus from web admin gui (and
>> automatically the Graphics Protocol becomes "VNC"), I get this when I press
>> the OK button:
>>
>> Error while executing action:
>>
>> HostedEngine:
>>
>>- There was an attempt to change Hosted Engine VM values that are
>>locked.
>>
>> The same if I choose "VGA"
>> Gianluca
>>
>
>
> I verified that I already have in place this parameter:
>
> [root@ractorshe ~]# engine-config -g AllowEditingHostedEngine
> AllowEditingHostedEngine: true version: general
> [root@ractorshe ~]#
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more engine console available

2017-04-27 Thread Gianluca Cecchi

On Thu, Apr 27, 2017 at 9:46 AM, Gianluca Cecchi 
wrote:

>
>
> BTW: if I try to set the video type to Cirrus from web admin gui (and
> automatically the Graphics Protocol becomes "VNC"), I get this when I press
> the OK button:
>
> Error while executing action:
>
> HostedEngine:
>
>- There was an attempt to change Hosted Engine VM values that are
>locked.
>
> The same if I choose "VGA"
> Gianluca
>


I verified that I already have in place this parameter:

[root@ractorshe ~]# engine-config -g AllowEditingHostedEngine
AllowEditingHostedEngine: true version: general
[root@ractorshe ~]#
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more engine console available

2017-04-27 Thread Gianluca Cecchi

On Wed, Apr 26, 2017 at 4:56 PM, Gianluca Cecchi 
wrote:

> On Wed, Apr 26, 2017 at 4:15 PM, Sharon Gratch  wrote:
>
>>
>>
>> You can do that.
>> But I still think that setting to qxl/spice should work In first round 
>> without
>> setting to cirrus/vnc first, since the "
>> 
>> 
>> Graphics protocol" is currently set to "None
>> "
>>
>> and not "spice" AFAIR (as displayed in general sub tab).
>>
>> If it is set to "None", then after the settings in (2) you will be
>> notified with a pop-up displaying the following:
>> "Changes that require Virtual Machine restart: graphicsProtocol"
>>
>> and after a restart both devices should be added.
>>
>>
>>
>>
>>
>> 
>>
>>
> Did you notice the screenshot I already sent in this thread on 24th of
> April?
> https://drive.google.com/file/d/0BwoPbcrMv8mvQVhzaGFHSmoxaGc
> /view?usp=sharing
>
>
> In
> that screenshot you can see that in general subtab there is indicated
> qxl/none, but at the same time in edit VM --> console there are the values
> qxl/SPICE
>
>

BTW: if I try to set the video type to Cirrus from web admin gui (and
automatically the Graphics Protocol becomes "VNC"), I get this when I press
the OK button:

Error while executing action:

HostedEngine:

   - There was an attempt to change Hosted Engine VM values that are locked.

The same if I choose "VGA"
Gianluca
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more engine console available

2017-04-26 Thread Gianluca Cecchi

On Wed, Apr 26, 2017 at 4:15 PM, Sharon Gratch  wrote:

>
>
> You can do that.
> But I still think that setting to qxl/spice should work In first round without
> setting to cirrus/vnc first, since the "
> 
> 
> Graphics protocol" is currently set to "None
> "
>
> and not "spice" AFAIR (as displayed in general sub tab).
>
> If it is set to "None", then after the settings in (2) you will be
> notified with a pop-up displaying the following:
> "Changes that require Virtual Machine restart: graphicsProtocol"
>
> and after a restart both devices should be added.
>
>
>
>
>
> 
>
>
Did you notice the screenshot I already sent in this thread on 24th of
April?
https://drive.google.com/file/d/0BwoPbcrMv8mvQVhzaGFHSmoxaGc/
view?usp=sharing

In
that screenshot you can see that in general subtab there is indicated
qxl/none, but at the same time in edit VM --> console there are the values
qxl/SPICE
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more engine console available

2017-04-26 Thread Sharon Gratch

On Wed, Apr 26, 2017 at 4:39 PM, Gianluca Cecchi 
wrote:

>
>
> On Wed, Apr 26, 2017 at 3:01 PM, Sharon Gratch  wrote:
>
>>
>>
>> On Wed, Apr 26, 2017 at 3:33 PM, Gianluca Cecchi <
>> gianluca.cec...@gmail.com> wrote:
>>
>>> On Wed, Apr 26, 2017 at 2:20 PM, Sharon Gratch 
>>> wrote:
>>>
 Hi,

 The configuration shown at 2016-07-04 of video set to "cirrus-vga" and
 graphic console set to "spice" is an invalid combination which is not
 supported by oVirt.

 I'm not sure how it get there ("vnc" changed to "spice" without
 changing the video device type to "qxl") but it may cause the problem
 afterwards of removing both graphic and video devices ...

 Regards,
 Sharon

>>> Is there a way I can fix, eventually going and modifying the db?
>>> Thanks,
>>> Gianluca
>>>
>>
>> 
>> yes, via the UI.
>> 1. Edit the HostedEngive vm and go to console tab
>> 2. Set "Video Type" value to "QXL" and "
>> 
>> Graphics protocol" value to "SPICE".
>> 3. restart the HostedEngive vm (It requires a HostedEngive vm restart for
>> the configuration changes to take effect)
>> 4. After the restart, the qxl, spice devices will be created as required.
>>
>> Regards,
>> Sharon
>>
>>
>>
> The problems is that, from a web gui point of view, the settings in 2. are
> already in place... ;-) but not honored.. is because of this that I asked
> about database manipulation...
> I could instead change the console parameters and set them to cirrus/vnc
> and see if they work after shutdown and restart of engine VM and in a
> second time change again to qxl/spice and see if they are honored then...
>
> What do you think?
>

You can do that.
But I still think that setting to qxl/spice should work In first round without
setting to cirrus/vnc first, since the "

Graphics protocol" is currently set to "None
"

and not "spice" AFAIR (as displayed in general sub tab).

If it is set to "None", then after the settings in (2) you will be notified
with a pop-up displaying the following:
"Changes that require Virtual Machine restart: graphicsProtocol"

and after a restart both devices should be added.

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

Re: [ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more engine console available

2017-04-26 Thread Gianluca Cecchi

On Wed, Apr 26, 2017 at 3:01 PM, Sharon Gratch  wrote:

>
>
> On Wed, Apr 26, 2017 at 3:33 PM, Gianluca Cecchi <
> gianluca.cec...@gmail.com> wrote:
>
>> On Wed, Apr 26, 2017 at 2:20 PM, Sharon Gratch 
>> wrote:
>>
>>> Hi,
>>>
>>> The configuration shown at 2016-07-04 of video set to "cirrus-vga" and
>>> graphic console set to "spice" is an invalid combination which is not
>>> supported by oVirt.
>>>
>>> I'm not sure how it get there ("vnc" changed to "spice" without changing
>>> the video device type to "qxl") but it may cause the problem afterwards of
>>> removing both graphic and video devices ...
>>>
>>> Regards,
>>> Sharon
>>>
>>>
>> Is there a way I can fix, eventually going and modifying the db?
>> Thanks,
>> Gianluca
>>
>
> 
> yes, via the UI.
> 1. Edit the HostedEngive vm and go to console tab
> 2. Set "Video Type" value to "QXL" and "Graphics protocol" value to
> "SPICE".
> 3. restart the HostedEngive vm (It requires a HostedEngive vm restart for
> the configuration changes to take effect)
> 4. After the restart, the qxl, spice devices will be created as required.
>
> Regards,
> Sharon
>
>
>
The problems is that, from a web gui point of view, the settings in 2. are
already in place... ;-) but not honored.. is because of this that I asked
about database manipulation...
I could instead change the console parameters and set them to cirrus/vnc
and see if they work after shutdown and restart of engine VM and in a
second time change again to qxl/spice and see if they are honored then...

What do you think?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more engine console available

2017-04-26 Thread Sharon Gratch

On Wed, Apr 26, 2017 at 3:33 PM, Gianluca Cecchi 
wrote:

> On Wed, Apr 26, 2017 at 2:20 PM, Sharon Gratch  wrote:
>
>> Hi,
>>
>> The configuration shown at 2016-07-04 of video set to "cirrus-vga" and
>> graphic console set to "spice" is an invalid combination which is not
>> supported by oVirt.
>>
>> I'm not sure how it get there ("vnc" changed to "spice" without changing
>> the video device type to "qxl") but it may cause the problem afterwards of
>> removing both graphic and video devices ...
>>
>> Regards,
>> Sharon
>>
>>
> Is there a way I can fix, eventually going and modifying the db?
> Thanks,
> Gianluca
>

yes, via the UI.
1. Edit the HostedEngive vm and go to console tab
2. Set "Video Type" value to "QXL" and "Graphics protocol" value to "SPICE".
3. restart the HostedEngive vm (It requires a HostedEngive vm restart for
the configuration changes to take effect)
4. After the restart, the qxl, spice devices will be created as required.

Regards,
Sharon
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more engine console available

2017-04-26 Thread Gianluca Cecchi

On Wed, Apr 26, 2017 at 2:20 PM, Sharon Gratch  wrote:

> Hi,
>
> The configuration shown at 2016-07-04 of video set to "cirrus-vga" and
> graphic console set to "spice" is an invalid combination which is not
> supported by oVirt.
>
> I'm not sure how it get there ("vnc" changed to "spice" without changing
> the video device type to "qxl") but it may cause the problem afterwards of
> removing both graphic and video devices ...
>
> Regards,
> Sharon
>
>
Is there a way I can fix, eventually going and modifying the db?
Thanks,
Gianluca
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more engine console available

2017-04-26 Thread Gianluca Cecchi

On Tue, Apr 25, 2017 at 1:00 PM, Evgenia Tokar  wrote:

> It seems that the main issue here is that the graphics device is missing
> from the engine db.
> This causes the generated ovf to not contain a graphics device which in
> turn makes the vm.conf not have it, and so the console is not available.
>
> So what we need to understand now is what caused the graphics device to
> disappear and a way to return it.
>
> Did anything out of the regular update flow happened with the vm?
>
>
> Thanks,
> Jenny
>
>
It seems not.
Based on log files that I see, the environment was initially installed with
3.6.0 and the engine installed from the ova contained into
ovirt-engine-appliance-20151104.0-1.el7.centos.ova
Then I updated the engine with the usual procedure to 3.6.1, 3.6.2, 3.6.3,
3.6.5, 4.0.0.6-1, 4.0.2.6-1, 4.0.2.7-1, 4.0.4.4-1, 4.0.5.5-
1, -4.0.6.3-1, 4.1.0.4-1, 4.1.1.8-1

Watching qemu logs on host for the HosteEngine VM I see this:

On 19/11/15 the console seemed to be vnc, based on HostedEngine.log-20170421

-device cirrus-vga,id=video0,bus=pci.0,addr=0x2

full line:

2015-11-19 14:29:33.908+: starting up
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
QEMU_AUDIO_DRV=none /usr/libexec/qem
u-kvm -name HostedEngine -S -machine pc-i440fx-rhel7.2.0,accel=kvm,usb=off
-cpu Nehalem -m 16384 -re
altime mlock=off -smp 4,sockets=4,cores=1,threads=1 -uuid
7b0ff898-0a9e-4b97-8292-1d9f2a0a6683 -smbi
os type=1,manufacturer=oVirt,product=oVirt Node,version=7-1.1503.el7.
centos.2.8,serial=4C4C4544-0054
-5910-8056-C4C04F30354A,uuid=7b0ff898-0a9e-4b97-8292-1d9f2a0a6683
-no-user-config -nodefaults -chard
ev socket,id=charmonitor,path=/var/lib/libvirt/qemu/
HostedEngine.monitor,server,nowait -mon chardev=
charmonitor,id=monitor,mode=control -rtc base=2015-11-19T14:29:33,driftfix=slew
-global kvm-pit.lost
_tick_policy=discard -no-hpet -no-reboot -boot strict=on -device
piix3-usb-uhci,id=usb,bus=pci.0,add
r=0x1.0x2 -device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x4 -device
virtio-serial-pci,id=virtio-se
rial0,bus=pci.0,addr=0x5 -drive file=/tmp/tmpKbdZDZ/seed.iso,
if=none,id=drive-ide0-1-0,readonly=on,f
ormat=raw,serial= -device
ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0
-drive file=/var/
run/vdsm/storage/2025c2ea-6205-4bc1-b29d-745b47f8f806/
d6287dfb-27af-461b-ab79-4eb3a45d8c8a/43ee87b9-4293-
4d43-beab-582f500667a7,if=none,id=drive-virtio-disk0,
format=raw,serial=d6287dfb-27af-461b-ab79-4eb3a45d8c8a,
cache=none,werror=stop,rerror=stop,aio=threads -device
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-
virtio-disk0,id=virtio-disk0,bootindex=1 -netdev
tap,fd=27,id=hostnet0,vhost=on,vhostfd=28 -device virtio-net-pci,netdev=
hostnet0,id=net0,mac=00:16:3e:3a:ee:a5,bus=pci.0,addr=0x3 -chardev
socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/
7b0ff898-0a9e-4b97-8292-1d9f2a0a6683.com.redhat.rhevm.vdsm,server,nowait
-device virtserialport,bus=virtio-serial0.0,nr=1,chardev=
charchannel0,id=channel0,name=com.redhat.rhevm.vdsm -chardev
socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/
7b0ff898-0a9e-4b97-8292-1d9f2a0a6683.org.qemu.guest_agent.0,server,nowait
-device virtserialport,bus=virtio-serial0.0,nr=2,chardev=
charchannel1,id=channel1,name=org.qemu.guest_agent.0 -chardev
socket,id=charchannel2,path=/var/lib/libvirt/qemu/channels/
7b0ff898-0a9e-4b97-8292-1d9f2a0a6683.org.ovirt.hosted-engine-setup.0,server,nowait
-device virtserialport,bus=virtio-serial0.0,nr=3,chardev=
charchannel2,id=channel2,name=org.ovirt.hosted-engine-setup.0 -chardev
socket,id=charconsole0,path=/var/run/ovirt-vmconsole-
console/7b0ff898-0a9e-4b97-8292-1d9f2a0a6683.sock,server,nowait -device
virtconsole,chardev=charconsole0,id=console0 -vnc 0:0,password -device
cirrus-vga,id=video0,bus=pci.0,addr=0x2 -msg timestamp=on

I don't know how and when I set it to spice, but I think I didn't do
anything...

The first entry with the word "spice" was here:

2016-07-04 16:01:43.443+: starting up libvirt version: 1.2.17, package:
13.el7_2.5 (CentOS Build
System , 2016-06-23-14:23:27,
worker1.bsys.centos.org), qemu version: 2.3.0
(qemu-kvm-ev-2.3.0-31.el7_2.10.1)
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
QEMU_AUDIO_DRV=spice /usr/libexec/qemu-kvm -name HostedEngine -S -machine
pc-i440fx-rhel7.2.0,accel=kvm,usb=off -cpu qemu64,-svm -m 16384 -realtime
mlock=off -smp 4,sockets=4,cores=1,threads=1 -uuid
7b0ff898-0a9e-4b97-8292-1d9f2a0a6683
-smbios type=1,manufacturer=oVirt,product=oVirt Node,version=7-2.1511.el7.
centos.2.10,serial=4C4C4544-0054-5910-8056-C4C04F30354A,
uuid=7b0ff898-0a9e-4b97-8292-1d9f2a0a6683 -no-user-config -nodefaults
-chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-
HostedEngine/monitor.sock,server,nowait -mon
chardev=charmonitor,id=monitor,mode=control
-rtc base=2016-07-04T16:01:43,driftfix=slew -global
kvm-pit.lost_tick_policy=discard -no-hpet -no-reboot -boot strict=on
-device

Re: [ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more engine console available

2017-04-25 Thread Evgenia Tokar

It seems that the main issue here is that the graphics device is missing
from the engine db.
This causes the generated ovf to not contain a graphics device which in
turn makes the vm.conf not have it, and so the console is not available.

So what we need to understand now is what caused the graphics device to
disappear and a way to return it.

Did anything out of the regular update flow happened with the vm?


Thanks,
Jenny

On Tue, Apr 25, 2017 at 12:38 AM, Gianluca Cecchi  wrote:

> On Mon, Apr 24, 2017 at 7:01 PM, Sharon Gratch  wrote:
>
>> Hi,
>>
>>
>> On Mon, Apr 24, 2017 at 6:06 PM, Gianluca Cecchi <
>> gianluca.cec...@gmail.com> wrote:
>>
>>>
>>>
>>> On Mon, Apr 24, 2017 at 12:57 PM, Evgenia Tokar 
>>> wrote:
>>>

 Thanks.

 1. In the UI under vm devices tab do you have an entry for graphical
 device (type=spice)?

>>>
>>> It doesn't seem so...
>>> Se the whole content:
>>> https://drive.google.com/file/d/0BwoPbcrMv8mvblV3dDlMelVFS1U
>>> /view?usp=sharing
>>>
>>>
>> According to the vm devices list you sent here, there is also no entry
>> for for the video device (device with type=qxl), although according to one
>> of your previous mails, the vm "general" sub tab shows "Video Type: qxl".
>>
>
> I confirm that. But please note that in the same general sub tab the
> "Graphics Protocol" appears as "None", while normally it should contain
> "SPICE".
> I resend the link of the general sub tab screenshot:
> https://drive.google.com/file/d/0BwoPbcrMv8mvUURobHhKb0kxemM
> /view?usp=sharing
>
>
>
>
>>
>> 1. Can you please check the vm console configuration to see if headless
>> mode is off, just to make sure?  (in ui - edit the vm and check the console
>> tab to see if the "Headless mode" is not checked).
>>
>> (*) headless mode is a new feature added to 4.1
>>
>
> I confirm headless is not checked.
> See here (you see underneath also the general sub tab):
> https://drive.google.com/file/d/0BwoPbcrMv8mvQVhzaGFHSmoxaGc/
> view?usp=sharing
>
>
>
>> 2. what values are assigned in vm console tab for "Video Type" and
>> "Graphics protocol" fields?
>>
>
> From the above screenshot you see that they are "QXL" and "SPICE"
>
>
>>
>> Thanks,
>> Sharon
>>
>>
>>
> You are welcome.
> I have another environment with single server and she, with similar update
> history and now at 4.1.1.6-1 level, where I had not the problem, but in
> that environment the engine was configured as "VNC" and "Cirrus" so it was
> not the same.
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more engine console available

2017-04-24 Thread Gianluca Cecchi

On Mon, Apr 24, 2017 at 7:01 PM, Sharon Gratch  wrote:

> Hi,
>
>
> On Mon, Apr 24, 2017 at 6:06 PM, Gianluca Cecchi <
> gianluca.cec...@gmail.com> wrote:
>
>>
>>
>> On Mon, Apr 24, 2017 at 12:57 PM, Evgenia Tokar 
>> wrote:
>>
>>>
>>> Thanks.
>>>
>>> 1. In the UI under vm devices tab do you have an entry for graphical
>>> device (type=spice)?
>>>
>>
>> It doesn't seem so...
>> Se the whole content:
>> https://drive.google.com/file/d/0BwoPbcrMv8mvblV3dDlMelVFS1U
>> /view?usp=sharing
>>
>>
> According to the vm devices list you sent here, there is also no entry
> for for the video device (device with type=qxl), although according to one
> of your previous mails, the vm "general" sub tab shows "Video Type: qxl".
>

I confirm that. But please note that in the same general sub tab the
"Graphics Protocol" appears as "None", while normally it should contain
"SPICE".
I resend the link of the general sub tab screenshot:
https://drive.google.com/file/d/0BwoPbcrMv8mvUURobHhKb0kxemM/
view?usp=sharing




>
> 1. Can you please check the vm console configuration to see if headless
> mode is off, just to make sure?  (in ui - edit the vm and check the console
> tab to see if the "Headless mode" is not checked).
>
> (*) headless mode is a new feature added to 4.1
>

I confirm headless is not checked.
See here (you see underneath also the general sub tab):
https://drive.google.com/file/d/0BwoPbcrMv8mvQVhzaGFHSmoxaGc/view?usp=sharing



> 2. what values are assigned in vm console tab for "Video Type" and
> "Graphics protocol" fields?
>

>From the above screenshot you see that they are "QXL" and "SPICE"


>
> Thanks,
> Sharon
>
>
>
You are welcome.
I have another environment with single server and she, with similar update
history and now at 4.1.1.6-1 level, where I had not the problem, but in
that environment the engine was configured as "VNC" and "Cirrus" so it was
not the same.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more engine console available

2017-04-24 Thread Sharon Gratch

Hi,


On Mon, Apr 24, 2017 at 6:06 PM, Gianluca Cecchi 
wrote:

>
>
> On Mon, Apr 24, 2017 at 12:57 PM, Evgenia Tokar  wrote:
>
>>
>> Thanks.
>>
>> 1. In the UI under vm devices tab do you have an entry for graphical
>> device (type=spice)?
>>
>
> It doesn't seem so...
> Se the whole content:
> https://drive.google.com/file/d/0BwoPbcrMv8mvblV3dDlMelVFS1U
> /view?usp=sharing
>
>
According to the vm devices list you sent here, there is also no entry for
for the video device (device with type=qxl), although according to one of
your previous mails, the vm "general" sub tab shows "Video Type: qxl".

1. Can you please check the vm console configuration to see if headless
mode is off, just to make sure?  (in ui - edit the vm and check the console
tab to see if the "Headless mode" is not checked).

(*) headless mode is a new feature added to 4.1

2. what values are assigned in vm console tab for "Video Type" and
"Graphics protocol" fields?

Thanks,
Sharon



>
>> 2. Can you paste again the contents of the local vm.conf? If you have a
>> graphical device in the engine it should appear there as well.
>>
>> Jenny
>>
>
> [root@ractor ovirt-hosted-engine-ha]# cat /run/ovirt-hosted-engine-ha/vm
> .conf
> cpuType=Nehalem
> emulatedMachine=pc-i440fx-rhel7.3.0
> vmId=7b0ff898-0a9e-4b97-8292-1d9f2a0a6683
> smp=4
> memSize=16384
> maxVCpus=16
> spiceSecureChannels=smain,sdisplay,sinputs,scursor,splayback
> ,srecord,ssmartcard,susbredir
> vmName=HostedEngine
> display=qxl
> devices={index:0,iface:virtio,format:raw,bootOrder:1,address
> :{slot:0x06,bus:0x00,domain:0x,type:pci,function:0x0},vo
> lumeID:43ee87b9-4293-4d43-beab-582f500667a7,imageID:d6287dfb
> -27af-461b-ab79-4eb3a45d8c8a,readonly:false,domainID:2025c2e
> a-6205-4bc1-b29d-745b47f8f806,deviceId:d6287dfb-27af-461b-
> ab79-4eb3a45d8c8a,poolID:----
> ,device:disk,shared:exclusive,propagateErrors:off,type:disk}
> devices={nicModel:pv,macAddr:00:16:3e:3a:ee:a5,linkActive:tr
> ue,network:ovirtmgmt,deviceId:4bbb90e6-4f8e-42e0-91ea-d89412
> 5ff4a8,address:{slot:0x03,bus:0x00,domain:0x,type:pci,fu
> nction:0x0},device:bridge,type:interface}
> devices={index:2,iface:ide,shared:false,readonly:true,device
> Id:8c3179ac-b322-4f5c-9449-c52e3665e0ae,address:{controller:
> 0,target:0,unit:0,bus:1,type:drive},device:cdrom,path:,type:disk}
> devices={device:usb,type:controller,deviceId:ee985889-6878-4
> 63a-a415-9b50a4a810b3,address:{slot:0x01,bus:0x00,domain:0x0
> 000,type:pci,function:0x2}}
> devices={device:virtio-serial,type:controller,deviceId:d9970
> 5cd-0ebf-40f0-950b-575ab4e6d934,address:{slot:0x05,bus:0x00,
> domain:0x,type:pci,function:0x0}}
> devices={device:ide,type:controller,deviceId:ef31f1a2-746a-4
> 188-ae45-ef157d7b5598,address:{slot:0x01,bus:0x00,domain:0x0
> 000,type:pci,function:0x1}}
> devices={device:scsi,model:virtio-scsi,type:controller,devic
> eId:f41baf47-51f8-42e9-a290-70da06191991,address:{slot:0x04,
> bus:0x00,domain:0x,type:pci,function:0x0}}
> devices={alias:rng0,specParams:{source:urandom},deviceId:4c7
> f0e81-c3e8-498f-a5a2-b8c1543e94b4,address:{slot:0x02,bus:0x0
> 0,domain:0x,type:pci,function:0x0},device:virtio,model:
> virtio,type:rng}
> devices={device:console,type:console}
> [root@ractor ovirt-hosted-engine-ha]#
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more engine console available

2017-04-24 Thread Gianluca Cecchi

On Mon, Apr 24, 2017 at 12:57 PM, Evgenia Tokar  wrote:

>
> Thanks.
>
> 1. In the UI under vm devices tab do you have an entry for graphical
> device (type=spice)?
>

It doesn't seem so...
Se the whole content:
https://drive.google.com/file/d/0BwoPbcrMv8mvblV3dDlMelVFS1U/view?usp=sharing



> 2. Can you paste again the contents of the local vm.conf? If you have a
> graphical device in the engine it should appear there as well.
>
> Jenny
>

[root@ractor ovirt-hosted-engine-ha]# cat
/run/ovirt-hosted-engine-ha/vm.conf
cpuType=Nehalem
emulatedMachine=pc-i440fx-rhel7.3.0
vmId=7b0ff898-0a9e-4b97-8292-1d9f2a0a6683
smp=4
memSize=16384
maxVCpus=16
spiceSecureChannels=smain,sdisplay,sinputs,scursor,splayback,srecord,ssmartcard,susbredir
vmName=HostedEngine
display=qxl
devices={index:0,iface:virtio,format:raw,bootOrder:1,address:{slot:0x06,bus:0x00,domain:0x,type:pci,function:0x0},volumeID:43ee87b9-4293-4d43-beab-582f500667a7,imageID:d6287dfb-27af-461b-ab79-4eb3a45d8c8a,readonly:false,domainID:2025c2ea-6205-4bc1-b29d-745b47f8f806,deviceId:d6287dfb-27af-461b-ab79-4eb3a45d8c8a,poolID:----,device:disk,shared:exclusive,propagateErrors:off,type:disk}
devices={nicModel:pv,macAddr:00:16:3e:3a:ee:a5,linkActive:true,network:ovirtmgmt,deviceId:4bbb90e6-4f8e-42e0-91ea-d894125ff4a8,address:{slot:0x03,bus:0x00,domain:0x,type:pci,function:0x0},device:bridge,type:interface}
devices={index:2,iface:ide,shared:false,readonly:true,deviceId:8c3179ac-b322-4f5c-9449-c52e3665e0ae,address:{controller:0,target:0,unit:0,bus:1,type:drive},device:cdrom,path:,type:disk}
devices={device:usb,type:controller,deviceId:ee985889-6878-463a-a415-9b50a4a810b3,address:{slot:0x01,bus:0x00,domain:0x,type:pci,function:0x2}}
devices={device:virtio-serial,type:controller,deviceId:d99705cd-0ebf-40f0-950b-575ab4e6d934,address:{slot:0x05,bus:0x00,domain:0x,type:pci,function:0x0}}
devices={device:ide,type:controller,deviceId:ef31f1a2-746a-4188-ae45-ef157d7b5598,address:{slot:0x01,bus:0x00,domain:0x,type:pci,function:0x1}}
devices={device:scsi,model:virtio-scsi,type:controller,deviceId:f41baf47-51f8-42e9-a290-70da06191991,address:{slot:0x04,bus:0x00,domain:0x,type:pci,function:0x0}}
devices={alias:rng0,specParams:{source:urandom},deviceId:4c7f0e81-c3e8-498f-a5a2-b8c1543e94b4,address:{slot:0x02,bus:0x00,domain:0x,type:pci,function:0x0},device:virtio,model:virtio,type:rng}
devices={device:console,type:console}
[root@ractor ovirt-hosted-engine-ha]#
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more engine console available

2017-04-24 Thread Evgenia Tokar

Thanks.

1. In the UI under vm devices tab do you have an entry for graphical device
(type=spice)?
2. Can you paste again the contents of the local vm.conf? If you have a
graphical device in the engine it should appear there as well.

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

Re: [ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more engine console available

2017-04-24 Thread Gianluca Cecchi

On Mon, Apr 24, 2017 at 10:38 AM, Evgenia Tokar  wrote:

> HI,
>
> Can you attach the agent log from the host?
>
> Thanks,
> Jenny
>
>
>
here it is:
https://drive.google.com/file/d/0BwoPbcrMv8mvamp1N0E5THVHNVE/view?usp=sharing
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more engine console available

2017-04-24 Thread Evgenia Tokar

HI,

Can you attach the agent log from the host?

Thanks,
Jenny

On Fri, Apr 21, 2017 at 12:52 AM, Gianluca Cecchi  wrote:

> Further infos:
>
> - ovirt-hosted-engine-ha package version
>
> [root@ractor ~]# rpm -q ovirt-hosted-engine-ha
> ovirt-hosted-engine-ha-2.1.0.5-1.el7.centos.noarch
> [root@ractor ~]#
>
>
> - serial console works
>
> [root@ractor ~]# hosted-engine --console
> The engine VM is running on this host
> Connected to domain HostedEngine
> Escape character is ^]
>
> CentOS Linux 7 (Core)
> Kernel 3.10.0-514.16.1.el7.x86_64 on an x86_64
>
> ractorshe login: root
> Password:
> Last login: Thu Apr 20 19:14:27 on pts/0
> [root@ractorshe ~]#
>
>
> - Current runtime vm.conf for hosted engine vm
>
> [root@ractor ~]# cat /run/ovirt-hosted-engine-ha/vm.conf
> cpuType=Nehalem
> emulatedMachine=pc-i440fx-rhel7.3.0
> vmId=7b0ff898-0a9e-4b97-8292-1d9f2a0a6683
> smp=4
> memSize=16384
> maxVCpus=16
> spiceSecureChannels=smain,sdisplay,sinputs,scursor,
> splayback,srecord,ssmartcard,susbredir
> vmName=HostedEngine
> display=qxl
> devices={index:0,iface:virtio,format:raw,bootOrder:1,
> address:{slot:0x06,bus:0x00,domain:0x,type:pci,function:0x0},volumeID:
> 43ee87b9-4293-4d43-beab-582f500667a7,imageID:d6287dfb-
> 27af-461b-ab79-4eb3a45d8c8a,readonly:false,domainID:
> 2025c2ea-6205-4bc1-b29d-745b47f8f806,deviceId:d6287dfb-27af-461b-ab79-
> 4eb3a45d8c8a,poolID:----,
> device:disk,shared:exclusive,propagateErrors:off,type:disk}
> devices={nicModel:pv,macAddr:00:16:3e:3a:ee:a5,linkActive:
> true,network:ovirtmgmt,deviceId:4bbb90e6-4f8e-42e0-
> 91ea-d894125ff4a8,address:{slot:0x03,bus:0x00,domain:
> 0x,type:pci,function:0x0},device:bridge,type:interface}
> devices={index:2,iface:ide,shared:false,readonly:true,
> deviceId:8c3179ac-b322-4f5c-9449-c52e3665e0ae,address:{
> controller:0,target:0,unit:0,bus:1,type:drive},device:
> cdrom,path:,type:disk}
> devices={device:usb,type:controller,deviceId:ee985889-
> 6878-463a-a415-9b50a4a810b3,address:{slot:0x01,bus:0x00,
> domain:0x,type:pci,function:0x2}}
> devices={device:virtio-serial,type:controller,deviceId:
> d99705cd-0ebf-40f0-950b-575ab4e6d934,address:{slot:
> 0x05,bus:0x00,domain:0x,type:pci,function:0x0}}
> devices={device:ide,type:controller,deviceId:ef31f1a2-
> 746a-4188-ae45-ef157d7b5598,address:{slot:0x01,bus:0x00,
> domain:0x,type:pci,function:0x1}}
> devices={device:scsi,model:virtio-scsi,type:controller,
> deviceId:f41baf47-51f8-42e9-a290-70da06191991,address:{
> slot:0x04,bus:0x00,domain:0x,type:pci,function:0x0}}
> devices={alias:rng0,specParams:{source:urandom},
> deviceId:4c7f0e81-c3e8-498f-a5a2-b8c1543e94b4,address:{
> slot:0x02,bus:0x00,domain:0x,type:pci,function:0x0},
> device:virtio,model:virtio,type:rng}
> devices={device:console,type:console}
> [root@ractor ~]#
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more engine console available

2017-04-20 Thread Gianluca Cecchi

Further infos:

- ovirt-hosted-engine-ha package version

[root@ractor ~]# rpm -q ovirt-hosted-engine-ha
ovirt-hosted-engine-ha-2.1.0.5-1.el7.centos.noarch
[root@ractor ~]#


- serial console works

[root@ractor ~]# hosted-engine --console
The engine VM is running on this host
Connected to domain HostedEngine
Escape character is ^]

CentOS Linux 7 (Core)
Kernel 3.10.0-514.16.1.el7.x86_64 on an x86_64

ractorshe login: root
Password:
Last login: Thu Apr 20 19:14:27 on pts/0
[root@ractorshe ~]#


- Current runtime vm.conf for hosted engine vm

[root@ractor ~]# cat /run/ovirt-hosted-engine-ha/vm.conf
cpuType=Nehalem
emulatedMachine=pc-i440fx-rhel7.3.0
vmId=7b0ff898-0a9e-4b97-8292-1d9f2a0a6683
smp=4
memSize=16384
maxVCpus=16
spiceSecureChannels=smain,sdisplay,sinputs,scursor,splayback,srecord,ssmartcard,susbredir
vmName=HostedEngine
display=qxl
devices={index:0,iface:virtio,format:raw,bootOrder:1,address:{slot:0x06,bus:0x00,domain:0x,type:pci,function:0x0},volumeID:43ee87b9-4293-4d43-beab-582f500667a7,imageID:d6287dfb-27af-461b-ab79-4eb3a45d8c8a,readonly:false,domainID:2025c2ea-6205-4bc1-b29d-745b47f8f806,deviceId:d6287dfb-27af-461b-ab79-4eb3a45d8c8a,poolID:----,device:disk,shared:exclusive,propagateErrors:off,type:disk}
devices={nicModel:pv,macAddr:00:16:3e:3a:ee:a5,linkActive:true,network:ovirtmgmt,deviceId:4bbb90e6-4f8e-42e0-91ea-d894125ff4a8,address:{slot:0x03,bus:0x00,domain:0x,type:pci,function:0x0},device:bridge,type:interface}
devices={index:2,iface:ide,shared:false,readonly:true,deviceId:8c3179ac-b322-4f5c-9449-c52e3665e0ae,address:{controller:0,target:0,unit:0,bus:1,type:drive},device:cdrom,path:,type:disk}
devices={device:usb,type:controller,deviceId:ee985889-6878-463a-a415-9b50a4a810b3,address:{slot:0x01,bus:0x00,domain:0x,type:pci,function:0x2}}
devices={device:virtio-serial,type:controller,deviceId:d99705cd-0ebf-40f0-950b-575ab4e6d934,address:{slot:0x05,bus:0x00,domain:0x,type:pci,function:0x0}}
devices={device:ide,type:controller,deviceId:ef31f1a2-746a-4188-ae45-ef157d7b5598,address:{slot:0x01,bus:0x00,domain:0x,type:pci,function:0x1}}
devices={device:scsi,model:virtio-scsi,type:controller,deviceId:f41baf47-51f8-42e9-a290-70da06191991,address:{slot:0x04,bus:0x00,domain:0x,type:pci,function:0x0}}
devices={alias:rng0,specParams:{source:urandom},deviceId:4c7f0e81-c3e8-498f-a5a2-b8c1543e94b4,address:{slot:0x02,bus:0x00,domain:0x,type:pci,function:0x0},device:virtio,model:virtio,type:rng}
devices={device:console,type:console}
[root@ractor ~]#
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more engine console available

2017-04-20 Thread Arsène Gschwind


Hi,

You just need to patch ovf2VmParams.py the other 3 files are just for 
testing purpose.

Don't forget to restart *ovirt-ha-agent* service before starting HE VM.

Rgds,
Arsène


On 04/20/2017 07:19 PM, Gianluca Cecchi wrote:
On Wed, Apr 19, 2017 at 4:26 PM, Arsène Gschwind 
> wrote:


I did start the hosted engine on the host I've applied the patch
but I've forgot to restart ovirt-ha-agent, and now it works.

Great job, thanks

Best regards,
Arsène



Hello,
I have the same on my single host hosted engine environment, after 
passing from 4.1.0 to 4.1.1

I tried to change the file as in gerrit entry

/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/ovf/ovf2VmParams.py

[root@ractor ovf]# diff ovf2VmParams.py ovf2VmParams.py.bck
164,168d163
< def buildGraphics(device):
< graphics = buildDevice(device)
< return graphics
<
<
257,258d251
< elif t == 'graphics':
< devices.append(buildGraphics(device))

I don't find in my environment the other 3 files
ovf2VmParams_test.py
ovf_test.xml
ovf_test_max_vcpu.xml

Then I
set global maintenance
restart ovirt-guest-agent
shutdown engine vm
exit global maintenance
the engine vm starts up and I'm able to connect, but its console still 
grey




--

*Arsène Gschwind*
Fa. Sapify AG im Auftrag der Universität Basel
IT Services
Klingelbergstr. 70 |  CH-4056 Basel  |  Switzerland
Tel. +41 79 449 25 63  | http://its.unibas.ch 
ITS-ServiceDesk: support-...@unibas.ch | +41 61 267 14 11

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

Re: [ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more engine console available

2017-04-20 Thread Martin Sivak

Are you sure you restarted the proper services?

I see -nographic in the qemu command line and you mentioned
ovirt-guest-agent intead of ovirt-ha-agent..

Best regards

Martin Sivak

On Thu, Apr 20, 2017 at 7:25 PM, Gianluca Cecchi
 wrote:
>
>
> On Thu, Apr 20, 2017 at 7:19 PM, Gianluca Cecchi 
> wrote:
>>
>> On Wed, Apr 19, 2017 at 4:26 PM, Arsène Gschwind
>>  wrote:
>>>
>>> I did start the hosted engine on the host I've applied the patch but I've
>>> forgot to restart ovirt-ha-agent, and now it works.
>>>
>>> Great job, thanks
>>>
>>> Best regards,
>>> Arsène
>>>
>>>
>>
>> Hello,
>> I have the same on my single host hosted engine environment, after passing
>> from 4.1.0 to 4.1.1
>>
>>
>>
>
> BTW the qemu command line generated for hosted engine is :
>
> qemu 23686 1 82 19:11 ?00:00:15 /usr/libexec/qemu-kvm -name
> guest=HostedEngine,debug-threads=on -S -object
> secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-8-HostedEngine/master-key.aes
> -machine pc-i440fx-rhel7.3.0,accel=kvm,usb=off -cpu Nehalem -m 16384
> -realtime mlock=off -smp 4,maxcpus=16,sockets=16,cores=1,threads=1 -uuid
> 7b0ff898-0a9e-4b97-8292-1d9f2a0a6683 -smbios
> type=1,manufacturer=oVirt,product=oVirt
> Node,version=7-3.1611.el7.centos,serial=4C4C4544-0054-5910-8056-C4C04F30354A,uuid=7b0ff898-0a9e-4b97-8292-1d9f2a0a6683
> -nographic -no-user-config -nodefaults -chardev
> socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-8-HostedEngine/monitor.sock,server,nowait
> -mon chardev=charmonitor,id=monitor,mode=control -rtc
> base=2017-04-20T17:11:49,driftfix=slew -global
> kvm-pit.lost_tick_policy=discard -no-hpet -no-reboot -boot strict=on -device
> piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device
> virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x4 -device
> virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x5 -drive
> file=/var/run/vdsm/storage/2025c2ea-6205-4bc1-b29d-745b47f8f806/d6287dfb-27af-461b-ab79-4eb3a45d8c8a/43ee87b9-4293-4d43-beab-582f500667a7,format=raw,if=none,id=drive-virtio-disk0,serial=d6287dfb-27af-461b-ab79-4eb3a45d8c8a,cache=none,werror=stop,rerror=stop,aio=threads
> -device
> virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
> -drive if=none,id=drive-ide0-1-0,readonly=on -device
> ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev
> tap,fd=30,id=hostnet0,vhost=on,vhostfd=33 -device
> virtio-net-pci,netdev=hostnet0,id=net0,mac=00:16:3e:3a:ee:a5,bus=pci.0,addr=0x3
> -chardev
> socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/7b0ff898-0a9e-4b97-8292-1d9f2a0a6683.com.redhat.rhevm.vdsm,server,nowait
> -device
> virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.rhevm.vdsm
> -chardev
> socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/7b0ff898-0a9e-4b97-8292-1d9f2a0a6683.org.qemu.guest_agent.0,server,nowait
> -device
> virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=org.qemu.guest_agent.0
> -chardev
> socket,id=charchannel2,path=/var/lib/libvirt/qemu/channels/7b0ff898-0a9e-4b97-8292-1d9f2a0a6683.org.ovirt.hosted-engine-setup.0,server,nowait
> -device
> virtserialport,bus=virtio-serial0.0,nr=3,chardev=charchannel2,id=channel2,name=org.ovirt.hosted-engine-setup.0
> -chardev pty,id=charconsole0 -device
> virtconsole,chardev=charconsole0,id=console0 -object
> rng-random,id=objrng0,filename=/dev/urandom -device
> virtio-rng-pci,rng=objrng0,id=rng0,bus=pci.0,addr=0x2 -msg timestamp=on
>
>
> and in /var/log/libvirt/qemu/HostedEngine.log
>
> 2017-04-20 17:11:49.947+: starting up libvirt version: 2.0.0, package:
> 10.el7_3.5 (CentOS BuildSystem ,
> 2017-03-03-02:09:45, c1bm.rdu2.centos.org), qemu version: 2.6.0
> (qemu-kvm-ev-2.6.0-28.el7_3.6.1), hostname: ractor.mydomain
> LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
> QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -name
> guest=HostedEngine,debug-threads=on -S -object
> secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-8-HostedEngine/master-key.aes
> -machine pc-i440fx-rhel7.3.0,accel=kvm,usb=off -cpu Nehalem -m 16384
> -realtime mlock=off -smp 4,maxcpus=16,sockets=16,cores=1,threads=1 -uuid
> 7b0ff898-0a9e-4b97-8292-1d9f2a0a6683 -smbios
> 'type=1,manufacturer=oVirt,product=oVirt
> Node,version=7-3.1611.el7.centos,serial=4C4C4544-0054-5910-8056-C4C04F30354A,uuid=7b0ff898-0a9e-4b97-8292-1d9f2a0a6683'
> -nographic -no-user-config -nodefaults -chardev
> socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-8-HostedEngine/monitor.sock,server,nowait
> -mon chardev=charmonitor,id=monitor,mode=control -rtc
> base=2017-04-20T17:11:49,driftfix=slew -global
> kvm-pit.lost_tick_policy=discard -no-hpet -no-reboot -boot strict=on -device
> piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device
> virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x4 -device
>

Re: [ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more engine console available

2017-04-20 Thread Gianluca Cecchi

On Thu, Apr 20, 2017 at 7:19 PM, Gianluca Cecchi 
wrote:

> On Wed, Apr 19, 2017 at 4:26 PM, Arsène Gschwind <
> arsene.gschw...@unibas.ch> wrote:
>
>> I did start the hosted engine on the host I've applied the patch but I've
>> forgot to restart ovirt-ha-agent, and now it works.
>>
>> Great job, thanks
>>
>> Best regards,
>> Arsène
>>
>>
> Hello,
> I have the same on my single host hosted engine environment, after passing
> from 4.1.0 to 4.1.1
>
>
>
>
BTW the qemu command line generated for hosted engine is :

qemu 23686 1 82 19:11 ?00:00:15 /usr/libexec/qemu-kvm -name
guest=HostedEngine,debug-threads=on -S -object
secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-8-HostedEngine/master-key.aes
-machine pc-i440fx-rhel7.3.0,accel=kvm,usb=off -cpu Nehalem -m 16384
-realtime mlock=off -smp 4,maxcpus=16,sockets=16,cores=1,threads=1 -uuid
7b0ff898-0a9e-4b97-8292-1d9f2a0a6683 -smbios
type=1,manufacturer=oVirt,product=oVirt
Node,version=7-3.1611.el7.centos,serial=4C4C4544-0054-5910-8056-C4C04F30354A,uuid=7b0ff898-0a9e-4b97-8292-1d9f2a0a6683
-nographic -no-user-config -nodefaults -chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-8-HostedEngine/monitor.sock,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -rtc
base=2017-04-20T17:11:49,driftfix=slew -global
kvm-pit.lost_tick_policy=discard -no-hpet -no-reboot -boot strict=on
-device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device
virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x4 -device
virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x5 -drive
file=/var/run/vdsm/storage/2025c2ea-6205-4bc1-b29d-745b47f8f806/d6287dfb-27af-461b-ab79-4eb3a45d8c8a/43ee87b9-4293-4d43-beab-582f500667a7,format=raw,if=none,id=drive-virtio-disk0,serial=d6287dfb-27af-461b-ab79-4eb3a45d8c8a,cache=none,werror=stop,rerror=stop,aio=threads
-device
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
-drive if=none,id=drive-ide0-1-0,readonly=on -device
ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev
tap,fd=30,id=hostnet0,vhost=on,vhostfd=33 -device
virtio-net-pci,netdev=hostnet0,id=net0,mac=00:16:3e:3a:ee:a5,bus=pci.0,addr=0x3
-chardev
socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/7b0ff898-0a9e-4b97-8292-1d9f2a0a6683.com.redhat.rhevm.vdsm,server,nowait
-device
virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.rhevm.vdsm
-chardev
socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/7b0ff898-0a9e-4b97-8292-1d9f2a0a6683.org.qemu.guest_agent.0,server,nowait
-device
virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=org.qemu.guest_agent.0
-chardev
socket,id=charchannel2,path=/var/lib/libvirt/qemu/channels/7b0ff898-0a9e-4b97-8292-1d9f2a0a6683.org.ovirt.hosted-engine-setup.0,server,nowait
-device
virtserialport,bus=virtio-serial0.0,nr=3,chardev=charchannel2,id=channel2,name=org.ovirt.hosted-engine-setup.0
-chardev pty,id=charconsole0 -device
virtconsole,chardev=charconsole0,id=console0 -object
rng-random,id=objrng0,filename=/dev/urandom -device
virtio-rng-pci,rng=objrng0,id=rng0,bus=pci.0,addr=0x2 -msg timestamp=on


and in /var/log/libvirt/qemu/HostedEngine.log

2017-04-20 17:11:49.947+: starting up libvirt version: 2.0.0, package:
10.el7_3.5 (CentOS BuildSystem ,
2017-03-03-02:09:45, c1bm.rdu2.centos.org), qemu version: 2.6.0
(qemu-kvm-ev-2.6.0-28.el7_3.6.1), hostname: ractor.mydomain
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -name
guest=HostedEngine,debug-threads=on -S -object
secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-8-HostedEngine/master-key.aes
-machine pc-i440fx-rhel7.3.0,accel=kvm,usb=off -cpu Nehalem -m 16384
-realtime mlock=off -smp 4,maxcpus=16,sockets=16,cores=1,threads=1 -uuid
7b0ff898-0a9e-4b97-8292-1d9f2a0a6683 -smbios
'type=1,manufacturer=oVirt,product=oVirt
Node,version=7-3.1611.el7.centos,serial=4C4C4544-0054-5910-8056-C4C04F30354A,uuid=7b0ff898-0a9e-4b97-8292-1d9f2a0a6683'
-nographic -no-user-config -nodefaults -chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-8-HostedEngine/monitor.sock,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -rtc
base=2017-04-20T17:11:49,driftfix=slew -global
kvm-pit.lost_tick_policy=discard -no-hpet -no-reboot -boot strict=on
-device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device
virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x4 -device
virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x5 -drive
file=/var/run/vdsm/storage/2025c2ea-6205-4bc1-b29d-745b47f8f806/d6287dfb-27af-461b-ab79-4eb3a45d8c8a/43ee87b9-4293-4d43-beab-582f500667a7,format=raw,if=none,id=drive-virtio-disk0,serial=d6287dfb-27af-461b-ab79-4eb3a45d8c8a,cache=none,werror=stop,rerror=stop,aio=threads
-device

Re: [ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more engine console available

2017-04-20 Thread Gianluca Cecchi

On Wed, Apr 19, 2017 at 4:26 PM, Arsène Gschwind 
wrote:

> I did start the hosted engine on the host I've applied the patch but I've
> forgot to restart ovirt-ha-agent, and now it works.
>
> Great job, thanks
>
> Best regards,
> Arsène
>
>
Hello,
I have the same on my single host hosted engine environment, after passing
from 4.1.0 to 4.1.1
I tried to change the file as in gerrit entry

/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/ovf/ovf2VmParams.py

[root@ractor ovf]# diff ovf2VmParams.py ovf2VmParams.py.bck
164,168d163
< def buildGraphics(device):
< graphics = buildDevice(device)
< return graphics
<
<
257,258d251
< elif t == 'graphics':
< devices.append(buildGraphics(device))

I don't find in my environment the other 3 files
ovf2VmParams_test.py
ovf_test.xml
ovf_test_max_vcpu.xml

Then I
set global maintenance
restart ovirt-guest-agent
shutdown engine vm
exit global maintenance
the engine vm starts up and I'm able to connect, but its console still
grey
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more engine console available

2017-04-19 Thread Arsène Gschwind

I did start the hosted engine on the host I've applied the patch but
I've forgot to restart ovirt-ha-agent, and now it works.

Great job, thanks

Best regards,
Arsène

On 04/19/2017 03:39 PM, Martin Sivak wrote:
> I've applied the patch on one off my host and restarted the hosted
engine as you wrote but it didn't help,

> the console button is still grayed out and not available.

Are you sure the host with the patch applied was used to start the
engine? Btw, you need to restart the ovirt-ha-agent service first
before restarting the engine VM.

Best regards

Martin Sivak

On Wed, Apr 19, 2017 at 3:17 PM, Arsène Gschwind
> wrote:

Hi,

I've applied the patch on one off my host and restarted the hosted
engine as you wrote but it didn't help, the console button is
still grayed out and not available.

Rgds,
Arsène

On 04/18/2017 02:20 PM, Evgenia Tokar wrote:

Hi,

Thanks for bringing the issue to our attention and for answering
the questions.

There is a patch to fix this: https://gerrit.ovirt.org/#/c/75515/

After applying the patch a restart to the hosted engine vm is
required (not just the engine).

Let me know if you are still experiencing issues with this.

Thanks,
Jenny

On Wed, Apr 12, 2017 at 8:05 PM, Rafał Wojciechowski
> wrote:

hi,

I will answer also. however I am using single hypervisor so
without ha and I have no performed steps:
https://www.ovirt.org/documentation/how-to/hosted-engine/

1. yes - however I have to start in headless mode so it is
quite obvius
if I am trying to start with spice/vnc console I am getting
segfault from libvirtd
2. as above
3. as above

W dniu 12.04.2017 o 14:12, Arsène Gschwind pisze:

Hi all,

I will answer your questions:

1. definitively yes
2. the command hosted-engine --console works well and I'm
able to connect.
3. Here are the device entries

devices={device:qxl,alias:video0,type:video,deviceId:5210a3c3-9cc4-4aed-90c6-432dd2d37c46,address:{slot:0x02,
bus:0x00,domain:0x,type:pci,function:0x0}}
devices={device:console,type:console}

Thanks and rgds,
Arsène

On 04/12/2017 10:53 AM, Evgenia Tokar wrote:

Hi all,

I have managed to reproduce this issue and opened a bug for
tracking it:
https://bugzilla.redhat.com/show_bug.cgi?id=1441570
.

There is no solution yet, but I would appreciate if any who
encountered this issue will answer some questions:
1. Is the console button greyed out in the UI?
2. On the hosted engine host, does the command
hosted-engine --console fails?
If it fails, try upgrading ovirt-hosted-engine-ha on
the hosted engine host. We had a bug related to this issue
that was fixed
(https://bugzilla.redhat.com/show_bug.cgi?id=1364132
).
After upgrade and restart of the vm, this should work,
and you should be able to connect to the console.
3. On the hosted engine host look at the content of:
/var/run/ovirt-hosted-engine-ha/vm.conf
Does it contain a graphical device? Or a console device?

Thanks,
Jenny

On Mon, Apr 10, 2017 at 11:44 AM, Martin Sivak
> wrote:

Hi,

we are working on that, we can only ask for patience
now, Jenny was trying to find out what happened and how
to fix it all week.

Best regards

--
Martin Sivak
SLA / oVirt

On Mon, Apr 10, 2017 at 9:38 AM, Rafał Wojciechowski
> wrote:

hi,

I have similiar issue(I also started my mailthread)
after upgrade 4.0 to 4.1

Version 4.1.1.8-1.el7.centos (before it was some
4.1.0.x or similiar - update not fixed it)

to run VM I have to set in Console tab Headless
mode - without it I got libvirtd segfault(logs
attached in my mailthread).

So I am able to run VMs only without Console - do
you also have to set headless before run VM?

I noticed that libvirt-daemon was also upgraded to
2.0 version during ovirt upgrade - I dont think
that 4.1 was not

Re: [ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more engine console available

2017-04-19 Thread Martin Sivak

> I've applied the patch on one off my host and restarted the hosted engine
as you wrote but it didn't help,
> the console button   is still grayed out and not available.

Are you sure the host with the patch applied was used to start the engine?
Btw, you need to restart the ovirt-ha-agent service first before restarting
the engine VM.

Best regards

Martin Sivak

On Wed, Apr 19, 2017 at 3:17 PM, Arsène Gschwind 
wrote:

> Hi,
>
> I've applied the patch on one off my host and restarted the hosted engine
> as you wrote but it didn't help, the console button is still grayed out and
> not available.
>
> Rgds,
> Arsène
>
> On 04/18/2017 02:20 PM, Evgenia Tokar wrote:
>
> Hi,
>
> Thanks for bringing the issue to our attention and for answering the
> questions.
>
> There is a patch to fix this: https://gerrit.ovirt.org/#/c/75515/
> After applying the patch a restart to the hosted engine vm is required
> (not just the engine).
>
> Let me know if you are still experiencing issues with this.
>
> Thanks,
> Jenny
>
>
> On Wed, Apr 12, 2017 at 8:05 PM, Rafał Wojciechowski <
> i...@rafalwojciechowski.pl> wrote:
>
>> hi,
>>
>> I will answer also. however I am using single hypervisor so without ha
>> and I have no performed steps:
>> https://www.ovirt.org/documentation/how-to/hosted-engine/
>>
>> 1. yes - however I have to start in headless mode so it is quite obvius
>> if I am trying to start with spice/vnc console I am getting segfault from
>> libvirtd
>> 2. as above
>> 3. as above
>>
>> W dniu 12.04.2017 o 14:12, Arsène Gschwind pisze:
>>
>> Hi all,
>>
>> I will answer your questions:
>>
>> 1. definitively yes
>> 2. the command hosted-engine --console works well and I'm able to connect.
>> 3. Here are the device entries
>>
>> devices={device:qxl,alias:video0,type:video,deviceId:5210a3c
>> 3-9cc4-4aed-90c6-432dd2d37c46,address:{slot:0x02,
>> bus:0x00,domain:0x,type:pci,function:0x0}}
>> devices={device:console,type:console}
>>
>> Thanks and rgds,
>> Arsène
>> On 04/12/2017 10:53 AM, Evgenia Tokar wrote:
>>
>> Hi all,
>>
>> I have managed to reproduce this issue and opened a bug for tracking it:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1441570 .
>>
>> There is no solution yet, but I would appreciate if any who encountered
>> this issue will answer some questions:
>> 1. Is the console button greyed out in the UI?
>> 2. On the hosted engine host, does the command hosted-engine --console
>> fails?
>>  If it fails, try upgrading ovirt-hosted-engine-ha on the hosted
>> engine host. We had a bug related to this issue that was fixed (
>> https://bugzilla.redhat.com/show_bug.cgi?id=1364132).
>>  After upgrade and restart of the vm, this should work, and you
>> should be able to connect to the console.
>> 3. On the hosted engine host look at the content of:
>> /var/run/ovirt-hosted-engine-ha/vm.conf
>> Does it contain a graphical device? Or a console device?
>>
>> Thanks,
>> Jenny
>>
>>
>> On Mon, Apr 10, 2017 at 11:44 AM, Martin Sivak  wrote:
>>
>>> Hi,
>>>
>>> we are working on that, we can only ask for patience now, Jenny was
>>> trying to find out what happened and how to fix it all week.
>>>
>>> Best regards
>>>
>>> --
>>> Martin Sivak
>>> SLA / oVirt
>>>
>>> On Mon, Apr 10, 2017 at 9:38 AM, Rafał Wojciechowski <
>>> i...@rafalwojciechowski.pl> wrote:
>>>
 hi,

 I have similiar issue(I also started my mailthread) after upgrade 4.0
 to 4.1

 Version 4.1.1.8-1.el7.centos (before it was some 4.1.0.x or similiar -
 update not fixed it)
 to run VM I have to set in Console tab Headless mode - without it I got
 libvirtd segfault(logs attached in my mailthread).

 So I am able to run VMs only without Console - do you also have to set
 headless before run VM?

 I noticed that libvirt-daemon was also upgraded to 2.0 version during
 ovirt upgrade - I dont think that 4.1 was not testes due to such libvirtd
 upgrade... but maybe?

 Regards,
 Rafal Wojciechowski

 W dniu 10.04.2017 o 08:24, Arsène Gschwind pisze:

 Hi,

 After updating to oVirt 4.1.1 Async release i can confirm that the
 problem still persists.

 Rgds,
 Arsène

 On 03/25/2017 12:25 PM, Arsène Gschwind wrote:

 Hi,
 After updating to 4.1.1 i'm observing the same behavior, HE without any
 console.
 Even when trying to edit the HE VMs it doesn't change anything,
 Graphics stays to NONE.

 Thanks for any Help.

 Regards,
 Arsène

 On 03/24/2017 03:11 PM, Nelson Lameiras wrote:

 Hello,

 When upgrading my test setup from 4.0 to 4.1, my engine vm lost it's
 console (from SPICE to None in GUI)

 My test setup :
 2 manually built hosts using centos 7.3, ovirt 4.1
 1 manually built hosted engine centos 7.3, oVirt 4.1.0.4-el7,
 accessible with SPICE console via GUI

 I updated

Re: [ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more engine console available

2017-04-19 Thread Martin Sivak

Hi Rafal,

segfaulting libvirt seems to be something different. Can you please start a
separate thread about it or open a bugzilla?

Best regards

Martin Sivak

On Tue, Apr 18, 2017 at 4:52 PM, Rafał Wojciechowski <
i...@rafalwojciechowski.pl> wrote:

> hi,
>
> I applied it for 
> /usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/ovf/
> content, then rebooted, reinstalled host in ovirt engine web administrator,
> again rebooted and tried again but I have still the same issue with
> libvirtd segfault
>
>
> Regards,
> Rafal Wojciechowski
>
>
> W dniu 18.04.2017 o 14:20, Evgenia Tokar pisze:
>
> Hi,
>
> Thanks for bringing the issue to our attention and for answering the
> questions.
>
> There is a patch to fix this: https://gerrit.ovirt.org/#/c/75515/
> After applying the patch a restart to the hosted engine vm is required
> (not just the engine).
>
> Let me know if you are still experiencing issues with this.
>
> Thanks,
> Jenny
>
>
> On Wed, Apr 12, 2017 at 8:05 PM, Rafał Wojciechowski <
> i...@rafalwojciechowski.pl> wrote:
>
>> hi,
>>
>> I will answer also. however I am using single hypervisor so without ha
>> and I have no performed steps:
>> https://www.ovirt.org/documentation/how-to/hosted-engine/
>>
>> 1. yes - however I have to start in headless mode so it is quite obvius
>> if I am trying to start with spice/vnc console I am getting segfault from
>> libvirtd
>> 2. as above
>> 3. as above
>>
>> W dniu 12.04.2017 o 14:12, Arsène Gschwind pisze:
>>
>> Hi all,
>>
>> I will answer your questions:
>>
>> 1. definitively yes
>> 2. the command hosted-engine --console works well and I'm able to connect.
>> 3. Here are the device entries
>>
>> devices={device:qxl,alias:video0,type:video,deviceId:5210a3c
>> 3-9cc4-4aed-90c6-432dd2d37c46,address:{slot:0x02,
>> bus:0x00,domain:0x,type:pci,function:0x0}}
>> devices={device:console,type:console}
>>
>> Thanks and rgds,
>> Arsène
>> On 04/12/2017 10:53 AM, Evgenia Tokar wrote:
>>
>> Hi all,
>>
>> I have managed to reproduce this issue and opened a bug for tracking it:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1441570 .
>>
>> There is no solution yet, but I would appreciate if any who encountered
>> this issue will answer some questions:
>> 1. Is the console button greyed out in the UI?
>> 2. On the hosted engine host, does the command hosted-engine --console
>> fails?
>>  If it fails, try upgrading ovirt-hosted-engine-ha on the hosted
>> engine host. We had a bug related to this issue that was fixed (
>> https://bugzilla.redhat.com/show_bug.cgi?id=1364132).
>>  After upgrade and restart of the vm, this should work, and you
>> should be able to connect to the console.
>> 3. On the hosted engine host look at the content of:
>> /var/run/ovirt-hosted-engine-ha/vm.conf
>> Does it contain a graphical device? Or a console device?
>>
>> Thanks,
>> Jenny
>>
>>
>> On Mon, Apr 10, 2017 at 11:44 AM, Martin Sivak  wrote:
>>
>>> Hi,
>>>
>>> we are working on that, we can only ask for patience now, Jenny was
>>> trying to find out what happened and how to fix it all week.
>>>
>>> Best regards
>>>
>>> --
>>> Martin Sivak
>>> SLA / oVirt
>>>
>>> On Mon, Apr 10, 2017 at 9:38 AM, Rafał Wojciechowski <
>>> i...@rafalwojciechowski.pl> wrote:
>>>
 hi,

 I have similiar issue(I also started my mailthread) after upgrade 4.0
 to 4.1

 Version 4.1.1.8-1.el7.centos (before it was some 4.1.0.x or similiar -
 update not fixed it)
 to run VM I have to set in Console tab Headless mode - without it I got
 libvirtd segfault(logs attached in my mailthread).

 So I am able to run VMs only without Console - do you also have to set
 headless before run VM?

 I noticed that libvirt-daemon was also upgraded to 2.0 version during
 ovirt upgrade - I dont think that 4.1 was not testes due to such libvirtd
 upgrade... but maybe?

 Regards,
 Rafal Wojciechowski

 W dniu 10.04.2017 o 08:24, Arsène Gschwind pisze:

 Hi,

 After updating to oVirt 4.1.1 Async release i can confirm that the
 problem still persists.

 Rgds,
 Arsène

 On 03/25/2017 12:25 PM, Arsène Gschwind wrote:

 Hi,
 After updating to 4.1.1 i'm observing the same behavior, HE without any
 console.
 Even when trying to edit the HE VMs it doesn't change anything,
 Graphics stays to NONE.

 Thanks for any Help.

 Regards,
 Arsène

 On 03/24/2017 03:11 PM, Nelson Lameiras wrote:

 Hello,

 When upgrading my test setup from 4.0 to 4.1, my engine vm lost it's
 console (from SPICE to None in GUI)

 My test setup :
 2 manually built hosts using centos 7.3, ovirt 4.1
 1 manually built hosted engine centos 7.3, oVirt 4.1.0.4-el7,
 accessible with SPICE console via GUI

 I updated ovirt-engine from 4.1.0 to 4.1.1 by doing on engine :
 - yum update
 - engine-setup
 - reboot

Re: [ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more engine console available

2017-04-19 Thread Arsène Gschwind

Hi,

I've applied the patch on one off my host and restarted the hosted
engine as you wrote but it didn't help, the console button is still
grayed out and not available.

Rgds,
Arsène

On 04/18/2017 02:20 PM, Evgenia Tokar wrote:

Hi,

Thanks for bringing the issue to our attention and for answering the
questions.

There is a patch to fix this: https://gerrit.ovirt.org/#/c/75515/
After applying the patch a restart to the hosted engine vm is required
(not just the engine).

Let me know if you are still experiencing issues with this.

Thanks,
Jenny

On Wed, Apr 12, 2017 at 8:05 PM, Rafał Wojciechowski
> wrote:

hi,

I will answer also. however I am using single hypervisor so
without ha and I have no performed steps:
https://www.ovirt.org/documentation/how-to/hosted-engine/

1. yes - however I have to start in headless mode so it is quite
obvius
if I am trying to start with spice/vnc console I am getting
segfault from libvirtd
2. as above
3. as above

W dniu 12.04.2017 o 14:12, Arsène Gschwind pisze:

Hi all,

I will answer your questions:

1. definitively yes
2. the command hosted-engine --console works well and I'm able to
connect.
3. Here are the device entries

devices={device:qxl,alias:video0,type:video,deviceId:5210a3c3-9cc4-4aed-90c6-432dd2d37c46,address:{slot:0x02,
bus:0x00,domain:0x,type:pci,function:0x0}}
devices={device:console,type:console}

Thanks and rgds,
Arsène

On 04/12/2017 10:53 AM, Evgenia Tokar wrote:

Hi all,

I have managed to reproduce this issue and opened a bug for
tracking it: https://bugzilla.redhat.com/show_bug.cgi?id=1441570
.

There is no solution yet, but I would appreciate if any who
encountered this issue will answer some questions:
1. Is the console button greyed out in the UI?
2. On the hosted engine host, does the command hosted-engine
--console fails?
If it fails, try upgrading ovirt-hosted-engine-ha on the
hosted engine host. We had a bug related to this issue that was
fixed (https://bugzilla.redhat.com/show_bug.cgi?id=1364132
).
After upgrade and restart of the vm, this should work, and
you should be able to connect to the console.
3. On the hosted engine host look at the content of:
/var/run/ovirt-hosted-engine-ha/vm.conf
Does it contain a graphical device? Or a console device?

Thanks,
Jenny

On Mon, Apr 10, 2017 at 11:44 AM, Martin Sivak
> wrote:

Hi,

we are working on that, we can only ask for patience now,
Jenny was trying to find out what happened and how to fix it
all week.

Best regards

--
Martin Sivak
SLA / oVirt

On Mon, Apr 10, 2017 at 9:38 AM, Rafał Wojciechowski
>
wrote:

hi,

I have similiar issue(I also started my mailthread)
after upgrade 4.0 to 4.1

Version 4.1.1.8-1.el7.centos (before it was some 4.1.0.x
or similiar - update not fixed it)

to run VM I have to set in Console tab Headless mode -
without it I got libvirtd segfault(logs attached in my
mailthread).

So I am able to run VMs only without Console - do you
also have to set headless before run VM?

I noticed that libvirt-daemon was also upgraded to 2.0
version during ovirt upgrade - I dont think that 4.1 was
not testes due to such libvirtd upgrade... but maybe?

Regards,
Rafal Wojciechowski

W dniu 10.04.2017 o 08:24, Arsène Gschwind pisze:

Hi,

After updating to oVirt 4.1.1 Async release i can
confirm that the problem still persists.

Rgds,
Arsène

On 03/25/2017 12:25 PM, Arsène Gschwind wrote:

Hi,

After updating to 4.1.1 i'm observing the same
behavior, HE without any console.
Even when trying to edit the HE VMs it doesn't change
anything, Graphics stays to NONE.

Thanks for any Help.

Regards,
Arsène

On 03/24/2017 03:11 PM, Nelson Lameiras wrote:

Hello,

When upgrading my test setup from 4.0 to 4.1, my
engine vm lost it's console (from SPICE to None in GUI)

My test setup :
2 manually built hosts using centos 7.3, ovirt 4.1
1 manually built hosted engine centos 7.3, oVirt
4.1.0.4-el7, accessible with

Re: [ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more engine console available

2017-04-18 Thread Rafał Wojciechowski

hi,

I applied it for
/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/ovf/
content, then rebooted, reinstalled host in ovirt engine web
administrator, again rebooted and tried again but I have still the same
issue with libvirtd segfault

Regards,
Rafal Wojciechowski

W dniu 18.04.2017 o 14:20, Evgenia Tokar pisze:

Hi,

Thanks for bringing the issue to our attention and for answering the
questions.

There is a patch to fix this: https://gerrit.ovirt.org/#/c/75515/
After applying the patch a restart to the hosted engine vm is required
(not just the engine).

Let me know if you are still experiencing issues with this.

Thanks,
Jenny

On Wed, Apr 12, 2017 at 8:05 PM, Rafał Wojciechowski
> wrote:

hi,

I will answer also. however I am using single hypervisor so
without ha and I have no performed steps:
https://www.ovirt.org/documentation/how-to/hosted-engine/

1. yes - however I have to start in headless mode so it is quite
obvius
if I am trying to start with spice/vnc console I am getting
segfault from libvirtd
2. as above
3. as above

W dniu 12.04.2017 o 14:12, Arsène Gschwind pisze:

Hi all,

I will answer your questions:

1. definitively yes
2. the command hosted-engine --console works well and I'm able to
connect.
3. Here are the device entries

devices={device:qxl,alias:video0,type:video,deviceId:5210a3c3-9cc4-4aed-90c6-432dd2d37c46,address:{slot:0x02,
bus:0x00,domain:0x,type:pci,function:0x0}}
devices={device:console,type:console}

Thanks and rgds,
Arsène

On 04/12/2017 10:53 AM, Evgenia Tokar wrote:

Hi all,

I have managed to reproduce this issue and opened a bug for
tracking it: https://bugzilla.redhat.com/show_bug.cgi?id=1441570
.

There is no solution yet, but I would appreciate if any who
encountered this issue will answer some questions:
1. Is the console button greyed out in the UI?
2. On the hosted engine host, does the command hosted-engine
--console fails?
If it fails, try upgrading ovirt-hosted-engine-ha on the
hosted engine host. We had a bug related to this issue that was
fixed (https://bugzilla.redhat.com/show_bug.cgi?id=1364132
).
After upgrade and restart of the vm, this should work, and
you should be able to connect to the console.
3. On the hosted engine host look at the content of:
/var/run/ovirt-hosted-engine-ha/vm.conf
Does it contain a graphical device? Or a console device?

Thanks,
Jenny

On Mon, Apr 10, 2017 at 11:44 AM, Martin Sivak
> wrote:

Hi,

we are working on that, we can only ask for patience now,
Jenny was trying to find out what happened and how to fix it
all week.

Best regards

--
Martin Sivak
SLA / oVirt

On Mon, Apr 10, 2017 at 9:38 AM, Rafał Wojciechowski
>
wrote:

hi,

I have similiar issue(I also started my mailthread)
after upgrade 4.0 to 4.1

Version 4.1.1.8-1.el7.centos (before it was some 4.1.0.x
or similiar - update not fixed it)

to run VM I have to set in Console tab Headless mode -
without it I got libvirtd segfault(logs attached in my
mailthread).

So I am able to run VMs only without Console - do you
also have to set headless before run VM?

I noticed that libvirt-daemon was also upgraded to 2.0
version during ovirt upgrade - I dont think that 4.1 was
not testes due to such libvirtd upgrade... but maybe?

Regards,
Rafal Wojciechowski

W dniu 10.04.2017 o 08:24, Arsène Gschwind pisze:

Hi,

After updating to oVirt 4.1.1 Async release i can
confirm that the problem still persists.

Rgds,
Arsène

On 03/25/2017 12:25 PM, Arsène Gschwind wrote:

Hi,

After updating to 4.1.1 i'm observing the same
behavior, HE without any console.
Even when trying to edit the HE VMs it doesn't change
anything, Graphics stays to NONE.

Thanks for any Help.

Regards,
Arsène

On 03/24/2017 03:11 PM, Nelson Lameiras wrote:

Hello,

When upgrading my test setup from 4.0 to 4.1, my
engine vm lost it's console (from SPICE to None in GUI)

My test setup :
2 manually built hosts using centos 7.3, ovirt 4.1

Re: [ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more engine console available

2017-04-18 Thread Evgenia Tokar

Hi,

Thanks for bringing the issue to our attention and for answering the
questions.

There is a patch to fix this: https://gerrit.ovirt.org/#/c/75515/
After applying the patch a restart to the hosted engine vm is required (not
just the engine).

Let me know if you are still experiencing issues with this.

Thanks,
Jenny


On Wed, Apr 12, 2017 at 8:05 PM, Rafał Wojciechowski <
i...@rafalwojciechowski.pl> wrote:

> hi,
>
> I will answer also. however I am using single hypervisor so without ha and
> I have no performed steps:
> https://www.ovirt.org/documentation/how-to/hosted-engine/
>
> 1. yes - however I have to start in headless mode so it is quite obvius
> if I am trying to start with spice/vnc console I am getting segfault from
> libvirtd
> 2. as above
> 3. as above
>
> W dniu 12.04.2017 o 14:12, Arsène Gschwind pisze:
>
> Hi all,
>
> I will answer your questions:
>
> 1. definitively yes
> 2. the command hosted-engine --console works well and I'm able to connect.
> 3. Here are the device entries
>
> devices={device:qxl,alias:video0,type:video,deviceId:
> 5210a3c3-9cc4-4aed-90c6-432dd2d37c46,address:{slot:0x02,
> bus:0x00,domain:0x,type:pci,function:0x0}}
> devices={device:console,type:console}
>
> Thanks and rgds,
> Arsène
> On 04/12/2017 10:53 AM, Evgenia Tokar wrote:
>
> Hi all,
>
> I have managed to reproduce this issue and opened a bug for tracking it:
> https://bugzilla.redhat.com/show_bug.cgi?id=1441570 .
>
> There is no solution yet, but I would appreciate if any who encountered
> this issue will answer some questions:
> 1. Is the console button greyed out in the UI?
> 2. On the hosted engine host, does the command hosted-engine --console
> fails?
>  If it fails, try upgrading ovirt-hosted-engine-ha on the hosted
> engine host. We had a bug related to this issue that was fixed (
> https://bugzilla.redhat.com/show_bug.cgi?id=1364132).
>  After upgrade and restart of the vm, this should work, and you should
> be able to connect to the console.
> 3. On the hosted engine host look at the content of:
> /var/run/ovirt-hosted-engine-ha/vm.conf
> Does it contain a graphical device? Or a console device?
>
> Thanks,
> Jenny
>
>
> On Mon, Apr 10, 2017 at 11:44 AM, Martin Sivak  wrote:
>
>> Hi,
>>
>> we are working on that, we can only ask for patience now, Jenny was
>> trying to find out what happened and how to fix it all week.
>>
>> Best regards
>>
>> --
>> Martin Sivak
>> SLA / oVirt
>>
>> On Mon, Apr 10, 2017 at 9:38 AM, Rafał Wojciechowski <
>> i...@rafalwojciechowski.pl> wrote:
>>
>>> hi,
>>>
>>> I have similiar issue(I also started my mailthread) after upgrade 4.0 to
>>> 4.1
>>>
>>> Version 4.1.1.8-1.el7.centos (before it was some 4.1.0.x or similiar -
>>> update not fixed it)
>>> to run VM I have to set in Console tab Headless mode - without it I got
>>> libvirtd segfault(logs attached in my mailthread).
>>>
>>> So I am able to run VMs only without Console - do you also have to set
>>> headless before run VM?
>>>
>>> I noticed that libvirt-daemon was also upgraded to 2.0 version during
>>> ovirt upgrade - I dont think that 4.1 was not testes due to such libvirtd
>>> upgrade... but maybe?
>>>
>>> Regards,
>>> Rafal Wojciechowski
>>>
>>> W dniu 10.04.2017 o 08:24, Arsène Gschwind pisze:
>>>
>>> Hi,
>>>
>>> After updating to oVirt 4.1.1 Async release i can confirm that the
>>> problem still persists.
>>>
>>> Rgds,
>>> Arsène
>>>
>>> On 03/25/2017 12:25 PM, Arsène Gschwind wrote:
>>>
>>> Hi,
>>> After updating to 4.1.1 i'm observing the same behavior, HE without any
>>> console.
>>> Even when trying to edit the HE VMs it doesn't change anything, Graphics
>>> stays to NONE.
>>>
>>> Thanks for any Help.
>>>
>>> Regards,
>>> Arsène
>>>
>>> On 03/24/2017 03:11 PM, Nelson Lameiras wrote:
>>>
>>> Hello,
>>>
>>> When upgrading my test setup from 4.0 to 4.1, my engine vm lost it's
>>> console (from SPICE to None in GUI)
>>>
>>> My test setup :
>>> 2 manually built hosts using centos 7.3, ovirt 4.1
>>> 1 manually built hosted engine centos 7.3, oVirt 4.1.0.4-el7, accessible
>>> with SPICE console via GUI
>>>
>>> I updated ovirt-engine from 4.1.0 to 4.1.1 by doing on engine :
>>> - yum update
>>> - engine-setup
>>> - reboot engine
>>>
>>> When accessing 4.1.1 GUI, Graphics is set to "None" on "Virtual
>>> Machines" page, with "console button" greyed out (all other VMs have the
>>> same Graphics set to the same value as before)
>>> I tried to edit engine VM settings, and console options are same as
>>> before (SPLICE, QXL).
>>>
>>> I'm hopping this is not a new feature, since if we loose network on
>>> engine, console is the only way to debug...
>>>
>>> Is this a bug?
>>>
>>> ps. I was able to reproduce this bug 2 times
>>>
>>> cordialement, regards,
>>>
>>> 
>>> Nelson LAMEIRAS
>>> Ingénieur Systèmes et Réseaux / Systems and Networks engineer
>>> Tel: +33 5 32 09 09 70
>>> nelson.lamei...@lyra-network.com
>>> www.lyra-network.com | www.payzen.eu

Re: [ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more engine console available

2017-04-12 Thread Rafał Wojciechowski

hi,

I will answer also. however I am using single hypervisor so without ha
and I have no performed steps:

https://www.ovirt.org/documentation/how-to/hosted-engine/

1. yes - however I have to start in headless mode so it is quite obvius
if I am trying to start with spice/vnc console I am getting segfault
from libvirtd

2. as above
3. as above

W dniu 12.04.2017 o 14:12, Arsène Gschwind pisze:

Hi all,

I will answer your questions:

1. definitively yes
2. the command hosted-engine --console works well and I'm able to connect.
3. Here are the device entries

devices={device:qxl,alias:video0,type:video,deviceId:5210a3c3-9cc4-4aed-90c6-432dd2d37c46,address:{slot:0x02,
bus:0x00,domain:0x,type:pci,function:0x0}}
devices={device:console,type:console}

Thanks and rgds,
Arsène

On 04/12/2017 10:53 AM, Evgenia Tokar wrote:

Hi all,

I have managed to reproduce this issue and opened a bug for tracking
it: https://bugzilla.redhat.com/show_bug.cgi?id=1441570 .

There is no solution yet, but I would appreciate if any who
encountered this issue will answer some questions:

1. Is the console button greyed out in the UI?
2. On the hosted engine host, does the command hosted-engine
--console fails?
If it fails, try upgrading ovirt-hosted-engine-ha on the hosted
engine host. We had a bug related to this issue that was fixed
(https://bugzilla.redhat.com/show_bug.cgi?id=1364132).
After upgrade and restart of the vm, this should work, and you
should be able to connect to the console.
3. On the hosted engine host look at the content of:
/var/run/ovirt-hosted-engine-ha/vm.conf

Does it contain a graphical device? Or a console device?

Thanks,
Jenny

On Mon, Apr 10, 2017 at 11:44 AM, Martin Sivak > wrote:

Hi,

we are working on that, we can only ask for patience now, Jenny
was trying to find out what happened and how to fix it all week.

Best regards

--
Martin Sivak
SLA / oVirt

On Mon, Apr 10, 2017 at 9:38 AM, Rafał Wojciechowski
> wrote:

hi,

I have similiar issue(I also started my mailthread) after
upgrade 4.0 to 4.1

Version 4.1.1.8-1.el7.centos (before it was some 4.1.0.x or
similiar - update not fixed it)

to run VM I have to set in Console tab Headless mode -
without it I got libvirtd segfault(logs attached in my
mailthread).

So I am able to run VMs only without Console - do you also
have to set headless before run VM?

I noticed that libvirt-daemon was also upgraded to 2.0
version during ovirt upgrade - I dont think that 4.1 was not
testes due to such libvirtd upgrade... but maybe?

Regards,
Rafal Wojciechowski

W dniu 10.04.2017 o 08:24, Arsène Gschwind pisze:

Hi,

After updating to oVirt 4.1.1 Async release i can confirm
that the problem still persists.

Rgds,
Arsène

On 03/25/2017 12:25 PM, Arsène Gschwind wrote:

Hi,

After updating to 4.1.1 i'm observing the same behavior, HE
without any console.
Even when trying to edit the HE VMs it doesn't change
anything, Graphics stays to NONE.

Thanks for any Help.

Regards,
Arsène

On 03/24/2017 03:11 PM, Nelson Lameiras wrote:

Hello,

When upgrading my test setup from 4.0 to 4.1, my engine vm
lost it's console (from SPICE to None in GUI)

My test setup :
2 manually built hosts using centos 7.3, ovirt 4.1
1 manually built hosted engine centos 7.3, oVirt
4.1.0.4-el7, accessible with SPICE console via GUI

I updated ovirt-engine from 4.1.0 to 4.1.1 by doing on
engine :
- yum update
- engine-setup
- reboot engine

When accessing 4.1.1 GUI, Graphics is set to "None" on
"Virtual Machines" page, with "console button" greyed out
(all other VMs have the same Graphics set to the same
value as before)
I tried to edit engine VM settings, and console options
are same as before (SPLICE, QXL).

I'm hopping this is not a new feature, since if we loose
network on engine, console is the only way to debug...

Is this a bug?

ps. I was able to reproduce this bug 2 times

cordialement, regards,

Nelson LAMEIRAS
Ingénieur Systèmes et Réseaux/ Systems and Networks engineer
Tel: +33 5 32 09 09 70
nelson.lamei...@lyra-network.com

www.lyra-network.com |
www.payzen.eu

Re: [ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more engine console available

2017-04-12 Thread Arsène Gschwind

Hi all,

I will answer your questions:

1. definitively yes
2. the command hosted-engine --console works well and I'm able to connect.
3. Here are the device entries

devices={device:qxl,alias:video0,type:video,deviceId:5210a3c3-9cc4-4aed-90c6-432dd2d37c46,address:{slot:0x02,
bus:0x00,domain:0x,type:pci,function:0x0}}
devices={device:console,type:console}

Thanks and rgds,
Arsène

On 04/12/2017 10:53 AM, Evgenia Tokar wrote:

Hi all,

I have managed to reproduce this issue and opened a bug for tracking
it: https://bugzilla.redhat.com/show_bug.cgi?id=1441570 .

There is no solution yet, but I would appreciate if any who
encountered this issue will answer some questions:

1. Is the console button greyed out in the UI?
2. On the hosted engine host, does the command hosted-engine --console
fails?
If it fails, try upgrading ovirt-hosted-engine-ha on the hosted
engine host. We had a bug related to this issue that was fixed
(https://bugzilla.redhat.com/show_bug.cgi?id=1364132).
After upgrade and restart of the vm, this should work, and you
should be able to connect to the console.
3. On the hosted engine host look at the content of:
/var/run/ovirt-hosted-engine-ha/vm.conf

Does it contain a graphical device? Or a console device?

Thanks,
Jenny

On Mon, Apr 10, 2017 at 11:44 AM, Martin Sivak > wrote:

Hi,

we are working on that, we can only ask for patience now, Jenny
was trying to find out what happened and how to fix it all week.

Best regards

--
Martin Sivak
SLA / oVirt

On Mon, Apr 10, 2017 at 9:38 AM, Rafał Wojciechowski
> wrote:

hi,

I have similiar issue(I also started my mailthread) after
upgrade 4.0 to 4.1

Version 4.1.1.8-1.el7.centos (before it was some 4.1.0.x or
similiar - update not fixed it)

to run VM I have to set in Console tab Headless mode - without
it I got libvirtd segfault(logs attached in my mailthread).

So I am able to run VMs only without Console - do you also
have to set headless before run VM?

I noticed that libvirt-daemon was also upgraded to 2.0 version
during ovirt upgrade - I dont think that 4.1 was not testes
due to such libvirtd upgrade... but maybe?

Regards,
Rafal Wojciechowski

W dniu 10.04.2017 o 08:24, Arsène Gschwind pisze:

Hi,

After updating to oVirt 4.1.1 Async release i can confirm
that the problem still persists.

Rgds,
Arsène

On 03/25/2017 12:25 PM, Arsène Gschwind wrote:

Hi,

After updating to 4.1.1 i'm observing the same behavior, HE
without any console.
Even when trying to edit the HE VMs it doesn't change
anything, Graphics stays to NONE.

Thanks for any Help.

Regards,
Arsène

On 03/24/2017 03:11 PM, Nelson Lameiras wrote:

Hello,

When upgrading my test setup from 4.0 to 4.1, my engine vm
lost it's console (from SPICE to None in GUI)

My test setup :
2 manually built hosts using centos 7.3, ovirt 4.1
1 manually built hosted engine centos 7.3, oVirt
4.1.0.4-el7, accessible with SPICE console via GUI

I updated ovirt-engine from 4.1.0 to 4.1.1 by doing on engine :
- yum update
- engine-setup
- reboot engine

When accessing 4.1.1 GUI, Graphics is set to "None" on
"Virtual Machines" page, with "console button" greyed out
(all other VMs have the same Graphics set to the same value
as before)
I tried to edit engine VM settings, and console options are
same as before (SPLICE, QXL).

I'm hopping this is not a new feature, since if we loose
network on engine, console is the only way to debug...

Is this a bug?

ps. I was able to reproduce this bug 2 times

cordialement, regards,

Nelson LAMEIRAS
Ingénieur Systèmes et Réseaux/ Systems and Networks engineer
Tel: +33 5 32 09 09 70
nelson.lamei...@lyra-network.com

www.lyra-network.com |
www.payzen.eu

Lyra Network, 109 rue de l'innovation, 31670 Labège, FRANCE

___
Users mailing list
Users@ovirt.org

Re: [ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more engine console available

2017-04-10 Thread Martin Sivak

Hi,

we are working on that, we can only ask for patience now, Jenny was trying
to find out what happened and how to fix it all week.

Best regards

--
Martin Sivak
SLA / oVirt

On Mon, Apr 10, 2017 at 9:38 AM, Rafał Wojciechowski <
i...@rafalwojciechowski.pl> wrote:

> hi,
>
> I have similiar issue(I also started my mailthread) after upgrade 4.0 to
> 4.1
>
> Version 4.1.1.8-1.el7.centos (before it was some 4.1.0.x or similiar -
> update not fixed it)
> to run VM I have to set in Console tab Headless mode - without it I got
> libvirtd segfault(logs attached in my mailthread).
>
> So I am able to run VMs only without Console - do you also have to set
> headless before run VM?
>
> I noticed that libvirt-daemon was also upgraded to 2.0 version during
> ovirt upgrade - I dont think that 4.1 was not testes due to such libvirtd
> upgrade... but maybe?
>
> Regards,
> Rafal Wojciechowski
>
> W dniu 10.04.2017 o 08:24, Arsène Gschwind pisze:
>
> Hi,
>
> After updating to oVirt 4.1.1 Async release i can confirm that the problem
> still persists.
>
> Rgds,
> Arsène
>
> On 03/25/2017 12:25 PM, Arsène Gschwind wrote:
>
> Hi,
> After updating to 4.1.1 i'm observing the same behavior, HE without any
> console.
> Even when trying to edit the HE VMs it doesn't change anything, Graphics
> stays to NONE.
>
> Thanks for any Help.
>
> Regards,
> Arsène
>
> On 03/24/2017 03:11 PM, Nelson Lameiras wrote:
>
> Hello,
>
> When upgrading my test setup from 4.0 to 4.1, my engine vm lost it's
> console (from SPICE to None in GUI)
>
> My test setup :
> 2 manually built hosts using centos 7.3, ovirt 4.1
> 1 manually built hosted engine centos 7.3, oVirt 4.1.0.4-el7, accessible
> with SPICE console via GUI
>
> I updated ovirt-engine from 4.1.0 to 4.1.1 by doing on engine :
> - yum update
> - engine-setup
> - reboot engine
>
> When accessing 4.1.1 GUI, Graphics is set to "None" on "Virtual Machines"
> page, with "console button" greyed out (all other VMs have the same
> Graphics set to the same value as before)
> I tried to edit engine VM settings, and console options are same as before
> (SPLICE, QXL).
>
> I'm hopping this is not a new feature, since if we loose network on
> engine, console is the only way to debug...
>
> Is this a bug?
>
> ps. I was able to reproduce this bug 2 times
>
> cordialement, regards,
>
> 
> Nelson LAMEIRAS
> Ingénieur Systèmes et Réseaux / Systems and Networks engineer
> Tel: +33 5 32 09 09 70
> nelson.lamei...@lyra-network.com
> www.lyra-network.com | www.payzen.eu 
> 
> 
> 
> 
> --
> Lyra Network, 109 rue de l'innovation, 31670 Labège, FRANCE
>
>
>
> ___
> Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>
>
> --
>
> *Arsène Gschwind*
> Fa. Sapify AG im Auftrag der Universität Basel
> IT Services
> Klingelbergstr. 70 |  CH-4056 Basel  |  Switzerland
> Tel. +41 79 449 25 63 <+41%2079%20449%2025%2063>  |  http://its.unibas.ch
> ITS-ServiceDesk: support-...@unibas.ch | +41 61 267 14 11
> <+41%2061%20267%2014%2011>
>
>
> ___
> Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>
>
> --
>
> *Arsène Gschwind*
> Fa. Sapify AG im Auftrag der Universität Basel
> IT Services
> Klingelbergstr. 70 |  CH-4056 Basel  |  Switzerland
> Tel. +41 79 449 25 63 <+41%2079%20449%2025%2063>  |  http://its.unibas.ch
> ITS-ServiceDesk: support-...@unibas.ch | +41 61 267 14 11
> <+41%2061%20267%2014%2011>
>
>
> ___
> Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more engine console available

2017-04-10 Thread Rafał Wojciechowski


hi,

I have similiar issue(I also started my mailthread) after upgrade 4.0 to 4.1

Version 4.1.1.8-1.el7.centos (before it was some 4.1.0.x or similiar - 
update not fixed it)


to run VM I have to set in Console tab Headless mode - without it I got 
libvirtd segfault(logs attached in my mailthread).


So I am able to run VMs only without Console - do you also have to set 
headless before run VM?


I noticed that libvirt-daemon was also upgraded to 2.0 version during 
ovirt upgrade - I dont think that 4.1 was not testes due to such 
libvirtd upgrade... but maybe?


Regards,
Rafal Wojciechowski

W dniu 10.04.2017 o 08:24, Arsène Gschwind pisze:


Hi,

After updating to oVirt 4.1.1 Async release i can confirm that the 
problem still persists.


Rgds,
Arsène


On 03/25/2017 12:25 PM, Arsène Gschwind wrote:


Hi,

After updating to 4.1.1 i'm observing the same behavior, HE without 
any console.
Even when trying to edit the HE VMs it doesn't change anything, 
Graphics stays to NONE.


Thanks for any Help.

Regards,
Arsène

On 03/24/2017 03:11 PM, Nelson Lameiras wrote:

Hello,

When upgrading my test setup from 4.0 to 4.1, my engine vm lost it's 
console (from SPICE to None in GUI)


My test setup :
2 manually built hosts using centos 7.3, ovirt 4.1
1 manually built hosted engine centos 7.3, oVirt 4.1.0.4-el7, 
accessible with SPICE console via GUI


I updated ovirt-engine from 4.1.0 to 4.1.1 by doing on engine :
- yum update
- engine-setup
- reboot engine

When accessing 4.1.1 GUI, Graphics is set to "None" on "Virtual 
Machines" page, with "console button" greyed out (all other VMs have 
the same Graphics set to the same value as before)
I tried to edit engine VM settings, and console options are same as 
before (SPLICE, QXL).


I'm hopping this is not a new feature, since if we loose network on 
engine, console is the only way to debug...


Is this a bug?

ps. I was able to reproduce this bug 2 times

cordialement, regards,



Nelson LAMEIRAS
Ingénieur Systèmes et Réseaux/ Systems and Networks engineer
Tel: +33 5 32 09 09 70
nelson.lamei...@lyra-network.com 

www.lyra-network.com  | www.payzen.eu 










Lyra Network, 109 rue de l'innovation, 31670 Labège, FRANCE




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


--

*Arsène Gschwind*
Fa. Sapify AG im Auftrag der Universität Basel
IT Services
Klingelbergstr. 70 |  CH-4056 Basel  |  Switzerland
Tel. +41 79 449 25 63  | http://its.unibas.ch 
ITS-ServiceDesk: support-...@unibas.ch | +41 61 267 14 11



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


--

*Arsène Gschwind*
Fa. Sapify AG im Auftrag der Universität Basel
IT Services
Klingelbergstr. 70 |  CH-4056 Basel  |  Switzerland
Tel. +41 79 449 25 63  | http://its.unibas.ch 
ITS-ServiceDesk: support-...@unibas.ch | +41 61 267 14 11



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


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

Re: [ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more engine console available

2017-03-27 Thread Резников А . А .


24.03.2017 17:11, Nelson Lameiras пишет:

Hello,

When upgrading my test setup from 4.0 to 4.1, my engine vm lost it's 
console (from SPICE to None in GUI)


My test setup :
2 manually built hosts using centos 7.3, ovirt 4.1
1 manually built hosted engine centos 7.3, oVirt 4.1.0.4-el7, 
accessible with SPICE console via GUI


I updated ovirt-engine from 4.1.0 to 4.1.1 by doing on engine :
- yum update
- engine-setup
- reboot engine

When accessing 4.1.1 GUI, Graphics is set to "None" on "Virtual 
Machines" page, with "console button" greyed out (all other VMs have 
the same Graphics set to the same value as before)
I tried to edit engine VM settings, and console options are same as 
before (SPLICE, QXL).


I'm hopping this is not a new feature, since if we loose network on 
engine, console is the only way to debug...


Is this a bug?

ps. I was able to reproduce this bug 2 times

cordialement, regards,



Nelson LAMEIRAS
Ingénieur Systèmes et Réseaux/ Systems and Networks engineer
Tel: +33 5 32 09 09 70
nelson.lamei...@lyra-network.com 
www.lyra-network.com  | www.payzen.eu 










Lyra Network, 109 rue de l'innovation, 31670 Labège, FRANCE




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

I confirm, on my test lab with 4.1.1 the console button is gray.
Please, screenshot http://nimb.ws/8mXFoA

Thanks, Alex.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more engine console available

2017-03-25 Thread Arsène Gschwind


Hi,

After updating to 4.1.1 i'm observing the same behavior, HE without any 
console.
Even when trying to edit the HE VMs it doesn't change anything, Graphics 
stays to NONE.


Thanks for any Help.

Regards,
Arsène

On 03/24/2017 03:11 PM, Nelson Lameiras wrote:

Hello,

When upgrading my test setup from 4.0 to 4.1, my engine vm lost it's 
console (from SPICE to None in GUI)


My test setup :
2 manually built hosts using centos 7.3, ovirt 4.1
1 manually built hosted engine centos 7.3, oVirt 4.1.0.4-el7, 
accessible with SPICE console via GUI


I updated ovirt-engine from 4.1.0 to 4.1.1 by doing on engine :
- yum update
- engine-setup
- reboot engine

When accessing 4.1.1 GUI, Graphics is set to "None" on "Virtual 
Machines" page, with "console button" greyed out (all other VMs have 
the same Graphics set to the same value as before)
I tried to edit engine VM settings, and console options are same as 
before (SPLICE, QXL).


I'm hopping this is not a new feature, since if we loose network on 
engine, console is the only way to debug...


Is this a bug?

ps. I was able to reproduce this bug 2 times

cordialement, regards,



Nelson LAMEIRAS
Ingénieur Systèmes et Réseaux/ Systems and Networks engineer
Tel: +33 5 32 09 09 70
nelson.lamei...@lyra-network.com 
www.lyra-network.com  | www.payzen.eu 










Lyra Network, 109 rue de l'innovation, 31670 Labège, FRANCE




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


--

*Arsène Gschwind*
Fa. Sapify AG im Auftrag der Universität Basel
IT Services
Klingelbergstr. 70 |  CH-4056 Basel  |  Switzerland
Tel. +41 79 449 25 63  | http://its.unibas.ch 
ITS-ServiceDesk: support-...@unibas.ch | +41 61 267 14 11

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

Re: [ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more engine console available

2017-03-24 Thread Lukáš Kaplan

Hello Nelson,

I did same thing today too and it was succesfull. But I used different
steps. Check this:
https://www.ovirt.org/documentation/how-to/hosted-engine/#upgrade-hosted-engine
http://www.ovirt.org/documentation/upgrade-guide/chap-Updates_between_Minor_Releases/

Hope it helps you.

Have a nice day,

--
Lukas Kaplan


2017-03-24 15:11 GMT+01:00 Nelson Lameiras :

> Hello,
>
> When upgrading my test setup from 4.0 to 4.1, my engine vm lost it's
> console (from SPICE to None in GUI)
>
> My test setup :
> 2 manually built hosts using centos 7.3, ovirt 4.1
> 1 manually built hosted engine centos 7.3, oVirt 4.1.0.4-el7, accessible
> with SPICE console via GUI
>
> I updated ovirt-engine from 4.1.0 to 4.1.1 by doing on engine :
> - yum update
> - engine-setup
> - reboot engine
>
> When accessing 4.1.1 GUI, Graphics is set to "None" on "Virtual Machines"
> page, with "console button" greyed out (all other VMs have the same
> Graphics set to the same value as before)
> I tried to edit engine VM settings, and console options are same as before
> (SPLICE, QXL).
>
> I'm hopping this is not a new feature, since if we loose network on
> engine, console is the only way to debug...
>
> Is this a bug?
>
> ps. I was able to reproduce this bug 2 times
>
> cordialement, regards,
>
> 
> Nelson LAMEIRAS
> Ingénieur Systèmes et Réseaux / Systems and Networks engineer
> Tel: +33 5 32 09 09 70 <+33%205%2032%2009%2009%2070>
> nelson.lamei...@lyra-network.com
> www.lyra-network.com | www.payzen.eu 
> 
> 
> 
> 
> --
> Lyra Network, 109 rue de l'innovation, 31670 Labège, FRANCE
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more engine console available

2017-03-24 Thread Nelson Lameiras

ok, I'm guessing that your situation is different to mine. 

I'm hopping someone confirms that upgrading oVirt engine from 4.0 to 4.1 does 
(or does not) indeed disable SPICE console on Engine VM ? 

cordialement, regards, 


Nelson LAMEIRAS 
Ingénieur Systèmes et Réseaux / Systems and Networks engineer 
Tel: +33 5 32 09 09 70 
nelson.lamei...@lyra-network.com 

www.lyra-network.com | www.payzen.eu 





Lyra Network, 109 rue de l'innovation, 31670 Labège, FRANCE 



From: "Lukáš Kaplan" <lkap...@dragon.cz> 
To: "Nelson Lameiras" <nelson.lamei...@lyra-network.com> 
Cc: "users" <users@ovirt.org> 
Sent: Friday, March 24, 2017 4:14:37 PM 
Subject: Re: [ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more engine 
console available 

Hello Nelson, 
I have hosted engine graphics console as VNC. I am using ssho directly to 
engine. I cant say if vnc is working or not, because I have no client for it... 
(Tested in debian jessie with virt-viewer 1.0 and 5.0 - does not work) 

-- 
Lukas Kaplan 



2017-03-24 15:32 GMT+01:00 Nelson Lameiras < nelson.lamei...@lyra-network.com > 
: 



Hello Lukas, 

Thanks for you feedback. 
I did something very similar to procedures you sent me. 

Can you confirm me that your HostedEngine vm still has it's SPICE console 
available and is working? 
(otherwise my update went ok) 

cordialement, regards, 


Nelson LAMEIRAS 
Ingénieur Systèmes et Réseaux / Systems and Networks engineer 
Tel: +33 5 32 09 09 70 

nelson.lamei...@lyra-network.com 

www.lyra-network.com | www.payzen.eu 





Lyra Network, 109 rue de l'innovation, 31670 Labège, FRANCE 



From: "Lukáš Kaplan" < lkap...@dragon.cz > 
To: "Nelson Lameiras" < nelson.lamei...@lyra-network.com > 
Cc: "users" < users@ovirt.org > 
Sent: Friday, March 24, 2017 3:22:44 PM 
Subject: Re: [ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more engine 
console available 

Hello Nelson, 
I did same thing today too and it was succesfull. But I used different steps. 
Check this: 
https://www.ovirt.org/documentation/how-to/hosted-engine/#upgrade-hosted-engine 
http://www.ovirt.org/documentation/upgrade-guide/chap-Updates_between_Minor_Releases/
 

Hope it helps you. 

Have a nice day, 

-- 
Lukas Kaplan 


2017-03-24 15:11 GMT+01:00 Nelson Lameiras < nelson.lamei...@lyra-network.com > 
: 

BQ_BEGIN

Hello, 

When upgrading my test setup from 4.0 to 4.1, my engine vm lost it's console 
(from SPICE to None in GUI) 

My test setup : 
2 manually built hosts using centos 7.3, ovirt 4.1 
1 manually built hosted engine centos 7.3, oVirt 4.1.0.4-el7, accessible with 
SPICE console via GUI 

I updated ovirt-engine from 4.1.0 to 4.1.1 by doing on engine : 
- yum update 
- engine-setup 
- reboot engine 

When accessing 4.1.1 GUI, Graphics is set to "None" on "Virtual Machines" page, 
with "console button" greyed out (all other VMs have the same Graphics set to 
the same value as before) 
I tried to edit engine VM settings, and console options are same as before 
(SPLICE, QXL). 

I'm hopping this is not a new feature, since if we loose network on engine, 
console is the only way to debug... 

Is this a bug? 

ps. I was able to reproduce this bug 2 times 

cordialement, regards, 


Nelson LAMEIRAS 
Ingénieur Systèmes et Réseaux / Systems and Networks engineer 
Tel: +33 5 32 09 09 70 

nelson.lamei...@lyra-network.com 

www.lyra-network.com | www.payzen.eu 





Lyra Network, 109 rue de l'innovation, 31670 Labège, FRANCE 


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






BQ_END


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

Re: [ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more engine console available

2017-03-24 Thread Lukáš Kaplan

Hello Nelson,

I have hosted engine graphics console as VNC. I am using ssho directly to
engine. I cant say if vnc is working or not, because I have no client for
it... (Tested in debian jessie with virt-viewer 1.0 and 5.0 - does not work)

--
Lukas Kaplan



2017-03-24 15:32 GMT+01:00 Nelson Lameiras <nelson.lamei...@lyra-network.com
>:

> Hello Lukas,
>
> Thanks for you feedback.
> I did something very similar to procedures you sent me.
>
> Can you confirm me that your HostedEngine vm still has it's SPICE console
> available and is working?
> (otherwise my update went ok)
>
> cordialement, regards,
>
> <https://www.lyra-network.com/>
> Nelson LAMEIRAS
> Ingénieur Systèmes et Réseaux / Systems and Networks engineer
> Tel: +33 5 32 09 09 70 <+33%205%2032%2009%2009%2070>
> nelson.lamei...@lyra-network.com
> www.lyra-network.com | www.payzen.eu <https://payzen.eu>
> <https://www.youtube.com/channel/UCrVl1CO_Jlu3KbiRH-tQ_vA>
> <https://www.linkedin.com/company/lyra-network_2>
> <https://twitter.com/LyraNetwork>
> <https://payzen.eu>
> --
> Lyra Network, 109 rue de l'innovation, 31670 Labège, FRANCE
>
>
> --
> *From: *"Lukáš Kaplan" <lkap...@dragon.cz>
> *To: *"Nelson Lameiras" <nelson.lamei...@lyra-network.com>
> *Cc: *"users" <users@ovirt.org>
> *Sent: *Friday, March 24, 2017 3:22:44 PM
> *Subject: *Re: [ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more
> engine console available
>
> Hello Nelson,
> I did same thing today too and it was succesfull. But I used different
> steps. Check this:
> https://www.ovirt.org/documentation/how-to/hosted-
> engine/#upgrade-hosted-engine
> http://www.ovirt.org/documentation/upgrade-guide/
> chap-Updates_between_Minor_Releases/
>
> Hope it helps you.
>
> Have a nice day,
>
> --
> Lukas Kaplan
>
>
> 2017-03-24 15:11 GMT+01:00 Nelson Lameiras <nelson.lameiras@lyra-network.
> com>:
>
>> Hello,
>>
>> When upgrading my test setup from 4.0 to 4.1, my engine vm lost it's
>> console (from SPICE to None in GUI)
>>
>> My test setup :
>> 2 manually built hosts using centos 7.3, ovirt 4.1
>> 1 manually built hosted engine centos 7.3, oVirt 4.1.0.4-el7, accessible
>> with SPICE console via GUI
>>
>> I updated ovirt-engine from 4.1.0 to 4.1.1 by doing on engine :
>> - yum update
>> - engine-setup
>> - reboot engine
>>
>> When accessing 4.1.1 GUI, Graphics is set to "None" on "Virtual Machines"
>> page, with "console button" greyed out (all other VMs have the same
>> Graphics set to the same value as before)
>> I tried to edit engine VM settings, and console options are same as
>> before (SPLICE, QXL).
>>
>> I'm hopping this is not a new feature, since if we loose network on
>> engine, console is the only way to debug...
>>
>> Is this a bug?
>>
>> ps. I was able to reproduce this bug 2 times
>>
>> cordialement, regards,
>>
>> <https://www.lyra-network.com/>
>> Nelson LAMEIRAS
>> Ingénieur Systèmes et Réseaux / Systems and Networks engineer
>> Tel: +33 5 32 09 09 70 <+33%205%2032%2009%2009%2070>
>> nelson.lamei...@lyra-network.com
>> www.lyra-network.com | www.payzen.eu <https://payzen.eu>
>> <https://www.youtube.com/channel/UCrVl1CO_Jlu3KbiRH-tQ_vA>
>> <https://www.linkedin.com/company/lyra-network_2>
>> <https://twitter.com/LyraNetwork>
>> <https://payzen.eu>
>> --
>> Lyra Network, 109 rue de l'innovation, 31670 Labège, FRANCE
>>
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more engine console available

2017-03-24 Thread Nelson Lameiras

Hello Lukas, 

Thanks for you feedback. 
I did something very similar to procedures you sent me. 

Can you confirm me that your HostedEngine vm still has it's SPICE console 
available and is working? 
(otherwise my update went ok) 

cordialement, regards, 


Nelson LAMEIRAS 
Ingénieur Systèmes et Réseaux / Systems and Networks engineer 
Tel: +33 5 32 09 09 70 
nelson.lamei...@lyra-network.com 

www.lyra-network.com | www.payzen.eu 





Lyra Network, 109 rue de l'innovation, 31670 Labège, FRANCE 



From: "Lukáš Kaplan" <lkap...@dragon.cz> 
To: "Nelson Lameiras" <nelson.lamei...@lyra-network.com> 
Cc: "users" <users@ovirt.org> 
Sent: Friday, March 24, 2017 3:22:44 PM 
Subject: Re: [ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more engine 
console available 

Hello Nelson, 
I did same thing today too and it was succesfull. But I used different steps. 
Check this: 
https://www.ovirt.org/documentation/how-to/hosted-engine/#upgrade-hosted-engine 
http://www.ovirt.org/documentation/upgrade-guide/chap-Updates_between_Minor_Releases/
 

Hope it helps you. 

Have a nice day, 

-- 
Lukas Kaplan 


2017-03-24 15:11 GMT+01:00 Nelson Lameiras < nelson.lamei...@lyra-network.com > 
: 



Hello, 

When upgrading my test setup from 4.0 to 4.1, my engine vm lost it's console 
(from SPICE to None in GUI) 

My test setup : 
2 manually built hosts using centos 7.3, ovirt 4.1 
1 manually built hosted engine centos 7.3, oVirt 4.1.0.4-el7, accessible with 
SPICE console via GUI 

I updated ovirt-engine from 4.1.0 to 4.1.1 by doing on engine : 
- yum update 
- engine-setup 
- reboot engine 

When accessing 4.1.1 GUI, Graphics is set to "None" on "Virtual Machines" page, 
with "console button" greyed out (all other VMs have the same Graphics set to 
the same value as before) 
I tried to edit engine VM settings, and console options are same as before 
(SPLICE, QXL). 

I'm hopping this is not a new feature, since if we loose network on engine, 
console is the only way to debug... 

Is this a bug? 

ps. I was able to reproduce this bug 2 times 

cordialement, regards, 


Nelson LAMEIRAS 
Ingénieur Systèmes et Réseaux / Systems and Networks engineer 
Tel: +33 5 32 09 09 70 

nelson.lamei...@lyra-network.com 

www.lyra-network.com | www.payzen.eu 





Lyra Network, 109 rue de l'innovation, 31670 Labège, FRANCE 


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





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

[ovirt-users] engine upgrade 4.1.0 => 4.1.1, no more engine console available

2017-03-24 Thread Nelson Lameiras

Hello, 

When upgrading my test setup from 4.0 to 4.1, my engine vm lost it's console 
(from SPICE to None in GUI) 

My test setup : 
2 manually built hosts using centos 7.3, ovirt 4.1 
1 manually built hosted engine centos 7.3, oVirt 4.1.0.4-el7, accessible with 
SPICE console via GUI 

I updated ovirt-engine from 4.1.0 to 4.1.1 by doing on engine : 
- yum update 
- engine-setup 
- reboot engine 

When accessing 4.1.1 GUI, Graphics is set to "None" on "Virtual Machines" page, 
with "console button" greyed out (all other VMs have the same Graphics set to 
the same value as before) 
I tried to edit engine VM settings, and console options are same as before 
(SPLICE, QXL). 

I'm hopping this is not a new feature, since if we loose network on engine, 
console is the only way to debug... 

Is this a bug? 

ps. I was able to reproduce this bug 2 times 

cordialement, regards, 


Nelson LAMEIRAS 
Ingénieur Systèmes et Réseaux / Systems and Networks engineer 
Tel: +33 5 32 09 09 70 
nelson.lamei...@lyra-network.com 

www.lyra-network.com | www.payzen.eu 





Lyra Network, 109 rue de l'innovation, 31670 Labège, FRANCE 

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

41 matches

Mail list logo