date:20190705

Hi oVirters,

Did a 4.1 - > 4.2.8 -> 4.3.4 upgrade in two hops. Here is my experience,
hope it can save you some pain.

Gotchas
1. For shutdown VMs, their disks were deactivated (though still attached)
2. For shutdown VMs, their NICs were "Up" but "Unplugged"
3. VM Custom Compatibility Version is hard to find. (If it is too old say
3.6, 4.1) they won't start up. The location is: VM -> Edit -> System ->
Advanced Parameters (click this)

"Advanced Parameters" is an expandable widget that is quite small when
collapsed. When it is expanded then you will see "Custom Compatibility
Version"

4. Storage Domain migration to V5: I use a NFS storoage domain. This is
migrated to the "V5" format and a lot of cleanup is done. If you have stray
files or images not owned by 36:36 (vdsm:kvm on my NFS server), the V5
upgrade will fail, there will be no SPM, and the Data Center will oscillate
between Non-responsive and Contending.

Why would there be non 36:36 uid/gid files? This is a long story, but from
the older 3.x days when there was less functionality, we would sometimes
directly manipulate the filesystem and/or qcow2 images using guestfish or
equivalent tools which would change the owner to qemu:qemu. Forgetting to
chown back to vdsm:kvm is a recipe for pain.

Cheers!

--
Richard Chan
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/HSPSXO3JQ5ZMECSB3UMJCNPOSNO5PKRR/

[ovirt-users] Ovirt Secure boot issues

2019-07-05 Thread Strahil

Hello All,

I would like to ask any of you to do a simple test.
Please install a linux on a VM with Secure boot and after the install wizzard 
is over -power it off and then on.

Here is what I have observed:
1. UEFI forgets the certificates after a poweroff and asks for the openSUSE 
certificate every time. Rebooting from the VM doesn't cause any problems till 
nextg boot.

2. RHEL8 grub menu consists only of 'System setup'.
When you select it - you are sent to the UEFI menu. If you select continue - 
everything is fine.
Poweroff + Poweron makes everything to repeat.

Do you observe the same issues. If I'm not the only one hitting this - I will 
open a bug, otherwise I will try to further debug this.

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/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/KRHVCLFGDSXHTTV3W72MMQ7CVK5XUFED/

[ovirt-users] Re: Bad Gateway buhaa

2019-07-05 Thread Vrgotic, Marko

This is great Dominik,

I promise to send my feedback by end of this week.

— — —
Met vriendelijke groet / Best regards,

Marko Vrgotic
Sr. System Engineer
ActiveVideo

Tel. +31 (0)35 677 4131
email: m.vrgo...@activevideo.com
skype: av.mvrgotic.se
www.activevideo.com

From: Dominik Holler 
Sent: Friday, July 5, 2019 8:42:01 AM
To: Vrgotic, Marko
Cc: users@ovirt.org; Miguel Duarte de Mora Barroso
Subject: Re: [ovirt-users] Bad Gateway buhaa

On Fri, 5 Jul 2019 06:36:15 +
"Vrgotic, Marko"  wrote:

> Thank you Dominik,
>
> I will look into ovn-provider configuration than.
>

It is step 8 in
https://www.ovirt.org/documentation/admin-guide/chap-External_Providers.html#adding-an-external-network-provider

> Where can I found some more technical  information on ovn-provider (is it in 
> any way related to openvswitch) and how it’s utilized by oVirt? I am talking 
> besides oVirt online documentation.
>

Happy you ask!
We have created the document
https://github.com/oVirt/ovirt-provider-ovn/blob/master/docs/provider_api_description.adoc
and would be interested in your feedback, to improve it.

>
> — — —
> Met vriendelijke groet / Best regards,
>
> Marko Vrgotic
> Sr. System Engineer
> ActiveVideo
>
> Tel. +31 (0)35 677 4131
> email: m.vrgo...@activevideo.com
> skype: av.mvrgotic.se
> www.activevideo.com
> 
> From: Dominik Holler 
> Sent: Friday, July 5, 2019 8:06:29 AM
> To: Vrgotic, Marko
> Cc: users@ovirt.org
> Subject: Re: [ovirt-users] Bad Gateway buhaa
>
> On Thu, 4 Jul 2019 13:10:52 +
> "Vrgotic, Marko"  wrote:
>
> > Dear oVIrt,
> >
> > Although it should be simple, I am failing to understand the connection 
> > between Default Gateway setting and Bad Gateway issue.
> >
> > On which network I need to set default gateway:
> >
> > Our ovirtmgmt is set not to be used by Guest VMs, only Hosted-Engine.
> >
> > We have tenant1 network which is assigned to VM Guest instances and it has 
> > Default Gateway, working one .
> > Why am I still seeing this message:
> >
> > 2019-07-04 12:53:08,991Z ERROR 
> > [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] 
> > (EE-ManagedThreadFactory-engineScheduled-Thread-54) [2cfff521] Command 
> > 'org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand' 
> > failed: EngineException: (Failed with error Bad Gateway and code 5050)
> >
> > What am I doing wrong?
> >
>
>
> There seems to be a problem with the configuration of the
> ovirt-provider-ovn. If you do not want to use OVN networking, you can
> just disable the "Automatic Synchronization" of the ovirt-provider-ovn.
>
> > If you need more info or log data, just let me know.
> >
> > oVIrt 4.3.3
> >
> > Kindly awating your reply.
> >
> > Marko Vrgotic
> > ActiveVideo
>

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/PC5U5Q27WY3AXTVJYTAGQ56MHAIQQ27T/

[ovirt-users] Regarding VDSM_Hooks

2019-07-05 Thread Vrgotic, Marko

Dear oVIrt,

Happy to report I have deployed my first python vdsm_hook which removes A, 
, TXT records of VM each time after_vm_destroy event is triggered, and it 
works fine.
This was required to be able to quickly redploy/rebuild VMs using same hostname.

Issue I am observing/just discovered now is:
Since live_migration of VM guest is considered a destruction from Host 
perspective, DNS records get deleted and VM lands on new host without being 
resolvable  .

I would like to introduce another python script for hook regarding migration 
events to get these entries back into DNS but for that I need there IPs.

Question:

  *   Where can I find/locate/read VMs IPs and Hostnames (is it dom_xml) to be 
able to incorporate them for DNS Update script?
Or even better:

  *   What would be even better, is there a way to not trigger the dns update 
if VM is being Migrated? Can I use dom_xml or other location to check wheter VM 
is migrated  or not,  which would allow me to control if dnsupdate should be 
triggered or not


If its relevant for the question: we are currently running oVIrt 4.3.3 version

Kindly awaiting your reply.

Marko Vrgotic
ActiveVideo
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/TRQJAAGDZN67BLLWRLLRAGYUSB2EDAWA/

[ovirt-users] Re: 4.2.8: NPE starting a specific VM

This VM and interface cause NPE

 id  |   vm_guid
 | vmt_guid | mac_addr  | name | speed | type |
_create_date  | _update_date  | linked |
vnic_profile_id
--+--+--+---+--+---+--+---+---++--
 29c09fc1-1ddf-40e1-8355-1acbdd84f913 |
cb5dee7e-5bc6-4eb3-88a9-614a90ebfd71 |  | 00:1a:4a:2f:48:83 | nic1
| 1 |3 | 2017-04-26 23:31:58.662743+08 | 2019-07-06
00:35:27.401616+08 | t  | 0f1c7d97-a156-416c-a62a-ed7d5bc3dc0e
(1 row)

On Fri, Jul 5, 2019 at 7:03 PM Dominik Holler  wrote:

> Can you please share the output of
> /usr/share/ovirt-engine/dbscripts/engine-psql.sh  -c "select * from
> vm_interface"
> ? You are welcme to restrict like
> /usr/share/ovirt-engine/dbscripts/engine-psql.sh  -c "select * from
> vm_interface where vm_guid='xxx' "
> if you know the id of the vm.
>
>
> On Fri, Jul 5, 2019 at 9:46 AM Richard Chan 
> wrote:
>
>> Encountering a NPE on 4.2.8. This is the first start after a 4.1 to 4.2
>> upgrade.
>>
>> 2019-07-05 15:36:56,912+08 ERROR
>> [org.ovirt.engine.core.vdsbroker.CreateVDSCommand]
>> (EE-ManagedThreadFactory-engine-Thread-45700) [64500cdd-b623-4bb1-a7a1-841
>> 6b4e6723b] Failed to create VM: java.lang.NullPointerException
>> at
>> org.ovirt.engine.core.vdsbroker.builder.vminfo.LibvirtVmXmlBuilder.lambda$writeInterfaces$26(LibvirtVmXmlBuilder.java:1198)
>> [vdsbroker.jar:]
>> at
>> java.util.Comparator.lambda$comparing$77a9974f$1(Comparator.java:469)
>> [rt.jar:1.8.0_212]
>> at java.util.TimSort.countRunAndMakeAscending(TimSort.java:355)
>> [rt.jar:1.8.0_212]
>> at java.util.TimSort.sort(TimSort.java:220) [rt.jar:1.8.0_212]
>> at java.util.Arrays.sort(Arrays.java:1512) [rt.jar:1.8.0_212]
>> at
>> java.util.stream.SortedOps$SizedRefSortingSink.end(SortedOps.java:348)
>> [rt.jar:1.8.0_212]
>> at
>> java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:483)
>> [rt.jar:1.8.0_212]
>> at
>> java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472)
>> [rt.jar:1.8.0_212]
>> at
>> java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
>> [rt.jar:1.8.0_212]
>> at
>> java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
>> [rt.jar:1.8.0_212]
>> at
>> java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
>> [rt.jar:1.8.0_212]
>> at
>> java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418)
>> [rt.jar:1.8.0_212]
>> at
>> org.ovirt.engine.core.vdsbroker.builder.vminfo.LibvirtVmXmlBuilder.writeInterfaces(LibvirtVmXmlBuilder.java:1199)
>> [vdsbroker.jar:]
>> at
>> org.ovirt.engine.core.vdsbroker.builder.vminfo.LibvirtVmXmlBuilder.writeDevices(LibvirtVmXmlBuilder.java:1045)
>> [vdsbroker.jar:]
>> at
>> org.ovirt.engine.core.vdsbroker.builder.vminfo.LibvirtVmXmlBuilder.buildCreateVm(LibvirtVmXmlBuilder.java:254)
>> [vdsbroker.jar:]
>> at
>> org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCommand.generateDomainXml(CreateBrokerVDSCommand.java:93)
>> [vdsbroker.jar:]
>> at
>> org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCommand.createInfo(CreateBrokerVDSCommand.java:50)
>> [vdsbroker.jar:]
>> at
>> org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCommand.executeVdsBrokerCommand(CreateBrokerVDSCommand.java:42)
>> [vdsbroker.jar:]
>> at
>> org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVdsCommandWithNetworkEvent(VdsBrokerCommand.java:123)
>> [vdsbroker.jar:]
>> at
>> org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVDSCommand(VdsBrokerCommand.java:111)
>> [vdsbroker.jar:]
>> at
>> org.ovirt.engine.core.vdsbroker.VDSCommandBase.executeCommand(VDSCommandBase.java:73)
>> [vdsbroker.jar:]
>> at
>> org.ovirt.engine.core.dal.VdcCommandBase.execute(VdcCommandBase.java:33)
>> [dal.jar:]
>>
>> This leads to Failed to run VM message. Any ideas?
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Thanks
>> Richard Chan
>> ___
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@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/ICCUANEM2C3FUJFGJYXT22XB6O54JBWN/
>>
>

