From: Benjamin Schweikert <b.schweikert@googlemail.com>
To: development@lists.ipfire.org
Subject: No Xen development for 3.x any more
Date: Thu, 07 Feb 2013 21:24:58 +0100 [thread overview]
Message-ID: <2C4D46C9-C1C4-4AFE-9A01-41FDB6527260@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 641 bytes --]
Hi,
after thinking a lot about continuing xen as a hypervisor for ipfire 3.x (and after having talked to micha) I decided to not maintain Xen Hypervisor and Xen Userspace tools any more for now.
The reasons for this are:
- I will switch from xen to kvm with my systems and so I will not spend a lot of time reading xen mailing lists
- The Xen-Sourcecode is not really well "written" and documented
- This leads to a big effort in looking for patches because of the hardened system
- libvirt is not supported yet
- and finally: I don't have the time to spend several evenings bug fixing after each new released xen version.
Ben
next reply other threads:[~2013-02-07 20:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 20:24 Benjamin Schweikert [this message]
2013-02-08 4:22 ` R. W. Rodolico
2013-02-08 7:52 ` Benjamin Schweikert
2013-02-08 8:04 ` Aw: " Jochen Rupp
2013-02-08 9:03 ` Arne Fitzenreiter
2013-02-08 9:55 ` Michael Tremer
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=2C4D46C9-C1C4-4AFE-9A01-41FDB6527260@gmail.com \
--to=b.schweikert@googlemail.com \
--cc=development@lists.ipfire.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