Is ovirt 3.1 include this patch?
Author: Eli Mesika <emesika(a)redhat.com>
Date: Sun Jul 15 18:08:32 2012 +0300
I used the latest vdsm, and found create vm with cdrom failed because of
Author: Eli Mesika <emesika(a)redhat.com>
Date: Sun Jul 15 18:22:11 2012 +0300
I guess the engine side should include patch e548c72e to make it work
Can someone tell me whether setting positive and negative VM affinity rules
will be at all possible with oVirt at some point in time, i.e. is this on
I need to be able to tell VM's to run on different hosts, spread them
around, so to speak. For example, domain controllers would be better off
running on as many different hypervisors as possible, the way I see it.
That way, the failure of a single hypervisor has minimal impact on the
infrastructure. I know there is a feature to pin VM's to a single
hypervisor, but that's not quite the same. I would like to group the domain
controllers and then tell them not to run on the same host as other members
of that group as much as possible.
The other way around would be nice as well: have several VM's run on the
same hardware. For example, a three tiered web application would probably
perform better if the VM's are all on the same hypervisor. I know I could
pin them all to the same hypervisor, but still: that's not quite the same.
I want to be able to group the web app VM's and tell them to try to run on
the same hypervisors as the other members of the group, so they can move to
another hypervisor as a group if the need arises.
Apologies if this has been asked before or documented in some place I
haven't looked yet.
Maxim Burgerhout <maxim(a)wzzrd.com>
I'm just in process of setting up an ovirt environment again. Using ovirt node HV 2.3.0, on fibre channel storage. I'm forced to use Fedora 16, since Fedora 17 doesn't work with fibre channel storage or at least not with Qlogic HBA's. I've allready told the list and Fedora forum that.
I asked some related questions before around fc storage with oVirt, and I will be back with more.
Anyway, I set up the oVirt node HV on a single LUN of 2 Gb, I've done it before on 1 Gb, and I tried it on 200 Mb. 200 Mb was too small, because it stopped at 25% and didn't want to go further. But the installation started without reporting it beeing too small, which is a bit odd, isn't it?
Anyway, 1 or 2 Gb works fine! When I enter the shell in the HV and run pvs the first time, I see this:
[root@node1 admin]# pvs PV VG Fmt Attr PSize PFree /dev/mapper/3600144f0e03a46000000501798dd0001p4 HostVG lvm2 a-- 288.00m 0
PSize say's 288.00m.
LUN is a thin provisioned LUN made from qcow2 zfs, so maybe it only reports the size that are used? Anyway, I just added a second LUN, for using as VM storage. Here you can see:
[root@node1 admin]# cat /proc/scsi/scsi
Host: scsi1 Channel: 00 Id: 00 Lun: 00 Vendor: HL-DT-ST Model: RW/DVD GCC-T10N Rev: 1.00 Type: CD-ROM ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 00 Lun: 00 Vendor: OI Model: COMSTAR Rev: 1.0 Type: Direct-Access ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 00 Lun: 01 Vendor: OI Model: COMSTAR Rev: 1.0 Type: Direct-Access ANSI SCSI revision: 05
But when I run pvs again in the HV, the new LUN doesn't show up. Note that I restarted the HV, because I ran pvs also before restarting it, and thought I needed to restart it for beeing able to see it through LVM. But LVM haven't yet touched it, or perhaps not seen it? Is it so that LVM on the HV doesn't see other LUN's than the first LUN, if it is not there during installation?
Last time I installed, I did the opposite, I installed with system LUN and with data LUN, and then LVM could see both LUN's, though I couldn't use the data LUN for storage. I've allready reported that.
So I wonder what is the right way of doing it, install with only system LUN and than add data LUN after, or install with both system LUN and data LUN?
I suppose it would be the best if both way's worked?
I get back with more info later, when I tried to connect the storage LUN through the engine...
I'm trying to create a User, going in the Users tab and then clicking add,
however, no field appears to me to fill out, just the option to search
This is some error oVirt?
“Encarada do ponto de vista da juventude, a vida parece um futuro
indefinidamente longo, ao passo que, na velhice, ela parece um passado
deveras curto. Assim, a vida no seu início se apresenta do mesmo modo
que as coisas quando as olhamos através de um binóculo usado ao contrário;
seu final, ela se parece com as coisas tal qual são vistas quando o
é usado de modo normal. Um homem precisa ter envelhecido e vivido
bastante para perceber como a vida é curta”.
(Poema de Arthur Schopenhauer)
I'm having trouble getting a F17 system added to engine. The symtoms
are in the engine UI, it says the install falls. I'm using the latest
On the end-point, the bootstrap log shows success.
However, when I attempt to test the vdsm install with:
vdsClient -s 0 getVdsCaps
I get a nice ssl error:
[root@hungerforce tmp]# vdsClient -s 0 getVdsCaps
Traceback (most recent call last):
File "/usr/share/vdsm/vdsClient.py", line 2275, in <module>
code, message = commands[command](commandArgs)
File "/usr/share/vdsm/vdsClient.py", line 403, in do_getCap
File "/usr/lib64/python2.7/xmlrpclib.py", line 1224, in __call__
return self.__send(self.__name, args)
File "/usr/lib64/python2.7/xmlrpclib.py", line 1578, in __request
File "/usr/lib64/python2.7/xmlrpclib.py", line 1264, in request
return self.single_request(host, handler, request_body, verbose)
File "/usr/lib64/python2.7/xmlrpclib.py", line 1292, in single_request
File "/usr/lib64/python2.7/xmlrpclib.py", line 1439, in send_content
File "/usr/lib64/python2.7/httplib.py", line 954, in endheaders
File "/usr/lib64/python2.7/httplib.py", line 814, in _send_output
File "/usr/lib64/python2.7/httplib.py", line 776, in send
File "/usr/lib/python2.7/site-packages/vdsm/SecureXMLRPCServer.py", line 98, in connect
File "/usr/lib64/python2.7/ssl.py", line 381, in wrap_socket
File "/usr/lib64/python2.7/ssl.py", line 141, in __init__
SSLError: [Errno 185090050] _ssl.c:340: error:0B084002:x509 certificate routines:X509_load_cert_crl_file:system lib
This problem is because not all of the ssl certs for vdsm are present.
On a working host:
[root@ichigo-dom226 tmp]# find /etc/pki/vdsm -type f
On the host with the error:
[root@hungerforce tmp]# find /etc/pki/vdsm -type f
As it turns out:
These files are generated from:
which is invoked by: deployUtils.instCert()
which is called by: vds_bootstrap_complete.py
So... the question is: why isn't vds_bootstrap_complete.py getting
Also, if I re-run the vdsm-gencerts.sh and validate my certificates I
can get vdsm to work properly on the host (vdsClient -s works)... then
if I go to engine and attempt to Activate, it just say the host is
non-responsive... re-installing re-breaks vdsm since it doesn't generate
the SSL certs.
1. [root@hungerforce tmp]# rpm -qa | egrep "(vdsm|libvirt)"
2. [root@bebop ~]# rpm -qa | egrep "(ovirt-engine|vdsm)"
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx