I have installed the oVirt all in one, and I can log in the user portal
through web browser to see user's VMs.
I am wondering if there is an client Application that can do the same
thing, like VMware Horizon client has version for Windows, Linux and IOS,
Department of Computer Science &Technology
Beijing, 100871, PRC
This is a multi-part message in MIME format.
Content-Type: text/plain; charset=utf-8; format=flowed
can anybody help me with importing oVirt DB v.3.5 to new clean oVIrt 3.6
# engine-backup --mode=restore --file=./backup --log=./restore.log
Preparing to restore:
- Unpacking file './backup'
FATAL: Backup version '3.6' doesn't match installed version
How to FIX it ??
Content-Type: text/html; charset=utf-8
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<body text="#000066" bgcolor="#FFFFFF">
can anybody help me with importing oVirt DB v.3.5 to new clean oVIrt
3.6 database ??<br>
# engine-backup --mode=restore --file=./backup --log=./restore.log<br>
Preparing to restore:<br>
- Unpacking file './backup'<br>
FATAL: Backup version '3.6' doesn't match installed version<br>
How to FIX it ??<br>
One of the host is down with H/w issue and and the vms which are using the
resources like (CPU and RAM ) in the faulty node are locked .
Is there any way to release these and deploy them in another host ? below
are the logs.
2015-11-06 11:28:31,866 INFO
[org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor)
Connecting to pbuovirt4.bnglab.psecure.net/10.206.68.4
2015-11-06 11:28:31,867 WARN
[org.ovirt.vdsm.jsonrpc.client.utils.retry.Retryable] (SSL Stomp Reactor)
2015-11-06 11:28:31,867 ERROR
(DefaultQuartzScheduler_Worker-87) Exception during connection
2015-11-06 11:28:31,868 ERROR
GetCapabilitiesVDSCommand(HostName = pbuovirt4, HostId =
vds=Host[pbuovirt4,9d56d598-0c0f-49d7-ba53-8d0b41083b0f]) execution failed.
Exception: VDSNetworkException: java.net.ConnectException: Connection
2015-11-06 11:28:31,868 WARN [org.ovirt.engine.core.vdsbroker.VdsManager]
(DefaultQuartzScheduler_Worker-87) Host pbuovirt4 is not responding. It
will stay in Connecting state for a grace period of 122 seconds and after
that an attempt to fence the host will be issued.
2015-11-06 11:28:31,873 ERROR
(DefaultQuartzScheduler_Worker-87) Failure to refresh Vds runtime info:
java.net.ConnectException: Connection refused
I'm writing a python script to draw a graph of the disks and virtual
machines in relation to their "position" in the data center.
I am using pygraphviz to draw the graph, I found the vm and their disks, data
centers and their storage domains, but I can not connect the disks to the
Here's the code I'm using:
import pygraphviz as PG
from ovirtsdk.api import API
from ovirtsdk.xml import params
A = PG.AGraph(directed=True, strict=False)
VERSION = params.Version(major='3', minor='0')
URL = 'https://xxx/api'
USERNAME = 'xxx'
PASSWORD = 'yyyy'
api = API ( url=URL,
for vm in api.vms.list():
for disco in vm.get_disks().list():
for dc in api.datacenters.list():
for dc_storage in dc.storagedomains.list():
A.draw('ovirt_graph.png') # draw png
Hello oVirt guru out there:
I notice our oVirt engine postgres db size is growing quite fast for past couple of months. I checked the database size. Found that our ovirt_engine_history is 73GB in size.
engine=# \connect ovirt_engine_history
You are now connected to database "ovirt_engine_history" as user "postgres".
ovirt_engine_history=# SELECT pg_size_pretty( pg_database_size( current_database() ) ) As human_size
, pg_database_size( current_database() ) As raw_size;
human_size | raw_size
73 GB | 78444213368
Brief check the records, there are entries dated back 2014.
I want to see if there is a safe way to archive and remove some of the older records?
The oVirt Project is pleased to announce the availability
of the Second oVirt 3.5.6 Release Candidate for testing, as of
November 5th, 2015.
This release is available now for
Red Hat Enterprise Linux 6.7, CentOS Linux 6.7 (or similar) and
Red Hat Enterprise Linux 7.1, CentOS Linux 7.1 (or similar).
This release supports Hypervisor Hosts running
Red Hat Enterprise Linux 6.7, CentOS Linux 6.7 (or similar),
Red Hat Enterprise Linux 7.1, CentOS Linux 7.1 (or similar) and Fedora 21.
This release includes updated packages for:
- oVirt Engine
See the release notes  for a list of fixed bugs.
Please refer to release notes  for Installation / Upgrade instructions.
a new oVirt Live ISO will be available soon.
Please note that mirrors may need usually one day before being
Please refer to the release notes for known issues in this release.
Please add yourself to the test page if you're testing this release.
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
Import existing, don't try to create one.
Tal - maybe instead of error we should detect and ask user for ISO domain if they meant to import.
On Nov 5, 2015 9:03 AM, Robert Story <rstory(a)tislabs.com> wrote:
> On Wed, 4 Nov 2015 19:16:58 -0500 Itamar wrote:
> IH> On 11/02/2015 10:14 AM, Robert Story wrote:
> IH> > On Fri, 30 Oct 2015 18:58:33 -0400 Liam wrote:
> IH> > LC> Tried setting up NFS ISO domain which works on one host/local
> IH> > LC> datacenter. I do not want to have to have multiple copies of iso
> IH> > LC> files on all hosts. If I try to import pre-existing ISO domain, I
> IH> > LC> either get an error that storage path exists or the dialog just
> IH> > LC> does nothing.
> IH> >
> IH> > I had the same goal, but for multiple independent ovirt installs. My
> IH> > work-around is to deal with it outside ovirt.
> IH> >
> IH> > - create generic nfs export for my iso mirrors
> IH> > - create iso export points for each install
> IH> > - add iso mount to each install
> IH> > - manually (or using puppet, etc) add mirror mount on each host node
> IH> > - run a script that creates a symlink in each ovirt iso mirror for
> IH> > all the isos in the mirror export
> IH> > - 3.5 handles iso images in subdirectories, but 3.4 does not ,
> IH> > so the script creates symlinks for every iso image in the top level
> IH> > of the iso export for 3.4, while only needing a symlnk to the distro
> IH> > directory fro 3.5.
> IH> >
> IH> > It's a hack, but it works.
> IH> This should work without any hacks. An ISO domain can be shared between
> IH> multiple DCs or Engines.
> IH> Tal?
> When I try and create an iso domain with the same NFS path as another
> domain I get 'the selected storage path is not empty[...] Either remove the
> existing Storage Domain from this path, or change the storage path.'
> Senior Software Engineer @ Parsons