Search results

  1. D

    PVE from RAMFS & LXC

    IIUC, CT not started cause of (from debugging output submitted earlier) lxc-start 101 20190830122341.107 ERROR conf - conf.c:lxc_chroot:1389 - Permission denied - Failed to mount "/usr/lib/x86_64-linux-gnu/lxc/rootfs" onto "/" as MS_REC | MS_BIND lxc-start 101 20190830122341.107 ERROR...
  2. D

    PVE from RAMFS & LXC

    pvereport output attached
  3. D

    PVE from RAMFS & LXC

    Hello, community. Cause of running PVE node from ramfs lxc containers not starting (VMs - ok.) config: arch: amd64 cores: 1 hostname: a memory: 512 net0: name=eth0,bridge=vmbr1,hwaddr=A6:5B:35:4B:2C:85,ip6=auto,tag=6,type=veth ostype: alpine rootfs: local:101/vm-101-disk-0.raw,size=512M swap...
  4. D

    Remove node from 2 nodes cluster

    Hi, Cyberavis. I successfully split 2 node cluster online with working vms with simple scripts executing on both nodes. ~# cat stop.sh #!/bin/sh systemctl stop pvestatd.service systemctl stop pvedaemon.service systemctl stop pve-cluster.service systemctl stop corosync systemctl stop...
  5. D

    Redirect IP port for a container via Proxmox firewall?

    BlueLineSwinger, your system is Debian. It seems you are not limited by Proxmox Filrewall functionality.
  6. D

    PXE boot not working after upgrade

    Thanks, Fabian. http://download2.proxmox.com/temp/pve/pve-qemu-kvm_2.7.0-7~test1_amd64.deb pxe boot working again.
  7. D

    PXE boot not working after upgrade

    After upgade to: pve-qemu-kvm-27.0-6 issue remains.
  8. D

    PXE boot not working after upgrade

    Hello, community. iPXE boot not working after last upgrade. :~# pveversion -v proxmox-ve: 4.3-71 (running kernel: 4.4.21-1-pve) pve-manager: 4.3-10 (running version: 4.3-10/7230e60f) pve-kernel-4.4.21-1-pve: 4.4.21-71 lvm2: 2.02.116-pve3 corosync-pve: 2.4.0-1 libqb0: 1.0-1 pve-cluster...
  9. D

    Private subnet: host can connect to guests, guests to internet, but not to host or each other

    To access proxmox from containers use 10.10.10.1 address as destination.
  10. D

    Private subnet: host can connect to guests, guests to internet, but not to host or each other

    It seems ещ ьу post-up iptables -t nat -A POSTROUTING -s '10.10.10.0/24' ! -d '10.10.10.0/24' -o eth0 -j MASQUERADE should help you.
  11. D

    One LetsEncrypt-certificate for all Clustermember and access behind an haproxy

    > If someone interesting in an tutorial I can posted it here. Yes, its's very cool!
  12. D

    Machine type q35 online migration problem

    Thanks, Tom, VM hasn't any disk device. Full config and kvm cmdline follows: root@pr0xm3x:# cat /etc/pve/nodes/pr0xm3x/qemu-server/120.conf #Standard PC (Q35 + ICH9, 2009) (alias of pc-q35-2.2) balloon: 512 boot: n cores: 1 ide2: none,media=cdrom localtime: 1 machine: q35 memory: 2048 name...
  13. D

    Machine type q35 online migration problem

    Hello, community. We are faced with migration problem today. root@pr0xm3x:~# qm migrate 120 pr0xm5x --online Mar 30 13:38:48 starting migration of VM 120 to node 'pr0xm5x' (172.26.6.221) Mar 30 13:38:48 copying disk images Mar 30 13:38:48 starting VM 120 on remote node 'pr0xm5x' Mar 30...