On Thu, 14 Dec 2017 11:24:27 +0100
Viktor Mihajlovski wrote:
> On 10.12.2017 10:10, Barak Korren wrote:
> [...]
> >
> > An update for everyone woh may have been watching this thread - we
> > made it work.
> What a nice surprise after returning from a few days off. Big thanks
> to both of you, Ba
On 14 December 2017 at 12:34, Dan Horák wrote:
> On Thu, 14 Dec 2017 11:24:27 +0100
> Viktor Mihajlovski wrote:
>
>> On 10.12.2017 10:10, Barak Korren wrote:
>> [...]
>> >
>> > An update for everyone woh may have been watching this thread - we
>> > made it work.
>> What a nice surprise after retu
On 10.12.2017 12:58, Fred Rolland wrote:
> I am getting some error logs when the engine starts looking for s390 icons.
> Nothing critical, but add noise
>
> 2017-12-10 13:51:01,987+02 WARN [org.ovirt.engine.core.bll.IconLoader]
> (ServerService Thread Pool -- 53) [] java.lang.RuntimeException
On 14.12.2017 11:34, Dan Horák wrote:
> On Thu, 14 Dec 2017 11:24:27 +0100
[...]
>> Lately, I've been using Fedora 27 for the s390x porting, mostly
>> because the newer package levels of the key virtualization
>> components. If possible, Fedora 27 would be nice.
>
> The Marist College agrees to pr
On 10.12.2017 10:10, Barak Korren wrote:
[...]
>
> An update for everyone woh may have been watching this thread - we made it
> work.
What a nice surprise after returning from a few days off. Big thanks to
both of you, Barak and Dan.
>
> With Dan's kind help we've attached an s390x VM to oVirt's
I am getting some error logs when the engine starts looking for s390 icons.
Nothing critical, but add noise
2017-12-10 13:51:01,987+02 WARN [org.ovirt.engine.core.bll.IconLoader]
(ServerService Thread Pool -- 53) [] java.lang.RuntimeException: Icon for
other_s390x was not found in
/home/froll
On 10 December 2017 at 13:38, Greg Sheremeta wrote:
>
>
> Great job all! So I guess the question is, for those of us that maintain
> oVirt projects, are there any that we know need s390x support added for?
>
>
Well, Viktor Mihajlovski had been contributing patches to VDSM et el. to
enable making
On Sun, Dec 10, 2017 at 4:10 AM, Barak Korren wrote:
> On 24 November 2017 at 14:36, Dan Horák wrote:
> > On Fri, 24 Nov 2017 13:16:53 +0200
> > Barak Korren wrote:
> >
> >> On 24 November 2017 at 11:05, Viktor Mihajlovski
> >> wrote:
> >> > On 21.11.2017 11:26, Dan Horák wrote:
> >> > [...]
>
On 24 November 2017 at 14:36, Dan Horák wrote:
> On Fri, 24 Nov 2017 13:16:53 +0200
> Barak Korren wrote:
>
>> On 24 November 2017 at 11:05, Viktor Mihajlovski
>> wrote:
>> > On 21.11.2017 11:26, Dan Horák wrote:
>> > [...]
>> >>> qemu s390x emulation does not work with code compiled for z12.
>>
On 24 November 2017 at 14:36, Dan Horák wrote:
>
> ok, I'm pretty sure we can make it work :-) Please send me your
> public SSH key and preferred username, then I'll set up you an account
> for you and we can work on the remaining details.
>
I would actually like two keys to be configured, one fo
sending once more for the s390x list ...
On Fri, 24 Nov 2017 10:05:06 +0100
Viktor Mihajlovski wrote:
> On 21.11.2017 11:26, Dan Horák wrote:
> [...]
> >> qemu s390x emulation does not work with code compiled for z12.
> >> Would a real virtual machine be what you need?
> >> The Fedora team DOES
On Fri, 24 Nov 2017 13:16:53 +0200
Barak Korren wrote:
> On 24 November 2017 at 11:05, Viktor Mihajlovski
> wrote:
> > On 21.11.2017 11:26, Dan Horák wrote:
> > [...]
> >>> qemu s390x emulation does not work with code compiled for z12.
> >>> Would a real virtual machine be what you need?
> >>> T
On 24 November 2017 at 11:05, Viktor Mihajlovski
wrote:
> On 21.11.2017 11:26, Dan Horák wrote:
> [...]
>>> qemu s390x emulation does not work with code compiled for z12.
>>> Would a real virtual machine be what you need?
>>> The Fedora team DOES have access to a z13. Not sure how much
>>> resourc
On Fri, 24 Nov 2017 10:05:06 +0100
Viktor Mihajlovski wrote:
> On 21.11.2017 11:26, Dan Horák wrote:
> [...]
> >> qemu s390x emulation does not work with code compiled for z12.
> >> Would a real virtual machine be what you need?
> >> The Fedora team DOES have access to a z13. Not sure how much
>
On 21.11.2017 11:26, Dan Horák wrote:
[...]
>> qemu s390x emulation does not work with code compiled for z12.
>> Would a real virtual machine be what you need?
>> The Fedora team DOES have access to a z13. Not sure how much
>> resources are available, but can you contact Dan Horak (on cc) if
>> the
On Mon, 20 Nov 2017 09:24:00 +0100
Martin Sivak wrote:
> Dan Horak used to be part of this project. Lets see if he still
> remembers that.
>
> Dan: Can you please tell us how the s390 builds in Fedora are/were
> done when no hw was available?
AFAIK Fedora was always building its packages on rea
On Mon, 20 Nov 2017 09:16:48 +0100
Christian Borntraeger wrote:
>
>
> On 11/19/2017 09:53 AM, Barak Korren wrote:
> > On 18 November 2017 at 13:14, Barak Korren
> > wrote:
> >> On 16 November 2017 at 19:38, Martin Sivak
> >> wrote:
> Koji is very opinionated about how RPMs and specfiles
On 11/19/2017 09:53 AM, Barak Korren wrote:
> On 18 November 2017 at 13:14, Barak Korren wrote:
>> On 16 November 2017 at 19:38, Martin Sivak wrote:
Koji is very opinionated about how RPMs and specfiles should look,
AFAIK
>>>
>>> Actually, koji does not care much. Fedora packaging rul
Dan Horak used to be part of this project. Lets see if he still remembers that.
Dan: Can you please tell us how the s390 builds in Fedora are/were
done when no hw was available?
Martin Sivak
On Sat, Nov 18, 2017 at 12:14 PM, Barak Korren wrote:
> On 16 November 2017 at 19:38, Martin Sivak wrot
On Fri, Nov 17, 2017 at 8:45 AM, Viktor Mihajlovski
wrote:
> On 16.11.2017 18:27, Barak Korren wrote:
>> On 16 November 2017 at 18:52, Viktor Mihajlovski
>> wrote:
>>>
>>> Short update, with yesterday's API model 4.2.25 release, there's basic
>>> support for s390 available in ovirt-engine. At thi
On Fri, 17 Nov 2017, Peter Robinson wrote:
> We don't currently have s390x EPEL
ummm -- I think Peter is suggesting EPEL executables -- this
is a solved problem
The ClefOS s390x distribution has all of RHEL 6, RHEL 7, EPEL
6, EPEL 7, and more in s390x, and has had for years. Neale
Ferguson (S
On 18 November 2017 at 13:14, Barak Korren wrote:
> On 16 November 2017 at 19:38, Martin Sivak wrote:
>>> Koji is very opinionated about how RPMs and specfiles should look,
>>> AFAIK
>>
>> Actually, koji does not care much. Fedora packaging rules are enforced
>> by package reviewers.
>>
>>> More
On 16 November 2017 at 19:38, Martin Sivak wrote:
>> Koji is very opinionated about how RPMs and specfiles should look,
>> AFAIK
>
> Actually, koji does not care much. Fedora packaging rules are enforced
> by package reviewers.
>
>> More specifically, Koji usually assumes the starting point for th
On 17 November 2017 at 10:45, Viktor Mihajlovski
wrote:
> On 16.11.2017 18:27, Barak Korren wrote:
>> On 16 November 2017 at 18:52, Viktor Mihajlovski
>> wrote:
>>>
>>> Short update, with yesterday's API model 4.2.25 release, there's basic
>>> support for s390 available in ovirt-engine. At this p
On 16.11.2017 18:27, Barak Korren wrote:
> On 16 November 2017 at 18:52, Viktor Mihajlovski
> wrote:
>>
>> Short update, with yesterday's API model 4.2.25 release, there's basic
>> support for s390 available in ovirt-engine. At this point in time, there
>> are no ovirt yum repositories for the s39
> Koji is very opinionated about how RPMs and specfiles should look,
> AFAIK
Actually, koji does not care much. Fedora packaging rules are enforced
by package reviewers.
> More specifically, Koji usually assumes the starting point for the
> build process would be a specfile
This is correct thoug
On 16 November 2017 at 18:52, Viktor Mihajlovski
wrote:
>
> Short update, with yesterday's API model 4.2.25 release, there's basic
> support for s390 available in ovirt-engine. At this point in time, there
> are no ovirt yum repositories for the s390x architecture - not sure what
> the process wou
On 18.09.2017 09:30, Viktor Mihajlovski wrote:
> Hi,
>
> as a heads up: I'd like to contribute some basic support for the s390
> architecture to oVirt. For that purpose I'll post some patches to
> gerrit, mostly for the following repositories: VDSM,
> ovirt-engine-api-model and ovirt-engine. There
On 18.09.2017 10:36, Barak Korren wrote:
> On 18 September 2017 at 10:30, Viktor Mihajlovski
> wrote:
>> Hi,
>>
>> as a heads up: I'd like to contribute some basic support for the s390
>> architecture to oVirt. For that purpose I'll post some patches to
>> gerrit, mostly for the following reposito
On 18 September 2017 at 10:30, Viktor Mihajlovski
wrote:
> Hi,
>
> as a heads up: I'd like to contribute some basic support for the s390
> architecture to oVirt. For that purpose I'll post some patches to
> gerrit, mostly for the following repositories: VDSM,
> ovirt-engine-api-model and ovirt-eng
Hi,
as a heads up: I'd like to contribute some basic support for the s390
architecture to oVirt. For that purpose I'll post some patches to
gerrit, mostly for the following repositories: VDSM,
ovirt-engine-api-model and ovirt-engine. There might be some collateral
patches that need to go into ovir
31 matches
Mail list logo