Search results

Tell me and we'll both know. In some ways it's good to know I'm not the only one.

No HA. Just a plain vanilla VM.

Huh? /etc/network/interfaces has as last line source /etc/network/interfaces.d/* so there is no need to duplicate definitions that are included in any file in that directory. The SDN config is activated by and integrated with systemd in this way. And without that source line, SDN won't work.

I think you missed the bit where it's working on my Ethernet-only machines without enabling forwarding using /proc/sys/net/ipv4/ip_forward -- which I presume is what the ip-forward on in the generated /etc/network/interfaces.d/sdn is supposed to achieve.

The only thing that is needed is to edit /etc/sysctl.conf and uncomment net.ipv4.ip_forward=1. For some reason this is needed on WiFi machines but not on machines with Ethernet as their primary interface. Go figure.

Question: Why do you define vnet1 both in /etc/network/interfaces and through SDN (which ends up in /etc/network/interfaces.d/sdn?

I've been trying to setup a laptop with Proxmox for working on the road. I have no bridge configured, only a WiFi interface. The laptop is a member of my home development cluster, and everything seems to work perfectly. The WiFi interface on the laptop and the vmbr0 interfaces on the other...

Windows 11 24H2 guest on Proxmox 8.2.7 On shutdown it goes through the whole shutdown process but then the UEFI just boots it again... Under VirtualBox 7.1.4 on macOS 15.0.1 Windows 11 23H2 shuts down as expected. Where should I start looking?

I have a 4-node cluster in my homelab. I want to rename two nodes, and also delete a third node (originally created for quorum purposes only). What is the best way to proceed? I could migrate all VMs and CTs to the one node that won't be renamed, remove all the others, rename two of the nodes...

Solved it. All I needed to do was to change managed=false to managed=true under [ifupdown] in /etc/NetworkManager/NetworkManager.conf

I use Proxmox as an XFCE-based workstation, following these instructions: https://pve.proxmox.com/wiki/Developer_Workstations_with_Proxmox_VE_and_X11 I need to be able to connect to an OpenVPN server with TOTP or Yubikey authentication so I'd like to be able to use the GUI to connect. I...

I had the exact same issue. What I find strange is that PVE works fine with vmvga while PBS needs vga.

Why has that bug been marked as "Resolved invalid"? By your own admission it's a bug -- even if it's a problem caused by an upstream package. Seems the bug has been fixed upstream, but there's no new release of udisks2 yet. Does/can Debian/Proxmox include the patch that fixes it...

The 6.2 kernel feels faster to me... but I'm not running anything fancy like you are.

What's the recommended way to install the newer 6.2 kernel? Just sudo apt install pve-kernel-6.2?

I've been running Proxmox as my workstation OS at the office for years. Since the pandemic I've been working from home where I've always been using (X)Ubuntu. Recently reinstalled and went up to 22.04 Now I wanted to spin up some VMs and wanted to get bridged networking for that. What a pain in...

We've been running this just fine with Ubuntu 18.04 and 20.04 inside the (unprivileged) containers. We did find we needed to add use_vmac to the instances inside the keepalived.conf to prevent both nodes in the keepalive pair from obtaining the virtual IP. Currently still on Proxmox 6.4 on the...

I just encountered a similar problem with dns_loopia.sh from acme.sh/dnsapi which was updated in the last 6 months or so after an API change at Loopia. What do we have to do to get Proxmox to do a refresh from upstream?

And no email support.

Does it need to be a pre-built mini PC? Otherwise look at an ITX motherboard with SFFPC case. IMHO the biggest limitation of these mini PCs (both pre-built and custom ITX-based builds) is only 2 RAM slots, and usually only a single M.2 slot. One ITX board that I know has two M.2 slots is the...