1.) Thanks for clarification. So why it is possible to add CT to HA without adding it to HA Group? Are there some other benefits beside of failover i can have from HA?
2.) I look forward for this auto recover being implemented. It would be super useful. Especialy if it was possible to enable...
I have testing cluster with 3 nodes of PVE 5.0, i've managed to setup ZFS replication and HA.
1.) HA Failover was not working unless i created HA group and put my CT in it (originaly i was thinking that any running node will be used when no group is assigned to resource)
2.) When i manualy...
Hello,
if i set container ostype: unmanaged will proxmox/lxc configure it's network?
I understand that it no longer can't do the distro specific setup (eg.: edit /etc/network/interfaces for debian), but it still can configure network dynamicaly eg. using lxc.net.0.ipv4.address = 192.168.1.1/25...
And here i go again adding $version = 6 if $version eq 'squeeze/sid'; to /usr/share/perl5/PVE/LXC/Setup/Debian.pm after upgrade to proxmox 5.0. I guess all testing version names are missing for older debian versions...
you know what is funny? I have two testing servers with PVE 5.0, one has 8GB ram, one has 1GB. They both use like 800M of memory, however the one with 1GB has problems operating. It seems to me that there are some burst of momentary needs of memory which leads to allocation failures. Hah, which...
I had PVE 4.4 test setup with 1 GB ram and recently upgraded to PVE 5.0, it gives lots of various memory allocation errors even when there's nothing else running (no CT, no VM, no nothing).
This page
https://www.proxmox.com/en/proxmox-ve/requirements
says:
Minimum Hardware (for testing only)...
Virtual Environment 4.4-18/ef2610e8
Sorry, i was actually doing shutdown followed by start. not sure why there's no restart. However that's not point. I am wondering how to give device permissions to container without restarting it (= having to shut down and restart all processes runing in that ct).
Hello, i've added these settings to CT config:
lxc.cgroup.devices.allow: c 10:200 rwm
lxc.hook.autodev: sh -c "modprobe tun; cd ${LXC_ROOTFS_MOUNT}/dev; mkdir net; mknod net/tun c 10 200; chmod 0666 net/tun"
now when i do pct shutdown <ctid>; pct start <ctid> then tun driver (and openvpn)...
Turns out i migrated ubuntu CT (OpenVZ) to debian CT (Proxmox LXC) using rsync. You have to create container with right os template. It cannot be changed using web, i had to manualy edit "ostype" in config file. There probably should be some warning if you try to boot CT with wrong ostype.
OMFG it happened again. This time with container that states "squeeze/sid" in /etc/debian_version here i am again doing workarounds in /usr/share/perl5/PVE/LXC/Setup/Debian.pm at 2:30 freaking o'clock AM to get LXC container working. (which worked without problem in pure OpenVZ without proxmox...
I think i've described it enough. I don't have problem with bug itself, but with this whole way of thinking that allowed this bug to happen at all. I was on vacation (= not upgrading proxmox) and admin of container upgraded debian inside it. Rendering it useless after reboot. This is just...
Also the message "unsupported debian version '9.1'" should be imediately visible in pve web interface without having to look it up manualy in logs using ssh and launching containers in foreground mode manualy specifiing the log file.
OMG. This is worst bug i've ever seen. Please remove this useless check completely. There should be warning or something. But certainly it should not prevent debian container from booting. There's no point. If it will fail to boot it's sufficient to have the warning message. As you can see it's...
man pveproxy says this:
Warning
Do not replace the automatically generated node certificate files in /etc/pve/local/pve-ssl.pem and etc/pve/local/pve-ssl.key
What's so wrong about replacing original snakeoil key+cert with eg. letsencrypt one? It seemed to work for me. I modified my...
It's strange. It works now for me. But i've been trying this few updates ago. Is that recently added feature? I am pretty sure that i've used ZFS storage for that. Maybe i screwed something up back then...
Hello,
i have ZFS storage configured in my PVE and when i create new LXC CT it automatically creates ZFS subvolume, which is really great. But when i create new KVM VM it creates raw image on the ZFS filesystem rather than ZVOL. This results in huge performance penalty and is approach that is...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.