- Users - oVirt List Archives

Problems with vdsm-tool and ovn-config option
by Gianluca Cecchi 13 Jul '17

13 Jul '17

Hello, on February I installed OVN controller on some hypervisors (CentOS 7.3 hosts). At that time the vdsm-tool command was part of vdsm-python-4.19.4-1.el7.centos.noarch I was able to configure my hosts with command vdsm-tool ovn-config OVN_central_server_IP local_OVN_tunneling_IP as described here: https://www.ovirt.org/blog/2016/11/ovirt-provider-ovn/ and now here https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/ht… I have 2 hosts that I added later and on which I want to configure OVN external network provider too. But now, with vdsm-python at version vdsm-python-4.19.10.1-1.el7.centos.noarch I get an usage error trying to execute the command [root@ov301 ~]# vdsm-tool ovn-config 10.4.192.43 10.4.167.41 Usage: /bin/vdsm-tool [options] <action> [arguments] Valid options: -h, --help Show this help menu. -l, --logfile <path> ... Also, the changelog of the package seems quite broken: [root@ov301 ~]# rpm -q --changelog vdsm-python * Wed Aug 03 2016 Yaniv Bronhaim <ybronhei(a)redhat.com> - 4.18.999 - Re-review of vdsm.spec to return it to fedora Bug #1361659 * Sun Oct 13 2013 Yaniv Bronhaim <ybronhei(a)redhat.com> - 4.13.0 - Removing vdsm-python-cpopen from the spec - Adding dependency on formal cpopen package * Sun Apr 07 2013 Yaniv Bronhaim <ybronhei(a)redhat.com> - 4.9.0-1 - Adding cpopen package * Wed Oct 12 2011 Federico Simoncelli <fsimonce(a)redhat.com> - 4.9.0-0 - Initial upstream release * Thu Nov 02 2006 Simon Grinberg <simong(a)qumranet.com> - 0.0-1 - Initial build [root@ov301 ~]# How can I configure OVN? Thanks in advance, Gianluca

1 1

Manually moving disks from FC to iSCSI
by Gianluca Cecchi 13 Jul '17

13 Jul '17

Hello, I have a source oVirt environment with storage domain on FC I have a destination oVirt environment with storage domain on iSCSI The two environments can communicate only via the network of their respective hypervisors. The source environment, in particular, is almost isolated and I cannot attach an export domain to it or something similar. So I'm going to plan a direct move through dd of the disks of some VMs The workflow would be On destination create a new VM with same config and same number of disks of the same size of corresponding source ones. Also I think same allocation policy (thin provision vs preallocated) Using lvs -o+lv_tags I can detect the names of my origin and destination LVs, corresponding to the disks When a VM is powered down, the LV that maps the disk will be not open, so I have to force its activation (both on source and on destination) lvchange --config 'global {use_lvmetad=0}' -ay vgname/lvname copy source disk with dd through network (I use gzip to limit network usage basically...) on src_host: dd if=/dev/src_vg/src_lv bs=1024k | gzip | ssh dest_host "gunzip | dd bs=1024k of=/dev/dest_vg/dest_lv" deactivate LVs on source and dest lvchange --config 'global {use_lvmetad=0}' -an vgname/lvname Try to power on the VM on destination Some questions: - about overall workflow - about dd flags, in particular if source disks are thin vs preallocated Thanks, Gianluca

3 5

Bizzare oVirt network problem
by FERNANDO FREDIANI 13 Jul '17

13 Jul '17

