I am trying to run engine-setup utility on rhels6.2 machines to configure ovirt-engine but get an error while starting jboss. (Exception: Error while updating jboss ROOT.war directory) Any ideas what is happening? Thanks
oVirt Engine will be installed using the following configuration:
org-name: NASA LaRC
Proceed with the configuration listed above? (yes|no): yes
Configuring oVirt-engine... [ DONE ]
Creating CA... [ DONE ]
Editing JBoss Configuration... [ ERROR ]
Error while updating jboss ROOT.war directory
Please check log file /var/log/ovirt-engine/engine-setup_2012_05_15_12_23_53.log for more information
File "/usr/share/ovirt-engine/scripts/setup_controller.py", line 54, in runAllSequences
File "/usr/share/ovirt-engine/scripts/setup_sequences.py", line 152, in run
File "/usr/share/ovirt-engine/scripts/setup_sequences.py", line 59, in run
File "/usr/bin/engine-setup", line 906, in _editRootWar
Exception: Error while updating jboss ROOT.war directory
What is the proper process for this in ovirt? Or has someone done it
Greater Boston Vineyard
Director of Operations
I'm attempting to fine-tune the process of getting my KVM/Libvirt
managed VMs over into my new oVirt infrastructure, and the virt-v2v
import is failing in the WUI with "Failed to read VM 'dh-imager01'
OVF, it may be corrupted". I've attached both engine and vdsm logs
that are a snapshot from when I ran the virt-v2v command until I saw
the failure under Events.
virt-v2v command used...
# virt-v2v -i libvirtxml -o rhev -os
virt-v2v: dh-imager01 configured with virtio drivers.
The xml has been modified numerous times based on past mailing list
comments to have VNC and Network information removed, but still the
same failure. I've attached the latest XML that was used in the log's
failure as dh-imager01.xml. I've also tried passing hte bridge device
(ovirtmgmt) in the above command with same failure results.
Node and Engine are both CentOS 6.2, with vdsm-4.10.0-4 and
Please let me know what other configuration information could be
helpful to debug / troubleshoot this.
Are there any other methods besides a virt-v2v migration that can
allow me to use my previous KVM VMs within oVirt?
Last week I pitched the idea of having some demo videos (I called them
"screencasts" although that's not quite accurate) ready before the 3.1
release next week.
I don't have the domain knowledge to do this myself, so I need your help!
What is there to do?
1. Go to http://wiki.ovirt.org/wiki/Screencasts - have a look at the
features I've proposed for the first round of videos. If you really
think one of them shouldn't be there, or there's a really important
feature you'd like to see a demo for, please reply here and we'll
discuss it. You can always add a proposed feature with the skeleton
template to the Screencasts page also, but there's no guarantee we'll
have a video by the time the release comes around. It would helkp me
prioritise if we could gather feedback here.
2. For each feature, we should have a scenario/script for the demo,
* Required pre-requisites and set-up (what do I need to do before I
start the demo)
* A step by step description of how to show the feature being demoed
Right now, only two features are described, and those descriptions may
If you see a feature which is not yet described, and you know how to use
it, please add a little script following the template. If you see a
feature which is not described well enough, please update the description.
3. For each feature with a script, we need a video. I have started a
page to help people record videos of their screen, for the systems I
know about: http://wiki.ovirt.org/wiki/Recording_video - the videos
(without sound) can, I think, be attached to the wiki page - ogv or webm
format preferably, please!
4. For each video, we will need a sound-track. I'm happy to voice over
some of the videos, but again, it would be nice to spread the load.
We're not even here yet, though.
Thanks everyone for your help! It will be greatly appreciated.
Community Action and Impact
Open Source and Standards Team, Red Hat
Phone: +33 9 50 71 55 62
I have an environment where I would like to be able to provide users
with a single web interface from which they would be able to open a
console on either a virtual machine or on a physical machine. Playing
with a clean install of oVirt 3.1 suggests that oVirt is not capable
of doing this.
Has anyone successfully configured oVirt to provide this capability,
or know of a system that could integrate with oVirt to meet that
In some setups, like when you got two datacenters that works like failover sites, you would like to have two external raid controllers(storage devices), one in each datacenter.
You then send two identical LUN's, from each controller, to a cluster, let's say two hosts, for simplicity. What you normally do is to host raid these LUN's in mirror(raid 1), so the hosts write the same to both LUN's, and both controllers.
Question for me here is if I can accomplish this in oVirt management? Because if I can't, it will be a problem, because if I host raid at the host level, then the storage would be local storage for oVirt, wouldn't it? And then I suppose it can't be used for live migration, can it?
I'm running an older version of ovirt-engine on Centos 6.2 and I'd
like to upgrade ovirt-engine and the other corresponding packages
Using yum even if I do a yum update ovirt-engine* the only updates I get are...
and yet I can see there are newer ovirt-engine packages available than
the ones I'm running, I've checked that the repo is enabled...
name=oVirt engine repo
name=oVirt 3.1 engine repo
...and browsing the repo manually through a browser I see the
following packages under ovirt-engine31/
and under the ovirt-engine/ directory I see the following versions...
Anyone have any ideas why yum won't find the newer versions?