[ovirt-users] Re: upload_disk.py - CLI Upload Disk

2021-01-03 Thread Steven Rosenberg
Dear Strahil,

For 4.4.4 the sdk examples do require that you create a configuration file.
Here is an example:

~/config/ovirt.conf:


[engine1]

engine_url = http://localhost:8080

username = admin@internal

password = 123

secure = yes

cafile = /home/user/ovirt_engine_master/etc/pki/ovirt-engine/ca.pem


With Best Regards.


Steven Rosenberg.




On Fri, Jan 1, 2021 at 4:48 PM Strahil Nikolov via Users 
wrote:

> Hi Ilan,
>
> Do you know how to use the config for disk_upload.py (or the --engine-url,
> --username, --password-file or --cafile params) on 4.3.10 as I had to
> directly edit the script  ?
>
>
>
> Best Regards,
> Strahil Nikolov
>
>
>
>
>
>
> В четвъртък, 31 декември 2020 г., 00:07:06 Гринуич+2, Jorge Visentini <
> jorgevisent...@gmail.com> написа:
>
>
>
>
>
> Hi Nikolov.
>
> I uploaded to 4.4.4
>
> Em qua., 30 de dez. de 2020 às 14:14, Strahil Nikolov <
> hunter86...@yahoo.com> escreveu:
> > Are you uploading to 4.4 or to the old 4.3 ?
> > I'm asking as there should be an enhancement that makes a checksum on
> the uploads in order to verify that the upload was successfull.
> >
> > Best Regards,
> > Strahil Nikolov
> >
> >
> >
> >
> >
> >
> > В сряда, 30 декември 2020 г., 18:37:52 Гринуич+2, Jorge Visentini <
> jorgevisent...@gmail.com> написа:
> >
> >
> >
> >
> >
> > Hi Ilan.
> >
> > Ohh sorry I didn't understand.
> >
> > I created the file and executed the script as you said and it worked.
> >
> > python3 /usr/share/doc/python3-ovirt-engine-sdk4/examples/upload_disk.py
> -c engine disk01-SO.qcow2 --disk-format qcow2 --disk-sparse --sd-name ISOs
> > [   0.0 ] Checking image...
> > [   0.4 ] Image format: qcow2
> > [   0.4 ] Disk format: cow
> > [   0.4 ] Disk content type: data
> > [   0.4 ] Disk provisioned size: 32213303296
> > [   0.4 ] Disk initial size: 12867010560
> > [   0.4 ] Disk name: disk01-SO.qcow2
> > [   0.4 ] Disk backup: False
> > [   0.4 ] Connecting...
> > [   0.4 ] Creating disk...
> > [  19.4 ] Disk ID: 9328e954-9307-420f-b5d7-7b81071f88a5
> > [  19.4 ] Creating image transfer...
> > [  22.5 ] Transfer ID: 16236f8e-79af-4159-83f7-8331a2f25919
> > [  22.5 ] Transfer host name: kcmi1kvm08.kosmo.cloud
> > [  22.5 ] Uploading image...
> > [ 100.00% ] 30.00 GiB, 197.19 seconds, 155.79 MiB/s
> > [ 219.7 ] Finalizing image transfer...
> > [ 227.0 ] Upload completed successfully
> >
> > Thank you for the explanation!
> >
> > Em qua., 30 de dez. de 2020 às 00:54, Ilan Zuckerman <
> izuck...@redhat.com> escreveu:
> >> Hi Jorge,
> >>
> >> Lately DEV started to implement the capability of passing the basic
> arguments for the SDK example scripts with a help of configuration file.
> >> I assume that not all of the example scripts support this new feature
> yet.
> >>
> >> Until now you had to run the examples with:
> >>
> >> --engine-url https://engine1
> >> --username admin@internal
> >> --password-file /path/to/engine1-password
> >> --cafile /path/to/engine1.pem
> >>
> >> This is very painful when running the example a lot.
> >> Now you can run them with:
> >>
> >> -c engine1
> >>
> >> Assuming that you have a configuration file with all the
> >> details at:
> >>
> >> ~/.config/ovirt.conf
> >>
> >> Here is an example for you of how this file should look like:
> >>
> >> [engine1]
> >> engine_url = https://
> >> username = admin@internal
> >> password = xx
> >> cafile = /path/to/engine1.pem
> >>
> >> On Wed, Dec 30, 2020 at 4:18 AM Jorge Visentini <
> jorgevisent...@gmail.com> wrote:
> >>> Hi All.
> >>>
> >>> I'm using version 4.4.4 (latest stable version -
> ovirt-node-ng-installer-4.4.4-2020122111.el8.iso)
> >>>
> >>> I tried using the upload_disk.py script, but I don't think I knew how
> to use it.
> >>>
> >>> When I try to use it, these errors occur:
> >>>
> >>> python3
> /usr/share/doc/python3-ovirt-engine-sdk4/examples/upload_disk.py
> disk01-SO.qcow2 --disk-format qcow2 --sd-name ISOs
> >>> usage: upload_disk.py [-h] -c CONFIG [--debug] [--logfile LOGFILE]
> >>>   [--disk-format {raw,qcow2}] [--disk-sparse]
> >>>   [--enable-backup] --sd-name SD_NAME [--use-proxy]
> >>

[ovirt-users] Re: what is OVF_STORE ?

2020-12-24 Thread Steven Rosenberg
https://en.wikipedia.org/wiki/Open_Virtualization_Format

On Thu, Dec 24, 2020 at 12:10 PM tommy  wrote:

> What’s meaning of the word OVF ?
>
>
>
> What’s OVF_STORE ?
>
>
>
> Thanks.
>
>
>
>
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/4FWS5H65KYUHWFUIRB7J7D6PDGHKXXA4/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/MUJ3WDSAHMPDCIXUSISJSSJJ5TPW2QNP/


[ovirt-users] Re: oVirt 4.4.2 MS Windows 10 sysprep floppy

2020-11-10 Thread Steven Rosenberg
Hi,

OK, it sounds like you should create a VM set to a Windows OS via the
Webadmin (such as in edit). run with Run Once, choose initial run and check
the sysprep check box. Then you can set any configuration you want, run the
VM, seal with sysprep and reboot. After that create a template from the VM.
Then you can use the template to create the VMs you need.

I believe this should clarify the functionality.

With Best Regards.

Steven Rosenberg.

On Tue, Nov 10, 2020 at 1:34 PM  wrote:

> thanks for reply,
> I've made a template W10 and sealed with sysprep generize.
> After now, we want to use this template for new user vms.
> For example, a user wants a vm for personnel usage.
> I create a new vm from template which sealed.
> after creation, we want to customize this vm for the person by using
> sysprep.
> Change Windows pc name, join domain and assign to specific OU
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/N5BF5NNEW7CQWA7A5JKQPB2L4ATBOZV3/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/UGG5NQKIUNJ4V7A7SC4KYDX5WKVSHDBR/


[ovirt-users] Re: oVirt 4.4.2 MS Windows 10 sysprep floppy

2020-11-10 Thread Steven Rosenberg
Hi,

You could use reboot. The idea of sealing is that one sets say the time
zone differently via run once, runs the VM, verify that the Unattend.xml
file does have the selected time zone, run the sysprep with generalize and
reboot and upon rebooting the OS should be set to the proper time zone.

Maybe you can clarify what you expect from sysprep.

With Best Regards.

Steven Rosenberg.

On Tue, Nov 10, 2020 at 10:43 AM  wrote:

> Hi,
> I've edited osconfig 00-defaults.properties  and sysprep.w10x64 files
> After sealed w10 by using "sysprep /generalize /oobe /shutdown" command
> i'm using run ones/initial boot/sysprep
> But windows passes the process and booted like a new machine.
> If i sysprep the template like ""sysprep /generalize /oobe /shutdown
> /unattend:D:\unattend.xml" and run the vm with sysprep option, it takes and
> applies only few options like create username not joindomain or productkey.
> Is there any proper guide to do sysprep on oVirt?
> By the way i've already red official guide
> Thanks for help
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/46DII2GF2GJ5JPHVKO5SNQNEQ2GZJZGC/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/T6X5MKLED6ZTKGDT74LOO547MZSI4WAK/


[ovirt-users] Re: oVirt 4.4.2 MS Windows 10 sysprep floppy

