A great week at linuxcon/cloudopen/kvmforum/ovirt conference at
Edinburgh, and some other nice feedback on oVirt, meriting a special
edition of this update.
Feel free to chime in with your feedback as well.
It is sometimes hard to remember we only released oVirt 3.0 last year,
and that it takes time to get traction.
For example, see slide 3 in the presentation i gave on oVirt Updates
to see the clear trend in adoption (via total users mailing list addresses).
Similarly, in Livnat's oVirt-intro session at CloudOpen, with ~75 people
in the room, almost all raised their hand on her question "who knows/has
We had a plethora of topics (same link as ), but i wanted to highlight:
During Livnat's talk, a question was raised wrt SUSE support.
Asking for more details, we got ~"I'm running oVirt in testing and RHEV
in production. with 200 SUSE 10/11 servers. I just want the guest-agent
to have their ip address in the gui".
So first of all, good to know SUSE runs as a guest without issues.
Also, the guest-agent itself is just a python script that should just
work. Just some packaging is required, so we're looking to revamp this
in build.opensuse.org, and hope some SUSE users will help us with
closing and testing this one.
In related SUSE news, I just saw this posted "After looking into oVirt
it looks absolutely fantastic. Might look into seeing if I can help with
porting this to openSUSE. What kind of work is involved in the porting
of the application like this?"
Leonardo from the Eldorado research center in Brazil gave a lecture on
their work to add PPC support to oVirt. Paul Mackerras (KVM PPC
developer) from IBM and Alexenader Graf attended and gave a lot of
feedback, and potential interest from other PPC vendors, which should be
hopefully mostly config level changes.
Keele university presented their path to oVirt. Always nice to hear how
our project is used, and we actually asked them a lot of questions on
why/how they use it the way they do. They also did a case study with
Dave Neary, which i hope to see more from oVirt community members.
Also, always nice to hear: in an irc chat on #ovirt: "I looked at ovirt
about 4 months ago and when I came back a few days ago I was blown away
at how far it had come! The devs have done an awesome job".
All KVM Forum/oVirt sessions slides (and youtube's) should be available
 oVirt Updates session by Itamar Heim
The oVirt team is pleased to announce that the 3.3.1 Release is now
available in beta.
Release notes for this update are still being worked on, but information
on the changes can be found on the wiki.
A new oVirt Node build will be available soon as well.
The oVirt Team is pleased to announce the availability of the 18.104.22.168
Update Release. This release fixes a number of issues with the 3.3.0
The release includes updates to the following packages:
Information on the issues fixed is below.
The oVirt Team
A vdsm bug (BZ#1007980) made it impossible to migrate or re-run a VM
with a glusterfs-backed virtual disk if the VM was originally started
with an empty cdrom.
If you have encountered this bug, you would have to manually find the
affected VMs with
psql -U engine -d engine -c "select distinct vm_name from
vm_static, vm_device where vm_guid=vm_id and device='cdrom' and address
and remove their junk cdrom address with
psql -U engine -d engine -c "update vm_device set address='' where
device='cdrom' and address ilike '%pci%';"
A vdsm bug introduced in a specific case of disk resize (raw on nfs)
accidentally wipes the content of the virtual disk.
The issue was masked on the master (and ovirt-3.3) branch by an unrelated
change that happened to fix the problem leaving only vdsm-4.12 affected.
It is of critical importance to update all your machines to the new vdsm
An engine-setup bug (BZ#1014115) made setup log the database-access password
when upgrading from 3.2. If you've upgraded from an older release you
may want to
secure or delete existing setup log files in /var/log/ovirt-engine/setup/
An engine bug (BZ#1008938) caused VM failing to start running after
changing the interface of bootable disk in UI.
An engine bug (BZ#1017285) may have caused upcoming ovirt-3.3.1 nodes
with vdsm >= 4.13.0 not to be accepted as hypervisors.