The initial setup is straightforward. It takes about a day to set up a two-node cluster. While deploying the solution, we have to just install the operating system.

The initial setup of Oracle VM is straightforward. It's very well documented, and you can do it if you follow up on documentation. You don't need more than two weeks to deploy the solution.

You need to check hardware compatibility and thoroughly plan the deployment process. Additionally, network configuration and migration steps must be carefully planned and executed. It's essential to acknowledge and address potential complexities. What is your network configuration, how is it set up, and how do we design your network? Network impact is significant, as are VLANs and these things. Once you have everything on paper, you can start to implement it. If it's VM migration, you will get a new VM. You start deploying a new application if it's the exact migration. Then, you must follow the migration steps to visit the application from where you come. One of the applications will give you steps to move from one system to a different one.

The initial setup was quite simple. We also were able to upgrade to various newer versions with minimum handholding.

The initial setup is not easy. Sometimes you have to spend one week to put some machines running on it. You need to clean the operation system, prepare everything, and do a lot of tests before you put the machine to get consistency and guarantee.

The product's initial setup phase was simple.

One can deploy the solution by just downloading and installing it.

The solution is deployed on an on-premises model.

The solution can be deployed in less than a minute.

One admin is enough to take care of the deployment and maintenance of the product.

The initial setup was straightforward. The deployment took one hour and required three people.

The initial setup for Oracle VM is very difficult. The main problem is the stability and scalability of the solution. The drawbacks are the backup. There are no backup products certified with Oracle VM. This is not a problem with Oracle KVM. Another problem is when you patch your kernel, Xen is in the kernel, and Xen is not very reliable. In fact, you may have some crashes, so it's very difficult to maintain Oracle VM.

It depends on if you are setting up a simple environment or a more complex one where you have to look at the Fiber Channel storage, high availability, and things like that. If you are looking at setting up a complex multi-site cluster of Oracle VM for SPARC, it is not easy. You have all of the clustering parts, multi-site parts, storage, and networking that come with the setup. It is still easier to set up these systems now compared to back when you had bare-bone systems and had to do everything yourself.

The initial setup was a little challenging at first as when we first started the hypervisor, we did not have support for our raid controller card so we had to learn to compile a custom kernel. However, the latest versions are much better.

The initial setup was straightforward.

The implementation process is very straightforward. It is very user-friendly and it is very well-documented. 

The deployment process can be handled by one or two people. It's a total single product. It's a single product that needs to be installed on the physical servers. On the station side, just you have to install Oracle VM Manager, and that's it. 

The setup is pretty straightforward. It doesn't require any maintenance once it is up and running. 

It took about three weeks to set up the VM itself, however, Oracle in general takes a long time to implement - maybe six months.

I wasn't directly involved in the deployment process and cannot speak to how it was done. 

We have 36 technical staff that help handle the deployment and maintenance. 

Unfortunately, I used my VMware experience and applied it to the Oracle VM setup. Looking back, that was probably not the right approach as some things in Oracle VM are very different. The LUN presentation issue came down to poor documentation as there were two ways to present the LUNs and the documentation made it seem the improper method was the way to go.

Within one day, we had migrated a physical to virtual server and then we had a database working, and it was like seamless transition. We just changed the alias of that machine to whatever the listing server alias name was, and the application picked up right away.

On a scale of one to ten, where one being difficult and ten being easy, I rate the setup a five because the vendor was supposed to have done the biggest part, and they actually don't configure everything.

The deployment was done in a week or two.

Three people, along with the vendor, were needed for deployment.

The initial setup is not as easy as VMware, but over time and with experience, it will become easier.

When we installed the product in 2014, its documentation was simple and crystal clear. Now, it is complicated. We have to jump from one page to another. I rate its deployment an eight out of ten. Deployment takes around two hours to complete. 

