On 2016-09-17 05:25, Felix Miata wrote:
Carlos E. R. composed on 2016-09-17 05:07 (UTC+0200):
I just noticed that the virtual machine implemented by vmware shares the virtual RAM with the graphical card, up to 768MB. The real ammount I don't know
FYI, if you use usessh=1, the installer will just start a shell. You can then ssh to the machine and add swap, or do it at the console before you start yast. No reboot needed.
Interesting. How do you fire the full graphical installer?
If I'm understanding the question:
startshell=1
No, no. We started the DVD with only a shell, no graphics mode, no installer, in order to use bash commands to add a swap partition and activate it. Once done, we can start the full blown graphics installer, with some command (not rebooting); but I don't know which. Ah, it is yast.ssh. There is a help text in the first console. But this starts a text mode installer. If I use "startshell=1" as booot parameter I get a text console, with a message that "exit" starts the installer, this time graphical. Trying ssh fails: cer@Telcontar:~> ssh -X root@192.168.74.128 The authenticity of host '192.168.74.128 (192.168.74.128)' can't be established. ECDSA key fingerprint is 33:d6:eb:45:7d:c5:ed:08:65:bf:7d:2e:f8:30:ae:90. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '192.168.74.128' (ECDSA) to the list of known hosts. Received disconnect from 192.168.74.128: 2: Too many authentication failures cer@Telcontar:~> This is a failure (Too many authentication failures) that I get normally here, and I solve by editing /etc/ssh/sshd_config in the server: #MaxAuthTries 6 MaxAuthTries 12 I can edit that change in the install system, but I can't restart sshd: both rcsshd and systemctl fail, no services. I have to do it directly, kill and call the binary. And yes, this time I can start the graphical installer in the host machine. There must be another way to start the graphical system in the "guest". It is possible that there is something in my client ssh that causes that auth failure, but it happens since years. My cure is on the server, but probably there is something else I can do on the client. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)