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 experienc
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
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 2
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
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
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 pr
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 d
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,
>>
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"
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.
>
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
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 probl
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 availabl
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 graphic
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 a
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:
> htt
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. C
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 mail
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
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@r
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 H
On Thu, Apr 20, 2017 at 7:39 PM, Martin Sivak wrote:
> 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
>
>
Yes, I mispelled the service in the text of m
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
mailto:arsene.gschw
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
> w
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, t
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 env
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
> 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 serv
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.
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 ans
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.0
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 wit
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 gettin
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:0x000
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. O
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 issu
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 mailthrea
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 c
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
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 se
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
ers"
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 ha
;innovation, 31670 Labège, FRANCE
>
>
> --
> *From: *"Lukáš Kaplan"
> *To: *"Nelson Lameiras"
> *Cc: *"users"
> *Sent: *Friday, March 24, 2017 3:22:44 PM
> *Subject: *Re: [ovirt-users] engine upgrade 4.1.0 =>
on Lameiras"
Cc: "users"
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.o
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
45 matches
Mail list logo