date:20161108

Re: [ovirt-users] Uploading an image with qcow2 compat 1.1 is unsupported for storage format type V3

2016-11-08 Thread Nir Soffer

On Tue, Nov 8, 2016 at 12:58 PM, Amit Aviram  wrote:
> Hi
> Nathanaël.
>
> On Mon, Nov 7, 2016 at 5:02 PM,
> Nathanaël Blanchet  wrote:
>>
>> Hi all, how can I get informations about supported formats with the image
>> upload feature ?
>
>
> Actually, supported QCOW formats are derived from the ovirt storage versions
> (V3, etc..) of a DC, and the upload flow just restricts the user so the
> supplied image that is being uploaded will be supported in the DC that owns
> the target storage domain.
>
> So basically, the DC specifies the supported formats, not the upload
> feature.
>
>>
>> All my domain storages are v3, does it exist v4?

Exist in upstream. You can install a development version if you like to
play with this on testing environment.

> If yes, how can I upgrade
>> them to a superior format?

If you don't care about backward compatibility in 4.0, you can configure
the system to use format 1.1 by like this:

[irs]
# Recent qemu-img supports two incompatible qcow2 versions. We use
# 0.10 format by default so hosts with older qemu can consume images
# created by newer versions. See https://bugzilla.redhat.com/1139707
# (supported versions: 0.10, 1.1)
qcow2_compat = 1.1

Note that this will break image upload, because engine allows only 0.10
images. We don't have similar configuration in engine.

> V4 is about to be introduced (targeted to 4.1), and it will support QCOW2
> version 1.1.
> You will be able to upgrade your DCs to this version easily when it will be
> available.
>
>>
>> Do I need to convert my non compatible 1.1 qcow2 appliance to an other
>> format?

Yes, you can convert 1.1 image to 0.10 using:

qemu-img amend -o compat=1.1 /path/to/image

In 4.1, when using storage domain version 4:
- new disk will use format 1.1
- you will be able to upload both 0.10 and 1.1 images
- you will be able to convert old images from 0.10 to 1.1

Nir

>>
>> This is what I found :
>> https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Virtualization_Deployment_and_Administration_Guide/sect-Using_qemu_img-Supported_qemu_img_formats.html
>>
>>
>> Thank you
>>
>>
>> --
>> Nathanaël Blanchet
>>
>> Supervision réseau
>> Pôle Infrastrutures Informatiques
>> 227 avenue Professeur-Jean-Louis-Viala
>> 34193 MONTPELLIER CEDEX 5
>> Tél. 33 (0)4 67 54 84 55
>> Fax  33 (0)4 67 54 84 14
>> blanc...@abes.fr
>>
>> ___
>> 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

[ovirt-users] Import from OVA with encrypted root

2016-11-08 Thread Chris Adams

I'm trying to import an appliance image from a vendor.  It is based on
Debian.  For some added level of "security" I guess, the vendor disk
image has the root filesystem encrypted (and then the key is in the
initrd - I know that's no real added security, but... whatever).

Trying to import this VM into oVirt fails because it can't find/mount
the root filesystem.

Is there any way around this?

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

Re: [ovirt-users] IP address doesn't appear in the host network interfaces tab

2016-11-08 Thread Dan Kenigsberg

On Tue, Nov 08, 2016 at 04:03:27PM +0100, Nathanaël Blanchet wrote:
> Hi all,
> 
> I try to change my migration network from one to an other. To do such a
> thing I assigned an IP  on the new vlan fo r each of my hosts by dhcp.but
> when changing the migration network at the cluster level, engine complains
> that my host doesn't have IP.
> 
> I tried the "Sync all networks tab" to refresh, but nothing happens. Howver
> IP in the vlan do exist on the host.
> 
> The only workaround to do this is to restart vdsmd and then, IP appear and I
> can go further.
> 
> Can it be considered as a bug?

How did you configure that vlan address on each of your hosts? Via the
Setup Host Network dialog?

Quite often, we have a race where networks configured with dhcp do not
report their acquired ip address to Engine. This is to be solved by

Bug 1240719 - [RFE] - Send an events to engine upon network changes

but until then - by clicking the "Refresh Capabilities" button, moving
the host to maintenance and back, or stopping-waiting-restarting Vdsm.

If "Refresh Capabilities" solves your issue as well, you're seeing the
problem I'm referring to.

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

[ovirt-users] [HELP] unmapping a deleted storage domain triggers crash ovirt

2016-11-08 Thread Andrea Ghelardi

Hello people,

something's not right in my ovirt infrastructure.
I currently have two different ovirt installation:
Ovirt3: 7 hosts linked to Compellent iscsi storage running ovirt 3.5.6
Ovirt4: 4 hosts linked to (same) Compellent iscsi storage running ovirt 4.0.4

I'm currently moving my guests from ovirt3 to ovirt4.
Since iscsi storage is linked to both installations, my high level approach is:

1)  Shutdown VM in ovirt3.

2)  Maintenance + detach + remove VM storage in ovirt3

3)  Change LUN mapping via iscsi storage manager from ovirt3 to ovirt4

4)  Import storage in ovirt4

5)  Import VM in ovirt4

6)  Run and cheers with high grade liquor. GOTO step 1 for different VM.

Now, as soon as I perform step 3 (remove mappings from LUN), ovirt3 goes crazy 
and eventually forces me to reboot all hosts one by one.
I tried different low level approaches to unmap LUN mpath'ed from hosts with 
inconsistent results.
A notable error log extract is:
Nov  8 15:30:52 sovana vdsm root ERROR Process failed with rc=1 out='\nudevadm 
settle - timeout of 5 seconds reached, the event queue contains:\n  
/sys/devices/virtual/block/dm-39 (8603)\n  /sys/devices/virtual/block/dm-39 
(8604)\n  /sys
/devices/virtual/block/dm-39 (8605)\n  /sys/devices/virtual/block/dm-39 
(8606)\n  /sys/devices/virtual/block/dm-39 (8607)\n  
/sys/devices/virtual/block/dm-39 (8608)\n  /sys/devices/virtual/block/dm-39 
(8609)\n  /sys/devices/virtual/block
/dm-39 (8610)\n  /sys/devices/virtual/block/dm-39 (8611)\n  
/sys/devices/virtual/block/dm-39 (8612)\n  /sys/devices/virtual/block/dm-39 
(8613)\n  /sys/devices/virtual/block/dm-39 (8614)\n  
/sys/devices/virtual/block/dm-39 (8615)\n  /sys/
devices/virtual/block/dm-39 (8616)\n  /sys/devices/virtual/block/dm-39 (8617)\n 
 /sys/devices/virtual/block/dm-39 (8618)\n  /sys/devices/virtual/block/dm-39 
(8619)\n  /sys/devices/virtual/block/dm-39 (8620)\n  /sys/devices/virtual/block/
dm-39 (8621)\n  /sys/devices/virtual/block/dm-39 (8622)\n  
/sys/devices/virtual/block/dm-39 (8623)\n  /sys/devices/virtual/block/dm-39 
(8624)\n  /sys/devices/virtual/block/dm-39 (8625)\n  
/sys/devices/virtual/block/dm-39 (8626)\n  /sys/d
evices/virtual/block/dm-39 (8627)\n  /sys/devices/virtual/block/dm-39 (8628)\n  
/sys/devices/virtual/block/dm-39 (8629)\n  /sys/devices/virtual/block/dm-39 
(8630)\n  /sys/devices/virtual/block/dm-39 (8631)\n  
/sys/devices/virtual/block/d
m-39 (8632)\n  /sys/devices/virtual/block/dm-39 (8633)\n  
/sys/devices/virtual/block/dm-39 (8634)\n  /sys/devices/virtual/block/dm-39 
(8635)\n  /sys/devices/virtual/block/dm-39 (8636)\n  
/sys/devices/virtual/block/dm-39 (8637)\n  /sys/de
vices/virtual/block/dm-39 (8638)\n  /sys/devices/virtual/block/dm-39 (8639)\n  
/sys/devices/virtual/block/dm-39 (8640)\n  /sys/devices/virtual/block/dm-39 
(8641)\n  /sys/devices/virtual/block/dm-39 (8642)\n  
/sys/devices/virtual/block/dm
-39 (8643)\n  /sys/devices/virtual/block/dm-39 (8644)\n  
/sys/devices/virtual/block/dm-39 (8645)\n  /sys/devices/virtual/block/dm-39 
(8646)\n  /sys/devices/virtual/block/d

I really need your help to sort this out as I'm actually blocked in my task.

Why mapping changes triggers ovirt crash on a storage which ovirt should not 
care about?
Thanks


Andrea Ghelardi

+39 050 2203 71 | www.iongroup.com | 
a.ghela...@iontrading.com
Via San Martino, 52 - 56125 Pisa - ITALY

