Search results

Hi, Maybe you can try to consolidate the snapshot into the original disk file and start it over again with a new standalone disk with all snapshots committed. https://stackoverflow.com/questions/22913384/transforming-qcows2-snapshot-plus-backing-file-into-standalone-image-file Regards,

I used GlusterFS last year on one of ours OpenStack Cluster, the performance is good while there is no problem on any brick node... my experience says that if you are going to use glusterfs with large RAW files, be aware that it will freeze your brain when a file-healing occurs at one of your...

Thanks, if possible, consider this feature for the future releases, would be great!!

Hi, There is any way to link firewall rules (security groups) based on POOL ? so, when we associate VMs as a member of a specific pool, the same firewall rules (security groups) created on parent pool, should be Inherited by those VMs. Thanks.

I think there is not such rule for this on any hypervisor... the CPU overcommit is something that is maybe OK for you but not for others, its depends on the workloads you have and the performance you expect for your environment. if you want to guarantee 100% allocation of vCPU processing for...

Hi, I would like your advises regarding enabling or not writeback cache on guest VMs.. We only use modern OSEs like, Centos 7, Centos 8, Ubuntu 16, WIndows 16/19... What are your recommendations with writeback cache enabled on proxmox guests? With these modern kernels, will be any chance of...

Yep!! just be in mind that for each -A rule you must have a -D rule to maintain the filter chain always clean.. (Append/Delete)

So, for now, the only way to manage iSCSI disks is through CLI ?

Not Really!! You have to use the REAL port (22) on FORWARD chain, not the prerouting port (2xxx). Your internal server does not listen on 2xxx, that's why you need to use the REAL port on FORWARD chain..

Everything is fine*, my only advice is to not publish port 23 for outside, this port is frequently used for a lot kind of attacks, like DoS, portScan, etc... modify it for anything like 2222. * Also, flushing the entire filter table of iptables on interface shutdown can lead to other side...

Just spend some time to understand how iptables works inside a linux box!!! You will need also some networking knowledge!! As an example, try this: iptables -t nat -A PREROUTING -p tcp --dport 80 -i vmbr0 -d 185.246.87.214 -j DNAT --to 10.0.0.15:80 iptables -A FORWARD -p tcp --dport 80 -i...

Glad to know that it solved your problem!!!

yes, it will always happen!! you have to fix it on /etc/sysctl.conf the file /etc/sysctl.conf on proxmox already have a sector explaining this: # Uncomment the next line to enable packet forwarding for IPv4 #net.ipv4.ip_forward=1

what happens if you traceroute to 8.8.8.8?

At least my nodes is not experiencing crashes after this!!! hope they correct the problem soon!! Cause we area a cloud company running hundred of VMs.. and not having the possibility to regain unused memory from guest is a waste of resources!!!

Yep, I turned off, and the errors disappeared, but in this case, I loose the dynamic memory feature!!!

are your nodes unstable also?

Yep, this is ok, but why the /dev/mapper/disk01 does not appear on DISKs tab of the proxmox node?

My understanding is that this line should do the JOB regarding the INTERNET access from guests... maybe the proxmox node is not allowing forwarding traffic or the routing is not enabled on sysctl.conf try this: on /etc/network/interfaces, add these lines below the other POSTROUTING rules...

Hi, I just configure a LUN-DISK over iscsi locally on proxmox node using multipathd and open-iscsi tools, but the disk does not appear under DISKs tab on proxmox gui. over ssh, I can see the LUN normally listed at /dev/mapper/disk01, can create PV,VG, etc... but cant see the disk listed under...