Warning: out of sync hosts ovirt-node3 ?
by wangyu13476969128＠126.com
In the ovirt-engine web interface, compute-->clusters, there is a cluster with the following information:
Warning: out of sync hosts ovirt-node3 ?
What is the cause ? How can I solve this problem ?
5 years, 2 months
engine manager VM not launching
by bepassionatenow＠gmail.com
Good evening/morning,
I can't launch the Engine Manager after the initial install through Cockpit.
It initially started fine but I could never login. Cockpit showed that the
VM was not set to auto-restart. I don't see how to change that and the
button to "run" won't work. Spinning box in the top right corner is causing
issues (won't register properly). Any help would be greatly appreciated.
Thanks!
Daniel
5 years, 2 months
Windows Server 2019 crash dxgkrnl.sys
by gregor
Hello,
during the Installation of Windows Server 2019 after the first reboot
the VM crashed and inside the ntbtlog.txt I found that dxgkrnl.sys can
not be loaded.
Environment:
oVirt 4.3.6.7-1.el7
CPU: Intel-Westmere
Memory: 4096MB
Operation System VM config: Windows 2019 x64
HDD: VirtIO-SCSI
VirtIO driver: virtio-win-0.1.171_servers_amd64.vfd
Does anybody has an hint how to solve this problem and use Windows
Server 2019?
Besides: It's possible to install and use Windows Server 2019 in
VirtualBox 6.*. We have to install it in the meantime there to have a
alternative solution because it took now about two days to find a
solution. We tried different settings for VGA and drivers IDE ... and
many more.
best regards
gregor
5 years, 2 months
oVirt change IP's & add new ISO share
by Jonathan Mathews
Good Day
I have to change the IP addresses of the oVirt Engine, hosts and storage to
a new IP range. Please, can you advise the best way to do this and if there
is anything I would need to change in the database?
I have also run into an issue where someone has removed the ISO share/data
on the storage, so I am unable to remove, activate, detach or even add a
new ISO share.
Please, can you advise the best wat to resolve this?
Please see the below engine logs:
2019-10-30 11:39:13,918 ERROR
[org.ovirt.engine.core.vdsbroker.irsbroker.DetachStorageDomainVDSCommand]
(org.ovirt.thread.pool-8-thread-27) [58f6cfb8] Failed in
'DetachStorageDomainVDS' method
2019-10-30 11:39:13,942 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(org.ovirt.thread.pool-8-thread-27) [58f6cfb8] Correlation ID: null, Call
Stack: null, Custom Event ID: -1, Message: VDSM command failed: Storage
domain does not exist: (u'42b7d819-ce3a-4a18-a683-f4817c4bdb06',)
2019-10-30 11:39:13,943 ERROR
[org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand]
(org.ovirt.thread.pool-8-thread-27) [58f6cfb8]
IrsBroker::Failed::DetachStorageDomainVDS: IRSGenericException:
IRSErrorException: Failed to DetachStorageDomainVDS, error = Storage domain
does not exist: (u'42b7d819-ce3a-4a18-a683-f4817c4bdb06',), code = 358
2019-10-30 11:39:13,951 INFO
[org.ovirt.engine.core.vdsbroker.irsbroker.DetachStorageDomainVDSCommand]
(org.ovirt.thread.pool-8-thread-27) [58f6cfb8] FINISH,
DetachStorageDomainVDSCommand, log id: 5547e2df
2019-10-30 11:39:13,951 INFO
[org.ovirt.engine.core.vdsbroker.irsbroker.SPMGetAllTasksInfoVDSCommand]
(org.ovirt.thread.pool-8-thread-38) [58f6cfb8] -- executeIrsBrokerCommand:
Attempting on storage pool '5849b030-626e-47cb-ad90-3ce782d831b3'
2019-10-30 11:39:13,951 ERROR
[org.ovirt.engine.core.bll.storage.DetachStorageDomainFromPoolCommand]
(org.ovirt.thread.pool-8-thread-27) [58f6cfb8] Command
'org.ovirt.engine.core.bll.storage.DetachStorageDomainFromPoolCommand'
failed: EngineException:
org.ovirt.engine.core.vdsbroker.irsbroker.IRSErrorException:
IRSGenericException: IRSErrorException: Failed to DetachStorageDomainVDS,
error = Storage domain does not exist:
(u'42b7d819-ce3a-4a18-a683-f4817c4bdb06',), code = 358 (Failed with error
StorageDomainDoesNotExist and code 358)
2019-10-30 11:39:13,952 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.HSMGetAllTasksInfoVDSCommand]
(org.ovirt.thread.pool-8-thread-38) [58f6cfb8] START,
HSMGetAllTasksInfoVDSCommand(HostName = host01,
VdsIdVDSCommandParametersBase:{runAsync='true',
hostId='291a3a19-7467-4783-a6f7-2b2dd0de9ad3'}), log id: 6cc238fb
2019-10-30 11:39:13,952 INFO
[org.ovirt.engine.core.bll.storage.DetachStorageDomainFromPoolCommand]
(org.ovirt.thread.pool-8-thread-27) [58f6cfb8] Command
[id=cec030b7-4a62-43a2-9ae8-de56a5d71ef8]: Compensating CHANGED_STATUS_ONLY
of org.ovirt.engine.core.common.businessentities.StoragePoolIsoMap;
snapshot:
EntityStatusSnapshot:{id='StoragePoolIsoMapId:{storagePoolId='5849b030-626e-47cb-ad90-3ce782d831b3',
storageId='42b7d819-ce3a-4a18-a683-f4817c4bdb06'}', status='Inactive'}.
2019-10-30 11:39:13,975 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(org.ovirt.thread.pool-8-thread-27) [58f6cfb8] Correlation ID: 28ac658, Job
ID: b31e0f44-2d82-47bf-90d9-f69e399d994f, Call Stack: null, Custom Event
ID: -1, Message: Failed to detach Storage Domain iso to Data Center
Default. (User: admin@internal)
2019-10-30 11:42:46,711 INFO
[org.ovirt.engine.core.vdsbroker.irsbroker.SPMGetAllTasksInfoVDSCommand]
(org.ovirt.thread.pool-8-thread-25) [31e89bba] START,
SPMGetAllTasksInfoVDSCommand( IrsBaseVDSCommandParameters:{runAsync='true',
storagePoolId='5849b030-626e-47cb-ad90-3ce782d831b3',
ignoreFailoverLimit='false'}), log id: 59192768
2019-10-30 11:42:48,825 ERROR
[org.ovirt.engine.core.vdsbroker.irsbroker.ActivateStorageDomainVDSCommand]
(org.ovirt.thread.pool-8-thread-34) [31e89bba] Failed in
'ActivateStorageDomainVDS' method
2019-10-30 11:42:48,855 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(org.ovirt.thread.pool-8-thread-34) [31e89bba] Correlation ID: null, Call
Stack: null, Custom Event ID: -1, Message: VDSM command failed: Storage
domain does not exist: (u'42b7d819-ce3a-4a18-a683-f4817c4bdb06',)
2019-10-30 11:42:48,856 ERROR
[org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand]
(org.ovirt.thread.pool-8-thread-34) [31e89bba]
IrsBroker::Failed::ActivateStorageDomainVDS: IRSGenericException:
IRSErrorException: Failed to ActivateStorageDomainVDS, error = Storage
domain does not exist: (u'42b7d819-ce3a-4a18-a683-f4817c4bdb06',), code =
358
2019-10-30 11:42:48,864 INFO
[org.ovirt.engine.core.vdsbroker.irsbroker.ActivateStorageDomainVDSCommand]
(org.ovirt.thread.pool-8-thread-34) [31e89bba] FINISH,
ActivateStorageDomainVDSCommand, log id: 518fdcf
2019-10-30 11:42:48,865 ERROR
[org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand]
(org.ovirt.thread.pool-8-thread-34) [31e89bba] Command
'org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand' failed:
EngineException:
org.ovirt.engine.core.vdsbroker.irsbroker.IRSErrorException:
IRSGenericException: IRSErrorException: Failed to ActivateStorageDomainVDS,
error = Storage domain does not exist:
(u'42b7d819-ce3a-4a18-a683-f4817c4bdb06',), code = 358 (Failed with error
StorageDomainDoesNotExist and code 358)
2019-10-30 11:42:48,865 INFO
[org.ovirt.engine.core.vdsbroker.irsbroker.SPMGetAllTasksInfoVDSCommand]
(org.ovirt.thread.pool-8-thread-25) [31e89bba] -- executeIrsBrokerCommand:
Attempting on storage pool '5849b030-626e-47cb-ad90-3ce782d831b3'
2019-10-30 11:42:48,865 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.HSMGetAllTasksInfoVDSCommand]
(org.ovirt.thread.pool-8-thread-25) [31e89bba] START,
HSMGetAllTasksInfoVDSCommand(HostName = host02,
VdsIdVDSCommandParametersBase:{runAsync='true',
hostId='3673a0e1-721d-40ba-a179-b1f13a9aec43'}), log id: 47ef923b
2019-10-30 11:42:48,866 INFO
[org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand]
(org.ovirt.thread.pool-8-thread-34) [31e89bba] Command
[id=68bf0e1e-6a0b-41cb-9cad-9eb2bf87c5ee]: Compensating CHANGED_STATUS_ONLY
of org.ovirt.engine.core.common.businessentities.StoragePoolIsoMap;
snapshot:
EntityStatusSnapshot:{id='StoragePoolIsoMapId:{storagePoolId='5849b030-626e-47cb-ad90-3ce782d831b3',
storageId='42b7d819-ce3a-4a18-a683-f4817c4bdb06'}', status='Inactive'}.
2019-10-30 11:42:48,888 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(org.ovirt.thread.pool-8-thread-34) [31e89bba] Correlation ID: 5b208434,
Job ID: dff5f615-9dc4-4d79-a37e-5c6e99a2cc6b, Call Stack: null, Custom
Event ID: -1, Message: Failed to activate Storage Domain iso (Data Center
Default) by admin@internal
Thanks
Jonathan
5 years, 2 months
DHCP Client in Guest VM does not work on ovirtmgmt
by ccesario＠blueit.com.br
Hello,
Is there any special config to usage dhcp client on Guest VM using ovirtmgmt/ovirtmgmt vnic profile ?
Currently I have a VM using the ovirtmgmt/ovirtmgmt NIC profile and this interface is configured as DHCP client, and this does not work when using ovirtmgmt/ovirtmgmt as NIC profile. But if I assign manual IP address from the same range of DHCP server the comunication it works.
And If usage other NIC profile in other VLAN with other DHCP server it works.
It seems ovirtmgmt/ovirtmgmt profile filter the DHCP protocol.
Could someone has idea to allow DHCP protocol works on ovirtmgmt/ovirtmgmt NIC profile?
Best regards
Carlos
5 years, 2 months
Tesla P4 and /sys/class/mdev_bus/
by Fabrice Bacchella
I have a Tesla P4 installed on a HPE ProLiant DL360 Gen10 on a CentOS 7.7. The setup was running fine since at least February. I made a successful upgrade from oVirt 4.2 to 4.3 and CentOS 7.6 to CentOS 7.7. I was using in oVirt in a pass-througth setting.
I made a minor upgrade a few days ago. And since the VM is unable to see the Tesla P4. I think that the main problem is with mdev. vdsm-client Host hostdevListByCaps | grep mdev return nothing. There is no directory /sys/class/mdev_bus. I tried a full modload: modprobe nvidia_vgpu_vfio nvidia vfio_mdev mdev vfio_iommu_type1 vfio nvidia nvidia-modeset nvidia-drm nvidia-uvm vfio-pci. But it does nothing.
Why did my kernel think the P4 is not mdev-compatible any more ? How can I check that ? I think it break when upgrading my kernel from kernel-3.10.0-1062.1.2.el7.x86_64 to kernel-3.10.0-1062.4.1.el7.x86_64.
I tried with both the nouveau driver and the nvidia driver.
5 years, 2 months
Re: Do I need to use self hosted engine with a GlusterFs three node setup
by Strahil
I remember creating my oVirt setup in 2 stages:
1. Using cockpit to deploy the gluster cluster
2. Using cockpit to deploy HCI on the created gluster clustet.
If that's not changed you can only deploy the gluster clustet, thrn deploy the engine somewhere else and then connect the engine (add storage domain) to the gluster cluster, which also can be your oVirt compute nodes (making them at the end HyperConverged oVirt Cluster).
Of course , that was an year ago - so it could be different.
Best Regards,
Strahil NikolovOn Nov 13, 2019 14:16, donagh.moran(a)oracle.com wrote:
>
> Hi Vojtech
>
> Thanks for the info, I have been looking for a method of creating the gluster cluster via cockpit on one of my three hosts but the only way I can see is via the hosted engine setup. Is it a case that we need to configure the hosts to use gluster storage with the cli commands prior to adding it to a pre-existing non hosted engine?
>
> Donagh
> _______________________________________________
> Users mailing list -- users(a)ovirt.org
> To unsubscribe send an email to users-leave(a)ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/IIEY3Z3GDGH...
5 years, 2 months
[ANN] oVirt 4.3.7 Third Release Candidate is now available for testing
by Sandro Bonazzola
The oVirt Project is pleased to announce the availability of the oVirt
4.3.7 Third Release Candidate for testing, as of November 13th, 2019.
This update is a release candidate of the seventh in a series of
stabilization updates to the 4.3 series.
This is pre-release software. This pre-release should not to be used in
production.
This release is available now on x86_64 architecture for:
* Red Hat Enterprise Linux 7.7 or later (but <8)
* CentOS Linux (or similar) 7.7 or later (but <8)
This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:
* Red Hat Enterprise Linux 7.7 or later (but <8)
* CentOS Linux (or similar) 7.7 or later (but <8)
* oVirt Node 4.3 (available for x86_64 only) has been built consuming
CentOS 7.7 Release
See the release notes [1] for known issues, new features and bugs fixed.
While testing this release candidate please note that oVirt node now
includes:
- ansible 2.9.0
- GlusterFS 6.6
Notes:
- oVirt Appliance is already available
- oVirt Node is already available
Additional Resources:
* Read more about the oVirt 4.3.7 release highlights:
http://www.ovirt.org/release/4.3.7/
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/
[1] http://www.ovirt.org/release/4.3.7/
[2] http://resources.ovirt.org/pub/ovirt-4.3-pre/iso/
--
Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <https://www.redhat.com/>
sbonazzo(a)redhat.com
<https://www.redhat.com/>*Red Hat respects your work life balance.
Therefore there is no need to answer this email out of your office hours.*
5 years, 2 months
Re: restore
by suporte＠logicworks.pt
yes you are right. I miss that. Sorry
Thanks a lot
De: "Staniforth, Paul" <P.Staniforth(a)leedsbeckett.ac.uk>
Para: suporte(a)logicworks.pt, "users" <users(a)ovirt.org>
Enviadas: Terça-feira, 12 De Novembro de 2019 17:49:18
Assunto: Re: restore
As you did a full backup including the data warehouse you need
engine-backup --mode=restore --file=file_name --log=log_file_name --provision-db --provision-dwh-db --restore-permissions
see https://www.ovirt.org/documentation/admin-guide/chap-Backups_and_Migratio...
Backups and Migration | oVirt
Chapter 12: Backups and Migration Backing Up and Restoring the oVirt Engine Backing up oVirt Engine - Overview. Use the engine-backup tool to take regular backups of the oVirt Engine. The tool backs up the engine database and configuration files into a single file and can be run without interrupting the ovirt-engine service.. Syntax for the engine-backup Command
www.ovirt.org
Regards,
Paul S.
From: suporte(a)logicworks.pt <suporte(a)logicworks.pt>
Sent: 12 November 2019 17:39
To: users <users(a)ovirt.org>
Subject: [ovirt-users] restore
Hi,
I did a backup of engine like this
# engine-backup --scope=all --mode=backup --file=file_name --log=log_file_name
In a newly installed machine try to restore it:
# yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release43.rpm
# yum update
# yum install ovirt-engine
# engine-backup --mode=restore --file=file_name --log=log_file_name --provision-db --restore-permissions
but get this error:
Start of engine-backup with mode 'restore'
scope: all
archive file: file_name
log file: log_file_name
Preparing to restore:
- Unpacking file 'file_name'
Restoring:
- Files
Provisioning PostgreSQL users/databases:
- user 'engine', database 'engine'
Restoring:
FATAL: Can't connect to database 'ovirt_engine_history'. Please see '/usr/bin/engine-backup --help'.
I'm running ovirt Version:4.3.4.3-1.el7
If I run
# engine-backup --mode=restore --file=file_name --log=log_file_name --provision-db --no-restore-permissions
still the same error
Any idea?
Many Thanks
--
Jose Ferradeira
http://www.logicworks.pt
To view the terms under which this email is distributed, please go to:-
http://leedsbeckett.ac.uk/disclaimer/email/
5 years, 2 months