This email and any attachments may contain information which is confidential 
and/or privileged. The information is intended exclusively for the addressee 
and the views expressed may not be official policy, but the personal views of 
the originator. If you are not the intended recipient, be aware that any 
disclosure, copying, distribution or use of the contents is prohibited. If you 
have received this email and any file transmitted with it in error, please 
notify the sender by telephone or return email immediately and delete the 
material from your computer. Internet communications are not secure and ION 
Trading is not responsible for their abuse by third parties, nor for any 
alteration or corruption in transmission, nor for any damage or loss caused by 
any virus or other defect. ION Trading accepts no liability or responsibility 
arising out of or in any way connected to this email.

[iON_HBlu_small]
Automation through innovation

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

Re: [ovirt-users] Can't upload qcow2 images via web UI

2016-11-08 Thread Amit Aviram

On Tue, Nov 8, 2016 at 12:50 PM, วีร์ ศรีทิพโพธิ์ 
wrote:

>
> On Nov 8, 2559 BE, at 16:50, Amit Aviram  wrote:
>
> Hi Wee.
> Looking in your logs, it looks like "ovirt-imageio-daemon" service, which
> runs in the oVirt's host (ovirt03.forest.go.th), doesn't accept the
> requests as should. Please, log into this host and restart this service,
> running:
>
> *service ovirt-imageio-daemon restart*
>
>
> And try upload.
>
> If this won't work, please send us the output of "journalctl -xeu
> ovirt-imageio-daemon" from ovirt03.forest.go.th.
>
> Thanks, Amit.
>
>
> Hi Amit,
>
> I restarted ‘overt-imageio-daemon’ service in
> 
> ovirt03.forest.go.th but still can’t upload. Here is the output from
> ‘journalctl -xeu overt-imageio-daemon’ command in ovirt03.forest.go.th:
>
>
>
> Thank you,
> Wee.
>
>
Indeed the requests from ovirt-imageio-proxy doesn't get to
ovirt-imageio-daemon. you can see in the proxy logs that a "No route to
host" is logged.
Initially our setup opens up the needed ports in iptables in order to allow
this connection, but if it was changed somehow it will break the upload
flow. Can you make sure that port 54322 is open for input requests in

ovirt03.forest.go.th, and also open for output request where the proxy
resides? Or whatever reason for the host not be reachable?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] IP address doesn't appear in the host network interfaces tab

2016-11-08 Thread Nathanaël Blanchet


Hi all,

I try to change my migration network from one to an other. To do such a 
thing I assigned an IP  on the new vlan fo r each of my hosts by 
dhcp.but when changing the migration network at the cluster level, 
engine complains that my host doesn't have IP.


I tried the "Sync all networks tab" to refresh, but nothing happens. 
Howver IP in the vlan do exist on the host.


The only workaround to do this is to restart vdsmd and then, IP appear 
and I can go further.


Can it be considered as a bug?


--
Nathanaël Blanchet

Supervision réseau
Pôle Infrastrutures Informatiques
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5   
Tél. 33 (0)4 67 54 84 55
Fax  33 (0)4 67 54 84 14
blanc...@abes.fr

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

Re: [ovirt-users] oVirt 4.04 Can't Migrate VMs - Cryptic "Migration Failed" Error

2016-11-08 Thread Petr Horacek

Hello,

could you please attach outputs of 'ovs-vsctl show' and 'ip link' from
your hosts?

Thanks,
Petr

2016-11-08 6:49 GMT+01:00 Ivan Bulatovic :
> Host configuration looks correct, but it shows that ovirtmgmt network is out
> of sync on the node, so first step should be to select the "Sync Network" in
> networking tab. I would try to delete all other defined networks for the
> cluster (if there are any). If that doesn't work out, another round of
> engine and vdsm logs after a failed migration could help to find the culprit
> for this issue. If there are no other networks defined on the cluster level
> (other than ovirtmgmt) and vdsm still reports that it can't find the ovs
> bridged interface and thus failing the lm, there could be a bug lurking
> somewhere.
>
> On Mon, Nov 7, 2016 at 4:29 PM, Beckman, Daniel
>  wrote:
>>
>> When I created the new cluster and selected 4.0 for Compatibility Mode, I
>> may have initially selected OVS (vs. Legacy) for Switch Type. But since then
>> I had changed it back to Legacy. So could there be something left over from
>> OVS? We definitely want to retain live migration.
>>
>>
>>
>> Here’s my networking configuration files:
>>
>>
>>
>> [root@labvmhostt05 network-scripts]# ls
>>
>> ifcfg-em1  ifcfg-ovirtmgmt  ifdown-eth   ifdown-ovs ifdown-Team
>> ifup-bnep  ifup-isdn   ifup-ppp   ifup-tunnel
>>
>> ifcfg-em2  ifcfg-p5p1   ifdown-ibifdown-postifdown-TeamPort
>> ifup-eth   ifup-ovsifup-routesifup-wireless
>>
>> ifcfg-em3  ifcfg-p5p2   ifdown-ippp  ifdown-ppp ifdown-tunnel
>> ifup-ibifup-plip   ifup-sit   init.ipv6-global
>>
>> ifcfg-em4  ifdown   ifdown-ipv6  ifdown-routes  ifup
>> ifup-ippp  ifup-plusb  ifup-Team  network-functions
>>
>> ifcfg-lo   ifdown-bnep  ifdown-isdn  ifdown-sit ifup-aliases
>> ifup-ipv6  ifup-post   ifup-TeamPort  network-functions-ipv6
>>
>> [root@labvmhostt05 network-scripts]#
>>
>>
>>
>> So “ifcfg-p5p1” is the single 10G Ethernet interface being used:
>>
>> DEVICE=p5p1
>>
>> HWADDR=a0:36:9f:ba:00:3c
>>
>> BRIDGE=ovirtmgmt
>>
>> ONBOOT=yes
>>
>> MTU=1500
>>
>> NM_CONTROLLED=no
>>
>> IPV6INIT=no
>>
>> PEERDNS=no
>>
>>
>>
>> And here is the bridge “ovirtmgmt”:
>>
>> DEVICE=ovirtmgmt
>>
>> TYPE=Bridge
>>
>> DELAY=0
>>
>> STP=off
>>
>> ONBOOT=yes
>>
>> IPADDR=10.50.3.97
>>
>> NETMASK=255.255.255.0
>>
>> GATEWAY=10.50.3.1
>>
>> BOOTPROTO=none
>>
>> MTU=1500
>>
>> DEFROUTE=yes
>>
>> NM_CONTROLLED=no
>>
>> IPV6INIT=no
>>
>> HOTPLUG=no
>>
>> PEERDNS=no
>>
>>
>>
>> The other interfaces are unconfigured (just the default per Anaconda
>> setup), set to ONBOOT=no, and not physically connected to anything. I
>> attached a screenshot of networking within the admin interface. No other
>> interfaces are enabled for anything.
>>
>>
>>
>> Is there some remnant of OVS I need to remove?
>>
>>
>>
>> Thanks,
>>
>> Daniel
>>
>>
>>
>>
>>
>> From: Ivan Bulatovic 
>> Date: Saturday, November 5, 2016 at 3:40 PM
>> To: "Beckman, Daniel" 
>> Cc: Michal Skrivanek , users
>> 
>> Subject: Re: [ovirt-users] oVirt 4.04 Can't Migrate VMs - Cryptic
>> "Migration Failed" Error
>>
>>
>>
>> After digging some more, culprit is that live migration is not yet
>> supported for Open vSwitch network configuration. There is an open bug
>> report to track the progress:
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1362495
>>
>> I haven't had any experience with ovs networking on oVirt, but it should
>> be fairly straightforward to switch from ovs until this is resolved (if lm
>> is a requirement).
>>
>>
>>
>> On Sat, Nov 5, 2016 at 8:50 PM, Ivan Bulatovic 
>> wrote:
>>
>> libvirtError: Cannot get interface MTU on 'vdsmbr_YMv4HqCU': No such
>> device
>>
>> This is the error vdsm reports after a failed migration. You have two
>> bridges defined, ovirtmgmt is up, vdmsbr_YMv4HqCU is down and it looks like
>> a remnant of openvswitch configuration. Can you remove or disable every
>> other interface from Networking tab on affected hosts, and just leave
>> ovirtmgmt bridge and underlying p5p1 interface 10Gbps interface configured?
>> After that, make sure that ovirtmgmt network is tagged as a Live Migration
>> network as shown here:
>>
>> https://www.ovirt.org/develop/release-management/features/network/migration-network/
>>
>> Regarding communication issues I've mentioned, your nodes were
>> unresponsive and I've seen from the engine logs several attempts of fencing
>> the nodes just after the live migration failed to complete.
>>
>>
>>
>> On Fri, Nov 4, 2016 at 8:31 PM, Beckman, Daniel
>>  wrote:
>>
>> I’m attaching vdsm.log from the three hyervisors running oVirt Node 4vdsd,
>> captured just after several failed VM migrations. I had stopped iptables on
>> the hosts, and even stopped firewalld on the engine. Here is a

