raising vm_vcpus fails suse builds about packer-templates HOT 6 CLOSED

@FlorianHeigl I actually do builds on nested as well occasionally and can confirm that your results may vary on various scenarios.

from packer-templates.

I might have an idea what happens there: It seems the installer goes more fancy if you have more than 1 core or more RAM. Somehow then the menu selection fails.

from packer-templates.

It seems this is an issue with running nested on KVM, too. I just gave VBox 2 vcpus in my little MacBook and there it works flawlessly.
So seems, for mass-building the only save way is to launch one VM per build, or use a baremetal build host. I am grateful for any input.

from packer-templates.

Also, I've debated on removing the facter dependencies and using more native bash functionality.

from packer-templates.

I was thinking about to verify how many of the facter-determined variables are actually used, it seems the shell parts do 90% already. it would seem useful to remove it but I got all SUSE / facter issues sorted by now.
I'm refactoring base.sh to be a bit easier on the eyes, since that was giving me the hardest time.
When you review that, maybe you can keep the "do we need facter" in mind - but also after that it will be easier to remove & thus less urgent.

from packer-templates.

Oh, closing this for the moment since you were able to confirm there's unstabilities with nested.
I see the debian builds also use QEMU. I'd like to try the same for SUSE at a later point.

from packer-templates.