public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Manfred_Knick <Manfred.Knick@T-Online.de>
To: Alexander Graf <agraf@suse.de>
Cc: Avi Kivity <avi@redhat.com>, kvm@vger.kernel.org
Subject: Re: KVM and VMware
Date: Thu, 26 Feb 2009 12:34:43 +0100	[thread overview]
Message-ID: <49A67E53.7010604@T-Online.de> (raw)
In-Reply-To: <15B35556-027D-4789-B159-67974B31325A@suse.de>

Alexander Graf schrieb:

> I have a patch lying around that activates hardware virtualization
> features on first VM creation and deactivates them on last destruction,
> so you can insmod kvm without blocking other VMMs from working.

> Of course you still can't run kvm and vmware virtual machines in
> parallel. But you can have both loaded without running into trouble.

That would help and ease work quite a bit, indeed!

Because:

A) There _are_ clients in the wild
which use different Virtualizations on different servers for different
applications -
especially during times of migration :)) !

B) Even if one client exclusively uses KVM,
another client exclusively uses Parallels,
another client exclusively uses VMware, ...,
the guy who has to work on those projects
is 'a bit unfortunate' to-day ;)

The procedure described in my former mail will work -
but I fear that every time e.g. a new kernel version has to be compiled,
you have to be very aware to take the right steps in the right order
again and again.

Of couse, having this patch applied,
VMware would need to be convinced
to take off their protective charm ;) at installation time.

> Of course you still can't run ...  in parallel.

Thus, if one would like to protect any ignorant user from harming
himself, the check for exclusiveness would have to be applied
dynamically at each try to start-up a VM instead, not at installation time.

Manfred


  reply	other threads:[~2009-02-26 11:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-25 13:10 KVM and VMware Manfred_Knick
2009-02-25 13:36 ` Avi Kivity
2009-02-25 14:37   ` Manfred_Knick
2009-02-25 16:03     ` Avi Kivity
2009-02-26  9:25       ` Alexander Graf
2009-02-26 11:34         ` Manfred_Knick [this message]
2009-02-26 12:03           ` Ricardo Botelho de Sousa
2009-02-26 13:43             ` Manfred_Knick
2009-02-25 14:50   ` Manfred_Knick

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49A67E53.7010604@T-Online.de \
    --to=manfred.knick@t-online.de \
    --cc=agraf@suse.de \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox