Blaster schreef op 2-12-2013 21:15:
> I've been able to find prebuilt virt-io drivers and spice agents for
It seems the Windows guest tools package from
http://www.spice-space.org/download.html is not installable on Windows
Server 2012 though :-(
I noticed rhel 6.5 was released and now most centos mirrors have been
It appears to have a new version of qemu-kvm-0.12.1.2-2.415.el6.x86_64.rpm
Is it now possible to switch from POSIX to native glusterfs? If so, how
would one do that, I assume it requires some sort of database hack.
The oVirt team is pleased to announce that the 3.3.2 Release is now available in beta.
Release notes and information on the changes for this update are still being worked on and will be available soon on the wiki.
A new oVirt Node build will be available soon as well.
You're welcome to join us testing  this beta release.
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
On 11/28/2013 3:54 AM, noc wrote:
> On 27-11-2013 18:18, Ted Miller wrote:
>> I am trying to set up a testing network using o-virt, but the networking
>> is refusing to cooperate. I am testing for possible use in two different
>> production setups.
>> My previous experience has been with VMWare. I have always set up a
>> single bridged network on each host. All my hosts, VMs, and non-VM
>> computers were peers on the LAN. They could all talk to each other, and
>> things worked very well. There was a firewall/gateway that provided
>> access to the Internet, and hosts, VMs, and could all communicate with the
>> Internet as needed.
>> o-virt seems to be compartmentalizing things beyond all reason.
> That is a way to use oVirt, but the following simple setup should work and
> give you a way to check against your setup.
> I have two setups, one at home and one at work. The one at home is a setup
> of 2 hosts and one of those is a hacked up host/engine.
> engine/host1: standard fedora19 kde install, static ip (192.168.1.11)
> configured with my NAS (192.168.1.16) as dhcp/dns server and my internet
> router (192.168.1.254) as gateway
> Just make sure that NetworkManager is off and that your interfaces are not
> NM managed, network on.
> This was a allinone setup but I got a NAS with NFS so I turned my aio setup
> into a engine/host system. It has problems with that but nothing network
> Host2: same as above but without the engine install, ip:192.168.1.22, gw
> 192.168.1.254 DNS:192.168.1.16.
> How does it all come together?
> Well in your case, and mine if I were to start over, start with a static
> network which is NOT managed by NetworkManager. Use either Fedora or Centos
> which ever you more comfortable with and it also depends on whether you
> want to test/use all the features in oVirt. Currently, there are a few
> features not available in Centos because the versions of
> libvirt/kvm/qemu/gluster are too old in Centos.
> Install ovirt-engine on your first 'server', probably choose NFS as your
> storage domain, either on your engine server or from somewhere else on your
> network. Make sure its nfs-v3 and not v4!, local default is v4!
> Make sure that ip addresses on you network are resolvable, either through
> /etc/hosts or through DNS! Engine-setup will complain if this doesn't work,
> using localhost will not work either!
> On the engine server there will be no bridge and nothing will change the
> network config.
> Next the first host.
> Prepare the host in a similar way you did the engine server. You can choose
> a minimal install of either Centos or Fedora or install a full desktop but
> make sure that ips are static and NOT managed by NetworkManager, hostname
> resolvable, ovirt repo available.
> From the webui add your prepared host and if everything went OK you'll see
> that on that host you will now have a bridge, ovirtmgmt, which acts as the
> primary interface.
> Create a VMs and choose ovirtmgmt as a network for its nics, can't choose
> anything else. Either give the VMs a static address or use a dhcp server
> but the VMs should be able to talk to each other, to the host(s), the
> engine and to the internet.
> Every host that you add after the first will also has its network turned
> into a bridge, ovirtmgmt, and communication/migration/display/etc will take
> place over this network. One caveat, storage domain mapping is from the
> host to the storage, the engine, if it is NOT the NFS server, doesn't have
> to have access to the storage.
> If you have servers with more that 1 nic then you can create additional
> networks using the webui of oVirt and assign these to clusters and to VMs.
> If you need vlans to coexist with ovirtmgmt on the same physical nic, I
> think that is possible but haven't tried it myself. In theory you need to
> setup the network first outside of oVirt, including you vlan structure and
> then install ovirt.
> Some concepts:
> oVirt engine: is just the manager, does 'nothing' related to running VMs
> itself. You can turn it off and all hosts with their VMs will keep running.
> You just can't start new ones, in short manage them.
> oVirt host: is the real workhorse and is managed using oVirt-engine. Runs
> VDSM which communicates with engine and starts/manages the VMs on the host
> on behalf of engine.
> oVirt node: is a special slimmed down Fedora distro that includes VDSM and
> a small setup so that it can be used as a oVirt host
> People tend to mix and match ovirt-host and ovirt-node which makes for nice
> communication problems :-)
> If you haven't done so, there is an irc channel, ovirt, on irc.oftc.net
> with helpful people, if they are awake.
> #irc jvandewege
When I get another project out of the way (hopefully this week), I will be
able to get back to my test setup and try again. Between your info,
something I stumbled onto on a blog, and the info from Mike, I hope to have
enough to make some progress when I take another stab at it.
I've lost the beggining of the thread so excuse me if I'm wrong about
Do you want to get all the vms and host in the same subnet as the rest
of your lan or the hole collision domain?
When you create the logical networks (LN) in ovirt you can check if they
are required or not. If you decide that all your hosts must give access
to some subnet for vm use, you can create a LN, mark it as required in
your data center (DC) and configure it in every host you have in the dc.
Then you have two choices, if you just want the vms to access that
subnet, add it to the host without configuring the ip on the host and
you'll just get a bridge for vm use. If you want the host to use the
bridge also, configure the ip and you'll get both, vms and host to be in
If what you need is to get every vm access to the hole collision domain,
then I don't think you can do it in ovirt as you get a bridge for every
logical network and if you have both, tagged and untagged vlan traffic,
you won't be able use the same nic (or bond) to place mixed LNs (a
limitation I've rised but yet haven't been resolved).
Hope this helps.
Blaster schreef op 30-11-2013 21:40:
> Contrary to my other post, which was more educational than practical,
> yes, you generally would not back up app data via a hypervisor
> snapshot. Generally you would only backup the OS disk and perhaps the
> application binaries. This would be for quick restore of the OS and
> app, so you don't have to spend hours reconfiguring your OS.
> (especially Windows based OSes....)
> I also do an IN OS backup as well, for individual file restores in the
> instances you accidentally destroy something in /etc for example.
If your backups are 1) recent and 2) consistent (to a level that suits
you), what does it matter how you make them?
<ovirtbot> Minutes: http://ovirt.org/meetings/ovirt/2013/ovirt.2013-12-02-15.02.html
<ovirtbot> Minutes (text): http://ovirt.org/meetings/ovirt/2013/ovirt.2013-12-02-15.02.txt
<ovirtbot> Log: http://ovirt.org/meetings/ovirt/2013/ovirt.2013-12-02-15.02.log.html
Meeting started by gchaplik_ at 15:02:00 UTC. The full logs are
* oVirt 3.4 SLA & Scheduling features (gchaplik_, 15:02:08)
* brief description of oVirt 3.4 SLA & Scheduling features
* agenda (gchaplik_, 15:03:23)
* time based policy (SLA during the day, power saving at night) (Kobi)
* application level HA (monitor the service inside the VM) (Jiri)
* power saving policy moving hosts to sleep (Martin) (gchaplik_,
* positive/negative affinity between group of VMs (Gilad) (gchaplik_,
* others (Doron) (gchaplik_, 15:04:33)
* time based policy (SLA during the day, power saving at night)
* application level HA (monitor the service inside the VM) (gchaplik_,
* power saving policy moving hosts to sleep (gchaplik_, 15:35:27)
* LINK: http://www.ovirt.org/Features/HostPowerManagementPolicy
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1035238 (msivak,
* AGREED: assume all hosts in same L2 (gchaplik_, 15:46:46)
* AGREED: used existing fence devices (gchaplik_, 15:47:21)
* positive/negative affinity between group of VMs (gchaplik_, 15:47:45)
* additional RFEs (gchaplik_, 15:59:37)
* AGREED: Even Distribution Policy by number of VMs policy name should
clarify the distinction from standard even distribution (gchaplik_,
Meeting ended at 16:39:00 UTC.
Action Items, by person
People Present (lines said)
* doron (131)
* msivak (75)
* gchaplik_ (58)
* itamar (40)
* kobi (32)
* jmoskovc (19)
* sherold (14)
* srevivo (10)
* ecohen (7)
* alitke (3)
* ovirtbot (2)
* mrao (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
I thought of adding a new public Glance image repository on oVirt.org, to be used in different oVirt environments.
The nice thing about glance compared to current export domain is that it can be attached to multiple oVirt environments / data centers, so it can be a public
image repository everyone can use.
Would you see such a repository as useful?
Would you use it?
What type of images/virtual appliances would you find beneficial to have there?
If you're interested let me know. If we see enough traction for it then I'll set it up.
On 11/27/2013 4:35 PM, Thomas Suckow wrote:
> On 11/27/2013 01:00 PM, Ted Miller wrote:
>> I am not using an all-in-one.
>> Do you have more than one host? If not, that is a very different story,
>> because it only has to "talk to itself". I have the engine on a VM (at the
>> moment on a KVM host not managed by ovirt). I was trying to bring up one
>> host, but couldn't get past that point. Will then have to add another host,
>> and migrate the engine to running on one of those two hosts.
>> Ted Miller
> I don't currently, I had dabbled with adding another host but found out the
> other server had a different processor and removed it. That said, my vms
> can talk to eachother and the host can talk to vms and vice versa.
That still doesn't offer what I need: VMs and host all talking on LAN to all
other LAN residents.
> It works better than when I just used virt-manager.
> After setting up the bridge on the host does it lose all network connectivity?
No, it could still talk to ovirt-engine. It seemed to work the way o-virt
wanted it to, just not the way I need it to.
> If so it may be the same issue I was having where I had to manually
> manipulate the network configuration to fix the bridge.
Thanks for the answer,