Univention Bugzilla – Bug 46990
Network components are not recognized during installations within Proxmox
Last modified: 2021-05-14 16:33:57 CEST
A user reported several installations of UCS in Proxmox as virtual machine. About half of the installations are aborted because the network components are not recognized. Other systems don't have such problems. The user assumes the recognition of the network components does not take the time needed to be successful.
Proxmox is QEMU-KVM. The VirtIO driver and other network drivers like e1000 and rtl8139 drivers are of the standard Linux kernel and are this included in UCS by default. Without any more detail on the exact problem we cannot help you: - what is the exact symptom? - does it work after a retry? - what do you exactly do to force the retry? - are there any log messages? Switch to the 4th console with Ctrl-Alt-F4 - how is your VM configured? - which network models? virtio, e1000, rtl8139, ... - how many network adapters? - are you using DHCP? - where does the DHCP server run? - does that DHCP sever show the DHCPREQ and DHCPOFFER messages? - ...
1) The user's symptom: The installation stalls at "Netzwerk-Hardware erkennen" (recognize network hardware). 2) Retries: Rebooting the system several times and retrying the installation leads to success. 3) Logs: CTRL-ALT-F4 yields the console of the host system. VM-Adapter: 1 DHCP: yes DHCP-Server: Fritzbox The PROXMOX machine is configured for the VM with: Disk: 32 GB CPU: 1 Socket - 2 Cores Automatic memory allocation: 512-6144 NIC: virtIO - bridge=vmbr0 (paravirtualized)
(In reply to Nico Gulden from comment #2) > 1) The user's symptom: The installation stalls at "Netzwerk-Hardware > erkennen" (recognize network hardware). > > 2) Retries: Rebooting the system several times and retrying the installation > leads to success. > > 3) Logs: CTRL-ALT-F4 yields the console of the host system. I'm less interested in the host system, but the console of the VM. Check the documentation of Proxmox how to send that key combination to the VM. > The PROXMOX machine is configured for the VM with: ... > NIC: virtIO - bridge=vmbr0 (paravirtualized) This is how we do it with our QEMUs, too. So ask Proxmox. Or check their bridge configuration: - bridge forward delay? `brctl show` - maybe they are affected by Bug #33160, too?
This issue has been filed against UCS 4.3. UCS 4.3 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed. If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.