Search results

Hello to all. I have some trouble to restore VM to a ceph. I can't understand the right parameters. This is the VM profile arch: amd64 cores: 2 features: nesting=1 hostname: fs memory: 4096 net0...

Yes, seems very similar, thank you. Now I switched to privileged container, 'cause seems similar problems happens only to my lxc unprivileged.

Often, always, when I run reboot from a Debian 9 container the LXC doesn't reboot, the pct list command doesn't works more and with ps aux | grep "lxc" there are two sessions of the same container. After kills them the pct list command start to works again, but the container don't starts...

Yes, me too

Very old post, but a simple and effective solution that I use on every my ProxMox is this: https://securedragon.net/clients/knowledgebase/40/HOW-TO-Setup-a-very-basic-Debian-VNC-server-XFCE4-Desktop.html Only 172Mb undertaked :)

Sometimes it can be useful starting a new lxc from a backup, instead of a template. But it can be interesting, and less confusing, if it can be possible rename a backup set with custom name. This can be made from cli, but after, the restore can't run (or at least I'm not capable). Leave the...

Yes, only for new backup, of course. After reboot, I don't know why, now it works, thank you.

It doesn't worked for me. I put the option in /etc/vzdump.conf. Must I reboot Proxmox ? # vzdump default settings tmpdir: /media/lxc/temp #dumpdir: DIR #storage: STORAGE_ID #mode: snapshot|suspend|stop #bwlimit: KBPS #ionice: PRI #lockwait: MINUTES #stopwait: MINUTES #size: MB #maxfiles: N...

Hello, backups on all my Debian 8 lxc skips some log files (mostly var/log/many_dirs, but not only). Either in snapshot, suspend or stop mode, either lzo or gzip compressions, either from cli (eg: vzdump 100 102 103 104 105 107 108 109 110 --mailto cip@ciop.com --quiet 1 --mode stop --storage...

Thank you for your prompt replay. And, mostly, for your incredible, fantastic work.

proxmox-ve: 4.2-49 (running kernel: 4.4.8-1-pve) pve-manager: 4.2-4 (running version: 4.2-4/2660193c) pve-kernel-4.4.6-1-pve: 4.4.6-48 pve-kernel-4.2.6-1-pve: 4.2.6-36 pve-kernel-4.4.8-1-pve: 4.4.8-49 pve-kernel-4.2.8-1-pve: 4.2.8-41 pve-kernel-4.2.2-1-pve: 4.2.2-16 lvm2: 2.02.116-pve2...

Hello, on ProxMox 4.1: proxmox-ve: 4.1-26 (running kernel: 4.2.6-1-pve) pve-manager: 4.1-22 (running version: 4.1-22/aca130cf) pve-kernel-4.2.6-1-pve: 4.2.6-36 lvm2: 2.02.116-pve2 corosync-pve: 2.3.5-2 libqb0: 1.0-1 pve-cluster: 4.0-29 qemu-server: 4.0-64 pve-firmware: 1.1-7 libpve-common-perl...

Ah, yes! I was missing no-subscription repositories. Thanks!: # PVE pve-no-subscription repository provided by proxmox.com, NOT recommended for production use deb http://download.proxmox.com/debian jessie pve-no-subscription

Trying to upgrade from 4.0 to 4.1, but I'm probably jumping some steps... My actual ProxMox version: pveversion -v proxmox-ve: 4.0-16 (running kernel: 4.2.2-1-pve) pve-manager: 4.0-48 (running version: 4.0-48/0d8559d0) pve-kernel-4.2.2-1-pve: 4.2.2-16 lvm2: 2.02.116-pve1 corosync-pve: 2.3.5-1...

There are some duplicated mac address, but I thought it was the right thing: the same mac is used for the network card and the correspondent vlan. Is not right? I post my ifconfig (with fake addresses) and route tables. Maybe some kind soul could look at it :-) eth0 Link encap:Ethernet...

Only ipv4 forwarding is active. Anyway, the problem is not related to proxmox, knockd or nothing else. The problem is caused because the ip associated to virtual bridge and ethernet card is not like I planned to be. Look at my network configuration (only the first two vlans): auto vmbr0...

Yes, usually I use -nnq switch, I don't know why I used extended form in my previous post. But I don't think it is important. No matter what open_p and close_p are doing (the problem is before), but yes, it is a standard form. You can use the "start_command" to activate a single iptables rule...

Thank you, but it is totally fake address.

Yep!? I'm using knockd version 0.5 of zeroflux.org which I found in the Debian Jessie repositories. Maybe is too old? I just see on zerflux site that the actual stable version is 0.7. But the syntax, for my version is correct. I go to try the last version. Thnak you

Yes. You can see above.