Bug#980528: debian-installer: net-install impossible because link is always reset

[etkaar]

Moin!

I did now try it via VNC installation, but no success.

I also tried it using following boot options:

--extra-args 'netcfg/disable_autoconfig=true netcfg/use_autoconfig=false net.ifnames=0 biosdevnames=0 console=ttyS0,115200n8'

This prevents DHCP (which I don't want) and directly shows me the "Configure the network" dialog where I can type in IP address, netmask and gateway. However, in the exact moment I reopen the "Configure the network" dialog after enabling the interface (ip link set eth0 up), it will set the link down.

It would be interesting to know what exactly the installer is doing once the user opens this dialog.

--etkaar

---

From: Geert Stappers <stapp...@stappers.nl>
Sent: Wednesday, 20. Jan 2021 – 20:53 CET +0100
To: etkaar <debian-b...@prvy.eu>

Subject: Re: Bug#980528: debian-installer: net-install impossible because link is always reset

On Wed, Jan 20, 2021 at 04:18:52PM +0000, etkaar wrote:
> Moin Geert,

 :-)

 
> thanks for helping!
> 
> > ???
> > (the triple question marks are for expressing my "Realy?",
> > please elaborate what is going on.
> > Yes, my request could be recieved as "vague",
> > do know that is being transmitted as "open")
> 
> Do you refer to the IPv4 addresses starting with two 255 groups?

Yes

> It was only an example, not the actual notation I used.

And the example introduced confusion.

 
> > And after configuring is actual traffic possible? 
> Yes. And once I go back to the installer, the link is down again and
> I am impossible to use the network.
> 
> > If so, provide some proof.
> Here is a proof, I made a video: https://youtu.be/9NOQAf6LOdo

I have seen the video.  I have the succesfull ping.

Also seen that installer menu is used.
Thing I would have done, is switch to another terminal

As far as I know does have QEMU support for sending ALT-F2
and ALT-F1.  But there is no ALT-F2 on serial line connections.


Anyway, there is some networking possible.
(my conclusion follows)


 
> > > #
> > > # libvirt VM configuration
> > > #
> > > <interface type='direct'>
> > > 	<mac address='52:54:00:5c:d3:e7'/>
> > > 	<source dev='eth0' mode='vepa'/>
> >
> >  I'm not sure if that is correct.
> 
> Why do you think that?

Mostly for keeping options on what to explore open.


> I use it with all my VMs.
 
Acknowledge on that.

Do know that we should avoid comparing apples and oranges.

Thing I slightly want to warn about, is that debian-installer
not the very same thing as a full blown system.



> > > #
> > > # Preseed (which also does not work)
> > > #
> > > d-i netcfg/choose_interface select ens1
> > > d-i netcfg/disable_autoconfig boolean true
> > > 
> > > d-i netcfg/get_ipaddress string 255.255.8.243
> > > d-i netcfg/get_netmask string 255.255.255.248
> > > d-i netcfg/get_gateway string 255.255.8.1
> > > d-i netcfg/get_nameservers string 8.8.8.8
> > > d-i netcfg/confirm_static boolean true
> > > 
> >
> > The "preseed stuff" is for later.
> 
> What do you mean by later?

For getting focus on the network problem.
d-i without any preseed stuff should be able to do DHCP


> I would think that the network configuration also (and at least)
> applies for the installer.
> 
> Please find also attached the virt-install command I use at the bottom
> (if I use a preseed or not, makes no difference).
> 
> Kind Regards,
> --etkaar
> 
> #
> # virt-install command
> #
> VM_NAME="vps2"
> 
> virt-install \
> --virt-type kvm \
> --name $VM_NAME \
> --ram 2048 \
> --vcpus 2 \
> --disk path=/var/lib/libvirt/images/$VM_NAME.qcow2,size=24 \
> --os-type linux \
> --os-variant debian10 \
> --graphics none \
> --console pty,target_type=serial \
> --location /var/lib/libvirt/images/.os/debian-10.7.0-amd64-netinst.iso \
> --network type=direct,source=eth0,source_mode=vepa,model=e1000 \
> --initrd-inject=/home/kvm/conf/preseed.cfg \
> --extra-args 'console=ttyS0,115200n8'

I can't spot any holes it  (due lack of indepth knowlegde)



My conclusion: Some how doesn't detect d-i link on the NIC


Advice:  Further debugging


My approach would be:

 * Temporary drop on the wish of a serial console
 * no preseed stuff yet
 * `virt-install` with having multiple VT [1]
 * install in VT-1, watch logs in other VT
 * have in another VT a shell for the `ip` commands


You probably want the syslog of d-i outside the VM
for more convinend analysis (pardon my english)



Regards
Geert Stappers
[1] https://en.wikipedia.org/wiki/Virtual_console
-- 
Silence is hard to parse