-- 
Richard Chan
Chief Architect

TreeBox Solutions Pte Ltd
1 Commonwealth Lane #03-01
Singapore 149544
Tel: 6570 3725
http://www.treeboxsolutions.com

Co.Reg.No. 201100585R
___
Users mailing list -- users@ovirt.org
To

[ovirt-users] Re: Upgraded to 4.3: getting SpmStart failure

This is in the engine.log

[storage.StoragePool] Trying to upgrade master domain
`f9aaa65a-0ac7-4c61-a27d-15af3901
6419` (sp:479)
2019-07-06 00:24:14,056+0800 INFO  (tasks/5) [storage.StorageDomain]
Converting domain f9aaa65a-0ac7-4c61-a27d-15af39016419 volumes
metadata from version 4 to version 5 (fileSD:811)
2019-07-06 00:24:14,121+0800 INFO  (tasks/5) [storage.StorageDomain]
Removing remnants of deleted images [] (fileSD:740)
2019-07-06 00:24:14,121+0800 ERROR (tasks/5) [storage.StoragePool]
Unexpected error (sp:383)
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/vdsm/storage/sp.py", line 333, in
startSpm

On Fri, Jul 5, 2019 at 11:31 PM Strahil  wrote:

> Can you run the engine manually on another server ?
> hosted-engine --vm-start
>
> Best Regards,
> Strahil Nikolov
> On Jul 5, 2019 18:05, Richard Chan  wrote:
>
> My engine is getting SpmStart failure.
>
> What is the best way to troubleshoot this?
>
>
> --
> Richard Chan
>
>

-- 
Richard Chan
Chief Architect

TreeBox Solutions Pte Ltd
1 Commonwealth Lane #03-01
Singapore 149544
Tel: 6570 3725
http://www.treeboxsolutions.com

Co.Reg.No. 201100585R
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/GW7HOCWLI2OVGC2OR7A6AAAYCBXGOPLT/

[ovirt-users] Re: Upgraded to 4.3: getting SpmStart failure

Unfortunately, this is a separate engine running external to the oVirt
cluster.
The main error on the hosts is: any idea what this Volume is referring to?
I have 3 existings storage domains
ISO EXPORT and DATA all upgraded to 4.3
None have this UUID.


VolumeDoesNotExist: Volume does not exist:
(u'1d1b6dfd-197a-4583-8398-6b941dbca854',)

2019-07-05 23:02:15,954+0800 ERROR (tasks/0) [storage.StoragePool] failed:
Volume does not exist: (u'1d1b6dfd-197a-4583-8398-6b941dbca854',) (sp:384)
2019-07-05 23:02:15,954+0800 INFO  (tasks/0) [storage.SANLock] Releasing
Lease(name='SDM',
path=u'/rhev/data-center/mnt/192.168.88.40:_genie_ovirt_data/f9aaa65a-0ac7-4c61-a27d-15af39016419/dom_md/leases',
offset=1048576) (clusterlock:488)
2019-07-05 23:02:15,955+0800 INFO  (tasks/0) [storage.SANLock] Successfully
released Lease(name='SDM',
path=u'/rhev/data-center/mnt/192.168.88.40:_genie_ovirt_data/f9aaa65a-0ac7-4c61-a27d-15af39016419/dom_md/leases',
offset=1048576) (clusterlock:497)
2019-07-05 23:02:15,955+0800 ERROR (tasks/0) [storage.TaskManager.Task]
(Task='159b9026-7034-43c2-9587-8fec036e92ba') Unexpected error (task:875)
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 882,
in _run
return fn(*args, **kargs)
  File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 336,
in run
return self.cmd(*self.argslist, **self.argsdict)
  File "/usr/lib/python2.7/site-packages/vdsm/storage/sp.py", line 333, in
startSpm
self._upgradePool(expectedDomVersion, __securityOverride=True)
  File "/usr/lib/python2.7/site-packages/vdsm/storage/securable.py", line
79, in wrapper
return method(self, *args, **kwargs)
  File "/usr/lib/python2.7/site-packages/vdsm/storage/sp.py", line 484, in
_upgradePool
str(targetDomVersion))
  File "/usr/lib/python2.7/site-packages/vdsm/storage/sp.py", line 1108, in
_convertDomain
targetFormat)
  File "/usr/lib/python2.7/site-packages/vdsm/storage/formatconverter.py",
line 447, in convert
converter(repoPath, hostId, imageRepo, isMsd)
  File "/usr/lib/python2.7/site-packages/vdsm/storage/formatconverter.py",
line 405, in v5DomainConverter
domain.convert_volumes_metadata(target_version)
  File "/usr/lib/python2.7/site-packages/vdsm/storage/fileSD.py", line 813,
in convert_volumes_metadata
for vol in self.iter_volumes():
  File "/usr/lib/python2.7/site-packages/vdsm/storage/sd.py", line 764, in
iter_volumes
yield self.produceVolume(img_id, vol_id)
  File "/usr/lib/python2.7/site-packages/vdsm/storage/sd.py", line 846, in
produceVolume
volUUID)
  File "/usr/lib/python2.7/site-packages/vdsm/storage/volume.py", line 817,
in __init__
self._manifest = self.manifestClass(repoPath, sdUUID, imgUUID, volUUID)
  File "/usr/lib/python2.7/site-packages/vdsm/storage/fileVolume.py", line
71, in __init__
volUUID)
  File "/usr/lib/python2.7/site-packages/vdsm/storage/volume.py", line 86,
in __init__
self.validate()
  File "/usr/lib/python2.7/site-packages/vdsm/storage/volume.py", line 112,
in validate
self.validateVolumePath()
  File "/usr/lib/python2.7/site-packages/vdsm/storage/fileVolume.py", line
131, in validateVolumePath
raise se.VolumeDoesNotExist(self.volUUID)

On Fri, Jul 5, 2019 at 11:31 PM Strahil  wrote:

> Can you run the engine manually on another server ?
> hosted-engine --vm-start
>
> Best Regards,
> Strahil Nikolov
> On Jul 5, 2019 18:05, Richard Chan  wrote:
>
> My engine is getting SpmStart failure.
>
> What is the best way to troubleshoot this?
>
>
> --
> Richard Chan
>
>

-- 
Richard Chan
Chief Architect

TreeBox Solutions Pte Ltd
1 Commonwealth Lane #03-01
Singapore 149544
Tel: 6570 3725
http://www.treeboxsolutions.com

Co.Reg.No. 201100585R
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/3A5Y2JMNHBTPWET4LOFTONYPEGORLGZK/

[ovirt-users] Re: Upgraded to 4.3: getting SpmStart failure

2019-07-05 Thread Strahil

Can you run the engine manually on another server ?
hosted-engine --vm-start

Best Regards,
Strahil NikolovOn Jul 5, 2019 18:05, Richard Chan 
 wrote:
>
> My engine is getting SpmStart failure.
>
> What is the best way to troubleshoot this?
>
>
> -- 
> Richard Chan
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/LTYGACYXBB65FMSWNZLZZFLC2XQZU7WG/

[ovirt-users] importing a vm is always very slow

2019-07-05 Thread Crazy Ayansh

Hi Users,

Why importing the vm from export domain is very slow and how can we do it
fast ? How to cancel a import process ?

[image: image.png]

Thanks
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/I6QPWTWOSAYNW6TPZXGW7LF6DB3EI763/

[ovirt-users] Upgraded to 4.3: getting SpmStart failure

My engine is getting SpmStart failure.

What is the best way to troubleshoot this?


-- 
Richard Chan
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/7B5NVNYOTFAEIIWUTOQWJ7NL56J6DAIR/

[ovirt-users] Re: Anaconda crashing on start while trying to Install oVirt Node on bare metal

2019-07-05 Thread rubentrindade

I ended up just installing CentOS. Wasn't my preferred way, but it gets things 
done.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/7O7KRTG2JNFBS2CK55TZ7R3DCYKZDPBG/

[ovirt-users] Re: HE deployment failing

2019-07-05 Thread Strahil Nikolov

 Parth,
did you use cockpit to deploy the gluster volume ? 
it's interesting why the cockpit allowed the engine's volume to be so small ...
Best Regards,Strahil Nikolov

В петък, 5 юли 2019 г., 10:17:11 ч. Гринуич-4, Simone Tiraboschi 
 написа:  
 
 

On Fri, Jul 5, 2019 at 4:12 PM Parth Dhanjal  wrote:

Hey!

I'm trying to deploy a 3 node cluster with gluster storage.
After the gluster deployment is completed successfully, the creation of storage 
domain fails during HE deployment giving the error:

[ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Error: the 
target storage domain contains only 46.0GiB of available space while a minimum 
of 61.0GiB is required If you wish to use the current target storage domain by 
extending it, make sure it contains nothing before adding it."}
I have tried to increase the disk size(provided in storage tab) to 90GiB. But 
the deployment still fails. A 50GiB storage domain is created by default even 
if some other size is provided.


The issue is on the size of the gluster volume not on the size of the 
hosted-engine VM disk.Please try extending the gluater volume.
 

Has anyone faced a similar issue?
Regards
Parth Dhanjal___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/W2CM74EU6KPPJ2NL3HXBTYPHDO7BMZB6/



-- 

Simone Tiraboschi

He / Him / His

Principal Software Engineer

Red Hat

stira...@redhat.com   
@redhatjobs   redhatjobs @redhatjobs  
|  |  |

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/2MFPZNCLNLXOT3YNB4S5XKP546GDHBHY/
  ___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/QN4HEPJ5BOTTKEYOIIFFN4XAK43O552E/

[ovirt-users] Re: HE deployment failing

2019-07-05 Thread Strahil Nikolov

 Did you expand all your Gluster Bricks to have at least 61Gb (arbiter is not 
needed) ?
A simple "df -h /gluster_bricks/engine/engine" should show the available space 
of your brick.
Best Regards,Strahil Nikolov

В петък, 5 юли 2019 г., 10:12:01 ч. Гринуич-4, Parth Dhanjal 
 написа:  
 
 Hey!

I'm trying to deploy a 3 node cluster with gluster storage.
After the gluster deployment is completed successfully, the creation of storage 
domain fails during HE deployment giving the error:

[ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Error: the 
target storage domain contains only 46.0GiB of available space while a minimum 
of 61.0GiB is required If you wish to use the current target storage domain by 
extending it, make sure it contains nothing before adding it."}
I have tried to increase the disk size(provided in storage tab) to 90GiB. But 
the deployment still fails. A 50GiB storage domain is created by default even 
if some other size is provided.

Has anyone faced a similar issue?
Regards
Parth Dhanjal___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/W2CM74EU6KPPJ2NL3HXBTYPHDO7BMZB6/
  ___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/5CT6Q4QLGYZQYMPG3NHTQ7MA4URW7YJG/

[ovirt-users] Re: VM snapshot - some info needed

2019-07-05 Thread Strahil Nikolov

 Can someone tell me if this is an expected behaviour , or only my setup is 
defective ?Thanks in advance.
Best Regards,Strahil Nikolov

В сряда, 3 юли 2019 г., 13:09:09 ч. Гринуич-4, Strahil Nikolov 
 написа:  
 
 Hello Community,
I have noticed that if I want a VM snapshot with memory - I get a warning "The 
VM will be paused while saving the memory" .Is there a way to make snapshot 
without pausing the VM for the whole duration ?

I have noticed that it doesn't matter if VM has qemu-guest-agent or 
ovirt-guest-agent.
Thanks in advance for sharing your thoughts.
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/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/H65UWNWRA4NLXASWUYMXTF2Y3Y5MGVZ2/

[ovirt-users] Re: HE deployment failing

On Fri, Jul 5, 2019 at 4:12 PM Parth Dhanjal  wrote:

> Hey!
>
> I'm trying to deploy a 3 node cluster with gluster storage.
> After the gluster deployment is completed successfully, the creation of
> storage domain fails during HE deployment giving the error:
>
> [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Error:
> the target storage domain contains only 46.0GiB of available space while a
> minimum of 61.0GiB is required If you wish to use the current target
> storage domain by extending it, make sure it contains nothing before adding
> it."}
> I have tried to increase the disk size(provided in storage tab) to 90GiB.
> But the deployment still fails. A 50GiB storage domain is created by
> default even if some other size is provided.
>

The issue is on the size of the gluster volume not on the size of the
hosted-engine VM disk.
Please try extending the gluater volume.



>
> Has anyone faced a similar issue?
>
> Regards
> Parth Dhanjal
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@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/W2CM74EU6KPPJ2NL3HXBTYPHDO7BMZB6/
>


-- 

Simone Tiraboschi

He / Him / His

Principal Software Engineer

Red Hat 

stira...@redhat.com
@redhatjobs    redhatjobs
 @redhatjobs



___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/2MFPZNCLNLXOT3YNB4S5XKP546GDHBHY/

[ovirt-users] HE deployment failing

2019-07-05 Thread Parth Dhanjal

Hey!

I'm trying to deploy a 3 node cluster with gluster storage.
After the gluster deployment is completed successfully, the creation of
storage domain fails during HE deployment giving the error:

[ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Error:
the target storage domain contains only 46.0GiB of available space while a
minimum of 61.0GiB is required If you wish to use the current target
storage domain by extending it, make sure it contains nothing before adding
it."}
I have tried to increase the disk size(provided in storage tab) to 90GiB.
But the deployment still fails. A 50GiB storage domain is created by
default even if some other size is provided.

Has anyone faced a similar issue?

Regards
Parth Dhanjal
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/W2CM74EU6KPPJ2NL3HXBTYPHDO7BMZB6/

[ovirt-users] Re: [ovirt-devel] USB on host support?

2019-07-05 Thread jplor...@gmail.com

Hi Hetz,

Nice video. I already did that in my setup. The thing is that it's not
working properly for audio devices. I see that it's mandatory to enable usb
support in console which creates me the doubt if this creates some kind of
flow through spice.
Regards,


El lun., 1 de julio de 2019 6:31 p. m., Hetz Ben Hamo 
escribió:

> Hi,
> See this video that I've created how to use usb on host
> https://youtu.be/pSLjH_gc09U
>
> Thanks
> Hetz
>
> On Tue, Jul 2, 2019, 00:04 Juan Pablo Lorier  wrote:
>
>> I'm having a similar problem. The passtrough needs 2 steps, the first is
>> to attach the host device to the VM, but if you don't enable the spice usb
>> the vm fails to start. I don't know if the USB works straight from the host
>> device or if it depends on the spice console.
>>
>> In my case, a device that work in a windows 10 pc doesn't work in a
>> windows 10 vm.
>>
>> Maybe we both can get help in this matter.
>>
>> Regards
>> El 1/7/19 a las 13:02, users-requ...@ovirt.org escribió:
>>
>> Send Users mailing list submissions to
>>  users@ovirt.org
>>
>> To subscribe or unsubscribe via email, send a message with subject or
>> body 'help' to
>>  users-requ...@ovirt.org
>>
>> You can reach the person managing the list at
>>  users-ow...@ovirt.org
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of Users digest..."
>>
>>
>> Today's Topics:
>>
>>1.  Re: Failed on HE-Storage migration (Strahil Nikolov)
>>2.  Adding a custom fence agent on 4.3.4 (Matteo)
>>3.  USB host support? (Hetz Ben Hamo)
>>4.  Re: [ovirt-devel] USB on host support? (Hetz Ben Hamo)
>>5.  Re: Ovirt Hyperconverged Cluster (Stefanile Raffaele)
>>
>>
>> ___
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@ovirt.org
>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>> oVirt Code of Conduct: 
>> https://www.ovirt.org/community/about/community-guidelines/
>>
>>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/3AQHL4VDPKGL6OUDQ4J7G6KKMTOMYR4N/

[ovirt-users] Re: 4.3 won't upgrade engine in standalone KVM VM: low_custom_compatibility_version 'agent03'

Ah - it found a oVirt VM called agent03 - that has nothing to do with the
engine VM.

I think I confused myself, and thought engine-setup did not like the engine
VM.
Actually it was complaining about an existing oVirt VM...Hmmm - this VM was
indeed set to 3.6.

Thank you!!

On Fri, Jul 5, 2019 at 9:22 PM Simone Tiraboschi 
wrote:

>
>
> On Fri, Jul 5, 2019 at 3:15 PM Simone Tiraboschi 
> wrote:
>
>>
>>
>> On Fri, Jul 5, 2019 at 3:06 PM Richard Chan 
>> wrote:
>>
>>> In libvirt/virsh  the VM is called "ovirt7"; here is the domain
>>> definition. This VM has been upgraded from
>>> 3.6->4.0->4.1->4.2. This is the first time engine-setup has complained
>>> about the "level" of the VM.
>>>
>>> libvirt domain definition:
>>>
>>
>> oVirt VMs contains something like:
>>
>>   http://ovirt.org/vm/tune/1.0; xmlns:ovirt-vm="
>> http://ovirt.org/vm/1.0;>
>> 
>> http://ovirt.org/vm/1.0;>
>> 4.2
>>
>> in the XML for libvirt so you are checking the wrong VM.
>>
>
> Please try executing this on your engine VM:
>
> sudo -u postgres scl enable rh-postgresql95 -- psql -d engine -c "select *
> from vms where vm_name='agent03'"
>
>
>>
>>
>>>
>>> 
>>>   ovirt7
>>>   cdb0f3fd-42c7-4a16-bcd1-5d65f19aca19
>>>   8388608
>>>   8388608
>>>   2
>>>   
>>> /machine
>>>   
>>>   
>>> hvm
>>> >> type='pflash'>/usr/share/edk2.git/ovmf-x64/OVMF_CODE-pure-efi.fd
>>> /var/lib/libvirt/qemu/nvram/ovirt7_VARS.fd
>>> 
>>>   
>>>   
>>> 
>>> 
>>> 
>>>   
>>>   
>>> Haswell-noTSX
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>>   
>>>   
>>> 
>>> 
>>> 
>>>   
>>>   destroy
>>>   restart
>>>   destroy
>>>   
>>> 
>>> 
>>>   
>>>   
>>> /usr/libexec/qemu-kvm
>>> 
>>>   
>>>   
>>>   
>>> 
>>> 
>>> 
>>>   
>>>   
>>>   
>>>   
>>> 
>>> 
>>>   
>>>   
>>>   
>>> 
>>> >> file='/var/lib/libvirt/images/ovirt7/database_01.WAEqcow2'/>
>>> 
>>>   
>>>   
>>>   
>>>   
>>> 
>>> 
>>>   
>>>   >> function='0x7'/>
>>> 
>>> 
>>>   
>>>   
>>>   >> function='0x0' multifunction='on'/>
>>> 
>>> 
>>>   
>>>   
>>>   >> function='0x1'/>
>>> 
>>> 
>>>   
>>>   
>>>   >> function='0x2'/>
>>> 
>>> 
>>>   
>>>   >> function='0x0'/>
>>> 
>>> 
>>>   
>>> 
>>> 
>>>   
>>>   >> function='0x0'/>
>>> 
>>> 
>>>   
>>>   
>>>   
>>>   
>>>   
>>>   >> function='0x0'/>
>>> 
>>> 
>>>   
>>>   
>>>   
>>> 
>>> 
>>>   
>>>   
>>>   
>>> 
>>> 
>>>   >> path='/var/lib/libvirt/qemu/channel/target/domain-15-ovirt7/org.qemu.guest_agent.0'/>
>>>   >> state='connected'/>
>>>   
>>>   
>>> 
>>> 
>>>   >> state='disconnected'/>
>>>   
>>>   
>>> 
>>> 
>>>   
>>>   
>>> 
>>> 
>>>   
>>> 
>>> 
>>>   
>>> 
>>> 
>>>   
>>> 
>>> 
>>>   
>>>   >> function='0x0'/>
>>> 
>>> 
>>>   >> heads='1' primary='yes'/>
>>>   
>>>   >> function='0x0'/>
>>> 
>>> 
>>>   
>>>   
>>> 
>>> 
>>>   
>>>   
>>> 
>>> 
>>>   
>>>   >> function='0x0'/>
>>> 
>>>   
>>>   
>>> system_u:system_r:svirt_t:s0:c194,c775
>>> system_u:object_r:svirt_image_t:s0:c194,c775
>>>   
>>>   
>>> +107:+107
>>> +107:+107
>>>   
>>> 
>>>
>>> On Fri, Jul 5, 2019 at 8:53 PM Simone Tiraboschi 
>>> wrote:
>>>


 On Fri, Jul 5, 2019 at 2:48 PM Richard Chan <
 rich...@treeboxsolutions.com> wrote:

> Hi,
>
>  I am running 4.2 engine in a standalone libvirt KVM VM (running on a
> hypervisor that is not part of the oVirt infrastructure); i.e., I am not
> using hosted engine but still running engine in a VM.
>
> Now 4.3 won't upgrade inside this libvirt KVM VM:
>
> Failed to execute stage 'Setup validation': Cannot upgrade the Engine
> due to low custom_compatibility_version for virtual
>  machines: ['agent03']. Please edit this virtual machines, in edit VM
> dialog go to System->Advanced Parameters -> Custom Compatibility Version
> and either reset to empty (cluster default) or set a value supported by 
> the
> new installation: 4.1, 4.2, 4.3.
>
> engine-setup has probably detected that it is running inside a VM:
> 1. Where did it get 'agent03' string from
> 2. Any suggestions how to fool engine-setup to think this is 4.3
>

 The engine is not going to check anything on hosts that are unknown at
 engine eyes.
 I think that you simply have in the engine a VM called 'agent03'.
 Please check it.


>
> Here is the dmidecode of the standalone engine VM:
>
> # dmidecode 3.1
> Getting SMBIOS data from sysfs.
> SMBIOS 2.8

[ovirt-users] Re: 4.3 won't upgrade engine in standalone KVM VM: low_custom_compatibility_version 'agent03'

This engine VM running as part of the oVirt cluster (not hosted engine/not
running under oVirt).

It is running on a separate libvirt/KVM server. This hypervisor is totally
separate and standalone: it is not a oVirt host.

This VM has been controlling the oVirt hosts since 3.6 days.

Inside this VM I have installed ovirt-release43.rpm and now running
engine-setup.

On Fri, Jul 5, 2019 at 9:15 PM Simone Tiraboschi 
wrote:

>
>
> On Fri, Jul 5, 2019 at 3:06 PM Richard Chan 
> wrote:
>
>> In libvirt/virsh  the VM is called "ovirt7"; here is the domain
>> definition. This VM has been upgraded from
>> 3.6->4.0->4.1->4.2. This is the first time engine-setup has complained
>> about the "level" of the VM.
>>
>> libvirt domain definition:
>>
>
> oVirt VMs contains something like:
>
>   http://ovirt.org/vm/tune/1.0; xmlns:ovirt-vm="
> http://ovirt.org/vm/1.0;>
> 
> http://ovirt.org/vm/1.0;>
> 4.2
>
> in the XML for libvirt so you are checking the wrong VM.
>
>
>>
>> 
>>   ovirt7
>>   cdb0f3fd-42c7-4a16-bcd1-5d65f19aca19
>>   8388608
>>   8388608
>>   2
>>   
>> /machine
>>   
>>   
>> hvm
>> > type='pflash'>/usr/share/edk2.git/ovmf-x64/OVMF_CODE-pure-efi.fd
>> /var/lib/libvirt/qemu/nvram/ovirt7_VARS.fd
>> 
>>   
>>   
>> 
>> 
>> 
>>   
>>   
>> Haswell-noTSX
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>   
>>   
>> 
>> 
>> 
>>   
>>   destroy
>>   restart
>>   destroy
>>   
>> 
>> 
>>   
>>   
>> /usr/libexec/qemu-kvm
>> 
>>   
>>   
>>   
>> 
>> 
>> 
>>   
>>   
>>   
>>   
>> 
>> 
>>   
>>   
>>   
>> 
>> > file='/var/lib/libvirt/images/ovirt7/database_01.WAEqcow2'/>
>> 
>>   
>>   
>>   
>>   
>> 
>> 
>>   
>>   > function='0x7'/>
>> 
>> 
>>   
>>   
>>   > function='0x0' multifunction='on'/>
>> 
>> 
>>   
>>   
>>   > function='0x1'/>
>> 
>> 
>>   
>>   
>>   > function='0x2'/>
>> 
>> 
>>   
>>   > function='0x0'/>
>> 
>> 
>>   
>> 
>> 
>>   
>>   > function='0x0'/>
>> 
>> 
>>   
>>   
>>   
>>   
>>   
>>   > function='0x0'/>
>> 
>> 
>>   
>>   
>>   
>> 
>> 
>>   
>>   
>>   
>> 
>> 
>>   > path='/var/lib/libvirt/qemu/channel/target/domain-15-ovirt7/org.qemu.guest_agent.0'/>
>>   > state='connected'/>
>>   
>>   
>> 
>> 
>>   > state='disconnected'/>
>>   
>>   
>> 
>> 
>>   
>>   
>> 
>> 
>>   
>> 
>> 
>>   
>> 
>> 
>>   
>> 
>> 
>>   
>>   > function='0x0'/>
>> 
>> 
>>   > primary='yes'/>
>>   
>>   > function='0x0'/>
>> 
>> 
>>   
>>   
>> 
>> 
>>   
>>   
>> 
>> 
>>   
>>   > function='0x0'/>
>> 
>>   
>>   
>> system_u:system_r:svirt_t:s0:c194,c775
>> system_u:object_r:svirt_image_t:s0:c194,c775
>>   
>>   
>> +107:+107
>> +107:+107
>>   
>> 
>>
>> On Fri, Jul 5, 2019 at 8:53 PM Simone Tiraboschi 
>> wrote:
>>
>>>
>>>
>>> On Fri, Jul 5, 2019 at 2:48 PM Richard Chan <
>>> rich...@treeboxsolutions.com> wrote:
>>>
 Hi,

  I am running 4.2 engine in a standalone libvirt KVM VM (running on a
 hypervisor that is not part of the oVirt infrastructure); i.e., I am not
 using hosted engine but still running engine in a VM.

 Now 4.3 won't upgrade inside this libvirt KVM VM:

 Failed to execute stage 'Setup validation': Cannot upgrade the Engine
 due to low custom_compatibility_version for virtual
  machines: ['agent03']. Please edit this virtual machines, in edit VM
 dialog go to System->Advanced Parameters -> Custom Compatibility Version
 and either reset to empty (cluster default) or set a value supported by the
 new installation: 4.1, 4.2, 4.3.

 engine-setup has probably detected that it is running inside a VM:
 1. Where did it get 'agent03' string from
 2. Any suggestions how to fool engine-setup to think this is 4.3

>>>
>>> The engine is not going to check anything on hosts that are unknown at
>>> engine eyes.
>>> I think that you simply have in the engine a VM called 'agent03'.
>>> Please check it.
>>>
>>>

 Here is the dmidecode of the standalone engine VM:

 # dmidecode 3.1
 Getting SMBIOS data from sysfs.
 SMBIOS 2.8 present.
 11 structures occupying 591 bytes.
 Table at 0xBFED7000.

 Handle 0x0100, DMI type 1, 27 bytes
 System Information
 Manufacturer: Red Hat
 Product Name: KVM
 Version: RHEL 7.3.0 PC (i440FX + PIIX, 1996)
 Serial Number: Not Specified
 UUID: cdb0f3fd-42c7-4a16-bcd1-5d65f19aca19
 Wake-up Type: Power Switch
 SKU Number: Not Specified
 Family: Red Hat

[ovirt-users] Re: 4.3 won't upgrade engine in standalone KVM VM: low_custom_compatibility_version 'agent03'

On Fri, Jul 5, 2019 at 3:15 PM Simone Tiraboschi 
wrote:

>
>
> On Fri, Jul 5, 2019 at 3:06 PM Richard Chan 
> wrote:
>
>> In libvirt/virsh  the VM is called "ovirt7"; here is the domain
>> definition. This VM has been upgraded from
>> 3.6->4.0->4.1->4.2. This is the first time engine-setup has complained
>> about the "level" of the VM.
>>
>> libvirt domain definition:
>>
>
> oVirt VMs contains something like:
>
>   http://ovirt.org/vm/tune/1.0; xmlns:ovirt-vm="
> http://ovirt.org/vm/1.0;>
> 
> http://ovirt.org/vm/1.0;>
> 4.2
>
> in the XML for libvirt so you are checking the wrong VM.
>

Please try executing this on your engine VM:

sudo -u postgres scl enable rh-postgresql95 -- psql -d engine -c "select *
from vms where vm_name='agent03'"


>
>
>>
>> 
>>   ovirt7
>>   cdb0f3fd-42c7-4a16-bcd1-5d65f19aca19
>>   8388608
>>   8388608
>>   2
>>   
>> /machine
>>   
>>   
>> hvm
>> > type='pflash'>/usr/share/edk2.git/ovmf-x64/OVMF_CODE-pure-efi.fd
>> /var/lib/libvirt/qemu/nvram/ovirt7_VARS.fd
>> 
>>   
>>   
>> 
>> 
>> 
>>   
>>   
>> Haswell-noTSX
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>   
>>   
>> 
>> 
>> 
>>   
>>   destroy
>>   restart
>>   destroy
>>   
>> 
>> 
>>   
>>   
>> /usr/libexec/qemu-kvm
>> 
>>   
>>   
>>   
>> 
>> 
>> 
>>   
>>   
>>   
>>   
>> 
>> 
>>   
>>   
>>   
>> 
>> > file='/var/lib/libvirt/images/ovirt7/database_01.WAEqcow2'/>
>> 
>>   
>>   
>>   
>>   
>> 
>> 
>>   
>>   > function='0x7'/>
>> 
>> 
>>   
>>   
>>   > function='0x0' multifunction='on'/>
>> 
>> 
>>   
>>   
>>   > function='0x1'/>
>> 
>> 
>>   
>>   
>>   > function='0x2'/>
>> 
>> 
>>   
>>   > function='0x0'/>
>> 
>> 
>>   
>> 
>> 
>>   
>>   > function='0x0'/>
>> 
>> 
>>   
>>   
>>   
>>   
>>   
>>   > function='0x0'/>
>> 
>> 
>>   
>>   
>>   
>> 
>> 
>>   
>>   
>>   
>> 
>> 
>>   > path='/var/lib/libvirt/qemu/channel/target/domain-15-ovirt7/org.qemu.guest_agent.0'/>
>>   > state='connected'/>
>>   
>>   
>> 
>> 
>>   > state='disconnected'/>
>>   
>>   
>> 
>> 
>>   
>>   
>> 
>> 
>>   
>> 
>> 
>>   
>> 
>> 
>>   
>> 
>> 
>>   
>>   > function='0x0'/>
>> 
>> 
>>   > primary='yes'/>
>>   
>>   > function='0x0'/>
>> 
>> 
>>   
>>   
>> 
>> 
>>   
>>   
>> 
>> 
>>   
>>   > function='0x0'/>
>> 
>>   
>>   
>> system_u:system_r:svirt_t:s0:c194,c775
>> system_u:object_r:svirt_image_t:s0:c194,c775
>>   
>>   
>> +107:+107
>> +107:+107
>>   
>> 
>>
>> On Fri, Jul 5, 2019 at 8:53 PM Simone Tiraboschi 
>> wrote:
>>
>>>
>>>
>>> On Fri, Jul 5, 2019 at 2:48 PM Richard Chan <
>>> rich...@treeboxsolutions.com> wrote:
>>>
 Hi,

  I am running 4.2 engine in a standalone libvirt KVM VM (running on a
 hypervisor that is not part of the oVirt infrastructure); i.e., I am not
 using hosted engine but still running engine in a VM.

 Now 4.3 won't upgrade inside this libvirt KVM VM:

 Failed to execute stage 'Setup validation': Cannot upgrade the Engine
 due to low custom_compatibility_version for virtual
  machines: ['agent03']. Please edit this virtual machines, in edit VM
 dialog go to System->Advanced Parameters -> Custom Compatibility Version
 and either reset to empty (cluster default) or set a value supported by the
 new installation: 4.1, 4.2, 4.3.

 engine-setup has probably detected that it is running inside a VM:
 1. Where did it get 'agent03' string from
 2. Any suggestions how to fool engine-setup to think this is 4.3

>>>
>>> The engine is not going to check anything on hosts that are unknown at
>>> engine eyes.
>>> I think that you simply have in the engine a VM called 'agent03'.
>>> Please check it.
>>>
>>>

 Here is the dmidecode of the standalone engine VM:

 # dmidecode 3.1
 Getting SMBIOS data from sysfs.
 SMBIOS 2.8 present.
 11 structures occupying 591 bytes.
 Table at 0xBFED7000.

 Handle 0x0100, DMI type 1, 27 bytes
 System Information
 Manufacturer: Red Hat
 Product Name: KVM
 Version: RHEL 7.3.0 PC (i440FX + PIIX, 1996)
 Serial Number: Not Specified
 UUID: cdb0f3fd-42c7-4a16-bcd1-5d65f19aca19
 Wake-up Type: Power Switch
 SKU Number: Not Specified
 Family: Red Hat Enterprise Linux

 Handle 0x0300, DMI type 3, 21 bytes
 Chassis Information
 Manufacturer: Red Hat
 Type: Other
 Lock: Not Present
 Version: RHEL 7.3.0 PC (i440FX + PIIX, 1996)

[ovirt-users] Re: 4.3 won't upgrade engine in standalone KVM VM: low_custom_compatibility_version 'agent03'

On Fri, Jul 5, 2019 at 3:06 PM Richard Chan 
wrote:

> In libvirt/virsh  the VM is called "ovirt7"; here is the domain
> definition. This VM has been upgraded from
> 3.6->4.0->4.1->4.2. This is the first time engine-setup has complained
> about the "level" of the VM.
>
> libvirt domain definition:
>

oVirt VMs contains something like:

  http://ovirt.org/vm/tune/1.0; xmlns:ovirt-vm="
http://ovirt.org/vm/1.0;>

http://ovirt.org/vm/1.0;>
4.2

in the XML for libvirt so you are checking the wrong VM.


>
> 
>   ovirt7
>   cdb0f3fd-42c7-4a16-bcd1-5d65f19aca19
>   8388608
>   8388608
>   2
>   
> /machine
>   
>   
> hvm
>  type='pflash'>/usr/share/edk2.git/ovmf-x64/OVMF_CODE-pure-efi.fd
> /var/lib/libvirt/qemu/nvram/ovirt7_VARS.fd
> 
>   
>   
> 
> 
> 
>   
>   
> Haswell-noTSX
> 
> 
> 
> 
> 
> 
> 
>   
>   
> 
> 
> 
>   
>   destroy
>   restart
>   destroy
>   
> 
> 
>   
>   
> /usr/libexec/qemu-kvm
> 
>   
>   
>   
> 
> 
> 
>   
>   
>   
>   
> 
> 
>   
>   
>   
> 
>  file='/var/lib/libvirt/images/ovirt7/database_01.WAEqcow2'/>
> 
>   
>   
>   
>   
> 
> 
>   
>function='0x7'/>
> 
> 
>   
>   
>function='0x0' multifunction='on'/>
> 
> 
>   
>   
>function='0x1'/>
> 
> 
>   
>   
>function='0x2'/>
> 
> 
>   
>function='0x0'/>
> 
> 
>   
> 
> 
>   
>function='0x0'/>
> 
> 
>   
>   
>   
>   
>   
>function='0x0'/>
> 
> 
>   
>   
>   
> 
> 
>   
>   
>   
> 
> 
>path='/var/lib/libvirt/qemu/channel/target/domain-15-ovirt7/org.qemu.guest_agent.0'/>
>state='connected'/>
>   
>   
> 
> 
>state='disconnected'/>
>   
>   
> 
> 
>   
>   
> 
> 
>   
> 
> 
>   
> 
> 
>   
> 
> 
>   
>function='0x0'/>
> 
> 
>primary='yes'/>
>   
>function='0x0'/>
> 
> 
>   
>   
> 
> 
>   
>   
> 
> 
>   
>function='0x0'/>
> 
>   
>   
> system_u:system_r:svirt_t:s0:c194,c775
> system_u:object_r:svirt_image_t:s0:c194,c775
>   
>   
> +107:+107
> +107:+107
>   
> 
>
> On Fri, Jul 5, 2019 at 8:53 PM Simone Tiraboschi 
> wrote:
>
>>
>>
>> On Fri, Jul 5, 2019 at 2:48 PM Richard Chan 
>> wrote:
>>
>>> Hi,
>>>
>>>  I am running 4.2 engine in a standalone libvirt KVM VM (running on a
>>> hypervisor that is not part of the oVirt infrastructure); i.e., I am not
>>> using hosted engine but still running engine in a VM.
>>>
>>> Now 4.3 won't upgrade inside this libvirt KVM VM:
>>>
>>> Failed to execute stage 'Setup validation': Cannot upgrade the Engine
>>> due to low custom_compatibility_version for virtual
>>>  machines: ['agent03']. Please edit this virtual machines, in edit VM
>>> dialog go to System->Advanced Parameters -> Custom Compatibility Version
>>> and either reset to empty (cluster default) or set a value supported by the
>>> new installation: 4.1, 4.2, 4.3.
>>>
>>> engine-setup has probably detected that it is running inside a VM:
>>> 1. Where did it get 'agent03' string from
>>> 2. Any suggestions how to fool engine-setup to think this is 4.3
>>>
>>
>> The engine is not going to check anything on hosts that are unknown at
>> engine eyes.
>> I think that you simply have in the engine a VM called 'agent03'.
>> Please check it.
>>
>>
>>>
>>> Here is the dmidecode of the standalone engine VM:
>>>
>>> # dmidecode 3.1
>>> Getting SMBIOS data from sysfs.
>>> SMBIOS 2.8 present.
>>> 11 structures occupying 591 bytes.
>>> Table at 0xBFED7000.
>>>
>>> Handle 0x0100, DMI type 1, 27 bytes
>>> System Information
>>> Manufacturer: Red Hat
>>> Product Name: KVM
>>> Version: RHEL 7.3.0 PC (i440FX + PIIX, 1996)
>>> Serial Number: Not Specified
>>> UUID: cdb0f3fd-42c7-4a16-bcd1-5d65f19aca19
>>> Wake-up Type: Power Switch
>>> SKU Number: Not Specified
>>> Family: Red Hat Enterprise Linux
>>>
>>> Handle 0x0300, DMI type 3, 21 bytes
>>> Chassis Information
>>> Manufacturer: Red Hat
>>> Type: Other
>>> Lock: Not Present
>>> Version: RHEL 7.3.0 PC (i440FX + PIIX, 1996)
>>> Serial Number: Not Specified
>>> Asset Tag: Not Specified
>>> Boot-up State: Safe
>>> Power Supply State: Safe
>>> Thermal State: Safe
>>> Security Status: Unknown
>>> OEM Information: 0x
>>> Height: Unspecified
>>> Number Of Power Cords: Unspecified
>>> Contained Elements: 0
>>>
>>> Handle 0x0400, DMI type 4, 42 bytes
>>> Processor Information
>>> Socket Designation: CPU 0
>>> Type: Central Processor
>>> Family: Other
>>> Manufacturer: Red Hat
>>> ID: C1 06 03 00 FF FB 8B 07
>>> Version: RHEL 7.3.0 PC (i440FX + PIIX,

[ovirt-users] Re: 4.3 won't upgrade engine in standalone KVM VM: low_custom_compatibility_version 'agent03'

In libvirt/virsh  the VM is called "ovirt7"; here is the domain definition.
This VM has been upgraded from
3.6->4.0->4.1->4.2. This is the first time engine-setup has complained
about the "level" of the VM.

libvirt domain definition:


  ovirt7
  cdb0f3fd-42c7-4a16-bcd1-5d65f19aca19
  8388608
  8388608
  2
  
/machine
  
  
hvm
/usr/share/edk2.git/ovmf-x64/OVMF_CODE-pure-efi.fd
/var/lib/libvirt/qemu/nvram/ovirt7_VARS.fd

  
  



  
  
Haswell-noTSX







  
  



  
  destroy
  restart
  destroy
  


  
  
/usr/libexec/qemu-kvm

  
  
  



  
  
  
  


  
  
  



  
  
  
  


  
  


  
  
  


  
  
  


  
  
  


  
  


  


  
  


  
  
  
  
  
  


  
  
  


  
  
  


  
  
  
  


  
  
  


  
  


  


  


  


  
  


  
  
  


  
  


  
  


  
  

  
  
system_u:system_r:svirt_t:s0:c194,c775
system_u:object_r:svirt_image_t:s0:c194,c775
  
  
+107:+107
+107:+107
  


On Fri, Jul 5, 2019 at 8:53 PM Simone Tiraboschi 
wrote:

>
>
> On Fri, Jul 5, 2019 at 2:48 PM Richard Chan 
> wrote:
>
>> Hi,
>>
>>  I am running 4.2 engine in a standalone libvirt KVM VM (running on a
>> hypervisor that is not part of the oVirt infrastructure); i.e., I am not
>> using hosted engine but still running engine in a VM.
>>
>> Now 4.3 won't upgrade inside this libvirt KVM VM:
>>
>> Failed to execute stage 'Setup validation': Cannot upgrade the Engine due
>> to low custom_compatibility_version for virtual
>>  machines: ['agent03']. Please edit this virtual machines, in edit VM
>> dialog go to System->Advanced Parameters -> Custom Compatibility Version
>> and either reset to empty (cluster default) or set a value supported by the
>> new installation: 4.1, 4.2, 4.3.
>>
>> engine-setup has probably detected that it is running inside a VM:
>> 1. Where did it get 'agent03' string from
>> 2. Any suggestions how to fool engine-setup to think this is 4.3
>>
>
> The engine is not going to check anything on hosts that are unknown at
> engine eyes.
> I think that you simply have in the engine a VM called 'agent03'.
> Please check it.
>
>
>>
>> Here is the dmidecode of the standalone engine VM:
>>
>> # dmidecode 3.1
>> Getting SMBIOS data from sysfs.
>> SMBIOS 2.8 present.
>> 11 structures occupying 591 bytes.
>> Table at 0xBFED7000.
>>
>> Handle 0x0100, DMI type 1, 27 bytes
>> System Information
>> Manufacturer: Red Hat
>> Product Name: KVM
>> Version: RHEL 7.3.0 PC (i440FX + PIIX, 1996)
>> Serial Number: Not Specified
>> UUID: cdb0f3fd-42c7-4a16-bcd1-5d65f19aca19
>> Wake-up Type: Power Switch
>> SKU Number: Not Specified
>> Family: Red Hat Enterprise Linux
>>
>> Handle 0x0300, DMI type 3, 21 bytes
>> Chassis Information
>> Manufacturer: Red Hat
>> Type: Other
>> Lock: Not Present
>> Version: RHEL 7.3.0 PC (i440FX + PIIX, 1996)
>> Serial Number: Not Specified
>> Asset Tag: Not Specified
>> Boot-up State: Safe
>> Power Supply State: Safe
>> Thermal State: Safe
>> Security Status: Unknown
>> OEM Information: 0x
>> Height: Unspecified
>> Number Of Power Cords: Unspecified
>> Contained Elements: 0
>>
>> Handle 0x0400, DMI type 4, 42 bytes
>> Processor Information
>> Socket Designation: CPU 0
>> Type: Central Processor
>> Family: Other
>> Manufacturer: Red Hat
>> ID: C1 06 03 00 FF FB 8B 07
>> Version: RHEL 7.3.0 PC (i440FX + PIIX, 1996)
>> Voltage: Unknown
>> External Clock: Unknown
>> Max Speed: 2000 MHz
>> Current Speed: 2000 MHz
>> Status: Populated, Enabled
>> Upgrade: Other
>> L1 Cache Handle: Not Provided
>> L2 Cache Handle: Not Provided
>> L3 Cache Handle: Not Provided
>> Serial Number: Not Specified
>> Asset Tag: Not Specified
>> Part Number: Not Specified
>> Core Count: 1
>> Core Enabled: 1
>> Thread Count: 1
>> Characteristics: None
>>
>> Handle 0x0401, DMI type 4, 42 bytes
>> Processor Information
>> Socket Designation: CPU 1
>> Type: Central Processor
>> Family: Other
>> Manufacturer: Red Hat
>> ID: C1 06 03 00 FF FB 8B 07
>> Version: RHEL 7.3.0 PC (i440FX + PIIX, 1996)
>> Voltage: Unknown
>> External Clock: Unknown
>> Max Speed: 2000 MHz
>> Current Speed: 2000 MHz
>> Status: Populated, Enabled
>> Upgrade: Other
>> L1 Cache Handle: Not Provided
>> L2 Cache Handle: Not Provided
>> L3 Cache Handle: Not Provided
>> Serial Number: Not Specified
>> Asset Tag: Not Specified
>> Part Number: Not Specified
>> Core Count: 1
>> Core Enabled: 1
>> Thread Count: 1
>> Characteristics: None
>>
>> Handle 0x1000, DMI type 16, 23

[ovirt-users] Re: 4.3 won't upgrade engine in standalone KVM VM: low_custom_compatibility_version 'agent03'

On Fri, Jul 5, 2019 at 2:48 PM Richard Chan 
wrote:

> Hi,
>
>  I am running 4.2 engine in a standalone libvirt KVM VM (running on a
> hypervisor that is not part of the oVirt infrastructure); i.e., I am not
> using hosted engine but still running engine in a VM.
>
> Now 4.3 won't upgrade inside this libvirt KVM VM:
>
> Failed to execute stage 'Setup validation': Cannot upgrade the Engine due
> to low custom_compatibility_version for virtual
>  machines: ['agent03']. Please edit this virtual machines, in edit VM
> dialog go to System->Advanced Parameters -> Custom Compatibility Version
> and either reset to empty (cluster default) or set a value supported by the
> new installation: 4.1, 4.2, 4.3.
>
> engine-setup has probably detected that it is running inside a VM:
> 1. Where did it get 'agent03' string from
> 2. Any suggestions how to fool engine-setup to think this is 4.3
>

The engine is not going to check anything on hosts that are unknown at
engine eyes.
I think that you simply have in the engine a VM called 'agent03'.
Please check it.


>
> Here is the dmidecode of the standalone engine VM:
>
> # dmidecode 3.1
> Getting SMBIOS data from sysfs.
> SMBIOS 2.8 present.
> 11 structures occupying 591 bytes.
> Table at 0xBFED7000.
>
> Handle 0x0100, DMI type 1, 27 bytes
> System Information
> Manufacturer: Red Hat
> Product Name: KVM
> Version: RHEL 7.3.0 PC (i440FX + PIIX, 1996)
> Serial Number: Not Specified
> UUID: cdb0f3fd-42c7-4a16-bcd1-5d65f19aca19
> Wake-up Type: Power Switch
> SKU Number: Not Specified
> Family: Red Hat Enterprise Linux
>
> Handle 0x0300, DMI type 3, 21 bytes
> Chassis Information
> Manufacturer: Red Hat
> Type: Other
> Lock: Not Present
> Version: RHEL 7.3.0 PC (i440FX + PIIX, 1996)
> Serial Number: Not Specified
> Asset Tag: Not Specified
> Boot-up State: Safe
> Power Supply State: Safe
> Thermal State: Safe
> Security Status: Unknown
> OEM Information: 0x
> Height: Unspecified
> Number Of Power Cords: Unspecified
> Contained Elements: 0
>
> Handle 0x0400, DMI type 4, 42 bytes
> Processor Information
> Socket Designation: CPU 0
> Type: Central Processor
> Family: Other
> Manufacturer: Red Hat
> ID: C1 06 03 00 FF FB 8B 07
> Version: RHEL 7.3.0 PC (i440FX + PIIX, 1996)
> Voltage: Unknown
> External Clock: Unknown
> Max Speed: 2000 MHz
> Current Speed: 2000 MHz
> Status: Populated, Enabled
> Upgrade: Other
> L1 Cache Handle: Not Provided
> L2 Cache Handle: Not Provided
> L3 Cache Handle: Not Provided
> Serial Number: Not Specified
> Asset Tag: Not Specified
> Part Number: Not Specified
> Core Count: 1
> Core Enabled: 1
> Thread Count: 1
> Characteristics: None
>
> Handle 0x0401, DMI type 4, 42 bytes
> Processor Information
> Socket Designation: CPU 1
> Type: Central Processor
> Family: Other
> Manufacturer: Red Hat
> ID: C1 06 03 00 FF FB 8B 07
> Version: RHEL 7.3.0 PC (i440FX + PIIX, 1996)
> Voltage: Unknown
> External Clock: Unknown
> Max Speed: 2000 MHz
> Current Speed: 2000 MHz
> Status: Populated, Enabled
> Upgrade: Other
> L1 Cache Handle: Not Provided
> L2 Cache Handle: Not Provided
> L3 Cache Handle: Not Provided
> Serial Number: Not Specified
> Asset Tag: Not Specified
> Part Number: Not Specified
> Core Count: 1
> Core Enabled: 1
> Thread Count: 1
> Characteristics: None
>
> Handle 0x1000, DMI type 16, 23 bytes
> Physical Memory Array
> Location: Other
> Use: System Memory
> Error Correction Type: Multi-bit ECC
> Maximum Capacity: 8 GB
> Error Information Handle: Not Provided
> Number Of Devices: 1
>
> Handle 0x1100, DMI type 17, 40 bytes
> Memory Device
> Array Handle: 0x1000
> Error Information Handle: Not Provided
> Total Width: Unknown
> Data Width: Unknown
> Size: 8192 MB
> Form Factor: DIMM
> Set: None
> Locator: DIMM 0
> Bank Locator: Not Specified
> Type: RAM
> Type Detail: Other
> Speed: Unknown
> Manufacturer: Red Hat
> Serial Number: Not Specified
> Asset Tag: Not Specified
> Part Number: Not Specified
> Rank: Unknown
> Configured Clock Speed: Unknown
> Minimum Voltage: Unknown
> Maximum Voltage: Unknown
> Configured Voltage: Unknown
>
> Handle 0x1300, DMI type 19, 31 bytes
> Memory Array Mapped Address
> Starting Address: 0x000
> Ending Address: 0x000BFFF
> Range Size: 3 GB
> Physical Array Handle: 0x1000
> Partition Width: 1
>
> Handle 0x1301, DMI type 19, 31 bytes
> Memory Array Mapped Address
> Starting Address: 0x001
> Ending Address: 0x0023FFF
> Range Size: 5 GB
> Physical Array Handle: 0x1000
> Partition Width: 1
>
> Handle 0x2000, DMI type 32, 11 bytes
> System Boot Information
> Status: No errors detected
>
> Handle 0x, DMI type 0, 24 bytes
> BIOS Information
> Vendor: EFI Development Kit II / OVMF
> Version: 0.0.0
> Release Date: 02/06/2015
> Address: 0xE8000
> Runtime Size: 96 kB
> ROM Size: 64 kB
> Characteristics:
> BIOS characteristics not supported
> Targeted content distribution is supported
> UEFI is supported
> System is a virtual machine
> BIOS Revision: 0.0
>
> Handle 0xFEFF, DMI type 127, 4 bytes
> End

[ovirt-users] 4.3 won't upgrade engine in standalone KVM VM: low_custom_compatibility_version 'agent03'

Hi,

 I am running 4.2 engine in a standalone libvirt KVM VM (running on a
hypervisor that is not part of the oVirt infrastructure); i.e., I am not
using hosted engine but still running engine in a VM.

Now 4.3 won't upgrade inside this libvirt KVM VM:

Failed to execute stage 'Setup validation': Cannot upgrade the Engine due
to low custom_compatibility_version for virtual
 machines: ['agent03']. Please edit this virtual machines, in edit VM
dialog go to System->Advanced Parameters -> Custom Compatibility Version
and either reset to empty (cluster default) or set a value supported by the
new installation: 4.1, 4.2, 4.3.

engine-setup has probably detected that it is running inside a VM:
1. Where did it get 'agent03' string from
2. Any suggestions how to fool engine-setup to think this is 4.3

Here is the dmidecode of the standalone engine VM:

# dmidecode 3.1
Getting SMBIOS data from sysfs.
SMBIOS 2.8 present.
11 structures occupying 591 bytes.
Table at 0xBFED7000.

Handle 0x0100, DMI type 1, 27 bytes
System Information
Manufacturer: Red Hat
Product Name: KVM
Version: RHEL 7.3.0 PC (i440FX + PIIX, 1996)
Serial Number: Not Specified
UUID: cdb0f3fd-42c7-4a16-bcd1-5d65f19aca19
Wake-up Type: Power Switch
SKU Number: Not Specified
Family: Red Hat Enterprise Linux

Handle 0x0300, DMI type 3, 21 bytes
Chassis Information
Manufacturer: Red Hat
Type: Other
Lock: Not Present
Version: RHEL 7.3.0 PC (i440FX + PIIX, 1996)
Serial Number: Not Specified
Asset Tag: Not Specified
Boot-up State: Safe
Power Supply State: Safe
Thermal State: Safe
Security Status: Unknown
OEM Information: 0x
Height: Unspecified
Number Of Power Cords: Unspecified
Contained Elements: 0

Handle 0x0400, DMI type 4, 42 bytes
Processor Information
Socket Designation: CPU 0
Type: Central Processor
Family: Other
Manufacturer: Red Hat
ID: C1 06 03 00 FF FB 8B 07
Version: RHEL 7.3.0 PC (i440FX + PIIX, 1996)
Voltage: Unknown
External Clock: Unknown
Max Speed: 2000 MHz
Current Speed: 2000 MHz
Status: Populated, Enabled
Upgrade: Other
L1 Cache Handle: Not Provided
L2 Cache Handle: Not Provided
L3 Cache Handle: Not Provided
Serial Number: Not Specified
Asset Tag: Not Specified
Part Number: Not Specified
Core Count: 1
Core Enabled: 1
Thread Count: 1
Characteristics: None

Handle 0x0401, DMI type 4, 42 bytes
Processor Information
Socket Designation: CPU 1
Type: Central Processor
Family: Other
Manufacturer: Red Hat
ID: C1 06 03 00 FF FB 8B 07
Version: RHEL 7.3.0 PC (i440FX + PIIX, 1996)
Voltage: Unknown
External Clock: Unknown
Max Speed: 2000 MHz
Current Speed: 2000 MHz
Status: Populated, Enabled
Upgrade: Other
L1 Cache Handle: Not Provided
L2 Cache Handle: Not Provided
L3 Cache Handle: Not Provided
Serial Number: Not Specified
Asset Tag: Not Specified
Part Number: Not Specified
Core Count: 1
Core Enabled: 1
Thread Count: 1
Characteristics: None

Handle 0x1000, DMI type 16, 23 bytes
Physical Memory Array
Location: Other
Use: System Memory
Error Correction Type: Multi-bit ECC
Maximum Capacity: 8 GB
Error Information Handle: Not Provided
Number Of Devices: 1

Handle 0x1100, DMI type 17, 40 bytes
Memory Device
Array Handle: 0x1000
Error Information Handle: Not Provided
Total Width: Unknown
Data Width: Unknown
Size: 8192 MB
Form Factor: DIMM
Set: None
Locator: DIMM 0
Bank Locator: Not Specified
Type: RAM
Type Detail: Other
Speed: Unknown
Manufacturer: Red Hat
Serial Number: Not Specified
Asset Tag: Not Specified
Part Number: Not Specified
Rank: Unknown
Configured Clock Speed: Unknown
Minimum Voltage: Unknown
Maximum Voltage: Unknown
Configured Voltage: Unknown

Handle 0x1300, DMI type 19, 31 bytes
Memory Array Mapped Address
Starting Address: 0x000
Ending Address: 0x000BFFF
Range Size: 3 GB
Physical Array Handle: 0x1000
Partition Width: 1

Handle 0x1301, DMI type 19, 31 bytes
Memory Array Mapped Address
Starting Address: 0x001
Ending Address: 0x0023FFF
Range Size: 5 GB
Physical Array Handle: 0x1000
Partition Width: 1

Handle 0x2000, DMI type 32, 11 bytes
System Boot Information
Status: No errors detected

Handle 0x, DMI type 0, 24 bytes
BIOS Information
Vendor: EFI Development Kit II / OVMF
Version: 0.0.0
Release Date: 02/06/2015
Address: 0xE8000
Runtime Size: 96 kB
ROM Size: 64 kB
Characteristics:
BIOS characteristics not supported
Targeted content distribution is supported
UEFI is supported
System is a virtual machine
BIOS Revision: 0.0

Handle 0xFEFF, DMI type 127, 4 bytes
End Of Table

Cheers

-- 
Richard Chan
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/VW6LVDLBNMZBXO5AW5CYG2BHACZSMPLR/

[ovirt-users] Re: Any one uses Nvidia T4 as vGPU in production?

2019-07-05 Thread Paolo Margara

Hi list,

so no one that want to share his experience with nVidia T4, vgpu and
ovirt? Who uses vgpus with ovirt what kind of gpu are using?


Greetings,

    Paolo

Il 15/06/19 21:22, Arman Khalatyan ha scritto:
> Hello,
> any successful stories of the Nvidia T4 usage with the Ovirt?
> I was wondered if one would get 2 hosts each with T4s , are there 
> live migrations possible? 
> thanks,
> Arman
>
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@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/KVFNFU3YFO5CACZFT3TGLYIA6OLLGIKF/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/JVEYTRKSWS2LQDWKC4BU7BJDHFNZ7BNH/

[ovirt-users] Re: 4.2.8: NPE starting a specific VM

Can you please share the output of
/usr/share/ovirt-engine/dbscripts/engine-psql.sh  -c "select * from
vm_interface"
? You are welcme to restrict like
/usr/share/ovirt-engine/dbscripts/engine-psql.sh  -c "select * from
vm_interface where vm_guid='xxx' "
if you know the id of the vm.


On Fri, Jul 5, 2019 at 9:46 AM Richard Chan 
wrote:

> Encountering a NPE on 4.2.8. This is the first start after a 4.1 to 4.2
> upgrade.
>
> 2019-07-05 15:36:56,912+08 ERROR
> [org.ovirt.engine.core.vdsbroker.CreateVDSCommand]
> (EE-ManagedThreadFactory-engine-Thread-45700) [64500cdd-b623-4bb1-a7a1-841
> 6b4e6723b] Failed to create VM: java.lang.NullPointerException
> at
> org.ovirt.engine.core.vdsbroker.builder.vminfo.LibvirtVmXmlBuilder.lambda$writeInterfaces$26(LibvirtVmXmlBuilder.java:1198)
> [vdsbroker.jar:]
> at
> java.util.Comparator.lambda$comparing$77a9974f$1(Comparator.java:469)
> [rt.jar:1.8.0_212]
> at java.util.TimSort.countRunAndMakeAscending(TimSort.java:355)
> [rt.jar:1.8.0_212]
> at java.util.TimSort.sort(TimSort.java:220) [rt.jar:1.8.0_212]
> at java.util.Arrays.sort(Arrays.java:1512) [rt.jar:1.8.0_212]
> at
> java.util.stream.SortedOps$SizedRefSortingSink.end(SortedOps.java:348)
> [rt.jar:1.8.0_212]
> at
> java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:483)
> [rt.jar:1.8.0_212]
> at
> java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472)
> [rt.jar:1.8.0_212]
> at
> java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
> [rt.jar:1.8.0_212]
> at
> java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
> [rt.jar:1.8.0_212]
> at
> java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> [rt.jar:1.8.0_212]
> at
> java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418)
> [rt.jar:1.8.0_212]
> at
> org.ovirt.engine.core.vdsbroker.builder.vminfo.LibvirtVmXmlBuilder.writeInterfaces(LibvirtVmXmlBuilder.java:1199)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.builder.vminfo.LibvirtVmXmlBuilder.writeDevices(LibvirtVmXmlBuilder.java:1045)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.builder.vminfo.LibvirtVmXmlBuilder.buildCreateVm(LibvirtVmXmlBuilder.java:254)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCommand.generateDomainXml(CreateBrokerVDSCommand.java:93)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCommand.createInfo(CreateBrokerVDSCommand.java:50)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCommand.executeVdsBrokerCommand(CreateBrokerVDSCommand.java:42)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVdsCommandWithNetworkEvent(VdsBrokerCommand.java:123)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVDSCommand(VdsBrokerCommand.java:111)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.VDSCommandBase.executeCommand(VDSCommandBase.java:73)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.dal.VdcCommandBase.execute(VdcCommandBase.java:33)
> [dal.jar:]
>
> This leads to Failed to run VM message. Any ideas?
>
>
>
>
>
>
>
>
>
> Thanks
> Richard Chan
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@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/ICCUANEM2C3FUJFGJYXT22XB6O54JBWN/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/LKA4S6P2LRM4AVVSX6G3BPXSXG6KVQO6/

[ovirt-users] 4.2.8: NPE starting a specific VM

Encountering a NPE on 4.2.8. This is the first start after a 4.1 to 4.2
upgrade.

2019-07-05 15:36:56,912+08 ERROR
[org.ovirt.engine.core.vdsbroker.CreateVDSCommand]
(EE-ManagedThreadFactory-engine-Thread-45700) [64500cdd-b623-4bb1-a7a1-841
6b4e6723b] Failed to create VM: java.lang.NullPointerException
at
org.ovirt.engine.core.vdsbroker.builder.vminfo.LibvirtVmXmlBuilder.lambda$writeInterfaces$26(LibvirtVmXmlBuilder.java:1198)
[vdsbroker.jar:]
at
java.util.Comparator.lambda$comparing$77a9974f$1(Comparator.java:469)
[rt.jar:1.8.0_212]
at java.util.TimSort.countRunAndMakeAscending(TimSort.java:355)
[rt.jar:1.8.0_212]
at java.util.TimSort.sort(TimSort.java:220) [rt.jar:1.8.0_212]
at java.util.Arrays.sort(Arrays.java:1512) [rt.jar:1.8.0_212]
at
java.util.stream.SortedOps$SizedRefSortingSink.end(SortedOps.java:348)
[rt.jar:1.8.0_212]
at
java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:483)
[rt.jar:1.8.0_212]
at
java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472)
[rt.jar:1.8.0_212]
at
java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
[rt.jar:1.8.0_212]
at
java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
[rt.jar:1.8.0_212]
at
java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
[rt.jar:1.8.0_212]
at
java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418)
[rt.jar:1.8.0_212]
at
org.ovirt.engine.core.vdsbroker.builder.vminfo.LibvirtVmXmlBuilder.writeInterfaces(LibvirtVmXmlBuilder.java:1199)
[vdsbroker.jar:]
at
org.ovirt.engine.core.vdsbroker.builder.vminfo.LibvirtVmXmlBuilder.writeDevices(LibvirtVmXmlBuilder.java:1045)
[vdsbroker.jar:]
at
org.ovirt.engine.core.vdsbroker.builder.vminfo.LibvirtVmXmlBuilder.buildCreateVm(LibvirtVmXmlBuilder.java:254)
[vdsbroker.jar:]
at
org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCommand.generateDomainXml(CreateBrokerVDSCommand.java:93)
[vdsbroker.jar:]
at
org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCommand.createInfo(CreateBrokerVDSCommand.java:50)
[vdsbroker.jar:]
at
org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCommand.executeVdsBrokerCommand(CreateBrokerVDSCommand.java:42)
[vdsbroker.jar:]
at
org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVdsCommandWithNetworkEvent(VdsBrokerCommand.java:123)
[vdsbroker.jar:]
at
org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVDSCommand(VdsBrokerCommand.java:111)
[vdsbroker.jar:]
at
org.ovirt.engine.core.vdsbroker.VDSCommandBase.executeCommand(VDSCommandBase.java:73)
[vdsbroker.jar:]
at
org.ovirt.engine.core.dal.VdcCommandBase.execute(VdcCommandBase.java:33)
[dal.jar:]

