Recent content by proximoxi

Hi Stoiko i only removed some privacy mail and users... and some monitoring lines which have nothing todo with this After exporting the pool i can start the vm again. i rebooted also again and its working now... # zvol_wait Testing 24 zvol links All zvol links are now present. Thank you much !

# zpool status pool: vms_lnx state: ONLINE scan: scrub repaired 0B in 00:24:43 with 0 errors on Sun Feb 13 00:48:44 2022 config: NAME STATE READ WRITE CKSUM vms_lnx ONLINE 0 0...

# pveversion -v proxmox-ve: 7.1-1 (running kernel: 5.13.19-5-pve) pve-manager: 7.1-10 (running version: 7.1-10/6ddebafe) pve-kernel-helper: 7.1-12 pve-kernel-5.13: 7.1-8 pve-kernel-5.11: 7.0-10 pve-kernel-5.13.19-5-pve: 5.13.19-13 pve-kernel-5.13.19-4-pve: 5.13.19-9 pve-kernel-5.13.19-2-pve...

edit: sorry, wrong forum :( can some mod move this to proxmox sever? hi there, after reboot from Host, 1 VM can't be started anymore. TASK ERROR: timeout: no zvol device link for 'vm-700-disk-0' found after 300 sec found. # zfs list NAME USED AVAIL REFER...

dhcp hat adresse nochmal vergeben... erledigt...

Hallo zusammen Habe seit heute Vormittag immer wieder Unterbrüche im Management. Sowohl Webinterface als auch SSH geht dann zu. Alle paar Sekunden ist für ein paar Sekunden alles weg und kommt dann wieder. Unregelmässig, aber alle paar Sekunden Ein Restart vom Host hat nichts gebracht. Ein...

hi there i found out, with my internal NIC it's working. But the second NIC (4 Port Ethernet Card) will not work :( but in the old "Server" they worked... Internal NIC (working): root@proxmox:~# ethtool -i enp9s0 driver: r8169 version: 5.11.22-1-pve firmware-version: rtl8168h-2_0.0.2 02/26/15...

Hi there got new Hardware and setting up proxmox new. my old config look like this: auto lo iface lo inet loopback iface enp0s31f6 inet manual iface enp4s0 inet manual iface enp4s0.20 inet manual auto enp0s31f6 iface enp0s31f6 inet static address 10.0.0.10/24 gateway 10.0.0.254...

ooooh :rolleyes: now i got it o_O lol... okay. thank you. now it makes sense for me.

What do you mean with this? 10.0.0.10/24 is a valid IP in my understanding? then why proxmox add a route if it don't need it? done. i do :)

Hello aaron Remove the Route did the trick... thank you Can you maybe explain me, why the existing route has not worked in this case? root@proxmox:~# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 10.0.0.254...

Hello aaron Thank you for you Reply. I think i describe the Problem too bad. The Host (10.0.0.10) is running on vmbr0 without VLAN. The VM1 (10.0.0.150) is running von vmbr0 without VLAN. They can Ping each other and 8.8.8.8, no Problem there... ______________________________________ VM2...

Hi there got a little problem and hope you can help me :) I added a new Bridge (vmbr1) as a Trunk. Setup: Proxmox Server (vmbr0) 10.0.0.10 VM2 (vmbr0) IP 10.0.0.20 VM1 (vmbr1 - tagged VLAN 20) IP 10.0.20.10 Problem: Proxmox Server can't Ping in the 10.0.20.0/24 Net. VM1 can ping VM2...

That's working thank you. Can you explain me what we did with this command? thank you! regards

Hi, get an Error with this command: qm set 120 -machine pc-i44fx-2.11 400 Parameter verification failed. machine: value does not match the regex pattern qm set <vmid> [OPTIONS]