Back in 2014 or 2013, during my tenure in the installation, I found it to be straightforward. It had simple steps including, installing the OVS server and OVM manager. The Oracle VM is installed on-premises. The initial deployment took over four days. But now if install any other environment, it won’t take more than four hours. It involved two people and we had done it ourselves. I would rate it an eight out of ten.

I configured the applications and deployed this solution. Deployment doesn't take very long, it just depends on the situation. I can build an Oracle environment in one day and deploy virtual machines. to mange Oracle VM server we need Oracle VM Mmanager. that is also easy configure. a complete guide is available. just study thoroughly before deployment.

The initial setup for Oracle VM was easy. It wasn't a complex process.

Oracle VM's initial setup takes around twenty minutes. I rate Oracle VM an eight out of ten for its initial setup.

The solution's initial setup process is easy.

The tool's deployment was straightforward. The deployment took around 10 minutes to complete. 

It is very difficult to implement.

It is not user-friendly, so you need a bit of skill to deploy it.

When compared to other solutions, it is quite complex. The complexity depends on the individual environment.

The initial setup of Oracle VM is as straightforward as it can be taking me 20 minutes.

The solution was not necessarily complex. It was very straightforward.

It was fairly easy for an experienced Linux admin.

That's the beautiful part. There's documentation out there and it's pretty straightforward, as long as you stick to the manual. It's pretty easy to set up. If you're installing an Oracle Database, you literally go to hours from what used to take days.

The initial setup takes a little bit of thinking, and a little bit of reading, however, it's not particularly difficult. If you have the rest of your hardware and everything in place, it installs within a day or two. By that I mean you need a day to install it and then another day or so to adjust and tweak, and I haven't found it to be that difficult to install.

Initial setup of Oracle VM and the rest of stack was very straightforward. The steps in Oracle documentation were very easy to follow.

I set up the manager first. Since this is an Oracle installation, I chose to install the manager software on Oracle Linux 6.1. Nothing fancy needed, but I installed the desktop to make things easier for me. I have two NICs set up, one to connect to my network, and the other to connect to the hosts (for management, VM live migrations, and the heartbeat). I then installed the manager software and you just need to click Next>Next>Next. Be sure to write the password down, as this is the password needed to gain access to the management console (via web).

The hosts were a snap. We do not have any hard drives in the host, but do have a flash card to boot from. So I chose the "minimal" install for the flash card install, and you need to set a root password and a discover password. Make note of them as you will need the discover password to make the connection in the manager. Keep the discover password the same for all hosts to make it easier. Once in the manager, before you discover all the hosts you need to manage, you will need to set what the VLANs are, bonds to the network, how many virtual NICs you will need, etc. After you discover the nodes, you will need to set up a pool repository that keeps all the info on the VMs. This repository should go on the SAN. Another repository should be set up for all your ISOs and other VM volumes if you chose not to use raw LUNs. Connect all the storage you will use (we have HP P4300s). We use all raw iSCSI LUNS for our VMs. We lose some functionality in OVM, but gain others via the SAN (snapshots, etc).

I would say it’s less straightforward than you’d expect. I haven’t installed it recently, but my impression was that it was about 70% ready for prime-time. Once you have it installed and sorted out, it runs pretty smoothly. Getting it there is another issue entirely.

It is very simple and straightforward. You just need to connect a bunch of servers to the storage, and you're done. For installation, you just download the parts of the software and install them on the server. Once installed, you discover them through the management interface, and that's about it.

The software installation takes about 20 minutes, but it also depends on how many services you are attaching to the storage. Its maintenance involves just upgrades.

Setting up Oracle VM depends on what you want to do with it. If you want to do a basic install and use the normal management console, I’ve done that in a couple of hours. I’m experienced with it. 

But if you want to build private clouds with it, you want to interface the Enterprise Manager, have chargeback functionality for users, you want to do cloud automation; that’s a little more complicated. If you haven’t done it, it takes about a week. However, there’s a book from Oracle Press about Oracle VM 3 and building private clouds, and that helps a lot with what's involved in this task, to build and support a system.

