July 2017 - Users - oVirt List Archives

Feature: Hosted engine VM management
by Roy Golan 27 Feb '19

27 Feb '19

Hi all, Upcoming in 3.6 is enhancement for managing the hosted engine VM. In short, we want to: * Allow editing the Hosted engine VM, storage domain, disks, networks etc * Have a shared configuration for the hosted engine VM * Have a backup for the hosted engine VM configuration please review and comment on the wiki below: http://www.ovirt.org/Hosted_engine_VM_management Thanks, Roy

2 3

Re: [ovirt-users] Large DWH Database, how to empty
by Matt . 26 Feb '19

26 Feb '19

Hi, OK thanks! I saw that after upgrading to 4.0.5 from 4.0.4 the DB already dropped with around 500MB directly and is now at 2GB smaller. Does this sounds familiar to you with other settings in 4.0.5 ? Thanks, Matt 2017-01-08 10:45 GMT+01:00 Shirly Radco <sradco(a)redhat.com>: > No. That will corrupt your database. > > Are you using the full dwh or the smaller version for the dashboards? > > Please set the delete thresholds to save less data and the data older then > the time you set will be deleted. > Add a file to /ovirt-engine-dwhd.conf.d/ > update_time_to_keep_records.conf > > Add these lines with the new configurations. The numbers represent the hours > to keep the data. > > DWH_TABLES_KEEP_SAMPLES=24 > DWH_TABLES_KEEP_HOURLY=1440 > DWH_TABLES_KEEP_DAILY=43800 > > > These are the configurations for a full dwh. > > The smaller version configurations are: > DWH_TABLES_KEEP_SAMPLES=24 > DWH_TABLES_KEEP_HOURLY=720 > DWH_TABLES_KEEP_DAILY=0 > > The delete process by default at 3am every day (DWH_DELETE_JOB_HOUR=3) > > Best regards, > > Shirly Radco > > BI Software Engineer > Red Hat Israel Ltd. > 34 Jerusalem Road > Building A, 4th floor > Ra'anana, Israel 4350109 > > > On Fri, Jan 6, 2017 at 6:35 PM, Matt . <yamakasi.014(a)gmail.com> wrote: >> >> Hi, >> >> I seem to have some large database for the DWH logging and I wonder >> how I can empty it safely. >> >> Can I just simply empty the database ? >> >> Have a good weekend! >> >> Cheers, >> >> Matt >> _______________________________________________ >> Users mailing list >> Users(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users > >

1 0

Re: [ovirt-users] Packet loss
by Doron Fediuck 26 Feb '19

26 Feb '19

----_com.android.email_640187878761650 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 SGkgS3lsZSzCoApXZSBtYXkgaGF2ZSBzZWVuIHNvbWV0aGluZyBzaW1pbGFyIGluIHRoZSBwYXN0 IGJ1dCBJIHRoaW5rIHRoZXJlIHdlcmUgdmxhbnMgaW52b2x2ZWQuwqAKSXMgaXQgdGhlIHNhbWUg Zm9yIHlvdT/CoApUb255IC8gRGFuLCBkb2VzIGl0IHJpbmcgYSBiZWxsP8Kg ----_com.android.email_640187878761650 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: base64 PGh0bWw+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0 L2h0bWw7IGNoYXJzZXQ9VVRGLTgiPjwvaGVhZD48Ym9keSA+PGRpdj5IaSBLeWxlLCZuYnNwOzwv ZGl2PjxkaXY+V2UgbWF5IGhhdmUgc2VlbiBzb21ldGhpbmcgc2ltaWxhciBpbiB0aGUgcGFzdCBi dXQgSSB0aGluayB0aGVyZSB3ZXJlIHZsYW5zIGludm9sdmVkLiZuYnNwOzwvZGl2PjxkaXY+SXMg aXQgdGhlIHNhbWUgZm9yIHlvdT8mbmJzcDs8L2Rpdj48ZGl2PlRvbnkgLyBEYW4sIGRvZXMgaXQg cmluZyBhIGJlbGw/Jm5ic3A7PC9kaXY+PC9ib2R5PjwvaHRtbD4= ----_com.android.email_640187878761650--

2 1

Unable to backend oVirt with Cinder
by Logan Kuhn 21 Jun '18

21 Jun '18

