Search results

  1. N

    Weird networking lags

    I've running the latest PVE 6.x on 2-host cluster: pve-manager/6.4-13/9f411e79 (running kernel: 5.4.128-1-pve) Physical servers aren't the same, but very similar. And I had weird issues with networking from the LXC containers. There are lost packets when there is some constant fast network flow...
  2. N

    [SOLVED] Restoring KVM backup from Proxmox 3.x

    Greetings, EDIT: NVM, seems this is not related with restore procedure, but instead same problem as here: https://forum.proxmox.com/threads/memory-allocation-failure.41441/ I'm trying to restore old VM (KVM) created with Proxmox 3.4. Restore process went without any errors/warnings, but I...
  3. N

    LXC iproute2 ip rule & udp packets

    Weird thing. I'm runinng latest Proxmox 5.1 with CentOS 7 LXC container inside. It's "multi-homed", i.e. having 2 networks attached with 2 different Internet IPv4's. This takes iproute2 rules to work. And such setup usually works perfectly fine for me with KVM/OpenVZ/Physical hosts. I just...
  4. N

    [SOLVED] Moving to NVMe, initrd doesn't creates /dev/nvme* nodes

    Running recent & updated proxmox 5.2. It was installed on SATA drive, but now I want to move it to NVMe drives. MB has the support for UEFI boot from NVMe. So I've created a GPT partition on NVMe. 512Mb FAT32 partition with ESP flag, and rest are for linux RAID partition where LVM volume will...
  5. N

    Proxmox 4.0 VLAN

    Hello. Since the Proxmox 4.0 release the vlan package are removed and marked as conflict with pve-manager and proxmox-ve packages. As far as I've read on forums the 4.0 uses it's own VLAN "manager". But could you please explain how it's done? Is it kernel library calls directly from Proxmox VE...
  6. N

    Gateway inside VM

    I've faced some strange behaviour I couldn't resolve yet. Probably I'll figure it out soon, but will post it here in case anyone can answer faster than I handle it myself. I'll simplify things a bit to keep it easier to understand. I have node with recent Proxmox running, call it pve-node1. eth0...
  7. N

    Multihomed cluster (CMAN/corosync multicast configuration)

    Hello. I've been running 2-node cluster. It was configured to work by default on vmbr0 interface, which had whole LAN subnet 192.168.9.0/24 behind. Lately I've added a new faster NIC attached to vmbr2 and re-configured cluster to work through it, with the dedicated VLAN 192.168.248.0/30 subnet...
  8. N

    Different IPs for web & cluster

    Hello. I'm running a 2-node cluster config with the latest PVE. Basic configuration uses eth0 as default iface for everything. I have another NIC (eth1) on different subnetwork (and physically different network) on both nodes. I want both nodes to be accessible via web&ssh on eth0 IP, but...
  9. N

    HA configuration questions

    Hello. I have two 3.2 Proxmox nodes and I want to setup a HA cluster with them. Both nodes got a dedicated 10Gbps NICs for this purpose. Both nodes run both KVM and OpenVZ CTs. CTs mostly. Currently a local storage is used and no SAN are planned. I want to setup a HA for those. I've read those...
  10. N

    SNAT inside CT?

    I have a proxmox 1.9 on a HN with 2 physical NICs. One container is setup (CT). Both NICs are bridged via own vmbr0 and vmbr1. Veth from CT are also attached to these bridges. So I'm having 2 veth devices inside a CT. CT eth0->veth101.0->HN physical eth0, CT eth1->veth101.1->HN physical eth1...
  11. N

    [Network] Both venet and veth in same CT

    I'm using Proxmox 1.9 distro for my needs. By default it's web interface doesn't allows to mix network types for one CT. But I wanted to setup a mixed network within one CT. My HN has 2 physical interfaces. So I've created a CT with veth interface bridged with eth0 via vmbr0 bridge. Then I've...
  12. N

    Network issues

    I'm running Linux node1 2.6.32-6-pve #1 SMP Mon Sep 26 06:32:53 CEST 2011 x86_64 GNU/Linux. (Proxmox VE 1.9 distro) I have the following network setup 192.168.X.0/24 local subnet. HN and all CTs have IPs in that subnet. Like HN has 192.168.X.33 and CTs have 192.168.X.34, 192.168.X.35, etc. Also...