This leads to Failed to run VM message. Any ideas?









Thanks
Richard Chan
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/ICCUANEM2C3FUJFGJYXT22XB6O54JBWN/

[ovirt-users] Re: Bad Gateway buhaa

On Fri, 5 Jul 2019 07:24:37 +
"Vrgotic, Marko"  wrote:

> This is great Dominik,
> 
> I promise to send my feedback by end of this week.
> 


Great!

There is a talk on conceptual level in
https://archive.fosdem.org/2018/schedule/event/vai_leveraging_sdn_for_virtualization/
which might be interesting for you, too.


> — — —
> Met vriendelijke groet / Best regards,
> 
> Marko Vrgotic
> Sr. System Engineer
> ActiveVideo
> 
> Tel. +31 (0)35 677 4131
> email: m.vrgo...@activevideo.com
> skype: av.mvrgotic.se
> www.activevideo.com
> 
> From: Dominik Holler 
> Sent: Friday, July 5, 2019 8:42:01 AM
> To: Vrgotic, Marko
> Cc: users@ovirt.org; Miguel Duarte de Mora Barroso
> Subject: Re: [ovirt-users] Bad Gateway buhaa
> 
> On Fri, 5 Jul 2019 06:36:15 +
> "Vrgotic, Marko"  wrote:
> 
> > Thank you Dominik,
> >
> > I will look into ovn-provider configuration than.
> >
> 
> It is step 8 in
> https://www.ovirt.org/documentation/admin-guide/chap-External_Providers.html#adding-an-external-network-provider
> 
> > Where can I found some more technical  information on ovn-provider (is it 
> > in any way related to openvswitch) and how it’s utilized by oVirt? I am 
> > talking besides oVirt online documentation.
> >
> 
> Happy you ask!
> We have created the document
> https://github.com/oVirt/ovirt-provider-ovn/blob/master/docs/provider_api_description.adoc
> and would be interested in your feedback, to improve it.
> 
> >
> > — — —
> > Met vriendelijke groet / Best regards,
> >
> > Marko Vrgotic
> > Sr. System Engineer
> > ActiveVideo
> >
> > Tel. +31 (0)35 677 4131
> > email: m.vrgo...@activevideo.com
> > skype: av.mvrgotic.se
> > www.activevideo.com
> > 
> > From: Dominik Holler 
> > Sent: Friday, July 5, 2019 8:06:29 AM
> > To: Vrgotic, Marko
> > Cc: users@ovirt.org
> > Subject: Re: [ovirt-users] Bad Gateway buhaa
> >
> > On Thu, 4 Jul 2019 13:10:52 +
> > "Vrgotic, Marko"  wrote:
> >
> > > Dear oVIrt,
> > >
> > > Although it should be simple, I am failing to understand the connection 
> > > between Default Gateway setting and Bad Gateway issue.
> > >
> > > On which network I need to set default gateway:
> > >
> > > Our ovirtmgmt is set not to be used by Guest VMs, only Hosted-Engine.
> > >
> > > We have tenant1 network which is assigned to VM Guest instances and it 
> > > has Default Gateway, working one .
> > > Why am I still seeing this message:
> > >
> > > 2019-07-04 12:53:08,991Z ERROR 
> > > [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] 
> > > (EE-ManagedThreadFactory-engineScheduled-Thread-54) [2cfff521] Command 
> > > 'org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand' 
> > > failed: EngineException: (Failed with error Bad Gateway and code 5050)
> > >
> > > What am I doing wrong?
> > >
> >
> >
> > There seems to be a problem with the configuration of the
> > ovirt-provider-ovn. If you do not want to use OVN networking, you can
> > just disable the "Automatic Synchronization" of the ovirt-provider-ovn.
> >
> > > If you need more info or log data, just let me know.
> > >
> > > oVIrt 4.3.3
> > >
> > > Kindly awating your reply.
> > >
> > > Marko Vrgotic
> > > ActiveVideo
> >
> 
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/OG54P3COUMTQLAHNZ6WMCJGRVZYMJ2PD/

