From: Jochen Rupp <jochen_rupp@web.de>
To: development@lists.ipfire.org
Subject: Aw: Re: No Xen development for 3.x any more
Date: Fri, 08 Feb 2013 09:04:08 +0100 [thread overview]
Message-ID: <trinity-60a56e15-0d44-4f40-89f9-fd98088d2852-1360310648326@3capp-webde-bs42> (raw)
In-Reply-To: <assp.07515115e6.51147D91.2010301@dailydata.net>
[-- Attachment #1: Type: text/plain, Size: 2094 bytes --]
Support for VMWare (ESXi) would be great. I assume you could install IPFire as VM there but are the VMWare-Tools available?
Cheers,
Jochen
--
WorldCommunityGrid.org: Gemeinsam für eine gute Sache!
Hilf mit, spende Deine ungenutzte PC-Rechenzeit!
Infos unter: http://www.worldcommunitygrid.org/
> Gesendet: Freitag, 08. Februar 2013 um 05:22 Uhr
> Von: "R. W. Rodolico" <rodo(a)dailydata.net>
> An: development(a)lists.ipfire.org
> Betreff: Re: No Xen development for 3.x any more
>
> I currently use ipFire under Xen, but this sounds like a whole lot of
> work just for one or two Xen machines. I'm assuming it can simply be
> installed by booting an HVM from the ISO? If not (if there would be
> security holes by doing it), I can simply change to a stand alone.
>
> Thank you very much for all the hard work.
>
> Rod
>
> On 02/07/2013 02:24 PM, Benjamin Schweikert wrote:
> > 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
> > _______________________________________________
> > Development mailing list
> > Development(a)lists.ipfire.org
> > http://lists.ipfire.org/mailman/listinfo/development
> >
>
> --
> R. W. "Rod" Rodolico
> Daily Data, Inc.
> POB 140465
> Dallas TX 75214-0465
> http://www.dailydata.net
> 214.827.2170
>
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development
>
next prev parent reply other threads:[~2013-02-08 8:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 20:24 Benjamin Schweikert
2013-02-08 4:22 ` R. W. Rodolico
2013-02-08 7:52 ` Benjamin Schweikert
2013-02-08 8:04 ` Jochen Rupp [this message]
2013-02-08 9:03 ` Aw: " 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=trinity-60a56e15-0d44-4f40-89f9-fd98088d2852-1360310648326@3capp-webde-bs42 \
--to=jochen_rupp@web.de \
--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