From: Avi Kivity <avi@redhat.com>
To: Manfred_Knick <Manfred.Knick@T-Online.de>
Cc: kvm@vger.kernel.org
Subject: Re: KVM and VMware
Date: Wed, 25 Feb 2009 18:03:29 +0200 [thread overview]
Message-ID: <49A56BD1.3080003@redhat.com> (raw)
In-Reply-To: <49A557AE.1010206@T-Online.de>
Manfred_Knick wrote:
>>> B) Any chance to solve this problem?
>>>
>> 'rmmod kvm-intel; rmmod kvm' should work.
>>
>
> Avi,
> thanks a lot for your _very_ speedy response!!
>
> So I take it that
> --> "You can't have them both at once, at the same time"
> which turns out to be really unfortunate for my tasks.
>
> ERGO: what I'm going to try is:
>
> o) delete all static kvm stuff in the kernel .config / rebuild / reboot
> o) un-merge app-emulation/kvm-84 "without modules"
> o) emerge vmware-workstation
> o) emerge app-emulation/kvm-84 "with modules"
> o) don't auto-load kvm and kvm-[intel|amd]
> o) !! EITHER start vmware
> o) !! OR load / start KVM,
> o) !! thus manually avoiding those threatening kernel lockups.
>
>
>
Looks right -- does "without modules" mean kvm is built-in into the kernel?
> Are there any plans @ KVM to change the (*) behavior in the future,
> e.g. switching in and out of root mode each time
> so as to not conflict with other virtualization software?
>
No, running multiple virtual machine monitors is a very esoteric use
case and is therefore not worth the performance hit.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-02-25 16:03 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 [this message]
2009-02-26 9:25 ` Alexander Graf
2009-02-26 11:34 ` Manfred_Knick
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=49A56BD1.3080003@redhat.com \
--to=avi@redhat.com \
--cc=Manfred.Knick@T-Online.de \
--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