------=_Part_51316288_608143832.1472587678781 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit I've got Cinder configured and pointed at Ceph for it's back end storage. I can run ceph commands on the cinder machine and cinder is configured for noauth and I've also tried it with Keystone for auth. I can run various cinder commands and it'll return as expected. When I configure it in oVirt it'll add the external provider fine, but when I go to create a disk it doesn't populate the volume type field, it's just empty. The corresponding command for cinder: cinder type-list and cinder type-show <name> returns fine and it is public. Ovirt and Cinder are on the same host so it isn't a firewall issue. Cinder config: [DEFAULT] rpc_backend = rabbit #auth_strategy = keystone auth_strategy = noauth enabled_backends = ceph #glance_api_servers = http://10.128.7.252:9292 #glance_api_version = 2 #[keystone_authtoken] #auth_uri = http://10.128.7.252:5000/v3 #auth_url = http://10.128.7.252:35357/v3 #auth_type = password #memcached_servers = localhost:11211 #project_domain_name = default #user_domain_name = default #project_name = services #username = user #password = pass [ceph] volume_driver = cinder.volume.drivers.rbd.RBDDriver volume_backend_name = ceph rbd_pool = ovirt-images rbd_user = cinder rbd_secret_uuid = <secret> rbd_ceph_conf = /etc/ceph/ceph.conf rbd_flatten_volume_from_snapshot = true rbd_max_clone_depth = 5 rbd_store_chunk_size = 4 rados_connect_timeout = -1 #glance_api_version = 2 [database] connection = postgresql://user:pass@10.128.2.33/cinder [oslo_concurrency] lock_path = /var/lib/cinder/tmp [oslo_messaging_rabbit] rabbit_host = localhost rabbit_port = 5672 rabbit_userid = user rabbit_password = pass Regards, Logan ------=_Part_51316288_608143832.1472587678781 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <html><body><div style=3D"font-family: Arial; font-size: 12pt; color: #0000= 00"><div>I've got Cinder configured and pointed at Ceph for it's back end s= torage.  I can run ceph commands on the cinder machine and cinder is c= onfigured for noauth and I've also tried it with Keystone for auth.  I= can run various cinder commands and it'll return as expected. </= div><div><br data-mce-bogus=3D"1"></div><div>When I configure it in oVirt i= t'll add the external provider fine, but when I go to create a disk it does= n't populate the volume type field, it's just empty.  The correspondin= g command for cinder: cinder type-list and cinder type-show <name> re= turns fine and it is public. </div><div><br data-mce-bogus=3D"1"></div= ><div>Ovirt and Cinder are on the same host so it isn't a firewall issue.</= div><div><br data-mce-bogus=3D"1"></div><div>Cinder config:</div><div>[DEFA= ULT]<br>rpc_backend =3D rabbit<br>#auth_strategy =3D keystone<br>auth_strat= egy =3D noauth<br>enabled_backends =3D ceph<br>#glance_api_servers =3D http= ://10.128.7.252:9292<br>#glance_api_version =3D 2<br><br>#[keystone_authtok= en]<br>#auth_uri =3D http://10.128.7.252:5000/v3<br>#auth_url =3D http://10= .128.7.252:35357/v3<br>#auth_type =3D password<br>#memcached_servers =3D lo= calhost:11211<br>#project_domain_name =3D default<br>#user_domain_name =3D = default<br>#project_name =3D services<br>#username =3D user<br>#passwo= rd =3D pass<br><br>[ceph]<br>volume_driver =3D cinder.volume.drivers.rbd.RB= DDriver<br>volume_backend_name =3D ceph<br>rbd_pool =3D ovirt-images<br>rbd= _user =3D cinder<br>rbd_secret_uuid =3D <secret><br>rbd_ceph_con= f =3D /etc/ceph/ceph.conf<br>rbd_flatten_volume_from_snapshot =3D true<br>r= bd_max_clone_depth =3D 5<br>rbd_store_chunk_size =3D 4<br>rados_connect_tim= eout =3D -1<br>#glance_api_version =3D 2<br><br>[database]<br>connection = =3D postgresql://user:pass@10.128.2.33/cinder<br><br>[oslo_concurrency]<br>= lock_path =3D /var/lib/cinder/tmp<br><br>[oslo_messaging_rabbit]<br>rabbit_= host =3D localhost<br>rabbit_port =3D 5672<br>rabbit_userid =3D <span = style=3D"color: #000000; font-family: Arial; font-size: 16px; font-style: n= ormal; font-variant-ligatures: normal; font-variant-caps: normal; font-weig= ht: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-a= lign: start; text-indent: 0px; text-transform: none; white-space: normal; w= idows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; display: inlin= e !important; float: none; background-color: #ffffff;" data-mce-style=3D"co= lor: #000000; font-family: Arial; font-size: 16px; font-style: normal; font= -variant-ligatures: normal; font-variant-caps: normal; font-weight: normal;= letter-spacing: normal; line-height: normal; orphans: 2; text-align: start= ; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; w= ord-spacing: 0px; -webkit-text-stroke-width: 0px; display: inline !importan= t; float: none; background-color: #ffffff;">user</span><br>rabbit_password = =3D <span style=3D"color: #000000; font-family: Arial; font-size: 16px= ; font-style: normal; font-variant-ligatures: normal; font-variant-caps: no= rmal; font-weight: normal; letter-spacing: normal; line-height: normal; orp= hans: 2; text-align: start; text-indent: 0px; text-transform: none; white-s= pace: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px;= display: inline !important; float: none; background-color: #ffffff;" data-= mce-style=3D"color: #000000; font-family: Arial; font-size: 16px; font-styl= e: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-= weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; te= xt-align: start; text-indent: 0px; text-transform: none; white-space: norma= l; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; display: i= nline !important; float: none; background-color: #ffffff;">pass</span></div= ><div><br></div><div data-marker=3D"__SIG_PRE__">Regards,<br>Logan</div></d= iv></body></html> ------=_Part_51316288_608143832.1472587678781--

4 4

vdsClient is removed and replaced by vdsm-client
by Irit Goihman 16 Apr '18

16 Apr '18

Hi All, vdsClient will be removed from master branch today. It is using XMLRPC protocol which has been deprecated and replaced by JSON-RPC. A new client for vdsm was introduced in 4.1: vdsm-client. This is a simple client that uses JSON-RPC protocol which was introduced in ovirt 3.5. The client is not aware of the available methods and parameters, and you should consult the schema [1] in order to construct the desired command. Future version should parse the schema and provide online help. If you're using vdsClient, we will be happy to assist you in migrating to the new vdsm client. *vdsm-client usage:* vdsm-client [-h] [-a ADDRESS] [-p PORT] [--unsecure] [--timeout TIMEOUT] [-f FILE] namespace method [name=value [name=value] ...] Invoking simple methods: # vdsm-client Host getVMList ['b3f6fa00-b315-4ad4-8108-f73da817b5c5'] For invoking methods with many or complex parameters, you can read the parameters from a JSON format file: # vdsm-client Lease info -f lease.json where lease.json file content is: { "lease": { "sd_id": "75ab40e3-06b1-4a54-a825-2df7a40b93b2", "lease_id": "b3f6fa00-b315-4ad4-8108-f73da817b5c5" } } It is also possible to read parameters from standard input, creating complex parameters interactively: # cat <<EOF | vdsm-client Lease info -f - { "lease": { "sd_id": "75ab40e3-06b1-4a54-a825-2df7a40b93b2", "lease_id": "b3f6fa00-b315-4ad4-8108-f73da817b5c5" } } EOF *Constructing a command from vdsm schema:* Let's take VM.getStats as an example. This is the entry in the schema: VM.getStats: added: '3.1' description: Get statistics about a running virtual machine. params: - description: The UUID of the VM name: vmID type: *UUID return: description: An array containing a single VmStats record type: - *VmStats namespace: VM method name: getStats params: vmID The vdsm-client command is: # vdsm-client VM getStats vmID=b3f6fa00-b315-4ad4-8108-f73da817b5c5 *Invoking getVdsCaps command:* # vdsm-client Host getCapabilities Please consult vdsm-client help and man page for further details and options. [1] https://github.com/oVirt/vdsm/blob/master/lib/api/vdsm-api.yml -- Irit Goihman Software Engineer Red Hat Israel Ltd.

4 7

Passing VLAN trunk to VM
by Simon Vincent 26 Mar '18

26 Mar '18

Is it possible to pass multiple VLANs to a VM (pfSense) using a single virtual NIC? All my existing oVirt networks are setup as a single tagged VLAN. I know this didn't used to be supported but wondered if this has changed. My other option is to pass each VLAN as a separate NIC to the VM however if I needed to add a new VLAN I would have to add a new interface and reboot the VM as hot-add of NICs is not supported by pfSense.

6 14

HostedEngine with HA
by Carlos Rodrigues 22 Mar '18

22 Mar '18

Hello, I have one cluster with two hosts with power management correctly configured and one virtual machine with HostedEngine over shared storage with FiberChannel. When i shutdown the network of host with HostedEngine VM, it should be possible the HostedEngine VM migrate automatically to another host? What is the expected behaviour on this HA scenario? Regards, -- Carlos Rodrigues Engenheiro de Software Sénior Eurotux Informática, S.A. | www.eurotux.com (t) +351 253 680 300 (m) +351 911 926 110

4 30

oVIRT 4.1 / iSCSI Multipathing
by Devin Acosta 05 Mar '18

05 Mar '18

I am using the latest release of oVIRT 4.1.3, and I am connecting a Dell Compelent SAN that has 2 fault domains each on a separate VLAN that I have attached to oVIRT. From what I understand I am suppose to go into “iSCSI Multipathing” option and add a BOND of the iSCSI interfaces. I have done this selecting the 2 logical networks together for iSCSI. I notice that there is an option below to select Storage Targets but if I select the storage targets below with the logical networks the the cluster goes crazy and appears to be mad. Storage, Nodes, and everything goes offline even thought I have NFS also attached to the cluster. How should this best be configured. What we notice that happens is when the server reboots it seems to log into the SAN correctly but according the the Dell SAN it is only logged into once controller. So only pulls both fault domains from a single controller. Please Advise. Devin

7 10

when creating VMs, I don't want hosted_storage to be an option
by Mike Farnam 09 Feb '18

09 Feb '18

Hi All - Is that a way to mark hosted_storage somehow so that it’s not available to add new VMs to? Right now it’s the default storage domain when adding a VM. At the least, I’d like to make another storage domain the default. Is there a way to do this? Thanks

6 8

Official Hyperconverged Gluster oVirt upgrade procedure?
by Hanson 23 Jan '18

23 Jan '18

Hi Guys, Just wondering if we have an updated manual or whats the current procedure for upgrading the nodes in a hyperconverged ovirt gluster pool? Ie Nodes run 4.0 oVirt, as well as GlusterFS, and hosted-engine running in a gluster storage domain. Put node in maintenance mode and disable glusterfs from ovirt gui, run yum update? Thanks!

4 4

[vdsm] status update: running containers alongside VMs
by Francesco Romani 05 Jan '18

05 Jan '18

Hi everyone, I'm happy to share some progress about the former "convirt"[1] project, which aims to let Vdsm containers alongside VMs, on bare metal. In the last couple of months I kept updating the patch series, which is approaching the readiness to be merged in Vdsm. Please read through this mail to see what the patchset can do now, how you could try it *now*, even before it is merged. Everyone is invited to share thoughts and ideas about how this effort could evolve. This will be a long mail; I will amend, enhance and polish the content and make a blog post (on https://mojaves.github.io) to make it easier to consume and to have some easy-to-find documentation. Later on the same content will appear also on the oVirt blog. Happy hacking! +++ # How to try how the experimental container support for Vdsm. Vdsm is gaining *experimental* support to run containers alongside VMs. Vdsm had since long time the ability to manage VMs which run containers, and recently gained support for [atomic guests](http://www.projectatomic.io/blog/2015/01/running-ovirt-guest-agent-as-privileged-container/). With the new support we are describing, you will be able to manage containers with the same, proven infrastructure that let you manage VMs. This feature is currently being developed and it is still not merged in the Vdsm codebase, so some extra work is needed if you want to try it out. We aiming to merge it in the oVirt 4.1.z cycle. ## What works, aka what to expect The basic features are expected to work: 1. Run any docker image on the public docker registry 2. Make the container accessible from the outside (aka not just from localhost) 3. Use file-based storage for persistent volumes ## What does not yet work, aka what NOT to expect Few things are planned and currently under active development: 1. Monitoring. Engine will not get any update from the container besides "VM" status (Up, Down...) One important drawback is that you will not be told the IP of the container from Engine, you will need to connect to the Vdsm host to discover it using standard docker tools. 2. Proper network integration. Some steps still need manual intervention 3. Stability and recovery - it's pre-alpha software after all! :) ## 1. Introduction and prerequisites Trying out container support affects only the host and the Vdsm. Besides add few custom properties (totally safe and supported since early 3.z), there are zero changes required to the DB and to Engine. Nevertheless, we recommend to dedicate one oVirt 4.y environment, or at least one 4.y host, to try out the container feature. To get started, first thing you need is to setup a vanilla oVirt 4.y installation. We will need to make changes to the Vdsm and to the Vdsm host, so hosted engine and/or oVirt node may add extra complexity, better to avoid them at the moment. The reminder of this tutorial assumes you are using two hosts, one for Vdsm (will be changed) and one for Engine (will require zero changes); furthermore, we assume the Vdsm host is running on CentOS 7.y. We require: - one test host for Vdsm. This host need to have one NIC dedicated to containers. We will use the [docker macvlan driver](https://raesene.github.io/blog/2016/07/23/Docker-MacVLAN/), so this NIC *must not be* part of one bridge. - docker >= 1.12 - oVirt >= 4.0.5 (Vdsm >= 4.18.15) - CentOS >= 7.2 Docker >= 1.12 is avaialable for download [here](https://docs.docker.com/engine/installation/linux/centos/) Caveats: 1. docker from official rpms conflicts con docker from CentOS, and has a different package name: docker-engine vs docker. Please note that the kubernetes package from CentOS, for example, require 'docker', not 'docker-engine'. 2. you may want to replace the default service file [with this one](https://github.com/mojaves/convirt/blob/master/patches/centos72/system… and to use this [sysconfig file](https://github.com/mojaves/convirt/blob/master/patches/centos72/syste…. Here I'm just adding the storage options docker requires, much like the CentOS docker is configured. Configuring docker like this can save you some troubleshooting, especially if you had docker from CentOS installed on the testing box. ## 2. Patch Vdsm to support containers You need to patch and rebuild Vdsm. Fetch [this patch](https://github.com/mojaves/convirt/blob/master/patches/vdsm/4.18.15.… and apply it against Vdsm 4.18.15.1. Vdsm 4.18.15.{1,2,...} are supported as well. Rebuild Vdsm and reinstall on your box. [centos 7.2 packages are here](https://github.com/mojaves/convirt/tree/master/rpms/centos72) Make sure you install the Vdsm command line client (vdsm-cli) Restart *both* Vdsm and Supervdsm, make sure Engine still works flawlessly with patched Vdsm. This ensure that no regression is introduced, and that your environment can run VMs just as before. Now we can proceed adding the container support. start docker: # systemctl start docker-engine (optional) # systemctl enable docker-engine Restart Vdsm again # systemctl restart vdsm Now we can check if Vdsm detects docker, so you can use it: still on the same Vdsm host, run $ vdsClient -s 0 getVdsCaps | grep containers containers = ['docker', 'fake'] This means this Vdsm can run containers using 'docker' and 'fake' runtimes. Ignore the 'fake' runtime; as the name suggests, is a test driver, kinda like /dev/null. Now we need to make sure the host network configuration is fine. ### 2.1. Configure the docker network for Vdsm PLEASE NOTE that the suggested network configuration assumes that * you have one network, `ovirtmgmt` (the default one) you use for everything * you have one Vdsm host with at least two NICs, one bound to the `ovirtmgmt` network, and one spare _This step is not yet automated by Vdsm_, so manual action is needed; Vdsm will take care of this automatically in the future. You can use [this helper script](https://github.com/mojaves/convirt/blob/master/patches/vdsm/cont-se…, which reuses the Vdsm libraries. Make sure you have patched Vdsm to support container before to use it. Let's review what the script needs: # ./cont-setup-net -h usage: cont-setup-net [-h] [--name [NAME]] [--bridge [BRIDGE]] [--interface [INTERFACE]] [--gateway [GATEWAY]] [--subnet [SUBNET]] [--mask [MASK]] optional arguments: -h, --help show this help message and exit --name [NAME] network name to use --bridge [BRIDGE] bridge to use --interface [INTERFACE] interface to use --gateway [GATEWAY] address of the gateway --subnet [SUBNET] subnet to use --mask [MASK] netmask to use So we need to feed --name, --interface, --gateway, --subnet and optionally --mask (default, /24, is often fine). For my case the default mask was indeed fine, so I used the script like this: # ./cont-setup-net --name ovirtmgmt --interface enp3s0 --gateway 192.168.1.1 --subnet 192.168.1.0 Thhis is the output I got: DEBUG:virt.containers.runtime:configuring runtime 'docker' DEBUG:virt.containers.command:* calling ['/bin/docker', 'network', 'inspect', 'ovirtmgmt'] Error: No such network: ovirtmgmt DEBUG:virt.containers.command:* called ['/bin/docker', 'network', 'inspect', 'ovirtmgmt'] DEBUG:virt.containers.runtime.Docker:config: cannot load 'ovirtmgmt', ignored DEBUG:virt.containers.command:* calling ['/bin/docker', 'network', 'create', '-d', 'macvlan', '--subnet=192.168.1.0/24', '--gateway=192.168.1.1', '--ip-range=192.168.1.0/24', '-o', 'parent=enp3s0', 'ovirtmgmt'] DEBUG:virt.containers.command:* called ['/bin/docker', 'network', 'create', '-d', 'macvlan', '--subnet=192.168.1.0/24', '--gateway=192.168.1.1', '--ip-range=192.168.1.0/24', '-o', 'parent=enp3s0', 'ovirtmgmt'] DEBUG:virt.containers.runtime:configuring runtime 'fake' You can clearly see what the script did, and why it needed the root privileges. Let's deoublecheck using the docker tools: # docker network ls NETWORK ID NAME DRIVER SCOPE 91535f3425a8 bridge bridge local d42f7e5561b5 host host local 621ab6dd49b1 none null local f4b88e4a67eb ovirtmgmt macvlan local # docker network inspect ovirtmgmt [ { "Name": "ovirtmgmt", "Id": "f4b88e4a67ebb7886ec74073333d613b1893272530cae4d407c95ab587c5fea1", "Scope": "local", "Driver": "macvlan", "EnableIPv6": false, "IPAM": { "Driver": "default", "Options": {}, "Config": [ { "Subnet": "192.168.1.0/24", "IPRange": "192.168.1.0/24", "Gateway": "192.168.1.1" } ] }, "Internal": false, "Containers": {}, "Options": { "parent": "enp3s0" }, "Labels": {} } ] Looks good! the host configuration is completed. Let's move to the Engine side. ## 3. Configure Engine As mentioned above, we need now to configure Engine. This boils down to: Add a few custom properties for VMs: In case you were already using custom properties, you need to amend the command line to not overwrite your existing ones. # engine-config -s UserDefinedVMProperties='volumeMap=^[a-zA-Z_-]+:[a-zA-Z_-]+$;containerImage=^[a-zA-Z]+(://|)[a-zA-Z]+$;containerType=^(docker|rkt)$' --cver=4.0 It is worth stressing that while the variables are container-specific, the VM custom properties are totally inuntrusive and old concept in oVirt, so this step is totally safe. Now restart Engine to let it use the new variables: # systemctl restart ovirt-engine The next step is actually configure one "container VM" and run it. ## 4. Create the container "VM" To finally run a container, you start creating a VM much like you always did, with few changes 1. most of the hardware-related configuration isn't relevant for container "VMs", besides cpu share and memory limits; this will be better documented in the future; unneeded configuration will just be ignored 2. You need to set some custom properties for your container "VM". Those are actually needed to enable the container flow, and they are documented in the next section. You *need* to set at least `containerType` and `containerImage`. ### 4.2. Custom variables for container support The container support needs some custom properties to be properly configured: 1. `containerImage` (*needed* to enable the container system). Just select the target image you want to run. You can use the standard syntax of the container runtimes. 2. `containerType` (*needed* to enable the container system). Selects the container runtime you want to use. All the available options are always showed. Please note that unavailable container options are not yet grayed out. If you *do not* have rkt support on your host, you still can select it, but it won't work. 3. `volumeMap` key:value like. You can map one "VM" disk (key) to one container volume (value), to have persistent storage. Only file-based storage is supported. Example configuration: `containerImage = redis` `containerType = docker` `volumeMap = vda:data` (this may not be needed, and the volume label is just for illustrative purposes) ### 4.2. A little bit of extra work: preload the images on the Vdsm host This step is not needed by the flow, and will be handled by oVirt in the future. The issue is how the container image are handled. They are stored by the container management system (rkt, docker) on each host, and they are not pre-downloaded. To shorten the duration of the first boot, you are advised to pre-download the image(s) you want to run. For example ## on the Vdsm host you want to use with containers # docker pull redis ## 5. Run the container "VM" You are now all set to run your "VM" using oVirt Engine, just like any existing VM. Some actions doesn't make sense for a container "VM", like live migration. Engine won't stop you to try to do those actions, but they will fail gracefully using the standard errors. ## 6. Next steps What to expect from this project in the future? For the integration with Vdsm, we want to fix the existing known issues, most notably: * add proper monitoring/reporting of the container health * ensure proper integration of the container image store with oVirt storage management * streamline the network configuration What is explicitely excluded yet is any Engine change. This is a Vdsm-only change at the moment, so fixing the following is currently unplanned: * First and foremost, Engine will not distinguish between real VMs and container VMs. Actions unavailable to container will not be hidden from UI. Same for monitoring and configuration data, which will be ignored. * Engine is NOT aware of the volumes one container can use. You must inspect and do the mapping manually. * Engine is NOT aware of the available container runtimes. You must select it carefully Proper integration with Engine may be added in the future once this feature exits from the experimental/provisional stage. Thanks for reading, make sure to share your thoughts on the oVirt mailing lists! +++ [1] we keep calling it that way _only_ internally, because it's a short name we are used to. After the merge/once we release it, we will use a different name, like "vdsm-containers" or something like it. -- Francesco Romani Red Hat Engineering Virtualization R & D Phone: 8261328 IRC: fromani

3 2

Empty cgroup files on centos 7.3 host
by Florian Schmid 18 Dec '17

18 Dec '17

Hi, I wanted to monitor disk IO and R/W on all of our oVirt centos 7.3 hypervisor hosts, but it looks like that all those files are empty. For example: ls -al /sys/fs/cgroup/blkio/machine.slice/machine-qemu\\x2d14\\x2dHostedEngine.scope/ insgesamt 0 drwxr-xr-x. 2 root root 0 30. Mai 10:09 . drwxr-xr-x. 16 root root 0 26. Jun 09:25 .. -r--r--r--. 1 root root 0 30. Mai 10:09 blkio.io_merged -r--r--r--. 1 root root 0 30. Mai 10:09 blkio.io_merged_recursive -r--r--r--. 1 root root 0 30. Mai 10:09 blkio.io_queued -r--r--r--. 1 root root 0 30. Mai 10:09 blkio.io_queued_recursive -r--r--r--. 1 root root 0 30. Mai 10:09 blkio.io_service_bytes -r--r--r--. 1 root root 0 30. Mai 10:09 blkio.io_service_bytes_recursive -r--r--r--. 1 root root 0 30. Mai 10:09 blkio.io_serviced -r--r--r--. 1 root root 0 30. Mai 10:09 blkio.io_serviced_recursive -r--r--r--. 1 root root 0 30. Mai 10:09 blkio.io_service_time -r--r--r--. 1 root root 0 30. Mai 10:09 blkio.io_service_time_recursive -r--r--r--. 1 root root 0 30. Mai 10:09 blkio.io_wait_time -r--r--r--. 1 root root 0 30. Mai 10:09 blkio.io_wait_time_recursive -rw-r--r--. 1 root root 0 30. Mai 10:09 blkio.leaf_weight -rw-r--r--. 1 root root 0 30. Mai 10:09 blkio.leaf_weight_device --w-------. 1 root root 0 30. Mai 10:09 blkio.reset_stats -r--r--r--. 1 root root 0 30. Mai 10:09 blkio.sectors -r--r--r--. 1 root root 0 30. Mai 10:09 blkio.sectors_recursive -r--r--r--. 1 root root 0 30. Mai 10:09 blkio.throttle.io_service_bytes -r--r--r--. 1 root root 0 30. Mai 10:09 blkio.throttle.io_serviced -rw-r--r--. 1 root root 0 30. Mai 10:09 blkio.throttle.read_bps_device -rw-r--r--. 1 root root 0 30. Mai 10:09 blkio.throttle.read_iops_device -rw-r--r--. 1 root root 0 30. Mai 10:09 blkio.throttle.write_bps_device -rw-r--r--. 1 root root 0 30. Mai 10:09 blkio.throttle.write_iops_device -r--r--r--. 1 root root 0 30. Mai 10:09 blkio.time -r--r--r--. 1 root root 0 30. Mai 10:09 blkio.time_recursive -rw-r--r--. 1 root root 0 30. Mai 10:09 blkio.weight -rw-r--r--. 1 root root 0 30. Mai 10:09 blkio.weight_device -rw-r--r--. 1 root root 0 30. Mai 10:09 cgroup.clone_children --w--w--w-. 1 root root 0 30. Mai 10:09 cgroup.event_control -rw-r--r--. 1 root root 0 30. Mai 10:09 cgroup.procs -rw-r--r--. 1 root root 0 30. Mai 10:09 notify_on_release -rw-r--r--. 1 root root 0 30. Mai 10:09 tasks I thought, I can get my needed values from there, but all files are empty. Looking at this post: http://lists.ovirt.org/pipermail/users/2017-January/079011.html this should work. Is this normal on centos 7.3 with oVirt installed? How can I get those values, without monitoring all VMs directly? oVirt Version we use: 4.1.1.8-1.el7.centos BR Florian

3 12

Re: [ovirt-users] iSCSI domain on 4kn drives
by Martijn Grendelman 13 Nov '17

13 Nov '17

--------------DE48748F7C67E1FABE46EEAF Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Op 7-8-2016 om 8:19 schreef Yaniv Kaul: > > On Fri, Aug 5, 2016 at 4:42 PM, Martijn Grendelman > <martijn.grendelman(a)isaac.nl <mailto:martijn.grendelman@isaac.nl>> wrote: > > Op 4-8-2016 om 18:36 schreef Yaniv Kaul: >> On Thu, Aug 4, 2016 at 11:49 AM, Martijn Grendelman >> <martijn.grendelman(a)isaac.nl >> <mailto:martijn.grendelman@isaac.nl>> wrote: >> >> Hi, >> >> Does oVirt support iSCSI storage domains on target LUNs using >> a block >> size of 4k? >> >> >> No, we do not - not if it exposes 4K blocks. >> Y. > > Is this on the roadmap? > > > Not in the short term roadmap. > Of course, patches are welcome. It's mainly in VDSM. > I wonder if it'll work in NFS. > Y. I don't think I ever replied to this, but I can confirm that in RHEV 3.6 it works with NFS. Best regards, Martijn. --------------DE48748F7C67E1FABE46EEAF Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: 7bit <html> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> Op 7-8-2016 om 8:19 schreef Yaniv Kaul:<br> <blockquote cite="mid:280cfbd3a16ad1b76cc7de56bda88f45,CAJgorsbJHLV1e3fH4b4AR3GBp1oi44fDhfeii+PQ1iY1RwUStw@mail.gmail.com" type="cite"> <div dir="ltr"><br> <div class="gmail_extra">On Fri, Aug 5, 2016 at 4:42 PM, Martijn Grendelman <span dir="ltr"><<a moz-do-not-send="true" href="mailto:martijn.grendelman@isaac.nl" target="_blank">martijn.grendelman(a)isaac.nl</a>></span> wrote:<br> <div class="gmail_quote"> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div bgcolor="#FFFFFF" text="#000000"> Op 4-8-2016 om 18:36 schreef Yaniv Kaul:<br> <blockquote type="cite"> <div dir="ltr"> <div class="gmail_extra"> <div class="gmail_quote"><span class="">On Thu, Aug 4, 2016 at 11:49 AM, Martijn Grendelman <span dir="ltr"><<a moz-do-not-send="true" href="mailto:martijn.grendelman@isaac.nl" target="_blank">martijn.grendelman(a)isaac.nl</a>></span> wrote:<br> </span><span class=""> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br> <br> Does oVirt support iSCSI storage domains on target LUNs using a block<br> size of 4k?<br> </blockquote> <div><br> </div> </span><span class=""> <div>No, we do not - not if it exposes 4K blocks.</div> <div>Y.</div> </span></div> </div> </div> </blockquote> <br> Is this on the roadmap?<br> </div> </blockquote> <div><br> </div> <div>Not in the short term roadmap.</div> <div>Of course, patches are welcome. It's mainly in VDSM.</div> <div>I wonder if it'll work in NFS.</div> <div>Y.</div> </div> </div> </div> </blockquote> <br> I don't think I ever replied to this, but I can confirm that in RHEV 3.6 it works with NFS.<br> <br> Best regards,<br> Martijn.<br> </body> </html> --------------DE48748F7C67E1FABE46EEAF--

4 4

Re: [ovirt-users] How to import a qcow2 disk into ovirt
by Martín Follonier 04 Oct '17

04 Oct '17

Hi, I've done all the recommendations in this thread, and I'm still getting the "Paused by System" message just after the transfer starts. Honestly I don't know were else to look at, cause I don't find any log entry or packet capture that give me a hint about what is happening. I'll appreciate any help! Thank you in advance! Regards Martin On Thu, Sep 1, 2016 at 5:01 PM, Amit Aviram <aavi...(a)redhat.com> wrote: > You can do both, > Through the database, the table is "vdc_options". change "option_value" > where "option_name" = 'ImageProxyAddress' . > > On Thu, Sep 1, 2016 at 4:56 PM, Gianluca Cecchi <gianluca.cec...(a)gmail.com > > wrote: > >> On Thu, Sep 1, 2016 at 3:53 PM, Amit Aviram <aavi...(a)redhat.com> wrote: >> >>> You can just replace this value in the DB and change it to the right >>> FQDN, it is a config value named "ImageProxyAddress". replace "localhost" >>> with the right address (notice that the port is there too). >>> >>> If this will keep happen after users will have the latest version, we >>> will have to open a bug and fix whatever causes the URL to be "localhost". >>> >>> >> Do you mean through "engine-config" or directly into database? >> In this second case which is the table involved? >> >> Gianluca >> > > [root@ractorshe bin]# systemctl stop ovirt-imageio-proxy engine=# select * from vdc_options where option_name='ImageProxyAddress'; option_id | option_name | option_value | version -----------+-------------------+-----------------+--------- 950 | ImageProxyAddress | localhost:54323 | general (1 row) engine=# update vdc_options set option_value='ractorshe.mydomain:54323' where option_name='ImageProxyAddress'; UPDATE 1 engine=# select * from vdc_options where option_name='ImageProxyAddress'; option_id | option_name | option_value | version -----------+-------------------+--------------------------------------+--------- 950 | ImageProxyAddress | ractorshe.mydomain:54323 | general (1 row) engine=# engine=# select * from vdc_options where option_name='ImageProxyAddress'; option_id | option_name | option_value | version -----------+-------------------+--------------------------------------+--------- 950 | ImageProxyAddress | ractorshe.mydomain:54323 | general (1 row) systemctl stop ovirt-engine (otherwise it remained localhost) systemctl start ovirt-engine systemctl start ovirt-imageio-proxy Now transfer is ok. I tried a qcow2 disck configured as 40Gb but containing about 1.6Gb of data. I'm going to connect it to a VM and see if all is ok also from a contents point of view. Gianluca _______________________________________________ Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users

5 6

oVirt's VM backup
by Victor José Acosta Domínguez 27 Sep '17

27 Sep '17

Hello everyone, i created a python tool to backup and restore oVirt's VMs. Also i created a little "how to" on my blog: http://blog.infratic.com/2017/07/create-ovirtrhevs-vm-backup/ I hope it help someone else Regards Victor Acosta

8 17

ovirt 4.1 hosted engine hyper converged on glusterfs 3.8.10 : "engine" storage domain alway complain about "unsynced" elements
by yayo (j) 08 Sep '17

08 Sep '17

Hi all, We have an ovirt cluster hyperconverged with hosted engine on 3 full replicated node . This cluster have 2 gluster volume: - data: volume for the Data (Master) Domain (For vm) - engine: volume fro the hosted_storage Domain (for hosted engine) We have this problem: "engine" gluster volume have always unsynced elements and we cant' fix the problem, on command line we have tried to use the "heal" command but elements remain always unsynced .... Below the heal command "status": [root@node01 ~]# gluster volume heal engine info Brick node01:/gluster/engine/brick /.shard/8aa74564-6740-403e-ad51-f56d9ca5d7a7.48 /.shard/8aa74564-6740-403e-ad51-f56d9ca5d7a7.64 /.shard/8aa74564-6740-403e-ad51-f56d9ca5d7a7.60 /.shard/8aa74564-6740-403e-ad51-f56d9ca5d7a7.2 /.shard/8aa74564-6740-403e-ad51-f56d9ca5d7a7.68 /8f215dd2-8531-4a4f-b6ed-ea789dd8821b/images/19d71267-52a4-42a3-bb1e-e3145361c0c2/7a215635-02f3-47db-80db-8b689c6a8f01 /8f215dd2-8531-4a4f-b6ed-ea789dd8821b/images/88d41053-a257-4272-9e2e-2f3de0743b81/6573ed08-d3ed-4d12-9227-2c95941e1ad6 /.shard/8aa74564-6740-403e-ad51-f56d9ca5d7a7.61 /.shard/8aa74564-6740-403e-ad51-f56d9ca5d7a7.1 /8f215dd2-8531-4a4f-b6ed-ea789dd8821b/dom_md/ids /.shard/8aa74564-6740-403e-ad51-f56d9ca5d7a7.20 /__DIRECT_IO_TEST__ Status: Connected Number of entries: 12 Brick node02:/gluster/engine/brick /8f215dd2-8531-4a4f-b6ed-ea789dd8821b/images/19d71267-52a4-42a3-bb1e-e3145361c0c2/7a215635-02f3-47db-80db-8b689c6a8f01 <gfid:9a601373-bbaa-44d8-b396-f0b9b12c026f> /8f215dd2-8531-4a4f-b6ed-ea789dd8821b/dom_md/ids <gfid:1e309376-c62e-424f-9857-f9a0c3a729bf> <gfid:e3565b50-1495-4e5b-ae88-3bceca47b7d9> <gfid:4e33ac33-dddb-4e29-b4a3-51770b81166a> /__DIRECT_IO_TEST__ <gfid:67606789-1f34-4c15-86b8-c0d05b07f187> <gfid:9ef88647-cfe6-4a35-a38c-a5173c9e8fc0> /8f215dd2-8531-4a4f-b6ed-ea789dd8821b/images/88d41053-a257-4272-9e2e-2f3de0743b81/6573ed08-d3ed-4d12-9227-2c95941e1ad6 <gfid:9ad720b2-507d-4830-8294-ec8adee6d384> <gfid:d9853e5d-a2bf-4cee-8b39-7781a98033cf> Status: Connected Number of entries: 12 Brick node04:/gluster/engine/brick Status: Connected Number of entries: 0 running the "gluster volume heal engine" don't solve the problem... Some extra info: We have recently changed the gluster from: 2 (full repliacated) + 1 arbiter to 3 full replicated cluster but i don't know this is the problem... The "data" volume is good and healty and have no unsynced entry. Ovirt refuse to put the node02 and node01 in "maintenance mode" and complains about "unsynced elements" How can I fix this? Thank you

4 20

imageio: Error setting ImageProxyAddress's value. No such entry with version general.
by Richard Chan 28 Aug '17

28 Aug '17

oVirt 4.1.4 - engine-setup of imageio proxy on a host, at the end it requires: engine-config -s ImageProxyAddress=xxxxxxxx:54323 But on engine: Error setting ImageProxyAddress's value. No such entry with version general. Any ideas thanks! -- Richard Chan

2 1

oVIRT Node / Network Manager / oVirt 4.1
by Devin Acosta 13 Aug '17

13 Aug '17

I noticed that for some reason when I am running oVirt node on my hosts and disabled NetworkManager it appears that it kept turning itself back on, and my understanding is that Network Manager should be disabled. I had to force remove Network Manager in order to get it to stay disabled. I have been seeing strangeness with my VM's where they disconnect, and where hosted-engine keeps trying to non-stop migrate to another host. Just wanted to first confirm about Network Manager and oVirt Node image. -- Devin Acosta Red Hat Certified Architect

2 1

Problemas with ovirtmgmt network used to connect VMs
by FERNANDO FREDIANI 08 Aug '17

08 Aug '17

Has anyone had problem when using the ovirtmgmt bridge to connect VMs ? I am still facing a bizarre problem where some VMs connected to this bridge stop passing traffic. Checking the problem further I see its mac address stops being learned by the bridge and the problem is resolved only with a VM reboot. When I last saw the problem I run brctl showmacs ovirtmgmt and it shows me the VM's mac adress with agening timer 200.19. After the VM reboot I see the same mac with agening timer 0.00. I don't see it in another environment where the ovirtmgmt is not used for VMs. Does anyone have any clue about this type of behavior ? Fernando

