-----Original Message-----
From: Jim Fehlig <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: Re: [opensuse-virtual] future of XEN (within SuSE)
Date: Tue, 11 Jun 2013 08:25:08 -0600

Hans Witvliet wrote:
> Hi all,
>
> It could be just my perception, but i've got the feeling that more and
> more attention is given to KVM, and i wonder if this is intentionally?
>
> For instance, on http://doc.opensuse.org/ it is about "Virtualization
> with KVM" in htmp, pdf and epub, while not a single word about XEN or
> LXC... Intentionally?
>   

I don't think it is intentional.  AFAIK, the docs come from the SLE
docs, and seems no one has added the Xen ones to doc.opensuse.org

https://www.suse.com/documentation/sles11/book_xen/?page=/documentation/sles11/book_xen/data/book_xen.html

> I got quite some paravirtualized servers, this is seriously worrying me.
> And as a long term XEN user, should i start looking for an alternative
> distro in case SuSE is going to drop XEN?
>   

There are no plans to drop Xen support.  SUSE is one of the largest
contributors upstream (2nd in upcoming Xen 4.3 [1] release) and we will
continue to provide Xen packages in the future.  openSUSE13.1 will have
Xen 4.3.x, where the new xl/libxl toolstack will be default and xm/xend
is deprecated.  Work continues on the Xen front within SUSE...

Regards,
Jim

[1] http://wiki.xen.org/wiki/Xen_4.3_Acknowledgements


-----Original Message-----

Thanks Jim, for re-assuring. Big sigh of relief.

Yeah i know that SuSE has been a mayor player in the XEN area:
I was told that "other" distro's have been using your patches for many
years, until they decide to switch completely to KVM.

Further down the thread, it is mentioned about the suse-specific kernel
patches. Is that still the case since XEN became part of main-stream
kernel? 
Excuse me my ignorance, since i only used openSUSE or SLES for dom0 and
mostly for domU, and only used distro-supplied kernels.


Hans


--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]

Reply via email to