2020-11-09 Thread Steven Rosenberg
Hi,

We removed the floppy option and added an additional cd rom that contains
the Unattend.xml file. You can still use the Unattend.xml file from the
additional CD ROM in order to seal the OS via the sysprep tool.

The floppy drive was removed because it is outdated technology.

Thank you for your enquiry.

With Best Regards.

Steven Rosenberg.

On Mon, Nov 9, 2020 at 4:50 PM Sandro Bonazzola  wrote:

>
>
> Il giorno lun 9 nov 2020 alle ore 15:43  ha scritto:
>
>> Thanks for response,
>> I've rad this docs several times.
>>
>> If you check "7.9.1. Configuring Sysprep on a Template" it says "Attach
>> Floppy", but there is no Floppy options.
>>
>
> +Arik Hadas  , +Steve Goodman 
> can you please fix this?
>
>
>>
>> I've figured out something.
>> If i use only initial boot sysprep enable option, after booting there is
>> no change but i can see addtional cdrom device that has unattend.xml file
>>
>> ___
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@ovirt.org
>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/T4OQOOU277CKIXCQ2AGY2XX3HCRCJ3FY/
>>
>
>
> --
>
> Sandro Bonazzola
>
> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
>
> Red Hat EMEA <https://www.redhat.com/>
>
> sbona...@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.
> <https://mojo.redhat.com/docs/DOC-1199578>*
>
>
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/2XDTRF5ILEYJLQOHOCSV6B55A32UNNWD/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/3NL3EPIPN5AO52ZO2CAJMVPOXL3JORO7/


[ovirt-users] Re: How to use sysprep to create Windows templates

2020-07-07 Thread Steven Rosenberg
Dear Wodel Youchi,

Sorry for the delayed response. Answers below.



On Tue, Jul 7, 2020 at 4:17 PM wodel youchi  wrote:

> Hi,
>
> Could someone give me some help.
>
> Regards.
>
> Le mer. 1 juil. 2020 15:45, wodel youchi  a
> écrit :
>
>> Hi,
>>
>> I need to create some Windows Templates for my client, and I am not quite
>> familiar with the Windows sysprep installations.
>> I read the "Sealing a Windows Virtual Machine for Deployment as a
>> Template" on the Virtual Machine Management Guide.
>>
>> What I don't understand is the process of sealing a Windows VM.
>>
>> When should I use the /usr/share/ovirt-engine/conf/sysprep/sysprep.*
>> files? at the creation of the VM that will be a template at the end? or at
>> the creation of new VMs based on the template?
>>
>
Sealing the VM is used within the Windows Guest OS via this command:

'C:\Windows\System32\Sysprep\sysprep.exe /oobe /generalize /shutdown'

or

'C:\Windows\System32\sysprep\sysprep.exe' (then: Select 'Enter System
Out-of-Box-Experience (OOBE)' and check the 'Generalize' checkbox)

Once Windows restarts, you should see your configuration applied to the OS.




> When should I use the /etc/ovirt-engine/osinfo.conf.d/xx.files.properties?
>> at the creation of the VM that will be a template at the end? or at the
>> creation of new VMs based on the template?
>>
>
To change any of the properties you may need to.


>
>> What is the difference between : "Use Cloud-Init/Sysprep" in the VM edit
>> window and the RUN Once window?
>>
>
One needs to set the OS properly within the VM New / Edit functionality for
this to work. Then one can choose Cloud-Init/Sysprep and a configuration
such as to set the Time Zone.

If the Guest OS is Windows, then Sysprep is used, if Linux then Cloud Init
is used.


>
>> For me it is not clear, could someone help me to understand.
>>
>> Regards.
>>
>
I hope this helps.

With Best Regards

Steven Rosenberg.

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


[ovirt-users] Re: Overt-Engine Down | Host Unresponsive

2019-12-26 Thread Steven Rosenberg
Dear Vijay Sachdeva,

Thank you for your question. There could have been a communication issue
that prevented the engine from communicating with the Host and sometimes
restarting the engine fixes the issue.

The Hosts do continue to run their VMs whether the engine is connected or
not so to answer your question there should be no impact to the Host(s)
when the engine goes down.

With Best Regards.

Steven Rosenberg.

On Thu, Dec 26, 2019 at 11:01 AM Vijay Sachdeva 
wrote:

> Dear Team,
>
>
>
> I have one question, if Ovirt-engine goes down for some reason. Will it
> impact my host to go un-responsive and all VMs down?
>
>
>
> I just faced a situation where my host was in un-responsive status and all
> VMs were down. I restart the ovirt-engine service and host got activated.
>
>
>
> Can anyone let me know this situation?
>
>
>
> Thanks
>
>
>
> Vijay Sachdeva
>
>
> ___
> 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/HJ2RIVD5MU4ARAUX3FK75QLPKSBZKQH6/
>
___
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/POQUUI36F5SCDMJKYWORAUTYTX6AWOH5/


[ovirt-users] Re: AMD EPYC 4.3 upgrade 'CPU type is not supported in this cluster compatibility version or is not supported at all'

2019-02-17 Thread Steven Rosenberg
Dear Ryan Bullock,

Thank you for help with this issue. I will correlate accordingly.

With Best Regards.

Steven Rosenberg.

On Mon, Feb 18, 2019 at 5:46 AM Ryan Bullock  wrote:

> Hey Steven,
>
> Including just the cpuFlags, since the output is pretty verbose. Let me
> know if you need anything else from the output.
>
> Without avic=1 (Works Fine):
> "cpuFlags":
> "fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,mmx,fxsr,sse,sse2,ht,syscall,nx,mmxext,fxsr_opt,pdpe1gb,rdtscp,lm,constant_tsc,art,rep_good,nopl,nonstop_tsc,extd_apicid,amd_dcm,aperfmperf,eagerfpu,pni,pclmulqdq,monitor,ssse3,fma,cx16,sse4_1,sse4_2,movbe,popcnt,aes,xsave,avx,f16c,rdrand,lahf_lm,cmp_legacy,svm,extapic,cr8_legacy,abm,sse4a,misalignsse,3dnowprefetch,osvw,skinit,wdt,tce,topoext,perfctr_core,perfctr_nb,bpext,perfctr_l2,cpb,hw_pstate,sme,retpoline_amd,ssbd,ibpb,vmmcall,fsgsbase,bmi1,avx2,smep,bmi2,rdseed,adx,smap,clflushopt,sha_ni,xsaveopt,xsavec,xgetbv1,clzero,irperf,xsaveerptr,arat,npt,lbrv,svm_lock,nrip_save,tsc_scale,vmcb_clean,flushbyasid,decodeassists,pausefilter,pfthreshold,avic,v_vmsave_vmload,vgif,overflow_recov,succor,smca,model_Opteron_G3,model_Opteron_G2,model_kvm32,model_kvm64,model_Westmere,model_Nehalem,model_Conroe,model_EPYC-IBPB,model_Opteron_G1,model_SandyBridge,model_qemu32,model_Penryn,model_pentium2,model_486,model_qemu64,model_cpu64-rhel6,model_EPYC,model_pentium,model_pentium3"
>
> With avic=1 (Problem Configuration):
> "cpuFlags":
> "fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,mmx,fxsr,sse,sse2,ht,syscall,nx,mmxext,fxsr_opt,pdpe1gb,rdtscp,lm,constant_tsc,art,rep_good,nopl,nonstop_tsc,extd_apicid,amd_dcm,aperfmperf,eagerfpu,pni,pclmulqdq,monitor,ssse3,fma,cx16,sse4_1,sse4_2,movbe,popcnt,aes,xsave,avx,f16c,rdrand,lahf_lm,cmp_legacy,svm,extapic,cr8_legacy,abm,sse4a,misalignsse,3dnowprefetch,osvw,skinit,wdt,tce,topoext,perfctr_core,perfctr_nb,bpext,perfctr_l2,cpb,hw_pstate,sme,retpoline_amd,ssbd,ibpb,vmmcall,fsgsbase,bmi1,avx2,smep,bmi2,rdseed,adx,smap,clflushopt,sha_ni,xsaveopt,xsavec,xgetbv1,clzero,irperf,xsaveerptr,arat,npt,lbrv,svm_lock,nrip_save,tsc_scale,vmcb_clean,flushbyasid,decodeassists,pausefilter,pfthreshold,avic,v_vmsave_vmload,vgif,overflow_recov,succor,smca"
>
> Flags stay the same, but with avic=1 no models are shown as supported.
> Also, I opened this bug
> https://bugzilla.redhat.com/show_bug.cgi?id=1675030 regarding the avic=1
> setting seemingly requiring the x2apic flag.
>
> -Ryan
>
> On Sun, Feb 17, 2019 at 5:22 AM Steven Rosenberg 
> wrote:
>
>> Dear Ryan Bullock,
>>
>> I am currently looking at this issue:
>>
>>
>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/4Y4X7UGDEYSB5JK45TLDERNM7IMTHIYY/
>>
>> We would like more information concerning the CPU Flags (even though you
>> included them in your engine log dump above).
>>
>> Could you run the following command on the same host running: AMD
>> EPYC-IBPB
>>
>> vdsm-client Host getCapabilities
>>
>> Please send me the output, especially the CPU Flags.
>>
>> Thank you in advance for your help.
>>
>> With Best Regards.
>>
>> Steven Rosenberg.
>>
>>
>>
>> On Thu, Feb 7, 2019 at 6:35 PM Ryan Bullock  wrote:
>>
>>> That would explain it.
>>>
>>> Would removing the host and then reinstalling it under a new 4.3 cluster
>>> work without having to set the entire old cluster into maintenance to
>>> change the cpu? Then I could just restart VM's into the new cluster as we
>>> transition to minimize downtime.
>>>
>>> Thanks for the info!
>>>
>>> Ryan
>>>
>>> On Thu, Feb 7, 2019 at 7:56 AM Greg Sheremeta 
>>> wrote:
>>>
>>>> AMD EPYC IBPB is deprecated in 4.3.
>>>> The deprecated CPUs (cpus variable, that entire list) are:
>>>>
>>>> https://gerrit.ovirt.org/#/c/95310/7/frontend/webadmin/modules/webadmin/src/main/java/org/ovirt/engine/ui/webadmin/widget/table/column/ClusterAdditionalStatusColumn.java
>>>>
>>>> So, *-IBRS [IBRS-SSBD is still ok], Epyc IBPB, Conroe, Penryn, and
>>>> Opteron G1-3. If you have those, you need to change it to a supported type
>>>> while it's in 4.2 still.
>>>>
>>>> Greg
>>>>
>>>> On Thu, Feb 7, 2019 at 1:11 AM Ryan Bullock  wrote:
>>>>
>>>>> We just updated our engine to 4.3, but when I tried to update one of
>>>>> our AMD EPYC hosts it could not activate with the error:
>>>>>
>>>>> Host vmc2h2 moved to Non-Operational state as host CPU t

[ovirt-users] Re: AMD EPYC 4.3 upgrade 'CPU type is not supported in this cluster compatibility version or is not supported at all'

2019-02-17 Thread Steven Rosenberg
Dear Ryan Bullock,

I am currently looking at this issue:

https://lists.ovirt.org/archives/list/users@ovirt.org/message/4Y4X7UGDEYSB5JK45TLDERNM7IMTHIYY/

We would like more information concerning the CPU Flags (even though you
included them in your engine log dump above).

Could you run the following command on the same host running: AMD EPYC-IBPB

vdsm-client Host getCapabilities

Please send me the output, especially the CPU Flags.

Thank you in advance for your help.

With Best Regards.

Steven Rosenberg.



On Thu, Feb 7, 2019 at 6:35 PM Ryan Bullock  wrote:

> That would explain it.
>
> Would removing the host and then reinstalling it under a new 4.3 cluster
> work without having to set the entire old cluster into maintenance to
> change the cpu? Then I could just restart VM's into the new cluster as we
> transition to minimize downtime.
>
> Thanks for the info!
>
> Ryan
>
> On Thu, Feb 7, 2019 at 7:56 AM Greg Sheremeta  wrote:
>
>> AMD EPYC IBPB is deprecated in 4.3.
>> The deprecated CPUs (cpus variable, that entire list) are:
>>
>> https://gerrit.ovirt.org/#/c/95310/7/frontend/webadmin/modules/webadmin/src/main/java/org/ovirt/engine/ui/webadmin/widget/table/column/ClusterAdditionalStatusColumn.java
>>
>> So, *-IBRS [IBRS-SSBD is still ok], Epyc IBPB, Conroe, Penryn, and
>> Opteron G1-3. If you have those, you need to change it to a supported type
>> while it's in 4.2 still.
>>
>> Greg
>>
>> On Thu, Feb 7, 2019 at 1:11 AM Ryan Bullock  wrote:
>>
>>> We just updated our engine to 4.3, but when I tried to update one of our
>>> AMD EPYC hosts it could not activate with the error:
>>>
>>> Host vmc2h2 moved to Non-Operational state as host CPU type is not
>>> supported in this cluster compatibility version or is not supported at all.
>>>
>>> Relevant (I think) parts from the the engine log:
>>>
>>> (EE-ManagedThreadFactory-engineScheduled-Thread-82) [ee51a70] Could not
>>> find server cpu for server 'vmc2h2' (745a14c6-9d31-48a4-9566-914647d83f53),
>>> flags:
>>> 'fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,mmx,fxsr,sse,sse2,ht,syscall,nx,mmxext,fxsr_opt,pdpe1gb,rdtscp,lm,constant_tsc,art,rep_good,nopl,nonstop_tsc,extd_apicid,amd_dcm,aperfmperf,eagerfpu,pni,pclmulqdq,monitor,ssse3,fma,cx16,sse4_1,sse4_2,movbe,popcnt,aes,xsave,avx,f16c,rdrand,lahf_lm,cmp_legacy,svm,extapic,cr8_legacy,abm,sse4a,misalignsse,3dnowprefetch,osvw,skinit,wdt,tce,topoext,perfctr_core,perfctr_nb,bpext,perfctr_l2,cpb,hw_pstate,sme,retpoline_amd,ssbd,ibpb,vmmcall,fsgsbase,bmi1,avx2,smep,bmi2,rdseed,adx,smap,clflushopt,sha_ni,xsaveopt,xsavec,xgetbv1,clzero,irperf,xsaveerptr,arat,npt,lbrv,svm_lock,nrip_save,tsc_scale,vmcb_clean,flushbyasid,decodeassists,pausefilter,pfthreshold,avic,v_vmsave_vmload,vgif,overflow_recov,succor,smca'
>>> 2019-02-06 17:23:58,527-08 INFO
>>> [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand]
>>> (EE-ManagedThreadFactory-engineScheduled-Thread-82) [7f6d4f0d] START,
>>> SetVdsStatusVDSCommand(HostName = vmc2h2,
>>> SetVdsStatusVDSCommandParameters:{hostId='745a14c6-9d31-48a4-9566-914647d83f53',
>>> status='NonOperational',
>>> nonOperationalReason='CPU_TYPE_INCOMPATIBLE_WITH_CLUSTER'
>>>
>>>
>>> From virsh -r capabilities:
>>>
>>> 
>>>   x86_64
>>>   EPYC-IBPB
>>>   AMD
>>>   
>>>   
>>>   
>>>   
>>>   
>>>   
>>>   
>>>   
>>>   
>>>   
>>>   
>>>   
>>>   
>>>   
>>>   
>>>   
>>>   
>>> 
>>>
>>> I also tried creating a new 4.3 cluster, set to the AMD EPYC IPBDB SSBD
>>> and moving the host into it, but it failed to move it into that cluster
>>> with a similar error about an unsupported CPU (for some reason it also made
>>> me clear the additional kernel options as well, we use 1gb hugepages). I
>>> have not yet tried removing the host entirely and adding it as part of
>>> creating the new cluster.
>>>
>>> We have been/are using a database change to update the 4.2 cluster level
>>> to include EPYC support with the following entries (can post the whole
>>> query if needed):
>>> 7:AMD EPYC:svm,nx,model_EPYC:EPYC:x86_64; 8:AMD EPYC
>>> IBPB:svm,nx,ibpb,model_EPYC:EPYC-IBPB:x86_64
>>>
>>> We have been running 4.2 with this for awhile. We did apply the same
>>> changes after the 4.3 update, but only for the 4.2 cluster l