2 7

supervdsmd IOError to /dev/stdout
by Richard Chan 03 Aug '17

03 Aug '17

After an upgrade to 4.0 I have a single host that cannot start supervdsmd because of IOError on /dev/stdout. All other hosts upgraded correctly. In the systemd unit I have to hack StandardOutput=null. Any thing I have overlooked? The hosts are all identical and it is just this one that has this weird behaviour. -- Richard Chan

4 7

After upgrading to 4.1.4 unable to start VM or migrate them
by Arman Khalatyan 02 Aug '17

02 Aug '17

Hi, I am running in to trouble with 4.1.4 after engine upgrade I am not able to start or migrate virtual machines: getting following error: General command validation failure Are there any workarounds?

5 11

sanlock ids file broken after server crash
by Johan Bernhardsson 02 Aug '17

02 Aug '17

Hello, The ids file for sanlock is broken on one setup. The first host id in the file is wrong. >From the logfile i have: verify_leader 1 wrong space name 0924ff77-ef51-435b-b90d-50bfbf2e�ke7 0924ff77-ef51-435b-b90d-50bfbf2e8de7 /rhev/data-center/mnt/glusterSD/ Note the broken char in the space name. This also apears. And it seams as the hostid too is broken in the ids file: leader4 sn 0924ff77-ef51-435b-b90d-50bfbf2e�ke7 rn ��7afa5-3a91-415b- a04c-221d3e060163.vbgkvm01.a ts 4351980 cs eefa4dd7 Note the broken chars there as well. If i check the ids file with less or strings the first row where my vbgkvm01 host are. That has broken chars. Can this be repaired in some way without taking down all the virtual machines on that storage? /Johan

3 6

VDSM Command failed: Heartbeat Exceeded
by Neil 02 Aug '17

02 Aug '17

Hi guys, Please could someone assist me, my DC seems to be trying to re-negotiate SPM and apparently it's failing. I tried to delete an old autogenerated snapshot and shortly after that the issue seemed to start, however after about an hour, the snapshot said successfully deleted, and then SPM negotiated again albeit for a short period before it started trying to re-negotiate again. Last week I upgraded from ovirt 3.5 to 3.6, I also upgraded one of my 4 hosts using the 3.6 repo to the latest available from that repo and did a yum update too. I have 4 nodes and my ovirt engine is a KVM guest on another physical machine on the network. I'm using an FC SAN with ATTO HBA's and recently we've started seeing some degraded IO. The SAN appears to be alright and the disks all seem to check out, but we are having rather slow IOPS at the moment, which we trying to track down. ovirt engine CentOS release 6.9 (Final) ebay-cors-filter-1.0.1-0.1.ovirt.el6.noarch ovirt-engine-3.6.7.5-1.el6.noarch ovirt-engine-backend-3.6.7.5-1.el6.noarch ovirt-engine-cli-3.6.2.0-1.el6.noarch ovirt-engine-dbscripts-3.6.7.5-1.el6.noarch ovirt-engine-extension-aaa-jdbc-1.0.7-1.el6.noarch ovirt-engine-extensions-api-impl-3.6.7.5-1.el6.noarch ovirt-engine-jboss-as-7.1.1-1.el6.x86_64 ovirt-engine-lib-3.6.7.5-1.el6.noarch ovirt-engine-restapi-3.6.7.5-1.el6.noarch ovirt-engine-sdk-python-3.6.7.0-1.el6.noarch ovirt-engine-setup-3.6.7.5-1.el6.noarch ovirt-engine-setup-base-3.6.7.5-1.el6.noarch ovirt-engine-setup-plugin-ovirt-engine-3.6.7.5-1.el6.noarch ovirt-engine-setup-plugin-ovirt-engine-common-3.6.7.5-1.el6.noarch ovirt-engine-setup-plugin-vmconsole-proxy-helper-3.6.7.5-1.el6.noarch ovirt-engine-setup-plugin-websocket-proxy-3.6.7.5-1.el6.noarch ovirt-engine-tools-3.6.7.5-1.el6.noarch ovirt-engine-tools-backup-3.6.7.5-1.el6.noarch ovirt-engine-userportal-3.6.7.5-1.el6.noarch ovirt-engine-vmconsole-proxy-helper-3.6.7.5-1.el6.noarch ovirt-engine-webadmin-portal-3.6.7.5-1.el6.noarch ovirt-engine-websocket-proxy-3.6.7.5-1.el6.noarch ovirt-engine-wildfly-8.2.1-1.el6.x86_64 ovirt-engine-wildfly-overlay-8.0.5-1.el6.noarch ovirt-host-deploy-1.4.1-1.el6.noarch ovirt-host-deploy-java-1.4.1-1.el6.noarch ovirt-image-uploader-3.6.0-1.el6.noarch ovirt-iso-uploader-3.6.0-1.el6.noarch ovirt-release34-1.0.3-1.noarch ovirt-release35-006-1.noarch ovirt-release36-3.6.7-1.noarch ovirt-setup-lib-1.0.1-1.el6.noarch ovirt-vmconsole-1.0.2-1.el6.noarch ovirt-vmconsole-proxy-1.0.2-1.el6.noarch node01 (CentOS 6.9) vdsm-4.16.30-0.el6.x86_64 vdsm-cli-4.16.30-0.el6.noarch vdsm-jsonrpc-4.16.30-0.el6.noarch vdsm-python-4.16.30-0.el6.noarch vdsm-python-zombiereaper-4.16.30-0.el6.noarch vdsm-xmlrpc-4.16.30-0.el6.noarch vdsm-yajsonrpc-4.16.30-0.el6.noarch gpxe-roms-qemu-0.9.7-6.16.el6.noarch qemu-img-rhev-0.12.1.2-2.479.el6_7.2.x86_64 qemu-kvm-rhev-0.12.1.2-2.479.el6_7.2.x86_64 qemu-kvm-rhev-tools-0.12.1.2-2.479.el6_7.2.x86_64 libvirt-0.10.2-62.el6.x86_64 libvirt-client-0.10.2-62.el6.x86_64 libvirt-lock-sanlock-0.10.2-62.el6.x86_64 libvirt-python-0.10.2-62.el6.x86_64 node01 was upgraded out of desperation after I tried changing my DC and cluster version to 3.6, but then found that none of my hosts could be activated out of maintenance due to an incompatibility with 3.6 (I'm still not sure why as searching seemed to indicate Centos 6.x was compatible. I then had to remove all 4 hosts, and change the cluster version back to 3.5 and then re-add them. When I tried changing the cluster version to 3.6 I did get a complaint about using the "legacy protocol" so on each host under Advanced, I changed them to use the JSON protocol, and this seemed to resolve it, however once changing the DC/Cluster back to 3.5 the option to change the protocol back to Legacy is no longer shown. node02 (Centos 6.7) vdsm-4.16.30-0.el6.x86_64 vdsm-cli-4.16.30-0.el6.noarch vdsm-jsonrpc-4.16.30-0.el6.noarch vdsm-python-4.16.30-0.el6.noarch vdsm-python-zombiereaper-4.16.30-0.el6.noarch vdsm-xmlrpc-4.16.30-0.el6.noarch vdsm-yajsonrpc-4.16.30-0.el6.noarch gpxe-roms-qemu-0.9.7-6.14.el6.noarch qemu-img-rhev-0.12.1.2-2.479.el6_7.2.x86_64 qemu-kvm-rhev-0.12.1.2-2.479.el6_7.2.x86_64 qemu-kvm-rhev-tools-0.12.1.2-2.479.el6_7.2.x86_64 libvirt-0.10.2-54.el6_7.6.x86_64 libvirt-client-0.10.2-54.el6_7.6.x86_64 libvirt-lock-sanlock-0.10.2-54.el6_7.6.x86_64 libvirt-python-0.10.2-54.el6_7.6.x86_64 node03 CentOS 6.7 vdsm-4.16.30-0.el6.x86_64 vdsm-cli-4.16.30-0.el6.noarch vdsm-jsonrpc-4.16.30-0.el6.noarch vdsm-python-4.16.30-0.el6.noarch vdsm-python-zombiereaper-4.16.30-0.el6.noarch vdsm-xmlrpc-4.16.30-0.el6.noarch vdsm-yajsonrpc-4.16.30-0.el6.noarch gpxe-roms-qemu-0.9.7-6.14.el6.noarch qemu-img-rhev-0.12.1.2-2.479.el6_7.2.x86_64 qemu-kvm-rhev-0.12.1.2-2.479.el6_7.2.x86_64 qemu-kvm-rhev-tools-0.12.1.2-2.479.el6_7.2.x86_64 libvirt-0.10.2-54.el6_7.6.x86_64 libvirt-client-0.10.2-54.el6_7.6.x86_64 libvirt-lock-sanlock-0.10.2-54.el6_7.6.x86_64 libvirt-python-0.10.2-54.el6_7.6.x86_64 node04 (Centos 6.7) vdsm-4.16.20-1.git3a90f62.el6.x86_64 vdsm-cli-4.16.20-1.git3a90f62.el6.noarch vdsm-jsonrpc-4.16.20-1.git3a90f62.el6.noarch vdsm-python-4.16.20-1.git3a90f62.el6.noarch vdsm-python-zombiereaper-4.16.20-1.git3a90f62.el6.noarch vdsm-xmlrpc-4.16.20-1.git3a90f62.el6.noarch vdsm-yajsonrpc-4.16.20-1.git3a90f62.el6.noarch gpxe-roms-qemu-0.9.7-6.15.el6.noarch qemu-img-0.12.1.2-2.491.el6_8.1.x86_64 qemu-kvm-0.12.1.2-2.491.el6_8.1.x86_64 qemu-kvm-tools-0.12.1.2-2.503.el6_9.3.x86_64 libvirt-0.10.2-60.el6.x86_64 libvirt-client-0.10.2-60.el6.x86_64 libvirt-lock-sanlock-0.10.2-60.el6.x86_64 libvirt-python-0.10.2-60.el6.x86_64 I'm seeing a rather confusing error in the /var/log/messages on all 4 hosts as follows.... Jul 31 16:41:36 node01 multipathd: 36001b4d80001c80d0000000000000000: sdb - directio checker reports path is down Jul 31 16:41:41 node01 kernel: sd 7:0:0:0: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK Jul 31 16:41:41 node01 kernel: sd 7:0:0:0: [sdb] CDB: Read(10): 28 00 00 00 00 00 00 00 01 00 Jul 31 16:41:41 node01 kernel: end_request: I/O error, dev sdb, sector 0 I say confusing, because I don't have a 3000GB LUN [root@node01 ~]# fdisk -l | grep 3000 Disk /dev/sdb: 3000.0 GB, 2999999528960 bytes I did have one on Friday, last week, but I trashed it and changed it to a 1500GB LUN instead, so I'm not sure if perhaps this error is still trying to connect to the old LUN perhaps? My LUNS are as follows... Disk /dev/sdb: 3000.0 GB, 2999999528960 bytes (this one doesn't actually exist anymore) Disk /dev/sdc: 1000.0 GB, 999999668224 bytes Disk /dev/sdd: 1000.0 GB, 999999668224 bytes Disk /dev/sde: 1000.0 GB, 999999668224 bytes Disk /dev/sdf: 1000.0 GB, 999999668224 bytes Disk /dev/sdg: 1000.0 GB, 999999668224 bytes Disk /dev/sdh: 1000.0 GB, 999999668224 bytes Disk /dev/sdi: 1000.0 GB, 999999668224 bytes Disk /dev/sdj: 1000.0 GB, 999999668224 bytes Disk /dev/sdk: 1000.0 GB, 999999668224 bytes Disk /dev/sdm: 1000.0 GB, 999999668224 bytes Disk /dev/sdl: 1000.0 GB, 999999668224 bytes Disk /dev/sdn: 1000.0 GB, 999999668224 bytes Disk /dev/sdo: 1000.0 GB, 999999668224 bytes Disk /dev/sdp: 1000.0 GB, 999999668224 bytes Disk /dev/sdq: 1000.0 GB, 999999668224 bytes Disk /dev/sdr: 1000.0 GB, 999988133888 bytes Disk /dev/sds: 1500.0 GB, 1499999764480 bytes Disk /dev/sdt: 1500.0 GB, 1499999502336 bytes I'm quite low on SAN disk space currently so I'm a little hesitant to migrate VM's around for fear of the migrations creating too many snapshots and filling up my SAN. We are in the process of expanding the SAN Array too, but we trying to get to the bottom of the bad IOPS at the moment before adding on addition overhead. Ping tests between hosts and engine all look alright, so I don't suspect network issues. I know this is very vague, everything is currently operational, however as you can see in the attached logs, I'm getting lots of ERROR messages. Any help or guidance is greatly appreciated. Thanks. Regards. Neil Wilson.

2 2

oVirt and Foreman
by Davide Ferrari 01 Aug '17

01 Aug '17

Hello list is anybody successfully using oVirt + Foreman for VM creation + provisioning? I'm using Foremn (latest version, 1.15.2) with latest oVirt version (4.1.3) but I'm encountering several problem, especially related to disks. For example: - cannot create a VM with multiple disks though Foreman CLI (hammer) - if I create a multidisk VM from Foreman, the second disk always gets the "bootable" flag and not the primary image, making the VMs not bootable at all. Any other Foreman user sharing the pain here? Foramn's list is not so useful so I'm trying to ask here. How do you programmatically create virtual machines with oVirt and Foreman? Should I switch do directly using oVirt API? Thanks in advance Davide

5 15

Deploying training lab
by Andy Michielsen 01 Aug '17

01 Aug '17

Hello all, Don't know if this is the right place to ask this but I would like to set up a trainingslab with oVirt. I have deployed an engine and a host with local storage and want to run 1 server and 5 desktops off it. But the desktops will be used on thin clients or old laptops with some minimal os installation running spice client or a webbrowser. I was wondering if anyone can give me pointer in how to set up a minimal laptop which only need to run an spice client. Kind regards.

3 5