From: Jason Long <hack3rcon@yahoo.com>
To: George Dunlap <dunlapg@umich.edu>, John Haxby <john.haxby@oracle.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Xen like VirtualBox
Date: Tue, 15 Nov 2016 14:05:59 +0000 (UTC) [thread overview]
Message-ID: <1344086623.181081.1479218759780@mail.yahoo.com> (raw)
In-Reply-To: <CAFLBxZaqs6u9rVQCm-NvOfJFRBCLzV43u4sxFcHxXih71JUzXQ@mail.gmail.com>
Thank you but I guess it is serious for Xen.
Are you Sure Red Hat company help Xen? I guess you wrong. Red Hat employee not mean Red Hat company and they can help other Open Source projects as hobbyist. I guess some Citrix guys help KVM as hobbyist too. When you read Virtualization books then all of them explain VirtualBox and VMWare Workstation but why not Xen? It is because of a GUI leak. In my opinion, Xen and Citrix guys must work on a nice interface for Xen and don't thinking about something like virt-manager or..
On Tuesday, November 15, 2016 5:28 PM, George Dunlap <dunlapg@umich.edu> wrote:
On Tue, Nov 15, 2016 at 11:54 AM, John Haxby <john.haxby@oracle.com> wrote:
> On 15/11/16 11:17, Jason Long wrote:
>> You said a Red Hat employee and this company like KVM not Xen.
>
> That makes no sense. You're denying what it says on the
> virt-manager.org web site as well as denying what it says in the
> description of the RPM. Even the Red Hat RPM for virt-manager says
> that it works with Xen (I'm looking at the RHEL6 source and it says
> "administering virtual machines for KVM, Xen, and QEmu").
>
> You can choose to avoid anything to do with Red Hat because of their
> preference of KVM over Xen, but, as the English saying goes, that's
> cutting your nose off to spite your face.
To corroborate this, two points:
First, RedHat generally do Open Source properly: They run projects
like virt-manager and libvirt as proper open-source communities, even
when their engineers are doing the lion's share of the work.
Obviously the RedHat engineers focus on functionality which is
important to RedHat. But it's been my consistent experience that
these projects accommodate work that people from the Xen community
put in. The libvirt guys don't actively develop Xen functionality for
libvirt, but if we submit patches they get constructive review, and if
someone else breaks existing Xen functionality they fix it.
Secondly, while Citrix doesn't use virt-manager for Xen, SuSE and
Oracle do (I believe).
If you know of bugs or deficiencies in virt-manager's Xen support,
then please do report them. But don't dismiss it out-of-hand simply
because RedHat are the main contributors.
-George
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-11-15 14:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <706778434.1491253.1478802016016.ref@mail.yahoo.com>
2016-11-10 18:20 ` Xen like VirtualBox Jason Long
2016-11-14 13:50 ` Dario Faggioli
2016-11-14 14:05 ` Jason Long
2016-11-14 18:40 ` Dario Faggioli
2016-11-15 6:01 ` Jason Long
2016-11-15 9:58 ` Paul Durrant
2016-11-15 11:16 ` Jason Long
2016-11-15 10:44 ` John Haxby
2016-11-15 11:17 ` Jason Long
2016-11-15 11:54 ` John Haxby
2016-11-15 13:58 ` George Dunlap
2016-11-15 14:05 ` Jason Long [this message]
2016-11-15 15:56 ` Cedric Bosdonnat
[not found] <277174510.2356321.1479417274189.ref@mail.yahoo.com>
2016-11-17 21:14 ` Jason Long
[not found] <1743265295.1503209.1478802011108.ref@mail.yahoo.com>
2016-11-10 18:20 ` Jason Long
[not found] <1367489592.1783564.1478542690773.ref@mail.yahoo.com>
2016-11-07 18:18 ` Jason Long
2016-11-07 18:28 ` Geza Gemes
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=1344086623.181081.1479218759780@mail.yahoo.com \
--to=hack3rcon@yahoo.com \
--cc=dunlapg@umich.edu \
--cc=john.haxby@oracle.com \
--cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).