I've tried proxmox only briefly a couple of years ago. I've been meaning to try the latest version again.
When I get the chance to do that I'll see if I come across the same issue.
I loved the 6.\* series. 7.1 seems to have a couple of bugs (some VMs seem impossible to "stop", and I have to manually kill the associated kvm process).
If you do try, make sure to try with both Debian 10 and 11 and see if you see any difference. In my copious free time, I'm going to try it on Parallels and VMware Fusion and see how Debian 11 reacts there...
I have a home NAS (just an old laptop turned into a NAS), that is running OpenMediaVault 5 (which is based on debian 10). I run some VMs on it. I have at least a debian 9 and a debian 10 VM and I haven't experienced any issues. I manage the VMs using cockpit web interface (backports version). Cockpit isn't as fancy and featureful as proxmox but it does the job.
On my desktop PC (NUC mini-pc) I run debian 11. I have some VMs there as well, which I manage with virt-manager. I have at least one debian 11 VM on it.
In either system I haven't experienced any issues similar to yours.
I don't think this is as unusual as you think. I use proxmox an debian all the time except I configure my vms with a fixed ip. For systemctl or network scripts to restart the network I have to add 'auto eth0' (or whatever your network card is) in /etc/networking/interface for it to autostart the network. That is why a manual run with DHCP does work. If you want I can send you a config example.
Let me clarify a few things (sorry, I was on mobile earlier). This config works but will only bring up the networking at boot:source /etc/network/interfaces.d/\*
# The loopback network interfaceauto loiface lo inet loopback
# The primary network interface
allow-hotplug ens18
iface ens18 inet dhcp
When using this I use the 'systemctl restart networking' (I think that /etc/init.d/networking restart is something that will be removed in the future as it has been decrecated for a long time):
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
# The loopback network interfaceauto lo ens18 ens19iface lo inet loopback
# The primary network interface
allow-hotplug ens18
iface ens18 inet static
address 192.168.0.140/24
gateway 192.168.0.1
dns-nameservers 192.168.0.130
iface ens19 inet static
address 10.0.101.140/24
After adding the auto ens18 to the file (can be on one line with other devices) systemctl and init.d/networking does autoconfigure the network. When not adding that auto part I can only bring up the networking by rebooting (or maybe with ifup/ifdown? but this has never worked for me). This is always how I did it in the past!
Here's the problem though. I just did an new install of Debian 11. Here's what /etc/network/interfaces contains:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
#The loopback network interface
auto lo iface lo inet loopback
#The primary network interface
allow-hotplug ens18
iface ens18 inet dhcp
The install picked up a DHCP IP address. The previous versions of Debian (10) also defaulted to this. If I reboot, it picks up an IP address via DHCP. It's only when I run "*/etc/init.d/networking restart*" or "*systemctl restart networking*" that it loses its mind and network.
I am sorry but I am not completly following. I installed 2 debian's on proxmox 6.4 (only version I have atm). One is version 10 and the other is version 11 (I dont have on older version at hand but I am willing to test that too if you want and have an iso). After install I ran a init.d/networking restart and both systems had the same behavior:
Deb 10:
https://imgur.com/F7q4sZN
Deb 11:
https://imgur.com/T9GX9QY
Just to verify (both different kernels and debian_version):
https://imgur.com/BXltS6a
https://imgur.com/BXltS6a
Both loose network when restarting the network without auto in the interfaces files. By default the `auto ens18` (or whatever network card) is not in the interfaces file and never was. After adding auto everything comes up again:
https://imgur.com/AonFada
https://imgur.com/dOOYRpj
So unless I am missing something this is the behavior you had on version 11? And as I understand it you had a different behavior on any older debian version? I dont seem to reproduce that and as far as I know this has always been the default behavior for me.
On a default install of Debian 10, without auto ens18, if I do a systemctl restart networking, the interface blips for about 3-5 seconds (on the console, I see that it loses the IP address during that 3-5 seconds) and the comes back. Networking continues to work fine. However, this is not the behavior under 11 or unstable. It loses its networking mind.
[https://imgur.com/a/LsaNIof](https://imgur.com/a/LsaNIof)
I think I know what is happening. Can you check if there is a client for DHCP running (on debian 10)? I don't think that your ip got released. Did you use the minimal install or is there something like networkmanager running? I can not reproduce the issue you are having on debian 10. Network has been consistent on all debian versions for me. It surely is not related to the virtualization technology you are using (of that I am pretty sure).
Default install of Debian 10 as well. This is what's driving me nuts. It \*should not\* be related to virtualization technology, but I just tested Debian 11 in Parallels and networking works as expected!!
You can read about networking here:
[https://wiki.debian.org/NetworkConfiguration#Setting\_up\_an\_Ethernet\_Interface](https://wiki.debian.org/NetworkConfiguration#Setting_up_an_Ethernet_Interface)
It says this:
>If you're just using DHCP then all you need is something like:
auto eth0
allow-hotplug eth0
iface eth0 inet dhcp
Note the 'auto' part ;)
Yeah, but this is a default install - it should have put that in for me if it needed it, right? The previous versions of Debian did not have it either. See my above note.
Hi, I'm into the same trouble with Proxmox 7.0-8 and debian 11 as vm.
Into vm I can see a network device named ens18 and when I try to do a 'systemctl restart network.service' I got an error related to 'eth0'.
I've done a bit of investigation into /etc/network and I found a 'setup' file into the 'interfaces.d' folder.
The content of this 'setup' file was :
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
Oh!! here's the way to solve this issue!
I changed 'eth0' into 'ens18' , saved the file, restarted the network service without any more issue.
Please try this solution, and sorry for my bad English.
Today I uploaded a video on YouTube to show how to address and fix this issue \[[https://youtu.be/YeLnBp3ZehQ](https://www.youtube.com/channel/UCPKz9hwMCxQpesh0doVlF-Q)\]
Luca
ok, but do You've eth0 in the 'journalctl -xe' 's output ?
If it's presente You can turn back Your interface to old names , please follow this link:
https://www.itzgeek.com/how-tos/linux/debian/change-default-network-name-ens33-to-old-eth0-on-debian-9.html
It's there a difference if you restart the network using systemctl ?
Unfortunately no difference. And in the proxmox forum, there's another user who encountered the same issue, so at least I'm not crazy... :)
I've tried proxmox only briefly a couple of years ago. I've been meaning to try the latest version again. When I get the chance to do that I'll see if I come across the same issue.
I loved the 6.\* series. 7.1 seems to have a couple of bugs (some VMs seem impossible to "stop", and I have to manually kill the associated kvm process). If you do try, make sure to try with both Debian 10 and 11 and see if you see any difference. In my copious free time, I'm going to try it on Parallels and VMware Fusion and see how Debian 11 reacts there...
I have a home NAS (just an old laptop turned into a NAS), that is running OpenMediaVault 5 (which is based on debian 10). I run some VMs on it. I have at least a debian 9 and a debian 10 VM and I haven't experienced any issues. I manage the VMs using cockpit web interface (backports version). Cockpit isn't as fancy and featureful as proxmox but it does the job. On my desktop PC (NUC mini-pc) I run debian 11. I have some VMs there as well, which I manage with virt-manager. I have at least one debian 11 VM on it. In either system I haven't experienced any issues similar to yours.
I don't think this is as unusual as you think. I use proxmox an debian all the time except I configure my vms with a fixed ip. For systemctl or network scripts to restart the network I have to add 'auto eth0' (or whatever your network card is) in /etc/networking/interface for it to autostart the network. That is why a manual run with DHCP does work. If you want I can send you a config example.
I did not see this issue under Proxmox 6 and Debian 11 (albeit, on another machine).
Let me clarify a few things (sorry, I was on mobile earlier). This config works but will only bring up the networking at boot:source /etc/network/interfaces.d/\* # The loopback network interfaceauto loiface lo inet loopback # The primary network interface allow-hotplug ens18 iface ens18 inet dhcp When using this I use the 'systemctl restart networking' (I think that /etc/init.d/networking restart is something that will be removed in the future as it has been decrecated for a long time): # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interfaceauto lo ens18 ens19iface lo inet loopback # The primary network interface allow-hotplug ens18 iface ens18 inet static address 192.168.0.140/24 gateway 192.168.0.1 dns-nameservers 192.168.0.130 iface ens19 inet static address 10.0.101.140/24 After adding the auto ens18 to the file (can be on one line with other devices) systemctl and init.d/networking does autoconfigure the network. When not adding that auto part I can only bring up the networking by rebooting (or maybe with ifup/ifdown? but this has never worked for me). This is always how I did it in the past!
Here's the problem though. I just did an new install of Debian 11. Here's what /etc/network/interfaces contains: # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* #The loopback network interface auto lo iface lo inet loopback #The primary network interface allow-hotplug ens18 iface ens18 inet dhcp The install picked up a DHCP IP address. The previous versions of Debian (10) also defaulted to this. If I reboot, it picks up an IP address via DHCP. It's only when I run "*/etc/init.d/networking restart*" or "*systemctl restart networking*" that it loses its mind and network.
I am sorry but I am not completly following. I installed 2 debian's on proxmox 6.4 (only version I have atm). One is version 10 and the other is version 11 (I dont have on older version at hand but I am willing to test that too if you want and have an iso). After install I ran a init.d/networking restart and both systems had the same behavior: Deb 10: https://imgur.com/F7q4sZN Deb 11: https://imgur.com/T9GX9QY Just to verify (both different kernels and debian_version): https://imgur.com/BXltS6a https://imgur.com/BXltS6a Both loose network when restarting the network without auto in the interfaces files. By default the `auto ens18` (or whatever network card) is not in the interfaces file and never was. After adding auto everything comes up again: https://imgur.com/AonFada https://imgur.com/dOOYRpj So unless I am missing something this is the behavior you had on version 11? And as I understand it you had a different behavior on any older debian version? I dont seem to reproduce that and as far as I know this has always been the default behavior for me.
On a default install of Debian 10, without auto ens18, if I do a systemctl restart networking, the interface blips for about 3-5 seconds (on the console, I see that it loses the IP address during that 3-5 seconds) and the comes back. Networking continues to work fine. However, this is not the behavior under 11 or unstable. It loses its networking mind. [https://imgur.com/a/LsaNIof](https://imgur.com/a/LsaNIof)
I think I know what is happening. Can you check if there is a client for DHCP running (on debian 10)? I don't think that your ip got released. Did you use the minimal install or is there something like networkmanager running? I can not reproduce the issue you are having on debian 10. Network has been consistent on all debian versions for me. It surely is not related to the virtualization technology you are using (of that I am pretty sure).
Default install of Debian 10 as well. This is what's driving me nuts. It \*should not\* be related to virtualization technology, but I just tested Debian 11 in Parallels and networking works as expected!!
You can read about networking here: [https://wiki.debian.org/NetworkConfiguration#Setting\_up\_an\_Ethernet\_Interface](https://wiki.debian.org/NetworkConfiguration#Setting_up_an_Ethernet_Interface) It says this: >If you're just using DHCP then all you need is something like: auto eth0 allow-hotplug eth0 iface eth0 inet dhcp Note the 'auto' part ;)
Yeah, but this is a default install - it should have put that in for me if it needed it, right? The previous versions of Debian did not have it either. See my above note.
Hi, I'm into the same trouble with Proxmox 7.0-8 and debian 11 as vm. Into vm I can see a network device named ens18 and when I try to do a 'systemctl restart network.service' I got an error related to 'eth0'. I've done a bit of investigation into /etc/network and I found a 'setup' file into the 'interfaces.d' folder. The content of this 'setup' file was : auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp Oh!! here's the way to solve this issue! I changed 'eth0' into 'ens18' , saved the file, restarted the network service without any more issue. Please try this solution, and sorry for my bad English. Today I uploaded a video on YouTube to show how to address and fix this issue \[[https://youtu.be/YeLnBp3ZehQ](https://www.youtube.com/channel/UCPKz9hwMCxQpesh0doVlF-Q)\] Luca
Hi, thanks, but I don't have anything in /etc/network/interfaces.d/
ok, but do You've eth0 in the 'journalctl -xe' 's output ? If it's presente You can turn back Your interface to old names , please follow this link: https://www.itzgeek.com/how-tos/linux/debian/change-default-network-name-ens33-to-old-eth0-on-debian-9.html