Yes kvm works way better with virualization support ! ;-) I really thought I did turn it on while inspecting the bios prior to install !!!

Any way moving forward to new installation problem in spack :

first , I completely missed the softadm password ( I got the one for demo) . I was giving all the same password each time I got a request to give one . I guess this one was generated like the demo account but I completely missed it. Not a big deal , try to change it under root in fe but was not allowed. Use QluMan/ldap for that. was able to ssh softadm@jclustert (my fe hostname) to initialize the stack.

Here is the error message when trying to initialize the stack using the "spack install gcc@13.1.0 target=x86_64" command

No patches needed for gmake
==> gmake: Executing phase: 'autoreconf'
==> gmake: Executing phase: 'configure'
==> gmake: Executing phase: 'build'
==> gmake: Executing phase: 'install'
==> gmake: Successfully installed gmake-4.4.1-d3ghmecmrwxdzizqkb2vfxixc4a7xyu4
Stage: 2.72s. Autoreconf: 0.00s. Configure: 15.33s. Build: 9.31s. Install: 0.03s. Post-install: 0.07s. Total: 27.71s
[+] /usr/share/spack/root/opt/spack/linux-ubuntu22.04-x86_64/gcc-11.4.0/gmake-4.4.1-d3ghmecmrwxdzizqkb2vfxixc4a7xyu4
[+] /usr (external m4-1.4.18-6mn3iho2fr6edfzw7cx4oju3h3nl5blf)
[+] /usr (external perl-5.34.0-hjugzvixfyfpl6yufq5injfzrafmzycu)
==> Waiting for autoconf-archive-2023.02.20-6mk7s3gez7sjc2h4edsgosm2xpetcel6
==> Installing autoconf-archive-2023.02.20-6mk7s3gez7sjc2h4edsgosm2xpetcel6
==> No binary for autoconf-archive-2023.02.20-6mk7s3gez7sjc2h4edsgosm2xpetcel6 found: installing from source
==> Fetching http://ftpmirror.gnu.org/autoconf-archive/autoconf-archive-2023.02.20.tar.xz
==> No patches needed for autoconf-archive
==> autoconf-archive: Executing phase: 'autoreconf'
==> autoconf-archive: Executing phase: 'configure'
==> autoconf-archive: Executing phase: 'build'
==> autoconf-archive: Executing phase: 'install'
==> autoconf-archive: Successfully installed autoconf-archive-2023.02.20-6mk7s3gez7sjc2h4edsgosm2xpetcel6
Stage: 2.74s. Autoreconf: 0.00s. Configure: 1.59s. Build: 0.05s. Install: 1.89s. Post-install: 0.87s. Total: 7.35s
[+] /usr/share/spack/root/opt/spack/linux-ubuntu22.04-x86_64/gcc-11.4.0/autoconf-archive-2023.02.20-6mk7s3gez7sjc2h4edsgosm2xpetcel6
[+] /usr (external texinfo-6.8-r5t34jrn4b3pnquzayc3f5yqnfc6ndet)
==> Waiting for zlib-1.2.13-qld66xb7dn5a33fda5qkb4emglsmn6ah
==> Installing zlib-1.2.13-qld66xb7dn5a33fda5qkb4emglsmn6ah
==> No binary for zlib-1.2.13-qld66xb7dn5a33fda5qkb4emglsmn6ah found: installing from source
==> Fetching http://zlib.net/fossils/zlib-1.2.13.tar.gz
==> No patches needed for zlib
==> zlib: Executing phase: 'edit'
==> zlib: Executing phase: 'build'
==> zlib: Executing phase: 'install'
==> zlib: Successfully installed zlib-1.2.13-qld66xb7dn5a33fda5qkb4emglsmn6ah
Stage: 0.44s. Edit: 0.81s. Build: 1.99s. Install: 0.25s. Post-install: 0.06s. Total: 3.71s
[+] /usr/share/spack/root/opt/spack/linux-ubuntu22.04-x86_64/gcc-11.4.0/zlib-1.2.13-qld66xb7dn5a33fda5qkb4emglsmn6ah
[+] /usr (external zstd-1.4.8-g7zt2gg24fodmzluy7sbmdgfu5klqhjg)
==> Waiting for libtool-2.4.7-sltp3y2ylxczu4arn5pruq4knb6y7j3a
==> Installing libtool-2.4.7-sltp3y2ylxczu4arn5pruq4knb6y7j3a
==> No binary for libtool-2.4.7-sltp3y2ylxczu4arn5pruq4knb6y7j3a found: installing from source
==> Fetching http://ftpmirror.gnu.org/libtool/libtool-2.4.7.tar.gz
==> Error: FetchError: All fetchers failed for spack-stage-libtool-2.4.7-sltp3y2ylxczu4arn5pruq4knb6y7j3a
==> Warning: Skipping build of gmp-6.2.1-f6ku7x6kk77rw6kknylbokmv26rwaaio since libtool-2.4.7-sltp3y2ylxczu4arn5pruq4knb6y7j3a failed
==> Warning: Skipping build of gcc-13.1.0-r6tkqt2qpvdhpvdwb67scwcupu5q7q6n since gmp-6.2.1-f6ku7x6kk77rw6kknylbokmv26rwaaio failed
==> Warning: Skipping build of mpc-1.3.1-lpzenm7ukqv5r2cty3hlxaeeovvz5t2w since gmp-6.2.1-f6ku7x6kk77rw6kknylbokmv26rwaaio failed
==> Warning: Skipping build of mpfr-4.2.0-7d7gia35xoeak45h65jqkedahg3dlios since gmp-6.2.1-f6ku7x6kk77rw6kknylbokmv26rwaaio failed
==> Waiting for autoconf-2.69-4v7zhe6rx5zlrdn3kztxwmzs6dmbed2p
==> Installing autoconf-2.69-4v7zhe6rx5zlrdn3kztxwmzs6dmbed2p
==> No binary for autoconf-2.69-4v7zhe6rx5zlrdn3kztxwmzs6dmbed2p found: installing from source
==> Error: FetchError: All fetchers failed for spack-stage-autoconf-2.69-4v7zhe6rx5zlrdn3kztxwmzs6dmbed2p
==> Warning: Skipping build of automake-1.16.5-ubievawv3tcjygyiofl2jevdqdahatpv since autoconf-2.69-4v7zhe6rx5zlrdn3kztxwmzs6dmbed2p failed
==> Error: gcc-13.1.0-r6tkqt2qpvdhpvdwb67scwcupu5q7q6n: Package was not installed
==> Error: Installation request failed. Refer to reported errors for failing package(s).

