George R Goffe wrote:
Per,
The partitioning is one major area. I select a lot of the products... multiple desktop managers... rename the ethernet device name (eth0)...
I'm looking at the partially(?) installed system via the rescue option from the .iso. I don't see any way to see where the installation was halted. It all looks ok so far, /boot is almost empty.
Hi George the latter is not good - a a brandnew installation, you ought to have at one initrd and one kernel, symlinked as initrd and vmlinuz. So clearly it did not finish.
Do you have a way to tell where the install failed?
Maybe check out the logs /var/log/YaST2/y2log (something like that). It's basically not so interesting when the VM is being killed - to me, that puts the blame entirely on the VM setup.
As it is now, the install appears to be running properly... the packages fly on by on the GUI. I step away for a few hours and come back to find the installation aborted. /var/log/messages shows the oom-killer has been invoked against the VM instance.
I'm not familiar with VirtualBox, but does it not have a specific amount of memory, with a hard upper limit? Well, apparently not, so maybe add some memory (provided your host has enough). I'm certain an installation of Leap takes no more than 2Gb or even 1Gb with active swap. -- Per Jessen, Zürich (11.1°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org