I’ve written an updated version of this howto for oVirt 3.3 at the Red Hat Community blog.
The latest version of the open source virtualization platform, oVirt, has arrived, which means it’s time for the third edition of my “running oVirt on a single machine” blog post. I’m delighted to report that this ought to be the shortest (and least-updated, I hope) post of the three so far.
When I wrote my first “Up and Running” post last year, getting oVirt running on a single machine was more of a hack than a supported configuration. Wrangling large groups of virtualization hosts is oVirt’s reason for being. oVirt is designed to run with its manager component, its virtualization hosts, and its shared storage all running on separate pieces of hardware. That’s how you’d want it set up for production, but a project that requires a bunch of hardware just for kicking the tires is going to find its tires un-kicked.
Fortunately, this changed in August’s oVirt 3.1 release, which shipped with an All-in-One installer plugin, but, as a glance at the volume of strikethrough text and UPDATE notices in my post for that release, there were more than a few bumps in the 3.1 road.
In oVirt 3.2, the process has gotten much smoother, and should be as simple as setting up the oVirt repo, installing the right package, and running the install script. Also, there’s now a LiveCD image available that you can burn onto a USB stick, boot a suitable system from, and give oVirt a try without installing anything. The downsides of the LiveCD are its size (2.1GB) and the fact that it doesn’t persist. But, that second bit is one of its virtues, as well. The All in One setup I describe below is one that you can keep around for a while, if that’s what you’re after.
Without further ado, here’s how to get up and running with oVirt on a single machine:
HARDWARE REQUIREMENTS: You need a machine with x86-64 processors with hardware virtualization extensions. This bit is non-negotiable–the KVM hypervisor won’t work without them. Your machine should have at least 4GB of RAM. Virtualization is a RAM-hungry affair, so the more memory, the better. Keep in mind that any VMs you run will need RAM of their own.
It’s possible to run an oVirt in a virtual machine–I’ve taken to testing oVirt on oVirt itself most of the time–but your virtualization host has to be set up for nested KVM for this to work. I’ve written a bit about running oVirt in a VM here.
SOFTWARE REQUIREMENTS: oVirt is developed on Fedora, and any given oVirt release tends to track the most recent Fedora release. For oVirt 3.2, this means Fedora 18. I run oVirt on minimal Fedora configurations, installed from the DVD or the netboot images. With oVirt 3.1, a lot of people ran into trouble installing oVirt on the default LiveCD Fedora media, largely due to conflicts with NetworkManager. When I teseted 3.2 with the With 3.2, the installer script disabled NM on its own, but I had to manually enable sshd (sudo service sshd start && sudo chkconfig sshd on).
A lot of oVirt community members run the project on CentOS or Scientific Linux using packages built by Andrey Gordeev, and official packages for these “el6” distributions are in the works from the oVirt project proper, and should be available soon for oVirt 3.2. I’ve run oVirt on CentOS in the past, but right now I’m using Fedora 18 for all of my oVirt machines, in order to get access to new features like the nested KVM I mentioned earlier.
NETWORK REQUIREMENTS: 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. If you take the hosts file editing route, the installer script will complain about the hostname–you can safely forge ahead.
CONFIGURE THE REPO: Somewhat confusingly, oVirt 3.1 is already in the Fedora 18 repositories, but due to some packaging issues I’m not fully up-to-speed on, that version of oVirt is missing its web admin console. In any case, we’re installing the latest, 3.2 version of oVirt, and for that we must configure our Fedora 18 system to use the oVirt project’s yum repository.
sudo yum localinstall http://ovirt.org/releases/ovirt-release-fedora.noarch.rpm
SILENCING SELINUX (OPTIONAL): I typically run my systems with SELinux in enforcing mode, but it’s a common source of oVirt issues. Right now, there’s
definitely one (now fixed), and maybe two SELinux-related bugs affecting oVirt 3.2. So…
sudo setenforce 0
To make this setting persist across reboots, edit the ‘SELINUX=’ line in /etc/selinux/config to equal ‘permissive’.
INSTALL THE ALL IN ONE PLUGIN: The package below will pull in everything we need to run oVirt Engine (the management server) as well as turn this management server into a virtualization host.
sudo yum install ovirt-engine-setup-plugin-allinone
RUN THE SETUP SCRIPT: Run the script below and answer all the questions. In almost every case, you can stick to the default answers. Since we’re doing an All in One install, I’ve tacked the relevant argument onto the command below. You can run “engine-setup -h” to check out all available arguments.
One of the questions the installer will ask deals with whether and which system firewall to configure. Fedora 18 now defaults to Firewalld rather than the more familiar iptables. In the handful of tests I’ve done with the 3.2 release code, I’ve had both success and failure configuring Firewalld through the installer. On one machine, throwing SELinux into permissive mode allowed the Firewalld config process to complete, and on another, that workaround didn’t work.
If you choose the iptables route, make sure to disable Firewalld and enable iptables before you run the install script (sudo service firewalld stop && sudo chkconfig firewalld off && sudo service iptables start && sudo chkconfig iptables on).
sudo engine-setup --config-allinone=yes
TO THE ADMIN CONSOLE: 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, click 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 activate it.
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. I made the “creating VMs” screencast below for oVirt 3.1, but the process hasn’t changed significantly for 3.2:[youtube:http://www.youtube.com/watch?v=C4gayV6dYK4&HTML5=1%5D
22 responses to “Up and Running with oVirt, 3.2 Edition”
[…] Update: I’ve written an updated version of this guide for oVirt 3.2. […]
Able to get Ovirt 3.2 up and running. Works well, however, can’t get the spice console to launch from windows IE… Console works fine from Linux with firefox though. Anyone else run into this??
Hey Ryan, check out: http://wiki.ovirt.org/How_to_Connect_to_SPICE_Console_With_Portal
Thanks Jason. With 3.1 it seems that the spice plugin for IE was installed and working fine so I assumed it would be the same for 3.2.. Anyway, this works now. Thanks!
Then, during the installation of oVirt, the last part appears:
AIO: Adding Local host (This may take Several minutes) …… ERROR
This can often be because of that?
I do not set the / etc / host.conf, then oVirt consigue not resolve hostname.
oVirt needs to be able ssh to itself from the hostname you provide for this to work.
Does anybody can add virtualized host? I am not abde to add it. I have fresh minimal installaon of Fedora 18. In vdsm.conf enabled fake kvm option. But in ovirt management I see these errors during adding this hosts:
Host ovrit-node1 installation failed. Command returned failure code 1 during SSH session ‘firstname.lastname@example.org’.
Failed to install Host ovrit-node1. Failed to execute stage ‘Setup validation’: [Errno 5] Input/output error.
I didn’t cover fake kvm in this walkthrough. Are you trying to set this up on a machine without hardware virt extensions?
I have one physical machine where I am running couple of VMs. There I create 2 new VMs. One as ovrit management and second one is “host” which I would like to add to ovirt. Fake KVM support is enabled in vdsm.conf. I found out some guy has same issue https://bugzilla.redhat.com/show_bug.cgi?id=911697 but it was caused by missing tar. I check my systems and I had it. I decided to reinstall both machine and during netinstallation process I selected minimal install + standard (common tools) but this also did not help.
I keep getting to the ‘Configuring the Default ISO Domain…’ stage and get an error every time. I suspect it’ll be service-related. Everything else is as per the (very appreciated!) guide. I’m looking for a production-ready open source alternative to vSphere and crossing my fingers I can get something on a box to show my boss.
It was SELinux. I had turned it off. My bad :-/ Thanks again for the walkthrough.
It was more than SELinux. I’ve wrestled with Firewalld (which seems to ignore any opened ports/services between reboots), had to go through the ‘troubleshooting nfs shares’ section of the Ovirt site and tweaked the hostame and hosts file. That left me with a functional Ovirt install. Impressive.
I’ve just found a problem with the network. It won’t come up on boot. If I start it manully, fine. All related services enabled and ifcfg files at post-Ovirt-install state.
Might well be a Fedora 18 issue. Any ideas? It’s stopping me putting this new toy in the rack and I want to play with it!
I’m able to set up Active Directory authentication if my ovirt engine is set to use dns that is hosted on the same system as Active Directory. However, if I use static host entries in my engine “hosts” file instead of using dns I’m getting the error “ldap server for domain not found” when I issue the command: “engine-manage-domains -action=add -domain=’ovirt.local’ -user=’admin’ -provider=ActiveDirectory -interactive” from the engine. I’ve googled to death how to configure static entries on my engine system for the ldap server and it seems that I need to configure my nsswitch and ldap.conf files but still no luck… Any ideas??
hi,”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
Hi there, Ive managed to make a fix for the few things that are currently broken with the engine-setup script. See my site here: http://www.hacktheory.org/index.php/projects/projects-by-eureka/ovirt-32-setup-all-required-bug-fixes/
I had to disable nfs 4 to get my iso_domain to mount
i was able to force “no v4″ on the ovirtmgr host, by adding
to /etc/sysconfig/nfs, then restarting NFS server, systemctl restart nfs-server.service
Somehow i cannot get the ISO domain attached to the local datacenter, i keep getting this error; “Failed to attach Storage Domain ISO_DOMAIN to Data Center local_datacenter. (User: admin@internal)”
I’m not sure what to look for in the logs, but i do not see any obvious errors there?
Am I missing something or is this normal: I cannot add users to my datacenter. I am using the “AiO” installation model.
When logged in through the Administration Portal, I see the “Users” pane. However, only “admin” & “everyone” is there. Trying to perform “Add” leads no where. I can only search for users when only “admin” comes up.
NVM. I need to integrate my box with an AD service to authenticate users.
Please post a step by step best practice doc to upgrade oVirt 3.1 to oVirt 3.2. I am running my production environment with oVirt 3.1 which need to be upgrade to latest version.
I’m on CentOS 6.4 and I’ve installed oVirt using the all in one plugin. Everything appears to be working correctly until I try to start a VM. I’ve uploaded a Ubuntu Server 12.04.2 iso and a CentOS minimal iso. I’ve tried to create VM using both, I set the Ubuntu to type as “other linux” and CentOS as RHEL 6.X. I then add the network and a new disk. After I click “run once” I select the appropriate ISO and press ok. That’s when it fails. In the events I get this:
2013-Jul-08, 21:02Failed to run VM CentOS_Test (User: admin@internal).
2013-Jul-08, 21:02Failed to run VM CentOS_Test on Host local_host.
2013-Jul-08, 21:02VM CentOS_Test is down. Exit message: internal error process exited while connecting to monitor: Supported machines are: pc RHEL 6.4.0 PC (alias of rhel6.4.0) rhel6.4.0 RHEL 6.4.0 PC (default) rhel6.3.0 RHEL 6.3.0 PC 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 .
2013-Jul-08, 21:02VM CentOS_Test was started by admin@internal (Host: local_host).
Any ideas of what to do next? Thanks
Can you explain how you got past the error “Exception: Error: could not create ovirtsdk API object”? I’m installing with 3.2.2 allinone onto a CentOS 6.4 server.