[ovirt-users] Re: Bad Gateway buhaa

2019-07-05 Thread Vrgotic, Marko

Thank you Dominik,

I will look into ovn-provider configuration than.

Where can I found some more technical  information on ovn-provider (is it in 
any way related to openvswitch) and how it’s utilized by oVirt? I am talking 
besides oVirt online documentation.


— — —
Met vriendelijke groet / Best regards,

Marko Vrgotic
Sr. System Engineer
ActiveVideo

Tel. +31 (0)35 677 4131
email: m.vrgo...@activevideo.com
skype: av.mvrgotic.se
www.activevideo.com

From: Dominik Holler 
Sent: Friday, July 5, 2019 8:06:29 AM
To: Vrgotic, Marko
Cc: users@ovirt.org
Subject: Re: [ovirt-users] Bad Gateway buhaa

On Thu, 4 Jul 2019 13:10:52 +
"Vrgotic, Marko"  wrote:

> Dear oVIrt,
>
> Although it should be simple, I am failing to understand the connection 
> between Default Gateway setting and Bad Gateway issue.
>
> On which network I need to set default gateway:
>
> Our ovirtmgmt is set not to be used by Guest VMs, only Hosted-Engine.
>
> We have tenant1 network which is assigned to VM Guest instances and it has 
> Default Gateway, working one .
> Why am I still seeing this message:
>
> 2019-07-04 12:53:08,991Z ERROR 
> [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] 
> (EE-ManagedThreadFactory-engineScheduled-Thread-54) [2cfff521] Command 
> 'org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand' 
> failed: EngineException: (Failed with error Bad Gateway and code 5050)
>
> What am I doing wrong?
>


