See what I wrote earlier about setting up Proxmox…
(XFS)
And keep an eye open for erroneous error messages during set up…
I use it now
for clarification…
During VM-configuration I have to select a bridge. Because vmbr0 is already used by Proxmox himself…I have to use now vmbr1 - right?
No, you must use vmbr0.
What you “see” as Proxmox’s LAN connection is actually the cable connecting a “virtual Switch” inside of Proxmox. Proxmox itself is connected, but (ideally) all your LAN Servers are connected to this 10 GB virtual Switch.
You’re reading right, if using VirtIO drivers / hardware, inside of Proxmox the network is 10 GB!
1 Like
Seems like a SSD (Or the controller) is soon dead… ;-(
I will ignore this - I will ignore this-I will ignore this-I will ignore this 
I’m totally relaxed 
This system negotiation always occurs only after a VM has been installed and not properly stopped
…
Hard reset
…
purging VM
…
rebooting w/o issues
Ok, that indicates that the VM isn’t being shutdown properly.
In other words: you forgot to install the qemu-agent.
This is needed for all Windows and Linux VMs in Proxmox, as the ACPI call to shutdown isn’t reliable enough when a UPS needs to shutdown the box before the power outages.
Certain Windows versions needed user intervention (Klicking OK…) when the UPS wanted to shutdown the system.
The Agent is very quickly installed, in NethServer and even in Windows, and needs no reboot.
If activating the QEMU Agent, the VM needs to be turned off at least once afterwards…
no no… yum install qemu-guest-agent
And reboot of the vm isn’t sufficient, it needs a shutdown and restart.
Also this helps:
This forces a shutdown after 180 seconds…
looks better…
between two issues: you should send me your address for a 
and a 
…
seriously!
1 Like
So how’s the server coming?
Now you can enable the second NIC in Proxmox.
NethServer usually doesn’t need one, but as the saying (german) goes:
Reboot tut immer gut…
(A reboot is always good…)
Afterwards the 2nd Interface should show up in NethServer
Note: The NIC must be connected to something, like your Router!
Actually, with Proxmox and HW changes, a shutdown and afterwards starting is MUCH better!
Took me a long time to get the QEMU right, as I always rebooted.
Also, check both the old interface and the newer cockpit. Some things still only work in the old Interface.
seems to be still enabled - but not connected to the router
Can we make a break? . .my wife…
Thank you very much
As said, it NEEDs to be connected (to something)
WAF: No Probs!
(WAF=Wife Acceptancy Factor)
current state:
auto lo
iface lo inet loopback
auto enp3s0
iface enp3s0 inet manual
#Connected to Switch
auto enp2s0
iface enp2s0 inet manual
# now connected to DSL router
auto vmbr0
iface vmbr0 inet static
address 192.168.3.200
netmask 255.255.255.0
gateway 192.168.3.1
bridge-ports enp3s0
bridge-stp off
bridge-fd 0
auto vmbr1
iface vmbr1 inet manual
bridge-ports none
bridge-stp off
bridge-fd 0
In Nethserver only one port again available.
Did you try with the old web UI (Port 980)?
You CAN setup a 2nd Nethserver with just vmbr1 active, just to confirm the fact it’s working