Re: [Devil-Linux-discuss] devil-linux-1.8.0-2015-12-21 uploaded

[Heiko Z. <he...@zu...>]

  Udo,

It seems that it doesn't like something related to grsecurity.
You could try and setting everything to 0 in
/etc/sysconfig/grsecurity.proc. The settings get applied at the end of the
boot process. This way we could at least attempt to track down what's
affecting it during runtime.

Heiko

Quoting Udo Lembke <udo...@al...>:

> Hi,
> tested devil-linux-1.8.0-2016-01-03-i686 on pve4.1 (host running kernel:
> 4.2.3-2-pve).
> The devil-linux VM start, but is extremly slowly - use 100%cpu and need
> app. 3 hours to boot with 1 CPU and automatic config upgrade.
>
> After boot the load is > 1 but in top is mostly all idle... shutdown
> takes also a long time.
>
> After that (with config-save for 1.8.0-2016-01-03) I added one more CPU
> and the boot proccess takes 9 min. "only".
>
> With dl-1.8.0-2016-01-03-x86_64-server boot the same VM in 27sec with
> automatic config update...
>
> How to dig where the issue is?
>
> BTW: config on virtio-devices work on pve4 (qemu 2.4) also!
>
> Udo
>
>   On 03.01.2016 19:41, Udo Lembke wrote:
>
>> Hi Heiko,
>> Thanks!! Work like a charm (bareos and virtio with config-data - tested
>> on pve3.4 only; on pve4 I will do the test tomorrow).
>>
>> One strange fact: Since >devil-linux 1.8.0 2015-12-04 the VMs don't
>> start on an 3.10 host-kernel!
>> They hang with 100% cpu.
>>
>> Last output is "Starting up final system...", or sometimes three
>> further Lines:
>> Changed Root
>> Populating /var
>> cp: preserving times for '/shm/var/adm/boot': Read-only file system
>>
>> Strange is, that the same VM run on the same proxmox ve version but
>> with an 2.6.32-kernel on the host.
>> And this only happens with the i686-system. The amd64-server-system
>> work well...
>> Will test, which happens on pve4 (kernel 4.x) tomorrow.
>>
>> Udo
>>
>>    On 03.01.2016 15:15, Heiko Zuerker wrote:
>>
>>> Udo,
>>>
>>> Bacula has now been replaced with Bareos on DL, so you should be good
>>> to go.
>>>
>>> Heiko
>>>
>>> Quoting Heiko Zuerker <he...@zu...>:
--

Regards
  Heiko Zuerker