Up and running with VMs in an afternoon. Easy!

The hypervisor installation and setup is one of the most simple things that I have ever done. Just boot, select the proper installation method, configure (Linux-like), and you're done.

On the other hand, the Manager can be a little tricky, but the newer versions have become much easier. Just set up your OS and pre-requisites, database, and OVM Manager.

It is simple and straightforward, and it will only require you one system integrator to do the job. If you can read the English directions on the screen, then you can do it.

I was involved in the initial setup. It was relatively simple. There were just Linux installs.

At first, the initial setup was not so straightforward and was rather complex. This is largely due to the fact that we were not aware of the environment and how to use it properly. I believe it will get easier to implement over time.

You need to deploy the server and have the virtualization on top of that. Then you configure and install everything. How long it takes depends on the environment. If it's a small deployment, it may only take about two days. A larger deployment could take as long as six to eight weeks. 

I've done a file server deployment, and that only took three days.

You only need one person to deploy the solution.

The initial setup was very hard and required me to create a build doc to my company so anyone could do it again. The cluster documentation is not straightforward when we use 3rd party SAN hardware.

The initial setup was straightforward and no more complex than PowerVM.

It depends on how deep I want to go, but normally the initial setup is straightforward.

It was complex.

I didn't handle the implementation. I don't know if the initial setup was complex or straightforward. Other people on my team handled that part of the process.

It is very simple to setup and deploy. But, it should be noted that a systems architect or systems engineer must be at the helm of the deployment. The setup must be conducted by someone well-versed in Linux. 

Initially, when we setup we had to make sure we had a staff architect that was knowledgeable with storage skills and Linux. Those were our requirements for proper deployment. 

It's been a struggle. Over the years, it's gotten better and better. I think what's helped tremendously is the integration of OVM with PCA, and so all the setup has really been taken out of the hands of the administrator. It's really more of a deployment thing than it is a setup thing. That's helped a lot.

Initial setup was pretty good. It was basically out of the box because the Oracle Database Appliance is being promoted as out of the box. You turn on a switch and a login script starts up the whole process; that worked out well. We had a few glitches in terms of learning how it all works together. We certainly overcame some of those challenges and we're really happy with the product.

It's implemented just fine. The setup was pretty easy and straightforward. It was a combination of an easy product to install and technical expertise as well.

If you only use the Command Line, it's easy. If you use the VM Management Console, you need to do more. Basically, another VM to manage, by itself, the cluster. But no, it's not complex.

It's a little bit cumbersome. To know exactly how to install it and the management pieces wasn't as straightforward as some of my admins have said.

The initial setup was pretty straightforward. All you have to do is to choose the right options.

The initial setup is straightforward, deployment time really depends on the client's needs. Sometime it takes two to three days and sometimes it can take months. We also do the maintenance for them. 

It's fairly straightforward.  All you have to do is to install via script the so-called "OVM Manager", which is basically a Java administration GUI run on a WebLogic server with MySQL underlying it as a metadata repository. At the time, Oracle Database was a choice too, but it's no longer the case because, as an Oracle guy revealed, the Database engine has a major bug which corrupts lob data which prevents the the manager from working properly.

It's slightly more complex to set up than other VM software. 

The initial setup was a bit of both straightforward and complex, but it's easy if you know VMware.

Oracle VM is easy to set up. It can be deployed with one person.

We have five analysts for support and that work with it.

The initial setup was a little complex because no one in the company knew about this product as it was something new at the time. My team and I did a successful installation of our Oracle VM environment and migrated all Oracle Database and Oracle WebLogic application servers to this new infrastructure, which are now in our production environment for client deliveries.

The initial setup is as easy as walking. After that, it gets a little complicated, but if one knows what one is doing, it is still easy.

It was a complex setup. It was very difficult for me.

It was very easy to setup. We used the wizard to automatically setup the master data and the initial data.

The initial setup wasn't complex.