Up and Running with oVirt, 3.1 Edition

Update: I’ve written an updated version of this guide for oVirt 3.2.

Last February or so, I wrote a post about getting up and running with oVirt, the open source virtualization management project, on a single test machine. Various things have changed since then, such as a shiny new oVirt 3.1 release, so I’m going to update the process in this post.

What you need:

A test machine, ideally an x86_64 system with multiple cores, hardware virtualization extensions and plenty of RAM (like 4GB or more). The default OS for oVirt 3.1 is Fedora 17, and that’s what I’ll be writing about here. Your test machine must have a host name that resolves properly on your network, whether you’re setting that up in a local dns server, or in the /etc/hosts file of any machine you expect to access your test machine from.

UPDATE: For my Fedora oVirt installs, I’ve been using a minimal install of Fedora, which is an option if you start from the DVD or network install images. I interact with my minimal installs via ssh. If you’re using a minimal install with ssh, my instructions work just fine. However, if you start from the default Fedora LiveCD media, you’ll need to take a couple of extra steps. You must disable NetworkManager: (sudo systemctl stop NetworkManager.service && sudo systemctl disable NetworkManager.service), you must enable sshd: (sudo systemctl start sshd && sudo systemctl enable sshd), and then reboot for good measure before proceeding with the rest of the steps.

 (BUG NOTE: With the latest Fedora 17 kernel, I’m hitting https://bugzilla.redhat.com/show_bug.cgi?id=845660, preventing nfs domains from attaching, so for now, you’ll want to run a previous fedora kernel. (BUG NOTE NOTE: This bug, at long last, is just about squashed. Stay tuned.))

 

The package vdsm-4.10.0-10 squashed the above bug dead. Make sure you’re up to date w/ it to avoid issues w/ post 3.5 Fedora kernels.

(A NEW BUG NOTE: There’s a new, 3.2 version of ovirt-engine-sdk in the Fedora 17 update repo. The oVirt 3.1 packages that depend on the sdk don’t call specifically for version 3.1, but they appear not to work with 3.2. For now, you must downgrade to the 3.1 version of the sdk in order for the all-in-one installer and other features to work properly: “yum downgrade ovirt-engine-sdk” I’ve filed a bug, here: https://bugzilla.redhat.com/show_bug.cgi?id=869457 — you can cc yourself on the bug for progress updates.)

 

All-in-One Install:

oVirt 3.1 now includes an installer plugin for setting up the sort of single machine installation I wrote about previously. It’s good for testing out oVirt, and if you want to expand from your single machine install to cover additional nodes and storage, you can do that. Read on for the steps involved, and/or watch this handy screencast I made of the process:

[youtube:http://www.youtube.com/watch?v=Aq3ctFhBIhk%5D

1. Install the ovirt-release package on your Fedora 17 machine: “yum install http://www.ovirt.org/releases/ovirt-release-fedora.noarch.rpm”

2. Install the ovirt-engine all-in-one package: “yum install ovirt-engine-setup-plugin-allinone”

2a. As pointed out by oVirt community member Adrián, in the comments below, you can ensure that the install script allows enough time for the host to add itself by editing “/usr/share/ovirt-engine/scripts/plugins/all_in_one_100.py” to make the “waitForHostUp timeout larger, like so:

def waitForHostUp():
utils.retry(isHostUp, tries=40, timeout=300, sleep=5)

3. Run engine-setup: “engine-setup” and answer all the questions.

I’ve found that the all-in-one installer sometimes times out during the install process. If the script times out during the final “AIO: Adding Local host (This may take several minutes)” step, you can proceed to the web admin console to complete the process. If it times out at an earlier point, like waiting for the jboss-as server to start, you should run “engine-cleanup” and then re-run “engine-setup”.

4. When the engine-setup script completes, visit the web admin console at the URL for your engine machine. It will be running at port 80 (unless you’ve chosen a different setting in the setup script). Choose “Administrator Portal” and log in with the credentials you entered in the engine-setup script.

From the admin portal, take a look at the “Storage” and “Hosts” tabs. If the all-in-one process completed, you should see a host named “local_host” with a status of “Up” under Hosts, and you should see a storage domain named “local_host-Local” under “Storage.”

If your local_host is still installing, you’ll need to wait for it to finish before proceeding. You should be able to view its progress from the events panel at the bottom of the console interface. Once the host is finished installing, click on your “local_host” and hit the “Maintenance” link to put it into maintenance mode. Once your host is in maintenance mode, you’ll be able to click on the “Configure Local Storage” link, where you enter the same local storage path you entered into the engine-setup script, and then hit “OK.”

5. Once the configure local storage process is complete (whether this was taken care of during engine-setup, or if you had to do it manually in step 4) click on the storage tab and highlight the iso domain you created during the setup-script. In the pane that appears below, choose the “Data Center” tab, click “Attach,” check the box next to your local data center, and hit “OK.” Once the iso domain is finished attaching, click “Activate” to, uh, activate it.

6. Now you have an oVirt management server that’s configured to double as a virtualization host. You have a local data domain (for storing your VM’s virtual disk images) and an NFS iso domain (for storing iso images from which to install OSes on your VMs).

To get iso images into your iso domain, you can copy an image onto your ovirt-engine machine, and from the command line, run, “engine-iso-uploader upload -i iso NAME_OF_YOUR_ISO.iso” to load the image. Otherwise (and this is how I do it), you can mount the iso NFS share from wherever you like. Your images don’t go in the root of the NFS share, but in a nested set of folders that oVirt creates automatically that looks like: “/nfsmountpoint/BIG_OLE_UUID/images/11111111-1111-1111-1111-111111111111/NAME_OF_YOUR_ISO.iso. You can just drop them in there, and after a few seconds, they should register in your iso domain.

Once you’re up and running, you can begin installing VMs. For your viewing pleasure, here’s another screencast, about creating VMs on oVirt:

[youtube:http://www.youtube.com/watch?v=C4gayV6dYK4%5D

Beyond All in One (or skipping it all together):

Installing: A “regular” multi-machine install of oVirt works in pretty much the same way, except that in step two, you simply install “yum install ovirt-engine” and during the “engine-setup” process, you won’t be asked about installing VDSM or a local data domain on your engine. I typically skip creating an iso domain on my engine, as I use a separate NAS device for my iso domain needs.

The local data center, cluster and storage domain created as part of the all-in-one installation option are only accessible to the virtualization host installed locally on the engine. Shifting to a multi-machine setup involves moving that local host to the Default datacenter and cluster, which starts with putting the host into maintenance mode, clicking edit, and switching the Data Center and Cluster values to “Default” (or to another, non-local set of data center and cluster values).

Hosts: Once the setup script is finished, you can head over to the web admin console to add hosts and storage domains. oVirt hosts can be either regular Fedora 17 boxes or machines installed with oVirt Node. In either case, you add one of these machines as an oVirt host by clicking “New” under the “Hosts” tab in the web admin console, and providing a name, IP address (or host name) and root password for your host-to-be, and clicking OK. A dialog will complain about configuring power management, but it’s not strictly required.

When adding an oVirt Node-based system as a host, you can also provide the ovirt-engine address and admin password in the admin interface of the node, which will add the node to your ovirt-engine server, pending approval through the web admin console.

Storage: A multi-machine setup requires a shared storage domain, such as one backed by NFS or iSCSI. Setting up an NFS storage domain involves clicking “New Domain” on the “Storage” tab, giving the new data domain a name and configuring its export path. Setting up an iSCSI domain is similar, but involves entering the IP address of your iSCSI target, discovering available LUNs, and selecting one to use.

When Things Go Wrong:

A few things to do/check when things go wrong.

1. Put selinux into permissive mode: “setenforce 0” I run my systems with selinux enabled, but there are sometimes selinux-related bugs. Putting your test system into permissive mode will get you past the errors.

2. Check the logs:

  • ovirt-engine install log lives at /var/log/ovirt-engine/engine-setup*.log
  • jboss app server logs live at /var/log/ovirt-engine/boot.log and /var/log/ovirt-engine/server.log
  • ovirt-engine logs live at /var/log/ovirt-engine/engine.log — you can tail -f /var/log/ovirt-engine/engine.log to watch what the engine is doing
  • vdsm logs live (on each virt host) at /var/log/vdsm/vdsm.log — you can watch these to see what’s going on with individual virt hosts

3. Visit us at #ovirt on OFTC. My handle there is jbrooks. If you don’t get an answer there, send a message to users@ovirt.org.

Faking It:

I mentioned right at the top that if you want to test oVirt virtualization, you need a machine with hardware virtualization extensions. The oVirt management engine can live happily within a VM, but for hosting VMs, you need those extensions.

While most physical machines these days come with those extensions, virtual machines don’t have them. There’s such a thing as nested KVM virtualization, but it’s tricky to set up and pretty unstable when you can set it up.

There is a way to test out oVirt without hardware virtualization extensions, but the catch is that you can’t actually run any VMs on one of these “fake” installs. Why bother? Well, there’s a lot to test and see in oVirt that falls short of running VMs–I made my whole installing oVirt hotwo video on a VM running inside of my real oVirt rig, for instance. You can get a feel for installing hosts and configuring storage, and managing Gluster volumes (a topic I haven’t covered here, but will, soon, in another post, till then see here for more info on oVirt/Gluster). For more on oVirt w/ Gluster, see here.

For the all-in-one setup instructions above, right after step 2:

  • install the “fake qemu” package (yum install vdsm-hook-faqemu)
  • edit /etc/vdsm/vdsm.conf, changing line # fake_kvm_support = false to fake_kvm_support = true
  • replace the contents of the of /usr/share/vdsm-bootstrap/vds_bootstrap.py (it’ll be there post step 2) with the file at http://gerrit.ovirt.org/cat/5611%2C3%2Cvds_bootstrap/vds_bootstrap.py%5E0
  • continue to step 3

That vds_bootstrap.py step shouldn’t be required, and I’m going to file a bug about it as soon as I finish this post. For more information on this topic, see: http://wiki.ovirt.org/wiki/Vdsm_Developers#Fake_KVM_Support.

If you’re trying to configure a separate fake host, for now, you’ll need to do it on a regular vdsm (not oVirt Node) host, though this should soon change. But, for your regular host, before trying to add the host through the oVirt web admin console:

  • run “yum install vdsm-hook-faqemu vdsm”
  • edit /etc/vdsm/vdsm.conf, changing line # fake_kvm_support = false to fake_kvm_support = true

Either way, you’ll need that modded /usr/share/vdsm-bootstrap/vds_bootstrap.py file on your engine, and you only have to change this file once, until/unless a future package update restores the faqemu-ignorant file.

85 thoughts on “Up and Running with oVirt, 3.1 Edition”

  1. Thanks for the write-up! Does bug 845660 apply to the latest Node version (2.5.1-1.0.fc17?) It has the 3.5.0 kernel and so far I’m unable to get an NFS storage domain to attach… mounts and creates a UUID-named directory and some files inside, then fails. NFS servers tried are CentOS 6.3 and OpenSolaris 10. I’m thinking of using a CentOS 6.3 minimal install and VDSM packages instead.

      1. Thanks Jason – FWIW I reinstalled the node using CentOS 6.3 and was able to create data and ISO storage domains with no problem.

  2. Same person who posted earlier: wish I could say it went better, but 3.1 needs some fixin’. I switched to a stock F17 ovirt-engine and node ISO. First – at least with node 2.5.0-2.0 ISO (newest that works with NFS storage domains and 3.1), spice console is broken:

    https://bugzilla.redhat.com/show_bug.cgi?id=790436

    Not a show stopper – VNC is okay for now.

    But: a new VM, once stopped, can’t be restarted. (using Solaris 10 NFS storage domains). I don’t think it’s the NFS server’s fault though, because it worked fine to install the OS in the VM. The message is a cryptic ‘truesize” error. I don’t have the logs any more but did look, saw some apparent permissions issues, and think it’s probably the same as the person hit in the below thread – not sure anyone’s filed an issue for it yet:

    http://www.mail-archive.com/users@ovirt.org/msg02755.html

    I hit a few more too, like export of a VM failed and unable to template a VM, both possibly caused by the above. Also filed one bug/RFE, to request support of mixed native/tagged VLANs on a host interface.

    Lots of potential, very nice FOSS virtualization framework, and I’m looking forward to experimenting more when at least the VMs can be restarted. :-)

  3. Good day! Need help… when attaching ISO domain, I get error
    error = Storage domain does not exist: (‘c4be68f1-dfeb-4a0e-8b5f-23af0df89e0c’,)

      1. someone know why after install a node in the same host that have ovirt-engine then i can not access to the web admin portal, just only appear Portals on the web and in both installation I did not have any error

  4. Hi,

    Thanks for your write-up

    On running engine-setup, I was stuck here

    Host fully qualified domain name, note that this name should be fully resolvable [fedora17] :
    Having tried:- demo.fedora17 / demo.localdomain / demo.localhost

    all failed.
    User input failed validation, do you still wish to use it? (yes|no): no

    $ cat /etc/hosts
    127.0.0.1 localhost.localdomain localhost
    ::1 localhost6.localdomain6 localhost6

    fedora17 was the host name entered during installing Fedora17

    I’m running ISP dns server

    $ cat /etc/resolv.conf
    nameserver 192.168.0.1

    Please help. TIA

    1. “demo.localdomain” was the hostname and domain for my test machine, you should use whatever name you have for your machine. On a default F17 system, it’s going to be localhost.localdomain. You can change it by editing /etc/sysconfig/network and rebooting.

      If your name isn’t going to resolve properly from a dns server, you can edit /etc/hosts to make it resolve, but if you do this, the FQDN check in the engine-setup script will fail, and you have to tell it to go ahead anyway.

      It’ll still work fine, you just have to make the same /etc/hosts configuration in every machine that’ll be accessing the engine. For instance, a separate client from which you intend to access the web admin.

  5. Still no breakthrough:

    Performed following steps.
    – made change on /etc/sysconfig/network

    $ cat /etc/sysconfig/network
    NETWORKING=yes
    HOSTNAME=localhost.localdomain
    NTPSERVERARGS=iburst

    and rebooted PC

    Host fully qualified domain name, note that this name should be fully resolvable [localhost.localdomain] :
    localhost.localdomain did not resolve into an IP address
    User input failed validation, do you still wish to use it? (yes|no):

    The dns server can’t resolve “localhost.localdomain”

    # cat /etc/hosts
    127.0.0.1 localhost.localdomain localhost
    ::1 localhost6.localdomain6 localhost6

    “127.0.0.1 localhost.localdomain localhost” is already there.

    $ sudo ifconfig
    [sudo] password for satimis:
    bond0: flags=5123 mtu 1500
    ether 00:00:00:00:00:00 txqueuelen 0 (Ethernet)
    RX packets 0 bytes 0 (0.0 B)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 0 bytes 0 (0.0 B)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    bond1: flags=5123 mtu 1500
    ether 00:00:00:00:00:00 txqueuelen 0 (Ethernet)
    RX packets 0 bytes 0 (0.0 B)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 0 bytes 0 (0.0 B)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    bond2: flags=5123 mtu 1500
    ether 00:00:00:00:00:00 txqueuelen 0 (Ethernet)
    RX packets 0 bytes 0 (0.0 B)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 0 bytes 0 (0.0 B)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    bond3: flags=5123 mtu 1500
    ether 00:00:00:00:00:00 txqueuelen 0 (Ethernet)
    RX packets 0 bytes 0 (0.0 B)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 0 bytes 0 (0.0 B)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    bond4: flags=5123 mtu 1500
    ether 00:00:00:00:00:00 txqueuelen 0 (Ethernet)
    RX packets 0 bytes 0 (0.0 B)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 0 bytes 0 (0.0 B)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    lo: flags=73 mtu 16436
    inet 127.0.0.1 netmask 255.0.0.0
    inet6 ::1 prefixlen 128 scopeid 0x10
    loop txqueuelen 0 (Local Loopback)
    RX packets 84 bytes 8554 (8.3 KiB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 84 bytes 8554 (8.3 KiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    p6p1: flags=4163 mtu 1500
    inet 192.168.0.10 netmask 255.255.255.0 broadcast 192.168.0.255
    inet6 fe80::226:18ff:fe44:b61a prefixlen 64 scopeid 0x20
    ether 00:26:18:44:b6:1a txqueuelen 1000 (Ethernet)
    RX packets 8635 bytes 11659356 (11.1 MiB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 6438 bytes 678157 (662.2 KiB)
    TX errors 0 dropped 0 overruns 0 carrier 1 collisions 0

    The PC is behind a router. Do I need forward ports 80 and 443 to 192.168.0.10 on the router?

    Or is there any other suggestion? Thanks

    1. When the script asks you if you want to continue even though the name doesn’t resolve, you should say, yes, you still wish to use it — the input validation won’t succeed with the /etc/hosts method, but it’ll still work.

      1. Continued

        Everything going on similar to your video.

        Except follows:

        1)

        Handling HTTPD… [ DONE ]
        AIO: Creating storage directory… [ DONE ]
        AIO: Adding Local Datacenter and cluster… [ DONE ]
        AIO: Adding Local host (This may take several minutes)… [ ERROR ]
        Error: Could not install local host
        Please check log file /var/log/ovirt-engine/engine-setup_2012_09_01_11_24_36.log for more information

        # tail /var/log/ovirt-engine/engine-setup_2012_09_01_11_24_36.log
        File “/usr/share/ovirt-engine/scripts/setup_controller.py”, line 54, in runAllSequences
        sequence.run()
        File “/usr/share/ovirt-engine/scripts/setup_sequences.py”, line 154, in run
        step.run()
        File “/usr/share/ovirt-engine/scripts/setup_sequences.py”, line 60, in run
        function()
        File “/usr/share/ovirt-engine/scripts/plugins/all_in_one_100.py”, line 244, in createHost
        raise Exception(ERROR_CREATE_LOCAL_HOST)
        Exception: Error: Could not install local host

        2)
        On browser
        localhost.localdomain

        started “oVirt Open Virtualization Manager”

        But clicking “Hosts” tag nothing was displayed.

        Please advise how to fix it. TIA

        Regards

      2. You can continue from here by clicking “New” on the the “Hosts” tab and entering your host’s ip address and root pw. See if that completes…

      3. I’m having similar problem. I have tried the IP address, localhost, 120.0.0.1 and localhost.localdomain without any success.

      4. From the “Hosts” tab, you’re clicking “New” providing the address and root pw of your machine, hitting “OK” and nothing’s happening? Is there any error message?

      5. I got the following error “Error: Cannot add Host. Failed creating an SSH session with the host.
        Verify that the host is reachable (IP address, routable address etc.)
        and authentication parameters are correct (Username/Password, public-key
        etc.) You may refer to the engine.log file for further details.”

        Here is my /var/log/ovirt-engine/engine.log:

        2012-09-13 14:51:16,636 ERROR [org.ovirt.engine.core.utils.hostinstall.MinaInstallWrapper] (ajp–0.0.0.0-8009-5) Could not connect to server 172.31.5.110: Failed to get the session.
        2012-09-13 14:51:16,637 WARN [org.ovirt.engine.core.bll.AddVdsCommand] (ajp–0.0.0.0-8009-5) [73f7dd52] CanDoAction of action AddVds failed.Reasons:VDS_CANNOT_CONNECT_TO_SERVER,VAR__ACTION__ADD,VAR__TYPE__HOST
        2012-09-13 14:51:48,283 ERROR [org.ovirt.engine.core.utils.hostinstall.MinaInstallWrapper] (ajp–0.0.0.0-8009-4) Could not connect to server localhost: Failed to get the session.
        2012-09-13 14:51:48,284 WARN [org.ovirt.engine.core.bll.AddVdsCommand] (ajp–0.0.0.0-8009-4) [38d524e6] CanDoAction of action AddVds failed. Reasons:VDS_CANNOT_CONNECT_TO_SERVER,VAR__ACTION__ADD,VAR__TYPE__HOST
        2012-09-13 14:51:58,242 ERROR [org.ovirt.engine.core.utils.hostinstall.MinaInstallWrapper] (ajp–0.0.0.0-8009-3) Could not connect to server localhost.localdomain: Failed to get the session.
        2012-09-13 14:51:58,243 WARN [org.ovirt.engine.core.bll.AddVdsCommand] (ajp–0.0.0.0-8009-3) [3a622482] CanDoAction of action AddVds failed. Reasons:VDS_CANNOT_CONNECT_TO_SERVER,VAR__ACTION__ADD,VAR__TYPE__HOST
        2012-09-13 14:52:09,089 ERROR [org.ovirt.engine.core.utils.hostinstall.MinaInstallWrapper] (ajp–0.0.0.0-8009-7) Could not connect to server 127.0.0.1: Failed to get the session.
        2012-09-13 14:52:09,091 WARN [org.ovirt.engine.core.bll.AddVdsCommand] (ajp–0.0.0.0-8009-7) [7bef53c5] CanDoAction of action AddVds failed. Reasons:VDS_CANNOT_CONNECT_TO_SERVER,VAR__ACTION__ADD,VAR__TYPE__HOST

        As you can see, I tried to use “127.0.0.1”, “localhost”, locahost.localdomain” and “172.31.5.110” (which is my local lan ip)..

        i suspected is a cert problem. So i tried to disable SSL in /etc/vdsm/vdsm.conf with the option “ssl = false”. Still doesn’t help..

        I can confirm that this machine has Intel-VT enable since I’m have used this same host to install Xen Server with Windows VMs.

        Hopefully someone can help. Thanks in advance.

      6. I solved my own problem! ^_^

        My SSH daemon is not started.

        Just run the following command to startup my SSH daemon and i can add my local machine as host!

        sudo /sbin/service sshd start

        Thanks Jason for this great guide!

      7. Still failed.

        New Host
        Name localhost.localdomian
        Address 192.168.0.10 (it can be pinged)
        Root Password xxxxx

        ->
        You haven’t configured Power Management for this Host. Are you sure you want to continue?

        OK

        Oops!
        Error: Cannot add Host. Failed creating an SSH session with the host. Verify that the host is reachable (IP address, routable address etc.) and authentication parameters are correct (Username/Password, public-key etc.) You may refer to the engine.log file for further details.

        $ tail /var/log/ovirt-engine/engine.log
        2012-09-26 11:51:48,438 ERROR [org.ovirt.engine.core.utils.hostinstall.MinaInstallWrapper] (ajp–0.0.0.0-8009-6) Could not connect to server 127.0.0.1: Failed to get the session.
        2012-09-26 11:51:48,439 WARN [org.ovirt.engine.core.bll.AddVdsCommand] (ajp–0.0.0.0-8009-6) [5da2b220] CanDoAction of action AddVds failed. Reasons:VDS_CANNOT_CONNECT_TO_SERVER,VAR__ACTION__ADD,VAR__TYPE__HOST
        2012-09-26 11:52:50,124 ERROR [org.ovirt.engine.core.utils.hostinstall.MinaInstallWrapper] (ajp–0.0.0.0-8009-4) Could not connect to server 192.168.0.10: Failed to get the session.
        2012-09-26 11:52:50,124 WARN [org.ovirt.engine.core.bll.AddVdsCommand] (ajp–0.0.0.0-8009-4) [19a8baea] CanDoAction of action AddVds failed. Reasons:VDS_CANNOT_CONNECT_TO_SERVER,VAR__ACTION__ADD,VAR__TYPE__HOST
        2012-09-26 11:53:20,695 ERROR [org.ovirt.engine.core.utils.hostinstall.MinaInstallWrapper] (ajp–0.0.0.0-8009-1) Could not connect to server 192.168.0.10: Failed to get the session.
        2012-09-26 11:53:20,696 WARN [org.ovirt.engine.core.bll.AddVdsCommand] (ajp–0.0.0.0-8009-1) [2e73e7ed] CanDoAction of action AddVds failed. Reasons:VDS_CANNOT_CONNECT_TO_SERVER,VAR__ACTION__ADD,VAR__TYPE__HOST
        2012-09-26 11:57:43,879 ERROR [org.ovirt.engine.core.utils.hostinstall.MinaInstallWrapper] (ajp–0.0.0.0-8009-9) Could not connect to server 192.168.0.10: Failed to get the session.
        2012-09-26 11:57:43,879 WARN [org.ovirt.engine.core.bll.AddVdsCommand] (ajp–0.0.0.0-8009-9) [78a97e2a] CanDoAction of action AddVds failed. Reasons:VDS_CANNOT_CONNECT_TO_SERVER,VAR__ACTION__ADD,VAR__TYPE__HOST
        2012-09-26 11:58:39,782 ERROR [org.ovirt.engine.core.utils.hostinstall.MinaInstallWrapper] (ajp–0.0.0.0-8009-4) Could not connect to server 192.168.0.10: Failed to get the session.
        2012-09-26 11:58:39,783 WARN [org.ovirt.engine.core.bll.AddVdsCommand] (ajp–0.0.0.0-8009-4) [35a4dc66] CanDoAction of action AddVds failed. Reasons:VDS_CANNOT_CONNECT_TO_SERVER,VAR__ACTION__ADD,VAR__TYPE__HOST

        On referring to the record building oVirt on Fedora 17, it mentioned;
        ….
        Host fully qualified domain name, note that this name should be fully resolvable [localhost.localdomain] :
        localhost.localdomain did not resolve into an IP address
        User input failed validation, do you still wish to use it? (yes|no): yes
        ….

        Also tried 127.0.0.1 (it can be pinged) without result

        $ tail /var/log/ovirt-engine/engine.log
        2012-09-26 11:53:20,695 ERROR [org.ovirt.engine.core.utils.hostinstall.MinaInstallWrapper] (ajp–0.0.0.0-8009-1) Could not connect to server 192.168.0.10: Failed to get the session.
        2012-09-26 11:53:20,696 WARN [org.ovirt.engine.core.bll.AddVdsCommand] (ajp–0.0.0.0-8009-1) [2e73e7ed] CanDoAction of action AddVds failed. Reasons:VDS_CANNOT_CONNECT_TO_SERVER,VAR__ACTION__ADD,VAR__TYPE__HOST
        2012-09-26 11:57:43,879 ERROR [org.ovirt.engine.core.utils.hostinstall.MinaInstallWrapper] (ajp–0.0.0.0-8009-9) Could not connect to server 192.168.0.10: Failed to get the session.
        2012-09-26 11:57:43,879 WARN [org.ovirt.engine.core.bll.AddVdsCommand] (ajp–0.0.0.0-8009-9) [78a97e2a] CanDoAction of action AddVds failed. Reasons:VDS_CANNOT_CONNECT_TO_SERVER,VAR__ACTION__ADD,VAR__TYPE__HOST
        2012-09-26 11:58:39,782 ERROR [org.ovirt.engine.core.utils.hostinstall.MinaInstallWrapper] (ajp–0.0.0.0-8009-4) Could not connect to server 192.168.0.10: Failed to get the session.
        2012-09-26 11:58:39,783 WARN [org.ovirt.engine.core.bll.AddVdsCommand] (ajp–0.0.0.0-8009-4) [35a4dc66] CanDoAction of action AddVds failed. Reasons:VDS_CANNOT_CONNECT_TO_SERVER,VAR__ACTION__ADD,VAR__TYPE__HOST
        2012-09-26 12:15:19,261 ERROR [org.ovirt.engine.core.utils.hostinstall.MinaInstallWrapper] (ajp–0.0.0.0-8009-3) Could not connect to server 127.0.0.1: Failed to get the session.
        2012-09-26 12:15:19,262 WARN [org.ovirt.engine.core.bll.AddVdsCommand] (ajp–0.0.0.0-8009-3) [1010c5b0] CanDoAction of action AddVds failed. Reasons:VDS_CANNOT_CONNECT_TO_SERVER,VAR__ACTION__ADD,VAR__TYPE__HOST
        2012-09-26 12:15:39,370 ERROR [org.ovirt.engine.core.utils.hostinstall.MinaInstallWrapper] (ajp–0.0.0.0-8009-9) Could not connect to server 127.0.0.1: Failed to get the session.
        2012-09-26 12:15:39,370 WARN [org.ovirt.engine.core.bll.AddVdsCommand] (ajp–0.0.0.0-8009-9) [7d52ddf3] CanDoAction of action AddVds failed. Reasons:VDS_CANNOT_CONNECT_TO_SERVER,VAR__ACTION__ADD,VAR__TYPE__HOST

        Any suggestion? Thanks

      8. From the command line on this machine, can you ssh 127.0.0.1 or ssh localhost and log in? You should be able to do that. It looks like this is where the process is failing. I’m not sure what’s causing the hangup, though.

      9. Yes,

        # ssh 127.0.0.1
        root@127.0.0.1’s password:

        Performed following steps;

        # /sbin/service sshd start
        # rm -rf /mnt/iso
        # rm -rf /mnt/data
        # gedit /etc/exports
        deleted old data;
        /mnt/iso
        /mnt/data

        # engine-cleanup
        # engine-setup
        anwser all questions

        On browser run;
        localhost.localdomain

        start “Open Virtualization Manager”

        login

        -> Hosts
        local_host localhost.localdomain …….
        found

        Action Items
        ! Host installation failed. Fix installation issues and try to Re-Install
        ! Power Management is not configured for this Host. Enable Power Management

        But clicking “Re-install”
        Install Host
        Root Password xxx
        Automatically configure host firewall
        [v]
        -> OK

        Fail
        ! Host installation failed. Fix installation issues and try to Re-Install
        coming back

        Any suggestion?

        What shall I fill in
        -> Enable Power Management

        Edit Host:-
        Address
        User Name
        Password
        Type
        Port
        Options
        Secure
        ?

        Thanks

      10. I don’t know what the problem is — I’ve installed this a bunch of times, just like in the video. It seems that your engine can’t connect to itself via ssh, but it can, so ????

        What’s the system you’re starting from? Like, I start from a minimal F17 instance running a pre 3.5 kernel.

      11. It is a full version F17

        $ uname -a
        Linux localhost.localdomain 3.5.4-1.fc17.x86_64 #1 SMP Mon Sep 17 15:03:59 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

        Now it comes to present situation:

        see Screenshot_01 and _02

        -> click “click here”

        see Screenshot_03

        -> click Re-Install

        it pop-up “Install Host” window
        (see Screenshot_04)

        filling in Root Password -> OK

        nothing happened. Re-Install still there

        -> click “Enable Power Management

        pop-up “Edit Host” window
        (Screeshot_05)

        What shall I enter on those boxes?

        -> Maintenance

        pop-up “Maintenance Host” window
        (Screeshot_06)
        click OK

        -> click “Configure Local Storage”
        nothing happened

        -> click “Event”

        see Screenshot_07

      12. OK, one thing is that you need to be running a pre 3.5 kernel, due to a bug that affects ovirt attaching to nfs domains: https://bugzilla.redhat.com/show_bug.cgi?id=845660

        I haven’t gone through this process on a full f17 install, I’ve always used a minimal install. Maybe there’s a conflict in the full install that I’m not seeing. I’m going to run through the process on a full install to see.

      13. Yes, I’m running 3.5.4 kernel

        $ uname -a
        Linux localhost.localdomain 3.5.4-1.fc17.x86_64 #1 SMP Mon Sep 17 15:03:59 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

      14. All right, I’ve set up oVirt 3.1 on an F17 machine installed from the regular live CD media, and I hit the same issues you’ve been seeing, Stephen.

        There are two additional steps required — first, we have to enable the sshd service, which is something we already figured out:

        sudo systemctl start sshd.service
        sudo systemctl enable sshd.service

        The second item is disabling networkmanager:

        sudo systemctl stop NetworkManager.service
        sudo systemctl disable NetworkManager.service
        sudo vi /etc/sysconfig/network-scripts/ifcfg-eth0, and set the NM managed value to no.

        Then clean up your engine setup:

        vi /etc/exports and remove the /mnt/iso line

        Then “sudo rm -rf /mnt/iso” to remove your iso domain mount point (assuming that this is your iso mount point.

        Then “sudo engine-cleanup” and “sudo reboot” to restart.

        After these steps, you should be able to “sudo engine-setup” and answer all the questions. The all in one install might stop at the installing vdsm stage (that timeout needs to be longer) just as it did in my video. You should, though, be able to proceed as I do in the video if that happens.

        So, the key was the NetworkManager bit — that has to be disabled — it holds up the all in one install. Since NetworkManager being enabled is the default for the regular Fedora install media, though, this is definitely a bug — something that needs to be dealt with.

        In my own installs, I’ve been using the DVD or the network install image and only installing a minimal system (no networkmanager). And I always interact with with my minimal system via ssh, so I’ve been automatically enabling that.

        Anyway, I hope you’re still with me (thanks for your patience!) and I hope this works for you!!

      15. $ sudo /sbin/service sshd start
        Redirecting to /bin/systemctl start sshd.service

        $ sudo systemctl start sshd.service
        sudo systemctl stop NetworkManager.service

        $ sudo systemctl enable sshd.service
        ln -s ‘/usr/lib/systemd/system/sshd.service’ ‘/etc/systemd/system/multi-user.target.wants/sshd.service’

        $ sudo systemctl stop NetworkManager.service

        $ sudo systemctl disable NetworkManager.service

        $ ls /etc/sysconfig/network-scripts/
        ifcfg-lo ifdown-isdn ifup-aliases ifup-plip ifup-wireless
        ifcfg-p6p1 ifdown-post ifup-bnep ifup-plusb init.ipv6-global
        ifdown ifdown-ppp ifup-eth ifup-post net.hotplug
        ifdown-bnep ifdown-routes ifup-ippp ifup-ppp network-functions
        ifdown-eth ifdown-sit ifup-ipv6 ifup-routes network-functions-ipv6
        ifdown-ippp ifdown-tunnel ifup-ipx ifup-sit
        ifdown-ipv6 ifup ifup-isdn ifup-tunnel

        ifcfg-eth0 is NOT on Fedora 17

      16. $ sudo gedit /etc/sysconfig/network-scripts/ifcfg-p6p1
        UUID=”7cc380ad-1b3c-462b-b0fd-040ca6a72cf0″
        NM_CONTROLLED=”yes”
        HWADDR=”00:26:18:44:B6:1A”
        BOOTPROTO=”dhcp”
        DEVICE=”p6p1″
        ONBOOT=”yes”

        Change;
        NM_CONTROLLED=”yes” to “no”

        $ sudo gedit /etc/exports
        comment out following line
        #/mnt/iso 0.0.0.0/0.0.0.0(rw) #rhev installer
        (only one line on the file)

        $ sudo rm -rf /mnt/iso
        $ sudo engine-cleanup
        WARNING: Executing oVirt Engine cleanup utility.
        This utility will wipe all existing data including configuration settings, certificates and database.
        In addition, all existing DB connections will be closed.
        Would you like to proceed? (yes|no): yes

        Stopping JBoss service… [ DONE ]
        Removing Database… [ DONE ]
        Removing CA… [ DONE ]
        Removing EAR link… [ DONE ]
        Stopping engine-notifierd service… [ DONE ]

        Cleanup finished successfully!
        Cleanup log available at /var/log/ovirt-engine/engine-cleanup_2012_10_16_23_56_02.log
        DB Backup available at /usr/share/ovirt-engine/db-backups/tmpEtbdRh.sql

        $ sudo reboot

        $ sudo engine-setup
        …..
        In order to proceed the installer must stop the JBoss service
        Would you like to stop the JBoss service? (yes|no): yes

        Do you wish to override current httpd configuration and restart the service? [‘yes’| ‘no’] [yes] : Enter
        HTTP Port [80] : Enter
        HTTPS Port [443] : Enter
        Host fully qualified domain name, note that this name should be fully resolvable [localhost.localdomain] : Enter

        localhost.localdomain did not resolve into an IP address
        User input failed validation, do you still wish to use it? (yes|no): yes
        Password for Administrator (admin@internal) : password

        Organization Name for the Certificate: Enter
        String length is less than the minimum allowed: 1 (what is this line ?)
        Organization Name for the Certificate: satimis
        The default storage type you will be using [‘NFS’| ‘FC’| ‘ISCSI’] [NFS] : Enter
        Enter DB type for installation [‘remote’| ‘local’] [local] : Enter
        Local database password : database
        Local ISO domain path: /mnt
        Error: directory /mnt is not empty

        Stopped here

        On another terminal”-
        # ls /mnt/
        data
        # ls /mnt/data/
        no printout

        # rm -rf /mnt/data/

        Went back to early terminal;
        Local ISO domain path: /mnt
        Error: directory /mnt is not empty

        Still the same. Stuck here

      17. When the script sees that there’s already an iso domain in the place where you tell it to create an iso domain, it stops, lest it overwrite something you don’t intend to overwrite.

        So, you need to either delete the files in /mnt that engine-setup created (it’s going to be a directory with a long name) or provide a different mount point, like /mnt/iso.

      18. Hi jasonbrooks,

        Fedora 17 desktop 64bit full version
        $ uname -a
        Linux localhost.localdomain 3.6.1-1.fc17.x86_64 #1 SMP Wed Oct 10 12:13:05 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

        I have other 2 spare HDs also running Fedora 17, 64bit desktop full version, ready to work with you for testing oVirt. One of them on this PC and another on another PC (not connected at the same time with other HDs)

        Current PC:-
        AMD Core4
        RAM 8GB

        Additional PC:-
        AMD Core 2
        RAM 4GB

        I’m prepared moving the test to the spare HD on this PC first. What will be your opinion?

  6. Im having trouble adding my local storage. I want to put my local storage in /opt/images but it fails and from the logs l see these errors:
    2012-08-20 20:52:33,437 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase] (ajp–0.0.0.0-8009-1) [_WEBADMIN_17901516_Configure_Local_Storage] Failed in CreateStorageDomainVDS method
    2012-08-20 20:52:33,439 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase] (ajp–0.0.0.0-8009-1) [_WEBADMIN_17901516_Configure_Local_Storage] Error code StorageServerAccessPermissionError and error message VDSGenericException: VDSErrorException: Failed to CreateStorageDomainVDS, error = Permission settings on the specified path do not allow access to the storage. Verify permission settings on the specified storage path.: ‘path = /rhev/data-center/mnt/_opt_images’

      1. Hello Jason,

        Could you tel me please what should I do with non-local nfs server to make it work?

        log: 2012-09-02 19:36:52,177 ERROR [org.ovirt.engine.core.vdsbroker.VDSCommandBase] (ajp–0.0.0.0-8009-2) [5489cacd] Command CreateStorageDomainVDS execution failed. Exception: VDSErrorException: VDSGenericException: VDSErrorException: Faild to CreateStorageDomainVDS, error = Error creating a storage domain: (‘storageType=1, sdUUID=2fe86085-bda7-42e9-b50f-2a9d298c0d33, domainName=ISO, domClass=2, typeSpecificArg=storage.ovirt.com:/iso domVersion=0’,)

        rcpbind and nfs server installed and runing

        cat /etc/exports
        /iso 192.168.10.0/24(rw)

        ls -la / | grep iso
        drwxr-xr-x 3 36 36 4096 Sep 2 13:42 iso

        cat /etc/fstab | grep iso
        /dev/md126 /iso ext4 rw 0 0

      2. I change my settings:

        cat /etc/exports
        /iso 192.168.10.0/24(rw,sync,no_subtree_check,all_squash,anonuid=36,anongid=36)

        create user vdsm and group kvm 36:36

        run nfs check script from http://wiki.ovirt.org/wiki/Troubleshooting_NFS_Storage_Issues
        (python nfs-check.py storage.ovirt.com:/iso
        Current hostname: admin.ovirt.com – IP addr 192.168.10.10
        Trying to /bin/mount -t nfs storage.ovirt.com:/iso…
        Executing NFS tests..
        Removing vdsmTest file..
        Status of tests [OK]
        Disconnecting from NFS Server..
        Done!
        )

        but still have error (Error: A Request to the Server failed with the following Status Code: 500)

        part of vdsm log whan ovirt try to create new domain:
        http://rhevnfs.biz.tm/shit/vdsm.log

  7. iam having trouble with setting up. engine-setup get a failure:
    2012-09-13 21:07:07::DEBUG::all_in_one_100::397::root:: Checking JBoss status.
    2012-09-13 21:07:07::ERROR::all_in_one_100::403::root:: Error: There’s a problem with JBoss service.Check that it’s up and rerun setup.
    2012-09-13 21:07:12::DEBUG::all_in_one_100::397::root:: Checking JBoss status.
    2012-09-13 21:07:12::ERROR::all_in_one_100::403::root:: Error: There’s a problem with JBoss service.Check that it’s up and rerun setup.
    2012-09-13 21:07:17::DEBUG::all_in_one_100::397::root:: Checking JBoss status.
    2012-09-13 21:07:17::ERROR::all_in_one_100::403::root:: Error: There’s a problem with JBoss service.Check that it’s up and rerun setup.
    2012-09-13 21:07:22::DEBUG::all_in_one_100::397::root:: Checking JBoss status.
    2012-09-13 21:07:22::ERROR::all_in_one_100::403::root:: Error: There’s a problem with JBoss service.Check that it’s up and rerun setup.
    2012-09-13 21:07:22::DEBUG::setup_sequences::62::root:: Traceback (most recent call last):
    File “/usr/share/ovirt-engine/scripts/setup_sequences.py”, line 60, in run
    function()
    File “/usr/share/ovirt-engine/scripts/plugins/all_in_one_100.py”, line 193, in waitForJbossUp
    utils.retry(isHealthPageUp, tries=25, timeout=15, sleep=5)
    File “/usr/share/ovirt-engine/scripts/common_utils.py”, line 717, in retry
    return func()
    File “/usr/share/ovirt-engine/scripts/plugins/all_in_one_100.py”, line 404, in isHealthPageUp
    raise Exception(ERROR_JBOSS_STATUS)
    Exception: Error: There’s a problem with JBoss service.Check that it’s up and rerun setup.

    2012-09-13 21:07:22::DEBUG::engine-setup::1742::root:: *** The following params were used as user input:
    2012-09-13 21:07:22::DEBUG::engine-setup::1747::root:: override-httpd-config: yes
    2012-09-13 21:07:22::DEBUG::engine-setup::1747::root:: http-port: 80
    2012-09-13 21:07:22::DEBUG::engine-setup::1747::root:: https-port: 443
    2012-09-13 21:07:22::DEBUG::engine-setup::1747::root:: mac-range: 00:1A:4A:A8:73:00-00:1A:4A:A8:73:FF
    2012-09-13 21:07:22::DEBUG::engine-setup::1747::root:: host-fqdn: kvmserv.local
    2012-09-13 21:07:22::DEBUG::engine-setup::1747::root:: auth-pass: ********
    2012-09-13 21:07:22::DEBUG::engine-setup::1747::root:: org-name: epalbertz
    2012-09-13 21:07:22::DEBUG::engine-setup::1747::root:: default-dc-type: NFS
    2012-09-13 21:07:22::DEBUG::engine-setup::1747::root:: db-remote-install: local
    2012-09-13 21:07:22::DEBUG::engine-setup::1747::root:: db-host: localhost
    2012-09-13 21:07:22::DEBUG::engine-setup::1747::root:: db-local-pass: ********
    2012-09-13 21:07:22::DEBUG::engine-setup::1747::root:: nfs-mp: /mnt/iso5
    2012-09-13 21:07:22::DEBUG::engine-setup::1747::root:: iso-domain-name: iso
    2012-09-13 21:07:22::DEBUG::engine-setup::1747::root:: config-nfs: yes
    2012-09-13 21:07:22::DEBUG::engine-setup::1747::root:: override-iptables: yes
    2012-09-13 21:07:22::DEBUG::engine-setup::1747::root:: config-allinone: yes
    2012-09-13 21:07:22::DEBUG::engine-setup::1747::root:: storage-path: /mnt/storage
    2012-09-13 21:07:22::DEBUG::engine-setup::1747::root:: superuser-pass: ********
    2012-09-13 21:07:22::ERROR::engine-setup::2376::root:: Traceback (most recent call last):
    File “/bin/engine-setup”, line 2370, in
    main(confFile)
    File “/bin/engine-setup”, line 2159, in main
    runSequences()
    File “/bin/engine-setup”, line 2105, in runSequences
    controller.runAllSequences()
    File “/usr/share/ovirt-engine/scripts/setup_controller.py”, line 54, in runAllSequences
    sequence.run()
    File “/usr/share/ovirt-engine/scripts/setup_sequences.py”, line 154, in run
    step.run()
    File “/usr/share/ovirt-engine/scripts/setup_sequences.py”, line 60, in run
    function()
    File “/usr/share/ovirt-engine/scripts/plugins/all_in_one_100.py”, line 193, in waitForJbossUp
    utils.retry(isHealthPageUp, tries=25, timeout=15, sleep=5)
    File “/usr/share/ovirt-engine/scripts/common_utils.py”, line 717, in retry
    return func()
    File “/usr/share/ovirt-engine/scripts/plugins/all_in_one_100.py”, line 404, in isHealthPageUp
    raise Exception(ERROR_JBOSS_STATUS)
    Exception: Error: There’s a problem with JBoss service.Check that it’s up and rerun setup.

    Do you have an idea?
    I am running fedora 17 with kernel 3.5 up to date.

    1. I’ve hit an issue w/ the jboss part of the script a few times. I’ve run engine-cleanup and tried again. (though, from the look of your iso mount path, numbered 5, it looks like you may have run through this a few times already?)

      1. yes, i did it several times now. No chance to get it work. i uses a lxde enviroment, is this maybe the reason ?
        why do you think it`s the jboss?
        Maybe more of this error:
        Installing:
        AIO: Validating CPU Compatibility…WARNING: gnome-keyring:: couldn’t connect to: /home/torsten/.cache/keyring-uBiIi6/pkcs11: Datei oder Verzeichnis nicht gefunden

      2. Hmm, I don’t know what’s up w/ the gnome-keyring error message. I’ve done all my testing w/ headless, minimal installs — no desktop environments. I don’t know why that would matter, though…

      3. – i have reinstalled the hole system with the fedora standalone iso as minimal.
        – next step was yum update
        – reboot
        – installed like you discribed
        no keyring error (maybe cause i have now only user root and no one else), installation stops now on adding local host, but this shouldn´t matter.

        Now i have 2 problems:
        – mainpage from ip_server is working, but clicking on administration couldn´t resolve path. a manually opend 192.168.115.31/webadmin opens the login screen
        – i can´t log in. i can´t remember to define any username than root. what or where do i find the username? there is only one password for all, so this can´t be wrong.

      4. You can add a line in /etc/hosts on your client machine (the one w/ the web browser) to make your engine’s IP address resolve to its host name.

        The default username is admin.

      5. thanks a lot, user name admin was the last i tried.
        But the problems doesn´t end. I am a pure ovir beginner so i hope i doesnt ask stupid thinks…
        – my local_host doesn´t start. ovirt always shows “not responsible”
        – storage says not attached although i added the path from engine_setup /home/storage
        – proppably something worng in configure local storage because the settings for path will not be stored, although i don´t get an error after saving.
        i thing this als is the same problem because the local_host is not responsible and therefor i can´t store the path?

      6. In order to add your storage, you need to take your host out of maintenance mode. Highlight it and click activate. If your host won’t become active, and says non-responsive, you can try running “sudo service vdsmd restart” on your engine. Vdsmd is the daemon that controls the virt hosts.

        Some other things: make sure you have all updates applied. Also, I see that you’re running kernel 3.5 — there’s a bug w/ that version of the kernel & ovirt. The 3.3 kernel that originally came w/ Fedora will work fine. The last 3.4.x Fedora kernel is no longer in the repos, but you can get it here: http://koji.fedoraproject.org/koji/buildinfo?buildID=333970.

      7. Kernel 3.3 has a big bug with vt-d under ubuntu 12.04. (forzen kvm when activating) Kernel 3.5 was my hope to get kvm better run with vt-d and the reason for trying ferdora with ovirt.
        surly i have done a yum update bevor adding ovir all in one. But your are right the iso domain type nfs is unattached. I thought i don´t need iso when installing from dvdrom?
        At this moment i have reinstalled after engine cleanup everything with the paths of your video (/mnt/iso and /mnt/data) and now the local_host and storage is running like discribed in your video. Could it be a permission problem when choosing /home ?

      8. i have replaced the 3.5 now with the 3.4 from your link. it needed a reinstallation of the all in one package (maybe not really nessesary but i lost the web connection).
        I can atach the local_datacenter but i am unable to activate it.
        It get´s “Failed to attach Storage Domain iso to Data Center local_datacenter. (User: admin@internal)”
        Am i right, i need iso´s for installing a vm? no redirection to local dvd rom possible?

      9. You do need an iso domain to install VMs. You have the 3.4 kernel installed now — just double check that you’re booted into it, because failure to attach to an nfs domain is the bug w/ 3.5. It might be easier to proceed w/ help from #ovirt on the OFTC server on irc. I’m jbrooks there.

    1. I thing you tried to use the virtio driver.
      Change the settings of vm for normal sata, install the system and then you can install the virtio driver in windows. last step is to change back to virtio.
      this should solve your problem.

      1. There is not sata in the VM disk option, instead i have IDE. I chose IDE but still encountering the same problem.

    2. Dear All,

      I found that this error was due to a bad Win7 Iso image. I downloaded the latest Trial ISO file from Microsoft and installation worked like a charm.

  8. Hmm, this does seem like a different issue — I haven’t seen it before, but someone in the irc room today was asking about what looks like the same issue. I’ll try to reproduce it.

    You might try going into the admin console and adding a local datacenter from there. See if you hit this same error through that path. Either way, this does look like a (new) bug w/ the all in one plugin.

    You should consider stopping in, as well, at the irc room, it’s #ovirt on the OFTC network. My handle is #jbrooks there.

    1. On browser
      login

      -> Administrator Portal
      Data Center
      Deafult NFS Uninitialized 3.1 The default Data Center (already displayed)

      highlight above
      -> Sorage (nothing displayed)
      -> Logical Networks (ovirtmgmt Management Network)
      -> Clusters (Default 3.1 The default server cluster)
      -> Quota (DefaultQuota-Default Automatic generated Quota for Data Center Default)
      -> Permissions (admin *admin@internal SuperUser (System)
      -> (nothing displayed, only blinking)

      Clusters
      Default 3.1 The default server cluster

      Hosts
      nothing displayed

      Storage
      satimis ISO NFS V1 Unattached You should consider stopping in, as well, at the
      > irc room, it’s #ovirt on the OFTC network. My
      > handle is #jbrooks there.

      Sorry I didn’t follow. Pls explain. Tks

  9. OK. This is indeed another bug. Your system is pulling in v 3.2 of the sdk, and it should be using v 3.1. You should be able to
    “yum downgrade http://www.ovirt.org/releases/3.1/rpm/Fedora/17/noarch/ovirt-engine-sdk-3.1.0.4-1.fc17.noarch.rpm” and then add “exclude=ovirt-engine-sdk” under the [main] section of your /etc/yum/yum.conf file. That will prevent that packaged from being upgraded. This should allow you to do engine-cleanup and then set up the engine. I’ve filed a bug about this, hopefully it’ll be addressed soon.

  10. I got it finally working. I got an strange problem of SElinux which I fixed by enabling SElinux in permissive mode.

    I got the 3.2 version problem which I fixed with the suggested package downgrade.

    Finally I got the:

    AIO: Adding Local host (This may take several minutes

    error… but the suggested steps in the WEB UI did not seem to work for me (Too long waiting for tasks to be completed).

    So… Here’s what you have to do… Before running engine-setup you have to edit:

    /usr/share/ovirt-engine/scripts/plugins/all_in_one_100.py

    file and edit the waitForHostUp function so that the timeout is smaller. Like this:

    def waitForHostUp():
    utils.retry(isHostUp, tries=40, timeout=300, sleep=5)

    I’m using Fedora 17.

    Thank you for your article and for the all-in-one installer plugin.

    adrian15

  11. hi, i am unable to down grade to the ovirtengine sdk ver 3.1…

    [root@localhost ~]# yum downgrade ovirt-engine-sdk
    Loaded plugins: langpacks, presto, refresh-packagekit, versionlock
    Resolving Dependencies
    –> Running transaction check
    —> Package ovirt-engine-sdk.noarch 0:3.1.0.4-1.fc17 will be a downgrade
    —> Package ovirt-engine-sdk.noarch 0:3.2.0.2-1.fc17 will be erased
    –> Finished Dependency Resolution
    Error: Package: ovirt-engine-setup-plugin-allinone-3.1.0-4.fc17.noarch (@ovirt-stable)
    Requires: ovirt-engine-sdk >= 3.2
    Removing: ovirt-engine-sdk-3.2.0.2-1.fc17.noarch (@updates)
    ovirt-engine-sdk = 3.2.0.2-1.fc17
    Downgraded By: ovirt-engine-sdk-3.1.0.4-1.fc17.noarch (ovirt-stable)
    ovirt-engine-sdk = 3.1.0.4-1.fc17
    Available: ovirt-engine-sdk-1.3-1.fc17.noarch (fedora)
    ovirt-engine-sdk = 1.3-1.fc17
    You could try using –skip-broken to work around the problem
    You could try running: rpm -Va –nofiles –nodigest

  12. Hi jason,
    I want to ask if it is possible to create multiple users to access the ovirt console instead of only logging in with the user “admin”?

    P.S. I have go tmy installation working already. thanks.

  13. Has anybody managed to get a 3.1 database running within 3.2 current release ? I tried finding a migration procedure, but it seems there hasn’t been one, done yet.

  14. Hi. Need urgent help, I’am trying to install oVirt AIO, but when starting “engine-setup” got an error:

    oVirt Engine will be installed using the following configuration:

    =================================================================

    http-port: 80
    https-port: 443
    host-fqdn: cloud.localdomain
    auth-pass: ********
    org-name: Demo
    default-dc-type: NFS
    db-remote-install: local
    db-local-pass: ********
    nfs-mp: /mnt/iso
    iso-domain-name: iso
    override-iptables: yes
    config-allinone: yes
    storage-path: /mnt/data
    superuser-pass: ********

    Proceed with the configuration listed above? (yes|no): yes
    Installing:
    AIO: Validating CPU Compatibility… [ DONE ]
    Configuring oVirt-engine… [ DONE ]
    Creating CA… [ DONE ]
    Editing JBoss Configuration… [ DONE ]
    Setting Database Configuration… [ DONE ]
    Setting Database Security… [ DONE ]
    Creating Database… [ ERROR ]

    Database creation failed

    Please check log file /var/log/ovirt-engine/engine-setup_2013_02_02_21_38_24.log for more information

    Fedora 18, netinstall, minimal installation.

    1. I think I got through this by enabling the ovirt beta repo, it was to do with the Postgresql version not matching what was expected.

      After many hurdles, I got it install and run on F18, but it just hung at admin login and I threw in the towel. I was going to try CentOS, but gave F17 a go and got it to work (see notes above).

  15. I’m installed F17, clean

    I’m installed http://www.ovirt.org/releases/ovirt-release-fedora.noarch.rpm

    I’m installed ovirt-engine-setup-plugin-allinone

    my hostname is resolvable, via DNS and /etc/hosts

    I’m disabled SELinux

    I’m started engine-setup, and answered all questions.

    I got “Creating Database… [ ERROR ]

    Failed updating configuration parameter: Error: failed updating configuration field CAEngineKey to /etc/pki/ovirt-engine/private/ca.pem

    OK. I’m removed all ovirt and postgresql packages, and after that removed /etc/ovirt-engine, /etc/pki/ovirt-engine, /var/lib/pgsql and iso/localstorage folders manually. Purged iso storage from /etc/exports

    I’m installed oVirt again, and started engine-setup again.
    All the same settings, but now I’m getting:
    “Starting JBoss Service… [ ERROR ]
    Error: Can’t start the ovirt-engine service”

    It makes me cry….

    I re-run all above again. Same results. All versions/updates from today.

    1. After one hurdle too many trying to get oVirt on F18 running, I went back to F17, got the same “Can’t start the ovirt-engine service” error.

      I found a PID file, rm /var/run/ovirt-engine.pid from previous attempts, deleted it, did a cleanup then setup, and it all finally installed.

      You’ll then see that you can’t log into the Admin portal as JBoss won’t start. Here’s a fun part – you need to downgrade openjdk rpm’s. Don’t bother with yum downgrade option, it won’t work. Do this;

      search and download these rpm’s:
      java-1.7.0-openjdk-1.7.0.9-2.3.3.fc18.1.x86_64.rpm
      java-1.7.0-openjdk-devel-1.7.0.9-2.3.3.fc18.1.x86_64.rpm

      remove the bad packages;
      rpm -e –nodeps java-1.7.0-openjdk java-1.7.0-openjdk-devel

      then install;
      yum locallinstall –nogpg java-1.7.0-openjdk-1.7.0.9-2.3.3.fc18.1.x86_64.rpm java-1.7.0-openjdk-devel-1.7.0.9-2.3.3.fc18.1.x86_64.rpm

      Now JBoss should be happy, test via;

      cd /usr/share/jboss-as/bin
      ./standalone.sh (kill it after it comes up).

      We can then start the engine again, but not before removing the pid file again (grrrr);

      rm /var/run/ovirt-engine.pid
      systemctl start ovirt-engine.service

      Wow, it’s been an adventure.

      1. Wow, thank you. I was tearing my hair out trying to figure out the jboss logmanager error. Got it running on F17 as well now.

        A little ways down Jason mentions the wrong ovirt engine sdk is being installed from the package list and he submitted a fix. Using the package provided here still loads up version 3.2 though; which I’m currently running. Didn’t downgrade it.

      2. Yep, I spent about 3 hours on the logmanager error, learned more about trying to set java properties than I wanted to. I stumbled on the solution today in an off the cuff sentence on http://www.ovirt.org/Quick_Start_Guide where it mentioned the problem on F18 and the solution. I couldn’t believe it was in the main doc but threads abounded with people trying to find a solution. Strangely, I can’t find it anywhere on the site now, I wonder of it’s been edited out.

        I only fixed my F17 logmanager problem because I’d already gone through it on F18.

  16. I install allinone in a machine and it work well,but I want to install node in another machine ,so error is come,”Failed to install Host node1.cec.com. Step: INSTALLER LIB; Details:
    deployUtil.py download failed. Pathname could not be resolved (verify
    computer/domain name)..”,what’s the matter?you can see the problem in the pic

Comments are closed.