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:
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.
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 gives:
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 ?
I
I do
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