<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt">
<div>Just for clarification sake, Xen is now part of the Linux Foundation and XenServer itself is open source as well.</div>
<div><br>
</div>
<div>Pretty much all of the bits to generate the XenServer build and all development of the Citrix product are done on Github now.</div>
<div><br>
</div>
<div>I get the push to use KVM but given the amount of interest and use there was on CentOS 6 with Xen, I believe the effort will still be made to get it into CentOS 7, which is why it would be nice if it was upstream as well.</div>
</div>
<div id="x_quoted_header"><br>
<div style="border:none; border-top:solid #E1E1E1 1.0pt; padding:3.0pt 0cm 0cm 0cm">
<span style="font-size:11.0pt; font-family:'Calibri','sans-serif'"><b>From:</b> Nico Kadel-Garcia <nkadel@gmail.com><br>
<b>Sent:</b> May 25, 2014 8:58 AM<br>
<b>To:</b> Discussion about the virtualization on CentOS<br>
<b>Subject:</b> Re: [CentOS-virt] Xen DomU supoprt in RHEL 7 and the CentOS Plan<br>
</span></div>
</div>
<br type="attribution">
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">On Fri, May 23, 2014 at 10:59 AM, Major Hayden <major@mhtx.net> wrote:<br>
> On May 23, 2014, at 9:13, Simon Rowe <simon.rowe@eu.citrix.com> wrote:<br>
><br>
>> Why do you say that? My minimal testing of the rc doesn't show any<br>
>> problems installing on Xen 4.4<br>
><br>
> I had the same results as Simon.<br>
><br>
> Running RHEL7rc as a domU on a machine running a Fedora-based Xen hypervisor works fine.<br>
><br>
> However, there is no Xen *dom0* support in RHEL7rc. There are no tools either. Last time I checked, Xen support wasn't evenincluded with libvirt on RHEL7rc. :/<br>
<br>
Given Red Hat's focus on and direct freeware support of KVM, why<br>
should they burn cycles on open source integration of a product that<br>
has a closed source upstream vendor at Citrix? They'd be much better<br>
off spending the engineering time on libvirt and getting the<br>
NetworkManager configuration tools to correctly support KVM compatible<br>
bridging or ordinary network pair bonding, jumbo frames, and VLAN<br>
tagging. None of that was working correctly on CentOS 6 or RHEL 6<br>
without hand editing config files, which would be overwritten and<br>
scrambled by using NetworkManager to configure anything. I've not<br>
spent time with the latest NetworkManager on the RHEL 7 betas, and<br>
would be very curious to see if they've gotten *that* straightened<br>
out.<br>
<br>
In Red Hat's position, I'd contact Citrix and get *them* to do the<br>
testing and debugging, which they'll need to do for their commercial<br>
products, anyway. That might get into interesting open source<br>
licensing issues, but it's a lot cheaper than replicating testing labs<br>
and doing Citrix's work for them.<br>
_______________________________________________<br>
CentOS-virt mailing list<br>
CentOS-virt@centos.org<br>
<a href="http://lists.centos.org/mailman/listinfo/centos-virt">http://lists.centos.org/mailman/listinfo/centos-virt</a><br>
</div>
</span></font>
</body>
</html>