Manually moving disks from FC to iSCSI
by Gianluca Cecchi
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
6 years, 9 months
Bizzare oVirt network problem
by FERNANDO FREDIANI
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">
<font face="arial, helvetica, sans-serif">Hello.<br>
<br>
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.<br>
<br>
It seems the bridge simply unlearn the VM's mac address which only
returns when the VM is rebooted.<br>
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.<br>
<br>
The main differences these Nodes have compared to others I have
and which don't show this problem are:<br>
- The CentOS 7 installed is a Minimal installation instead of
oVirt-NG<br>
- The Kernel used is 4.12 (elrepo) instead of the default 3.10<br>
- The ovirtmgmt network is used also for the Virtual Machine
showing this problem.<br>
<br>
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 ?<br>
<br>
Thanks<br>
Fernando<br>
</font>
</body>
</html>
--------------2363491D1BDE9DA861A526B0--
6 years, 9 months
Deleted the default Datacenter and hosted-engine was there...
by Vinícius Ferrão
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.
6 years, 9 months
[ovirt 4.1] how to increase HA VM retry count ?
by TranceWorldLogic .
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
6 years, 9 months
Add disk image from node command line?
by Chris Adams
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>
6 years, 9 months
trying to use raw disks from foreign KVM directly in oVirt
by Matthias Leopold
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
6 years, 9 months
[ovirt 4.1] tutorial for external Scheduling policy
by TranceWorldLogic .
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
6 years, 9 months
oVIRT 4.1 / iSCSI Multipathing / Dell Compellent
by Devin Acosta
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
6 years, 9 months
Template for imported VMs?
by Eduardo Mayoral
Hi,
I am using oVirt 4.1 and I am importing a significant number of VMs
from VMWare. So far, everything is fine.
However, I find that after importing each VM I have to modify some
parameters of the imported VM (Timezone, VM type from desktop to server,
VNC console...).
I have those parameters changed on the "blank" template, but it
seems that the import process is not picking that template as the base
for the imported VM. Where is the import process picking the defaults
for the imported VM from? Can those be changed? I have failed to find
that information on the docs.
Thanks in advance!
--
Eduardo Mayoral Jimeno (emayoral(a)arsys.es)
Administrador de sistemas. Departamento de Plataformas. Arsys internet.
+34 941 620 145 ext. 5153
6 years, 9 months