This is a multi-part message in MIME format. --------------2363491D1BDE9DA861A526B0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hello. I am facing a pretty bizzare problem in two of my Nodes running oVirt. A given VM running a few hundred Mbps of traffic simply stops passing traffic and only recovers after a reboot. Checking the bridge with 'brctl showmacs BRIDGE' I see the VM's MAC address missing during this event. It seems the bridge simply unlearn the VM's mac address which only returns when the VM is rebooted. This problems happened in two different Nodes running in different hardware, in different datacenter, in different network architecture, different switch vendors and different bonding modes. The main differences these Nodes have compared to others I have and which don't show this problem are: - The CentOS 7 installed is a Minimal installation instead of oVirt-NG - The Kernel used is 4.12 (elrepo) instead of the default 3.10 - The ovirtmgmt network is used also for the Virtual Machine showing this problem. Has anyone have any idea if it may have anything to do with oVirt (any filters) or any of the components different from a oVirt-NG installation ? Thanks Fernando --------------2363491D1BDE9DA861A526B0 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body bgcolor="#FFFFFF" text="#000000"> Hello. I am facing a pretty bizzare problem in two of my Nodes running oVirt. A given VM running a few hundred Mbps of traffic simply stops passing traffic and only recovers after a reboot. Checking the bridge with 'brctl showmacs BRIDGE' I see the VM's MAC address missing during this event. It seems the bridge simply unlearn the VM's mac address which only returns when the VM is rebooted. This problems happened in two different Nodes running in different hardware, in different datacenter, in different network architecture, different switch vendors and different bonding modes. The main differences these Nodes have compared to others I have and which don't show this problem are: - The CentOS 7 installed is a Minimal installation instead of oVirt-NG - The Kernel used is 4.12 (elrepo) instead of the default 3.10 - The ovirtmgmt network is used also for the Virtual Machine showing this problem. Has anyone have any idea if it may have anything to do with oVirt (any filters) or any of the components different from a oVirt-NG installation ? Thanks Fernando </body> </html> --------------2363491D1BDE9DA861A526B0--

2 3

Deleted the default Datacenter and hosted-engine was there...
by Vinícius Ferrão 13 Jul '17

13 Jul '17

Hello, As someone may know I’m learning my way through oVirt. During the configuration of the my production oVirt pool I’ve created a new datacenter and a cluster to put my hosts and deleted the default one. But now I don’t know what to do. I can’t add one of my machines to the new datacenter since it’s still on the “old” and deleted Datacenter. The hosted engine is running on the same machine. What are the next steps? I think I’ve screwed all the installation removing the default DC. Any help is appreciated, V. PS: I still have access to the Hosted Engine, and it’s running fine.

1 0

[ovirt 4.1] how to increase HA VM retry count ?
by TranceWorldLogic . 13 Jul '17

13 Jul '17

Hi, I have created HA VM with priority as High. And then I block host network connection using firewall rule as shown below. e.g. iptables -I INPUT -j DROP; iptables -I OUTPUT -j DROP; As expected ovirt had call fencing to power off host and power on it again. At backgroud ovirt tried 10 time to start that VM but as host down it fail to start. And after 10 trial it giveup to start VM. Is there any way to increase trail count ? And also let me know how to change retry timer. Thanks, ~Rohit

3 4

Add disk image from node command line?
by Chris Adams 12 Jul '17

12 Jul '17

I have a qcow2 disk image sitting on the local filesystem of one node. Is there a way to copy this image to oVirt (into an iSCSI storage domain) without copying it to my desktop and uploading through the web UI? -- Chris Adams <cma(a)cmadams.net>

1 0

trying to use raw disks from foreign KVM directly in oVirt
by Matthias Leopold 12 Jul '17

12 Jul '17

hi, i'm using a KVM system that creates it's disks in raw format as LVM logical volumes. there's one VG with one LV per disk. the physical devices for these LVM entities are iSCSI devices. now my idea was to use these disks directly in oVirt as "Direct LUN". i did the following: - stopped the foreign KVM domain - deactivated the LV that is the disk - reconfigured the SAN so the iSCSI device is removed from foreign KVM host and is visible to the oVirt hosts - created an oVirt "Direct LUN" disk with the iSCSI device - created a VM in oVirt, attached the "Direct LUN" disk to it and set the "bootable" flag - started the VM - console displays "boot failed: not a bootable disk" :-( i tried virtIO, virtIO-SCSI, IDE interfaces for the disk, no change i ran "scan alignment" for the disk, no change i tried without bootable flag, no change strange thing is the wrong virtual size the oVirt GUI display for this disk, GUI says virtual size is 372GB, "qemu-img info" (in the oVirt host) says virtual size is 47GB (which was the size in the foreign KVM system) what could be wrong? can this work at all? could LVM metadata from the old system be a problem? i know the whole operation is a litte crazy, but if this worked the migration process would be so much easier... thx matthias

