Comment 1 Jürn Brodersen 2016-06-08 14:15:18 CEST

Created attachment 7725 [details]
console-server.log

Comment 2 Jürn Brodersen 2016-06-08 14:15:45 CEST

Created attachment 7726 [details]
console-web-server.log

Comment 3 Jürn Brodersen 2016-06-08 14:20:11 CEST

Created attachment 7727 [details]
error message

Comment 4 Jürn Brodersen 2016-06-08 14:22:42 CEST

Using the vmware image in qemu doesn't work either.

Comment 5 Jürn Brodersen 2016-06-08 14:23:29 CEST

(In reply to Jürn Brodersen from comment #0)
> The UCS installation wizard doesn't load if qemu is used for virtualization.
> The debian installer does work.
> 
> qemu-system-x -cdrom ~/Downloads/UCS-Installation-amd64.iso -boot order=d
> -drive file=ucs41.img

qemu-system-x -> qemu-system-x86_64

Comment 6 Philipp Hahn 2016-10-04 14:17:54 CEST

(In reply to Jürn Brodersen from comment #5)
> (In reply to Jürn Brodersen from comment #0)
> > The UCS installation wizard doesn't load if qemu is used for virtualization.
> > The debian installer does work.
> > 
> > qemu-system-x -cdrom ~/Downloads/UCS-Installation-amd64.iso -boot order=d
> > -drive file=ucs41.img
> 
> qemu-system-x -> qemu-system-x86_64

You MUST specify a network interface; at least one working interface is required for UCS. Otherwise UMC will fail as you've seen.

*** This bug has been marked as a duplicate of bug 36837 ***

Comment 7 Jürn Brodersen 2016-10-06 20:16:17 CEST

I looked into this again:
The network interface was not the problem, qemu does add one by default. But qemu does not use a hypervisor by default resulting in a really slow vm.

There is a timeout for loading modules (around 10s) and loading the setup modules just took to long, resulting in an error. I don't know where that timeout is set.

Using "-enable-kvm" solves the problem.

It would be nice to have a better error message for slow systems. Or maybe even some sort of system benchmark.

Comment 8 Jürn Brodersen 2016-10-07 09:26:11 CEST

Here is the error message in text form so that this bug is easier to find:
'''
 An error occurred

Internal server error: Could not connect to the module process.

Server error message:

Connection to module process failed
'''

Comment 9 Stefan Gohmann 2019-01-03 07:18:40 CET

This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.