[ovirt-users] Changing video memory size

[Alexis HAUSER]

Hi,

I would like to change the video memory size (vram_size parameter), how can I 
proceed ?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] secure ovirt hosts 4.0

[Rafael Almeida]

Hello, i need secure my hosts runining ovirt (vdsm-4.18.4.1-0) over 
centos 7, this because oVirt installed on a minimal install of centos 
7x, could helpme by sending all required ports enabled for hosts.


pd. selinux=disabled, firewalld=enabled

Thanks for the help

*Rafael Almeida Orellana *


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Is it possible to disable qxl video?

[Arman Khalatyan]

Thanks for clarification. the kvm=off solved the problem.
NICE!!! I got now inside the VM:
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GT 630/PCIe/SSE2
OpenGL core profile version string: 4.4.0 NVIDIA 367.27
OpenGL core profile shading language version string: 4.40 NVIDIA via Cg
compiler
OpenGL core profile context flags: (none)

the steps to reproduce:
1) virsh edit render
2) change schema of xml: 
3) add following in the end before :



  
4)  start vm, install nvidia driver, check gpu: nvidia smi
5) install virtualgl, init 3
6) nvidia-xconfig --enable-all-gpus --separate-x-screens
--use-display-device=None --virtual=1280x1024
init 5
7) vglconnet render01.vm and finally: vglrun glxinfo or whatever!!!

Now back to origin: how to add this tweak in to ovirt?? :)









***

 Dr. Arman Khalatyan  eScience -SuperComputing
 Leibniz-Institut für Astrophysik Potsdam (AIP)
 An der Sternwarte 16, 14482 Potsdam, Germany

***

On Mon, Jul 11, 2016 at 5:30 PM, Martin Polednik 
wrote:

> On 11/07/16 17:16 +0200, Arman Khalatyan wrote:
>
>> Yes I have a BusID inside the xorg.conf.
>> I just tested with virt-manager and indeed it is not a ovirt failure.
>> It is something to do with qemu-kvm + nvidia.
>> I found here:https://wiki.debian.org/VGAPassthrough  that nvidia disables
>> device when it is running on qemu-kvm is it still the case? to overcome
>> that one need to set:
>>
>> -cpu host,kvm=off
>>
>> in the command line of qemu.
>>
>
> This applies to GPUs that NVIDIA does not support in virtualized
> environments (actually your GTX630). Quadro K2200 and higher
> (incl. grid, tesla) should not require masking the hypervisor. It
> could be worth to supply dmesg from the host and from the guest so we
> could see if there is any apparent failure.
>
> That being said, I have had failures even with supported card that
> just stopped at one point. It's worth trying the kvm=off trick.
>
> I was trying to convert virsh commands to qemu native, but it fails on
>> Centos 7 :(
>> virsh dumpxml > render.xml
>> virsh  domxml-to-native qemu-argv render.xml
>> error: internal error: invalid PCI passthrough type 'default'
>>
>
> I usually take the qemu command line from
> /var/log/libvirt/qemu/${VM_NAME}, tweak it in vim and launch. Works
> even for oVirt VMs (if you can hack around the storage).
>
>
> ***
>>
>> Dr. Arman Khalatyan  eScience -SuperComputing
>> Leibniz-Institut für Astrophysik Potsdam (AIP)
>> An der Sternwarte 16, 14482 Potsdam, Germany
>>
>> ***
>>
>> On Mon, Jul 11, 2016 at 11:55 AM, Martin Polednik 
>> wrote:
>>
>> On 11/07/16 09:46 +, Karli Sjöberg wrote:
>>>
>>>
 Den 11 jul 2016 11:37 fm skrev Arman Khalatyan :


> I just testing several GPUs with pci-passthrough: GTX630, Tesla 2050
> and
> FX5800.
> None of them I got running with opengl/direct rendering inside the
> virtual machine.
> I was thinking something to do with qxl driver, but after blacklisting
> it in the VMs kernel nothing was changed.
> The VMs Xorg claiming always no display found even if I configure it
> with headless option: nvidia-xconfig -a --use-display-device=None
> --virtual=1280x1024
> But with nvidia-smi I can see the GPU status, and I can run all cuda
> tests where opengl/X11 is not involved.
> My test system is CentOS 7 with ovirt 4.
> BTW If I clone VM which was not running, to real host on bare metal,
> everything is running as expecting.
>
>
 Don't remember If this was mentioned but have you tried doing the same
 thing but with virt-manager on a standalone host, just to rule out oVirt
 from the equation?


>>> Also, the xorg must be setup to use the VFIO GPU. There is BusID
>>> option in device section that must point to the guest address of the
>>> GPU. I'm not sure if you've done that (and I'm quite sure it's missing
>>> on the wiki, noted).
>>>
>>> [in the guest]
>>> $ lspci | grep VGA
>>> 03:00.0 VGA compatible controller: NVIDIA Corporation GM107GL [Quadro
>>> K2200] (rev a2)
>>>
>>> and  using the address, add device section to /etc/X11/xorg.conf
>>>
>>> Section "Device"
>>>Identifier "Device0"
>>>Driver "nvidia"
>>>VendorName "NVIDIA Corporation"
>>>BusID  "PCI:3:0:0"
>>> EndSection
>>>
>>> That should allow xorg to use the assigned GPU.
>>>
>>> mpolednik
>>>
>>>
>>> /K
>>>


>
>
>
>
>
>
> ***
>
>  Dr. Arman Khalatyan  eScience -SuperComputing
>  Leibniz-Institut für Astrophysik Potsdam (AIP)
>  An der Sternwarte 16, 14482 Potsdam, Germany
>
> 

Re: [ovirt-users] ldap and multiple profiles

[Ondra Machacek]

On 07/04/2016 04:13 PM, Fabrice Bacchella wrote:

I want to setup two LDAP base profile.

One is backed using an active directory (for real users)
One is backed using an openldap (for service account).

I have to problem with this setup.

One it's that in the log I see many "Creating LDAP pool 'authz'" and "Creating LDAP 
pool 'authn'". If I have two LDAP backend, I'm afraid they will be a conflict of ldap pool if 
they used the same name.


I am unsure I understand the problem, if you will use different profiles 
you won't share the
pool. Can you send the log and explain on that what's going on, so we 
can understand the

problem?



I tried to add in my openldap.properties:

search.simple-namespace.pool = authz-prod
search.simple-user-fetch.pool = authz-prod
search.simple-resolve-groups-member.pool = authz-prod
search.simple-resolve-groups-memberOf-item.pool = authz-prod
search.simple-resolve-groups-memberOf.pool = authz-prod
search.simple-query-principals.pool = authz-prod
search.simple-query-groups.pool = authz-prod

Is that enough ? And Why is it replicated many time ?

I have another problem, there is a stupid bug in my openldap configuration, but 
it will be difficult to resolve that.

In it, there is two naming context
dc=sub,dc=example,dc=com
and
dc=example,dc=com

Ovirt only see the first one, and of course, with a little help from Murphy, I 
need the seconde one. Is there anything I can do about that ?


Yes, you can. Please see[1] and check 'Is it possible to use specific 
base DN instead of automatic resolution?'


[1] http://www.ovirt.org/develop/release-management/features/infra/aaa_faq/



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Is it possible to disable qxl video?

[Martin Polednik]

On 11/07/16 17:16 +0200, Arman Khalatyan wrote:

Yes I have a BusID inside the xorg.conf.
I just tested with virt-manager and indeed it is not a ovirt failure.
It is something to do with qemu-kvm + nvidia.
I found here:https://wiki.debian.org/VGAPassthrough  that nvidia disables
device when it is running on qemu-kvm is it still the case? to overcome
that one need to set:

-cpu host,kvm=off

in the command line of qemu.


This applies to GPUs that NVIDIA does not support in virtualized
environments (actually your GTX630). Quadro K2200 and higher
(incl. grid, tesla) should not require masking the hypervisor. It
could be worth to supply dmesg from the host and from the guest so we
could see if there is any apparent failure.

That being said, I have had failures even with supported card that
just stopped at one point. It's worth trying the kvm=off trick.


I was trying to convert virsh commands to qemu native, but it fails on
Centos 7 :(
virsh dumpxml > render.xml
virsh  domxml-to-native qemu-argv render.xml
error: internal error: invalid PCI passthrough type 'default'


I usually take the qemu command line from
/var/log/libvirt/qemu/${VM_NAME}, tweak it in vim and launch. Works
even for oVirt VMs (if you can hack around the storage).


***

Dr. Arman Khalatyan  eScience -SuperComputing
Leibniz-Institut für Astrophysik Potsdam (AIP)
An der Sternwarte 16, 14482 Potsdam, Germany

***

On Mon, Jul 11, 2016 at 11:55 AM, Martin Polednik 
wrote:


On 11/07/16 09:46 +, Karli Sjöberg wrote:



Den 11 jul 2016 11:37 fm skrev Arman Khalatyan :



I just testing several GPUs with pci-passthrough: GTX630, Tesla 2050 and
FX5800.
None of them I got running with opengl/direct rendering inside the
virtual machine.
I was thinking something to do with qxl driver, but after blacklisting
it in the VMs kernel nothing was changed.
The VMs Xorg claiming always no display found even if I configure it
with headless option: nvidia-xconfig -a --use-display-device=None
--virtual=1280x1024
But with nvidia-smi I can see the GPU status, and I can run all cuda
tests where opengl/X11 is not involved.
My test system is CentOS 7 with ovirt 4.
BTW If I clone VM which was not running, to real host on bare metal,
everything is running as expecting.



Don't remember If this was mentioned but have you tried doing the same
thing but with virt-manager on a standalone host, just to rule out oVirt
from the equation?



Also, the xorg must be setup to use the VFIO GPU. There is BusID
option in device section that must point to the guest address of the
GPU. I'm not sure if you've done that (and I'm quite sure it's missing
on the wiki, noted).

[in the guest]
$ lspci | grep VGA
03:00.0 VGA compatible controller: NVIDIA Corporation GM107GL [Quadro
K2200] (rev a2)

and  using the address, add device section to /etc/X11/xorg.conf

Section "Device"
   Identifier "Device0"
   Driver "nvidia"
   VendorName "NVIDIA Corporation"
   BusID  "PCI:3:0:0"
EndSection

That should allow xorg to use the assigned GPU.

mpolednik


/K










***

 Dr. Arman Khalatyan  eScience -SuperComputing
 Leibniz-Institut für Astrophysik Potsdam (AIP)
 An der Sternwarte 16, 14482 Potsdam, Germany

***

On Mon, Jul 11, 2016 at 9:06 AM, Martin Polednik 
wrote:



On 08/07/16 11:29 +0200, Michal Skrivanek wrote:




On 06 Jul 2016, at 14:06, Francesco Romani  wrote:



From: "Arman Khalatyan" 
To: "users" 
Sent: Monday, July 4, 2016 11:52:24 AM
Subject: [ovirt-users] Is it possible to disable qxl video?


Hi,
I am doing PCI Passthrough for GPUs.
Is it possible somehow to disable/remove default video qxl?
thanks,
Arman,.
Hi,

The 4.0 Vdsm allows you to run a headless VM, meaning a VM without
graphic device/frontend.
Not sure Engine allows you that however.




no it doesn’t




Even if engine allowed that, it may not be the correct solution.

Running headless with PCI passthrough is considered primary VGA
passthrough[1]. Using primary VGA passthrough without OVMF could cause
(will cause) quite a bit of headaches.

If you really want to try that, I assume using before_vm_start hook to
remove the video device should be enough.

[1] http://wiki.xenproject.org/wiki/Xen_VGA_Passthrough - it's
possible to read about primary and secondary passthrough between the
lines

However, if QXL is the problem (why is that so?) then you can switch to

VGA(or CIRRUS if this is still 3.6)

I'm afraid you will need to write a Vdsm hook.


There could be simpler solutions depending on the Engine

Bests,

--
Francesco Romani
RedHat Engineering Virtualization R & D
Phone: 8261328
IRC: fromani
___

Re: [ovirt-users] Is it possible to disable qxl video?

[Arman Khalatyan]

Yes I have a BusID inside the xorg.conf.
I just tested with virt-manager and indeed it is not a ovirt failure.
It is something to do with qemu-kvm + nvidia.
I found here:https://wiki.debian.org/VGAPassthrough  that nvidia disables
device when it is running on qemu-kvm is it still the case? to overcome
that one need to set:

-cpu host,kvm=off

in the command line of qemu.

I was trying to convert virsh commands to qemu native, but it fails on
Centos 7 :(
virsh dumpxml > render.xml
virsh  domxml-to-native qemu-argv render.xml
error: internal error: invalid PCI passthrough type 'default'



***

 Dr. Arman Khalatyan  eScience -SuperComputing
 Leibniz-Institut für Astrophysik Potsdam (AIP)
 An der Sternwarte 16, 14482 Potsdam, Germany

***

On Mon, Jul 11, 2016 at 11:55 AM, Martin Polednik 
wrote:

> On 11/07/16 09:46 +, Karli Sjöberg wrote:
>
>>
>> Den 11 jul 2016 11:37 fm skrev Arman Khalatyan :
>>
>>>
>>> I just testing several GPUs with pci-passthrough: GTX630, Tesla 2050 and
>>> FX5800.
>>> None of them I got running with opengl/direct rendering inside the
>>> virtual machine.
>>> I was thinking something to do with qxl driver, but after blacklisting
>>> it in the VMs kernel nothing was changed.
>>> The VMs Xorg claiming always no display found even if I configure it
>>> with headless option: nvidia-xconfig -a --use-display-device=None
>>> --virtual=1280x1024
>>> But with nvidia-smi I can see the GPU status, and I can run all cuda
>>> tests where opengl/X11 is not involved.
>>> My test system is CentOS 7 with ovirt 4.
>>> BTW If I clone VM which was not running, to real host on bare metal,
>>> everything is running as expecting.
>>>
>>
>> Don't remember If this was mentioned but have you tried doing the same
>> thing but with virt-manager on a standalone host, just to rule out oVirt
>> from the equation?
>>
>
> Also, the xorg must be setup to use the VFIO GPU. There is BusID
> option in device section that must point to the guest address of the
> GPU. I'm not sure if you've done that (and I'm quite sure it's missing
> on the wiki, noted).
>
> [in the guest]
> $ lspci | grep VGA
> 03:00.0 VGA compatible controller: NVIDIA Corporation GM107GL [Quadro
> K2200] (rev a2)
>
> and  using the address, add device section to /etc/X11/xorg.conf
>
> Section "Device"
>Identifier "Device0"
>Driver "nvidia"
>VendorName "NVIDIA Corporation"
>BusID  "PCI:3:0:0"
> EndSection
>
> That should allow xorg to use the assigned GPU.
>
> mpolednik
>
>
> /K
>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> ***
>>>
>>>  Dr. Arman Khalatyan  eScience -SuperComputing
>>>  Leibniz-Institut für Astrophysik Potsdam (AIP)
>>>  An der Sternwarte 16, 14482 Potsdam, Germany
>>>
>>> ***
>>>
>>> On Mon, Jul 11, 2016 at 9:06 AM, Martin Polednik 
>>> wrote:
>>>

 On 08/07/16 11:29 +0200, Michal Skrivanek wrote:

>
>
> On 06 Jul 2016, at 14:06, Francesco Romani  wrote:
>>
>>
>> From: "Arman Khalatyan" 
>> To: "users" 
>> Sent: Monday, July 4, 2016 11:52:24 AM
>> Subject: [ovirt-users] Is it possible to disable qxl video?
>>
>>
>> Hi,
>> I am doing PCI Passthrough for GPUs.
>> Is it possible somehow to disable/remove default video qxl?
>> thanks,
>> Arman,.
>> Hi,
>>
>> The 4.0 Vdsm allows you to run a headless VM, meaning a VM without
>> graphic device/frontend.
>> Not sure Engine allows you that however.
>>
>
>
> no it doesn’t
>


 Even if engine allowed that, it may not be the correct solution.

 Running headless with PCI passthrough is considered primary VGA
 passthrough[1]. Using primary VGA passthrough without OVMF could cause
 (will cause) quite a bit of headaches.

 If you really want to try that, I assume using before_vm_start hook to
 remove the video device should be enough.

 [1] http://wiki.xenproject.org/wiki/Xen_VGA_Passthrough - it's
 possible to read about primary and secondary passthrough between the
 lines

 However, if QXL is the problem (why is that so?) then you can switch to
> VGA(or CIRRUS if this is still 3.6)
>
> I'm afraid you will need to write a Vdsm hook.
>>
>> There could be simpler solutions depending on the Engine
>>
>> Bests,
>>
>> --
>> Francesco Romani
>> RedHat Engineering Virtualization R & D
>> Phone: 8261328
>> IRC: fromani
>> ___
>> Users mailing list
>> Users@ovirt.org 
>> http://lists.ovirt.org/mailman/listinfo/users <
>> 

Re: [ovirt-users] VM convert Windows2012R2 to Ovirt

[Vinzenz Feenstra]

> On Jul 4, 2016, at 7:05 PM, Pavel Gashev  wrote:
> 
> Vinzenz,
>  
> I just tried libguestfs-RHEL-7.3-preview. I have converted a Windows2012R2 VM 
> with no issues, except it doesn't boot – see attached screenshot.

Hi Pavel, 

Sorry for the delay I have been on Vacation last week therefore I couldn’t 
respond any earlier.

First of all, please ensure that the configured system matches the actual 
Windows 2012 R2 configuration 

Also please let me know what is the supported CPU Family on your cluster?

Regards,

>  
> Thanks
>  
> On 21/06/16 14:14, "users-boun...@ovirt.org  
> on behalf of Vinzenz Feenstra"   on behalf of vfeen...@redhat.com 
> > wrote:
>  
>  
> On Jun 21, 2016, at 11:42 AM, Carlos García Gómez 
> > wrote:
>  
> Hi,
>  
> Yes I have tried...
>  
> virt-v2v -v -i ova -o rhev -os NFS:/Export/ --network ovirtmgmt 
> /rhev/data-center/mnt/NFS:_Export/TemplateWin2012.ova -of raw
>  
> But I get...
>  
> [ 101,0] Converting Windows Server 2012 R2 Datacenter Evaluation to run on KVM
> virt-v2v: error: virt-v2v cannot be used to convert Windows > 7 / 2008R2
>  
> Please try the https://people.redhat.com/~rjones/libguestfs-RHEL-7.3-preview/ 
>  repository 
> and upgrade the virt-v2v version to 1.32 which will bring the support for 
> higher Windows versions
>  
> 
> 
>  
>  
> 
>  
>  
> From: Vinzenz Feenstra 
> Sent: Tuesday, June 21, 2016 11:30 AM
> To: Carlos García Gómez 
> Cc: users 
> Subject: Re: [ovirt-users] VM convert Windows2012R2 to Ovirt
>  
>  
> On Jun 21, 2016, at 10:09 AM, Carlos García Gómez 
> > wrote:
>  
> Hello,
> 
> Anybody know if there is any way to convert(export) some VM Windows 2012R2 to 
> Ovirt?
> 
> Windows 2012 is in vmware enviorment. (ova) and vmdk files
>  
> Hi there for this we have the virt-v2v tool
>  
> http://www.ovirt.org/develop/release-management/features/virt/virt-v2v-integration/
>  
> 
>  
> 
> 
> 
> Regards,
> 
> Carlos 
> ___
> Users mailing list
> Users@ovirt.org 
> http://lists.ovirt.org/mailman/listinfo/users 
> 
>  
>  
> 

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Communicating with ovirt agent

[Vinzenz Feenstra]

> On Jul 4, 2016, at 2:49 PM, Tadas  wrote:
> 
> We are mostly using Debian based distros (Debian, Ubuntu).
> And since this is a massive project it takes much time to adopt it to 
> different distro and also maintain it.
> On the other hand our project is in production at the moment and the only 
> thing that was still unfinished was SSO part. With help of oVirt agents it 
> will take little time to extend SSO in our code.

hi there,

sorry for the late reply I have been last week on vacation.

Well we can also try to improve the support for those systems instead :-)
If we have someone who can give us active feedback on things working or not we 
can fix the things.

We already have the guest agent “in” debian and ubuntu however they seem to be 
still having some troubles to run properly.

Anyway I am glad to work with you and we can get these things fixed asap to 
make it work properly on Debian based systems 

Regards,

>  
> Indeed, it is EL (CentOS, Scientific, etc.) friendly.
> Which distribution are you looking for?
> (And of course, patches are welcome).
> Y.
>  
> On Mon, 2016-07-04 at 11:11 +0300, Yaniv Kaul wrote:
> >
> >
> > On Mon, Jul 4, 2016 at 10:25 AM, Tadas  > > wrote:
> > > I'm developing a simple VDI solution for our university. And I find
> > > "windows-credprov" and "virt-agent" very useful to provide SSO from
> > > user dashboard to VM.
> > >
> >
> > But we already provide SSO functionality in oVirt. With Active
> > Directory integration.
> > Y.
> >
> >  
> > > On Mon, 2016-07-04 at 10:00 +0300, Yaniv Kaul wrote:
> > > >
> > > >
> > > > On Mon, Jul 4, 2016 at 9:16 AM, Tadas  > > > > wrote:
> > > > > Got everything working now.
> > > >
> > > > Great to hear.
> > > > What is your use case?
> > > > Y.
> > > >  
> > > > > Thank you for your help.
> > > > > For any users, whom it may be useful, heres the code for
> > > external
> > > > > (SSO)
> > > > > logins from hypervisor.
> > > > >
> > > > > http://paste.ubuntu.com/18435531/ 
> > > > >
> > > > > On Fri, 2016-07-01 at 13:53 +0200, Vinzenz Feenstra wrote:
> > > > > >
> > > > > > > On Jul 1, 2016, at 12:05 PM, Tadas  > > > > > > > wrote:
> > > > > > >
> > > > > > >
> > > > > > > is there any documentation o oVirt guest agent commands?
> > > > > > > To be more precise: i need to pass commands to oVirt guest
> > > > > agent
> > > > > > > from
> > > > > > > hypervisor.
> > > > > > > Reading info works fine:
> > > > > > >
> > > > > > > socat /var/lib/libvirt/qemu/channel/target/domain-20-
> > > > > > > win7_32bit/com.redhat.serial.0 -
> > > > > > >
> > > > > > > {"applications": ["Python 2.7.12rc1", "SPICE Guest Tools",
> > > > > "Total
> > > > > > > Commander (Remove or Repair)", "Python 2.7 pywin32-216",
> > > > > "Microsoft
> > > > > > > .NET Framework 4.6.1", "Git version 2.9.0", "WinRAR 5.40
> > > beta 2
> > > > > > > (32-
> > > > > > > bit)", "Notepad++"], "__name__": "applications"}
> > > > > > > {"__name__": "host-name", "name": "WIN7_32BIT"}
> > > > > > > {"__name__": "os-version", "version": "Win 7”}
> > > > > >
> > > > > > Every command has to be send as a whole JSON object and sent
> > > as
> > > > > line
> > > > > > terminated by a \n character
> > > > > >
> > > > > > The commands available are currently not documented however.
> > > > > >
> > > > > > {“__name__”: “name”, … args}
> > > > > >
> > > > > > - name: shutdown
> > > > > >   parameters:
> > > > > >   - timeout: optional integer (seconds)
> > > > > >   - reboot: optional boolean
> > > > > >   - message: string
> > > > > >
> > > > > > - name: refresh
> > > > > >   parameters:
> > > > > >   - apiVersion: optiona integer 
> > > > > > this defines what information can be exchanged
> > > > > >
> > > > > > - name: hibernate:
> > > > > >   parameters:
> > > > > >   - state: disk or mem (default is disk if not specified)
> > > > > >
> > > > > > if you need more you can look here:  https://github.com/oVirt 
> > > > > > 
> > > /ovi
> > > > > rt-g
> > > > > > uest-agent/blob/master/ovirt-guest-
> > > > > agent/OVirtAgentLogic.py#L306 at
> > > > > > the parseCommand function
> > > > > > or just ask here :-)
> > > > > >
> > > > > > >
> > > > > > > I'm unable to find how to send command (lets say
> > > "shutdown") to
> > > > > > > agent?.
> > > > > > > echo "shutdown" | socat
> > > > > > > /var/lib/libvirt/qemu/channel/target/domain-20-
> > > > > > > win7_32bit/com.redhat.kvm-vdi.0  -
> > > > > > > Does not seem to work
> > > > > > > Thank you for your help.
> > > > > > > ___
> > > > > > > Users mailing list
> > > > > > > Users@ovirt.org 
> > > > > > > http://lists.ovirt.org/mailman/listinfo/users 
> > > > > > > 
> > > > > >
> > > > > 

Re: [ovirt-users] Ovirt Java SDK access to 'next run' configuration

[Juan Hernández]

On 07/08/2016 04:09 PM, Sebastien Fuchs wrote:
> Hi,
> 
> I'm developping (in JAVA) an automatic configuration manager to modify
> memory and cpu allocation (cpushares for the moment) updated on a
> calendar basis. It will also be used as a kind of enforcer/elastic
> scheduler on top of the ovirt policy scheduler.
> 
> Because oVirt is not yet able to update memory and cpushares on live
> guests like XenServer, my configurator needs to know the running config
> and the next_run config as well, and force directly the config on live
> guests (with virsh schedinfo --live arg ? ).
> 
> Unfortunately, the Host.getVMs().getById( "uuid" ) method returns only
> the running config so there's no way I can check if the future config is
> setup.
> 
> Any suggestion?
> 

Version 3 of the SDK doesn't support GET parameters, unfortunately. If
you are using version 4 of the engine then you may consider using
version 4 of the SDK, which does support them:

---8<---
import static org.ovirt.engine.sdk4.ConnectionBuilder.connection;

import org.ovirt.engine.sdk4.Connection;
import org.ovirt.engine.sdk4.services.VmService;
import org.ovirt.engine.sdk4.services.VmsService;
import org.ovirt.engine.sdk4.types.Vm;

// This example will connect to the server and start a virtual machine:
public class GetVmNextRun {
public static void main(String[] args) throws Exception {
// Create the connection to the server:
Connection connection = connection()
.url("https://engine41.example.com/ovirt-engine/api;)
.user("admin@internal")
.password("...")
.trustStoreFile("truststore.jks")
.build();

// Get the reference to the "vms" service:
VmsService vmsService = connection.systemService().vmsService();

// Find the virtual machine (we need this in order to find
// the identifier of the virtual machine given its
// name):
Vm vm = vmsService.list()
.search("name=myvm")
.send()
.vms()
.get(0);

// Locate the service that manages the virtual machine:
VmService vmService = vmsService.vmService(vm.id());

// Call the "get" method using the "next_run" parameter to
//  retrieve the configuration of the virtual machine that
// will be used the next time it is started:
vm = vmService.get()
.nextRun(true)
.send()
.vm();

// Print some details of the virtual machine:
System.out.printf("cpu shares: %s", vm.cpuShares());

// Close the connection to the server:
connection.close();
}
}
--->8---

If this isn't an alternative for you, then please open a bug requesting
that this support is added to version 3 of the SDK.

-- 
Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta
3ºD, 28016 Madrid, Spain
Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Is it possible to disable qxl video?

[Karli Sjöberg]

Den 11 jul 2016 11:37 fm skrev Arman Khalatyan :
>
> I just testing several GPUs with pci-passthrough: GTX630, Tesla 2050 and 
> FX5800.
> None of them I got running with opengl/direct rendering inside the virtual 
> machine.
> I was thinking something to do with qxl driver, but after blacklisting it in 
> the VMs kernel nothing was changed.
> The VMs Xorg claiming always no display found even if I configure it with 
> headless option: nvidia-xconfig -a --use-display-device=None 
> --virtual=1280x1024
> But with nvidia-smi I can see the GPU status, and I can run all cuda tests 
> where opengl/X11 is not involved.
> My test system is CentOS 7 with ovirt 4.
> BTW If I clone VM which was not running, to real host on bare metal, 
> everything is running as expecting.

Don't remember If this was mentioned but have you tried doing the same thing 
but with virt-manager on a standalone host, just to rule out oVirt from the 
equation?

/K
>
>
>
>
>
>
>
> ***
>
>  Dr. Arman Khalatyan  eScience -SuperComputing
>  Leibniz-Institut für Astrophysik Potsdam (AIP)
>  An der Sternwarte 16, 14482 Potsdam, Germany
>
> ***
>
> On Mon, Jul 11, 2016 at 9:06 AM, Martin Polednik  wrote:
>>
>> On 08/07/16 11:29 +0200, Michal Skrivanek wrote:
>>>
>>>
 On 06 Jul 2016, at 14:06, Francesco Romani  wrote:


 From: "Arman Khalatyan" 
 To: "users" 
 Sent: Monday, July 4, 2016 11:52:24 AM
 Subject: [ovirt-users] Is it possible to disable qxl video?


 Hi,
 I am doing PCI Passthrough for GPUs.
 Is it possible somehow to disable/remove default video qxl?
 thanks,
 Arman,.
 Hi,

 The 4.0 Vdsm allows you to run a headless VM, meaning a VM without graphic 
 device/frontend.
 Not sure Engine allows you that however.
>>>
>>>
>>> no it doesn’t
>>
>>
>> Even if engine allowed that, it may not be the correct solution.
>>
>> Running headless with PCI passthrough is considered primary VGA
>> passthrough[1]. Using primary VGA passthrough without OVMF could cause
>> (will cause) quite a bit of headaches.
>>
>> If you really want to try that, I assume using before_vm_start hook to
>> remove the video device should be enough.
>>
>> [1] http://wiki.xenproject.org/wiki/Xen_VGA_Passthrough - it's
>> possible to read about primary and secondary passthrough between the
>> lines
>>
>>> However, if QXL is the problem (why is that so?) then you can switch to 
>>> VGA(or CIRRUS if this is still 3.6)
>>>
 I'm afraid you will need to write a Vdsm hook.

 There could be simpler solutions depending on the Engine

 Bests,

 --
 Francesco Romani
 RedHat Engineering Virtualization R & D
 Phone: 8261328
 IRC: fromani
 ___
 Users mailing list
 Users@ovirt.org 
 http://lists.ovirt.org/mailman/listinfo/users 
 
>>
>>
>>> ___
>>> Users mailing list
>>> Users@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Is it possible to disable qxl video?

[Martin Polednik]

On 11/07/16 09:46 +, Karli Sjöberg wrote:


Den 11 jul 2016 11:37 fm skrev Arman Khalatyan :


I just testing several GPUs with pci-passthrough: GTX630, Tesla 2050 and FX5800.
None of them I got running with opengl/direct rendering inside the virtual 
machine.
I was thinking something to do with qxl driver, but after blacklisting it in 
the VMs kernel nothing was changed.
The VMs Xorg claiming always no display found even if I configure it with 
headless option: nvidia-xconfig -a --use-display-device=None --virtual=1280x1024
But with nvidia-smi I can see the GPU status, and I can run all cuda tests 
where opengl/X11 is not involved.
My test system is CentOS 7 with ovirt 4.
BTW If I clone VM which was not running, to real host on bare metal, everything 
is running as expecting.


Don't remember If this was mentioned but have you tried doing the same thing 
but with virt-manager on a standalone host, just to rule out oVirt from the 
equation?


Also, the xorg must be setup to use the VFIO GPU. There is BusID
option in device section that must point to the guest address of the
GPU. I'm not sure if you've done that (and I'm quite sure it's missing
on the wiki, noted).

[in the guest]
$ lspci | grep VGA
03:00.0 VGA compatible controller: NVIDIA Corporation GM107GL [Quadro
K2200] (rev a2)

and  using the address, add device section to /etc/X11/xorg.conf

Section "Device"
   Identifier "Device0"
   Driver "nvidia"
   VendorName "NVIDIA Corporation"
   BusID  "PCI:3:0:0"
EndSection

That should allow xorg to use the assigned GPU.

mpolednik


/K








***

 Dr. Arman Khalatyan  eScience -SuperComputing
 Leibniz-Institut für Astrophysik Potsdam (AIP)
 An der Sternwarte 16, 14482 Potsdam, Germany

***

On Mon, Jul 11, 2016 at 9:06 AM, Martin Polednik  wrote:


On 08/07/16 11:29 +0200, Michal Skrivanek wrote:




On 06 Jul 2016, at 14:06, Francesco Romani  wrote:


From: "Arman Khalatyan" 
To: "users" 
Sent: Monday, July 4, 2016 11:52:24 AM
Subject: [ovirt-users] Is it possible to disable qxl video?


Hi,
I am doing PCI Passthrough for GPUs.
Is it possible somehow to disable/remove default video qxl?
thanks,
Arman,.
Hi,

The 4.0 Vdsm allows you to run a headless VM, meaning a VM without graphic 
device/frontend.
Not sure Engine allows you that however.



no it doesn’t



Even if engine allowed that, it may not be the correct solution.

Running headless with PCI passthrough is considered primary VGA
passthrough[1]. Using primary VGA passthrough without OVMF could cause
(will cause) quite a bit of headaches.

If you really want to try that, I assume using before_vm_start hook to
remove the video device should be enough.

[1] http://wiki.xenproject.org/wiki/Xen_VGA_Passthrough - it's
possible to read about primary and secondary passthrough between the
lines


However, if QXL is the problem (why is that so?) then you can switch to VGA(or 
CIRRUS if this is still 3.6)


I'm afraid you will need to write a Vdsm hook.

There could be simpler solutions depending on the Engine

Bests,

--
Francesco Romani
RedHat Engineering Virtualization R & D
Phone: 8261328
IRC: fromani
___
Users mailing list
Users@ovirt.org 
http://lists.ovirt.org/mailman/listinfo/users 





___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users






___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Is it possible to disable qxl video?

[Arman Khalatyan]

I just testing several GPUs with pci-passthrough: GTX630, Tesla 2050 and
FX5800.
None of them I got running with opengl/direct rendering inside the virtual
machine.
I was thinking something to do with qxl driver, but after blacklisting it
in the VMs kernel nothing was changed.
The VMs Xorg claiming always no display found even if I configure it with
headless option: nvidia-xconfig -a --use-display-device=None
--virtual=1280x1024
But with nvidia-smi I can see the GPU status, and I can run all cuda tests
where opengl/X11 is not involved.
My test system is CentOS 7 with ovirt 4.
BTW If I clone VM which was not running, to real host on bare metal,
everything is running as expecting.







***

 Dr. Arman Khalatyan  eScience -SuperComputing
 Leibniz-Institut für Astrophysik Potsdam (AIP)
 An der Sternwarte 16, 14482 Potsdam, Germany

***

On Mon, Jul 11, 2016 at 9:06 AM, Martin Polednik 
wrote:

> On 08/07/16 11:29 +0200, Michal Skrivanek wrote:
>
>>
>> On 06 Jul 2016, at 14:06, Francesco Romani  wrote:
>>>
>>>
>>> From: "Arman Khalatyan" 
>>> To: "users" 
>>> Sent: Monday, July 4, 2016 11:52:24 AM
>>> Subject: [ovirt-users] Is it possible to disable qxl video?
>>>
>>>
>>> Hi,
>>> I am doing PCI Passthrough for GPUs.
>>> Is it possible somehow to disable/remove default video qxl?
>>> thanks,
>>> Arman,.
>>> Hi,
>>>
>>> The 4.0 Vdsm allows you to run a headless VM, meaning a VM without
>>> graphic device/frontend.
>>> Not sure Engine allows you that however.
>>>
>>
>> no it doesn’t
>>
>
> Even if engine allowed that, it may not be the correct solution.
>
> Running headless with PCI passthrough is considered primary VGA
> passthrough[1]. Using primary VGA passthrough without OVMF could cause
> (will cause) quite a bit of headaches.
>
> If you really want to try that, I assume using before_vm_start hook to
> remove the video device should be enough.
>
> [1] http://wiki.xenproject.org/wiki/Xen_VGA_Passthrough - it's
> possible to read about primary and secondary passthrough between the
> lines
>
> However, if QXL is the problem (why is that so?) then you can switch to
>> VGA(or CIRRUS if this is still 3.6)
>>
>> I'm afraid you will need to write a Vdsm hook.
>>>
>>> There could be simpler solutions depending on the Engine
>>>
>>> Bests,
>>>
>>> --
>>> Francesco Romani
>>> RedHat Engineering Virtualization R & D
>>> Phone: 8261328
>>> IRC: fromani
>>> ___
>>> Users mailing list
>>> Users@ovirt.org 
>>> http://lists.ovirt.org/mailman/listinfo/users <
>>> http://lists.ovirt.org/mailman/listinfo/users>
>>>
>>
> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Only 1 VM migrated to another host after setting a host to maintenance mode - another VM didn't

[Roy Golan]

This is by design. The engine VM is migrated only manually (from the
engine) or automatically by the HA agent on the host in case of failures
detected in the infra.

On 7 July 2016 at 11:34, Wee Sritippho  wrote:

> Hi, I was trying to upgrade the hosted-engine environment from v3.6.5 to
> v3.6.7.
>
> Upgrading host01 and host02 is OK. But when I was trying to put host03
> (which has the engine VM in it) to maintenance mode, the process stuck -
> only the engine VM was migrated, another ordinary VM didn't.
>
> I also noted that a lot of "Moving Host xxx to Maintenance" task was
> gradually created but didn't finished.
>
> Here are the log files:
> https://app.box.com/s/ibi8pjxyxv4khek2menho1orumstek8y
>
> --
> Wee
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] VMs freeze during vm-host reboot

[Sahina Bose]

Did you see any errors in the gluster mount logs during the time when 
the VMs were frozen ( I assume the I/O not responding during this time?) 
. There have been bugs fixed around concurrent I/O on gluster volume and 
vm's pausing in 3.7.12 - the mount logs can tell us if you ran into 
similar issue.


On 07/08/2016 03:58 PM, bertjan wrote:

Hi Michal,

That's right. I put it in maintenance mode, so there were no VMs.

The frozen VMs were on the other hosts. That's wat makes it strange and
why it doesn't give me a good feeling. When someone can say  'I know the
issue and it is fixed with gluster version 3.7.12', I would feel more reassured
about it...

Regards,

Bertjan

On Fri, Jul 08, 2016 at 12:23:21PM +0200, Michal Skrivanek wrote:

On 08 Jul 2016, at 12:06, bertjan  wrote:

Hi,

I have a 3-node CentOS7 based oVirt+replica-3 gluster environment with an engine
on dedicated hardware.

After putting the first vm-host into maintenance mode to update it from 
vdsm-4.17.28-1
to vdsm-4.17.32-0 and from glusterfs-3.7.11-1 to glusterfs-3.7.12-2 (among 
others),
random VMs froze (not pauzed. oVirt showed them as 'up') until the update was 
done and
the vm-host was rebooted and active again.

I suppose the host you were updating at that time had no running VMs, right?
If so, then indeed perhaps a gluster issue


After all the vm-hosts were upgraded, I never experienced the problem again.
Can this be a bug, fixed with the upgrade to glusterfs-3.7.12-2?

Has anyone experienced the same problem?

Thanks in advance! (next week I'm not able to check my e-mail, so response can 
be delayed).

Regards,

Bertjan



--

De informatie opgenomen in dit bericht kan vertrouwelijk zijn en is
uitsluitend bestemd voor de geadresseerde. Indien u dit bericht onterecht
ontvangt, wordt u verzocht de inhoud niet te gebruiken en de afzender direct
te informeren door het bericht te retourneren. Het Universitair Medisch
Centrum Utrecht is een publiekrechtelijke rechtspersoon in de zin van de W.H.W.
(Wet Hoger Onderwijs en Wetenschappelijk Onderzoek) en staat geregistreerd bij
de Kamer van Koophandel voor Midden-Nederland onder nr. 30244197.

Denk s.v.p aan het milieu voor u deze e-mail afdrukt.

--

This message may contain confidential information and is intended exclusively
for the addressee. If you receive this message unintentionally, please do not
use the contents but notify the sender immediately by return e-mail. University
Medical Center Utrecht is a legal person by public law and is registered at
the Chamber of Commerce for Midden-Nederland under no. 30244197.

Please consider the environment before printing this e-mail.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Is it possible to disable qxl video?

[Martin Polednik]

On 08/07/16 11:29 +0200, Michal Skrivanek wrote:



On 06 Jul 2016, at 14:06, Francesco Romani  wrote:


From: "Arman Khalatyan" 
To: "users" 
Sent: Monday, July 4, 2016 11:52:24 AM
Subject: [ovirt-users] Is it possible to disable qxl video?


Hi,
I am doing PCI Passthrough for GPUs.
Is it possible somehow to disable/remove default video qxl?
thanks,
Arman,.
Hi,

The 4.0 Vdsm allows you to run a headless VM, meaning a VM without graphic 
device/frontend.
Not sure Engine allows you that however.


no it doesn’t


Even if engine allowed that, it may not be the correct solution.

Running headless with PCI passthrough is considered primary VGA
passthrough[1]. Using primary VGA passthrough without OVMF could cause
(will cause) quite a bit of headaches.

If you really want to try that, I assume using before_vm_start hook to
remove the video device should be enough.

[1] http://wiki.xenproject.org/wiki/Xen_VGA_Passthrough - it's
possible to read about primary and secondary passthrough between the
lines


However, if QXL is the problem (why is that so?) then you can switch to VGA(or 
CIRRUS if this is still 3.6)


I'm afraid you will need to write a Vdsm hook.

There could be simpler solutions depending on the Engine

Bests,

--
Francesco Romani
RedHat Engineering Virtualization R & D
Phone: 8261328
IRC: fromani
___
Users mailing list
Users@ovirt.org 
http://lists.ovirt.org/mailman/listinfo/users 




___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] No hosted Engine VM in portal after migrating

[Roy Golan]

On 10 July 2016 at 17:52, Matt .  wrote:

> Or add a new cluster it seems.
>

The import has 2 conditions, 1. The Data center must be active (i.e it must
have a Master domain attached).  2. Your DC should be level 3.5 at least.
The  the Storage Domain and the VM are imported.


> 2016-07-10 11:25 GMT+02:00 Yaniv Dary :
> > You need to add one storage to make the import trigger.
> >
> > Yaniv Dary
> > Technical Product Manager
> > Red Hat Israel Ltd.
> > 34 Jerusalem Road
> > Building A, 4th floor
> > Ra'anana, Israel 4350109
> >
> > Tel : +972 (9) 7692306
> > 8272306
> > Email: yd...@redhat.com
> > IRC : ydary
> >
> >
> > On Fri, Jul 8, 2016 at 8:43 PM, Matt .  wrote:
> >>
> >> By adding a new cluster the Hosted Engine was imported also...
> >>
> >> There seem to be some issues with changing the clusters from 3.6 to
> >> 4.0 and adding new cluster to make that happen the HostedEngine was
> >> added also.
> >>
> >> 2016-07-08 9:43 GMT+02:00 Simone Tiraboschi :
> >> > On Fri, Jul 8, 2016 at 9:25 AM, Matt . 
> wrote:
> >> >> Hi,
> >> >>
> >> >> I see on the engine gthe following message:
> >> >>
> >> >> 2016-07-08 09:24:24,986 INFO
> >> >> [org.ovirt.engine.core.bll.exportimport.ImportVmCommand]
> >> >> (org.ovirt.thread.pool-8-thread-5) [49c1c8c1] Lock Acquired to object
> >> >>
> 'EngineLock:{exclusiveLocks='[5576ec24-112e-4995-89f8-57e40c43cc5a= >> >> ACTION_TYPE_FAILED_VM_IS_BEING_IMPORTED$VmName HostedEngine>,
> >> >> HostedEngine=]',
> >> >> sharedLocks='[5576ec24-112e-4995-89f8-57e40c43cc5a= >> >> ACTION_TYPE_FAILED_VM_IS_BEING_IMPORTED$VmName HostedEngine>]'}'
> >> >>
> >> >> The issue is that there is no entry as VM in the database.
> >> >
> >> > Adding Roy here.
> >> >
> >> >> What should I check more ?
> >> >>
> >> >> Thanks,
> >> >>
> >> >> Matt
> >> >>
> >> >> 2016-07-07 23:26 GMT+02:00 Matt . :
> >> >>> The storage domain is there, the host-engine is just not being
> added,
> >> >>> also not after some time waiting.
> >> >>>
> >> >>> 2016-07-07 14:15 GMT+02:00 Simone Tiraboschi :
> >>  On Thu, Jul 7, 2016 at 1:34 PM, Matt . 
> >>  wrote:
> >> > Hi,
> >> >
> >> > I did a successfull migration to hosted engine and noticed there
> is
> >> > no
> >> > HostedEngine VM in the portal.
> >> 
> >>  Do you just miss the hosted-engine VM or also the whole
> hosted-engine
> >>  storage domain?
> >> 
> >> > In earlier tests it showed up so I wonder if I can import it in
> some
> >> > way so it exists in the portal.
> >> >
> >> > I used this migration way which earlier added the hosted engine
> and
> >> > stayed in the portal also after restoring the old backup.
> >> >
> >> >
> >> >
> http://www.ovirt.org/develop/developer-guide/engine/migrate-to-hosted-engine/
> >> >
> >> > Thanks,
> >> >
> >> > Matt
> >> > ___
> >> > Users mailing list
> >> > Users@ovirt.org
> >> > http://lists.ovirt.org/mailman/listinfo/users
> >> >> ___
> >> >> Users mailing list
> >> >> Users@ovirt.org
> >> >> http://lists.ovirt.org/mailman/listinfo/users
> >> ___
> >> Users mailing list
> >> Users@ovirt.org
> >> http://lists.ovirt.org/mailman/listinfo/users
> >
> >
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users