From: jmerkey@wolfmountaingroup.com
To: "Morten P.D. Stevens" <mstevens@win-professional.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"jmerkey@wolfmountaingroup.com" <jmerkey@wolfmountaingroup.com>
Subject: RE: Xen vs. KVM
Date: Wed, 17 Jun 2009 20:25:09 -0600 (MDT) [thread overview]
Message-ID: <59150.166.70.238.43.1245291909.squirrel@webmail.wolfmountaingroup.com> (raw)
In-Reply-To: <520B2A28AACEE94388C511BBB8349337078B4889D6@IGR-IMC-01.corp.win-profes sional.com>
> 2009/6/15 <jmerkey@wolfmountaingroup.com>
>
>> I have worked with both KVM and XEN and to be honest, XEN is infested
>> with
>> bugs -- mostly of the paging type -- and you need an logic analyzer of
>> an
>> ICE to debug some of it. I have nothing but trouble with it. KVM is
>> more
>> stable but also sucks on performance, but I occasionally see the same
>> issues.
>
> This is bullshit.
>
> KVM is buggy und very unstable. It´s NOT RECOMMENDED for production usage.
>
> Xen is fully developed, fast and more reliable than KVM.
> Thousands of companies are using Xen or Citrix XenServer and its super
> fast, easy to use and 100% rockstable!
> The XEN PV Guest drivers are excellent in comparison with the KVM windows
> guest drivers. (after installing the 64 bit networking drivers with Server
> 2008 x64 > blue screen...).. I hate kvm.
>
> @ Linus : Please merge xen as hypervisor into linux, right now !
>
> -
>
> Morten
>
They are both buggy. but Xen is BUGGIER.
Before you call bullshit try eating your own dogfood. I threw both of
these pieces of shit away in the trash and went back to VMWare, which is
slower than crap, but it least it fucking works.
Jeff
next prev parent reply other threads:[~2009-06-18 3:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 3:33 jmerkey
2009-06-17 23:51 ` Morten P.D. Stevens
[not found] ` <520B2A28AACEE94388C511BBB8349337078B4889D6@IGR-IMC-01.corp.win-profes sional.com>
2009-06-18 2:25 ` jmerkey [this message]
2009-06-19 11:52 ` Morten P.D. Stevens
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=59150.166.70.238.43.1245291909.squirrel@webmail.wolfmountaingroup.com \
--to=jmerkey@wolfmountaingroup.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mstevens@win-professional.com \
/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
all inboxes | Powered by JetHome®