Re: [ovirt-users] can't import vm from KVM host

2016-11-08 Thread Shahar Havivi

On 08.11.16 10:58, Nelson Lameiras wrote:
> Hi Shahar,
> 
> We try to prioritise vm behaviour predictability over ressources consumption, 
> so "thin provisionning" is not a option for us. "Preallocated" is always 
> selected over default behaviour.
> 
> Nevertheless, while trying to import a KVM vm (from another host), I get a 0 
> disk count on the VM, which means I do not event get to the point where I can 
> chose allocation policy (usually next screen).
> This is true with or without patch proposed below (assuming it has not 
> changed since sept 29).

I assume that this line is failing:
vol = conn.storageVolLookupByPath(disk['alias'])
it may be the reason that the storage is not part of a pool.
(look at pool-xxx commands via virsh)

If it doesn't work it may be related to a different API that we will need to
implement as Tomas suggested in the gerrit patch.

> 
> Can I give you any more information?
> 
> cordialement, regards, 
> Nelson LAMEIRAS 
> 
> Lyra Network 
> Service Projets et Processus 
> Tel : +33 (0) 5 32 09 09 70 
> 109 rue de l’innovation 
> 31670 Labège - France 
> www.lyra-network.com
> 
> - Original Message -
> From: "Shahar Havivi" 
> To: "Nelson Lameiras" , "Tomas 
> Golembiovsky" 
> Cc: "Michal Skrivanek" , users@ovirt.org
> Sent: Monday, November 7, 2016 1:58:34 PM
> Subject: Re: [ovirt-users] can't import vm from KVM host
> 
> Hi Nelson,
> 
> Sorry for the long wait (I was on PTO).
> I just test the patch with the following disk xml:
> 
> 
> 
> 
> 
>  slot='0x07' function='0x0'/>
> 
> 
> I did manage to see the disk with its actual size,
> I was able to import the VM as well when I choose:
> "Allocation Policy": "Preallocated"
> (not the "Thin Provision" as is the default.
> Currently we need to pre allocated kvm block disk and cannot use the thin
> provision (we may need to disable it in the UI).
> 
> Did you try that?
> It may related to the reason that the dev path you have is a /dev/mapper/ and
> this is the reason that libvirt not returning the disk size? (Tomas?)
> 
>  Shahar.
> 
> 
> On 20.10.16 14:10, Nelson Lameiras wrote:
> > Hello,
> > 
> > Any update on this issue?
> > Can I do anything to help?
> > 
> > cordialement, regards, 
> > Nelson LAMEIRAS 
> > 
> > Lyra Network 
> > Service Projets et Processus 
> > Tel : +33 (0) 5 32 09 09 70 
> > 109 rue de l’innovation 
> > 31670 Labège - France 
> > www.lyra-network.com
> > 
> > - Original Message -
> > From: "Michal Skrivanek" 
> > To: "Tomas Golembiovsky" 
> > Cc: "Nelson Lameiras" , users@ovirt.org
> > Sent: Tuesday, October 11, 2016 4:11:36 PM
> > Subject: Re: [ovirt-users] can't import vm from KVM host
> > 
> > > On 11 Oct 2016, at 16:01, Tomáš Golembiovský  wrote:
> > > 
> > > Hi,
> > > 
> > > On Mon, 10 Oct 2016 12:21:47 +0200 (CEST)
> > > Nelson Lameiras  wrote:
> > > 
> > >> hello michal,
> > >> 
> > >> Yes, both paths are correct and working on the source host since the VM 
> > >> starts and works correctly on source host. Nevertheless I have checked 
> > >> with fdisk and mount to assure that these devices are indeed reachable.
> > >> 
> > >> Please understand that my setup is the following:
> > >> source host : KVM (hosting the VM to migrate)
> > >> target host : oVirt 4.0.4 (patched)
> > >> 
> > >> The error "no storage vol with matching path '/dev/sdc'" is returned by 
> > >> the target host script /usr/lib/python2.7/site-packages/vdsm/v2v.py.
> > >> This almost seems normal since the device /dev/sdc is not mounted on 
> > >> target host (where script is running) but only on source host.
> > >> 
> > >> Can this be the source of the error ?
> > > 
> > > To me this looks more like a bug in the engine, not in VDSM.
> > > 
> > > The exception in the VDSM log is OK and it is not fatal. It is actually
> > > to be expected for block devices. VDSM is trying to find out the size of
> > > the disk, but the way it does that is tailored for volumes in storage
> > > pool. But the block device is not a volume in a storage pool and that is
> > > why libvirt complains. We can potentially skip the check for block
> > > devices to avoid error in the log, or provide some other logic of
> > > getting the size.
> > > 
> > > 
> > > But the real problem is this error in engine.log:
> > > 
> > >> 2016-09-29 14:13:48,637 ERROR 
> > >> [org.ovirt.engine.core.bll.GetVmsFromExternalProviderQuery] (default 
> > >> task-30) [] Exception: 
> > >> org.ovirt.engine.core.common.errors.EngineException: EngineException: 
> > >> java.lang.NumberFormatException: null (Failed with error ENGINE and code 
> > >> 5001)
> > > 
> > > We don't send the size (or rather send null value) for the disk and
> > > engine does not like that. I assume engine does not really consider

Re: [ovirt-users] Uploading an image with qcow2 compat 1.1 is unsupported for storage format type V3

2016-11-08 Thread Amit Aviram

Hi

Nathanaël.

On Mon, Nov 7, 2016 at 5:02 PM,

Nathanaël Blanchet  wrote:

> Hi all, how can I get informations about supported formats with the image
> upload feature ?
>

Actually, supported QCOW formats are derived from the ovirt storage
versions (V3, etc..) of a DC, and the upload flow just restricts the user
so the supplied image that is being uploaded will be supported in the DC
that owns the target storage domain.

So basically, the DC specifies the supported formats, not the upload
feature.

> All my domain storages are v3, does it exist v4? If yes, how can I upgrade
> them to a superior format?

V4 is about to be introduced (targeted to 4.1), and it will support QCOW2
version 1.1.
You will be able to upgrade your DCs to this version easily when it will be
available.

> Do I need to convert my non compatible 1.1 qcow2 appliance to an other
> format?
>
> This is what I found : https://access.redhat.com/docu
> mentation/en-US/Red_Hat_Enterprise_Linux/7/html/Virtualizati
> on_Deployment_and_Administration_Guide/sect-Using_qemu_img-
> Supported_qemu_img_formats.html
>
>
> Thank you
>
>
> --
> Nathanaël Blanchet
>
> Supervision réseau
> Pôle Infrastrutures Informatiques
> 227 avenue Professeur-Jean-Louis-Viala
> 34193 MONTPELLIER CEDEX 5
> Tél. 33 (0)4 67 54 84 55
> Fax  33 (0)4 67 54 84 14
> blanc...@abes.fr
>
> ___
> 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] hosted-engine cant access engine appliance

2016-11-08 Thread Simone Tiraboschi

On Tue, Nov 8, 2016 at 11:30 AM, Steffen Nolden <
steffen.nol...@alumni.fh-aachen.de> wrote:

> Attached the VDSM logs from 'hosted-engine --deploy' to 'hosted-engine
> --console'
>
>
Everything seams fine here.
Now I read that you are using a nested env: do you removed mac spoof
filters on the physical host?


> Am 08.11.2016 um 10:43 schrieb Simone Tiraboschi:
>
>
>
> On Tue, Nov 8, 2016 at 9:35 AM, Steffen Nolden  aachen.de> wrote:
>
>> Hello Florian,
>>
>> there is no problem to reslove the FQDN
>>
>
> Can you please attach also VDSM logs fro the relevant time frame?
>
>
>> [nolden@oVirtNode01 ~]$ nslookup oVirtEngine.com
>> Server:192.168.122.1
>> Address:192.168.122.1#53
>>
>> Name:oVirtEngine.com
>> Address: 192.168.122.201
>>
>> The '/etc/hosts' file of each host is configured to resolve the name.
>>
>> I tried it with stopped firewall,
>>
>> [nolden@oVirtNode01 ~]$ sudo systemctl stop firewalld
>> [nolden@oVirtNode01 ~]$ sudo systemctl status firewalld
>> ● firewalld.service - firewalld - dynamic firewall daemon
>>Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled;
>> vendor preset: enabled)
>>Active: inactive (dead) since Di 2016-11-08 09:10:46 CET; 3s ago
>>   Process: 724 ExecStart=/usr/sbin/firewalld --nofork --nopid
>> $FIREWALLD_ARGS (code=exited, status=0/SUCCESS)
>>  Main PID: 724 (code=exited, status=0/SUCCESS)
>>
>> but i got the same error!
>>
>>
>> Am 04.11.2016 um 15:50 schrieb Florian Nolden:
>>
>> Hello Steffen,
>>
>> can your nodes resolve the FQDN "ovirtengine.com" to the hosted engine
>> ip ( nslookup ovirtengine.com) ?
>> If that works have you tried to disable the firewall temporarily?
>>
>> 2016-11-04 14:11 GMT+01:00 Steffen Nolden > en.de>:
>>
>>> Hello,
>>>
>>> i tried to deploy hosted-engine on a testing environment. First of all i
>>> tried to deploy with the option
>>>
>>> "Automatically execute engine-setup on the engine appliance on first
>>> boot (Yes, No)[Yes]? Yes"
>>>
>>> but it got stuck.
>>>
>>> [ INFO  ] Running engine-setup on the appliance
>>> [ ERROR ] Engine setup got stuck on the appliance
>>> [ ERROR ] Failed to execute stage 'Closing up': Engine setup is stalled
>>> on the appliance since 600 seconds ago. Please check its log on the
>>> appliance.
>>> [ INFO  ] Stage: Clean up
>>> [ INFO  ] Generating answer file '/var/lib/ovirt-hosted-engine-
>>> setup/answers/answers-20161104112913.conf'
>>> [ INFO  ] Stage: Pre-termination
>>> [ INFO  ] Stage: Termination
>>> [ ERROR ] Hosted Engine deployment failed: this system is not reliable,
>>> please check the issue,fix and redeploy
>>>   Log file is located at /var/log/ovirt-hosted-engine-s
>>> etup/ovirt-hosted-engine-setup-20161104110104-kyhq1e.log
>>>
>>> Next try i said 'No' and i tried to execute it myself. But i can't
>>> access the engine appliance.
>>>
>>> [nolden@oVirtNode01 ~]$ sudo hosted-engine --console
>>> /usr/share/vdsm/vdsClient.py:33: DeprecationWarning: vdscli uses
>>> xmlrpc. since ovirt 3.6 xmlrpc is deprecated, please use vdsm.jsonrpcvdscli
>>>from vdsm import utils, vdscli, constants
>>> The engine VM is running on this host
>>> Verbunden mit der Domain: HostedEngine
>>> Escape-Zeichen ist ^]
>>> Fehler: Interner Fehler: Charakter-Einheit console0 verwendet nicht
>>> ein PTY
>>>
>>> Additionally i can't ping or access the engine appliance via ssh.
>>>
>>> Did i forget to install a packege or configure something?
>>>
>>> Below my infrastructure and configs. Attached the log file.
>>>
>>>
>>> Thanks for help.
>>>
>>>
>>>
>>> My infrastructure is a nestedVM system:
>>> All systems have nested visualization activated
>>>
>>> HW with LinuxMint x86_64;
>>> - VM with CentOS-7-x86_64; 24GB Ram; 7 cores;
>>> - Nested VM with CentOS-7-x86_64; 12288GB Ram; 4 cores; Hostname:
>>> oVirtNode01.com (192.168.122.101): Here i deploy hosted-engine, Hostname:
>>> oVirtEngine.com (192.168.122.201)
>>> - Nested VM with CentOS-7-x86_64; 4096GB  Ram; 1 cores; Hostname:
>>> oVirtNode02.com (192.168.122.102):
>>> - Nested VM with CentOS-7-x86_64; 4096GB  Ram; 1 cores; Hostname:
>>> oVirtNode03.com (192.168.122.103):
>>>
>>> All three NestedVMs are updated, have installed the ovirt-release40.rpm.
>>> Additional installed:
>>> screen (4.1.0), ovirt-hosted-engine-setup (2.0.2.2), vdsm-gluster
>>> (4.18.13), bridge-utils (1.5),
>>> vdsm (4.18.13), vdsm-cli (4.18.13), glusterfs-server (3.7.16), samba.
>>>
>>> First NestedVM additional installed ovirt-engine-appliance
>>> 4.0-20160928.1.el7.centos
>>>
>>> The three VMs building a glusterfs volume "engine" 3 replica, with the
>>> options...
>>>
>>> Volume Name: engine
>>> Type: Replicate
>>> Volume ID: e92849b7-af3b-4ccd-bd0d-69a5ab3b6214
>>> Status: Started
>>> Number of Bricks: 1 x 3 = 3
>>> Transport-type: tcp
>>> Bricks:
>>> Brick1: oVirtNode01.com:/gluster/engine/brick1
>>> Brick2:

Re: [ovirt-users] Can't upload qcow2 images via web UI

2016-11-08 Thread วีร์ ศรีทิพโพธิ์

On Nov 8, 2559 BE, at 16:50, Amit Aviram  wrote:Hi Wee.Looking in your logs, it looks like "ovirt-imageio-daemon" service, which runs in the oVirt's host (ovirt03.forest.go.th), doesn't accept the requests as should. Please, log into this host and restart this service, running:service ovirt-imageio-daemon restartAnd try upload.If this won't work, please send us the output of "journalctl -xeu ovirt-imageio-daemon" from ovirt03.forest.go.th.Thanks, Amit.Hi Amit,I restarted ‘overt-imageio-daemon’ service in ovirt03.forest.go.th but still can’t upload. Here is the output from ‘journalctl -xeu overt-imageio-daemon’ command in ovirt03.forest.go.th:-- Logs begin at Thu 2016-10-13 19:41:49 ICT, end at Tue 2016-11-08 17:45:20 
ICT. --
Oct 25 15:04:21 ovirt03.forest.go.th systemd[1]: Starting oVirt ImageIO 
Daemon...
-- Subject: Unit ovirt-imageio-daemon.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit ovirt-imageio-daemon.service has begun starting up.
Oct 25 15:04:21 ovirt03.forest.go.th systemd[1]: Started oVirt ImageIO Daemon.
-- Subject: Unit ovirt-imageio-daemon.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit ovirt-imageio-daemon.service has finished starting up.
-- 
-- The start-up result is done.
Nov 08 14:18:51 ovirt03.forest.go.th ovirt-imageio-daemon[13577]: / - - 
[08/Nov/2016 14:18:51] "PUT /tickets/1346bbb2-3b0a-4517-94bb-41959dba996d 
HTTP/1.1" 200 0
Nov 08 14:19:07 ovirt03.forest.go.th ovirt-imageio-daemon[13577]: / - - 
[08/Nov/2016 14:19:07] "DELETE /tickets/1346bbb2-3b0a-4517-94bb-41959dba996d 
HTTP/1.1" 204 0
Nov 08 14:42:07 ovirt03.forest.go.th ovirt-imageio-daemon[13577]: / - - 
[08/Nov/2016 14:42:07] "PUT /tickets/06a78ba7-47e1-45fd-a1eb-58058bb8d1e9 
HTTP/1.1" 200 0
Nov 08 14:42:21 ovirt03.forest.go.th ovirt-imageio-daemon[13577]: / - - 
[08/Nov/2016 14:42:21] "DELETE /tickets/06a78ba7-47e1-45fd-a1eb-58058bb8d1e9 
HTTP/1.1" 204 0
Nov 08 17:39:32 ovirt03.forest.go.th systemd[1]: Stopping oVirt ImageIO 
Daemon...
-- Subject: Unit ovirt-imageio-daemon.service has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit ovirt-imageio-daemon.service has begun shutting down.
Nov 08 17:39:34 ovirt03.forest.go.th systemd[1]: Starting oVirt ImageIO 
Daemon...
-- Subject: Unit ovirt-imageio-daemon.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit ovirt-imageio-daemon.service has begun starting up.
Nov 08 17:39:34 ovirt03.forest.go.th systemd[1]: Started oVirt ImageIO Daemon.
-- Subject: Unit ovirt-imageio-daemon.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit ovirt-imageio-daemon.service has finished starting up.
-- 
-- The start-up result is done.
Nov 08 17:40:30 ovirt03.forest.go.th ovirt-imageio-daemon[7486]: / - - 
[08/Nov/2016 17:40:30] "PUT /tickets/f4659c11-5c4d-4d63-b521-f299149c3fed 
HTTP/1.1" 200 0
Nov 08 17:40:50 ovirt03.forest.go.th ovirt-imageio-daemon[7486]: / - - 
[08/Nov/2016 17:40:50] "DELETE /tickets/f4659c11-5c4d-4d63-b521-f299149c3fed 
HTTP/1.1" 204 0
Thank you,Wee.___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] can't import vm from KVM host

2016-11-08 Thread Nelson Lameiras

Hi Shahar,

We try to prioritise vm behaviour predictability over ressources consumption, 
so "thin provisionning" is not a option for us. "Preallocated" is always 
selected over default behaviour.

Nevertheless, while trying to import a KVM vm (from another host), I get a 0 
disk count on the VM, which means I do not event get to the point where I can 
chose allocation policy (usually next screen).
This is true with or without patch proposed below (assuming it has not changed 
since sept 29).