1 0

[ovirt 4.1] tutorial for external Scheduling policy
by TranceWorldLogic . 12 Jul '17

12 Jul '17

Hi, Can some one point me to some document or tutorial for external Scheduling policy ? I want to understand this feature "external scheduling policy" but not got any idea how to implement that. Please point me some document [best will be tutorial or sample code]. Thanks, ~Rohit

2 1

oVIRT 4.1 / iSCSI Multipathing / Dell Compellent
by Devin Acosta 12 Jul '17

12 Jul '17

I just installed a brand new Dell Compellent SAN for use with our oVIRT 4.1.3 fresh installation. I presented a LUN of 30TB to the cluster over iSCSI 10G. I went into the Storage domain and added a new storage mount called “dell-storage” and logged into each of the ports for the target. It detects the targets just right and the Dell SAN is happy, until a host is rebooted at which point the iSCSI seems to choose to log into only one of the controllers and not all the paths that it originally logged into. At this point the Dell SAN shows only 1/2 connected and therefore my e-mail. When I looked at the original iscsiadm session information after initially joining to domain it shows correct connected to (1f,21,1e,20) ports. tcp: [11] 10.4.77.100:3260,0 iqn.2002-03.com.compellent:5000d310013dfe1f (non-flash) tcp: [12] 10.4.77.100:3260,0 iqn.2002-03.com.compellent:5000d310013dfe21 (non-flash) tcp: [13] 10.4.78.100:3260,0 iqn.2002-03.com.compellent:5000d310013dfe1e (non-flash) tcp: [14] 10.4.78.100:3260,0 iqn.2002-03.com.compellent:5000d310013dfe20 (non-flash) tcp: [15] 10.4.77.100:3260,0 iqn.2002-03.com.compellent:5000d310013dfe1f (non-flash) tcp: [16] 10.4.78.100:3260,0 iqn.2002-03.com.compellent:5000d310013dfe1e (non-flash) After I reboot the hypervisor and it re-connects to the cluster it shows: tcp: [1] 10.4.78.100:3260,0 iqn.2002-03.com.compellent:5000d310013dfe1e (non-flash) tcp: [2] 10.4.78.100:3260,0 iqn.2002-03.com.compellent:5000d310013dfe1e (non-flash) tcp: [3] 10.4.77.100:3260,0 iqn.2002-03.com.compellent:5000d310013dfe1f (non-flash) tcp: [4] 10.4.77.100:3260,0 iqn.2002-03.com.compellent:5000d310013dfe1f (non-flash) What is bizarre is it shows multiple connections to the same IP but it shows 2 connections to 1e, and 2 connections to 1f. It seems to selected only the top controller on each fault domain and not the bottom controller also. I did configure a “bond” inside the iSCSI Multipathing of selecting only the 2 VLANS together for the iSCSI. I didn’t select a target with it because wasn’t sure the proper configuration for this. If I selected both virtual and target port the cluster goes down hard. Any ideas? Devin Acosta

1 0

Detach disk from one VM, attach to another VM
by Davide Ferrari 11 Jul '17

11 Jul '17

Hello I'm using oVirt 4.1.3 and I was wondering if it's possible to detach a disk created specifically for a VM from that VM and attach it to another VM. Reading this https://www.ovirt.org/documentation/admin-guide/chap-Virtual_Machine_Disks/ it seems that's only possible with floating virtual disks, but I have a disk that was created for a specific VM. Thanks!

1 0