[ovirt-users] Re: Windows VirtIO drivers

[eevans]

My experience is using the vfd file to load the drivers. You can install tools 
after the completed install. Just the virtio scsi drivers are needed for the 
initial install.

Server CD and virtio-win-server.vfd I think is the name of it.

 

Eric Evans

Digital Data Services LLC.

304.660.9080



 

From: Alex McWhirter  
Sent: Thursday, April 02, 2020 12:55 PM
To: Shareef Jalloq 
Cc: Robert Webb ; eev...@digitaldatatechs.com; 
users@ovirt.org
Subject: Re: [ovirt-users] Re: Windows VirtIO drivers

 

I've never had any of these issues... These are my usual windows steps.

1. boot fresh vm into windows ISO image installer.

2. when i get to disk screen (blank because i use VirtIO-SCSI), change windows 
ISO to ovirt guest tools ISO

3. click load drivers, browse, load VirtIO-SCSI driver from CD, go back to disk 
screen.

4. swap ovirt guest tools ISO for Windows ISO, click refresh, then install on 
HDD.

5. when windows boots, swap ISO's again and run the ovirt guest tools 
installer. Sometimes my mouse breaks at this point, but i can click restart in 
the admin portal and after that all is well.

 

On 2020-04-02 12:30, Shareef Jalloq wrote:

I can't seem to do anything.  If I hit the Windows key and start typing, I get 
a black popup with no options.  Win+R doesn't do anything aside from spit out a 
GSpice critical error in the terminal I'm running remote-viewer from.

 

You spend a week trying to launch a VM and when you do, you can't do nowt.  :-)

 

On Thu, Apr 2, 2020 at 5:24 PM Robert Webb mailto:rw...@ropeguru.com> > wrote:

I have yet to figure that one out. All of the VM's I built I had to go old 
school with the tab key and arrow keys...

Very annoying..


From: Shareef Jalloq mailto:shar...@jalloq.co.uk> >
Sent: Thursday, April 2, 2020 12:21 PM
To: eev...@digitaldatatechs.com  
Cc: Robert Webb; users@ovirt.org  
Subject: Re: [ovirt-users] Re: Windows VirtIO drivers

Any idea what I need to do to get a working mouse in a Windows VM?  I can click 
on the SPICE viewer but the mouse pointer is fixed to the left hand border.

On Thu, Apr 2, 2020 at 4:38 PM Shareef Jalloq mailto:shar...@jalloq.co.uk>  >> wrote:
Sorry, I missed all these replies.  Thanks for the help.

I just noticed something funny in the Windows installer.  When you get to the 
point where it can't find any installation media, if you Load Driver, a popup 
appears with a Browse and OK/Cancel options.  I assumed that I should be 
browsing to the floppy here but if you do that, you get an error that no signed 
drivers can be found.  Instead, you just have to hit OK when the popup appears 
and that somehow finds the drivers.

I'm assuming that I will need to install the network driver once the 
installation has finished?

On Wed, Mar 25, 2020 at 8:37 PM mailto:eev...@digitaldatatechs.com>  >> wrote:
Ok. Personally, I like having an ISO repository, but I like the fact that's
it will be optional.
Thanks.

Eric Evans
Digital Data Services LLC.
304.660.9080


-Original Message-
From: Robert Webb mailto:rw...@ropeguru.com> 
 >>
Sent: Wednesday, March 25, 2020 4:26 PM
To: eev...@digitaldatatechs.com  
 >; 
'Shareef Jalloq' mailto:shar...@jalloq.co.uk> 
 >>;
users@ovirt.org   >
Subject: Re: [ovirt-users] Re: Windows VirtIO drivers

It does work that way.

I found that out as I was testing oVirt and had not created a separate ISO
Domain. I believe it was Strahil who pointed me in the right direction.

So if one does not have an ISO Domain, it is no longer required. Along with
the fact that ISO Domains are or in the process of being deprecated.


From: eev...@digitaldatatechs.com  
 > 
mailto:eev...@digitaldatatechs.com> 
 >>
Sent: Wednesday, March 25, 2020 3:13 PM
To: Robert Webb; 'Shareef Jalloq'; users@ovirt.org  
 >
Subject: RE: [ovirt-users] Re: Windows VirtIO drivers

That may be true, but in the ISO domain, when you open virt viewer you can
change the cd very easily...maybe it works that way as well..

Eric Evans
Digital Data Services LLC.
304.660.9080


-Original Message-
From: Robert Webb mailto:rw...@ropeguru.com> 
 >>
Sent: Wednesday, March 25, 2020 2:35 PM
To: 

[ovirt-users] Re: New Issue - Ovirt Status shows '?' or Down for all elements

[eevans]

There are ovirt and an ovirt-dependencies repos. You need both.

 

Eric Evans

Digital Data Services LLC.

304.660.9080



 

From: Mark Steele  
Sent: Thursday, April 02, 2020 7:36 AM
To: Strahil Nikolov 
Cc: users ; Ian Easter 
Subject: [ovirt-users] Re: New Issue - Ovirt Status shows '?' or Down for all 
elements

 

All,

 

We've read some things stating to try running the engine-setup again to get the 
certs inline. That is failing due to missing repo's - does anyone know of 
alternative or archived repo's we could point at to get past that part?

 

[root@ovirt-01 ~]# engine-setup
[ INFO  ] Stage: Initializing
[ INFO  ] Stage: Environment setup
  Configuration files: 
['/etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf', 
'/etc/ovirt-engine-setup.conf.d/10-packaging.conf', 
'/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf']
  Log file: 
/var/log/ovirt-engine/setup/ovirt-engine-setup-20200402072811-h72nc0.log
  Version: otopi-1.3.0 (otopi-1.3.0-1.el6)
[ INFO  ] Stage: Environment packages setup
[ ERROR ] Yum Cannot queue package iproute: Cannot find a valid baseurl for 
repo: ovirt-3.5-jpackage-6.0-generic
[ ERROR ] Failed to execute stage 'Environment packages setup': Cannot find a 
valid baseurl for repo: ovirt-3.5-jpackage-6.0-generic
[ INFO  ] Yum Performing yum transaction rollback
[ INFO  ] Stage: Clean up
  Log file is located at 
/var/log/ovirt-engine/setup/ovirt-engine-setup-20200402072811-h72nc0.log
[ INFO  ] Generating answer file 
'/var/lib/ovirt-engine/setup/answers/20200402072821-setup.conf'
[ INFO  ] Stage: Pre-termination
[ INFO  ] Stage: Termination
[ ERROR ] Execution of setup failed

 

***

Mark Steele

CIO / VP Technical Operations | TelVue Corporation

TelVue - We Share Your Vision

16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054

800.885.8886 | mste...@telvue.com   |  
 http://www.telvue.com

twitter:   http://twitter.com/telvue | facebook:  
 https://www.facebook.com/telvue

 

 

On Thu, Apr 2, 2020 at 12:43 AM Strahil Nikolov mailto:hunter86...@yahoo.com> > wrote:

On April 1, 2020 11:21:34 PM GMT+03:00, Mark Steele mailto:mste...@telvue.com> > wrote:
>More information:
>
>- the host that ovirt hosted engine is running on is not running
>libvirtd.
>When we attempt to start it, it complains about expired certs and
>fails.
>Any ideas on this new development?
>
>***
>*Mark Steele*
>CIO / VP Technical Operations | TelVue Corporation
>TelVue - We Share Your Vision
>16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
>800.885.8886 | mste...@telvue.com   | 
>http://www.telvue.com
>twitter: http://twitter.com/telvue | facebook:
>https://www.facebook.com/telvue
>
>
>On Wed, Apr 1, 2020 at 1:43 PM Mark Steele  > wrote:
>
>> A million years ago - we are going to be upgrading with a new cluster
>but
>> for now, we have this one.
>>
>> It's production and we cannot take it down unless absolutely
>necessary.
>>
>> ***
>> *Mark Steele*
>> CIO / VP Technical Operations | TelVue Corporation
>> TelVue - We Share Your Vision
>> 16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
>> 800.885.8886 | mste...@telvue.com   | 
>> http://www.telvue.com
>> twitter: http://twitter.com/telvue | facebook:
>> https://www.facebook.com/telvue
>>
>>
>> On Wed, Apr 1, 2020 at 1:17 PM Strahil Nikolov
>mailto:hunter86...@yahoo.com> >
>> wrote:
>>
>>> On April 1, 2020 5:40:27 PM GMT+03:00, Mark Steele
>mailto:mste...@telvue.com> >
>>> wrote:
>>> >Two other symptoms:
>>> >
>>> >- Some of the HV's respond 'Destination Host Prohibited' on ping,
>but
>>> >SSH
>>> >works fine
>>> >
>>> >- Seeing this in the log:
>>> >
>>> >2020-04-01 10:34:31,839 ERROR
>>> >[org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp
>Reactor)
>>> >Unable to process messages: javax.net.ssl.SSLException: Received
>fatal
>>> >alert: certificate_expired
>>> >
>>> >
>>> >***
>>> >*Mark Steele*
>>> >CIO / VP Technical Operations | TelVue Corporation
>>> >TelVue - We Share Your Vision
>>> >16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
>>> >800.885.8886 | mste...@telvue.com   | 
>>> >http://www.telvue.com
>>> >twitter: http://twitter.com/telvue | facebook:
>>> >https://www.facebook.com/telvue
>>> >
>>> >
>>> >On Wed, Apr 1, 2020 at 10:25 AM Mark Steele >> > >
>wrote:
>>> >
>>> >> Yesterday we had a storage crash that caused our hosted engine to
>>> >stop and
>>> >> not auto-restart. We manually restarted it and this morning, all
>>> >elements
>>> >> are showing a status of either question mark '?' or a red down
>>> >chevron.
>>> >>
>>> >> We are running version oVirt Engine Version: 3.5.0.1-1.el6.
>>> >>
>>> >> We are chasing it down and see this in the log:
>>> >>
>>> >> 2020-04-01 10:15:53,060 WARN
>>> 

[ovirt-users] Re: DR on hyperconverged deployment

[wodel youchi]

Hi,
Thank you for your reply, but I already did all of that but I didn't
understand everything and I got several problems on the way of doing the
fail-over then a fail-back. I am writing this mail in hope to clarify those
things.
I will try to express my self correctly and give as much details as that I
can.

*The LAB :*
My LAB contains two single-host oVirt-HCI platforms, one to act as the *primary
site  (the source)* the second as the *disaster-recovery site (the target)*.
Each HCI site contains one data domain, the domain is comprised of a
gluster volume which is backed by one brick. The volumes (source and
target) have the same size, and they have been created within the process
of the HCI deployment.
*At the end of the deployment, I detached the deleted the gluster data
domain on the target site, but I didn't delete the target volume.*

My goal is to test the disaster recovery (active-passive DR to be precise)
process on an HCI implementation. To test the fail-over and the fail-back
process entirely.

*Documentation*

RHHI 1.7
Maintaining_Red_Hat_Hyperconverged_Infrastructure_for_Virtualization-en-US
and I started my implementation

I prepared all the ansible playbooks.


*The Test procedure:*

*Fail-over*

1 - Create a Windows10 VM on the source volume.

2 - Replicate to the DR site.

3 - Execute the fail-over procedure and test if the WM is usable in the
target platform.

4 - Detach and Delete the data domain in the target platform without
touching the target volume

5 - Make changes to the Win10 VM on the source volume (creating files and
installing software)

6 - Replicate again to the DR site then execute another fail-over and see
if the modification were synced.


*Fail-back*

1 - Make changes to the Win10 VM on the target volume (deleting files) *and
especially creating a snapshot*

2 - Detach and Delete the data domain in the source platform without
touching the source volume.

3 - Replicate to the source site.

4 - Execute the clean up playbook

5 - Execute the fail-over and WM is usable in the source platform and that
the modifications were synced especially the snapshot


*Things I need to confirm :*

1 - When creating the geo-replication from the primary site to the target
site, we get to a point where we have to create "*Scheduling regular
backups using geo-replication*", from my understanding it's like a cron job
that starts the geo-replication at a specific time (or day time), and from
my testing, the geo-replication starts syncing at that precise time and
when its "*CRAWL STATUS*" reaches "Changelog Crawl" it stops the
synchronization. In other terms when the geo-replication reaches the same
date as the check-point (the specific time).

The smallest time you can get from the configuration window is 24hours,
which means in the event of a disaster, you can at most recover the data
from the day before. *Is this correct?*



*Problems encountered during the test:*

*Fail-over*

1 - When executing the fail-over the first time (ansible-playbook
dr-rhv-failover.yml --tags "fail_over"), the import of the target data
domain failed with the error : *An exception occurred during task
execution. To see the full traceback, use -vvv. The error was:
ovirtsdk4.Error: Fault reason is "Operation Failed". Fault detail is
"[Error in creating a Storage Domain. The selected storage path is not
empty (probably contains another Storage Domain). Either remove the
existing Storage Domain from this path, or change the Storage path).]".
HTTP response code is 400. *I tried manually to import the domain from
oVirt's admin console and I got the same error. so I did the following

- I deleted the target volume and the brick and the sub-directory of the
brick.

- I recreated the volume from scratch.

- I redid the geo-replication synchronization from the source.

- I executed the fail-over and this time the target data domain was
imported correctly and the Win10 VM was started correctly.


2 - I detached then deleted the target data domain without touching the
target volume, then I made change to the Win10 VM on the source site, then
I created a new schedule of geo-replication, and after the replication I
executed another fail-over.

- The Win10 VM started successfully and the changes made were synced.


*Fail-back*
1 - The documentation doesn't explain the fail-back procedure thoroughly.
It doesn't explain what does the dr-cleanup.yml do?

2 - When launching the fail-back playbook at some point I get this message :


*TASK [oVirt.disaster-recovery : Failback Replication Sync pause]
[oVirt.disaster-recovery
: Failback Replication Sync pause][Failback Replication Sync] Please press
ENTER once the destination storage domains are ready to be used for the
destination setup:*
What does this mean?

3 - I did some changed on the Win10 VM and I created snapshot of that VM.

4.a - To replicate the data 

[ovirt-users] Re: NFS permissions error on ISODomain file with correct permissions

[Strahil Nikolov]

On April 2, 2020 9:51:47 PM GMT+03:00, eev...@digitaldatatechs.com wrote:
>It depends on the NAS. What NAS do you have? How is NFS setup and what
>version? It could be several different things but without knowing the
>specific setup, I’d be guessing.
>
> 
>
>Eric Evans
>
>Digital Data Services LLC.
>
>304.660.9080
>
>
>
> 
>
>From: Shareef Jalloq  
>Sent: Thursday, April 02, 2020 10:41 AM
>To: eev...@digitaldatatechs.com
>Cc: users@ovirt.org
>Subject: [ovirt-users] Re: NFS permissions error on ISODomain file with
>correct permissions
>
> 
>
>OK, think this is solved and it was a permissions issue.  I eventually
>logged into the NAS to see if I could see anything different in the
>exports and the ISO Domain didn't have any group ownership rights.
>
> 
>
>This is strange because when you browse the directory from an oVirt
>node, it shows each directory and file as having full permissions. Is
>this an NFS thing?
>
> 
>
>On Thu, Apr 2, 2020 at 3:20 PM Shareef Jalloq  > wrote:
>
>On your second point about an Export domain, how do you configure oVirt
>to look in an Export domain for the Run Once setup?
>
> 
>
>On Thu, Apr 2, 2020 at 3:01 PM Shareef Jalloq  > wrote:
>
>This doesn't seem, to me, to be an issue with the NAS or the mounts. 
>In my original post you can see the VFD files in the mounted directory
>under /rhev.  Is that not what you're asking?
>
> 
>
>I have both the ISODomain and two DataDomain's mounted.  I have a bunch
>of VM's running off this NAS with no issues.  The permissions to the
>VFD files are all correct and I can create and list files in the
>ISODomain with no issue.
>
> 
>
>On Tue, Mar 31, 2020 at 9:40 PM  > wrote:
>
>If you issue the mount command does the path show. 
>
>mount |grep 
>
> 
>
>It looks like the ISO domain is on a NAS, so I would try a mount of the
>actual folder on the ovirt node to make sure you are able to access it.
>Also, can you place it in an export domain instead and try? 
>
>I think version 4.2+ it just needs to be in an export domain.
>
> 
>
>Also make sure the NAS path is correct. Most NAS use a data or shares
>for nfs mounts. (nasname:/shares/
>
> 
>
> 
>
>Eric Evans
>
>Digital Data Services LLC.
>
>304.660.9080
>
>
>
> 
>
>From: Shareef Jalloq  > 
>Sent: Tuesday, March 31, 2020 4:59 AM
>To: users@ovirt.org  
>Subject: [ovirt-users] NFS permissions error on ISODomain file with
>correct permissions
>
> 
>
>Hi,
>
> 
>
>I asked this question in another thread but it seems to have been lost
>in the noise so I'm reposting with a more descriptive subject.
>
> 
>
>I'm trying to start a Windows VM and use the virtio-win VFD floppy to
>get the drivers but the VM startup fails due to a permissions issue
>detailed below.  The permissions look fine to me so why can't the VFD
>be read?
>
> 
>
>Shareef.
>
> 
>
>I found a permissions issue in the engine.log:
>
> 
>
>2020-03-25 21:28:41,662Z ERROR
>[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
>(ForkJoinPool-1-worker-14) [] EVENT_ID: VM_DOWN_ERROR(119), VM win-2019
>is down with error. Exit message: internal error: qemu unexpectedly
>closed the monitor: 2020-03-25T21:28:40.324426Z qemu-kvm: -drive
>file=/rhev/data-center/mnt/nas-01.phoelex.com:_volume2_isostore/41cebb4b-c164-4956-8f44-6426170cd9f5/images/----/virtio-win_servers_amd64.vfd,format=raw,if=none,id=drive-ua-0b9c28b5-f75c-4575-ad85-b5b836f67d61,readonly=on:
>Could not open
>'/rhev/data-center/mnt/nas-01.phoelex.com:_volume2_isostore/41cebb4b-c164-4956-8f44-6426170cd9f5/images/----/virtio-win_servers_amd64.vfd':
>Permission denied.
>
> 
>
>But when I look at that path on the node in question, every folder and
>the final file have the correct vdsm:kvm permissions:
>
> 
>
>[root@ovirt-node-01 ~]# ll
>/rhev/data-center/mnt/nas-01.phoelex.com:_volume2_isostore/41cebb4b-c164-4956-8f44-6426170cd9f5/images/----/virtio-win_servers_amd64.vfd
>-rwxrwxrwx. 1 vdsm kvm 2949120 Mar 25 21:24
>/rhev/data-center/mnt/nas-01.phoelex.com:_volume2_isostore/41cebb4b-c164-4956-8f44-6426170cd9f5/images/----/virtio-win_servers_amd64.vfd
>
> 
>
>The files were uploaded to the ISO domain using:
>
> 
>
>engine-iso-uploader --iso-domain=iso_storage upload virtio-win.iso
>virtio-win_servers_amd64.vfd 
>
> 

Hey Shareef,

Many users report  that they  use 'all_squash' with  anonuid  36 and anonguid 
36.
The  all  squash is forcing anyone using the NFS to the  user  nfsnobody with 
uid:gid '36:36'  -> which should be  vdsm:kvm on the Hypervisors.

Best Regards,
Strahil Nikolov
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 

[ovirt-users] Re: New Issue - Ovirt Status shows '?' or Down for all elements

[Strahil Nikolov]

On April 2, 2020 3:26:14 PM GMT+03:00, Mark Steele  wrote:
>As a followup - is it possible to move the hosted-engine to another HV
>manually? Meaning we shutdown the hosted-engine VM, and copy it's XML
>to
>another HV and fire it up over there where libvirt IS running?
>
>If that is possible, where do we find the live / running XML files on a
>host?
>
>Mark
>
>***
>*Mark Steele*
>CIO / VP Technical Operations | TelVue Corporation
>TelVue - We Share Your Vision
>16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
>800.885.8886 | mste...@telvue.com | http://www.telvue.com
>twitter: http://twitter.com/telvue | facebook:
>https://www.facebook.com/telvue
>
>
>On Thu, Apr 2, 2020 at 7:35 AM Mark Steele  wrote:
>
>> All,
>>
>> We've read some things stating to try running the engine-setup again
>to
>> get the certs inline. That is failing due to missing repo's - does
>anyone
>> know of alternative or archived repo's we could point at to get past
>that
>> part?
>>
>> [root@ovirt-01 ~]# engine-setup
>> [ INFO  ] Stage: Initializing
>> [ INFO  ] Stage: Environment setup
>>   Configuration files:
>['/etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf',
>'/etc/ovirt-engine-setup.conf.d/10-packaging.conf',
>'/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf']
>>   Log file:
>/var/log/ovirt-engine/setup/ovirt-engine-setup-20200402072811-h72nc0.log
>>   Version: otopi-1.3.0 (otopi-1.3.0-1.el6)
>> [ INFO  ] Stage: Environment packages setup
>> [ ERROR ] Yum Cannot queue package iproute: Cannot find a valid
>baseurl for repo: ovirt-3.5-jpackage-6.0-generic
>> [ ERROR ] Failed to execute stage 'Environment packages setup':
>Cannot find a valid baseurl for repo: ovirt-3.5-jpackage-6.0-generic
>> [ INFO  ] Yum Performing yum transaction rollback
>> [ INFO  ] Stage: Clean up
>>   Log file is located at
>/var/log/ovirt-engine/setup/ovirt-engine-setup-20200402072811-h72nc0.log
>> [ INFO  ] Generating answer file
>'/var/lib/ovirt-engine/setup/answers/20200402072821-setup.conf'
>> [ INFO  ] Stage: Pre-termination
>> [ INFO  ] Stage: Termination
>> [ ERROR ] Execution of setup failed
>>
>>
>> ***
>> *Mark Steele*
>> CIO / VP Technical Operations | TelVue Corporation
>> TelVue - We Share Your Vision
>> 16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
>> 800.885.8886 | mste...@telvue.com | http://www.telvue.com
>> twitter: http://twitter.com/telvue | facebook:
>> https://www.facebook.com/telvue
>>
>>
>> On Thu, Apr 2, 2020 at 12:43 AM Strahil Nikolov
>
>> wrote:
>>
>>> On April 1, 2020 11:21:34 PM GMT+03:00, Mark Steele
>
>>> wrote:
>>> >More information:
>>> >
>>> >- the host that ovirt hosted engine is running on is not running
>>> >libvirtd.
>>> >When we attempt to start it, it complains about expired certs and
>>> >fails.
>>> >Any ideas on this new development?
>>> >
>>> >***
>>> >*Mark Steele*
>>> >CIO / VP Technical Operations | TelVue Corporation
>>> >TelVue - We Share Your Vision
>>> >16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
>>> >800.885.8886 | mste...@telvue.com | http://www.telvue.com
>>> >twitter: http://twitter.com/telvue | facebook:
>>> >https://www.facebook.com/telvue
>>> >
>>> >
>>> >On Wed, Apr 1, 2020 at 1:43 PM Mark Steele 
>wrote:
>>> >
>>> >> A million years ago - we are going to be upgrading with a new
>cluster
>>> >but
>>> >> for now, we have this one.
>>> >>
>>> >> It's production and we cannot take it down unless absolutely
>>> >necessary.
>>> >>
>>> >> ***
>>> >> *Mark Steele*
>>> >> CIO / VP Technical Operations | TelVue Corporation
>>> >> TelVue - We Share Your Vision
>>> >> 16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
>>> >> 800.885.8886 | mste...@telvue.com | http://www.telvue.com
>>> >> twitter: http://twitter.com/telvue | facebook:
>>> >> https://www.facebook.com/telvue
>>> >>
>>> >>
>>> >> On Wed, Apr 1, 2020 at 1:17 PM Strahil Nikolov
>>> >
>>> >> wrote:
>>> >>
>>> >>> On April 1, 2020 5:40:27 PM GMT+03:00, Mark Steele
>>> >
>>> >>> wrote:
>>> >>> >Two other symptoms:
>>> >>> >
>>> >>> >- Some of the HV's respond 'Destination Host Prohibited' on
>ping,
>>> >but
>>> >>> >SSH
>>> >>> >works fine
>>> >>> >
>>> >>> >- Seeing this in the log:
>>> >>> >
>>> >>> >2020-04-01 10:34:31,839 ERROR
>>> >>> >[org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp
>>> >Reactor)
>>> >>> >Unable to process messages: javax.net.ssl.SSLException:
>Received
>>> >fatal
>>> >>> >alert: certificate_expired
>>> >>> >
>>> >>> >
>>> >>> >***
>>> >>> >*Mark Steele*
>>> >>> >CIO / VP Technical Operations | TelVue Corporation
>>> >>> >TelVue - We Share Your Vision
>>> >>> >16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
>>> >>> >800.885.8886 | mste...@telvue.com | http://www.telvue.com
>>> >>> >twitter: http://twitter.com/telvue | facebook:
>>> >>> >https://www.facebook.com/telvue
>>> >>> >
>>> >>> >
>>> >>> >On Wed, Apr 1, 2020 at 10:25 AM Mark Steele
>
>>> >wrote:
>>> >>> >
>>> >>> >> Yesterday we had a storage crash that caused our hosted
>engine to
>>> >>> 

[ovirt-users] Re: Failing to redeploy self hosted engine

[Strahil Nikolov]

On April 2, 2020 9:27:20 AM GMT+03:00, Yedidyah Bar David  
wrote:
>On Thu, Apr 2, 2020 at 7:41 AM Strahil Nikolov 
>wrote:
>>
>> On April 1, 2020 5:28:35 PM GMT+03:00, eev...@digitaldatatechs.com
>wrote:
>>
>>https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html/self-hosted_engine_guide/troubleshooting
>> >
>> >
>> >
>> >It should tell you the steps to take to troubleshoot your
>deployment.
>> >
>> >
>> >
>> >Eric Evans
>> >
>> >Digital Data Services LLC.
>> >
>> >304.660.9080
>> >
>> >
>> >
>> >
>> >
>> >From: Maton, Brett 
>> >Sent: Tuesday, March 31, 2020 11:52 PM
>> >To: eev...@digitaldatatechs.com
>> >Cc: Ovirt Users 
>> >Subject: [ovirt-users] Re: Failing to redeploy self hosted engine
>> >
>> >
>> >
>> >So, how would I go about disabling global maintenance when hosted
>> >engine isn't running?
>> >
>> >
>> >
>> >I tried editing /var/lib/ovirt-hosted-engine-ha/ha.conf and setting
>> >both values to False but that didn't help.
>> >
>> >
>> >
>> >local_maintenance=False
>> >local_maintenance_manual=False
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >On Tue, 31 Mar 2020 at 23:01, Maton, Brett > > > wrote:
>> >
>> >Oooh probably...
>> >
>> >
>> >
>> >I'll give that a try in the morning, cheers for the tip!
>> >
>> >
>> >
>> >On Tue, 31 Mar 2020, 21:23 , > > > wrote:
>> >
>> >Did you put the ovirt host into global maintenance mode? That may be
>> >the issue.
>> >
>> >
>> >
>> >Eric Evans
>> >
>> >Digital Data Services LLC.
>> >
>> >304.660.9080
>> >
>> >
>> >
>> >
>> >
>> >From: Maton, Brett > > >
>> >Sent: Tuesday, March 31, 2020 2:35 PM
>> >To: Ovirt Users mailto:users@ovirt.org> >
>> >Subject: [ovirt-users] Failing to redeploy self hosted engine
>> >
>> >
>> >
>> >I keep running into this error when I try to (re)deploy self-hosted
>> >engine.
>> >
>> >
>> >
>> >
>> >
>> ># ovirt-hosted-engine-cleanup
>> >
>> ># hosted-engine --deploy
>> >
>> >...
>> >
>> >...
>> >
>> >[ INFO  ] TASK [ovirt.hosted_engine_setup : Fail with error
>> >description]
>> >
>> >[ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg":
>"The
>> >host has been set in non_operational status, deployment errors:  
>code
>> >9000: Failed to verify Power Management configuration for Host
>> >physhost01.example.com  ,   fix
>> >accordingly and re-deploy."}
>> >
>> >
>> >
>> >I shut down all of the VM's and detached the storage before cleaning
>up
>> >and trying to re-deploy the hosted engine, first time I've run into
>> >this particular problem.
>> >
>> >
>> >
>> >Any help appreciated
>> >
>> >
>> >
>> >Brett
>> >
>> >
>>
>> I'm not very pleased of this article.
>
>One more place to check is:
>
>https://www.ovirt.org/images/Hosted-Engine-4.3-deep-dive.pdf
>
>I found it a few months ago, and added to the site under:
>
>https://www.ovirt.org/community/get-involved/resources/slide-decks.html
>
>But that one sadly isn't easy to find either. Google does know about
>it, but only if you know what to search for. We should probably add a
>few more internal links to make sure all content is easily accessible.
>
>> Last time I needed to fix my HostedEngine, I couldn't find anything
>useful.
>> Looking into retrospection ,  If I knew  how to attach a rescue media
>and boot from it  - it would take no more than 10 min to fix it - way
>faster than to restore from backup.
>
>There is an option '--vm-conf' you can use with '--vm-start', to pass
>your own libvirt-style conf. There you can add a virtual CD with an
>image or whatever.
>See slide 58 in above presentation.
>
>Best regards,

Hey Didi,

Last time I tried  the '--vm-conf' ->  it  didn't work :)
I  hope  it does  now.

Anyway, that PDF  is  10 times  more valuable -  I  like  it  !

Maybe  we can improve  the  ovirt  page  and make it  more  easy to find  ?

Best Regards,
Strahil Nikolov
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/U26HNHJEPIOWV3V3H5NL4D455RY3BG6V/

[ovirt-users] Re: NFS permissions error on ISODomain file with correct permissions

[eevans]

It depends on the NAS. What NAS do you have? How is NFS setup and what version? 
It could be several different things but without knowing the specific setup, 
I’d be guessing.

 

Eric Evans

Digital Data Services LLC.

304.660.9080



 

From: Shareef Jalloq  
Sent: Thursday, April 02, 2020 10:41 AM
To: eev...@digitaldatatechs.com
Cc: users@ovirt.org
Subject: [ovirt-users] Re: NFS permissions error on ISODomain file with correct 
permissions

 

OK, think this is solved and it was a permissions issue.  I eventually logged 
into the NAS to see if I could see anything different in the exports and the 
ISO Domain didn't have any group ownership rights.

 

This is strange because when you browse the directory from an oVirt node, it 
shows each directory and file as having full permissions. Is this an NFS thing?

 

On Thu, Apr 2, 2020 at 3:20 PM Shareef Jalloq mailto:shar...@jalloq.co.uk> > wrote:

On your second point about an Export domain, how do you configure oVirt to look 
in an Export domain for the Run Once setup?

 

On Thu, Apr 2, 2020 at 3:01 PM Shareef Jalloq mailto:shar...@jalloq.co.uk> > wrote:

This doesn't seem, to me, to be an issue with the NAS or the mounts.  In my 
original post you can see the VFD files in the mounted directory under /rhev.  
Is that not what you're asking?

 

I have both the ISODomain and two DataDomain's mounted.  I have a bunch of VM's 
running off this NAS with no issues.  The permissions to the VFD files are all 
correct and I can create and list files in the ISODomain with no issue.

 

On Tue, Mar 31, 2020 at 9:40 PM mailto:eev...@digitaldatatechs.com> > wrote:

If you issue the mount command does the path show. 

mount |grep 

 

It looks like the ISO domain is on a NAS, so I would try a mount of the actual 
folder on the ovirt node to make sure you are able to access it. Also, can you 
place it in an export domain instead and try? 

I think version 4.2+ it just needs to be in an export domain.

 

Also make sure the NAS path is correct. Most NAS use a data or shares for nfs 
mounts. (nasname:/shares/

 

 

Eric Evans

Digital Data Services LLC.

304.660.9080



 

From: Shareef Jalloq mailto:shar...@jalloq.co.uk> > 
Sent: Tuesday, March 31, 2020 4:59 AM
To: users@ovirt.org  
Subject: [ovirt-users] NFS permissions error on ISODomain file with correct 
permissions

 

Hi,

 

I asked this question in another thread but it seems to have been lost in the 
noise so I'm reposting with a more descriptive subject.

 

I'm trying to start a Windows VM and use the virtio-win VFD floppy to get the 
drivers but the VM startup fails due to a permissions issue detailed below.  
The permissions look fine to me so why can't the VFD be read?

 

Shareef.

 

I found a permissions issue in the engine.log:

 

2020-03-25 21:28:41,662Z ERROR 
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(ForkJoinPool-1-worker-14) [] EVENT_ID: VM_DOWN_ERROR(119), VM win-2019 is down 
with error. Exit message: internal error: qemu unexpectedly closed the monitor: 
2020-03-25T21:28:40.324426Z qemu-kvm: -drive 
file=/rhev/data-center/mnt/nas-01.phoelex.com:_volume2_isostore/41cebb4b-c164-4956-8f44-6426170cd9f5/images/----/virtio-win_servers_amd64.vfd,format=raw,if=none,id=drive-ua-0b9c28b5-f75c-4575-ad85-b5b836f67d61,readonly=on:
 Could not open 
'/rhev/data-center/mnt/nas-01.phoelex.com:_volume2_isostore/41cebb4b-c164-4956-8f44-6426170cd9f5/images/----/virtio-win_servers_amd64.vfd':
 Permission denied.

 

But when I look at that path on the node in question, every folder and the 
final file have the correct vdsm:kvm permissions:

 

[root@ovirt-node-01 ~]# ll 
/rhev/data-center/mnt/nas-01.phoelex.com:_volume2_isostore/41cebb4b-c164-4956-8f44-6426170cd9f5/images/----/virtio-win_servers_amd64.vfd
-rwxrwxrwx. 1 vdsm kvm 2949120 Mar 25 21:24 
/rhev/data-center/mnt/nas-01.phoelex.com:_volume2_isostore/41cebb4b-c164-4956-8f44-6426170cd9f5/images/----/virtio-win_servers_amd64.vfd

 

The files were uploaded to the ISO domain using:

 

engine-iso-uploader --iso-domain=iso_storage upload virtio-win.iso 
virtio-win_servers_amd64.vfd 

 


___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/ELA7O7B5OJAUUYCACITMX6I3WDXLFGA2/

[ovirt-users] Re: Windows VirtIO drivers

[Shareef Jalloq]

OK, thanks.  I might try that flow next time.

In the end I managed to tab/arrow through the start menu to install the
drivers from the virtio-win.iso.  I'll now install the guest tools.

On Thu, Apr 2, 2020 at 5:55 PM Alex McWhirter  wrote:

> I've never had any of these issues... These are my usual windows steps.
>
> 1. boot fresh vm into windows ISO image installer.
>
> 2. when i get to disk screen (blank because i use VirtIO-SCSI), change
> windows ISO to ovirt guest tools ISO
>
> 3. click load drivers, browse, load VirtIO-SCSI driver from CD, go back to
> disk screen.
>
> 4. swap ovirt guest tools ISO for Windows ISO, click refresh, then install
> on HDD.
>
> 5. when windows boots, swap ISO's again and run the ovirt guest tools
> installer. Sometimes my mouse breaks at this point, but i can click restart
> in the admin portal and after that all is well.
>
>
> On 2020-04-02 12:30, Shareef Jalloq wrote:
>
> I can't seem to do anything.  If I hit the Windows key and start typing, I
> get a black popup with no options.  Win+R doesn't do anything aside from
> spit out a GSpice critical error in the terminal I'm running remote-viewer
> from.
>
> You spend a week trying to launch a VM and when you do, you can't do
> nowt.  :-)
>
> On Thu, Apr 2, 2020 at 5:24 PM Robert Webb  wrote:
>
> I have yet to figure that one out. All of the VM's I built I had to go old
> school with the tab key and arrow keys...
>
> Very annoying..
>
> 
> From: Shareef Jalloq 
> Sent: Thursday, April 2, 2020 12:21 PM
> To: eev...@digitaldatatechs.com
> Cc: Robert Webb; users@ovirt.org
> Subject: Re: [ovirt-users] Re: Windows VirtIO drivers
>
> Any idea what I need to do to get a working mouse in a Windows VM?  I can
> click on the SPICE viewer but the mouse pointer is fixed to the left hand
> border.
>
> On Thu, Apr 2, 2020 at 4:38 PM Shareef Jalloq  > wrote:
> Sorry, I missed all these replies.  Thanks for the help.
>
> I just noticed something funny in the Windows installer.  When you get to
> the point where it can't find any installation media, if you Load Driver, a
> popup appears with a Browse and OK/Cancel options.  I assumed that I should
> be browsing to the floppy here but if you do that, you get an error that no
> signed drivers can be found.  Instead, you just have to hit OK when the
> popup appears and that somehow finds the drivers.
>
> I'm assuming that I will need to install the network driver once the
> installation has finished?
>
> On Wed, Mar 25, 2020 at 8:37 PM  eev...@digitaldatatechs.com>> wrote:
> Ok. Personally, I like having an ISO repository, but I like the fact that's
> it will be optional.
> Thanks.
>
> Eric Evans
> Digital Data Services LLC.
> 304.660.9080
>
>
> -Original Message-
> From: Robert Webb mailto:rw...@ropeguru.com>>
> Sent: Wednesday, March 25, 2020 4:26 PM
> To: eev...@digitaldatatechs.com;
> 'Shareef Jalloq' mailto:shar...@jalloq.co.uk>>;
> users@ovirt.org
> Subject: Re: [ovirt-users] Re: Windows VirtIO drivers
>
> It does work that way.
>
> I found that out as I was testing oVirt and had not created a separate ISO
> Domain. I believe it was Strahil who pointed me in the right direction.
>
> So if one does not have an ISO Domain, it is no longer required. Along with
> the fact that ISO Domains are or in the process of being deprecated.
>
> 
> From: eev...@digitaldatatechs.com <
> eev...@digitaldatatechs.com>
> Sent: Wednesday, March 25, 2020 3:13 PM
> To: Robert Webb; 'Shareef Jalloq'; users@ovirt.org
> Subject: RE: [ovirt-users] Re: Windows VirtIO drivers
>
> That may be true, but in the ISO domain, when you open virt viewer you can
> change the cd very easily...maybe it works that way as well..
>
> Eric Evans
> Digital Data Services LLC.
> 304.660.9080
>
>
> -Original Message-
> From: Robert Webb mailto:rw...@ropeguru.com>>
> Sent: Wednesday, March 25, 2020 2:35 PM
> To: eev...@digitaldatatechs.com;
> 'Shareef Jalloq' mailto:shar...@jalloq.co.uk>>;
> users@ovirt.org
> Subject: [ovirt-users] Re: Windows VirtIO drivers
>
> Don't think you have to use the ISO Domain any longer.
>
> You can upload to a Data Domain and when you highlight the VM in the
> management GUI, select the three dots in the top left for extra options and
> there is a change cd option. That option will allow for attaching an ISO
> from a Data Domain.
>
> That is what I recall when I was using oVirt a month or so ago.
>
> 
> From: eev...@digitaldatatechs.com <
> eev...@digitaldatatechs.com>
> Sent: Wednesday, March 25, 2020 2:28 PM
> To: 'Shareef Jalloq'; 

[ovirt-users] Re: Windows VirtIO drivers

[Alex McWhirter]

I've never had any of these issues... These are my usual windows steps. 

1. boot fresh vm into windows ISO image installer. 


2. when i get to disk screen (blank because i use VirtIO-SCSI), change
windows ISO to ovirt guest tools ISO 


3. click load drivers, browse, load VirtIO-SCSI driver from CD, go back
to disk screen. 


4. swap ovirt guest tools ISO for Windows ISO, click refresh, then
install on HDD. 


5. when windows boots, swap ISO's again and run the ovirt guest tools
installer. Sometimes my mouse breaks at this point, but i can click
restart in the admin portal and after that all is well. 


On 2020-04-02 12:30, Shareef Jalloq wrote:

I can't seem to do anything.  If I hit the Windows key and start typing, I get a black popup with no options.  Win+R doesn't do anything aside from spit out a GSpice critical error in the terminal I'm running remote-viewer from. 

You spend a week trying to launch a VM and when you do, you can't do nowt.  :-) 

On Thu, Apr 2, 2020 at 5:24 PM Robert Webb  wrote: 


I have yet to figure that one out. All of the VM's I built I had to go old 
school with the tab key and arrow keys...

Very annoying..


From: Shareef Jalloq 
Sent: Thursday, April 2, 2020 12:21 PM
To: eev...@digitaldatatechs.com
Cc: Robert Webb; users@ovirt.org
Subject: Re: [ovirt-users] Re: Windows VirtIO drivers

Any idea what I need to do to get a working mouse in a Windows VM?  I can click 
on the SPICE viewer but the mouse pointer is fixed to the left hand border.

On Thu, Apr 2, 2020 at 4:38 PM Shareef Jalloq 
mailto:shar...@jalloq.co.uk>> wrote:
Sorry, I missed all these replies.  Thanks for the help.

I just noticed something funny in the Windows installer.  When you get to the 
point where it can't find any installation media, if you Load Driver, a popup 
appears with a Browse and OK/Cancel options.  I assumed that I should be 
browsing to the floppy here but if you do that, you get an error that no signed 
drivers can be found.  Instead, you just have to hit OK when the popup appears 
and that somehow finds the drivers.

I'm assuming that I will need to install the network driver once the 
installation has finished?

On Wed, Mar 25, 2020 at 8:37 PM 
mailto:eev...@digitaldatatechs.com>> wrote:
Ok. Personally, I like having an ISO repository, but I like the fact that's
it will be optional.
Thanks.

Eric Evans
Digital Data Services LLC.
304.660.9080

-Original Message-
From: Robert Webb mailto:rw...@ropeguru.com>>
Sent: Wednesday, March 25, 2020 4:26 PM
To: eev...@digitaldatatechs.com; 'Shareef Jalloq' 
mailto:shar...@jalloq.co.uk>>;
users@ovirt.org
Subject: Re: [ovirt-users] Re: Windows VirtIO drivers

It does work that way.

I found that out as I was testing oVirt and had not created a separate ISO
Domain. I believe it was Strahil who pointed me in the right direction.

So if one does not have an ISO Domain, it is no longer required. Along with
the fact that ISO Domains are or in the process of being deprecated.


From: eev...@digitaldatatechs.com 
mailto:eev...@digitaldatatechs.com>>
Sent: Wednesday, March 25, 2020 3:13 PM
To: Robert Webb; 'Shareef Jalloq'; users@ovirt.org
Subject: RE: [ovirt-users] Re: Windows VirtIO drivers

That may be true, but in the ISO domain, when you open virt viewer you can
change the cd very easily...maybe it works that way as well..

Eric Evans
Digital Data Services LLC.
304.660.9080

-Original Message-
From: Robert Webb mailto:rw...@ropeguru.com>>
Sent: Wednesday, March 25, 2020 2:35 PM
To: eev...@digitaldatatechs.com; 'Shareef Jalloq' 
mailto:shar...@jalloq.co.uk>>;
users@ovirt.org
Subject: [ovirt-users] Re: Windows VirtIO drivers

Don't think you have to use the ISO Domain any longer.

You can upload to a Data Domain and when you highlight the VM in the
management GUI, select the three dots in the top left for extra options and
there is a change cd option. That option will allow for attaching an ISO
from a Data Domain.

That is what I recall when I was using oVirt a month or so ago.


From: eev...@digitaldatatechs.com 
mailto:eev...@digitaldatatechs.com>>
Sent: Wednesday, March 25, 2020 2:28 PM
To: 'Shareef Jalloq'; users@ovirt.org
Subject: [ovirt-users] Re: Windows VirtIO drivers

You have to copy the iso and vfd files to the ISO domain to make them
available to the vm's that need drivers.

engine-iso-uploader options list
# engine-iso-uploader options upload file file file Documentation is found
here: https://www.ovirt.org/documentation/admin-guide/chap-Utilities.html

Eric Evans
Digital Data Services LLC.
304.660.9080
[cid:image001.jpg@01D602B1.9FEA2EC0]

From: Shareef Jalloq 

[ovirt-users] Re: Windows VirtIO drivers

[Shareef Jalloq]

I can't seem to do anything.  If I hit the Windows key and start typing, I
get a black popup with no options.  Win+R doesn't do anything aside from
spit out a GSpice critical error in the terminal I'm running remote-viewer
from.

You spend a week trying to launch a VM and when you do, you can't do nowt.
:-)

On Thu, Apr 2, 2020 at 5:24 PM Robert Webb  wrote:

> I have yet to figure that one out. All of the VM's I built I had to go old
> school with the tab key and arrow keys...
>
> Very annoying..
>
> 
> From: Shareef Jalloq 
> Sent: Thursday, April 2, 2020 12:21 PM
> To: eev...@digitaldatatechs.com
> Cc: Robert Webb; users@ovirt.org
> Subject: Re: [ovirt-users] Re: Windows VirtIO drivers
>
> Any idea what I need to do to get a working mouse in a Windows VM?  I can
> click on the SPICE viewer but the mouse pointer is fixed to the left hand
> border.
>
> On Thu, Apr 2, 2020 at 4:38 PM Shareef Jalloq  > wrote:
> Sorry, I missed all these replies.  Thanks for the help.
>
> I just noticed something funny in the Windows installer.  When you get to
> the point where it can't find any installation media, if you Load Driver, a
> popup appears with a Browse and OK/Cancel options.  I assumed that I should
> be browsing to the floppy here but if you do that, you get an error that no
> signed drivers can be found.  Instead, you just have to hit OK when the
> popup appears and that somehow finds the drivers.
>
> I'm assuming that I will need to install the network driver once the
> installation has finished?
>
> On Wed, Mar 25, 2020 at 8:37 PM  eev...@digitaldatatechs.com>> wrote:
> Ok. Personally, I like having an ISO repository, but I like the fact that's
> it will be optional.
> Thanks.
>
> Eric Evans
> Digital Data Services LLC.
> 304.660.9080
>
>
> -Original Message-
> From: Robert Webb mailto:rw...@ropeguru.com>>
> Sent: Wednesday, March 25, 2020 4:26 PM
> To: eev...@digitaldatatechs.com;
> 'Shareef Jalloq' mailto:shar...@jalloq.co.uk>>;
> users@ovirt.org
> Subject: Re: [ovirt-users] Re: Windows VirtIO drivers
>
> It does work that way.
>
> I found that out as I was testing oVirt and had not created a separate ISO
> Domain. I believe it was Strahil who pointed me in the right direction.
>
> So if one does not have an ISO Domain, it is no longer required. Along with
> the fact that ISO Domains are or in the process of being deprecated.
>
> 
> From: eev...@digitaldatatechs.com <
> eev...@digitaldatatechs.com>
> Sent: Wednesday, March 25, 2020 3:13 PM
> To: Robert Webb; 'Shareef Jalloq'; users@ovirt.org
> Subject: RE: [ovirt-users] Re: Windows VirtIO drivers
>
> That may be true, but in the ISO domain, when you open virt viewer you can
> change the cd very easily...maybe it works that way as well..
>
> Eric Evans
> Digital Data Services LLC.
> 304.660.9080
>
>
> -Original Message-
> From: Robert Webb mailto:rw...@ropeguru.com>>
> Sent: Wednesday, March 25, 2020 2:35 PM
> To: eev...@digitaldatatechs.com;
> 'Shareef Jalloq' mailto:shar...@jalloq.co.uk>>;
> users@ovirt.org
> Subject: [ovirt-users] Re: Windows VirtIO drivers
>
> Don't think you have to use the ISO Domain any longer.
>
> You can upload to a Data Domain and when you highlight the VM in the
> management GUI, select the three dots in the top left for extra options and
> there is a change cd option. That option will allow for attaching an ISO
> from a Data Domain.
>
> That is what I recall when I was using oVirt a month or so ago.
>
> 
> From: eev...@digitaldatatechs.com <
> eev...@digitaldatatechs.com>
> Sent: Wednesday, March 25, 2020 2:28 PM
> To: 'Shareef Jalloq'; users@ovirt.org
> Subject: [ovirt-users] Re: Windows VirtIO drivers
>
> You have to copy the iso and vfd files to the ISO domain to make them
> available to the vm's that need drivers.
>
> engine-iso-uploader options list
> # engine-iso-uploader options upload file file file Documentation is found
> here: https://www.ovirt.org/documentation/admin-guide/chap-Utilities.html
>
> Eric Evans
> Digital Data Services LLC.
> 304.660.9080
> [cid:image001.jpg@01D602B1.9FEA2EC0]
>
> From: Shareef Jalloq mailto:shar...@jalloq.co.uk>>
> Sent: Wednesday, March 25, 2020 1:51 PM
> To: users@ovirt.org
> Subject: [ovirt-users] Windows VirtIO drivers
>
> Hi,
>
> it seems the online documentation regarding the windows installation steps
> is well out of date.  Where is there any current documentation on where to
> get the VirtIO drivers for a Windows installation?
>
> From a bit of Googling, it seems that I need to 'yum 

[ovirt-users] Re: Windows VirtIO drivers

[Shareef Jalloq]

Any idea what I need to do to get a working mouse in a Windows VM?  I can
click on the SPICE viewer but the mouse pointer is fixed to the left hand
border.

On Thu, Apr 2, 2020 at 4:38 PM Shareef Jalloq  wrote:

> Sorry, I missed all these replies.  Thanks for the help.
>
> I just noticed something funny in the Windows installer.  When you get to
> the point where it can't find any installation media, if you Load Driver, a
> popup appears with a Browse and OK/Cancel options.  I assumed that I should
> be browsing to the floppy here but if you do that, you get an error that no
> signed drivers can be found.  Instead, you just have to hit OK when the
> popup appears and that somehow finds the drivers.
>
> I'm assuming that I will need to install the network driver once the
> installation has finished?
>
> On Wed, Mar 25, 2020 at 8:37 PM  wrote:
>
>> Ok. Personally, I like having an ISO repository, but I like the fact
>> that's
>> it will be optional.
>> Thanks.
>>
>> Eric Evans
>> Digital Data Services LLC.
>> 304.660.9080
>>
>>
>> -Original Message-
>> From: Robert Webb 
>> Sent: Wednesday, March 25, 2020 4:26 PM
>> To: eev...@digitaldatatechs.com; 'Shareef Jalloq' ;
>> users@ovirt.org
>> Subject: Re: [ovirt-users] Re: Windows VirtIO drivers
>>
>> It does work that way.
>>
>> I found that out as I was testing oVirt and had not created a separate ISO
>> Domain. I believe it was Strahil who pointed me in the right direction.
>>
>> So if one does not have an ISO Domain, it is no longer required. Along
>> with
>> the fact that ISO Domains are or in the process of being deprecated.
>>
>> 
>> From: eev...@digitaldatatechs.com 
>> Sent: Wednesday, March 25, 2020 3:13 PM
>> To: Robert Webb; 'Shareef Jalloq'; users@ovirt.org
>> Subject: RE: [ovirt-users] Re: Windows VirtIO drivers
>>
>> That may be true, but in the ISO domain, when you open virt viewer you can
>> change the cd very easily...maybe it works that way as well..
>>
>> Eric Evans
>> Digital Data Services LLC.
>> 304.660.9080
>>
>>
>> -Original Message-
>> From: Robert Webb 
>> Sent: Wednesday, March 25, 2020 2:35 PM
>> To: eev...@digitaldatatechs.com; 'Shareef Jalloq' ;
>> users@ovirt.org
>> Subject: [ovirt-users] Re: Windows VirtIO drivers
>>
>> Don't think you have to use the ISO Domain any longer.
>>
>> You can upload to a Data Domain and when you highlight the VM in the
>> management GUI, select the three dots in the top left for extra options
>> and
>> there is a change cd option. That option will allow for attaching an ISO
>> from a Data Domain.
>>
>> That is what I recall when I was using oVirt a month or so ago.
>>
>> 
>> From: eev...@digitaldatatechs.com 
>> Sent: Wednesday, March 25, 2020 2:28 PM
>> To: 'Shareef Jalloq'; users@ovirt.org
>> Subject: [ovirt-users] Re: Windows VirtIO drivers
>>
>> You have to copy the iso and vfd files to the ISO domain to make them
>> available to the vm's that need drivers.
>>
>> engine-iso-uploader options list
>> # engine-iso-uploader options upload file file file Documentation is found
>> here: https://www.ovirt.org/documentation/admin-guide/chap-Utilities.html
>>
>> Eric Evans
>> Digital Data Services LLC.
>> 304.660.9080
>> [cid:image001.jpg@01D602B1.9FEA2EC0]
>>
>> From: Shareef Jalloq 
>> Sent: Wednesday, March 25, 2020 1:51 PM
>> To: users@ovirt.org
>> Subject: [ovirt-users] Windows VirtIO drivers
>>
>> Hi,
>>
>> it seems the online documentation regarding the windows installation steps
>> is well out of date.  Where is there any current documentation on where to
>> get the VirtIO drivers for a Windows installation?
>>
>> From a bit of Googling, it seems that I need to 'yum install virtio-win'
>> on
>> the engine VM and then copy the relevant .iso/.vfd to the ISO domain.  Is
>> that correct?
>>
>> Where is the documentation maintained and how do I open a bug on it?
>>
>> Thanks, Shareef.
>>
>>
>>
>>
>>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/NSVUCZ63DZCWTUMV2WYHA6WRTZMGGK5U/

[ovirt-users] Re: Windows VirtIO drivers

[Shareef Jalloq]

Sorry, I missed all these replies.  Thanks for the help.

I just noticed something funny in the Windows installer.  When you get to
the point where it can't find any installation media, if you Load Driver, a
popup appears with a Browse and OK/Cancel options.  I assumed that I should
be browsing to the floppy here but if you do that, you get an error that no
signed drivers can be found.  Instead, you just have to hit OK when the
popup appears and that somehow finds the drivers.

I'm assuming that I will need to install the network driver once the
installation has finished?

On Wed, Mar 25, 2020 at 8:37 PM  wrote:

> Ok. Personally, I like having an ISO repository, but I like the fact that's
> it will be optional.
> Thanks.
>
> Eric Evans
> Digital Data Services LLC.
> 304.660.9080
>
>
> -Original Message-
> From: Robert Webb 
> Sent: Wednesday, March 25, 2020 4:26 PM
> To: eev...@digitaldatatechs.com; 'Shareef Jalloq' ;
> users@ovirt.org
> Subject: Re: [ovirt-users] Re: Windows VirtIO drivers
>
> It does work that way.
>
> I found that out as I was testing oVirt and had not created a separate ISO
> Domain. I believe it was Strahil who pointed me in the right direction.
>
> So if one does not have an ISO Domain, it is no longer required. Along with
> the fact that ISO Domains are or in the process of being deprecated.
>
> 
> From: eev...@digitaldatatechs.com 
> Sent: Wednesday, March 25, 2020 3:13 PM
> To: Robert Webb; 'Shareef Jalloq'; users@ovirt.org
> Subject: RE: [ovirt-users] Re: Windows VirtIO drivers
>
> That may be true, but in the ISO domain, when you open virt viewer you can
> change the cd very easily...maybe it works that way as well..
>
> Eric Evans
> Digital Data Services LLC.
> 304.660.9080
>
>
> -Original Message-
> From: Robert Webb 
> Sent: Wednesday, March 25, 2020 2:35 PM
> To: eev...@digitaldatatechs.com; 'Shareef Jalloq' ;
> users@ovirt.org
> Subject: [ovirt-users] Re: Windows VirtIO drivers
>
> Don't think you have to use the ISO Domain any longer.
>
> You can upload to a Data Domain and when you highlight the VM in the
> management GUI, select the three dots in the top left for extra options and
> there is a change cd option. That option will allow for attaching an ISO
> from a Data Domain.
>
> That is what I recall when I was using oVirt a month or so ago.
>
> 
> From: eev...@digitaldatatechs.com 
> Sent: Wednesday, March 25, 2020 2:28 PM
> To: 'Shareef Jalloq'; users@ovirt.org
> Subject: [ovirt-users] Re: Windows VirtIO drivers
>
> You have to copy the iso and vfd files to the ISO domain to make them
> available to the vm's that need drivers.
>
> engine-iso-uploader options list
> # engine-iso-uploader options upload file file file Documentation is found
> here: https://www.ovirt.org/documentation/admin-guide/chap-Utilities.html
>
> Eric Evans
> Digital Data Services LLC.
> 304.660.9080
> [cid:image001.jpg@01D602B1.9FEA2EC0]
>
> From: Shareef Jalloq 
> Sent: Wednesday, March 25, 2020 1:51 PM
> To: users@ovirt.org
> Subject: [ovirt-users] Windows VirtIO drivers
>
> Hi,
>
> it seems the online documentation regarding the windows installation steps
> is well out of date.  Where is there any current documentation on where to
> get the VirtIO drivers for a Windows installation?
>
> From a bit of Googling, it seems that I need to 'yum install virtio-win' on
> the engine VM and then copy the relevant .iso/.vfd to the ISO domain.  Is
> that correct?
>
> Where is the documentation maintained and how do I open a bug on it?
>
> Thanks, Shareef.
>
>
>
>
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/RKZXX32D3FPJJJZFCPNZPODOK7P2NCVE/

[ovirt-users] Re: NFS permissions error on ISODomain file with correct permissions

[Shareef Jalloq]

OK, think this is solved and it was a permissions issue.  I eventually
logged into the NAS to see if I could see anything different in the exports
and the ISO Domain didn't have any group ownership rights.

This is strange because when you browse the directory from an oVirt node,
it shows each directory and file as having full permissions. Is this an NFS
thing?

On Thu, Apr 2, 2020 at 3:20 PM Shareef Jalloq  wrote:

> On your second point about an Export domain, how do you configure oVirt to
> look in an Export domain for the Run Once setup?
>
> On Thu, Apr 2, 2020 at 3:01 PM Shareef Jalloq 
> wrote:
>
>> This doesn't seem, to me, to be an issue with the NAS or the mounts.  In
>> my original post you can see the VFD files in the mounted directory under
>> /rhev.  Is that not what you're asking?
>>
>> I have both the ISODomain and two DataDomain's mounted.  I have a bunch
>> of VM's running off this NAS with no issues.  The permissions to the VFD
>> files are all correct and I can create and list files in the ISODomain with
>> no issue.
>>
>> On Tue, Mar 31, 2020 at 9:40 PM  wrote:
>>
>>> If you issue the mount command does the path show.
>>>
>>> mount |grep 
>>>
>>>
>>>
>>> It looks like the ISO domain is on a NAS, so I would try a mount of the
>>> actual folder on the ovirt node to make sure you are able to access it.
>>> Also, can you place it in an export domain instead and try?
>>>
>>> I think version 4.2+ it just needs to be in an export domain.
>>>
>>>
>>>
>>> Also make sure the NAS path is correct. Most NAS use a data or shares
>>> for nfs mounts. (nasname:/shares/
>>>
>>>
>>>
>>>
>>>
>>> Eric Evans
>>>
>>> Digital Data Services LLC.
>>>
>>> 304.660.9080
>>>
>>>
>>>
>>> *From:* Shareef Jalloq 
>>> *Sent:* Tuesday, March 31, 2020 4:59 AM
>>> *To:* users@ovirt.org
>>> *Subject:* [ovirt-users] NFS permissions error on ISODomain file with
>>> correct permissions
>>>
>>>
>>>
>>> Hi,
>>>
>>>
>>>
>>> I asked this question in another thread but it seems to have been lost
>>> in the noise so I'm reposting with a more descriptive subject.
>>>
>>>
>>>
>>> I'm trying to start a Windows VM and use the virtio-win VFD floppy to
>>> get the drivers but the VM startup fails due to a permissions issue
>>> detailed below.  The permissions look fine to me so why can't the VFD be
>>> read?
>>>
>>>
>>>
>>> Shareef.
>>>
>>>
>>>
>>> I found a permissions issue in the engine.log:
>>>
>>>
>>>
>>> 2020-03-25 21:28:41,662Z ERROR
>>> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
>>> (ForkJoinPool-1-worker-14) [] EVENT_ID: VM_DOWN_ERROR(119), VM win-2019 is
>>> down with error. Exit message: internal error: qemu unexpectedly closed the
>>> monitor: 2020-03-25T21:28:40.324426Z qemu-kvm: -drive
>>> file=/rhev/data-center/mnt/nas-01.phoelex.com:_volume2_isostore/41cebb4b-c164-4956-8f44-6426170cd9f5/images/----/virtio-win_servers_amd64.vfd,format=raw,if=none,id=drive-ua-0b9c28b5-f75c-4575-ad85-b5b836f67d61,readonly=on:
>>> Could not open 
>>> '/rhev/data-center/mnt/nas-01.phoelex.com:_volume2_isostore/41cebb4b-c164-4956-8f44-6426170cd9f5/images/----/virtio-win_servers_amd64.vfd':
>>> Permission denied.
>>>
>>>
>>>
>>> But when I look at that path on the node in question, every folder and
>>> the final file have the correct vdsm:kvm permissions:
>>>
>>>
>>>
>>> [root@ovirt-node-01 ~]# ll /rhev/data-center/mnt/nas-01.phoelex.com:
>>> _volume2_isostore/41cebb4b-c164-4956-8f44-6426170cd9f5/images/----/virtio-win_servers_amd64.vfd
>>> -rwxrwxrwx. 1 vdsm kvm 2949120 Mar 25 21:24
>>> /rhev/data-center/mnt/nas-01.phoelex.com:
>>> _volume2_isostore/41cebb4b-c164-4956-8f44-6426170cd9f5/images/----/virtio-win_servers_amd64.vfd
>>>
>>>
>>>
>>> The files were uploaded to the ISO domain using:
>>>
>>>
>>>
>>> engine-iso-uploader --iso-domain=iso_storage upload virtio-win.iso
>>> virtio-win_servers_amd64.vfd
>>>
>>>
>>>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/IFCKQILEFXJP7FFJIWU63YINMDLWVG4V/

[ovirt-users] Re: NFS permissions error on ISODomain file with correct permissions

[Shareef Jalloq]

On your second point about an Export domain, how do you configure oVirt to
look in an Export domain for the Run Once setup?

On Thu, Apr 2, 2020 at 3:01 PM Shareef Jalloq  wrote:

> This doesn't seem, to me, to be an issue with the NAS or the mounts.  In
> my original post you can see the VFD files in the mounted directory under
> /rhev.  Is that not what you're asking?
>
> I have both the ISODomain and two DataDomain's mounted.  I have a bunch of
> VM's running off this NAS with no issues.  The permissions to the VFD files
> are all correct and I can create and list files in the ISODomain with no
> issue.
>
> On Tue, Mar 31, 2020 at 9:40 PM  wrote:
>
>> If you issue the mount command does the path show.
>>
>> mount |grep 
>>
>>
>>
>> It looks like the ISO domain is on a NAS, so I would try a mount of the
>> actual folder on the ovirt node to make sure you are able to access it.
>> Also, can you place it in an export domain instead and try?
>>
>> I think version 4.2+ it just needs to be in an export domain.
>>
>>
>>
>> Also make sure the NAS path is correct. Most NAS use a data or shares for
>> nfs mounts. (nasname:/shares/
>>
>>
>>
>>
>>
>> Eric Evans
>>
>> Digital Data Services LLC.
>>
>> 304.660.9080
>>
>>
>>
>> *From:* Shareef Jalloq 
>> *Sent:* Tuesday, March 31, 2020 4:59 AM
>> *To:* users@ovirt.org
>> *Subject:* [ovirt-users] NFS permissions error on ISODomain file with
>> correct permissions
>>
>>
>>
>> Hi,
>>
>>
>>
>> I asked this question in another thread but it seems to have been lost in
>> the noise so I'm reposting with a more descriptive subject.
>>
>>
>>
>> I'm trying to start a Windows VM and use the virtio-win VFD floppy to get
>> the drivers but the VM startup fails due to a permissions issue detailed
>> below.  The permissions look fine to me so why can't the VFD be read?
>>
>>
>>
>> Shareef.
>>
>>
>>
>> I found a permissions issue in the engine.log:
>>
>>
>>
>> 2020-03-25 21:28:41,662Z ERROR
>> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
>> (ForkJoinPool-1-worker-14) [] EVENT_ID: VM_DOWN_ERROR(119), VM win-2019 is
>> down with error. Exit message: internal error: qemu unexpectedly closed the
>> monitor: 2020-03-25T21:28:40.324426Z qemu-kvm: -drive
>> file=/rhev/data-center/mnt/nas-01.phoelex.com:_volume2_isostore/41cebb4b-c164-4956-8f44-6426170cd9f5/images/----/virtio-win_servers_amd64.vfd,format=raw,if=none,id=drive-ua-0b9c28b5-f75c-4575-ad85-b5b836f67d61,readonly=on:
>> Could not open 
>> '/rhev/data-center/mnt/nas-01.phoelex.com:_volume2_isostore/41cebb4b-c164-4956-8f44-6426170cd9f5/images/----/virtio-win_servers_amd64.vfd':
>> Permission denied.
>>
>>
>>
>> But when I look at that path on the node in question, every folder and
>> the final file have the correct vdsm:kvm permissions:
>>
>>
>>
>> [root@ovirt-node-01 ~]# ll /rhev/data-center/mnt/nas-01.phoelex.com:
>> _volume2_isostore/41cebb4b-c164-4956-8f44-6426170cd9f5/images/----/virtio-win_servers_amd64.vfd
>> -rwxrwxrwx. 1 vdsm kvm 2949120 Mar 25 21:24
>> /rhev/data-center/mnt/nas-01.phoelex.com:
>> _volume2_isostore/41cebb4b-c164-4956-8f44-6426170cd9f5/images/----/virtio-win_servers_amd64.vfd
>>
>>
>>
>> The files were uploaded to the ISO domain using:
>>
>>
>>
>> engine-iso-uploader --iso-domain=iso_storage upload virtio-win.iso
>> virtio-win_servers_amd64.vfd
>>
>>
>>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/UMXVXZB6PZMMAGW7TSIXBVQW3LHPDTO6/

[ovirt-users] Re: NFS permissions error on ISODomain file with correct permissions

[Shareef Jalloq]

This doesn't seem, to me, to be an issue with the NAS or the mounts.  In my
original post you can see the VFD files in the mounted directory under
/rhev.  Is that not what you're asking?

I have both the ISODomain and two DataDomain's mounted.  I have a bunch of
VM's running off this NAS with no issues.  The permissions to the VFD files
are all correct and I can create and list files in the ISODomain with no
issue.

On Tue, Mar 31, 2020 at 9:40 PM  wrote:

> If you issue the mount command does the path show.
>
> mount |grep 
>
>
>
> It looks like the ISO domain is on a NAS, so I would try a mount of the
> actual folder on the ovirt node to make sure you are able to access it.
> Also, can you place it in an export domain instead and try?
>
> I think version 4.2+ it just needs to be in an export domain.
>
>
>
> Also make sure the NAS path is correct. Most NAS use a data or shares for
> nfs mounts. (nasname:/shares/
>
>
>
>
>
> Eric Evans
>
> Digital Data Services LLC.
>
> 304.660.9080
>
>
>
> *From:* Shareef Jalloq 
> *Sent:* Tuesday, March 31, 2020 4:59 AM
> *To:* users@ovirt.org
> *Subject:* [ovirt-users] NFS permissions error on ISODomain file with
> correct permissions
>
>
>
> Hi,
>
>
>
> I asked this question in another thread but it seems to have been lost in
> the noise so I'm reposting with a more descriptive subject.
>
>
>
> I'm trying to start a Windows VM and use the virtio-win VFD floppy to get
> the drivers but the VM startup fails due to a permissions issue detailed
> below.  The permissions look fine to me so why can't the VFD be read?
>
>
>
> Shareef.
>
>
>
> I found a permissions issue in the engine.log:
>
>
>
> 2020-03-25 21:28:41,662Z ERROR
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (ForkJoinPool-1-worker-14) [] EVENT_ID: VM_DOWN_ERROR(119), VM win-2019 is
> down with error. Exit message: internal error: qemu unexpectedly closed the
> monitor: 2020-03-25T21:28:40.324426Z qemu-kvm: -drive
> file=/rhev/data-center/mnt/nas-01.phoelex.com:_volume2_isostore/41cebb4b-c164-4956-8f44-6426170cd9f5/images/----/virtio-win_servers_amd64.vfd,format=raw,if=none,id=drive-ua-0b9c28b5-f75c-4575-ad85-b5b836f67d61,readonly=on:
> Could not open 
> '/rhev/data-center/mnt/nas-01.phoelex.com:_volume2_isostore/41cebb4b-c164-4956-8f44-6426170cd9f5/images/----/virtio-win_servers_amd64.vfd':
> Permission denied.
>
>
>
> But when I look at that path on the node in question, every folder and the
> final file have the correct vdsm:kvm permissions:
>
>
>
> [root@ovirt-node-01 ~]# ll /rhev/data-center/mnt/nas-01.phoelex.com:
> _volume2_isostore/41cebb4b-c164-4956-8f44-6426170cd9f5/images/----/virtio-win_servers_amd64.vfd
> -rwxrwxrwx. 1 vdsm kvm 2949120 Mar 25 21:24
> /rhev/data-center/mnt/nas-01.phoelex.com:
> _volume2_isostore/41cebb4b-c164-4956-8f44-6426170cd9f5/images/----/virtio-win_servers_amd64.vfd
>
>
>
> The files were uploaded to the ISO domain using:
>
>
>
> engine-iso-uploader --iso-domain=iso_storage upload virtio-win.iso
> virtio-win_servers_amd64.vfd
>
>
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/FRBYZV3D26EUZR563YRRZY4VI4VZLWZ2/

[ovirt-users] Re: New Issue - Ovirt Status shows '?' or Down for all elements

[Mark Steele]

As a followup - is it possible to move the hosted-engine to another HV
manually? Meaning we shutdown the hosted-engine VM, and copy it's XML to
another HV and fire it up over there where libvirt IS running?

If that is possible, where do we find the live / running XML files on a
host?

Mark

***
*Mark Steele*
CIO / VP Technical Operations | TelVue Corporation
TelVue - We Share Your Vision
16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
800.885.8886 | mste...@telvue.com | http://www.telvue.com
twitter: http://twitter.com/telvue | facebook:
https://www.facebook.com/telvue


On Thu, Apr 2, 2020 at 7:35 AM Mark Steele  wrote:

> All,
>
> We've read some things stating to try running the engine-setup again to
> get the certs inline. That is failing due to missing repo's - does anyone
> know of alternative or archived repo's we could point at to get past that
> part?
>
> [root@ovirt-01 ~]# engine-setup
> [ INFO  ] Stage: Initializing
> [ INFO  ] Stage: Environment setup
>   Configuration files: 
> ['/etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf', 
> '/etc/ovirt-engine-setup.conf.d/10-packaging.conf', 
> '/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf']
>   Log file: 
> /var/log/ovirt-engine/setup/ovirt-engine-setup-20200402072811-h72nc0.log
>   Version: otopi-1.3.0 (otopi-1.3.0-1.el6)
> [ INFO  ] Stage: Environment packages setup
> [ ERROR ] Yum Cannot queue package iproute: Cannot find a valid baseurl for 
> repo: ovirt-3.5-jpackage-6.0-generic
> [ ERROR ] Failed to execute stage 'Environment packages setup': Cannot find a 
> valid baseurl for repo: ovirt-3.5-jpackage-6.0-generic
> [ INFO  ] Yum Performing yum transaction rollback
> [ INFO  ] Stage: Clean up
>   Log file is located at 
> /var/log/ovirt-engine/setup/ovirt-engine-setup-20200402072811-h72nc0.log
> [ INFO  ] Generating answer file 
> '/var/lib/ovirt-engine/setup/answers/20200402072821-setup.conf'
> [ INFO  ] Stage: Pre-termination
> [ INFO  ] Stage: Termination
> [ ERROR ] Execution of setup failed
>
>
> ***
> *Mark Steele*
> CIO / VP Technical Operations | TelVue Corporation
> TelVue - We Share Your Vision
> 16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
> 800.885.8886 | mste...@telvue.com | http://www.telvue.com
> twitter: http://twitter.com/telvue | facebook:
> https://www.facebook.com/telvue
>
>
> On Thu, Apr 2, 2020 at 12:43 AM Strahil Nikolov 
> wrote:
>
>> On April 1, 2020 11:21:34 PM GMT+03:00, Mark Steele 
>> wrote:
>> >More information:
>> >
>> >- the host that ovirt hosted engine is running on is not running
>> >libvirtd.
>> >When we attempt to start it, it complains about expired certs and
>> >fails.
>> >Any ideas on this new development?
>> >
>> >***
>> >*Mark Steele*
>> >CIO / VP Technical Operations | TelVue Corporation
>> >TelVue - We Share Your Vision
>> >16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
>> >800.885.8886 | mste...@telvue.com | http://www.telvue.com
>> >twitter: http://twitter.com/telvue | facebook:
>> >https://www.facebook.com/telvue
>> >
>> >
>> >On Wed, Apr 1, 2020 at 1:43 PM Mark Steele  wrote:
>> >
>> >> A million years ago - we are going to be upgrading with a new cluster
>> >but
>> >> for now, we have this one.
>> >>
>> >> It's production and we cannot take it down unless absolutely
>> >necessary.
>> >>
>> >> ***
>> >> *Mark Steele*
>> >> CIO / VP Technical Operations | TelVue Corporation
>> >> TelVue - We Share Your Vision
>> >> 16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
>> >> 800.885.8886 | mste...@telvue.com | http://www.telvue.com
>> >> twitter: http://twitter.com/telvue | facebook:
>> >> https://www.facebook.com/telvue
>> >>
>> >>
>> >> On Wed, Apr 1, 2020 at 1:17 PM Strahil Nikolov
>> >
>> >> wrote:
>> >>
>> >>> On April 1, 2020 5:40:27 PM GMT+03:00, Mark Steele
>> >
>> >>> wrote:
>> >>> >Two other symptoms:
>> >>> >
>> >>> >- Some of the HV's respond 'Destination Host Prohibited' on ping,
>> >but
>> >>> >SSH
>> >>> >works fine
>> >>> >
>> >>> >- Seeing this in the log:
>> >>> >
>> >>> >2020-04-01 10:34:31,839 ERROR
>> >>> >[org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp
>> >Reactor)
>> >>> >Unable to process messages: javax.net.ssl.SSLException: Received
>> >fatal
>> >>> >alert: certificate_expired
>> >>> >
>> >>> >
>> >>> >***
>> >>> >*Mark Steele*
>> >>> >CIO / VP Technical Operations | TelVue Corporation
>> >>> >TelVue - We Share Your Vision
>> >>> >16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
>> >>> >800.885.8886 | mste...@telvue.com | http://www.telvue.com
>> >>> >twitter: http://twitter.com/telvue | facebook:
>> >>> >https://www.facebook.com/telvue
>> >>> >
>> >>> >
>> >>> >On Wed, Apr 1, 2020 at 10:25 AM Mark Steele 
>> >wrote:
>> >>> >
>> >>> >> Yesterday we had a storage crash that caused our hosted engine to
>> >>> >stop and
>> >>> >> not auto-restart. We manually restarted it and this morning, all
>> >>> >elements
>> >>> >> are showing a status of either question mark '?' or a red down
>> >>> >chevron.

[ovirt-users] Re: Artwork: 4.4 GA banners

[Laura Wright]

Great! I'll make some other banners with the other dimensions based off of
this layout.

On Thu, Apr 2, 2020 at 5:37 AM Sandro Bonazzola  wrote:

>
>
> Il giorno mer 1 apr 2020 alle ore 21:38 Laura Wright 
> ha scritto:
>
>> Would something like this work?
>>
>
> Nice!
>
>
>>
>> On Thu, Mar 26, 2020 at 4:04 AM Sandro Bonazzola 
>> wrote:
>>
>>>
>>>
>>> Il giorno mar 24 mar 2020 alle ore 18:56 Laura Wright <
>>> lwri...@redhat.com> ha scritto:
>>>
 Hi Sandro,

 For the content we want to feature in the banners, besides the version
 number, is there any other specific information we would want to include
 like the release date?

>>>
>>> I would exclude release date from the banner
>>>
>>>

 Best,
 Laura

 On Tue, Mar 24, 2020 at 1:35 PM Sandro Bonazzola 
 wrote:

>
>
> Il giorno mar 24 mar 2020 alle ore 18:20 Jayme  ha
> scritto:
>
>> Hey Sandro,
>>
>> Do you have more specific details or guidelines in regards to the
>> graphics you are looking for?
>>
>
> Artwork should be shared under a license oVirt project can use, I
> would recommend CC-BY-SA.
> The oVirt brand is now blue/white, like
> https://media-exp1.licdn.com/dms/image/C4D1BAQG5ElRFcXlsAQ/company-background_1/0?e=1585159200=beta=z90HpSiz36UFDRg7nrwv1FN343liI_byj_1kP-1Rtxw
> Maybe Laura can give more guidelines for the graphics.
>
>
>
>>
>> Thanks!
>>
>> On Tue, Mar 24, 2020 at 1:27 PM Sandro Bonazzola 
>> wrote:
>>
>>> Hi,
>>> in preparation of oVirt 4.4 GA it would be nice to have some
>>> graphics we can use for launching oVirt 4.4 GA on social media and oVirt
>>> website.
>>> If you don't have coding skills but you have marketing or design
>>> skills this is a good opportunity to contribute back to the project.
>>> Looking forward to your designs!
>>>
>>> --
>>>
>>> Sandro Bonazzola
>>>
>>> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
>>>
>>> Red Hat EMEA 
>>>
>>> sbona...@redhat.com
>>> *
>>> *
>>> *Red Hat respects your work life balance. Therefore there is no need
>>> to answer this email out of your office hours.*
>>> ___
>>> Users mailing list -- users@ovirt.org
>>> To unsubscribe send an email to users-le...@ovirt.org
>>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
>>> oVirt Code of Conduct:
>>> https://www.ovirt.org/community/about/community-guidelines/
>>> List Archives:
>>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/WQWKXCPQVII5SZX2AX2SGUYORDVG5KS6/
>>>
>>
>
> --
>
> Sandro Bonazzola
>
> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
>
> Red Hat EMEA 
>
> sbona...@redhat.com
> *
> *
> *Red Hat respects your work life balance. Therefore there is no need
> to answer this email out of your office hours.
> *
>


 --

 Laura Wright

 She/Her/Hers

 UXD Team

 Red Hat Massachusetts 

 314 Littleton Rd

 lwri...@redhat.com
 

>>>
>>>
>>> --
>>>
>>> Sandro Bonazzola
>>>
>>> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
>>>
>>> Red Hat EMEA 
>>>
>>> sbona...@redhat.com
>>> *
>>> *
>>> *Red Hat respects your work life balance. Therefore there is no need to
>>> answer this email out of your office hours.
>>> *
>>>
>>
>>
>> --
>>
>> Laura Wright
>>
>> She/Her/Hers
>>
>> UXD Team
>>
>> Red Hat Massachusetts 
>>
>> 314 Littleton Rd
>>
>> lwri...@redhat.com
>> 
>>
>
>
> --
>
> Sandro Bonazzola
>
> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
>
> Red Hat EMEA 
>
> sbona...@redhat.com
> *
> *
> *Red Hat respects your work life balance. Therefore there is no need to
> answer this email out of your office hours.
> *
>


-- 

Laura Wright

She/Her/Hers

UXD Team

Red Hat Massachusetts 

314 Littleton Rd

lwri...@redhat.com

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 

[ovirt-users] Re: vm console problem

[Milan Zamazal]

David David  writes:

> can connect to a vm which has spice console protocol by remote-viewer but
> that not working with vnc protocol
> the remote-viewer can't validate the server certs, is this a bug on the
> remote-viewerside or in the hypervisor?
> this problem is generally known? will it be fixed?

It works for me, so it's either a problem with your remote-viewer or an
unknown problem on the oVirt side.  I'd suggest paying attention to the
authentication method negotiation as pointed out earlier.  I'm not
expert in that area, so I can't help you with that but maybe someone
else can.

Regards,
Milan

> вс, 29 мар. 2020 г. в 12:52, David David :
>
>> there is no such problem with the ovirt-engine 4.2.5.2-1.el7
>> it appeared when upgrading to 4.3.*
>>
>> вс, 29 мар. 2020 г. в 12:46, David David :
>>
>>> tested on four different workstations with: fedora20, fedora31 and
>>> windows10(remote-manager last vers)
>>>
>>> вс, 29 мар. 2020 г. в 12:39, Strahil Nikolov :
>>>
 On March 29, 2020 9:47:02 AM GMT+03:00, David David 
 wrote:
 >I did as you said:
 >copied from engine /etc/ovirt-engine/ca.pem onto my desktop into
 >/etc/pki/ca-trust/source/anchors and then run update-ca-trust
 >it didn’t help, still the same errors
 >
 >
 >пт, 27 мар. 2020 г. в 21:56, Strahil Nikolov :
 >
 >> On March 27, 2020 12:23:10 PM GMT+02:00, David David
 >
 >> wrote:
 >> >here is debug from opening console.vv by remote-viewer
 >> >
 >> >2020-03-27 14:09 GMT+04:00, Milan Zamazal :
 >> >> David David  writes:
 >> >>
 >> >>> yes i have
 >> >>> console.vv attached
 >> >>
 >> >> It looks the same as mine.
 >> >>
 >> >> There is a difference in our logs, you have
 >> >>
 >> >>   Possible auth 19
 >> >>
 >> >> while I have
 >> >>
 >> >>   Possible auth 2
 >> >>
 >> >> So I still suspect a wrong authentication method is used, but I
 >don't
 >> >> have any idea why.
 >> >>
 >> >> Regards,
 >> >> Milan
 >> >>
 >> >>> 2020-03-26 21:38 GMT+04:00, Milan Zamazal :
 >>  David David  writes:
 >> 
 >> > copied from qemu server all certs except "cacrl" to my
 >> >desktop-station
 >> > into /etc/pki/
 >> 
 >>  This is not needed, the CA certificate is included in console.vv
 >> >and no
 >>  other certificate should be needed.
 >> 
 >> > but remote-viewer is still didn't work
 >> 
 >>  The log looks like remote-viewer is attempting certificate
 >>  authentication rather than password authentication.  Do you have
 >>  password in console.vv?  It should look like:
 >> 
 >>    [virt-viewer]
 >>    type=vnc
 >>    host=192.168.122.2
 >>    port=5900
 >>    password=fxLazJu6BUmL
 >>    # Password is valid for 120 seconds.
 >>    ...
 >> 
 >>  Regards,
 >>  Milan
 >> 
 >> > 2020-03-26 2:22 GMT+04:00, Nir Soffer :
 >> >> On Wed, Mar 25, 2020 at 12:45 PM David David
 >
 >> >> wrote:
 >> >>>
 >> >>> ovirt 4.3.8.2-1.el7
 >> >>> gtk-vnc2-1.0.0-1.fc31.x86_64
 >> >>> remote-viewer version 8.0-3.fc31
 >> >>>
 >> >>> can't open vm console by remote-viewer
 >> >>> vm has vnc console protocol
 >> >>> when click on console button to connect to a vm, the
 >> >remote-viewer
 >> >>> console disappear immediately
 >> >>>
 >> >>> remote-viewer debug in attachment
 >> >>
 >> >> You an issue with the certificates:
 >> >>
 >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.238:
 >> >> ../src/vncconnection.c Set credential 2 libvirt
 >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239:
 >> >> ../src/vncconnection.c Searching for certs in /etc/pki
 >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239:
 >> >> ../src/vncconnection.c Searching for certs in /root/.pki
 >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239:
 >> >> ../src/vncconnection.c Failed to find certificate
 >CA/cacert.pem
 >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239:
 >> >> ../src/vncconnection.c No CA certificate provided, using
 >GNUTLS
 >> >global
 >> >> trust
 >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239:
 >> >> ../src/vncconnection.c Failed to find certificate CA/cacrl.pem
 >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239:
 >> >> ../src/vncconnection.c Failed to find certificate
 >> >> libvirt/private/clientkey.pem
 >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239:
 >> >> ../src/vncconnection.c Failed to find certificate
 >> >> libvirt/clientcert.pem
 >> >> (remote-viewer:2721): 

[ovirt-users] Re: New Issue - Ovirt Status shows '?' or Down for all elements

[Mark Steele]

All,

We've read some things stating to try running the engine-setup again to get
the certs inline. That is failing due to missing repo's - does anyone know
of alternative or archived repo's we could point at to get past that part?

[root@ovirt-01 ~]# engine-setup
[ INFO  ] Stage: Initializing
[ INFO  ] Stage: Environment setup
  Configuration files:
['/etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf',
'/etc/ovirt-engine-setup.conf.d/10-packaging.conf',
'/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf']
  Log file:
/var/log/ovirt-engine/setup/ovirt-engine-setup-20200402072811-h72nc0.log
  Version: otopi-1.3.0 (otopi-1.3.0-1.el6)
[ INFO  ] Stage: Environment packages setup
[ ERROR ] Yum Cannot queue package iproute: Cannot find a valid
baseurl for repo: ovirt-3.5-jpackage-6.0-generic
[ ERROR ] Failed to execute stage 'Environment packages setup': Cannot
find a valid baseurl for repo: ovirt-3.5-jpackage-6.0-generic
[ INFO  ] Yum Performing yum transaction rollback
[ INFO  ] Stage: Clean up
  Log file is located at
/var/log/ovirt-engine/setup/ovirt-engine-setup-20200402072811-h72nc0.log
[ INFO  ] Generating answer file
'/var/lib/ovirt-engine/setup/answers/20200402072821-setup.conf'
[ INFO  ] Stage: Pre-termination
[ INFO  ] Stage: Termination
[ ERROR ] Execution of setup failed


***
*Mark Steele*
CIO / VP Technical Operations | TelVue Corporation
TelVue - We Share Your Vision
16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
800.885.8886 | mste...@telvue.com | http://www.telvue.com
twitter: http://twitter.com/telvue | facebook:
https://www.facebook.com/telvue


On Thu, Apr 2, 2020 at 12:43 AM Strahil Nikolov 
wrote:

> On April 1, 2020 11:21:34 PM GMT+03:00, Mark Steele 
> wrote:
> >More information:
> >
> >- the host that ovirt hosted engine is running on is not running
> >libvirtd.
> >When we attempt to start it, it complains about expired certs and
> >fails.
> >Any ideas on this new development?
> >
> >***
> >*Mark Steele*
> >CIO / VP Technical Operations | TelVue Corporation
> >TelVue - We Share Your Vision
> >16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
> >800.885.8886 | mste...@telvue.com | http://www.telvue.com
> >twitter: http://twitter.com/telvue | facebook:
> >https://www.facebook.com/telvue
> >
> >
> >On Wed, Apr 1, 2020 at 1:43 PM Mark Steele  wrote:
> >
> >> A million years ago - we are going to be upgrading with a new cluster
> >but
> >> for now, we have this one.
> >>
> >> It's production and we cannot take it down unless absolutely
> >necessary.
> >>
> >> ***
> >> *Mark Steele*
> >> CIO / VP Technical Operations | TelVue Corporation
> >> TelVue - We Share Your Vision
> >> 16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
> >> 800.885.8886 | mste...@telvue.com | http://www.telvue.com
> >> twitter: http://twitter.com/telvue | facebook:
> >> https://www.facebook.com/telvue
> >>
> >>
> >> On Wed, Apr 1, 2020 at 1:17 PM Strahil Nikolov
> >
> >> wrote:
> >>
> >>> On April 1, 2020 5:40:27 PM GMT+03:00, Mark Steele
> >
> >>> wrote:
> >>> >Two other symptoms:
> >>> >
> >>> >- Some of the HV's respond 'Destination Host Prohibited' on ping,
> >but
> >>> >SSH
> >>> >works fine
> >>> >
> >>> >- Seeing this in the log:
> >>> >
> >>> >2020-04-01 10:34:31,839 ERROR
> >>> >[org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp
> >Reactor)
> >>> >Unable to process messages: javax.net.ssl.SSLException: Received
> >fatal
> >>> >alert: certificate_expired
> >>> >
> >>> >
> >>> >***
> >>> >*Mark Steele*
> >>> >CIO / VP Technical Operations | TelVue Corporation
> >>> >TelVue - We Share Your Vision
> >>> >16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
> >>> >800.885.8886 | mste...@telvue.com | http://www.telvue.com
> >>> >twitter: http://twitter.com/telvue | facebook:
> >>> >https://www.facebook.com/telvue
> >>> >
> >>> >
> >>> >On Wed, Apr 1, 2020 at 10:25 AM Mark Steele 
> >wrote:
> >>> >
> >>> >> Yesterday we had a storage crash that caused our hosted engine to
> >>> >stop and
> >>> >> not auto-restart. We manually restarted it and this morning, all
> >>> >elements
> >>> >> are showing a status of either question mark '?' or a red down
> >>> >chevron.
> >>> >>
> >>> >> We are running version oVirt Engine Version: 3.5.0.1-1.el6.
> >>> >>
> >>> >> We are chasing it down and see this in the log:
> >>> >>
> >>> >> 2020-04-01 10:15:53,060 WARN
> >>> >[org.ovirt.engine.core.vdsbroker.VdsManager]
> >>> >(DefaultQuartzScheduler_Worker-23) Failed to refresh VDS , vds =
> >>> >e98f8f1d-dd1d-47c4-b039-d6eaaf578317 : hv-06, VDS Network Error,
> >>> >continuing
> >>> >>
> >>> >>
> >>> >> Any insight into what might be causing this or the fix would be
> >>> >> appreciated.
> >>> >>
> >>> >> ***
> >>> >> *Mark Steele*
> >>> >>
> >>> >>
> >>>
> >>> Hey Mark,
> >>> When was the oVirt last updated ?
> >>>
> >>> Best Regards,
> >>> Strahil Nikolov
> >>>
> >>
>
> That's why I asked  about the update.
> The update  process renews  somee certificates, and as it wasn't 

[ovirt-users] Re: Failing to redeploy self hosted engine

[Maton, Brett]

It is useful information, but it doesn't help in this case.


Every one also seems to have missed the point, this is not about recovering
a broken hosted engine.

The problem I ran into is installing a NEW self hosted engine on physical
hosts that had already been configured in the old cluster.
(because of storage and network changes, but the reason doesn't really
matter)

What happened:

Ovirt UI:
   Shutdown all VMS
   Maintenance Mode / Detach storage domains
   Remove all physical hosts from cluster except the one running HE
   Switch to HE Engine global maintenance

On last physical host:
hosted-engine --vm-poweroff

On all physical hosts:
ovirt-hosted-engine-cleanup


- Physical network changes to all hosts

Power on "host 1", (expectation deploy a new SHE on a new storage domain)

# hosted-engine --deploy
...
...
[ INFO  ] TASK [ovirt.hosted_engine_setup : Fail with error description]
[ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "The
host has been set in non_operational status, deployment errors:   code
9000: Failed to verify Power Management configuration for Host
physhost01.example.com,   fix accordingly and re-deploy."}

At this point after removing the host from the old cluster I don't/didn't
expect legacy configuration to be left lurking in places unknown.
In this case it's a power management configuration that wasn't cleaned up
that's stopping the very first SHE from being deployed.  Although I'mn sure
there is a raft of 'unclean' configuration left behind when a host is
removed from a cluster.


The only way I could get SHE to redeploy onto the same hardware was to do a
full clean OS install and basically start from scratch.

On Thu, 2 Apr 2020 at 07:27, Yedidyah Bar David  wrote:

> On Thu, Apr 2, 2020 at 7:41 AM Strahil Nikolov 
> wrote:
> >
> > On April 1, 2020 5:28:35 PM GMT+03:00, eev...@digitaldatatechs.com
> wrote:
> > >
> https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html/self-hosted_engine_guide/troubleshooting
> > >
> > >
> > >
> > >It should tell you the steps to take to troubleshoot your deployment.
> > >
> > >
> > >
> > >Eric Evans
> > >
> > >Digital Data Services LLC.
> > >
> > >304.660.9080
> > >
> > >
> > >
> > >
> > >
> > >From: Maton, Brett 
> > >Sent: Tuesday, March 31, 2020 11:52 PM
> > >To: eev...@digitaldatatechs.com
> > >Cc: Ovirt Users 
> > >Subject: [ovirt-users] Re: Failing to redeploy self hosted engine
> > >
> > >
> > >
> > >So, how would I go about disabling global maintenance when hosted
> > >engine isn't running?
> > >
> > >
> > >
> > >I tried editing /var/lib/ovirt-hosted-engine-ha/ha.conf and setting
> > >both values to False but that didn't help.
> > >
> > >
> > >
> > >local_maintenance=False
> > >local_maintenance_manual=False
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >On Tue, 31 Mar 2020 at 23:01, Maton, Brett  > > > wrote:
> > >
> > >Oooh probably...
> > >
> > >
> > >
> > >I'll give that a try in the morning, cheers for the tip!
> > >
> > >
> > >
> > >On Tue, 31 Mar 2020, 21:23 ,  > > > wrote:
> > >
> > >Did you put the ovirt host into global maintenance mode? That may be
> > >the issue.
> > >
> > >
> > >
> > >Eric Evans
> > >
> > >Digital Data Services LLC.
> > >
> > >304.660.9080
> > >
> > >
> > >
> > >
> > >
> > >From: Maton, Brett  > > >
> > >Sent: Tuesday, March 31, 2020 2:35 PM
> > >To: Ovirt Users mailto:users@ovirt.org> >
> > >Subject: [ovirt-users] Failing to redeploy self hosted engine
> > >
> > >
> > >
> > >I keep running into this error when I try to (re)deploy self-hosted
> > >engine.
> > >
> > >
> > >
> > >
> > >
> > ># ovirt-hosted-engine-cleanup
> > >
> > ># hosted-engine --deploy
> > >
> > >...
> > >
> > >...
> > >
> > >[ INFO  ] TASK [ovirt.hosted_engine_setup : Fail with error
> > >description]
> > >
> > >[ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "The
> > >host has been set in non_operational status, deployment errors:   code
> > >9000: Failed to verify Power Management configuration for Host
> > >physhost01.example.com  ,   fix
> > >accordingly and re-deploy."}
> > >
> > >
> > >
> > >I shut down all of the VM's and detached the storage before cleaning up
> > >and trying to re-deploy the hosted engine, first time I've run into
> > >this particular problem.
> > >
> > >
> > >
> > >Any help appreciated
> > >
> > >
> > >
> > >Brett
> > >
> > >
> >
> > I'm not very pleased of this article.
>
> One more place to check is:
>
> https://www.ovirt.org/images/Hosted-Engine-4.3-deep-dive.pdf
>
> I found it a few months ago, and added to the site under:
>
> https://www.ovirt.org/community/get-involved/resources/slide-decks.html
>
> But that one sadly isn't easy to find either. Google does know about
> it, but only if you know what to search for. We should probably add a
> few more internal links to make sure all content is easily 

[ovirt-users] Re: Failing to redeploy self hosted engine

[Maton, Brett]

That document really isn't that useful in general and really doesn't relate
to 'failing to deploy hosted engine'

On Wed, 1 Apr 2020 at 20:18,  wrote:

>
> https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html/self-hosted_engine_guide/troubleshooting
>
>
>
> It should tell you the steps to take to troubleshoot your deployment.
>
>
>
> Eric Evans
>
> Digital Data Services LLC.
>
> 304.660.9080
>
>
>
> *From:* Maton, Brett 
> *Sent:* Tuesday, March 31, 2020 11:52 PM
> *To:* eev...@digitaldatatechs.com
> *Cc:* Ovirt Users 
> *Subject:* [ovirt-users] Re: Failing to redeploy self hosted engine
>
>
>
> So, how would I go about disabling global maintenance when hosted engine
> isn't running?
>
>
>
> I tried editing /var/lib/ovirt-hosted-engine-ha/ha.conf and setting both
> values to False but that didn't help.
>
>
>
> local_maintenance=False
> local_maintenance_manual=False
>
>
>
>
>
>
>
> On Tue, 31 Mar 2020 at 23:01, Maton, Brett 
> wrote:
>
> Oooh probably...
>
>
>
> I'll give that a try in the morning, cheers for the tip!
>
>
>
> On Tue, 31 Mar 2020, 21:23 ,  wrote:
>
> Did you put the ovirt host into global maintenance mode? That may be the
> issue.
>
>
>
> Eric Evans
>
> Digital Data Services LLC.
>
> 304.660.9080
>
>
>
> *From:* Maton, Brett 
> *Sent:* Tuesday, March 31, 2020 2:35 PM
> *To:* Ovirt Users 
> *Subject:* [ovirt-users] Failing to redeploy self hosted engine
>
>
>
> I keep running into this error when I try to (re)deploy self-hosted engine.
>
>
>
>
>
> # ovirt-hosted-engine-cleanup
>
> # hosted-engine --deploy
>
> ...
>
> ...
>
> [ INFO  ] TASK [ovirt.hosted_engine_setup : Fail with error description]
>
> [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "The
> host has been set in non_operational status, deployment errors:   code
> 9000: Failed to verify Power Management configuration for Host
> physhost01.example.com,   fix accordingly and re-deploy."}
>
>
>
> I shut down all of the VM's and detached the storage before cleaning up
> and trying to re-deploy the hosted engine, first time I've run into this
> particular problem.
>
>
>
> Any help appreciated
>
>
>
> Brett
>
>
>
>
>
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/L7I4IFULFGPN7Q2LLGGWEW7R7JW3YK6G/

[ovirt-users] Re: Artwork: 4.4 GA banners

[Sandro Bonazzola]

Il giorno mer 1 apr 2020 alle ore 21:38 Laura Wright 
ha scritto:

> Would something like this work?
>

Nice!


>
> On Thu, Mar 26, 2020 at 4:04 AM Sandro Bonazzola 
> wrote:
>
>>
>>
>> Il giorno mar 24 mar 2020 alle ore 18:56 Laura Wright 
>> ha scritto:
>>
>>> Hi Sandro,
>>>
>>> For the content we want to feature in the banners, besides the version
>>> number, is there any other specific information we would want to include
>>> like the release date?
>>>
>>
>> I would exclude release date from the banner
>>
>>
>>>
>>> Best,
>>> Laura
>>>
>>> On Tue, Mar 24, 2020 at 1:35 PM Sandro Bonazzola 
>>> wrote:
>>>


 Il giorno mar 24 mar 2020 alle ore 18:20 Jayme  ha
 scritto:

> Hey Sandro,
>
> Do you have more specific details or guidelines in regards to the
> graphics you are looking for?
>

 Artwork should be shared under a license oVirt project can use, I would
 recommend CC-BY-SA.
 The oVirt brand is now blue/white, like
 https://media-exp1.licdn.com/dms/image/C4D1BAQG5ElRFcXlsAQ/company-background_1/0?e=1585159200=beta=z90HpSiz36UFDRg7nrwv1FN343liI_byj_1kP-1Rtxw
 Maybe Laura can give more guidelines for the graphics.



>
> Thanks!
>
> On Tue, Mar 24, 2020 at 1:27 PM Sandro Bonazzola 
> wrote:
>
>> Hi,
>> in preparation of oVirt 4.4 GA it would be nice to have some graphics
>> we can use for launching oVirt 4.4 GA on social media and oVirt website.
>> If you don't have coding skills but you have marketing or design
>> skills this is a good opportunity to contribute back to the project.
>> Looking forward to your designs!
>>
>> --
>>
>> Sandro Bonazzola
>>
>> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
>>
>> Red Hat EMEA 
>>
>> sbona...@redhat.com
>> *
>> *
>> *Red Hat respects your work life balance. Therefore there is no need
>> to answer this email out of your office hours.*
>> ___
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@ovirt.org
>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/WQWKXCPQVII5SZX2AX2SGUYORDVG5KS6/
>>
>

 --

 Sandro Bonazzola

 MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

 Red Hat EMEA 

 sbona...@redhat.com
 *
 *
 *Red Hat respects your work life balance. Therefore there is no need to
 answer this email out of your office hours.
 *

>>>
>>>
>>> --
>>>
>>> Laura Wright
>>>
>>> She/Her/Hers
>>>
>>> UXD Team
>>>
>>> Red Hat Massachusetts 
>>>
>>> 314 Littleton Rd
>>>
>>> lwri...@redhat.com
>>> 
>>>
>>
>>
>> --
>>
>> Sandro Bonazzola
>>
>> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
>>
>> Red Hat EMEA 
>>
>> sbona...@redhat.com
>> *
>> *
>> *Red Hat respects your work life balance. Therefore there is no need to
>> answer this email out of your office hours.
>> *
>>
>
>
> --
>
> Laura Wright
>
> She/Her/Hers
>
> UXD Team
>
> Red Hat Massachusetts 
>
> 314 Littleton Rd
>
> lwri...@redhat.com
> 
>


-- 

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

Red Hat EMEA 

sbona...@redhat.com
*
*
*Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.
*
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/6FWN7BOPMVXP4YKPGDSSH2XEY3EBKKBE/

[ovirt-users] Re: DR on hyperconverged deployment

[Eyal Shenitzky]

If you intention is to use active-passive disaster recovery solution, you
can have a look at the following guild:
https://ovirt.org/documentation/disaster-recovery-guide/active_passive_overview.html

On Wed, 1 Apr 2020 at 16:42, wodel youchi  wrote:

> Hi,
>
> I am trying to configure and test disaster recovery on ovirt HCI
>
> And to understand how it works
> What is the minimum RPO and its relationship with checkpoint
> And what are the steps to fail back
>
> Regards
>
> Le mer. 1 avr. 2020 14:16, Eyal Shenitzky  a écrit :
>
>> Hi Wodel,
>>
>> Can you please explain what you are trying to do?
>> I am not sure I understand it from your question.
>>
>> On Wed, 1 Apr 2020 at 12:55, wodel youchi  wrote:
>>
>>> Hi,
>>>
>>> I re-did the test and it seems that the minimum RPO is one day and if
>>> someone could confirm that would be great
>>>
>>> As for the snapshot this time it was synced
>>>
>>> Then I tried to test the fail back and I found that the documentation is
>>> not clear :
>>> - it is not clear what is the purpose of the dr-clear playbook
>>> - it is not clear what does mean : put the target volume in read write
>>> mode and source volume in read-only mode
>>> - Do we have to sync back using a new georeplication link from the dr
>>> volume to source volume?
>>> I tried to so, in my first trial I forced the creation of the back
>>> georeplication without deleting the content of the source volume then I
>>> started the replication manually  (I didn't use the checkpoint) and I
>>> stopped the replication once it reached the changelog state, but I couldn't
>>> import the source volume I got the error : volume is not empty
>>>
>>> In my second trial I deleted and recreated the source volume from
>>> scratch and the i started the replication back manually at the end I got
>>> the error
>>>
>>> In my third trial I deleted the source volume and recreated it from
>>> scratch but I replicated back using the check point method and this time
>>> the fail back worked.
>>>
>>>  Could someone sheds some light on this?
>>>
>>> Thank you
>>> Regards.
>>>
>>> Le dim. 29 mars 2020 19:19, wodel youchi  a
>>> écrit :
>>>
 Hi,

 Need to understand somethings about DR on oVirt-HI


- What does mean : Scheduling regular backups using geo-replication
(point 3.3.4 RHHI 1.7 Doc Maintaining RHHI) :
   - Does this mean creating a check-point?
   - If yes, does this mean that the geo-replication process will
   sync data up to that check-point and then stops the synchronization, 
 then
   repeat the same cycle the day after? does this mean that the minimum 
 RPO is
   one day?
- I created a snapshot of a VM on the source Manager, I synced the
volume then I executed a DR, The VM was started on the Target Manager 
 but
the VM didn't have its snapshot, any idea???


 Regards, be safe.

>>> ___
>>> Users mailing list -- users@ovirt.org
>>> To unsubscribe send an email to users-le...@ovirt.org
>>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
>>> oVirt Code of Conduct:
>>> https://www.ovirt.org/community/about/community-guidelines/
>>> List Archives:
>>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/N2MSZUYT2GE33IVUKGVYHLAO33ZFMJ7N/
>>>
>>
>>
>> --
>> Regards,
>> Eyal Shenitzky
>>
>

-- 
Regards,
Eyal Shenitzky
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/LSPFJDYXF4A3LL275EQ6WFT7UZDNUPTR/

[ovirt-users] Re: oVirt 4.4.0 Beta release is now available for testing

[Gobinda Das]

On Mon, Mar 30, 2020 at 8:45 PM Sandro Bonazzola 
wrote:

>
>
> Il giorno lun 30 mar 2020 alle ore 16:56 Joop  ha
> scritto:
>
>> On 27-3-2020 15:48, Sandro Bonazzola wrote:
>>
>> oVirt 4.4.0 Beta release is now available for testing
>>
>> The oVirt Project is excited to announce the availability of the beta
>> release of oVirt 4.4.0 for testing, as of March 27th, 2020
>>
>> This release unleashes an altogether more powerful and flexible open
>> source virtualization solution that encompasses hundreds of individual
>> changes and a wide range of enhancements across the engine, storage,
>> network, user interface, and analytics on top of oVirt 4.3.
>>
>> Important notes before you try it
>>
>> Please note this is a Beta release.
>>
>> The oVirt Project makes no guarantees as to its suitability or usefulness.
>>
>> This pre-release must not to be used in production.
>>
>> In particular, please note that upgrades from 4.3 and future upgrades
>> from this beta to the final 4.4 release from this version are not supported.
>>
>> Some of the features included in oVirt 4.4.0 Beta require content that
>> will be available in CentOS Linux 8.2 which are currently included in Red
>> Hat Enterprise Linux 8.2 beta. If you want to have a better experience you
>> can test oVirt 4.4.0 Beta on Red Hat Enterprise Linux 8.2 beta.
>>
>> Known Issues
>>
>>-
>>
>>ovirt-imageio development is still in progress. In this beta you
>>can’t upload images to data domains. You can still copy iso images into 
>> the
>>deprecated ISO domain for installing VMs.
>>
>> Installation instructions
>>
>> For the engine: either use appliance or:
>>
>> - Install CentOS Linux 8 minimal from
>> 
>> http://centos.mirror.garr.it/centos/8.1.1911/isos/x86_64/CentOS-8.1.1911-x86_64-dvd1.iso
>>
>> - dnf install
>> 
>> https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm
>>
>> - dnf update (reboot if needed)
>>
>> - dnf module enable -y javapackages-tools pki-deps 389-ds
>>
>> - dnf install ovirt-engine
>>
>> - engine-setup
>>
>> For the nodes:
>>
>> Either use oVirt Node ISO or:
>>
>> - Install CentOS Linux 8 from
>> 
>> http://centos.mirror.garr.it/centos/8.1.1911/isos/x86_64/CentOS-8.1.1911-x86_64-dvd1.iso
>> ; select minimal installation
>>
>> - dnf install
>> https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm
>>
>> - dnf update (reboot if needed)
>>
>> - Attach the host to engine and let it be deployed.
>>
>> I have tested the HCI setup but ran into a problem at the the end of the
>> storage step.
>>
>
> Thanks for testing and for the feedback!
>
>
>
>> What I did is follow https://ovirt.org/download/beta.html
>> Host is Centos-8.1 from above both steps done, no problem
>> Install oVirt using the Cockpit wizard
>> 1 - not needed as its CentOS
>> 2 - 5 no problems, BUT
>> Cockpit session timeout if you're not careful, fix:
>> (add
>> [Session]
>> IdleTimeout=0
>> in /etc/cockpit/cockpit.conf
>> )
>>
>
> Yes, we found it too: https://bugzilla.redhat.com/show_bug.cgi?id=1818566
>
>
>
>> AND
>> If using step 6 and then choosing HCI setup the following is observed:
>> Deploy fails at certain steps because missing:
>> - hostname not in /etc/hosts
>> - gluster-ansible-roles not installed
>> - glusterfs-server not installed (firewall service name not available)
>> - vdsm-gluster (don't now if its needed but sounds logical)
>> - ssh-keygen
>> - ssh-copy-id `hostname -f`
>>
>> --> dnf install gluster-ansible-roles glusterfs-server vdsm-gluster -y
>>
>
> adding +Gobinda Das  here. I think that the HCI
> deployment has been developed and tested only for oVirt Node consumption,
> not really supported on plain CentOS installation.
>
Not really, It supports plain CentOS as well, Only extra effort is to
install all required pkgs.

> Maybe worth to document above steps in HCI deployment doc or make it clear
> to use oVirt Node instead.
>
>
>>
>> If the above is in place than gluster deploy will succeed and the
>> hosted-engine deploy will succeed but the storage step fails when it tries
>> to access glusterfs.
>> I can't find the reason in the logs and maybe I'm looking at the wrong
>> one.
>> The wizard doesn't copy all relevant logs when it encounters an error as
>> it did in the alpha release, atleast not at this point, never got to here
>> in the alpha.
>>
>
> Gobinda can you please have a look? +Evgeny Slutsky  can
> you have a look too?
>
Trying to deploy  ovirt 4.4.0 beta, having some issues with setup. Will
check and update.

>
>
>>
>> Following is attached:
>> From engine: /var/log/ovirt-engine
>> From host: /var/log/glusterfs and /var/log/ovirt-hosted-engine-setup
>>
>> I can provide further logs if needed.
>>
>> Thanks in advance,
>>
>> Joop
>>
>> 

[ovirt-users] Re: Failing to redeploy self hosted engine

[Yedidyah Bar David]

On Thu, Apr 2, 2020 at 7:41 AM Strahil Nikolov  wrote:
>
> On April 1, 2020 5:28:35 PM GMT+03:00, eev...@digitaldatatechs.com wrote:
> >https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html/self-hosted_engine_guide/troubleshooting
> >
> >
> >
> >It should tell you the steps to take to troubleshoot your deployment.
> >
> >
> >
> >Eric Evans
> >
> >Digital Data Services LLC.
> >
> >304.660.9080
> >
> >
> >
> >
> >
> >From: Maton, Brett 
> >Sent: Tuesday, March 31, 2020 11:52 PM
> >To: eev...@digitaldatatechs.com
> >Cc: Ovirt Users 
> >Subject: [ovirt-users] Re: Failing to redeploy self hosted engine
> >
> >
> >
> >So, how would I go about disabling global maintenance when hosted
> >engine isn't running?
> >
> >
> >
> >I tried editing /var/lib/ovirt-hosted-engine-ha/ha.conf and setting
> >both values to False but that didn't help.
> >
> >
> >
> >local_maintenance=False
> >local_maintenance_manual=False
> >
> >
> >
> >
> >
> >
> >
> >On Tue, 31 Mar 2020 at 23:01, Maton, Brett  > > wrote:
> >
> >Oooh probably...
> >
> >
> >
> >I'll give that a try in the morning, cheers for the tip!
> >
> >
> >
> >On Tue, 31 Mar 2020, 21:23 ,  > > wrote:
> >
> >Did you put the ovirt host into global maintenance mode? That may be
> >the issue.
> >
> >
> >
> >Eric Evans
> >
> >Digital Data Services LLC.
> >
> >304.660.9080
> >
> >
> >
> >
> >
> >From: Maton, Brett  > >
> >Sent: Tuesday, March 31, 2020 2:35 PM
> >To: Ovirt Users mailto:users@ovirt.org> >
> >Subject: [ovirt-users] Failing to redeploy self hosted engine
> >
> >
> >
> >I keep running into this error when I try to (re)deploy self-hosted
> >engine.
> >
> >
> >
> >
> >
> ># ovirt-hosted-engine-cleanup
> >
> ># hosted-engine --deploy
> >
> >...
> >
> >...
> >
> >[ INFO  ] TASK [ovirt.hosted_engine_setup : Fail with error
> >description]
> >
> >[ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "The
> >host has been set in non_operational status, deployment errors:   code
> >9000: Failed to verify Power Management configuration for Host
> >physhost01.example.com  ,   fix
> >accordingly and re-deploy."}
> >
> >
> >
> >I shut down all of the VM's and detached the storage before cleaning up
> >and trying to re-deploy the hosted engine, first time I've run into
> >this particular problem.
> >
> >
> >
> >Any help appreciated
> >
> >
> >
> >Brett
> >
> >
>
> I'm not very pleased of this article.

One more place to check is:

https://www.ovirt.org/images/Hosted-Engine-4.3-deep-dive.pdf

I found it a few months ago, and added to the site under:

https://www.ovirt.org/community/get-involved/resources/slide-decks.html

But that one sadly isn't easy to find either. Google does know about
it, but only if you know what to search for. We should probably add a
few more internal links to make sure all content is easily accessible.

> Last time I needed to fix my HostedEngine, I couldn't find anything useful.
> Looking into retrospection ,  If I knew  how to attach a rescue media and 
> boot from it  - it would take no more than 10 min to fix it - way faster than 
> to restore from backup.

There is an option '--vm-conf' you can use with '--vm-start', to pass
your own libvirt-style conf. There you can add a virtual CD with an
image or whatever.
See slide 58 in above presentation.

Best regards,
-- 
Didi
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/22SDBKIJAHKNKVNGYNTA2MV7W6DIY4DN/

[ovirt-users] Re: vm console problem

[David David]

can connect to a vm which has spice console protocol by remote-viewer but
that not working with vnc protocol
the remote-viewer can't validate the server certs, is this a bug on the
remote-viewerside or in the hypervisor?
this problem is generally known? will it be fixed?

вс, 29 мар. 2020 г. в 12:52, David David :

> there is no such problem with the ovirt-engine 4.2.5.2-1.el7
> it appeared when upgrading to 4.3.*
>
> вс, 29 мар. 2020 г. в 12:46, David David :
>
>> tested on four different workstations with: fedora20, fedora31 and
>> windows10(remote-manager last vers)
>>
>> вс, 29 мар. 2020 г. в 12:39, Strahil Nikolov :
>>
>>> On March 29, 2020 9:47:02 AM GMT+03:00, David David 
>>> wrote:
>>> >I did as you said:
>>> >copied from engine /etc/ovirt-engine/ca.pem onto my desktop into
>>> >/etc/pki/ca-trust/source/anchors and then run update-ca-trust
>>> >it didn’t help, still the same errors
>>> >
>>> >
>>> >пт, 27 мар. 2020 г. в 21:56, Strahil Nikolov :
>>> >
>>> >> On March 27, 2020 12:23:10 PM GMT+02:00, David David
>>> >
>>> >> wrote:
>>> >> >here is debug from opening console.vv by remote-viewer
>>> >> >
>>> >> >2020-03-27 14:09 GMT+04:00, Milan Zamazal :
>>> >> >> David David  writes:
>>> >> >>
>>> >> >>> yes i have
>>> >> >>> console.vv attached
>>> >> >>
>>> >> >> It looks the same as mine.
>>> >> >>
>>> >> >> There is a difference in our logs, you have
>>> >> >>
>>> >> >>   Possible auth 19
>>> >> >>
>>> >> >> while I have
>>> >> >>
>>> >> >>   Possible auth 2
>>> >> >>
>>> >> >> So I still suspect a wrong authentication method is used, but I
>>> >don't
>>> >> >> have any idea why.
>>> >> >>
>>> >> >> Regards,
>>> >> >> Milan
>>> >> >>
>>> >> >>> 2020-03-26 21:38 GMT+04:00, Milan Zamazal :
>>> >>  David David  writes:
>>> >> 
>>> >> > copied from qemu server all certs except "cacrl" to my
>>> >> >desktop-station
>>> >> > into /etc/pki/
>>> >> 
>>> >>  This is not needed, the CA certificate is included in console.vv
>>> >> >and no
>>> >>  other certificate should be needed.
>>> >> 
>>> >> > but remote-viewer is still didn't work
>>> >> 
>>> >>  The log looks like remote-viewer is attempting certificate
>>> >>  authentication rather than password authentication.  Do you have
>>> >>  password in console.vv?  It should look like:
>>> >> 
>>> >>    [virt-viewer]
>>> >>    type=vnc
>>> >>    host=192.168.122.2
>>> >>    port=5900
>>> >>    password=fxLazJu6BUmL
>>> >>    # Password is valid for 120 seconds.
>>> >>    ...
>>> >> 
>>> >>  Regards,
>>> >>  Milan
>>> >> 
>>> >> > 2020-03-26 2:22 GMT+04:00, Nir Soffer :
>>> >> >> On Wed, Mar 25, 2020 at 12:45 PM David David
>>> >
>>> >> >> wrote:
>>> >> >>>
>>> >> >>> ovirt 4.3.8.2-1.el7
>>> >> >>> gtk-vnc2-1.0.0-1.fc31.x86_64
>>> >> >>> remote-viewer version 8.0-3.fc31
>>> >> >>>
>>> >> >>> can't open vm console by remote-viewer
>>> >> >>> vm has vnc console protocol
>>> >> >>> when click on console button to connect to a vm, the
>>> >> >remote-viewer
>>> >> >>> console disappear immediately
>>> >> >>>
>>> >> >>> remote-viewer debug in attachment
>>> >> >>
>>> >> >> You an issue with the certificates:
>>> >> >>
>>> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.238:
>>> >> >> ../src/vncconnection.c Set credential 2 libvirt
>>> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239:
>>> >> >> ../src/vncconnection.c Searching for certs in /etc/pki
>>> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239:
>>> >> >> ../src/vncconnection.c Searching for certs in /root/.pki
>>> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239:
>>> >> >> ../src/vncconnection.c Failed to find certificate
>>> >CA/cacert.pem
>>> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239:
>>> >> >> ../src/vncconnection.c No CA certificate provided, using
>>> >GNUTLS
>>> >> >global
>>> >> >> trust
>>> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239:
>>> >> >> ../src/vncconnection.c Failed to find certificate CA/cacrl.pem
>>> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239:
>>> >> >> ../src/vncconnection.c Failed to find certificate
>>> >> >> libvirt/private/clientkey.pem
>>> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239:
>>> >> >> ../src/vncconnection.c Failed to find certificate
>>> >> >> libvirt/clientcert.pem
>>> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239:
>>> >> >> ../src/vncconnection.c Waiting for missing credentials
>>> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239:
>>> >> >> ../src/vncconnection.c Got all credentials
>>> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239:
>>> >> >> ../src/vncconnection.c No CA certificate provided; trying the
>>> >> >system
>>> >> >> trust store instead
>>> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: