[ovirt-users] Ovirt Host Crashed

2020-09-02 Thread Darin Schmidt
I am running this as an all in one system for a test bed at home. The system 
crashed which lead me to have to reinstall the OS (CentOS 8) and I imported the 
data stores but I cannot find any way to import the VM's that were in the DATA 
store. I havent had a chance to backup/export the VMs. I havent been able to 
find anything in the documentation on how to import these VMs. Any suggestions 
or links to what Im looking for?

I had to create a new DATA store as the option for importing a local data store 
wasnt an option, I assume its because the host was down. THen I imported the 
old data store.
___
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/JLXAUHGSTLL45A4TLLJT3JL4TEINJLZR/


[ovirt-users] USB turns off and wont come alive

2019-07-23 Thread Darin Schmidt
I have 2 usb controllers installed via a riser card plugged into a M.2 slot. 
(Like those used for mining with GPU's). Everything works great for a long 
time, then my Windows 10 VM freezes and I lose all USB activity. LSPCI still 
sees the devices:

0a:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller
0b:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller
43:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller
44:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller

I assume a and b are the same physical card as its supposed to have 2 channels 
each, same with 44 and 43.

I tried for both 44 and 43

echo "1" > /sys/bus/pci/devices/\:43\:00.0/remove
echo "1" > /sys/bus/pci/rescan
echo "1" > /sys/bus/pci/devices/\:43\:00.0/reset

This did not work. I cannot determine if its just the VM thats no longer 
seeing/using the hardware or if its the hardware itself. I wonder if its a 
power state thing as well? Nothing I plug into the card seems to be recognized. 
Any Suggestions? rebooting the VM doesnt help either. It appears the hardware 
is functioning, but anything you plug into it isnt being detected.
___
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/4ST2T3NEL3EP54ZWR5KF5RW4VHUCVFN6/


[ovirt-users] Re: vender_id syntax UserDefinedVMProperties

2019-03-20 Thread Darin Schmidt
I was hoping someone would know how to because I don't know python

On Wed, Mar 20, 2019, 12:52 AM Strahil  wrote:

> Can't you make the script check if it windows or Linux and skip if it's
> Linux?
>
> Best Regards,
> Strahil Nikolov
> On Mar 19, 2019 23:02, Darin Schmidt  wrote:
>
> You also need to have this code hooked in:
> cd /usr/libexec/vdsm/hooks/before_vm_start/
> vi 99_mask_kvm
>
> #!/usr/bin/python2
>
> import hooking
> domxml = hooking.read_domxml()
>
> hyperv = domxml.getElementsByTagName('hyperv')[0]
> smm = domxml.createElement('vendor_id')
> smm.setAttribute('state', 'on')
> smm.setAttribute('value', '1234567890ab')
> hyperv.appendChild(smm)
>
> features = domxml.getElementsByTagName('features')[0]
> kvm = domxml.createElement('kvm')
> hidden = domxml.createElement('hidden')
> hidden.setAttribute('state', 'on')
> kvm.appendChild(hidden)
> features.appendChild(kvm)
>
> hooking.write_domxml(domxml)
>
>
> only problem now is that I cant boot a linux VM with the vendor_is portion
> there..
>
> On Mon, Mar 18, 2019 at 3:30 PM Darin Schmidt 
> wrote:
>
> Seems that the system has to be running with bios Q35 UEFI. Standard bios
> does not work. System is operational now.
>
> On Mon, Mar 18, 2019, 6:30 AM Darin Schmidt 
> wrote:
>
> Still no luck getting the gtx 1080 to enable inside the VM. I see the code
> is being generated in the xml with the hook. But I still get error code 43.
> Someone mentioned doing it with eufi bios and that worked for them. So when
> I get back from work today, perhaps ill give that a try.
>
> On Mon, Mar 18, 2019, 6:10 AM Darin Schmidt 
> wrote:
>
> I have gotten the system to see the card, its in device manager. The
> problem seems to be that I cannot use it in the VM because from what I have
> been finding out is that it gets and error code 43. Nvidia drivers disable
> the card if it detects that its being used in a VM. I have found some code
> to use to hook it into the xml before_vm_starts.
>
> 99_mask_kvm
> #!/usr/bin/python2
>
> import hooking
> domxml = hooking.read_domxml()
>
> hyperv = domxml.getElementsByTagName('hyperv')[0]
> smm = domxml.createElement('vendor_id')
> smm.setAttribute('state', 'on')
> smm.setAttribute('value', '1234567890ab')
> hyperv.appendChild(smm)
>
> features = domxml.getElementsByTagName('features')[0]
> kvm = domxml.createElement('kvm')
> hidden = domxml.createElement('hidden')
> hidden.setAttribute('state', 'on')
> kvm.appendChild(hidden)
> features.appendChild(kvm)
>
> hooking.write_domxml(domxml)
>
>
> I am currently reinstalling the drivers to see if this helps.
>
> kvm off and vender_id is now in the xml code that get generated when the
> VM is started. Im going off of examples Im finding online. Perhaps I just
> need to add the 10de to it instead of some generic # others are using.
>
> On Mon, Mar 18, 2019 at 6:02 AM Nisim Simsolo  wrote:
>
> Hi
>
> Vendor ID of Nvidia is usually 10de.
> You can locate 'vendor ID:
>
>
___
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/MHVEAMILIV66X3ORCO3G5OOZ5XZFZVG3/


[ovirt-users] Re: vender_id syntax UserDefinedVMProperties

2019-03-19 Thread Darin Schmidt
You also need to have this code hooked in:
cd /usr/libexec/vdsm/hooks/before_vm_start/
vi 99_mask_kvm

#!/usr/bin/python2

import hooking
domxml = hooking.read_domxml()

hyperv = domxml.getElementsByTagName('hyperv')[0]
smm = domxml.createElement('vendor_id')
smm.setAttribute('state', 'on')
smm.setAttribute('value', '1234567890ab')
hyperv.appendChild(smm)

features = domxml.getElementsByTagName('features')[0]
kvm = domxml.createElement('kvm')
hidden = domxml.createElement('hidden')
hidden.setAttribute('state', 'on')
kvm.appendChild(hidden)
features.appendChild(kvm)

hooking.write_domxml(domxml)


only problem now is that I cant boot a linux VM with the vendor_is portion
there..

On Mon, Mar 18, 2019 at 3:30 PM Darin Schmidt 
wrote:

> Seems that the system has to be running with bios Q35 UEFI. Standard bios
> does not work. System is operational now.
>
> On Mon, Mar 18, 2019, 6:30 AM Darin Schmidt 
> wrote:
>
>> Still no luck getting the gtx 1080 to enable inside the VM. I see the
>> code is being generated in the xml with the hook. But I still get error
>> code 43. Someone mentioned doing it with eufi bios and that worked for
>> them. So when I get back from work today, perhaps ill give that a try.
>>
>> On Mon, Mar 18, 2019, 6:10 AM Darin Schmidt 
>> wrote:
>>
>>> I have gotten the system to see the card, its in device manager. The
>>> problem seems to be that I cannot use it in the VM because from what I have
>>> been finding out is that it gets and error code 43. Nvidia drivers disable
>>> the card if it detects that its being used in a VM. I have found some code
>>> to use to hook it into the xml before_vm_starts.
>>>
>>> 99_mask_kvm
>>> #!/usr/bin/python2
>>>
>>> import hooking
>>> domxml = hooking.read_domxml()
>>>
>>> hyperv = domxml.getElementsByTagName('hyperv')[0]
>>> smm = domxml.createElement('vendor_id')
>>> smm.setAttribute('state', 'on')
>>> smm.setAttribute('value', '1234567890ab')
>>> hyperv.appendChild(smm)
>>>
>>> features = domxml.getElementsByTagName('features')[0]
>>> kvm = domxml.createElement('kvm')
>>> hidden = domxml.createElement('hidden')
>>> hidden.setAttribute('state', 'on')
>>> kvm.appendChild(hidden)
>>> features.appendChild(kvm)
>>>
>>> hooking.write_domxml(domxml)
>>>
>>>
>>> I am currently reinstalling the drivers to see if this helps.
>>>
>>> kvm off and vender_id is now in the xml code that get generated when the
>>> VM is started. Im going off of examples Im finding online. Perhaps I just
>>> need to add the 10de to it instead of some generic # others are using.
>>>
>>> On Mon, Mar 18, 2019 at 6:02 AM Nisim Simsolo 
>>> wrote:
>>>
>>>> Hi
>>>>
>>>> Vendor ID of Nvidia is usually 10de.
>>>> You can locate 'vendor ID:product ID' by running lspci command, for
>>>> example:
>>>> [root@intel-vfio ~]# lspci -Dnn | grep -i nvidia
>>>> :03:00.0 VGA compatible controller [0300]: NVIDIA Corporation
>>>> GK104GL [Quadro K4200] [10de:11b4] (rev a1)
>>>> :03:00.1 Audio device [0403]: NVIDIA Corporation GK104 HDMI Audio
>>>> Controller [10de:0e0a] (rev a1)
>>>> [root@intel-vfio ~]#
>>>>
>>>> In this example, the vendor ID of VGA controller is 10de and the
>>>> product ID is 11b4
>>>>
>>>> Please bare in mind that you need to enable IOMMU, add pci-stub
>>>> (prevent the host driver for using GPU device) and disable the default
>>>> nouveau driver on the host Kernel command line.
>>>> to do that:
>>>> 1. Edit host /etc/sysconfig/grub and add the next to GRUB_CMDLINE_LINUX:
>>>>
>>>>- intel_iommu=on or amd_iommu=on
>>>>- pci-stub.ids=10de:11b4,10de:0e0a
>>>>- rdblacklist=nouveau
>>>>
>>>> 2. Regenerate the boot loader configuration using grub2-mkconfig
>>>> command:
>>>> # grub2-mkconfig -o /etc/grub2.cfg
>>>> 3. Reboot the host.
>>>> 4. Verify configuration:
>>>> [root@intel-vfio ~]# cat /proc/cmdline
>>>> BOOT_IMAGE=/vmlinuz-3.10.0-957.5.1.el7.x86_64
>>>> root=/dev/mapper/vg0-lv_root ro crashkernel=auto rd.lvm.lv=vg0/lv_root
>>>> rd.lvm.lv=vg0/lv_swap rhgb quiet pci-stub.ids=10de:11b4,10de:0e0a
>>>> intel_iommu=on rdblacklist=nouveau LANG=en_US.UTF-8
>>>> [root@intel-vfio ~]#
>>>>
>>>>
>>>> After ru

[ovirt-users] Re: vender_id syntax UserDefinedVMProperties

2019-03-18 Thread Darin Schmidt
Seems that the system has to be running with bios Q35 UEFI. Standard bios
does not work. System is operational now.

On Mon, Mar 18, 2019, 6:30 AM Darin Schmidt  wrote:

> Still no luck getting the gtx 1080 to enable inside the VM. I see the code
> is being generated in the xml with the hook. But I still get error code 43.
> Someone mentioned doing it with eufi bios and that worked for them. So when
> I get back from work today, perhaps ill give that a try.
>
> On Mon, Mar 18, 2019, 6:10 AM Darin Schmidt 
> wrote:
>
>> I have gotten the system to see the card, its in device manager. The
>> problem seems to be that I cannot use it in the VM because from what I have
>> been finding out is that it gets and error code 43. Nvidia drivers disable
>> the card if it detects that its being used in a VM. I have found some code
>> to use to hook it into the xml before_vm_starts.
>>
>> 99_mask_kvm
>> #!/usr/bin/python2
>>
>> import hooking
>> domxml = hooking.read_domxml()
>>
>> hyperv = domxml.getElementsByTagName('hyperv')[0]
>> smm = domxml.createElement('vendor_id')
>> smm.setAttribute('state', 'on')
>> smm.setAttribute('value', '1234567890ab')
>> hyperv.appendChild(smm)
>>
>> features = domxml.getElementsByTagName('features')[0]
>> kvm = domxml.createElement('kvm')
>> hidden = domxml.createElement('hidden')
>> hidden.setAttribute('state', 'on')
>> kvm.appendChild(hidden)
>> features.appendChild(kvm)
>>
>> hooking.write_domxml(domxml)
>>
>>
>> I am currently reinstalling the drivers to see if this helps.
>>
>> kvm off and vender_id is now in the xml code that get generated when the
>> VM is started. Im going off of examples Im finding online. Perhaps I just
>> need to add the 10de to it instead of some generic # others are using.
>>
>> On Mon, Mar 18, 2019 at 6:02 AM Nisim Simsolo 
>> wrote:
>>
>>> Hi
>>>
>>> Vendor ID of Nvidia is usually 10de.
>>> You can locate 'vendor ID:product ID' by running lspci command, for
>>> example:
>>> [root@intel-vfio ~]# lspci -Dnn | grep -i nvidia
>>> :03:00.0 VGA compatible controller [0300]: NVIDIA Corporation
>>> GK104GL [Quadro K4200] [10de:11b4] (rev a1)
>>> :03:00.1 Audio device [0403]: NVIDIA Corporation GK104 HDMI Audio
>>> Controller [10de:0e0a] (rev a1)
>>> [root@intel-vfio ~]#
>>>
>>> In this example, the vendor ID of VGA controller is 10de and the product
>>> ID is 11b4
>>>
>>> Please bare in mind that you need to enable IOMMU, add pci-stub (prevent
>>> the host driver for using GPU device) and disable the default nouveau
>>> driver on the host Kernel command line.
>>> to do that:
>>> 1. Edit host /etc/sysconfig/grub and add the next to GRUB_CMDLINE_LINUX:
>>>
>>>- intel_iommu=on or amd_iommu=on
>>>- pci-stub.ids=10de:11b4,10de:0e0a
>>>- rdblacklist=nouveau
>>>
>>> 2. Regenerate the boot loader configuration using grub2-mkconfig command:
>>> # grub2-mkconfig -o /etc/grub2.cfg
>>> 3. Reboot the host.
>>> 4. Verify configuration:
>>> [root@intel-vfio ~]# cat /proc/cmdline
>>> BOOT_IMAGE=/vmlinuz-3.10.0-957.5.1.el7.x86_64
>>> root=/dev/mapper/vg0-lv_root ro crashkernel=auto rd.lvm.lv=vg0/lv_root
>>> rd.lvm.lv=vg0/lv_swap rhgb quiet pci-stub.ids=10de:11b4,10de:0e0a
>>> intel_iommu=on rdblacklist=nouveau LANG=en_US.UTF-8
>>> [root@intel-vfio ~]#
>>>
>>>
>>> After running this, you should be able to passthrough GPU to VM.
>>>
>>> BTW, why are you using engine-config and not doing it from oVirt UI or
>>> using virsh edit command?
>>>
>>> Thanks
>>>
>>>
>>> On Mon, Mar 18, 2019 at 1:52 AM Darin Schmidt 
>>> wrote:
>>>
>>>> Hello all, im trying to figure out how to configure the custom
>>>> properties to enable my NVIDIA card to work in the VM. Its my understanding
>>>> that the drives dont work because it detects its in a VM..
>>>>
>>>> Im trying to do something like this:
>>>>
>>>> engine-config -s
>>>> UserDefinedVMProperties="kvmhidden=^(true|false)$;{type=vendor_id;state={^(on|off)$;value=^([0-9])$}}"
>>>>
>>>>
>>>> But thats clearly not working. If I do this:
>>>>
>>>> engine-config -s
>>>> UserDefinedVMProperties="kvmhidden=^(true|false)$;vendor_id={state=^(on|off)$;value=^([0-9])$}"
>>>>
>>>>
>>>> It works but, the options are messed up. Im not sure how to find out
>>>> the correct syntax to get this to work. Would appreciate any advice.
>>>>
>>>
>>>
>>> --
>>> Nisim Simsolo
>>> QE -Testing Engineer
>>> IRC: nsimsolo
>>> int phone - 8272305
>>> mobile - 054-4779934
>>>
>>
___
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/4UBAZ6DATBEYEISWT2N3LKXWESWA77NH/


[ovirt-users] Re: vender_id syntax UserDefinedVMProperties

2019-03-18 Thread Darin Schmidt
Still no luck getting the gtx 1080 to enable inside the VM. I see the code
is being generated in the xml with the hook. But I still get error code 43.
Someone mentioned doing it with eufi bios and that worked for them. So when
I get back from work today, perhaps ill give that a try.

On Mon, Mar 18, 2019, 6:10 AM Darin Schmidt  wrote:

> I have gotten the system to see the card, its in device manager. The
> problem seems to be that I cannot use it in the VM because from what I have
> been finding out is that it gets and error code 43. Nvidia drivers disable
> the card if it detects that its being used in a VM. I have found some code
> to use to hook it into the xml before_vm_starts.
>
> 99_mask_kvm
> #!/usr/bin/python2
>
> import hooking
> domxml = hooking.read_domxml()
>
> hyperv = domxml.getElementsByTagName('hyperv')[0]
> smm = domxml.createElement('vendor_id')
> smm.setAttribute('state', 'on')
> smm.setAttribute('value', '1234567890ab')
> hyperv.appendChild(smm)
>
> features = domxml.getElementsByTagName('features')[0]
> kvm = domxml.createElement('kvm')
> hidden = domxml.createElement('hidden')
> hidden.setAttribute('state', 'on')
> kvm.appendChild(hidden)
> features.appendChild(kvm)
>
> hooking.write_domxml(domxml)
>
>
> I am currently reinstalling the drivers to see if this helps.
>
> kvm off and vender_id is now in the xml code that get generated when the
> VM is started. Im going off of examples Im finding online. Perhaps I just
> need to add the 10de to it instead of some generic # others are using.
>
> On Mon, Mar 18, 2019 at 6:02 AM Nisim Simsolo  wrote:
>
>> Hi
>>
>> Vendor ID of Nvidia is usually 10de.
>> You can locate 'vendor ID:product ID' by running lspci command, for
>> example:
>> [root@intel-vfio ~]# lspci -Dnn | grep -i nvidia
>> :03:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK104GL
>> [Quadro K4200] [10de:11b4] (rev a1)
>> :03:00.1 Audio device [0403]: NVIDIA Corporation GK104 HDMI Audio
>> Controller [10de:0e0a] (rev a1)
>> [root@intel-vfio ~]#
>>
>> In this example, the vendor ID of VGA controller is 10de and the product
>> ID is 11b4
>>
>> Please bare in mind that you need to enable IOMMU, add pci-stub (prevent
>> the host driver for using GPU device) and disable the default nouveau
>> driver on the host Kernel command line.
>> to do that:
>> 1. Edit host /etc/sysconfig/grub and add the next to GRUB_CMDLINE_LINUX:
>>
>>- intel_iommu=on or amd_iommu=on
>>- pci-stub.ids=10de:11b4,10de:0e0a
>>- rdblacklist=nouveau
>>
>> 2. Regenerate the boot loader configuration using grub2-mkconfig command:
>> # grub2-mkconfig -o /etc/grub2.cfg
>> 3. Reboot the host.
>> 4. Verify configuration:
>> [root@intel-vfio ~]# cat /proc/cmdline
>> BOOT_IMAGE=/vmlinuz-3.10.0-957.5.1.el7.x86_64
>> root=/dev/mapper/vg0-lv_root ro crashkernel=auto rd.lvm.lv=vg0/lv_root
>> rd.lvm.lv=vg0/lv_swap rhgb quiet pci-stub.ids=10de:11b4,10de:0e0a
>> intel_iommu=on rdblacklist=nouveau LANG=en_US.UTF-8
>> [root@intel-vfio ~]#
>>
>>
>> After running this, you should be able to passthrough GPU to VM.
>>
>> BTW, why are you using engine-config and not doing it from oVirt UI or
>> using virsh edit command?
>>
>> Thanks
>>
>>
>> On Mon, Mar 18, 2019 at 1:52 AM Darin Schmidt 
>> wrote:
>>
>>> Hello all, im trying to figure out how to configure the custom
>>> properties to enable my NVIDIA card to work in the VM. Its my understanding
>>> that the drives dont work because it detects its in a VM..
>>>
>>> Im trying to do something like this:
>>>
>>> engine-config -s
>>> UserDefinedVMProperties="kvmhidden=^(true|false)$;{type=vendor_id;state={^(on|off)$;value=^([0-9])$}}"
>>>
>>>
>>> But thats clearly not working. If I do this:
>>>
>>> engine-config -s
>>> UserDefinedVMProperties="kvmhidden=^(true|false)$;vendor_id={state=^(on|off)$;value=^([0-9])$}"
>>>
>>>
>>> It works but, the options are messed up. Im not sure how to find out the
>>> correct syntax to get this to work. Would appreciate any advice.
>>>
>>
>>
>> --
>> Nisim Simsolo
>> QE -Testing Engineer
>> IRC: nsimsolo
>> int phone - 8272305
>> mobile - 054-4779934
>>
>
___
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/F4RSJDPHOTCC7HW2BCNKAEMILB65W6DZ/


[ovirt-users] Re: vender_id syntax UserDefinedVMProperties

2019-03-18 Thread Darin Schmidt
I have gotten the system to see the card, its in device manager. The
problem seems to be that I cannot use it in the VM because from what I have
been finding out is that it gets and error code 43. Nvidia drivers disable
the card if it detects that its being used in a VM. I have found some code
to use to hook it into the xml before_vm_starts.

99_mask_kvm
#!/usr/bin/python2

import hooking
domxml = hooking.read_domxml()

hyperv = domxml.getElementsByTagName('hyperv')[0]
smm = domxml.createElement('vendor_id')
smm.setAttribute('state', 'on')
smm.setAttribute('value', '1234567890ab')
hyperv.appendChild(smm)

features = domxml.getElementsByTagName('features')[0]
kvm = domxml.createElement('kvm')
hidden = domxml.createElement('hidden')
hidden.setAttribute('state', 'on')
kvm.appendChild(hidden)
features.appendChild(kvm)

hooking.write_domxml(domxml)


I am currently reinstalling the drivers to see if this helps.

kvm off and vender_id is now in the xml code that get generated when the VM
is started. Im going off of examples Im finding online. Perhaps I just need
to add the 10de to it instead of some generic # others are using.

On Mon, Mar 18, 2019 at 6:02 AM Nisim Simsolo  wrote:

> Hi
>
> Vendor ID of Nvidia is usually 10de.
> You can locate 'vendor ID:product ID' by running lspci command, for
> example:
> [root@intel-vfio ~]# lspci -Dnn | grep -i nvidia
> :03:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK104GL
> [Quadro K4200] [10de:11b4] (rev a1)
> :03:00.1 Audio device [0403]: NVIDIA Corporation GK104 HDMI Audio
> Controller [10de:0e0a] (rev a1)
> [root@intel-vfio ~]#
>
> In this example, the vendor ID of VGA controller is 10de and the product
> ID is 11b4
>
> Please bare in mind that you need to enable IOMMU, add pci-stub (prevent
> the host driver for using GPU device) and disable the default nouveau
> driver on the host Kernel command line.
> to do that:
> 1. Edit host /etc/sysconfig/grub and add the next to GRUB_CMDLINE_LINUX:
>
>- intel_iommu=on or amd_iommu=on
>- pci-stub.ids=10de:11b4,10de:0e0a
>- rdblacklist=nouveau
>
> 2. Regenerate the boot loader configuration using grub2-mkconfig command:
> # grub2-mkconfig -o /etc/grub2.cfg
> 3. Reboot the host.
> 4. Verify configuration:
> [root@intel-vfio ~]# cat /proc/cmdline
> BOOT_IMAGE=/vmlinuz-3.10.0-957.5.1.el7.x86_64 root=/dev/mapper/vg0-lv_root
> ro crashkernel=auto rd.lvm.lv=vg0/lv_root rd.lvm.lv=vg0/lv_swap rhgb
> quiet pci-stub.ids=10de:11b4,10de:0e0a intel_iommu=on rdblacklist=nouveau
> LANG=en_US.UTF-8
> [root@intel-vfio ~]#
>
>
> After running this, you should be able to passthrough GPU to VM.
>
> BTW, why are you using engine-config and not doing it from oVirt UI or
> using virsh edit command?
>
> Thanks
>
>
> On Mon, Mar 18, 2019 at 1:52 AM Darin Schmidt 
> wrote:
>
>> Hello all, im trying to figure out how to configure the custom properties
>> to enable my NVIDIA card to work in the VM. Its my understanding that the
>> drives dont work because it detects its in a VM..
>>
>> Im trying to do something like this:
>>
>> engine-config -s
>> UserDefinedVMProperties="kvmhidden=^(true|false)$;{type=vendor_id;state={^(on|off)$;value=^([0-9])$}}"
>>
>>
>> But thats clearly not working. If I do this:
>>
>> engine-config -s
>> UserDefinedVMProperties="kvmhidden=^(true|false)$;vendor_id={state=^(on|off)$;value=^([0-9])$}"
>>
>>
>> It works but, the options are messed up. Im not sure how to find out the
>> correct syntax to get this to work. Would appreciate any advice.
>>
>
>
> --
> Nisim Simsolo
> QE -Testing Engineer
> IRC: nsimsolo
> int phone - 8272305
> mobile - 054-4779934
>
___
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/BNUKZSPXNJZSDKLX42EKTTPDOWRA362I/


[ovirt-users] vender_id syntax UserDefinedVMProperties

2019-03-17 Thread Darin Schmidt
Hello all, im trying to figure out how to configure the custom properties
to enable my NVIDIA card to work in the VM. Its my understanding that the
drives dont work because it detects its in a VM..

Im trying to do something like this:

engine-config -s
UserDefinedVMProperties="kvmhidden=^(true|false)$;{type=vendor_id;state={^(on|off)$;value=^([0-9])$}}"


But thats clearly not working. If I do this:

engine-config -s
UserDefinedVMProperties="kvmhidden=^(true|false)$;vendor_id={state=^(on|off)$;value=^([0-9])$}"


It works but, the options are messed up. Im not sure how to find out the
correct syntax to get this to work. Would appreciate any advice.
___
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/6HDKQJBHJ5KEBIPSDBI4ZVSTOZSKCIAB/


[ovirt-users] Re: GPU passthrough

2019-03-16 Thread Darin Schmidt
Im able to get the vm to see the GPU, its saying Error 43: Driver failed to
load

>From what Im finding out I should be able to edit the XML file and trick
the NVIDIA drivers into not knowing its a part of a VM.

First you have to setup the libvirt user:
saslpasswd2 -f /etc/libvirt/passwd.db -c root

then you edit the xml:
cd /etc/libvirt/qemu
virsh edit Win-A

Add kvm hidden state and such as shown here:
https://wiki.archlinux.org/index.php/PCI_passthrough_via_OVMF#Troubleshooting


Then I try to save it but then it complains about:

 Requested operation is not valid: domain has assigned non-USB host devices

This is as far as I have made it.


On Sat, Mar 16, 2019 at 12:43 PM Wesley Stewart  wrote:

> I actually use an oVirt VM as my desktop at home.  Why?  Because I can and
> I didn't want to have to buy another box for my desktop.  However there are
> a few caveats to this and some lessons I learned.
>
> The consumer grade GTX cards are going to have issues being passed
> through.  NVIDIA blocks this in their drivers and RedHat honors NVIDIA's
> requirements for this.  You can enter an agreement with NVIDIA, which I am
> sure costs some money somewhere, to get special drivers.  Or you can use
> their enterprise Quadro cards, however I tested a P2000 and could not get
> it to work on oVIrt.  But I did not try very hard.
>
> At home, I am using an AMD Radeon RX 480/580.  AMD doesn't care if you
> pass it through and it works almost right out of the box.  You just want to
> make sure to blacklist the AMD drivers for the host, and put them in the
> PCI-Stubs group.  It's really easy with some basic bash/terminal knowledge:
>
> https://ovirt.org/develop/release-management/features/virt/hostdev-passthrough.html
> Check the physical GPU portion.
>
> You can, HOWEVER, trick the VM into not thinking it's a VM in KVM and
> QEMU.  To prove this, I built a proxmox box at work to test it and I was
> able to successfully pass through a GTX 1060 without too much trouble.  I
> Have some notes here:
>
> https://docs.google.com/document/d/1vlOIbJ4iXE7ypdSJ0OWQZfgcG9dEx2_PxXh6oRjl878/edit?usp=sharing
> However these are pretty rough notes.  I just wanted to prove it could be
> done.
>
> For oVirt a lot of the QEMU/KVM settings and commands are going to be
> stored in databases and files.  and I had trouble getting these to pick up
> on the oVirt side.  I even tried creating a VDSM hook, as mentioned in this
> thread:
> https://lists.ovirt.org/pipermail/users/2017-March/080905.html
> But I never got it working.
>
> I am definitely no expert, but I have done a lot of tinkering with this.
> But you will get pushback from oVirt/Redhat as this is not officially
> supported.  If you want it to work with consumer grade cards, use AMD.  If
> you want to do it "right" you will have to buy the enterprise quadro
> cards.  But these get quite pricey.
>
> On Sat, Mar 16, 2019 at 12:15 PM Darin Schmidt 
> wrote:
>
>> If I'm reading through the documents correctly, you can't use consumer
>> grade gpus such as gtx 1080's and assign them to a VM?
>>
>> I'm trying to do something similar to how Linus used untaid to build
>> several gaming machines from one.
>>
>> Any help would be appreciated.
>>
>> 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/DJBX3NMFJRP3L5DRFMJAD7FWA3WAX4PM/
>>
>
___
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/ZRON32TALP7SXTISRFR5TYKIG3EGUAVN/


[ovirt-users] GPU passthrough

2019-03-16 Thread Darin Schmidt
If I'm reading through the documents correctly, you can't use consumer
grade gpus such as gtx 1080's and assign them to a VM?

I'm trying to do something similar to how Linus used untaid to build
several gaming machines from one.

Any help would be appreciated.

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


[ovirt-users] Re: Windows 10 - Ovirt 4.3 - EPYC

2019-03-09 Thread Darin Schmidt
This is what I'm experiencing.
https://bugzilla.redhat.com/show_bug.cgi?id=1592276

On Sat, Feb 2, 2019, 4:39 AM Dominik Holler  wrote:

> On Fri, 1 Feb 2019 17:37:30 -0500
> Darin Schmidt  wrote:
>
> > [root@ovirt ~]# rpm -qa kernel
> > kernel-3.10.0-957.1.3.el7.x86_64
> > kernel-3.10.0-862.el7.x86_64
> > [root@ovirt ~]# uname -a
> > Linux ovirt 3.10.0-957.1.3.el7.x86_64 #1 SMP Thu Nov 29 14:49:43 UTC 2018
>
> https://bugzilla.redhat.com/1638835 looks like there is at least
> kernel 3.10.0-957.3.1.el7.x86_64 required.
> Can you please check if upgrading to kernel solves the issue for you?
> I expectect at least kernel 3.10.0-957.5.1 to be availible.
>
> > x86_64 x86_64 x86_64 GNU/Linux
> > [root@ovirt ~]# rpm -qa qemu-kvm-ev
> > qemu-kvm-ev-2.12.0-18.el7_6.3.1.x86_64
> > [root@ovirt ~]# rpm -qa libvirt
> > libvirt-4.5.0-10.el7_6.3.x86_64
>
> > here is the vdsm
> >
>
> contains:
> Hyper-V SynIC is not supported by kernel
>
>
> > On Fri, Feb 1, 2019 at 3:05 PM Dominik Holler 
> > wrote:
> >
> > > On Fri, 1 Feb 2019 11:48:51 -0500
> > > Darin Schmidt  wrote:
> > >
> > > > I have successfully setup a centos vm, its up and running. Now I
> > > > need to setup a windows 10 VM and I cant seem to get anything to
> > > > work.
> > > >
> > > > Ive tried setting the OS type to other or Windows 10 64bit. With
> > > > Windows 64bit, it fails to startup at all When I select
> > > > OtherOS it will allow me to start to run the Windows ISO, but
> > > > then fails after a few seconds as well. Is there something I'm
> > > > not correctly configuring?
> > >
> > > Would you please share vdsm.log,  and the output of
> > > rpm -qa kernel
> > > uname -a
> > > rpm -qa qemu-kvm-ev
> > > rpm -qa libvirt
> > > from of the host, and the relevant part of engine.log?
> > >
>
>
___
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/QVR3TFBZ57FFIV2BWC52DUHVNBP2MDHW/


[ovirt-users] Re: Windows 10 - Ovirt 4.3 - EPYC

2019-02-15 Thread Darin Schmidt
If you watch this guy, I can get to where he is at 8:30 except I don't get
the activity circle, it failed before then.

On Fri, Feb 15, 2019, 9:12 PM Darin Schmidt   qemu-kvm: warning: CPU(s) not present in any NUMA nodes: CPU 4
> [socket-id: 4, core-id: 0, thread-id: 0], CPU 5 [socket
> -id: 5, core-id: 0, thread-id: 0], CPU 6 [socket-id: 6, core-id: 0,
> thread-id: 0], CPU 7 [socket-id: 7, core-id: 0, thread-id: 0], CPU 8
> [socket-i
> d: 8, core-id: 0, thread-id: 0], CPU 9 [socket-id: 9, core-id: 0,
> thread-id: 0], CPU 10 [socket-id: 10, core-id: 0, thread-id: 0], CPU 11
> [socket-
> id: 11, core-id: 0, thread-id: 0], CPU 12 [socket-id: 12, core-id: 0,
> thread-id: 0], CPU 13 [socket-id: 13, core-id: 0, thread-id: 0], CPU 14 [soc
> ket-id: 14, core-id: 0, thread-id: 0], CPU 15 [socket-id: 15, core-id: 0,
> thread-id: 0]
> 2019-02-16T01:45:22.366102Z qemu-kvm: warning: All CPU(s) up to maxcpus
> should be described in NUMA config, ability to start up with partial NUMA
> mappings is obsoleted and will be removed in future
>
>
> as far as I am aware, I have assigned this VM to NUMA 1 which has 12
> cores, 64GB ram
>
>
>
>
> On Fri, Feb 15, 2019 at 4:32 PM Darin Schmidt 
> wrote:
>
>> Sorry it took so long, but I got a hold of a windows 7 pro ISO and it
>> does the same thing. I get the same " Sytem Thread Exception Not Handled"
>> error after a few seconds of trying to boot up from the install iso.
>>
>> On Tue, Feb 5, 2019 at 8:06 AM Darin Schmidt 
>> wrote:
>>
>>> Currently I dont, but I can get my hands on one later today. I'll let
>>> you know how it goes. I dont think I'll have access to the system today
>>> though.
>>>
>>> On Tue, Feb 5, 2019 at 7:57 AM Nisim Simsolo 
>>> wrote:
>>>
>>>> Do you have any other Windows ISO (not necessarily Windows 10) to check
>>>> in order to see if it's not an issue with the ISO file?
>>>>
>>>>
>>>> On Tue, Feb 5, 2019 at 2:52 PM Darin Schmidt 
>>>> wrote:
>>>>
>>>>> I dont even get to that point. The VM seems to detect the windows.iso
>>>>> I downloaded from MS, the windows icon shows up, then it sits there for a
>>>>> while, then I get the error in the picture I attached complaining about a
>>>>> Sytem Thread Exception Not Handled. I dont make it to the install process
>>>>> for windows.
>>>>>
>>>>> On Tue, Feb 5, 2019 at 7:46 AM Nisim Simsolo 
>>>>> wrote:
>>>>>
>>>>>> Hi
>>>>>>
>>>>>> If it's not Hyper-V SynIC issue, then it might be related to the disk
>>>>>> interface.
>>>>>> By default, the disk interface is VirtIO and Windows cannot see this
>>>>>> interface until you intall VirtIO-Win disk driver.
>>>>>> In order to do that, make sure you have VirtIO-Win.ISO in the ISO
>>>>>> domain
>>>>>> and during the Windows installation, when it's asking for disk
>>>>>> location, change the VM CD to virtio-win.iso
>>>>>> Click on "browse drivers" in the Windows installation window and
>>>>>> install viostor from the ISO file.
>>>>>> after the driver is installed, change the VM CD back to the Windows
>>>>>> ISO -> refresh and continue the Windows installation.
>>>>>>
>>>>>> Please let me know if you still have issues.
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sat, Feb 2, 2019 at 5:22 PM Darin Schmidt 
>>>>>> wrote:
>>>>>>
>>>>>>> Thanks, that sort of helped. I've ran yum update a dozen times and
>>>>>>> not till this morning was there a kernel update... lol
>>>>>>>
>>>>>>> I'm able to startup the VM, but when it loads the ISO to install
>>>>>>> Windows 10 which I downloaded from Microsoft, Attached is what always
>>>>>>> happens. Perhaps my ISO is corrupt?
>>>>>>>
>>>>>>> On Sat, Feb 2, 2019 at 4:39 AM Dominik Holler 
>>>>>>> wrote:
>>>>>>>
>>>>>>>> On Fri, 1 Feb 2019 17:37:30 -0500
>>>>>>>> Darin Schmidt  wrote:
>>>>>>>>
>>>>>>>> > [root@ovirt ~]# rpm -qa kernel
>>>>>>>> > kernel-3.10.0-957.

[ovirt-users] Re: Windows 10 - Ovirt 4.3 - EPYC

2019-02-15 Thread Darin Schmidt
 qemu-kvm: warning: CPU(s) not present in any NUMA nodes: CPU 4 [socket-id:
4, core-id: 0, thread-id: 0], CPU 5 [socket
-id: 5, core-id: 0, thread-id: 0], CPU 6 [socket-id: 6, core-id: 0,
thread-id: 0], CPU 7 [socket-id: 7, core-id: 0, thread-id: 0], CPU 8
[socket-i
d: 8, core-id: 0, thread-id: 0], CPU 9 [socket-id: 9, core-id: 0,
thread-id: 0], CPU 10 [socket-id: 10, core-id: 0, thread-id: 0], CPU 11
[socket-
id: 11, core-id: 0, thread-id: 0], CPU 12 [socket-id: 12, core-id: 0,
thread-id: 0], CPU 13 [socket-id: 13, core-id: 0, thread-id: 0], CPU 14 [soc
ket-id: 14, core-id: 0, thread-id: 0], CPU 15 [socket-id: 15, core-id: 0,
thread-id: 0]
2019-02-16T01:45:22.366102Z qemu-kvm: warning: All CPU(s) up to maxcpus
should be described in NUMA config, ability to start up with partial NUMA
mappings is obsoleted and will be removed in future


as far as I am aware, I have assigned this VM to NUMA 1 which has 12 cores,
64GB ram




On Fri, Feb 15, 2019 at 4:32 PM Darin Schmidt 
wrote:

> Sorry it took so long, but I got a hold of a windows 7 pro ISO and it does
> the same thing. I get the same " Sytem Thread Exception Not Handled" error
> after a few seconds of trying to boot up from the install iso.
>
> On Tue, Feb 5, 2019 at 8:06 AM Darin Schmidt 
> wrote:
>
>> Currently I dont, but I can get my hands on one later today. I'll let you
>> know how it goes. I dont think I'll have access to the system today though.
>>
>> On Tue, Feb 5, 2019 at 7:57 AM Nisim Simsolo  wrote:
>>
>>> Do you have any other Windows ISO (not necessarily Windows 10) to check
>>> in order to see if it's not an issue with the ISO file?
>>>
>>>
>>> On Tue, Feb 5, 2019 at 2:52 PM Darin Schmidt 
>>> wrote:
>>>
>>>> I dont even get to that point. The VM seems to detect the windows.iso I
>>>> downloaded from MS, the windows icon shows up, then it sits there for a
>>>> while, then I get the error in the picture I attached complaining about a
>>>> Sytem Thread Exception Not Handled. I dont make it to the install process
>>>> for windows.
>>>>
>>>> On Tue, Feb 5, 2019 at 7:46 AM Nisim Simsolo 
>>>> wrote:
>>>>
>>>>> Hi
>>>>>
>>>>> If it's not Hyper-V SynIC issue, then it might be related to the disk
>>>>> interface.
>>>>> By default, the disk interface is VirtIO and Windows cannot see this
>>>>> interface until you intall VirtIO-Win disk driver.
>>>>> In order to do that, make sure you have VirtIO-Win.ISO in the ISO
>>>>> domain
>>>>> and during the Windows installation, when it's asking for disk
>>>>> location, change the VM CD to virtio-win.iso
>>>>> Click on "browse drivers" in the Windows installation window and
>>>>> install viostor from the ISO file.
>>>>> after the driver is installed, change the VM CD back to the Windows
>>>>> ISO -> refresh and continue the Windows installation.
>>>>>
>>>>> Please let me know if you still have issues.
>>>>>
>>>>> Thanks
>>>>>
>>>>>
>>>>>
>>>>> On Sat, Feb 2, 2019 at 5:22 PM Darin Schmidt 
>>>>> wrote:
>>>>>
>>>>>> Thanks, that sort of helped. I've ran yum update a dozen times and
>>>>>> not till this morning was there a kernel update... lol
>>>>>>
>>>>>> I'm able to startup the VM, but when it loads the ISO to install
>>>>>> Windows 10 which I downloaded from Microsoft, Attached is what always
>>>>>> happens. Perhaps my ISO is corrupt?
>>>>>>
>>>>>> On Sat, Feb 2, 2019 at 4:39 AM Dominik Holler 
>>>>>> wrote:
>>>>>>
>>>>>>> On Fri, 1 Feb 2019 17:37:30 -0500
>>>>>>> Darin Schmidt  wrote:
>>>>>>>
>>>>>>> > [root@ovirt ~]# rpm -qa kernel
>>>>>>> > kernel-3.10.0-957.1.3.el7.x86_64
>>>>>>> > kernel-3.10.0-862.el7.x86_64
>>>>>>> > [root@ovirt ~]# uname -a
>>>>>>> > Linux ovirt 3.10.0-957.1.3.el7.x86_64 #1 SMP Thu Nov 29 14:49:43
>>>>>>> UTC 2018
>>>>>>>
>>>>>>> https://bugzilla.redhat.com/1638835 looks like there is at least
>>>>>>> kernel 3.10.0-957.3.1.el7.x86_64 required.
>>>>>>> Can you please check if upgrading to kernel solves the issue for you?
>

[ovirt-users] Re: Windows 10 - Ovirt 4.3 - EPYC

2019-02-15 Thread Darin Schmidt
Sorry it took so long, but I got a hold of a windows 7 pro ISO and it does
the same thing. I get the same " Sytem Thread Exception Not Handled" error
after a few seconds of trying to boot up from the install iso.

On Tue, Feb 5, 2019 at 8:06 AM Darin Schmidt  wrote:

> Currently I dont, but I can get my hands on one later today. I'll let you
> know how it goes. I dont think I'll have access to the system today though.
>
> On Tue, Feb 5, 2019 at 7:57 AM Nisim Simsolo  wrote:
>
>> Do you have any other Windows ISO (not necessarily Windows 10) to check
>> in order to see if it's not an issue with the ISO file?
>>
>>
>> On Tue, Feb 5, 2019 at 2:52 PM Darin Schmidt 
>> wrote:
>>
>>> I dont even get to that point. The VM seems to detect the windows.iso I
>>> downloaded from MS, the windows icon shows up, then it sits there for a
>>> while, then I get the error in the picture I attached complaining about a
>>> Sytem Thread Exception Not Handled. I dont make it to the install process
>>> for windows.
>>>
>>> On Tue, Feb 5, 2019 at 7:46 AM Nisim Simsolo 
>>> wrote:
>>>
>>>> Hi
>>>>
>>>> If it's not Hyper-V SynIC issue, then it might be related to the disk
>>>> interface.
>>>> By default, the disk interface is VirtIO and Windows cannot see this
>>>> interface until you intall VirtIO-Win disk driver.
>>>> In order to do that, make sure you have VirtIO-Win.ISO in the ISO domain
>>>> and during the Windows installation, when it's asking for disk
>>>> location, change the VM CD to virtio-win.iso
>>>> Click on "browse drivers" in the Windows installation window and
>>>> install viostor from the ISO file.
>>>> after the driver is installed, change the VM CD back to the Windows ISO
>>>> -> refresh and continue the Windows installation.
>>>>
>>>> Please let me know if you still have issues.
>>>>
>>>> Thanks
>>>>
>>>>
>>>>
>>>> On Sat, Feb 2, 2019 at 5:22 PM Darin Schmidt 
>>>> wrote:
>>>>
>>>>> Thanks, that sort of helped. I've ran yum update a dozen times and not
>>>>> till this morning was there a kernel update... lol
>>>>>
>>>>> I'm able to startup the VM, but when it loads the ISO to install
>>>>> Windows 10 which I downloaded from Microsoft, Attached is what always
>>>>> happens. Perhaps my ISO is corrupt?
>>>>>
>>>>> On Sat, Feb 2, 2019 at 4:39 AM Dominik Holler 
>>>>> wrote:
>>>>>
>>>>>> On Fri, 1 Feb 2019 17:37:30 -0500
>>>>>> Darin Schmidt  wrote:
>>>>>>
>>>>>> > [root@ovirt ~]# rpm -qa kernel
>>>>>> > kernel-3.10.0-957.1.3.el7.x86_64
>>>>>> > kernel-3.10.0-862.el7.x86_64
>>>>>> > [root@ovirt ~]# uname -a
>>>>>> > Linux ovirt 3.10.0-957.1.3.el7.x86_64 #1 SMP Thu Nov 29 14:49:43
>>>>>> UTC 2018
>>>>>>
>>>>>> https://bugzilla.redhat.com/1638835 looks like there is at least
>>>>>> kernel 3.10.0-957.3.1.el7.x86_64 required.
>>>>>> Can you please check if upgrading to kernel solves the issue for you?
>>>>>> I expectect at least kernel 3.10.0-957.5.1 to be availible.
>>>>>>
>>>>>> > x86_64 x86_64 x86_64 GNU/Linux
>>>>>> > [root@ovirt ~]# rpm -qa qemu-kvm-ev
>>>>>> > qemu-kvm-ev-2.12.0-18.el7_6.3.1.x86_64
>>>>>> > [root@ovirt ~]# rpm -qa libvirt
>>>>>> > libvirt-4.5.0-10.el7_6.3.x86_64
>>>>>>
>>>>>> > here is the vdsm
>>>>>> >
>>>>>>
>>>>>> contains:
>>>>>> Hyper-V SynIC is not supported by kernel
>>>>>>
>>>>>>
>>>>>> > On Fri, Feb 1, 2019 at 3:05 PM Dominik Holler 
>>>>>> > wrote:
>>>>>> >
>>>>>> > > On Fri, 1 Feb 2019 11:48:51 -0500
>>>>>> > > Darin Schmidt  wrote:
>>>>>> > >
>>>>>> > > > I have successfully setup a centos vm, its up and running. Now I
>>>>>> > > > need to setup a windows 10 VM and I cant seem to get anything to
>>>>>> > > > work.
>>>>>> > > >
>>>

[ovirt-users] Re: Windows 10 - Ovirt 4.3 - EPYC

2019-02-05 Thread Darin Schmidt
Currently I dont, but I can get my hands on one later today. I'll let you
know how it goes. I dont think I'll have access to the system today though.

On Tue, Feb 5, 2019 at 7:57 AM Nisim Simsolo  wrote:

> Do you have any other Windows ISO (not necessarily Windows 10) to check in
> order to see if it's not an issue with the ISO file?
>
>
> On Tue, Feb 5, 2019 at 2:52 PM Darin Schmidt 
> wrote:
>
>> I dont even get to that point. The VM seems to detect the windows.iso I
>> downloaded from MS, the windows icon shows up, then it sits there for a
>> while, then I get the error in the picture I attached complaining about a
>> Sytem Thread Exception Not Handled. I dont make it to the install process
>> for windows.
>>
>> On Tue, Feb 5, 2019 at 7:46 AM Nisim Simsolo  wrote:
>>
>>> Hi
>>>
>>> If it's not Hyper-V SynIC issue, then it might be related to the disk
>>> interface.
>>> By default, the disk interface is VirtIO and Windows cannot see this
>>> interface until you intall VirtIO-Win disk driver.
>>> In order to do that, make sure you have VirtIO-Win.ISO in the ISO domain
>>> and during the Windows installation, when it's asking for disk location,
>>> change the VM CD to virtio-win.iso
>>> Click on "browse drivers" in the Windows installation window and install
>>> viostor from the ISO file.
>>> after the driver is installed, change the VM CD back to the Windows ISO
>>> -> refresh and continue the Windows installation.
>>>
>>> Please let me know if you still have issues.
>>>
>>> Thanks
>>>
>>>
>>>
>>> On Sat, Feb 2, 2019 at 5:22 PM Darin Schmidt 
>>> wrote:
>>>
>>>> Thanks, that sort of helped. I've ran yum update a dozen times and not
>>>> till this morning was there a kernel update... lol
>>>>
>>>> I'm able to startup the VM, but when it loads the ISO to install
>>>> Windows 10 which I downloaded from Microsoft, Attached is what always
>>>> happens. Perhaps my ISO is corrupt?
>>>>
>>>> On Sat, Feb 2, 2019 at 4:39 AM Dominik Holler 
>>>> wrote:
>>>>
>>>>> On Fri, 1 Feb 2019 17:37:30 -0500
>>>>> Darin Schmidt  wrote:
>>>>>
>>>>> > [root@ovirt ~]# rpm -qa kernel
>>>>> > kernel-3.10.0-957.1.3.el7.x86_64
>>>>> > kernel-3.10.0-862.el7.x86_64
>>>>> > [root@ovirt ~]# uname -a
>>>>> > Linux ovirt 3.10.0-957.1.3.el7.x86_64 #1 SMP Thu Nov 29 14:49:43 UTC
>>>>> 2018
>>>>>
>>>>> https://bugzilla.redhat.com/1638835 looks like there is at least
>>>>> kernel 3.10.0-957.3.1.el7.x86_64 required.
>>>>> Can you please check if upgrading to kernel solves the issue for you?
>>>>> I expectect at least kernel 3.10.0-957.5.1 to be availible.
>>>>>
>>>>> > x86_64 x86_64 x86_64 GNU/Linux
>>>>> > [root@ovirt ~]# rpm -qa qemu-kvm-ev
>>>>> > qemu-kvm-ev-2.12.0-18.el7_6.3.1.x86_64
>>>>> > [root@ovirt ~]# rpm -qa libvirt
>>>>> > libvirt-4.5.0-10.el7_6.3.x86_64
>>>>>
>>>>> > here is the vdsm
>>>>> >
>>>>>
>>>>> contains:
>>>>> Hyper-V SynIC is not supported by kernel
>>>>>
>>>>>
>>>>> > On Fri, Feb 1, 2019 at 3:05 PM Dominik Holler 
>>>>> > wrote:
>>>>> >
>>>>> > > On Fri, 1 Feb 2019 11:48:51 -0500
>>>>> > > Darin Schmidt  wrote:
>>>>> > >
>>>>> > > > I have successfully setup a centos vm, its up and running. Now I
>>>>> > > > need to setup a windows 10 VM and I cant seem to get anything to
>>>>> > > > work.
>>>>> > > >
>>>>> > > > Ive tried setting the OS type to other or Windows 10 64bit. With
>>>>> > > > Windows 64bit, it fails to startup at all When I select
>>>>> > > > OtherOS it will allow me to start to run the Windows ISO, but
>>>>> > > > then fails after a few seconds as well. Is there something I'm
>>>>> > > > not correctly configuring?
>>>>> > >
>>>>> > > Would you please share vdsm.log,  and the output of
>>>>> > > rpm -qa kernel
>>>>> > > uname -a
>>>>> > > rpm -qa qemu-kvm-ev
>>>>> > > rpm -qa libvirt
>>>>> > > from of the host, and the relevant part of engine.log?
>>>>> > >
>>>>>
>>>>> ___
>>>> 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/BYIZ36LEPVD5FAD77L7FSDBHN2TZD4SD/
>>>>
>>>
>>>
>>> --
>>> Nisim Simsolo
>>> QE -Testing Engineer
>>> IRC: nsimsolo
>>> int phone - 8272305
>>> mobile - 054-4779934
>>>
>>
>
> --
> Nisim Simsolo
> QE -Testing Engineer
> IRC: nsimsolo
> int phone - 8272305
> mobile - 054-4779934
>
___
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/SWE5EILXGJBIW6WSAQ3TGOMASQKOGBTR/


[ovirt-users] Re: Windows 10 - Ovirt 4.3 - EPYC

2019-02-05 Thread Darin Schmidt
I dont even get to that point. The VM seems to detect the windows.iso I
downloaded from MS, the windows icon shows up, then it sits there for a
while, then I get the error in the picture I attached complaining about a
Sytem Thread Exception Not Handled. I dont make it to the install process
for windows.

On Tue, Feb 5, 2019 at 7:46 AM Nisim Simsolo  wrote:

> Hi
>
> If it's not Hyper-V SynIC issue, then it might be related to the disk
> interface.
> By default, the disk interface is VirtIO and Windows cannot see this
> interface until you intall VirtIO-Win disk driver.
> In order to do that, make sure you have VirtIO-Win.ISO in the ISO domain
> and during the Windows installation, when it's asking for disk location,
> change the VM CD to virtio-win.iso
> Click on "browse drivers" in the Windows installation window and install
> viostor from the ISO file.
> after the driver is installed, change the VM CD back to the Windows ISO ->
> refresh and continue the Windows installation.
>
> Please let me know if you still have issues.
>
> Thanks
>
>
>
> On Sat, Feb 2, 2019 at 5:22 PM Darin Schmidt 
> wrote:
>
>> Thanks, that sort of helped. I've ran yum update a dozen times and not
>> till this morning was there a kernel update... lol
>>
>> I'm able to startup the VM, but when it loads the ISO to install Windows
>> 10 which I downloaded from Microsoft, Attached is what always happens.
>> Perhaps my ISO is corrupt?
>>
>> On Sat, Feb 2, 2019 at 4:39 AM Dominik Holler  wrote:
>>
>>> On Fri, 1 Feb 2019 17:37:30 -0500
>>> Darin Schmidt  wrote:
>>>
>>> > [root@ovirt ~]# rpm -qa kernel
>>> > kernel-3.10.0-957.1.3.el7.x86_64
>>> > kernel-3.10.0-862.el7.x86_64
>>> > [root@ovirt ~]# uname -a
>>> > Linux ovirt 3.10.0-957.1.3.el7.x86_64 #1 SMP Thu Nov 29 14:49:43 UTC
>>> 2018
>>>
>>> https://bugzilla.redhat.com/1638835 looks like there is at least
>>> kernel 3.10.0-957.3.1.el7.x86_64 required.
>>> Can you please check if upgrading to kernel solves the issue for you?
>>> I expectect at least kernel 3.10.0-957.5.1 to be availible.
>>>
>>> > x86_64 x86_64 x86_64 GNU/Linux
>>> > [root@ovirt ~]# rpm -qa qemu-kvm-ev
>>> > qemu-kvm-ev-2.12.0-18.el7_6.3.1.x86_64
>>> > [root@ovirt ~]# rpm -qa libvirt
>>> > libvirt-4.5.0-10.el7_6.3.x86_64
>>>
>>> > here is the vdsm
>>> >
>>>
>>> contains:
>>> Hyper-V SynIC is not supported by kernel
>>>
>>>
>>> > On Fri, Feb 1, 2019 at 3:05 PM Dominik Holler 
>>> > wrote:
>>> >
>>> > > On Fri, 1 Feb 2019 11:48:51 -0500
>>> > > Darin Schmidt  wrote:
>>> > >
>>> > > > I have successfully setup a centos vm, its up and running. Now I
>>> > > > need to setup a windows 10 VM and I cant seem to get anything to
>>> > > > work.
>>> > > >
>>> > > > Ive tried setting the OS type to other or Windows 10 64bit. With
>>> > > > Windows 64bit, it fails to startup at all When I select
>>> > > > OtherOS it will allow me to start to run the Windows ISO, but
>>> > > > then fails after a few seconds as well. Is there something I'm
>>> > > > not correctly configuring?
>>> > >
>>> > > Would you please share vdsm.log,  and the output of
>>> > > rpm -qa kernel
>>> > > uname -a
>>> > > rpm -qa qemu-kvm-ev
>>> > > rpm -qa libvirt
>>> > > from of the host, and the relevant part of engine.log?
>>> > >
>>>
>>> ___
>> 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/BYIZ36LEPVD5FAD77L7FSDBHN2TZD4SD/
>>
>
>
> --
> Nisim Simsolo
> QE -Testing Engineer
> IRC: nsimsolo
> int phone - 8272305
> mobile - 054-4779934
>
___
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/DH4HW274WA2S3O6TAFTHVT7SMLI65NFE/


[ovirt-users] Re: Windows 10 - Ovirt 4.3 - EPYC

2019-02-02 Thread Darin Schmidt
Thanks, that sort of helped. I've ran yum update a dozen times and not till
this morning was there a kernel update... lol

I'm able to startup the VM, but when it loads the ISO to install Windows 10
which I downloaded from Microsoft, Attached is what always happens. Perhaps
my ISO is corrupt?

On Sat, Feb 2, 2019 at 4:39 AM Dominik Holler  wrote:

> On Fri, 1 Feb 2019 17:37:30 -0500
> Darin Schmidt  wrote:
>
> > [root@ovirt ~]# rpm -qa kernel
> > kernel-3.10.0-957.1.3.el7.x86_64
> > kernel-3.10.0-862.el7.x86_64
> > [root@ovirt ~]# uname -a
> > Linux ovirt 3.10.0-957.1.3.el7.x86_64 #1 SMP Thu Nov 29 14:49:43 UTC 2018
>
> https://bugzilla.redhat.com/1638835 looks like there is at least
> kernel 3.10.0-957.3.1.el7.x86_64 required.
> Can you please check if upgrading to kernel solves the issue for you?
> I expectect at least kernel 3.10.0-957.5.1 to be availible.
>
> > x86_64 x86_64 x86_64 GNU/Linux
> > [root@ovirt ~]# rpm -qa qemu-kvm-ev
> > qemu-kvm-ev-2.12.0-18.el7_6.3.1.x86_64
> > [root@ovirt ~]# rpm -qa libvirt
> > libvirt-4.5.0-10.el7_6.3.x86_64
>
> > here is the vdsm
> >
>
> contains:
> Hyper-V SynIC is not supported by kernel
>
>
> > On Fri, Feb 1, 2019 at 3:05 PM Dominik Holler 
> > wrote:
> >
> > > On Fri, 1 Feb 2019 11:48:51 -0500
> > > Darin Schmidt  wrote:
> > >
> > > > I have successfully setup a centos vm, its up and running. Now I
> > > > need to setup a windows 10 VM and I cant seem to get anything to
> > > > work.
> > > >
> > > > Ive tried setting the OS type to other or Windows 10 64bit. With
> > > > Windows 64bit, it fails to startup at all When I select
> > > > OtherOS it will allow me to start to run the Windows ISO, but
> > > > then fails after a few seconds as well. Is there something I'm
> > > > not correctly configuring?
> > >
> > > Would you please share vdsm.log,  and the output of
> > > rpm -qa kernel
> > > uname -a
> > > rpm -qa qemu-kvm-ev
> > > rpm -qa libvirt
> > > from of the host, and the relevant part of engine.log?
> > >
>
>
___
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/BYIZ36LEPVD5FAD77L7FSDBHN2TZD4SD/


[ovirt-users] Windows 10 - Ovirt 4.3 - EPYC

2019-02-01 Thread Darin Schmidt
I have successfully setup a centos vm, its up and running. Now I need to
setup a windows 10 VM and I cant seem to get anything to work.

Ive tried setting the OS type to other or Windows 10 64bit. With Windows
64bit, it fails to startup at all When I select OtherOS it will allow
me to start to run the Windows ISO, but then fails after a few seconds as
well. Is there something I'm not correctly configuring?
___
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/QFUOS7MX2J37YWNVFSDTJC4PJYAFHOV3/


[ovirt-users] Re: Storage Domain Ovirt 4.3 RC EPYC

2019-01-31 Thread Darin Schmidt
Seems the system is version locked? Looks like ovirt-engine 4.3.0.4 is
available and I have 4.3.0.2 installed. Should I disable the version lock?

[root@ovirt ~]# yum versionlock status
Loaded plugins: enabled_repos_upload, fastestmirror, langpacks,
package_upload, product-id, search-disabled-repos,
  : subscription-manager, vdsmupgrade, versionlock
This system is not registered with an entitlement server. You can use
subscription-manager to register.
Loading mirror speeds from cached hostfile
 * base: mirror.cisp.com
 * epel: epel.mirror.constant.com
 * extras: repo1.ash.innoscale.net
 * ovirt-4.3: mirrors.ibiblio.org
 * ovirt-4.3-epel: epel.mirror.constant.com
 * updates: mirror.cisp.com
0:ovirt-engine-webadmin-portal-4.3.0.4-1.el7.*
0:ovirt-engine-tools-backup-4.3.0.4-1.el7.*
0:ovirt-engine-restapi-4.3.0.4-1.el7.*
0:ovirt-engine-dbscripts-4.3.0.4-1.el7.*
0:ovirt-engine-4.3.0.4-1.el7.*
0:ovirt-engine-backend-4.3.0.4-1.el7.*
0:ovirt-engine-tools-4.3.0.4-1.el7.*
versionlock status done
Uploading Enabled Repositories Report
Loaded plugins: fastestmirror, langpacks, product-id, subscription-manager,
  : versionlock
This system is not registered with an entitlement server. You can use
subscription-manager to register.
Cannot upload enabled repos report, is this client registered?


On Thu, Jan 31, 2019 at 7:38 PM Darin Schmidt 
wrote:

> Same issue
>
> [root@ovirt ~]# rpm -qa|grep ovirt-engine-appliance
> ovirt-engine-appliance-4.3-20190131.1.el7.x86_64
>
> Error while executing action New Local Storage Domain: Storage format is
> unsupported
>
>
>
> On Thu, Jan 31, 2019 at 5:06 PM Greg Sheremeta 
> wrote:
>
>> Hi,
>>
>> On Thu, Jan 31, 2019 at 4:19 PM Darin Schmidt 
>> wrote:
>>
>>>
>>>
>>> Uncaught exception occurred. Please try reloading the page. Details:
>>> (TypeError) : Cannot read property 'Vg' of null
>>> Please have your administrator check the UI logs
>>>
>>
>> please attach ui.log
>>
>>
>>>
>>> Im trying to setup Ovirt 4.3 RC because its the only one that supports
>>> AMD EPYC. The issue Im having is that I creates a raid 5 array of 5 120GB
>>> SSDs using mdadm and mounted it at /VM. I put the Host into maintenance,
>>> select Configure Local Storage, and it fails telling me:
>>> New Local Storage Domain: Storage format is unsupported
>>>
>>
>> We fixed this one this morning -- update your appliance to
>> ovirt-engine-appliance-4.3-20190131.1.el7.x86_64
>> Then redeploy and it should work.
>> https://bugzilla.redhat.com/show_bug.cgi?id=1669606
>>
>> Best wishes,
>> Greg
>>
>>
>>>
>>> I formatted the array to ext4. This is a self hosted system.  Anyone
>>> have any ideas?
>>>
>>> [root@ovirt VM]# uname -r
>>> 3.10.0-957.1.3.el7.x86_64
>>> [root@ovirt VM]# cat /etc/centos-release
>>> CentOS Linux release 7.6.1810 (Core)
>>>
>>> [root@ovirt VM]# rpm -qa|grep ovirt
>>> ovirt-engine-backend-4.3.0.2-1.el7.noarch
>>> ovirt-imageio-common-1.4.6-1.el7.x86_64
>>> ovirt-engine-setup-plugin-websocket-proxy-4.3.0.4-1.el7.noarch
>>> ovirt-ansible-vm-infra-1.1.12-1.el7.noarch
>>> ovirt-ansible-infra-1.1.11-1.el7.noarch
>>> ovirt-engine-setup-plugin-ovirt-engine-common-4.3.0.4-1.el7.noarch
>>> libgovirt-0.3.4-1.el7.x86_64
>>> ovirt-hosted-engine-setup-2.3.3-1.el7.noarch
>>> ovirt-iso-uploader-4.3.0-1.el7.noarch
>>> ovirt-engine-4.3.0.2-1.el7.noarch
>>> python2-ovirt-host-deploy-1.8.0-1.el7.noarch
>>> ovirt-ansible-repositories-1.1.4-1.el7.noarch
>>> python-ovirt-engine-sdk4-4.3.0-2.el7.x86_64
>>> ovirt-engine-webadmin-portal-4.3.0.2-1.el7.noarch
>>> ovirt-engine-vmconsole-proxy-helper-4.3.0.4-1.el7.noarch
>>> ovirt-vmconsole-proxy-1.0.6-2.el7.noarch
>>> ovirt-ansible-image-template-1.1.9-1.el7.noarch
>>> ovirt-ansible-shutdown-env-1.0.3-1.el7.noarch
>>> ovirt-engine-dwh-4.3.0-1.el7.noarch
>>> ovirt-ansible-roles-1.1.6-1.el7.noarch
>>> ovirt-host-deploy-common-1.8.0-1.el7.noarch
>>> ovirt-engine-api-explorer-0.0.3-1.el7.noarch
>>> ovirt-engine-setup-base-4.3.0.4-1.el7.noarch
>>> ovirt-engine-extensions-api-impl-4.3.0.4-1.el7.noarch
>>> cockpit-ovirt-dashboard-0.12.1-1.el7.noarch
>>> ovirt-engine-tools-backup-4.3.0.2-1.el7.noarch
>>> ovirt-engine-restapi-4.3.0.2-1.el7.noarch
>>> ovirt-ansible-hosted-engine-setup-1.0.8-1.el7.noarch
>>> ovirt-engine-websocket-proxy-4.3.0.4-1.el7.noarch
>>> ovirt-hosted-engine-ha-2.3.1-1.el7.noarch
>>> ovirt-ansible-cluster-upgrade

[ovirt-users] Re: Storage Domain Ovirt 4.3 RC EPYC

2019-01-31 Thread Darin Schmidt
Same issue

[root@ovirt ~]# rpm -qa|grep ovirt-engine-appliance
ovirt-engine-appliance-4.3-20190131.1.el7.x86_64

Error while executing action New Local Storage Domain: Storage format is
unsupported



On Thu, Jan 31, 2019 at 5:06 PM Greg Sheremeta  wrote:

> Hi,
>
> On Thu, Jan 31, 2019 at 4:19 PM Darin Schmidt 
> wrote:
>
>>
>>
>> Uncaught exception occurred. Please try reloading the page. Details:
>> (TypeError) : Cannot read property 'Vg' of null
>> Please have your administrator check the UI logs
>>
>
> please attach ui.log
>
>
>>
>> Im trying to setup Ovirt 4.3 RC because its the only one that supports
>> AMD EPYC. The issue Im having is that I creates a raid 5 array of 5 120GB
>> SSDs using mdadm and mounted it at /VM. I put the Host into maintenance,
>> select Configure Local Storage, and it fails telling me:
>> New Local Storage Domain: Storage format is unsupported
>>
>
> We fixed this one this morning -- update your appliance to
> ovirt-engine-appliance-4.3-20190131.1.el7.x86_64
> Then redeploy and it should work.
> https://bugzilla.redhat.com/show_bug.cgi?id=1669606
>
> Best wishes,
> Greg
>
>
>>
>> I formatted the array to ext4. This is a self hosted system.  Anyone have
>> any ideas?
>>
>> [root@ovirt VM]# uname -r
>> 3.10.0-957.1.3.el7.x86_64
>> [root@ovirt VM]# cat /etc/centos-release
>> CentOS Linux release 7.6.1810 (Core)
>>
>> [root@ovirt VM]# rpm -qa|grep ovirt
>> ovirt-engine-backend-4.3.0.2-1.el7.noarch
>> ovirt-imageio-common-1.4.6-1.el7.x86_64
>> ovirt-engine-setup-plugin-websocket-proxy-4.3.0.4-1.el7.noarch
>> ovirt-ansible-vm-infra-1.1.12-1.el7.noarch
>> ovirt-ansible-infra-1.1.11-1.el7.noarch
>> ovirt-engine-setup-plugin-ovirt-engine-common-4.3.0.4-1.el7.noarch
>> libgovirt-0.3.4-1.el7.x86_64
>> ovirt-hosted-engine-setup-2.3.3-1.el7.noarch
>> ovirt-iso-uploader-4.3.0-1.el7.noarch
>> ovirt-engine-4.3.0.2-1.el7.noarch
>> python2-ovirt-host-deploy-1.8.0-1.el7.noarch
>> ovirt-ansible-repositories-1.1.4-1.el7.noarch
>> python-ovirt-engine-sdk4-4.3.0-2.el7.x86_64
>> ovirt-engine-webadmin-portal-4.3.0.2-1.el7.noarch
>> ovirt-engine-vmconsole-proxy-helper-4.3.0.4-1.el7.noarch
>> ovirt-vmconsole-proxy-1.0.6-2.el7.noarch
>> ovirt-ansible-image-template-1.1.9-1.el7.noarch
>> ovirt-ansible-shutdown-env-1.0.3-1.el7.noarch
>> ovirt-engine-dwh-4.3.0-1.el7.noarch
>> ovirt-ansible-roles-1.1.6-1.el7.noarch
>> ovirt-host-deploy-common-1.8.0-1.el7.noarch
>> ovirt-engine-api-explorer-0.0.3-1.el7.noarch
>> ovirt-engine-setup-base-4.3.0.4-1.el7.noarch
>> ovirt-engine-extensions-api-impl-4.3.0.4-1.el7.noarch
>> cockpit-ovirt-dashboard-0.12.1-1.el7.noarch
>> ovirt-engine-tools-backup-4.3.0.2-1.el7.noarch
>> ovirt-engine-restapi-4.3.0.2-1.el7.noarch
>> ovirt-ansible-hosted-engine-setup-1.0.8-1.el7.noarch
>> ovirt-engine-websocket-proxy-4.3.0.4-1.el7.noarch
>> ovirt-hosted-engine-ha-2.3.1-1.el7.noarch
>> ovirt-ansible-cluster-upgrade-1.1.11-1.el7.noarch
>> ovirt-cockpit-sso-0.1.1-1.el7.noarch
>> ovirt-engine-ui-extensions-1.0.2-1.el7.noarch
>> ovirt-engine-setup-4.3.0.4-1.el7.noarch
>> ovirt-imageio-daemon-1.4.6-1.el7.noarch
>> ovirt-host-4.3.0-2.el7.x86_64
>> ovirt-vmconsole-1.0.6-2.el7.noarch
>> ovirt-imageio-proxy-1.4.6-1.el7.noarch
>> ovirt-engine-wildfly-overlay-14.0.1-3.el7.noarch
>> ovirt-web-ui-1.5.0-1.el7.noarch
>> ovirt-provider-ovn-1.2.19-1.el7.noarch
>> ovirt-engine-dbscripts-4.3.0.2-1.el7.noarch
>> ovirt-ansible-engine-setup-1.1.7-1.el7.noarch
>> ovirt-engine-setup-plugin-ovirt-engine-4.3.0.4-1.el7.noarch
>> ovirt-provider-ovn-driver-1.2.19-1.el7.noarch
>> ovirt-engine-extension-aaa-jdbc-1.1.8-1.el7.noarch
>> python2-ovirt-setup-lib-1.2.0-1.el7.noarch
>> ovirt-host-deploy-java-1.8.0-1.el7.noarch
>> ovirt-engine-tools-4.3.0.2-1.el7.noarch
>> cockpit-machines-ovirt-176-4.el7.centos.noarch
>> ovirt-engine-metrics-1.2.0.3-1.el7.noarch
>> ovirt-imageio-proxy-setup-1.4.6-1.el7.noarch
>> ovirt-vmconsole-host-1.0.6-2.el7.noarch
>> ovirt-ansible-manageiq-1.1.13-1.el7.noarch
>> ovirt-engine-wildfly-14.0.1-3.el7.x86_64
>> ovirt-engine-setup-plugin-vmconsole-proxy-helper-4.3.0.4-1.el7.noarch
>> ovirt-host-dependencies-4.3.0-2.el7.x86_64
>> ovirt-ansible-disaster-recovery-1.1.4-1.el7.noarch
>> ovirt-engine-dwh-setup-4.3.0-1.el7.noarch
>> ovirt-ansible-v2v-conversion-host-1.9.1-1.el7.noarch
>> python2-ovirt-engine-lib-4.3.0.4-1.el7.noarch
>> ovirt-release43-pre-4.3.0-0.7.rc4.el7.noarch
>>
>> __

[ovirt-users] Storage Domain Ovirt 4.3 RC EPYC

2019-01-31 Thread Darin Schmidt


Uncaught exception occurred. Please try reloading the page. Details: 
(TypeError) : Cannot read property 'Vg' of null
Please have your administrator check the UI logs

Im trying to setup Ovirt 4.3 RC because its the only one that supports AMD 
EPYC. The issue Im having is that I creates a raid 5 array of 5 120GB SSDs 
using mdadm and mounted it at /VM. I put the Host into maintenance, select 
Configure Local Storage, and it fails telling me:
New Local Storage Domain: Storage format is unsupported

I formatted the array to ext4. This is a self hosted system.  Anyone have any 
ideas?

[root@ovirt VM]# uname -r
3.10.0-957.1.3.el7.x86_64
[root@ovirt VM]# cat /etc/centos-release
CentOS Linux release 7.6.1810 (Core)

[root@ovirt VM]# rpm -qa|grep ovirt
ovirt-engine-backend-4.3.0.2-1.el7.noarch
ovirt-imageio-common-1.4.6-1.el7.x86_64
ovirt-engine-setup-plugin-websocket-proxy-4.3.0.4-1.el7.noarch
ovirt-ansible-vm-infra-1.1.12-1.el7.noarch
ovirt-ansible-infra-1.1.11-1.el7.noarch
ovirt-engine-setup-plugin-ovirt-engine-common-4.3.0.4-1.el7.noarch
libgovirt-0.3.4-1.el7.x86_64
ovirt-hosted-engine-setup-2.3.3-1.el7.noarch
ovirt-iso-uploader-4.3.0-1.el7.noarch
ovirt-engine-4.3.0.2-1.el7.noarch
python2-ovirt-host-deploy-1.8.0-1.el7.noarch
ovirt-ansible-repositories-1.1.4-1.el7.noarch
python-ovirt-engine-sdk4-4.3.0-2.el7.x86_64
ovirt-engine-webadmin-portal-4.3.0.2-1.el7.noarch
ovirt-engine-vmconsole-proxy-helper-4.3.0.4-1.el7.noarch
ovirt-vmconsole-proxy-1.0.6-2.el7.noarch
ovirt-ansible-image-template-1.1.9-1.el7.noarch
ovirt-ansible-shutdown-env-1.0.3-1.el7.noarch
ovirt-engine-dwh-4.3.0-1.el7.noarch
ovirt-ansible-roles-1.1.6-1.el7.noarch
ovirt-host-deploy-common-1.8.0-1.el7.noarch
ovirt-engine-api-explorer-0.0.3-1.el7.noarch
ovirt-engine-setup-base-4.3.0.4-1.el7.noarch
ovirt-engine-extensions-api-impl-4.3.0.4-1.el7.noarch
cockpit-ovirt-dashboard-0.12.1-1.el7.noarch
ovirt-engine-tools-backup-4.3.0.2-1.el7.noarch
ovirt-engine-restapi-4.3.0.2-1.el7.noarch
ovirt-ansible-hosted-engine-setup-1.0.8-1.el7.noarch
ovirt-engine-websocket-proxy-4.3.0.4-1.el7.noarch
ovirt-hosted-engine-ha-2.3.1-1.el7.noarch
ovirt-ansible-cluster-upgrade-1.1.11-1.el7.noarch
ovirt-cockpit-sso-0.1.1-1.el7.noarch
ovirt-engine-ui-extensions-1.0.2-1.el7.noarch
ovirt-engine-setup-4.3.0.4-1.el7.noarch
ovirt-imageio-daemon-1.4.6-1.el7.noarch
ovirt-host-4.3.0-2.el7.x86_64
ovirt-vmconsole-1.0.6-2.el7.noarch
ovirt-imageio-proxy-1.4.6-1.el7.noarch
ovirt-engine-wildfly-overlay-14.0.1-3.el7.noarch
ovirt-web-ui-1.5.0-1.el7.noarch
ovirt-provider-ovn-1.2.19-1.el7.noarch
ovirt-engine-dbscripts-4.3.0.2-1.el7.noarch
ovirt-ansible-engine-setup-1.1.7-1.el7.noarch
ovirt-engine-setup-plugin-ovirt-engine-4.3.0.4-1.el7.noarch
ovirt-provider-ovn-driver-1.2.19-1.el7.noarch
ovirt-engine-extension-aaa-jdbc-1.1.8-1.el7.noarch
python2-ovirt-setup-lib-1.2.0-1.el7.noarch
ovirt-host-deploy-java-1.8.0-1.el7.noarch
ovirt-engine-tools-4.3.0.2-1.el7.noarch
cockpit-machines-ovirt-176-4.el7.centos.noarch
ovirt-engine-metrics-1.2.0.3-1.el7.noarch
ovirt-imageio-proxy-setup-1.4.6-1.el7.noarch
ovirt-vmconsole-host-1.0.6-2.el7.noarch
ovirt-ansible-manageiq-1.1.13-1.el7.noarch
ovirt-engine-wildfly-14.0.1-3.el7.x86_64
ovirt-engine-setup-plugin-vmconsole-proxy-helper-4.3.0.4-1.el7.noarch
ovirt-host-dependencies-4.3.0-2.el7.x86_64
ovirt-ansible-disaster-recovery-1.1.4-1.el7.noarch
ovirt-engine-dwh-setup-4.3.0-1.el7.noarch
ovirt-ansible-v2v-conversion-host-1.9.1-1.el7.noarch
python2-ovirt-engine-lib-4.3.0.4-1.el7.noarch
ovirt-release43-pre-4.3.0-0.7.rc4.el7.noarch

___
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/3ASMB4IW74TXD576KKIIZBKYCQTTISJI/


[ovirt-users] Re: Ovirt 4.3 Alpha AMD 2970WX Windows VM creation and NUMA

2018-12-13 Thread Darin Schmidt
I cant get any further though for some reason. I think its with qemu. I can get 
a VM up to install the OS by selecting somethign other than Windows for the VM 
type as specified as a possible workaround. But as Windows boot ISO does its 
thing, it throws a thread error. I can get the error later today if needed. I 
just been patiently waiting for 4.3 to become more developed so I can use my 
hardware. 
___
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/TDRJMXHA22XRAD6B2PF7DP6QFTEA4KKL/


[ovirt-users] Re: Ovirt 4.3 Alpha AMD 2970WX Windows VM creation and NUMA

2018-12-13 Thread Darin Schmidt
https://bugzilla.redhat.com/show_bug.cgi?id=1655340

is been marked as a duplicateof bug:

https://bugzilla.redhat.com/show_bug.cgi?id=1644693

which pretty much from my understanding stated that they require qemu and
kernel for new hyperv flags

On Thu, Dec 13, 2018 at 10:10 AM Sandro Bonazzola 
wrote:

>
>
> Il giorno lun 3 dic 2018 alle ore 00:59 Darin Schmidt <
> darinschm...@gmail.com> ha scritto:
>
>> I went ahead and submitted a bug report. I cannot find the typo anywhere.
>>
>
> Can you please share the bug URL?
> 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/HD4VG4ZO3ZP2VBDTFWLRYVS5FAPRD27A/
>>
>
>
> --
>
> SANDRO BONAZZOLA
>
> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
>
> Red Hat EMEA <https://www.redhat.com/>
>
> sbona...@redhat.com
> <https://red.ht/sig>
>
___
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/M7E3E2XQDMUQNPJTGNENXEDBKZXSNWLR/


[ovirt-users] Re: Ovirt 4.3 Alpha AMD 2970WX Windows VM creation and NUMA

2018-12-02 Thread Darin Schmidt
I went ahead and submitted a bug report. I cannot find the typo anywhere. 
___
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/HD4VG4ZO3ZP2VBDTFWLRYVS5FAPRD27A/


[ovirt-users] Re: Ovirt 4.3 Alpha AMD 2970WX Windows VM creation and NUMA

2018-12-02 Thread Darin Schmidt
That was my thought too, I'll do some investigating. Not 100% sure where to 
look atm. 
___
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/3SHLZ6KL2CEP6SWO4SSNG4ZQUVJPSH2R/


[ovirt-users] Ovirt 4.3 Alpha AMD 2970WX Windows VM creation and NUMA

2018-12-02 Thread Darin Schmidt
Not sure if Users is the best place for this as Im using 4.3 to test support 
for my AMD 2970WX Threadripper but While trying to setup a Windows VM, it 
fails. I have a working CentOS 7 running. Heres what I get when I try to 
startup the VM. 

VM Windows-Darin is down with error. Exit message: internal error: process 
exited while connecting to monitor: WARNING: Image format was not specified for 
'/dev/sg0' and probing guessed raw.
 Automatically detecting the format is dangerous for raw images, write 
operations on block 0 will be restricted.
 Specify the 'raw' format explicitly to remove the restrictions.
2018-12-02T18:43:05.358741Z qemu-kvm: warning: CPU(s) not present in any NUMA 
nodes: CPU 10 [socket-id: 10, core-id: 0, thread-id: 0], CPU 11 [socket-id: 11, 
core-id: 0, thread-id: 0], CPU 12 [socket-id: 12, core-id: 0, thread-id: 0], 
CPU 13 [socket-id: 13, core-id: 0, thread-id: 0], CPU 14 [socket-id: 14, 
core-id: 0, thread-id: 0], CPU 15 [socket-id: 15, core-id: 0, thread-id: 0]
2018-12-02T18:43:05.358791Z qemu-kvm: warning: All CPU(s) up to maxcpus should 
be described in NUMA config, ability to start up with partial NUMA mappings is 
obsoleted and will be removed in future
2018-12-02T18:43:05.359052Z qemu-kvm: can't apply global 
EPYC-x86_64-cpu.hv-synic=on: Property '.hv-synic' not found.

NUMA doesnt seem to resolve the issue any even if I set NUMA to be 1 and place 
it on a NUMA that has 12 cores and 64GB ram. I also dont fully understand NUMA 
because it creates 4 NUMA sockets even though technically there should be 2 
correct? I dont get how NUMA is setup, but either way it doesnt help resolve 
any issues. 

[root@ovirt ~]# numactl --hardware
available: 4 nodes (0-3)
node 0 cpus: 0 1 2 3 4 5 24 25 26 27 28 29
node 0 size: 65429 MB
node 0 free: 54322 MB
node 1 cpus: 12 13 14 15 16 17 36 37 38 39 40 41
node 1 size: 0 MB
node 1 free: 0 MB
node 2 cpus: 6 7 8 9 10 11 30 31 32 33 34 35
node 2 size: 32754 MB
node 2 free: 27699 MB
node 3 cpus: 18 19 20 21 22 23 42 43 44 45 46 47
node 3 size: 0 MB
node 3 free: 0 MB
node distances:
node   0   1   2   3
  0:  10  16  16  16
  1:  16  10  16  16
  2:  16  16  10  16
  3:  16  16  16  10

link to my messages and vdsm log
https://drive.google.com/open?id=1v-Wjcj7xLZIcR2GKR-P659yE14r1-hsz
https://drive.google.com/open?id=1BHvcS2Dgan68hQkVdOmme1gP1ciSsejL
___
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/KJ3L4GDRANRO376V5LJHL734QJ2FYU6A/


[ovirt-users] Re: oVirt Node on CentOS 7.5 and AMD EPYC Support

2018-11-30 Thread Darin Schmidt
I was curious, I have an AMD Threadripper (2970wx). Do you know where Ovirt is 
grepping or other to get the info needed to use the cpu type? I assume lscpu is 
possibly where it gets it and is just matching? Id like to be able to test this 
on a threadripper. 
___
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/4TUJ3LLVDOMPFEQGNU7IPAKE3AO2KH3D/


[ovirt-users] Re: AMD Threadripper support

2018-11-29 Thread Darin Schmidt
Can anyone shed some light on this?

I see that for EPYC you add 

7:AMD EPYC:svm,nx,model_EPYC:EPYC:x86_64; 8:AMD EPYC 
IBPB:svm,nx,ibpb,model_EPYC:EPYC,+ibpb:x86_64;

Would this work for the AMD Ryzen as they are the same thing(ish)?
___
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/PPSREPJ53TNPLVIMUVGZV3VV3CFOQ7JN/


[ovirt-users] Re: AMD Threadripper support

2018-11-24 Thread Darin Schmidt
I figured out the issue with the command issues above. So Now I just need to 
know how to figure out what to add to be able to use the CPU I have. I dont 
know how or where you get the info to add to the DB and it be correct. Would 
appreciate some insight. 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/WSOYPMVK34CZJ7OQ3LXK7ZPXBPNR7WWT/


[ovirt-users] Re: AMD Threadripper support

2018-11-24 Thread Darin Schmidt
here's the link with the info on adding an EPYC CPU. 
https://lists.ovirt.org/archives/list/users@ovirt.org/thread/T3XL6NU7SUPYLYFL4TEKLOZTBWY6ID3S/
___
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/OR5YV34QFGB64J7NT6TFYGDFBQ2SLK2Q/


[ovirt-users] AMD Threadripper support

2018-11-24 Thread Darin Schmidt
My Issue is that there isnt an option to select anything other than Opteron 
based AMD chips. Is there a way to add my CPU to the list? I have an AMD 2970wx 
Threadripper. I found an article stating that you can edit the postre database. 
But where do I find the info needed to add a CPU to the list? Also when I tried 
to follow the instructions, I get:

-bash-4.2$ /opt/rh/rh-postgresql95/root/bin/psql -h localhost -p 5432 -U engine 
-W
/opt/rh/rh-postgresql95/root/bin/psql: error while loading shared libraries: 
libpq.so.rh-postgresql95-5: cannot open shared object file: No such file or 
directory
___
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/4Q6PNRZ5JXH4A27HKXHQSCBPZC3L66G3/