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. Do you have a way to tell where the install failed?
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. This seems to tell me that the installer has a memory problem. "buying" memory but never freeing it. Eventually, the VM is killed.
Again, THANKS for responding.
George...
On Saturday, March 21, 2020, 5:04:24 AM PDT, Per Jessen
Per,
Here's what I sent to David who also responded to my plea for help.
I do NOT think it's the VB config. I've been able to install/run MANY versions of Fedora Core. I suspect that it's my config options that are breaking the install.
I run TW and Leap both on xen and on real iron, many of them - sometimes a config (nfsroot, iscsi, multipathing) can be a little tricky to get to work, but in the end it works. Which config options are you referring to here ? -- Per Jessen, Zürich (10.7°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 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org