There seems to be a problem with the configuration of the
ovirt-provider-ovn. If you do not want to use OVN networking, you can
just disable the "Automatic Synchronization" of the ovirt-provider-ovn.

> If you need more info or log data, just let me know.
>
> oVIrt 4.3.3
>
> Kindly awating your reply.
>
> Marko Vrgotic
> ActiveVideo

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/AKHUSGEPHL6CBX3CGLLR234VC67LQ3SW/

[ovirt-users] Re: Bad Gateway buhaa

On Fri, 5 Jul 2019 06:36:15 +
"Vrgotic, Marko"  wrote:

> Thank you Dominik,
> 
> I will look into ovn-provider configuration than.
> 

It is step 8 in
https://www.ovirt.org/documentation/admin-guide/chap-External_Providers.html#adding-an-external-network-provider

> Where can I found some more technical  information on ovn-provider (is it in 
> any way related to openvswitch) and how it’s utilized by oVirt? I am talking 
> besides oVirt online documentation.
>

Happy you ask!
We have created the document
https://github.com/oVirt/ovirt-provider-ovn/blob/master/docs/provider_api_description.adoc
and would be interested in your feedback, to improve it.
 
> 
> — — —
> Met vriendelijke groet / Best regards,
> 
> Marko Vrgotic
> Sr. System Engineer
> ActiveVideo
> 
> Tel. +31 (0)35 677 4131
> email: m.vrgo...@activevideo.com
> skype: av.mvrgotic.se
> www.activevideo.com
> 
> From: Dominik Holler 
> Sent: Friday, July 5, 2019 8:06:29 AM
> To: Vrgotic, Marko
> Cc: users@ovirt.org
> Subject: Re: [ovirt-users] Bad Gateway buhaa
> 
> On Thu, 4 Jul 2019 13:10:52 +
> "Vrgotic, Marko"  wrote:
> 
> > Dear oVIrt,
> >
> > Although it should be simple, I am failing to understand the connection 
> > between Default Gateway setting and Bad Gateway issue.
> >
> > On which network I need to set default gateway:
> >
> > Our ovirtmgmt is set not to be used by Guest VMs, only Hosted-Engine.
> >
> > We have tenant1 network which is assigned to VM Guest instances and it has 
> > Default Gateway, working one .
> > Why am I still seeing this message:
> >
> > 2019-07-04 12:53:08,991Z ERROR 
> > [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] 
> > (EE-ManagedThreadFactory-engineScheduled-Thread-54) [2cfff521] Command 
> > 'org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand' 
> > failed: EngineException: (Failed with error Bad Gateway and code 5050)
> >
> > What am I doing wrong?
> >
> 
> 
> There seems to be a problem with the configuration of the
> ovirt-provider-ovn. If you do not want to use OVN networking, you can
> just disable the "Automatic Synchronization" of the ovirt-provider-ovn.
> 
> > If you need more info or log data, just let me know.
> >
> > oVIrt 4.3.3
> >
> > Kindly awating your reply.
> >
> > Marko Vrgotic
> > ActiveVideo
> 
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/O5Q6YNA7C2QUUTF6447AUEMNLLXHHJOD/

[ovirt-users] Re: Bad Gateway buhaa