Re: Anyone Running Oracle on VMWare?

  • From: Thomas Roach <troach@xxxxxxxxx>
  • To: pioro1@xxxxxxxxx
  • Date: Fri, 16 Apr 2010 12:00:37 -0400

One of the other options to consider is from a support standpoint. Oracle
does not "officially" support VMWARE. if you encounter an issue with your
Databases running on VMWARE, Oracle reserves the right to ask you to
recreate the issue on a physical environment that is supported. I have only
seen this in instances where it was a new issue they had not seen and needed
to file a bug to get it fixed, but it "can happen" so beware.

On Fri, Apr 16, 2010 at 11:07 AM, Marcin Przepiorowski <pioro1@xxxxxxxxx>wrote:

> Hi,
>
> If you are going to use VMotion as far as I know you have to use VM
> datastore which is a
> kind of cluster file system. I have a lot of performance issues in
> relation to run Oracle on one physical box (part of VM cluster) and
> then migrate using VMotion to next one. From time to time
> I have problem even with start other VM's when VMotion was in progress
> due to problem with accessing data store.
>
> VMware is a good solution for test/dev not for production.
>
> regards,
> --
> Marcin Przepiorowski
> http://oracleprof.blogspot.com
>
>
>
> On Fri, Apr 16, 2010 at 8:50 AM, Martin Bach
> <development@xxxxxxxxxxxxxxxxx> wrote:
> > Good morning,
> >
> > I'm also jumping on this thread ;)
> >
> > On 04/14/2010 10:05 PM, Crisler, Jon wrote:
> >> We do have extensive resource limits on place.    Although there is some
> >> minor cpu / memory overhead , the real bottleneck seems to be I/O
> >> overhead.     As for running Oracle on a dedicated VMware host, that
> >> seems like a lot of effort just to get VMotion capabilities;  if your
> >> not going to share with other guests, then our business model does not
> >> lend itself to VMware at all.  We have some customers that actually want
> >> that capability and have done it, but they are the exception rather than
> >> the rule.
> >
> > From what I read VMWare performance is partly dependent on the CPU and
> > it's virtualisation capabilities. Again, the Xeon 55xx Range and most
> > likely the new 56xx processors will lead the race. The most expensive
> > operations in VMware are system calls though.
> > I/O performance depends on how you use your storage-vmdks are slow by
> > design (remember that the hypervisor needs to do some magic to system
> > calls). Is anyone using Direct NFS with their VMWare databases? In
> > theory the NFS implementation in userland should take the edges off the
> > IO problem. Not that I have done this myself tough ...
> >
> > Regards,
> >
> > Martin
> >
> > --
> > Martin Bach
> > OCM 10g
> > http://martincarstenbach.wordpress.com
> > http://www.linkedin.com/in/martincarstenbach
> > --
> > //www.freelists.org/webpage/oracle-l
> >
> >
> >
> --
> //www.freelists.org/webpage/oracle-l
>
>
>


-- 
Thomas Roach
813-404-6066
troach@xxxxxxxxx

Other related posts:

  1. Home
  2. oracle-l
  3. Archive
  4. 04-2010