[virt-tools-list] Fwd: locked out after preseed install

[Mario Gummies]

18.04.2016, 16:05, "Cole Robinson" <crobinso at redhat.com>:
> On 04/18/2016 09:53 AM, Mario Gummies wrote:
>>  Hi Cole, hi all,
>>
>>  18.04.2016, 14:00, "Cole Robinson" <crobinso at redhat.com>:
>>>  On 04/15/2016 08:43 PM, Mario Gummies wrote:
>>>>   Hi Cole, hi all,
>>>>   could login via ssh from the host without preseeding. Thanks, now I know how
>>>>   the result, I am after, looks like.
>>>>   Well, then thinking about it. If my preseeding script seems the culprit:
>>>>   1) Who should I ask? (guess the d-i, preseeding ppl)
>>>>   2) My preseeding script to perform actually what? (Is there a requirements
>>>>   interface standard between virt-install and d-i preseeding for the present use
>>>>   case? The search for an existing, proper preseeding script gets easier knowing
>>>>   to name.
>>>>   3) what not to touch, because is is virt-install's job to setup the network?
>>>>
>>>>   4)
>>>>   Is it what is called by libvirt virtual networking?
>>>>  http://wiki.libvirt.org/page/VirtualNetworking#The_default_configuration
>>>>
>>>>   5)
>>>>   from my preseeding script
>>>>   #in-target /bin/bash /root/postinst.sh #on the guest
>>>>   One sees that one can trigger shell commands on the host. Is it not possible
>>>>   to setup the missing network manual/scripted?
>>>>
>>>>   Really do not know, what would be best practice here or from here.
>>>
>>>  The preseeding script is entirely a debian/ubuntu installer convention. There
>>>  is no communication between virt-install and the preseed script. So I suggest
>>>  asking on ubuntu support channels
>>  Hi,
>>  Yes, I am already asking there. Well, virt-install and d-i preseeding might not communicate in a narrower sense, but it is true that the latter produces files which the former makes use of. To have that transaction functioning, the question for a format specification comes up.
>>
>>  Question: Is there such a specification, about how the data transferred to lib-install should look like?
>>
>>  Well, you might say: Just as the unpreseeded install and it might be the truth, but it is hard to understand for me and hard to believe, cause anybody who provides a new install to virt-install then runs into the same problem, preseeded or not.
>>
>>  Question: Is it maybe the case, that there is such "convention" not explicit, but implicit in the code to be read?
>
> All virt-install really does is set up the configuration file that describes
> the VM's hardware. After that virt-install is completely out of the equation.
>
> After the VM is started, the VM OS (ubuntu here) basically proceeds onward as
> if it was on a real physical machine. There isn't any magic virt configuration
> being passed back and forth here, the ubuntu installer is just detecting
> hardware like disks and network through normal means and acting on it in the
> same way as if it was a physical machine.
>
> If a non-preseeded install, has working network at the end, but the same
> virt-install command line _with_ a preseed file does _not_ work, then 99%
> chance the issue is either with the preseed file or less likely the ubuntu
> installer
>
> - Cole

Hi,
1) I resume what I have understood: 
-there is a configuration file (between qemu(?)?
-the specification of virt-installs interaction with the enviroment is limited to the proposed network model. 
-preseed could not set up a v-machine that does not fit into your virtual network specs. So pressed did not meet the interface requirements as reason and source of failure, that is all to say from your sight.

 Then question: But virt-inst actually orders to set up the network? 
2) Hypothesis: Who is it asking? It asks qemu, right? And it does so in a way, that is complies with the interface set up standard of quemuand  d-i, right?
So you might say: There is a spec with qemu we are basing on (for non trivial guest network setup).
It could be however, that there are more specs in the chain between qemu and d-i, we do not care about.

3) So a advice to me would be rather, if all other failed: 
Go, try it with qemu instead of virt-install as user interface, then you manage setting up running networks with it, then you can try to troubleshoot better your failing interaction of preseed and qemu and solve your problem!

Is that something valid?
Tia