Can I give you any more information?

cordialement, regards, 
Nelson LAMEIRAS 

Lyra Network 
Service Projets et Processus 
Tel : +33 (0) 5 32 09 09 70 
109 rue de l’innovation 
31670 Labège - France 
www.lyra-network.com

- Original Message -
From: "Shahar Havivi" 
To: "Nelson Lameiras" , "Tomas Golembiovsky" 

Cc: "Michal Skrivanek" , users@ovirt.org
Sent: Monday, November 7, 2016 1:58:34 PM
Subject: Re: [ovirt-users] can't import vm from KVM host

Hi Nelson,

Sorry for the long wait (I was on PTO).
I just test the patch with the following disk xml:








I did manage to see the disk with its actual size,
I was able to import the VM as well when I choose:
"Allocation Policy": "Preallocated"
(not the "Thin Provision" as is the default.
Currently we need to pre allocated kvm block disk and cannot use the thin
provision (we may need to disable it in the UI).

Did you try that?
It may related to the reason that the dev path you have is a /dev/mapper/ and
this is the reason that libvirt not returning the disk size? (Tomas?)

 Shahar.


On 20.10.16 14:10, Nelson Lameiras wrote:
> Hello,
> 
> Any update on this issue?
> Can I do anything to help?
> 
> cordialement, regards, 
> Nelson LAMEIRAS 
> 
> Lyra Network 
> Service Projets et Processus 
> Tel : +33 (0) 5 32 09 09 70 
> 109 rue de l’innovation 
> 31670 Labège - France 
> www.lyra-network.com
> 
> - Original Message -
> From: "Michal Skrivanek" 
> To: "Tomas Golembiovsky" 
> Cc: "Nelson Lameiras" , users@ovirt.org
> Sent: Tuesday, October 11, 2016 4:11:36 PM
> Subject: Re: [ovirt-users] can't import vm from KVM host
> 
> > On 11 Oct 2016, at 16:01, Tomáš Golembiovský  wrote:
> > 
> > Hi,
> > 
> > On Mon, 10 Oct 2016 12:21:47 +0200 (CEST)
> > Nelson Lameiras  wrote:
> > 
> >> hello michal,
> >> 
> >> Yes, both paths are correct and working on the source host since the VM 
> >> starts and works correctly on source host. Nevertheless I have checked 
> >> with fdisk and mount to assure that these devices are indeed reachable.
> >> 
> >> Please understand that my setup is the following:
> >> source host : KVM (hosting the VM to migrate)
> >> target host : oVirt 4.0.4 (patched)
> >> 
> >> The error "no storage vol with matching path '/dev/sdc'" is returned by 
> >> the target host script /usr/lib/python2.7/site-packages/vdsm/v2v.py.
> >> This almost seems normal since the device /dev/sdc is not mounted on 
> >> target host (where script is running) but only on source host.
> >> 
> >> Can this be the source of the error ?
> > 
> > To me this looks more like a bug in the engine, not in VDSM.
> > 
> > The exception in the VDSM log is OK and it is not fatal. It is actually
> > to be expected for block devices. VDSM is trying to find out the size of
> > the disk, but the way it does that is tailored for volumes in storage
> > pool. But the block device is not a volume in a storage pool and that is
> > why libvirt complains. We can potentially skip the check for block
> > devices to avoid error in the log, or provide some other logic of
> > getting the size.
> > 
> > 
> > But the real problem is this error in engine.log:
> > 
> >> 2016-09-29 14:13:48,637 ERROR 
> >> [org.ovirt.engine.core.bll.GetVmsFromExternalProviderQuery] (default 
> >> task-30) [] Exception: 
> >> org.ovirt.engine.core.common.errors.EngineException: EngineException: 
> >> java.lang.NumberFormatException: null (Failed with error ENGINE and code 
> >> 5001)
> > 
> > We don't send the size (or rather send null value) for the disk and
> > engine does not like that. I assume engine does not really consider all
> > the optional VM properties as optional.
> 
> is it really optional in schema?
> even if it is, indeed it’s wrong:)
> 
> the best would be to handle it on v2v.py side first to avoid libvirt err, but 
> i don’t know if we can get that info via libvirt in any other way:/
> 
> > 
> > 
> > 
> >Tomas
> > 
> > -- 
> > Tomáš Golembiovský 
> ___
> 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] Can't upload qcow2 images via web UI

2016-11-08 Thread Amit Aviram

On Tue, Nov 8, 2016 at 10:24 AM, วีร์ ศรีทิพโพธิ์ 
wrote:

> Hi,
>
> I’m trying to transfer one of my VM from KVM to oVirt. My understanding is
> that I can upload its qcow2 to oVirt via ’Upload > Start’ in ‘Disks’ tab of
> the web UI.
>
> However, the upload won’t start. I found this message in the events tab:
>
> "Unable to upload image to disk 2a2e3afc-825b-4022-b402-669731003f3a due
> to a network error. Make sure ovirt-imageio-proxy service is installed and
> configured, and ovirt-engine's certificate is registered as a valid CA in
> the browser."
>
> I already installed the CA from 'https://[engine address]/
> ovirt-engine/services/pki-resource?resource=ca-
> certificate=X509-PEM-CA’ and ovirt-imageio-proxy is still running.
>
> [root@oengine ~]# systemctl status ovirt-imageio-proxy
> *●* ovirt-imageio-proxy.service - oVirt ImageIO Proxy
>Loaded: loaded (/usr/lib/systemd/system/ovirt-imageio-proxy.service;
> enabled; vendor preset: disabled)
>Active: *active (running)* since Tue 2016-11-08 02:06:55 UTC; 5h 28min
> ago
>  Main PID: 503 (ovirt-imageio-p)
>CGroup: /system.slice/ovirt-imageio-proxy.service
>└─503 /usr/bin/python /usr/bin/ovirt-imageio-proxy
>
> Please guide me in this regard,
> Wee.
>
> oVirt Engine Version: 4.0.4.4-1.el7.centos
>
> Logs:
>
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
Hi Wee.
Looking in your logs, it looks like "ovirt-imageio-daemon" service, which
runs in the oVirt's host (ovirt03.forest.go.th), doesn't accept the
requests as should. Please, log into this host and restart this service,
running:

*service ovirt-imageio-daemon restart*


And try upload.

If this won't work, please send us the output of "journalctl -xeu
ovirt-imageio-daemon" from ovirt03.forest.go.th .

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

Re: [ovirt-users] hosted-engine cant access engine appliance

2016-11-08 Thread Simone Tiraboschi

On Tue, Nov 8, 2016 at 9:35 AM, Steffen Nolden <
steffen.nol...@alumni.fh-aachen.de> wrote:

> Hello Florian,
>
> there is no problem to reslove the FQDN
>

Can you please attach also VDSM logs fro the relevant time frame?


> [nolden@oVirtNode01 ~]$ nslookup oVirtEngine.com
> Server:192.168.122.1
> Address:192.168.122.1#53
>
> Name:oVirtEngine.com
> Address: 192.168.122.201
>
> The '/etc/hosts' file of each host is configured to resolve the name.
>
> I tried it with stopped firewall,
>
> [nolden@oVirtNode01 ~]$ sudo systemctl stop firewalld
> [nolden@oVirtNode01 ~]$ sudo systemctl status firewalld
> ● firewalld.service - firewalld - dynamic firewall daemon
>Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled;
> vendor preset: enabled)
>Active: inactive (dead) since Di 2016-11-08 09:10:46 CET; 3s ago
>   Process: 724 ExecStart=/usr/sbin/firewalld --nofork --nopid
> $FIREWALLD_ARGS (code=exited, status=0/SUCCESS)
>  Main PID: 724 (code=exited, status=0/SUCCESS)
>
> but i got the same error!
>
>
> Am 04.11.2016 um 15:50 schrieb Florian Nolden:
>
> Hello Steffen,
>
> can your nodes resolve the FQDN "ovirtengine.com" to the hosted engine
> ip ( nslookup ovirtengine.com) ?
> If that works have you tried to disable the firewall temporarily?
>
> 2016-11-04 14:11 GMT+01:00 Steffen Nolden  aachen.de>:
>
>> Hello,
>>
>> i tried to deploy hosted-engine on a testing environment. First of all i
>> tried to deploy with the option
>>
>> "Automatically execute engine-setup on the engine appliance on first
>> boot (Yes, No)[Yes]? Yes"
>>
>> but it got stuck.
>>
>> [ INFO  ] Running engine-setup on the appliance
>> [ ERROR ] Engine setup got stuck on the appliance
>> [ ERROR ] Failed to execute stage 'Closing up': Engine setup is stalled
>> on the appliance since 600 seconds ago. Please check its log on the
>> appliance.
>> [ INFO  ] Stage: Clean up
>> [ INFO  ] Generating answer file '/var/lib/ovirt-hosted-engine-
>> setup/answers/answers-20161104112913.conf'
>> [ INFO  ] Stage: Pre-termination
>> [ INFO  ] Stage: Termination
>> [ ERROR ] Hosted Engine deployment failed: this system is not reliable,
>> please check the issue,fix and redeploy
>>   Log file is located at /var/log/ovirt-hosted-engine-s
>> etup/ovirt-hosted-engine-setup-20161104110104-kyhq1e.log
>>
>> Next try i said 'No' and i tried to execute it myself. But i can't access
>> the engine appliance.
>>
>> [nolden@oVirtNode01 ~]$ sudo hosted-engine --console
>> /usr/share/vdsm/vdsClient.py:33: DeprecationWarning: vdscli uses
>> xmlrpc. since ovirt 3.6 xmlrpc is deprecated, please use vdsm.jsonrpcvdscli
>>from vdsm import utils, vdscli, constants
>> The engine VM is running on this host
>> Verbunden mit der Domain: HostedEngine
>> Escape-Zeichen ist ^]
>> Fehler: Interner Fehler: Charakter-Einheit console0 verwendet nicht
>> ein PTY
>>
>> Additionally i can't ping or access the engine appliance via ssh.
>>
>> Did i forget to install a packege or configure something?
>>
>> Below my infrastructure and configs. Attached the log file.
>>
>>
>> Thanks for help.
>>
>>
>>
>> My infrastructure is a nestedVM system:
>> All systems have nested visualization activated
>>
>> HW with LinuxMint x86_64;
>> - VM with CentOS-7-x86_64; 24GB Ram; 7 cores;
>> - Nested VM with CentOS-7-x86_64; 12288GB Ram; 4 cores; Hostname:
>> oVirtNode01.com (192.168.122.101): Here i deploy hosted-engine, Hostname:
>> oVirtEngine.com (192.168.122.201)
>> - Nested VM with CentOS-7-x86_64; 4096GB  Ram; 1 cores; Hostname:
>> oVirtNode02.com (192.168.122.102):
>> - Nested VM with CentOS-7-x86_64; 4096GB  Ram; 1 cores; Hostname:
>> oVirtNode03.com (192.168.122.103):
>>
>> All three NestedVMs are updated, have installed the ovirt-release40.rpm.
>> Additional installed:
>> screen (4.1.0), ovirt-hosted-engine-setup (2.0.2.2), vdsm-gluster
>> (4.18.13), bridge-utils (1.5),
>> vdsm (4.18.13), vdsm-cli (4.18.13), glusterfs-server (3.7.16), samba.
>>
>> First NestedVM additional installed ovirt-engine-appliance
>> 4.0-20160928.1.el7.centos
>>
>> The three VMs building a glusterfs volume "engine" 3 replica, with the
>> options...
>>
>> Volume Name: engine
>> Type: Replicate
>> Volume ID: e92849b7-af3b-4ccd-bd0d-69a5ab3b6214
>> Status: Started
>> Number of Bricks: 1 x 3 = 3
>> Transport-type: tcp
>> Bricks:
>> Brick1: oVirtNode01.com:/gluster/engine/brick1
>> Brick2: oVirtNode02.com:/gluster/engine/brick1
>> Brick3: oVirtNode03.com:/gluster/engine/brick1
>> Options Reconfigured:
>> auth.allow: 192.168.122.*
>> storage.owner-gid: 36
>> storage.owner-uid: 36
>> performance.readdir-ahead: on
>>
>> ## Session 1 (hosted-engine deploy without automatically execute
>> engine-setup)
>> [nolden@oVirtNode01 ~]$ sudo hosted-engine --deploy
>> /usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/storage_backends.py:15:
>> DeprecationWarning: vdscli uses xmlrpc. since ovirt 3.6 xmlrpc is
>>

Re: [ovirt-users] Unexpected SSL errors (unexpected eof) in vdsm log?

2016-11-08 Thread Piotr Kliczewski

Derek,

This error may occur from time to time due to [1] but in your listing
it is much to often.
Please share engine and vdsm logs so we could see why.

Thanks,
Piotr


[1] https://bugzilla.redhat.com/1349829

On Mon, Nov 7, 2016 at 7:04 PM, Derek Atkins  wrote:
> Trying to track down some issues I'm seeing and I've noticed a log full
> of SSL Errors:
>
> JsonRpc (StompReactor)::ERROR::2016-11-07 
> 13:03:04,402::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
> reading data: unexpected eof
> JsonRpc (StompReactor)::ERROR::2016-11-07 
> 13:03:08,135::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
> reading data: unexpected eof
> JsonRpc (StompReactor)::ERROR::2016-11-07 
> 13:03:11,896::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
> reading data: unexpected eof
> JsonRpc (StompReactor)::ERROR::2016-11-07 
> 13:03:15,532::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
> reading data: unexpected eof
> JsonRpc (StompReactor)::ERROR::2016-11-07 
> 13:03:29,155::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
> reading data: unexpected eof
> JsonRpc (StompReactor)::ERROR::2016-11-07 
> 13:03:36,418::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
> reading data: unexpected eof
> JsonRpc (StompReactor)::ERROR::2016-11-07 
> 13:03:36,612::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
> reading data: unexpected eof
> JsonRpc (StompReactor)::ERROR::2016-11-07 
> 13:03:40,418::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
> reading data: unexpected eof
> JsonRpc (StompReactor)::ERROR::2016-11-07 
> 13:03:44,158::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
> reading data: unexpected eof
> JsonRpc (StompReactor)::ERROR::2016-11-07 
> 13:03:47,878::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
> reading data: unexpected eof
>
> Any idea where this is coming from, and how to fix it?
>
> -derek
> --
>Derek Atkins 617-623-3745
>de...@ihtfp.com www.ihtfp.com
>Computer and Internet Security Consultant
> ___
> 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

[ovirt-users] About fibre channel storage

2016-11-08 Thread Carlos García Gómez


Hello,
I have a design with of 3 hosts and a storage space on Fiber Channel SAN.

I'm not going to deceive you. I come from the vmware world. (And I do not 
want to compare)


I would like to understand how ovirt/kvm works at level of 
folders/virtual-machine files.

I do not understand how or where this is organized.

For example... How can I access (low level) to san storage datastore in 
order to see files?


Regards,

Carlos 


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

Re: [ovirt-users] Checking VmPool status with Python-SDK?

2016-11-08 Thread Juan Hernández

On 11/08/2016 09:46 AM, nico...@devels.es wrote:
> Hi,
> 
> We're running oVirt 4.0.4.4 with engine python SDK version 3.6.7, and 
> currently we're developing an application that first creates a VmPool 
> and afterwards it updates it. However, sometimes happens that both 
> operations occur at the same time, which results in an oVirt error 
> claiming that a VmPool cannot be updated if there are still pending 
> operations to do.
> 
> We want to control this situation, so we've checked if the VmPool class 
> has a .get_status() method but it seems it doesn't, so I'm asking for 
> alternative ways of handling this. Would it be enough to say a VmPool is 
> not "busy" if all its VMs are not in a blocked state (for example, with 
> a blocked disk due to clonation)?
> 

You are right, there is no "status" attribute in VM pools, the only way
to check if the pool is busy is as you suggest.

I take the opportunity to remind you that we will drop version 3 of the
API and version 3 of the SDKs in oVirt 4.2. Consider switching to versin
4 of the API and version 4 of the SDK. There are documentation and
examples here:

  https://github.com/oVirt/ovirt-engine-sdk/tree/master/sdk
  https://github.com/oVirt/ovirt-engine-sdk/tree/master/sdk/examples

Also, when checking what attributes are available in the API you can use
the documentation that is included in the system itself. For example, to
see the attributes of the "vm_pool" type you can go here:

  https://myengine.example.com/ovirt-engine/api/model#types/vm_pool

-- 
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] RHEVM3.3 java SDK on RHEV3.6

2016-11-08 Thread Juan Hernández

On 11/06/2016 09:39 AM, Tejesh M wrote:
> Hi All,
> 
> I'm facing an issue in invoking Cloudinit while customization in RHEV
> 3.6 using RHEV Java SDK 3.6.
> 
> Below link says we need to explicitly call *use_cloud_init=True*, but
> i'm not sure how to pass this value as parameter while creating VM.
> 
> http://users.ovirt.narkive.com/BGUkanAk/ovirt-users-cloud-init-not-apply-when-v-create-from-api
> 

You need to use version 3.6.0.0 of the SDK, or newer, as that is where
the support for this "use_cloud_init" parameter was added.

The new parameter is part of the "Action" class, so in your code you
need to set it:

  actionData.setUseCloudInit(true);

I take the opportunity to remind you that in version 4.2 of the engine
we will drop support for version 3 of the API and of version 3 of the
SDKs. So, once you migrate to version 4 of the engine consider using
version 4 of the SDK. There is an example of how to use cloud-init with
version 4 of the SDK here:


https://github.com/oVirt/ovirt-engine-sdk-java/blob/master/sdk/src/test/java/org/ovirt/engine/sdk4/examples/StartVmWithCloudInit.java

Note that this won't work with version 3.6 of the engine, for that you
need to keep using version 3 of the SDK.

> 
> _*My Code:*_
> String password = "password"; //"password"
> 
> String templateName = "centos6.7-final";
> String clusterName = "Default";
> String vmName = "testVM3";
> 
> //Prepare the data to create the VM from the template:
> org.ovirt.engine.sdk.entities.Template templateData = new Template();
> templateData.setName(templateName);
> org.ovirt.engine.sdk.entities.Cluster clusterData = new Cluster();
> clusterData.setName(clusterName);
> org.ovirt.engine.sdk.entities.VM vmDataForCreate = new VM();
> vmDataForCreate.setName(vmName);
> vmDataForCreate.setCluster(clusterData);
> vmDataForCreate.setTemplate(templateData);
> 
> api.getVMs().add(vmDataForCreate);
> String state;
> for (;;) {
>  state = api.getVMs().get(vmName).getStatus().getState();
> if ("down".equals(state)) {
>   break;
> }
> Thread.sleep(1000);
> }
> System.out.println("System Status:"+state); 
> org.ovirt.engine.sdk.entities.User userData = new User();
> userData.setUserName("root");
> userData.setPassword(password);
> Users usersData = new Users();
> usersData.getUsers().add(userData);
> CloudInit cloudData = new CloudInit();
> 
> 
> cloudData.setUsers(usersData);
> Host hostData = new Host();
> hostData.setAddress(vmName);
> cloudData.setHost(hostData);
> 
> org.ovirt.engine.sdk.entities.NetworkConfiguration
> networkConfiguration=new NetworkConfiguration();
> 
> networkConfiguration.setNics(new Nics());
> 
> Nics nics = networkConfiguration.getNics();
> nics.getNics().add(createNic("eth0", "STATIC",
> createNetwork("192.168.1.102", "255.255.0.0", "192.168.2.1"), true));
> 
> networkConfiguration.setNics(nics);
> 
> cloudData.setNetworkConfiguration(networkConfiguration);
> 
> Initialization initData = new Initialization();
> 
> initData.setCloudInit(cloudData);
> 
> VM vmDataForStart = new VM();
> vmDataForStart.setInitialization(initData);
> Action actionData = new Action();
> 
> actionData.setVm(vmDataForStart);
> 
> // Send the request to start the VM to the server:
> api.getVMs().get(vmName).start(actionData);
> 
> -- 
> Thanks & Regards
> Tejesh
> 
-- 
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

[ovirt-users] Checking VmPool status with Python-SDK?

2016-11-08 Thread nicolas


Hi,

We're running oVirt 4.0.4.4 with engine python SDK version 3.6.7, and 
currently we're developing an application that first creates a VmPool 
and afterwards it updates it. However, sometimes happens that both 
operations occur at the same time, which results in an oVirt error 
claiming that a VmPool cannot be updated if there are still pending 
operations to do.


We want to control this situation, so we've checked if the VmPool class 
has a .get_status() method but it seems it doesn't, so I'm asking for 
alternative ways of handling this. Would it be enough to say a VmPool is 
not "busy" if all its VMs are not in a blocked state (for example, with 
a blocked disk due to clonation)?


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

Re: [ovirt-users] hosted-engine cant access engine appliance

2016-11-08 Thread Steffen Nolden


Hello Florian,

there is no problem to reslove the FQDN

[nolden@oVirtNode01 ~]$ nslookup oVirtEngine.com
Server:192.168.122.1
Address:192.168.122.1#53

Name:oVirtEngine.com
Address: 192.168.122.201

The '/etc/hosts' file of each host is configured to resolve the name.

I tried it with stopped firewall,

[nolden@oVirtNode01 ~]$ sudo systemctl stop firewalld
[nolden@oVirtNode01 ~]$ sudo systemctl status firewalld
● firewalld.service - firewalld - dynamic firewall daemon
   Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; 
vendor preset: enabled)

   Active: inactive (dead) since Di 2016-11-08 09:10:46 CET; 3s ago
  Process: 724 ExecStart=/usr/sbin/firewalld --nofork --nopid 
$FIREWALLD_ARGS (code=exited, status=0/SUCCESS)

 Main PID: 724 (code=exited, status=0/SUCCESS)

but i got the same error!


Am 04.11.2016 um 15:50 schrieb Florian Nolden:

Hello Steffen,

can your nodes resolve the FQDN "ovirtengine.com 
" to the hosted engine ip ( nslookup 
ovirtengine.com ) ?

If that works have you tried to disable the firewall temporarily?

2016-11-04 14:11 GMT+01:00 Steffen Nolden 
>:


Hello,

i tried to deploy hosted-engine on a testing environment. First of
all i tried to deploy with the option

"Automatically execute engine-setup on the engine appliance on
first boot (Yes, No)[Yes]? Yes"

but it got stuck.

[ INFO  ] Running engine-setup on the appliance
[ ERROR ] Engine setup got stuck on the appliance
[ ERROR ] Failed to execute stage 'Closing up': Engine setup is
stalled on the appliance since 600 seconds ago. Please check its
log on the appliance.
[ INFO  ] Stage: Clean up
[ INFO  ] Generating answer file
'/var/lib/ovirt-hosted-engine-setup/answers/answers-20161104112913.conf'
[ INFO  ] Stage: Pre-termination
[ INFO  ] Stage: Termination
[ ERROR ] Hosted Engine deployment failed: this system is not
reliable, please check the issue,fix and redeploy
  Log file is located at

/var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20161104110104-kyhq1e.log

Next try i said 'No' and i tried to execute it myself. But i can't
access the engine appliance.

[nolden@oVirtNode01 ~]$ sudo hosted-engine --console
/usr/share/vdsm/vdsClient.py:33: DeprecationWarning: vdscli
uses xmlrpc. since ovirt 3.6 xmlrpc is deprecated, please use
vdsm.jsonrpcvdscli
   from vdsm import utils, vdscli, constants
The engine VM is running on this host
Verbunden mit der Domain: HostedEngine
Escape-Zeichen ist ^]
Fehler: Interner Fehler: Charakter-Einheit console0 verwendet
nicht ein PTY

Additionally i can't ping or access the engine appliance via ssh.

Did i forget to install a packege or configure something?

Below my infrastructure and configs. Attached the log file.


Thanks for help.



My infrastructure is a nestedVM system:
All systems have nested visualization activated

HW with LinuxMint x86_64;
- VM with CentOS-7-x86_64; 24GB Ram; 7 cores;
- Nested VM with CentOS-7-x86_64; 12288GB Ram; 4 cores;
Hostname: oVirtNode01.com (192.168.122.101): Here i deploy
hosted-engine, Hostname: oVirtEngine.com (192.168.122.201)
- Nested VM with CentOS-7-x86_64; 4096GB  Ram; 1 cores;
Hostname: oVirtNode02.com (192.168.122.102):
- Nested VM with CentOS-7-x86_64; 4096GB  Ram; 1 cores;
Hostname: oVirtNode03.com (192.168.122.103):

All three NestedVMs are updated, have installed the
ovirt-release40.rpm. Additional installed:
screen (4.1.0), ovirt-hosted-engine-setup (2.0.2.2), vdsm-gluster
(4.18.13), bridge-utils (1.5),
vdsm (4.18.13), vdsm-cli (4.18.13), glusterfs-server (3.7.16), samba.

First NestedVM additional installed ovirt-engine-appliance
4.0-20160928.1.el7.centos

The three VMs building a glusterfs volume "engine" 3 replica, with
the options...

Volume Name: engine
Type: Replicate
Volume ID: e92849b7-af3b-4ccd-bd0d-69a5ab3b6214
Status: Started
Number of Bricks: 1 x 3 = 3
Transport-type: tcp
Bricks:
Brick1: oVirtNode01.com:/gluster/engine/brick1
Brick2: oVirtNode02.com:/gluster/engine/brick1
Brick3: oVirtNode03.com:/gluster/engine/brick1
Options Reconfigured:
auth.allow: 192.168.122.*
storage.owner-gid: 36
storage.owner-uid: 36
performance.readdir-ahead: on

## Session 1 (hosted-engine deploy without automatically execute
engine-setup)
[nolden@oVirtNode01 ~]$ sudo hosted-engine --deploy

/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/storage_backends.py:15:
DeprecationWarning: vdscli uses xmlrpc. since ovirt 3.6 xmlrpc is
deprecated, please use vdsm.jsonrpcvdscli
  import vdsm.vdscli
[ INFO  ] Stage:

[ovirt-users] Can't upload qcow2 images via web UI

2016-11-08 Thread วีร์ ศรีทิพโพธิ์

Hi,I’m trying to transfer one of my VM from KVM to oVirt. My understanding is that I can upload its qcow2 to oVirt via ’Upload > Start’ in ‘Disks’ tab of the web UI.However, the upload won’t start. I found this message in the events tab:"Unable to upload image to disk 2a2e3afc-825b-4022-b402-669731003f3a due to a network error. Make sure ovirt-imageio-proxy service is installed and configured, and ovirt-engine's certificate is registered as a valid CA in the browser."I already installed the CA from 'https://[engine address]/ovirt-engine/services/pki-resource?resource=ca-certificate=X509-PEM-CA’ and ovirt-imageio-proxy is still running.[root@oengine ~]# systemctl status ovirt-imageio-proxy● ovirt-imageio-proxy.service - oVirt ImageIO Proxy   Loaded: loaded (/usr/lib/systemd/system/ovirt-imageio-proxy.service; enabled; vendor preset: disabled)   Active: active (running) since Tue 2016-11-08 02:06:55 UTC; 5h 28min ago Main PID: 503 (ovirt-imageio-p)   CGroup: /system.slice/ovirt-imageio-proxy.service           └─503 /usr/bin/python /usr/bin/ovirt-imageio-proxyPlease guide me in this regard,Wee.oVirt Engine Version: 4.0.4.4-1.el7.centosLogs:

image-proxy.log
Description: Binary data
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt SDK v4 backwards compatibility

2016-11-08 Thread Juan Hernández

On 11/07/2016 07:06 PM, Rafael Martins wrote:
> - Original Message -
>> From: "Karli Sjöberg" 
>> To: "Rafael Martins" 
>> Cc: users@ovirt.org
>> Sent: Monday, November 7, 2016 6:13:33 PM
>> Subject: Re: [ovirt-users] oVirt SDK v4 backwards compatibility
>>
>>
>> Den 7 nov. 2016 15:53 skrev Rafael Martins :
>>>
>>> - Original Message -
 From: "Karli Sjöberg" 
 To: users@ovirt.org
 Sent: Monday, November 7, 2016 3:06:10 PM
 Subject: [ovirt-users] oVirt SDK v4 backwards compatibility

 Heya!

 Quick question, if I have on my computer installed a newer version
 Python SDK than what´s installed on the engine (4.0.3 locally and 3.6.X
 in engine), is it possible to connect?
>>>
>>> It is not possible, but you can still install the RPM for the version 3 of
>>> the SDK. Please note that the code of the SDK versions is not compatible.
>>
>> Ok, as I thought. But how does others handle that, like moVirt e.g? Is there
>> a best-practice for backwards compatibility?
> 
> Right now if you use the old SDK you should be able to "talk" with both 3.6 
> and 4.0, because 4.0 api provides backward compatibility with 3.6. But I'm 
> not sure if you can rely on this. Juan may have more details for you.
> 

It is important to understand the following:

* There are two different versions of the API: version 3 and version 4.

* Version 3 of the engine implements only version 3 of the API.

* Version 4 of the engine implements versions 3 and 4 of the API. This
is the current situation. In version 4.2 we will probably drop suport
for version 3 of the API completely.

* Version 3 of the SDK implements only version 3 of the SDK. The name of
the package is "ovirt-engine-sdk-python".

* Version 4 of the SDK implements only version 4 of the SDK. The name of
the package is "python-ovirt-engine-sdk4".

In your specific use case, version 4.0.3 of the
"python-ovirt-engine-sdk4" package can't talk to version 3.6.X of the
engine. But as Rafael says, you can install version 3 of the SDK, the
"ovirt-engine-sdk-python" package, and then it will version 3.6.X of the
engine.

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

[ovirt-users] OVN Provider setup issues

2016-11-08 Thread Andrea Fagiani


Hi all,

I've been messing around with the ovirt-ovn-provider [1] and I've run 
into some issues during the initial setup.


I have a 5-node cluster (running the hosted-engine VA), LEGACY virtual 
switch; this test was done on a single host. Following the instructions 
from the aforementioned blog post, I have downloaded the 
ovirt-provider-ovn and ovirt-provider-ovn-driver rpms, and built the rpm 
packages for:


- openvswitch (2.6.90)
- openvswitch-ovn-common
- openvswitch-ovn-host
- openvswitch-ovn-central
- python-openvswitch

I set up a dedicated VM for the OVN controller, installed ovs and 
ovn-central, started the ovn-northd and ovirt-provider-ovn services. So 
far so good. I then moved on to the oVirt host and installed the above 
packages (minus ovn-central) as well as the ovirt-provider-ovn-driver 
provided, started the ovn-controller service and ran


# vdsm-tool ovn-config  

Executing the suggested checks I noticed that something didn't quite go 
as planned. Below is the /var/log/openvswitch/ovn-controller.log from 
the host machine. There are no firewalls involved (not even on the 
servers) and I also tried disabling SELinux but to no avail.


Any ideas?

Thanks,
Andrea

[1] http://www.ovirt.org/blog/2016/11/ovirt-provider-ovn/


2016-11-07T14:22:09.552Z|1|vlog|INFO|opened log file 
/var/log/openvswitch/ovn-controller.log
2016-11-07T14:22:09.553Z|2|reconnect|INFO|unix:/var/run/openvswitch/db.sock: 
connecting...
2016-11-07T14:22:09.553Z|3|reconnect|INFO|unix:/var/run/openvswitch/db.sock: 
connected
2016-11-07T14:22:09.555Z|4|reconnect|INFO|tcp:10.100.248.11:6642: 
connecting...
2016-11-07T14:22:09.555Z|5|reconnect|INFO|tcp:10.100.248.11:6642: 
connected
2016-11-07T14:22:09.556Z|6|ofctrl|INFO|unix:/var/run/openvswitch/br-int.mgmt: 
connecting to switch
2016-11-07T14:22:09.556Z|7|rconn|INFO|unix:/var/run/openvswitch/br-int.mgmt: 
connecting...
2016-11-07T14:22:09.557Z|8|pinctrl|INFO|unix:/var/run/openvswitch/br-int.mgmt: 
connecting to switch
2016-11-07T14:22:09.557Z|9|rconn|INFO|unix:/var/run/openvswitch/br-int.mgmt: 
connecting...
2016-11-07T14:22:09.557Z|00010|rconn|INFO|unix:/var/run/openvswitch/br-int.mgmt: 
connected
2016-11-07T14:22:09.557Z|00011|rconn|INFO|unix:/var/run/openvswitch/br-int.mgmt: 
connected
2016-11-07T14:22:09.558Z|00012|ofctrl|INFO|OpenFlow error: OFPT_ERROR 
(OF1.3) (xid=0x9): OFPBMC_BAD_FIELD

OFPT_FLOW_MOD (OF1.3) (xid=0x9):
(***truncated to 64 bytes from 240***)
  04 0e 00 f0 00 00 00 09-00 00 00 00 00 00 00 00 
||
0010  00 00 00 00 00 00 00 00-22 00 00 00 00 00 00 00 
|"...|
0020  ff ff ff ff ff ff ff ff-ff ff ff ff 00 00 00 00 
||
0030  00 01 00 04 00 00 00 00-00 04 00 b8 00 00 00 00 
||


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

Re: [ovirt-users] Uploading an image with qcow2 compat 1.1 is unsupported for storage format type V3

[ovirt-users] Import from OVA with encrypted root

Re: [ovirt-users] IP address doesn't appear in the host network interfaces tab

[ovirt-users] [HELP] unmapping a deleted storage domain triggers crash ovirt

Re: [ovirt-users] Can't upload qcow2 images via web UI

[ovirt-users] IP address doesn't appear in the host network interfaces tab

Re: [ovirt-users] oVirt 4.04 Can't Migrate VMs - Cryptic "Migration Failed" Error

Re: [ovirt-users] can't import vm from KVM host

Re: [ovirt-users] Uploading an image with qcow2 compat 1.1 is unsupported for storage format type V3

Re: [ovirt-users] hosted-engine cant access engine appliance

Re: [ovirt-users] Can't upload qcow2 images via web UI

Re: [ovirt-users] can't import vm from KVM host

Re: [ovirt-users] Can't upload qcow2 images via web UI

Re: [ovirt-users] hosted-engine cant access engine appliance

Re: [ovirt-users] Unexpected SSL errors (unexpected eof) in vdsm log?

[ovirt-users] About fibre channel storage

Re: [ovirt-users] Checking VmPool status with Python-SDK?

Re: [ovirt-users] RHEVM3.3 java SDK on RHEV3.6

[ovirt-users] Checking VmPool status with Python-SDK?

Re: [ovirt-users] hosted-engine cant access engine appliance

[ovirt-users] Can't upload qcow2 images via web UI

Re: [ovirt-users] oVirt SDK v4 backwards compatibility

[ovirt-users] OVN Provider setup issues

23 matches

Site Navigation

Mail list logo

Footer information