As mentioned in the oVirt 3.1 release notes:
"Live snapshotting of virtual machines running on virtualization hosts
with QEMU 1.1 or higher is now supported".
What about Fedora 17? The Fedora version is still at 1.01:
rpm -qi qemu-system-x86
Name : qemu-system-x86
Epoch : 2
Version : 1.0.1
Release : 1.fc17
Install Date: vr 10 aug 2012 11:33:59 CEST
Group : Development/Tools
Size : 13594005
License : GPLv2+ and LGPLv2+ and BSD
Signature : RSA/SHA256, ma 30 jul 2012 20:05:08 CEST, Key ID
Source RPM : qemu-1.0.1-1.fc17.src.rpm
Build Date : ma 30 jul 2012 03:34:33 CEST
Build Host : x86-01.phx2.fedoraproject.org
Relocations : (not relocatable)
Packager : Fedora Project
Vendor : Fedora Project
URL : http://www.qemu.org/
Summary : QEMU system emulator for x86
Thanks to all for the great work getting 3.1 out the door, 3.0 is working
well for us and looking forward to playing with all the new features.
At the moment, am having a small problem during initial engine setup where
it fails if selinux is configured as "disabled" - is this intended
- selinux disabled
- reports nfs domain setup as failed
[root@ovirt-m-2 ~]# engine-setup
Configuring the Default ISO Domain... [ ERROR ]
[root@ovirt-m-2 ~]# engine-cleanup
- After setting CONFIG_NFS=no, in the answer file; it gives an explicit
error about selinux during the HTTPD phase (OVERRIDE_HTTPD_CONFIG=yes)
[root@ovirt-m-2 ~]# engine-setup
-- snip ----
Handling HTTPD... [ ERROR ]
Failed to enable SELinux boolean
-- snip -----
- set selinux to permissive and reboot
- install succeeds (OVERRIDE_HTTPD_CONFIG=yes, CONFIG_NFS=yes)
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
Sorry to re-post this, just not sure what to try next.
----- Original Message -----
> On Tue, Jul 31, 2012 at 1:04 PM, Itamar Heim <ih...(a)redhat.com>
> > you need to run the upgrade script since the setup locks the rpm's
> > to make
> > sure the code isn't updated without updating the db in sync
After running... "engine-upgrade --force-current-setup-rpm --no-yum-rollback"
The upgrade goes through and completes, however at the end if I check
my rpm versions they are all still the same as what they were, as
Seems like the script isn't picking up the later versions available in
the dre repo, I have also updated to the latest dre repo as well just
On a side note, during the upgrade script it says at the end,
"starting jboss-as..." and the script never completes. Only if I then
re-log in with another SSH session and restart the jboss-as service
does the upgrade script continue and complete, not sure if this is
perhaps a bug that's already been fixed in later versions? Not
Thanks, any assistance is greatly appreciated.
This is a multi-part message in MIME format.
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
My name is Garrett LeSage and I'm a designer in the Open Source and
Standards team (OSAS), working with Carl Trieloff, Dave Neary, Jason
Brooks, Karsten Wade, Leslie Hawthorn, and a few other folks who
frequent these lists. I have already met some of you at conferences (Red
Hat Summit & GUADEC), and wanted to introduce myself to everyone here.
From what I've seen so far, oVirt is a fantastic piece of
virtualization technology and I'd like to help the project from a design
A bit of background about myself: I've been a Linux user since 1995 and
I've contributed graphic design resources to Fedora, the Tango icon
project, and Better Desktop. For the past few years, I was working at
SUSE on cloud and virtualization products (such as SUSE Studio), and am
happy to have recently re-joined Red Hat. (:
For oVirt, I have started working on a new site structure (based on Dave
Neary's work) and also have a few drafts for a new website look as well.
In the next few days, I'll be sending some of my already in-progress
drafts to the lists for feedback. I look forward to all constructive
responses --- positive, negative, and indifferent.
Thanks, and I'm looking forward to working with you all more!
Content-Type: text/html; charset=ISO-8859-1
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
<body bgcolor="#FFFFFF" text="#000000">
<div id="readme" class="blob instapaper_body">
<article class="markdown-body entry-content"
<p>My name is Garrett LeSage and I'm a designer in the Open
Source and Standards team (OSAS), working with Carl Trieloff,
Dave Neary, Jason Brooks, Karsten Wade, Leslie Hawthorn, and a
few other folks who frequent these lists. I have already met
some of you at conferences (Red Hat Summit & GUADEC), and
wanted to introduce myself to everyone here.</p>
<p>From what I've seen so far, oVirt is a fantastic piece of
virtualization technology and I'd like to help the project
from a design perspective.</p>
<p>A bit of background about myself: I've been a Linux user
since 1995 and I've contributed graphic design resources to
Fedora, the Tango icon project, and Better Desktop. For the
past few years, I was working at SUSE on cloud and
virtualization products (such as SUSE Studio), and am happy to
have recently re-joined Red Hat. (:</p>
<p>For oVirt, I have started working on a new site structure
(based on Dave Neary's work) and also have a few drafts for a
new website look as well.</p>
<p>In the next few days, I'll be sending some of my already
in-progress drafts to the lists for feedback. I look forward
to all constructive responses — positive, negative, and
<p>Thanks, and I'm looking forward to working with you all more!</p>
I tried to export a VM image, and it apparently succeeded:
2012-Aug-06, 17:00:25 Vm varanus was exported successfully to glusternfs-export
But now the VM "Virtual Disk" is labeled as "locked" and I can't start or even remove and re-import the VM. Any clues how this can be resolved?
Meeting Time and Place
oVirt Weekly Sync
* Wednesdays @ 15:00 UTC (may change during DST changes) - always
at 7:00am US Pacific, 10:00am US Eastern.
* To see in your timezone date -d 'WEDNESDAY 1000 EDT'
* On IRC: #ovirt on irc.oftc.net
This is the agenda for the 2012-08-15 meeting:
* Status of Release
* Sub-project reports (engine, vdsm, node, infra)
* Upcoming workshops
If you have other topics, please reply to me and I will add them to the
agenda. If you propose a topic, please be prepared to lead the
discussion during the meeting.
I'd like to share a few things regarding installation(and use) of oVirt node on thin provisioned LUN's. I had problems here, perhaps someone else have noticed similarities?
I use ZFS and comstar on solaris to provide volume's and LUN`S to the fibre channel SAN. When I create a thin provisioned LUN in comstar it uses the format qcow2, to be able to "fool" the OS that installs on it about the real size of the LUN.
This seem to work fine with normal OS installation, but I'm doubtful about oVist node. I had issues, especially when I try to reinstall on the same LUN. During reinstallation it seems that the installation process tries to "clean" the LUN with dd if=/dev/zero , and that seem to be difficult.
I've run the same cleaning process on different LUN's provided with the same qcow2 format with live media, to see what happens.
First time it seems to go fine, but after one cleaning and another partitioning with LVM the dd seems to get stuck. My feeling is that the LVM partitioning seems to get stuck on the LUN and difficult to get rid of...? Perhaps due to the qcow2 format...?
Could this have something to do with "nested qcow"? qcow on qcow...?"
So, when I get to this stage, the LUN becomes unusable for oVirt node installation. I don't know yet about installing other software, like a normal linux os...
The only oVist node's I've been able to try this on is Fc16-based, since the Fc17 have problems with the qlogic HBA's that I use in my SAN. Fc 17 doesn't load the qlogic firmware image, which makes it impossible to install on the LUN's visible through the qlogic HBA's.
So, anyone that can comments, views, other perspectives, etc, on these subjects are wellcome to do so...
What is the proper process for this in ovirt? Or has someone done it
Greater Boston Vineyard
Director of Operations
With ovirt 3.1 EL 6.3 nodes will only work with a data center set to 3.0
compatibility mode. Is there any reason(s) why EL 6.3+ nodes would not be
allowed in a 3.1 compatibility level cluster? This assumes non use of
gluster since adding vdsm-gluster to an EL 6 node requires some work
package update/version wise (not impossible).
Hi, I installed oVirt 3.1 under CentOS 6.3 (from dre repos) and when I want
to start a VM the following error is displayed:
VM TestVM is down. Exit message: internal error Process exited while
reading console log output: Supported machines are: pc RHEL 6.3.0 PC (alias
of rhel6.3.0) rhel6.3.0 RHEL 6.3.0 PC (default) rhel6.2.0 RHEL 6.2.0 PC
rhel6.1.0 RHEL 6.1.0 PC rhel6.0.0 RHEL 6.0.0 PC rhel5.5.0 RHEL 5.5.0 PC
rhel5.4.4 RHEL 5.4.4 PC rhel5.4.0 RHEL 5.4.0 PC .
What could it be ?