Re: Trying to get poudriere to start

2017-07-30 Thread Willem Jan Withagen
On 30-7-2017 19:59, Chris Rees wrote:
> 
> 
> On 29 July 2017 20:01:42 BST, Willem Jan Withagen  wrote:
>>
>>
>> Op 29-7-2017 om 13:34 schreef Chris Rees:
>>>
>>>
>>> On 29 Jul 2017 11:56, Willem Jan Withagen  wrote:
>>>
>>>
>>>
>>> Op 28-7-2017 om 22:50 schreef Chris Rees:
>>>
>>>
>>>
>>> On 26 Jul 2017 23:59, Willem Jan Withagen 
>>>  wrote:
>>>
>>> Op 27-7-2017 om 00:48 schreef Miroslav Lachman:
>>> > Willem Jan Withagen wrote on 2017/07/26 23:24:
>>> >> Hi,
>>> >>
>>> >> This has been working, but now the jail does not even
>>> start
>>> >> Any suggestions why the linux module is giving me
>> trouble?
>>> >>
>>> >>  >  sudo poudriere bulk -vv -j ceph -p local net/ceph
>>> >> kldload: an error occurred while loading module linux.
>>> Please check
>>> >> dmesg(8) for more details.
>>> >> [00:00:00] >> Error: Required kernel module
>> 'linux'
>>> not found
>>> >>
>>> >> The parent system has linux stuff mounted in
>>> /compat/linux/proc
>>> >>
>>> >> Running 12-CURRENT.
>>> >
>>> > Did you tried "kldload linux" in host system? Will
>>> kldstat show you
>>> > loaded kernel module "linux"?
>>> >
>>> Right,
>>> I feel rather stupid... Because I do kknow how most of
>>> this works.
>>> So indeed this is all at the upper level:
>>>
>>> Looks like a incompatability
>>> link_elf_obj: symbol freebsd32_exec_copyin_args undefined
>>> linker_load_file: /boot/kernel/linux.ko - unsupported
>> file
>>> type
>>>
>>> But why
>>>
>>> [~] w...@freetest.digiware.nl
>>> > ls -asl
>>> /boot/kernel/*linux*
>>>   14 -r-xr-xr-x  1 root  wheel   13232 Jul 19 12:55
>>> /boot/kernel/amr_linux.ko*
>>>   47 -r-xr-xr-x  1 root  wheel   47480 Jul 19 12:55
>>> /boot/kernel/geom_linux_lvm.ko*
>>>   14 -r-xr-xr-x  1 root  wheel   13312 Jul 19 12:55
>>> /boot/kernel/ipmi_linux.ko*
>>> 771 -r-xr-xr-x  1 root  wheel  659248 Jul 19 12:55
>>> /boot/kernel/linux.ko*
>>> 643 -r-xr-xr-x  1 root  wheel  590328 Jul 19 12:55
>>> /boot/kernel/linux64.ko*
>>>   56 -r-xr-xr-x  1 root  wheel   55936 Jul 19 12:55
>>> /boot/kernel/linux_common.ko*
>>> 259 -r-xr-xr-x  1 root  wheel  186336 Jul 19 12:55
>>> /boot/kernel/linuxkpi.ko*
>>>   16 -r-xr-xr-x  1 root  wheel   15120 Jul 19 12:55
>>> /boot/kernel/mfi_linux.ko*
>>>   16 -r-xr-xr-x  1 root  wheel   15448 Jul 19 12:55
>>> /boot/kernel/mrsas_linux.ko*
>>> 102 -r-xr-xr-x  1 root  wheel  103416 Jul 19 12:55
>>> /boot/kernel/systrace_linux.ko*
>>> 112 -r-xr-xr-x  1 root  wheel  113416 Jul 19 12:55
>>> /boot/kernel/systrace_linux32.ko*
>>>
>>> [~] w...@freetest.digiware.nl
>>> > file
>> /boot/kernel/linux.ko
>>> /boot/kernel/linux.ko: ELF 64-bit LSB relocatable,
>> x86-64,
>>> version 1
>>> (FreeBSD), not stripped
>>>
>>> Are the jail and host the same version?
>>>
>>>
>>> Nope,
>>>
>>> But if I check the jail scripts, the modules are loaded outside
>> of
>>> the jail in the host.
>>> So I would expect that not to mater.
>>>
>>> --WjW
>>>
>>>
>>> Well, depends entirely on which modules are loaded!  Are you loading 
>>> host modules?
>>>
>>
>> This is the code I commented out:
>>
>> /usr/local/share/poudriere/common.sh: 1780
>> #   if [ -z "${NOLINUX}" ]; then
>> #   if [ "${arch}" = "i386" -o "${arch}" = "amd64" ]; then
>> #   needfs="${needfs} linprocfs"
>> #   needkld="${needkld} linuxelf:linux"
>> #   if [ "${arch}" = "amd64" ] && \
>> #   [ ${HOST_OSVERSION} -ge 1002507 ]; then
>> #   needkld="${needkld} linux64elf:linux64"
>> #   fi
>> #   fi
>> #   fi
>>
>> Which suggest that it is the host that is loading the modules.
>>
>> --WjW
> 
> Long shot, but it's worth a try... Have you rebooted since installing that 
> kernel 11 days ago?  If you were running an old kernel that'll give the 
> problem you're having.

Rebooting was the first thing I did when I could not get it to work.
The I checked that all components are of the same dat/time, and thus
from the same compilation run.

> Also, please 

Re: Trying to get poudriere to start

2017-07-30 Thread Chris Rees


On 29 July 2017 20:01:42 BST, Willem Jan Withagen  wrote:
>
>
>Op 29-7-2017 om 13:34 schreef Chris Rees:
>>
>>
>> On 29 Jul 2017 11:56, Willem Jan Withagen  wrote:
>>
>>
>>
>> Op 28-7-2017 om 22:50 schreef Chris Rees:
>>
>>
>>
>> On 26 Jul 2017 23:59, Willem Jan Withagen 
>>  wrote:
>>
>> Op 27-7-2017 om 00:48 schreef Miroslav Lachman:
>> > Willem Jan Withagen wrote on 2017/07/26 23:24:
>> >> Hi,
>> >>
>> >> This has been working, but now the jail does not even
>> start
>> >> Any suggestions why the linux module is giving me
>trouble?
>> >>
>> >>  >  sudo poudriere bulk -vv -j ceph -p local net/ceph
>> >> kldload: an error occurred while loading module linux.
>> Please check
>> >> dmesg(8) for more details.
>> >> [00:00:00] >> Error: Required kernel module
>'linux'
>> not found
>> >>
>> >> The parent system has linux stuff mounted in
>> /compat/linux/proc
>> >>
>> >> Running 12-CURRENT.
>> >
>> > Did you tried "kldload linux" in host system? Will
>> kldstat show you
>> > loaded kernel module "linux"?
>> >
>> Right,
>> I feel rather stupid... Because I do kknow how most of
>> this works.
>> So indeed this is all at the upper level:
>>
>> Looks like a incompatability
>> link_elf_obj: symbol freebsd32_exec_copyin_args undefined
>> linker_load_file: /boot/kernel/linux.ko - unsupported
>file
>> type
>>
>> But why
>>
>> [~] w...@freetest.digiware.nl
>> > ls -asl
>> /boot/kernel/*linux*
>>   14 -r-xr-xr-x  1 root  wheel   13232 Jul 19 12:55
>> /boot/kernel/amr_linux.ko*
>>   47 -r-xr-xr-x  1 root  wheel   47480 Jul 19 12:55
>> /boot/kernel/geom_linux_lvm.ko*
>>   14 -r-xr-xr-x  1 root  wheel   13312 Jul 19 12:55
>> /boot/kernel/ipmi_linux.ko*
>> 771 -r-xr-xr-x  1 root  wheel  659248 Jul 19 12:55
>> /boot/kernel/linux.ko*
>> 643 -r-xr-xr-x  1 root  wheel  590328 Jul 19 12:55
>> /boot/kernel/linux64.ko*
>>   56 -r-xr-xr-x  1 root  wheel   55936 Jul 19 12:55
>> /boot/kernel/linux_common.ko*
>> 259 -r-xr-xr-x  1 root  wheel  186336 Jul 19 12:55
>> /boot/kernel/linuxkpi.ko*
>>   16 -r-xr-xr-x  1 root  wheel   15120 Jul 19 12:55
>> /boot/kernel/mfi_linux.ko*
>>   16 -r-xr-xr-x  1 root  wheel   15448 Jul 19 12:55
>> /boot/kernel/mrsas_linux.ko*
>> 102 -r-xr-xr-x  1 root  wheel  103416 Jul 19 12:55
>> /boot/kernel/systrace_linux.ko*
>> 112 -r-xr-xr-x  1 root  wheel  113416 Jul 19 12:55
>> /boot/kernel/systrace_linux32.ko*
>>
>> [~] w...@freetest.digiware.nl
>> > file
>/boot/kernel/linux.ko
>> /boot/kernel/linux.ko: ELF 64-bit LSB relocatable,
>x86-64,
>> version 1
>> (FreeBSD), not stripped
>>
>> Are the jail and host the same version?
>>
>>
>> Nope,
>>
>> But if I check the jail scripts, the modules are loaded outside
>of
>> the jail in the host.
>> So I would expect that not to mater.
>>
>> --WjW
>>
>>
>> Well, depends entirely on which modules are loaded!  Are you loading 
>> host modules?
>>
>
>This is the code I commented out:
>
>/usr/local/share/poudriere/common.sh: 1780
>#   if [ -z "${NOLINUX}" ]; then
>#   if [ "${arch}" = "i386" -o "${arch}" = "amd64" ]; then
>#   needfs="${needfs} linprocfs"
>#   needkld="${needkld} linuxelf:linux"
>#   if [ "${arch}" = "amd64" ] && \
>#   [ ${HOST_OSVERSION} -ge 1002507 ]; then
>#   needkld="${needkld} linux64elf:linux64"
>#   fi
>#   fi
>#   fi
>
>Which suggest that it is the host that is loading the modules.
>
>--WjW

Long shot, but it's worth a try... Have you rebooted since installing that 
kernel 11 days ago?  If you were running an old kernel that'll give the problem 
you're having.

Also, please check that

# sysctl kern.bootfile

is somewhere in /boot/kernel. 

Chris
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
freebsd-ports@freebsd.org mailing list

Re: Trying to get poudriere to start

2017-07-29 Thread Willem Jan Withagen



Op 29-7-2017 om 13:34 schreef Chris Rees:



On 29 Jul 2017 11:56, Willem Jan Withagen  wrote:



Op 28-7-2017 om 22:50 schreef Chris Rees:



On 26 Jul 2017 23:59, Willem Jan Withagen 
 wrote:

Op 27-7-2017 om 00:48 schreef Miroslav Lachman:
> Willem Jan Withagen wrote on 2017/07/26 23:24:
>> Hi,
>>
>> This has been working, but now the jail does not even
start
>> Any suggestions why the linux module is giving me trouble?
>>
>>  >  sudo poudriere bulk -vv -j ceph -p local net/ceph
>> kldload: an error occurred while loading module linux.
Please check
>> dmesg(8) for more details.
>> [00:00:00] >> Error: Required kernel module 'linux'
not found
>>
>> The parent system has linux stuff mounted in
/compat/linux/proc
>>
>> Running 12-CURRENT.
>
> Did you tried "kldload linux" in host system? Will
kldstat show you
> loaded kernel module "linux"?
>
Right,
I feel rather stupid... Because I do kknow how most of
this works.
So indeed this is all at the upper level:

Looks like a incompatability
link_elf_obj: symbol freebsd32_exec_copyin_args undefined
linker_load_file: /boot/kernel/linux.ko - unsupported file
type

But why

[~] w...@freetest.digiware.nl
> ls -asl
/boot/kernel/*linux*
  14 -r-xr-xr-x  1 root  wheel   13232 Jul 19 12:55
/boot/kernel/amr_linux.ko*
  47 -r-xr-xr-x  1 root  wheel   47480 Jul 19 12:55
/boot/kernel/geom_linux_lvm.ko*
  14 -r-xr-xr-x  1 root  wheel   13312 Jul 19 12:55
/boot/kernel/ipmi_linux.ko*
771 -r-xr-xr-x  1 root  wheel  659248 Jul 19 12:55
/boot/kernel/linux.ko*
643 -r-xr-xr-x  1 root  wheel  590328 Jul 19 12:55
/boot/kernel/linux64.ko*
  56 -r-xr-xr-x  1 root  wheel   55936 Jul 19 12:55
/boot/kernel/linux_common.ko*
259 -r-xr-xr-x  1 root  wheel  186336 Jul 19 12:55
/boot/kernel/linuxkpi.ko*
  16 -r-xr-xr-x  1 root  wheel   15120 Jul 19 12:55
/boot/kernel/mfi_linux.ko*
  16 -r-xr-xr-x  1 root  wheel   15448 Jul 19 12:55
/boot/kernel/mrsas_linux.ko*
102 -r-xr-xr-x  1 root  wheel  103416 Jul 19 12:55
/boot/kernel/systrace_linux.ko*
112 -r-xr-xr-x  1 root  wheel  113416 Jul 19 12:55
/boot/kernel/systrace_linux32.ko*

[~] w...@freetest.digiware.nl
> file /boot/kernel/linux.ko
/boot/kernel/linux.ko: ELF 64-bit LSB relocatable, x86-64,
version 1
(FreeBSD), not stripped

Are the jail and host the same version?


Nope,

But if I check the jail scripts, the modules are loaded outside of
the jail in the host.
So I would expect that not to mater.

--WjW


Well, depends entirely on which modules are loaded!  Are you loading 
host modules?




This is the code I commented out:

/usr/local/share/poudriere/common.sh: 1780
#   if [ -z "${NOLINUX}" ]; then
#   if [ "${arch}" = "i386" -o "${arch}" = "amd64" ]; then
#   needfs="${needfs} linprocfs"
#   needkld="${needkld} linuxelf:linux"
#   if [ "${arch}" = "amd64" ] && \
#   [ ${HOST_OSVERSION} -ge 1002507 ]; then
#   needkld="${needkld} linux64elf:linux64"
#   fi
#   fi
#   fi

Which suggest that it is the host that is loading the modules.

--WjW
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: Trying to get poudriere to start

2017-07-29 Thread Chris Rees

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: Trying to get poudriere to start

2017-07-29 Thread Willem Jan Withagen



Op 28-7-2017 om 22:50 schreef Chris Rees:



On 26 Jul 2017 23:59, Willem Jan Withagen  wrote:

Op 27-7-2017 om 00:48 schreef Miroslav Lachman:
> Willem Jan Withagen wrote on 2017/07/26 23:24:
>> Hi,
>>
>> This has been working, but now the jail does not even start
>> Any suggestions why the linux module is giving me trouble?
>>
>>  >  sudo poudriere bulk -vv -j ceph -p local net/ceph
>> kldload: an error occurred while loading module linux. Please
check
>> dmesg(8) for more details.
>> [00:00:00] >> Error: Required kernel module 'linux' not found
>>
>> The parent system has linux stuff mounted in /compat/linux/proc
>>
>> Running 12-CURRENT.
>
> Did you tried "kldload linux" in host system? Will kldstat show you
> loaded kernel module "linux"?
>
Right,
I feel rather stupid... Because I do kknow how most of this works.
So indeed this is all at the upper level:

Looks like a incompatability
link_elf_obj: symbol freebsd32_exec_copyin_args undefined
linker_load_file: /boot/kernel/linux.ko - unsupported file type

But why

[~] w...@freetest.digiware.nl> ls -asl /boot/kernel/*linux*
  14 -r-xr-xr-x  1 root  wheel   13232 Jul 19 12:55
/boot/kernel/amr_linux.ko*
  47 -r-xr-xr-x  1 root  wheel   47480 Jul 19 12:55
/boot/kernel/geom_linux_lvm.ko*
  14 -r-xr-xr-x  1 root  wheel   13312 Jul 19 12:55
/boot/kernel/ipmi_linux.ko*
771 -r-xr-xr-x  1 root  wheel  659248 Jul 19 12:55
/boot/kernel/linux.ko*
643 -r-xr-xr-x  1 root  wheel  590328 Jul 19 12:55
/boot/kernel/linux64.ko*
  56 -r-xr-xr-x  1 root  wheel   55936 Jul 19 12:55
/boot/kernel/linux_common.ko*
259 -r-xr-xr-x  1 root  wheel  186336 Jul 19 12:55
/boot/kernel/linuxkpi.ko*
  16 -r-xr-xr-x  1 root  wheel   15120 Jul 19 12:55
/boot/kernel/mfi_linux.ko*
  16 -r-xr-xr-x  1 root  wheel   15448 Jul 19 12:55
/boot/kernel/mrsas_linux.ko*
102 -r-xr-xr-x  1 root  wheel  103416 Jul 19 12:55
/boot/kernel/systrace_linux.ko*
112 -r-xr-xr-x  1 root  wheel  113416 Jul 19 12:55
/boot/kernel/systrace_linux32.ko*

[~] w...@freetest.digiware.nl> file /boot/kernel/linux.ko
/boot/kernel/linux.ko: ELF 64-bit LSB relocatable, x86-64, version 1
(FreeBSD), not stripped

Are the jail and host the same version?


Nope,

But if I check the jail scripts, the modules are loaded outside of the 
jail in the host.

So I would expect that not to mater.

--WjW
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: Trying to get poudriere to start

2017-07-28 Thread Chris Rees

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: Trying to get poudriere to start

2017-07-28 Thread Willem Jan Withagen
On 28-7-2017 09:21, Shane Ambler wrote:
> On 27/07/2017 09:30, Willem Jan Withagen wrote:
>> On 27-7-2017 01:43, mokhi wrote:
>>> Aha,
>>> Okay...
>>> Good if it works :)
>>>
>>
>> It is a gross hack, but it gets me going for the time being.
>>
>> Also needed to fight with ninja.
>> Turns out that somebody changed my old port to include noninja, without
>> telling me... :(
> 
> That change would be related to r444324
> http://leader/viewvc/viewvc.cgi/FreeBSD-ports?view=revision=444324
> 
> Your port uses cmake, which previously would use make to build your
> port. The options to use ninja instead of make was an option but is now
> the default as speed improvements on larger projects were found. The
> addition of USES= cmake:noninja means your port failed using ninja
> during the tests of that change, which means it was left to build the
> same way it was before the change.

ninja complains about problems with $'s.
And since this project also needs to work with cmake/gmake on Linux, I'm
not even going to try to meddle with this.
Assuming that the current combo is going to stay workable?

--WjW

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: Trying to get poudriere to start

2017-07-28 Thread Shane Ambler

On 28/07/2017 16:51, Shane Ambler wrote:

On 27/07/2017 09:30, Willem Jan Withagen wrote:

On 27-7-2017 01:43, mokhi wrote:

Aha,
Okay...
Good if it works :)



It is a gross hack, but it gets me going for the time being.

Also needed to fight with ninja.
Turns out that somebody changed my old port to include noninja, without
telling me... :(


That change would be related to r444324
http://leader/viewvc/viewvc.cgi/FreeBSD-ports?view=revision=444324


Sorry, ignore that link, it should be
https://svnweb.freebsd.org/ports/head/Mk/Uses/cmake.mk?revision=444324=markup


Your port uses cmake, which previously would use make to build your
port. The options to use ninja instead of make was an option but is now
the default as speed improvements on larger projects were found. The
addition of USES= cmake:noninja means your port failed using ninja
during the tests of that change, which means it was left to build the
same way it was before the change.





--
FreeBSD - the place to B...Software Developing

Shane Ambler

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: Trying to get poudriere to start

2017-07-28 Thread Shane Ambler

On 27/07/2017 09:30, Willem Jan Withagen wrote:

On 27-7-2017 01:43, mokhi wrote:

Aha,
Okay...
Good if it works :)



It is a gross hack, but it gets me going for the time being.

Also needed to fight with ninja.
Turns out that somebody changed my old port to include noninja, without
telling me... :(


That change would be related to r444324
http://leader/viewvc/viewvc.cgi/FreeBSD-ports?view=revision=444324

Your port uses cmake, which previously would use make to build your
port. The options to use ninja instead of make was an option but is now
the default as speed improvements on larger projects were found. The
addition of USES= cmake:noninja means your port failed using ninja
during the tests of that change, which means it was left to build the
same way it was before the change.


--
FreeBSD - the place to B...Software Developing

Shane Ambler

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: Trying to get poudriere to start

2017-07-26 Thread Adam Weinberger
> On 26 Jul, 2017, at 17:23, Willem Jan Withagen  wrote:
> 
> Op 27-7-2017 om 01:15 schreef mokhi:
>> Hmm,
>> I don't know if it's same thing happened to me once.
>> But I **guess** you should kldload both of linux32 and linux64 and
>> also linprocfs modules
>> 
> 
> I did it the other way around.
> Hacked poudriere//common.sh
> And commented the kldoad for linux out...
> So I can atleast check this one port.

Setting NOLINUX=yes in poudriere.conf accomplishes the same thing.

# Adam


-- 
Adam Weinberger
ad...@adamw.org
https://www.adamw.org

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: Trying to get poudriere to start

2017-07-26 Thread Willem Jan Withagen
On 27-7-2017 01:43, mokhi wrote:
> Aha,
> Okay...
> Good if it works :)
> 

It is a gross hack, but it gets me going for the time being.

Also needed to fight with ninja.
Turns out that somebody changed my old port to include noninja, without
telling me... :(

Only when I actually started digging in my old poudriere  Makefile and
diffing it against what was in /usr/ports, it becaem clean.

But a new ceph-devel version is being tested.

--WjW
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: Trying to get poudriere to start

2017-07-26 Thread mokhi
Aha,
Okay...
Good if it works :)
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: Trying to get poudriere to start

2017-07-26 Thread Willem Jan Withagen

Op 27-7-2017 om 01:15 schreef mokhi:

Hmm,
I don't know if it's same thing happened to me once.
But I **guess** you should kldload both of linux32 and linux64 and
also linprocfs modules



I did it the other way around.
Hacked poudriere//common.sh
And commented the kldoad for linux out...
So I can atleast check this one port.

--WjW
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: Trying to get poudriere to start

2017-07-26 Thread mokhi
Hmm,
I don't know if it's same thing happened to me once.
But I **guess** you should kldload both of linux32 and linux64 and
also linprocfs modules

Regards,
MMokhi
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: Trying to get poudriere to start

2017-07-26 Thread Willem Jan Withagen

Op 27-7-2017 om 00:48 schreef Miroslav Lachman:

Willem Jan Withagen wrote on 2017/07/26 23:24:

Hi,

This has been working, but now the jail does not even start
Any suggestions why the linux module is giving me trouble?

 >  sudo poudriere bulk -vv -j ceph -p local net/ceph
kldload: an error occurred while loading module linux. Please check
dmesg(8) for more details.
[00:00:00] >> Error: Required kernel module 'linux' not found

The parent system has linux stuff mounted in /compat/linux/proc

Running 12-CURRENT.


Did you tried "kldload linux" in host system? Will kldstat show you 
loaded kernel module "linux"?



Right,
I feel rather stupid... Because I do kknow how most of this works.
So indeed this is all at the upper level:

Looks like a incompatability
link_elf_obj: symbol freebsd32_exec_copyin_args undefined
linker_load_file: /boot/kernel/linux.ko - unsupported file type

But why

[~] w...@freetest.digiware.nl> ls -asl /boot/kernel/*linux*
 14 -r-xr-xr-x  1 root  wheel   13232 Jul 19 12:55 
/boot/kernel/amr_linux.ko*
 47 -r-xr-xr-x  1 root  wheel   47480 Jul 19 12:55 
/boot/kernel/geom_linux_lvm.ko*
 14 -r-xr-xr-x  1 root  wheel   13312 Jul 19 12:55 
/boot/kernel/ipmi_linux.ko*

771 -r-xr-xr-x  1 root  wheel  659248 Jul 19 12:55 /boot/kernel/linux.ko*
643 -r-xr-xr-x  1 root  wheel  590328 Jul 19 12:55 /boot/kernel/linux64.ko*
 56 -r-xr-xr-x  1 root  wheel   55936 Jul 19 12:55 
/boot/kernel/linux_common.ko*

259 -r-xr-xr-x  1 root  wheel  186336 Jul 19 12:55 /boot/kernel/linuxkpi.ko*
 16 -r-xr-xr-x  1 root  wheel   15120 Jul 19 12:55 
/boot/kernel/mfi_linux.ko*
 16 -r-xr-xr-x  1 root  wheel   15448 Jul 19 12:55 
/boot/kernel/mrsas_linux.ko*
102 -r-xr-xr-x  1 root  wheel  103416 Jul 19 12:55 
/boot/kernel/systrace_linux.ko*
112 -r-xr-xr-x  1 root  wheel  113416 Jul 19 12:55 
/boot/kernel/systrace_linux32.ko*


[~] w...@freetest.digiware.nl> file /boot/kernel/linux.ko
/boot/kernel/linux.ko: ELF 64-bit LSB relocatable, x86-64, version 1 
(FreeBSD), not stripped




___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: Trying to get poudriere to start

2017-07-26 Thread Miroslav Lachman

Willem Jan Withagen wrote on 2017/07/26 23:24:

Hi,

This has been working, but now the jail does not even start
Any suggestions why the linux module is giving me trouble?

 >  sudo poudriere bulk -vv -j ceph -p local net/ceph
kldload: an error occurred while loading module linux. Please check
dmesg(8) for more details.
[00:00:00] >> Error: Required kernel module 'linux' not found

The parent system has linux stuff mounted in /compat/linux/proc

Running 12-CURRENT.


Did you tried "kldload linux" in host system? Will kldstat show you 
loaded kernel module "linux"?


Miroslav Lachman

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"