Sponsored Content
Operating Systems Linux Red Hat VMware and Red Hat Virtualization Post 302652603 by mark54g on Thursday 7th of June 2012 10:55:00 AM
Old 06-07-2012
They are very different. RHEV is a product based on KVM. Vmware is based on their own hypervisor. Both have similar features, though different strengths and weaknesses.

One thing to note, is that RHEV does not play nicely (support wise) with other OSes besides RHEL based ones and Windows.

You'd have to ask more specific questions than the ones you have asked.
 

4 More Discussions You Might Find Interesting

1. Red Hat

Red Hat and Intel: Smart processors, virtualization boost efficiency and performance

On Monday March 30, Intel announced the availability of their much anticipated new line of processors, the Intel® Xeon® Processor 5500 series–nicknamed Nehalem. Red Hat, a long-time partner of the market-leading chip maker , collaborated on the chip’s debut, testing and optimizing the... (0 Replies)
Discussion started by: Linux Bot
0 Replies

2. UNIX for Dummies Questions & Answers

how to know if i use "Red Hat Enterprise Linux" or "Red Hat Desktop" ?

how to know if i use "Red Hat Enterprise Linux" or "Red Hat Desktop" ? (2 Replies)
Discussion started by: ahmedamer12
2 Replies

3. Ubuntu

Vmware Citrix Xenn virtualization on dedicated server

hi, I am newbie and I think I am trying to bit off more than I could chew in this field. I would like to know if virtualization with Vmware Citrix on a dedicated server under ubuntu 64bit is simple. I looked up in the board with keyword "virtualization, vmware, dedicated" but replied threads are... (2 Replies)
Discussion started by: baris35
2 Replies

4. Virtualization and Cloud Computing

Virtualization on vmware

Got tired of messing around with real hardware old and others.. Decided to spend some $$ for a QUAD-core dual cpu laptop with 8 gig of ram and 1 TB disk space.. running VMware workstation 10 on windows 8.0 , with a pair of solx86 vcs 5.1 cluster and a pair of rhel 6.4 vcs 6.x cluster.. ... (0 Replies)
Discussion started by: ppchu99
0 Replies
SYSTEMD-DETECT-VIRT(1)						systemd-detect-virt					    SYSTEMD-DETECT-VIRT(1)

NAME
systemd-detect-virt - Detect execution in a virtualized environment SYNOPSIS
systemd-detect-virt [OPTIONS...] DESCRIPTION
systemd-detect-virt detects execution in a virtualized environment. It identifies the virtualization technology and can distinguish full machine virtualization from container virtualization. systemd-detect-virt exits with a return value of 0 (success) if a virtualization technology is detected, and non-zero (error) otherwise. By default, any type of virtualization is detected, and the options --container and --vm can be used to limit what types of virtualization are detected. When executed without --quiet will print a short identifier for the detected virtualization technology. The following technologies are currently identified: Table 1. Known virtualization technologies (both VM, i.e. full hardware virtualization, and container, i.e. shared kernel virtualization) +----------+----------------+--------------------------------------+ |Type | ID | Product | +----------+----------------+--------------------------------------+ |VM | qemu | QEMU software virtualization, | | | | without KVM | | +----------------+--------------------------------------+ | | kvm | Linux KVM kernel virtual machine, | | | | with whatever software, except | | | | Oracle Virtualbox | | +----------------+--------------------------------------+ | | zvm | s390 z/VM | | +----------------+--------------------------------------+ | | vmware | VMware Workstation or Server, and | | | | related products | | +----------------+--------------------------------------+ | | microsoft | Hyper-V, also known as Viridian or | | | | Windows Server Virtualization | | +----------------+--------------------------------------+ | | oracle | Oracle VM VirtualBox (historically | | | | marketed by innotek and Sun | | | | Microsystems), | | | | for legacy and KVM | | | | hypervisor | | +----------------+--------------------------------------+ | | xen | Xen hypervisor (only domU, not dom0) | | +----------------+--------------------------------------+ | | bochs | Bochs Emulator | | +----------------+--------------------------------------+ | | uml | User-mode Linux | | +----------------+--------------------------------------+ | | parallels | Parallels Desktop, Parallels Server | | +----------------+--------------------------------------+ | | bhyve | bhyve, FreeBSD hypervisor | +----------+----------------+--------------------------------------+ |Container | openvz | OpenVZ/Virtuozzo | | +----------------+--------------------------------------+ | | lxc | Linux container implementation by | | | | LXC | | +----------------+--------------------------------------+ | | lxc-libvirt | Linux container implementation by | | | | libvirt | | +----------------+--------------------------------------+ | | systemd-nspawn | systemd's minimal container | | | | implementation, see systemd- | | | | nspawn(1) | | +----------------+--------------------------------------+ | | docker | Docker container manager | | +----------------+--------------------------------------+ | | rkt | rkt app container runtime | +----------+----------------+--------------------------------------+ If multiple virtualization solutions are used, only the "innermost" is detected and identified. That means if both machine and container virtualization are used in conjunction, only the latter will be identified (unless --vm is passed). OPTIONS
The following options are understood: -c, --container Only detects container virtualization (i.e. shared kernel virtualization). -v, --vm Only detects hardware virtualization). -r, --chroot Detect whether invoked in a chroot(2) environment. In this mode, no output is written, but the return value indicates whether the process was invoked in a chroot() environment or not. --private-users Detect whether invoked in a user namespace. In this mode, no output is written, but the return value indicates whether the process was invoked inside of a user namespace or not. See user_namespaces(7) for more information. -q, --quiet Suppress output of the virtualization technology identifier. -h, --help Print a short help text and exit. --version Print a short version string and exit. EXIT STATUS
If a virtualization technology is detected, 0 is returned, a non-zero code otherwise. SEE ALSO
systemd(1), systemd-nspawn(1), chroot(2), namespaces(7) systemd 237 SYSTEMD-DETECT-VIRT(1)
All times are GMT -4. The time now is 05:00 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy