All of lore.kernel.org
 help / color / mirror / Atom feed
From: Igor Kozhukhov <igor@dilos.org>
To: "Jürgen Groß" <jgross@suse.com>
Cc: "Pasi Kärkkäinen" <pasik@iki.fi>,
	xen-devel <xen-devel@lists.xenproject.org>,
	"Boris Ostrovsky" <boris.ostrovsky@oracle.com>,
	"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>
Subject: Re: [Xen-devel] Xen Solaris support still required? Illumos/Dilos Xen
Date: Fri, 2 Oct 2020 13:08:43 +0300	[thread overview]
Message-ID: <01D5E481-0221-440F-865C-F362F344295C@dilos.org> (raw)
In-Reply-To: <746d05db-cbe0-4013-41fb-a4a5b9b71d5c@suse.com>

[-- Attachment #1: Type: text/plain, Size: 2577 bytes --]

Hi All,

sorry for long delay with XEN.

we have plans with Xen support on DilOS.
i have made some changes on dilos-illumos side for it.
but we have some priority to OpenZFS updates and XEN support will be a little bit later.

we have plans for XEN on 2021 year, but all depends on business needs and investments.

best regards,
-Igor

> On 2 Oct 2020, at 12:53, Jürgen Groß <jgross@suse.com> wrote:
> 
> On 05.12.16 06:32, Juergen Gross wrote:
>> On 04/12/16 18:11, Igor Kozhukhov wrote:
>>> Hi Pasi,
>>> 
>>> i’m using both addresses, but probably @gmale missed some emails with
>>> maillist.
>>> 
>>> About DilOS + Xen.
>>> 
>>> i’m using xen-3.4 - old version what i backported to DilOS based on old
>>> opensolaris varsion and upadted it to use python2.7 and some others zfs
>>> updates - more updates :)
>>> i tried to port Xen-4.3, but not finished it yet because i have no found
>>> sponsors and i have been moved to some aonther job without DilOS/illumos
>>> activities.
>>> try to do it by free time was/is overhead.
>>> 
>>> i have plans try to return back and look at latest Xen.
>>> 
>>> right now i try to move DilOS bulid env to use more Debian style build
>>> env and to use gcc-5.4 as primary compiler.
>>> Also, i have SPARC support with DilOS and it eat some additional free time.
>>> please do not drop solaris support :) - i’ll use and update it soon -
>>> probably on next year.
>> Got it. Thanks for the note and good luck for the port!
> 
> As a followup after nearly 4 years:
> 
> It seems nothing has happened, and Solaris specific coding in Xen is
> bit-rotting further. Last example is xenstored, which lost an interface
> mandatory for Solaris about 1 year ago (nobody noticed, as Solaris
> specific parts are neither built nor tested).
> 
> I stumbled over this one as I did some reorg of the Xen libraries and
> checked all the dependencies between those.
> 
> I think at least the no longer working Solaris stuff in xenstored should
> be removed now (in theory it would still be possible to use xenstore-
> stubdom in Solaris), but I honestly think all the other Solaris cruft in
> Xen tools should go away, too, in case nobody is really showing some
> interest in it (e.g. by doing some basic build tests and maybe a small
> functional test for each release of Xen).
> 
> So how does the realistic future of a Solaris dom0 look like? Is there
> a non-neglectable chance it will be revived in the near future, or can
> we remove the Solaris abstractions?
> 
> 
> Juergen


[-- Attachment #2: Type: text/html, Size: 18730 bytes --]

      reply	other threads:[~2020-10-02 10:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-03 12:49 Xen Solaris support still required? Juergen Gross
2016-11-03 13:56 ` Xen Solaris support still required? Illumos Xen Pasi Kärkkäinen
2016-12-04 16:57   ` Xen Solaris support still required? Illumos/Dilos Xen Pasi Kärkkäinen
2016-12-04 17:11     ` Igor Kozhukhov
2016-12-05  5:32       ` Juergen Gross
2020-10-02  9:53         ` Re: [Xen-devel] " Jürgen Groß
2020-10-02 10:08           ` Igor Kozhukhov [this message]

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=01D5E481-0221-440F-865C-F362F344295C@dilos.org \
    --to=igor@dilos.org \
    --cc=boris.ostrovsky@oracle.com \
    --cc=jgross@suse.com \
    --cc=konrad.wilk@oracle.com \
    --cc=pasik@iki.fi \
    --cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.