its just the end of the screen log, please let me know if you need the whole log.

On 11/14/23 01:38, Roland Fehrenbacher wrote:

it's clear now that the FE and demo VMs don't start properly for some reason. Please check that your head-node is capable of running KVM virtual machines at all by executing

If this doesn't show either kvm_intel or kvm_amd, virtualization support has been disabled in the BIOS of your head and you need to re-enable it.

If kvm_amd/intel is loaded you can try to startup the FE node VM directly with the Qlustar KVM management script on the cmdline as root:

$ manage-kvm-guest -a start -n login

This should then tell you where things go wrong.

BTW: Renaming head and FE to jcluster(t) while executing the installer is supported and cannot cause the problem.

On 11/13/23 22:53, Christophe Guilbert wrote:

Thanks for the very fast answer Roland.

I did learn tmux on my linux workstation, beside the fact that its really cool and plan to use it the future, I am still struggling to have the demo and fe working in tmux

When starting the demo-system (demo-system -a start) -> console-demo-vms, I know as a fact now that I am in tmux but I am still on the c1-head. any Ctrlr-t n (or p) said "no next windows" , not only I can't switch to demo but also fe which if I understand correctly must have started automatically.

Once I exit from tmux with Ctrl-t d,

tmux ls
error connecting to /tmp/tmux-0/default (No such file or directory)

I don't see demo or fe.

When trying to start console-fe-vm

console-fe-vm
No tmux session 'login-vm' with server socket 'ql-vms'

What's happening here ?

note that during the install I rename the host c1-head jcluster and the fe jclustert (jcluster and jclustert are found in the DNS).

Would it change anything ?

0 root@jcluster ~ #
dsh -a uptime
beo-201: ssh: connect to host beo-201 port 22: No route to host
beo-202: ssh: connect to host beo-202 port 22: No route to host
beo-203: ssh: connect to host beo-203 port 22: No route to host
beo-204: ssh: connect to host beo-204 port 22: No route to host
login-c: ssh: connect to host login-c port 22: No route to host

So yes , no demo or fe connection.

Why do you thing is happening.

Thanks for your help